This appendix lists the relevant technical and compliance specifications for the Cisco MGX 8850 Release 3 PXM45 and PXM1E based PNNI controllers, PNNI, and ATM switched virtual circuits in the following sections:
PNNI Compliance
ATM Signaling Compliance
Processor Switching Module Specifications
UNI 4.0
AINI 3.0 and 3.1
Note This appendix is not a comprehensive list of all the standards that are supported on the Cisco MGX 8850
Release 3 PXM45 and PXM1E based switch. To verify the support of a specific standard that is not listed
in this appendix, please contact your Cisco account representative.
PNNI Compliance
The PXM45 and PXM1E based PNNI routing software was designed to be compliant with 1 below. The software supports robust topology convergence, dynamic and QoS based routing in hierarchical ATM networks with scalability from small to very large networks.
Other specifications to which the PNNI routing conforms are as follows:
1. ATM Forum, "PNNI Specification Version 1.0," af-pnni-0055.000, March 1996
2. ATM Forum, "PNNI V1.0 Errata and PICS," af-pnni-0081.000, March 1997
3. ATM Forum, "Interim Inter-switch Signaling Protocol (IISP) Specification Version 1.0," af-pnni-0026.000, December 1994
4. AINI
5. PNNI v2.0 draft
6. Path and Connection Trace
ATM Signaling Compliance
The following ATM Forum signaling specifications are supported:
UNI 3.0/3.1 Signaling
IISP Signaling
PNNI Signaling
ATM Signaling Interworking
Note ITU recommendations for B-ISDN DSS2 signaling is not currently supported.
UNI 3.0/3.1 Signaling
UNI 3.x signaling is supported.
Table D-1 UNI 3.x Signaling
Capability
Reference
Network Equipment Mandatory/Optional
Support
Point-to-Point calls
5.5
M
x
Address Registration
5.8
—
x
Sub-addressing
5.4.5.12, 14
—
x
B-LLI Negotiation
Annex C
M
x
AAL Parameter Negotiation
Annex F
M
x
UNI 4.0 Signaling
UNI 4.0 signaling is supported.
IISP Signaling
IISP 1.0 signaling is supported, including transport of SPVC IEs over an IISP trunk.
PNNI Signaling
PNNI signaling is supported,
Table D-2 PNNI Signaling
Capability
Reference
Network Equipment Mandatory//Optional
Support
Point-to-Point calls
6.5.2
M
x
Associated signaling
6.5.2.2.1
O
x
Non-associated signaling
6.5.2.2.2
O
x
ATM Parameter Negotiation
6.5.2.3.4
O
—
QoS Parameter Selection
6.5.2.3.5
O
x
ABR Signaling
6.5.2.3.6
O
x
Switched Virtual Path
6.5.2.2.2.2
O
x
Crankback
8. Annex B
M
x
Soft PVPC and PVCC
9. Annex C
O
x
SPVC Any VCCI value
9.2.3.1
O
Generic Identifier Transport
6.4.5.31
O
x
Frame Discard
—
O
x
In addition to the above, the following PNNI 2.0 capabilities are supported on an interface.
Table D-3 PNNI 2.0 Interface Capabilities
Capability
Reference
Network Equipment Mandatory//Optional
Support
Connection Tracing
6.7
—
x
Path Tracing
6.7
—
x
ATM Signaling Interworking
Interworking between all combinations of signaling protocol is supported at all interfaces types: UNI to UNI, UNI to NNI and NNI to NNI.
Table D-4 ATM Signaling Interworking
Protocol
UNI 3.0
UNI 3.1
UNI 4.0
IISP 1.0
PNNI 1.0
AINI 3.0
AINI 3.1
UNI 3.0/3.1
x
x
x
x
x
x
x
UNI 4.0
x
x
x
x
x
x
x
IISP 1.0
x
x
x
x
x
x
x
PNNI 1.0
x
x
x
x
x
x
x
AINI 3.0
x
x
x
x
x
x
x
AINI 3.1
x
x
x
x
x
x
x
SONET/SDH
The standards and responsible organizations with which MGX 8850 SONET technology complies are as follows:
Bell Communications Research-SONET Transport Systems: Common Generic Criteria, GR-253-CORE, Issue 2, 1995.
ITU Recommendation G.782-Types and General Characteristics of Synchronous Digital Hierarchy (SDH) Equipment, January 1994.
ITU Recommendation G.783-Characteristics of Synchronous Digital Hierarchy (SDH) Equipment Functional Blocks, January 1994.
ITU Recommendation G.832-Transport of SDH Elements on PDH Networks: Frame and Multiplexing Structures, November 1993.
ITU Recommendation G.958-Digital Line Systems based on the Synchronous Digital Hierarchy for use on Optical Fibre Cables, November 1994.
