Task: Implementing IS-IS over IPv6 on IOS-XE and IOS-XR

All routers have been pre-configured with IPv4 and IPv6 addressing. As a network engineer for INE, you have
been assigned the following tasks to complete:

1. Configure IS-IS over IPv4 and IPv6 adjacency between R2 and R5 and between R1 and R5. R1 must be
configured as an L1/L2 router. R2 and R5 must be configured as an L1-only router. Area information is
given in the topology diagram. Ensure System ID is in the format of XXXX.XXXX.XXXX, where X is the
router number. Ensure the Loopback0 interface does not send hellos and no adjacency can be
established but the link is still advertised in ISIS. Ensure links only run the appropriate level of IS-IS
with the neighbors.

2. Configure IS-IS over IPv4 and IPv6 adjacency between R3 and R4. R3 and R4 must be configured as an
L2-only router. Area information is given in the topology diagram. Ensure System ID is in the format of
XXXX.XXXX.XXXX, where X is the router number. Ensure the Loopback0 interface does not send hellos
and no adjacency can be established but the link is still advertised in ISIS. Ensure links only run the
appropriate level of IS-IS with the neighbors.

3. Configure IS-IS over IPv4 and IPv6 adjacency between R6 and XR12 and between R6 and XR11. XR11
must be configured as an L1/L2 router. R6 and XR12 must be configured as an L1-only router. Area
information is given in the topology diagram. Ensure System ID is in the format of XXXX.XXXX.XXXX,
where X is the router number. Ensure the Loopback0 interface does not send hellos and no adjacency
can be established but the link is still advertised in ISIS. Ensure links only run the appropriate level of
IS-IS with the neighbors.

4. Configure inter-area IS-IS over IPv4 and IPv6 adjacency between R1 and R3 and between R1 and R4.
Configure inter-area IS-IS adjacency between R3 and XR11 and between R4 and XR11. Identify the
problem and fix the issue on XR11. Your task is complete when 150.2.2.2 and 150.12.12.12 can ping
each other and also when 2001:150:2:2::2 and 2001:150:12:12::12 can ping each other.

5. Configure IS-IS adjacency between R1 and R7 and between R8 and XR11. R7 and R8 must be
configured as an L2-only router. Area information is given in the topology diagram. Ensure System ID
is in the format of XXXX.XXXX.XXXX, where X is the router number. Ensure the Loopback0 interface of
R7 and R8 does not send hellos and no adjacency can be established but the link is still advertised in
ISIS. Your task is complete once R2 and XR12 can ping 150.7.7.7, 150.8.8.8, 2001:150:7:7::7, and
2001:150:8:8::8.
6. Ensure R2 can reach 150.7.7.7 and 2001:150:7:7::7 if the link between R1 and R3 and between R1 and
R4 goes down. Ensure XR12 can reach 150.8.8.8 and 2001:150:8:8::8 if the link between R3 and XR11
and between R4 and XR11 goes down.

7. Ensure only IPv6 traffic from 2001:150:2:2::2 to 2001:150:12:12::12 and reverse traffic from
2001:150:12:12::12 to 2001:150:2:2::2 takes the path as per the diagram below:

8. Configure BFD for ISIS over IPv6 between R1 and R3 so that if there is a failure of the link between
them, they begin reconvergence in less than one second.

1.

Solutions:

Based on the diagram the Area portion is 49.0005 and the system ID is based on the router number
which must be unique for every router. System ID is like the router-id in OSPF.

R1:

ipv6 unicast-routing

router isis 1

net 49.0005.1111.1111.1111.00

passive-interface Loopback0

is-type level-1-2

interface GigabitEthernet0/0

ip router isis 1
 ipv6 router isis 1

isis circuit-type level-1

R2:

ipv6 unicast-routing

router isis 1

net 49.0005.2222.2222.2222.00

passive-interface Loopback0

is-type level-1

interface GigabitEthernet0/2

ip router isis 1

ipv6 router isis 1

isis circuit-type level-1

R5:

ipv6 unicast-routing

router isis 1

net 49.0005.5555.5555.5555.00

passive-interface Loopback0

is-type level-1

interface GigabitEthernet0/0

ip router isis 1

ipv6 router isis 1

isis circuit-type level-1

interface GigabitEthernet0/2

ip router isis 1

ipv6 router isis 1

isis circuit-type level-1

2. Based on the diagram the Area portion is 49.0034 and the system ID is based on the router number
which must be unique for every router. System ID is like the router-id in OSPF.

R3:

ipv6 unicast-routing

router isis 1

net 49.0034.3333.3333.3333.00

passive-interface Loopback0

is-type level-2

interface GigabitEthernet0/0

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

R4:

ipv6 unicast-routing

router isis 1

net 49.0034.4444.4444.4444.00

passive-interface Loopback0

is-type level-2
 !

interface GigabitEthernet0/0

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

3. Based on the diagram the Area portion is 49.0006 and the system ID is based on the router number
which must be unique for every router. System ID is like the router-id in OSPF.

R6:

ipv6 unicast-routing

router isis 1

net 49.0006.6666.6666.6666.00

passive-interface Loopback0

is-type level-1

interface GigabitEthernet0/1

ip router isis 1

ipv6 router isis 1

isis circuit-type level-1

interface GigabitEthernet0/2

ip router isis 1

ipv6 router isis 1

isis circuit-type level-1

XR11:

router isis 1
 net 49.0006.1111.1111.1111.00

is-type level-1-2

address-family ipv6 unicast

single-topology

interface Loopback0

passive

address-family ipv4 unicast

address-family ipv6 unicast

interface GigabitEthernet0/0/0/2

address-family ipv4 unicast

address-family ipv6 unicast

circuit-type level-1

commit

XR12:

router isis 1

net 49.0006.1212.1212.1212.00

is-type level-1

address-family ipv6 unicast

single-topology

interface Loopback0

passive

address-family ipv4 unicast

address-family ipv6 unicast

circuit-type level-1

interface GigabitEthernet0/0/0/1
 address-family ipv4 unicast

address-family ipv6 unicast

circuit-type level-1

commit

4. Inter-Area IS-IS adjacency is always formed using L2 adjacency. Level 2 routes learned by the L1/L2
router is never advertised to an L1 router. A default route is generated by the L1 router towards the
closest L1/L2 router because the L1/L2 router sets the attached bit.

R1:

interface GigabitEthernet0/1

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

interface GigabitEthernet0/2

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

R3:

interface GigabitEthernet0/1

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

interface GigabitEthernet0/3

ip router isis 1

ipv6 router isis 1

R4:

interface GigabitEthernet0/1

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

interface GigabitEthernet0/2

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

XR11:

router isis 1

no net 49.0006.1111.1111.1111.00

net 49.0006.1111.1111.0011.00

interface GigabitEthernet0/0/0/1

address-family ipv4 unicast

address-family ipv6 unicast

circuit-type level-2

interface GigabitEthernet0/0/0/3

address-family ipv4 unicast

address-family ipv6 unicast

circuit-type level-2

commit
5. By default all Level-1 learned routes are automatically converted by the L1/L2 router to L2 routes and
advertised to L2 neighbors.

R1:

interface GigabitEthernet0/3

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

R7:

ipv6 unicast-routing

router isis 1

net 49.0005.7777.7777.7777.00

passive-interface Loopback0

is-type level-2

interface GigabitEthernet0/3

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

R8:

ipv6 unicast-routing

router isis 1

net 49.0006.8888.8888.8888.00

passive-interface Loopback0

is-type level-2
 !

interface GigabitEthernet0/4

ip router isis 1

ipv6 router isis 1

isis circuit-type level-2

XR11:

router isis 1

interface GigabitEthernet0/0/0/4

circuit-type level-2-only

address-family ipv4 unicast

address-family ipv6 unicast

commit

6. Route-leaking can be done by the L1/L2 router using redistribution on an IOS XE router and using the
propagate command on IOS XR. Route-leaking can also be used for path selection.

R1:

router isis 1

redistribute isis ip level-2 into level-1 route-map R7_V4_ROUTES

address-family ipv6 unicast

redistribute isis level-2 into level-1 distribute-list R7_ROUTES

route-map R7_V4_ROUTES permit 10

match ip address 1

access-list 1 permit 150.7.7.7

!
 ipv6 prefix-list R7_ROUTES permit 2001:150:7:7::7/128

XR11:

route-policy R8_V4_ROUTES

if destination in (150.8.8.8) then

pass

endif

end-policy

route-policy R8_V6_ROUTES

if destination in (2001:150:8:8::8) then

pass

endif

end-policy

router isis 1

address-family ipv4 unicast

propagate level 2 into level 1 route-policy R8_V4_ROUTES

address-family ipv6 unicast

propagate level 2 into level 1 route-policy R8_V6_ROUTES

commit

7. Since we need to change the path for only IPv6 addresses and not IPv4, we must enable multi-
topology.

R1:

router isis 1

metric-style wide
 address-family ipv6 unicast

multi-topology

interface GigabitEthernet0/2

isis ipv6 metric 30

R2:

router isis 1

metric-style wide

address-family ipv6 unicast

multi-topology

R3:

router isis 1

metric-style wide

address-family ipv6 unicast

multi-topology

interface GigabitEthernet0/3

isis ipv6 metric 30

R4:

router isis 1

metric-style wide

address-family ipv6 unicast

multi-topology

interface GigabitEthernet0/2

isis ipv6 metric 30

router isis 1

metric-style wide

address-family ipv6 unicast

multi-topology

R6:

router isis 1

metric-style wide

address-family ipv6 unicast

multi-topology

R7:

router isis 1

metric-style wide

address-family ipv6 unicast

multi-topology

R8:

router isis 1

metric-style wide

address-family ipv6 unicast

multi-topology

XR11:

router isis 1

address-family ipv4 unicast

metric-style wide

address-family ipv6 unicast

metric-style wide
 no single-topology

interface GigabitEthernet0/0/0/3

address-family ipv6 unicast

metric 30

commit

XR12:

router isis 1

address-family ipv4 unicast

metric-style wide

address-family ipv6 unicast

metric-style wide

no single-topology

commit

8. When R1 and R3 are configured as BFD adjacent neighbors, any link failure between them would be
detected in less than 1 second and ISIS adjacency would be torn down so that they can re-converge
using an alternate path.

R1:

interface GigabitEthernet0/1

bfd interval 250 min_rx 250 multiplier 3

isis ipv6 bfd

R3:

interface GigabitEthernet0/1

bfd interval 250 min_rx 250 multiplier 3

isis ipv6 bfd