Configure ATM 1 and ATM 2 Cell-Relay Promiscuous Mode

For ATM 1 and ATM 2 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.

For ATM 1 and ATM 2 interfaces, changing modes between promiscuous and non-promiscuous causes all physical interfaces to be deleted and re-added.

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];

    }

}

For multiport PICs, all ports must be configured in either promiscuous mode or non-promiscuous mode. For promiscuous mode, you must configure all ports with atm-ccc-cell-relay encapsulation.

When you configure interfaces to use promiscuous mode, you cannot configure VCIs.

For the ATM 2 PIC, if you include the promiscuous-mode statement in the configuration, you must also include the pic-type atm2 statement. For more information, see Configure the ATM 1 and ATM 2 PIC Type.

To map incoming traffic from a port to an LSP, you must include the allow-any-vci statement at the [edit interfaces interface-name unit 0] hierarchy level, as shown in the following example:

[edit interfaces at-1/2/0]

encapsulation atm-ccc-cell-relay;

atm-options {

    promiscuous-mode;

}

unit 0 {

    allow-any-vci;

}

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, as shown in the following example:

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, as shown in the following example:

[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;

        }

    }

}