[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Spoke CE3

Configure spoke CE3 as follows:

[edit routing-options]
autonomous-system 100;
[edit protocols]
bgp {
group spoke {
type external;
export loopback;
peer-as 200;
neighbor 10.49.6.1;
}
}

In this configuration example, traffic forwarding is as follows between spoke CE2 and hub CE1:

  1. Spoke CE2 forwards traffic using the default route learned from spoke PE2 through BGP. 
        0.0.0.0/0          *[BGP/170] 02:24:15, localpref 100
                          AS path: 200 200 I
                        > to 10.49.3.1 via t1-3/0/1.0
  2. Spoke PE2 performs a route lookup in the spoke VRF table and forwards the traffic to hub PE2 (through the P router—PE2 pushes two labels) using the default route learned through BGP. 
        0.0.0.0/0          *[BGP/170] 01:35:45, localpref 100, from 10.255.14.176
                          AS path: 100 I
                        > via t3-0/0/1.0, Push 100336, Push 100224(top)
  3. Hub PE1 does a route lookup in the mpls.0 table for the VPN label 100336. 
        100336             *[VPN/170] 01:37:03
                        > to 10.49.4.2 via t3-0/0/0.0, Pop
  4. Hub PE1 forwards the traffic out the interface t3-0/0/0.0 to hub CE1.

In this configuration example, traffic forwarding is as follows between hub CE1 and spoke CE2:

  1. Hub CE1 forwards traffic to the hub PE1 using the route learned through BGP. 
        10.49.10.250/32    *[BGP/170] 02:28:46, localpref 100
                          AS path: 200 200 I
                        > to 10.49.4.1 via t3-3/1/0.0
  2. Hub PE1 does a route lookup in the hub VRF table and forwards the traffic to spoke PE2 (through the P router—PE1 pushes two labels). 
        10.49.10.250/32    *[BGP/170] 01:41:05, localpref 100, from 10.255.14.182
                          AS path: 100 I
                        > via t1-0/1/0.0, Push 100352, Push 100208(top)
  3. Spoke PE2 does a route lookup in the mpls.0 table for the VPN label 100352. 
        100352             *[VPN/170] 02:31:39
                        > to 10.49.3.2 via t1-0/1/2.0, Pop
  4. Spoke PE2 forwards the traffic out the interface t1-0/1/2.0 to spoke CE2.

In this configuration example, traffic forwarding is as follows between spoke CE2 and spoke CE3:

  1. Spoke CE2 forwards traffic using the default route learned from spoke PE2 through BGP. 
        0.0.0.0/0          *[BGP/170] 02:24:15, localpref 100
                          AS path: 200 200 I
                        > to 10.49.3.1 via t1-3/0/1.0
  2. Spoke PE2 does a route lookup in the spoke VRF table and forwards the traffic to hub PE1 (through the P router—PE2 pushes two labels) using the default route learned through BGP. 
        0.0.0.0/0          *[BGP/170] 01:35:45, localpref 100, from 10.255.14.176
                          AS path: 100 I
                        > via t3-0/0/1.0, Push 100336, Push 100224(top)
  3. Hub PE1 does a route lookup in the mpls.0 table for the VPN label 100336. 
        100336             *[VPN/170] 01:37:03
                        > to 10.49.4.2 via t3-0/0/0.0, Pop
  4. Hub PE1 forwards the traffic out the interface t3-0/0/0.0 to the hub CE1.
  5. Hub CE1 forwards the traffic to hub PE1 using the router learned through BGP. 
        10.49.10.253/32    *[BGP/170] 02:40:03, localpref 100
                          AS path: 200 200 I
                        > to 10.49.4.1 via t3-3/1/0.0
  6. Hub PE1 does a route lookup in the hub VRF table and forwards the traffic to spoke PE3 (through the P router—PE1 pushes two labels). 
        10.49.10.253/32    *[BGP/170] 01:41:05, localpref 100, from 10.255.14.178
                          AS path: 100 I
                        > via t1-0/1/0.0, Push 100128, Push 100192(top)
  7. Spoke PE3 does a route lookup in the mpls.0 table for VPN label 100128. 
        100128             *[VPN/170] 02:41:30
                        > to 10.49.6.2 via t3-0/0/0.0, Pop
  8. Spoke PE3 forwards the traffic out the interface t3-0/0/0.0 to spoke CE3.

If egress features are needed on the hub PE that require an IP forwarding lookup on the hub VRF routing table, see Enabling Egress Features on the Hub PE Router.

[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.