Check the Configuration of the VCI on an ATM1 Interface
Purpose
If your configuration of the virtual channel identifier (VCI) is incorrect, the logical interface is not created.
Action
To check that VCI is configured correctly on your ATM1 interface, follow these steps:
- Check the configuration with the following JUNOS CLI operational mode command:
user@host>show configuration interfaces at-fpc/pic/portFor example, the following output shows an incorrectly configured ATM1 interface:
user@host>show configuration interfaces at-1/2/0atm-options {vpi 1;}<<< the maximum-vcs statement is missingunit 100 {vci 1.100;family inet {address 25.25.25.2/30;}}
- Check if the logical interface unit 100 is created with the following command:
user@host>show interfaces terseat-fpc/pic/portFor example, the following output shows that the link is not created:
user@host>show interfaces terse at-1/2/0Interface Admin Link Proto Local Remoteat-1/2/0 up up<<< missing logical interface at-1/2/0.100
- Include the
maximum-vcsstatement in the configuration:user@host>edituser@host#edit interfacesinterface-nameatm-options vpivpi-identifiermaximum-vcsmaximum-vcsuser@host#showuser@host#commitFor example, the following output shows a correctly configured ATM1 interface:
user@host>show configuration interfaces at-0/1/0atm-options {vpi 1 {maximum-vcs 1024;}}unit 100 {vci 1.100;family inet {address 25.25.25.2/30;}}
- Check that the logical interface is created with the following command:
user@host>run show interfaces terseat-fpc/pic/portFor example, the following output shows that the link is created:
user@host#run show interfaces terse at-1/2/0Interface Admin Link Proto Local Remoteat-1/2/0 up upat-1/2/0.100 up up inet 25.25.25.2/30What It Means
The steps above show that initially the logical interface
at-1/2/0.100is not created because themaximum-vcsstatement is not included in the ATM1 configuration. When that statement is included, the logical interface is created.