Table of Contents
LAB 1 HARDWARE CONFIGURATION ...............................................................................................................3
SECTION 1.1 SYSTEM IDENTIFICATION ...................................................................................................................3
SECTION 1.2 SYSTEM CONFIGURATION ..................................................................................................................4
SECTION 1.3 HARDWARE ........................................................................................................................................6
SECTION 1.4 LOGS ..................................................................................................................................................8
LAB 2 IP ADDRESSING AND ROUTING ............................................................................................................11
List of Figures
Figure 1 Two Enterprises linked to a common ISP ............................................................ 11
Figure 2 Two ISPS............................................................................................................. 13
Figure 3 Static routes CE to PE and P, PE to CE ............................................................... 21
Figure 4 OSPF in each ISP ................................................................................................. 26
Figure 5 BGP between ISPs and within ISPs ..................................................................... 30
The CLI system prompt will now display the system name.
Login to your node using the default login (admin) and password (admin).
This will save the configuration to the config.cfg file shown above in the bof output
To save the configuration to a different file name, the exact location and name of the
file must be specified
RX# admin save
- save [<file-url>] [detail] [index]
<file-url>
a. Verify that the IP address is the management IP address used to login to the router
b. Verify the Management Ethernet port configuration settings.
<detail>
<index>
<remote-locn>/][<file-path>]
cf1:|cf1-A:| cf3:|cf3-A:|cf3-B:
: keyword - Adds default configuration
: keyword - Forces a save of the index file
The location here can be a compact flash location, ftp server or tftp server
2. The next step is to configure the daughter card slots on the IOM
RX# show mda
RX>config>card# mda 1
RX>config>card>mda# mda-type m60-10/100eth-tx (this can be different,
Please verify the correct mda in the slot by doing a show mda <card>)
RX>config>card>mda# no shutdown
3. Confirm that the configurations were correctly done by using the following
commands. The equipped card type and the provisioned card type listed in the CLI
window should be identical.
RX# show card 1
RX# show mda 1/1
1. In this step the student is not actually configuring the IOM card. The student is
configuring the card slot. The IOM card itself already knows what it is. This
command shows what type of cards it should expect to see installed.
4. Note: The cards and MDAs can be configured incorrectly; there is no visible warning
to determine if these components were wrongly configured other than the default
alarm logs (see Configuring Alarms Section 1.4). Although the router will accept an
incorrect configuration, any service on the incorrectly configured cards/MDAs will
not work correctly
RX>config>port 1/1/1
RX>config>port#> no shut
RX>config# port 1/1/[1..4] no shut
(This command will enable you to configure a string of ports at one time. In this case,
this command will turn all 4 ports administratively on.)
6. Use the following commands to verify that the configurations at the port level are
correct and functioning properly.
RX# show port
RX# show port 1/1/1 detail
(The detail extension on a show command will display everything possible about the
item specified. This command is very useful in troubleshooting.)
5. Once the cards are correctly configured then configure the ports on the MDAs.
Unlike the cards where it was a hierarchical configuration structure, the ports are not
configured as part of the MDA hierarchy. The student must exit back to the root and
then enter into the port configuration mode. The ports are identified by first
identifying the IOM, then the MDA and then the port (1/1/1). By default, the ports on
a 60 port 10/100 card are network mode with a MTU of 1514. The default settings
will suffice for the remainder of this course.
RX>configure>log>log-id$ exit
RX# show log log-id 21
2. Using the same configuration steps that you have just completed for step 1, repeat the
process to configure three other log files using the following parameters:
Description:
Log id:
Log Source:
Destination
Description:
Log-id:
Log Source:
Destination:
Debug-Trace
23
debug-trace
session
Description:
Log-id:
Log Source:
Destination:
Change Log
24
change
memory
RX# configure log log-id 21 (the range is 1-100 however 99,100 are
reserved)
Observe all the events in the change log. What kind of events are logged here?
d. Observe the Debug log
Note: This will be viewed when debug events are turned up in succeeding labs
e. Observe the Main log
RX# configure port 1/1/5 no shut
RX# exit
Compare the output of the info command to the output obtained at the beginning of this
step. Is there a difference and why?
4. Configuring and viewing alarms
Alarms on the 7x50 are not directly displayed. Two log files (log id 99 and log id 100)
are configured automatically on startup to capture alarm events for layer 1 and layer 2.
To view these alarms execute
admin save
10
Ent. B.2
30 hosts
300 hosts
Ent. A.1
ISP
Ent. B.1
90 hosts
Ent. A.2
60 hosts
11
Two enterprises, A and B are connected to a central Tier 2 ISP. A.1 and A.2 are two of
Enterprise As locations connected to the Tier 2 ISP and B.1 and B.2 are two of
Enterprise Bs locations connected to the same Tier 2.
The ISP has a public IP addressing space of 138.120.16.0/20. The Enterprises A and B
lease their IP addressing from their ISP. Enterprise A requires an IP addressing scheme
that can scale to at most 30 nodes in location A.1 and 60 nodes in location A.2. The
Enterprise B requires an IP addressing scheme with at most 90 nodes in location B.1 and
less than 300 nodes in location B.2. The ISP can only lease 500 IP addresses (among the
two enterprises) and will utilize the last part of its assigned sub-network to both the
enterprises.
Hint: Divide the assigned ISP IP sub-network into equal blocks satisfying the smallest
requirement and then combine the smaller blocks into aggregate or non aggregate
blocks.
Entity
ISP Network
Subnetwork Assigned to
Enterprise A and B
Number of Host
Addresses
4094
IP Network
138.120.16.0/20
510
Enterprise A
Location A.1
Location A.2
Enterprise B
Location B.1
Location B.2
12
CE2/R10
P1/R1
PE2/R6
ISP 1
P4/R4
P3/R3
PE3/R7
P2/R2
ISP 2
PE4/R8
CE3/R11
CE4/R12
Figure 2 Two ISPS
There are two ISPs shown in the above diagram. ISP 1 consists of routers P1, P2, PE5
and PE6. ISP 2 consists of routers P3, P4, PE3 and PE4.
P1 and P2, P3 and P4 are considered provider routers and serve as transit points to other
provider routers. PE1 and PE2, PE3 and PE4 are provider edge routers and connect to the
ISP customers. These routers provide Internet and other network access to the ISP
customers.
13
PE1/R5
CE 1 and CE2 are customer edge routers that represent customers of ISP 1. CE3 and CE4
are routers that represent customers of ISP2. These routers provide traffic from the ISP to
the various customer entities
Each ISP is assigned the following public address space by IANA
ISP 1
ISP 2
140.10.0.0/24
150.10.0.0/24
Requirements
1. The first 32 addresses in the assigned IP space for both ISPs are reserved for system
and other internal loopback addresses on the P, PE. Each of the routers in the ISP and
will require a system address from this block
2. The next 64 addresses in the assigned IP space for both ISPs are reserved for future
use.
3. All customer routers on both ISPs are connected to at most 60 hosts. So each ISP
needs to assign two 60 host addressing schemes to represent all the customers.
4. All inter router links including CE-PE router links within each ISP are point to point
links, however for the sake of convenience, they should be assigned /30 based
addresses.
5. ISP 1 and ISP2 provider routers are physically connected to each other but are not
peering to each other.
ISP Number 1
Router
PE1
P1
PE2
Port
Interface name
System
toP1
toPE2
toCE1
System
toP3
toP2
toPE1
System
toP2
IP Address
Not used
14
Your task is to design an IP sub-network based on the address space provided and assign
the sub networks to the various routers based on the following requirements which are the
same for both ISPs. Note: All students assigned to each of the ISP must collaborate
together.
P2
CE1
CE2
ISP Number 2
Router
PE3
P3
PE4
P4
CE3
CE4
Port
Interface name
System
toP3
toPE4
toCE3
System
toP1
toP4
toPE3
System
toP4
toPE3
toCE4
System
toPE4
toP3
toP2
System
toPE3
Aggregate
System
toPE4
Aggregate
Not used
Not used
Not used
toPE1
toP1
System
toPE2
toP4
toP1
System
toPE1
Aggregate
System
toPE2
Aggregate
IP Address
Not used
Not used
Not used
Not used
15
2. Assign the IP address to the system interface as per the above table on the PE and P
routers.
XXX>config>router
XXX>config>router# interface system
XXX>config>router>if# address xxx.xxx.xxx.xxx/32
XXX>config>router>if# exit
3. Assign the IP addresses to the rest of the interfaces on the CE, PE and P routers. The
difference between these interfaces and the system interface is the fact that the nonsystem interfaces require the addition of a physical port.
a. The system interface, being a loopback or virtual interface, does not have a
physical port assigned to it.
b. Other non-system interfaces can also be created as loopback interfaces (as
shown below) and also not required the addition of a physical port. However
they need to be explicitly configured as a loopback interfaces by specifying
the command loopback.
c. The customer networks on the CE router can be specified as a loopback
interface for the purpose of aggregation, however on the loopback interface, a
single host address in the customer network needs to be defined.
Interface Type
Normal
System
Loopback
Name
Any String
system
Any String
Loopback
No
Implicit
Explicit
Subnet Mask
/8-/31
/32
/8-/31
Port Config
Required
None
loopback
16
1. Using the following command take a look at any existing interfaces on the router.
Notice that the system interface is already created. This interface exists by default
and cannot be removed. The only requirement is to assign the system interface with
an IP address. The system interface will be automatically used by the various routing
protocols as the router-id.
4. Continue until all the interfaces have been assigned an IP address and the interface
has been associated to the correct port. Once completed, use the show command to
see the status of the router interfaces that have just been created. The administrative
and operational status should both be up. If an interface shows operationally down,
this could be indicative of a physical problem. Use the info command to view the
configuration of the router interfaces to ensure that they have all (with the exception
of the System interface) been associated with a port.
5. Using the show command, check the route tables of all the CE, PE and P routers in
your ISP. Notice the routes that now appear in the route table and take note of their
protocol type. The PE routers should see 4 routes in the route table while the P
routers should see 4 routes in the route table.
XXX>show router route-table
Is there a difference between the outputs of the show router interface command and
the show router route-table command? What is the difference?
__________
6. Using the ping command, check connectivity from a router to the distant end of each
of its interfaces to the neighboring routers. For example, on the PE routers check the
connectivity to the distant end of the interface connecting it to the P router and on the
CE router, check the connectivity to the PE router.
XXX>ping xxx.xxx.xxx.xxx
17
2. From the edge devices, attempt to ping the IP address of the far-end interface to your
core router, using your edges system interface address as the source address. Observe
the debug ICMP messages on the core routers.
3. To verify ARP operation by the router, turn on debug IP ARP on the routers in any
ISP (P1-P2, P3-P4, PE1 and PE2, PE3 and PE4) routers. Execute the following
command on each of the routers
XXX>
XXX>
XXX>
XXX>
4. NOTE: Wait until all students are at this point before proceeding.
From any PE router, attempt to ping the system interface IP address of all the other
directly connected routers. Observe the debug ARP message. Verify the ARP entry
for the neighboring interface has been added
XXX> show router arp
How many ARP entries are on each router at this point? __________
5. From any P router, attempt to ping the network interface IP address of all the other
connected routers. Observe the debug ARP message. Verify the ARP entry for the
neighboring interface has been added
XXX> show router arp
How many ARP entries are on each router at this point? __________
18
Explain
________________________________________________________________________
________________________________________________________________________
19
1. The first step is to define the network that the operator wishes to reach. In this case it
will be the address of the system interface of the distant router. Once that is defined
then the router must be informed of which interface to send the information out of to
reach the distant network. Note, when defining the next-hop interface information,
the IP address used is the distant IP address of the interface not the local IP address of
the router interface. Log in to the PE router and configure a static route using the
following command structure. The first IP address defined is the destination network
plus mask. In this case it is the system interface of the P router. The second IP
address defined is the IP address of the P end of the interface that connects the P to
the PE.
XXX>configure
xx.xx.xx.xx
router
static-route
xx.xx.xx.xx/yy
next-hop
2. The next step is to log on to the P routers and configure a static route to the system
interface of the PE router. The command structure is the same as above. The only
thing that will change is the IP addresses.
3. Once completed, verify connectivity between the P and PE routers in your pod by
pinging the system interface of the other router.
XXX>ping xxx.xxx.xxx.xxx
4. View the contents of the routing table and answer the following questions.
XXX>show router route-table
In this exercise the student will configure a static route from the PE to the P router and
from the P router to the PE router that will allow both routers to ping the system interface
of each other. At this point, the operator can only ping the interfaces that are directly
connected to the router. This is because those are the only networks that are known by
the router. Should the operator at the PE router attempt to ping the system interface of
the P router it will fail as the PE router has no route to the destination (it is not shown in
the route-table).
Section
ction 3.2 Default Routes and Router Logic
Objective:
In this exercise the student will configure a default route on the Customer Edge CE
router. The purpose of this default route is to allow IP connectivity from the CE router to
the rest of the routers in the network. This is possible due to the fact that the CE router
has only one interface towards the ISP core. Therefore, if the destination is not local, it
must be out that interface.
CE2/R10
PE1/R5
P1/R1
PE2/R6
ISP 1
P4/R4
P3/R3
PE3/R7
P2/R2
ISP 2
PE4/R8
CE3/R11
CE4/R12
21
CE1/R9
For this exercise, the CE devices will configure default routes towards their
connected PE router. Each P and PE router will configure static routes for the CE
networks (the aggregate networks that were created as part of the subnetwork exercise
in Section 2.2) connected to their local ISP. For example P1 and PE1 will each
configure a static route to CE1 networks and another static route to the CE2 networks.
Note that each P and PE router will configure 2 static routes for each CE.
2. Log on to the core (P and PE) routers and configure static routes for each CE
customer network address of the CE routers in your local ISP. For each network,
there are 2 paths through your ISP. For this exercise, you will enter both static routes
into each P/PE router. The difference will be the metric value that is used. The value
of the metric is the total number of routers (including the local router) traversed to
reach the destination device.
XXX>configure
router
xx.xx.xx.xx metric z
static-route
xx.xx.xx.xx/yy
next-hop
3. Use the show command to verify the existence of the default and static routes.
XXX>show router route-table
How many routes are there in the P/PE routers routing table? _______
Explain?
_____________________________________________________________________
_____________________________________________________________________
4. Once everyone has completed the default route configuration log on to the CE router
and ping and traceroute the various system interfaces of the various routers within the
network. Log into the P and PE router and try to ping the configured host address on
both the CE routers in the ISP
XXX>ping xxx.xxx.xxx.xxx
22
1. To configure a default route is to configure a static route. The only difference is the
destination network and mask information. In a default route, the wild card network
and mask is used to match all network prefix values that do not match anything else
in the route-table. Use the following configuration on the edge router of your pod.
For the next hop use the interface as defined on the previous page.
What path is being taken to the other CE within your local ISP?
____________________________________________________________________
23
CE Routers Only:
6. Create and describe the filter ip instance on the CE device
XXX> configure filter ip-filter 77 create
XXX>config>filter>ip-filter$ description Block ICMP to Customer
network
8. Deny access to all host address range only for ICMP echo-requests. Note: We will
match in the ingress direction.
XXX>config>filter>ip-filter$ entry
XXX>config>filter>ip-filter>entry$
XXX>config>filter>ip-filter>entry$
request
XXX>config>filter>ip-filter>entry$
XXX>config>filter>ip-filter>entry$
10 create
match dst-ip xx.xx.xx.xx/yy
match protocol 1 icmp-type echoaction drop
exit all
9. From the PE, ping the attached CEs configured loopback host IP address.
Successful? _____
Explain:
_____________________________________________________________________
_____________________________________________________________________
10. Apply the filter on the CE to the router interface connected to the PE device
XXX> configure router interface toPEx
XXX >config>router>if$ ingress filter ip 77
24
To configure an IP filter, we must first determine the address and protocol types that we
will be allowing access to, and the direction where the filter will be applied. In this case,
we will be blocking access to any of the CE customer host addresses from the protocol
ICMP (IP Protocol type 1). We will block access in the INGRESS direction on the CE
interface towards the PE.
11. From the PE, ping the attached CEs configured host loopback address. Successful?
_____
12. From the CE, ping the attached PEs system IP addresses. Successful? _____
Explain:
_____________________________________________________________________
_____________________________________________________________________
15. Deny access to the system IP address only for ICMP echo-requests. Note: We will
match in the ingress direction, so the packets will destined to the system IP address.
XXX>config>filter>ip-filter$ entry
XXX>config>filter>ip-filter>entry$
XXX>config>filter>ip-filter>entry$
request
XXX>config>filter>ip-filter>entry$
XXX>config>filter>ip-filter>entry$
10 create
match dst-ip xx.xx.xx.xx/yy
match protocol 1 icmp-type echoaction drop
exit all
16. Apply the filter to the router interface connected to the CE device
XXX>configure router interface toCEx
XXX>ingress filter ip 77
17. From the PE, ping the attached CEs loopback host IP address. Successful? _____
18. From the CE, ping the attached PEs system IP address. Successful? _____
Explain:
_____________________________________________________________________
_____________________________________________________________________
25
CE1/R9
CE2/R10
PE1/R5
P1/R1
PE2/R6
OSPF
P2/R2
ISP 1
P3/R3
PE3/R7
P4/R4
ISP 2
OSPF
PE4/R8
CE3/R11
CE4/R12
NOTE: Remove all static routes configured in the P and PE devices in the previous
labs. DO NOT remove the static routes to CE networks on the PE.
26
In this exercise the student will configure a single area OSPF network for each ISP. This
lab will demonstrate the different databases that are created by the OSPF routing
protocol.
1. The first step is to enable the OSPF routing process on the router
XXX# configure router ospf
2. Next define the area that the interfaces will be placed in. Remember that the area
must match between routers connected on the same interface for OSPF to establish an
adjacency. The objective of this exercise is to configure a single area OSPF network;
therefore, all students should use the same area number.
XXX#>config>router>ospf$ area 0
Continue until all the interfaces on the PE and P routers, within the ISP, are entered
into the OSPF process in area 0.
XXX>show router route-table
a. How many routes in the table? ________
b. What is the preference and metric value of each OSPF Route?
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
4. Use the show command to look at the OSPF neighbors of the P routers.
XXX>show router ospf neighbor
a. How many neighbors do you see on the P devices? _____ PE? _____ CE? _____
b. What is the state of their adjacency? ____ Why?
____________________________________________________________________
____________________________________________________________________
Use the following command to show the ospf link state database. This database is a
listing of all LSAs that have been received by the router. It is these LSAs that the SPF
algorithm uses to create the forwarding table.
XXX# show router ospf database detail
27
3. Now enter into this area all the interfaces that you want OSPF to operate on and send
out its advertisements. In this case, place all the PE and P router interfaces inside the
local ISP into the OSPF process area 0. Note that ISPs rarely exchange routes with
each other using an IGP protocol of any sort.
a. What
types
of
LSAs
are
in
the
database?
_______________________________________________________________
_______________________________________________________________
b. Is the database consistent on all the ISP routers? _______
5. Once everyone has completed the OSPF configuration login to the P router and ping
the other PE router system interfaces.
XXX>ping xxx.xxx.xxx.xxx
6. To reach the CE networks from any of the PE and P routers, the CE networks need to
be distributed into OSPF running on PE and P routers. The static routes to the CE
networks are defined on the PE routers and need to be distributed on the PE routers.
To do this:
a. the PE router must be configured as an ASBR (Autonomous System Border
Router). The ASBR configuration under OSPF enables a router running the OSPF
routing protocol to distribute networks external to the OSPF domain into OSPF.
In this case the static routes to the CE networks are not part of the ISP OSPF
domain.
On the PE router
XXX#>config>router>ospf>area 0# asbr
XXX>config>router>policy-options>policy-statement$ entry 10
XXX>config>router>policy-options>policy-statement>entry$
from protocol static
XXX>config>router>policy-options>policy-statement>entry#
action accept
XXX>config>router>policy-options>policy-statement>entry>action#
back
XXX>config>router>policy-options>policy-statement>entry# back
XXX>config>router>policy-options>policy-statement# back
XXX>config>router>policy-options# commit
XXX>config>router>policy-options# exit all
XXX>config>router>ospf# export Export_Routes
28
7. From the PE and the P routers, ping all the CE networks (i.e. ping the CE host
loopback address) within the ISP
Which devices were reachable? _______________________________
Which devices were not reachable? ______________________________
Explain?
_____________________________________________________________________
___________________________________________________________________
29
PE1/R5
P1/R1
PE2/R6
OSPF
P2/R2
ISP 1
BGP
P3/R3
PE3/R7
ISP 2
OSPF
P4/R4
PE4/R8
CE3/R11
CE4/R12
Figure 5 BGP between ISPs and within ISPs
30
CE2/R10
CE1/R9
2. P1 and P3, P2 and P4 will be configured as external BGP peers (eBGP). Note that
eBGP peers typically use the next-hop interface IP address as the neighbor address.
Since the ISPs will now be peering (share an IP network) between them, assign the
link between P1 and P3 host addresses from 145.0.0.10/31 and the link between P2
and P4 will be assigned hosts from the 145.0.0.20/31 network.
3. P1 and P2, P3 and P4 will be configured as internal BGP peers (iBGP). Note that
iBGP peers typically use the system interface IP address as the neighbor address.
XXX#>config>router# bgp group iBGP
XXX#>config>router>bgp>group$ neighbor xx.xx.xx.xx
XXX#>config>router>bgp>group>neighbor$ peer-as <local AS>
4. At this point, each P router should have one internal and one external BGP session.
xxx# show router bgp summary
5. We can see the advertised routes for reach neighbor using the following command.
xxx# show router bgp neighbor xx.xx.xx.xx advertised-routes
routes to other BGP peers. The most accepted way to originate a route from an ISP is
to create a black-hole static route for all aggregates to be advertised. This will ensure
these routes always exit to eliminate IGP related route flapping. Create the black-hole
static route for the aggregate of your local ISP. A black hole indicates that traffic for
a particular route will be discarded unless a more specific route exists in the routing
table. A black hole static-route only makes sense from an aggregation view point. For
e.g if there are the following routes in the routing table
XXX# configure router static-route xx.xx.xx.xx/yy black-hole
preference 250
31
8. Execute the following set of commands on the core routers (R1-R4). This will export
all static routes to the eBGP peers.
32
Lab 6 Services
Section 6.1: Services Framework
Objective:
CE1/R9
CE2/R10
PE1/R5
PE2/R6
P2/R2
P1/R1
OSPF
P3/R3
PE3/R7
In order to complete the next group of labs, we need to create a topology to support the
services we will deploy. The two service providers from the previous sections have
merged into one and are offering a VPLS service across their network. As long as routes
exist to the system addresses of all the PE devices in the provider network, a VPLS
service can be created. The new service provider is running OSPF as the IGP for their
core network.
P4/R4
PE4/R8
CE3/R11
CE4/R12
33
2) The MPLS signaling protocol that will be used in the following section is LDP. LDP
must be enabled on ALL interfaces that will be required to perform MPLS Label
exchange.
XXX#>configure router ldp interface-parameters interface toP_
XXX#>config>router>ldp>if-params>if$ exit
XXX#>configure router ldp no shut
34
1) In the previous lab, routing between ISPs is provided by BGP. Since the ISPs have
merged, they will be merged into one routing domain, running OSPF as their IGP.
The interfaces between R1 and R3 and between R2 and R4 must be added to OSPF to
make this a single routing domain.
each of the other 3 PEs. The SDP is identified by an integer and we will use the router
number (5, 6, 7 or 8) of the far end PE to identify the SDP. So, PE1 (R5) will have 3
SDPs numbered 6, 7 and 8 to each of the other three PEs.
XXX#>configure service sdp x mpls create
XXX#>config>service>sdp$ far-end xxx.xxx.xxx.xxx
XXX#>config>service>sdp$ ldp
XXX#>config>service>sdp$ no shutdown
In the following service labs, the Customer Edge devices will be configured as traditional
routers. Each CE router has an interface in the same IP subnet. The VPLS service will
join these four routers in the same way an Ethernet switch would join them. The
following configuration is required on each CE device
1) Create the router interface on the interface connecting the CE to the service enabled
PE devices.
XXX#>configure router interface servicesCE_
XXX#>config>router>if$ address 192.168.1.x/24
XXX#>config>router>if$ port X/Y/Z
XXX#>config>router>if$ no shutdown
Part 4: Verification
NOTE: Wait till your peer nodes are also at this step before proceeding.
35
1) LDP is the protocol used for signaling which tunnel labels will be PUSHed,
SWAPped, POPped while data traverses the LSP. To view which labels will be used,
and their function use the following command
XXX# show router ldp bindings active.
2) CE Connectivity:
a. How many OSPF adjacencies are there on your CE device? _____
b. Ping the other CE devices in the network (ping 192.168.1.x).
Explain the results?
________________________________________________________________________
________________________________________________________________________
36
CE1/R9
CE2/R10
PE1/R5
PE2/R6
SAP
SAP
P2/R2
P1/R1
VPLS 1
P3/R3
PE3/R7
SAP
A VPLS is a layer 2 service that can connect multiple sites in one LAN. Its like creating
a virtual Switch out of a network of Service Routers. In this lab, we will create a VPLS
across all the PE nodes. The PE devices will connect to each other with a full mesh using
mesh-sdp. Note that after the service reference topology has been configured, adding
services from edge to edge does not require any further modification of the P devices.
P4/R4
PE4/R8
SAP
CE3/R11
CE4/R12
Figure 6 VPLS service in each ISP between PE and P routers with SAP connections to CE routers
37
2) SDPs are used to distribute services across multiple service routers, and therefore,
bind a transport tunnel to the service. You will need to create a mesh-sdp between
each PE router (R5-R8) to allow full communication across the PE routers. Each PE
router should have 3 mesh-SDPs at the conclusion of this step. Note that a mesh-sdp
will not forward a frame out another mesh-sdp, allowing for a loop free service
topology within the core.
Where x is the sdp # to the other PE routers. (R5=5, R6=6. R7=7, R8=8)
3) Service Access Points are used to attach CE devices to services on PE devices.
XXX#>configure service vpls 1 sap X/Y/Z create
Part2: Verification
NOTE: Wait till your peer nodes are also at this step before proceeding.
a. View the in-use Service LDP bindings on the P and PE routers. (U after label
indicates in-use)
XXX# show router ldp bindings fec-type services.
38
c. Services: Use the following command to determine the health of your services.
XXX#> show service service-using
a. How many services are there on each device in your POD? ______
b. What is their status? ______
c. Use the following command to find out more information about your service:
XXX#> show service id 1 base
d. On each PE device, we can see the MAC database per service using the
following command.
XXX#> show service id 1 fdb detail
i.
ii.
Where x is the SDP to the remote PE device (R5=5, R6=6, R7=7, R8=8)
i. How many OSPF adjacencies are there on your CE device? _____
ii. Ping the system IP addresses of all other CE devices in the lab.
39
b. Network Connectivity:
a. How many OSPF adjacencies are there on your CE device? _____
b. Are you able to ping the other CE devices in the lab? _____
c. Are you able to ping the system IP address of the P device from the CE
device? ____
d. Explain the results?
_______________________________________________________________
_______________________________________________________________
40
Explain.
__________________________________________________________________
__________________________________________________________________
Solutions
Exercise 1.3: Hardware
Sample Relevant Config
Exercise 2.1
41
Divide up the ISP address space into equal space 512 host addresses
138.120.16.0/22
138.120.20.0/22
138.120.24.0/22
138.120.28.0/22 - divide into 138.120.28.0/23 and 138.120.30.0/23
Take the last 138.120.30.0/23 and divide that into
A.1
30 hosts
138.120.30.32/27
138.120.30.64/27
A.2
62 hosts
138.120.30.96/27
138.120.30.128/26
B.1
92 hosts
138.120.30.192/26
138.120.31.0/24
B.2
316 hosts
138.120.30.0/27
Exercise 2.2
Divide 140.10.0.0/24 into 8/27 address spaces
140.10.0.0/27
140.10.0.32/27
140.10.0.64/27
140.10.0.96/27
Reserved
140.10.0.128/27
Aggregate
140.10.0.96/30
140.10.0.100/30
140.10.0.104/30
140.10.0.108/30
140.10.0.112/30
140.10.0.116/30
140.10.0.120/30
140.10.0.124/30
140.10.0.128/26
140.10.0.160/27
140.10.0.192/27
Aggregate
140.10.0.192/26
Split
Reserved
Unused
Unused
All interface addresses
Assigned to Customer
space
Assigned to customer
space
140.10.0.224/27
Exercise 2.3
42
5. Is there a difference between the outputs of the show router interface command
and the show router route-table command? What is the difference?
Yes there is a difference. The route table shows me the networks that are connected to my
router and the logical interface it is connected to. The router interface command shows
me the host address assigned to the port from the network that is used on my router along
with the physical port it is bound to.
Relevant Configuration from P1
Exercise 2.4
4. How many ARP entries are on each router at this point?
There are no ARP entries in my ARP table at this point. The routers do not know how to
reach the system addresses of other routers so no ARP responses are received.
5. How many ARP entries are on each router at this point?
I see entries for each of my directly connected peers. The MAC address belongs to the
remote routers interface. ARP entries are populated because all routers know of their
directly connected networks and will respond to ARP requests accordingly.
Exercise 3.1
5. View the contents of the routing table and answer the following questions.
43
How many routes are there in the P/PE routers routing table?
Even though I entered 4 static routes total on the router, only 2 are active in my
routing table. The router preferred the static-route with the lowest metric.
Exercise 3.3
9. From the PE, ping the attached CEs configured loopback host IP address.
Successful?
44
Exercise 3.2
YES. While the filter is created, it is not applied to any interface yet
11. From the PE, ping the attached CEs configured host loopback address?
Successful?
YES
12. From the CE, ping the attached PEs system IP addresses.
17. From the PE, ping the attached CEs loopback host IP address.
Successful?
YES. ICMP echo-requests are not blocked to the Loopback segment, ONLY the
system IP.
18. From the CE, ping the attached PEs system IP address.
Successful?
NO. The filter is now blocking ICMP echo-requests to both CE and PE system
addresses.
Sample PE Relevant Config
#-------------------------------------------------echo "Filter Configuration"
#-------------------------------------------------filter
ip-filter 77 create
default-action forward
description "Block ICMP to System Address"
entry 10 create
match protocol icmp
dst-ip 151.10.0.30/32
icmp-type echo-request
exit
action drop
exit
exit
exit
#-------------------------------------------------echo "Router (Network Side) Configuration"
#-------------------------------------------------interface "to-R12"
address 151.10.0.126/30
port 1/1/2
ingress filter ip 77
exit
45
Successful?
NO. The filter is blocking icmp echo-requests in only one direction therefore ping
works one way, but not the other.
Exercise 4.1
3.
c. How many routes in the table?
There are 5 OSPF routes in my routing table. 3 System Addresses and 2 Inteface
networks that are not directly connected to my local system
d. What is the preference and metric value of each OSPF Route?
The OSPF routes vary in metric depending how far away they are (OSPF uses
cumulative cost based on bandwidth), but all have a preference of 10.
4.
c. How many neighbors do you see on the P devices? 2
PE? 2
CE? 0
d. What is the state of their adjacency?
The P and PE adjacencies are Established because there is a OSPF speaker on the
other end with the proper parameters configured.
There is no OSPF adjacency to the CE router listed as none was configured
e. What type of LSAs are in the database?
46
Only Type 1 Router LSA are present due to the interface being configured as pointto-point
Exercise 5.1
5. How many routes are advertised to each neighbor?
There are no routes advertised to the neighbors because BGP does not originate
routes until an export policy is created and applied to the BGP instance.
47
The devices in the remote ISP were not reachable because there is no routing protocol
between the 2 ISPs. Also, none of the CE Host Networks were reachable as the
routers did not have routes for these networks in their local routing table.
48
All routers in the remote ISP were still unreachable. This is due to the local PE router
not participating in the BGP routing protocol and therefore it is not aware of the
aggregate route advertised from P to P router.
peer-as 65001
exit
exit
exit
exit
Exercise 6.1
Part 4: Verification
1.
a. How many PUSH actions on the P, PE, and CE devices?
Exercise 6.2
3. Were you successful at adding the SAP?
No. The port must be in access mode before you can create a SAP on it.
Part 2: Verification
1.
g. How many Ingress labels?
There are now 3 Ingress labels on the PE devices. The P and CE device has no
service labels.
49
There are 7 PUSH operations on each P and PE device. There are no PUSH
operations on the CE as it is not running LDP
iv.
50
51
exit
vpls 612 customer 1 create
stp
shutdown
exit
sap 1/1/2 create
exit
mesh-sdp 6:612 create
mesh-sdp 7:612 create
mesh-sdp 8:612 create
exit
no shutdown
exit
exit
52