[an error occurred while processing this directive][an error occurred while processing this directive]

Example: Configuring a Remote LSP CCC over Aggregated Ethernet

See the topology in Figure 1. In this topology, CE Router G has an aggregated Ethernet connection to PE Router F. CE Router D has an aggregated Ethernet connection to PE Router E. Router E and Router F have an MPLS LSP between them. With remote CCC, you specify that the circuit from Router D is connected to the circuit from Router G. The circuit from Router D is connected to the LSP on Router E; the circuit from Router G is connected to the LSP on Router F. In other words, ae0.0 and ae1.0 are connected using lsp1-2 and lsp2-1. You configure Router D and Router G as standard aggregated Ethernet interfaces. For more information about aggregated Ethernet, see Aggregated Ethernet Interfaces Overview.

Figure 1: Remote Interface-LSP-Interface Circuit Cross-Connect over Aggregated Ethernet Interfaces

Image g017015.gif

On Router D

[edit interface]ae0 {aggregated-ether-options {minimum-links 1;link-speed 1g;lacp {active;periodic fast;}}unit 0 {family inet {address 192.168.2.1/30;}}}

On Router E

[edit interfaces]ae0 {encapsulation ethernet-ccc;aggregated-ether-options {minimum-links 1;link-speed 100m;lacp {active;periodic fast;}}unit 0 {encapsulation vlan-ccc; # defaultfamily ccc; # default}}[edit protocols]mpls {interface all;}connections {remote-interface-switch remote-sw-1 {interface ae0.0;receive-lsp lsp2_1;transmit-lsp lsp1_2;}}

On Router F

[edit interfaces]ae1 {encapsulation ethernet-ccc;aggregated-ether-options {minimum-links 1;link-speed 100m;lacp {active;periodic fast;}}unit 0 {encapsulation vlan-ccc; # defaultfamily ccc; # default}}[edit protocols]mpls {interface all;}connections {remote-interface-switch remote-sw-2 {interface ae1.0;receive-lsp lsp1_2;transmit-lsp lsp2_1;}}

On Router G

[edit interface]ae1 {aggregated-ether-options {minimum-links 1;link-speed 1g;lacp {active;periodic fast;}}unit 0 {family inet {address 192.168.2.2/30;}}}

Published: 2010-04-20

[an error occurred while processing this directive]