Related Documentation
- M Series
- Checklist for Determining ATM Interface Type
- Determine the ATM Interface Type and Configuration
- Check that the ATM Configuration Is Correct
- MX Series
- Checklist for Determining ATM Interface Type
- Determine the ATM Interface Type and Configuration
- T Series
- Checklist for Determining ATM Interface Type
- Determine the ATM Interface Type and Configuration
- Check that the ATM Configuration Is Correct
Examples of Incorrect Configurations of ATM Options
Even though ATM1 and ATM2 IQ interfaces may be configured with the incorrect options, the configuration may commit but the logical interface may not come up. Here are some examples of incorrectly configured options:
- Check the Configuration of the VCI on an ATM1 Interface
- Check the Configuration of the VCI on an ATM2 IQ Interface
- Check the Configuration of Promiscuous Mode on an ATM2 IQ Interface
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 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.
Check the Configuration of the VCI on an ATM2 IQ Interface
Purpose
If your configuration of the VCI is incorrect, the logical interface is not created.
Action
To check that VCI is configured correctly on your ATM2 IQ interface, follow these steps:
- Check 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 ATM2 IQ interface:
user@host> show configuration interfaces at-0/1/0atm-options { vpi 1 { maximum-vcs 200; <<< incorrectly included } } unit 100 { vci 1.100; family inet { address 25.25.25.1/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-0/1/0Interface Admin Link Proto Local Remote at-0/1/0 up up <<< missing logical interface at-0/1/0.100
- Delete the incorrect maximum-vcs statement from
the configuration: user@host> edit user@host# edit interfaces interface-name atm-options vpi vpi-identifier user@host# delete maximum-vcs user@host# show user@host# commit
For example, the following output shows a correctly configured ATM2 IQ interface:
user@host> show configuration interfaces at-0/1/0atm-options { vpi 1 { } } unit 100 { vci 1.100; family inet { address 25.25.25.1/30; } } - Check that the logical interface 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 created:
user@host> show interfaces terse at-0/1/0Interface Admin Link Proto Local Remote at-0/1/0 up up at-0/1/0.100 up up inet 25.25.25.1/30
Meaning
The steps above show that initially the logical interface at-0/1/0.100 is not created because the maximum-vcs statement is included in the ATM2 IQ configuration. When that statement is deleted, the logical interface is created.
Check the Configuration of Promiscuous Mode on an ATM2 IQ Interface
Purpose
If your configuration of promiscuous mode is incorrect, the logical interface is not created. ATM2 IQ interfaces must have the pic-type atm2 statement included if you are including the promiscuous-mode statement in the configuration.
Action
To check that promiscuous mode is configured correctly on your ATM2 IQ interface, follow these steps:
- Check 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 promiscuous mode incorrectly configured on an ATM2 IQ interface:
user@host> show configuration interfaces at-1/2/0encapsulation atm-ccc-cell-relay; atm-options { promiscuous-mode { <<< the pic-type statement is missing vpi 1; } } unit 1 { vpi 1; } - Check if the logical interface unit 1 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 not created:
user@host# run show interfaces terse at-0/1/0Interface Admin Link Proto Local Remote at-0/1/0 up up <<< missing logical interface at-0/1/0.1
- Include the pic-type statement in the configuration:user@host> edit user@host# set interfaces interface-name atm-options pic-type atm2 user@host# show user@host# commit
For example, the following output shows promiscuous mode correctly configured on an ATM2 IQ interface:
user@host> show configuration interfaces at-0/1/0encapsulation atm-ccc-cell-relay; atm-options { pic-type atm2; promiscuous-mode { vpi 1; } } unit 1 { vpi 1; } - 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-0/1/0Interface Admin Link Proto Local Remote at-0/1/0 up up at-0/1/0.1 up up ccc
Meaning
The steps above show that initially the logical interface at-0/1/0.1 is not created because the pic-type statement is not included with the promiscuous-mode statement in the ATM2 IQ configuration. When that statement is included, the logical interface is created.
Related Documentation
- M Series
- Checklist for Determining ATM Interface Type
- Determine the ATM Interface Type and Configuration
- Check that the ATM Configuration Is Correct
- MX Series
- Checklist for Determining ATM Interface Type
- Determine the ATM Interface Type and Configuration
- T Series
- Checklist for Determining ATM Interface Type
- Determine the ATM Interface Type and Configuration
- Check that the ATM Configuration Is Correct

