Sie sind auf Seite 1von 64

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Alcatel-Lucent Interior Routing Protocols Lab Guide

Alcatel-Lucent Interior Routing Protocols Lab Guide

Revision 2.3 Sep 22nd, 2010

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Table of Contents LAB 1 INITIAL LAB

Table of Contents

LAB 1 INITIAL LAB TOPOLOGY CONFIGURATION

LAB 2 CONFIGURING STATIC AND DEFAULT ROUTES

LAB 3 SPF PATH SELECTION

LAB 4 CONFIGURING OSPF IN A SINGLE AREA

LAB 5 CONFIGURING OSPF FOR MULTIPLE AREAS AND SUMMARIZATION

LAB 6 CONFIGURING IS-IS FOR A SINGLE AREA

LAB 7 ROUTE REDISTRIBUTION

APPENDIX A ANSWERS TO LAB QUESTIONS

APPENDIX B LAB SOLUTIONS

List of Figures

Figure 1-1: Physical connectivity

Figure 1-2: Internal view of one pod

Figure 2-1: Pod physical connectivity

Figure 2-2: Physical connectivity

Figure 2-3: Physical connectivity

Figure 2-4: Physical connectivity

Figure 3.1: SPF Path Selection

Figure 4-1: OSPF single area

Figure 4-2: Physical Connectivity

Figure 4-3: VPLS Connection

Figure 4-4: VPLS Configuration

Figure 5-1: Multi-area OSPF

Figure 5-2: OSPF Virtual link

Figure 6-1: IS-IS Single area network

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

4

12

20

21

29

39

51

54

58

5

8

13

14

15

17

20

22

25

25

26

30

37

40

2

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 6-2: Physical Connectivity

Figure 6-3: ISIS VPLS Connection

Figure 6-4: ISIS VPLS Configuration

Figure 6-5: IS-IS multiple area network

Figure 7-1: Route redistribution

List of Tables

Table 1-1: Lab 1 commands

Table 1-2: Router remote access addresses

Table 1-3: Initial router parameters

Table 1-4: Router system IP addresses

Table 1-5: Core IP addresses

Table 1-6: IP addressing and labels

Table 2-1: Lab 2 commands

Table 2-2: Pod connectivity

Table 2-3: Pod connectivity

Table 3.1: SPF Path Selection

Table 4-1: Lab 4 commands

Table 5-1: Lab 5 commands

Table 6-1: Lab 6 commands

Table 8-1: Lab verification commands

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

44

44

45

47

51

4

5

6

7

7

10

12

16

18

20

21

29

39

58

3

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Lab 1 Initial Lab Topology Configuration Objective:

Lab 1 Initial Lab Topology Configuration

Objective:

Develop an IP addressing plan for the lab topology and configure routers interfaces according to figure 1.1.

Syntax

The commands required for this exercise are listed in Table 1-1. Each command may have additional possible parameters. Use the “?” character for help and to explore all command line options.

Lab 1 configuration commands

telnet

admin display-config

system name <name>

configure router interface <name> address <address>

configure router interface <name> loopback

configure router interface <name> port <port>

admin save

Table 1-1: Lab 1 commands

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

4

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Figure 1-1: Physical connectivity Pod number Router

Figure 1-1: Physical connectivity

Pod number

Router name

Connect address

Pod 1 Core Edge

Core-Pod1

 

Edge-Pod1

 

Access

Access-Pod1

 

Pod 2 Core Edge

Core-Pod2

 

Edge-Pod2

 

Access

Access-Pod2

 

Pod 3 Core Edge

Core-Pod3

 

Edge-Pod3

 

Access

Access-Pod3

 

Pod 4 Core Edge

Core-Pod4

 

Edge-Pod4

 

Access

Access-Pod4

 

Table 1-2: Router remote access addresses

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

5

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 1.1 Physical connectivity Objective: Verify the

Exercise 1.1 Physical connectivity

Objective:

Verify the operation and physical connectivity of the routers, which are connected according to Figure 1-1.

Exercise

1. Together with your instructor and other class members, develop on the whiteboard a consistent IP address plan for the lab, following the guidelines in Tables 1-3 to 1-5.

2. Connect to the routers in your pod using the addresses provided by your instructor. Fill in the required fields for Table 1-2. The username and password for all devices is “admin”. If you are unable to connect to any of the routers, notify your instructor.

3. Verify that the router has no configuration. Note: If a prior configuration is on your router, you need to remove it before starting this lab. If you are unsure how to accomplish this, ask your instructor.

Verification

1. Determine if you can connect to your routers.

2. Ensure that the router has no residual configuration on it.

Parameter

Value

Pod number

1, 2, 3, or 4 (circle your pod number)

System IP address

Pod IP address/32 (see Table 1-4 for addresses)

Pod 1 IP addressing range

172.16.0.0/16

Pod 2 IP addressing range

172.17.0.0/16

Pod 3 IP addressing range

172.18.0.0/16

Pod 4 IP addressing range

172.19.0.0/16

Core IP addressing range

172.31.0.0/16 (see Table 1-5 for addresses)

Loopback interfaces of core router

Pod IP address/32

Loopback interfaces of edge router

Pod IP address/32

Table 1-3: Initial router parameters

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

6

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Pod component

IP address

Pod 1 core system

172.16.1.1/32

Pod 1 edge system

172.16.254.1/32

Pod 1 Access system

172.16.253.1/32

Pod 2 core system

172.17.1.1/32

Pod 2 edge system

172.17.254.1/32

Pod 2 Access system

172.17.253.1/32

Pod 3 core system

172.18.1.1/32

Pod 3 edge system

172.18.254.1/32

Pod 3 Access system

172.18.253.1/32

Pod 4 core system

172.19.1.1/32

Pod 4 edge system

172.19.254.1/32

Pod 4 Access system

172.19.253.1/32

Table 1-4: Router system IP addresses

Pod connection

IP address

Pod 1 to Pod 2

172.31.1.1/30

Pod 1 to Pod 3

 

Pod 1 to Pod 4

 

Pod 2 to Pod 1

 

Pod 2 to Pod 3

 

Pod 2 to Pod 4

 

Pod 3 to Pod 1

 

Pod 3 to Pod 2

 

Pod 3 to Pod 4

 

Pod 4 to Pod 1

 

Pod 4 to Pod 2

 

Pod 4 to Pod 3

 

Table 1-5: Core IP addresses

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

7

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 1.2 Connectivity Objective Configure the interfaces

Exercise 1.2 Connectivity

Objective

Configure the interfaces and IP addressing in your pod.

Configure the interfaces and IP addressing in your pod. Figure 1-2: Internal view of one pod

Figure 1-2: Internal view of one pod

Exercise

Configure the routers in your assigned pod, using the address plan developed in Exercise 1.1.

1. Name each router, if not already named with the naming convention shown in Figure 1-2.

echo "System Configuration"

#--------------------------------------------------

name "Core1-Pod1"

exit

2. Configure each pod router with a system interface and a minimum of two loopback interfaces.

3. Configure the Ethernet connection between pod routers.

4. Configure IP addresses on all internal interfaces and the Ethernet connections between pods.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

8

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

5. Make sure that your IP subnetting is consistent.

echo "IP Configuration"

#--------------------------------------------------

interface "C1_C2" address 172.31.1.1/30 port 1/1/2

exit interface "C1_C3" address 172.31.2.1/30 port 1/1/3

exit interface "C1_C4" address 172.31.3.1/30 port 1/1/4

exit interface "C_E1" address 172.16.2.1/30 port 1/1/1

exit interface "loopback1" address 172.16.1.2/32 loopback

exit interface "loopback2" address 172.16.1.3/32 loopback exit interface "system" address 172.16.1.1/32

exit

----------------------------------------------

Verification

1. Verify that all required interfaces are active and operational.

2. On the core router, ensure that you have configured the following interfaces with IP addressing:

Three core interfaces with an IP address starting with 172.31.X.Y/30

One system IP address from your pod IP address range

Two loopback IP addresses from your pod IP address range

One Ethernet IP address that connects to your edge router

3. On the edge router, ensure that you have configured the following interfaces with IP addressing:

Two Ethernet IP address that connect to your core and access routers

Two loopback IP addresses from your pod IP address range

One system IP address from your pod IP address range

4. On the Access router, ensure that you have configured the following interfaces with IP addressing:

One Ethernet IP address that connects to your Edge router

Two loopback IP addresses from your pod IP address range

One system IP address from your pod IP address range

5. You should be able to ping between the core and edge routers and the access routers on the physical interface, directly connecting the two together, and between the core routers on the segments that interconnect them.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

9

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute 6. Complete Table 1-6 for your pod.

6. Complete Table 1-6 for your pod. Use this table in the subsequent labs: each interface should be associated with an IP address. This addressing will not vary in future labs, so you need to be familiar with it.

Router

Interface

IP address

Mask

Port number

Core

System

 

255.255.255.255

System

Core

Loopback 1

 

255.255.255.255

Loopback

Core

Loopback 2

 

255.255.255.255

Loopback

Core

Ethernet to edge

 

255.255.255.252

 

Core

To Core pod:

 

255.255.255.252

 

Core

To Core pod:

 

255.255.255.252

 

Core

To Core pod:

 

255.255.255.252

 

Edge

System

 

255.255.255.255

System

Edge

Loopback 1

 

255.255.255.255

Loopback

Edge

Loopback 2

 

255.255.255.255

Loopback

Edge

Ethernet to Access

 

255.255.255.252

 

Edge

Ethernet to core

 

255.255.255.252

 

Access

System

 

255.255.255.255

System

Access

Loopback 1

 

255.255.255.255

Loopback

Access

Loopback 2

 

255.255.255.255

Loopback

Access

Ethernet to Edge

 

255.255.255.252

 

Table 1-6: IP addressing and labels

Bonus Step

If time permits, you may configure additional loopback interfaces on the routers in your pod. Use the next available subnets from your defined range.

Questions

1. Which command is used to ensure all ports are active?

2. Which command can be used to determine the naming convention for the interfaces?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

10

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Notes

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

11

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Lab 2 Configuring Static and Default Routes

Lab 2 Configuring Static and Default Routes

Objective

Configure and verify direct, floating, and black-hole static routes between routers

Syntax

The commands required for this exercise are listed in Table 2-1. See Module 2, Static Routing and Default Routes, for more information. Each command may have additional possible parameters. Use the “?” character for help and to explore all command line options. Other commands may also be used, including those from previous courses.

Lab 2 configuration commands

telnet

admin display-config

configure router static-route <remote network/mask> next-hop <next-hop-address> {preference} <value>

Configure port 1/1/X shutdown

Configure port 1/1/X no shutdown

trace <ip-address>

ping <ip-address>

admin save

Table 2-1: Lab 2 commands

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

12

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise 2.1 Configuring static routes on the core and edge routers

Objective

Configure static routes between the core, edge and access routers and then verify connectivity between the routers.

routers and then verify connectivity between the routers. Figure 2-1: Pod physical connectivity Exercise 1. Configure

Figure 2-1: Pod physical connectivity

Exercise

1. Configure default routes from the access router to the edge and core routers.

echo "Static Route Configuration"

#--------------------------------------------------

static-route 0.0.0.0/0 next-hop 172.16.3.1

2. Configure an explicit static route from your pod’s core router to the loopback and system interfaces of your edge and access routers, and from your pod’s edge router to the loopback and system interfaces of the your core and access routers.

echo "Static Route Configuration"

#--------------------------------------------------

static-route 172.16.1.1/32 next-hop 172.16.2.1 static-route 172.16.1.2/32 next-hop 172.16.2.1

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

13

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute 3. Verify that the core router has

3. Verify that the core router has the static routes in its routing table.

4. Verify that the edge and access routers have the default route in its routing table.

Verification

1. Ping the core router’s system interface IP address from your access router.

2. Ping the core router’s system interface IP address from your edge router.

3. Ping the edge router’s system interface IP address from your core router.

4. Execute a show router route command to view the static routes in your routing table.

Exercise 2.2 Configuring static routes to other pods

Objective

Configure static routes between the core routers to provide direct connectivity between pods. Each core router should have a total of three static routes.

Each core router should have a total of three static routes. Figure 2-2: Physical connectivity Exercise

Figure 2-2: Physical connectivity

Exercise

Configure static routes between the core routers.

1. Configure static routes on your pod’s core router to the core routers of the other pods.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

14

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

echo "Static Route Configuration"

#--------------------------------------------------

static-route 172.17.1.1/32 next-hop 172.31.1.2 static-route 172.18.1.1/32 next-hop 172.31.4.2

2. Verify that the core router has the static routes listed in its routing table.

Verification

1. From your core router, ping the system interfaces of all other core routers.

2. From your core router, ping the system interfaces of all other pods’ edge and access routers.

3. From your edge router, ping the system interfaces of all other pods’ edge and access routers.

4. Execute a show command on your routers to verify the static routes.

Exercise 2.3 Configuring floating static routes to another pod

Objective

Configure floating static routes between the core routers to provide redundant connectivity between the pods, as listed in Table 2-2.

connectivity between the pods, as listed in Table 2-2. Figure 2-3: Physical connectivity Alcatel-Lucent Interior

Figure 2-3: Physical connectivity

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

15

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Pod number: Via pod Remote pod Pod

Pod number:

Via pod

Remote pod

Pod 1

Core

Pod 4

Pod 2 Core

Pod 2 Core

Pod 4

Pod 1 Core

Pod 3 Core

Pod 1

Pod 4 Core

Pod 4 Core

Pod 1

Pod 3 Core

Table 2-2: Pod connectivity

Exercise

Configure floating static routes between the core routers.

1. Configure a floating static route from your pod’s core router to access a remote pod, as listed in Table 2-2. Each pod should have a single floating static route.

echo "Static Route Configuration"

#--------------------------------------------------

static-route 172.19.1.1/32 next-hop 172.31.1.2 preference 200

static-route 172.19.1.1/32 next-hop 172.31.5.2

2. Examine your configuration to ensure that the floating static route is configured.

Verification

1. From your core router, ping the system interfaces of the remote pod’s routers that your floating static route has been configured for.

2. On your core router, type the show router static-route command and examine the current static route entries.

3. From your core router, shut down the port to the remote pod that the floating static route has been configured for.

4. On your core router, retype the show router static-route command and note the differences in the static route entries.

5. Check your routing table to ensure that the floating static route has replaced the original static route that you configured to the remote pod.

6. From your core router, ping the system interfaces of the remote pod’s routers that your floating static route has been configured for.

7. Using the trace command, trace the path being taken to the remote pod. Map and verify the path being taken.

8. Upon completion, reactivate the port that you shut down in step 3.

Questions

1. Which command was used to configure a static route to your remote peer?

2. How can a floating static route become active?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

16

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. What is the default preference value for a static route?

Exercise 2.4 Configuring a black-hole static route

Objective

Configure a black hole static route on the core routers and examine the routing table.

route on the co re routers and examine the routing table. Figure 2-4: Physical connectivity Alcatel-Lucent

Figure 2-4: Physical connectivity

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

17

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Pod number: Remote pod Pod 1 core

Pod number:

Remote pod

Pod 1 core

Pod 1 edge

Pod 2 core

Pod 2 edge

Pod 3 core

Pod 3 edge

Pod 4 core

Pod 4 edge

Pod 1 edge

Pod 1 access

Pod 2 edge

Pod 2 access

Pod 3 edge

Pod 3 access

Pod 4 edge

Pod 4 access

Table 2-3: Pod connectivity

Exercise

Configure a black hole static route on the core routers.

1. Configure a black hole static route from your pod’s core router to drop packets that are destined for your pod address range. Each pod should have a single black hole static route. It should show the previous floating static route and the black-hole static route.

echo "Static Route Configuration"

#--------------------------------------------------

static-route 172.19.0.0/16 black-hole static-route 172.19.1.1/32 next-hop 172.31.1.2 preference 200

static-route 172.19.1.1/32 next-hop 172.31.5.4

2. Examine your configuration to ensure that the black hole route is configured.

3. Are you able to test the functionality of black hole? Why?

Verification

1. From your core router, ping the system interfaces of the edge routers that your black hole static route has been configured.

2. On your core router, type the show router static-route command and examine the current static route entries.

Questions

1. Which command was used to configure a black hole static route to your edge router?

2. Did the ping and traceroute commands to the system interface of the edge router work?

Notes

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

18

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

19

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Lab 3 SPF Path Selection Objective: Build

Lab 3 SPF Path Selection

Objective:

Build a link state database for rtr1 that consist of the link state information from the other routers in order to perform SPF calculation for a given path.

in order to perform SP F calculation for a given path. Figure 3.1: SPF Path Selection
in order to perform SP F calculation for a given path. Figure 3.1: SPF Path Selection

Figure 3.1: SPF Path Selection

Rtr1 link state packet

Rtr1 to rtr2

10

Rtr2 link state packet

Rtr3link state packet

Rtr4 link state packet

Rtr5 link state packet

Table 3.1: SPF Path Selection

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

20

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Lab 4 Configuring OSPF in a Single Area

Objectives

Configure OSPF in single area and analyze the OSPF database and routing tables. Examine OSPF packets exchanges to form an adjacency Inspect the designated router election process in broadcast domain

Syntax

The commands required for Lab 4 are listed in Table 4-1. Each command may have additional possible parameters. Use the “?” character for help and to explore all command line options. Other commands may also be used, including those in previous exercises.

Lab 4 configuration commands

configure router router-id <ip-address>

configure router ospf

configure router ospf area <area-id>

configure router ospf area interface <ip-int-name>

configure router no isis

show router ospf area <area-id> {detail}

show router ospf database

show router ospf interface

show router ospf status

show router ospf neighbor

admin save

Table 4-1: Lab 4 commands

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

21

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 4.1 Implementing OSPF in a single

Exercise 4.1 Implementing OSPF in a single area

Objective

Migrate from the current implementation to that of OSPF in a single area.

current implementation to that of OSPF in a single area. Figure 4-1: OSPF single area Exercise

Figure 4-1: OSPF single area

Exercise

1. Configure OSPF on the core and edge routers in area 0.0.0.0.

area 0.0.0.0 interface "system" exit interface "C_E1" exit interface "loopback1" exit interface "loopback2" exit interface "C1_C2" exit interface "C1_C3" exit interface "C1_C4" exit

exit

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

22

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

2. Ensure that all interfaces are participating in the OSPF instance.

Verification

1. Verify your routing configuration by examining the OSPF tables on all routers.

2. Ensure that all networks propagate to peers just as they did prior to this lab.

3. Verify connectivity by issuing the traceroute and ping commands.

4. Use the OSPF show commands to examine the databases for accuracy.

5. How many routes are in your routing table?

Questions

1. What is another term for area 0.0.0.0?

2. Which command is used to confirm that OSPF is working correctly?

3. How is cost calculated on an interface by default?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

23

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 4.2 Router adjacency study Objective Examine

Exercise 4.2 Router adjacency study

Objective

Examine the packets exchanged as OSPF routers form an adjacency.

Exercise

4. Enable debug-trace to look at OSPF packets on the edge router. To enable debug-trace:

configure log log-id <log-id> configure log > from debug-trace configure log > to session exit

debug router ospf packet <packet-type> detail

5. Shut down OSPF on the edge router and start it again. Approximately how many packets are exchanged to establish the adjacency?

6. With debug-trace running, turn on authentication on the edge router and watch the packets that are exchanged. Use the password Alcatel. Note which packets are being exchanged when authentication fails.

7. Note the state that the edge and the core router are stuck in. Enable authentication on the core router to the edge and verify that the adjacency is formed. Enable authentication on your other interfaces.

8. Verify the routes in the routing table. Verify that you can ping the edge routers in the other pods.

9. Change the link from the edge to the core back to broadcast mode while running debug- trace. Watch to see which router is selected as the DR.

Verification

10. Verify that all the expected adjacencies are formed with authentication.

11. Verify that the expected routes are in the routing table.

12. Using ping, verify connectivity to the other edge routers from your edge router.

Questions

13. Approximately how many packets are required to establish the adjacency?

14. Which packets are being exchanged when authentication fails?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

24

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise 4.3 Broadcast and VPLS

Objective

Configure VPLS connections between the routers in a given Pod and examine the Designated Router election in a broadcast networks in OSPF.

Designated Router election in a broadcast networks in OSPF. Figure 4-2: Physical Connectivity Figure 4-3: VPLS

Figure 4-2: Physical Connectivity

networks in OSPF. Figure 4-2: Physical Connectivity Figure 4-3: VPLS Connection Alcatel-Lucent Interior Routing

Figure 4-3: VPLS Connection

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

25

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Figure 4-4: VPLS Configuration Exercise 1. In
Confidential for Internal Use ONLY - Do Not Distribute Figure 4-4: VPLS Configuration Exercise 1. In

Figure 4-4: VPLS Configuration

Exercise

1. In this exercise, students will work in two groups, one group will configure a VPLS on the upper pods, and the second group will do the same on the lower pods. The VPLS will be configured on the edge routers. The three routers participating in the service will be a core, access, and the opposite pod edge router. Use the same VPLS ID for all SAPs. Notice the change to the interface IP addresses on the access, core and opposite pod edge routers towards the VPLS on the edge router to be /29 from /30. Use the following commands to create the VPLS connection between the routers.

*A:Edge_Pod1# configure port 1/1/1 shutdown *A:Edge_Pod1# configure router interface E1_C1 no port *A:Edge_Pod1# configure port 1/1/1 ethernet mode access *A:Edge_Pod1# configure port 1/1/1 no shutdown *A:Edge_Pod1# configure service vpls 100 customer 1 create *A:Edge_Pod1>config>service>vpls$ sap 1/1/1 create *A:Edge_Pod1>config>service>vpls>sap$ exit all *A:Edge_Pod1# configure port 1/1/2 shutdown *A:Edge_Pod1# configure router interface E1_A1 no port *A:Edge_Pod1# configure port 1/1/2 ethernet mode access *A:Edge_Pod1# configure port 1/1/2 no shutdown *A:Edge_Pod1# configure service vpls 100 customer 1 create *A:Edge_Pod1>config>service>vpls# sap 1/1/2 create A:Edge_Pod1# configure port 1/1/3 shutdown *A:Edge_Pod1# configure router interface E1_E2 no port *A:Edge_Pod1# configure port 1/1/3 ethernet mode access *A:Edge_Pod1# configure port 1/1/3 no shutdown *A:Edge_Pod1# configure service vpls 100 customer 1 create *A:Edge_Pod1>config>service>vpls# sap 1/1/3 create

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

26

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Verify the VPLS is operational.

*A:Edge_Pod1# show service id 100 base

=========================================================== Service Basic Information ===========================================================

Service Id

: 100

Vpn Id

:

0

Service Type

: VPLS

Customer Id

:

1

Last Status Change: 05/03/2010 13:14:50 Last Mgmt Change : 05/03/2010 13:15:22

 

Admin State

: Up

: 1514

Oper State

: Up

MTU

Def. Mesh VC Id

: 100

SAP Count

:

3

SDP Bind Count

:

0

Snd Flush on Fail : Disabled Propagate MacFlush: Disabled

Def. Gateway IP

: None

Def. Gateway MAC

: None

Host Conn Verify : Disabled

-----------------------------------------------------------

Service Access & Destination Points

-----------------------------------------------------------

Identifier

Type

AdmMTU OprMTU Adm

Opr

-----------------------------------------------------------

 

sap:1/1/1

null

1514

1514

Up

Up

sap:1/1/2

null

1514

1514

Up

Up

sap:1/1/3

null

1514

1514

Up

Up

2. Configure the OSPF interfaces between the routers as broadcast.

*A:Core_Pod1>config>router>ospf>area# interface C1_E1 *A:Core_Pod1>config>router>ospf>area>if# interface-type broadcast *A:Access_Pod1>config>router>ospf>area# interface A1_E1 *A:Access_Pod1>config>router>ospf>area>if# interface-type broadcast *A:Edge_Pod1>config>router>ospf>area# interface E2_E1 *A:Edge_Pod1>config>router>ospf>area>if# interface-type broadcast

3. Determine which is the DR and which the BDR in your pod. Note this information.

*A:Core_Pod1# show router ospf interface

4. Check your routing table to verify that you have routes to all networks.

5. From the access router, ping the system interfaces of the other core routers to verify connectivity.

Verification

1. Verify your routing configuration by examining the OSPF tables on all routers.

2. Ensure that all networks propagate to peers just as they did in the previous lab.

3. Verify connectivity by issuing the traceroute and ping commands.

4. Use the OSPF show commands to examine the databases for accuracy.

5. How many routes are in your routing table?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

27

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Note: To remove the vpls services use

Note: To remove the vpls services use the following commands:

config>service# vpls 100 config>service>vpls# shutdown config>service>vpls# sap 1/1/1 shutdown config>service>vpls# sap 1/1/2 shutdown config>service>vpls# sap 1/1/3 shutdown config>service>vpls# back config>service>vpls# no sap 1/1/1 config>service>vpls# no sap 1/1/2 config>service>vpls# no sap 1/1/3 config>service>vpls# back config>service# no vpls 100

To configure the ports in network mode, shut down the ports and then use the command

config>port# ethernet mode network

Questions

1. Which of the two routers in your pod is the DR?

2. Which state are the routers in if the link type does not match?

3. How are the type 1 and type 2 LSAs labeled in the database?

4. Which state are the routers in if the authentication password does not match?

Notes

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

28

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Lab 5 Configuring OSPF for Multiple Areas and Summarization

Objectives

Configure OSPF for multiple areas.

Test and verify OSPF routes between routers in different area

Examine OSPF database and inspect the different types of LSA

Inspect the changes to OSPF database by configuring different OSPF area types

Syntax

The commands required for Lab 5 are listed in Table 5-1. Each command may have additional possible parameters. Use the “?” character for help and to explore all command line options. Other commands may also be used, including those in previous exercises.

Lab 5 configuration commands

configure router router-id <ip-address>

configure router ospf

configure router ospf area <area-id>

configure router ospf area interface <ip-int-name>

area-range <ip-prefix/mask> {advertise | not-advertise}

show router ospf area <area-id> {detail}

show router ospf database

show router ospf interface

show router ospf status

show router ospf neighbor

Admin save

Table 5-1: Lab 5 commands

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

29

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 5.1 Implementing O SPF for a

Exercise 5.1 Implementing OSPF for a multi-area topology

Objective

Modify the current single-area OSPF to a multi-area topology as described in the figure below. The core routers will remain as area 0 while each Pod edge and access will be configured into a different area.

edge and access will be configured into a different area. Figure 5-1: Multi-area OSPF Alcatel-Lucent Interior

Figure 5-1: Multi-area OSPF

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

30

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise

1. Examine the LSDB to see what types of LSAs it contains. How many are there?

2. Modify the current OSPF topology from a single area to a multi-area topology, as shown in Figure 5-1.

router-id 172.19.1.1 area 0.0.0.0 interface "system" exit interface "C4_C2" exit interface "C4_C1" exit interface "C4_C3" exit interface "loopback1" exit interface "loopback2" exit

exit area 0.0.0.4 interface "C4_E6" exit

exit

3. Verify the operation of OSPF.

4. Examine the LSDB to see what types of LSAs are there now. What new types of LSAs are in the database?

Verification:

1. Verify your routing policies by examining the OSPF tables on all routers.

2. Ensure that summary networks propagate to peer core routers, by having a Telnet session with a remote peer and checking its routing table.

3. Verify connectivity by issuing the traceroute and ping commands.

4. Use the OSPF show commands to examine the databases for accuracy.

5. How many routes are in your routing table?

Questions

1. Which type of router connects more than one area together?

2. Which types of LSAs exist in a multi-area network that are not in a single area OSPF network?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

31

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 5.2 Routes from non-OSPF areas Objective

Exercise 5.2 Routes from non-OSPF areas

Objective

Change the edge router to an ASBR and examine the LSAs that are exchanged throughout the network.

Exercise

1. Examine the LSDB to see what types of LSAs it contains.

2. Remove the loopback interfaces on the edge router from OSPF.

echo "IP Configuration"

#--------------------------------------------------

interface "E6_C4" address 172.17.2.2/30 port 1/1/1

exit interface "system" address 172.19.254.1/32

exit

#--------------------------------------------------

echo "OSPFv2 Configuration"

#--------------------------------------------------

ospf

 

router-id 172.19.254.1 area 0.0.0.4 interface "E6_C4" exit

exit

exit

3. Configure the edge router as an ASBR, and create and apply an export policy to export the loopback networks to OSPF. To create an export policy, use the following commands. For more details, you can refer to the scalable IP network lab guide.

To create a Routing Policy

config>router# policy-options

To enter the edit mode for creating a policy option

config>router>policy-options# begin

To name the routing policy

config>router>policy-options# policy-statement "EXPOL"

To edit routing policy entries

config>router>policy-options>policy-statement# entry 10

To define the routing protocol being advertised

config>router>policy-options>policy-statement>entry# from protocol direct

To define the action to be taken by the policy

action {accept | next-entry | next-policy | reject} Example: config>router>policy-options>policy-statement>entry# action accept

To save the configured policy-option

config>router>policy-options# commit

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

32

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

router-id 172.19.254.1 asbr export "EXPOL" area 0.0.0.4 interface "E6_C4" exit

exit

4. On the core router, verify that the routing table contains routes to your loopback networks.

5. Check the LSDB and note the types of LSAs it contains.

6. Verify the operation of OSPF.

Verification

1. Verify your route policies by examining the OSPF tables on all routers.

2. Verify connectivity by issuing the traceroute and ping commands.

3. Use the OSPF show commands to examine the databases for accuracy.

4. How many routes are in your routing table?

Questions

1. Which type of router connects to non-OSPF routing domains?

2. Which types of LSAs exist in an OSPF network connected to other routing domains that are not in an OSPF-only network?

Exercise 5.3 OSPF stub areas

Objective

Together with your instructor, choose two areas and convert them to an OSPF stub areas, and then examine the differences in the routing table.

Exercise

1. Examine the LSDB to see what types of LSAs it contains, and verify the routes in the routing table.

2. Remove the export policy from your edge router so it is no longer flooding Type 5 LSAs. Convert your area to a stub area.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

33

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute router-id 172.19.1.1 area 0.0.0.0 interface "system"

router-id 172.19.1.1 area 0.0.0.0 interface "system" exit interface "C4_C2" exit interface "C4_C1" exit interface "C4_C3" exit interface "loopback1" exit interface "loopback2" exit

exit area 0.0.0.4 stub exit interface "C4_E6" exit

exit

3. Check the routing table and compare it to the previous version.

4. Examine the LSDB to see what LSAs are being filtered.

5. Verify reachability to the other pods in the network.

Verification

1. Verify connectivity by issuing the traceroute and ping commands.

2. Use the OSPF show commands to examine the databases for accuracy.

3. How many routes are in your routing table?

Questions

1. What changes occur when the network is converted to a stub area?

Exercise 5.4 OSPF stub areas with summaries

Objective

Together with your instructor, choose two areas and convert them to OSPF totally stubby areas, and then examine the differences in the routing table.

Exercise

1. Examine the LSDB to see what types of LSAs it contains, and verify the routes in the routing table.

2. Implement summarization on your ABR to advertise your area as a single network entry to the other pods.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

34

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

config>router>ospf>area#area-range <ip-prefix/mask> [advertise|not- advertise]

3. Verify reachability to the other pods in the network.

4. Examine the size and content of your routing table and LSDB.

5. Use the no summaries command to convert your area to a totally stubby area.

config>router>ospf>area>stub# no summaries

6. Check the routing table and compare it to the previous version.

7. Examine the LSDB to see what LSAs are being filtered.

Verification

1. Verify connectivity by issuing the traceroute and ping commands.

2. Use the OSPF show commands to examine the databases for accuracy.

3. How many routes are in your routing table?

Questions

1. What is the effect on the rest of the network of implementing summarization on your ABR?

2. What changes occur when the stub area is configured with no summaries?

Exercise 5.5 OSPF NSSA

Objective

Together with your instructor, choose two areas and convert them to OSPF NSSA areas, and then examine the differences in the routing table.

Exercise

1. Examine the LSDB to see what types of LSAs it contains, and verify the routes in the routing table.

2. Convert your area to an NSSA. Add a policy on your edge router to export your loopback networks and apply it to export these networks into OSPF.

export "EXP_Loop" exit area 0.0.0.4 nssa exit interface "C4_E6" exit

exit

3. Check the routing table and compare it to the previous version.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

35

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute 4. Examine the LSDB to see what

4. Examine the LSDB to see what LSAs are there.

5. Verify reachability to the other pods in the network.

6. Use the no summaries command to convert your area to a totally NSSA area. You need to explicitly tell the ABR to advertise a default route into the NSSA area.

7. Check the routing table and compare it to the previous version.

8. Examine the LSDB to see what LSAs are being filtered.

9. Verify reachability to the other pods in the network.

10. Examine the size and content of your routing table and LSDB.

Verification

1. Verify connectivity by issuing the traceroute and ping commands.

2. Use the OSPF show commands to examine the databases for accuracy.

3. How many routes are in your routing table?

Questions

1. What changes occur when the network is converted to an NSSA?

2. What is the effect of the no summaries command on the NSSA?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

36

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise 5.6 (Optional) Configuring a virtual link to the edge router

Objective

Create a virtual link to connect a remote OSPF area to the backbone area.

link to connect a remot e OSPF area to the backbone area. Figure 5-2: OSPF Virtual

Figure 5-2: OSPF Virtual link

Exercise

1. Configure your loopback interfaces on the edge router to be in area 1.1.1.X, where X is your pod number.

2. Remove the NSSA configuration.

3. Configure area 0.0.0.0 on the edge router so that the virtual link can operate correctly.

4. Identify the RID of each router (core and edge) by using the show router ospf neighbor command.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

37

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute 5. Implement a virtual link between your

5. Implement a virtual link between your core and edge routers.

virtual-link 172.19.1.1 transit-area 0.0.0.1 exit interface "system" exit interface "C_E1" exit interface "loopback1" exit interface "loopback2" exit interface "C1_C2" exit interface "C1_C3" exit interface "C1_C4" exit

exit

6. Ensure that network convergence occurs.

Verification

1. Verify your virtual link implementation by examining the OSPF tables on all routers.

2. Ensure that the core and edge routers maintain OSPF convergence.

3. Verify connectivity by issuing the traceroute and ping commands.

4. Use the OSPF show commands to examine the databases for accuracy.

Questions

1. Why are there so many more LSAs in the router databases after the virtual link is implemented?

Notes

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

38

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Lab 6 Configuring IS-IS for a Single Area

Objectives

Configure IS-IS in single area and analyze the IS-IS routes. Examine IS-IS packets exchanges to form an adjacency Inspect the designated intermediate system election process in broadcast domain Configure multiple areas IS-IS and inspect route summarization

Syntax

The commands required for Lab 6 are listed in Table 6-1. Each command may have additional possible parameters. Use the “?” character for help and to explore all command line options. Other commands may also be used, including those in previous exercises.

Lab 6 configuration commands

configure router isis

Shutdown

no isis

configure router isis area-id <area-address>

configure router isis level-capability <level-1 | level-2 | level-1/2>

configure router isis interface <ip-int-name>

configure router isis interface <ip-name> level-capability level-1

configure router isis summary-address <ip-prefix/mask | ip-prefix {netmask}> level <level>

show router route

show router isis adjacency

show router isis routes

show router isis interface

show router isis status

admin save

Table 6-1: Lab 6 commands

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

39

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 6.1 Activating IS-IS on your core,

Exercise 6.1 Activating IS-IS on your core, edge, and access routers

Objective

Configure IS-IS on all routers to be in a single area.

Configure IS-IS on all router s to be in a single area. Figure 6-1: IS-IS Single

Figure 6-1: IS-IS Single area network

Exercise

1. Configure IS-IS on the core, edge and access routers in area 49.0051.

2. Ensure all interfaces are participating in the IS-IS instance.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

40

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

A:Core_Pod1>config>router>isis# info

----------------------------------------------

area-id 49.0051 interface "system" exit interface "C_E1" exit interface "C1_C2" exit interface "C1_C3" exit interface "C1_C4" exit

----------------------------------------------

3. When you have confirmed that IS-IS is active and converged, shut down OSPF on the router.

Verification

1. Verify your route policies by examining the IS-IS tables on all routers.

2. Ensure that all networks propagate to peers just as they did prior to this lab.

3. Verify connectivity by issuing the traceroute and ping commands.

4. Use the IS-IS show commands to examine the databases for accuracy.

5. How many routes are in your routing table?

Questions

1. IS-IS is what type of routing protocol?

2. What is the default cost for each link in an IS-IS network?

3. What does “area 49” denote in IS-IS?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

41

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 6.2 IS-IS adjacency study Objective Examine

Exercise 6.2 IS-IS adjacency study

Objective

Examine the packets exchanged as IS-IS routers form an adjacency.

Exercise

1. Enable debug-trace to look at IS-IS packets on the edge router.

2. Shut down IS-IS on the edge router and start it again. Note the packets exchanged to establish the adjacency.

3. With debug-trace running, turn on authentication on the edge router and watch the packets that are exchanged. Use the password Alcatel. Note which packets are being exchanged when authentication fails.

4. Note the state that the edge and the core router are stuck in. Enable authentication on the core router to the edge and verify that the adjacency is formed. Enable authentication on your other interfaces.

*A:Core_Pod1>config>router>isis# info

----------------------------------------------

area-id 49.0051 authentication-key "B8KjnQ7FUVsaiZJg8TjroibV7dti5iHF" hash2 authentication-type password

interface "system" exit interface "C_E1" exit interface "C1_C2" exit interface "C1_C3" exit interface "C1_C4" exit

----------------------------------------------

5. Verify the routes in the routing table. Verify that you can ping the edge routers in the other pods.

6. Change your link from the edge to the core to point-to-point mode while running debug- trace. Note which packets are being exchanged when the adjacency fails to form. See what state the edge and core routers are stuck in.

*A:Edge_Pod1>config>router>isis# info

----------------------------------------------

level-capability level-1 area-id 49.0051 interface "system" exit interface "E_C1" interface-type point-to-point

exit

interface "E_A1"

exit

-----------------------------------------------------------

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

42

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

7. Change the other end of the link to point-to-point and note the packets that are exchanged as the adjacency forms.

*A:Core_Pod1>config>router>isis# info

----------------------------------------------

area-id 49.0001 authentication-key "B8KjnQ7FUVsaiZJg8TjroibV7dti5iHF" hash2

authentication-type password interface "system" exit interface "C_E1" interface-type point-to-point

exit interface "C1_C2" exit interface "C1_C3" exit interface "C1_C4" exit

-----------------------------------------------------------

Verification

1. Verify that all the expected adjacencies are formed with authentication.

2. Verify that the expected routes are in the routing table.

3. Using ping, verify connectivity to the other edge routers from your edge router.

Questions

1. Approximately how many packets are required to establish the adjacency?

2. Draw a time/sequence diagram that shows the packets exchanged to establish an adjacency.

3. Which packets are being exchanged when authentication fails?

4. Which state are the routers stuck in if the authentication password does not match?

5. Which packets are being exchanged when the adjacency fails because the link types do not match?

6. Which state are the routers stuck in when the link types do not match?

7. Draw a time/sequence diagram that shows the packets exchanged to establish an adjacency on a point-to-point link.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

43

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 6.3 Broadcast and VPLS Objective Configure

Exercise 6.3 Broadcast and VPLS

Objective

Configure VPLS connections between the routers in a given Pod and examine the Intermediate System election in a broadcast networks in ISIS.

System election in a broadcast networks in ISIS. Figure 6-2: Physical Connectivity Figure 6-3: ISIS VPLS

Figure 6-2: Physical Connectivity

networks in ISIS. Figure 6-2: Physical Connectivity Figure 6-3: ISIS VPLS Connection Alcatel-Lucent Interior

Figure 6-3: ISIS VPLS Connection

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

44

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Figure 6-4: ISIS VPLS Configuration Exercise 8.

Figure 6-4: ISIS VPLS Configuration

Exercise

8. In this exercise, students will work in two groups, one group will configure a VPLS on the upper pods, and the second group will do the same on the lower pods. The VPLS will be configured on the edge routers. The three routers participating in the service will be a core, access, and the opposite pod edge router. Use the same VPLS ID for all SAPs. Notice the change to the interface IP addresses on the access, core and opposite pod edge routers towards the VPLS on the edge router to be /29 from /30. Use the following commands to create the VPLS connection between the routers.

*A:Edge_Pod1# configure port 1/1/1 shutdown *A:Edge_Pod1# configure router interface E1_C1 no port *A:Edge_Pod1# configure port 1/1/1 ethernet mode access *A:Edge_Pod1# configure port 1/1/1 no shutdown *A:Edge_Pod1# configure service vpls 100 customer 1 create *A:Edge_Pod1>config>service>vpls$ sap 1/1/1 create *A:Edge_Pod1>config>service>vpls>sap$ exit all *A:Edge_Pod1# configure port 1/1/2 shutdown *A:Edge_Pod1# configure router interface E1_A1 no port *A:Edge_Pod1# configure port 1/1/2 ethernet mode access *A:Edge_Pod1# configure port 1/1/2 no shutdown *A:Edge_Pod1# configure service vpls 100 customer 1 create *A:Edge_Pod1>config>service>vpls# sap 1/1/2 create A:Edge_Pod1# configure port 1/1/3 shutdown *A:Edge_Pod1# configure router interface E1_E2 no port *A:Edge_Pod1# configure port 1/1/3 ethernet mode access *A:Edge_Pod1# configure port 1/1/3 no shutdown *A:Edge_Pod1# configure service vpls 100 customer 1 create *A:Edge_Pod1>config>service>vpls# sap 1/1/3 create

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

45

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Verify the VPLS is operational. *A:Core_Pod1# show

Verify the VPLS is operational.

*A:Core_Pod1# show service id 100 base

=========================================================== Service Basic Information ===========================================================

Service Id

: 100

Vpn Id

:

0

Service Type

: VPLS

Customer Id

:

1

Last Status Change: 05/03/2010 13:14:50 Last Mgmt Change : 05/03/2010 13:15:22

 

Admin State

: Up

: 1514

Oper State

: Up

MTU

Def. Mesh VC Id

: 100

SAP Count

:

3

SDP Bind Count

:

0

Snd Flush on Fail : Disabled Propagate MacFlush: Disabled

Def. Gateway IP

: None

Def. Gateway MAC

: None

Host Conn Verify : Disabled

-----------------------------------------------------------

Service Access & Destination Points

-----------------------------------------------------------

Identifier

Type

AdmMTU OprMTU Adm

Opr

-----------------------------------------------------------

 

sap:1/1/1

null

1514

1514

Up

Up

sap:1/1/2

null

1514

1514

Up

Up

sap:1/1/3

null

1514

1514

Up

Up

9. Configure the ISIS interfaces between the routers as broadcast.

*A:Core_Pod1>config>router>isis>area# interface C1_E1 *A:Core_Pod1>config>router>isis>area>if# interface-type broadcast *A:Core_Pod1>config>router>isis>area# interface A1_E1 *A:Core_Pod1>config>router>isis>area>if# interface-type broadcast *A:Core_Pod1>config>router>isis>area# interface E2_E1 *A:Core_Pod1>config>router>isis>area>if# interface-type broadcast

10. Determine which is the DIS

*A:Core_Pod1# show router isis interface detail

11. Check your routing table to verify that you have routes to all networks.

12. From the access router, ping the system interfaces of the other core routers to verify connectivity.

Verification

13. Verify your routing configuration by examining the ISIS tables on all routers.

14. Ensure that all networks propagate to peers just as they did in the previous lab.

15. Verify connectivity by issuing the traceroute and ping commands.

16. Use the ISIS show commands to examine the databases for accuracy.

17. How many routes are in your routing table?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

46

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise 6.4 Configuring IS-IS for multiple areas

Objective

Optimize the IS-IS routing environment by creating areas for each pod.

IS-IS routing environment by creating areas for each pod. Figure 6-5: IS-IS multiple area network Exercise

Figure 6-5: IS-IS multiple area network

Exercise

1. Verify IS-IS operation in a single area.

2. Remove the current implementation of IS-IS.

3. Activate IS-IS in the correct area, as shown in Figure 6-5. Implement only the required level of IS-IS, based on the type of router you are configuring (L1, L2, or L1/L2).

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

47

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute *A:Core_Pod1>config>router>isis# info

*A:Core_Pod1>config>router>isis# info

----------------------------------------------

area-id 49.0051 authentication-key "B8KjnQ7FUVsaiZJg8TjroibV7dti5iHF" hash2

authentication-type password interface "system" exit interface "C_E1" level-capability level-1

exit interface "C1_C2" level-capability level-2

exit interface "C1_C3" level-capability level-2

exit interface "C1_C4" level-capability level-2

exit

----------------------------------------------

4. Ensure that each interface is only running the level of IS-IS required, and not both L1 and L2 unless it is specifically required to.

Verification

1. Verify your routing policies by examining the IS-IS tables on all routers.

2. Ensure that all networks propagate to peers just as they did prior to this lab.

3. Verify connectivity by issuing the traceroute and ping commands.

4. Use the show router isis and show router route commands to verify the operation of IS-IS on your routers.

5. How many routes are in your routing table?

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

48

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise 6.5 Implementing route summarization per area

Objective

Summarize the addresses being advertised from your pod as they are sent to the core routers in the other pods.

Exercise

1. Using the summary-address command, implement summarization on your core routers.

2. Ensure that this summary is only advertised using L2 updates, not L1 updates.

*A:Core_Pod3>config>router>isis# info

----------------------------------------------

area-id 49.0002 summary-address 172.18.0.0/16 level-2 interface "system" exit interface "C3_C1" level-capability level-2

exit interface "C3_C2" exit interface "C3_C4" level-capability level-1

exit

-----------------------------------------------------------

Verification

1. Verify your routing policies by examining the IS-IS tables on all routers.

2. Ensure that the summary networks propagate to the peer core routers.

3. Verify connectivity by issuing the traceroute and ping commands.

4. Use the IS-IS show commands to examine the databases for accuracy.

5. How many routes are in your core and edge routers? Why?

Questions

1. What is the default level that is set on a router?

2. Which level should a router that connects multiple areas be set to?

3. A router that connects to only those routers in its area should be set to which level? (L1, L2, or L1/L2)

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

49

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Notes Alcatel-Lucent Interior Routing Protocols Lab Guide

Notes

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

50

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Lab 7 Route Redistribution

Objective

Configure multiple routing protocols in the network and then create a redistribution policy, applying it to those protocols to ensure that all networks are learned by all routers.

to ensure th at all networks are learned by all routers. Figure 7-1: Route redistribution Exercise

Figure 7-1: Route redistribution

Exercise

As shown in Figure 7-1, you will create a separate OSPF area for each edge and access routers and a portion of the core router (ASBR). The core routers will be interconnected using IS-IS area ID 49.0000. When the core routers see both OSPF and IS-IS routes, you will create a policy to redistribute OSPF into IS-IS and IS-IS into OSPF.

1. Remove the IS-IS routing protocol from the edge and access routers.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

51

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute 2. Configure the edge and access routers

2. Configure the edge and access routers as OSPF routers. The area number is your pod number, and all interfaces will be in that area.

*A:Edge_Pod1> config>router>ospf#> info area 0.0.0.1 interface "system" exit interface "E1_C1" exit interface "loopback1" exit interface "loopback2" exit interface "E1_A1" exit exit

3. Remove the current IS-IS area from the core router and enter the new IS-IS area (49.0000).

4. Configure OSPF on the core router, using the same area number as the edge and access routers.

5. Remove the interface that connects the core to the edge from the IS-IS routing protocol and enter it into the OSPF routing protocol.

6. Ensure that the IS-IS routing process on the core router has an L1/L2 capability. To redistribute routes from another routing protocol, IS-IS must have an L2 capability.

7. On the core router, enter into the OSPF routing process and configure the core as an ASBR. As previously discussed, the ASBR is the only OSPF router that can connect to another routing protocol.

*A:Core_Pod1> config>router>ospf# asbr

This has prepared the network.

8. Examine the routing table of the core router and ensure that it has learned both OSPF and IS-IS routes.

9. Examine the status of the OSPF portion of the core router and ensure that it has been configured as an ASBR.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

52

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

10. Create a route policy on the core router that will take routing information from IS-IS to OSPF and allow OSPF to accept these routes and export them to the other OSPF routers. Then, create a route policy that will take routing information from OSPF to IS-IS and allow IS-IS to accept these routes and export them to the other IS-IS routers.

entry 10 from protocol isis exit to protocol ospf exit action accept exit exit entry
entry 10
from
protocol isis
exit
to
protocol ospf
exit
action accept
exit
exit
entry 20
from
protocol ospf
exit
to
protocol isis
exit
action accept
exit
exit
entry 30
from
protocol direct
exit
action accept
exit
exit

11. Apply the policy under the routing protocols to make it effective.

configure router ospf export <policy-name>

configure router isis export <policy-name>

12. Examine the routing table of the edge or access router and you should see all the networks.

A:Edge_Pod1> show router route-table

Verification

1. On the core router, verify that there are routes from IS-IS and OSPF in the routing table.

2. On the edge router, verify that all routes are in the routing table.

3. From the edge router, ping the other edge routers to verify connectivity across the network.

Notes

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

53

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Appendix A Answers to Lab Questions Exercise

Appendix A Answers to Lab Questions

Exercise 1.2

Questions

1. Which command is used to ensure all ports are active? The show port command identifies any and all ports and their operational statuses.

2. Which command can be used to determine the naming convention for the interfaces? The show router interface command states this information.

Exercise 2.3

Questions

1. Which command was used to configure a static route to your remote peer? The configure router static-route command accomplishes this task.

2. How can a floating static route become active? When the path of lower preference is removed from the routing table, the floating static route takes precedence.

3. What is the default preference value for a static route? The default preference value for static routes is 5.

Exercise 4.1

Questions

1.

What is another term for area 0.0.0.0? The backbone area

2.

Which command is used to confirm that OSPF is working correctly? The show router ospf command provides enough information to validate if OSPF is working on the router.

3.

How is cost calculated on an interface by default? The default reference bandwidth is 100,000,000 kb/s divided by the bandwidth of the interface.

Exercise 4.2

Questions

1. Which of the two routers in your pod is the DR?

2. Which state are the routers in if the link type does not match? The router would be in the initializing state

3. How are the type 1 and type 2 LSAs labeled in the database? Router and network

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

54

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise 4.3

Questions

1. Which packets are being exchanged when authentication fails? Only hello packets will be exchanged, routers have to agree on the authentication before they can be neighbors

2. Which state are the routers in if the authentication password does not match? Initializing state

Exercise 5.1

Questions

1. What type of router connects more than one area together? An ABR connects more than one area together.

2. Which types of LSAs exist in a multi-area network that are not in a single area OSPF network? Type 3,4, 5 and 7

Exercise 5.2

Questions

1. Which type of router connects to non-OSPF routing domains? ASBR

2. Which type of LSAs exist in an OSPF network connected to other routing domains that are not in an OSPF-only network? Type 5

Exercise 5.3

Question

1. What changes occur when the network is converted to a stub area? A default route 0.0.0.0/0 will be added to the database, and no external routes are allowed into the area

Exercise 5.4

Questions

1. What changes occur when the stub area is configured with no summaries? No summary routes will be allowed to the area, instead the default route will be used

2. What is the effect on the rest of the network of implementing summarization on your ABR? Reduces the size of network routing tables and LSA traffic

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

55

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 5.5 Questions 1. What changes occur

Exercise 5.5

Questions

1. What changes occur when the network is converted to an NSSA? The network would allow type 7 to be transmitted through it, and it will be converted to type 5 LSA at the ABR

2. What is the effect of the no summaries command on the NSSA? Type 3 LSA would not be allowed into the area

Exercise 5.6

Question

1. Why are there so many more LSAs in the router databases after the virtual link is implemented? Virtual link would allow the connection of new are into the backbone area, and therefore new LSAs will be added to the database

Exercise 6.1

Questions

1. IS-IS is what type of routing protocol? IS-IS is a link-state routing protocol.

2. What is the default cost for each link in an IS-IS network? The default cost for each network segment is 10.

3. What does “area 49” denote in IS-IS? Area 49 denotes that a locally administered area addressing scheme is in use, not one allocated by a government authority. This is the most common implementation in IS-IS.

Exercise 6.2

Questions

1. Draw a time/sequence diagram that shows the packets exchanged to establish an adjacency.

2. Which packets are being exchanged when authentication fails? Hello packets

3. Which state are the routers stick in if the authentication password does not match? Down state

4. Which packets are being exchanged when the adjacency fails because the link types do not match? Hello packets, different hello packets are sent on broadcast and point to point links

5. Which state are the routers stuck in when the link types do not match? Down state

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

56

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

6. Draw a time/sequence diagram that shows the packets exchanged to establish an adjacency on a point-to-point link.

Exercise 6.4

Questions

1. What is the default level that is set on a router? The default level of a route is L1/L2.

2. Which level should a router that connects multiple areas be set to?

A router that only connects between other areas should be set to L2.

3. A router that connects to only those routers in its area should be set to which level (L1, L2, or L1/L2?

A router that connects to only routers in its own area should be configured as an L1

router.

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

57

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Appendix B Lab Solutions The configurations on

Appendix B Lab Solutions

The configurations on the following pages are sample solutions for Pod 1. Other solutions are possible.

Verification commands

Use the commands in Table 8-1 for verification of the lab exercises. Use the subcommands for more detailed information. Other commands may also be used. Refer to your courseware for more information.

Command

Results

Admin display-config

Shows the router configuration

show router route

Shows the routing table

configure router# info

Provides information about the configuration of your router

show router isis

Provides information about the IS-IS process

show route ospf

Provides information about the OSPF protocol attributes

show router vrrp

Shows the VRRP process

show router vrrp instance interface

Provides VRRP information about a specific interface

XXX

show cflowd

Provides information about the cflowd operation

show filter

Shows the status of the filter you created

trace

Traces the path being taken

ping

Sends ICMP echo packets

Table 8-1: Lab verification commands

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

58

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Exercise 1.2

Configure IP addressing and define the interfaces on your pod’s routers:

Core-Pod1>config>router# interface "system" Core-Pod1>config>router>if# address 172.16.1.1/32 Core-Pod1>config>router>if# exit Core-Pod1> config>router# interface "loopback" Core-Pod1> config>router>if$ address 172.16.1.2/32 Core-Pod1> config>router>if$ loopback Core-Pod1> config>router>if$ exit Core-Pod1>config>router# interface "C1-E1” Core-Pod1>config>router>if# address 172.16.2.1/30 Core-Pod1>config>router>if# port 1/1/1 Core-Pod1>config>router>if# no shutdown Core-Pod1>config>router>if# exit Core-Pod1>config>router# interface "C1-C2” Core-Pod1>config>router>if# address 172.31.1.1/30 Core-Pod1>config>router>if# port 1/1/2 Core-Pod1>config>router>if# no shutdown Core-Pod1>config>router>if# exit Core-Pod1>config>router# interface "C1-C3” Core-Pod1>config>router>if# address 172.31.2.1/30 Core-Pod1>config>router>if# port 1/1/3 Core-Pod1>config>router>if# no shutdown Core-Pod1>config>router>if# exit Core-Pod1>config>router# interface "C1-C4” Core-Pod1>config>router>if# address 172.31.3.1/30 Core-Pod1>config>router>if# port 1/1/4 Core-Pod1>config>router>if# no shutdown Core-Pod1>config>router>if# exit

Exercise 2.1

Configure a default static route on the edge router:

Edge-Pod1# configure router static-route 0.0.0.0/0 next-hop 172.16.2.1

Exercise 2.3

Configure floating static routes and test them by shutting down the primary path. When completed, activate the primary path:

configure router static-route 172.19.1.1/32 next-hop 172.31.1.2 preference 200

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

59

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Exercise 3.1 Build a link state database

Exercise 3.1

Build a link state database for rtr1 that consist of the link state information from the other routers in order to perform SPF calculation for a given path.

Rtr1 link state packet

Rtr1 to rtr2

10

Rtr1 to rtr3

20

Rtr2 link state packet

Rtr2 to rtr1

10

Rtr2 to rtr3

20

Rtr2 to rtr4

5

Rtr3link state packet

Rtr3 to rtr1

20

Rtr3 to rtr2

20

Rtr3 to rtr5

20

Rtr4 link state packet

Rtr4 to rtr2

5

Rtr4 to rtr5

80

Rtr5 link state packet

Rtr5 to rtr4

80

Rtr5 to rtr3

20

Exercise 4.1

Configure OSPF on your pod routers:

Configure OSPF

Edge-Pod1>config>router# ospf Edge-Pod1>config>router>ospf$ area 0.0.0.0 Edge-Pod1>config>router>ospf>area$ interface E1-C1 Edge-Pod1>config>router>ospf>area>if$ exit Edge-Pod1>config>router>ospf>area$ interface E1-A1 Edge-Pod1>config>router>ospf>area>if$ exit Edge-Pod1>config>router>ospf>area# interface EL-1 Edge-Pod1>config>router>ospf>area>if$ exit Edge-Pod1>config>router>ospf>area# interface EL-2 Edge-Pod1>config>router>ospf>area>if$ exit Edge-Pod1>config>router>ospf>area# interface system Edge-Pod1>config>router>ospf>area>if$ exit

Edge-Pod1>config>router>ospf>area#

Core-Pod1>config>router# ospf Core-Pod1>config>router>ospf$ area 0.0.0.0 Core-Pod1>config>router>ospf>area$ interface C-E Core-Pod1>config>router>ospf>area>if$ exit Core-Pod1>config>router>ospf>area# interface C1-C2 Core-Pod1>config>router>ospf>area>if$ exit Core-Pod1>config>router>ospf>area# interface C1-C3 Core-Pod1>config>router>ospf>area>if$ exit Core-Pod1>config>router>ospf>area# interface C1-C4 Core-Pod1>config>router>ospf>area>if$ exit Core-Pod1>config>router>ospf>area# interface CL-1

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

60

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Core-Pod1>config>router>ospf>area>if$ exit Core-Pod1>config>router>ospf>area# interface CL-2 Core-Pod1>config>router>ospf>area>if$ exit Core-Pod1>config>router>ospf>area# interface system

Core-Pod1>config>router>ospf>area>if$

Exercise 5.1

Change to an OSPF multiple-area topology, and implement summarization:

Modify the core router

Core-Pod1>config>router# ospf Core-Pod1>config>router>ospf# area 0.0.0.0 Core-Pod1>config>router>ospf>area# interface "C1-C2" Core-Pod1>config>router>ospf>area>if# exit Core-Pod1>config>router>ospf>area# interface "C1-C3" Core-Pod1>config>router>ospf>area>if# exit Core-Pod1>config>router>ospf>area# interface "C1-C4" Core-Pod1>config>router>ospf>area>if# exit Core-Pod1>config>router>ospf>area# exit Core-Pod1>config>router>ospf>area$ interface "system" Core-Pod1>config>router>ospf>area>if$ exit Core-Pod1>config>router>ospf>area# interface "CL-1" Core-Pod1>config>router>ospf>area>if# exit Core-Pod1>config>router>ospf>area# interface "CL-2" Core-Pod1>config>router>ospf>area>if# exit Core-Pod1>config>router>ospf# area 0.0.0.1 Core-Pod1>config>router>ospf>area# interface "C1-E1" Core-Pod1>config>router>ospf>area>if# exit

Modify the edge router

Edge-Pod1>config>router# ospf Edge-Pod1>config>router>ospf# area 0.0.0.1 Edge-Pod1>config>router>ospf>area$ interface "E1-C1" Edge-Pod1>config>router>ospf>area>if$ exit Edge-Pod1>config>router>ospf>area# interface "system" Edge-Pod1>config>router>ospf>area>if# exit Edge-Pod1>config>router>ospf>area# interface "EL-1" Edge-Pod1>config>router>ospf>area>if# exit Edge-Pod1>config>router>ospf>area# interface "EL-2" Edge-Pod1>config>router>ospf>area>if# exit

Exercise 5.3

Configure your area as a stub and then an enhanced stub configuration:

Edge-Pod1# configure router ospf Edge-Pod1>config>router>ospf# area 0.0.0.1 Edge-Pod1>config>router>ospf>area# stub

Edge-Pod1>config>router>ospf>area>stub#

Core-Pod1# configure router ospf Core-Pod1>config>router>ospf# area 0.0.0.1 Core-Pod1>config>router>ospf>area# stub

Exercise 5.4

Configure your area as a stub with no summaries and with network summarization:

Core-Pod1>config>router>ospf>area# stub no summaries

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

61

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Summarize the areas Core-Pod1# configure router ospf

Summarize the areas

Core-Pod1# configure router ospf Core-Pod1>config>router>ospf# area 0.0.0.0 Core-Pod1>config>router>ospf>area# area-range 172.31.0.0/30 Core-Pod1>config>router>ospf>area# exit Core-Pod1>config>router>ospf# area 0.0.0.1 Core-Pod1>config>router>ospf>area# area-range 172.16.0.0/16

Exercise 5.5

Change to an NSSA and subsequently to an enhanced NSSA configuration:

Edge-Pod1# configure router ospf Edge-Pod1>config>router>ospf# area 0.0.0.1 Edge-Pod1>config>router>ospf>area# nssa

Edge-Pod1>config>router>ospf>area>nssa#

Core-Pod1>config>router# ospf Core-Pod1>config>router>ospf# area 0.0.0.1 Core-Pod1>config>router>ospf>area# nssa

Core-Pod1>config>router>ospf>area# nssa no summaries Core-Pod1>config>router>ospf>area# nssa originate-default-route

Exercise 5.6

Remove NSSA and configure a virtual link:

Core-Pod1>config>router# ospf Core-Pod1>config>router>ospf# area 0.0.0.1 Core-Pod1>config>router>ospf>area# no nssa Core-Pod1>config>router>ospf>area# virtual-link 172.16.8.1 transit-area 0.0.0.1

Edge-Pod1# configure router ospf Edge-Pod1>config>router>ospf# area 0.0.0.1 Edge-Pod1>config>router>ospf>area# no nssa Edge-Pod1>config>router>ospf# area 1.1.1.1 Edge-Pod1>config>router>ospf>area# interface "EL-1" Edge-Pod1>config>router>ospf>area>if# exit Edge-Pod1>config>router>ospf>area# interface "EL-2" Edge-Pod1>config>router>ospf>area>if# exit Edge-Pod1>config>router>ospf# area 0.0.0.0 Edge-Pod1>config>router>ospf>area$ virtual-link 172.16.1.1 transit-area 0.0.0.1

Exercise 6.1

Configure IS-IS for a single area:

Core-Pod1# configure router isis Core-Pod1>config>router>isis$ area-id 49.0051 Core-Pod1>config>router>isis# interface C1-E1 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface C1-C2 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface C1-C3 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface C1-C4 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface CL-1 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface CL-2

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

62

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# exit

Edge-Pod1>config>router# isis Edge-Pod1>config>router>isis$ area-id 49.0051 Edge-Pod1>config>router>isis$ interface E1-C1 Edge-Pod1>config>router>isis>if$ exit Edge-Pod1>config>router>isis# interface EL-1 Edge-Pod1>config>router>isis>if# exit Edge-Pod1>config>router>isis# interface EL-2 Edge-Pod1>config>router>isis>if# exit Edge-Pod1>config>router>isis# interface system Edge-Pod1>config>router>isis>if# exit

Exercise 6.2

Implement authentication for IS-IS updates:

Core-Pod1>config>router>isis# authentication-type message-digest Core-Pod1>config>router>isis# authentication-key Alcatel

Edge-Pod1>config>router>isis# authentication-type message-digest Edge-Pod1>config>router>isis# authentication-key Alcatel

Exercise 6.3

Migrate to a multiple-area IS-IS configuration:

Core-Pod1>config>router# isis Core-Pod1>config>router>isis# shutdown Core-Pod1>config>router>isis# exit Core-Pod1>config>router# no isis Core-Pod1# configure router isis Core-Pod1>config>router>isis# area-id 40.0001 Core-Pod1>config>router>isis# interface system Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface CL-1 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface CL-2 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface C-E Core-Pod1>config>router>isis>if# level-capability level-1 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface C1-C2 Core-Pod1>config>router>isis>if# level-capability level-2 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface C1-C3 Core-Pod1>config>router>isis>if# level-capability level-2 Core-Pod1>config>router>isis>if# exit Core-Pod1>config>router>isis# interface C1-C4 Core-Pod1>config>router>isis>if# level-capability level-2 Core-Pod1>config>router>isis>if# exit

Core-Pod1>config>router>isis#

Edge-Pod1>config>router# isis Edge-Pod1>config>router>isis# shutdown Edge-Pod1>config>router>isis# exit Edge-Pod1>config>router# no isis Edge-Pod1>config>router# isis Edge-Pod1>config>router>isis$ area-id 49.0001 Edge-Pod1>config>router>isis$ level-capability level-1 Edge-Pod1>config>router>isis$ interface E1-C1

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

63

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Confidential for Internal Use ONLY - Do Not Distribute Edge-Pod1>config>router>isis>if$ exit

Edge-Pod1>config>router>isis>if$ exit Edge-Pod1>config>router>isis# interface EL-1 Edge-Pod1>config>router>isis>if# exit Edge-Pod1>config>router>isis# interface EL-2 Edge-Pod1>config>router>isis>if# exit Edge-Pod1>config>router>isis# interface system Edge-Pod1>config>router>isis>if# exit Edge-Pod1>config>router>isis# interface E1-C1 Edge-Pod1>config>router>isis>if# level-capability level-1

Exercise 6.4

Configure summary advertisements on the core router for your pod area:

Core-Pod1>config>router>isis# summary-address 172.16.0.0/16 level-2 Core-Pod1>config>router>isis# exit

http: / /www.alcatel-lucent.com

Alcatel-Lucent Interior Routing Protocols Lab Guide v2.3

64