CCNA 2 - Capitulo 8.3

CCNA 2 - Capitulo 8.3

1. DYNAMIC GUA ASSIGNMENT IPV6

   • STATEFULL
     • DHCPV6 - STATEFULL
       • FLAG RA MESSAGE
         • A - 0
           • INTRUCT THE CLIENT TO USE THE INFORMATION IN THE DHCPv6 STATEFUL SERVER
         • O - 0
           • INTRUCT THE CLIENT TO USE ADDITIONAL INFORMATIONS STATELESS DHCPv6
         • M - 1
           • HOST CLIENT OBTAIN ALL ADDRESSING INFORMATION FROM STATEFUL DHCPv6 SERVER
           • EXCEPT ? DEFAUL GATEWAY LLA OF THE RA
       • ENABLE STATEFULL DHCP INTERFACE
         • R1(CONFIG-IF)# IPV6 ND MANAGED-CONFIG-FLAG
         • R1(CONFIG-IF)#IPV6 ND PREFIX DEFAULT NO-AUTOCONFIG
           • DISABLE SLAAC
             • SET FLA A TO 0
         • THE HINGLIGHTED CONFIRMS THAT THE RA WILL TEL THE HOST OBATIN IPV6 FROM DHCPv6
       • SIMILAR DHCP V4
       • MAINTAINS IPV6 STATE INFORMATION.
       • DOES NOT REQUIRE SLAAC
       • DHCPv6 - RFC 3315
         • SERVER TO CLIENT UDP 546
         • CLIENT TO SERVER UDP 547
       • DHCPv6 STATEFULL / DHCP STETELESS
         • 1. THE HOST SENDS AN RS MESSAGE.
           • RECEIVED TO ALL IPV6-ENABLED ROUTERS
         • 2. THE ROUTER RESPONDS WITH AN RA MESSAGE.
           • ROUTER RECEIVES RS AND RESPONDS WITH RA
           • INDICATING THE CLIENT INITIATE COMMUNICATION WITH A DHCPv6 SERVER
         • 3. THE HOST SENDS A DHCPV6 SOLICIT MESSAGE.
           • CLIENT NOW NEEDS LOCATE A DHCPv6 SERVER AND SENDS A DHCPv6 SOLICIT TO THE
           • PV6 MULTICAST ALL-DHCPv6-SERVERS ADDRESS (FF02::1:2)
         • 4. THE DHCPV6 SERVER RESPONDS WITH AN ADVERTISE MESSAGE.
           • DHCPv6 SERVERS RESPOND WITH A DHCPv6 ADVERTISE UNICAST MESSAGE
         • 5. THE HOST RESPONDS TO THE DHCPV6 SERVER.
           • STATELESS DHCv6 CLIENT
             • CLIENT CREATES AN IPV6 ADDRESS USING THE PREFIX IN THE RA MESSAGE
             • CLIENT THEN SENDS A DHCP INFORMATION-REQUEST MESSAGE TO THE DHCPV6 SERVER
               • ADDITIONAL CONFIGURATION ( DNS SERVER )
           • STATEFUL DHCPv6 CLIENT
             • CLIENT SENDS A DHCPv6 SOLICIT MESSAGE
               • TO OBAIN ALL NECESSARY IPV6 CONFIGURATION PARAMETERS
         • 6. THE DHCPV6 SERVER SENDS A REPLY MESSAGE.
           • THE SERVER SENDS A DHCPV6 REPLY UNICAST MESSAGE TO THE CLIENT.
             • THE CONTENT OF THE MESSAGE VARIES DEPENDING ON IF IT IS REPLYING TO A REQUEST OR INFORMATION-REQUEST MESSAGE.
       • CHECK IF IT IS ENABLED IN THE INTERFACE
         • R1#SHOW IPV6 INTERFACE G0/0/1 | BEGIN ND
       • CONFIGURE DHCPv6 SERVER
         • CISCO IOS ROUTER CAN BE CONFIGURED TO PRIVEDE
           • STATEFUL DHCPv6 SERVER
             • 1 ) ENABLE IPV6 ROUTING
               • R1(CONFIG)#IPV6 UNICAST-ROUTING
               • JOINED GROUP ALL-ROUTERS - FF02:001
             • 2) DEFINE A DHCP POOL NAME
               • (CONFIG-IF)#IPV6 DHCP POOL NAME IPV6-STATEFULL
             • 3) CONFIGURE DHCPV6 POOL
               • R1(CONFIG-DHCPV6)#ADDRESS-PREFIX 2001:ABCD:DB8:ACAD:1::254
                 • POOL OF ADDRESSES TO BE ALLOCATED BY THE SERVER
               • R1(CONFIG-DHCPV6)#DNS-SERVER 2001:4860:4860::8888
               • R1(CONFIG-DHCPV6)#DOMAIN-NAME tecno.com
             • 4) BIND DHCPV6 POOL INTERFACE
               • R1(CONFIG-IF)IPV6 ND MANAGED-CONFIG-FLAG
               • R1(CONFIG-IF)#IPV6 ND PREFIX DEFAULT NO AUTOCONFIG
               • R1(CONFIG-DHCPV6)# IPV6 DHCP SERVER IPV6-STATELESS (POOL-NAME)
                 • BINDS THE DHCPv6 POOL TO THE INTERFACE
               • R1(CONFIG-IF)# IPV6 ADDRESS FE80 :: 1 LINK-LOCAL
               • R1(CONFIG-IF)# IPV6 ADDRESS 2001:DB8:ACAD:1 :: 1/64
             • ROUTER INTERFACE ACQUIRES IPV6 FROM DHCPv6 SERVER
           • STATEFUL DHCPv CLIENT
             • 1 ) ENABLE IPV6 ROUTING
               • R1(CONFIG)#IPV6 UNICAST-ROUTING
             • 2) CLIENT ROUTER CREATE LLA
               • R1(CONFIG-IF)IPV6 ENABLE
                 • LLA WITHOUT NEEDING A GUA
             • 3) CLIENT ROUTER USE DHCPV6
               • R1(CONFIG)#IPV6 ADDRESS DHCP
             • 4 ) VERIFY THAT THE CLIENT ROUTER IS ASSIGNED A GUA
               • R1#SHOW IPV6 INTERFACE BRIEF
             • 5 ) VERIFY THAT THE CLIENT ROUTER RECEIVED OTHER NECESSARY IPV4 INFORMATION
               • R3# SHOW IPV6 DHCP INTERFACE G0/0/1
           • DHCPv6 RELAY AGENT
             • WHEN DHCPv6 SERVER IS LOCATED ON A DIFFERENT NETWORK THAN THE CLIENT
             • ALWAYS INTERFACE FACING THE DHCPv6 CLIENTS
               • R1(CONFIG)# INTERFACE GIGABITETHERNET 0/0/1
             • SPECIFIES THE EGRESS INTERFACE. THE DHCPV6 SERVER EGRESS INTERFACE IS ONLY REQUIRED WHEN THE NEXT HOP IS A LINK-LOCAL ADDRESS (LLA).
               • R1(CONFIG-IF)# IPV6 DHCP RELAY DESTINATION 2001 :DB8 : ACAD:1 :: 2 G0/0/0
             • HOW VERIFY ?
               • R1#SHOW IPV6 DHCP INTERFACES
               • R1#SHOW IPV6 DHCP BINDING
       • VERIFICATION DHCPv6 SERVER COMMANDS
         • DISPLAY THE LLA AND GUA ASSGINED BY SERVER
           • R1#SHOW IPV6 DHCP BINDING
         • VERIFIES THA NAME OF POOL AND ITS PARAMETERS ; NUMBER OF ACTIVE CLIENTS
           • R1#SHOW IPV6 DHCP POOL