cc/td/doc/product/wanbu/ses/1_0_10
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Technical Specifications

Technical Specifications

This appendix lists the relevant technical and compliance specifications for the SES PNNI controller, PNNI and ATM switched virtual circuits in the following sections:


Note   Physical specifications for the Service Expansion Shelf are listed in the Cisco Service Expansion Shelf Hardware Installation Guide.

PNNI Compliance

The SES PNNI controller 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.

The software must also be upgradable to support all enhancements defined in the PNNI V2.0, currently being developed by the ATM Forum.

Other specifications to which the PNNI routing conforms are:

    1. ATM Forum, "PNNI Specification Version 1.0", March 1996, af-pnni-0055.000.

    2. ATM Forum, "PNNI V1.0 Errata and PICS", March 1997, af-pnni-0081.000.

    3. ATM Forum, "Interim Inter-switch Signaling Protocol (IISP) Specification Version 1.0", December 1994, af-pnni-0026.000.

    4. ATM Forum, "Interworking among ATM Networks (draft) Specification", BTD-RA-IAN-01.07, April 1998

    5. ATM Forum, "BISDN Inter Carrier Interface (B-ICI) Specification Version2.2", February, 1997, btd-bici-01.02.

ATM Signaling Compliance

The following ATM Forum signaling specifications are supported, and described in the following sections:


Note   ITU recommendations for B-ISDN DSS2 Signaling is not currently supported.

UNI 3.x Signaling

Capability Reference Network Equipment Mandatory//Optional Support

Point-to-point calls

5.5

M

x

Point-to-multipoint calls

5.6

M

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

IISP Signaling

IISP 1.0 Signaling is supported, including transport of SPVC IEs over an IISP trunk.

PNNI Signaling

Capability Reference Network Equipment Mandatory//Optional Support

Point-to-point calls

6.5.2

M

x

Point-to-multipoint calls

6.6

M

Narrowband ISDN

6.3.2, 6.4.7

O

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
Capability Reference Network Equipment Mandatory//Optional Support

Connection Tracing

6.7

x

Path Tracing

6.7

x

1.

ATM Signaling Interworking

Interworking between all combinations of signaling protocol will be supported at all interfaces types: UNI to UNI, UNI to NNI and NNI to NNI.

Protocol

UNI 3.0

UNI 3.1

UNI 4.0

IISP 1.0

PNNI 1.0

UNI 3.0

x

x

x

x

x

UNI 3.1

x

x

x

x

x

IISP 1.0

x

x

x

x

x

PNNI 1.0

x

x

x

x

x

Networking Application Support


Table A-1: Networking Applications Support
Application Support

LANE

x

Classical IP over ATM (RFC 1577)

x

MPOA

x

MARS

VTOA

x

SPVC Services

x

LANE, Classical IP over ATM, and MPOA will not be implemented as part of the SVC services in the SES PNNI controller, but will be supported when they are running on equipment directly or indirectly connected to it.

VTOA is implemented on MGX8850 Release 1.0. BPX/SES will support VTOA when MGX8850 Release 1.0 become a feeder node for BPX/SES.

SPVC service is supported and implemented in BPX/SES PNNI Controller in this release.

Interoperability Support

The SES PNNI controller is interoperable with all standards-compliant networking equipment.

The SES PNNI controller is also backward compatible with ESP v2.X.

Processor Switching Module (PXM) Specifications

Table A-2 contains general specifications for the Processor Switching Module (PXM) on the Service Expansion Shelf. The table includes information for the two types of back cards—the control access card and uplink card (with ports serving either as trunks or user-ports)


Table A-2: PXM Specifications.
Category Description

Control access:

These ports exits on the
PXM-UI back card.

  • Control port: RJ45 connector, EIA/TIA 232, DTE mode, asynchronous interface 19,200 baud, 1 start bit, 1 stop bit, no parity bits.

  • Maintenance port: RJ45 connector, EIA/TIA 232, DTE mode, asynchronous interface 9600 baud, 1 start bit, 1 stop bit, no parity bits.

  • LAN port: RJ45 connector, 10-baseT, 802.3 Ethernet.

Uplink ports and connectors:

An uplink card can have
one of these number and type of connectors. The wavelength on optical lines is 1310 nm.

  • 2 T3 ports, BNC connectors

  • 2 E3, BNC connectors

  • 4 OC3 multi-mode fiber, SC connectors

  • 4 OC3 single-mode fiber, intermediate reach, SC connectors

  • 4 OC3 single-mode fiber, long reach, SC connectors

Number of logical ports:

32 across all physical ports on the uplink card.

LEDs on PXM front card:

LEDs display status, but alarm history is a switch.

Status for the card:

  • Green means active.

  • Red means failed.

  • Yellow indicates the standby card.

LAN activity: flashing green indicates activity.

Node alarm:

  • Red indicates major alarm.

  • Yellow indicates minor alarm.

Node power (note that each AC power supply also has an LED):

  • "DC OK A" is green for okay or red for trouble.

  • "DC OK B" is green for okay or red for trouble.

Alarm history: ACO

Port interface (per port):

  • Green means active and okay.

  • Red means active and local alarm.

  • Yellow means active and remote alarm.

  • No light means inactive or not provided.

LEDs on back cards:

Green means active. No light means inactive or not provided.

Synchronization:

These clock sources satisfy Stratum 4 requirements.

8 KHz clock derived from the following sources:

  • Internal 8 KHz clock (10 ppm).

  • Service modules or trunk line interfaces.

  • External BITS clock port.

  • T1 clock rate 1.544 MHz +/- 50 bps.

  • E1 clock rate 2.048 MHz +/- 100 bps (can be either sync or data signal).

BITS clock interface:

  • T1 with an RJ45 connector.

  • E1 with an SMB connector.

Trunk history counters:

  • Ingress, per connection:
    Number of received cells with CLP=0.
    Number of received cells with CLP=1.

  • Egress, per connection:
    Number of received cells.
    Number of transmitted cells.
    Number of received cells with EFCI bit set.
    Number of transmitted cells with EFCI bit set.

Connection capacities
supported by PXM:

  • Maximum number of connections:
    16,000 bi-directional channels for local switching.
    32,000 bi-directional channels for switching across uplink card.

  • Maximum aggregate bandwidth:
    600 Mbps local switching (service module to service module).
    1,200 Mbps switching across uplink.

  • Cell memory: 256K cells.

Processor clock speed and memory specifics:

  • Clock speed: 200 MHz internal, 50 Mhz external.

  • Flash memory: 2 Mbytes.

  • DRAM: 64 Mbytes, upgradeable to 128 Mbytes.

  • Secondary cache: 512 Kbytes.

  • BRAM: 128 Kbytes.

  • Hard disk: 2.1 Gbytes.

Alarm indicators (audible and visual):

Central office-compatible alarm indicators and controls through a DB15 connector.

Maintenance features:

  • Internal isolation loopback.
    External remote loopback.
    Hot-pluggable.

Card dimensions:

  • Front card: 15.65 inches by 16.83 inches.
    Back card: 7.25 inches by 4.125 inches.

Power:

Requires -48 VDC, dissipates 150 W.


1
PNNI 2.0 is yet to be finalized. A pre-standard connection trace and path trace are supported in this release.

hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Sep 28 15:07:04 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.