Skip to main content

IPV6 Configuration on Cisco Router:

Image
By
IPV6 Configuration on Cisco Router:            



By default Cisco Router was enabled with only IPv4 traffic we have to give the command "ipv6 unicast-routing" on the cisco router to enable IPv6 traffic in the Cisco router.

R1(config)#ipv6 unicast-routing
Next configure the IPv6 address on the Interface as shown in below.

R1(config)#int Gi0/0
R1(config-if)#ipv6 address 2001:0BB9:AABB:1234::1024/64
Configure the IPv6  global unicast address on an interface using the ipv6 address address/prefix-length [eui-64] command. If you omit omit the eui-64 parameter, you will need to configure the entire address manually. After you enter this command, the link local address will be automatically derived.
 or
R1(config-if)#ipv6 address 2001:0BB9:AABB:1234::/64 eui-64
To verify with the show command : show ipv6 int gi0/0

R1#show ipv6 interface Gi0/0
GigabitEthernet0/0 is up, line protocol is up
  IPv6 is enabled, link-local address is FE80::201:42FF:FE65:3E01
  No Virtual link-local address(es):
  Global unicast address(es):
    2001:BB9:AABB:1234:201:42FF:FE65:3E01, subnet is 2001:BB9:AABB:1234::/64 [EUI]
  Joined group address(es):
    FF02::1
    FF02::2
    FF02::1:FF65:3E01
  MTU is 1500 bytes
  ....
From the output above we can verify two things:

the link local IPv6 address has been automatically configured. Link local IP addresses begin with FE80::/10 and the interface ID is used for the rest of the address. Because the MAC address of the interface is 00:01:42:65:3E01, the calculated address is FE80::201:42FF:FE65:3E01.
the global IPv6 address has been created using the modified EUI-64 method. Remember that IPv6 global addresses begin with 2000::/3. So in our case, the IPv6 global address is 2001:BB9:AABB:1234:201:42FF:FE65:3E01.


                                                                                                                                    By
                                                                                                                        Sudhakar Ganapareddy

Popular posts from this blog

UPGRADING EOS in the ARISTA Switches

By
UPGRADING EOS in the ARISTA Switches: EOS is the Firmware for Arista Switches whereas IOS for Cisco. This blog post shows the detailed procedures to follow and to upgrade the EOS in the Arista Switches. This Post was supports for any platform or the Version you are going to upgrade in the Arista Switches. This Post was divided into three parts : Pre-Upgrade Process Upgrade Process Post-Upgrade Process PRE-UPGRADING-PROCESS: 1       1)        Check the Upgrade Path tool by clicking the below link. https://www.arista.com/en/support/mlag-portal/mlaglist and confirm it is in mlag issu compatible 2)       Check if the  STP agent is restartable by giving the command switch-1# show spanning-tree bridge detail | grep agent Stp agent restartable                      :      ...
Read more

Destination IP Address of DHCP

By
When DHCP starts the client has no idea about the network it’s currently on. Some clients may store the IP address they were previously on and send this out with the Discovery and Request packets, but the network is not truly set up until after the server has sent it’s final Ack message. Because of this the server does not know the network’s true broadcast address, however there is an address mapped for this very purpose. 255.255.255.255 If you run arp -a you will see that every interface has the following mapping 255.255.255.255 ff-ff-ff-ff-ff-ff static This means that just like a networks broadcast IP this message will be transmitted to all network adapters on the local network segment. The DHCP server listens for messages heading for port 67 UDP while the DHCP client listens for messages on port 68 UDP Lets lake a look at a DORA sequence in Wireshark 148 16.564069 0.0.0.0 255.255.255.255 DHCP 342 DHCP Discover - Transaction ID 0xaccba128 149 16.5...
Read more

Loadbalancing on Static Routes

By
If you have two routers / two Layer3 switches connected with two L3 links (two paths) you can route with two equal static routes towards the same prefix and the router will load balance traffic across both links. The idea is to make two same static routes on the same router but with different next-hops. The question was: Which link or which route will be used? And if the traffic will be load balanced, which mechanism will be used to share the traffic across both of links. ip route 10.0.0.0 255.0.0.0 192.168.10.2 ip route 10.0.0.0 255.0.0.0 192.168.11.2 If both routes have the same destination prefix and no different Administrative Distance is configured, both routes will get installed in the routing table. Routing table will then leave to the switching process the job of load-sharing. That is, route-cache mechanisms, CEF in case of Cisco device will do load-share per session using source-destination IP. MORE ABOUT THAT CEF Load-Balancing Overview CEF – Cisco E...
Read more