As I promised, a short briefing on the MPLS-TE.
CONFIGURATION CONCEPT
1) Configuring a Device to Support Tunnels
Enable standard CEF operation.
Enables the MPLS traffic engineering tunnel feature on a device.
and additionsRouter(config)# ip cef Router(config)# mpls traffic-eng tunnels
Router(config)#mpls traffic-eng logging lsp setups Router(config)#mpls traffic-eng logging lsp teardowns Router(config)#mpls traffic-eng reoptimize events link-up
2) Configuring an Interface to Support RSVP-based Tunnel Signalling and IGP Flooding
Enable the MPLS traffic engineering tunnel feature on an interface.
Enable RSVP for IP on an interface and specify amount of bandwidth to be reserved.
and additions:Router(config-if)# mpls traffic-eng tunnels Router(config-if)# ip rsvp bandwidth [bandwidth]
3) Configuring extension for MPLS Traffic EngineeringRouter(config-if)# mpls traffic-eng administrative-weight 100
a) Configuring IS-IS for MPLS Traffic Engineering
Enable IS-IS routing and specify an IS-IS process for IP, which places you in router configuration mode. Turn on MPLS traffic engineering for IS-IS level 1
Specify the traffic engineering router identifier for the node to be the IP address associated with interface loopback0.
Configure a router to generate and accept only new-style TLVs.
b) Configuring OSPF for MPLS Traffic EngineeringRouter(config)# router isis Router(config-router)# mpls traffic-eng level-1 Router(config-router)# mpls traffic-eng router-id loopback0 Router(config-router)# metric-style wide
Configures OSPF routing process for IP, which places you in global configuration mode.
The process ID is an internally used identification parameter for an OSPF routing process. It is locally assigned and can be any positive integer. A unique value is assigned for each OSPF routing process.
Turn on MPLS traffic engineering for OSPF area 0.
Specify the traffic engineering router identifier for the node to be the IP address associated with interface loopback0.
4) Configuring an MPLS Traffic Engineering TunnelRouter(config)# router ospf process-id Router(config-router)# mpls traffic-eng area 0 Router(config-router)# mpls traffic-eng router-id loopback0
a) Configuring an MPLS Traffic Engineering Tunnel not be used IGP path
Configure an interface type and enter interface configuration mode.
Give the tunnel interface an IP address. An MPLS traffic engineering tunnel interface should be unnumbered since it represents a unidirectional link.
Specify the destination for a tunnel. Set encapsulation mode of the tunnel to MPLS traffic engineering.
Configure bandwidth for the MPLS traffic engineering tunnel.
Configure the tunnel to use a named IP explicit path.
Configure the tunnel to use a path dynamically calculated from the traffic engineering topology database.
Path option 2 is used if path option 1 is currently unavailable.
Router(config)# interface tunnel1 Router(config)# ip unnumbered loopback0 Router(config-if)# tunnel destination A.B.C.D Router(config-if)# tunnel mode mpls traffic-eng Router(config-if)# tunnel mpls traffic-eng bandwidth [bandwidth] Router(config-if)# tunnel mpls traffic-eng path-option 1 explicit name test Router(config-if)# tunnel mpls traffic-eng path-option 2 dynamic
additions:ip explicit-path name test enable next-address strict A.B.C.D next-address strict A.B.C.D
b) To configure an MPLS traffic engineering tunnel to be used by an IGPtunnel mpls traffic-eng priority 0 0
Causes the IGP to use the tunnel in its enhanced SPF calculation.
Router(config-if)# interface tunnel1 Router(config-if)# tunnel mpls traffic-eng autoroute announce
EXAMPLE
1) Configuring a Device to Support Tunnels
----------------------------------
You must enter the following commands (step 1 and 2) on EVERY ROUTER in the traffic-engineered portion of your network.
----------------------------------
IS-IS
Step 1: MPLS Traffic Engineering Configuration
Step 2: IS-IS Configurationip cef mpls traffic-eng tunnels interface loopback 0 ip address 11.11.11.11 255.255.255.255 ip router isis interface s1/0 ip address 131.0.0.1 255.255.0.0 ip router isis mpls traffic-eng tunnels ip rsvp bandwidth 1000
router isis network 47.0000.0011.0011.00 is-type level-1 metric-style wide mpls traffic-eng router-id Loopback0 mpls traffic-eng level-1
OSPF
Step 1. MPLS Traffic Engineering Configuration
Step 2: OSPF Configurationip cef mpls traffic-eng tunnels interface loopback 0 ip address 11.11.11.11 255.255.255.255 interface s1/0 ip address 131.0.0.1 255.255.0.0 mpls traffic-eng tunnels ip rsvp bandwidth 1000
2) Configuring an MPLS Traffic Engineering Tunnel ( OSPF Example )router ospf 0 network 10.0.0.0.255.255.255 area 0 mpls traffic-eng router-id Loopback0 mpls traffic-eng area 0
This example shows you how to configure a dynamic path tunnel and an explicit path in the tunnel. Before you configure MPLS traffic engineering tunnels, you must enter the appropriate global and interface commands on the specified router.
Tunnel1
Tunnel 1: Dynamic Path Tunnel Configuration
If everything is configured correctly, you can be happy ^_^ and see it hereinterface tunnel1 ip unnumbered loopback 0 tunnel destination 15.15.15.15 tunnel mode mpls traffic-eng tunnel mpls traffic-eng bandwidth 100 tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng path-option 1 dynamic
16:24:40.747: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel1, changed state to up
Tunnel 1: Dynamic Path Tunnel Verification
and pingshow mpls traffic-eng tunnel show ip interface tunnel1
Tunnel2
Tunnel 2: Explicit Path Tunnel Configuration
Explicit Path Configurationinterface tunnel2 ip unnumbered loopback 0 tunnel destination 15.15.15.15 tunnel mode mpls traffic-eng tunnel mpls traffic-eng bandwidth 100 tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng path-option 1 explicit identifier 1
Tunnel 2: Explicit Path Tunnel Verifcation This section includes the commands that verify that the tunnel is up.ip explicit-path identifier 1 next-address 131.0.0.1 next-address 135.0.0.1 next-address 136.0.0.1 next-address 133.0.0.1
--------------------------------------------------------show mpls traffic-eng tunnel show ip interface tunnel2
Aaaaaand
Congratulations, the task is completed.
Комментариев нет:
Отправить комментарий