Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 55

InterVLAN Routing

Implementing Cisco IP Switched Networks


(SWITCH) Foundation Learning Guide
SWITCH Chapter 5 Overview
• Given an enterprise network, design, implement,
and verify Inter-VLAN routing using an external
router or a multilayer switch using either switch
virtual interfaces or routed interfaces
• Understand Layer 3 EtherChannel and its
configuration
• Understand DHCP operation and its
implementation and verification in a given
enterprise network
Describe InterVLAN Routing
• Introduction to inter-VLAN routing
• Inter-VLAN routing with an external router
• Inter-VLAN routing with switch virtual
interfaces
• Routing with routed ports
• Configuring inter-VLAN routing using SVI and
routed ports
• Troubleshooting inter-VLAN routing
Introduction to Inter-VLAN routing

• VLANs isolate traffic to a defined broadcast domain and subnet,


network devices in different VLANs cannot communicate with
each other natively
Introduction to Inter-VLAN routing

• The following devices can provide Inter-VLAN routing:


– Any Layer 3 multilayer Catalyst Switch
– Any external router with an interface that support trunking
– Any external router or group of routers with separate interface in each vlan
Type of Layer 3 Interfaces
• Catalyst multilayer switches support three
different types of Layer 3 interfaces:
– Routed port

– Switch Virtual Interface (SVI)

– Bridge Virtual Interface (BVI)


Inter-VLAN Routing Using an External
Router
Configuring IVL routing using External
Router
Pro’s and Con’s of External Routers
IVL routing using Switch Virtual Interfaces
SVI vs External Router
Routing with Routed Ports
Configuring IVL with routing using SVI and
Routed Ports
Forwarding Path using SVI
Layer 3 EtherChannel
Layer 3 EtherChannel Configuration
Routing Protocol Configuration
Lab 6: IVL routing
Packet Tracer Based lab – Use revised “worksheet”
USE Cat 3560 for ALS1 and 2960 for ALS2
Individual worksheet submission with a signature
DHCP Overview
DHCP Implementation in Campus
Environment
DHCP Configuration
DHCP Operation
DHCP Relay
Static Routes
• Static routes defines explicit path between two routers. They are not
automatically updated which means you must manually reconfigure static routes
when network changes occur.
• Static routes use less bandwidth than dynamic routes.
• No CPU cycles are used to calculate and analyze routing updates.
• Static routes should be used in an environments where network traffic is
predictable and where the network design is simple.
• Static routes should not be used in a large network environment where it’s
constantly changing because static routes cannot react to network changes.
• Even though static routes are obsolete due to the high use of dynamic routes in a
network, some companies still implement static routes for special occasions.
• Static routes are also useful for specifying a gateway of last resort (a default route
which all un-routeable packets are sent).
Types of Static Routes

There are four types of static routes. The following


types of IPv4 and IPv6 static routes will be
discussed:
• Standard static route
• Default static route
• Summary static route
• Floating static route
Directly Connected Static Route
• You must specify only the output interface (the interface on which all
packets are sent to the destination network) in a directly connected static
route.
• The router assumes the destination is directly attached to the output
interface.

LAN-1
2001:DB8:2::1/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::1/64

Directly Connected

Directly Connected
Branch-1(config)# ipv6 route 2001:DB8:2::1/64 s0/0/1
Branch-1(config)# ipv6 route 2001:DB8:3::1/64 s0/0/1
Directly Connected Static Route
LAN-1
2001:DB8:2::1/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::1/64
Branch-1(config)# ipv6 route 2001:DB8:2::1/64 s0/0/1
Branch-1(config)# ipv6 route 2001:DB8:3::1/64 s0/0/1
Branch-1#show ipv6 route
(Output Omitted)
S 2001:DB8:2::/62 [1/0]
Directly Connected via ::, Serial0/0/1
S 2001:DB8:3::/62 [1/0]
via ::, Serial0/0/1
C 2001:DB8:A::2/127 [0/0]
via ::, Serial0/0/1
“L” in the routing table is a new L 2001:DB8:A::3/128 [0/0]
identifier which indicates the via ::, Serial0/0/1
specific address assigned to an C 2001:DB8:B::/127 [0/0]
interface, as opposed to “C” which via ::, Serial0/0/0
L 2001:DB8:B::/128 [0/0]
only displays
via ::, Serial0/0/0
the subnet. L FF00::/8 [0/0]
via ::, Null0
Branch-2#
Next Hop/Recursive Static Route
• In a next-hop static route, the IPv6 address of the neighboring router is
specified.
• The output interface is derived from the next hop.
• Before any packet is forwarded by router, the routing table process must
determine the exit interface to use to in order to forward the packet. This
causes the router to take a second look at the routing table to determine
the exit interface for the destination network.

LAN-1
2001:DB8:2::1/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::1/64

Next Hop/Recursive
Branch-1(config)# ipv6 route 2001:DB8:2::1/64 2001:DB8:A::2
Branch-1(config)# ipv6 route 2001:DB8:3::1/64 2001:DB8:A::2
Next Hop/Recursive Static Route
LAN-1
2001:DB8:2::1/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::1/64

Branch-1(config)# ipv6 route 2001:DB8:2::1/64 2001:DB8:A::2


Branch-1(config)# ipv6 route 2001:DB8:3::1/64 2001:DB8:A::2
Branch-1#show ipv6 route
(Output Omitted)
S 2001:DB8:2::/64 [1/0]
Next Hop/Recursive
via 2001:DB8:A::2
S 2001:DB8:3::/64 [1/0]
via 2001:DB8:A::2
C 2001:DB8:A::2/127 [0/0]
via ::, Serial0/0/1
L 2001:DB8:A::3/128 [0/0]
via ::, Serial0/0/1
C 2001:DB8:B::/127 [0/0]
via ::, Serial0/0/0
L 2001:DB8:B::/128 [0/0]
via ::, Serial0/0/0
L FF00::/8 [0/0]
via ::, Null0
Branch-2#
Fully Specified Static Route
• The output interface and the next-hop address are both used in a fully
specify static route.
• Used when the output interface is a multi-access interface and needs the
next-hop address to be identified.
• The next-hop must be directly attached to the specified output interface.

2001:DB8:A::4/64
G0/0 Branch-4

LAN-1
2001:DB8:2::1/64
G0/0 2001:DB8:A::2/64 2001:DB8:A::1/64
Branch-2
G0/0 DSW-1 G0/0
Branch-1
G0/1

LAN-2
G0/0
2001:DB8:3::1/64
2001:DB8:A::3/64
Branch-3

Branch-1(config)# ipv6 route 2001:DB8:2::1/64 g0/0 2001:DB8:A::2


Fully Specified Branch-1(config)# ipv6 route 2001:DB8:3::1/64 g0/0 2001:DB8:A::2
Fully Specified Static Route Output
2001:DB8:A::4/64
G0/0 Branch-4

LAN-1
2001:DB8:2::1/64
G0/0 2001:DB8:A::2/64 2001:DB8:A::1/64
Branch-2
G0/0 DSW-1 G0/0
Branch-1
G0/1

LAN-2
G0/0
2001:DB8:3::1/64
2001:DB8:A::3/64
Branch-3

Branch-1#show ipv6 route


(Output Omitted)
S 2001:DB8:2::1/64 [1/0]
Fully Specified via 2001:DB8:A::2, Gigabit0/0
S 2001:DB8:3::1/64 [1/0]
via 2001:DB8:A::2, Gigabit0/0
C 2001:DB8:A::2/127 [0/0]
via ::, Serial0/0/1
L 2001:DB8:A::3/128 [0/0]
via ::, Serial0/0/1
C 2001:DB8:B::/127 [0/0]
via ::, Serial0/0/0
L 2001:DB8:B::/128 [0/0]
via ::, Serial0/0/0
L FF00::/8 [0/0]
via ::, Null0
Branch-2#
Default Static Route
• No other routes in the routing table match the packet destination IP address.
In other words, when a more specific match does not exist.
• A common use is when connecting a company's edge router to the ISP’s
network.

LAN-1
2001:DB8:2::1/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::1/64

Branch-1(config)#ipv6 route ::/0 s0/0/0


Branch-1(config)#ipv6 route ::/0 2001:DB8:A::2
Branch-1(config)#ipv6 route ::/0 s0/0/0 2001:DB8:A::2
Default Static Route
LAN-1
2001:DB8:2::1/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::1/64

Branch-1(config)#ipv6 route ::/0 s0/0/0


Branch-1#sh ipv6 route
(Output Omitted)
Default Route S ::/0 [1/0]
via ::, Serial0/0/0
S 2001:DB8:2::1/64 [1/0]
via 2001:DB8:A::2, Serial0/0/1
S 2001:DB8:3::1/64 [1/0]
via 2001:DB8:A::2, Serial0/0/1
C 2001:DB8:A::2/127 [0/0]
via ::, Serial0/0/1
L 2001:DB8:A::3/128 [0/0]
via ::, Serial0/0/1
C 2001:DB8:B::/127 [0/0]
via ::, Serial0/0/0
L 2001:DB8:B::/128 [0/0]
via ::, Serial0/0/0
L FF00::/8 [0/0]
via ::, Null0
Branch-1#
Summary Route
• Summary routes are used to reduce the number of routing table entries.
• Multiple static routes can be summarized into a single static route if:
– - The destination networks are contiguous and can
be summarized into a single network address.
– - The multiple static routes all use the same exit
interface or next-hop IP address.
LAN-1
2001:DB8:2::1/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::1/64
Summary Route
LAN-1
2001:DB8:2::/64 2001:DB8:A::2/127
S0/0/0
S0/0/1 S0/0/0 Internet
Branch-2 2001:DB8:A::3/127 Branch-1

LAN-2
2001:DB8:3::/64
Branch-1(config)#ipv6 route 2001:DB8:2::/46 s0/0/0

Common Bits
2001:DB8:0000000000000010
2001:DB8:0000000000000011
Summarize based on common bits:
• 16-bits in the 1st and 2nd hextets for a total of 32-bits
• 14-bits in the 3rd hextet
• Total of 46-bits in common between the two addresses
Branch-1#show ipv6 route Branch-1# ping 2001:db8:2::1
(output omitted) Type escape sequence to abort.
S ::/0 [1/0] Sending 5, 100-byte ICMP Echos to 2001:db8:2::, timeout is 2 seconds:
via ::, Serial0/0/0 !!!!!
S 2001:DB8::/46 [1/0] Success rate is 100 percent (5/5), round-trip min/avg/max = 1/10/41 ms
via ::, Serial0/0/1 Branch-1# ping 2001:db8:3::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:db8:3::, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/9/18 ms
Branch-1#
Floating Static Route
• A floating static route is a static route that the router uses to back up
dynamic route.
• You must configure a floating static route with a higher administrative
distance than the dynamic route that it backs up.
• In this instance, the router prefers a dynamic route to a floating static
route. You can use a floating static route as a replacement if the dynamic
route is lost.

col 200
roto 1 : DB
ti ng P 8 : B:
: 1 /1
Rou 27
S0/

Branch-1
S0/0
/0
S0/0/1
Internet 0 /0

/ 1 Branch-2
Floa S0/0
ting 27
Stati : 1 /1
c Ro
ute D B8: A :
01 :
20
Floating Static Route
col 200
P roto 1 : DB
ti ng 8 : B:
Rou : 1 /1
27
S0/

Branch-1
S0/0
/0
S0/0/1
Internet 0 /0

/ 1 Branch-2
S0/0
Floa 12 7
ting 1/
Stati
c Ro B8 : A ::
ute
20 0 1 :D

Branch-1(config)# ipv6 route 2001:DB8:4::1/127 s0/0/1 91


Branch-1(config)# ipv6 route 2001:DB8:5::1/127 s0/0/1 91
Branch-1(config)# ipv6 route 2001:DB8:6::1/127 s0/0/1 91
Branch-1(config)# ipv6 route 2001:DB8:C::1/127 s0/0/1 91
Branch-1(config)# ipv6 route 2001:DB8:A::1/127 s0/0/1 91

Branch-1#sh ipv6 route Branch-1#show ipv6 route


(output omitted)
(output omitted)
D 2001:DB8:4::/128 [90/3321856]
S 2001:DB8:4::/128 [91/0]
via FE80::2E0:8FFF:FE31:4201, Serial0/0/0
via ::, Serial0/0/1
D 2001:DB8:5::/128 [90/3321856]
S 2001:DB8:5::/128 [91/0]
via FE80::2E0:8FFF:FE31:4201, Serial0/0/0
via ::, Serial0/0/1
D 2001:DB8:6::/128 [90/3321856] S 2001:DB8:6::/128 [91/0]
via FE80::2E0:8FFF:FE31:4201, Serial0/0/0
via ::, Serial0/0/1
D 2001:DB8:B::/127 [90/3193856]
S 2001:DB8:A::/128 [91/0]
via FE80::2E0:8FFF:FE31:4201, Serial0/0/0
via ::, Serial0/0/1
D 2001:DB8:C::/127 [90/2681856]
S 2001:DB8:C::/128 [91/0]
via FE80::2E0:8FFF:FE31:4201, Serial0/0/0 Branch-1#
Branch-1#
Stateful DHCPv6
• In Stateful DHCP, the adddress assignment is centrally managed
and clients must obtain configuration information such as address
autoconfiguration and neighbor discovery that is not available
through protocols.
• DHCPv6 can be implemented in two ways
- Rapid Commit - DHCP client obtains configuration parameters from the
server through a rapid two message exchange (solicit and reply).
- Normal Commit - DHCP client uses four message exchanges (solicit,
advertise, request and reply).

• By default normal-commit is used.


• In order to use the rapid-commit option, it has to be enabled by
both client and server so that it uses the two-message exchange.

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 38
Stateless Address Autoconfiguration
(SLAAC)
• Requires no manual configuration of hosts, minimal (if any)
configuration of routers, and no additional servers.
• DHCP clients autoconfigure their own IPv6 address based on router
advertisements. Routers advertise prefixes that identify the subnet(s)
associated with a link, while hosts generate an "interface identifier" that
uniquely identifies an interface on a subnet.
• DHCP clients uses the DHCP server to obtain the other useful
configuration information (such as the address of DNS servers).
• By using the eui-64 command, a host can automatically assign itself
a unique 64-bit IPv6 interface identifier without the need for manual
configuration or DHCP.
• This approach is used when a network is not concerned with the
exact addresses hosts use on a network so long as they are unique
and routable.
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 39
DHCPv6 Message Types
DHCPv6 Message DHCPv4 Message
Types Types
SOLICIT(1) DHCPDISCOVER
Used to locate DHCP Servers
ADVERTISE(2) DHCPOFFER
Sent by servers to indicate that it is
REQUEST (3), RENEW DHCPREQUEST available for DHCP service.
(5), REBIND (6)
Sent by hosts to request addressing
REPLY (7) DHCPACK/DHCPNAK information from the server, renew
an old IP address and extend the
RELEASE (8) DHCPRELEASE lifetime of an address.
INFORMATION- DHCPINFORM
REQUEST (11)
DECLINE (9 DHCPDECLINE
CONFIRM (4) None
RECONFIGURE (10) DHCPFORCERENEW
RELAY-FORW (12), None
RELAY-REPLY (13)

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 40
DHCPv6 Message Types
DHCPv6 Message DHCPv4 Message
Types Types
SOLICIT(1) DHCPDISCOVER
Sent by the server containing
ADVERTISE(2) DHCPOFFER address configuration.
REQUEST (3), RENEW DHCPREQUEST
(5), REBIND (6) Sent by hosts to indicate that the
host will no longer use an address.
REPLY (7) DHCPACK/DHCPNAK Sent by hosts to request
configuration parameters without the
RELEASE (8) DHCPRELEASE
assignment of any address to the
INFORMATION- DHCPINFORM client.
REQUEST (11)
Sent by hosts to deny updates sent
DECLINE (9 DHCPDECLINE
from the server.
CONFIRM (4) None
Sent by the server to inform
RECONFIGURE (10) DHCPFORCERENEW clients of changes in addressing
RELAY-FORW (12), None configuration.
RELAY-REPLY (13)

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 41
DHCPv6 Messages Types
• There are 3 DHCPv6 message types exclusive to only DHCPv6:
- CONFIRM (4)
A client sends a Confirm message to any available server to determine
whether the addresses it was assigned are still appropriate to the link
to which the client is connected.
- RELAY-FORW (12)
A relay agent sends a Relay-forward message to relay messages to
servers, either directly or through another relay agent.
- RELAY-REPL (13)
A server sends a Relay-reply message to a relay agent containing a
message that the relay agent delivers to a client.

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 42
Stateful DHCPv6 Server Configuration
Example 1
Client Server
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2 Link-Local FE80::1

• The ipv6 dhcp pool command creates a pool and enters the router in DHCPv6
configuration mode.
• The address command is used to indicate the pool of addresses to be allocated
by the server. The lifetime option indicates the valid and preferred lease times in
seconds.
• The ipv6 dhcp server interface command binds the DHCPv6 pool to the
interface.
• The M flag needs to be changed from 0 to 1 using the interface command ipv6
nd managed-config-flag.

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 43
Stateful DHCPv6 Server Configuration
Client Server
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2 Link-Local FE80::1

R1(config)#ipv6 unicast-routing
R1(config)#ipv6 dhcp pool Stateful_DHCP
R1(config-dhcpv6)#address prefix 2001:DB8:acad:1::/64 lifetime infinite infinite
R1(config-dhcpv6)#dns-server AAAA:BBBB:CCCC:DDDD::FFFF
R1(config-dhcpv6)#domain-name StatefulDHCP.com
R1(config-dhcpv6)#exit
R1(config)#interface s0/0/0
R1(config-if)#ipv6 address 2001:db8:acad:1::1/64
R1(config-if)#ipv6 dhcp server Stateful_DHCP
R1(config-if)#ipv6 nd managed-config-flag

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 44
Stateful DHCPv6 Client Configuration
• The ipv6 enable interface command allow the router to receive a link-
local address in order to send RS messages and participate in DHCPv6.
• The ipv6 address dhcp interface command enables the router as a
DHCPv6 client on this interface.

R2(config)#interface s0/0/0
R2(config-if)#ipv6 enable
R2(config-if)#ipv6 address dhcp

Client Server
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2 Link-Local FE80::1

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 45
Stateful DHCPv6 Server Verification
R1#show ipv6 dhcp pool
DHCPv6 pool: Stateful_DHCP
Address allocation prefix: 2001:DB8:ACAD:1::/64 valid
4294967295 preferred 4294967295 (1 in use, 0 conflicts)
DNS server: AAAA:BBBB:CCCC:DDDD::FFFF
Domain name: StatefulDHCP.com
Active clients: 1

• The show ipv6 dhcp pool command verifies the name of the DHCPv6 pool and
its parameters. The number of active clients is 1, which reflects client R2
receiving its IPv6 global unicast address from this server.
• The show ipv6 dhcp binding command, displays the automatic binding between
the link-local address of the client and the address assigned by the server.

R1#show ipv6 dhcp binding


Client: FE80::2
DUID: 000300016C2056EC6F18
Username : unassigned
IA NA: IA ID 0x00070001, T1 43200, T2 69120
Address: 2001:DB8:ACAD:1:2CFA:91CC:C683:D1F5
preferred lifetime INFINITY, , valid lifetime INFINITY,

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 46
Stateful DHCPv6 Client Verification
Client Server
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2 Link-Local FE80::1

R2#show ipv6 dhcp interface


Serial0/0/0 is in client mode
Prefix State is IDLE
Address State is OPEN
Renew for address will be sent in 11:59:44
List of known servers:
Reachable via address: FE80::1
DUID: 000300016C2056FF38A0
Preference: 0
Configuration parameters:
IA NA: IA ID 0x00070001, T1 43200, T2 69120
Address: 2001:DB8:ACAD:1:B0A4:64F:CA3F:FA2D/128
preferred lifetime INFINITY, valid lifetime INFINITY
DNS server: AAAA:BBBB:CCCC:DDDD::FFFF
Domain name: StatefulDHCP.com
Information refresh time: 0
Prefix Rapid-Commit: disabled
Address Rapid-Commit: disabled

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 47
DHCPv6 Configuration Example 2
Server
Client Link-Local FE80::1
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2

R1(config)#ipv6 unicast-routing
R1(config)#ipv6 dhcp pool MY_DHCP_POOL
R1(config-dhcpv6)#address prefix 2001:DB8:cc1e:1::/64 lifetime infinite infinite
R1(config-dhcpv6)#dns-server AAAA:BBBB:CCCC:DDDD::FFFF
R1(config-dhcpv6)#domain-name HOSTdhcp.com
R1(config-dhcpv6)#exit
R1(config)#interface g0/0
R1(config-if)#ipv6 address 2001:db8:cc1e:1::/64 DHCP Host
R1(config-if)#ipv6 dhcp server MY_DHCP_POOL
R1(config-if)#ipv6 nd managed-config-flag

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 48
DHCPv6 Host Verification
Server
Client Link-Local FE80::1
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2

DHCP Host

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 49
Stateless DHCPv6
• During the SLAAC process, the client receives information to create an
IPv6 global unicast address. This includes the default gateway
information from the source IPv6 address in the RA message, which is
the link-local address of the router. A stateless DHCPv6 server can be
used to provide information that might not be included in the RA
message (DNS server address and the domain name).
• The ipv6 dhcp server interface command binds the DHCPv6
pool to the interface.
• The O flag needs to be changed from 0 to 1 using the interface
command ipv6 nd other-config-flag.
Client Server
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2 Link-Local FE80::1

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 50
Stateless DHCPv6 Server Configuration
Client Server
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2 Link-Local FE80::1

R1(config)#ipv6 unicast-routing
R1(config)#ipv6 dhcp pool Stateless_DHCP
R1(config-dhcpv6)#dns-server AAAA:BBBB:CCCC:DDDD::FFFF
R1(config-dhcpv6)#domain-name StatelessDHCP.com
R1(config-dhcpv6)#exit
R1(config)#interface s0/0/0
R1(config-if)#ipv6 address 2001:db8:acad:1::1/64
R1(config-if)#ipv6 dhcp server Stateless_DHCP
R1(config-if)#ipv6 nd other-config-flag

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 51
Stateless DHCPv6 Client Configuration
Client Server
2001:DB8:ACAD:1::/64
S0/0/0
S0/0/0
R2 R1
Link-Local FE80::2 Link-Local FE80::1

R2(config)#interface s0/0/0
R2(config-if)#ipv6 enable
R2(config-if)#ipv6 address autoconfig

• The ipv6 enable command is used because the router does not
have a global unicast address.
• The ipv6 address autoconfig command enables automatic
configuration of IPv6 addressing using SLAAC.

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 52
Stateless DHCPv6 Verification
R2#show ipv6 interface s0/0/0
Serial0/0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::2
No Virtual link-local address(es):
Stateless address autoconfig enabled
Global unicast address(es):
2001:DB8:ACAD:1::2, subnet is 2001:DB8:ACAD:1::/64 [EUI/CAL/PRE]
valid lifetime 2591259 preferred lifetime 604059
Joined group address(es):
FF02::1
FF02::1:FF00:2
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 53
Summary
• Questions??
Lab 7: DHCPv4v6 Lab
Group work individual submission of the
worksheet with signature

You might also like