نمایش نتایج: از شماره 1 تا 2 از مجموع 2

موضوع: How to Implement IPv6 and Configure a Cisco Router to Use IPv6

  
  1. #1
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272

    How to Implement IPv6 and Configure a Cisco Router to Use IPv6

    کد:
    http://www.trainsignaltraining.com/ipv6-implementation/2010-05-20/

    Implementation of IPv6 is spreading across the globe and network professionals are put in the spotlight as this new protocol is added to their organization’s network infrastructure. The CCNA 604-802 exam requires candidates to have a good understanding of IPv6 and how to implement the protocol.
    In my previous article, IPv6 Addresses: Form and Function, we compared the structures of the IPv4 and IPv6 addresses and headers. We also examined the differences in the types of IPv4 and IPv6 addresses.
    In this article, we will take the next step and investigate what types of implementations are possible for IPv6 and how to assign an address to interface. Upcoming articles in this series will focus on some of the key features like mobility and IPSec and also look at configuring routing protocols to use IPv6.

    IPv6 Implementation Strategies

    There are four distinct methods to implement IPv6 in a network infrastructure:

    • Native Implementation
    • Dual Stack Implementation
    • IPv6 Tunneling
    • IPv6 Only to IPv4 Only Translation

    Let’s go over each of these in more detail.

    • IPv6 Native Implementation

    The first implementation method is to install IPv6 in a native configuration. This configuration configures all hosts and routers to utilize IPv6 only and not in conjunction with IPv4.
    Native implementation limits the network to only IPv6 communication to other networks and would require translation to interface other IPv4 networks.

    • IPv6 Dual Stack Implementation

    The second and most popular implementation is dual stack. Dual stack implementation allows IPv4 and IPv6 addresses to exist on the same physical and/or logical interface. This implementation is also the easiest to implement in an environment that already is established.
    The primary concerns for the dual stack implementation are in software and hardware. Hardware must be evaluated in the network infrastructure to see if there is proper memory for route tables and the switch forwarding tables to handle IPv6 routes and packets. Software on the network infrastructure must support IPv6 configuration and routing protocols, while operating systems on the host side must also be IPv6 capable.
    Dual stack offers the best of both worlds with hosts able to communicate with other hosts on networks that could support either protocol. Let’s take a look at what IPv4 only application stack looks like for data flow as depicted in Figure 1.


    So how would a dual stack implementation work? Well, Figure 2 shows how an application must be aware of both IP stacks to utilize either. Operating systems are configured to select which one will have priority if connectivity is available on the remote side for both protocols. If applications allow, like web browsers, IPv4 or IPv6 addresses can be manually selected.



    • IPv6 Tunneling

    The next implementation available for IPv6 is tunneling. Tunneling is used to connect two native IPv6 implementations over an existing IPv4 only network, which is typically seen as a WAN network.
    Edge routers for each IPv6 implementation are connected to the IPv4 network and a tunnel is configured between them. IPv6 original headers and payloads are not modified in the tunnel, but instead an IPv4 header is inserted in front of the IPv6 header for transmission over the IPv4 network and then stripped off on the other side.
    Figure 3 displays the implementation of this tunnel and communication between two IPv6 native environments.


    One of the most common tunnel protocols to use for this implementation is 6to4 and is defined in RFC 3056: Connection for IPv6 Domains via IPv4 Clouds. The 6to4 protocol supports a dynamic method to tunnel IPv6 addresses across IPv4 clouds and will utilize global unicast IPv6 prefixes for each IPv6 site for communication. 6to4 must be installed on the edge routers and will map addresses according to their global prefixes, so IPv6 route propagation to other sites is not needed.

    • IPv6 Only to IPv4 Only Translation

    IPv6 only to IPv4 only translation is the last implementation method we will examine. Why would we need this? Well, IPv6 nodes may require interaction with IPv4 only nodes for certain services such as: mail or web services.
    There are several ways to accomplish translation. The most commonly method used is Application Level Gateways (ALG), which utilizes a server that act as proxy to services that may be other IPv6 or IPv4 nodes. Figure 4 shows how this might be implemented.


    For ALGs to properly function the applications on the server must be IPv6 aware and the server must configured to support both protocols. The best location for the ALG is often identified by the location of the targeted services. For IPv6 nodes that require access, but offer no services to other IPv4 nodes, placing an ALG at the edge of the IPv6 network is the best location.
    Let’s look quickly at some other translation methods that could be employed. Other translation methods include NAT-PT, TCP-UDP relay, Bump in the Stack (BIS), Dual Stack Translation Mechanism (DSTM), and SOCKS-based IPV6/IPv4 gateway.

    • NAT is not favored for use with IPv6, but it does offer a mechanism to achieve connectivity to end IPv4 nodes.
    • TCP-UDP relay is similar to NAT-PT, but performs translation at the Transport Layer of the OSI stack and not the Network Layer.
    • BIS is designed to work with dual stack hosts and was used as an initial step for translation since many applications did not support IPv6.
    • DSTM allows dual stacked hosts in IPv6 only domains to communicate to other IPv4 hosts by dynamically creating tunnels for communication.
    • SOCKS-based IPv6/IPv4 gateway is based on the SOCKSv5 protocol and is a proxy mechanism to translate addresses.

    Translation between IPv6 and IPv4 is an advanced topic that requires more in depth study beyond the current CCNA scope and is taken up in more detail for CCNP candidates.

    Implementing IPv6 Addresses on Cisco Router Interfaces

    Now that we have talked about IPv6 implementation schemes, let’s look at how to implement IPv6 addresses on a router interface. Before this can be accomplished, you need to verify that the current version of IOS code on the Cisco router will support IPv6.
    Once you have logged into a router and entered enabled mode, type "show ipv6 ?" at the router prompt. If a syntax error occurs, the IOS version is not setup to support IPv6 and will need to be upgraded.
    To enable IPv6 on a router for configuration, IPv6 unicast routing and CEF forwarding will need to be enabled. Enter configuration mode on the router and type the following:
    Router (config) #ipv6 unicast-routing
    Router (config) #ipv6 cef distributed
    This will enable IPv6 to be statically configured for routes and on interfaces. Now let’s configure and interface with IPv6 address.
    Below is an example of a ten Gigabit Ethernet interface 2/1 that has a sub interface assigned. The designation of the interface is ten 2/1.1. IP address currently assigned to the interface is 192.168.100.1/30. A show interface gives us this result:
    Router# show interface ten 2/1.1
    TenGigabitEthernet2/1.1 is up, line protocol is up (connected)
    Hardware is C6k 10000Mb 802.3, address is 001c.b0b4.7400 (bia 001c.b0b4.7400)
    Description: “Interface 1″
    Internet address is 192.168.100.1/30
    MTU 9216 bytes, BW 10000000 Kbit, DLY 10 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation 802.1Q Virtual LAN, Vlan ID 501.
    ARP type: ARPA, ARP Timeout 04:00:00routert#sh int ten 2/1
    Now let’s enter configuration mode again and add ipv6 address.
    Router (config) #interface ten 2/1.1
    Router (config-subif) #ipv6 address FEC0:0:0:100::1/128
    We have now configured the interface with an IPv6 IP address, but to see the result and all the associated IPv6 types of addresses that were discussed in my previous article, a special show command is needed for the interface. The example below displays the IPv6 addresses assigned to the ten 2/1.1 interface:
    Router# show ipv6 interface ten 2/1.1
    TenGigabitEthernet2/1.1 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80::21C:B0FF:FEB4:7400
    Description: “Interface 1″
    Global unicast address(es):
    FEC0:0:0:100::1, subnet is FEC0:0:0:100::1/128
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::1:FF00:1
    FF02::1:FFB4:7400
    MTU is 9216 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    ND advertised reachable time is 0 milliseconds
    ND advertised retransmit interval is 0 milliseconds
    ND router advertisements are sent every 200 seconds
    ND router advertisements live for 1800 seconds
    Hosts use stateless autoconfig for addresses
    You can clearly see that interface has a link-local and a global unicast address. Also, the Joined group addresses define the multicast and anycast addresses also needed for our router interface using IPv6.

    What Did We Learn?

    In this article we looked at the various methods for implementing the IPv6 protocol and talked about how to configure a Cisco router interface to use IPv6.
    Understanding the implementations is an element for CCNA candidates to be aware of and so is IPv6 address assignment to router interfaces. These topics are basic building blocks overall IPv6 design and configuration and future articles will drill down into more features and configuration.
    IPv6 has some real complexity, but proper training and education can empower you with the tools to take full advantage of this protocol




    موضوعات مشابه:

  2. #2
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272

    IPv6 Addresses: Form & Function

    کد:
    http://www.trainsignaltraining.com/ipv6-addressing/2010-02-23/

    The transition to IPv6 will be one of the most important issues that network professionals will address in this new decade. As CCNA candidates, a solid understanding of the IPv6 protocol and how to use it in addition to IPv4 is essential. In my previous article, we examined the history of IPv6 and answered the question of Why is IPv6 needed?
    In this article, we will examine the structural differences between IPv4 and IPv6 and we’ll investigate the different types of IPv6 addresses and how they communicate.

    IPv4 vs. IPv6: Structure Comparison

    In my last IPv6 article, I mentioned that IPv4 addresses are 32 bits in length and IPv6 addresses are 128. The 32 bit structure of the address for IPv4 was designed to be represented as four separate octets, or sets of eight bits, separated by dots. The maximum range of values in each octet is seen to be 0-255.
    IPv6 addresses contain eight different fields, instead of octets, and each field consists of 16 bits. Due to their larger size, IPv6 addresses are noted using hexadecimal characters, not decimal as seen with IPv4. I would strongly advise reviewing hexadecimal notation (0-15 = 0-F) before doing anything with IPv6 (and for your CCNA exam), just as you would have reviewed binary notation for IPv4.
    Another important item to note about IPv6 addressing is the subnet mask identification. IPv4 could use the standard 255.x.x.x or the /xx CIDR of VLSM notation. IPv6 only uses the /xx notation for mask representation.

    The example in Figure 1 illustrates some of the structural differences you would see between IPv4 and IPv6 address.




    IPv6 addresses can also be compressed in size if certain conditions exist. If a field contains all zeroes, that field can be reduced to just one zero. In addition, if there are multiple fields adjacent to one another that have all zeroes, those fields can be displayed by on a “::” notation.
    It definitely can get confusing if you have multiple fields missing from the address, but there is an important point to remember. The compression to the “::” notation can only happen once in an address. You would be allowed to have a “::” and a few single 0 fields, but anything else is invalid.
    Figure 2 below shows two IPv6 addresses and the valid and invalid ways to compress them.




    Continuing with our comparison on structure, let’s dig deeper and look at the full IP address headers of IPv4 and IPv6. To best understand the header configurations, you may want to look up the corresponding Request for Comments (RFCs) that are posted by the IETF for topics that they wish to become standardized.
    RFC 791: Internet Protocol DARPA Internet Program Specification, defines the IPv4 header and description of the IP packet, while RFC 2460: Internet Protocol, Version 6(IPv6) Specification, describes the same for IPv6.
    Some of the IETFs RFCs are lengthy, often contain high level research discussion points, and can read like very bad stereo instructions, but careful reading can unlock a lot of useful information.
    The IP packet contains the IP header and a data payload. For IPv4, the IP header is a total of 20 bytes (160 bits), but this can be increased if the options field is used. The options field is variable in length and if a field does not equal an even 32 bits, padding is added to accommodate. A graphic of the IPv4 header is shown in Figure 3.


    Figure 3: IPv4 Header (click on image to expand)


    In contrast, IPv6 addresses utilize a fixed length of 40 octets (320 bits) and have been simplified in its format compared to the IPv4 version. The IPv4 options field has been replaced by extension headers, which were designed to provide more structure and easier processing for network devices.
    IPv6 addresses can contain zero, one, or multiple extension headers depending on the services the IP packet will be supporting. As you can from the structure of the IPv6 header graphic in Figure 4, a Next Header field identifies any headers that follow and this field is present in all extension headers, thus providing a defined chain.


    Figure 4: IPv6 Header (click on image to expand)


    Types of IPv6 Addresses

    Different types of IPv6 addresses are defined in RFC 2373: IP Version 6 Addressing Architecture. As we look at these address types, it is important to understand that unlike IPv4, IPv6 does not use Broadcasts in its communication and therefore, does not require network number and Broadcast addresses for each subnet.
    Much of the functions like ARP (Address Resolution Protocol) and other subnet only protocols are accomplished with different mechanisms that utilize Multicast or Anycast instead of Broadcast.
    Unlike IPv4, each host and router utilizing IPv6 will have multiple IPv6 addresses which are used for different functions. The address types seen with IPv6 are:

    • Link-Local
    • Global Unicast
    • Loopback
    • Multicast
    • Anycast

    IPv6 did contain a private address space called a Site-Local address, but this was removed from the IPv6 RFCs in 2004. The following tables describe the required addresses and their representation for hosts and routers.



    Putting the IPv6 Address Together

    We have talked about the representation of the IPv6 address compared to IPv6 and listed the different types of IPv6 addresses. Now let’s dig deeper into the formation of an IPv6 addresses.
    To illustrate this topic, I will use the Link-Local and Global Unicast addresses as examples.
    Link-Local addresses are used for communication between nodes on the same local link or subnet. Communication to the broader Internet requires the Global Unicast address. In IPv4 and IPv6, addresses can be subnetted down to very small groups, but the IETF has chosen that IPv6 addresses utilized in the broader Internet will use a 64 bit interface identifier or host id. This consumes the last half of the 128 bits of the IPv6 address.
    This same interface identifier is utilized for both the Link-Local and Global Unicast addresses on a network interface. The interface identifier can be configured manually or automatically utilizing the EUI-64 address. This address is a combination of a 24 bit manufacturer id provided by the IEEE and a 40 bit value given to the product by the manufacturer.
    Why consume so much of the address for host id you ask?
    The IETF structured the first block of 48 bits of the IPv6 address to utilize a very hierarchical structure for routing in the Internet and this block is often referred to as an IPv6 Global Prefix. The minimum subnet that can be assigned from a Regional Internet Registry (RIR) is /48. This leaves 16 bits of the first block of 64 bits of an IPv6 addresses to be used by a site or ISP for subnetting.
    Based on this format, the IETF believes that there will be enough addresses to support the world’s IP addressing needs for decades to come. An illustrated example of the structure of a Link-Local and a Global Uncast Address is shown in Figure 5.



    What Did We Learn?

    In this article, we investigated the differences between IPv4 and IPv6 addresses and reviewed the different ways to display an IPv6 address. In addition, we discuss some of the types of IPv6 addresses and what the format means.
    As you can see, there is a bit more complexity to IPv6 than IPv4, but also a great deal more structure and flexibility.
    In upcoming articles, I will explain some of the key features of IPv6 such as: stateless and stateful configuration, end-to-end encryption, and IP MTU discovery. I will also address how to implement this new protocol into your network and discuss what is needed for configuring IPv6 to use different routing protocols.
    IPv6 has a lot of promise, but new protocols like this often require a great deal of change in a network to properly implement and significant change is often feared. As we look at all the necessary requirements for implementation of IPv6, we will find that some of the fears we might have can be easily alleviated




کلمات کلیدی در جستجوها:

شبکه

ipv6

CISCO IPV6 ROUTER SUB-INTERFACE

برچسب برای این موضوع

مجوز های ارسال و ویرایش

  • شما نمی توانید موضوع جدید ارسال کنید
  • شما نمی توانید به پست ها پاسخ دهید
  • شما نمی توانید فایل پیوست ضمیمه کنید
  • شما نمی توانید پست های خود را ویرایش کنید
  •