-
Notifications
You must be signed in to change notification settings - Fork 0
configs for CSG
interface GigabitEthernet0/0/2
interface LoopBack1 ip address 1.1.1.1 255.255.255.255 isis enable 1
bgp 100 peer 1.1.1.1 as-number 100 peer 2.2.2.2 as-number 100 peer 2.2.2.2 connect-interface LoopBack1 peer 3.3.3.3 as-number 100
ipv4-family unicast undo synchronization network 1.1.1.1 255.255.255.255 peer 1.1.1.1 enable peer 1.1.1.1 route-policy policy1 export peer 1.1.1.1 reflect-client peer 1.1.1.1 next-hop-local peer 1.1.1.1 label-route-capability peer 2.2.2.2 enable peer 2.2.2.2 route-policy policy1 export peer 2.2.2.2 label-route-capability peer 3.3.3.3 enable peer 3.3.3.3 route-policy policy1 export peer 3.3.3.3 reflect-client peer 3.3.3.3 next-hop-local peer 3.3.3.3 label-route-capability
ospf 1 area 0.0.0.0 network 1.1.1.1 0.0.0.0 network 10.1.1.0 0.0.0.255
route-policy policy! permit node 1 apply mpls-label
The configuration roadmap is as follows:
Configure IGP protocols at the access, aggregation, and core layers to implement network connectivity at each layer.
Configure MPLS and MPLS LDP and establish MPLS LSPs on devices.
Establish IBGP peer relationships at each layer and enable devices to exchange labeled routes.
Configure each AGG and core ABR as RRs to help a CSG and MASG obtain the route destined for each other's loopback interface.
Configure a routing policy to control label distribution for a BGP LSP to be established on each device. The egress of the BGP LSP to be established needs to assign an MPLS label to the route advertised to an upstream node. If a transit node receives a labeled IPv4 route from downstream, the downstream node must re-assign an MPLS label to the transit node.