1 / 34

Label Switch Router (LSR) Configuration

Label Switch Router (LSR) Configuration. BXR-48000 Switch Router. Objectives. Create router interfaces Configure IGP OSPF IS-IS Configure LDP RSVP-TE LDP Configure BGP. IP/MPLS Model.

aria
Télécharger la présentation

Label Switch Router (LSR) Configuration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Label Switch Router (LSR) Configuration BXR-48000 Switch Router

  2. Objectives • Create router interfaces • Configure IGP • OSPF • IS-IS • Configure LDP • RSVP-TE • LDP • Configure BGP

  3. IP/MPLS Model • Could work on statically defined LSPs but this is usually reserved for LSPs with traffic engineering constraints • Configuring LSRs to engage in dynamic routing exchanges requires the configuration of an Interior Gateway Protocol (IGP) to distribute IP destinations • If LSRs are to establish dynamic LSPs, a signaling protocol must be configured • Once the IGP is functioning, an Exterior Gateway Protocol (EGP) could be configured

  4. + Signaling(e.g., RSVP-TE, LDP) IGP (e.g., OSPF) Sample MPLS Diagram

  5. Differences with IPA ATM Port Cards • IP interfaces can be on Packet-over-SONET (POS) port cards or IP Aware (IPA) ATM port cards • IPA ATM port cards can present some unusual choices • ATM interfaces do not usually get an IP address • Encapsulation methods must match on connected interfaces • ATM and IP control planes can coexist

  6. LSR Initial Configuration • Define a loopback interface • Define router interface(s) • Configure IGP/EGP (as needed) • Configure IP signaling

  7. Define a Loopback Interface • Not always required but is a good practice BXR_Pgh:interfaces loopback-> new ? Usage: [[-index] <integer>] Loopback Interface Index (default: 1) [-ipaddr] <IP Address> IP Address [[-mask] <IP Address>] Subnet Mask (default: 255.255.255.255) [[-description] <text (size 0..80)>] Interface Description [[-vrf] <VrfName>] VRF Name of this i/f (default: "") BXR_Pgh:interfaces loopback-> new -ipaddr 150.150.150.150 WARNING: You are about to add a loopback interface whose IP address will be used for Router Address. This operation will affect existing active protocols. Do you wish to continue? (y or n): y BXR_Pgh:interfaces loopback-> show Index IfName IfIndex IP Address Network Mask ---------- ------------ ------- --------------- --------------- 0 lo0 1 127.0.0.1 255.0.0.0 1 lo1 9 150.150.150.150 255.255.255.255

  8. IPA Default Configuration • One RFC 1483 interface is created by default on each IPA port • Control channel is 0/32 • Multiplexing method is llc • Encapsulation method is routed PDU BXR_Pgh:interfaces atmif rfc1483-> show 1d* IfName vpi vci Mux PDU Admin Oper Method Type Status Status 1D1.1 0 32 llc routed up up 1D2.1 0 32 llc routed up LowerLayerDown 1D3.1 0 32 llc routed up up 1D4.1 0 32 llc routed up LowerLayerDown

  9. IPA Layer 2 Interface • New interfaces cannot use the same control channel (0/32) • Creates additional logical interfaces on the same ATM port BXR_Pgh:interfaces atmif rfc1483-> new ? [-atmifindex] <AtmIf> Atm If Index [-index] <integer> Index [-vpi] <integer> Vpi [-vci] <integer> Vci [[-muxmethod] <muxmethod>] Mux Method (default: llc) [[-pdutype] <pdutype>] PDU Type (default: routed) [[-adminstatus] <ifadminstatus>] Admin Status (default: up) BXR_Pgh:interfaces atmif rfc1483-> new 1d1 2 0 33 SWITCH/ROUTER:interfaces atmif rfc1483-> show 1d* IfName vpi vci Mux PDU Admin Oper Method Type Status Status 1D1.1 0 32 llc routed up up 1D1.2 0 33 llc routed up up

  10. IPA Router Interface Configuration (riatm) BXR_Pgh:interfaces ip-> new Usage: [-layer2if] <IpLayer2If> Layer-2 Interface Name [[-ipaddr] <IP Address>] IP Address [[-mask] <IP Mask>] Network Mask|Mask Len [[-adminstatus] (up|down)] Administrative Status (default: up) [[-nbraddr] <IP Address>] Neighbor IP Address [[-bcast] (0|1)] Broadcast Setting (default: 0) [[-mtu] <integer>] MTU [[-unnumbered] (no|yes)] Unnumbered Interface (default: no) [[-description] <text (size 0..80)>] Interface Description [[-mplsmode] (none|shim|lcatm)] MPLS Mode (default: none) : BXR_Pgh:interfaces ip-> new 1d1.1 10.1.1.2 24 -mplsmode shim BXR_Pgh:interfaces ip-> show ri* IfName Layer2 IP Address Mask Unnum MTU Admin Oper Interface Status Status --------- -------------- --------------- ---- ----- ----- ------ ------ riatm1 1D1.1 10.1.1.2 24 no 4470 up up

  11. POS Router Interface Configuration (ripos) BXR_Pgh:interfaces ip-> new 1C1 10.3.3.3 24 -mplsmode shim BXR_Pgh:interfaces ip-> show IfName Layer2 IP Address Mask Unnum MTU Admin Oper Interface Status Status --------- -------------- --------------- ---- ----- ----- ------ ------ ie0 ie0 192.168.82.108 23 N/A 1500 up up lo0 lo0 127.0.0.1 8 N/A 32768 up up lo1 lo1 150.150.150.150 32 N/A 32768 up up qaa0 qaa0 N/A N/A N/A N/A down down qaa1 qaa1 N/A N/A N/A N/A down down qaa2 qaa2 N/A N/A N/A N/A down down qaa3 qaa3 N/A N/A N/A N/A down down riatm1 1D1.1 10.1.1.2 24 no 4470 up up ripos1 1C1 10.3.3.3 24 no 4474 up up BXR_Pgh:interfaces mpls-> show MplsIf TotalBW(kbps) AvailBW(kbps) Layer2If Admin Oper LabelType 1D1.1 599039 598742 rfc1483 up up shim 1C1 2396160 2396160 pos up up shim

  12. OSPF-TE or IS-IS-TE Area boundaries Establish adjacencies as needed Configuring the IGP

  13. + Area 0.0.0.0 riatm1 ripos1 OSPF Configuration Steps • Define an area • Configure interfaces for the IGP • Optional: Configure Router ID/ System ID • Optional: Configure authentication(password or MD5) • Enable the protocol • Check for connectivity Active

  14. OSPF Area Configuration • Area 0.0.0.0 should be defined first BXR_Pgh:routing ip ospf area-> new ? Usage: [-id] <IP Address> Area ID (IP Address Format) [[-stub] (yes|no)] Stub Area (default: no) [[-importsum] (yes|no)] Import Summary LSAs [[-stubmetric] (1..16777215)] Stub Metric [[-vrf] <VrfName>] VRF Name (default: "") BXR_Pgh:routing ip ospf area-> new 0.0.0.0 BXR_Pgh:routing ip ospf area-> show Area ID Stub Import Sum Stub Metric SPFRuns ABRCnt ASBRCnt LSACnt --------------- ---- ---------- ----------- ------- ------ ------- ------ 0.0.0.0 no N/A N/A 3 0 0 0

  15. Add an OSPF Interface • Existing IP interfaces may be attached to an OSPF area BXR_Pgh:routing ip ospf interface-> new ? [-ifname] <IfName> Interface Name [[-areaid] <IP Address>] Area ID (default: 0.0.0.0) [[-adminstatus] (enabled|disabled)] Administrative Status (default: enabled) [[-priority] (0..255)] Router Priority : BXR_Pgh:routing ip ospf interface->new riatm1 0.0.0.0 enabled BXR_Pgh:routing ip ospf interface->new ripos1 0.0.0.0 enabled BXR_Pgh:routing ip ospf interface-> show IF Name Area ID DR Backup DR Metric Admin Oper --------- --------------- --------------- --------------- ------ -------- ---- lo1 0.0.0.0 N/A N/A 1 enabled up riatm1 0.0.0.0 N/A N/A 1 enabled up ripos1 0.0.0.0 N/A N/A 1 enabled up For IPA For POS

  16. Enable OSPF BXR_Pgh:-> routing ip ospf BXR_Pgh:routing ip ospf-> modify Usage: [[-adminstatus] (enabled|disabled)] Administrative Status [[-asbr] (enabled|disabled)] ASBR Option [[-teState] (on|off)] Traffic Engineering Extensions [[-shortcuts] (enabled|disabled)] LSP Shortcuts [[-rfc1583Compat] (enabled|disabled)] RFC1583 Compatibility [[-spfInterval] (1..120)] SPF Interval (Sec.) (Def: 5) [[-vrf] <VrfName>] VRF Name (default: "") BXR_Pgh:routing ip ospf-> modify –adminstatus enabled BXR_Pgh:routing ip ospf-> show Ver Router ID Admin Oper ASBR ABR TE State Short Cuts --- --------------- -------- ---- -------- ----- -------- ---------- 2 150.150.150.150 enabled up enabled false on disabled

  17. Verify OSPF Operation • Database entries from other routers and neighbor display BXR_Pgh:routing ip ospf-> lsdb-summary Area ID Router Network Sumnet Sumasb Nssa Ar-opq --------------- ------ ---------- ---------- ---------- ---------- ---------- 0.0.0.0 3 0 0 0 0 7 BXR3:routing ip ospf-> neighbor Nbr Addr IF Name Nbr Router ID Pri State Events ReTxQ Type --------------- ---------- --------------- --- -------- ------ ----- ---- 10.1.1.1 riatm1 100.100.100.100 0 full 6 0 Disc 10.3.3.3 ripos1 200.200.200.200 0 full 6 0 Disc

  18. Area aa.bbcc Level 1 Level 2 riatm1 ripos1 IS-IS Configuration Steps + • Define an area • Configure router type and System ID • Optional: Configure authentication(password or MD5) • Name interface and enable circuit • Check for connectivity System ID: 150.150.150.150

  19. IS-IS Area Configuration • IS-IS areas are defined by three hexadecimal bytes BXR_Pgh: routing ip isis area-> new ? Usage: [-address] <IS-IS Address> Area Address (1-13 bytes xx.yyyy...) BXR_Pgh:routing ip isis area-> new aa.bbcc BXR_Pgh:routing ip isis area-> show Area Address type aa.bbcc manual

  20. Configure IS-IS Router Type and ID • System ID is six hexadecimal bytes BXR_Pgh:routing ip isis-> modify Usage: [[-type] (L1|L2|L1L2)] IS-IS Type [[-sysId] <IS-IS Address>] IS-IS Instance ID (6 bytes:1122.3344.5566) [[-adminstatus] (enabled|disabled)] Administrative Status : BXR_Pgh:routing ip isis-> modify -type l1 -sysid 1150.1150.1150 -adminstatus enable BXR3:routing ip isis-> show Version : 1 Type : L1 System ID : 1150.1150.1150 Administrative Status : enabled Operational Status : up SPF Interval for L1 and L2 (Sec.) : 5 Level 1 Database State : on Level 2 Database State : off : BXR_Pgh: routing ip isis

  21. Add an IS-IS Interface • A circuit type starts communication BXR_Pgh:routing ip isis circuit-> new ? [-ifname] <text> Layer2 I/F name [-level] (L1|L2|L1L2) Circuit Level [[-adminstatus] (enabled|disabled)] Admin Status (default: enabled) : BXR_Pgh:routing ip isis circuit-> new riatm1 l1 enabled BXR_Pgh:routing ip isis circuit-> new ripos1 l1 enabled BXR3:routing ip isis circuit-> show I/F Level I/F Address L1Metric L2Metric Passive Admin Oper Name State State State lo1 L1 150.150.150.150 0 0 true enabled up riatm1 L1 10.1.1.2 10 10 false enabled up ripos1 L1 10.3.3.3 10 10 false enabled up BXR_Pgh:routing ip isis-> interfaceshow I/F I/F Address Metric Unnum Admin Oper Name State State lo1 150.150.150.150 0 no enabled up riatm1 10.1.1.2 10 no enabled up ripos1 10.3.3.3 10 no enabled up For IPA For POS

  22. Check Adjacencies • Neighbor systems should display; Level 1 and Level 2 circuits have separate entries BXR3:routing ip isis-> adjacency Circuit Nbr. Neighbor System ID Neighbor Adj. Adj. Adj. I/F Name Ckt. Type IP Address Usage State Rem. riatm1 L1IS 1110.1110.1110 10.1.1.1 level1 up 27 riatm2 L1IS 1175.1175.1175 10.1.2.1 level1 up 28 ripos1 L1IS 1200.1200.1200 10.3.3.3 level1 up 29

  23. RSVP-TE or LDP Downstream on Demand (DoD) Downstream unsolicited (DU) Enabling IP/MPLS Signaling

  24. Configure RSVP-TE Signaling Interface BXR_Pgh:-> signalling ip rsvpte interface BXR_Pgh: signalling ip rsvpte interface-> new ? Usage: [-ifname] <text> Interface Name [[-adminstatus] (enabled|disabled)] Administrative Status (default: enabled) : BXR_Pgh: signalling ip rsvpte interface-> new riatm1 enabled BXR_Pgh: signalling ip rsvpte interface-> new ripos1 enabled BXR_Pgh:signalling ip rsvpte interface-> show Interface Refresh Refresh Admin Oper Hello Hello Name Mult Interval Admin Oper ---------- ------- ---------- -------- ----- -------- ----- riatm1 3 30000ms enabled up disabled down ripos1 3 30000ms enabled up disabled down For IPA For POS

  25. Enable RSVP-TE • RSVP-TE interface comes up after the protocol is enabled BXR_Pgh:signalling ip rsvpte-> modify –adminstatus enabled BXR_Pgh:signalling ip rsvpte-> show Administrative Status : enabled Best-Effort representation : cos Default IntServ service : controlledLoad Signal resource affinities : true Signal default E-LSP with a DIFFSERV object: no Message ID Epoch : 14354348 BXR_Pgh:signalling ip rsvpte-> interface show Interface Refresh Refresh Admin Oper Hello Hello Name Mult Interval Admin Oper ---------- ------- ---------- -------- ----- -------- ----- riatm1 3 30000ms enabled up disabled down ripos1 3 30000ms enabled up disabled down Note: Marconi implementation of RSVP-TE includes RSVP refresh reduction mechanisms defined in RFC 2961

  26. Configure an LDP Interface • Same procedure as other protocols: Create the interface, then enable the protocol BXR_Pgh:signalling ip ldp interface-> new ? [ifname] <text> Interface Name [[-adminstatus] (enabled|disabled)] Administrative Status (default: enabled) BXR_Pgh:signalling ip ldp interface-> new riatm1 –adminstatus enabled BXR_Pgh:signalling ip ldp interface-> new ripos1 –adminstatus enabled BXR_Pgh :signalling ip ldp interface-> show Intf Name Intf Index Intf Address Label Space Admin State Oper Status --------- ---------- --------------- ----------- ----------- ----------- riatm1 10 10.1.1.2 10 enabled down ripos1 1210.3.3.3 12 enabled down For IPA For POS

  27. Enable LDP BXR_Pgh:signalling ip ldp-> modify -adminstatus enable BXR_Pgh:signalling ip ldp-> show LSR Id : 150.150.150.150 Administrative Status : enabled Protocol Version : 1 Loop Detection : enabled Keep Alive Hold Time (Sec.) : 45 Keep Alive Interval (Sec.) : 15 Hello Hold Time (Sec.) : 15 Hello Interval (Sec.) : 5 Distribution Control : ordered Path Vector Limit : 30 Hop Count Limit : 30 Operational Status : up Total Operational Session : 2 Total Local Label Bindings : 8 Total Remote Label Bindings : 2

  28. Verify LDP Operation • Hello state and session information displays with no LSPs BXR_Pgh:signalling ip ldp interface-> show Intf Name Intf Index Intf Address Label Space Admin State Oper Status --------- ---------- --------------- ----------- ----------- ----------- riatm1 10 10.1.1.2 10 enabled up ripos1 12 10.3.3.3 12 enabled up BXR_Pgh:signalling ip ldp-> hello_adjacency show Local Ldp Id Peer Ldp Id Adjacency Type ---------------------- ---------------------- -------------- 150.150.150.150:10 100.100.100.100:10 link 150.150.150.150:11 175.175.175.175:10 link 150.150.150.150:12 200.200.200.200:10 link BXR_Pgh:signalling ip ldp-> session peer_address Local Ldp Id Peer Ldp Id Next Hop Address ---------------------- ------------------------ ---------------- 150.150.150.150:10 100.100.100.100:10 10.1.1.1 150.150.150.150:11 175.175.175.175:10 10.1.2.2 150.150.150.150:12 200.200.200.200:10 10.3.3.3

  29. Using BGP • EBGP can be configured to advertise prefixes from one AS to another • IBGP can be configured to advertise prefixes within an AS • Must define an AS number and enable the protocol, then define the BGP peer • Some RPCL configuration will be needed to advertise prefixes on BGP

  30. Configure BGP, Define Peer BXR_Pgh:routing ip bgp-> modify enabled –localAS 100 BXR_Pgh:routing ip bgp peer-> new ? Usage: [-peerAddr] <IP Address> Peer IP Address [-peerAS] (1..65535) Peer AS number [[-adminstatus] (enabled|disabled)] Administrative Status (default: enabled) [[-localAddr] <IP Address>] Local IP Address : BXR_Pgh:routing ip bgp peer-> new -peerAddr 10.3.3.2 -peerAS 150 -adminstatus enabled -localAddr 10.3.3.3 BXR_Pgh:routing ip bgp peer-> show PeerAddr PeerAS PeerType AdminStatus PeerState OperStatus ----------------- --------- ----------- ------------ ------------- ---------- 10.3.3.2 150 Ext enabled established up

  31. BGP Display BXR_Pgh:routing ip bgp-> show Router Id : 10.10.91.23 Local AS Number : 100 Confederation Id <none OR (1..65535)> : none Cluster Id <none OR IP-Address OR (1..4294967295)> : none Administrative Status : enabled Operational Status : up Always Compare MED : no Never use MED in decision process : no Start Time : WED DEC 18 11:36:44 2003 Total Path Attribute : 0 Total Enabled Peer(s) : 1 Total Disabled Peer(s) : 0 Total Established Peer(s) : 1 Total Peer(s) In Bringup : 0 Max Peer(s) In Bringup : 0 Total Peer(s) In Bringdown : 0 Total Configured Peer(s) : 1 Internal Hold : 0 Total Route Count : 0 Suppress Intra-Cluster Reflection : no

  32. Route Export Example BXR_Pgh:routing ip bgp-> rpcl (Entering the RPCL interpreter shell BXR_Pgh:RPCL% table insert export-direct-bgp {to any announce any} 10 BXR_Pgh:RPCL% changes commit BXR_Pgh:RPCL% table export-direct-bgp { 10 : on-the-fly { 10: to any-peer announce any } } ==================== BXR_Pgh:RPCL% save rpcl.cfg BXR_Pgh:RPCL% exit Any direct routes will be given to BGP, including new or changed direct routes. Any instance of BGP will receive these advertised prefixes.

  33. View from BGP Peer BXR_Atlanta:routing ip bgp-> pathAttr Prefix Peer Next Hop Best AS Path --------------------- ---------------- ---------------- ---- ------------------ 5.2.2.2 /32 10.3.3.2 10.3.3.2 yes [100] 10.10.0.0 /16 10.3.3.210.3.3.2 yes [100] 11.11.11.0 /24 10.3.3.210.3.3.2 yes [100] 11.11.11.11 /32 10.3.3.210.3.3.2 yes [100] 110.110.120.0 /24 10.3.3.210.3.3.2 yes [100] 110.110.120.110 /32 10.3.3.210.3.3.2 yes [100] BXR_Atlanta:routing ip bgp-> route Policy/ Damp Local Prefix NextHop NH-State State Proto Pref MED ------------------ --------------- ------------- ---------- ------ ----- ---- 5.2.2.2 /32 10.3.3.2 ResolvedNoLsp UnDamped EBGP 100 0 10.10.0.0 /16 10.3.3.2 ResolvedNoLsp UnDamped EBGP 100 0 11.11.11.0 /24 10.3.3.2 ResolvedNoLsp UnDamped EBGP 100 0 11.11.11.11 /32 10.3.3.2 ResolvedNoLsp UnDamped EBGP 100 0 110.110.120.0 /24 10.3.3.2 ResolvedNoLsp UnDamped EBGP 100 0 110.110.120.110/32 10.3.3.2 ResolvedNoLsp UnDamped EBGP 100 0

  34. Summary • Created router interfaces • Configured IGP • OSPF • IS-IS • Configured LDP • RSVP-TE • LDP • Configured BGP

More Related