Syntax Description
(Optional) Specifies which destinations should have their labels advertised. (Optional) Specifies which LSR neighbors should receive label advertisements. A label switch router (LSR) is identified by its router ID, which consists of the first four bytes of its six-byte LDP identifier. Conditional Label Distribution Configuration (Cont.) Example in mini mini mini nil iiiiiii mini iiiiiii ii c r The customer is already running IP infrastructure. MPLS is needed only to support MPLS VPN services
Course Glossary
The Course Glossary for Implementing Cisco MPLS (MPLS) v2.0 highlights and defines key terms and acronyms used throughout this course. Many of these terms are also described in the Cisco Internetworking Terms and Acronyms resource, available via http www.cisco.com. access control list. A filter list kept by routers to control access to or from the router for a number of services (for example, to prevent packets with a certain IP address from leaving a particular interface on the router)....
Show ip bgp vpnv4
To display VPN address information from the BGP table, use the show ip bgp vpnv4 command in EXEC mode show ip bgp vpnv4 all rd route-distinguisher vrf vrf-name ip-prefix length longer-prefixes output-modifiers network-address mask longer-prefixes output-modifiers cidr-only community community-list dampened-paths filter-list flap-statistics inconsistent-as neighbors paths line peer-group quote-regexp regexp summary labels Displays the complete VPNv4 database. Displays Network Layer Reachability...
Pata Mpt Mpt group created on demand for mVPN SG pairs usually highbandwidth traffic
All rights reaefved MPLS v20- - VPN-aware multicast technology has introduced a new set of terminology. Multicast VPNs introduce multicast routing information to the VRF table. When a PE router receives multicast data or control packets from a CE router, forwarding is performed according to information in the multicast virtual routing and forwarding instance (MVRF). A set of MVRFs that can send multicast traffic to each other constitutes a multicast domain. For...
Maintains support for all existing applications and protocols in an MPLS vPn environment
All right* reserved. MPLS v20- -9 NAT can be implemented on the PE route in the following scenarios Service point Shared access can be from a generic interface or from a VPN interface. NAT point NAT can be configured on the PE router that is directly connected to the shared access gateway, or on the PE router that is not directly connected to the shared access gateway. NAT interface The shared access gateway interface is most often configured as the outside interface...
DHCP Relay Cont Shared DHCP Server
End station makes DHCP request DHCP relay agent adds VPN info Server assigns address based on option 82 data and replies W 2003, Cisco System , Inc. All right* reserved In this example, the corporate DHCP server has been replaced with a shared DHCP server provided by the service provider. Because the server is shared between VPNs, a NAT PE could also be included to provide address translation. The client broadcasts a DHCP request to the local relay. The local relay converts the broadcast to a...
OnDemand Address Pools Cont VRF Pool Example
All rights reserved. In this example, the PE router is configured as a DHCP server with ODAP, and a second router is configured to be a subnet allocation server for VNP A. On the PE router, a DHCP pool named A_pool has been created. This pool is associated with VPN A. Three new commands have been introduced to the DHCP command presented in the previous topic. To configure an address pool as an ODAP, use the origin command. The subnet size initial size option is used...
- A different method is needed in which a set of identifiers can be attached to a route
- A label can be removed one hop earlier
- A label is removed on the router before the last hop within an MPLS domain
- A route is installed in the site VRF that matches the RT attribute
- A route that is matched by the export route map will have additional RTs attached
- A router requests a label for every destination in the routing table with the next hop reachable over an LCATM interface
- Access Vpn Vpdn provides dialup access into a customer network
- Addressfamily
- Addressfamily ipv4
- After the BGP session is established with the local PE router verify that the local link is shown as the preferred link for traffic Use the show ip bgp command to verify
- After this operation the provider AS number is prepended to the AS path
- Aggregation should not be used where endtoend LSPs are required Mpls Vpn
- All Internet traffic from all sites goes across the central site
- All loopback interfaces are in one contiguous address block 192168254024
- All nonBGP perVRF routes have to be redistributed into perVrf Bgp context to be propagated by MPBGP to other PE routers
- Allocating a Label
- Allocating a Label Allocation Requests Additional LSRs
- Allowasin Cont
- Allowasin The issue
- Alternatively only internal OSPF routes can be redistributed into MPBGP on the PE routers
- Am A
- An ICMP timetolive exceeded message is sent to the source from router A
- An ICMP timetolive exceeded message is sent to the source from router D
- An LDP session is established from the router with the higher IP address
- An LSP can take a different path from the one chosen by an IP routing protocol MPLS Traffic Engineering
- An LSR can assign a label only if it has already received a label from the nexthop LSR otherwise it must request a label from the neXthop LSR
- Any number of RTs can be attached to a single route
- Any other BGP attribute for example AS path local preference MED standard community
- Are CE routes received by PE
- Are large labeled packets propagated across the MPLS backbone maximum transmission unit issues
- Are routes redistributed into MPBGP with proper extended communities
- Are VPNv4 routes inserted into VRFs on PE2
- Are VPNv4 routes propagated to other CE routers
- Are VPNv4 routes propagated to other PE routers
- Are VPNv4 routes redistributed from BGP into the PECE routing protocol
- Areas could correspond to individual sites from Mpls Vpn perspective
- As each virtual routing table requires a distinct RD value the number of RDs in the Mpls Vpn network increases
- AS pathbased BGP loop prevention is bypassed with ASoverride and allowasin features
- Ask questions
- ASPath Prepending
- Assign interfaces to VRFs
- Assigning an Interface to a VRF Table
- ATM LSRs can swap a label with only one label Vpivci fields change
- ATM Virtual Path Usages Cont Example
- Basic Lcatm Configuration
- Basic MPLS Concepts Cont Example
- Benefits and Drawbacks of VC Merge
- BGP Route Propagation Outbound
- BGP Route Propagation Outbound Cont
- BGP that supports address families other than IPv4 addresses is called Multiprotocol Bgp Mpbgp
- Bit TTL equal to the TTL in IP header
- Both TCP and UDP use wellknown LDP port number 646 711 for TDP
- Break and lunchroom locations
- Building the IP Forwarding Table
- Building the IP Routing Table
- CE routers run standard OSPF software
- Cell Interleave Issues
- Cell Interleave Issues Cont Additional Label Allocation
- Cell Mode MPLS Network Issues
- Central Firewall Service Addressing
- Central Services Extranet
- Central Services VPN Data Flow Model
- Central Services VPN Routing
- Check BGP connectivity with the show ip bgp summary command on the CE routers CEpop Ash ip bgp sum
- Classical Internet Access for a VPN Customer - 2
- Clients can communicate with all servers but not with each other
- Command List - 2 3 4 5 6
- Command Modes
- Complex VPN topologies are supported by multiple virtual routing tables on the PE routers
- Conclusion Mpls Vpn must extend the classic Ospfbgp routing model
- Configuration of Mpibgp sessions
- Configuration steps on CEwg2A
- Configuration steps on CEwg2B router
- Configuration steps on CEwglA
- Configuration steps on CEwglB
- Configuration steps on PE routers
- Configuration steps on PEwg2 - 2 3 4 5 6 7
- Configuration steps on PEwgl - 2 3 4
- Configuration steps on PEwgl for Customer A
- Configuration steps on PEwgl for Customer B
- Configuration steps on PEwgl PEpopconfigno 5
- Configuration steps on PEwgl routers 6 7
- Configuration steps on Pwg2
- Configuration steps on Pwgl
- Configuration Tasks for MPLS on Lcatm Interfaces
- Configure redistribution of OSPF into MPBGP
- Configuring a Label Switching MTU
- Configuring Additional Lcatm Parameters Cont
- Configuring an Lcatm Interface on a Catalyst ATM Switch
- Configuring an Lcatm Interface on a Router
- Configuring Eigrp Pece Routing Cont
- Configuring MPIBGP
- Configuring MPLS on a Frame Mode Interface Cont Example
- Configuring MPLS over ATM Virtual Path Routers
- Configuring MPLS over ATM Virtual Path Routers Cont
- Configuring MPLS over ATM Virtual Path Switches Cont
- Configuring Pece Ospf Routing Cont
- Configuring PerVrf Bgp Routing Context
- Configuring PerVRF Static Routes
- Configuring RDs in a Central Services and Simple VPN
- Configuring RTs in a Central Services and Simple VPN
- Configuring Selective VRF Import
- Configuring VRFs
- Connect to CEwgA2 and try to ping CEwg2B or CEwglB Those routers should not be reachable from CEwgA2 For subgroup B ping CEwglA and CEwg2A from CEwglB
- Connect to CEwgAl and perform ping and trace to the loopback address of CEwg2B or vice versa The other router should be reachable For subgroup B perform the test in the other direction
- Course Evaluations
- Course Objectives
- Customer uses only public IP addresses in the private networknot realistic for many customers
- Customers can use overlapping addresses
- Data plane Forwards packets based on labels
- Debug mpls atmldp routes
- Debug mpls packets
- Debugging MPLS and LDP
- Defaults - 2 3 4 5 6 7 8 9
- Designing Internet Access Separated from VPNs
- Destinationbased routing lookup is needed on every hop
- DHCP Relay Cont Corporate DHCP Server
- DHCP Relay DHCP Today
- Disabling VC Merge
- Drawbacks of Traditional Peerto Peer VPNs
- Drawbacks of VPN Implementations
- Each interface assignable to only one VRF
- Easier to achieve in extranet scenarios because every site is already secured against other sites
- Edge LSR primarily labels IP packets and forwards them into the MPLS domain or removes labels and forwards IP packets out of the MPLS domain
- Edge LSRs that receive the label from their next hop also store the label information in the FIB
- Even if the two topologies overlap the hubandspoke topology is usually used because of easier management
- Every LSR builds its Lib Lfib and FIB data structures based on received labels
- Example
- Example of Internet Access Through a Dedicated Subinterface
- Examples - 2
- Exercise Objectives - 2 3 4
- Exercise Procedure - 2 3 4 5
- Exercise Verification - 2 3 4 5
- Extranet VPNs Cont Peerto Peer VPN Implementation
- Fast Switching and IP Multicast
- FIBs are built based on IP routing tables with no labeling information
- For other routing protocols the SOO can be applied to routes learned through a particular VRF interface during the redistribution into BGP
- Forwarded IP packets are labeled only on the path segments where the labels have already been assigned
- GRE is simpler and quicker IPSec provides authentication and security
- Here ACentral talks to BCentral
- Huband Spoke Overlay VPN Topology
- Impact of Complex VPN Topologies on Virtual Routing Tables Cont
- Impact of Disabling TTL Propagation
- Implementing Separate Subinterfaces
- Implementing SOO for Loop Prevention
- Independent control can be used only for LSRs with Layer 3 capabilities
- Independent perinstance router variables for each instance
- Instructions - 2
- Interactions Between MPLS Applications
- Internet Access as a Separate VPN
- Internet Access as a Separate VPN Cont
- Internet Access from an Mpls Vpn
- Internet Access from Every Customer Site - 2
- Internet Access in VPNs Benefits
- Internet Access Through a Central Firewall Service
- Internet Access Through a Dedicated Subinterface Traffic Flow
- Internet Access Through Global Routing
- Introduction to ATM Virtual Path
- Is CEF enabled on the ingress PE router interface
- Is the BGP route selection process working correctly on PE2
- It can limit the total number of routes in a VRF
- Lab Exercise 31 Establishing the Service Provider IGP Routing Environment
- Lab Exercise 32 Establishing the Core MPLS Environment
- Lab Exercise 63 Common Services VPN
- Label Allocation Independent Control
- Label allocation is secureLSRs cannot send packets with labels that were not assigned to them
- Label Distribution Cont Downstreamon Demand
- Label distribution is a hopbyhop parameter different label distribution mechanisms can coexist in an MPLS network
- Label Distribution Parameters
- Label Distribution Unsolicited Downstream
- Label Fields
- Label Space Cont Negotiation
- Label Space Cont Per Platform
- Label Switch Routers Cont Architecture of Atm Lsrs Cont
- Label Switch Routers Cont ATM Label Switch Router
- Large packets are not propagated across the network
- LDP Hop Count TLV
- Ldp Id 10010
- LDP Monitoring Commands Cont show mpls Idp bindings
- LDP Session Negotiation
- Learner Skills and Knowledge
- LIB and LFIB structures have to be initialized on the LSR allocating the label
- Limitations of Running an Internet Backbone in a VPN
- Limitations of Separate internet Access
- Link Failure Actions
- Link Recovery Actions
- Link Recovery Actions Cont IP Routing Convergence
- Load sharing across unequal paths can be achieved
- Loop Detection
- Loop Detection in Cell Mode MPLS
- LSA flooding occurs across the sham link
- LSP Building Cont
- LSR A discovers the length of the LSP across the ATM domain to LSR D through LDP
- LSR announces a label to an adjacent LSR only once even if there are parallel links between them
- Major Design Models
- Managed CE Routers
- Managed network A dedicated VPN is established to manage CE routers
- Managed Services Overview
- Managed Services Overview Cont - 2
- Mixing Routing Protocols
- Mllllll lllllll lllllll lllllll lllllll lllllll lllllll lllllll I
- Module Assessment Answer - 2
- Module Objectives - 2 3 4 5 6
- Module Outline
- Monitoring an Mpbgp Vpnv4 Table
- Monitoring IP CEF
- Monitoring Label Switching Cont show ip cef detail
- Monitoring Label Switching Cont show mpls forwardingtable
- Monitoring Label Switching Cont show mpls forwardingtable detail
- Monitoring Labels Associated with VPNv4 Routes
- Monitoring Mpbgp Sessions
- Monitoring PerVrf Cef and LFIB Structures
- Monitoring VRF Routing
- MPLS Architecture Cont
- MPLS Configuration Tasks
- MPLS Convergence
- MPLS Convergence Cont After a Link Failure
- MPLS Forwarding Cont Cell Mode
- Mpls ip propagatettl
- MPLS Lab IP Addressing Scheme - 2
- MPLS Lab Logical Connection Diagram Module
- MPLS Lab Overlapping VPNs
- MPLS Lab Physical Connection Diagram
- Mpls label protocol [tdp ldp both
- MPLS Labels Cont Frame Mode MPLS
- Mpls ldp advertiselabels
- Mpls ldp routerid
- MPLS Monitoring Commands Cont show mpls Idp parameters
- MPLS over ATM uses the ATM header as the label cellmode
- MPLS over Frame Relay Networks
- MPLS provides a virtual fullmesh topology
- MPLS Unicast IP Routing Architecture Cont - 2 3
- Mpls Vpn Network Example
- Mpls Vpn Routing Cont PE Router Perspective
- Mpls Vpns and Label Propagation
- Mpls Vpns and Packet Forwarding
- Mpls Vpns combined with Mpls Te three or more labels
- MPLS was designed to support forwarding of other protocols as well
- Multilevelcombines several levels of overlay VPN topologies
- NAT for Shared Services
- Need for Routing Protocol Contexts
- Neighbor maximumprefix
- Neighbor nexthopself
- Neighbor updatesource
- Network Address Translation NAT Today
- Next Steps - 2 3 4
- No other set operations can be performed by this route map
- No upgrade or configuration changes to customer equipment
- NonBGP Route propagationOutbound Cont
- Objectives - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
- On egress TTL is copied from label header to IP header
- On your P router verify that an LDP neighbor relationship has been established between your P router and Pl
- On your PE router verify that labels are being received from the other workgroups
- On your PE router verify that you are seeing the BGP routes from the other workgroups using the show ip route bgp command
- OnDemand Address Pools Cont Provisioning and Startup
- OnDemand Address Pools IP Address Management Today
- Only RIPv2 is supported
- Only the sites are provisioned not the links between them
- Optimizing of Packet Forwarding Across the Mpls Vpn Backbone
- Optimizing of Packet Forwarding Across the Mpls Vpn Backbone Cont
- OSPF Down Bit Ospfbgp Routing Loops
- OSPF in an Mpls Vpn Routing Model
- OSPF in an Mpls Vpn Routing Model Cont Ospfbgp Redistribution Issue
- OSPF Superbackbone Cont External Routes
- OSPF Superbackbone Cont Implementation - 2
- OSPF Superbackbone Ospfbgp Hierarchy Issue
- OSPF Superbackbone Rules
- Other Mpls Vpn Monitoring Commands
- Outline - 2 3 4 5
- Overlapping VPN Routing
- Overlay VPN Implementation - 2
- Overlay VPNs Cont Frame Relay Example
- Overlay VPNs Cont Layer 2 Forwarding
- Overlay VPNs Cont Layer 3 Routing
- Overview - 2 3 4 5 6
- P routers run backbone IGP with the PE routers and exchange information about global subnets core links and loopbacks
- Packet Propagation Across an MPLS Network
- Packet Propagation Issues
- Partial Mesh Overlay VPN Topology
- Parts of the network already migrated can be linked with virtual paths during the transition period
- PE routers export VPN routes from VRF tables into MPBGP and propagate them as VPNv4 routes to other PE routers
- PE routers never redistribute OSPF routes with down bit set into MPBGP
- PE1 RD and RT Numbering Scheme
- Peerto Peer VPNs
- Peerto Peer VPNs Cont Controlled Route Distribution
- Penultimate Hop Popping After
- Penultimate Hop Popping Before
- Peraddressfamily parameters can be configured for these neighbors
- Per Interface Label Allocation
- Perinterface label allocation is securelabeled packets or ATM cells are accepted only from the interface where the label was actually assigned
- Per Platform Label Allocation Cont Benefits and Drawbacks of Per Platform Label Allocation
- Pim
- Platform MPLS Implementation
- Prerequisite Learner Skills and Knowledge
- Prerequisites
- Propagation of Routing Information Across the PNetwork
- Propagation of Routing Information Across the PNetwork Cont
- Propagation of Routing information Across the PNetwork Cont
- Propagation Routing information Across the PNetwork Cont
- Quiz - 2
- Quiz Answer - 2
- Quiz Answer Key - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 3 4 5 6 7 8 9 10
- Receiving router uses the top label only
- Redundant Internet Access
- Redundant Internet Access Cont
- References - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
- Regardless of the application the functionality is always split into the control plane and the data forwarding plane
- Requesting a Label
- Requirements
- Route Distinguishers Cont
- Route Propagation Inbound
- Route Targets Cont Connectivity Requirements
- Router C is forwarding packets based on Layer 3 information
- Router functionality is divided into two major parts control plane and data plane
- Routing lookups are performed on every hop
- Routing Loops Across OSPF Domains
- Routing Protocol Convergence
- Routing Tables on PE Routers
- RSVP or CRLDP is used to establish TE tunnels and propagate labels
- Sample router configuration for simple customer VPN
- Select routes to be inserted into the virtual routing table
- Selects configuration of perVrf Pece Ebgp parameters
- Separate Interface for Internet Connectivity
- Set of import and export route targets
- Sham Link
- Show ip bgp neighbors
- Show ip cef - 2
- Show ip route vrf
- Show mpls atmldp bindings
- Show mpls atmldp capability
- Show mpls atmldp summary
- Show mpls interfaces
- Specify additional parameters for VPNv4 route exchange filters next hops and so on
- Specify the maximum number of routes in a VRF to prevent memory exhaustion on PE routers or denialofservice attacks
- Specifying Export and Import RTs
- Steady State Description
- Step 1Enable CEF and label switching
- Step 2 Enable conditional label advertisement
- Steps to Configuring a Central Services VPN
- Subinterfaces
- Summary - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
- Support for Existing Internet Routing
- Switched WANs VPN Terminology
- Syntax Description - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
- Task 1 Configuring BGP as the PECE Routing Protocol
- Task 1 Configuring Multiprotocol BGP
- Task 1 Designing a Network Management VPN
- Task 1 Designing Your VPN Solution
- Task 1 Enabling LDP on Your PE and P Routers
- Task 1 Establishing Central Site Connectivity for Internet Access
- Task 1 Establishing CEPE Connectivity for Internet Access - 2
- Task 1 Verifying the Service Provider IP Interfaces
- Task 2 Configuring the Service Provider IGP
- Task 2 Configuring Virtual Routing and Forwarding Tables
- Task 2 Disabling TTL Propagation
- Task 2 Establishing Connectivity Between the Nms Vrf and Other VRFs
- Task 2 Establishing Routing Between the Customer and the Internet - 2
- Task 2 Migrating the Core to ISIS
- Task 2 Removing CEwgl Aand CEwg2B from Existing VRFs
- Task 3 Configuring Conditional Label Distribution
- Task 3 Configuring New VRFs for CEwgl Aand CEwg2B
- Task 3 Selecting the Primary and Backup Link with BGP
- Task 4 Enabling IBGP Connectivity for All PE Routers
- Task 4 Removing Conditional Label Distribution
- The ATM network is not aware of MPLS between the routers
- The Cisco iOS software can be configured to reject routes optional
- The commands used in this exercise are described in the table here
- The commands used in this exercise are described in the table here Network Management VPN Commands
- The customer wants to reuse the same AS number on several sites
- The FEC is equal to a destination network stored in the IP routing table
- The firewall provides Network Address Translation NAT between the private address space and the small portion of public address space assigned to the customer
- The forwarding information from the MPBGP route is used
- The IP routing protocol determines the path
- The last function is part of the data plane
- The outgoing label is inserted in the LFIB after the label is received from the next hop LSR
- The overall number of routing processes per router is limited to 32 of which only 28 are available for VRF assignment
- The P routers are hidden from the customer
- The PE router appears as another router in the Cnetwork
- The PE router will reject the update only if its AS number appears in the AS path more often than the configured limit
- The pop or implicit null label uses a reserved value when being advertised to a neighbor
- The same AS number may be used for all sites
- The second option has been used because there are too many existing IP routing protocols that would have to be modified to carry labels
- The show ip cef command can also display the label stack associated with the Mpibgp route
- The virtual path number has to match between peers
- These routes do not enter IP routing table even when they are selected as the best routes using the SPF algorithm
- This command creates a route map that matches routes based on any route map conditions and sets RTs
- This situation results in a combination of rules from overlapping VPN and central services VPN
- Topologydriven switching
- Traceroute across an MPLS domain does not show any core routers
- Traditional Router Based Networks
- Traffic flow between an individual site and Internet destinations is always optimal
- Typical Overlapping VPN Usages
- Usage Guidelines - 2
- Usage guidelines 3 4 5 6
- Use an extended ping to verify that host addresses with the customer network can reach the Internet
- Use the show ip bgp vpnv4 vrf name prefix command to display details of an individual route and verify that the proper RTs are attached to the route Your printout should be similar to the one here
- Use the show ip route command and verify that all routers are sending and receiving the appropriate prefixes
- Use this command when the same router carries Internet and VPNv4 routes and you do not want to propagate Internet routes to some PE neighbors
- Using a central firewall is the most costeffective way to provide this service
- Validating the Endto End Label Switched Path
- Validating the LFIB Status
- Verify access list contents with show accesslist
- Verify local LDP identifier with show mpls ldp neighbors
- Verify that the backup link the link to your local PE router is being used Use the show ip bgp command to verify
- Verify that the Internet routes being received by the central site CE route are coming from its PE neighbor
- Verify that your CE router is seeing only prefixes within your VPN and that no prefixes are being leaked from other VPNs
- Verify the BGP neighbor relationship has been removed on the PE router with the show ip bgp vpnv4 vrf summary command This action should give you a printout similar to the one here Check the status of CEwglA and CEwg2B in the printout
- Verify the perVrf Bgp table for your customer on your PE routers with the show ip bgp vpnv4 vrf command You should still see that the BGP routes coming from the CE routers are being selected as the best routes for those destinations
- Verify the perVRF table for your customer on your PE routers with the show ip route vrf command You should still see only the routes coming from the CE routers being selected
- Verify the proper setting of the MED by using the show ip bgp vpnv4 vrf command on the PE routers Make sure that the PE routers select routes coming from the primary link as the best routes
- Verify the routing information flow
- Verify with show cef interface
- Verify with show mpls interface detail on both routers
- Virtual Private Networks
- Visual Objective
- Volume
- VPN Implementation Technologies
- VPN Label Propagation
- VPN Packet Forwarding Across an Mpls Vpn Backbone
- VPN Packet Forwarding Across an Mpls Vpn Backbone Cont
- VPN Penultimate Hop Popping
- VPN routes are exchanged with CE routers through perVrf Ebgp sessions
- VRF Creation and RD Overview
- VSI protocol is used to populate the ATM switching matrix LFIB in the data plane of some ATM switches Cisco implementation
- When the SPF algorithm is executed the shamlink will have the specified cost
- Wholesale Internet Access - 2
- Wholesale Internet Access Addressing
- You have completed this exercise when you attain these results Verify pointtopoint connectivity over the new subinterface




