Specifications

3-60
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches
Release 5.2, Part Number OL-6484-01 Rev. C0, September 2005
Chapter 3 Provisioning ATM Services
General AXSM Configuration Procedures
M8950_DC.5.AXSM.a > addfdr 1
Tip The interface number is displayed in the dspports command report.
Note The addfdr command is blocked if other connections have been defined on the interface.
Step 3 To display the feeder ports configured on the AXSM card, enter the dspfdrs command.
Step 4 To display information on a specific feeder port, enter the dspfdr <ifnum> command and replace ifnum
with the interface number.
Note For more information on managing feeder node connections, refer to the Cisco MGX 8800/8900 Series
Configuration Guide, Release 5.2.
After you configure a feeder connection, you can enter the dspcons command to check for alarms on the
feeder line. In the example below, the Abitfail alarm on connections 3 and 4 indicate a communication
problem between the routing switch and the feeder node.
MGX8850.13.AXSM.a > dspcons
record Identifier Type SrvcType M/S Upld Admn Alarm
------ ---------- ---- -------- --- ---- ---- -----
0 01.0001.00032 VCC ubr1 M 00dfdfe9 UP multiple
1 01.0001.00033 VCC ubr1 M 00de8ad8 UP multiple
2 01.0001.00041 VCC cbr1 S 00dfb0d8 UP Condn
3 01.0001.00042 VCC cbr1 S 00dfe281 UP Abitfail
4 01.0001.00043 VCC cbr1 S 00dfe28a UP Abitfail
5 01.0001.00052 VCC ubr1 S 00e1244f UP multiple
Possible causes for the alarms shown above include:
• Disconnected or damaged line
• Feeder port not configured to communicate with routing switch
• Service module failure in feeder
Defining Destination Addresses for Static Links
Typically, an AINI or IISP static link joins two independent networks. AINI or IISP links are used
instead of PNNI so that the topologies of the two networks remain unknown to the each other.
When creating a static link, you must identify destination addresses for each side of the link. These
addresses identify which ATM nodes are accessible on the other side of the link. After you define these
addresses, all requests for these addresses are routed over the static link to the other network.
Note To enable bidirectional call initiation, the appropriate destination address must be configured at each end
of the link. For example, if nodes A and B have PNNI connections to a static link, the ATM address for
Node B must be added to the Node A side of the static link, and the Node A address must be added to
the Node B side of the static link.