This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
3.6.1 AtmPort without IMA ............................................................................................................................................................................................................ 77 3.6.2 AtmPort with IMA .................................................................................................................................................................................................................. 79
Physical media: - PDH = Plesiochronous Digital Hierarchy: E1, T1, J1. Electrical signal, copper cable. - SDH = Synchronous Digital Hierarchy. Optical signal, fiber. - EthernetWays of sharing the physical media with several users: - TDM (on PDH) = Time Division Multiplexing (dividing the physical media in timeslots) - ATM (on PDH/SDH) = Asynchronous Transfer Mode (cells, virtual paths, virtual channels) - IP (on Ethernet or ATM)
1.1 Supported Standards and HW capabilities
Standard Interface PDH/SDH Physical media Raw Bitrate (Mb/s)
ET-M1 ROJ 119 2101 8 E1/J1/T1 1 slot yes yes no no 1 per port 28 per port 2 per port 1ET-MC1 ROJ 119 2163 8 E1/J1/T1 1 slot yes yes yes no 2 per port 28 per port 2 per port 2
CBU ROJ 119 2209 4 E1/J1/T1 1 slot yes yes yes no 2 per port 28 per port 2 per port 2ET-M3 ROJ 119 2214 2 E3/T3 1 slot yes yes no no 16 per port 240 per port 16 per port 2
ET-MFG ROJ 119 2232 2 Gigabit Ethernet 1 slot no no n/a n/a n/a n/a n/a n/aGPB 1 Fast Ethernet (10/100Mb) 1 slot no no n/a n/a n/a n/a n/a n/a
Note: when using more than 2 ports on ET-MF4, consideration has to be taken to the fact that there is a bandwidth limitation of 320Mb/s (if Aal2 is used) and 450 Mb/s (if Aal2 is not used).Note: ET-MFG supports link protection where one port can be standby for the other.
1.2 Configuration
CPP4
RXI1> momt etm
--------------------------------MO classes under Etm1--------------------------------E1PhysPathTerm[0-8] Ds0Bundle[0-31]J1PhysPathTerm[0-8] Ds0Bundle[0-24]T1PhysPathTerm[0-8] Ds0Bundle[0-24]--------------------------------MO classes under Etmc1--------------------------------E1PhysPathTerm[0-8] Ds0Bundle[0-31]J1PhysPathTerm[0-8] Ds0Bundle[0-24]T1PhysPathTerm[0-8] Ds0Bundle[0-24]--------------------------------MO classes under Etm3--------------------------------
##################################################################################MO Class Attributes/Actions##################################################################################Etm4 Etm4Id,availabilityStatus,operationalState,userLabelThis MO represents the hardware of the ET-M4 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO.The ET-M4 board contains 2 physical ports that can be configured as either STM1(ETSI/TTC) or OC3C (ANSI). The board supports unchannelised ATM access (i.e. it maps ATMs cells directly into an SDH VC4 container).The board supports up to 1800 ATM VC connections.The number of terminated VPs are limited to 48/board.The board supports up to 750 VC UBR+ connections.The ET-M4 board contains 128 AAL2 multiplexers.The ET-M4 board supports up to 256 bidirectional F4/F5 PM flow per board. Note that only 128 can be used for VccTp.Note! IMA is not applicable for the ETM4 board.
Finn Magnusson 2008-05-12 rev PA32 5/167
Note! The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 256 per board.Note! When using the Etm4 board the performance monitoring counters in the transmit direction found on the AtmPort MO does not show the following cells: CC cells and OAM FPM cells.----------------------------------------------------------------------------------
CPP5
The EtmX MOs are replaced with a generic MO ExchangeTerminal. This is to facilitate replacing ET boards with different kind of ET boards. Eg. to replace ET-M1 with ET-MC1, ET-M4 with ET-MF4, etc.
availabilityStatus 0 (NO_STATUS)description Struct{5} >>> 1.aal2LayerDescription = This board provides a maximum of 128 AAL2 multiplexers per port. The board does not support QOS separation within one and the same AAL2 path >>> 2.atmLayerDescription = This board provides a maximum of 48VP connections and 1800 VC connections. 750 of these can be used for connections with service category UBR+. The board supports up to 256 bidirectional PM F4/F5 PM measurement per physical port The board does not support >>> 3.etType = ET-M4 >>> 4.physicalLayerDescription = This board provides 2 physical STM-1 ports that can be configured for unchannalised ATM in either ETSI/ANSI or TTC mode. >>> 5.tdmSupport = This board does not support TDM switching or circuit emulationoperationalState 1 (ENABLED)userLabel =================================================================================================================Total: 1 MOs
// Os155SpiTtp::standardMode tells if the port is for ETSI, ANSI, TTC// Os155SpiTtp::muxMode tells if the port is channelised, unchannelised and if it is active or standby in the Mspg.
MO Class Attribute Type Flags##################################################################################################Os155SpiTtp muxMode enumRef:MuxMode restricted,noNotification,mandatory--------------------------------------------------------------------------------------------------The level at which the STM-1 or OC3 signal is demultiplexed.**************************************************************************************************Os155SpiTtp standardMode enumRef:StandardMode restricted,noNotification,mandatory--------------------------------------------------------------------------------------------------The standard that this MO complies to.**************************************************************************************************
RXI3> mom muxmode|standardmode
##################################################################################Enum Values##################################################################################MuxMode 0:STANDBY, 1:E1_T1_HG_LEVEL, 2:VC4_STS3CSPE_LEVEL----------------------------------------------------------------------------------Indicates what multiplexing is being used. - STANDBY: Standby for protection. - E1_T1_HG_LEVEL: Multiplexing terminated at the E1/T1/HG level. - VC4_STS3CSPE_LEVEL: Multiplexing terminated at the VC-4/STS3CSPE level.**********************************************************************************StandardMode 0:ANSI, 1:ETSI, 2:TTC----------------------------------------------------------------------------------Indicates what standard the MAO is operating to. - ANSI: The standard mode is ANSI. - ETSI: The standard mode is ETSI. - TTC: The standard mode is Telecommunication Technology Committee (TTC).**********************************************************************************
=================================================================================================================346 Equipment=1,Subrack=MS,Slot=22,PlugInUnit=1,ExchangeTerminal=1=================================================================================================================ExchangeTerminalId 1availabilityStatus 0 (NO_STATUS)description Struct{5} >>> 1.aal2LayerDescription = The board provides a maximum of 2 AAL2 multiplexers per E1/DS1 channel. The board does support QOS separation within one and the same AAL2 path >>> 2.atmLayerDescription = This board provides a maximum of 2 VP connections and 30 VC connections per E1/DS1 channel. The board supports fractional ATM and IMA.The E1/DS1 channels on the board are divided into 9 (in case of ETSI configuration) or 12 (in case of ANSI configuration) >>> 3.etType = ET-MC41 >>> 4.physicalLayerDescription = This board provides 1 physical STM-1 port that can be configured for E1/DS1 channalisation in either ETSI or ANSI mode. The board supports MSP 1+1 and equipment protection, in which case two boards are connected to each other via a node internal cable cal >>> 5.tdmSupport = All ports on the board can be used for circuit emulation and TDM switchingoperationalState 1 (ENABLED)userLabel =================================================================================================================349 Equipment=1,Subrack=MS,Slot=22,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1=================================================================================================================Os155SpiTtpId pp1administrativeState 1 (UNLOCKED)availabilityStatus 0 (NO_STATUS)lineNo 1loopBack 0 (NONE)msAisReporting falsemsDegM 7msDegThreshold 30msRdiReporting falsemuxMode 1 (E1_T1_HG_LEVEL)operationalState 1 (ENABLED)reservedBy [0] = reservedBySync shutDownTimeout 1800standardMode 1 (ETSI)userLabel =================================================================================================================350 Equipment=1,Subrack=MS,Slot=22,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1,Vc4Ttp=1=================================================================================================================Vc4TtpId 1
Ds0Bundle::tdmMode should be set to: - true when used for TDM (by TdmTermGrp or Mtp2Tp MO) - false when used for fractional ATM (by AtmPort MO) - false when used for Circuit Emulation (by Aal1TpVccTp MO, used for carrying TDM traffic over ATM)
=================================================================================================================533 Equipment=1,Subrack=MS,Slot=18,PlugInUnit=1,ExchangeTerminal=1=================================================================================================================ExchangeTerminalId 1availabilityStatus 0 (NO_STATUS)description Struct{5} >>> 1.aal2LayerDescription = The board provides a maximum of 16 AAL2 multiplexers. The board does support QOS separation within one and the same AAL2 path >>> 2.atmLayerDescription = This board provides a maximum of 16VP connections and 240 VC connections. The board supports fractional ATM and IMA. The board supports up to 1 bidirectional PM F4/F5 PM measurement per physical port.At the VP/VC end points, the Lost FPM/BR cells counters >>> 3.etType = ET-MC1 >>> 4.physicalLayerDescription = This board provides 8 physical ports that can be configured in either E1, DS1 or J1 mode. All ports on the board must be configured to the same standard. >>> 5.tdmSupport = All ports on the board can be used for circuit emulation and TDM switchingoperationalState 1 (ENABLED)userLabel =================================================================================================================541 Equipment=1,Subrack=MS,Slot=18,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm=pp1=================================================================================================================E1PhysPathTermId pp1administrativeState 1 (UNLOCKED)aisReporting falseavailabilityStatus 0 (NO_STATUS)crc4Mode 2 (AUTOMATIC)degDegM 7degDegThr 30idlePattern 0 (UNDEFINED)lineNo 1loopback 0 (NONE)operationalState 1 (ENABLED)
Finn Magnusson 2008-05-12 rev PA32 16/167
rdiReporting falsereservedByImaLink ImaGroup=MS-18-ima1,ImaLink=1reservedBySync reservedByTraffic shutDownTimeout 1800userLabel =================================================================================================================Total: 2 MOs
=================================================================================================================69 Equipment=1,Subrack=MS,Slot=21,PlugInUnit=1,ExchangeTerminal=1=================================================================================================================ExchangeTerminalId 1availabilityStatus 0 (NO_STATUS)description Struct{5} >>> 1.aal2LayerDescription = This board provides a maximum of 128 AAL2 multiplexers per port. The board does not support QOS separation within one and the same AAL2 path >>> 2.atmLayerDescription = This board provides a maximum of 48VP connections and 1800 VC connections. 750 of these can be used for connections with service category UBR+. The board supports up to 256 bidirectional PM F4/F5 PM measurement per physical port The board does not support >>> 3.etType = ET-M4 >>> 4.physicalLayerDescription = This board provides 2 physical STM-1 ports that can be configured for unchannalised ATM in either ETSI/ANSI or TTC mode. >>> 5.tdmSupport = This board does not support TDM switching or circuit emulationoperationalState 1 (ENABLED)userLabel =================================================================================================================72 Equipment=1,Subrack=MS,Slot=21,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1=================================================================================================================Os155SpiTtpId pp1administrativeState 1 (UNLOCKED)availabilityStatus 2 (FAILED)lineNo 1loopBack 0 (NONE)msAisReporting falsemsDegM 7
Multiplex Section Protection (MSP) is supported on ET-MC41, ET-C41 and ET-MF4 to provide 1+1 STM-1 link redundancy:- if both links are on two separate boards then there is equipment protection (protection against HW fault on ET). A special cable called AUG link must then be connected between the active board and the standby board. - if both links are on the same board then there is only link protection (only possible on ET-MF4 since ET-MC41 only has one port).
Node A
Node B
ET
ET
Node A
Node B
ET
ET
ET
Link Protection only Equipment and Link
Protection
Active
Standby
AUG link
AUG link
ET
RXI4> mom mspg
##################################################################################MO Class Attributes/Actions##################################################################################Mspg MspgId,availabilityStatus,degCauseMsp,operationalState,os155SpiStandbyId,os155SpiWorkingId,selectedBoard,selectedPort,switchMode,userLabel manualMspSwitchThe MSPG (Multiplex Section Protection Group) object enables two different protection mechanism in Cello. First it enables a standard 1+1 MSP mechanism. A failure on the working line will thus cause a sub 50 ms switch to the standby line.Secondly the MSPG is used to enable equipment protection, whereas a failure of the working board will cause a switch to the standby board. While executing an equipment protection switch, the node on the other end of the multiplexer section, will experience a standard 1+1 MSP switch.It is possible to force traffic to one port/board by using administrative state.Setting administrative state to locked on the working board, will automatically cause an equipment switch to the standby board. Similarily setting administrative state to locked on the working port, will cause an MSP switch to the standby port.The process of configuring a MSP protection interface is as follows:1) Create the working interface as normal.2) Create the standby interface by creating an Os155SpiTtp with mux mode set to STANDBY (standby for protection).3) Create a MSPG object with references to the two Os155SpiTtp objects.Note! The ports selected for MSPG must be have the attribute standardMode configured in exactly the same way.Note! The Os155SpiTtp created for standby will not create any children, i.e no Vc4Ttp or Vc4Ttp, Vc12Ttp and E1Ttp will be created. Nor will object of type Sts1SpeTtp, Vt15Ttp or T1Ttp be created.----------------------------------------------------------------------------------
1011 Equipment=1,Subrack=MS,Slot=10,PlugInUnit=1,Program=CXC1324173_R50KV01===================================================================================Total: 11 MOs
1.2.4 IMA
Inverse Multiplexing for ATM (IMA) allows to map an AtmPort onto several physical ports. Up to 8 physical ports can be used in an ImaGroup.This is useful, for instance, in order to have an Aal2 VC with a larger bandwidth than the capacity of the physical port.For instance in HSDPA, having one large Aal2 VC gives better throughput than having several smaller Aal2 VC’s.
stt[r] [<Filter>] [<stateFilter>]*******************************************************Purpose: Display state and user of Physical Ports and Ds0Bundles....<cut>...
Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=1,T1Ttp=1 1/1.1.1 11 AtmPort=MS-24-1-1-1Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=2,T1Ttp=1 1/1.1.2 111 AtmPort=MS-24-ima1Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=3,T1Ttp=1 1/1.1.3 111 AtmPort=MS-24-ima1Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=4,T1Ttp=1 1/1.1.4 0 Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=5,T1Ttp=1 1/1.2.1 0 Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=6,T1Ttp=1 1/1.2.2 111 AtmPort=MS-24-imaSubrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=7,T1Ttp=1 1/1.2.3 111 AtmPort=MS-24-imaSubrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=8,T1Ttp=1 1/1.2.4 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=9,T1Ttp=1 2/1.3.1 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=10,T1Ttp=1 2/1.3.2 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=11,T1Ttp=1 2/1.3.3 L ...<cut>...======================================================================================================================Total: 265 MOs
MGW1> h stt
*******************************************************stt[r] [<Filter>] [<stateFilter>]*******************************************************Display state and user of Physical Ports and Ds0Bundles.
Filtering: show only ports connected to TdmTermGroups:
======================================================================================================================Port CG/K.L.M PUI USER======================================================================================================================Subrack=MS,Slot=9,..*,Os155.*=pp1,Vc4Ttp=1 00 AtmPort=MS-9-1Subrack=MS,Slot=9,..*,Os155.*=pp2,Vc4Ttp=1 00 AtmPort=MS-9-2Subrack=MS,Slot=16,.*,E1PhysPathTerm=pp5 L0 AtmPort=MS-16-5Subrack=MS,Slot=16,.*,E1PhysPathTerm=pp6 L0 AtmPort=MS-16-6Subrack=MS,Slot=16,.*,E1PhysPathTerm=pp7 L0 AtmPort=MS-16-7Subrack=MS,Slot=16,.*,E1PhysPathTerm=pp8 10 AtmPort=MS-16-8Subrack=MS,Slot=20,.*,E1PhysPathTerm=pp5 L00 AtmPort=MS-20-ima2Subrack=MS,Slot=20,.*,E1PhysPathTerm=pp6 L00 AtmPort=MS-20-ima2Subrack=MS,Slot=20,.*,E1PhysPathTerm=pp7 L00 AtmPort=MS-20-ima2Subrack=MS,Slot=20,.*,E1PhysPathTerm=pp8 L00 AtmPort=MS-20-ima2Subrack=MS,Slot=21,.*,E1PhysPathTerm=pp5 L Subrack=MS,Slot=21,.*,E1PhysPathTerm=pp6 L Subrack=MS,Slot=21,.*,E1PhysPathTerm=pp7 L Subrack=MS,Slot=21,.*,E1PhysPathTerm=pp8 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=4,T1Ttp=1 1/1.1.4 0 Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=5,T1Ttp=1 1/1.2.1 0 Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=8,T1Ttp=1 1/1.2.4 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=9,T1Ttp=1 2/1.3.1 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=10,T1Ttp=1 2/1.3.2 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=11,T1Ttp=1 2/1.3.3 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=12,T1Ttp=1 2/1.3.4 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=13,T1Ttp=1 2/1.4.1 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=14,T1Ttp=1 2/1.4.2 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=15,T1Ttp=1 2/1.4.3 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=16,T1Ttp=1 2/1.4.4 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=17,T1Ttp=1 3/1.5.1 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=18,T1Ttp=1 3/1.5.2 0 Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=19,T1Ttp=1 3/1.5.3 0 Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=20,T1Ttp=1 3/1.5.4 0 Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=21,T1Ttp=1 3/1.6.1 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=22,T1Ttp=1 3/1.6.2 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=23,T1Ttp=1 3/1.6.3 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=24,T1Ttp=1 3/1.6.4 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=25,T1Ttp=1 4/1.7.1 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=26,T1Ttp=1 4/1.7.2 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=27,T1Ttp=1 4/1.7.3 L Subrack=MS,Slot=24,.*,Os155.*=pp1,Sts1.*=1,Vt15Ttp=28,T1Ttp=1 4/1.7.4 L ======================================================================================================================Total: 37 MOs
Finn Magnusson 2008-05-12 rev PA32 30/167
MGW01 > stt
======================================================================================================================Port CG/K.L.M PUI USER======================================================================================================================Subrack=2,Slot=4,..*,Os155.*=2041,Vc4Ttp=1 11 AtmPort=2041Subrack=2,Slot=4,..*,Os155.*=2042,Vc4Ttp=1 11 AtmPort=2042Subrack=2,Slot=5,..*,Os155.*=2051,Vc4Ttp=1 11 AtmPort=2051Subrack=2,Slot=5,..*,Os155.*=2052,Vc4Ttp=1 11 AtmPort=2052Subrack=2,Slot=6,..*,Os155.*=2061,Vc4Ttp=1 11 AtmPort=2061Subrack=2,Slot=6,..*,Os155.*=2062,Vc4Ttp=1 00 AtmPort=2062Subrack=2,Slot=7,..*,Os155.*=2071,Vc4Ttp=1 11 AtmPort=2071Subrack=2,Slot=7,..*,Os155.*=2072,Vc4Ttp=1 00 AtmPort=2072...<cut>....Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=1,E1Ttp=1,Ds0Bundle=1 1/1.1.1 11 TdmTermGrp=5Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=2,E1Ttp=1,Ds0Bundle=1 1/1.1.2 11 TdmTermGrp=6Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=3,E1Ttp=1,Ds0Bundle=1 1/1.1.3 11 TdmTermGrp=7Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=4,E1Ttp=1,Ds0Bundle=1 1/1.2.1 11 TdmTermGrp=8Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=5,E1Ttp=1,Ds0Bundle=1 1/1.2.2 11 TdmTermGrp=3Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=6,E1Ttp=1,Ds0Bundle=1 1/1.2.3 11 TdmTermGrp=4Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=7,E1Ttp=1,Ds0Bundle=1 1/1.3.1 11 TdmTermGrp=17Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=8,E1Ttp=1,Ds0Bundle=1 1/1.3.2 11 TdmTermGrp=18Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=9,E1Ttp=1,Ds0Bundle=1 2/1.3.3 11 TdmTermGrp=19Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=10,E1Ttp=1,Ds0Bundle=1 2/1.4.1 11 TdmTermGrp=20Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=11,E1Ttp=1,Ds0Bundle=1 2/1.4.2 11 TdmTermGrp=21Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=12,E1Ttp=1,Ds0Bundle=1 2/1.4.3 11 TdmTermGrp=22Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=13,E1Ttp=1 2/1.5.1 L Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=14,E1Ttp=1 2/1.5.2 L ...<cut>...Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=57,E1Ttp=1 8/3.5.3 L Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=58,E1Ttp=1 8/3.6.1 L Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=59,E1Ttp=1 9/3.6.2 L Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=60,E1Ttp=1 9/3.6.3 L Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=61,E1Ttp=1 9/3.7.1 L Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=62,E1Ttp=1 9/3.7.2 L Subrack=2,Slot=21,.*,Os155.*=2211,Vc4Ttp=1,Vc12Ttp=63,E1Ttp=1 9/3.7.3 L Subrack=2,Slot=25,.*,E1PhysPathTerm=2251,Ds0Bundle=1 11 Mtp2TpItu=1Subrack=2,Slot=25,.*,E1PhysPathTerm=2251,Ds0Bundle=2 11 Mtp2TpItu=2Subrack=2,Slot=25,.*,E1PhysPathTerm=2252,Ds0Bundle=1 11 Mtp2TpItu=3Subrack=2,Slot=25,.*,E1PhysPathTerm=2252,Ds0Bundle=2 11 Mtp2TpItu=4Subrack=2,Slot=25,.*,E1PhysPathTerm=2252,Ds0Bundle=3 11 Mtp2TpItu=5Subrack=2,Slot=25,.*,E1PhysPathTerm=2252,Ds0Bundle=4 11 Mtp2TpItu=6Subrack=2,Slot=25,.*,E1PhysPathTerm=2252,Ds0Bundle=5 11 Mtp2TpItu=7Subrack=2,Slot=25,.*,E1PhysPathTerm=2252,Ds0Bundle=6 11 Mtp2TpItu=8Subrack=2,Slot=25,.*,E1PhysPathTerm=2253 L
Finn Magnusson 2008-05-12 rev PA32 31/167
Subrack=2,Slot=25,.*,E1PhysPathTerm=2254 L Subrack=2,Slot=25,.*,E1PhysPathTerm=2255 L Subrack=2,Slot=25,.*,E1PhysPathTerm=2256 L Subrack=2,Slot=25,.*,E1PhysPathTerm=2257 L Subrack=2,Slot=25,.*,E1PhysPathTerm=2258 L ...<cut>...======================================================================================================================Total: 167 MOs
1.4 Performance Management
Useful for checking the quality of the physical layer.Look for increases of the Errored Seconds (pmEs and pmSes).The number of Errored Seconds is incremented when 30% of the blocks received in a second have bit errors (the percentage can be set in attribute degThr)
##################################################################################################MO Class Attribute Type Flags##################################################################################################E1Ttp degDegThr long readOnly--------------------------------------------------------------------------------------------------The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad.This is a percentage value.Range: 0 to 100, Default=30 **************************************************************************************************E3PhysPathTerm degDegThr long readOnly--------------------------------------------------------------------------------------------------The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad.This is a percentage value.Range: 0 to 100, Default=30 **************************************************************************************************E1PhysPathTerm degDegThr long readOnly--------------------------------------------------------------------------------------------------The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad.This is a percentage value.Range: 0 to 100, Default=30 **************************************************************************************************Os155SpiTtp msDegThreshold long readOnly
Finn Magnusson 2008-05-12 rev PA32 34/167
--------------------------------------------------------------------------------------------------MS - multiplexer section.The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad.This is a percentage value.Note: When operating to the ANSI standard, this attribute has no meaning.Range: 0 to 100, Default=30 **************************************************************************************************J1PhysPathTerm degThreshold long readOnly--------------------------------------------------------------------------------------------------Maximum allowed BER(Bit Error Rate). Degraded signal (DEG) if BER > degThreshold. The attribute gives a maximum BER of 10e-X, where X ranges from 5 to 9 (default 6)Range: 3 to 9, Default=6 **************************************************************************************************Vc12Ttp vcDegThreshold long readOnly--------------------------------------------------------------------------------------------------This threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad.The attribute value is in unit of % (percent).Range: 0 to 100, Default=30 **************************************************************************************************Vc4Ttp vcDegThreshold long readOnly--------------------------------------------------------------------------------------------------This threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad.The attribute value is in unit of % (percent).Range: 0 to 100, Default=30 **************************************************************************************************
RXI3> uv pm_wait
pm_wait = 25 //the interval of 25 seconds can be changed here
RXI3> lpdiff exchangeterminal . !^0
first check...waiting 25 seconds before next check...second check
The ports with unavailable seconds are disabled, this explains why they were unavailable for the whole duration of the pdiffOne port is enabled but has got some errored seconds. This means that there are disturbances on this port.If the disturbances are too frequent, an alarm will be raised to indicate the degraded signal on this port.Possible consequences of degraded signal: - disabled ImaGroup - synchronization problems (if the port is used as syncreference) - node synch problems (if the port goes to RBS) - intermittent loss of contact to the remote node - poor speech quality on the calls going to that node
ALARMS ARE RAISED WHEN THE ERRORED SECONDS ARE TOO HIGH (30% BER for more than 7 seconds)CHECK LGA TO LOOK FOR RAISED/CEASED ALARMS ON DEGRADED TRANSMISSION
RXI3> lga ...<cut>...2007-08-20 18:01:55 AL m PDH Degraded Signal degraded_signal_m3100 Subrack=MS,Slot=12,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1,Vc4Ttp=1,Vc12Ttp=62,E1Ttp=12007-08-20 18:02:11 AL * PDH Degraded Signal degraded_signal_m3100 Subrack=MS,Slot=12,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1,Vc4Ttp=1,Vc12Ttp=62,E1Ttp=1
RXI3> pmom os155 uas
##################################################################################MO Class Pm Counter##################################################################################
Finn Magnusson 2008-05-12 rev PA32 36/167
Os155SpiTtp pmMsUas----------------------------------------------------------------------------------Description: Transmission Unavailable Seconds (SES).The accumulated unavailable time in seconds during the interval. Unavailable time starts when 10 consecutive SES are detected (them being part of the unavailable time) and ends when 10 consecutive non-SES are detected.Condition: This counter is incremented for each second of unavailable time.Note that there is a delay of 10 seconds in the classification of a second as available or unavailable.Counter is reset after measurement period: YesCounter type: PEGUnit: Seconds**********************************************************************************
1.5 Fault Management
1.5.1 Supervision of physical ports
In both examples below we assume that we are supervising the connections from the point of view of Node A.
Example 1• E1PhysPathTerm 1 will appear enabled and without alarms.• E1PhysPathTerm 2 will appear enabled and without alarms. Supervision on ATM layer is necessary to detect the fault, see 3.3• E1PhysPathTerm 3 will appear disabled and with alarms.• E1PhysPathTerm 4 will appear enabled without alarms. Supervision on ATM layer is necessary to detect the fault, see 3.3• E1PhysPathTerm 5 will appear disabled and with alarms.
Finn Magnusson 2008-05-12 rev PA32 37/167
NODE A DACS/DXX (physical layer connections). NODE 1 E1PhysPathTerm=1
NODE 2
NODE 3
E1PhysPathTerm=2
E1PhysPathTerm=3
E1PhysPathTerm=4
NODE 4
E1PhysPathTerm=5
NODE 5
Example 2The Vc12Ttp can be seen as representing the E1 on the channelised STM-1 segment.The E1Ttp can be seen as representing the E1 between Node A and the remote Node.
• To Node1: Both Vc12Ttp and E1Ttp will appear enabled without alarms.• To Node2: Vc12Ttp will appear enabled but E1Ttp will appear disabled with alarms.• To Node3: Both Vc12Ttp and E1Ttp will appear enabled without alarms. Supervision on ATM layer is necessary to detect the fault, see 3.3• To Node4: Both Vc12Ttp and E1Ttp will appear disabled with alarms. Connection needs to be made in DACS/DXX.
Finn Magnusson 2008-05-12 rev PA32 38/167
NODE A DACS/DXX (physical layer connections).
NODE 1
Channelised STM-1 NODE 2
NODE 3
Vc12Ttp=1,E1Ttp=1
Vc12Ttp=2,E1Ttp=1
Vc12Ttp=3,E1Ttp=1
NODE 4
Vc12Ttp=4,E1Ttp=1
1.5.2 Supervision of ImaGroups
Possible reasons for ImaGroup disabled:- 1. not enough ImaLinks are up (there must be at least requiredNumberOfLinks up). Check state of the ImaLinks and E1/T1/J1’s.- 2. some ImaLinks have degraded signal. Check pm counters on ImaLinks and E1/T1/J1s, look for errored seconds.- 3. the IMA chip has hung in the ET device (should be fixed in later CPP releases though).
//Port 3 has degraded signal, too many disturbances caused the ImaGroup to go down
RXI3> pdiff e1group . !^0
...waiting 25 seconds before next check.......=================================================================================================================MO Counter DiffValue=================================================================================================================Subrack=MS,Slot=18,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm=pp3 pmEs 3Subrack=MS,Slot=18,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm=pp3 pmSes 3=================================================================================================================Total: 1 MOs
...waiting 25 seconds before next check.......=================================================================================================================MO Counter DiffValue==================================================================================================================================================================================================================================Total: 0 MOs
Finn Magnusson 2008-05-12 rev PA32 42/167
//Check the T&E log on the ET board
RXI3> lhsh 002000 te log read
$ lhsh 002000 te log read.....0010: [2005-11-01 23:17:04.508] Aet_locIma_proc imagroupro.c:2056 ERROR:ImaGroupRo_handleConstructImaGroupReq:: Failed to set up IMA group on IMADRV (imaGroupFroId=1)....
RXI3> fro ImaGroup=MS-18-ima1
=================================================================================================================MO FroName FroId=================================================================================================================ImaGroup=MS-18-ima1 imaGroupFroId 1=================================================================================================================Total: 1 MOs
RXI3> aet_imamp imagroupfro 1
$ aet_imamp imagroupfro 1******* AET status info - Attribute values for IMA group FRO 1atmPortFroId: 8imaFiCacseCepId: 9totalBw: 8805 ATM cells/seceqmtFroId: 14circuitNo: 1imaGroupRoId: 0 //THERE IS NO RESOURCE OBJECT FOR THE IMAGROUP FROnumberOfLinksInStart: 0numberOfActiveLinks: 4numberOfLinksInStop: 0reqNumberOfLinks: 2numberOfLinks: 4noOfRsrvRspCallbacks: 1clientRef: 0oldReqNumberOfLinks: 0oldNumberOfLinks: 0setAttrReqIndex: 0hecCorrectionMode: ENABLEdeleteGroup: FALSEretValue: AET_IMAGROUPMI_RSP_OK...<cut>...
//CORRECT THE PROBLEM BY UNDEFINING/REDEFINING THE IMAGROUP, THIS WILL FORCE THE RO TO BE CREATEDRXI3> u+
Finn Magnusson 2008-05-12 rev PA32 43/167
....RXI3> rdel ImaGroup=MS-18-ima1....RXI3> u-....RXI3> run $undocommandfile....
//OR: COLD RESTART ON ET BOARD
RXI3> acc 002000 restart
---> cold
2 NETWORK SYNCHRONISATION
Sync references can be connected directly on each TU board (they are then mapped to the MO TuSyncRef) or the signal from a physical port can be used as sync refererence. The clock signal generated by the TU clocks is a 19.44 MHz signal (correponds to 1/8 of the STM-1 bitrate).(Note: TuSyncRef with 1.544 or 10 MHz is not recommended as these signals are usually less reliable than the 2.048 MHz or GPS)
Finn Magnusson 2008-05-12 rev PA32 44/167
TU Board
TuSyncRef 2.048 MHz
(1.544 MHz)
(10 MHz)
GPS
E1PhysPathTerm
T1PhysPathTerm
J1PhysPathTerm
Os155SpiTtp
19.44 MHz (=155,520/8)
//THIS SHOWS THAT E1 IN SLOT 16 IS CURRENTLY THE ACTIVE SYNCH REFERENCE
##################################################################################################MO Class Attribute Type Flags##################################################################################################Synchronization syncRefActivity sequence:enumRef-RefActivity readOnly,nonPersistent,noNotification--------------------------------------------------------------------------------------------------Set of synchronization reference activity attributes.Note: The length of this sequence is always 8.**************************************************************************************************Synchronization syncRefStatus sequence:enumRef-RefState readOnly,nonPersistent,noNotification--------------------------------------------------------------------------------------------------Set of synchronization reference status attributes.Note: The length of this sequence is always 8.**************************************************************************************************
RXI3> mom ref(activity|state)
##################################################################################Enum Values##################################################################################RefState 0:FAILED, 1:DEGRADED, 2:LOSS_OF_TRACKING, 3:OK, 4:REF_PATH_FAILED_A, 5:REF_PATH_FAILED_B----------------------------------------------------------------------------------RefState can have the following values:failed = synchronization reference is not capable to perform its required tasks.degraded = capability of synchronization reference to perform its required tasks is degraded e.g. because of signal level degradation. This value is only applicable for traffic carrying (ET physical path termination) synchronization references. Note:
Finn Magnusson 2008-05-12 rev PA32 46/167
attribute degradationIsFault controls whether synchronization reference degradation is interpreted as a synchronization reference fault or not.lossOfTracking = system clock regulation algorithm on TU board can not follow the 8kHz synchronization reference signal either because of the poor quality of the signal or because of a HW fault at TU board. If all synchronization references repeatedly end up to state lossOfTracking, fault is likely in TU HW.ok = synchronization reference is capable of performing its required tasks.refPathFailed_A = Synchronization reference cannot be distributed on plane A.refPathFailed_B = Synchronization reference cannot be distributed on plane B. - FAILED: - DEGRADED: - LOSS_OF_TRACKING: - OK: - REF_PATH_FAILED_A: - REF_PATH_FAILED_B: **********************************************************************************RefActivity 1:INACTIVE, 2:ACTIVE----------------------------------------------------------------------------------RefActivity can have the following values:inactive = Synchronization reference is currently not used in system clock generation.active = Synchronization is used in system clock generation. - INACTIVE: - ACTIVE: **********************************************************************************
##################################################################################MO Class Attributes/Actions
Finn Magnusson 2008-05-12 rev PA32 47/167
##################################################################################Synchronization SynchronizationId,degradationIsFault,syncRefActivity,syncRefPriority,syncRefStatus,syncReference,systemClockA,systemClockB,systemClockRedundancy,userLabel addSyncRefResource,changeSyncRefPriority,removeSyncRefResource,resetLossOfTrackingThis MO is used to administer synchronization references for the network synchronization function and to view the system clock state of Timing Unit boards.Synchronization can have 0 to 8 relations to other MOs. The only valid MOs where relations can exist are E1Physpathterm, J1Physpathterm, T1Physpathterm, Os155SpiTtp, TU Synchronization Reference, and ManagedObject (for the non-Cello RXI820 MO) MOs. Note that maximum number of relations to these MOs is 8 all together.The synchronization MO is automatically created and cannot be deleted.Note: An external ManagedObject that wishes to be connected to the Synchronization MO must implement the following interface se.ericsson.cello.equipment.SyncReservable!The local distinguished name of this MO is ManagedElement=1,TransportNetwork=1,Synchronization=1.----------------------------------------------------------------------------------
RNC10> acc 793 removeSyncRefResource
=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 793 Synchronization=1 removeSyncRefResource 1
Parameter 1 of 1, syncReference (moRef-ManagedObject): Enter mo LDN: Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=1
>>> Return value = null
=================================================================================================================Total: 1 MOs attempted, 1 MOs actioned
RNC10> acc 793 addSyncRefResource
=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 793 Synchronization=1 addSyncRefResource 2
Parameter 1 of 2, syncReference (moRef-ManagedObject): Enter mo LDN: Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=1
Parameter 2 of 2, syncPriority (long): 3 >>> Return value = null
Finn Magnusson 2008-05-12 rev PA32 48/167
=================================================================================================================Total: 1 MOs attempted, 1 MOs actioned
This command shows a bit more detail on the clock state, but most of the info is the same as what can be seen from the MOsRXI3> nssmpinfo all
$ nssmpinfo all******** Reference Information ******** ET REF in position: SMN= 0, APN= 16 - priority= 1 - synch state= OK - LOSS OF TRACKING= NO (0 || 0) - reference path A state= REF PATH A OK - reference path B state= REF PATH B OK - ref ADM state= ADM UNLOCKED - ref is active= True* ET REF in position: SMN= 0, APN= 7 - priority= 4 - synch state= OK - LOSS OF TRACKING= NO (0 || 0) - reference path A state= REF PATH A UNKNOWN - reference path B state= REF PATH B UNKNOWN - ref ADM state= ADM UNLOCKED - ref is active= False* ET REF in position: SMN= 0, APN= 12 - priority= 3 - synch state= OK - LOSS OF TRACKING= NO (0 || 0) - reference path A state= REF PATH A UNKNOWN - reference path B state= REF PATH B UNKNOWN - ref ADM state= ADM UNLOCKED - ref is active= False* ET REF in position: SMN= 0, APN= 8 - priority= 2 - synch state= OK - LOSS OF TRACKING= NO (0 || 0) - reference path A state= REF PATH A UNKNOWN - reference path B state= REF PATH B UNKNOWN - ref ADM state= ADM UNLOCKED - ref is active= False
******** Alarms Information *******
Finn Magnusson 2008-05-12 rev PA32 49/167
* NSS_SYNCH_LOSS_OF_SYSTEM_CLOCK alarm= OFF* NSS_SYNCH_LOSS_OF_SYSTEM_CLOCK_REDUNDANCY alarm= OFF* NSS_SYNCH_SYSTEM_CLOCK_QUALITY_DEGRADATION alarm= OFF* NSS_SYNCH_SYSTEM_CLOCK_IN_HOLDOVER_MODE alarm= OFF* NSS_SYNCH_LOSS_OF_SYNCH_REF_REDUNDANCY alarm= OFF* NSS_SYNCH_LOSS_OF_TRACKING alarm= OFF* NSS_SYNCH_REF_PATH_HW_FAILURE alarm= OFF* NSS_TU_HW_FAILURE alarm on TU A= OFF* NSS_TU_SYS_CLOCK_PATH_HW_FAILURE alarm on TU A= OFF* NSS_TU_HW_FAILURE alarm on TU B= OFF* NSS_TU_SYS_CLOCK_PATH_HW_FAILURE alarm on TU B= OFF* TU A Dedicated 1.5/2/10 MHz Input alarm= OFF* TU A Dedicated 1PPS Input alarm= OFF* TU B Dedicated 1.5/2/10 MHz Input alarm= OFF* TU B Dedicated 1PPS Input alarm= OFF
******** Clock Information *******Legenda for clock states: WARMUP_MODE = 1 SYNCH1_MODE= 2 SYNCH2_MODE= 3 SYNCH3_MODE= 4 LOCKED_MODE= 5 HOLD_OVER_MODE= 6 FREERUNNING_MODE= 7 LOSS_OF_TRACKING_MODE= 8 FAILURE_MODE= 9 UNKNOWN= 10* TU A Type= TU1* System clock TU A= 5* TU B Type= TU1* System clock TU B= 5******************
* SYCI Selected System Clock Plane= A_THEN_B_PLANE* SCSPI Selected System Clock plane= SYSTEM CLOCK PLANE A$
ATM = a transport technology for sharing the physical media (E1, T1, STM-1, etc) between several users.User data is transported in cells of fixed size of 53 bytes: 5 bytes header + 48 bytes data.Short fixed size of the cells gives cheap hardware based switching and tight control on delay.
ATM Cell structure:- GFC = Generic Flow Control = 4 bits. Not used in CPP.- VPI = Virtual Path Identifier = 8 bits. Possible values: 0 to 255- VCI = Virtual Channel Identifier = 16 bits. Possible values: 32 to 65535 (0 to 31 is reserved).- PTI = Payload Type Indication = 3 bits. Possible values: 0 to 7. To distinguish OAM or idle cells from payload cells. Also used for Early Packet
Discard.- CLP = Cell Loss Priority = 1 bit. Not used in CPP.- HEC = Header Error Control = 8 bits checksum. Used for error detection and error correction in the header bits. Also used by receiver to
synchronise on the cell flow.
VPI P T I
CLP
HEC PAYLOAD VCI GFC
Virtual channels carry the user data and are grouped into virtual pathes.The bitrate and delay of the VP’s and VC’s is specified by the ATM traffic descriptors.
Since ATM cells have fixed size but user data frames can have variable size, an adaption layer is necessary to fit the user data into the ATM cells:- AAL5: for non delay sensitive data contained in long frames, eg signalling and IP. The Aal5 user frames are segmented into 48 bytes fragments and
reassembled at other end- AAL2: for delay sensitive data, eg AMR speech or Iub Frame protocols. Frames from multiple Aal2 users can be multiplexed into one ATM VCC. - AAL0: Aal0 does not perform any adaptation. It is used in Ericsson networks to carry the node sync on Iub.- AAL1: to carry TDM traffic over ATM.
Finn Magnusson 2008-05-12 rev PA32 51/167
VCI=32
VPI=2
VPI=1
VCI=33
VCI=32
VCI=34
VCI=33
Cable/Fiber
AtmPort
CP = the point below the layerCEP = the point above the layer.VPL/VCL = Virtual Path Link / Virtual Channel Link = Link between two Connection Points (CP)VPC/VCC = Virtual Path Connection / Virtual Channel Connection = Connection between two Connection End Points (CEP)
VCL and VPL Termination Points (VclTp, VplTp) are found in every node.VPC Termination Points (VpcTp) are found in every node since VP cross connect is not supported in CPP.VCC Termination Points are only found in the nodes where the Aal layer terminates.
Defined on VP and VC level. Specified by:- quality of service: 1, 2, 3, 4- service category: CBR, UBR, UBR+
RXI4> mom atmqos
##################################################################################Enum Values##################################################################################AtmQos 1:CLASS_ONE, 2:CLASS_TWO, 3:CLASS_THREE, 4:CLASS_FOUR----------------------------------------------------------------------------------ATM's Quality of Service classes.The ATM layer system provides four QoS classes, numbered 1 to 4, where CLASS_ONE gives the best QoS in regards to Cell Loss Ratio <CLR> and Cell Delay Variation <CDV> and CLASS_FOUR doesn't give any QoS guarantees. CLASS_ONE and CLASS_TWO are the only classes applicable for real time traffic. - CLASS_ONE: CDV < 1 ms (milliseconds), CLR < 10e-8. Typically used by timing unit. - CLASS_TWO: CDV < 1 ms, CLR < 10e-7. Typically used for speech (Aal2). - CLASS_THREE: CLR < 10e-5. Typically used for signalling. - CLASS_FOUR: Typically used for IP, eg. OAM traffic.**********************************************************************************
RXI4> mom servicecat
##################################################################################Enum Values##################################################################################ServiceCategory 1:SERVICE_CATEGORY_CBR, 2:SERVICE_CATEGORY_UBR, 3:SERVICE_CATEGORY_UBR_PLUS---------------------------------------------------------------------------------- - SERVICE_CATEGORY_CBR: Service category Constant Bit rate, CBR.
Finn Magnusson 2008-05-12 rev PA32 56/167
- SERVICE_CATEGORY_UBR: Service category Unspecified Bit rate, UBR. - SERVICE_CATEGORY_UBR_PLUS: Service category Unspecified Bit rate+, UBR+. UBR+ guarantees a certain bandwidth. If higher bandwidth is used it will be handled as UBR. **********************************************************************************
Enter a second argument in the mom command for more detailed description
//USED BY nodesync AND VP’SRXI4> get AtmTrafficDescriptor=C1P7000
>>> reservedBy = TransportNetwork=1,AtmPort=MS-6-1,VplTp=1,VpcTp=1,VclTp=vc50serviceCategory 3 (SERVICE_CATEGORY_UBR_PLUS)userLabel =================================================================================================================Total: 1 MOs
//used by o&mRXI4> get AtmTrafficDescriptor=U4
=================================================================================================================2131 TransportNetwork=1,AtmTrafficDescriptor=U4=================================================================================================================AtmTrafficDescriptorId U4egressAtmMcr 0 //MCR not applicable, no garanteed minimum cell rate, best effortegressAtmPcr 0 //PCR not applicable, Peak Cell Rate is the maximum availableegressAtmQos 4 (CLASS_FOUR)ingressAtmMcr 0ingressAtmPcr 0ingressAtmQos 4 (CLASS_FOUR)packetDiscard true //Early Packet Discard can be used as long as only Aal5TpVccTps are using these VC’sreservedBy [17] = >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-1-ima1,VplTp=vp1,VpcTp=1,VclTp=vc47 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-1-ima2,VplTp=vp1,VpcTp=1,VclTp=vc47 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-2-ima1,VplTp=vp1,VpcTp=1,VclTp=vc47 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-2-ima2,VplTp=vp1,VpcTp=1,VclTp=vc47 >>> reservedBy = TransportNetwork=1,AtmPort=MS-8-1-1-1,VplTp=vp1,VpcTp=1,VclTp=vc46 >>> reservedBy = TransportNetwork=1,AtmPort=MS-8-1-1-5,VplTp=vp1,VpcTp=1,VclTp=vc46 >>> reservedBy = TransportNetwork=1,AtmPort=MS-8-1-2-1,VplTp=vp1,VpcTp=1,VclTp=vc46 >>> reservedBy = TransportNetwork=1,AtmPort=MS-8-1-2-9,VplTp=vp1,VpcTp=1,VclTp=vc46 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-1-ima3,VplTp=vp1,VpcTp=1,VclTp=vc47 >>> reservedBy = TransportNetwork=1,AtmPort=MS-8-1-1-3,VplTp=vp1,VpcTp=1,VclTp=vc46 >>> reservedBy = TransportNetwork=1,AtmPort=MS-25-2,VplTp=vp2,VpcTp=1,VclTp=vc40 >>> reservedBy = TransportNetwork=1,AtmPort=MS-25-1,VplTp=vp2,VpcTp=1,VclTp=vc47 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-1-ima5,VplTp=vp1,VpcTp=1,VclTp=vc32 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-1-ima5,VplTp=vp1,VpcTp=1,VclTp=vc40 >>> reservedBy = TransportNetwork=1,AtmPort=MS-27-1,VplTp=vp8,VpcTp=1,VclTp=vc40 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-1-ima4,VplTp=vp1,VpcTp=1,VclTp=vc32 >>> reservedBy = TransportNetwork=1,AtmPort=MS-12-1-1-ima4,VplTp=vp1,VpcTp=1,VclTp=vc40serviceCategory 2 (SERVICE_CATEGORY_UBR)userLabel =================================================================================================================Total: 1 MOs
RXI4> mom . packetdisc
Finn Magnusson 2008-05-12 rev PA32 59/167
##################################################################################################MO Class Attribute Type Flags##################################################################################################AtmTrafficDescriptor packetDiscard boolean restricted,noNotification--------------------------------------------------------------------------------------------------PacketDiscard - Controls the functions Early Packet Discard (EPD) and Partial Packet Discard (PPD) used in AAL5 for traffic classes UBR and UBR+. N.B. should never be enabled for non-AAL5 traffic.Default=false **************************************************************************************************
RXI4> hget atmtraffic egress|packet
=================================================================================================================MO egressAtmMcr egressAtmPcr egressAtmQos packetDiscard=================================================================================================================AtmTrafficDescriptor=C1P5 0 5 1 (CLASS_ONE) false //THIS ONE IS FOR NODESYNCH, THEREFORE CLASS 1 AtmTrafficDescriptor=C1P70000 0 70000 1 (CLASS_ONE) false //THIS ONE IS FOR VPLTP, THEREFORE CLASS 1 AtmTrafficDescriptor=C1P27500 0 27500 1 (CLASS_ONE) false //IDEM AtmTrafficDescriptor=C2P3000 0 3000 2 (CLASS_TWO) false //Aal2 AtmTrafficDescriptor=C2P6500 0 6500 2 (CLASS_TWO) false //Aal2 AtmTrafficDescriptor=C2P12000 0 12000 2 (CLASS_TWO) false //Aal2 AtmTrafficDescriptor=U3P20000M1600 1600 20000 3 (CLASS_THREE) true //THIS ONE IS FOR AAL5, THEREFORE EPD=TRUE AtmTrafficDescriptor=U3P1000M80 80 1000 3 (CLASS_THREE) true //IDEM AtmTrafficDescriptor=U4 0 0 4 (CLASS_FOUR) true //IDEMAtmTrafficDescriptor=U42 0 0 4 (CLASS_FOUR) false //THIS ONE IS FOR AAL2, THEREFORE EPD=FALSE=================================================================================================================Total: 20 MOs
- The bandwidth reserved by a VP is locked and cannot be used by VC’s located in other VP’s, even if its bandwidth is not fully used.
- The bandwidth reserved for a VC is not locked and can be used by other VC’s within the same VP if unused. ====> Therefore it is more bandwidth efficient to put many VC’s in the same VP so that the bandwidth is pooled.
Finn Magnusson 2008-05-12 rev PA32 60/167
VP-1
VC-11
VC-12
VC-13
VP-2
VC-21
VC-22
VC-23
AtmPort
VP-1
VC-11
VC-12
VC-13
VC-21
VC-22
VC-23
AtmPort
- Until CPP5.1, VP must use CBR traffic descriptor. - From CPP5.1, it is possible to have one VP using UBR+, per AtmPort.This is useful for IMA, it allows for the ImaGroup to still work even if some ImaLinks go down.
Example:This ImaGroup contains two ImaLinks and one VP occupies the AtmPort. The VP is using UBR+ with minimum cell rate equal to the bandwidth of one ImaLink only.When all ImaLinks are working the VP “expands” to use the full bandwidth provided by the ImaLinks.When some ImaLinks are not working the VP “contracts” to use the minimum bandwidth specified in its traffic descriptor.
Finn Magnusson 2008-05-12 rev PA32 61/167
ImaGroup with requiredNumberOfLinks=1 and activeLinks=2
(The attribute requiredNumberOfLinks defines how many physical links must be up to enable the CBR PeakCellRate plus UBR+ MinimumCellRate component of the VP(s) to be guaranteed. Previously this meant that setting requiredNumberOfLinks lower than the physical ports in the ImaGroup meant the bandwidth of extra links could not be used because only CBR VP was supported.Since CPP5.1 it is possible to create UBR/UBR+ VPs. This means that the requiredNumberOfLinks can be reduced to satisify the CBR PCR plus UBR+ MCR. The UBR/UBR+ VP can then utilize the rest of the bandwidth available. If one physical link goes down, the system automatically reconfigures the available bandwidth available for the UBR/UBR+ VP. Note: A UBR/UBR+ VP cannot use the (unused) allocated bandwidth of a CBR VP like in the case with VCs. Therefore it is recommended to use one UBR/UBR+ VP with CBR VCs for Class A traffic in order to get maximum utilization of the “fat pipe”.)
//VP’s are using a CBR CLASS 1 traffic descriptor//UBR+ VP’s are supported from CPP5.1
OAM cells are ATM cells with a special value in the PTI field of the ATM header. They are used for O&M of the VP/VC’s.OAM F4 is for management of the VP’s and F5 is for management of the VC’s.Following features are provided by OAM:- Automatic Continuity check on VPC/VCC, to detect “breaks” on the VPC/VCC. - Alarm surveillance on the VccTp/VpcTp (AIS, RDI, etc)- Manual Loopback test, on VP/VC segment, or end-to-end. (only end-to-end loopback test supported in CPP).
ContinuityCheck set to true means that an OAM cell is sent every second to check continuity across the VCC/VPC.If there is a “break” in the VPC/VCC, the VccTp/VpcTp MO becomes disabled and an alarm is raised.
Which alarm is raised depends on the alarmReport attribute. Example:
RNC11> get Aal2PathVccTp=Iub-6-1 continu
=================================================================================================================MO Attribute Value=================================================================================================================Aal2PathVccTp=Iub-6-1 continuityCheck true=================================================================================================================Total: 1 MOs
RNC11> get Aal2PathVccTp=Iub-6-1 alarm
=================================================================================================================MO Attribute Value=================================================================================================================Aal2PathVccTp=Iub-6-1 alarmReport 2 (ALARM_LOC)=================================================================================================================Total: 1 MOs
RNC11> al================================================================================================Sever Specific Problem Cause Mo-Reference================================================================================================Min VC ete Loss of Connectivity unavailable Aal2PathVccTp=Iub-6-1Min VC ete Loss of Connectivity unavailable Aal2PathVccTp=Iub-6-2
RNC11> st Aal2PathVccTp=Iub-6-1
Finn Magnusson 2008-05-12 rev PA32 64/167
===================================================================================Proxy Adm State Op. State MO=================================================================================== 3026 1 (UNLOCKED) 0 (DISABLED) TransportNetwork=1,Aal2PathVccTp=Iub-6-1===================================================================================Total: 1 MOs
If ContinuityCheck is false then no alarms is raised upon loss of continuity and the VccTp/VpcTp MO will always be enabled as long as the physical layer is up.The recommendation is to have:- continuityCheck=false on VpcTp since VP’s are not cross-connected in CPP nodes.- continuityCheck=false on Aal5TpVccTp since the layer above (e.g. IpOverAtm, Nbap, Mtp3b, etc.) is already checking VCC continuity so we don’t
need duplicate alarms .- continuityCheck=true on Aal2TpVccTp/Aal0TpVccTp since there is no layer above that checks VCC continuity.Note: CONTINUITYCHECK MUST HAVE THE SAME SETTING ON BOTH SIDES!
//The Aal5TpVccTp MO represents an Aal5 TerminationPoint and its corresponding VC CEP, ie. an Aal5Tp and its corresponding VccTp.//It contains attributes both for the Aal5 layer and the VCC.
Alarm report for the Virtual path connection termination point.RDI - Remote defect indicationLOC - Loss of continuityAIS - Alarm indication signal - ALARM_LOC: For alarms of type Loss of continuity. - ALARM_LOC_RDI: For alarms of type Loss of continuity and Remote defect indication. - ALARM_AIS_LOC: For alarms of type Alarm indication signal and Loss of continuity. - ALARM_AIS_RDI_LOC: For alarms of type Alarm indication signal, Remote defect indication and Loss of continuity.**********************************************************************************
Loopback Test can be performed on VclTp or VpcTp. Usually it is done on VclTp MO.Only end-to-end loopback test is supported in CPP but it is still possible to check individual segments by choosing the point where the test is performed.The VclTp sends an OAM cell to the remote end who shall change some bits in the payload of the OAM cell and send it back. - If there is no reply within 5 seconds then it means that some segment of the VCC is broken, either at the physical layer or in one of the VC cross-
connects.- If the OAM cell comes back with the exact same payload as when it was sent then it means that there is a physical loopback somewhere on the line.
Finn Magnusson 2008-05-12 rev PA32 67/167
RNC RXI (VC cross-connect) RBS CEP
CP CP CEP
Test continuity on the VCC
Test continuity on the VCC Test continuity on each segment
=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 14 AtmPort=MS-6-2,VplTp=vp2,VpcTp=1,VclTp=vc12532 eteLoopBack 0 >>> Return value = false
37 AtmPort=MS-26-1,VplTp=vp2,VpcTp=1,VclTp=vc68 eteLoopBack 0 >>> Return value = true
Finn Magnusson 2008-05-12 rev PA32 68/167
LIMITATIONS on continuityCheck and eteloopback:
1) Not supported by some other vendor’s equipment
2) Fooled by physical loop. Use loopbackdetection on AtmPort in order to detect physical loops.(Note: loopback detection is not supported on certain ET boards like ET-M4)
PM counters on VclTp/VplTp show transmitted/received cells. PM counters give an indication of whether there is some traffic going on the VC/VP. No traffic can mean that there is a loss of continuity on the VPC/VCC but not necessarily: it could just be that no user data is being sent at the moment.Traffic does not necessary mean that there is continuity on the VPC/VCC. It could be that the physical interface has been loopedback in which case the received/transmitted cells will be incrementing at the same rate.
Look for VclTp’s that are transmitting but not receiving.Could indicate a loss of continuity --> Useful in case the other vendor equipment not suppporting loopback test or continuity check
RNC10> uv pm_wait
Finn Magnusson 2008-05-12 rev PA32 69/167
pm_wait = 25 //the interval of 25 seconds can be changed here RXI1> pdiff vcltp transmitted !^0
Logging to file: /home/eanzmagn/moshell_logfiles/logs_moshell/tempfiles/20070110-220418_17503/boLog17503.................................................waiting 20 seconds before next check............................Log close: /home/eanzmagn/moshell_logfiles/logs_moshell/tempfiles/20070110-220418_17503/boLog17503=================================================================================================================MO Counter DiffValue=================================================================================================================AtmPort=MS-22-2,VplTp=vp1,VpcTp=1,VclTp=vc45 pmTransmittedAtmCells 47AtmPort=MS-22-2,VplTp=vp1,VpcTp=1,VclTp=vc44 pmTransmittedAtmCells 46...<cut>...AtmPort=MS-17-1,VplTp=vp1,VpcTp=1,VclTp=vc44 pmTransmittedAtmCells 48AtmPort=MS-17-1,VplTp=vp1,VpcTp=1,VclTp=vc45 pmTransmittedAtmCells 48AtmPort=MS-17-1,VplTp=vp1,VpcTp=1,VclTp=vc39 pmTransmittedAtmCells 24AtmPort=MS-17-1,VplTp=vp1,VpcTp=1,VclTp=vc40 pmTransmittedAtmCells 24=================================================================================================================Total: 473 MOs
=================================================================================================================Total: 27 MOs
Added 27 MOs to group: pdiff_group
Perform loopback test on the VCs that are transmitting but not receiving
RXI1> acc pdiff_group eteloopback
=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 175 AtmPort=MS-26-2,VplTp=vp2,VpcTp=1,VclTp=vc6233 eteLoopBack 0 >>> Return value = false
182 AtmPort=MS-26-2,VplTp=vp2,VpcTp=1,VclTp=vc21833 eteLoopBack 0 >>> Return value = false
189 AtmPort=MS-26-2,VplTp=vp2,VpcTp=1,VclTp=vc12333 eteLoopBack 0 >>> Return value = false
196 AtmPort=MS-26-2,VplTp=vp2,VpcTp=1,VclTp=vc21633 eteLoopBack 0 >>> Return value = false
203 AtmPort=MS-26-2,VplTp=vp2,VpcTp=1,VclTp=vc9133 eteLoopBack 0 >>> Return value = false
210 AtmPort=MS-26-2,VplTp=vp2,VpcTp=1,VclTp=vc12033 eteLoopBack 0 >>> Return value = false
216 AtmPort=MS-26-2,VplTp=vp2,VpcTp=1,VclTp=vc17033 eteLoopBack 0 >>> Return value = false
300 AtmPort=MS-11-2,VplTp=vp2,VpcTp=1,VclTp=vc12133 eteLoopBack 0 >>> Return value = false
302 AtmPort=MS-11-2,VplTp=vp2,VpcTp=1,VclTp=vc4333 eteLoopBack 0 >>> Return value = false
308 AtmPort=MS-11-2,VplTp=vp2,VpcTp=1,VclTp=vc633 eteLoopBack 0 >>> Return value = false
315 AtmPort=MS-11-2,VplTp=vp2,VpcTp=1,VclTp=vc647 eteLoopBack 0 >>> Return value = false
Finn Magnusson 2008-05-12 rev PA32 71/167
316 AtmPort=MS-11-2,VplTp=vp2,VpcTp=1,VclTp=vc649 eteLoopBack 0 >>> Return value = false
323 AtmPort=MS-11-1,VplTp=vp2,VpcTp=1,VclTp=vc4133 eteLoopBack 0 >>> Return value = false
330 AtmPort=MS-11-1,VplTp=vp2,VpcTp=1,VclTp=vc3033 eteLoopBack 0 >>> Return value = false
337 AtmPort=MS-11-1,VplTp=vp2,VpcTp=1,VclTp=vc5933 eteLoopBack 0 >>> Return value = false
344 AtmPort=MS-11-1,VplTp=vp2,VpcTp=1,VclTp=vc1733 eteLoopBack 0 >>> Return value = false
408 AtmPort=MS-10-2,VplTp=vp2,VpcTp=1,VclTp=vc2533 eteLoopBack 0 >>> Return value = false
415 AtmPort=MS-10-2,VplTp=vp2,VpcTp=1,VclTp=vc2433 eteLoopBack 0 >>> Return value = false
416 AtmPort=MS-10-2,VplTp=vp2,VpcTp=1,VclTp=vc4433 eteLoopBack 0 >>> Return value = false
429 AtmPort=MS-10-1,VplTp=vp2,VpcTp=1,VclTp=vc5133 eteLoopBack 0 >>> Return value = false
577 AtmPort=MS-8-2,VplTp=vp2,VpcTp=1,VclTp=vc646 eteLoopBack 0 >>> Return value = false
578 AtmPort=MS-8-2,VplTp=vp2,VpcTp=1,VclTp=vc648 eteLoopBack 0 >>> Return value = false
644 AtmPort=MS-7-2,VplTp=vp2,VpcTp=1,VclTp=vc23933 eteLoopBack 0 >>> Return value = false
657 AtmPort=MS-7-2,VplTp=vp2,VpcTp=1,VclTp=vc8233 eteLoopBack 0 >>> Return value = false
658 AtmPort=MS-7-2,VplTp=vp2,VpcTp=1,VclTp=vc21333 eteLoopBack 0 >>> Return value = false
671 AtmPort=MS-7-2,VplTp=vp2,VpcTp=1,VclTp=vc5433 eteLoopBack 0 >>> Return value = false
Finn Magnusson 2008-05-12 rev PA32 72/167
678 AtmPort=MS-7-2,VplTp=vp2,VpcTp=1,VclTp=vc21133 eteLoopBack 0 >>> Return value = false
=================================================================================================================Total: 27 MOs attempted, 27 MOs actioned
reservedBy AtmCrossConnection=b287dauserLabel vc37=================================================================================================================Total: 1 MOs
*******************************************************stc[p][r] [<Filter>] [<stateFilter>]*******************************************************This command shows the state and information about atm cross connections.
This command shows the state and information about atm cross connections.The filter allows to only show the rows matching the filter string.The stateFilter allows to only shows the MOs matching the state filter.The first time the command is run, it takes a bit longer because the data has to be fetched from the node before parsing.The following times the command is run, the data is parsed again from the cache, unless the "r" switch is used ("refresh"), in which case, the data is fetched again from the node.The "p" option is to perform a check on the PM counters. In this case, a 0 will be given if the VC is transmitting cells but not receiving.
The first field is the MO id of the AtmCrossConnection.The second field is the state information, consists of five digits: - 1st digit: operationalState of the AtmCrossConnection MO (0=disabled, 1=enabled) - 2nd and 3rd digits: operationalState of the VclTp MOs (A and B side). - 4th and 5th digits: only applicable if "p" option was used. Shows the status of the "pget" on VclTp MOs (A and B side). Set to 0 if the transmittedCells counter has incremented but the receivedCells counter has not incremented within a given time period (by default 25 seconds, can be changed in the uservariable pm_wait): this indicates that there is no response from the remote end.The third and fourth field are the MoId for VclTpA and VclTpB, abbreviated in the following way: AtmPortId/VplTpId/VclTpIdThe fifth and sixth fields are the actual Vpi/Vci value for VclTpA and VclTpB. Can be useful in case the MoId of the VclTp does not match the Vpi/Vci value.The seventh and eigth fields are the MoId for the traffic descriptor of VclTpA and VclTpB.The last field is the userLabel of the AtmCrossConnection MO.
3.6 AtmPort Bandwidth usage
3.6.1 AtmPort without IMA
Method 1
RNC10> fro atmport=ms-26-1
=================================================================================================================MO FroName FroId=================================================================================================================AtmPort=MS-26-1 atmPortFroId 4=================================================================================================================Total: 1 MOs
(alternatively:)
RNC10> fget atmport=ms-26-1 atmportfroid
=================================================================================================================MO Attribute Value
Finn Magnusson 2008-05-12 rev PA32 77/167
=================================================================================================================AtmPort=MS-26-1 atmportfroid 4=================================================================================================================Total: 1 MOs
RNC10> aet_atmmp etatmportfro 4
$ aet_atmmp etatmportfro 4******* AET state info - data for an EtAtmPortFROData for EtAtmPortFRO 4 (At address: 0x49DF1DB0)
=================================================================================================================MO Attribute Value=================================================================================================================AtmPort=MS-19-ima1 uses ImaGroup=MS-19-ima1=================================================================================================================Total: 1 MOs
//Available bandwidth = 0.972347 * bandwidth per port * numberOfWorkingLinks = 0.972347 * 4528 * 4 = 17611 cell/s//Or we can use directly the value in table 1.1: available bandwidth = 4 * 4402 = 17608 cell/s
=================================================================================================================MO Attribute Value=================================================================================================================AtmPort=MS-19-ima1,VplTp=vp1 atmTrafficDescriptor AtmTrafficDescriptor=C1P17600=================================================================================================================Total: 1 MOs
Finn Magnusson 2008-05-12 rev PA32 81/167
3.7 Overview
RXI3> h stv
*******************************************************stv[b][r] [<Filter>] [<stateFilter>]*******************************************************Purpose: Display state, user, and bandwidth usage for ATM ports and channels....<cut>...
======================================================================================================================VclTp VPI/VCI BwUsage/TraffDesc VU M User
Aal2 consists of :- user plane connections: one or more aal2 connection is established for the duration of a call. up to 248 simultaneous connections can be multiplexed
in one Aal2Path. Each Aal2Path is carried by an ATM VC. - control plane connections: the Aal2 Signaling protocol (Q.Aaal2 / Q.2630) is carried on a separate ATM VC than the Aal2Pathes. It is used for
establishing and releasing the aal2 connections on the user plane. Every node in the Aal2 network has a unique Aal2 address which consists of a string of integers (maximum size is 15 digits).
Finn Magnusson 2008-05-12 rev PA32 85/167
Aal2 User plane frame structure:User data frames are segmented and put into CPS packets of up to 45 bytes and given a Channel Identity (CID=8 to 255) and a length indicator (LI=1 to 45 bytes). The user data frames are then reassembled at the other end.CPS=Common Part SublayerSSCS= Service Specific Convergence Sublayer
Finn Magnusson 2008-05-12 rev PA32 86/167
AAL2 SSSAR-SDU
AAL2
SegmentationReassembly
CPS-SDUAAL2
CPS-SDUAAL2
CPS-SDUAAL2
CPS-SDU
CID UUI CPS-INFO LI HEC
CPS-Packet Header (3 octets)
CPS-Packet (4..48 octets)
CPS-Packet Payload (1..45)
OSF P
S t art
CPS-PDU (48 octets)
CPS-PDU Payload (47 octets)
S N CPS-packets in an endless stream
Field
PAD ATM header
4.2 MO mapping
RNC10> momt ....Aal2Sp[0-1] Aal2Ap[0-850] Aal2PathDistributionUnit[0-28] Aal2PathVccTp[0-2000] Aal2RoutingCase[0-900] Aal2QosCodePointProfile[0-20] Aal2QosProfile[0-20] - The Aal2Sp MO (Aal2 Signaling Point) is used to store the node’s aal2 address, in the attribute a2ea (only one Aal2Sp MO in the whole node).
Finn Magnusson 2008-05-12 rev PA32 87/167
- The Aal2Ap MO (Aal2 Access Point) represents the signaling association to an adjacent node (one Aal2Ap per adjacent node).- The Aal2PathVccTp MO represents an Aal2 path. An aal2 path is used to carry user plane connections towards an adjacent node. Up to 248
simultaneous connections can be multiplexed in an aal2 path. - The Aal2PathDistributionUnit MO is used to tie a number of Aal2PathVccTp’s with a specific Aal2Ap. - The Aal2RoutingCase MOs are used to point out which Aal2 addresses can be reached from which Aal2Ap’s.- The Aal2QosCodePointProfile and Aal2QosProfile are used for Aal2 Quality Of Service definitions. Aal2 QoS will be described further down.
4.2.1 Aal2 connections without aal2 transit node, Nb interface
In this example, every MGW is adjacent to every other MGW and there are no aal2 transit nodes.
Note: - Each Aal2 Path within an Aal2Ap must have a unique path id. The path id values can however be reused in other Aal2Ap’s. The path id must be identical on both sides of the path.
Finn Magnusson 2008-05-12 rev PA32 88/167
MGW1
Aal2Sp=1 (a2ea=231)
Aal2Ap=mgw2
Aal2PathDistributionUnit=1
Aal2RoutingCase=mgw2 (numberDirection=232)
Aal2PathVccTp=21 (pathId=1)
Aal2PathVccTp=22 (pathId=2)
Aal2Ap=mgw3
Aal2PathDistributionUnit=1
Aal2RoutingCase=mgw3 (numberDirection=233)
Aal2PathVccTp=31 (pathId=1)
Aal2PathVccTp=32 (pathId=2)
MGW2
Aal2Sp=1 (a2ea=232)
Aal2Ap=mgw1
Aal2PathDistributionUnit=1
Aal2RoutingCase=mgw1 (numberDirection=231)
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
MGW3
Aal2Sp=1 (a2ea=233)
Aal2Ap=mgw1
Aal2PathDistributionUnit=1
Aal2RoutingCase=mgw1 (numberDirection=231)
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
Control plane (Q.AAL2)
User plane (AAL2)
Finn Magnusson 2008-05-12 rev PA32 89/167
4.2.2 Aal2 connections without aal2 transit node, Iub interface
RNC1
Aal2Sp=1 (a2ea=331)
Aal2Ap=rbs1
Aal2PathDistributionUnit=1
Aal2RoutingCase=rbs1 (numberDirection=33201)
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
ATM CrossConnect RBS1
Aal2Sp=1 (a2ea=33201)
Aal2Ap=rnc1
Aal2PathDistributionUnit=1
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
RBS2
Aal2Sp=1 (a2ea=33202)
Aal2Ap=rnc1
Aal2PathDistributionUnit=1
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
Aal2Ap=rbs2
Aal2PathDistributionUnit=1
Aal2RoutingCase=rbs2 (numberDirection=33202)
Aal2PathVccTp=21 (pathId=1)
Aal2PathVccTp=22 (pathId=2)
Finn Magnusson 2008-05-12 rev PA32 90/167
4.2.3 Aal2 connections through aal2 transit node, Iub interface
In this example, the user plane connections are terminated in RNC and RBS. RXI is only acting as an aal2 transit node (performing aal2 switching). This allows to reduce the number of Aal2 terminations in the RNC, thus saving resources and bandwidth on the RNC-RXI interface.
Note: - An Aal2RoutingCase must be connected to an Aal2Ap in case the node needs to establish outgoing aal2 connections to that adjacent node. If only incoming connections will be received in that Aal2Ap, then no RoutingCase is needed.
Finn Magnusson 2008-05-12 rev PA32 91/167
RNC1
Aal2Sp=1 (a2ea=331)
Aal2Ap=rxi1
Aal2PathDistributionUnit=1
Aal2RoutingCase=rxi1 (numberDirection=332)
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
RXI1
Aal2Sp=1 (a2ea=332)
Aal2Ap=rnc1
Aal2PathDistributionUnit=1
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
Control plane (Q.AAL2)
User plane (AAL2)
Aal2Ap=rbs1
Aal2PathDistributionUnit=1
Aal2PathVccTp=101 (pathId=1)
Aal2RoutingCase=rbs1 (numberDirection=33201)
Aal2Ap=rbs2
Aal2PathDistributionUnit=1
Aal2PathVccTp=201 (pathId=1)
Aal2RoutingCase=rbs2 (numberDirection=33202)
Aal2PathVccTp=102 (pathId=2)
Aal2PathVccTp=202 (pathId=2)
RBS1
Aal2Sp=1 (a2ea=33201)
Aal2Ap=rxi1
Aal2PathDistributionUnit=1
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
RBS2
Aal2Sp=1 (a2ea=33202)
Aal2Ap=rxi1
Aal2PathDistributionUnit=1
Aal2PathVccTp=11 (pathId=1)
Aal2PathVccTp=12 (pathId=2)
Finn Magnusson 2008-05-12 rev PA32 92/167
4.3 Connection points and connection end points
RNC RBS
RXI
VclTp
VpcTp
VplTp
VclTp
Aal2PathVccTp
VpcTp
VplTp
VclTp
VpcTp
VplTp
VclTp
VpcTp
VplTp
VCC
VCL
VPC
VCL
VPC
VPL VPL
AtmPort AtmPort AtmPort AtmPort
VC CEP
VC CEP
VC CP
VC CP
VC CP
VC CP
Aal2PathVccTp Aal2PathVccTp
AAL2 PATH
AAL2 CP
AAL2 CP
AAL2 PATH
AAL2 CP
AAL2 CP
USER (Eg. Iu/Iub Frame Protocol)
USER (Eg. Iu/Iub Frame Protocol)
Aal2PathVccTp
VC CEP
VC CEP
AAL2 CONNECTION AAL2 CEP
AAL2 CEP
4.4 Underlying transport layer
- On Iu/Iur/Nb, Q.Aal2 is carried by MTP3 or M3UA. - On Iub, Q.Aal2 is carried by UniSaal
Each aal2 connection can be connected to a quality of service levelCPP supports 4 different quality of service on Aal2:- class A: high priority, low delay. Used for speech, video streaming, etc.- class B: medium priority, medium delay. Used for interactive packet data.- class C: lower priority, no guarantee on the delay. Used for HSDPA.- class D: lower priority. Used for EUL.
Default settings (configurable):Class Node
DelayUpper Boundary ofProbability for Delay
Upper Boundary ofProbability for Loss
A 10 ms 0.05% 0.05%B 20 ms 0.05% 0.05%C 25 ms 100% 100%D 50 ms 100% 100%
Different types of calls will use different Aal2 QoS for the aal2 connection.
In RNC, the relationship between the Radio Access Bearer and the Aal2 Connection QoS is defined in MO data:
Relation between AAL2 QoS and RAB/RRC part requested, for Iub Interface
//The UeRc MOs model the various radio connection configurations available.//This includes the signalling (UeRcRrc) and RAB part (UeRcRab) which are children of the UeRc MO.//Each of these parts can have a different AAL2 QoS, see below.
It is then possible to create Aal2 Pathes with different quality of Service and map them to VC’s with different bitrates:
Finn Magnusson 2008-05-12 rev PA32 98/167
Speech/Video
CBR VC
Aal2 Path Class A
Packet Data
UBR+ VC
Aal2 Path Class B
It is also possible to use Aal2Pathes that will support several quality of service. This gives the most efficient use of the bandwidth. In this case, the VC will have different queues for each Aal2 quality of service. The class A connections will be prioritised over the class B connections. This method is more bandwidth efficient than the method above but requires newer ET hardware: ET-MC1, ET-MC41, ET-MF4, ET-M3 (ie. ET-M4 and ET-M1 do not support Aal2 quality of service separation within the same Aal2 Path). Speech/Video
Aal2 Path Class A and B
Packet Data
UBR+ VC
//This Aal2Path is configured to handle Class A only//The QoS of Class A has been configured for a guaranteed delay of 10ms and probability of delay exceeding 10ms of 0.05%//It is using a CBR VC with PCR 5900 cell/s
##################################################################################Struct StructMember Type##################################################################################QoSProfileClassA boundOnNodeDelay long----------------------------------------------------------------------------------The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. Unit is micro seconds.Range: 0 to 10000, Default=5000 **********************************************************************************QoSProfileClassA boundOnProbOfDelay long----------------------------------------------------------------------------------Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". Unit is 1/1000000000.Range: 0 to 1000000000, Default=500000 **********************************************************************************QoSProfileClassA boundOnProbOfLoss long----------------------------------------------------------------------------------Represents the upper bound of the cell loss probability in the current node. Unit is 1/1000000000.Range: 0 to 1000000000, Default=500000 **********************************************************************************
Finn Magnusson 2008-05-12 rev PA32 101/167
//This Aal2Path is configured for Class C traffic only//The QoS of class C has been configured for best effort, no guarantee (loss and delay probability=100%)//The VC traffic descriptor is UBR for aal2 (same as UBR for aal5 but packetdiscard is disabled)
//This aal2 path is configured for traffic class C and D//Class C and D have the same QoS profile, no guarantee.//The traffic descriptor is UBR+ with MCR 5000 cell/s
AtmPort=MS-25-2-1,VplTp=200,VpcTp=1,VclTp=Iub-261-400 atmTrafficDescriptorId AtmTrafficDescriptor=U3P35000M5000=================================================================================================================Total: 1 MOs
In CPP5, it is possible to have Aal2 Pathes configured for all traffic classes (A, B, C, D) and using UBR+ traffic descriptor.This is more efficient since there is no specific dimensioning to do for each traffic class.Newer hardware is needed to support QoS separation inside the Aal2Path (ET-MF4, ET-MC1, ET-MC41)
Finn Magnusson 2008-05-12 rev PA32 105/167
4.6 Aal2 Signaling
Aal2 signaling is called Q.AAL2 or Q.2630 or ALCAP.
Aal2 Signaling procedures are used for:- setup and release of on-demand aal2 connections - maintenance of the aal2 pathes
Message Request Message Confirm ExplanationEstablish Request (ERQ) Establish Confirm (ECF) Establish an AAL2 connection between two CEPs Release Request (REL) Release Confirm (RLC) Release an AAL2 connection between two CEPs Reset Request (RES) Reset Confirm (RSC) This will reset all connections using the concerned channels. Can be used to reset a single
channel, all channels on an AAL2 path, all channels on all paths belonging to an AAL2 APBlock Request (BLO) Block Confirm (BLC) Prevent any more AAL2 connections being setup on this pathUnblock Request (UBL) Unblock Confirm (UBC) Path can only be unblocked by node which blocked the pathConfusion (CFN) N/A Indicates that an adjacent AAL2 node does not support a previously sent parameter or message
Example: setting up a radio link and its associated aal2 connection. (Note: when IP is used instead of ATM, TLA=ip-address and B-ID=UDP-port. No need for ALCAP)
Originating e.g. SRNC
RL Setup Req
RL Setup Resp (TLA; B-ID)
Q.2630: ERQ (A2EA; SUGR;PathID;CID;PathType)
Q.2630: ECF
TLA = A2EA
B-ID = SUGR
Terminating e.g. RBS
Nbap
Alcap
Finn Magnusson 2008-05-12 rev PA32 106/167
Trace taken with “te e bus_send bus_receive NBAP” and “te e bus_send bus_receive Ans_aal2ap_proc”
Rnc requests a radio link to be set up in RBS [00:41:39.084] <<---<< (NBAP) RadioLinkSetupRequestFDD (transID=12L) (UE:3) (RNC.CCID=0) (UL-SC=14451073) (DLsf128) (dCH-ID=31) (rL-ID=0) (C-ID=13) (first-RLS)
Rbs confirms that the resource has been allocated and returns its Aal2 address and the binding ID for the aal2 CEP[00:41:39.092] >>--->> (NBAP) RadioLinkSetupResponseFDD (transID=12L) (UE:3) (RNC.CCID=3) (RBS.CCID=1) (rL-ID=0) (RL-SetID=0) (dCH-ID=31) (bindID=0x07C00136) (addr=614183604142171)
Here we can see the aal2 address of the RBS RBS1> get aal2sp=1
=================================================================================================================198 TransportNetwork=1,Aal2Sp=1=================================================================================================================Aal2SpId 1a2ea 614183604142171userLabel =================================================================================================================Total: 1 MOs
Rnc finds an Aal2RoutingCase whose numberDirection corresponds to this Aal2 address:
RNC> get routingcase numberdir 614183604142171
=================================================================================================================MO Attribute Value=================================================================================================================Aal2RoutingCase=330001321 numberDirection 614183604142171=================================================================================================================Total: 1 MOs
From the corresponding Aal2 Access Point, RNC is able to choose a suitable Aal2 Path and CID for the connection
Two pathes belong to this Aal2Ap, one for Aal2 QoS Class A/B (uses a CBR class 2 VC) and one for Class C (uses a UBR class 4 VC).The Aal2 Path with the most appropriate QoS and bandwidth for the call will be selected.If several Aal2 Path have the same QoS/bandwidth, they are selected in round robin.
RNC> get Aal2PathVccTp=b330001321a qosavailableprofiles|pathid
Rnc sets up the Aal2 connection, uniquely identified by its path Id and CID.The SUGR field is used to indicate which CEP shall use this Aal2 Connection, the SUGR matches the binding ID that was given by the RBS. The message also contains the Quality Of Service indicator for the connection.[00:41:39.092] <<---<< (Q.2630) ERQ (DSAI=00000000) (OSASID=ED00900A) (PthId=1) (ChId=12) (NSEA=614183604142171) (maxBRf=4.8k) (avgBRf=1.0k) (SUGR=0x7C00136)[00:41:39.096] >>--->> (Q.2630) ECF (DSAI=ED00900A) (OSASID=C03E8701)
The ERQ message also contains information about the Aal2 Quality of Service to be used for this connection:[2007-01-24 20:41:41.784] Ans_aal2ap_proc outgoing.c:567 BUS SEND:Q.2630 ERQ to be sent0000 00 00 00 00 05 33 06 11 04 F6 0A 4D 01 02 11 05 '.....3.....M....'0010 00 00 02 E3 13 04 11 14 45 90 15 20 00 43 01 00 '........E.. .C..'0020 7F 00 00 00 00 00 00 00 00 00 00 00 05 11 0C 04 '................'0030 14 04 21 04 14 04 21 2D 2D 2A 2B 07 11 04 2F C1 '..!...!--*+.../.'0040 16 B0 10 54 01 80 0C 11 07 00 00 A7 00 00 A9 00 '...T............'$ ...<cut>.....--- 10 PT Path Type (Q.2630 Para 7.3.14) 54 Message Compatibility 01 Length Indicator (hex) 80 128 (dec) Reserved for network specific assignment---...<cut>.....
Here we can see that PT=128 corresponds to quality of service A.
RNC> get aal2ap=b330001321$ code
=================================================================================================================MO Attribute Value=================================================================================================================Aal2Sp=1,Aal2Ap=b330001321 aal2QoSCodePointProfileId Aal2QosCodePointProfile=1 =================================================================================================================Total: 1 MOs
All Aal2Ap MOs should have an Aal2CodePointProfile, otherwise they will always use the default value PT=128 to setup aal2 connections, which means that there will be no aal2 quality of service separation.It is very important that two adjacent Aal2 nodes use the same QoS coding scheme.
RNC2> set aal2ap=b2060073 aal2QoSCodePointProfileId Aal2QosCodePointProfile=1
============================================================================================================ Id MO aal2QoSCodePointProfileId Result============================================================================================================ 1996 Aal2Sp=1,Aal2Ap=b2060073 1620 >>> Set.============================================================================================================Total: 1 MOs attempted, 1 MOs set
userLabel b330001321a2vclTpId AtmPort=MS-16-ima8,VplTp=vp1,VpcTp=vp1,VclTp=vc50=================================================================================================================Total: 2 MOs
- PathOwner=true means that the CID for each connection are selected from 8 to 255- PathOwner=false means that the CID values are selected from 255 to 8.- This is useful on links where both sides can setup aal2 connections, it reduces the risk of CID collisions, eg on Iur interface or MGW-MGW
interfaces. - For Iu/Iub interface, the pathOwner is not relevant since it is always RNC who sets up Aal2 Connections towards Core Network and RBS.
RNC A (true)
RNC B (false)
RNS B
RNS A
UE 1
UE 2
Cid 23
Cid 22
Cid 24
Cid 23
4.8 Fault Management
4.8.1 ContinuityCheck
- Continuitycheck=true means that the MO will go disabled and will raise an alarm if there is breakage somewhere on the Aal2 Path. If no Aal2 traffic is received during 3½ seconds the alarm is raised. When there is no Aal2 traffic, a test cell is sent every second.
Finn Magnusson 2008-05-12 rev PA32 112/167
- If continuitycheck=false and there is loss of continuity, this is not shown on the MO and the node will still try to use this Aal2Path to setup connections and of course will fail, causing dropped calls etc.
- ContinuityCheck setting must be the same on both sides of the path !!!- The alarm(s) that are raised upon loss of continuity can be specified in the alarmReport attribute.- It is very important to set continuitycheck to the same value on both sides of the Aal2Path. If one side has continuitycheck and not the other, the
Aal2Path will be disabled on the side that has continuitycheck active.- It is highly recommended to activate continuitycheck on all Aal2PathVccTp MOs across the network.
##################################################################################Enum Values##################################################################################AlarmReport 2:ALARM_LOC, 3:ALARM_LOC_RDI, 6:ALARM_AIS_LOC, 7:ALARM_AIS_RDI_LOC----------------------------------------------------------------------------------Alarm report for the Virtual path connection termination point.RDI - Remote defect indicationLOC - Loss of continuityAIS - Alarm indication signal
Finn Magnusson 2008-05-12 rev PA32 113/167
- ALARM_LOC: For alarms of type Loss of continuity. - ALARM_LOC_RDI: For alarms of type Loss of continuity and Remote defect indication. - ALARM_AIS_LOC: For alarms of type Alarm indication signal and Loss of continuity. - ALARM_AIS_RDI_LOC: For alarms of type Alarm indication signal, Remote defect indication and Loss of continuity.**********************************************************************************
4.8.2 RemoteBlockingState
For the Aal2 Path to be up, the other side must also be up, this can be checked in the remoteBlockingState attribute.
Trace bus_send bus_receive on Ans_aal2ap_proc on following boards: - MGW: board group “aal2ap”
Finn Magnusson 2008-05-12 rev PA32 115/167
- RNC: board group “mod” (Iub) and “sccpmp” (Iu/Iur) - RBS: central mp
> lh aal2ap te e bus_send bus_receive Ans_aal2ap_proc> lh aal2ap te log read | decoder.pl | flow.pl....Here we are blocking an Aal2Path[06:34:32.440] <<---<< (Q.2630) BLO (DSAI=00000000) (OSASID=00008833) (PthId=1039) (ChId=0)[06:34:32.448] <<---<< (Q.2630) RES (DSAI=00000000) (OSASID=00008833) (PthId=1039) (ChId=0)[06:34:32.448] >>--->> (Q.2630) BLC (DSAI=00008833)[06:34:32.456] >>--->> (Q.2630) RSC (DSAI=00008833)Here we are deblocking the Aal2Path[06:34:55.296] <<---<< (Q.2630) UBL (DSAI=00000000) (OSASID=00008833) (PthId=1039) (ChId=0)[06:34:55.296] >>--->> (Q.2630) UBC (DSAI=00008833)
Examples of messages in Trace and Error which can help to pinpoint cause of Aal2 setup failures.
This means that the aal2PathId is different on each side of the link:[2005-04-26 15:23:50.468] Ans_aal2cpsrc_proc dispatcher.c:752 INFO:Inconsistent AAL2 network configuration:Received UBL from ApFroid = 1 on unknown PathId = 61
AAL2 REJECTION CAUSES
Explanation for the reject causes: http://utran01.epa.ericsson.se/utranwiki/Aal2RejectCauses
MGW:Trace9 on Ans_aal2ncc2_proc shows Aal2 reject codes, eg:> lh aal2ncc te e trace9 Ans_aal2ncc2_proc> lh aal2ncc te log read.....
AAL2NCCADMAns_aal2nccadm_proc Administrative process managing all fROs belonging to AAL2. Implements client side of all management IFs towards other subsystems
trace1 General information during startuptrace2 Memory consumption. Printed at startuptrace3 CLI (RPU) state changestrace5 Database handing (SQL commands)trace7 Relation handling, detailed DB handing
AAL2ADM Act_aal2Adm_proc Administrative process managing SP resources (CEPs)
trace1 CLI (RPU) state changestrace2 General information during startuptrace7 CLI (RPU) state changes, resource registration
AAL2RH Act_aal2RH_proc Traffical process handling SP resources (CEPs)
AAL2 Reasons for reject during reservation of end point (This is a trace object)trace7 CLI (RPU) state changes, detailed reservation information
AAL2APAns_aal2ap_proc Traffical process handling AAL2 access point(s).
Q.2630 protocol validator(checks syntax etc. on msg)/dispatcher(distributes msg)trace3 Relation handling, signalling status changestrace4 Detailed Q.2630 informationtrace5 Outgoing Q.2630 message with diagnostic information
Ans_aal2cpsrc_dcr_bg_proc Traffical process used by CAC to calculate delays for a requested connection.Ans_aal2cpsrc_bg_proc Traffical process used during startup (configuration & relation handling)
trace2 Memory consumption. Printed at startuptrace7 Status concerning states for AP (signalling) and paths (reset & block)trace8 Time consumption/received signal (thread)trace9 Relation handling
AAL2DISTNCCAns_aal2nccroot_proc Traffical process handling CLI client functionality for AAL2DISTNCCAns_aal2ncc2_proc Traffical process for connection handling.
AAL2REJECTS AAL2 connection setup rejects (This a a trace object)trace1 General information during startuptrace2 CLI (RPU) state changes, memory consumption (printed at startup)trace3 State informationtrace6 PM counterstrace7 Routing table updates, reset handing, connection cleanuptrace8 Hanging connectionstrace9 Connection rejects,
4.9 Performance Management
Aal2Ap counters (can be viewed with pmx, pget, hpget)
pmExisOrigConns Number of connections currently setup originating from the node via the AAL2 AP. Increases when Q.2630 confirm message is received. Decreased with connection is released
pmExisTransConns Number of connections currently setup which transit through the node via the AAL2 AP
pmExistTermConns Number of connections currently setup which terminate in this node via the AAL2 AP
pmSuccInConnsRemote Number of successful incoming connection establishments. In a terminating node it increases when an Establish Request is received. In a transit node it increses when an establish confirm message is receieved
Finn Magnusson 2008-05-12 rev PA32 119/167
pmSuccOutConnsRemote Number of successful outgoing connection establishements
pmUnSuccOutConnsRemote Increments when an establish request message is sent and either a reject is received from the remote side, a reset is received from the remote side, no reply (timeout) occurs, or the signalling link fails
pmUnSuccInConnsRemote Number of unsuccessful establishments of incoming connections caused by external nodes
pmUnSuccInConnsLocal Number of unsuccessful attempts to allocate AAL2 path (CPS) resources caused by CID collisions --> Check pathOwner, could be an issue on Iur or Nb interfaces
pmUnSuccOutConnsLocal Number of unsuccessful attempts to allocate AAL2 path (CPS) resources caused by rejectes in CAC (Connection Admission Control) --> Check trafficdescriptor of Aal2Path, could be a lack of bandwidth
pmUnRecMessages Number of uncognised Q.2630 messages from the AAL2 AP
pmUnRecParams Number of Q.2630 messages received with unrecognised parameters on the AAL2 AP
Example: What bandwidth to choose for an Aal2 path on Iub which will be used for speech calls only.
From the following printout below, we see that each speech call (AMR 12.2 kbps) needs two Aal2 connections. - One for signaling at avgbitrate 1088 b/s (17*64) - One for speech at avgbitrate 9024 b/s (141*64). So total per speech call is 10112 b/s (9024+1088).
So if an AAL2 path is only carrying speech and you have 124 simultaneous calls (248/2), then the bandwidth required for the AAL2 path will be 124*10112=1253888 b/s=1.2 MB/s=2957 cell/s.So the traffic descriptor for the Aal2 path should have a PCR of 2957 cell/s.
UeRc=2 userLabel AMR12200 Speech RAB on DCH=================================================================================================================Total: 1 MOs
##################################################################################################MO Class Attribute Type Flags##################################################################################################UeRcRab egressBitRateAverage long mandatory--------------------------------------------------------------------------------------------------Egress Bit Rate AverageTraffic Descriptor parameter for the AAL2 connection between the RNC and RBS for the RAB leg.0: 0 bit/s1: 64 bit/s..32000: 2048000 bit/s (2048 kbit/s)This attribute may only be changed by Ericsson personnel.Range: 0 to 32000
Note: Why is the speech call using more than 6.1 kb/s (half of 12.2 for DTX): - there is some bandwidth needed for the associated RRC signaling (measurement reports, etc) - there is some RLC/MAC overhead on the payload part as wellIn this case the total is 10.1 kb/s per call instead of 6.1kb/s.
Finn Magnusson 2008-05-12 rev PA32 121/167
5 SS7
5.1 General Concepts
The SS7 protocol suite contains the following protocols:BICC Bearer Independent Call Control protocoBISUP B-ISDN User PartDUP Data User PartISUP ISDN User PartMAP Mobile Application PartMTP-3 Message Transfer Part Level 3Q2140 Recommendation Q.2140SCCP Signalling Connection Control PartTCAP Transaction Capabilities Application PartTUP Telephone User Part
The following SS7 protocols are used in CPP: MTP-3 and SCCP. - MTP3 is a routing protocol to carry signaling messages (compare with IP). There are 3 variants of MTP3: MTP3 Narrowband, MTP3 Broadband, and M3UA (SIGTRAN). - SCCP is a connection control protocol which supports 3 QoS classes, basic connectionless, sequenced connectionless, connection oriented (compare with TCP/UDP).
5.2 MTP3 addressing
Each node in the MTP network is uniquely identified with:- a SPC (signaling point code), 14 bits long for ITU (0 to 16384), 24 bits for ANSI (0 to 16777216)- a network indicator, 2 bits longA CPP node can belong to several MTP networks, it will then appear as a different node for each MTP network, and will have several Point Codes and network indicators. Similar to an IP router with several IP addresses to connect several LANs with each other.
The MO Mtp3bSp Itu/Ansi/Ttc/China represents the node’s own signaling point. There can be more than one Mtp3bSp in a MGW in case it is interconnecting several MTP3 networks and thus needs to have several point codes. (RNC always has one point code only).
MO Attribute Value=================================================================================================================Mtp3bSpItu=1 networkInd 2 (NATIONAL_NETWORK)Mtp3bSpItu=1 rpuId ReliableProgramUniter=51Mtp3bSpItu=1 signallingPointCode 11337=================================================================================================================Total: 1 MOs
MGW01> mom networkind
##################################################################################Enum Values##################################################################################Mtp3bNetworkInd 0:INTERNATIONAL_NETWORK, 1:SPARE, 2:NATIONAL_NETWORK, 3:RESERVED_FOR_NATIONAL_USE----------------------------------------------------------------------------------Indicates which type of geographical network, e.g. national, international, etc..Note: Not applicable for TTC. - INTERNATIONAL_NETWORK: International Network. - SPARE: Spare (for international use only). - NATIONAL_NETWORK: National network. - RESERVED_FOR_NATIONAL_USE: Reserved for national use.**********************************************************************************
5.3 MTP3 Link Set and Route Set
- Signalling link (Mtp3bSl) – a point-to-point signaling channel, carried by a 64 kb/s timeslot (MTP3 Narrowband) or an ATM VC (MTP3 Broadband)- Signalling link set (Mtp3bSls) – a set of signaling links between two Signaling Points. Should contain 2, 4, 8 or 16 signaling links for proper
loadsharing between the links. Each signaling link in the LinkSet is uniquely identified by its SignalingLinkCode (SLC).- Signalling Route (Mtp3bSr) – a sequence of signaling link sets connecting two Signaling Points.- Signalling Route Set (Mtp3bSrs) – all signaling Routes connecting two Signaling Points.
Here we see the MTP3 routing table of MGW01. It shows all neighbouring nodes and their point code.Routes that are reserved by a linkset go to an adjacent node (in red)We can see to which node each SLS is going. Example: SLS=14 goes to RNC27. SLS=16 goes to RNC23.
##################################################################################################MO Class Attribute Type Flags##################################################################################################Mtp3bSlItu linkState long readOnly,nonPersistent,noNotification--------------------------------------------------------------------------------------------------The link state of the Mtp3bSl.The link state is a bit map which contains a combination of the following values: (in hexadecimal format)0x00 Available0x01 Failed0x02 Remotely blocked0x04 Locally blocked0x08 Remotely inhibited0x10 Locally inhibited0x20 Deactivated**************************************************************************************************
5.4 Protocol layers
MTP3
MTP2
TDM (one 64kb
timeslot) PHY (E1/J1/T1)
SCCP
MTP3B
NNISAAL
AAL5
ATM
PHY (STM-1/E1/J1/T1)
GCP
Q.AAL2
M3UA
SCTP
IP
Ethernet (10/100/1000)
SCCP
GCP
Q.AAL2
RANAP
RNSAP
SCCP
RANAP
RNSAP
MTP3 AccessPoint , identified by Service Indicator (SI)
SCCP AccessPoint , identified by Subsystem Number (SSN)
NARROWBAND BROADBAND SIGTRAN
MTP Access Points: Service Indicator (SI) SCCP Access Points: SubSystem Number (SSN)
Finn Magnusson 2008-05-12 rev PA32 131/167
0 = Signalling network management messages1 = Signalling network testing & maintenance regular messages2 = Signalling network testing & maintenance special messages*3 = SCCP4 = Telephone User Part (TUP)5 = ISDN User Part (ISUP)6 = Data User Part, call and circuit related messages7 = Data User Part, facility registration and cancellation messages8 = MTP Testing User Part9 = Broadband ISDN User Part10 = Satellite ISDN User Part11 = Spare12 = Q.2630.1 (Q.AAL2)13 = Spare14 = H.248 (GCP)15 = Spare
Node behaviour MTP3:- SEP: Signaling End Point --> the MTP3/M3U layer is used by an application part (RANAP, RNSAP, GCP, Q.AAL2)- STP: Signaling Transfer Point --> the MTP layer is not used by an application part, it is doing MTP routing only.- SGW: Signaling Gateway Point --> the node is doing routing between the MTP and M3UA layers.
MGW01> get mtp3bsp behaviour
=================================================================================================================MO Attribute Value=================================================================================================================Mtp3bSpItu=1 nodeBehaviour 5 (SGW_STP_SEP)=================================================================================================================Total: 1 MOs
RNC01> get mtp3bsp behaviour
=================================================================================================================MO Attribute Value=================================================================================================================Mtp3bSpItu=1 nodeBehaviour 0 (SEP)=================================================================================================================Total: 1 MOs
MGW01> mom nodebehav
Finn Magnusson 2008-05-12 rev PA32 132/167
##################################################################################Enum Values##################################################################################NodeBehaviourType 0:SEP, 4:SEP_STP, 5:SGW_STP_SEP----------------------------------------------------------------------------------The nodeBehaviorType attribute represents the MTP3b node type. - SEP: Signaling End Point. - SEP_STP: Signalling Transfer and End Point, i.e the signalling point is of both type Signalling End Point (SEP) and Signalling Transfer Point (STP). - SGW_STP_SEP: Signaling GateWay, Signaling End Point and Signalling Transfer Point, i.e the signalling point is of both type Signalling Transfer Point (STP), Signaling End Point (SEP) and Signaling GateWay (SGW).**********************************************************************************
Node behaviour SCCP:- SRP: Signaling Relay Point. --> the MTP layer is used by an SCCP layer which is not used by an application part (it is doing global title translation
only).- SEP: Signaling End Point
5.4.1 Example: MGW
Finn Magnusson 2008-05-12 rev PA32 133/167
AtmPort=2061
VpcTp=1
VplTp=1
ExchangeTerminal=1
PlugInUnit=1
Subrack=2,Slot=26
Mtp3bSls=1
MTP3B
NNISAAL
AAL
ATM
PHY (SDH)
GCP
MTP2
TDM
PHY
(PDH)
MTP3
Mtp3bSlItu=1
NniSaalTp=1
Aal5TpVccTp=1
VclTp=1
Os155SpiTtp=1
ExchangeTerminal=1
PlugInUnit=1
Vc4Ttp=1
Subrack=2,Slot=6
Vmgw=1
Mtp3bAp=1 (SI=14)
Mtp3bSrs=1
Mtp3bSr=1
Mtp3bSls=8
Mtp3bSlItu=1
Mtp2Tp Itu=9
E1PhysPath=2261
Ds0Bundle=1
Mtp3bSrs=9
Mtp3bSr=1
Example: GCP in MGW, carried by MTP3B Example: MTP3 Narrowband Signaling Transfer Point in MGW
Route sets that are reserved by an Mtp3b Access Point are used by an application part.Those that are not reserved by an Mtp3b Access Point are used as Signaling Transfer Point (STP).
===================================================================================Proxy Adm State Op. State MOs linked to 2283:Mtp3bSrs=1=================================================================================== 2403 1 (UNLOCKED) 1 (ENABLED) MgwApplication=1,Vmgw=1
===================================================================================Proxy Adm State Op. State MOs linked to 2266:Mtp3bSpItu=1,Mtp3bSrs=9===================================================================================
RANAP/RNSAP use SCCP routing on DPC+SSN and do not use global title.Therefore SccpGlobalTitle and SccpEntitySet MOs are not needed in the RANAP/RNSAP stack
##################################################################################################MO Class Attribute Type Flags##################################################################################################Ranap preferredAddressing long --------------------------------------------------------------------------------------------------Preferred addressing for called party address, defined as: 1: "DPC+SSN" (RI=SSN) 2: "DPC+SSN+GT" (RI=GT) 3: "DPC+SSN+GT" (RI=SSN) 4: "GT+SSN" (RI=GT) Where RI is the Routing Indicator to be set by the application.Note: this attribute is currently not used by the system. Changing it has no effect.This attribute may only be changed by Ericsson personnel.Reference: [41]Range: 1 to 4, Default=1 **************************************************************************************************
Decoding is normally done by moshell (not working on CPP5.1, will be fixed in moshell 7.0s).Decoding help: http://utran01.epa.ericsson.se/utranwiki/CelloInformation/MtpSccpSs7TraceHelper
To catch the signaling messages:
RNC11> lh sccpmp te e trace3 Scc_Server_proc
$ lhsh 000800 te e trace3 Scc_Server_proc$
RNC11> lhsh 000800 te log read | decoder_ss7 | flow_ss7
============================================================================================TIME HSN SDL SI OPC DPC SLC DIR FROM/TO MESSAGE============================================================================================10:56:16.468 0 2 MAINT 2351 2300 2 SEND MTPL3/MTPL2 DL_MSU_REQ SLTA10:56:16.676 1 2 MAINT 2351 2810 2 SEND MTPL3/MTPL2 DL_MSU_REQ SLTM10:56:16.676 1 2 MAINT 2810 2351 2 RECV MTPL2/MTPL3 DL_MSU_IND SLTA...<cut>...11:03:41.788 MTPL3: LINK IN SERVICE11:03:41.792 MTPL3: LINK IN SERVICE11:04:00.484 MTPL3: LINK OUT OF SERVICE10:48:17.928 MTPL3: LINK IN SERVICE
=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 2251 AtmPort=MS-6-1,VplTp=1,VpcTp=1,VclTp=vc50 eteLoopBack 0 >>> Return value = false
=================================================================================================================Total: 1 MOs attempted, 1 MOs actioned
##################################################################################################MO Class Attribute Type Flags
Finn Magnusson 2008-05-12 rev PA32 161/167
##################################################################################################Mtp3bSlItu linkState long readOnly,nonPersistent,noNotification--------------------------------------------------------------------------------------------------The link state of the Mtp3bSl.The link state is a bit map which contains a combination of the following values: (in hexadecimal format)0x00 Available0x01 Failed0x02 Remotely blocked0x04 Locally blocked0x08 Remotely inhibited0x10 Locally inhibited0x20 Deactivated**************************************************************************************************
RNC11> lacl Mtp3bSls=Iuc-2351-2300,
=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 2682 Mtp3bSpItu=Iu,Mtp3bSls=Iuc-2351-2300,Mtp3bSlItu=Iuc-2351-2300 activate 0 2682 Mtp3bSpItu=Iu,Mtp3bSls=Iuc-2351-2300,Mtp3bSlItu=Iuc-2351-2300 deactivate 0 2682 Mtp3bSpItu=Iu,Mtp3bSls=Iuc-2351-2300,Mtp3bSlItu=Iuc-2351-2300 emergencyActivate 0 2682 Mtp3bSpItu=Iu,Mtp3bSls=Iuc-2351-2300,Mtp3bSlItu=Iuc-2351-2300 localInhibit 0 2682 Mtp3bSpItu=Iu,Mtp3bSls=Iuc-2351-2300,Mtp3bSlItu=Iuc-2351-2300 localUninhibit 0=================================================================================================================
4) Mtp3bSl . Check the signallinglinkcode . Must match on both ends.
//SignallingLinkCode on RNC:RNC10> get slitu code
=================================================================================================================MO Attribute Value=================================================================================================================Mtp3bSpItu=Iu1,Mtp3bSls=Iuc-1-2300-3,Mtp3bSlItu=1 signLinkCode 9Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1 signLinkCode 3=================================================================================================================Total: 2 MOs
//SignallingLinkCode in CoreNetwork:CRB10> get mtp3bslitu code
=================================================================================================================MO Attribute Value
Finn Magnusson 2008-05-12 rev PA32 162/167
=================================================================================================================Mtp3bSpItu=Iu,Mtp3bSls=Iuc-1-2351-3,Mtp3bSlItu=1 signLinkCode 2Mtp3bSpItu=Iup,Mtp3bSls=Iup-2-2351-3,Mtp3bSlItu=1 signLinkCode 3=================================================================================================================Total: 2 MOs
Deleting ...=================================================================================== 5204 TransportNetwork=1,Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1 >>> Mo deleted===================================================================================Total: 1 MOs attempted, 1 MOs deleted
MO Attribute Value=================================================================================================================Mtp3bSpItu=Iu1,Mtp3bSrs=Iuc-1-2300-3 destPointCode 2300Mtp3bSpItu=Iu1,Mtp3bSrs=Iup-2-2810-3 destPointCode 2999=================================================================================================================Total: 2 MOs
//Own point codes and dest point codes in Core Network
CRB10> get mtp3bspitu code
=================================================================================================================MO Attribute Value=================================================================================================================Mtp3bSpItu=Iup signallingPointCode 2810Mtp3bSpItu=Iu signallingPointCode 2300=================================================================================================================Total: 2 MOs
CRB10> get mtp3bsrs code
=================================================================================================================MO Attribute Value=================================================================================================================Mtp3bSpItu=Iup,Mtp3bSrs=Iup-2-2351-3 destPointCode 2351Mtp3bSpItu=Iu,Mtp3bSrs=Iuc-1-2351-3 destPointCode 2351=================================================================================================================Total: 2 MOs
//In the trace we see that each side are using different point codes
RNC10> lh sccpmp te e trace3 Scc_Server_proc
$ lhsh 000800 te e trace3 Scc_Server_proc$
RNC10> lh sccpmp te log read | decoder_ss7 | flow_ss7