Verifying 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 verify that VCI is configured correctly on your ATM1 interface, follow these steps:
- Verify the configuration with the following Junos OS CLI
operational mode command:user@host> show configuration interfaces at-fpc/pic/port
For 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 missing unit 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 terse at-fpc/pic/port
For example, the following output shows that the link is not created:
user@host> show interfaces terse at-1/2/0Interface Admin Link Proto Local Remote at-1/2/0 up up <<< missing logical interface at-1/2/0.100
- Include the maximum-vcs statement in the configuration:user@host> edit user@host# edit interfaces interface-name atm-options vpi vpi-identifier maximum-vcs maximum-vcs user@host# show user@host# commit
For example, the following output shows a correctly configured ATM1 interface:
user@host> show configuration interfaces at-0/1/0 atm-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 terse at-fpc/pic/port
For example, the following output shows that the link is created:
user@host# run show interfaces terse at-1/2/0Interface Admin Link Proto Local Remote at-1/2/0 up up at-1/2/0.100 up up inet 25.25.25.2/30
Meaning
The steps above show that initially the logical interface at-1/2/0.100 is not created because the maximum-vcs statement is not included in the ATM1 configuration. When that statement is included, the logical interface is created.

