For ATM1 and ATM2 IQ interfaces with atm-ccc-cell-relay encapsulation, you can map all incoming cells from either an interface port or a virtual path (VP) to a single LSP without restricting the VCI number. Promiscuous mode allows you to map traffic from all 65,535 VCIs to a single LSP, or from all 256 VPIs to a single LSP.
To map incoming traffic from a port or VC to an LSP, include the promiscuous-mode statement at the [edit interfaces interface-name atm-options] hierarchy level:
- [edit interfaces interface-name]
- atm-options {
-
-
promiscuous-mode {
-
vpi vpi-identifier;
- }
- }
You can include multiple vpi statements in the configuration.
To enable all VCIs in a VPI to open in ATM CCC cell-relay mode, you must also map the logical interface to a VPI by including the vpi statement in the logical interface configuration:
-
vpi vpi-identifier;
You can include this statement at the following hierarchy levels:
Also, note the following:
This section includes the following examples:
Configuring Port-Promiscuous Mode
- [edit interfaces]
- at-0/2/1 {
- encapsulation atm-ccc-cell-relay; # at the physical interface
level only
-
- atm-options {
- pic-type atm2;
- promiscuous-mode;
- }
-
- unit 0 {
- allow-any-vci;
- }
- }
Configuring VP-Promiscuous Mode
- [edit interfaces]
- at-0/2/0 {
-
- atm-options {
- pic-type atm2;
-
- promiscuous-mode {
- vpi 0;
- vpi 1;
- }
- vpi 2;
- vpi 3;
- }
-
- unit 0 {
- encapsulation atm-ccc-cell-relay; # at the logical interface
level only
- vpi 0;
- }
-
- unit 1 {
- encapsulation atm-ccc-cell-relay;
- vpi 1;
- }
-
- unit 2 {
- encapsulation atm-snap;
- vci 2.100;
- }
-
- unit 3 {
- encapsulation atm-vc-mux;
- vci 3.100;
- }
- }
To map incoming traffic from a port to an LSP, include the allow-any-vci statement at the [edit interfaces interface-name unit 0] hierarchy level. When you include the allow-any-vci statement, you cannot configure other logical interfaces in the same physical interface. Next, you must map unit 0 to an LSP using the CCC connection.
Mapping Incoming Traffic from a Port to an LSP
- [edit interfaces at-1/2/0]
- encapsulation atm-ccc-cell-relay;
- atm-options {
- promiscuous-mode;
- }
- unit 0 {
- allow-any-vci;
- }
Mapping Unit 0 to an LSP
- protocols {
-
- connections {
-
- remote-interface-switch router-a-router-c {
- interface at-1/2/0.0;
- }
-
- lsp-switch router-a-router-c {
- transmit-lsp lsp1
- receive-lsp lsp2;
- }
- }
- }
To map a VPI to an LSP, you must define the allowed VPIs. You can configure one or more logical interfaces, each mapped to a different VPI. You can then route traffic from each of these interfaces to different LSPs.
Mapping a VPI to an LSP
- [edit interfaces at-1/1/0]
- encapsulation atm-ccc-cell-relay;
- atm-options {
- pic-type atm1;
-
- promiscuous-mode {
- vpi 10;
- vpi 20;
- }
- }
- unit 0 {
- encapsulation atm-ccc-cell-relay;
- vpi 10;
- }
- unit 1 {
- encapsulation atm-ccc-cell-relay;
- vpi 20;
- }
- [edit interfaces at-3/1/0]
- encapsulation atm-ccc-cell-relay;
- atm-options {
- pic-type atm2;
-
- promiscuous-mode {
- vpi 10;
- vpi 20;
- }
- }
- unit 0 {
- encapsulation atm-ccc-cell-relay;
- vpi 10;
- }
- unit 1 {
- encapsulation atm-ccc-cell-relay;
- vpi 20;
- }
- [edit protocols]
- mpls {
-
- connections {
-
- interface-switch router-a-router-c {
- interface at-1/1/0.0;
- interface at-3/1/0.0;
- }
-
- interface-switch router-a-router-d {
- interface at-1/1/0.1;
- interface at-3/1/0.1;
- }
- }
- }