Академический Документы
Профессиональный Документы
Культура Документы
GSM / UMTS
R4 Media Gateway
OAM and Troubleshooting Guide
Nortel CONFIDENTIAL
The information contained herein is the property of Nortel and is strictly confidential. Except as expressly authorized in writing by
Nortel, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know,
and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to
protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel,
the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress in
engineering and manufacturing may warrant.
* Nortel, the Nortel logo, the Globemark HOW the WORLD SHARES IDEAS, and Unified Networks are trademarks of Nortel. DMS,
DMS-HLR, DMS-MSC, MAP, and SuperNode are trademarks of Nortel. GSM is a trademark of GSM MOU Association.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
iv
Nortel Confidential Copyright 2004-2006 Nortel
Publication history
This section contains a high-level listing of updates and changes to this
product documentation for the current release cycle.
May 2006
NSS18/MGW18, Standard, 02.06. Modified severity of APS alarm
C1860003; updated Type, Legend, Component, Probable Cause and/or
Severity of MGW alarms 7056 7000, 7056 7001, 7075 0005 through 7075
0010, 7075 0100 and 7075 0101. Updated references to Multiservice Switch
NTPs per the Media Gateway PCR6.1 list of titles and numbers. Added
software upgrade and patching procedures, and health checks, for the MGW
and AN, in the Software Management chapter.
October 2005
NSS18/MGW18, Preliminary, 02.05. Editorial changes.
October 2005
NSS18/MGW18, Preliminary, 02.04. Removed nodal provisioning tool.
Removed NSS17-based installation chapters. Updated information per
internal reviewers feedback.
September 2005
NSS18/MGW18, Preliminary, 02.02 and 02.03. Updated chapters 1-3, 15,
and appendices C-G for MG18. Incorporated internal reviewers feedback.
Changed all occurrences of Nortel Networks to Nortel*.
October 2004
NSS18/MGW18, Draft, 02.01.
October 2004
NSS17/MGW17, Standard, 01.08. A new appendix, Appendix B: Manual
adjustment for DST on MGW nodes, is inserted. New sections for handling
glare problems and announcement error scenarios have been added in the
Troubleshooting chapter.
August 2004
NSS17/MGW17, Standard, 01.07. This release contains editorial changes
based on internal reviews and feedback.
August 2004
NSS17/MGW17, Standard, 01.06. This release adds Chapter 15:
Troubleshooting the GSM Media Gateway. It also renames the title of this
NTP to R4 BICN Media Gateway OAM and Troubleshooting Guide.
April 2004
NSS17/MGW17, Preliminary, 01.05. This release adds the following chapters
that were formerly in NTP 411-2231-330. With the addition of these chapters,
the title of this NTP is now changed from Media Gateway Provisioning and
Troubleshooting Reference Guide to R4 BICN Media Gateway OA&M Manual.
Chapter 1: GSM BICN Media Gateway performance management and
CDL
Chapter 2: GSM Media Gateway fault management
Chapter 3: GSM Media Gateway configuration management (including
the Provisioning Parameters table that was included as a separate
appendix in the previous release of this NTP, 411-2231-331)
Chapter 4: BICC Media Gateway CDL for OM Groups and Registers
Chapter 12: GSM Media Gateway general maintenance
Chapter 13: GSM Media Gateway basic card maintenance
December 2003
NSS17/MGW17, Preliminary Phase 5, 01.03. This is the second issue of this
NTP. It contains editorial changes to improve the clarity of the content.
Emphasis was given in Chapter 1 that the templates are examples only and
the customers actual template names and contents will vary, depending on
the needs of their network.
September 2003
NSS17/MGW17, Preliminary Phase 4, 01.02. This is the first issue of this
NTP. This NTP includes eight chapters concerning provisioning and
troubleshooting that were formerly reviewed in draft format as part of NTP
411-2231-330, Univity Media Gateway Operations and Maintenance
Reference Guide.
Contents 1
About this document xxiii
Audience for this document xxiii
Organization of this document xxiii
Software release applicability xxiv
GSM18/UMTS04 Product Computing Module Loads xxiv
Special text conventions in this document xxv
Indication of hypertext links xxv
Figures
Figure 2-1 MGW CDL Hierarchy Part 1 2-2
Figure 2-2 MGW CDL Hierarchy Part 2 2-3
Figure 2-3 MGW CDL Hierarchy Part 3 2-4
Figure 2-4 MCP OSI State Transitions 2-5
Figure 2-5 Mtp3/ OSI State Transitions 2-6
Figure 2-6 Mtp3/ Ls/ OSI State Transitions 2-8
Figure 2-7 Mtp3/ Ls/ Link/ OSI State Transitions 2-10
Figure 2-8 Mtp3/ Ls/ Link/ OSI States 2-12
Figure 2-9 Mtp3/ Rs/ OSI State Transitions 2-13
Figure 2-10 Mtp3/ Rs/ Route/ OSI State Transitions 2-15
Figure 2-11 Nsta/ Vgs M2ua OSI State Transitions 2-17
Figure 2-12 Nsta/ Vgs M2ua As OSI State Transitions 2-19
Figure 2-13 Nsta/ Vgs M2ua As/ Asp/ OSI State Transitions 2-21
Figure 2-14 Nsta/ Vgs MgcIf OSI State Transitions 2-23
Figure 2-15 Nsta/ Vgs Mtp2/ OSI State Transitions 2-26
Figure 2-16 Q2630/ OSI State Transitions 2-27
Figure 2-17 SaalNni/ OSI State Transitions 2-30
Tables
Table 1-1 CallStatistics Statistics 1-3
Table 1-2 AAL2Svc Statistics 1-9
Table 1-3 Profile/n Statistics 1-10
Table 1-4 TConn/n Statistics 1-14
Table 1-5 AtmSubnet/<name> Statistics 1-15
Table 1-6 MgcIf Statistics 1-17
Table 1-7 CasDef/n Statistics 1-19
Table 1-8 Tag/n Statistics 1-20
Table 1-9 Cas Statistics 1-20
Table 1-10 DS0/n Statistics 1-21
Table 1-11 MultiParty Statistics 1-22
Table 1-12 M2ua Statistics 1-23
Table 1-13 As/n Statistics 1-24
Table 1-14 Asp/m Statistics 1-25
Table 1-15 Iid/y Statistics 1-29
Table 1-16 SctpAssoc Statistics 1-31
Table 1-17 Mtp2 Statistics 1-35
Table 1-18 Q2630 Statistics 1-36
Table 1-19 MTP3 Statistics 1-43
Table 1-20 Link/z Statistics 1-44
Table 1-21 Route/z Statistics 1-44
Table 2-1 MCP OSI States 2-5
Table 2-2 Mtp3/ OSI States 2-7
Table 2-3 Mtp3/ Ls/ OSI States 2-9
Table 2-4 Mtp3/ Rs/ OSI States 2-14
Table 2-5 Mtp3/ Rs/ Route/ OSI States 2-16
Table 2-6 Nsta/ Vgs M2ua OSI States 2-18
This publication is applicable to the DMS-MSC Family offices that have the
GSM NSS18/UMTS VCN04 software release. Unless this publication is
revised, it also applies to offices that have software releases greater than GSM
NSS18/UMTS VCN04. In the GSM market 3GPP R99 and R4 is supported in
NSS18. 3GPP support in the UMTS market for NSS18 is R99 only.
For more information about the new features contained in the GSM NSS18/
UMTS VCN04 software release, refer to the GSM / UMTS MSC Software
Delta, 411-2231-199, and the GSM / UMTS HLR100/200 Software Delta,
411-2831-199.
Before GSM05, software loads were package-based loads. GSM05 was the
first MSC Product Computing Module Load (PCL). PCLs are composed of
layers of software, or Delivery Receivable Units (DRUs).
Note: The component data model for the MGW is based on the Nortel
PVG product component data model with additional components and
attributes added to meet MGW needs. See the appendices for a complete
listing of all the MGW specific components and subcomponents, and their
attributes.
Table 1-1
CallStatistics Statistics
Table 1-1
CallStatistics Statistics (continued)
Table 1-1
CallStatistics Statistics (continued)
Table 1-1
CallStatistics Statistics (continued)
Table 1-1
CallStatistics Statistics (continued)
nbUpInitTimeOuts This attribute counts Nb User Plane (Nb UP) Operational and
initialization failures due to initialization Collected
message reply timeouts.
nbUpInitNacksRx This attribute counts Nb User Plane (Nb UP) Operational and
initialization failures due to negative Nb UP Collected
initialization acknowledgements received from
the peer Media Gateway.
Table 1-1
CallStatistics Statistics (continued)
nbUpInitVersionMismatches This attribute counts Nb User Plane (Nb UP) Operational and
initialization failures due to an Nb UP mode Collected
version mismatch with the peer Media
Gateway.
nbUpInitSubflowMismatche This attribute counts Nb User Plane (Nb UP) Operational and
s initialization failures due to a Radio Access Collected
Bearer (RAB) subflow mismatch with the peer
Media Gateway.
nbUpInitFormatErrors This attribute counts Nb User Plane (Nb UP) Operational and
initialization failures due to a message format Collected
error received from the peer Media Gateway.
upspeedGttFailures This attribute counts upspeed failures for the Operational and
Global Text Telephony (GTT) service that Collected
requires G.711 for reliable transport.
Table 1-1
CallStatistics Statistics (continued)
upspeedIdenFailures This attribute counts upspeed failures for the Operational and
Integrated Digital Enhanced Network (iDEN) Collected
service that requires G.711 for reliable
transport.
upspeedCsdFailures This attribute counts upspeed failures for the Operational and
Circuit Switched Data (CSD) service that Collected
requires G.711 for reliable transport.
Table 1-2
AAL2Svc Statistics (continued)
Table 1-3
Profile/n Statistics (continued)
neverUsedSvcsDeleted This attribute counts the number of SVCs that Operational and
were created by this gateway using this Profile Collected
and deleted without carrying any traffic.
Table 1-3
Profile/n Statistics (continued)
svcSetupTimeoutCount This attribute counts the number of times the Operational and
SVC setup timeout expired for SVCs using this Collected
Profile.
Table 1-3
Profile/n Statistics (continued)
adds a new Profile, or changes the addressPrefix for a Profile, the software
updates all active SVCs based on the new data. This means that the profile for
a given TConn may change after the SVC has been established. However, not
all new attributes affect an SVC that has already been created.
Table 1-4
TConn/n Statistics
Table 1-4
TConn/n Statistics (continued)
Table 1-5
AtmSubnet/<name> Statistics (continued)
Attribute Name Description Type
resourceCongestion This attribute counts the number of times that Operational and
ThresholdSurpassed a state of resource congestion has been Collected
entered, and thus, the number of times the
MgcIf resource congestion alarm was set. A
state of resource congestion is entered when
the contextLoadPercent attribute of the
CallStatistics component surpasses the
congestionThreshold of the MgcIf component.
Resource congestion may only be reentered
after the contextLoadPercent attribute falls to
or below the congestionAbatementThreshold
of the MgcIf component.
Throughput Congestion This attribute counts the number of times Operational and
ThresholdSurpassed throughput congestion has been entered, and Collected
thus, the number of times the MgcIf
throughput congestion alarm was set. A state
of throughput congestion is entered when the
throughputLoadPercent attribute of the
CallStatistics component surpasses the
congestionThreshold of the MgcIf component.
Throughput congestion may only be reentered
after the throughputLoadPercent attribute falls
to or below the
congestionAbatementThreshold of the MgcIf
component.
Table 1-6
MgcIf Statistics (continued)
Attribute Name Description Type
subnetCongestion This attribute counts the number of times that Operational and
ThresholdSurpassed a state of subnet congestion has been Collected
entered, and thus, the number of times that
the MgcIf subnet congestion alarm was set. A
state of subnet congestion is entered when the
currentPercentBandwidthUtil of any of the
AtmCac AtmSubnet or IpCac IpSubnet
components surpasses the
congestionThreshold of the MgcIf component.
Subnet congestion may only be reentered
after the currentPercentBandwidthUtil attribute
of all of the AtmCac AtmSubnet or IpCac
IpSubnet components falls to or below the
congestionAbatementThreshold of the MgcIf
component.
enabled - no failure.
Table 1-9
Cas Statistics (continued)
Attribute Name Description Type
Table 1-10
DS0/n Statistics (continued)
Attribute Name Description Type
callControllerPort This attribute indicates the UDP port of the call Operational
controller, if this DS0 is being used for a call. It
represents the Media Gateway Controller
(MGC) UDP port.
Table 1-11
MultiParty Statistics (continued)
Attribute Name Description Type
Table 1-14
Asp/m Statistics (continued)
Attribute Name Description Type
aspDownMsgsReceived The attribute counts the number of ASP Down Operational and
(DOWN) messages received. Collected
aspDownAcksSent This attribute counts the number of ASP Down Operational and
Acknowledge (DOWN ACK) messages sent. Collected
Table 1-14
Asp/m Statistics (continued)
Attribute Name Description Type
Table 1-14
Asp/m Statistics (continued)
Attribute Name Description Type
Table 1-15
Iid/y Statistics (continued)
Attribute Name Description Type
bytesSent This attribute counts the total number of bytes Operational and
sent. This count includes the Stream Control Collected
Transmission Protocol (SCTP) message
headers and chunk headers but does not
include the Internet Protocol (IP) header.
bytesReceived This attribute counts the total number of bytes Operational and
received. This count includes the Stream Collected
Control Transmission Protocol (SCTP)
message headers and chunk headers but
does not include the Internet Protocol (IP)
header.
Table 1-16
SctpAssoc Statistics (continued)
Attribute Name Description Type
lastFailureReason This attribute indicates the reason for the most Operational
recent SCTP association failure. Reason may
be one of the following:
maxUnackedMsgsLimit - Number of
unacknowledged messages reached the
internal limit.
Table 1-16
SctpAssoc Statistics (continued)
Attribute Name Description Type
Table 1-16
SctpAssoc Statistics (continued)
Attribute Name Description Type
notAlignedTimeouts This attribute counts the timeouts of the Not Operational and
Aligned timer (T2) represented by the attribute Collected
notAlignedTimer.
Table 1-17
Mtp2 Statistics (continued)
Attribute Name Description Type
Q2630 Stats
The following are the statistics for the Q2630 component:
Table 1-18
Q2630 Statistics
Attribute Name Description Type
establishReqTimerExpiries This attribute counts the number of times the Operational and
timer Timer_ERQ has expired. The timer Collected
expiring could be due to the following reasons:
Table 1-18
Q2630 Statistics (continued)
Attribute Name Description Type
establishReqRetryExhausts This attribute counts the number of times the Operational and
ESTABLISH REQUEST retry mechanism Collected
(specified by the value of the provisionable
attribute establishRequestRetries) failed to get
the expected response from the Q.2630 peer
entity. This could be due to the following
reasons:
releaseReqTimerExpiries This attribute counts the number of times the Operational and
timer Timer_REL has expired. The timer Collected
expiring could be due to the following reasons:
Table 1-18
Q2630 Statistics (continued)
Attribute Name Description Type
resetReqTimerExpiries This attribute counts the number of times the Operational and
timer Timer_RES has expired. Collected
Table 1-18
Q2630 Statistics (continued)
Attribute Name Description Type
blockReqTimerExpiries This attribute counts the number of times the Operational and
timer Timer_BLO has expired. Collected
blockReqRetryExhausts This attribute counts the number of times the Operational and
BLOCK REQUEST retry mechanism Collected
(specified by the value of the provisionable
attribute blockRequestRetries) failed to get the
expected response from the Q.2630 peer
entity.
Table 1-18
Q2630 Statistics (continued)
Attribute Name Description Type
unblockReqTimerExpiries This attribute counts the number of times the Operational and
timer Timer_UBL has expired. The timer Collected
expiring could be due to the following reasons:
unblockReqRetryExhausts This attribute counts the number of times the Operational and
UNBLOCK REQUEST retry mechanism Collected
(specified by the value of the provisionable
attribute unblockRequestRetries) failed to get
the expected response from the Q.2630 peer
entity.
Table 1-18
Q2630 Statistics (continued)
Attribute Name Description Type
msgsRxFromClient This attribute counts the messages that the Operational and
Q2630 component has received from the Collected
Q2630Client component.
msgsTxToClient This attribute counts the messages that the Operational and
Q2630 component has sent to the Collected
Q2630Client component.
Table 1-18
Q2630 Statistics (continued)
Attribute Name Description Type
MTP3 Stats
The following table contains the statistics defined for the MTP3 component.
Table 1-19
MTP3 Statistics
Attribute Name Description Type
Table 1-21
Route/z Statistics (continued)
Attribute Name Description Type
This chapter describes the fault management for the MGW. Please refer to the
Multiservice Switch 6400, 7400, 15000, 20000 Alarms Reference NTP
NN10600-500 for all non-MGW specific alarms.
Analysis of CDL 2
The following diagrams depict the CDL hierarchy for the MGW. Many of the
components are re-used or modified versions of Nortel Packet Voice
Gateway (PVG) components. Please reference Media Gateway 7480/15000
Technology Fundamentals NTP NN10600-780 for more in-depth information
on all of these components.
Figure 2-1
MGW CDL Hierarchy Part 1
Legend
Legend
Existing New Link Nsta/n
Nsta/n
Existing New
OSI State
Modified
Modified Dynamic
Dynamic
Vgs
Vgs
CasDef/n
CasDef/n Aal2Svc
Aal2Svc H248
H248 MgcIf/n
MgcIf/n Ctrl/mg
Ctrl/mg CallStats
CallStats AtmTConn/n
AtmTConn/n
Prof/n
Prof/n TConn/n
TConn/n VrAp
VrAp UdpPort/n
UdpPort/n Aap
Aap Pap
Pap
Tag/n
Tag/n TProf/n
TProf/n PathOwner SpvcAp
PathOwner SpvcAp
Cas
Cas Ds0/n
Ds0/n TagUser
TagUser Vp/n
Vp/n
Agc
Agc Gtt
Gtt Bnc
Bnc Bnr
Bnr Mec
Mec Ecan
Ecan MultiParty
MultiParty
TTPProfile
TTPProfile PTPProfile
PTPProfile
Figure 2-2
MGW CDL Hierarchy Part 2
Legend
Legend
Existing New Link Nsta/n
Nsta/n
Existing New
OSI State
Modified
Modified Dynamic
Dynamic
Vgs
Vgs
AtmCac
AtmCac Mtp2/n
Mtp2/n Mtp2Profile/n
Mtp2Profile/n M2ua
M2ua Ctrl/Sg
Ctrl/Sg
As/n
As/n SctpPort/n
SctpPort/n VrAp
VrAp
AtmSubnet/n
AtmSubnet/n MCP
MCP
Iid/n
Iid/n Asp/n
Asp/n SctpLink/n
SctpLink/n
MCP
MCP SctpAssoc
SctpAssoc
Figure 2-3
MGW CDL Hierarchy Part 3
Legend
Legend
Existing New Link
Existing New
OSI State
Modified
Modified Dynamic
Dynamic
Shelf
Shelf SaalNni/n
SaalNni/n
Card/n
Card/n MCP
MCP Nap
Nap
CarrierCard
CarrierCard Mtp3/n
Mtp3/n Q2630/n
Q2630/n
Ls/n
Ls/n Rs/n
Rs/n ServInd/12
ServInd/12 PeerAddr/n
PeerAddr/n MCP
MCP Mtp3Conn
Mtp3Conn
Link/n
Link/n RInfo/n
RInfo/n Route/n
Route/n Q2630Client
Q2630Client
MCP
MCP MCP
MCP
MCP Component
Figure 2-4
MCP OSI State Transitions
Unlocked
Unlocked
Disabled 1 Enabled
Disabled Enabled
2
Idle
Idle Idle
Idle Active
Active Busy
Busy
4 3
5
Idle
Idle Idle
Idle Active
Active Busy
Busy
Disabled
Disabled Enabled
Enabled Enabled
Enabled
Locked
Locked Shutting
ShuttingDown
Down
Table 2-1
MCP OSI States
State Details
(Admin/Operational/Usage)
Unlocked/Disabled/Idle This is the initial state and the state when communication is
not up between the MCP applications.
Table 2-1
MCP OSI States (continued)
State Details
(Admin/Operational/Usage)
Unlocked/Enabled/Busy This state is entered when the send window of the MCP
application is full.
Mtp3/ Component
Figure 2-5
Mtp3/ OSI State Transitions
Unlocked
Disabled Enabled
5
1 2
Idle Idle Active Busy
4 3
The initial OSI state of Mtp3 is Unlocked/Disabled/Idle and is set during the
initialization of Mtp3. The following describes the OSI state transitions:
Table 2-2
Mtp3/ OSI States
State Details
(Admin/Operational/Usage)
Unlocked/Disabled/Idle This is the initial state of Mtp3 while waiting for Mtp3 to
complete initialization. This is also the state of Mtp3 when all
Linksets are in a disabled state rendering Mtp3 inoperable.
Unlocked/Enabled/Idle This is a valid state when at least one Linkset has transitioned
to an Unlocked/Enabled/Idle state after being Disabled.
Unlocked/Enabled/Active This is a valid state when at least one Linkset has successfully
transitioned to an Active state.
Unlocked
Disabled Enabled
1 2
Idle Idle Active
4 3
Unu sed
State
10 9 7 6
Enabled
Disabled Enabled
Shutting Down
Locked
1. When one or more links in the Linkset become enabled and no links are active.
6, 7. This is the semi-transient state after receiving the Lock command while waiting for
SaalNni to send out-of-service message in response to the Stop command sent from
every link.
Table 2-3
Mtp3/ Ls/ OSI States
State Details
(Admin/Operational/Usage)
Unlocked
Disabled Enabled
9
1 2
Idle Idle Active Busy
10 3
7
8 5 4
6
Idle Idle Active Busy
The initial OSI state of the Link is Unlocked/Disabled/Idle and is set during
the initialization of the Link. The following describes the OSI state
transitions:
Links it manages. Once a Link has been marked as in-service, it may have zero, one, or
many users but that fact is abstracted from Mtp3 therefore Mtp3 is unaware of how the
Link is being used. This transition may also occur as a result of Mtp3 receiving an
uninhibit command from the operator. This allows Mtp3 to start using Layer 2 again after
being inhibited. See transition #5 for details on inhibiting an Mtp3 Link.
6. The Link transitions from Locked, Enabled/Idle to Locked, Disabled/Idle when Mtp3
receives the Out-of-service message from Layer 2 as a result of the Stop command being
sent to Layer 2.
The Link generates a Set Alarm during this transition only if Layer 2 stops responding to
requests from the Mtp3.
10. The Link transitions from Unlocked/Enabled/Idle to Unlocked/Disabled/Idle when the Link
becomes inoperable while the Link is inhibited.
a. Layer-2 sends Mtp3 an Out-of-service indicating that it should no longer be used by the
link.
b. The link SLT failed.
The Link generates a Set Alarm during this transition only if Layer 2 stops responding to
requests from the Mtp3.
Figure 2-8
Mtp3/ Ls/ Link/ OSI States
State Details
(Admin/Operational/Usage)
Unlocked/Disabled/Idle This is the initial state of the Link while Mtp3 is establishing a
communication link with Layer 2. This is also a valid state
when the communication link is broken rendering the Link
inoperable.
Unlocked
Disabled Enabled
1 2
Idle Idle Active Busy
4 3
Unused
State
Enabled
Disabled Enabled
Shutting Down
Locked
Table 2-4
Mtp3/ Rs/ OSI States
State Details
(Admin/Operational/Usage)
Unlocked
Disabled Enabled
1 2
Idle Idle Active Busy
4 3
Unused
State
Enabled
Disabled Enabled
Shutting Down
Locked
1. When the associated Linkset becomes enabled and idle, or when the remote signaling
becomes available but the Route is not in use due to a higher priority route being
available.
2. When the Route becomes in use due to this Route being the highest priority available
route (a higher priority route has become unavailable).
3. When the Route is not in use due to higher priority route becoming available, and when
the associated Linkset becomes enabled/idle.
Table 2-5
Mtp3/ Rs/ Route/ OSI States
State Details
(Admin/Operational/Usage)
Unlocked
Disabled Enabled
1 2 3
Idle Idle Active Busy
7 5 4
6
8
9
Unused
State
Enabled
Disabled Enabled
Shutting Down
Locked
Table 2-6
Nsta/ Vgs M2ua OSI States
State Details
(Admin/Operational/Usage)
Unlocked
Disabled Enabled
1 2
Idle Idle Active Busy
4 3
Unused
State
Enabled
Disabled Enabled
Shutting Down
Locked
Table 2-7
Nsta/ Vgs M2ua As OSI States
State Details
(Admin/Operational/Usage)
Unlocked
Disabled Enabled
1 2 3
Idle Idle Active Busy
7 5 4
6
8
9
Unused
State
Enabled
Disabled Enabled
Shutting Down
Locked
Table 2-8
Nsta/ Vgs M2ua As/ Asp/ OSI States
State Details
(Admin/Operational/Usage)
Unlocked
Unlocked
Disabled
Disabled Enabled
Enabled
1 2 3
Idle
Idle Idle
Idle Active
Active Busy
Busy
6 5 4
20 19 13 14 12 10 11 9 7 8
18
Idle Idle 16 Active 15 Busy
Idle Idle Active Busy
17
Disabled
Disabled Enabled
Enabled Enabled
Enabled
Locked
Locked Shutting
ShuttingDown
Down
The initial OSI state of the MgcIf component is Unlocked, Disabled, Idle and
is set during the initialization of the MgcIf component. The following
describes the OSI state transitions for the MgcIf component:
Table 2-9
Nsta/ Vgs MgcIf OSI States
Locked, Disabled, Idle This is the state after the MgcIf has successfully deregistered
the MGW with the MGC and is locked by the administrator.
Locked, Enabled, Idle This is the state where MgcIf still has MGW registered with
MGC, there are no active calls, and is locked by the
administrator.
Shutting Down, Enabled, This is a valid state when the MgcIf component is processing
Active call requests, (i.e. setup calls) and/or has at least one active
call and is locked by the administrator.
Shutting Down, Enabled, This is a valid state when a congestion alarm is raised, an
Busy overload alarm is raised, or all provisioned TDM resources are
in use.
Unlocked
Disabled Enabled
1 2
Idle Idle Active Busy
3
Unused
State
Enabled
Disabled Enabled
Shutting Down
Locked
3. Mtp2 loses the Layer 3 communication link which results in Mtp2 de-aligning.
Table 2-10
Nsta/ Vgs Mtp2/ OSI State
State Details
(Admin/Operational/Usage)
Q2630/ Component
Figure 2-16
Q2630/ OSI State Transitions
Unlocked
Unlocked
Enabled
Enabled 6
Disabled
Disabled
1 2 3
Idle
Idle Idle
Idle Active
Active Busy
Busy
7 5 4
8 9 10
Idle
Idle Idle
Idle Active
Active Busy
Busy
Disabled
Disabled Enabled
Enabled Enabled
Enabled
Locked
Locked Shutting
ShuttingDown
Down
The Q2630 OSI state will indicate the overall health of the application (e.g.
an initialization failure would inhibit the transition to the enabled state) and
the Q2630 component will appear on an element manager (MDM) providing
OA&M personnel a persistent mechanism for conveying application health.
Table 2-11
Q2630 OSI States
State Details
(Admin/Operational/Usage)
Table 2-11
Q2630 OSI States (continued)
State Details
(Admin/Operational/Usage)
Unlocked/Enabled/Active This is a valid state when the Q2630 component has at least
one established call and at least one unblocked path to its
peer.
Unlocked/Enabled/Busy This is a valid state when all paths to the Q2630 components
peers have been blocked.
SaalNni/ Component
Figure 2-17
SaalNni/ OSI State Transitions
Unlocked
Disabled Enabled
3
1 2
Idle Idle Active Busy
4
1) SaalNni receives a Stop command indicating SaalNni should cease providing service.
2) SaalNni fails to receive messages from its peer SaalNni which results in SaalNni sending
its user an Out-of-service message indicating it should no longer be used.
3) SaalNni loses the Layer 3 communication link which results in SaalNni de-aligning.
Table 2-12
SaalNni/ OSI States
State Details
(Admin/Operational/Usage)
This is a valid state once the SaalNni receives a Start Command from
Unlocked/Enabled/Idle
Layer 3 initiating the alignment process.
This is a valid state when SaalNni successfully aligns with its peer
Unlocked/Enabled/Active
SaalNni and sends an In-service message to Layer 3.
Unlocked
Unlocked
Disabled 1 Enabled
Disabled Enabled
Idle
Idle Idle
Idle Active
Active Busy
Busy
2
Idle
Idle Idle
Idle Active
Active Busy
Busy
Disabled
Disabled Enabled
Enabled Enabled
Enabled
Locked
Locked Shutting
ShuttingDown
Down
Table 2-13
Shelf Card/ CarrierCard/ OSI States
State Details
(Admin/Operational/Usage)
Table 2-13
Shelf Card/ CarrierCard/ OSI States
State Details
(Admin/Operational/Usage)
Alarms 2
Table 2-14 lists all MGW alarms. Detailed descriptions can be found below
the table.
Table 2-14
MGW Alarms List
Index Title
Table 2-14
MGW Alarms List (continued)
Index Title
7056 7006 MgcIf Call Admission Control Subnet Bandwidth Congestion Alarm
M2ua Alarms
M2ua Communication Failure Alarm
Legend
<x> = Nsta instance identifier
<y> = As instance identifier
Details
The M2ua Communication Failure Alarm is raised by the As component when it
becomes inaccessible due to a communication failure with a remote Application
Server Process (Asp) component.
This alarm is set with critical severity if the As component is down or inactive,
meaning that no communication is possible with the remote node.
This alarm is set with minor severity when the As is in the pending state.
This alarm is cleared when this As becomes accessible due to (re-)established
communication with the remote Asp component.
Probable Cause
commSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
Verify remote network connectivity.
Legend
<x> = Nsta instance identifier
<y> = As instance identifier
<z> = Asp instance identifier
Details
The M2ua Sctp Congestion Alarm is raised by M2ua for an Application Server
Process (Asp) component when the underlying Sctp layer detects that it can no
longer transmit payload messages to the remote node. This condition may occur
due to network congestion or an overload condition at the Asp. The Asp
component transitions to the Unlocked/Enabled/Busy state when this alarm is
raised.
This alarm is cleared when the Asp returns to Unlocked/Enabled/Active state.
This occurs when no message congestion has been detected for at least 1 minute
Probable Cause
congestionCause_c
Type
qualityOfServiceType_c
Remedial action
Verify and reconfigure the network if necessary.
Legend
<x> = Nsta instance identifier
Details
This message alarm is raised by the M2ua component when an M-Sctp Establish
Request indication is received from an Application Server Process (Asp) that is
not recognized by this media gateway. This typically indicates a configuration
problem on the local or remote node. For example, the Asp is not provisioned or
has been provisioned with an incorrect IP address or port.
Probable Cause
probCauseUnknownCause_c
Type
communicationsType_c
Remedial action
Verify the provisioning on this and the remote M2ua components.
Legend
<x> = Nsta instance identifier
<y> = As instance identifier
Details
This M2ua Unrecognized Interface Identifier message alarm is raised on the As
component when M2ua receives an unrecognized Interface Identifier (IID) from
an Application Server Process (Asp) and responds with an Invalid Interface
Identifier error. It is also generated when M2ua receives an Invalid Interface
Identifier error from the Asp. This typically indicates a configuration problem on
the local or remote node. For example, the IID is not provisioned or has been
provisioned with an incorrect instance value. This alarm is throttled by the DCS
collection period for messages received when the As is Unlocked/Enabled/
Active.
Probable Cause
probCauseUnknownCause_c
Type
communicationsType_c
Remedial action
Verify the provisioning on this and the remote M2ua components.
Legend
<x> = Nsta instance identifier
Details
The M2ua Overload Alarm is raised when M2ua has reached its throughput limit
and is throttling back incoming traffic. This includes the Asp (USP) and SS7
layer 2 interfaces (Mtp2 and/or SaalNni). The alarm is set with warning severity
and corresponds with a transition to the Unlocked/Enabled/Busy state.
The alarm is cleared when M2ua returns to the Unlocked/Enabled/Active state.
This occurs when M2ua does not detect a local overload condition on any of its
interfaces for at least one minute.
Probable Cause
atOrNearCapacityCause_c
Type
qualityOfServiceType_c
Remedial action
Verify and reconfigure the network if necessary.
Legend
<a> = Nsta instance identifier
<b> = M2ua instance identifier
<c> = As instance identifier
<d> = Iid instance identifier
Details
Monitored Communications Protocol (MCP) Availability Alarm is raised when
there is a loss of communication between adjacent layers.
This alarm is cleared when the communication between the layers is restored.
Probable Cause
commSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
If the problem persists, the component should be deleted and then added back.
Mtp2 Alarms
Mtp2 Link Failure Alarm
Legend
<x> = Nsta instance identifier
<y> = Mtp2 instance identifier
Details
The Link Failure Alarm is raised by the Mtp2 component when an error occurs
on the link resulting in the link being taken out-of-service. The link failure can
be due to an error in the provisioning of the link, such as a bad timeslot, or a
physical connectivity problem.
The alarm is cleared when the link returns to service.
Probable Cause
applicationSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
Verify that the following conditions are met:
The InterfaceName attribute of the Nsta/<x> Vgs Mtp2/<y> component
points to the correct Chan component.
Physical connectivity is correct.
The Chan component that is linked to the Nsta/<x> Vgs Mtp2/<y> is in the
Enabled state.
Legend
<x> = Nsta instance identifier
<y> = Mtp2 instance identifier
Details
This alarm is raised by the Mtp2 component when the Mtp2 layer fails to
initialize properly. This can be caused by the internal hardware and software
problems on the card
The alarm is cleared when the initialization completes.
Probable Cause
applicationSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
The component should be deleted and then added back.
Legend
<a> = Nsta instance identifier
<b> = Mtp2 instance identifier
Details
Monitored Communications Protocol (MCP) Availability Alarm is raised when
there is a loss of communication between adjacent layers.
This alarm is cleared when the communication between the layers is restored.
Probable Cause
commSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
If the problem persists, the component should be deleted and then added back.
MgcIf Alarms
MgcIf Control Link Failure Alarm
Legend
<x> = Nsta instance identifier
<string> = 20 character string identifier
Details
The MgcIf Control Link Failure alarm is raised when the communication link
with the Media Gateway Controller (MGC) is determined to have failed. Such a
failure could be determined, for example, by the expiration of the inactivity
timer.
When the communication link is lost, the Media Gateway (MGW) is unable to
setup new calls. It can, in a limited way, handle the existing calls. However, it
does not know when to take down the calls until it re-establishes the connection
with the MGC.
Due to the significant impact it can have on the MGW, the severity of this alarm
is set to critical. The OSI Availability Status is set to a value of degraded while
the other OSI states remain unchanged.
The alarm is cleared when the control link is successfully re-established with an
MGC.
Probable Cause
underlyingResourceUnavailableCause_c
Type
processingType_c
Remedial action
Verify that the AtmIf component used to provide connectivity to the MGC is
enabled. Verify that the network used for transporting H.248 messages between
the MGC and MGW is functioning properly. Verify that the Nsta/n Vgs H248/0
maximumInactivityTime attribute is set to a reasonable value. This attribute is
initialized through H.248 messaging and is not provisionable. If the value is set
too low by the MGC, Control Link Failure's may result. If network latency is
preventing audit messages from arriving within the maximum inactivity time, the
MGC configuration should be set to a more reasonable maximum inactivity time.
Legend
<x> = Nsta instance identifier
<string> = 20 character string identifier
Details
The MgcIf Registration Failure Alarm is raised when the MgcIf component fails
to register the MGW with the MGC (MSC) after five registration attempts.
Registration failure is defined as follows:
1.When the MGC sends a NACK to the Mgc component after it receives a
registration request.
2.When a registration request is unacknowledged (timeout) and the Mgc
component has exhausted the provisioned maximumTransmissionRetries.
For example, if the maximumTransmissionRetries is set to two and the Mgc
component does not receive any acknowledgement message from the MGC, then
it will resend the registration message. If it still has not registered with the MGC
after two attempts due to timeout, then the number of failed registrations is
incriminated by one.
The alarm is cleared when the MgcIf component is successfully registered with
an MGC (MSC).
Probable Cause
underlyingResourceUnavailableCause_c
Type
processing
Remedial action
The 'Nsta/<n> Vgs H248/0 mgMid' attribute on the MGW matches the H248
MID expected by the MGC.
The 'Nsta/<n> Vgs MgcIf/<m> initialMgcAddress' and 'Nsta/<n> Vgs MgcIf/
<m> initialMgcPort' attributes on the MGW match the actual address and port at
which the MGC is configured to receive H248 messages.
Ensure that the 'Nsta/<n> Vgs Ctrl/mg' component provisioning matches the
address and port from which the MGC is expecting to receive messages from the
MGW. The MGC may verify that source address and port of initial messages
from the MGW to protect against an unauthorized MGW attempting to register.
Legend
<x> = Nsta instance identifier
<string> = 20 character string identifier
Details
The MgcIf Overload Alarm is raised when the message input queue exceeds the
MgcIf callRejectionLatencyThreshold attribute indicating that the MGC is over-
utilizing a given MGW. During an overload condition, Modify, Subtract, and
Audit requests are queued and handled as normal. Add requests for existing calls
are also handled. Add requests that result in the creation of a new context and
are not marked as an emergency or high-priority, are discarded.
The alarm is cleared when the input queue length has dropped below the MgcIf
callRejectionLatencyThreshold attribute for at least one minute.
Probable Cause
thresholdCrossedCause_c
Type
qualityOfServiceType_c
Remedial action
If overload alarm is seen frequently or for long periods of time, consider adding
more MGW capacity.
Legend
<x> = Nsta instance identifier
<string> = 20 character string identifier
Details
The MgcIf Resource Congestion Alarm is raised when the resource allocators
total call context congestion percentage level exceeds the MgcIf
congestionThreshold attribute.
The alarms severity changes as a function of the conditions percent given the
following ranges:
- warning: congestionAbatementThreshold+1 to congestionThreshold,
- minor: congestionThreshold+1 to 100%.
The alarm is cleared when the resource allocators total call context congestion
level is equal to or falls below the MgcIf congestionAbatementThreshold
attribute.
Probable Cause
thresholdCrossedCause_c
Type
qualityOfServiceType_c
Remedial action
Display the Nsta/<n> Vgs CallStatistics contextLoadPercent operational
attribute. If the MGWs call context utilization remains at 100% for extended
periods of time, the operator may wish to consider adding more MGW's to the
network. Depending on how the network is configured and how a MGC is
designed to function, this alarm, caused by call volume, may not be problematic.
It simply indicates that the MGW is fully utilized.
Legend
<x> = Nsta instance identifier
<string> = 20 character string identifier
Details
The MgcIf Throughput Congestion Alarm is raised when the resource allocators
throughput utilization percentage level exceeds the MgcIf congestionThreshold
attribute.
The alarms severity changes as a function of the conditions percent given the
following ranges:
- warning: congestionAbatementThreshold+1 to congestionThreshold,
- minor: congestionThreshold+1 to 100%.
The alarm is cleared when the resource allocators throughput utilization
percentage level is equal to or falls below the MgcIf
congestionAbatementThreshold attribute.
Probable Cause
thresholdCrossedCause_c
Type
qualityOfServiceType_c
Remedial action
Display the Nsta/<n> Vgs CallStatistics throughputLoadPercent operational
attribute. If the MGWs throughput remains at 100% for extended periods of
time, the operator may wish to consider adding more MGW's to the network or
consider increasing the use of bearer traffic compression. Depending on how the
network is configured and how a MGC is designed to function, this alarm, caused
by call volume, may not be problematic. It simply indicates that the MGW is
fully utilized.
Legend
<x> = Nsta instance identifier
<string> = 20 character string identifier
Details
The MgcIf Call Admission Control (CAC) Subnet Bandwidth Congestion Alarm
is raised when the CAC backbone bandwidth utilization percentage level exceeds
the MgcIf congestionThreshold attribute.
The text for the alarm will identify the subnet name that has exceeded the
congestion threshold.
The alarms severity changes as a function of the conditions percent given the
following ranges:
- warning: congestionAbatementThreshold+1 to congestionThreshold,
- minor: congestionThreshold+1 to 100%.
The alarm is cleared when the CAC backbone bandwidth utilization percentage
level is equal to or falls below the MgcIf congestionAbatementThreshold
attribute.
Probable Cause
thresholdCrossedCause_c
Type
qualityOfServiceType_c
Remedial action
Display the Nsta/<n> Vgs atmCac atmSubnet/<s> (or ipCac ipSubnet/s)
operational attributes where <s> identifies the subnet name from the alarm text.
If the MGWs currentPercentBandwidthUtil remains at 100% for extended
periods of time and connectionsRejected increases during this time, the
operator may wish to consider adding backbone bandwidth capability to the
network or consider increased use of bearer traffic compression. Depending on
how the network is configured and how a MGC is designed to function, this
alarm, caused by call volume, may not be problematic. It simply indicates that
the MGW is fully utilizing its allocated portion of the backbone bandwidth.
Mtp3 Alarms
Mtp3 Signaling Link Test Failed Alarm
Legend
<x> = Mtp3 instance identifier
<y> = linkset instance identifier
<z> = link instance identifier; z = 0 - 15
Details
The signaling link test failed message alarm is raised by an Mtp3 Link when the
Signalling Link Test (SLT) fails indicating that the Signalling Link Test
Controller (SLTC) has detected a bad link. Once a bad link is detected it will be
restarted.
Probable Cause
callEstablishmentErrorCause_c
Type
communicationsType_c
Remedial action
Monitor the bad link to ensure the link comes back into service.
Legend
<x> = Mtp3 instance identifier
<y> = linkset instance identifier
Details
The Destination Inaccessible Alarm is raised by the Mtp3/ Linkset component
when a destination (i.e. remote Mtp3) is inaccessible due to all links in the linkset
being inaccessible and the linkset is not part of a routeset (i.e. the linkset that
represents F-link). The destination is considered inaccessible when all links in
the linkset are either locked or disabled.
The alarm is cleared when a destination becomes accessible due to one or more
links in the linkset becoming accessible. The destination becomes accessible
when a locked linked becomes unlocked or a disabled link becomes enabled.
Probable Cause
localTransmissionErrorCause_c
Type
communicationsType_c
Remedial action
Links that are locked may be unlocked as appropriate. For disabled links, they
should be monitored to ensure the links come back into service.
Legend
<x> = Mtp3 instance identifier
<y> = routeset instance identifier
Details
The routeset destination inaccessible minor alarm is raised by the Mtp3/ Routeset
component when one or more routes to a destination are inaccessible.
The routeset destination inaccessible critical alarm is raised by the Mtp3/
Routeset component when all routes to a destination are inaccessible.
A route to a destination is considered inaccessible when the associated linkset is
unavailable or a transfer-prohibited message is received.
The transfer-prohibited message indicates that the signalling traffic toward a
particular destination cannot be transferred via the signalling transfer point
sending the message.
The alarm is cleared when all routes in the routeset become accessible.
A route is considered accessible when the associated linkset is available or a
transfer-allowed message is received.
The transfer-allowed message indicates that signalling traffic towards a
particular destination can be transferred via the signaling transfer point sending
the message.
Probable Cause
localTransmissionErrorCause_c
Type
communicationsType_c
Remedial action
LinkSets that are locked may be unlocked as appropriate. For disabled links in
the linkset, they should be monitored to ensure the links come back into service.
Legend
<a> = Mtp3 instance identifier
<b> = LinkSet instance identifier
<c> = Link instance identifier
Details
Monitored Communications Protocol (MCP) Availability Alarm is raised when
there is a loss of communication between adjacent layers.
This alarm is cleared when the communication between the layers is restored.
Probable Cause
applicationSubsystemFailureCause_c
commSubsystemFailureCause_c
probCauseUnknownCause_c
Type
communicationsType_c
Remedial action
If the problem persists, the component should be deleted and then added back.
SAAL-NNI Alarms
SaalNni Alignment Failure Alarm
7075 SaalNni/<x>
major/cleared set/clear
0300
Legend
<x> = SaalNni instance identifier
Details
The Alignment Failure alarm is raised by the SaalNni component when
alignment fails with the peer SaalNni layer.
The alignment fails when the operational attribute SaalNni/ currentProvingPdus
is lower than operational attribute SaalNni/ targetProvingPdus. If SaalNni
receives less than the expected value then there is a communication problem
which could be due to congestion.
When currentProvingPdus is equal to the targetProvingPdus, then the link is
working properly, since there was no loss of PDUS during the proving process.
The alarm is also raised whenever the SaalNni link goes down.
The alarm is cleared when alignment on the link completes successfully as a
result of increased bandwidth or the reduction of traffic.
Probable Cause
callEstablishmentErrorCause_c
Type
communicationsType_c
Remedial action
Verify the bandwidth is sufficient to support the link and increase it if necessary.
Verify the health of the physical connectivity (e.g. optical link or interface).
Q2630 Alarms
7075 Q2630/<x>
major message
0000
Legend
<x> = Q2630 instance identifier
Details
The Q2630 Initialization Failure Alarm is raised when the Q2630 layer cannot
successfully complete its initialization sequence. The Q2630 layer may fail to
initialize when it cannot perform initialization with the Q2630 Client on the VSP
SPM or cannot allocate required resources from memory on the PDC.
Probable Cause
commSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
The component should be deleted and then added back.
7075 Q2630/<x>
major message
0003
Legend
<x> = Q2630 instance identifier
Details
This alarm is raised when an Establish Request message is received and contains
a destination AESA that is different than the AESA that represents this Q2630
component. This indicates that the association between the received AESA and
the Point Code that supports this Q2630 component has been set improperly at
the sending protocol entity.
Probable Cause
callEstablishmentErrorCause_c
Type
communicationsType_c
Remedial action
Ensure that the AESA for this MGW is set correctly at the sending protocol
entity.
7075 Q2630/<x>
major message
0004
Legend
<x> = Q2630 instance identifier
Details
The Q2630 Remote Routing Error Alarm is raised when either of the following
conditions occurs:
1) The corresponding AESA could not be determined given the Point Code from
which a Q2630 message originated (e.g. the originating Point Code does not exist
in any Q2630 Peer Media Gateway Address provisioning for the MGW that
received the Q2630 message, and thus, the MGW is unable to determine from
which AESA the Q2630 message was sent).
2) The corresponding Point Code could not be determined given the AESA to
which a Q2630 message must be sent (e.g. the destination AESA does not exist
in any Q2630 Peer Media Gateway Address provisioning for the MGW
transmitting the Q2630 message or Mtp3b is not provisioned with the destination
Point Code).
Probable Cause
callEstablishmentErrorCause_c
Type
communicationsType_c
Remedial action
Verify that the Q2630/ PeerAddr/ component exists and is provisioned with the
correct point code for the remote AESA.
Legend
<a> = Q2630 instance identifier
Details
Monitored Communications Protocol (MCP) Availability Alarm is raised when
there is a loss of communication between adjacent layers.
This alarm is cleared when the communication between the layers is restored.
Probable Cause
commSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
If the problem persists, the component should be deleted and then added back.
Legend
<a> = Q2630 instance identifier
Details
Monitored Communications Protocol (MCP) Availability Alarm is raised when
there is a loss of communication between adjacent layers.
This alarm is cleared when the communication between the layers is restored.
Probable Cause
commSubsystemFailureCause_c
Type
communicationsType_c
Remedial action
If the problem persists, the component should be deleted and then added back.
VSP4e Alarms
VSP4e CarrierCard Temperature Alarm
Legend
<num> = 0 - 15
Details
The VSP4e CarrierCard Temperature alarm is raised with a severity of major
when the temperature measured by the sensors on the VSP4es carrier card
exceeds the value specified by the failureTemperatureThreshold attribute.
The alarm is raised with a severity of warning, when the temperature measured
exceeds the value specified by the warningTemperatureThreshold attribute.
The alarm severity is lowered from major to warning when the temperature
measured falls three degrees below the value specified by the
failureTemperatureThreshold attribute.
The alarm is cleared when the temperature measured falls three degrees below
the value specified by the warningTemperatureThreshold attribute.
Probable Cause
equipmentFailureCause_c
Type
equipmentType_c
Remedial action
Verify that the shelf fans are working properly. Verify that the air temperature
inside of the shelf is within normal limits. Verify that the air filter is clean.
Legend
<num> = 0 - 15
Details
The VSP4e CarrierCard Sensor Failure alarm is raised when an error is returned
while attempting to read the temperature from the carrier cards thermal sensors.
The alarm is cleared on the next successful attempt.
Probable Cause
equipmentFailureCause_c
Type
equipmentType_c
Remedial action
The component should be deleted and then added back.
Legend
<num> = 0 - 15
Details
The VSP4e CarrierCard DSP Failure Alarm is raised when there is reduction of
DSP resources on the VSP4e Carrier Card. The card continues to run with
degraded capacity.
Probable Cause
equipmentFailureCause_c
Type
equipmentType_c
Remedial action
The component should be deleted and then added back. If the problem persists,
run diagnostics.
This component data model is based on the Nortel PVG product component
data model with additional components and attributes described next.
Nsta/x Vgs 3
The CDL hierarchy below shows new and modified components introduced
in the MG18 software release.
Figure 3-1
CDL Hierarchy for Nsta/x Vgs
Nsta/n link to
Vsp
link to
Chan
Vgs
MgcIf/
AtmTConn/n CasDef/n Tag/n TProf/n H248 Aal2Svc CallStats AtmCac
primary
AtmSubnet/
Aap Pap Cas Tag Prof/n TConn/n <name>
Vp/n
User
SpvcAp
DS0/n
New component
Table 3-1
Nsta/x Vgs CDL components summary
New Dynamic Nsta/x Vgs CallStats This component represents 1 per Vgs No
the statistics for calls handled
by this Vgs component.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
Modified Nsta/x Vgs Aal2Svc This component creates and 1 per Vgs No
Optional enables the Asynchronous
Transfer Mode Adaptation
Layer 2 (AAL2) Switched
Virtual Circuit (SVC) service.
New Dynamic Nsta/x Vgs Aal2Svc This dynamic component 0 to 4096 per No
TConn/n provides visibility for all Aal2Svc
automatically created
Switched Virtual Circuits
(SVCs).
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs AtmCac This component represents 0 or 1 per Vgs No
the Asynchronous Transfer
Mode (ATM) Call Admission
Control (CAC) application.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
On Multiservice Switch
(formerly known as Passport)
7000, a maximum of 1022
AtmTrunkConnection
components may be
provisioned for Vsp2 cards
and a maximum of 127
AtmTrunkConnection
components may be
provisioned for 12mVspAal
cards. On Multiservice Switch
15000 up to 2700
AtmTrunkConnection
components may be
provisioned.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs Tag/y This component represents a 84 per Lp Yes
group of TDM timeslots in a (DS1)
TDM primary rate stream
associated with this VSP, and 63 per Lp (E1)
relates them to a processing
profile.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
Up to 31 instances of this
component are created based
on the trunk type, E1 can
have 31 instances and T1 can
have 24 instances.
New Optional. Nsta/x Vgs Tag/y This component ties a service 0 to 1 per Tag No
TagUser to a specific Tag, and hence
(Note: This is the set of timeslots
marked as associated with it. The
optional but it absence of this component
must be means that the services can
provisioned be applied to all the Tags.
manually. The
reason for this
is that it can not
be added
automatically
as a required
component
since the user
needs to set
the
linkToProfile
attribute which
can not be auto
populated.)
Table 3-1
Nsta/x Vgs CDL components summary (continued)
A separate VoiceProfile
component must be
provisioned for each codec.
New Optional Nsta/x Vgs Vp/n This component represents 0 to 1 per Vp Yes
MultiParty the Conferencing and Lawful
Intercept Distribution
Function capabilities of the
Media Gateway.
New Optional Nsta/x Vgs Vp/n This component represents a 1 per instance No
TdmToPktProfile profile of the packet-side of Vp
(Note: This is characteristics of calls
marked as handled by Nsta/x Vgs.
optional but if
the
externalInterfac
eType attribute
of the Vp/n is
set to pstn or
aIf then the
TdmToPktProfil
e component
must be added
under the Vp/
n.)
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs Vp/n This component represents a 1 per instance No
PktToPktProfile profile of the AAL2 AAL2 of Vp
(Note: This is call characteristics of Nsta/x
marked as Vgs. This component is used
optional but if only for packet-packet Media
the gateways.
externalInterfac
eType attribute
of the Vp/n is
set to iuIf or
nbIf then the
PktToPktProfile
component
must be added
under the Vp/
n.)
New Optional Nsta/x Vgs Vp/n Agc This component represents 0 to 1 per Vp No
enabling of the Automatic
Gain Control (AGC) voice
quality feature for this Voice
Profile.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs Vp/n Bnc This component represents 0 to 1 per Vp No
the enabling of the
Background Noise
Conditioning (BNC) voice
quality feature for this Voice
Profile, and the configuration
parameters needed by this
feature.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs Vp/n Bnr This component represents 0 to 1 per Vp No
the enabling of the
Background Noise Reduction
(BNR) for this voice profile.
BNR is a technique
developed to adoptively filter
noisy speech signal that
originates from mobile
terminals immersed in an
environment with background
noise. The background noise
is filtered or reduced after the
decoding at the Media
Gateway. BNR enhances the
perceived quality of the
speech signal by reducing the
background noise content.
This voice quality feature is
only applicable for UMTS.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs Vp/n Gtt This component represents 0 to 1 per Vp No
enabling of the Global Text
Telephony (GTT) voice quality
feature for the profile
associated with this
VoiceProfile component, and
the configuration parameters
needed by this feature.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs M2ua This component represents 0 to 1 per Vgs Yes
the Message Transfer Part
Layer 2 User Adaptation
(M2UA) layer.
New Optional Nsta/x Vgs M2ua This component represents 0 to 8 per Yes
AS/n the peer Application Server M2ua
(AS) that establishes a
Stream Control Transmission
Protocol (SCTP) association
with this Message Transfer
Part Layer 2 User Adaptation
(M2UA) application.
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs M2ua This component represents 0 to 1 per AS Yes
AS/n Asp/m the peer Application Server
Process (ASP) that
establishes a Stream Control
Transmission Protocol
(SCTP) association with this
Message Transfer Part Layer
2 User Adaptation (M2UA)
application.
New Dynamic Nsta/x Vgs M2ua This component represents a 1 per Asp No
AS/n Asp/m Stream Control Transmission
SctpAssoc Protocol (SCTP) association
between this Message
Transfer Part Layer 2 User
Adaptation (M2UA)
application and the peer
Application Server Process
(ASP).
Table 3-1
Nsta/x Vgs CDL components summary (continued)
New Optional Nsta/x Vgs Mtp2/n This component represents 0 to 4 per Vgs Yes
the Message Transfer Part
Layer 2 (MTP2) transport
layer between the Media
Gateway and either the
Public Switched Telephone
Network (PSTN) or the 2G
Radio Access Network
(RAN).
Table 3-2
Aal2Svc Profile attribute details
Table 3-2
Aal2Svc Profile attribute details
Table 3-2
Aal2Svc Profile attribute details
The constantBitRate
service category is
intended for real time
applications, that is
those requiring tightly
constrained delay and
delay variation, as
would be appropriate
for voice and video
applications. The
consistent availability
of a fixed quantity of
bandwidth is
considered appropriate
for constant bit rate
service.
The rtVariableBitRate
service category is
intended for real time
applications, that is
those requiring tightly
constrained delay and
delay variation, as
would be appropriate
for voice and video
applications. Sources
are expected to
transmit at a rate
which varies with time.
Equivalently, the
source can be
described as "bursty".
The real-time variable
bit rate service may
support statistical
multiplexing of real
time sources.
Table 3-2
Aal2Svc Profile attribute details
This attribute is
obsoleted in MG18.0.
This attribute is
obsoleted in MG18.0.
Table 3-2
Aal2Svc Profile attribute details
This attribute is
obsoleted in MG18.0.
Table 3-2
Aal2Svc Profile attribute details
Table 3-2
Aal2Svc Profile attribute details
Table 3-2
Aal2Svc Profile attribute details
If svcPreCreation is
enabled then an SVC
setup is initiated when
the bandwidth
available in existing
Virtual Circuit
Connections (VCCs)
between two Network
Service Access Point
(NSAP) addresses is
down to a level such
that a new SVC would
be required for the
next call.
Table 3-3
AtmSubnet attribute details
Table 3-3
AtmSubnet attribute details
A new connection
attempt is rejected if
adding the new
connection would
exceed the bandwidth
limit.
Table 3-4
AtmTConn attribute details
Table 3-5
MgcIf attribute details
Table 3-5
MgcIf attribute details
shortText - a short,
space efficient format,
suitable for machine
asn1Ber - ASN.1
binary encoded format,
faster than text format
but less readable.
Table 3-5
MgcIf attribute details
Table 3-5
MgcIf attribute details
Table 3-5
MgcIf attribute details
Table 3-5
MgcIf attribute details
Table 3-5
MgcIf attribute details
Table 3-5
MgcIf attribute details
Q2630 3
The CDL hierarchy for Q2630 is shown below.
Figure 3-2
CDL Hierarchy for Q2630
(root)
AtmTConn/n MCP
SpvcAp PathOwner
Aap Pap
Existing component
inter-component link
Modified component
New component
CDL Notes:
For readability, only the ServiceIndicator (ServInd) subcomponent is
shown under Mtp3 in the diagram; Mtp3 has other subcomponents such
as SS7Linkset. These are described in the next section.
Only AtmTConn is shown under Nsta/n Vgs. The Nsta/n Vgs component
details were described in the previous section.
The resetRequestRetries provisionable attribute under Q2630 has been
taken out from the MGW.
Table 3-6
Q2630 PeerAddress attributes
No Default.
Table 3-6
Q2630 PeerAddress attributes (continued)
No Default.
MTP3 3
The figure below shows the CDL hierarchy for MTP3, including its
relationship with SAAL-NNI and Q2630. MTP3 in the MG18 software
release supports routesets. It also supports a component link with SAAL
rather than using provisioned IP addresses and ports. This makes it consistent
with SIGTRAN. Since MTP3 serves only a single VSP card (for Iu or Nb
ALCAP signaling), there is no need to spread its SAAL links across shelves.
Figure 3-3
CDL Hierarchy for MTP3 CDL
(root)
link to link to
AtmIf/n SaalNni/n Lp/n Gips/n Mtp3/n Dlep/n Q2630/n
(other Q2630
subcomponents not shown)
Mcp Udp
Nep Route/n
Port/n
Link/n RInfo
MCP
Existing Component
Ls Linkset
New Component Rs Routeset
Mcp MonitoredCommunicationProtocol
Nap NailedUpAdaptationPoint
Modified Component Nep NailedUpEndPoint
Hardware Link
ServInd ServiceIndicator
Dynamic Component Software Link Vcc VirtualChannelConnection
Table 3-7
MTP3 attributes
Table 3-7
MTP3 attributes (continued)
A routeset is a grouping of
routes that are used to
transfer signalling between
this node and a specific
destination signalling point.
Routes under this
component represent quasi-
associated links (A-links).
SAAL-NNI Provisioning 3
SaalNni is an existing component representing a SAAL-NNI link that lives on
an ATM I/O card. SaalNni is linked to a nailed-up ATM AAL5 VCC.
Previously SaalNni was also linked to an MTP3 link by means of a
provisioned IP address and UDP port. On the Wireless Gateway, it was not
possible to use a component link because SAAL can reside on a different
shelf from MTP3. Links were spread across multiple shelves to ensure that
some links (at least one) in a linkset remained active during an upgrade.
Component links are much more user-friendly, and they are possible in the
MG18 software release because SAAL always resides in the same shelf as its
layer-3 entity. With signaling backhaul it is still possible to spread links
across shelves, but each link is handled entirely inside one shelf. MTP3 on the
USP communicates with links on multiple MGW shelves.
Table 3-8
SAAL-NNI attributes
Table 3-8
SAAL-NNI attributes
ATTENTION
Always read the latest GSM/UMTS MGW Release Notes before
applying patches or performing a software upgrade.
The MGW Release Notes, published by Nortel for each Media Gateway
software release, contains important information about the current
software loadname (application version), the applicable software patch
baseline, and special instructions you need to know for the current
software release.
Assumptions
The following assumptions apply:
All patches should be set up for download into the SDS /software directory.
Prior to downloading patches, the SDS should be set up as described in NTP
NN10600-270, Multiservice Switch 7400, 15000, 20000 Software
Installation, which has information about the SDS and its directory structure.
Prior to downloading the patch application software from the web site, the
SDS should be configured as described in NTP NN10600-270, Multiservice
Switch 7400, 15000, 20000 Software Installation. One SDS site should be
used for all patch downloads for a particular load. This will prevent
previously downloaded patches from being removed.
An individual patch consists of a package of the new code and the mechanism
to modify the existing code, and a patch description file. The patch
description file is a text file that provides specific instructions for applying
the patch.
ATTENTION
Each patch is delivered with release notes that should be read in their
entirety before application. Some patches do disrupt call processing
capabilities and require specific application procedures (shedding
existing traffic, applying the patch, etc.). Failure to perform the
procedures as outlined in the instructions for each patch can result in
abnormal call termination. Furthermore, patches should only be applied
in the network operators maintenance window when traffic levels are
relatively low.
Some patch applications may require a reset of the CP cards. These patch
applications should be performed during a maintenance window when call
volumes are relatively low.
Commands are shown in bold print and the resulting outputs are shown in
regular print (not bolded). In both procedures the example outputs are
captured from a Media Gateway that has software base load MI009DB.
Procedure 4-1
General instructions for downloading and applying MGW patches
Step Action
1 Locate the patch application in the SDS /software directory. The patch
application is stored as a compressed tar file (.tar.Z). The filename is in
the form of patch_<application version>.
zrc2h0p7> cd /software
zrc2h0p7> ls
patch
patch_MI009DB.tar.z
sheet 1 of 6
Procedure 4-1
General instructions for downloading and applying MGW patches (continued)
Step Action
3 Untar the file in the SDS /software directory with the tar -xvf command.
zrc2h0p7> ls
patch
patch_MI009DB.tar
x. /patch/MI009DB/baseQ01331876_MI009DB.pd, 1733
bytes, 4 tape blocks
.
.
.
x. /patch/MI009DB/ppc/b01331876p_MI009DB.o, 8228
bytes, 17 tape blocks
.
.
.
The tar command creates the appropriate directories and extracts the
files into them. In the example above, the tar command creates directory
~/patch/MI009DB/ppc/ and places in it the patch executables (*.o),
beginning with file baseQ01331876_MI009DB.pd. Similarly, the tar
command creates directory ~/patch/MI009DB and places in the directory
the patch description (*.pd) files. In this example, the first patch
description file is b01331876p_MI009DB.o.
4 Review the patch description files (*.pd) found in the directory ~/patch/
<application version>. In the example above, this is directory ~/patch/
MI009DB. The patch description files are text files.
Specific patch application instructions will be documented in the patch
description files, and procedures to follow if a particular patch is disruptive
and requires a card reset to take affect.
5 Go to the patch executables directory and display the checksum value for
each patch executable (*.o), using the cksum command.
zrc2h0p7> cd ~/patch/MI009DB/ppc
zrc2h0p7> cksum b01331876p_MI009DB.o
Compare and verify that the output value of the cksum command of each
patch executable is the same as the checksum value provided in the
corresponding patch description file under the Patched File Checksum
section.
sheet 2 of 6
Procedure 4-1
General instructions for downloading and applying MGW patches (continued)
Step Action
Sw dld
ok 2004-05-26 16:48:41.87
> d sw dld
Sw Dld
avBeingDownloaded =
status = inactive
filesToTransfer = 0
avListToDownload = patch_MI009DB
downloadedAvList =
processorTargets = i960 ppc
9 Download the patches using the start command. This will download all
the Media Gateway patches available on the SDS for the current software
release. The start command has the following format:
start -h(<ip_address>) -u(<login_id>) -p(<password>) sw dld
For example,
> start -h(47.255.255.255) -u(special) -p(password) sw dld
sheet 3 of 6
Procedure 4-1
General instructions for downloading and applying MGW patches (continued)
Step Action
10 Verify that the patches have been downloaded to the Media Gateway. For
example,
> list sw av/patch_MI009DB patch/*
Sw Av/PATCH_MI009DB Patch/baseQ01331876
Sw Av/PATCH_MI009DB Patch/baseQ01106238
Sw Av/PATCH_MI009DB Patch/mgwQ01291823
Sw Av/PATCH_MI009DB Patch/pvgQ01239145
Sw Av/PATCH_MI009DB Patch/pvgQ01247410
Sw Av/PATCH_MI009DB Patch/pvgQ01249258
Sw Av/PATCH_MI009DB Patch/pvgQ01282827
Sw Av/PATCH_MI009DB Patch/pvgQ01289101
Sw Av/PATCH_MI009DB Patch/pvgQ01328729
11 Once the download has completed, the patches are ready to be applied.
Each patch will have instructions in its patch description file (*.pd) on how
to apply the patch. You must read these instructions and follow them
exactly when applying the patch.
sheet 4 of 6
Procedure 4-1
General instructions for downloading and applying MGW patches (continued)
Step Action
12 If you have read the instructions and have the switch in a state ready to
apply a patch, you can execute the following commands to apply a patch.
Note that the patch identifier on the MGW is the downloaded file name
less the _<application version> extension, in this case _MI009DB.
The following commands show the application of one patch.
>set sw patch baseQ01331876
>display -p sw
Sw
avList = base_MI009DB,ip_MI009DB,
networking_MI009DB,atmNetworking_MI009DB,
wanDte_MI009DB,pvg_MI009DB,
genericUtilities_MI009DB,wirelessCommon_MI009DB,
ss7_MI009DB,mediaGateway_MI009DB,
fabric_MI009DB,aal1Ces_MI009DB,
patch_MI009DB
patchList = baseQ01331876
sheet 5 of 6
Procedure 4-1
General instructions for downloading and applying MGW patches (continued)
Step Action
Check with local office policy regarding file naming conventions for the
saved view. Follow the existing convention.
Prov
adminState = unlocked
operationalState = enabled
...
...
...
committedFileName = G6001CF_lockdown.full.002
currentViewFileName = G6001CF_lockdown.full.002
...
...
...
editViewName = G6001CF_lockdown.full.002
sheet 6 of 6
Each MGW patch includes a patch description file with specific instructions.
For patch pvgQ01328729, the patch description file contains the following
warning:
In this example activating the patch requires a shelf reset. To minimize the
impact to network traffic, the network traffic is routed away from the shelf
during the patch application. The patch must only be applied to one shelf at a
time.
.
Procedure 4-2
Example of a MGW patch that requires a shelf reset, pvgQ01328729
Step Action
Sw Av/PATCH_MI009DB Patch/baseQ01331876
Sw Av/PATCH_MI009DB Patch/baseQ01106238
Sw Av/PATCH_MI009DB Patch/mgwQ01291823
Sw Av/PATCH_MI009DB Patch/pvgQ01239145
Sw Av/PATCH_MI009DB Patch/pvgQ01247410
Sw Av/PATCH_MI009DB Patch/pvgQ01249258
Sw Av/PATCH_MI009DB Patch/pvgQ01282827
Sw Av/PATCH_MI009DB Patch/pvgQ01289101
Sw Av/PATCH_MI009DB Patch/pvgQ01328729
+====+--------+--------+------+---------+----------+----------+-----------+----------+
| Nsta | MgcIf | osiAd | osiO| osiUs | osiAvai | osiProc | osiCntr | osiAlar |
| | | min | per | age | l | | l | m |
+====+--------+--------+------+---------+----------+----------+-----------+----------+
| 9| 0 | unlck | ena | idle | | | | |
| 12 | 0 | unlck | ena | idle | | | | |
| 13 | 0 | unlck | ena | idle | | | | |
sheet 1 of 4
Procedure 4-2
Example of a MGW patch that requires a shelf reset, pvgQ01328729 (continued)
Step Action
3 Lock all the MgcIf components. This will route new calls away from the
shelf being upgraded.
Use the information from the previous step to identify the Nsta and
MGCIF values,
where x is the Nsta instance
Under Trunks in the alarm banner, several alarms will appear for the
MGW due to the cards being locked. This is expected and normal while
the cards are locked. If the alarms do not clear after unlocking the cards,
contact the next level of support for assistance.
4 Verify that the osiAdmin state is locked for each Nsta Vgs Mgcif
component.
> d Nsta/* Vgs MgcIf/* osistate
+====+--------+---------+
| Nsta | MgcIf | osiAd |
| | | min |
+====+--------+---------+
| 9| 0 | locked |
| 12 | 0 | locked |
| 13 | 0 | locked |
5 Wait until activeContexts under all NSTA/ VGS instances is zero (no calls
are active), or until the number of calls active has diminished to an
acceptable level, per local office policy.
> d nsta/<x> vgs activeContexts
Nsta/x Vgs
activeContexts = 0
sheet 2 of 4
Procedure 4-2
Example of a MGW patch that requires a shelf reset, pvgQ01328729 (continued)
Step Action
In the example above, two patches are removed (using a tilda ~ before
the patch name) per the instructions included in the patch description file
of patch pvgQ01328729.
7 The following alarm will be generated upon patch application for all
MGCIF components.
Nsta/ Vgs MgcIf/; 2006-03-10 12:12:21.88
SET minor qualityOfService thresholdCrossed 70567004
ADMIN: locked OPER: disabled USAGE: idle
AVAIL: PROC: CNTRL:
ALARM: minor STBY: notSet UNKNW: false
Id: 0C000074 Rel:
Com: Congestion = 100%
Int: 12/0/2/8615; vgsOoa_NSTA_DCS.cc; 363; MI009DB
8 Once all the Admin: locked alarms have appeared (one for each
MGCIF), Unlock each MGCIF component using the following command:
9 > unlock nsta/<x> vgs mgcif<y>
sheet 3 of 4
Procedure 4-2
Example of a MGW patch that requires a shelf reset, pvgQ01328729 (continued)
Step Action
10 Wait until the following alarm is generated for all MGCIF components. It
may take several minutes before this alarm is generated.
Nsta/ Vgs MgcIf/; 2006-03-10 12:20:13.04
CLR cleared qualityOfService thresholdCrossed 70567004
ADMIN: unlocked OPER: disabled USAGE: idle
AVAIL: PROC: CNTRL:
ALARM: STBY: notSet UNKNW: false
Id: 0C000076 Rel:
Com: Congestion Level <= 70%
Int: 12/0/2/8615; vgsOoa_NSTA_DCS.cc; 363; MI009DB
11 After all the MGCIF instances are reported unlocked, execute the
following commands to confirm, save and commit the provisioning view.
prov> confirm prov
prov> save -f(<prov_filename>) -ascii -portable pr
prov> commit prov
prov> end prov
Check with local office policy regarding file naming conventions for the
saved view. Follow the existing convention.
sheet 4 of 4
ATTENTION
Removing a patch may result in a card reset, which could be service
impacting. Follow all the instructions given in the patch description file
for the removal of the patch.
Procedure 4-3
Example of removing a MGW patch
Step Action
Sw
avList = base_MI009DB,ip_MI009DB,
networking_MI009DB,atmNetworking_MI009DB,
wanDte_MI009DB,pvg_MI009DB,
genericUtilities_MI009DB,wirelessCommon_MI009DB,
ss7_MI009DB,mediaGateway_MI009DB,
fabric_MI009DB,aal1Ces_MI009DB,
patch_MI009DB
patchList =
Check with local office policy regarding file naming conventions for the saved view. Follow
the existing convention.
5 End provisioning.
> end prov
Because the procedures invoke a reset of the CP cards, the upgrade should
only be performed during a maintenance window when call volumes are
relatively low.
Preparations
Familiarity with the Multiservice Switch (MSS) 15000, and with the GSM/
UMTS network, is required to perform the procedures. It is strongly
recommended that this method be read in its entirety before starting any of
the operations contained in it.
ATTENTION
Always read the latest GSM/UMTS MGW Release Notes before
applying patches or performing a software upgrade.
The MGW Release Notes, published by Nortel for each Media Gateway
software release, contains important information about software
loadnames (application versions), applicable software patches, and
special instructions that you need to know for the current software
release.
Procedure conventions
Throughout the procedures that follow, the following writing conventions are
maintained:
IP and ATM addressing: All IP and ATM addresses used in this document
are for reference only. Refer to the customer specific CIQ data for
information regarding actual IP and ATM values.
Software Version: This document uses the following notation
<SoftwareVersion> wherever a specific software version should be
referenced. Refer to the MGW18 Release Notes to determine which
Software Version should be used.
Card and Application references: All references to card locations and
applications associated with the card within the shelf are to be used as
examples only. Refer to the CIQ for information regarding actual cards
and associated applications.
Other component and attribute values: The document uses the following
notation component/instance and attribute value wherever the CIQ
should be referenced. All of the instance and attribute values used in this
document are examples only. Refer to the CIQ for the actual values.
Sequence of steps
The following procedures should be followed, in the order given, to perform
an MNCL software upgrade:
Prepare to download the software to the MGW shelf
Download the software to the MGW shelf
Set the software download application version list (AVL)
Verify and save the provisioning file
Perform and monitor the software download
Route calls away from the MGW shelf
Activate the new software on the MGW shelf
Set the software AVL to the downloaded software
Activate the software and save the provisioning view
Note: For more SDS workstation setup details, refer to NTP NN10600-
270, Multiservice Switch 7400, 15000, 20000 Software Installation.
Procedure 4-4
Identify Software on a MGW Shelf
Step Action
If the file system does not have enough available space, remove any unused
software and provisioning files, using the information gathered in the
previous procedure, Procedure 4-4. The tidy and synchronize commands
may be needed to remove unneeded files. Refer to NTP NN10600-550,
Nortel Multiservice Switch 7400/15000/20000 Common Configuration
Procedures, subsection Disk full conditions.
Procedure 4-5
Verify and save the provisioning view on a MGW shelf
Step Action
3 Save the current provisioning view. Check with local office policy
regarding file naming conventions. Follow the existing convention.
(shelf)PROV>save -f(<prov_filename>) -ascii -portable pr
Procedure 4-6
Set software download AVL on a MGW shelf
Step Action
For the MGW, the command will be similar to the following example.
Refer to the MGW18 Release Notes for the software version.
(MGW)>set sw dld avl ! base_<SoftwareVersion>
ip_<SoftwareVersion> networking_<SoftwareVersion>
atmNetworking_<SoftwareVersion> wanDte_<SoftwareVersion>
pvg_<SoftwareVersion> genericUtilities_<SoftwareVersion>
wirelessCommon_<SoftwareVersion> ss7_<SoftwareVersion>
mediaGateway_<SoftwareVersion> fabric_<SoftwareVersion>
aal1Ces_<SoftwareVersion> patch_<SoftwareVersion>
Attention: The bang (!) above clears any existing applications that were
previously stored in the avListToDownload variable. Removing the bang
causes the list of applications to be appended to the avListToDownload
variable.
Procedure 4-7
Perform and monitor a software download on a MGW shelf
Step Action
Wait until the download is complete before proceeding to the next step.
Note: You may press the Enter key to get the prompt back while waiting
for the download to complete.
Sw Dld
avBeingDownloaded = <SoftwareVersion>
status = active
filesToTransfer = 555
avListToDownload = base_<SoftwareVersion>
ip_<SoftwareVersion> networking_<SoftwareVersion>
atmNetworking_<SoftwareVersion
wanDte_<SoftwareVersion> pvg_<SoftwareVersion>
genericUtilities_<SoftwareVersion>
wirelessCommon_<SoftwareVersion> ss7_<SoftwareVersion>
mediaGateway_<SoftwareVersion>
fabric_<SoftwareVersion> aal1Ces_MI009DB
patch_<SoftwareVersion>
sheet 1 of 2
Procedure 4-7
Perform and monitor a software download on a MGW shelf (continued)
Step Action
3 Continue to monitor the download until the files to transfer reaches zero
and the AV list to download is blank, as shown below
(shelf)>d sw dld
Sw Dld
avBeingDownloaded =
status = inactive
filesToTransfer = 0
avListToDownload =
downloadedAvList = base_<SoftwareVersion>
ip_<SoftwareVersion> networking_<SoftwareVersion>
atmNetworking_<SoftwareVersion
wanDte_<SoftwareVersion> pvg_<SoftwareVersion>
genericUtilities_<SoftwareVersion>
wirelessCommon_<SoftwareVersion> ss7_<SoftwareVersion>
mediaGateway_<SoftwareVersion>
fabric_<SoftwareVersion> aal1Ces_MI009DB
patch_<SoftwareVersion>
Sw Av/base_<SoftwareVersion>
Sw Av/ip_<SoftwareVersion>
Sw Av/networking_<SoftwareVersion>
Sw Av/atmNetworking_<SoftwareVersion>
Sw Av/wanDte_<SoftwareVersion>
Sw Av/pvg_<SoftwareVersion>
Sw Av/genericUtilities_<SoftwareVersion>
Sw Av/wirelessCommon_<SoftwareVersion>
Sw Av/ss7_<SoftwareVersion>
Sw Av/mediaGateway_<SoftwareVersion>
Sw Av/fabric_<SoftwareVersion>
Sw Av/aal1Ces_<SoftwareVersion>
Sw Av/patch_<SoftwareVersion>
sheet 2 of 2
Procedure 4-8
Route calls away from the MGW shelf
Step Action
+====+--------+--------+------+---------+----------+----------+-----------+----------+
| Nsta | MgcIf | osiAd | osiO| osiUs | osiAvai | osiProc | osiCntr | osiAlar |
| | | min | per | age | l | | l | m |
+====+--------+--------+------+---------+----------+----------+-----------+----------+
| 9| 0 | unlck | ena | idle | | | | |
| 12 | 0 | unlck | ena | idle | | | | |
| 13 | 0 | unlck | ena | idle | | | | |
2 Lock all the MgcIf components. This will route new calls away from the
shelf being upgraded.
Use the information from the previous step to identify the Nsta and
MGCIF values,
where x is the Nsta instance
Under Trunks in the alarm banner, several alarms will appear for the
MGW due to the cards being locked. This is expected and normal while
the cards are locked. If the alarms do not clear after unlocking the cards,
contact the next level of support for assistance.
sheet 1 of 2
Procedure 4-8
Route calls away from the MGW shelf (continued)
Step Action
3 Verify that the osiAdmin state is locked for each Nsta Vgs Mgcif
component.
> d Nsta/* Vgs MgcIf/* osistate
+====+--------+---------+
| Nsta | MgcIf | osiAd |
| | | min |
+====+--------+---------+
| 9| 0 | locked |
| 12 | 0 | locked |
| 13 | 0 | locked |
4 Wait until activeContexts under each NSTA/ VGS instances is zero (no
calls are active), or until the number of calls active has diminished to an
acceptable level, per local office policy.
> d nsta/<x> vgs activeContexts
Nsta/x Vgs
activeContexts = 0
sheet 2 of 2
Procedure 4-9
Set softwareAVL on the MGW shelf
Step Action
3 Display the software application version list (AVL) to verify that the
desired software is set.
(shelf)PROV > d sw avl
Sw
The example above shows that software version MI009DB has been set
for the application version list.
Attention: The bang (!) above clears any existing applications that were
previously stored in the avList. Removing the bang causes the list of
applications to be appended to the avListT.
Procedure 4-10
Activate the new software on the MGW shelf
Step Action
Procedure 4-11
Route calls back to the upgraded MGW shelf
Step Action
2 Once all the Admin: locked alarms have appeared (one for each
MGCIF), Unlock each MGCIF component using the following command:
(shelf)PROV> unlock nsta/<x> vgs mgcif<y>
3 Wait until the following Admin: unlocked alarm has been generated for
each MGCIF component. It may take several minutes before all the
alarms appear.
Nsta/ Vgs MgcIf/; 2006-03-10 12:20:13.04
CLR cleared qualityOfService thresholdCrossed 70567004
ADMIN: unlocked OPER: disabled USAGE: idle
AVAIL: PROC: CNTRL:
ALARM: STBY: notSet UNKNW: false
Id: 0C000076 Rel:
Com: Congestion Level <= 70%
Int: 12/0/2/8615; vgsOoa_NSTA_DCS.cc; 363; MI009DB
Procedure 4-12
Save the provisioning view on the MGW shelf
Step Action
1 Save the current provisioning view. Check with local office policy
regarding file naming conventions. Follow the existing convention.
(shelf)PROV>save -f(<prov_filename>) -ascii -portable pr
The MGW health checks are given in the following sections of this document:
Check the health of the network from the MSC
Check the overall health of the MGW shelf
Procedure 4-13
Check the health of the network from the MSC
Step Action
PRODUCT: GMSO.180
LOAD: GMSO0.180
LAYER: BAS.21.0.CQ
LAYER: TL.20.0.CQ
LAYER: SHR.20.0.AA
LAYER: GSM.18.0.CV
2 Check the current SWER counts. The numbers will not be zero.
>logutil
(logutil)>open swer
00C9A4FC=GLOGTIDI.CC01:FREE_LOG+#02BC
00C9CE64=GLOGTIDI.CC01:GLOGTID_VS+#0064
03779B88=CPENCUI.CR02:DRIVER_P+#0588
04D6D9D4=XACALLP.CH08:CALL_PROCESS_+#0254
...
...
...
sheet 1 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
3 Check the current TRAP counts. The numbers will not be zero.
(logutil)>open trap
Traceback:
017FEBC0=AISPPRMI.AY01:AIP_ISUP_GA+#0020
017F0CD8=AISPAFEI.BK01:ADD_ISUP_IAM_P+#0238
...
...
...
sheet 2 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
4 Display the thirty day history of call success ratios. Use the results for
comparison against the snapshot of current call statistics obtained in the
next step.
(omsnapshot)>dumpstats_all
*************************************
SUCCESS STATS OF MS to MS
(Below values are in %)
*************************************
TIME
DATE | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 00
------------------------------------------------------
|
05/02 | 77 73 76 72 69 78 85 82 80 78 79 80 79 79 80 82
82 82 82 81 78 78 75 75
|
05/01 | 70 74 67 66 77 81 85 83 80 77 79 81 80 80 79 81
82 82 82 80 77 76 74 70
...
...
...
sheet 3 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
(omsnapshot)>omratios all
sheet 4 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
...
...
...
sheet 5 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
VLR:
Total
-----
Population : 922337 MS Next TMSI :
1849919503
CM Only
-------
...
...
...
sheet 6 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
9 Check the status of the MMUs. Note their current states and call counts.
>mmuselect; pool
...
...
...
10 Verify that no MSRNs are hung (no gvlr 300 logs). Investigate if there are
any. An example of a gvlr 300 log is shown below:
>logutil
sheet 7 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
C7SCCP
CLASS: HOLDING
0 0 0 181 263
0 0 0 0
26518 11 18742 9
0 63 10963 69
24436 10 7566 2
15852 2 18952 9
2946 7 0 0
49537 57
sheet 8 of 9
Procedure 4-13
Check the health of the network from the MSC (continued)
Step Action
12 Check the log count. Do this before and after a patch or upgrade activy to
look for any increase in logs that you did not have before. Observe the
high running logs.
>dmsmon
(dmsmon)>logcount
*********************************
* Log Report Counts *
*********************************
..
....
...
(dmsmon)>highlogs
****************************
* High Runner Logs *
****************************
sheet 9 of 9
Procedure 4-14
Verify the state of carriers and trunks serving the MGW
Step Action
1 Display all MGW entities (up to eight per shelf) in Table GWINV. Use this
information to obtain the MID and Nsta for the MGW being verified.
(MSC)>TABLE GWINV
TABLE: GWINV
TOP
GWID MID PROTOCOL TRANS INACT MGWINFO MGWPROF
---------------------------------------------
MGW 4 PP429_15K_8 H248 UDP 10 (10 160 137 5 2945 1) $
MGW 5 PP430_15K_8 H248 UDP 10 (10 160 137 12 2945 1) $
MGW 6 PP429_15K_9 H248 UDP 10 (10 160 137 6 2945 1) $
BOTTOM
sheet 1 of 3
Procedure 4-14
Verify the state of carriers and trunks serving the MGW
Step Action
2 Verify the Nsta instance for the MGW matches the MID for the MGW
being verified.
(MGW)>d -p Nsta/<Nsta#> Vgs H248/0
where <Nsta#> is the Nsta # associated with the MGW being verified.
For example:
(MGW)>d -p Nsta/8 Vgs H248/0
==|===================================================
| PP429_15K Nsta/8 Vgs H248/0
==|=====================(A)===========================
1|mgMid PP289_15K_8
2|udpPortConnection Nsta/8 Vgs Ctrl/mediaGateway
UdpPort/2945
3|sdpFormat nonH248
4|atmSdpTransmitFormat rfc3108
5|mgcList Nsta/8 Vgs MgcIf/1
==|===================================================
In this example, Nsta 8 matches the mgMid. This is the VSP where all the
trunks reside for the MGW being verified.
sheet 2 of 3
Procedure 4-14
Verify the state of carriers and trunks serving the MGW
Step Action
Verify there are no alarms in the alarm banner under Trks (that is, only a
dot . appears under Trks.) If the alarm banner is not clear, investigate
before proceeding. Use the following command to post a MGW carrier:
(MSC)>POST D MGW X Y
sheet 3 of 3
Procedure 4-15
MGW shelf identification
Step Action
Procedure 4-16
Verify shelf, card, lp, and ports on the MGW
Step Action
+==+=====+------+----------+----------+
|Lp |Sonet |osiAdmin |osiOper|
+==+=====+------+----------+----------+
| 8 | 0 |unlck |ena
| 9 | 0 |unlck |ena
|14 | 0 |unlck |ena
|14 | 1 |unlck |ena
|14 | 2 |unlck |ena
|15 | 0 |unlck |ena
|15 | 1 |unlck |ena
|15 | 2 |unlck |ena
cpEquipmentProtection = hot
repeatFanAlarm = off
commentText = ""
sheet 1 of 2
Procedure 4-16
Verify shelf, card, lp, and ports on the MGW (continued)
Step Action
+====+-----+----+-----+
|Card|osiAd|osiO|osiUs
| | min |per | age |
+====+-----+----+-----+
| 0 |unlck|ena |activ|
| 1 |unlck|ena |activ|
| 2 |unlck|ena |activ|
| 3 |unlck|ena |activ|
4 Verify there are no Sonet port alarms and all alarms are off.
(MGW)>d Lp/* Sonet/*
+==+===+------+----+---+----+-----+-----+---+
|Lp|Sonet |los |lof| |ais |rfi |ais |txA |txR
| | | | | | | |is |di |
+==+=====+---+---+----+-----+----+----+----+
| 2 | 0 |off |off |off |off |off |off |off |
| 2 | 1 |off |off |off |off |off |off |off |
| 2 | 2 |off |off |off |off |off |off |off |
| 2 | 3 |off |off |off |off |off |off |off |
| 3 | 0 |off |off |off |off |off |off |off |
| 3 | 1 |off |off |off |off |off |off |off |
| 3 | 2 |off |off |off |off |off |off |off |
| 3 | 3 |off |off |off |off |off |off |off |
|14 | 0 |off |off |off |off |off |off |off |
|14 | 1 |off |off |off |off |off |off |off |
sheet 2 of 2
Procedure 4-17
Verify MTP2 (USP only) on the MGW
Step Action
==|===================================================
| 15KPP665 Nsta/8 Vgs Mtp2/1
==|==============================(A)==================
1 |adminState unlocked
2 |operationalState enabled
3 |usageState active
16|msuOctetsSent 0
17|msuOctetsReceived 0
==|===================================================
Procedure 4-18
Verify MTP3 (UMTS and Nb only) on the MGW
Step Action
==|=======================================
| PP301_15K Mtp3/8 Ls/0
==|=================(A)===================
1|adminState unlocked
2|operationalState enabled
3|usageState active
==|=======================================
2 Verify the link status of the MTP3 link is unlocked, enabled, and active.
(MGW)>d -o Mtp3/* Ls/* Link/*
==|==============================================
| PP301_15K Mtp3/8 Ls/0 Link/0
==|=================(A)==========================
1|adminState unlocked
2|operationalState enabled
3|usageState active
4|pdusRx 6162
5|payloadPdusRx 185
6|pdusTx 6166
7|payloadPdusTx 185
8|invalidPdusRx 0
==|==============================================
3 Verify MTP3 routeset and routes are unlocked, enabled, and active if an
STP is used.
The STP would be between the MGW and the RNC and/or between the
MGW and Nb peers.
(MGW)>d -o Mtp3/* Routeset/*
(MGW)>d -o Mtp3/* Route/*
Procedure 4-19
Verify SaalNni (UMTS and Nb only) on the MGW
Step Action
==|=======================================
| PP301_15K SaalNni/2
==|===================(A)=================
1|adminState unlocked
2|operationalState enabled
3|usageState active
4|state completeSuccess
5|targetProvingPdus 0
6|currentProvingPdus 0
7|maxCcReached 0
8|noResponseTimeouts 0
9|pdusTx 12027
10|pdusRx 12029
11|pduOctetsTx 127287
12|pduOctetsRx 124409
13|insvFailures 3
==|=======================================
Procedure 4-20
Verify PVC to RNC (UMTS and Nb only) on the MGW
Step Action
==|===================================================
| PP80 Nsta/10 Vgs AtmTConn/0-4 SpvcAp
==|===========================(A)=====================
1|svcStatus connected
2|lastSetupFailureCause 0
3|lastSetupFailureDiagnostic ""
4|retryTimeRemaining 0 seconds
5|retryFailures 0
6|remoteAddress
471391234567890ABCDE1234000020480D005000
7|lastTearDownCause 0
8|lastTearDownDiagnostic ""
==|===================================================
Step Action
1 Verify the operational state of the Q2630 is unlocked, enabled, and active.
(MGW)>d q2630/*
==|================================================
| PP429_15K Q2630/8
==|==============================(A)===============
1|adminState unlocked
2|operationalState enabled
3|usageState active (for Nb it can be active or Idle)
...
...
...
72|protocolErrorsTx 0
==|================================================
==|================================================
| PP429_15K Q2630/8
==|==============================(A)===============
1|adminState unlocked
2|operationalState enabled
...
...
...
54|currentExistingPaths 1
55|localBlockedPaths 0
56|remoteBlockedPaths 0
...
...
...
72|protocolErrorsTx 0
==|================================================
sheet 1 of 2
Procedure 4-21
Verify Q2630 (UMTS and Nb only) on the MGW (continued)
Step Action
==|================================================
| PP429_15K Q2630/8
==|==============================(A)===============
1|adminState unlocked
...
...
...
54|currentExistingPaths 2
...
...
...
72|protocolErrorsTx 0
==|================================================
==|=======================================================
| PP429_15K Q2630/8 PeerAddr/1
==|===================(A)=================================
1|remoteAesa 470000000000000000000004760020480D508000
2|remotePointCode 1.19.1
3|linkToOwnedPaths Nsta/8 Vgs AtmTCon/2 pathOwner,
Nsta/8 Vgs AtmTCon/3 pathOwner
4|linkToVoiceProfile Nsta/8 Vgs Vp/2
==|=======================================================
The linkToOwnedPaths is a comma separated list. In the example output
above, there are two linkToOwnedPaths: Nsta/8 Vgs AtmTCon/2
pathOwner, and Nsta/8 Vgs AtmTCon/3 pathOwner.
sheet 2 of 2
Procedure 4-22
Verify VSP4e on the MGW
Step Action
1 Verify the operational state of the NSTA VGS MGCIF components are
unlocked and enabled.
(MGW)>d nsta/* vgs mgcif/* osistate
==|===================================================
| PP301_15K Nsta/14-15 Vgs MgcIf/PRIMARY
==|===================(A)=============================
1|adminState unlocked
2|operationalState enabled
3|usageState idle
4|availabilityStatus
5|proceduralStatus
6|controlStatus
7|alarmStatus
8|standbyStatus notSet
9|unknownStatus false
==|===================================================
sheet 1 of 3
Procedure 4-22
Verify VSP4e on the MGW (continued)
Step Action
==|===================================================
| PP301_15K_Shelf_1 PP301_15K_Shelf_1
| If/200 Vcc/0.5 If/200 Vcc/0.18
==|=================(A)==================(B)==========
1|txCell 194386 319021
2|txCellDiscard 0 0
3|txFrameDiscard 0 0
4|txFrameDiscardClp 0 0
5|rxCell 194250 435021
6|rxCellDiscard 0 0
7|rxCellDiscardClp 0 0
8|rxFrameDiscard 0 0
9|rxFrameDiscardClp 0 0
10|rxAal5FrameError 0 0
11|rxAal5FrameAbort 0 0
==|===================================================
sheet 2 of 3
Procedure 4-22
Verify VSP4e on the MGW (continued)
Step Action
Note: RNC bearer PVCs can be identified with the following command:
(MGW)>d Nsta/ Vgs AtmTCon/ atmCon nextHop
The value of that will be an AtmIf/ Vcc/ instance.
3 Verify the OSI state for all Tag instances for all VSP cards on this shelf.
Verify the OSI state is unlocked, enabled, active, and enabled.
(MGW)>d Nsta/* Vgs Tag/*
sheet 3 of 3
Procedure 4-23
Verify M2UA interface on the MGW
Step Action
1 Identify the Virtual Router (Vr) associated with the M2UA interface.
The Vr with "SIGVRAP" indicates that this is the Vr.
(MGW)>d vr/* pp/*
=|===================================================
|WTCRWABRU401 WTCRWABRU401 WTCRWABRU401 WTCRWABRU401
|Vr/0 Pp/OAM Vr/3 Pp/H248AN Vr/3 Pp/H248VRAP Vr/3 Pp/
SIGVRAP
=|=================(A)=====(B)======(C)=======(D)====
1|snmpOperStatus up up up up
2|adminState unlocked unlocked unlocked unlocked
3|operationalState enabled enabled enabled enabled
4|usageState active active active active
5|ifIndex 14 3 4 17
=|===================================================
==|===================================================
|WTCRWABRU401 Nsta/14 Vgs M2ua As/14 Asp/0
==|==========(A)======================================
1 |ipAddress 172.20.64.157
==|==================================================
sheet 1 of 2
Procedure 4-23
Verify M2UA interface on the MGW (continued)
Step Action
4 Verify that the operational state is unlocked, enabled, and active and the
heartbeats and heartbeatAcks are being sent/received.
(MGW)>d Nsta/* Vgs M2ua As/* Asp/*
==|===================================================
| PP429_15K Nsta/14 Vgs M2ua As/2 Asp/0
==|==========================(A)======================
1|adminState unlocked
2|operationalState enabled
3|usageState active
...
...
...
17|heartbeatsSent 48737
...
...
...
20|heartbeatAcksReceived 48737
===|==================================================
Note: The values of heartbeats and heartbeatAcks will be close but may
not be exactly the same.
5 Verify the link to the USP for each backhauled SS7 link from the RNC,
BSC, or PSTN interface is active.
(MGW)>d Nsta/* Vgs M2ua As/* Iid/*
==|===================================================
| PP80 Nsta/10 Vgs M2ua As/1 Iid/81
==|=======================(A)=========================
1|state active
...
...
...
20|congestionIndicationsSent 0
==|===================================================
6 On the Call Server, verify all SS7 links expected to be up are up.
(Call Server)>mapci;mtc;ccs;ccs7
If they are not up, resolve the issues and contact your next level of
support if needed.
sheet 2 of 2
Procedure 4-24
Verify VSP4e call processing on the MGW
Step Action
==|=======================================================
|PP301_15K Nsta/8 Vgs Aal2Svc PP301_15K Nsta/9 Vgs Aal2Svc
==|============================(A)============(B)=========
1|activeOriginatedSvcs 4 3
2|activeTerminatedSvcs 3 3
3|originatedSvcs 25 6
4|terminatedSvcs 23 4
5|activeSvcsDeleted 0 0
6|neverUsedSvcsDeleted 3 1
7|svcsPending 0 0
8|emptySvcCount 7 6
9|networkReleaseCount 20 1
10|unavailableSvcCount 3 3
11|narrowbandConnectionsRefused 0 0
12|svcSetupTimeoutCount 0 0
13|overloadedSvcCount 0 0
==|=======================================================
2 Verify active contexts, connections set up, and disabled ATM trunks.
Observe the following:
activeContexts should be changing when the display command is
executed multiple times
connectionsSetup should be incrementing when the command is
executed multiple times
disabledATMTrunks should always be 0
Procedure 4-25
Verify Nb Interfaces are Operating Correctly on the MGW
Step Action
activeOriginatedSvcs = 0
activeTerminatedSvcs = 0
originatedSvcs = 153
terminatedSvcs = 116
activeSvcsDeleted = 0
neverUsedSvcsDeleted = 0
svcsPending = 0
emptySvcCount = 0
networkReleaseCount = 116
unavailableSvcCount = 0
narrowbandConnectionsRefused = 0
svcSetupTimeoutCount = 0
overloadedSvcCount = 0
AN software patching 4
Refer to the MGW18 Release Notes for instructions on how to obtain the
current patch baseline. Included with the patch baseline bundle will be
detailed instructions in a README text file.
ATTENTION
Always read the latest GSM/UMTS MGW Release Notes before
applying patches or performing a software upgrade.
The MGW Release Notes, published by Nortel for each Media Gateway
software release, contains important information about the current
software loadname (application version), the applicable software patch
baseline, and special instructions you need to know for the current
software release.
AN software upgrades 4
This section describes how to upgrade the software to a new application
version on an AN shelf.
ATTENTION
Always read the latest GSM/UMTS MGW Release Notes before
applying patches or performing a software upgrade.
The MGW Release Notes, published by Nortel for each Media Gateway
software release, contains important information about the current
software loadname (application version), the applicable software patch
baseline, and special instructions you need to know for the current
software release.
Since all the cards are paired and no VSP cards are in the AN shelf, no traffic
re-direction is needed for the AN software upgrade.
At any point during the software upgrade, if any unexpected system responses
appear, such as unexpected alarms, logs or command outputs, then halt the
activity and contact the next level of support.
Procedure 4-26
Download the software to the AN disk
Step Action
1 Display the disk status. Verify that the disk is unlocked, enabled and
active. Verify that the sync status (syncStatus) is synchronized, and the
disk usage (usage) is 85% or less.
If necessary, use the tidy and synchronize commands to remove
unneeded files. Refer to NTP NN10600-550, Nortel Multiservice Switch
7400/15000/20000 Common Configuration Procedures, subsection Disk
full conditions.
(AN)>d fs
Fs
adminState = unlocked
operationalState = enabled
usageState = active
volumeName = volumeNotSe
activeDisk = Fs Disk/0
syncStatus = synchronized
syncProgress = 100 %
capacity = 4294770688 bytes
freeSpace = 624295936 bytes
usage = 85 %
Sw Dld
status = inactive
sheet 1 of 4
Procedure 4-26
Download the software to the AN disk (continued)
Step Action
3 If the current AN load is less than PCR 6.1.1 (such as PCR 5.1 or PCR
5.2), perform this step. Otherwise, go to step 4.
a. List all of the patches that have been downloaded to the AN.
(AN)>l sw appl/* pa/*
Sw Av/base_CE02S2D Patch/baseFT420A
Sw Av/base_CE02S2D Patch/baseFR057A
Sw Av/base_CE02S2D Patch/baseFR075A
The example output above shows the first several patches of the
CE02S2D patches.
b. List the current active patches:
(AN)>d sw pa
Sw
patchList = baseFR057A, baseFT183A,
baseFT207B, baseFT409A, ipFT120A,
ipFT126A, ipFT1195A, baseFR1437A,
baseFT420A
The example output above shows a patch list that includes patch
baseFT420A. This patch must be present if the current AN load is less
than PCR 6.1.1. Patch baseFT420A enables patch bundling, which is
required to complete the remaining steps of this procedure. (AN loads
PCR 6.1.1 and higher already have patch bundling enabled.)
If patch baseFT420A is not active, and the current AN load is less than
PCR 6.1.1, contact your next level of support and the Project Manager,
because the AN is not patch current.
4 Display the software applications version list (AVL). This shows the
software currently provisioned on the AN.
(AN)>d sw avl
Sw
avList = base_CE02S2D, ip_CE02S2D,
networking_CE02S2D, aal1Ces_CE02S2, wanDte_CE02S2D,
fabric_CE02S2D, atmNetworking_CE02S2D, patch_CE02S2D
The example output shows CE02S2D, which is the software version load
name for the PCR software release 5.2.
sheet 2 of 4
Procedure 4-26
Download the software to the AN disk (continued)
Step Action
The example above shows CF01S1E, which is the software version load
name for the PCR 6.1.1 release.
Sw Dld
Sw Dld
avBeingDownloaded =
status = inactive
filesToTransfer = 0
avListToDownload = base_CF01S1E, ip_CF01S1E,
networking_CF01S1E,
aal1Ces_CF01S1E,
wanDte_CF01S1E,fabric_CF01S1E
atmNetworking_CF01S1E,
patch_CF01S1E
downloadedAvList =
processorTargets = i960 ppc
sheet 3 of 4
Procedure 4-26
Download the software to the AN disk (continued)
Step Action
9 Verify that software is being downloaded. Press Enter and then enter the
following:
(AN)>d sw dld
Sw Dld
avBeingDownloaded = base_CF01S1E
status = active
filesToTransfer = 555
avListToDownload = base_CF01S1E, ip_CF01S1E,
networking_CF01S1E,
aal1Ces_CF01S1E,
wanDte_CF01S1E,fabric_CF01S1E
atmNetworking_CF01S1E,
patch_CF01S1E
Sw Av/base_CF01S1E
Sw Av/ip_CF01S1E
Sw Av/networking_CF01S1E
Sw Av/aal1Ces_CF01S1E
Sw Av/wanDte_CF01S1E
Sw Av/fabric_CF01S1E
Sw Av/atmNetworking_CF01S1E
Sw Av/patch_CF01S1E
11 List all of the patches that have been downloaded to the AN.
(AN)>l sw appl/* pa/*
Sw Av/patch_CF01S1E Patch/aal1CesFT1376A
Sw Av/patch_CF01S1E Patch/atmNetworkingFR1014C
Sw Av/patch_CF01S1E Patch/atmNetworkingFR1334A
Sw Av/patch_CF01S1E Patch/atmNetworkingFR1334B
The example output shows some of the patches downloaded with the
patch_CF01S1E patch bundle.
sheet 4 of 4
Procedure 4-27
Verify and save the AN current working provisioning view
Step Action
Prov
The edit view is identical to the current view.
If the system indicates that the edit view and the current view are the
same, proceed. If they are not the same, contact your next level of
support.
Prov
3 Save the current provisioning view. Check with local office policy
regarding file naming conventions. Follow the existing convention. An
example naming convention is given in the following command.
(AN)PROV>save -f(AN_PCRload#) -ascii -portable pr
For example:
(AN)PROV>save -f(AN_PCR611) -ascii -portable pr
Prov
Saving the edit view into AN_PCRload522.full.001
(with ascii,portable formats) ...
The provisioning data is saved in file
AN_PCRload522.full.001.
LOSS OF SERVICE:
Do not perform a general AN software upgrade when migrating
software versions of a particular feature (example: feature
atmNetworking_CF01S1E). The impact on service cannot be
predicted if both migrations are attempted at the same time.
Procedure 4-28
Activate the new AN software load and save the provisioning view
Step Action
2 Display the software applications version list (AVL). This shows the
software currently provisioned on the AN.
(AN)>d sw avl
Sw
avList = base_CE02S2D, ip_CE02S2D,
networking_CE02S2D, aal1Ces_CE02S2, wanDte_CE02S2D,
fabric_CE02S2D, atmNetworking_CE02S2D, patch_CE02S2D
The example output shows CE02S2D, which is the software version load
name for PCR software release 5.2.
3 Replace all of the old application versions in the application version list
with the new application versions. Refer to the MGW18 Release Notes for
the complete list of application versions to be applied. The following
command shows application versions applicable for the PCR 6.1.1
release as an example.
(AN)PROV>set sw avl ! base_CF01S1E ip_CF01S1E
networking_CF01S1E aal1Ces_CF01S1E wanDte_CF01S1E
fabric_CF01S1E atmNetworking_CF01S1E patch_CF01S1E
sheet 1 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
4 List all of the patches that have been downloaded to the AN.
(AN)PROV>l sw appl/* pa/*
Sw Av/patch_CF01S1E Patch/aal1CesFT1376A
Sw Av/patch_CF01S1E Patch/atmNetworkingFR1014C
Sw Av/patch_CF01S1E Patch/atmNetworkingFR1334A
Sw Av/patch_CF01S1E Patch/atmNetworkingFR1334B
The example output shows some of the patches downloaded with the
patch_CF01S1E patch bundle.
5 If there are patches required for the release being migrated to, apply the
patches. For specific instructions, refer to the README text file included
with the AN patch baseline. Nortel Global Product Support may
recommend additional patches that have been released since the last
bundling of patches. The following is only an example of the command
used to set the software patch list.
(AN)PROV>set Software patchlist ! baseFR057A baseFT183A
baseFT207B baseFT409A xApplFR021A ipFT120A ipFT126A
xApplFT1048B atmNetworkingFT075A
Sw
patchList = baseFR057A, baseFT183A,
baseFT207B, baseFT409A, xapplFR021A,
ipFT120A, ipFT126A, xApplFT1048B,
atmNetworkingFT075A
The example output above illustrates the use of the command. The actual
patch names in the patch list will vary with the patch bundle and patches
applied.
sheet 2 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
The following example warnings can be expected and are normal when
the check prov command is executed:
Warning:
Reason: Lp 0 (card 1) will be reset when this view is
activated.
Warning:
Activation will disrupt service for the following
component(s):
Lp/0
Warning:
Activation will result in a software migration system
reload. Some applications may experience service
outage.
sheet 3 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
8 After resolving all error message in the check prov, activate the
provisioning view to start the migration.
(AN)PROV>activate prov
If you get an error message such as the one below, the activation has
paused. At this point you do not have an active standby; therefore, abort
the activation using the stop prov command, and contact your next level
of support for assistance in resolving the problem.
Here is an example of the error message showing that the migration has
paused:
The software migration is paused, pause reason:
Details:
On Card 1: some appl(s) may not be ready for SO.
On Card 14: Pausable Alarm recvd;
To resume, type Continue Prov.
To stop, type Stop Prov.
sheet 4 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
Prov
sheet 5 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
adminState = unlocked
operationalState = enabled
usageState = busy
provisioningActivity = waiting for confirm
activityProgress = n/a
standbyCpActivity = none
standbyCpActivityProgress = n/a
committedFileName = mabo522.full.003
currentViewFileName = none
lastUsedFileName = none
provisioningSession = Nmis Telnet Session/1
provisioningUser = gxin
checkRequired = yes
confirmRequired = yes
editViewName = none
sheet 6 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
13 When a warning message has appeared stating that you have 15 minutes
to confirm prov, or the display prov command has shown
"confirmRequired = yes", you must confirm the provisioning view to avoid
a non-hitless rollback to the previously committed configuration:
(AN)PROV>confirm prov
The following example error message may appear, indicating that certain
patches must be removed from the patch list due to being incompatible
with the new application version list just installed:
Error:
Attribute: patchList
Reason: Each patch below either does not exist for the
version of its application in the avList, or requires
its application to be added to the avList:
xapplFR021A ipFT120A
ipFT126A xApplFT1048B
atmNetworkingFT075A
sheet 7 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
15 Save the current provisioning view. Check with local office policy
regarding file naming conventions. Follow the existing convention. An
example file name, AN_PCR611, is given in the example command
below.
(AN)PROV>save -f(AN_PCR611) -ascii -portable pr
Prov
17 End provisioning.
(AN)PROV>end prov
Prov
18 Verify the edit file is the same as the committed file. The following output
should appear when the start prov command is executed:
(AN)start prov
Prov
The edit view is identical to the current view.
19 End provisioning
(AN)PROV>end prov
sheet 8 of 9
Procedure 4-28
Activate the new AN software load and save the provisioning view (continued)
Step Action
Sw
avList = base_CF01S1E, ip_CF01S1E, networking_CF01S1E,
aal1Ces_CF01S1E, wanDte_CF01S1E, fabric_CF01S1E
atmNetworking_CF01S1E, patch_CF01S1E
Sw
patchList = baseFR057A, baseFT183A,
baseFT207B, baseFT409A, xapplFR021A,
ipFT120A, ipFT126A, xApplFT1048B,
atmNetworkingFT075A
The example output above illustrates the use of the command. The actual names
in the patch list will vary with the patch bundle and patches applied.
sheet 9 of 9
Procedure 4-29
Upgrade the AN Fabric Card firmware
Step Action
2 Lock fabric X.
(AN)>lock -force sh fabric/x
When the display shows the following message, go to the next step to
unlock Fabric X:
The command completed successfully.
5 Unlock fabric X.
(AN)>unlock sh fabric/x
sheet 1 of 2
Procedure 4-29
Upgrade the AN Fabric Card firmware (continued)
Step Action
When the display shows the following message, go to the next step to
unlock Fabric Y:
The command completed successfully.
9 Unlock fabric Y.
(AN)>unlock sh fabric/y
11 Save the current provisioning view. Check with local office policy
regarding file naming conventions. Follow the existing convention. An
example file name, AN_PCR611_fabricupgrade, is given in the command
below.
(AN)PROV>save -f(AN_PCR611_fabricupgrade) -ascii -portable pr
sheet 2 of 2
AN health checks 4
The following procedures should be run before and after an AN patch
application or software upgrade. Performing the health checks offers the
following benefits:
They will help identify any problems before an activity starts, and may
also serve as an aid for debugging should any problems arise during or
after the activity.
The tests also serve as a way to establish a baseline of the systems
configuration and performance, so that when the same tests are run after
an activity, a comparison can be made to verify that the system is back to
operating as it was before.
As part of testing, test calls should be performed by the local telco team
immediately after the completion of a patch or software upgrade, in parallel
with the health checks described in the following procedures.
The AN health checks can be found in the following sections of this document:
Verify the LP switchover functionality of the AN
Check the overall health of the AN
For instance, Active and Standby will appear for LP Instance 0 across
card slots 0 and 1. An example output of the command is given below:
Procedure 4-30
Verify Logical Processor switchover functionality on the AN
Step Action
Note: Do not perform another switch over on LP0 until more than 10
minutes have passed.
sheet 1 of 4
Procedure 4-30
Verify Logical Processor switchover functionality on the AN (continued)
Step Action
6 Verify that each Laps component Lp/10 and Lp/11 can be successfully
switched.
(AN)>Switch Lp/10
sheet 2 of 4
Procedure 4-30
Verify Logical Processor switchover functionality on the AN (continued)
Step Action
7 Verify that each Laps component Lp/12 and Lp/13 can be successfully
switched.
(AN)>Switch Lp/12
8 Verify that each Laps component Lp/14 and Lp/15 can be successfully
switched.
(AN)>Switch Lp/14
sheet 3 of 4
Procedure 4-30
Verify Logical Processor switchover functionality on the AN (continued)
Step Action
10 One by one, switch over each Logical Processor to bring the shelf back to
its original serving and hot standby configuration.
(AN)>Switch Lp/xx
Note: Do not perform another switch over on LP0 until more than 10
minutes have passed.
11 Display the status of all cards and verify that no cards are in a degraded
state.
(AN)>d sh ca/* sps
sheet 4 of 4
If any of the components displayed are not enabled or if any have alarms,
contact the next level of support for assistance in investigating the cause and
correcting the problem.
Procedure 4-31
Verify the overall health of the AN
Step Action
==|===================================================
| PP300_15K Lp/0
==|===================================================
1|adminState unlocked
2|operationalState enabled
3|usageState active
4|availabilityStatus
5|proceduralStatus
6|controlStatus
7|alarmStatus
8|standbyStatus providingService
9|unknownStatus false
==|===================================================
=============================
| Lp/0 Lp/2 Lp/3
=============================
1|cpuUtil 3 % 2 % 2 %
=|===========================
sheet 1 of 4
Procedure 4-31
Verify the overall health of the AN (continued)
Step Action
==|===================================================
| PP300_15K Lp/8
| Sonet/0-15
==|===================================================
1|adminState unlocked
2|operationalState enabled
3|usageState active
4|availabilityStatus
5|proceduralStatus
6|controlStatus
7|alarmStatus
8|standbyStatus notSet
9|unknownStatus false
==|===================================================
4 Display the status of the service interfaces.The output should show the
operationalState=enabled, if the Lp component is up and running.
(AN)>display AtmIf/* osistate
==|===================================================
| PP300_15K AtmIf/800-801 PP300_15K AtmIf/802
==|===================(A)===============(B)===========
1|adminState unlocked unlocked
2|operationalState enabled enabled
3|usageState active active
4|availabilityStatus
5|proceduralStatus
6|controlStatus
7|alarmStatus
8|standbyStatus notSet notSet
9|unknownStatus false false
==|===================================================
sheet 2 of 4
Procedure 4-31
Verify the overall health of the AN (continued)
Step Action
==|===================================================
| PP300_15K Shelf PP300_15K Shelf
| Card/0 SpServ Card/1 SpServ
==|===================(A)================(B)==========
1|adminState unlocked unlocked
2|operationalState enabled enabled
3|usageState active active
4|availabilityStatus
5|proceduralStatus
6|controlStatus
7|alarmStatus
8|standbyStatus providingService hotStandby
9|unknownStatus false false
==|===================================================
The osiStby values of serving and hotstandby for each Lp will vary. The
above are examples only.
sheet 3 of 4
Procedure 4-31
Verify the overall health of the AN (continued)
Step Action
==|===============================================
| PP300_15K AtmIf/802
==|===============================================
1|adminState unlocked
2|operationalState enabled
3|usageState active
...
27|rxCellDiscard 0 [not increasing]
...
32|droppedRxCells 5521 [not increasing]
...
72|txCell 1619375[increasing]
73|txCellClp 296
74|txCellDiscard 3 [not increasing]
75|txLinkUtilization 0 %
76|rxCell 1956669[increasing]
77|rxCellClp 0
78|rxLinkUtilization 0 %
...
==|===============================================
sheet 4 of 4
Roll back 4
Procedure 4-32 may be performed if the software upgrade or patch
application on an AN or MGW fails. Always contact the next level of support
first, for specific instructions and directions and a decision on whether a roll
back to the previous provisioning view is the best course of action.
ATTENTION
Performing a rollback will result in a shelf reset and loss of service.
Contact the next level of support before performing a rollback, for
consultation on whether a rollback is the best course of action and for
assistance with specific instructions and directions.
Procedure 4-32
Rollback proceduresheet 1 of 2
Step Action
1 Contact the next level of support for advice on whether a roll back to the
previous provisioning view is the best course of action, and for specific
instructions and directions regarding the roll back procedure.
3 Reload the view that was saved before the software upgrade or patch
application started.
(MGW)PROV>load -f(filename_of_saved_view) prov
7 Save the current provisioning view. Check with local office policy
regarding file naming conventions. Follow the existing convention. An
example file name, AN_PCR611_rollback, is given in the example
command below.
(AN)PROV>save -f(AN_PCR611_rollback) -ascii -portable pr
sheet 1 of 2
Procedure 4-32
Rollback proceduresheet 2 of 2
Step Action
10 Run the Health Checks to verify the operation of the MGW or AN node.
sheet 2 of 2
Once the MSC Server has responded, both the MSC Server and the MGW
consider one another In-Service. The arrival of a response at the MGW
completes the negotiation of the control association between the given MGW
and MSC Server or the alteration of an existing control association. This
association is only broken by one of the following procedures:
MGW Out-of-Service
MSC Server Ordered Re-register (not supported)
MSC Server Out-of-Service
In its response message the MSC Server may specify a value for the service
change address parameter indicating to the MGW that it wants to receive all
future control messages at the specified address and port. The message id
(MID) used by the MSC Server in this response is recorded by the MGW and
used to verify future control messages. Any future message that does not use
this MID is not processed. The error reply 402, Unauthorized, is sent to
the MSC Server in this case.
MGW out-of-service
The MGW Out-Of-Service procedure is initiated by the MGW toward the
MSC Server with which it has a control association. This procedure is used by
the MGW to indicate that it will no longer be able to provide service to the
given MSC Server. This may occur because new provisioning on the MGW
did not include the current MSC Server in the list of MSC Servers that can
control this MGW or perhaps the entire Media Gateway was de-provisioned.
Upon receipt of this command, the MSC Server tears down all calls that were
established through this MGW. It is not necessary for the MSC Server to send
any subtract commands to the MGW. The MGW destroys all existing
contexts without any further messaging from the MSC Server. Once the MSC
Server has responded to this command, the control association between the
two is ended.
MGW communication up
The MGW Communication Up procedure is initiated by the MGW toward its
controlling MSC Server when a communication loss is detected by the MGW.
The MGW detects a communication loss with its controlling MSC Server
through the Inactivity Timer Package. Once communication loss is
determined, the MGW begins sending the MGW Communication Up
command to the MSC Server. The command is resent until a response is
received.
When the MSC Server receives this command, it must respond. Once the
MSC Server has responded to this command, the control association is
continued as before, and the MGW and MSC Server continue operations as
before the communication loss. The MGW maintains the state of all Contexts
and Terminations as they were before the communication loss.
used in the command. If Cold is specified, the MGW will delete all
contexts. If warm is specified, the MGW will maintain the state of all
contexts and terminations as they were before receiving the command. The
MGW responds to the command, and the control association is never broken
by this procedure.
Carrier maintenance
In existing GSM networks, all carriers and their states are owned by the MSC.
When individual carriers are taken out of service (either through an
automatically detected fault or manually by a maintenance system), the
carrier state on the MSC is updated accordingly, and the corresponding trunk
members become CFL. When the carrier is returned to the service, the carrier
state on the MSC is updated to INSV and the CFL state is cleared on the
corresponding trunk members as well.
In the BICN architecture, the MGW has ownership of the TDM carriers.
Aspects of maintenance of these carriers is now shared by the MSC and the
MGW. Changes in the carrier status are detected by the MGW and reported to
the MSC by means of the H.248 ServiceChange messages as described in the
following paragraphs.
Termination out-of-service
The Termination Out-of-Service procedure is initiated by the MGW toward
the MSC Server with which it maintains a control association when a
termination is no longer available to be in a context due to termination failure
or a customer provisioning change. Upon receipt, the MSC Server sends a
response and takes the appropriate actions. If the specified termination(s) is in
the NULL context, the MSC Server shall refrain from adding the specified
terminations to any new contexts. If the termination is currently in a non
NULL context, the MSC Server should tear down the associated call and
immediately send the appropriate subtract command(s) to the MGW. The
state of the specified terminations shall be considered OutOfService.
If an entire TDM Span fails (Carrier Failure from the perspective of the
MSC Server), two ServiceChange commands whose termination ID is
wildcarded from the carrier down are sent to the MSC. One of these messages
specifies the NULL context ID and the other specifies the wildcarded ALL
context ID. This will indicate carrier failure to the MSC, which will mark the
carrier as Failed and all its members as OutOfService.
Note: Failure of an ATM or Vsp4e TDM Physical span could result in the
MGW sending a flood of messages to the MSC Server. In the GSM BICN
MGW planned configuration, each ATM and Vsp4e TDM Physical span
is 1 for 1 spared, and a double failure is considered to be highly
improbable. However, if a Vsp4e TDM Physical span does fail and is
either not spared or equipment failure occurs on the spared span
simultaneously, the MGW initiates the Termination Out-Of-Service
procedure for each of its carriers that are provisioned on this span. For an
ATM FP failure under similar conditions, the MGW generates either a
Notify message to the MGC (specifically a nt/netfail notification or g/
cause notification). Note that the MGC is responsible for configuring the
MGW to generate the Notify upon ATM failures. If the MGW is not
configured as such, the default behavior is to generate a Service Change.
Termination restoration
The Termination Restoration procedure is initiated by the MGW towards the
MSC Server with which it maintains a control association when a termination
that was previously unavailable becomes available for addition to a context.
The MSC Server shall regard the state of the specified termination(s) as In-
Service, and may consider these terminations eligible for addition to non-
Null contexts.
ATM card restoration does not result in any ServiceChange commands being
generated by the MGW.
Audits
The MSC Server employs Audits to check the sanity of call data and state of
trunks and carriers. The MGW supports the following audits:
MGW Carrier Audit check the states of trunk members of a given
carrier that are currently in non-Null contexts
H.248 Context Audit - synchronizes active context data between the
MSC Server and the MGW
Audit values
The Audit Values procedure is used in support of the Carrier and Context
Audits. The MSC Server toward any MGW with which it maintains a control
relationship initiates this procedure. Upon receipt of this command, the
MGW responds with Package/Property Names and Values realized by the
Terminations as requested.
For the Carrier Audit, the Audit Request contains a list of TDM Carriers with
wildcarded trunk members. Note that to fully audit a carrier, two Audit Requests
are needed: 1 for active trunks (those in a call) and 1 for idle trunks (those in
the Null Context) The MGW reports, in the AuditValue reply message, the
status for all terminations requested by the MSC Server. This audit is triggered
by the MSC Server upon the following conditions:
Periodic: This audit is run automatically every fifteen minutes.
MGW node state change on the MSC: Every time communication with a
MGW is restored, this audit is run for that
MGW.
Provisioning: During trunk provisioning, when certain number of trunk
members are provisioned, this audit is run for those trunk members. For
further information regarding provisioning, refer to NTP 411-2231-331,
Media Gateway Provisioning Guide.
For the Context Audit, the Audit Request will contain a list of Context Ids to
be audited. The MGW returns an Audit Reply with all the terminations
associated to the requested contexts. This audit is triggered by the MSC
Server upon re-establishment of the communication link after a failure, and is
triggered periodically (every 15 minutes).
The MSC Server may also Audit the MGWs ROOT component. If the
ROOT termination is specified in this command, the MGW behaves as
indicated in Table 5-1.
Table 5-1
MGW behavior, if the ROOT termination is specified
ALL Reply with all existing context IDs except NULL. The reply is of the
following
Context=1{AuditValue=ROOT},
Context=2{AuditValue=ROOT},
Context=3{AuditValue=ROOT}, etc
The MSC Server initializes this timer by sending a Modify command to the
ROOT termination of the MGW with which it has established a control
association. This command specifies a value for the maximum inactivity time
attribute of the Inactivity Time-out Event specified by the Inactivity Timer
Package. This event only has to be requested once for a given control
association. It does not have to be re-requested after a timeout occurs.
The MGW then monitors message activity from the MSC Server. If it
receives no message from the MSC Server over a period of time greater than
the maximum inactivity time, it sends a Notify command to the MSC Server.
If no response is received, it initiates the MGW Communication Up
procedure.
Maintenance flow 5
MGW maintenance flow diagrams
There are critical maintenance call flows that have been identified. These call
flows represent the Call Independent H.248 Procedures that are supported
by the GSM BICN MGW and the Inactivity Timer Package.
Each of the procedures supported by the MGW have nearly identical call
flows. The only difference is the values of the various attributes of the Service
Change Descriptor that are used.
Figure 5-1
Basic maintenance flow
Table 5-2
Maintenance procedures initiated by the MGW
Table 5-2
Maintenance procedures initiated by the MGW
Inactivity timer
The Inactivity Timer Package is supported by the MGW. Figure 5-2 provides
a call flow diagram to indicate how the inactivity timer is set up.
Figure 5-2
Inactivity timer flows
The MSC Server first sends a Modify command to the Root termination of
the MGW, requesting notification for the Inactivity Timer event and
indicating the maximum inactivity time value.
Second, the MGW responds to the modify command and begins to time
periods of message inactivity. If the MGW does not receive a message from
the MSC Server within the amount of time specified by the MGC, it sends a
Notify command to the MSC Server.
If it does not hear back from the MSC Server, it assumes that there has been a
communication link failure and begins to send Service Change commands to
the Root termination of the MSC Server with the service change method set
to disconnected. At this point, the MGW Communication Up procedure
is in effect.
Figure 6-1
Control and function processor LEDs
running on the failed FP, (for example, Mobiles attached to the network,
message queries waiting a response, and so on).
Table 6-1
Functional Processor (FP) Redundancy Summary
16p OC-3/STM-1 ATM 1:1 Hot with APS Ethernet Hot Switch-
over
CP3
Each shelf will be equipped with two CP3 cards. The CP3 cards run in a 1:1
warm spare mode.
2pGpDsk
The 2pGpDsk FP supports 1:1 Equipment Protection with Ethernet hot
switchover capabilities. Ethernet hot switchover provides an uninterrupted
Ethernet connection by automatically switching over to a hot standby
Ethernet port on a spare 2pGpDsk FP when the system detects a carrier
failure on a port on the active FP.
The switchover time will be under 2.5 seconds. All data traffic on the
Ethernet port will be lost during the switchover.
Figure 6-2
12p DS3 Sparing Panel
Vsp4e
Vsp4e FPs are provisioned as N+M spared (M=1 for the cost-optimized
configurations). Traffic from the Access Network should be divided between
at least 2 Vsp4e FPs located on different shelves to allow for availability
during network upgrades or failures. When Vsp4e serving the same access
node are spread across multiple shelves (with traffic load-shared between the
shelves), each shelf can be upgraded independently of all other shelves.
While the total capacity of a MGW is reduced during a software upgrade, it
can continue to process new circuit calls and in-progress calls on the shelves
not being upgraded are unaffected. Similarly for redundancy, while in-
progress calls fail on a shelf that has a failure, the MGW overall continues to
function normally with only reduced capacity. The Vsp4e also supports 2
spare DSPs, which may be activated upon failure of any of the 50 active
DSPs.
When you associate an LP with more than one processor card, you have
processor card sparing. In a sparing configuration, one processor card is the
main and the other is the spare. Typically, the main processor card is active
and provides the services and capabilities of the LP. The spare card is in
standby mode, waiting to take over in case the main card fails. Since
applications are linked to the LP rather than the physical card, messages
addressed to the LP are still addressed correctly if the primary processor fails
and the standby is activated.
Figure 6-3
Finding physical ports
LogicalProcessor/4
Port/0 Port/1
Transmit (Tx)
Port 1-16
Receive (Rx)
Transmit (Tx)
Port 17-32 Receive (Rx)
Figure 6-4
Finding physical ports (Continued)
How to find the physical ports ?
d sh ca/* configuredlp
Which LP for each card?
Or
d sh ca/* currentlp
Figure 6-5
Removing a card
if if
if no Hardware if no Hardware
Hardware Redundancy Hardware Redundancy
Redundancy and Redundancy and
Physical Ports Physical Ports
Remove the card
Remove the hardware
There are two standby modes for CP switchover: cold standby and hot
standby. In cold standby, all function processors (FP) must restart when the
CPs switch over. In hot standby, certain FPs continue running uninterrupted
when the CPs switch over.
Effects of a CP switchover
When a CP switchover occurs:
Network management sessions such as telnet, FTP, and FMIP, terminate,
dropping all connections to the active CP. A local network management
session on the standby CP does not terminate. However, it is suspended
until the CP becomes active.
Information stored in the edit view is lost unless it was saved on disk.
Some components that were in the locked state move to the unlocked
state. The fabricCard component remains locked if it was locked prior to
the switchover.
CAUTION
Risk of service loss on Passport 15000
If the switchover on failure option is enabled, both
active and standby CP Ethernet ports are available, and
the standby CP Ethernet port has failed or been
disconnected, a switchover occurs. The switchover
activates the standby CP. If the switchover detects that
the Ethernet port of the standby CP has failed, the
switchover tries to switch back to the other CP. This can
can cause the shelf to reset. If the shelf resets, the switch
is out of service for approximately 30 seconds.
Figure 6-6
Removing a redundant card
Lab: Removing a card when 1+1 redundancy
Yes Yes
No Is the spare No
Is the spare
card inserted? card inserted?
Insert a Insert a
spare card spare card
Yes Yes
Figure 6-7
Removing a card when loadsharing
Lab: Removing a card when loadsharing
PORTS NOT
Lock the logical processor
Lock lp/x
USED
Remove the card
Remove the card
For an overview of the MGW, please refer to the following Nortel technical
publications:
411-2231-014, GSM / UMTS R4 MSC Solution Overview
411-2231-330, GSM / UMTS R4 Media Gateway Operations and
Reference Guide
For information on troubleshooting the Multiservice Switch 15000 product
platform, refer to the following NTPs:
NN10600-520, Multiservice Switch 7400/15000/20000 Fault &
Performance Management: Troubleshooting
NN10600-715, Multiservice Switch 7400/15000/20000 ATM Fault and
Performance Management
There are three kinds of Passport shelves in the GSM BICN Media Gateway
feature:
Media Gateway shelf (MGW Shelf):
This shelf can be used either as a central MGW that co-resides in the same
region as the MSC and may have direct TDM links to the MSC, in which
case it is called a CFIWF, or as a remote MGW that connects to the MSC
through an AN, or directly without an AN (i.e. a two shelf configuration),
to the ATM network. This kind of shelf contains the Vsp cards.
Note: Note: in most instances in this document, the term MGW is
intended to imply a single VSP card.
Central AN:
The Aggregation Node that has direct IP connection to the HIOP of MSC.
Remote AN:
The Aggregation Node that connects to the MSC through other AN node
or ATM network.
Throughout this chapter, components are designated in italic font and the
attributes in bold font.
Figure 7-1 shows the logical view of inter-shelf communications for the
Media Gateway.
Figure 7-1
MGW inter-shelf communication
ATM
ATM
AN (remote) ATM
ATM
MGW(remote)
ATM
MGW (remote) ATM AN(remote)
TDM .
ATM MGW(remote)
MGW(remote)
BSS MGW (remote)
TDM
PSTN
If the Dual Shelf is deployed in the remote region, a MGW can be connected
to the ATM network as shown in Figure 7-2. The user can directly ping the
MSC to verify the IP connectivity on each Shelf.
The H.248 control signaling from a remote MGW Shelf to a MSC is via an
ATM connection when an AN is present. See Fig. 3. In addition to the ping
approach in Figure 7-2, the approach in Figure 3 can be used as well.
After the figures, three procedures are provided for troubleshooting H.248
signalling transport problems:
IP link between a Stand Alone MGW Shelf and the MSC
IP link between a MGW Shelf and the connected Aggregation Node or
Other MGW Shelf
IP link between the MSC and the connected Central Aggregation Node
IP link between the MSC and the connected Remote Aggregation Node
Figure 7-2
H.248 Control link between remote MGW Shelf and MSC
IP
H.248 H.248 AAL5
UDP UDP
IP IP ATM
Vr AAL5 (SPVC)
OC3
ATM
(PVC)
OC3ATM or
SPM
OC3ATM 12pDS3ATM
VSP
loopback Ping
Remote MG Shelf
ATM
Central AN IP
M AAL5
S IP
Vr ATM
C H.248 (SPVC)
UDP OC3
IP
Ethernet
2pGPDsk OC3ATM
Figure 7-3
H.248 Control link between remote MGW Shelf and MSC
IP
H.248 AAL5
UDP
IP ATM
Vr (SPVC) Remote AN
OC3
OC3ATM
SPM ping
VSP
Remote MG Shelf
ATM
Central AN IP
M AAL5
S IP
Vr ATM
C H.248 (SPVC)
UDP OC3
IP
Ethernet
2pGPDsk OC3ATM
Procedure 7-1
Checking the IP link between a remote stand alone MGW shelf and the MSC
1 Ping the IP address of HIOP (This is the orange line in Figure 7-2 above).
2 If ICMP packets are being received, then a valid communication link exists from the AN to the
HIOP. Skip the rest of these steps.
3 If the ping times out, the link from this Shelf bound toward the HIOP is not working. Find out the
corresponding AtmIf instance number and the ATM card slot and port number. The protocol port
instance name usually has embedded string network or H248.
l vr/* pp/*
Vr/0 Pp/OAM0
Vr/3 Pp/MG
Vr/3 Pp/MG1
Vr/3 Pp/Network
d -p AtmIf/1401 interfaceName
AtmIf/1401
interfaceName = Lp/14 Sonet/0 Sts/1
The nailed-up ATM connection is used between the AtmMpe, AtmIf/ Vcc/ and the external ATM
network Soft Pvc origination point on the network OC3 card.
4 Check the osiState of AtmMpe Ac/. The adminState should be unlocked and the opState
should be enabled.
5 Verify the AtmIf component is enabled. If disabled, check the physical connection (fiber link)
between the Shelf and the ATM network. Make sure all cables are connected correctly.
d atmif/1401 osistate
AtmIf/1401
adminState = unlocked
operationalState = enabled
usageState = active
availabilityStatus =
proceduralStatus =
controlStatus =
alarmStatus =
standbyStatus = notSet
unknownStatus = false
ok 2003-05-21 11:54:30.74
6 Repeat the above procedure as needed on the MGW shelf itself and in the direction of the
MGW, by replacing the HIOP address with that of the particular MGW card that is to be pinged.
This is the case of the blue line in Figure 7-2 and Figure 7-3 above.
Procedure 7-2
Checking the IP link between the AN and each MGW
1 Find out the IP address of the media gateway when logged into that Passport shelf.
d -p nsta/* vgs ctrl/mg ipaddress
2 Login to the connected AN node, find out the Virtual Router instance number that is connected
to the MGW under investigation.
l vr/* pp/* ipport
Usually the instance number is 3 and protocolPort has the name with embedded H248 string.
3 Ping the IP address of the media gateway when login to the connected AN node
ping -ip(xx.xx.xx.xx) vr/y ip icmp
4 If ICMP packets are being received, then a valid IP link exists from the AN to the MG. Skip the
rest of the steps.
5 If the ping times out, the link from the AN to the MG is not working. Find out the correct AtmIf
instance number and the ATM card slot and port number.
d -p Vr/3 Pp/H248
Vr/3 Pp/H248
snmpAdminStatus = up
linkToMedia = AtmMpe/902
accountingControl = sameAsProtocol
d -p AtmIf/90 interfaceName
AtmIf/90
interfaceName = Lp/9 Sonet/0 Sts/0
6 In this case, the AtmIf instance number is 90 and the ATM port number is at slot 9 with port
number 0.
7
a. Verify the AtmIf component on both AN and the MGW are enabled. If disabled, check the
physical connection (fiber link) between the AN and the MGW. Make sure all cables are
connected correctly, as shown in Figure 7-4 below.
d atmif/90 osistate
AtmIf/90
adminState = unlocked
operationalState = enabled
usageState = active
availabilityStatus =
proceduralStatus =
controlStatus =
alarmStatus =
standbyStatus = notSet
unknownStatus = false
ok 2003-05-21 11:54:30.74
b. Verify the Vcc component on the AN is provisioned correctly (there is a single Vcc from the
AN to each MGW Shelf that carries H248 traffic from the AN Vr to each MGW Shelf Vr via
ATM) and is in a correct osiState.
c. On the MGW, verify the matching Vcc as per the command above.
IP link between the MSC and the connected Central Aggregation Node
If the MG under investigation is a central media gateway, determine if a valid
communication link exists between the central AN and MSC by pinging
HIOP from the AN.
Procedure 7-3
Checking the IP link between the MSC and the connected central AN
1 Ping the IP address of HIOP when login to the AN node
ping -ip(xx.xx.xx.xx) vr/y ip icmp
2 If ICMP packets are being received, then a valid communication link exists from the AN to the
HIOP. Skip the rest of the steps.
3 If the ping times out, the link from the AN to the HIOP is not working. Check the Vr/, be sure
there is a protocol port connected to the MSC and it is enabled.
4 Check if the protocol port is linked to the correct media, and this media is connected to the right
Ethernet card.
d -p La/140
La/140
customerIdentifier = 0
linkToProtocolPort = Vr/3 Pp/MSC
ifAdminStatus = up
ifIndex =1
d La/140
La/140
adminState = unlocked
operationalState = enabled
usageState = busy
snmpOperStatus = up
d -p La/140 Framer
La/140 Framer
interfaceName = Lp/14 Eth100/0
IP link between the MSC and the connected Remote Aggregation Node
If the MGW under investigation is a remote media gateway, determine if a
valid communication link exists between the remote AN and MSC by pinging
HIOP from the AN.
Procedure 7-4
Checking the IP link between the MSC and the connected remote AN
2 If ICMP packets are being received, then a valid communication link exists from this AN to the
HIOP. Skip the rest of the steps.
3 If the ping times out, the link from the remote AN to the HIOP is not working. Find out the
corresponding AtmIf instance number and the ATM card slot and port number. The protocol port
instance name usually has embedded string H248 or Network.
l vr/* pp/*
Vr/0 Pp/OAM0
Vr/3 Pp/2
Vr/3 Pp/Network
Vr/3 Pp/H248
d -p AtmIf/1401 interfaceName
AtmIf/1401
interfaceName = Lp/14 Sonet/0 Sts/1
In this case, the AtmIf instance number is 1401 and the ATM port number is at slot 14 with port
number 0.
4 Check the osiState of AtmMpe Ac/. The adminState should be unlocked and the opState
should be enabled.
5 Verify the AtmIf component on the AN is enabled. If disabled, check the physical connection
(fiber link) between the AN and the ATM network. Make sure all cables are connected correctly.
d atmif/1401 osistate
AtmIf/1401
adminState = unlocked
operationalState = enabled
usageState = active
availabilityStatus =
proceduralStatus =
controlStatus =
alarmStatus =
standbyStatus = notSet
unknownStatus = false
ok 2003-05-21 11:54:30.74
Do it several times and if this number keeps increasing, that means MGW is
keep trying but failed to register.
Procedure 7-5
Checking the provisioning on the MGW
1 Determine if the MgcIf is provisioned correctly
d -p nsta/x vgs mgcif/y initialMgcAddress
2 Verify that the initialMgcPort is the port number of HIOP that is used to communicate with this
MGW. This number should be set to 2945 for binary H.248, a well-known UDP port between
MGWs and the MSC.
This mgMid has to match the value that is configured in MID field of table GWINV on the MSC.
The Protocol field of table GWINV must be set to H248.
The UdpPort instance number 2945 must match the TRANS field of table GWINV on the MSC.
b. Verify that the IP address of the Ctrl/Mg is the same value as that displayed in the field
CMIPHOST 0 or 1 of CMIPADDR table on the MSC.
The busy usage state will change to active automatically when the MGW
processes enough messages in its queue and the depth of the queue is below
certain level.
AAL2 AAL2
B Remote MG A
S ATM N
(SVC)
S SPM ATM OC3
/ TDM (SVC)
OC3 O
M C
U 3
A
X T
S VSP M
ATM
AAL2
M Central MG AAL2 ATM
S (SVC)
4 OC3
C SPM A
TDM ATM p
O N
OC3 (SVC)
C
3
A
T
VSP M
Procedure 7-6
Checking on an ATM bearer problem
d AtmIf/3 osistate
AtmIf/3
adminState = unlocked
operationalState = enabled
usageState = active
availabilityStatus =
proceduralStatus =
controlStatus =
alarmStatus =
standbyStatus = notSet
unknownStatus = false
2 Check the usage state of the AtmIf/ vcc/ to which the SpvcAp is connected. This should be
busy.
3 If the AtmIf is enabled and the Vcc is not busy, or the operational attributes, such as rxCell/
rxCellDiscard are noticeably strange, it is not communicating properly with the AN or stand
alone shelf. In some cases even if Nsta/ Vgs AtmTCon/ SpvcAp components are connected on
the local shelf, but the other side is not connected or provisioned, this will not be obvious. The
following Trace command could be used to check where the next connected ATM node is.
AtmIf/2 Vcc/1.3011
Link Side results:
EM/PP188_15K AtmIf/2 Vcc/1.3011
This means the AtmIf/2 Vcc/1.3011 is linked to the AN/Stand Alone shelf PP188_15K. Be aware
that the Trace command can display link information only if the attribute
oamSegmentBoundary in AtmIf/3 is set to No.
d -p AtmIf/3 oamSegmentBoundary
AtmIf/3
oamSegmentBoundary = no
AtmIf/2 Vcc/1.3011
Switch Side results:
AtmIf/4 Vcc/1.3011
Use the Trace command to verify the ATM segment is unbroken and ensure the operational
state of the segment end-points are enabled.
Checking ATM bearer connections
If there is a problem in ATM bear channels when a call is originated or
terminated from/to this MGW under investigation, check the following.
Procedure 7-7
Checking ATM bearer connections
In the above example, the SVC call is originated from this MGW. The remoteAddress
must be a valid MGW gatewayAtmAddress within the reach of the connected ATM network.
4 Display the dynamic component AtmCon
In the above example, the AtmIf/20 must be provisioned to a valid ATM port with PNNI
signaling.
5 Display the receive cell and transmit cell of AtmIf/20 Vcc/0.108 and they should keep increasing
while the call is up.
card via Sonet TDM trunking. In this sense the physical multiplexing and
framing hierarchy are much the same as in the MG17 release except that no
AAL1 fabric connection is required to transport the TDM data from a
separate card to the Vsp. The Vsp now has Sonet ports for direct TDM
connection to PSTN or BSS equipment as in Figure 7-6 below.
Figure 7-6
Example of TDM Bearer connection
AAL2 AAL2
B Remote MG A
S ATM N
(SVC)
S SPM ATM OC3
/ TDM (SVC) O
OC3
M C
3
U A
X T
S VSP M
ATM
AAL2
M Central MG AAL2 ATM
S (SVC)
4 OC3
C A
TDM
SPM ATM
p
O N
OC3 (SVC)
C
3
A
T
VSP M
1 Check the alarmStatus of the connected DS1. If it is not empty, there is some problem with
physical connection.
2 Check the alarm status of the DS1 and insure the following values.
3 If any of these values are not as shown above check the far end physical connection and
provisioning for the DS1 to insure they match.
The SS7 signaling from a remote BSS A interface is transported to the MSC
in the network as shown in Figure 7-7. The SS7 signaling is carried in one of
TDM bearer trunk and converted to an AAL1 trunk except it is not terminated
on VSP. This signaling channel is directly connected to an ATM end point
using SVC. No static ATM trunks have to be provisioned within the ATM
network. Eventually, the ATM packets are converted back to TDM stream on
a central MGW and terminated on MSC. Once the Aal1Ces/ AccessEndPoint
and its peer Aal1Ces PassiveEndPoint are provisioned, the SVC trunk
between two endpoints is established. The ISUP signaling is similar to SS7
but the access network is coming from PSTN instead of BSS. The MF Trunk
uses similar transportation mechanism except it requires all the 24 channels
on the entire DS1 span.
Figure 7-7
SS7signaling backhaul connection: remote BSS to MSC
AAL1
B Remote MG A
S ATM N
(SVC)
S OC3
/ TDM
OC3
M 4pOC3ChSmlr 4pOC3ATM
U
X
S
ATM
AAL1
M Central MG A
S ATM N
(SVC)
C TDM OC3
OC3
4pOC3ChSmlr 4pOC3ATM
The SS7 signaling from the central BSS A interface is transported to the MSC
in Figure 10. The SS7 signaling is carried in one of TDM bearer channel and
converted to an AAL1 trunk except it is not terminated on VSP. This AAL1
trunk is directly connected to an ATM end point using SVC. Eventually, the
ATM packets are converted back to TDM stream terminated on MSC. The
ISUP signaling is similar to SS7 but the access network is coming from PSTN
instead of BSS. The MF Trunk uses similar transportation mechanism except
it requires all the 24 channels on the entire DS1 span.
Figure 7-8
SS7signaling backhaul connection: central region BSS to MSC
AAL1
TDM ATM
B OC3 (SVC) M
S OC3 S
TDM
S OC3 C
/
M 4pOC3ChSmlr 4pOC3ChSmlr
U Aal1Ces Aep Pep Aal1Ces
X
S
Central MGW
Procedure 7-9
Checking the SS7/ISUP/MF connection between a remote region and the MSC
1 Verify the Aal1Ces provisioning. This component should link to the SS7/ISUP/MF TDM channel
at one end. And at the other end, it links with an ATM VCC trunk dynamically.
l aal1ces/* Aep
Aal1Ces/161 Aep
d -p Aal1Ces/161 interfacename
Aal1Ces/161
interfaceName = Lp/4 Sonet/0 Sts/0 Vt1dot5/1,1 DS1 Chan/1
d -p Aal1Ces/161 Aep
Aal1Ces/161 Aep
expectedRemoteAddress = ""
localAddress = 471391111111111111111250010020480D100230
activeEndPointType = svc
addressToCall = 471391111111111111111260010020480D110230
calledVpiVci = 0.1
routingOption = atmOnly
profile =
firstRetryInterval = 10 seconds
retryLimit =0
2 If the MGW under investigation is a remote MGW, the addressToCall has to match the
localAddress of Aal1Ces/ Pep in a central MGW for SS7 signaling channel. Go to the central
MGW and find out the matched localAddress.
d Aal1Ces/161 osiState
Aal1Ces/161
adminState = unlocked
operationalState = enabled
usageState = busy
availabilityStatus =
proceduralStatus =
controlStatus =
alarmStatus =
standbyStatus = notSet
unknownStatus = false
5 Check the dynamically generated AtmCon component and trace it to the connected Multiservice
Switch shelf. The Trace command can be used to follow the link between remote MGW to the
central MGW.
d Aal1Ces/161 AtmCon
Aal1Ces/161 AtmCon
nextHop = AtmIf/80 Vcc/0.845 Ep
6 Verify the TDM signaling channel OSI state. If the operationalState is disabled, check all the
parent component OSI states. If one of the operationalState is disabled, check the
4pOC3ChSmlr card cable connection.
7 Check the alarmStatus of the connected DS1. If it is not empty, there is some problem with
physical connection or setting on Chan component.
8 Check the provisioning on Chan component. The timeslots attribute should be set to 24 and the
applicationFramerName should be linked to correct Aal1Ces.
Procedure 7-10
SS7/ISUP/MF backhaul connection problem between a central region and the MSC
1 Verify the Aal1Ces provisioning. This component should link to the SS7/ISUP/MF TDM channel
at one end. And at the other end, it links with another Aa11Ces end point on the same shelf that
is connected to the MSC.
l aal1ces/* Aep
Aal1Ces/11014 Aep
d -p Aal1Ces/11014 interfacename
Aal1Ces/11014
interfaceName = Laps/10111 Sts/0 Vt1dot5/1,4 DS1 Chan/0
d -p Aal1Ces/11014 aep
Aal1Ces/11014 Aep
expectedRemoteAddress = ""
localAddress = 470000000000000000000002890020480D551014
activeEndPointType = svc
addressToCall = 470000000000000000000002890020480D550012
calledVpiVci = 0.1
routingOption = atmOnly
profile =
firstRetryInterval = 10 seconds
retryLimit =0
2 The addressToCall has to match the localAddress of Aal1Ces/ Pep in the same shelf.
d Aal1Ces/11014 osistate
Aal1Ces/11014
adminState = unlocked
operationalState = enabled
usageState = busy
availabilityStatus =
proceduralStatus =
controlStatus =
alarmStatus =
standbyStatus = notSet
unknownStatus = false
5 Verify the TDM signaling channel OSI state. If the operationalState is disabled, check all the
parent component OSI states. If one of the operationalState is disabled, check the
4pOC3ChSmlr card cable connection.
6 Check the alarmStatus of the connected DS1. If it is not empty, there is some problem with
physical connection or setting on Chan component.
7 Check the provisioning on Chan component. The timeslots attribute should be set to 24 and the
applicationFramerName should be linked to correct Aal1Ces.
Glare problem 7
Follow the steps in Procedure 7-11 to correct a GLARE problem.
Procedure 7-11
Correcting a GLARE problem
Step Action
1 As the ICOT option for the TST command at the "MAPCI;MTC;TRKS;TTP;Level C7TTP"
level of the XA-Core Maintenance Administration Position is not supported for Media
Gateway Based trunks, COT testing must be performed from the distant end non-R4 MSC or
LEC switching system.
2 To validate proper GLARE functionality for trunk groups connecting to LEC switching systems
the value of GLARETYP in Table TRKSGRP for the trunk group should be SGRPYLD and
GLAREYLD should be Y. The distant end, on the other hand should not yield to glare.
Tone Problem 7
If the tone does not sound as expected, perform the following check in
Procedure 7-12.
Procedure 7-12
Checking the tone set for a tone problem
Check if the tone set is provisioned with the correct country code. For example, in U.S. or
Canada, it should be canadaUsa.
Announcement Problems 7
If there is an announcement problem, follow Procedure 7-13.
Procedure 7-13
Checking for announcement problems
1 Check the provisioning on localAnnouncement component on the VSP card.
2 In this example, three files with 322_1 as a prefix should be found in the directory /user/PVG/
announcements.
cd -p("user/PVG/announcements") fs
Fs
ok 2003-11-07 17:05:08.63
ls fs
Fs
Type Prot Size Date Time Name
dir no 0 2003-05-28 11:24:06 .
dir no 0 2003-05-28 11:24:00 ..
file no 633964 2003-05-28 11:28:06 322_1.aud
file no 1091 2003-05-28 11:28:10 322_1.cat
file no 174 2003-05-28 11:28:14 322_1.ind
Procedure 7-14
Switching between active and standby CP cards
d lp/0 activecard
Lp/0
activeCard = Shelf Card/1
2 If the processor card to be removed is the active CP, transfer the traffic to the standby CP.
switchover lp/0
d fs syncStatus
Fs
syncStatus = synchronized
4 Remove the standby CP card per Nortel technical publication NN10600-175 Nortel Multiservice
Switch 7400 Hardware Installation, Maintenance, and Upgrades.
Never remove an active CP from the shelf without going through the proper procedure; failure to
do so may result in a shelf crash. Follow the instructions given in the Nortel publication cited
above.
Table 7-1
Helpful information to collect
H.248 problems d -notab nsta/* vgs mgcif/* Displays operational attributes for
each MgcIf component
H.248 problems d -notab nsta/* vgs h248/* Display operational attributes for
each h248 component
H.248 problems d -notab nsta/* vgs ctrl/mg Displays operational attributes for
each Ctrl/Mg component
H.248 problems d -notab nsta/* vgs ctrl/mg udpport/* Display the UdpPort number for
each MGW
H.248 problems d nsta/* vgs ctrl/mg VrAp Display the operational attributes of
VrAp
H.248 problems d -p nsta/* vgs ctrl/mg VrAp Display the provisioned attributes
of VrAp
H.248 problems d -p -notab nsta/* vgs ctrl/mg Display the IP address provisioned
for each MGW
SVC connection d -p -notab nsta/x vgs aal2svc prof/* Display the provisioned attributes
problems of Prof component for the VSP
card x
SVC connection d -notab nsta/x vgs aal2svc tconn/* Display the operational attributes of
problems tconn for the VSP card x if tconn
exists
TDM bearer d laps/x Sts/y vt1dot5/l.m DS1 Display the operational attributes of
connection DS1 component for the VSP card
problems x, sts/y and vt1dot5/l m.
sheet 1 of 2
Table 7-1
Helpful information to collect (continued)
TDM bearer d p laps/x Sts/y vt1dot5/l.m DS1 Display the provisioned attributes
connection of DS1 component for the VSP
problems card x, sts/y and vt1dot5/l,m.
TDM bearer d p laps/x Sts/y vt1dot5/l.m DS1 Chan/n Display the provisioned attributes
connection of DS1 component for the VSP
problems card x, sts/y vt1dot5/l,m and Chan/
n.
TDM bearer d -p nsta/x vgs tag/y taguser Display the provisioned attributes
connection of TagUser component for the VSP
problems card x and the tag number y.
sheet 2 of 2
http://nortelnetworks.com/help/contact/global
Additional configuration
You can find all of the configuration required for this cartridge in Preside,
Generic Device Integration Cartridge Installation and Administration Guide,
241-6003-100. There are no additional configuration tasks for this cartridge.
The dcdAddNode utility is used for discovering the device in the network.
The IP Discovery tool is not supported.
Application launching.
Launch point Reachthrough command Element management system
command
Note 1: In MDM, the telnet functionality is obtained by using a Xterm window. Xterm must
be present and accessible from the default path
Note 2: The APS Web Client is launched using Netscape. Netscape must be present and
accessible.
Default C1869999
Component Identifier the name of the component as it appears in component identifier. The
component identifier is indented to indicate its level in the device model
hierarchy.
Criticality An indication of how important the alarm is. The value is from 1 to 4,
where.4 represents the highest level of importance.
Cardinality If known, this is the number of instances possible. The number can be
exact, a range, or an approximation. For example: 1,4, 1-7, 1...n, or ~20.
If the number of instances cannot be determined, this field in the table
is blank.
Instance Naming Possible naming schemes are a set of known names or an arbitrary text
string. Information is only included in this field if the Cardinality field is
blank, or if the value requires explanation.
Discovered An x (x) indicates that software can discover the component. (That is,
there is a discovery class). If this field is blank, software cannot discover
the component.
Polled An x (x) indicates that software polls the component for state change
information. It this field is blank the software does not poll the
component.
Table A-3
Device component model for APS
Component identifier Cardinality Criticality Discovery Poll
Instance naming
Description
APS 1 4 x
APS/<sysName>
sheet 1 of 2
Table A-3
Device component model for APS
Component identifier Cardinality Criticality Discovery Poll
Instance naming
Description
OBJECT 0...n 3
sheet 2 of 2
Trap registration
The dcdAddNode action script is used to register for traps. Use of the IP Discovery tool is also supported.
To use the IP Discovery tool, use Procedure A-1 and Procedure A-2 given on the following pages.
Procedure A-1
Add Network Settings for APS
Step Action
3 Do a save.
Do you want to save? yes
Procedure A-2
Enroll APS from Device Discovery
Step Action
4 Click on Start.
Status I Succeeded
5 Click on Close.
Legend
Describes the possible values for anything in brackets in the component field.
Details
Provides details on the cause of the alarm, and where applicable, the impacts the fault will have on
the system or on other components.
Also, provides the alarm aging period, if applicable. This applies only to set or message alarms that
are automatically cleared after a predefined amount of time has passed (the alarm aging period).
Remedial action
Gives the suggested operator action for correcting the failure (if possible).
Fault code field
Each alarm heading consists of an eight-character fault code identifying the alarm. The fault code consists
of four characters (identifying the device to MDM) a space and then four characters (identifying the
alarm). The fault code is the principal alarm identifier and provides the means by which you can find your
alarm quickly. Fault codes appear sequentially in this chapter for easy access.
Component field
The component field contains the name of the component needing repair or detecting the fault.
Severity field
Severity is always one of: indeterminate, critical, major, minor, warning, or cleared. These values and their
definitions correspond to those defined by OSI in ITU-T X.733.
Following are explanations of the different types of severity:
indeterminatethe system cannot determine the level of severity.
criticalrequires you to react immediately to the failure. Usually it implies that the resource is
completely disabled and that service is affected.
majorrequires that you take immediate corrective measures. The resource is severely disabled and
service is affected.
minorcorrective action should be taken to prevent a more serious fault. The resource is partially
disabled but service is not affected.
warningaction should be taken to diagnose and correct a problem. Some problem has been detected
but the resource is not disabled and service is not affected.
In some cases, more than one trap can raise an alarm against the same fault code. A common case is when
there is a set trap and a corresponding clear trap. In such cases, there is more than one entry for severity.
Status field
For every severity entry, there is a corresponding status entry. Possible status values are:
message indicates a condition in which you may be interested. Alarms whose status value is message
only appear in Preside MDM.
setindicates that a fault or failure has occurred and that an operator action may be required to correct
the problem.
clearindicates the condition has returned to normal. For example, the fault is repaired.
Legend field
The legend field describes the possible values for anything in brackets in the component field.
Details field
The details field explains what caused the alarm. For alarms that are automatically cleared after a preset
amount of time (alarm aging), the alarm aging period is provided.
Remedial action field
The action field contains information telling the operator what actions to take to correct the problem. Not
all alarm descriptions will have this field. The remedial action might include one of the following:
issuing an operator command
replacing hardware
waiting until the alarm clears itself (no action is required)
opening an service request (SR)
clearedall previous alarms on this component are cleared. Alarms that have a status of clear always
have a severity of cleared.
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the Oracle DataBase is not available or the user cannot get a connection to the
DataBase. Maps to APS alarm id 26625.
Remedial action
Check the status of the APS Oracle DataBase. See the UAS SN06 Security and Administration
document for details on checking the APS Oracle DataBase. Contact your next line of support.
C1860002
Component Severity Status
APS/<device name> OBJECT/ critical set
FILE_TRANSFER_MGR_0 cleared clear
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the Oracle DataBase is not available or the user cannot get a connection to the
DataBase. Maps to APS alarm id 43009.
Remedial action
Check the status of the APS Oracle DataBase. See the UAS SN06 Security and Administration
document for details on checking the APS Oracle DataBase. Contact your next line of support.
C1860003
Component Severity Status
APS/<device name> OBJECT/ critical set
AUDIO_MANAGEMENT_0 cleared clear
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the Oracle DataBase is not available or the user cannot get a connection to the
DataBase. Maps to APS alarm id 28673.
Remedial action
Check the status of the APS Oracle DataBase. See the UAS SN06 Security and Administration
document for details on checking the APS Oracle DataBase. Contact your next line of support.
C1860004
Component Severity Status
APS/<device name> OBJECT/ critical set
DATABASE_SERVER_0 cleared clear
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the primary APS is not in-service and redirection is required to the standby
APS. Note: This alarm appears in the APS documentation. However, it is not currently implemented.
Maps to APS alarm id 45057.
Remedial action
Not applicable.
C1860005
Component Severity Status
APS/<device name> OBJECT/ <APS managed warning, minor, set
object> major, critical clear
cleared
Legend
<device name> identifies the name of the APS device. <APS managed object> identifies the APS
managed object / software component that the alarm was raised against.
Details
This trap is sent when a alarm notification trap is received from the APS and the APS managed
object does not correspond to one of the following: CONFIG_MANAGER_0, FTP_MANAGER_0,
AUDIO_MANAGEMENT_0, or DATABASE_SERVER_0.
Remedial action
See the alarm text for any remedial action required. Contact your next line of support.
C1866801
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a software exception is raised. See the alarm text for specific information.
Maps to APS log id 26625.
Remedial action
Not applicable.
C1866802
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an SQL exception. See the alarm text for specific information. Maps
to APS log id 26626.
Remedial action
Not applicable.
C1866803
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error while accessing the Oracle DataBase. Maps to APS log id
26627.
Remedial action
Not applicable.
C1866804
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a NULL value was encountered. Maps to APS log id 26628.
Remedial action
Not applicable.
C1866805
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error creating a user. Maps to APS log id 26629.
Remedial action
Not applicable.
C1866806
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error creating a directory. Maps to APS log id 26630.
Remedial action
Not applicable.
C1866807
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error creating a node. Maps to APS log id 26631.
Remedial action
Not applicable.
C1866808
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error removing a node. Maps to APS log id 26632.
Remedial action
Not applicable.
C1866809
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error updating the host file. Maps to APS log id 26633.
Remedial action
Not applicable.
C186680A
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the node is not enabled. Maps to APS log id 26634
Remedial action
Not applicable.
C186680B
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid program group. Maps to APS log id 26635.
Remedial action
Not applicable.
C186680C
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid segment id. Maps to APS log id 26636.
Remedial action
Not applicable.
C186680D
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid package id. Maps to APS log id 26637.
Remedial action
Not applicable.
C186680E
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid PE type. Maps to APS log id 26638
Remedial action
Not applicable.
C186680F
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid selector type. Maps to APS log id 26639.
Remedial action
Not applicable.
C1866810
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid selector value. Maps to APS log id 26640.
Remedial action
Not applicable.
C1866811
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid provisionable set. Maps to APS log id 26641.
Remedial action
Not applicable.
C1866812
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid node id. Maps to APS log id 26642.
Remedial action
Not applicable.
C1866813
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid user id. Maps to APS log id 26643.
Remedial action
Not applicable.
C1866814
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid sys parm value. Maps to APS log id 26644.
Remedial action
Not applicable.
C1866815
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid entity. Maps to APS log id 26645.
Remedial action
Not applicable.
C1866816
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid old password entered for a user. Maps to APS log id 26646.
Remedial action
Not applicable.
C1866817
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the CallP selector value is not unique. Maps to APS log id 26647.
Remedial action
Not applicable.
C1866818
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the program group is not unique. Maps to APS log id 26648.
Remedial action
Not applicable.
C1866819
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the provision set is not unique. Maps to APS log id 26649.
Remedial action
Not applicable.
C186681A
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the selector type display value is not unique. Maps to APS log id 26650.
Remedial action
Not applicable.
C186681B
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the user has no access to the program group. Maps to APS log id 26651.
Remedial action
Not applicable.
C186681C
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the selector type already exists. Maps to APS log id 26652.
Remedial action
Not applicable.
C186681D
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the selector value already exists. Maps to APS log id 26653.
Remedial action
Not applicable.
C186681E
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the association already exists. Maps to APS log id 26654.
Remedial action
Not applicable.
C186681F
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when an exit code is encountered while changing permissions. Maps to APS log id
26655.
Remedial action
Not applicable.
C1866820
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when an exit code is encountered while removing a node. Maps to APS log id 26656.
Remedial action
Not applicable.
C1866821
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when an exit code is encountered while removing the user directory for a user. Maps
to APS log id 26657.
Remedial action
Not applicable.
C1866822
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there are inconsistent array sizes. Maps to APS log id 26658.
Remedial action
Not applicable.
C1866823
Component Severity Status
APS/<device name> OBJECT/ critical set
CONFIG_MANAGER_0 cleared clear
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the CallP value is not unique. Maps to APS log id 26659.
Remedial action
Not applicable.
C1866824
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the selector value is not unique. Maps to APS log id 26660.
Remedial action
Not applicable.
C1866825
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the selector type display value is not unique. Maps to APS log id 26661.
Remedial action
Not applicable.
C1866826
Component Severity Status
APS/<device name> OBJECT/ warning message
CONFIG_MANAGER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid AE type. Maps to APS log id 26662.
Remedial action
Not applicable.
C1867001
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a software exception is raised against the AUDIO_MANAGEMENT_0
software component. Maps to APS log id 28673.
Remedial action
Not applicable.
C1867002
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an SQL exception. Maps to APS log id 28674.
Remedial action
Not applicable.
C1867003
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error while accessing the Oracle DataBase. Maps to APS log id
28675.
Remedial action
Not applicable.
C1867004
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a user is beginning a session. Maps to APS log id 28676.
Remedial action
Not applicable.
C1867005
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a user ends a session. Maps to APS log id 28677.
Remedial action
Not applicable.
C1867006
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the user status is not active. Maps to APS log id 28678.
Remedial action
Not applicable.
C1867007
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a user is uploading files. Maps to APS log id 28679.
Remedial action
Not applicable.
C1867008
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error while reading from a file. Maps to APS log id 28680.
Remedial action
Not applicable.
C1867009
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error while writing to a file. Maps to APS log id 28681.
Remedial action
Not applicable.
C186700A
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error deleting a file. Maps to APS log id 28682.
Remedial action
Not applicable.
C186700B
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid file or directory. Maps to APS log id 28683.
Remedial action
Not applicable.
C186700C
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a directory is created. Maps to APS log id 28684.
Remedial action
Not applicable.
C186700D
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a new segment id is generated. Maps to APS log id 28685.
Remedial action
Not applicable.
C186700E
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a segment id is released. Maps to APS log id 28686.
Remedial action
Not applicable.
C186700F
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a new package id is generated. Maps to APS log id 28687.
Remedial action
Not applicable.
C1867010
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a package id is released. Maps to APS log id 28688.
Remedial action
Not applicable.
C1867011
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the max number of versions is reached for physical segment id. Maps to APS
log id 28689.
Remedial action
Not applicable.
C1867012
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the max version number for physical segment id is exceeded. Maps to APS
log id 28690.
Remedial action
Not applicable.
C1867013
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the max number of versions for package id is reached. Maps to APS log id
28691.
Remedial action
Not applicable.
C1867014
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the max version number for package id is exceeded. Maps to APS log id
28692.
Remedial action
Not applicable.
C1867015
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the max set depth is reached for set id. Maps to APS log id 28693.
Remedial action
Not applicable.
C1867016
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the max sequence depth is reached for sequence id. Maps to APS log id 28694.
Remedial action
Not applicable.
C1867017
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there are no segments in the DataBase. Maps to APS log id 28695.
Remedial action
Not applicable.
C1867018
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid segment id. Maps to APS log id 28696.
Remedial action
Not applicable.
C1867019
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid physical segment id. Maps to APS log id 28697.
Remedial action
Not applicable.
C186701A
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid package id. Maps to APS log id 28698.
Remedial action
Not applicable.
C186701B
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid PE type. Maps to APS log id 28699.
Remedial action
Not applicable.
C186701C
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid program group. Maps to APS log id 28700.
Remedial action
Not applicable.
C186701D
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid selector type. Maps to APS log id 28701.
Remedial action
Not applicable.
C186701E
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid selector value. Maps to APS log id 28702.
Remedial action
Not applicable.
C186701F
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a zip archive is extracted. Maps to APS log id 28703.
Remedial action
Not applicable.
C1867020
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an infinite loop in set id. Maps to APS log id 28704.
Remedial action
Not applicable.
C1867021
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an infinite loop in sequence id. Maps to APS log id 28705.
Remedial action
Not applicable.
C1867022
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the segment id is not unique. Maps to APS log id 28706.
Remedial action
Not applicable.
C1867023
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the alias is not unique. Maps to APS log id 28707.
Remedial action
Not applicable.
C1867024
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the selector value is not unique. Maps to APS log id 28708.
Remedial action
Not applicable.
C1867025
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when segment id and alias are not unique. Maps to APS log id 28709.
Remedial action
Not applicable.
C1867026
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is no permission to set cache for user. Maps to APS log id 28710.
Remedial action
Not applicable.
C1867027
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is no permission to change lock status for user. Maps to APS log id
28711.
Remedial action
Not applicable.
C1867028
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when segment id cannot be added to locked package. Maps to APS log id 28712.
Remedial action
Not applicable.
C1867029
Component Severity Status
APS/<device name> OBJECT/ warning message
AUDIO_MANAGEMENT_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid package format, and the segment id cannot be added to the
package. Maps to APS log id 28713.
Remedial action
Not applicable.
C186A801
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a software exception is raised against the FILE_TRANSFER_MGR_0
software component. Maps to APS log id 43009.
Remedial action
Not applicable.
C186A802
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when an SQL exception occurs. Maps to APS log id 43010.
Remedial action
Not applicable.
C186A803
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is a IO file error. Maps to APS log id 43011.
Remedial action
Not applicable.
C186A804
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a connection to host IP is established. Maps to APS log id 43012.
Remedial action
Not applicable.
C186A805
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a connection could not be established to host IP. Maps to APS log id 43013.
Remedial action
Not applicable.
C186A806
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when unable to change to a directory. Maps to APS log id 43014.
Remedial action
Not applicable.
C186A807
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a file could not be transferred. Maps to APS log id 43015.
Remedial action
Not applicable.
C186A808
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a zip archive is extracted. Maps to APS log id 43016.
Remedial action
Not applicable.
C186B001
Component Severity Status
APS/<device name> OBJECT/ warning message
DATABASE_SERVER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the APS is not primary. Maps to APS log id 45057.
Remedial action
Not applicable.
C186B002
Component Severity Status
APS/<device name> OBJECT/ warning message
DATABASE_SERVER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the session timer has expired. Maps to APS log id 45058.
Remedial action
Not applicable.
C186B003
Component Severity Status
APS/<device name> OBJECT/ warning message
DATABASE_SERVER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a software exception is raised against the DATABASE_SERVER_0 software
component. Maps to APS log id 45059.
Remedial action
Not applicable.
C186B004
Component Severity Status
APS/<device name> OBJECT/ warning message
DATABASE_SERVER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an RMI exception. Maps to APS log id 45060.
Remedial action
Not applicable.
C186B005
Component Severity Status
APS/<device name> OBJECT/ warning message
DATABASE_SERVER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an error while accessing the Oracle DataBase. Maps to APS log id
45061.
Remedial action
Check the status of the APS Oracle DataBase. See the UAS SN06 Security and Administration
document for details on checking the APS Oracle DataBase. See your next line of support.
C186B006
Component Severity Status
APS/<device name> OBJECT/ warning message
DATABASE_SERVER_0
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when there is an invalid OpCode. Maps to APS log id 45062.
Remedial action
Not applicable.
C186B801
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_1
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the langver.dat file was not able to be provisioned. Maps to APS log id 47105.
Remedial action
Refer to Trouble-shooting the APS provisioner section of the UAS SN06 Fault Management
document
C186B802
Component Severity Status
APS/<device name> OBJECT/ critical set
FILE_TRANSFER_MGR_1
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when the provisioner experienced early termination. Maps to APS log id 47106.
This alarm is cleared by aging.
Remedial action
Refer to Trouble-shooting the APS provisioner section of the UAS SN06 Fault Management
document. Check the status of the APS Oracle DataBase. See the UAS SN06 Security and
Administration document for details on checking the APS Oracle DataBase. Contact your next line
of support.
C186B803
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_1
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a specified node was not provisioned. Maps to APS log id 47107.
Remedial action
Refer to Trouble-shooting the APS provisioner section of the UAS SN06 Fault Management
document
C186B81F
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_1
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a file cannot be accessed. Maps to APS log id 47135.
Remedial action
Not applicable.
C186B863
Component Severity Status
APS/<device name> OBJECT/ warning message
FILE_TRANSFER_MGR_1
Legend
<device name> identifies the name of the APS device.
Details
This trap is sent when a segment was not able to be provisioned. Maps to APS log id 47203.
Remedial action
Refer to Trouble-shooting the APS provisioner section of the UAS SN06 Fault Management
document
>d time
Time
mainServer = 0.0.0.0
syncSources =
xntpVersion = 3
>d -o time
Note the offset. Add 60 to the offset and set the new time offset. If the current
offset is 300, then set the time offset to 360 as follows:
>d -o time
Note the offset. Subtract 60 from the offset and set the new time offset. If the
current offset is 300, then set the time offset to 240 as follows:
Appendix C: Component
NarrowbandServicesTrunkOverATM
(Nsta) C
This appendix contains CDL descriptions for component
NarrowbandServicesTrunkOverATM (Nsta) and its subcomponents. All the
attributes specific to the MG18 release, including operational, collected
statistic, and provisionable attributes, are included. Additional CDL
information for components and attributes common to the Multiservice Switch
(formerly known as Passport) family can be found in the following documents:
NN10600-060_Overview, Nortel Multiservice Switch 7400/15000/20000
Components Overview
the NN10600-060 series of NTPs that reference components
alphabetically.
Component Nsta and its subcomponents are presented below, beginning with
the Instance and Groups descriptions.
Scope Device
Description NarrowbandServicesTrunkOverATM/n
This component represents the application which is responsible for managing
voice services on a Voice Services Processor (VSP) card.
Mib Nsta
Description This group contains provisioning data for the Nsta Component.
Mib Nsta
Criticality Process
Description This attribute specifies a hardware link to a Vsp component on a Voice Services
Processor FP.
Mib Nsta
Default No default
Criticality Process
Description This attribute specifies the pattern that is transmitted on the TDM interface when
a particular timeslot is not used.
Mib Nsta
Default H.7f
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Nsta
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Nsta
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Nsta
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Nsta
Values idle
active (activ)
busy
Default idle
Description This group contains aggregate statistical data incorporating statistics from all Nsta
Connections.
Mib Nsta
Description This attribute counts the number of packets received on unconfigured CIDs. The
Brag cidList holds all valid CIDs. Any packets received on a CID which is not
valid will be dropped and counted.
The counter wraps to 0 when it exceeds its maximum value.
This attribute is not displayed if there is a Vgs component under the Nsta
component.
Mib Nsta
Default No default
Description This attribute indicates the VPI, VCI and CID (AAL2 Channel ID) of the last
dropped AAL2 packet received on an unprovisioned CID. The value is displayed
in the format vpi.vci.cid.
This attribute is not displayed if there is a Vgs component under the Nsta
component.
Mib Nsta
Default No default
Scope Device
Mib Vgs
Description This group contains the attribute for a components Customer Identifier (CID).
Refer to the attribute description for a detailed explanation of CIDs.
Mib Vgs
Every component has a CID. If a component has a cid attribute, the components
CID is the provisioned value of that attribute; otherwise the component inherits
Every operator session also has a CID, which is the CID provisioned for the
operators user ID. An operator will see only the stream data for components
having a matching CID. Also, the operator will be allowed to issue commands for
only those components which have a matching CID.
Mib Vgs
Default 0
Description This group contains the provisioning data for the Vgs component.
Mib Vgs
Criticality Component
This address is used for identifying this gateway to remote gateways. A change in
the value of this attribute causes all current calls to be dropped.
This attribute is only relevant when one of the following features is provisioned:
vgsAtm
vgsAtmDc
vgsAtmG729
mgw
multiPartyMgw
Mib Vgs
Default No default
Criticality Component
Description This attribute specifies the hostname to identify this gateway. The value
provisioned for this gateway should match the value provisioned in its associated
controller.
This attribute must be unique within the group of gateways controlled by the
controller. A change in the value of this attribute causes all current calls to be
dropped.
Mib Vgs
Default No default
Description This attribute specifies whether the digitizing scheme is mu law or A law.
For Voice over IP, this attribute defines the log law to use at call setup. For Voice
over ATM, this attribute defines a default which can be overridden by the
packetLogLaw attribute of individual AtmTConn components at call setup. This
attribute may be changed without impacting existing calls.
The value provisioned can be overridden by per call values signaled by the
controller in the CRCX (create connection) and MDCX (modify connection)
messages.
There is no relationship between this attribute and the tdmLogLaw attribute of the
Brag component.
Mib Vgs
Values muLaw
aLaw
Default aLaw
Description This attribute specifies the default Differentiated Service Field (DSF) value for all
voice packets transmitted on all IpMConn components.
Mib Vgs
Default 46
Description This attribute specifies the IP address of an associated Remote SGCP/MF IWF to
which SGCP commands (against endpoints provisioned as MF) will be relayed.
Mib Vgs
Values IP address
Default No default
Description This attribute specifies the UDP port of an associated Remote SGCP/MF IWF to
which SGCP commands (against endpoints provisioned as MF) will be relayed.
This attribute is only applicable to IpMConn components and is ignored by
CtrlConn and AtmTConn components.
Mib Vgs
Default 2427
Description This attribute specifies the default tone set for all Brag and Tag subcomponents.
This value can be overwritten by the toneset attribute in the Brag and Tag
components.
Mib Vgs
Values canadaUsa
spain
uk
france
portugal
belgium
germany
netherlands
sweden
austria
italy
switzerland
australia
brazil
ireland
mexico
israel
romania
turkey
czech
china
taiwan
korea
japan
panama
argentina
greece
poland
newZealand
singapore
venezuela
chile
hongKong
malaysia
philippines
thailand
india
russia
jfpt
Default canadaUsa
Description This group contains operational data for the Nsta Vgs component.
Mib Vgs
Description This attribute counts the number of media connections successfully established by
this gateway Vgs component and acknowledged to the Controller.
Mib Vgs
Default No default
Description This attribute indicates the current number of AtmTConn components under the
Vgs that are disabled.
This attribute is only applicable when the vgsAtm, vgsAtmDc, vgsAtmG729, mgw
or multiPartyMgw feature is provisioned. If any other feature is provisioned, this
attribute is filtered.
Mib Vgs
Default No default
Description This attribute indicates the status of the connection to the remote MF signaling
device.
Mib Vgs
Values connected
notConnected
Default notConnected
Description This attribute counts the connections which are identified as carrying fax modem
traffic. The counter wraps to 0 when it reaches its maximum value. The counter
will also be reset to 0 if the Vsp component is locked.
Mib Vgs
Default No default
Description This attribute counts the connections which are identified as carrying non fax
modem traffic. The counter wraps to 0 when it reaches its maximum value. The
counter will also be reset to 0 if the Vsp component is locked.
Mib Vgs
Default No default
Description This attribute indicates the total number of available DS0s for use by this Voice
Gateway Service (VGS).
Mib Vgs
Default No default
Description This attribute indicates the number of DS0s currently in use by this Voice
Gateway Service (VGS).
Mib Vgs
Default No default
Description This attribute indicates the current number of active connections on all
Asynchronous Transfer Mode (ATM) Virtual Channel Connections (VCCs) within
this voice gateway. This includes connections on both provisioned and dynamic
VCCs.
Mib Vgs
Default No default
Description This attribute indicates the current number of active media contexts.
Mib Vgs
Default No default
Description This attribute counts the emergency contexts currently in use. The controller
determines whether a context is for emergency purposes, and instructs the
gateway via the control protocol.
This attribute is only relevant if the H.248 protocol is in use. If any other protocol
is used, this attribute is filtered.
Mib Vgs
Default No default
Description This group stores the connection statistics for the VGS component.
Note these attributes are filtered based on VSP card type as they are not applicable
on 12mVspAal and Vsp2 cards.
Mib Vgs
Description This attribute counts the connections lost to Gateway-detectable network failures.
This includes:
- individual connection media integrity time-outs.
- bulk connection loss due to ATM VCC failure or release or associated component
deprovisioning.
- bulk connection loss due to local IP media link failure or associated component
deprovisioning.
Mib Vgs
Default No default
Description This attribute counts the connections lost to TDM port failure, internal failures or
TDM port deletion since component creation.
Mib Vgs
Default No default
Description This attribute counts the average number of connections over the time interval
given by Nsta/n Vgs timeInterval.The values are sampled every 1 second.
Mib Vgs
Default No default
Description This attribute counts the maximum number of connections at any point over the
time interval given by Nsta/n Vgs timeInterval.
Mib Vgs
Default No default
Description This attribute counts the minimum number of connections at any point over the
time interval given by Nsta/n Vgs timeInterval.
Mib Vgs
Default No default
Description This attribute indicates the number of minutes into the statistical sampling period
for which activeConnectionsAvg, activeConnectionsMin and
activeConnectionsMax are measured.
As per any time interval attribute, this resets to 0 on the quarter hour.
Mib Vgs
Default No default
This attribute is only applicable when the mgw feature is provisioned. If any other
feature is provisioned, the value of this attribute does not change.
This attribute is set to the current number of active connections at the beginning of
each collection interval.
The counter is reset to the current value of the operational attribute activeContexts
at the beginning of the collection interval.
This attribute is only applicable when the H.248 protocol is in use. If any other
protocol is used, the value of this attribute does not change.
Scope Device
Mib Vgs
This command causes an ICMP echo request to be sent to the host specified by
the ipAddr option. If a response is received for the request, a second request is
sent; if no response is received for the first request, no further request is sent.
The remote IP host must respond to an ICMP ping request within 5 seconds of the
request being generated.
This is intended for testing network connections at the IP level. Only one Ping
command per component is allowed to be in progress at any one time.
Description This group contains the provisioning data for the ControlConnection component.
Mib Vgs
Description This attribute specifies the IP address of the media or signaling gateway. Control
messages from the controller will be sent to this IP address to manage connections
within this gateway.
This address is used to advertise the gateway to the local IP router, and to filter
incoming IP packets (only packets destined for this ipAddress attribute value are
accepted; all other packets are silently dropped).
When the ControlConnection component is copied using the Copy command, this
attribute is set to 0.0.0.0 to prevent a duplication of IP addresses.
Mib Vgs
Values IP address
Default No default
Description This attribute specifies the IP addresses of the DNS servers available to this media
gateway. Each DNS server has one IP address associated with it.
If the list is empty then no DNS lookup is attempted by the media gateway.
The list has no implied ordering. If more than one entry is present then one entry
is arbitrarily chosen as the first IP address to use for a DNS lookup.
Mib Vgs
List of IP address
List Size 2
Default No default
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Vgs
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Vgs
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Vgs
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Vgs
Values idle
active (activ)
busy
Default idle
Description This group contains attributes which indicate traffic load and error statistics.
Mib Vgs
Description This attribute counts the messages transmitted since the component was activated.
The value wraps to zero when the maximum value is exceeded.
Mib Vgs
Default No default
Description This attribute counts messages received without errors since the component was
activated. The value wraps to zero when the maximum value is exceeded.
Mib Vgs
Default No default
Description This attribute counts AAL5 errors over this control connection, where AAL5
errors represents the combined total of CRC, Length Field, and
max_SDU_deliver_length errors.
Mib Vgs
Default No default
Description This group contains an attribute which provides information on the status of the
VGS connections.
Mib Vgs
Description This attribute specifies the current status of a Vgs AtmTConn, IpMConn or Ctrl
connection.
enabled indicates that the component is enabled and available to transport traffic.
vspNotReady indicates that the Vsp component linked to the parent Nsta
component is either disabled or locked.
Mib Vgs
Values enabled
activating
atmConnectionNotReady
vspNotReady
outOfResource
ipNetworkInaccessible
Default No default
Scope Device
Mib Vgs
Mib Vgs
Criticality Process
Description This attribute specifies the link to the AtmIf Vcc Nep component that defines the
access to the ATM network.
Mib Vgs
Default No default
Scope Device
Mib Vgs
This command may be used after the connection procedure has been abandoned
due to reaching the maximum number of retries allowed as specified by
retryLimit, or before the limit has been reached.
This command may also be used when a connection has been established, in
which case the connection is released first.
This command fails if the svcStatus attribute has the value initializing or the value
failed.
Description This group contains provisioning data for the Aap component.
Mib Vgs
Criticality Component
Description This attribute specified the ATM service category for SVCs.
The constantBitRate service category is intended for real time applications, that is
The rtVariableBitRate service category is intended for real time applications, that
is those requiring tightly constrained delay and delay variation, as would be
appropriate for voice and video applications. Sources are expected to transmit at a
rate which varies with time. Equivalently, the source can be described as "bursty".
Cells which are delayed beyond the value specified by cellTransferDelay are
assumed to be of significantly reduced value to the application. The real-time
variable bit rate service may support statistical multiplexing of real time sources.
If the parent of the Aap is a Ctrl component then the default value of
atmServiceCategory attribute is nrtVariableBitRate; it may not take the value
rtVariableBitRate. If the parent of the Aap is an IpMConn or Conn component
then the default value of atmServiceCategory attribute is rtVariableBitRate; it
may not take the value nrtVariableBitRate.
Mib Vgs
Default No default
Criticality Component
Description This attribute specifies the peak cell rate of the ATM connection.
Mib Vgs
Units cell/s
Default No default
Criticality Component
Description This attribute specifies the sustained cell rate of the ATM connection. It must be
provisioned with a non-zero value when the atmServiceCategory attribute has the
value rtVariableBitRate or nrtVariableBitRate, and it must be provisioned with
zero value when it has the value constantBitRate.
Mib Vgs
Units cell/s
Default 0
Criticality Component
Description This attribute specifies the maximum burst size, at the peak cell rate, of the ATM
connection. It must be provisioned with a non-zero value when the
atmServiceCategory attribute has the value rtVariableBitRate or
nrtVariableBitRate, and it must be provisioned with zero value when it has the
value constantBitRate.
Mib Vgs
Units cells
Default 0
Criticality Component
Description This attribute specifies the maximum number of consecutive unsuccessful setup
attempts before further attempts are abandoned. If this limit is reached,
management action is required (restart the connection attempts with the Restart
verb). A value of zero indicates no limit; attempts will continue indefinitely until a
successful connection is established.
Mib Vgs
Default 0
Mib Vgs
Criticality Component
Description This attribute specifies the expected remote address information for an incoming
setup request.
Mib Vgs
Default ""
Criticality Process
If a default cannot be generated the operator is forced to set a value for this
attribute. Alternatively, the ModuleData nodePrefix attribute may be provisioned,
and this access point component then deleted and re-added.
Mib Vgs
Default No default
Criticality Component
Description This attribute specifies the list of remote NSAP addresses which this component
can call. At least one address must be provisioned.
For the ControlConnection component in switched VoATM and VoIP and for the
IpMediaStreamConnection application the remote end is a router. It is required to
be able to establish SVCs to different routers. Therefore, the addressToCall
attribute is a list of remote addresses.
The first SVC call is sent to the first address listed in the addressToCall attribute.
If the setup fails or the call is established but fails at a later time, the system
attempts to set up a connection to next address listed in the addressToCall
attribute. If a failure occurs when using the last address in the list, the system
attempts to setup a connection to the first address in the list and then continues as
before.
Mib Vgs
List Size 3
Default No default
Description This group contains operational status information for the Aap component.
Mib Vgs
Description This attribute indicates the status of the SVC connection. When this attribute has
the value initializing, it indicates that the component is initializing when first
created; a connection has not been established, and no incoming setup requests
will be processed.
When this attribute has the value connecting, it indicates that a connection has not
yet been established, but that incoming setup requests are processed. A connection
has been requested but not yet established.
When this attribute has the value connected, it indicates that a connection has
been established.
When this attribute has the value idle, it indicates that the connection has just been
torn down and an attempt to re-establish the connection has not yet occurred. This
is a transient state of the component.
When this attribute has the value retriesExhausted, it indicates that retryLimit
consecutive connection setup attempts have failed, and the connection procedure
has been aborted.
When this attribute has the value failed, it indicates that an error occurred while
sending a release message to the network (as a consequence of a Delete request)
while the component was in connecting state.
Mib Vgs
Values initializing
connecting
connected
idle
retriesExhausted
failed
Default No default
Description This attribute indicates the cause code in the last call release message following
an unsuccessful call setup attempt. The values are as defined in the ATM Forum
ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message
following an unsuccessful call setup attempt. The diagnostic code is contained in
the CAUSE information element and is present only if a procedural error is
detected by the signaling protocol. A diagnostic code is always accompanied by
the cause code.
Mib Vgs
Default No default
Description This attribute indicates the current value of the retry timer for this connection; it
indicates the number of seconds before the next connection attempt is made.
When the value reaches 0 an attempt will be made to establish the connection.
When the timer is not running this attribute has a value of 0.
Mib Vgs
Units seconds
Default No default
Description This attribute counts the number of consecutive failed connection attempts. This
counter is reset to 0 whenever a connection is successfully established or the
connection is restarted using the Restart verb. The counter wraps to zero when the
maximum value is exceeded.
Mib Vgs
Default No default
Description This group contains operational information regarding the end point of the
connection. This group is common to all types of access points.
Mib Vgs
Criticality Component
Description This attribute indicates the address of the remote end point. If a connection is
currently established, it will contain the NSAP address of the remote end point. If
a connection is not established, the remoteAddress attribute has the value
unknown.
Mib Vgs
Default No default
Description This attribute indicates the cause code in the last call release message that
contained the CAUSE information element. Note that the call must have been
successfully established before being torn down. The values are as defined in the
ATM Forum ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message. The
diagnostic code is contained in the CAUSE information element and is present
only if a procedural error is detected by the signaling protocol. A diagnostic code
is always accompanied by the cause code.
Mib Vgs
Default No default
Scope Device
Mib Vgs
Mib Vgs
Criticality Component
Description This attribute specifies the expected remote address information for an incoming
connection setup request.
Mib Vgs
Default ""
Criticality Process
Description This attribute specifies the ATM address of the access point.
If the switch prefix (the nodePrefix attribute of the ModuleData component) has
been provisioned, a default value for localAddress based on the nodePrefix is
provided.
If a default can not be generated the operator is forced to set a value for this
attribute. Alternatively, the ModuleData nodePrefix attribute may be provisioned,
and this access point component then deleted and re-added.
Mib Vgs
Default No default
Description This group contains status information common to the PassiveAccessPoint and
AddresslessPassiveAccessPoint components.
Mib Vgs
Description This attribute indicates the status of the SVC connection. When this attribute has
the value initializing, it indicates that the component is initializing when first
created; a connection has not been established, and no incoming setup requests
will be processed.
When this attribute has the value connecting, it indicates that a connection has not
yet been established, but that incoming setup requests are processed. A connection
has been requested but not yet established.
When this attribute has the value connected, it indicates that a connection has
been established.
When this attribute has the value idle, it indicates that the connection has just been
torn down and an attempt to re-establish the connection has not yet occurred. This
is a transient state of the component.
When this attribute has the value failed, it indicates that an error occurred while
sending a release message to the network (as a consequence of a Delete request)
while the component was in connecting state.
Mib Vgs
Values initializing
connecting
connected
idle
failed
Default No default
Description This group contains operational information regarding the end point of the
connection. This group is common to all types of access points.
Mib Vgs
Criticality Component
Description This attribute indicates the address of the remote end point. If a connection is
currently established, it will contain the NSAP address of the remote end point. If
a connection is not established, the remoteAddress attribute has the value
unknown.
Mib Vgs
Default No default
Description This attribute indicates the cause code in the last call release message that
contained the CAUSE information element. Note that the call must have been
successfully established before being torn down. The values are as defined in the
ATM Forum ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message. The
diagnostic code is contained in the CAUSE information element and is present
only if a procedural error is detected by the signaling protocol. A diagnostic code
is always accompanied by the cause code.
Mib Vgs
Default No default
Scope Device
subcomponents in the Nsta hierarchy which require dynamic links into the ATM
network but have no addressing information.
Mib Vgs
This command may be used after the connection procedure has been abandoned
due to reaching the maximum number of retries allowed as specified by
retryLimit, or before the limit has been reached.
This command may also be used when a connection has been established, in
which case the connection is released first.
This command fails if the svcStatus attribute has the value initializing or the value
failed.
Description This group contains provisioning data for the SpvcAp component.
Mib Vgs
Criticality Component
Description This attribute specifies the ATM service category for SVCs.
The constantBitRate service category is intended for real time applications, that is
those requiring tightly constrained delay and delay variation, as would be
appropriate for voice and video applications. The consistent availability of a fixed
quantity of bandwidth is considered appropriate for constant bit rate service. Cells
which are delayed beyond the value specified by cellTransferDelay are assumed
to have significantly reduced value for the application.
The rtVariableBitRate service category is intended for real time applications, that
is those requiring tightly constrained delay and delay variation, as would be
appropriate for voice and video applications. Sources are expected to transmit at a
rate which varies with time. Equivalently, the source can be described as "bursty".
Cells which are delayed beyond the value specified by cellTransferDelay are
assumed to be of significantly reduced value to the application. The real-time
variable bit rate service may support statistical multiplexing of real time sources.
If the parent of the SpvcAp is a Ctrl component then the default value of
atmServiceCategory attribute is nrtVariableBitRate; it may not take the value
rtVariableBitRate. If the parent of the SpvcAp is an IpMConn component then the
default value of atmServiceCategory attribute is rtVariableBitRate; it may not
take the value nrtVariableBitRate.
Mib Vgs
Default No default
Criticality Component
Description This attribute specifies the peak cell rate of the ATM connection.
Mib Vgs
Units cell/s
Default No default
Criticality Component
Description This attribute specifies the sustained cell rate of the ATM connection. It must be
provisioned with a non-zero value when the atmServiceCategory attribute has the
value rtVariableBitRate or nrtVariableBitRate, and it must be provisioned with
zero value when it has the value constantBitRate.
Mib Vgs
Units cell/s
Default 0
Criticality Component
Description This attribute specifies the maximum burst size, at the peak cell rate, of the ATM
connection. It must be provisioned with a non-zero value when the
atmServiceCategory attribute has the value rtVariableBitRate or
nrtVariableBitRate, and it must be provisioned with zero value when it has the
value constantBitRate.
Mib Vgs
Units cells
Default 0
Criticality Component
Description This attribute specifies the maximum number of consecutive unsuccessful setup
attempts before further attempts are abandoned. If this limit is reached,
management action is required (restart the connection attempts with the Restart
verb). A value of zero indicates no limit; attempts will continue indefinitely until a
successful connection is established.
Mib Vgs
Default 0
Description This group contains NSAP address provisioning data for the SpvcAp component.
Mib Vgs
Criticality Process
If a default cannot be generated the operator is forced to set a value for this
attribute. Alternatively, the ModuleData nodePrefix attribute may be provisioned,
and this access point component then deleted and re-added.
Mib Vgs
Default No default
Criticality Component
Description This attribute specifies the remote VPI and VCI for an SpvcAp component.
Mib Vgs
Default No default
Criticality Component
Description This attribute specifies the list of remote NSAP addresses which this component
can call. At least one address must be provisioned.
For the ControlConnection application in switched VoATM and VoIP and for the
IpMediaStreamConnection application the remote end is a router. It is required to
be able to establish SVCs to different routers. Therefore, the addressToCall
attribute is a list of remote addresses.
The first SVC call is sent to the first address listed in the addressToCall attribute.
If the setup fails or the call is established but fails at a later time, the system
attempts to set up a connection to next address listed in the addressToCall
attribute. If a failure occurs when using the last address in the list, the system
attempts to set up a connection to the first address in the list and then continues as
before.
Mib Vgs
List Size 3
Default No default
Description This group contains operational status information for the SpvcAp component.
Mib Vgs
Description This attribute specifies the status of the SVC connection. When this attribute has
the value initializing, it indicates that the component is initializing when first
created; a connection has not been established, and no incoming setup requests
will be processed.
When this attribute has the value connecting, it indicates that a connection has not
yet been established, but that incoming setup requests are processed. A connection
has been requested but not yet established.
When this attribute has the value connected, it indicates that a connection has
been established.
When this attribute has the value idle, it indicates that the connection has just been
torn down and an attempt to re-establish the connection has not yet occurred. This
is a transient state of the component.
When this attribute has the value retriesExhausted, it indicates that retryLimit for
consecutive connection set up attempts have failed, and the connection procedure
has been aborted.
When this attribute has the value failed, it indicates that an error occurred while
sending a release message to the network (as a consequence of a Delete request)
while the component was in connecting state.
Mib Vgs
Values initializing
connecting
connected
idle
retriesExhausted
failed
Default No default
Description This attribute contains the cause code in the last call release message following an
unsuccessful call set up attempt. The values are as defined in the ATM Forum
ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute contains the diagnostic code in the last call release message
following an unsuccessful call set up attempt. The diagnostic code is contained in
the CAUSE information element and is present only if a procedural error is
detected by the signaling protocol. A diagnostic code is always accompanied by
the cause code.
Mib Vgs
Default No default
Description This attribute indicates the current value of the retry timer for this connection; it
indicates the number of seconds before the next connection attempt is made.
When the value reaches 0 an attempt will be made to establish the connection.
When the timer is not running a value of 0 is returned.
Mib Vgs
Units seconds
Default No default
Description This attribute counts the number of consecutive failed connection attempts. This
counter is reset to 0 whenever a connection is successfully established or the
connection is restarted using the Restart verb. The counter wraps to 0 when the
maximum value is exceeded.
Mib Vgs
Default No default
Description This group contains operational information regarding the end point of the
connection. This group is common to all types of access points.
Mib Vgs
Criticality Component
Description This attribute indicates the address of the remote end point. If a connection is
currently established, it will contain the NSAP address of the remote end point. If
a connection is not established, the remoteAddress attribute has the value
unknown.
Mib Vgs
Default No default
Description This attribute indicates the cause code in the last call release message that
contained the CAUSE information element. Note that the call must have been
successfully established before being torn down. The values are as defined in the
ATM Forum ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message. The
diagnostic code is contained in the CAUSE information element and is present
Mib Vgs
Default No default
Scope Device
The UdpPort component is used to link a UDP port, within a control connection,
to an application that sends and receives packets using the port.
Mib Vgs
Mib Vgs
Description This attribute specifies the application that sends and receives packets using the
UDP port. The application must have a provisionable attribute called
udpPortConnection.
This attribute must be the name of a valid application within the same Vgs
component hierarchy, otherwise a semantic check error will be generated.
Mib Vgs
Default No default
Description This attribute specifies the Differentiated Service Field in IP packets transmitted
using this UDP port. Refer to RFC 791 for service field types.
Mib Vgs
Default 40
Scope Device
Mib Vgs
Description This attribute group contains the operational attributes for the NapAtmConnection
component.
Mib Vgs
Description This attribute shows the component name of the AtmIf Vcc Ep or AtmCon
component to which this switched connection is established.
Mib Vgs
Default No default
Scope Device
The Stream Control Transmission Protocol (SCTP) Port provides access to the IP
network. Note that the instance number indicates the SCTP port number used.
This component is mutually exclusive with UdpPort.
Mib Vgs
Description This group contains the provisioning data for the SctpPort component.
Mib Vgs
Description This attribute specifies the Differentiated Service Codepoint field in IP datagrams
from this port. Refer to RFC 2474. On changing, subsequent datagrams will use
the new value.
Mib Vgs
Default 40
Description This attribute specifies the initial time-out value for the retransmission timer
(RTO). This value is used until a Round Trip Time (RTT) measurement has been
made for the destination transport address.
The value of this attribute must be greater than or equal to the value of the rtoMin
attribute and less than or equal to the value of the rtoMax attribute.
Mib Vgs
Units seconds
Default 1
Description This attribute specifies the minimum permissible value for the recalculated
retransmission timer (RTO). If the computed RTO value is less than rtoMin, the
RTO value is set to the value of rtoMin.
Mib Vgs
Units seconds
Default 1
Description This attribute specifies the smoothing factor used in the computation and
management of the retransmission timer (RTO) in steps of 0.125 (the entered
value is rounded to the nearest multiple of 0.125). These values have been
selected in the SCTP specification as being optimal for this application where
Round Trip Time (RTT) measurements are made not more than once per round-
trip.
Mib Vgs
Default 0.125
Description This attribute specifies the delay variance factor used in the computation and
management of the retransmission timer (RTO) in steps of 0.125 (the entered
value is rounded to the nearest multiple of 0.125).
Mib Vgs
Default 0.250
Description This attribute specifies the message parameter indicating to the receiver how
much increment the sender wishes the receiver to add to its default cookie life-
span.
Mib Vgs
Units seconds
Default 60
Description This attribute specifies the maximum number of retransmission attempts before
the sender of data indicates the destination endpoint as unreachable.
Mib Vgs
Default 2
Description This attribute specifies the maximum permissible value for the recalculated
retransmission timer time-out (RTO). If the computed RTO value is more than
rtoMax, the RTO value is set to the value of rtoMax.
Mib Vgs
Units seconds
Default 2
Description This attribute specifies a link to the Nsta/n Vgs Iua, Nsta/n Vgs V5ua or Nsta/n
Vgs M2ua component that is making use of this port.
Mib Vgs
Default No default
Description An SCTP endpoint monitors the reachability of the idle destination transport
addresses of its peer by sending a heartbeat chunk every heartbeatInterval to the
destination transport address defined for the association.
Mib Vgs
Units seconds
Default 3
Scope Device
This component represents an MGC link to the SCTP port. The IP address and
SCTP port number used in the instance identifier refer to the remote connection.
At most three instances may be provisioned.
Mib Vgs
Description This group contains attributes which describe the SctpLink component status.
Mib Vgs
Description This attribute counts the chunks received on this SctpLink. The counter wraps to 0
when it exceeds the maximum value.
Mib Vgs
Default No default
Description This attribute counts the chunks transmitted on this SctpLink. It includes
retransmitted chunks. The counter wraps to 0 when it exceeds the maximum
value.
Mib Vgs
Default No default
Description This attribute counts the chunks retransmitted on this SctpLink. The counter wraps
to 0 when it exceeds the maximum value.
Mib Vgs
Default No default
Description This attribute indicates the current number of outbound streams for this SCTP
association.
Mib Vgs
Default No default
Description This attribute indicates the current number of inbound streams for this SCTP
association.
Mib Vgs
Default No default
Scope Application
If at least one VrAp component is used within a Nsta/n Vgs component hierarchy,
then all IP network access from within that hierarchy must be via VrAp
components.
Mib Vgs
Description This group contains provisioning data for the VrAp component.
Mib Vgs
Description This attribute specifies the Vr/n Pp/m IpPort LogicalIf/x.y.z.u component instance
to be used by this VrAp.
The value of the ipAddr attribute defined by the parent of this VrAp must belong
to the subnet defined by the specified Vr/n Pp/m IpPort LogicalIf/x.y.z.u
component instance.
Mib Vgs
Default No default
Scope Device
This component represents an ATM connection from the Voice services function
processor to the ATM network. The Vgs component allocates AAL2 streams to
ATM connections as required by the controller. An ATM connection can carry
several AAL2 streams concurrently.
Mib Vgs
Description This group contains provisioning data for the AtmTrunkConnection component.
Mib Vgs
Criticality Component
Description This attribute specifies the ATM address of the node that may be reached via this
trunk.
The remoteAddress attribute must be set to a valid ATM address. This address
must not be the same as the value of the gatewayAtmAddress attribute of the Nsta
Vgs component.
Mib Vgs
Default No default
Criticality Component
The vcci attribute must be set to a value to uniquely identify an ATM trunk
between two nodes. Consequently all ATM trunks between any two nodes must
have distinct vcci attribute values.
The connection on the remote node must be configured with the same vcci
attribute value.
ATM trunks terminating on different remote nodes may share the same vcci
attribute value.
A Check Prov command will fail if the user tries to provision a value greater than
4095 for the vcci attribute of a AtmTConn component, when its subcomponent is
an Aap, a Pap or an SpvcAp.
Mib Vgs
Default No default
Description
This attribute specifies whether the digitizing scheme is mu-law or A-law.
This attribute defines the default that is used by individual AtmTConn components
at call setup unless an alternative value is provided by the controller. The default
value sameAsGateway specifies that the packetLogLaw attribute will take the
same value as the defaultLogLaw attribute of the Vgs.
The remote end of this connection should be provisioned with the same
packetLogLaw attribute value.
Mib Vgs
Values muLaw
aLaw
sameAsGateway
Default sameAsGateway
Criticality Process
Description
This attribute specifies the maximum period of time before a partially filled AAL2
packet is scheduled for transmission. It is also referred to as the combined use
timer period (Timer_CU).
Mib Vgs
Units msec
Default 2.000
Description This attribute specifies the maximum number of AAL2 trunks that may be
allocated on this ATM trunk. The local node may allocate no more than this
number of trunks.
Mib Vgs
Default 240
Description This attribute specifies the length of time that a Channel Identification (CID) will
be quarantined after termination of a call. While quarantined, the CID is not
available to the local trunk selection algorithm; however, it can still be requested
by the remote Media Gateway.
The value of this attribute must be the same across all of the instances of this
component. If any instances of the VgsAal2SvcProfile component are
Mib Vgs
Units seconds
Default 10
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Vgs
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Vgs
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Vgs
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Vgs
Values idle
active (activ)
busy
Default idle
Mib Vgs
Description This attribute indicates the status of the AAL2 common part sublayer alarm. It is
set to loss when the alarm has been raised. It is set to noLoss when the alarm is
cleared.
Mib Vgs
Values noLoss
loss
Default No default
Description This attribute indicates the current number of active AAL2 trunk connections for
the AtmTConn component.
Mib Vgs
Default No default
Mib Vgs
Description This attribute counts the cells received with an AAL2 Common Part Sublayer
Protocol Data Unit (CPS-PDU) Start Field error.
The definition of a Start Field error includes a cell with a parity error or a cell in
which the packet pointed-to by the offset field (OSF) has a packet HEC error.
Mib Vgs
Default No default
Description
This attribute counts the cells received with an unexpected AAL2 Common Part
Sublayer Protocol Data Unit (CPS-PDU) sequence number.
Mib Vgs
Default No default
Description This group contains an attribute which provides information on the status of the
VGS connections.
Mib Vgs
Description This attribute specifies the current status of a Vgs AtmTConn, IpMConn or Ctrl
connection.
enabled indicates that the component is enabled and available to transport traffic.
vspNotReady indicates that the Vsp component linked to the parent Nsta
component is either disabled or locked.
Mib Vgs
Values enabled
activating
atmConnectionNotReady
vspNotReady
outOfResource
ipNetworkInaccessible
Default No default
Scope Device
Mib Vgs
Mib Vgs
Criticality Process
Description This attribute specifies the link to the AtmIf Vcc Nep component that defines the
access to the ATM network.
Mib Vgs
Default No default
Scope Device
Mib Vgs
This command may be used after the connection procedure has been abandoned
due to reaching the maximum number of retries allowed as specified by
retryLimit, or before the limit has been reached.
This command may also be used when a connection has been established, in
which case the connection is released first.
This command fails if the svcStatus attribute has the value initializing or the value
failed.
Description This group contains provisioning data for the ActiveAccessPoint component.
Mib Vgs
Criticality Process
Description This attribute specified the ATM service category for SVCs.
The constantBitRate service category is intended for real time applications, that is
those requiring tightly constrained delay and delay variation, as would be
appropriate for voice and video applications. The consistent availability of a fixed
quantity of bandwidth is considered appropriate for constant bit rate service. Cells
which are delayed beyond the value specified by cellTransferDelay are assumed
to have significantly reduced value for the application.
The rtVariableBitRate service category is intended for real time applications, that
Mib Vgs
Default rtVariableBitRate
Criticality Component
Description This attribute specifies the peak cell rate of the ATM connection.
Mib Vgs
Units cell/s
Default No default
Criticality Component
Description This attribute specifies the sustained cell rate of the ATM connection. It must be
provisioned with a non-zero value when the atmServiceCategory attribute has the
value rtVariableBitRate, and it must be provisioned with zero value when it has
the value constantBitRate.
Mib Vgs
Units cell/s
Default 0
Criticality Component
Description This attribute specifies the maximum burst size, at the peak cell rate, of the ATM
connection. It must be provisioned with a non-zero value when the
Mib Vgs
Units cell/s
Default 0
Criticality Component
Description This attribute specifies the maximum number of consecutive unsuccessful setup
attempts before further attempts are abandoned. If this limit is reached,
management action is required (restart the connection attempts with the Restart
verb). A value of zero indicates no limit; attempts will continue indefinitely until a
successful connection is established.
Mib Vgs
Default 0
Description This group contains operational status information for the Aap component.
Mib Vgs
Description This attribute indicates the status of the SVC connection. When this attribute has
the value initializing, it indicates that the component is initializing when first
created; a connection has not been established, and no incoming setup requests
will be processed.
When this attribute has the value connecting, it indicates that a connection has not
yet been established, but that incoming setup requests are processed. A connection
has been requested but not yet established.
When this attribute has the value connected, it indicates that a connection has
been established.
When this attribute has the value idle, it indicates that the connection has just been
torn down and an attempt to re-establish the connection has not yet occurred. This
is a transient state of the component.
When this attribute has the value retriesExhausted, it indicates that retryLimit
consecutive connection setup attempts have failed, and the connection procedure
has been aborted.
When this attribute has the value failed, it indicates that an error occurred while
sending a release message to the network (as a consequence of a Delete request)
while the component was in connecting state.
Mib Vgs
Values initializing
connecting
connected
idle
retriesExhausted
failed
Default No default
Description This attribute indicates the cause code in the last call release message following
an unsuccessful call setup attempt.The values are as defined in the ATM Forum
ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute contains the diagnostic code in the last call release message
following an unsuccessful call setup attempt. The diagnostic code is contained in
the CAUSE information element and is present only if a procedural error is
detected by the signaling protocol. A diagnostic code is always accompanied by
the cause code.
Mib Vgs
Default No default
(timer)
Access Read only
Description This attribute indicates the current value of the retry timer for this connection; it
indicates the number of seconds before the next connection attempt is made.
When the value reaches 0 an attempt will be made to establish the connection.
When the timer is not running this attribute has a value of 0.
Mib Vgs
Units seconds
Default No default
Description This attribute counts consecutive failed connection attempts. This counter is reset
to 0 whenever a connection is successfully established or the connection is
restarted using the Restart verb. The counter wraps to zero when the maximum
value is exceeded.
Mib Vgs
Default No default
Description This group contains operational information regarding the end point of the
connection. This group is common to all types of access points.
Mib Vgs
Criticality Component
Description This attribute indicates the address of the remote end point. If a connection is
currently established, it will contain the NSAP address of the remote end point. If
a connection is not established, the remoteAddress attribute has the value
unknown.
Mib Vgs
Default No default
(cause)
Access Read only
Description This attribute indicates the cause code in the last call release message that
contained the CAUSE information element. Note that the call must have been
successfully established before being torn down. The values are as defined in the
ATM Forum ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message. The
diagnostic code is contained in the CAUSE information element and is present
only if a procedural error is detected by the signaling protocol. A diagnostic code
is always accompanied by the cause code.
Mib Vgs
Default No default
Scope Device
Mib Vgs
Description This group contains operational status information for the Pap component.
Mib Vgs
Description This attribute indicates the status of the SVC connection. When this attribute has
the value initializing, it indicates that the component is initializing when first
created; a connection has not been established, and no incoming setup requests
will be processed.
When this attribute has the value connecting, it indicates that a connection has not
yet been established, but that incoming setup requests are processed. A connection
has been requested but not yet established.
When this attribute has the value connected, it indicates that a connection has
been established.
When this attribute has the value idle, it indicates that the connection has just been
torn down and an attempt to re-establish the connection has not yet occurred. This
is a transient state of the component.
When this attribute has the value failed, it indicates that an error occurred while
sending a release message to the network (as a consequence of a Delete request)
while the component was in connecting state.
Mib Vgs
Values initializing
connecting
connected
idle
failed
Default No default
Description This group contains operational information regarding the end point of the
connection. This group is common to all types of access points.
Mib Vgs
Criticality Component
Description This attribute indicates the address of the remote end point. If a connection is
currently established, it will contain the NSAP address of the remote end point. If
a connection is not established, the remoteAddress attribute has the value
unknown.
Mib Vgs
Default No default
Description This attribute indicates the cause code in the last call release message that
contained the CAUSE information element. Note that the call must have been
successfully established before being torn down. The values are as defined in the
ATM Forum ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message. The
diagnostic code is contained in the CAUSE information element and is present
only if a procedural error is detected by the signaling protocol. A diagnostic code
is always accompanied by the cause code.
Mib Vgs
Default No default
Scope Device
Mib Vgs
This command may be used after the connection procedure has been abandoned
due to reaching the maximum number of retries allowed as specified by
retryLimit, or before the limit has been reached.
This command may also be used when a connection has been established, in
which case the connection is released first.
This command fails if the svcStatus attribute has the value initializing or the value
failed.
Description This group contains provisioning data for the SpvcAp component.
Mib Vgs
Criticality Component
Description This attribute specifies the ATM service category for SVCs.
The constantBitRate service category is intended for real time applications, that is
those requiring tightly constrained delay and delay variation, as would be
appropriate for voice and video applications. The consistent availability of a fixed
quantity of bandwidth is considered appropriate for constant bit rate service. Cells
which are delayed beyond the value specified by cellTransferDelay are assumed
to have significantly reduced value for the application.
The rtVariableBitRate service category is intended for real time applications, that
is those requiring tightly constrained delay and delay variation, as would be
appropriate for voice and video applications. Sources are expected to transmit at a
rate which varies with time. Equivalently, the source can be described as "bursty".
Cells which are delayed beyond the value specified by cellTransferDelay are
assumed to be of significantly reduced value to the application. The real-time
variable bit rate service may support statistical multiplexing of real time sources.
Mib Vgs
Default rtVariableBitRate
Criticality Component
Description This attribute specifies the peak cell rate of the ATM connection.
Mib Vgs
Units cell/s
Default No default
Criticality Component
Description This attribute specifies the sustained cell rate of the ATM connection. It must be
provisioned with a non-zero value when the atmServiceCategory attribute has the
value rtVariableBitRate, and it must be provisioned with zero value when it has
the value constantBitRate.
Mib Vgs
Units cell/s
Default 0
Criticality Component
Description This attribute specifies the maximum burst size, at the peak cell rate, of the ATM
connection. It must be provisioned with a non-zero value when the
atmServiceCategory attribute has the value rtVariableBitRate, and it must be
provisioned with zero value when it has the value constantBitRate.
Mib Vgs
Units cells
Default 0
Criticality Component
Description This attribute specifies the maximum number of consecutive unsuccessful setup
attempts before further attempts are abandoned. If this limit is reached,
management action is required (restart the connection attempts with the Restart
verb). A value of zero indicates no limit; attempts will continue indefinitely until a
successful connection is established.
Mib Vgs
Default 0
Criticality Process
Description This attribute specifies the remote NSAP address which is called.
Mib Vgs
Default No default
Criticality Component
Description This attribute specifies the remote VPI and VCI for the component.
Mib Vgs
Default No default
Description This group contains operational status information for the Aap component.
Mib Vgs
Description This attribute indicates the status of the SVC connection. When this attribute has
the value initializing, it indicates that the component is initializing when first
created; a connection has not been established, and no incoming setup requests
will be processed.
When this attribute has the value connecting, it indicates that a connection has not
yet been established, but that incoming setup requests are processed. A connection
has been requested but not yet established.
When this attribute has the value connected, it indicates that a connection has
been established.
When this attribute has the value idle, it indicates that the connection has just been
torn down and an attempt to re-establish the connection has not yet occurred. This
is a transient state of the component.
When this attribute has the value retriesExhausted, it indicates that retryLimit
consecutive connection setup attempts have failed, and the connection procedure
has been aborted.
When this attribute has the value failed, it indicates that an error occurred while
sending a release message to the network (as a consequence of a Delete request)
while the component was in connecting state.
Mib Vgs
Values initializing
connecting
connected
idle
retriesExhausted
failed
Default No default
Description This attribute indicates the cause code in the last call release message following
an unsuccessful call setup attempt.The values are as defined in the ATM Forum
ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message
following an unsuccessful call setup attempt. The diagnostic code is contained in
the CAUSE information element and is present only if a procedural error is
detected by the signaling protocol. A diagnostic code is always accompanied by
the cause code.
Mib Vgs
Default No default
Description This attribute indicates the current value of the retry timer for this connection; it
indicates the number of seconds before the next connection attempt is made.
When the value reaches 0 an attempt will be made to establish the connection.
When the timer is not running a value of 0 is returned.
Mib Vgs
Units seconds
Default No default
Description This attribute counts the number of consecutive failed connection attempts. This
counter is reset to 0 whenever a connection is successfully established or the
connection is restarted using the Restart verb. The counter wraps to zero when the
maximum value is exceeded.
Mib Vgs
Default No default
Description This group contains operational information regarding the end point of the
connection. This group is common to all types of access points.
Mib Vgs
Criticality Component
Description This attribute indicates the address of the remote end point. If a connection is
currently established, it will contain the NSAP address of the remote end point. If
a connection is not established, the remoteAddress attribute has the value
unknown.
Mib Vgs
Default No default
Description This attribute indicates the cause code in the last call release message that
contained the CAUSE information element. Note that the call must have been
successfully established before being torn down. The values are as defined in the
ATM Forum ATM User-Network Interface (UNI) Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code in the last call release message. The
diagnostic code is contained in the CAUSE information element and is present
only if a procedural error is detected by the signaling protocol. A diagnostic code
is always accompanied by the cause code.
Mib Vgs
Default No default
Scope Device
Mib Vgs
Description This attribute group contains the operational attributes for the NapAtmConnection
component.
Mib Vgs
Description This attribute shows the component name of the AtmIf Vcc Ep or AtmCon
component to which this switched connection is established.
Mib Vgs
Default No default
Scope Device
This component represents the owner of the Asynchronous Transfer Mode (ATM)
Mib Vgs
Description This group contains the provisioning data for the PathOwner component.
Mib Vgs
Description This attribute specifies the owner of the Asynchronous Transfer Mode (ATM)
protocol connection.
Mib Vgs
Values Link
Default No default
Scope Device
This component provides the control and status of the Local Announcement
facility.
Mib Vgs
Description This group contains the provisioning data for the Local Announcement facility.
Mib Vgs
Description The attribute specifies the filename (without extension) of the announcement
fileset which is used for the LocalAnnouncements component. The files are
located in /user/pvg/announcements/.
Changing the value will not affect announcements in progress. The specified
fileset is automatically transferred from the CP to the FP before it is used and the
file currently being used can be determined from the currentFileName attribute.
Mib Vgs
Default ""
Description This attribute specifies the language to be used on the announcement when no
language is provided via the Media Gateway Controller. This value may be
overridden on a per Brag component basis in the Nsta/n Vgs Brag/n
AnnouncementLanguage component.
Possible values: any 3 character ASCII string (lower case a-z) for example "eng",
or an empty string.
When the Media Gateway Controller specifies a language value, it overrides the
provisioned values in the Media Gateway.
Mib Vgs
Default ""
Description This group contains the three OSI State attributes and the six OSI Status
attributes. The descriptions generically indicate what each attribute implies about
the component. Note that not all the values and state combinations described here
are supported by every component which reuses this group. For component-
specific information and the valid state combinations, refer to the appropriate
NTP.
Mib Vgs
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib Vgs
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib Vgs
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib Vgs
Values idle
active (activ)
busy
Default idle
Description If supported by the component, this attribute indicates the OSI Availability status
of the component. Note that, even though it is defined as a multi-valued set, at
most one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value inTest indicates that the resource is undergoing a test procedure. If
adminState is locked or shuttingDown, the normal users are precluded from using
the resource and controlStatus is reservedForTest. Tests that do not exclude
additional users can be present in any operational or administrative state but the
reservedForTest condition should not be present.
The value failed indicates that the component has an internal fault that prevents it
The value dependency indicates that the component cannot operate because some
other resource on which it depends is unavailable. The operationalState is
disabled.
The value powerOff indicates the resource requires power to be applied and it is
not powered on. The operationalState is disabled.
The value offLine indicates the resource requires a routine operation (either
manual, automatic, or both) to be performed to place it on-line and make it
available for use. The operationalState is disabled.
The value degraded indicates the service provided by the component is degraded
in some way, such as in speed or operating capacity. Usually, the resource remains
available for service. The operationalState is almost always enabled. There is one
exception where an operationalState of disabled is used in conjunction with
degraded for a component which represents a rolled up view of a set of other
components.
The value notInstalled indicates the resource is not present. The operationalState
is disabled.
Mib Vgs
Set of inTest
failed
dependency (depend)
powerOff (pwrOff)
offLine
offDuty
degraded (degrad)
notInstalled (notIn)
logFull
migrating
Default No default
Description If supported by the component, this attribute indicates the OSI Procedural status
of the component. Note that, even though it is defined as a multi-valued set, at
most one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value initializing indicates that initialization has been initiated but is not yet
complete. The operationalState may be enabled or disabled.
The value reporting indicates the resource has completed some processing
operation and is notifying the results. The operationalState is enabled.
Mib Vgs
Default No default
Description If supported by the component, this attribute indicates the OSI Control status of
the component. Note that, even though it is defined as a multi-valued set, at most
one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value subjectToTest indicates the resource is available but tests may be
conducted simultaneously at unpredictable times, which may cause it to exhibit
unusual characteristics.
The value suspended indicates that the service has been administratively
suspended.
Mib Vgs
Default No default
Description If supported by the component, this attribute indicates the OSI Alarm status of the
component. Note that, even though it is defined as a multi-valued set, at most one
value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value underRepair indicates the component is currently being repaired. The
operationalState is enabled or disabled.
The value critical indicates one or more critical alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
The value major indicates one or more major alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
The value minor indicates one or more minor alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
Mib Vgs
Default No default
Description If supported by the component, this attribute indicates the OSI Standby status of
the component.
The value notSet indicates that either the attribute is not supported or that none of
the status conditions described below is present. Note that this is a non-standard
value, used because the original specification indicated this attribute was set-
valued and thus, did not provide a value to indicate that none of the other three are
applicable.
The value hotStandby indicates that the resource is not providing service but will
be immediately able to take over the role of the resource to be backed up, without
initialization activity, and containing the same information as the resource to be
backed up.
The value coldStandby indicates the resource is a backup for another resource but
will not be immediately able to take over the role of the backed up resource and
will require some initialization activity.
Mib Vgs
Default notSet
Description This attribute indicates the OSI Unknown status of the component.
The value false indicates that all of the other OSI State and Status attribute values
can be considered accurate.
The value true indicates that the actual state of the component is not known for
sure.
Mib Vgs
Values false
true
Default false
Description This group contains attributes which indicate the causes of any
LocalAnnouncements component failure.
Mib Vgs
Description This attribute indicates the name (without path or extension) of the current
announcement file which LocalAnnouncements is using for new announcements.
The value may be different from that specified by the fileName attribute if the
value of fileTransferStatus attribute is not complete.
If no file has been transferred, then this attribute is an empty string.
Mib Vgs
Default No default
Description This attribute indicates the status of the transfer of the announcement file from the
CP to the FP.
complete: The file transfer is complete. The file as specified in fileName is the
same as the file specified in currentFileName.
missing: The system cannot find the complete fileset specified in fileName on the
CP. The current file is left as is. An alarm is raised in this state. The FP will poll
for files until transfer can commence.
fileError: The current fileset as defined in fileName on the CP has failed sanity
checks after download, and is not to be used as an active load. The current file is
left as is. An alarm is raised in this state. The FP will poll to look for changes in
file length or timestamp. This causes automatic download to occur once it is
deemed that the file is stable.
Mib Vgs
Values inProgress
complete
missing
fileTooLong
fileError
cpNotResponding
Default No default
Description This attribute counts the announcement requests rejected due to unknown name or
unsupported name or language combination. The value is reset to zero whenever a
new announcement file is transferred or the Supplementary Services Module is
reset.
Mib Vgs
Default No default
Description This attribute counts the announcement requests rejected due to insufficient
resource. The value is reset to zero whenever the Supplementary Services Module
is reset.
Mib Vgs
Default No default
Description This attribute indicates the instantaneous percentage of the local announcement
resource in use.
Mib Vgs
Units %
Default No default
Description This attribute indicates the peak announcement resource used since this attribute
was last reset. The value of this attribute can be reset to 0 by the Zero command.
Mib Vgs
Units %
Default No default
Scope Device
This component creates and enables the Asynchronous Transfer Mode Adaptation
Layer 2 (AAL2) Switched Virtual Circuit (SVC) service.
Mib Vgs
Description This group contains operational data for the Aal2SvcService component.
Mib Vgs
Description This attribute indicates the number of currently active Switched Virtual Circuits
(SVCs) originated by this gateway.
Mib Vgs
Default No default
Description This attribute indicates the number of currently active Switched Virtual Circuits
(SVCs) terminated by this gateway.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) originated
by the gateway.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) terminated
by this gateway.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) deleted
while in the active state carrying traffic.
Mib Vgs
Default No default
Description This attribute indicates the number of Switched Virtual Circuit (SVC) creation
requests currently requested but not yet established.
Mib Vgs
Default No default
Description This attribute indicates the number of Switched Virtual Circuits (SVCs) that are
enabled but not carrying narrowband calls.
Mib Vgs
Default No default
Description This attribute counts the number of Asynchronous Transfer Mode (ATM) network
releases received by the Aal2SvcService component. This provides an indication
of the total number of Switched Virtual Circuits (SVCs) or SVC setup attempts
that failed due to ATM network conditions.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) that were
created by this gateway and deleted without carrying any traffic.
Mib Vgs
Default No default
Description This attribute indicates the number of Switched Virtual Circuits (SVCs) currently
unavailable for trunk selection.
Mib Vgs
Default No default
Description This attribute counts the narrowband connections rejected due to failure of the
Switched Virtual Circuit (SVC) creation process.
Mib Vgs
Default No default
Description This attribute counts the number of times the Switched Virtual Circuit (SVC)
setup timeout expired.
Mib Vgs
Default No default
Description This attribute counts the number of times an Switched Virtual Circuit (SVC) was
overloaded. An SVC is overloaded when narrowband calls are simultaneously
placed on the SVC at both its originating and terminating ends, causing the
activeConnections attribute of the TConn component to exceed the
maxNumberAal2Trunks specified in the Profile component.
Mib Vgs
Default No default
Scope Device
The attributes of this component are only used when SVCs are created and do not
affect values used by an existing trunk.
Mib Vgs
Description This group contains provisioning data for the Profile component.
Mib Vgs
Description This attribute specifies the maximum period of time before a partially filled
Asynchronous Transfer Mode Adaptation Layer 2 (AAL2) packet is scheduled for
transmission. It is also referred to as "combined use timer" (Timer_CU), in the
ITU-T I.363.2.
The holdOverTime affects the packet delay and the bandwidth used by the
connection. The longer the delay the higher the bandwidth efficiency of the ATM
connection and vice versa. The holdOverTime is rounded to the nearest multiple
of 0.125 milliseconds.
Mib Vgs
Units msec
Default 2.000
Description This attribute specifies the maximum number of Asynchronous Transfer Mode
Adaptation Layer 2 (AAL2) trunks that may be allocated on this ATM trunk. The
local node may allocate no more than this number of trunks. The number of
currently active trunks is indicated by the activeConnections attribute of the
TrunkConnection component.
Mib Vgs
Default 4
Description This attribute specifies the length of time that an Asynchronous Transfer Mode
Adaptation Layer 2 (AAL2) Switched Virtual Circuit (SVC) is kept up after the
last narrowband call to use it has been deleted.
This attribute is used to modify the SVC caching system. Longer values result in
larger caches of SVCs.
The value of this attribute must be greater than or equal to the value of the
provisionable attribute terminatedSvcAvailability. This prevents the glare
condition where an SVC is chosen by the SVC terminator while the same SVC is
being deleted by the SVC originator. For optimal results, the same value should be
provisioned on all media gateways to which SVCs can be created.
Mib Vgs
Units seconds
Default 180
Description This attribute specifies the ATM Service Category for Switched Virtual Circuits
(SVCs).
The rtVariableBitRate service category is intended for real time applications, that
is those requiring tightly constrained delay and delay variation, as would be
appropriate for voice and video applications. Sources are expected to transmit at a
rate which varies with time. Equivalently, the source can be described as "bursty".
The real-time variable bit rate service may support statistical multiplexing of real
time sources.
Mib Vgs
Default rtVariableBitRate
Description This attribute specifies the period of time that a terminated Switched Virtual
Circuit (SVC) may be chosen by the local trunk selection algorithm after the last
call using the SVC has been deleted. Once this time expires, the particular SVC
will not be locally picked for new calls. The remote Media Gateway (MGW) may
still request this SVC and those requests are accepted.
The value of this attribute must be less than or equal to the value of the
provisionable attribute svcPersistence. This is necessary to prevent the glare
condition where an SVC is chosen by the SVC terminator while the same SVC is
being deleted by the SVC originator. For optimal results, the same value should be
provisioned on all MGWs to which SVCs can be created.
Mib Vgs
Units seconds
Default 0
Description This attribute specifies the length of time that a Channel Identification (CID) will
be quarantined after termination of a call. While quarantined, the CID is not
available to the local trunk selection algorithm; however, it can still be requested
by the remote Media Gateway.
The value of this attribute must be same as the value of the cidReuseQuarantine
attribute of each provisioned AtmTconn component.
Mib Vgs
Units seconds
Default 10
Description This attribute specifies the length of time allowed for an Switched Virtual Circuit
(SVC) setup before calls waiting for that SVC are cleared.
This attribute is used when trunks are created and does not affect existing trunks.
Mib Vgs
Units msec
Default 1000
Description This attribute specifies whether pre-creation of Switched Virtual Circuits (SVCs)
is enabled.
Mib Vgs
Values enabled
disabled
Default enabled
Description This attribute specifies the prefix digits of the remote Asynchronous Transfer
Mode Adaptation Layer 2 (AAL2) endpoint (Network Service Access Point)
NSAP address.
The value is defaulted to a null string, meaning that it matches any address. Any
Switched Virtual Circuit (SVC) established with a remote NSAP address
matching the prefix digits uses this profile. The Profile with the longest prefix
match is used.
Mib Vgs
Default No default
Description This group contains operational data for the Profile component.
Mib Vgs
Description This attribute indicates the number of currently active Switched Virtual Circuits
(SVCs) originated by this gateway that use this Profile.
Mib Vgs
Default No default
Description This attribute indicates the number of currently active Switched Virtual Circuits
(SVCs) terminated by this gateway that use this Profile.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) originated
by the gateway that use this Profile.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) terminated
by this gateway that use this Profile.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) that use this
Profile which are deleted while in the active state carrying traffic.
Mib Vgs
Default No default
Description This attribute counts the number of Switched Virtual Circuits (SVCs) that were
created by this gateway using this Profile and deleted without carrying any traffic.
Mib Vgs
Default No default
Description This attribute indicates the number of Switched Virtual Circuit (SVC) creation
requests currently requested but not yet established on this gateway that use this
Profile.
Mib Vgs
Default No default
Description This attribute indicates the number of Switched Virtual Circuits (SVCs) that are
enabled and use this Profile but not carrying narrowband calls on this gateway.
Mib Vgs
Default No default
Description This attribute counts the number of Asynchronous Transfer Mode (ATM) network
releases received by the Aal2SvcService component for the Switched Virtual
Circuits (SVCs) that use this Profile. This provides an indication of the total
number of SVCs that use this Profile or SVC attempts that failed due to ATM
network conditions.
Mib Vgs
Default No default
Description This attribute indicates the number of Switched Virtual Circuits (SVCs) that use
this Profile which are currently unavailable for trunk selection.
Mib Vgs
Default No default
Description This attribute counts the narrowband connections rejected due to failure of the
Switched Virtual Circuit (SVC) creation process for SVCs that use this Profile.
Mib Vgs
Default No default
Description This attribute counts the number of times the Switched Virtual Circuit (SVC)
setup timeout expired for SVCs that use this Profile.
Mib Vgs
Default No default
Description This attribute counts the number of times an Switched Virtual Circuit (SVC) that
use this Profile was overloaded. An SVC is overloaded when narrowband calls are
simultaneously placed on the SVC at both its originating and terminating ends,
causing the activeConnections attribute of the TConn component to exceed the
value of maxNumberAal2Trunks attribute.
Mib Vgs
Default No default
Description This attribute indicates the remote Network Service Access Point (NSAP) address
of the last Switched Virtual Circuit (SVC) setup attempt for which the SVC setup
timeout attribute expired for the SVC that uses this Profile.
Mib Vgs
Default No default
Description This attribute indicates the remote Network Service Access Point (NSAP) address
of the last Switched Virtual Circuit (SVC) setup attempt for which the setup
request failed for the SVC that uses this Profile.
Mib Vgs
Default No default
Description This attribute indicates the cause of the last Switched Virtual Circuit (SVC) setup
failure for the SVC that uses this Profile, as defined in the ATM Forum ATM
User-Network Interface Specification.
Mib Vgs
Default No default
Description This attribute indicates the diagnostic code associated with the last Switched
Virtual Circuit (SVC) setup failure for the SVC that uses this Profile, as defined in
the ATM Forum ATM User-Network Interface Specification.
Mib Vgs
Default No default
Description This attribute indicates the remote Network Service Access Point (NSAP) address
of the last Switched Virtual Circuit (SVC) that uses this Profile which did not
experience a normal tear down.
If the string is empty, an abnormal SVC tear down has not occurred.
Mib Vgs
Default No default
Description This attribute indicates the tear down cause for the last Switched Virtual Circuit
(SVC) that uses this Profile and did not experience a normal tear down, as defined
in the ATM Forum ATM User-Network Interface Specification.
Mib Vgs
Default No default
Description This attribute indicates the tear down diagnostic code associated with the last
Switched Virtual Circuit (SVC) that uses this Profile and did not experience a
normal tear down, as defined in the ATM Forum ATM User-Network Interface
Specification.
Mib Vgs
Default No default
The counter is reset to the current value of the operational attribute svcsPending at
the beginning of the next collection interval.
Scope Device
Mib Vgs
Description This group contains operational data for the VgsAal2SvcConnection component.
Mib Vgs
Description This attribute indicates the Asynchronous Transfer Mode (ATM) address of the
node at the remote end of this trunk.
Mib Vgs
Default No default
Description This attribute indicates the Virtual Channel Connection Identifier (VCCI) for this
Virtual Channel Connection (VCC).
The vcci attribute value uniquely identifies a VCC between two nodes in a given
direction.
Mib Vgs
Default No default
Description This attribute indicates whether this Asynchronous Transfer Mode (ATM) Virtual
Channel Connection (VCC) was originated or terminated by this ATM Adaptation
Layer 2 (AAL2) Switched Virtual Circuit (SVC) Service.
Mib Vgs
Values originated
terminated
Default No default
Description This attribute indicates the number of active narrowband connections on this
Asynchronous Transfer Mode (ATM) Virtual Channel Connection (VCC).
Mib Vgs
Default No default
Mib Vgs
Values noLoss
loss
Default No default
Description This attribute counts the number of cells received with an Asynchronous Transfer
Mode Adaptation Layer 2 (AAL2) Common Part Sublayer Protocol Data Unit
(CPS-PDU) Start Field error.
A Start Field error includes a cell with a parity error or a cell in which the packet
pointed to by the offset field (OSF) has a packet Header Error Check (HEC) error.
Mib Vgs
Default No default
Description This attribute counts the number of cells received with an unexpected
Asynchronous Transfer Mode Adaptation Layer 2 (AAL2) Common Part
Sublayer Protocol Data Unit (CPS-PDU) sequence number.
Mib Vgs
Default No default
Description This attribute indicates the component name of the Profile associated with this
Tconn.
Mib Vgs
Default No default
Scope Device
Mib Vgs
Description This attribute group contains the operational attributes for the NapAtmConnection
component.
Mib Vgs
Description This attribute shows the component name of the AtmIf Vcc Ep or AtmCon
component to which this switched connection is established.
Mib Vgs
Default No default
Scope Device
Mib Vgs
Description This group contains the provisioning data for the H248 component.
Mib Vgs
Criticality Component
Description This attribute specifies the Message Identifier that the gateway includes as part of
every message sent to the controller.
Mib Vgs
Default No default
Description This attribute is a link to the Nsta/n Vgs Ctrl/n UdpPort/n component that defines
the Media Gateway (MGW) local UDP port for the H.248 protocol. The default
UDP port for H.248 text format is 2944.
Mib Vgs
Default No default
Description This attribute specifies the Session Description Protocol (SDP) media line
compliance for SDPs sent and received by the gateway.
strictH248 - force strict H.248 SDP media line compliance for both receiving and
transmitting SDPs.
h248 - flexible when receiving SDP media lines. Complies with H.248 when
sending SDP media lines.
nonH248 - flexible when receiving SDP media lines and may send multiple SDP
media lines per SDP group when appropriate.
This attribute is not applicable when the Media Gateway is registered with a
Media Gateway Controller that specifies asn1Ber as the value for the
encodingFormat attribute defined under the Mgc or MgcIf component.
Mib Vgs
Values h248
strictH248
nonH248
Default nonH248
Description This attribute indicates the Session Description Protocol (SDP) format that the
gateway sends when establishing an AAL2 connection.
This attribute is not applicable when the Media Gateway is registered with a
Media Gateway Controller that specifies asn1Ber as the value for the
encodingFormat attribute defined under the Mgc or MgcIf component.
Mib Vgs
Values vgcp
rfc3108
Default rfc3108
Description This attribute specifies an ordered list of links to associated Mgc components,
which specify the provisioned attributes for use with the primary and (multiple)
secondary controllers. The controller preference used by the gateway when
registering is determined by the order of adding links (that is, the first is
preferred).
The list must contain at least one entry. A maximum of three links are allowed.
If the mgw or multiPartyMgw feature is being used then only one link is allowed.
Mib Vgs
List Size 3
Default No default
Description This group contains operational data for the H248 component.
Mib Vgs
Description This attribute is the current H.248 protocol version which the gateway sends in
H.248 transaction requests and is therefore the negotiated version between the
controller and the gateway.
Mib Vgs
Default No default
Description This attribute indicates the maximum number of H.248 contexts supported by the
gateway.
Mib Vgs
Default No default
Description This attribute indicates the current value of the interval within which the
controller expects a response from the gateway, exclusive of network delay.
Mib Vgs
Units msec
Default No default
Description This attribute indicates the current value of the interval within which the gateway
expects a response from the controller, exclusive of network delay.
Mib Vgs
Units msec
Default No default
Description This attribute indicates the current value of the time within which the gateway
expects a Pending Response from the controller if a Transaction cannot be
completed.
Mib Vgs
Units msec
Default No default
Description This attribute indicates the time the gateway will wait for an H.248 message from
the controller before the gateway attempts to contact the controller to determine if
it is still active. The value off indicates that the maximum inactivity timer is not
enabled.
Mib Vgs
Units msec
Default No default
Description This attribute indicates the Message Identifier of the current controller being used.
This value is obtained from the controller response to the gateway registration
message.
Mib Vgs
Default No default
Description This attribute indicates the current controller IP address to which the gateway
sends H.248 transaction requests.
Mib Vgs
Values IP address
Default No default
Description This attribute indicates the current controller UDP port to which the gateway
sends H.248 transaction requests.
Mib Vgs
Default No default
Description This attribute indicates the instance name of the Mgc component currently in use.
Mib Vgs
Default No default
Description This attribute indicates the current value of the time within which the controller
expects a Pending Response from the gateway if a Transaction cannot be
completed.
Mib Vgs
Units msec
Default No default
Description This group contains statistics for the H248 component. These are filtered on
12mVspAal and Vsp2 cards.
Mib Vgs
Description This attribute counts the Add commands processed. The Add command adds a
termination to a context, creating the context if necessary. Wildcarded requests are
counted for each termination the Add is applied to.
Mib Vgs
Default No default
Description This attribute counts the responses sent to the Media Gateway Controller (MGC)
for the Add commands received. The count includes both successful and failed
Mib Vgs
Default No default
Description This attribute counts the Subtract commands processed. The Subtract command
removes a termination from its context and deletes the context if no terminations
remain.Wildcarded requests are counted for each termination the Subtract is
applied to.
Mib Vgs
Default No default
Description This attribute counts the responses sent to the Media Gateway Controller (MGC)
for the Subtract commands received. The count includes both successful and
failed Subtract command responses.
Mib Vgs
Default No default
Description This attribute counts the Modify commands processed. The Modify command
modifies one or more of the properties, events, and signals of a termination.
Wildcarded requests are counted for each termination the Modify is applied to.
Mib Vgs
Default No default
Description This attribute counts the responses sent to the Media Gateway Controller (MGC)
for the Modify commands received. The count includes both successful and failed
Modify command responses.
Mib Vgs
Default No default
Description This attribute counts the Move commands processed. The Move command
atomically moves a termination to another context. Wildcarded requests are
counted for each termination the Move is applied to.
Mib Vgs
Default No default
Description This attribute counts the responses sent to the Media Gateway Controller (MGC)
for the Move commands received. The count includes both successful and failed
Move command responses.
Mib Vgs
Default No default
Description This attribute counts the Notify commands processed. The Notify command
informs the Controller of events occurring in the Gateway.
Mib Vgs
Default No default
Description This attribute counts the responses received for the Notify transactions sent to the
Media Gateway Controller (MGC). The count includes both successful and failed
Notify transaction responses.
Mib Vgs
Default No default
Description This attribute counts the AuditValue commands processed. The Audit Value
command returns the current state of properties, events, signals, and statistics of
terminations. Wildcarded requests are counted for each termination the
AuditValue is applied to.
Mib Vgs
Default No default
Description This attribute counts the responses sent to the Media Gateway Controller (MGC)
for the Audit Value commands received. The count includes both successful and
Mib Vgs
Default No default
Description This attribute counts the AuditCapability commands processed. The Audit
Capabilities command returns all the possible values for termination properties,
events and signals allowed by the Gateway. Wildcarded requests are counted for
each termination the AuditCapability is applied to.
Mib Vgs
Default No default
Description This attribute counts the responses sent to the Media Gateway Controller (MGC)
for the Audit Capability commands received. The count includes both successful
and failed Audit Capability command responses.
Mib Vgs
Default No default
Description This attribute counts the ServiceChange commands sent to the Controller. The
Service Change command allows the Gateway to notify the Controller that a
termination or group of terminations is about to be taken out of service or has just
been returned to service. The Service Change command is also used by the
Gateway to announce its availability to a Controller (registration), and to notify
Mib Vgs
Default No default
Description This attribute counts the responses received for the Service Change transactions
sent to the Media Gateway Controller (MGC). The count includes both successful
and failed Service Change transaction responses.
Mib Vgs
Default No default
Description This attribute counts the ServiceChange commands processed. The Service
Change command is used by the Controller to announce a handover to the
Gateway.Wildcarded requests are counted for each termination the ServiceChange
is applied to.
The Controller may also use service change to instruct the Gateway to take a
termination or group of terminations in to or out of service.
Mib Vgs
Default No default
Description This attribute counts the responses sent to the Media Gateway Controller (MGC)
for the Service Change transactions received. The count includes both successful
and failed Service Change transaction responses.
Mib Vgs
Default No default
Description This attribute counts the unknown commands received from the Media Gateway
Controller (MGC).
Mib Vgs
Default No default
Description This attribute counts the messages with invalid Transaction ID received during the
collection interval in response to the transactions sent to the Media Gateway
Controller (MGC).
Mib Vgs
Default No default
The Controller may also use service change to instruct the Gateway to take a
termination or group of terminations in to or out of service.
Scope Device
Mib Vgs
Description This group contains the provisioning data for the PacketNetworkProfile
component.
Mib Vgs
Criticality Component
Description This attribute represents the capacity of the packet delay variation (PDV) buffer in
milliseconds of data.
To ensure that PDV can be tolerated it is necessary to initialize the system with a
reserve of information in the buffer used to reassemble data for transmission
across the TDM network. The size of this reserve is defined by the pdvt and
bufferSize attributes. The amount of data played out to the TDM network (a
period of time defined by the packetDelayVariationTolerance attribute) is equal to
the size of the initialization reserve. There should be enough data in the
reassembly buffer to allow transmission for a period of time defined by the pdvt
attribute before buffer underflow due to the next delayed packet occurs.
The value should always be greater than the maximum packet size plus two times
the value of the pdvt attribute, except on 2pGeMmSrVsp3 and
2pOC3ChSmIrVsp3 cards where it need only be greater than or equal to two
times the value of the pdvt attribute. The maximum packet size is 20ms for VgsIp,
VgsIpG729, VgsIpGe and VgsIpG729Ge features and 10ms for all other features.
Mib Vgs
Units msec
Default No default
Criticality Component
Description This attribute represents the maximum packet arrival jitter in milliseconds that the
reassembly process will tolerate in the packet stream without producing errors on
the TDM interface.
This attribute together with the bufferSize attribute, can be configured to optimize
the jitter versus absolute delay trade off in various network configurations.
The value should always be less than the value of the bufferSize attribute minus
the maximum packet size divided by two, except on 2pGeMmSrVsp3 and
2pOC3ChSmIrVsp3 cards, where it need only be less than or equal to the value of
the bufferSize attribute divided by two. The maximum packet size is 20ms for
VgsIp, VgsIpG729, VgsIpGe, and VgsIpG729Ge features and 10ms for all other
features.
If set to adaptive, the hardware attempts to minimize the absolute delay while
allowing for the maximum packet arrival jitter encountered. This value is only
supported on the following cards:
2pGeMmSrVsp3,
2pOC3ChSmIrVsp3.
Mib Vgs
Units msec
Default 20
Description This attribute represents the interval of time in seconds for which a loss of packet
condition must persist before the corresponding call is dropped. A value of zero
specifies that packet loss integration is disabled and therefore call connections are
not suspended after packet loss.
Mib Vgs
Units seconds
Default 5
Description This attribute represents the default coding algorithm to be used under normal
conditions (when no 2100 Hz tone is detected).
For each connection, this default coding algorithm can be overridden by the
controller.
When the vgsIpGe feature is provisioned, the value 64kG711 must be used.
When the VSP card type is 2pOC3ChSmIrVsp3, and the vgsIp feature is
provisioned, the value must be either 64kG711 or 8kG729. For all other VSP card
types, the following restrictions apply:
- if the vgsAtm or vgsAtmDc feature is provisioned, the value must be 64kG711 or
32kG726;
- if the vgsIp feature is provisioned, the value must be 64kG711.
Mib Vgs
Values 64kG711
32kG726
24kG726
8kG729
Default 64kG711
Description This attribute represents the coding algorithm to be used when a 2100 Hz tone is
detected (phase reversal may or may not be detected). This attribute takes
precedence over the defaultVoiceRate attribute.
For all card types, this attribute must be set to 64kG711 when using IP transport.
Mib Vgs
Values 64kG711
32kG726
Default 64kG711
Description This attribute represents the time in milliseconds for which the speech path is left
on, before being suppressed when a timeslot is silent. This helps to prevent
clipping at the end of words.
Mib Vgs
Units msec
Default 200
A value of disabled indicates that silence suppression is not performed under any
circumstances.
Mib Vgs
Values enabled
disabled
Default disabled
Description This attribute represents the level above which silence suppression is not
performed. A value in the range -39 to -36 dBm0 is only permitted on
2pGeMmSrVsp3 and 2pOC3ChSmIrVsp3 cards.
Mib Vgs
Units dBm0
Default -40
Description This attribute represents the method by which digit tones are transported.
If set to 64kG711, then G.729 voice channels will upspeed to send 64kG711
packets when DTMF is detected.
If set to squelch, during the playback of a digit, silence is sent over the voice path,
encoded at the current encoding rate.
If set to relay, this value enables negotiation of mutual support for the relay of
DTMF tones as RFC2833 VoIP packets. Should this negotiation fail then behavior
is the same as for 64kG711.
If the Sw Lpt featureList attribute contains vgsAtm, vgsAtmDc or vgsIp and the
card type is 12mVspAal or Vsp2, this attribute is ignored and the value of
sendAsVoice will be the digit tone transport method.
Mib Vgs
Values sendAsVoice
64kG711
squelch
relay
Default No default
Description This attribute represents the method by which voiceband data tones are
transported.
Mib Vgs
Values useTone2100RateIfNegotiated
useTone2100Rate
Default useTone2100RateIfNegotiated
Description This attribute specifies the mechanism that the gateway uses to signal inband
changes in call state to the gateway on the far side of the packet network. This
attribute only applies to the following features:
vgsAtm
vgsAtmG729
itu - Standard User State Control (USC) packets are sent, in compliance with
ITU-T Recommendation 1.366.2 Annex O.
12mVspAal,
Vsp2,
VSP4e,
2pGeMmSrVsp3.
2pGeMmSrVsp3,
2pOC3ChSmIrVsp3.
For the 2pOC3ChSmIrVsp3 card, the default for this attribute is itu. For all other
cards the default for this attribute is proprietary.
Mib Vgs
Values proprietary
itu
Default No default
Scope Device
This component defines default processing for all TDM connections represented
Mib Vgs
Description This group contains the provisioning data for the TdmAccessGroup component.
Mib Vgs
Criticality Process
Description This attribute specifies the link to a Chan component. This Chan component must
exist on the same Functional Processor.
Mib Vgs
Default No default
Description This attribute specifies the TdmNetworkProfile component to use on the TDM
trunks of the Tag component when a call is setup.
Mib Vgs
Default No default
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Vgs
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Vgs
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Vgs
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Vgs
Values idle
active (activ)
busy
Default idle
Description This group contains attributes that indicate the Tag component status.
Mib Vgs
enabled - no failure.
Mib Vgs
Values vgsNotReady
chanNotReady
enabled
chanDegraded
resourceUnavailable
casNotReady
tagUserNotReady
Default No default
Description This group contains operational attributes common to Brag and DBrag.
Mib Vgs
Description This attribute is a list of TDM terminations placed out of service by the controller.
This does not include TDM terminations placed out of service by the gateway.
This attribute is only relevant if the H.248 protocol is in use. If any other attribute
is used, this attribute is filtered.
Mib Vgs
Default No default
Scope Device
This component represents the capability to terminate, process and redirect any
Channel Associated Signaling information associated with the parent component.
Mib Vgs
Description This group contains provisioning data for the Cas component.
Mib Vgs
Criticality Process
Description This attribute specifies a link to an Nsta/n Vgs CasDefn/n component, which
defines the CAS signaling details.
Mib Vgs
Default No default
Description This group contains attributes that indicate the status of a Cas component.
Mib Vgs
Description This attribute counts CAS line signals transmitted towards the TDM interface
since the component was activated.
Mib Vgs
Default No default
Description This attribute counts CAS line signals received from the TDM interface since the
component was activated.
Mib Vgs
Default No default
Description This attribute indicates the number of endpoints in answer or setup state for the
Chan component specified in the interfaceName attribute of the parent
component. This includes only the endpoints that are not in idle or blocked state.
Mib Vgs
Default No default
Description This attribute indicates the number of endpoints in blocked state for the Chan
component specified in the interfaceName attribute of the parent component.
Mib Vgs
Default No default
Description This attribute counts the number of incoming line state changes that are not
recognized as valid candidates for that stage in a call, and that are reported as a
Signal Failure to the MSC call server.
Mib Vgs
Default No default
Scope Application
Service Level 0 (DS0) is the fundamental digital speed level used to classify the
capacities of lines and trunks. It has a standard speed of 66 kilobits per second for
digitizing voice conversation using Pulse Code Modulation (PCM).
Up to 31 instances of this component are created based on the trunk type, E1 can
have 31 instances and T1 can have 24 instances.
Mib Vgs
Description This group contains the operational attributes for the DigitalService0 (Ds0)
component.
Mib Vgs
Description This attribute indicates the Termination Identifier associated with this DS0 in
hexadecimal format (binary).
Mib Vgs
Default No default
Description This attribute indicates the current call state of this DS0. A DS0 can be in one of
the following possible states:
idle - indicates that the DS0 is not being used for a call.
inCall - indicates that the DS0 is in a call.
oos - indicates that the DS0 is out of service.
Mib Vgs
Values idle
inCall
oos
Default No default
Description This attribute indicates the time elapsed since the connection has been established.
Mib Vgs
Units seconds
Default No default
Description This attribute indicates the resource information associated with this DS0, if it is
being used for a call. The resource Identifier contains the Digital Signaling
Processor (DSP) chip Identifier, DSP Core Identifier, and channel Identifier.
Mib Vgs
Default No default
Description This attribute indicates the codec currently used by this DS0 if the DS0 is being
used for a call. A DS0 can use one of the following codecs:
q13 - the Q13 codec.
evrc - the Enhanced Vocoder Rate Control (EVRC) codec.
smv - the Selectable Mode Vocoder (SMV) codec.
g711 - the G711 codec
amr - the Adaptive Multi-Rate (AMR) codec.
Mib Vgs
Values q13
evrc
smv
g711
amr
Default No default
Description This attribute indicates the IP address of the call controller, if this DS0 is being
used for a call.
Mib Vgs
Values IP address
Default No default
Description This attribute indicates the UDP port of the call controller, if this DS0 is being
used for a call.
If the featureList attribute is set to cdmaCodec, this attribute represents the UDP
port of the Activity Concentration Point (ACP). For all other features, it represents
the Media Gateway Controller (MGC) UDP port.
Mib Vgs
Default No default
Scope Application
This component ties a service to a specific Tag component, and hence the set of
timeslots associated with the Tag component. The absence of this component
means that the services can be applied to all the Tag components.
Mib Vgs
Description This group contains the provisioning data for the TdmAccessGroupUser
component.
Mib Vgs
Criticality Process
Mib Vgs
Default No default
Scope Device
This component represents a profile defining TDM network behavior that can be
referenced by Tag components.
Mib Vgs
Description This group contains the provisioning data for the TdmNetworkProfile component.
Mib Vgs
Mib Vgs
Values muLaw
aLaw
autoConfigured
Default autoConfigured
Description This attribute specifies the tone set available to the controller.
vgsAtm,
vgsIp.
Mib Vgs
Values sameAsVgs
canadaUsa
spain
uk
france
portugal
belgium
germany
netherlands
sweden
austria
italy
switzerland
australia
brazil
ireland
mexico
israel
romania
turkey
czech
china
taiwan
korea
japan
panama
argentina
greece
poland
newZealand
singapore
venezuela
chile
hongKong
malaysia
philippines
thailand
india
russia
jfpt
Default sameAsVgs
Description This attribute specifies the value of the minimum power level at which DTMF
digits must be detected. This value is used to allow for different specification for
different administrations. This attribute is ignored if the DigitCollection
component is not present under the parent Vgs.
Mib Vgs
Units dBm0
Default -27
Description This attribute specifies the bit inversion scheme to be applied to G.711 samples on
the TDM side of a Media Gateway.
For applicable features, the default for this attribute is autoConfigure, otherwise
the default for this attribute is noBitInversion.
Mib Vgs
Values noBitInversion
oddBitInversion
evenBitInversion
allBitInversion
autoConfigure
Default No default
Description This attribute specifies the bit inversion scheme to be applied to data on the TDM
side of a Media Gateway for Wireless CSD applications.
Mib Vgs
Values noBitInversion
oddBitInversion
evenBitInversion
allBitInversion
Default noBitInversion
Description This attribute contains a list of Tag components linked to this profile.
Mib Vgs
Default No default
Scope Device
Mib Vgs
Description This group contains the provisioning data for the CasDefn component.
Mib Vgs
Criticality Process
Description This attribute specifies the name (without path or extension) of the file that
contains the specific CAS variant. The file will be delivered with the software
load.
Changing the value of this attribute triggers the transfer of the file from the CP to
the VSP FP, and clears down any existing CAS trunks associated with this
CasDefn component.
Mib Vgs
Default ""
Criticality Process
Description This attribute specifies the type of standard framing used at the TDM interface.
All CasDefn components, under the same Vgs hierarchy, must have the same
value provisioned for this attribute.
ds1 - TDM interfaces associated with this CasDefn component are compliant to
the DS1 standard. CAS signaling transport using DS1 Robbed-Bit Signaling is
used.
e1 - TDM interfaces associated with this CasDefn component are compliant to the
E1 standard. CAS signaling transport using timeslot 16 is used.
Mib Vgs
Values ds1
e1
Default ds1
Description This attribute lists all of the Cas components associated with this CasDefn
component.
Mib Vgs
Default No default
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Vgs
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Vgs
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Vgs
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Vgs
Values idle
active (activ)
busy
Default idle
Description This group contains attributes that indicate the status of the CasDefn component.
Mib Vgs
Description This attribute indicates the status of the transfer of the CAS profile file from the
CP to the VSP FP.
complete: The file transfer is complete. CAS signaling requests against trunks
associated to this CasDefn component are accepted.
missing: The system can not find the file, specified in the fileName attribute, on
the CP. An alarm is raised in this state. The VSP FP polls for the file until the
transfer can commence.
fileTooLong: The file set in the fileName attribute is too long to be loaded
successfully. An alarm is raised in this state. The VSP FP polls to look for
changes in file length or timestamp.
fileError: The file set in the fileName attribute has failed sanity checks after the
transfer, and can not be used. An alarm is raised in this state. The VSP FP polls to
look for changes in file length or timestamp.
Mib Vgs
Values inProgress
complete
missing
fileTooLong
fileError
cpNotResponding
Default missing
Scope Device
This component represents the interface between the Media Gateway Controller
(MGC) and the Media Gateway (MGW).
Mib GsmBicn
Description This group contains the provisioning data for the Mgc component.
Mib GsmBicn
Description This attribute specifies the controller IP address to which the gateway sends the
initial H.248 registration message.
The value provisioned is only in effect on a cold boot of the Media Gateway
(MGW) and thereafter the analogous H.248 parameter may not have the same
setting since it may be modified by the Media Gateway Controller (MGC), via the
root package.
Mib GsmBicn
Values IP address
Default No default
Description This attribute specifies the controller UDP port to which the gateway sends the
initial H.248 registration message.
The controller UDP port to which the gateway sends subsequent H.248
transaction requests may be different from this attribute, depending on whether
H.248 registration redirection, handoff, or failover procedures have been
performed. The controller UDP port currently in use is given by the H248
mgcPort operational attribute.
The value provisioned is only in effect on a cold boot of the Media Gateway
(MGW) and thereafter the analogous H.248 parameter may not have the same
setting since it may be modified by the Media Gateway Controller (MGC), via the
root package.
Mib GsmBicn
Default 2944
Description This attribute specifies the encoding format used by the gateway to send H.248
messages to this controller. The format may be one of the following: -
shortText - a short, space efficient format, suitable for machine transfer, but less
readable.
asn1Ber - ASN.1 binary encoded format, faster than text format but less readable.
Mib GsmBicn
Values shorttext
longtext
asn1Ber
Default shorttext
Criticality Component
Description This attribute specifies the DS3 physical termination identifier format used in the
H.248 messages.
Mib GsmBicn
Default DS3/#2/#1/#2/#1
Criticality Component
Description This attribute represents the E1 physical termination identifier format used by the
controller.
Mib GsmBicn
Default E1/#2/#2/#1
Criticality Component
Description This attribute specifies the STM-n with VC4/VC12 physical termination identifier
format used by the controller.
Mib GsmBicn
Default STM/#1/#1/#1/VC4VC12/#1/#1/#1/#1/#1
Criticality Component
Description This attribute specifies the STS-n/OC-n with VT15 physical termination identifier
format used by the controller.
Mib GsmBicn
Default STS/#1/#1/#1/VT15/#1/#1/#1/#1
Criticality Component
Description This attribute specifies the IP ephemeral termination identifier format being used
by the controller.
Mib GsmBicn
Default rtp/#1
Criticality Component
Description This attribute specifies the AAL2 ephemeral termination identifier format used by
the controller.
Mib GsmBicn
Default aal2/#1
Description This attribute specifies the value of the H.248 MG property root/
normalMGExecutionTime on H.248 cold boot. This is the initial value of the
interval within which the controller expects a response, exclusive of network
delay.
The value provisioned is only in effect on a cold boot of the Media Gateway
(MGW) and thereafter the analogous H.248 parameter may not have the same
setting since it may be modified by the Media Gateway Controller (MGC), via the
root package.
Mib GsmBicn
Units msec
Default 500
Description This attribute specifies the value of the H.248 MG property root/
normalMGCExecutionTime on H.248 cold boot. This is the initial value of the
interval within which the gateway expects a response from the controller,
exclusive of network delay.
The value provisioned is only in effect on a cold boot of the Media Gateway
(MGW) and thereafter the analogous H.248 parameter may not have the same
setting since it may be modified by the Media Gateway Controller (MGC), via the
root package
Mib GsmBicn
Units msec
Default 500
Description This attribute specifies the value of the H.248 MG property root/
MGProvisionalResponseTimerValue on H.248 cold boot. This is the initial value
of the time within which the controller expects a Pending Response from the
gateway if a Transaction cannot be completed.
The value provisioned is only in effect on a cold boot of the Media Gateway
(MGW) and thereafter the analogous H.248 parameter may not have the same
setting since it may be modified by the Media Gateway Controller (MGC), via the
root package
Mib GsmBicn
Units msec
Default 2000
Description This attribute specifies the value of the H.248 MG property root/
MGCProvisionalResponseTimerValue on H.248 cold boot. This is the initial value
of the time within which the gateway expects a Pending Response from the
controller if a Transaction cannot be completed.
The value provisioned is only in effect on a cold boot of the Media Gateway
(MGW) and thereafter the analogous H.248 parameter may not have the same
setting since it may be modified by the Media Gateway Controller (MGC), via the
root package
Mib GsmBicn
Units msec
Default 500
Mib GsmBicn
Default 2
Mib GsmBicn
Units msec
Default 1000
Description This attribute is the H.248 long timer value (LONG-TIMER) used for
quarantining H.248 responses sent to the controller. The gateway will keep H.248
response copies for at least this time.
If the value of this attribute is set to disabled, then H.248 responses are not saved
and therefore duplicate messages that arrive after the response is sent will be
executed as new transactions.
Mib GsmBicn
Units seconds
Default disabled
Description This attribute specifies the default duration of the egress continuity test tone
generated by the gateway.
Mib GsmBicn
Units msec
Default 20000
Description This attribute specifies the highest protocol version to be negotiated with the
controller upon H.248 registration.
Mib GsmBicn
Default 1
Description This attribute specifies a list of links to H248 components that use this
component.
Mib GsmBicn
List Size 1
Default No default
Mib GsmBicn
Description This attribute counts the total control link failures between the Media Gateway
Controller (MGC) and the Media Gateway (MGW).
Control link failures occur when no messages have been received from the MGC
within the time value indicated by the value of the operational attribute,
maximumInactivityTime, of the H248. Control link failures can also occur when
the Nsta Vgs Ctrl/MG is disabled. When a control link failure occurs the MGW
sends an H.248 command of type ServiceChange to the MGC specifying
disconnected as the value of the method field. Control link failure is not
resolved until a response is received from the MGC.
Mib GsmBicn
Default No default
Description This attribute counts the total registration attempts that the Media Gateway
(MGW) made to the Media Gateway Controller (MGC).
The MGW counts each transaction initiated towards the MGC that contains an
H.248 command of type ServiceChange specifying cold or warm as the
value of the method field as a registration attempt.
Mib GsmBicn
Default No default
Description This attribute counts the total registration attempts that the Media Gateway
(MGW) made to the Media Gateway Controller (MGC) that have failed.
Mib GsmBicn
Default No default
Description This attribute counts the number of H.248 messages sent by the Media Gateway
(MGW) to the Media Gateway Controller (MGC).
All H.248 messages sent by the MGW to the specified MGC are included in this
count. Messages containing transaction requests, transaction replies, and
transaction reply acknowledgements are included. Any transactions that are
retransmitted due to a timeout while waiting for a reply or acknowledgement from
the MGC are included in this count as well.
Mib GsmBicn
Default No default
Description This attribute counts the number of octets sent by the Media Gateway (MGW) to
the Media Gateway Controller (MGC).
All H.248 messages sent by the MGW to the specified MGC are included in this
count. The octets counted do not include any of the overhead added by the
transport layer but only the contents of the actual H.248 messages.
Mib GsmBicn
Default No default
Description This attribute counts the number of H.248 messages received by the Media
Gateway (MGW) from the Media Gateway Controller (MGC). This count
includes messages containing transaction requests, transaction replies, and
transaction reply acknowledgements. Any retransmitted transactions are also
counted.
Mib GsmBicn
Default No default
Description This attribute counts the number of octets received by the Media Gateway (MGW)
from the Media Gateway Controller (MGC). The contents of all H.248 messages
received from the MGC are included in this count. The octets counted do not
include any of the overhead added by the transport layer but only the contents of
Mib GsmBicn
Default No default
Description This attribute counts the number of H.248 defined error codes sent to the Media
Gateway Controller (MGC) and is incremented when an H.248 error code is
encoded in a message reply, transaction reply, action reply, or command reply sent
to the MGC. If a transaction reply containing an error code is retransmitted due to
a timeout while waiting for a transaction response acknowledgement from the
MGC, this counter is not incremented. An error code in a given transaction reply
is only counted once regardless of the number of times the transaction reply is
retransmitted.
H.248 error codes are encoded when a message received from the MGC contains
semantic or syntactic errors.
Mib GsmBicn
Default No default
Description This attribute counts the number of syntactically incorrect H.248 messages
received by the Media Gateway (MGW) from the Media Gateway Controller
(MGC).
This count includes corrupted data stream, invalid tags, invalid lengths, violations
of the Basic Encoding Rule (BER) visible constraints, and message size limit
errors.
Since decoding errors would result in an error reply to MGC, the errorsSent
attribute is incremented as well.
Mib GsmBicn
Default No default
Description This attribute counts the number of times the Media Gateway (MGW) has
retransmitted H.248 transaction requests or transaction replies to the Media
Gateway Controller (MGC) due to a timeout while waiting on a transaction reply
or transaction response acknowledgement from the MGC.
Mib GsmBicn
Default No default
Description This attribute counts the number of H.248 transaction requests rejected by the
Media Gateway (MGW) due to overload conditions. In the Nb Media Gateway
this attribute also counts the number of H.248 transaction requests rejected due to
congestion, locked MgcIf component, or internal communication in the MGW.
Since these transactions are explicitly rejected using error replies, the errorsSent
attribute is incremented as well.
Mib GsmBicn
Default No default
Description This attribute counts the number of times that a state of resource congestion has
been entered, and thus, the number of times the MgcIf congestion alarm was set.
Mib GsmBicn
Default No default
Description This attribute counts the number of times throughput congestion has been entered,
and thus, the number of times the MgcIf throughput congestion alarm was set.
Mib GsmBicn
Default No default
Description This attribute counts the number of times that a state of subnet congestion has
been entered, and thus, the number of times that the MgcIf subnet congestion
alarm was set.
Mib GsmBicn
Default No default
Description This attribute counts the expired contexts discovered by the LifeTime Context
Auditor within the Context Database on the Media Gateway (MGW).
Expired contexts occur when a SUBTRACT request from the Media Gateway
Controller (MGC) is not received by the MGW. An expired context also occurs
when the ADD reply from the MGW is not received by the MGC.
Mib GsmBicn
Default No default
Description This attribute counts transactions with ADD commands discarded due to their
queue latency exceeding an internal call rejection latency threshold.
Mib GsmBicn
Default No default
Description This attribute counts transactions discarded due to the queue latency exceeding an
internal stale message discard latency threshold.
Mib GsmBicn
Default No default
Description This attribute counts transactions rejected due to the exhaustion of Media
Gateway ephemeral terminations.
Resource congestion occurs when all available ephemeral terminations are in use
and the Media Gateway can no longer create new ephemeral terminations. When
congestion occurs, transactions containing Add commands are rejected and this
attribute is incremented.
Mib GsmBicn
Default No default
Description This attribute counts the number of seconds for which new media connection
requests have been discarded because the Media Gateway was overloaded.
Mib GsmBicn
Units seconds
Default No default
Description This attribute counts the number of seconds for which add requests have been
rejected due to the exhaustion of Media Gateway ephemeral terminations.
Resource congestion occurs when all available ephemeral terminations are in use
and the Media Gateway can no longer create new ephemeral terminations.
Mib GsmBicn
Units seconds
Default No default
Description This attribute indicates the average message queue latency since the last card
reset.
Message queue latency is the amount of time a message is held within a queue.
Mib GsmBicn
Units msec
Default No default
Description This attribute indicates the message queue latency of the last message retrieved
from the queue.
Message queue latency is the amount of time a message is held within a queue.
Mib GsmBicn
Units msec
Default No default
Description This group contains the three OSI State attributes and the six OSI Status
attributes. The descriptions generically indicate what each attribute implies about
the component. Note that not all the values and state combinations described here
are supported by every component which reuses this group. For component-
specific information and the valid state combinations, refer to the appropriate
NTP.
Mib GsmBicn
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib GsmBicn
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib GsmBicn
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib GsmBicn
Values idle
active (activ)
busy
Default idle
Description If supported by the component, this attribute indicates the OSI Availability status
of the component. Note that, even though it is defined as a multi-valued set, at
most one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value inTest indicates that the resource is undergoing a test procedure. If
adminState is locked or shuttingDown, the normal users are precluded from using
the resource and controlStatus is reservedForTest. Tests that do not exclude
additional users can be present in any operational or administrative state but the
reservedForTest condition should not be present.
The value failed indicates that the component has an internal fault that prevents it
from operating. The operationalState is disabled.
The value dependency indicates that the component cannot operate because some
other resource on which it depends is unavailable. The operationalState is
disabled.
The value powerOff indicates the resource requires power to be applied and it is
not powered on. The operationalState is disabled.
The value offLine indicates the resource requires a routine operation (either
manual, automatic, or both) to be performed to place it on-line and make it
available for use. The operationalState is disabled.
The value degraded indicates the service provided by the component is degraded
in some way, such as in speed or operating capacity. Usually, the resource remains
available for service. The operationalState is almost always enabled. There is one
exception where an operationalState of disabled is used in conjunction with
degraded for a component which represents a rolled up view of a set of other
components.
The value notInstalled indicates the resource is not present. The operationalState
is disabled.
Mib GsmBicn
Set of inTest
failed
dependency (depend)
powerOff (pwrOff)
offLine
offDuty
degraded (degrad)
notInstalled (notIn)
logFull
migrating
Default No default
Description If supported by the component, this attribute indicates the OSI Procedural status
of the component. Note that, even though it is defined as a multi-valued set, at
most one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value initializing indicates that initialization has been initiated but is not yet
complete. The operationalState may be enabled or disabled.
The value reporting indicates the resource has completed some processing
operation and is notifying the results. The operationalState is enabled.
Mib GsmBicn
Default No default
Description If supported by the component, this attribute indicates the OSI Control status of
the component. Note that, even though it is defined as a multi-valued set, at most
one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value subjectToTest indicates the resource is available but tests may be
conducted simultaneously at unpredictable times, which may cause it to exhibit
unusual characteristics.
The value suspended indicates that the service has been administratively
suspended.
Mib GsmBicn
Default No default
Description If supported by the component, this attribute indicates the OSI Alarm status of the
component. Note that, even though it is defined as a multi-valued set, at most one
value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value underRepair indicates the component is currently being repaired. The
operationalState is enabled or disabled.
The value critical indicates one or more critical alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
The value major indicates one or more major alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
The value minor indicates one or more minor alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
Mib GsmBicn
Default No default
Description If supported by the component, this attribute indicates the OSI Standby status of
the component.
The value notSet indicates that either the attribute is not supported or that none of
the status conditions described below is present. Note that this is a non-standard
value, used because the original specification indicated this attribute was set-
valued and thus, did not provide a value to indicate that none of the other three are
applicable.
The value hotStandby indicates that the resource is not providing service but will
be immediately able to take over the role of the resource to be backed up, without
initialization activity, and containing the same information as the resource to be
backed up.
The value coldStandby indicates the resource is a backup for another resource but
will not be immediately able to take over the role of the backed up resource and
will require some initialization activity.
Mib GsmBicn
Default notSet
Description This attribute indicates the OSI Unknown status of the component.
The value false indicates that all of the other OSI State and Status attribute values
can be considered accurate.
The value true indicates that the actual state of the component is not known for
sure.
Mib GsmBicn
Values false
true
Default false
Description This group contains the provisioning data for the MgcIf component.
Mib GsmBicn
Description This attribute specifies the congestion alarm level threshold. At least one of the
resource, throughput, or subnetwork congestion alarm is raised when the value of
the congestionPercent attribute of the CallStatistics component rises above this
threshold.
The value of this attribute must be greater than the value of the
congestionAbatementThreshold attribute.
Mib GsmBicn
Units %
Default 90
Description This attribute specifies the congestion alarm level abatement threshold. Any raised
resource, throughput, or subnetwork congestion alarms are cleared when the value
of the congestionPercent attribute of the CallStatistics component falls to or
below this threshold.
The value of this attribute must be less than the value of the congestionThreshold
attribute.
Mib GsmBicn
Units %
Default 70
Description This attribute specifies the time with which to delay congestion package
notification to the Media Gateway Controller (MGC). This delay time has the
effect of reducing the number of congestion notifications sent when the
congestion level crosses above and below any of the ten-percent notification levels
at a high frequency.
Mib GsmBicn
Units seconds
Default 10
Description This attribute specifies the enabling or disabling of overload detection and
prevention on the Media Gateway (MGW).
When the value of this attribute is set to disable, the MGW will not detect
overload or take any preventive actions.
Mib GsmBicn
Values disable
enable
Default enable
Description This attribute specifies the threshold at which the contexts in the Context
Database on the Media Gateway(MGW) are considered to have expired.
If this attribute is set to a value other than zero, then those contexts that are
discovered to have a difference between their creation time and the present time
that exceeds the value of this attribute will be reported to the Media Gateway
Controller (MGC).
Mib GsmBicn
Units minutes
Default 1440
Description This attribute specifies the interval at which the LifeTime Context Auditor will
poll the Context Database to search for contexts that have exceeded the value of
the maximumContextLifeTime attribute.
The maximumContextLifeTime attribute must be set to a value other than zero for
the audit to take place.
Mib GsmBicn
Units minutes
Default 360
Control link failures occur when no messages have been received from the MGC
within the time indicated by the value of the operational attribute,
maximumInactivityTime, of the H248 component. Control link failures can also
occur when the Nsta Vgs Ctrl/MG is disabled. When a control link failure occurs,
the MGW sends an H.248 command of type ServiceChange to the MGC
specifying disconnected as the value of the method field. A control link failure
is not resolved until a response is received from the MGC.
Description This attribute counts the syntactically incorrect H.248 messages received by the
Media Gateway (MGW) from the Media Gateway Controller (MGC).
This count includes corrupted message data, invalid tags, invalid lengths,
violations of the Basic Encoding Rule (BER) visible constraints, and message size
limit errors.
Since decoding errors would result in an error reply to the MGC, the errorsSent
attribute is incremented as well.
H.248 error codes are encoded when a message received from the MGC contains
semantic or syntactic errors.
Description This attribute counts the H.248 messages sent by the Media Gateway (MGW) to
the Media Gateway Controller (MGC).
All H.248 messages sent by the MGW to the specified MGC are included in this
count. Messages containing transaction requests, transaction replies, and
transaction reply acknowledgements are included. Any transactions that are
retransmitted due to a timeout while waiting for a reply or acknowledgement from
the MGC are included in this count as well.
All H.248 messages sent by the MGW to the specified MGC are included in this
count. The octets counted do not include any of the overhead added by the
transport layer but only the contents of the actual H.248 messages.
reconcile the observed octet traffic against the observed call processing traffic,
assisting the operator in refining the expected octet traffic on the MGW against
the expected call processing traffic. This particular octet activity can be a factor in
the MGW entering an overload condition.
The MGW counts each transaction initiated towards the MGC that contains an
H.248 command of type ServiceChange specifying cold or warm as the
value of the method field as a registration attempt.
attribute also counts the H.248 transaction requests rejected due to congestion or
due to MgcIf component being locked.
Since these transactions are explicitly rejected using error replies, the errorsSent
attribute is incremented as well.
Expired contexts occur when a SUBTRACT request from the Media Gateway
Controller (MGC) is not received by the MGW. An expired context also occurs
when the ADD reply from the MGW is not received by the MGC.
Description This attribute counts transactions with ADD commands discarded due to their
queue latency exceeding an internal call rejection latency threshold.
Resource congestion occurs when all available ephemeral terminations are in use
and the Media Gateway can no longer create new ephemeral terminations. When
congestion occurs, transactions containing Add commands are rejected and this
attribute is incremented.
Units seconds
Resource congestion occurs when all available ephemeral terminations are in use
and the Media Gateway can no longer create new ephemeral terminations.
Units seconds
Message queue latency is the amount of time a message is held within a queue.
This attribute indicates the average value within the collection interval.
Units msec
Message queue latency is the amount of time a message is held within a queue.
This attribute indicates the peak value within the collection interval.
Units msec
Scope Device
This component represents the profile of the characteristics of the codec used for
voice calls handled by this Media Gateway.
Mib Vgs
Description This group contains the provisioning data for the VoiceProfile component.
Mib Vgs
Mib Vgs
Values disable
enableWithoutNoDataFrameTx
enableWithNoDataFrameTx
Default disable
Description This attribute specifies the enabling or disabling of the Time Alignment algorithm
for the Iu-UP feature of the Media Gateway.
When the value of this attribute is set to disabled, all time alignment requests
made to the Transcoding Rate Adaptation Unit (TRAU) via the Iu protocol are
rejected.
Mib Vgs
Values disabled
enabled
Default disabled
Description This attribute specifies the external interface type that this voice profile represents.
Mib Vgs
Values iuIf
pstnIf
nbIf
aIf
multiParty
Default iuIf
Description This attribute specifies whether the adaptive dejitter buffer feature is enabled or
disabled.
It should be noted that this parameter is not applicable when the Transcoding and
Rate Adaptation Unit (TRAU) is in Frame Protocol Interworking Function (FPIF)
mode where no transcoding is performed.
Mib Vgs
Values disabled
enabled
Default disabled
Description This attribute specifies the enabling or disabling of the unilateral codec upspeed
feature of the Transcoding Rate Adaptation Unit (TRAU).
When enabled, the bearer connection can be upspeeded from using the Adaptive
Multi-Rate (AMR) codec to the G.711 codec upon detection of a service that
requires G.711 for reliable transport (for example, Global Text Telephony (GTT)
and Circuit-Switched Data (CSD) calls). This operation is performed unilaterally
by the TRAU without intervention from the Media Gateway Controller (MGC).
In order to interoperate with other vendors Media Gateways that do not support
the upspeed mechanism, the value of this attribute should be set to disabled.
Mib Vgs
Values disabled
enabled
Default disabled
Description This attribute specifies the estimated average percentage of time that calls will
carry Adaptive Multi Rate (AMR) voice activity.
The value of this attribute can be estimated by the value of the Nsta/n Vgs
CallStatistics averageAmrVoiceActivity attribute.
Mib Vgs
Units %
Default 60
Description This attribute specifies the support to avoid transcoding when the Integrated
Digital Enhanced Network (iDEN) Vocoder probe is detected and corresponding
Media Gateway engages the iDEN probe. The Transcoding and Rate Adaptation
Unit (TRAU) verifies that both the peer Media Gateways are compatible and
running the same codec before performing the upspeed.
This attribute is enabled for wireless networks where iDEN is supported and
Tandem Free Operation (TFO) is required on detection of the iDEN probe.
This attribute is disabled for the networks where iDEN is not supported, in which
case the voice will be encoded at the current voice rate.
Mib Vgs
Values disabled
enabled
Default disabled
Description This attribute specifies a list of Tag/n component instances to which this
VoiceProfile component is linked.
Mib Vgs
Default No default
Mib Vgs
Default No default
Scope Device
This component represents enabling of the Automatic Gain Control (AGC) voice
quality functionality for all calls on the Media Gateway.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
The egress direction refers to the other direction.
Mib MediaGateway
Description This group contains the provisioning data for the AutomaticGainControl (Agc)
component.
Mib MediaGateway
Description This attribute specifies the direction in which the Automatic Gain Control (AGC)
functionality is enabled.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
The egress direction refers to the other direction.
The value of this attribute must be set to egress for the mgw feature.
Mib MediaGateway
Values egress
ingress
both
Default No default
Description This attribute specifies the target signal power level of the Automatic Gain
Control (AGC) functionality in the ingress direction.
AGC attempts to maintain a consistent call volume at the specified target level.
AGC is performed on the signal using this target value before the value of the
ingressGain attribute of the PktToPktProfile component or the
TdmNetworkProfile component is applied.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
This attribute has no effect if the value of agcDirection attribute is set to egress.
Mib MediaGateway
Units dBm0
Default -19
Description This attribute specifies the minimum gain that can be applied to any frame by the
Automatic Gain Control (AGC) functionality in the ingress direction.
The value of this attribute affects how slowly variations in call volume can be
adjusted towards the value of the ingressAgcTargetLevel attribute when a signal
power gain is required for the adjustment.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
This attribute has no effect if the value of the agcDirection attribute is set to
egress.
Mib MediaGateway
Units dB
Default -10
Description This attribute specifies the maximum gain that can be applied to a frame by the
Automatic Gain Control (AGC) functionality in the ingress direction.
The value of this attribute affects how quickly variations in call volume can be
adjusted towards the value of the ingressAgcTargetLevel attribute when a signal
power gain is required for the adjustment.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
This attribute has no effect if the value of the agcDirection attribute is set to
egress.
Mib MediaGateway
Units dB
Default 10
(egrAgcTargLev)
Access Read: All
Write: All
Description This attribute specifies the target signal power level of the Automatic Gain
Control (AGC) functionality in the egress direction.
AGC attempts to maintain a consistent call volume at the specified target level.
AGC is performed on the signal using this target value before the value of the
egressGain attribute of the PktToPktProfile component or the TdmNetworkProfile
component is applied.
The egress direction refers to the direction in which packets depart from the
packet core network towards the mobile or the Public Switched Telephone
Network (PSTN).
This attribute has no effect if the value of the agcDirection attribute is set to
ingress.
Mib MediaGateway
Units dBm0
Default -19
Description This attribute specifies the minimum gain that can be applied to any frame by the
Automatic Gain Control (AGC) functionality in the egress direction.
The value of this attribute affects how slowly variations in call volume can be
adjusted towards the value of the egressAgcTargetLevel attribute when a signal
power gain is required for the adjustment.
The egress direction refers to the direction in which packets depart from the
packet core network towards the mobile or the Public Switched Telephone
Network (PSTN).
This attribute has no effect if the value of the agcDirection attribute is set to
ingress.
Mib MediaGateway
Units dB
Default -10
Description This attribute specifies the maximum gain that can be applied to a frame by the
Automatic Gain Control (AGC) functionality in the egress direction.
The value of this attribute affects how quickly variations in call volume can be
adjusted towards the value of the egressAgcTargetLevel attribute when a signal
power gain is required for the adjustment.
The egress direction refers to the direction in which packets depart from the
packet core network towards the mobile or the Public Switched Telephone
Network (PSTN).
This attribute has no effect if the value of the agcDirection attribute is set to
ingress.
Mib MediaGateway
Units dB
Default 10
Scope Device
Mib MediaGateway
Description This group contains the provisioning data for the PktToPktProfile component.
Mib MediaGateway
Description This attribute specifies the companding law to be used on the internal side of the
packet network at a packet-to-packet Media Gateway.
Mib MediaGateway
Values muLawAbi
aLawEbi
Default muLawAbi
Description This attribute specifies the companding law to be used on the external side of the
packet network at a packet-to-packet Media Gateway.
Mib MediaGateway
Values muLawAbi
aLawEbi
Default muLawAbi
Description This attribute specifies the interval of time for which a loss of packet condition
must persist before the corresponding call is dropped in either egress or ingress
direction.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
The egress direction refers to the other direction.
A value of disabled specifies that packet loss integration is disabled and therefore
call connections will not be dropped due to packet loss.
Mib MediaGateway
Units seconds
Default 5
Description The attribute is used by the Transcoding Rate Adaptation Unit (TRAU) to set the
dejitter buffer size and the reserve level based on the expected jitter level on the
internal packet network.
It should be noted that this parameter is not applicable when the TRAU is in
Frame Protocol Interworking Function (FPIF) mode where no transcoding is
performed.
Mib MediaGateway
Units msec
Default 3
Description The attribute is used by the Trancoding Rate Adaptation Unit (TRAU) to set the
dejitter buffer size and the reserve level based on the expected jitter level on the
external packet network.
It should be noted that this parameter is not applicable when the TRAU is in
Frame Protocol Interworking Function (FPIF) mode where no transcoding is
performed.
Mib MediaGateway
Units msec
Default 3
Scope Device
This component represents the profile of the Time Division Multiplexing (TDM)
to Asynchronous Transfer Mode Adaptation Layer 2 (AAL2) call characteristics
handled by this Media Gateway.
Mib MediaGateway
Description This group contains the provisioning data for the TdmToPktProfile component.
Mib MediaGateway
Description The attribute is used by the Transcoding Rate Adaptation Unit (TRAU) to set the
dejitterBuffer size and the reserve level based on the expected jitter level on the
packet network.
Mib MediaGateway
Units msec
Default 3
Description This attribute specifies the interval of time for which a Loss Of Packet (LOP)
condition must persist before the corresponding call is dropped.
A value of disabled specifies that packet loss integration is disabled and therefore
call connections will not be dropped due to packet loss.
Mib MediaGateway
Units seconds
Default 5
Description This attribute specifies the G.711 companding law to be used on the
Asynchronous Transfer Mode (ATM) side of a Narrowband Services Trunk over
ATM.
Mib MediaGateway
Values muLawAbi
aLawEbi
Default muLawAbi
Description This attribute specifies the gain applied on the Time Division Multiplexing ingress
side to balance the network loss plan.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
Mib MediaGateway
Units dB
Default 0
Description This attribute specifies the gain applied on the Time Division Multiplexing egress
side to balance the network loss plan.
The egress direction refers to the direction in which packets depart from the
packet core network towards the mobile or the Public Switched Telephone
Network (PSTN).
Mib MediaGateway
Units dB
Default 0
Scope Device
This component represents the enabling of the Mobile Echo Control (MEC) voice
quality feature for the profile associated with this VoiceProfile component, and
the configuration parameters needed by this feature.
Acoustic echo is caused by the acoustic coupling between the speaker and the
microphone of the mobile unit, mostly in handsfree units and smaller mobile
handsets.
This feature uses an adaptive comfort noise generator that learns the
characteristics of the environment noise and produces a replica when it is
necessary to mask the echo. MEC operates in the ingress direction.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
The operator may desire not to provision this component if an external third-party
voice quality equipment that performs a similar function is used in the network.
Performing mobile echo control more than once may degrade voice quality.
Mib MediaGateway
Description This group contains the provisioning data for the MobileEchoControl (Mec)
component.
Mib MediaGateway
Description This attribute specifies the fixed delay offset for the mobile echo control tail
length applied to all timeslots.
If the value of the codec attribute (defined in the VoiceProfile component) is set to
amr, then the default for this attribute is automatically set to 220. If the value of
the codec attribute is instead set to g711, then the default for this attribute is
automatically set to 200.
If the feature list is set to mgw, the value of this attribute must be a multiple of 5;
otherwise, the value should be a multiple of 10.
Mib MediaGateway
Units msec
Default No default
Scope Device
This component represents the voice quality features available to the profile
associated with this VoiceProfile component while operating in Tandem Free
Operation (TFO) mode, and the configuration parameters for the features.
Mib MediaGateway
Description This group contains the provisioning data for the TandemFreeOperation (Tfo)
component.
Mib MediaGateway
Description This attribute specifies the enabling or disabling of Automatic Gain Control
(AGC) in the ingress direction for Tandem Free Operation (TFO) mode. AGC in
the ingress direction may be turned off for TFO mode, and it may still be on for
the normal operations.
The ingress direction refers to the direction in which packets arrive into the packet
core network from the mobile or the Public Switched Telephone Network (PSTN).
Mib MediaGateway
Values disabled
enabled
sameAsNormal
Default sameAsNormal
Description This attribute specifies the enabling or disabling of Automatic Gain Control
(AGC) in the egress direction for Tandem Free Operation (TFO) mode. AGC in
the egress direction may be turned off for TFO mode, and it may still be on for the
normal operations.
The egress direction refers to the direction in which packets depart from the
packet core network towards the mobile or the Public Switched Telephone
Network (PSTN).
Mib MediaGateway
Values disabled
enabled
sameAsNormal
Default sameAsNormal
Mib MediaGateway
Values disabled
enabled
enabledLowPass
sameAsNormal
Default sameAsNormal
Description This attribute specifies the enabling or disabling of Mobile Echo Control (MEC)
in Tandem Free Operation (TFO) mode. MEC in the egress direction may be
turned off for TFO mode and it may still be on for the normal operations.
The operator may desire to enable this functionality to detect and suppress
acoustic echoes originating from the mobile user equipment.
The operator may desire to disable this functionality if external third-party voice
quality equipment that performs a similar function is used in the network.
Performing mobile echo control more than once may degrade voice quality.
Mib MediaGateway
Values disabled
enabled
sameAsNormal
Default sameAsNormal
Scope Device
This component represents enabling of the Global Text Telephony (GTT) voice
quality feature for the profile associated with this VoiceProfile component, and
the configuration parameters needed by this feature.
Global text telephony offers individuals the ability to communicate with one
another with written text in real time by relaying these messages over voice
channels. The user can switch between text and voice as desired.
Mib MediaGateway
Description This group contains the provisioning data for the GlobalTextTelephony (Gtt)
component.
Mib MediaGateway
Description This attribute specifies the baud rate of the Baudot codec used in the Public
Switched Telephone Network (PSTN), with which the Voice Services Processor
(VSP) Global Text Telephony (GTT) codec must interwork with.
GTT text messages are encoded for transmission over the circuit switched voice
channels. The VSP encodes the text telephony messages from text to voice or
voice to text, depending on the direction of the message flow.
The default value for this attribute is automatically set to autoConfigured for the
cdmaCodec feature, and 45.45 for all others. Only the cdmaCodec feature will
have the ability to detect the incoming data rate and adjust to it accordingly.
Mib MediaGateway
Default No default
The operator may choose not to provision this component if there is another
device in the network that performs a similar function. Performing background
noise reduction more than once might degrade voice quality.
Mib MediaGateway
Scope Device
Vocoders can cause artifacts and distortions known as the waterfall effect when
operating on background noise signals. BNC is a signal processing technique that
operates on the reproduced noise signal to remove the artefacts and restore the
natural quality of the audio signal.
Mib MediaGateway
Description This group contains the provisioning data for the BackgroundNoiseConditioning
(Bnc) component.
Mib MediaGateway
Description This attribute specifies the enabling or disabling of the low-pass filter post-
processing of the background noise conditioned signal.
Mib MediaGateway
Values disabled
enabled
Default disabled
Scope Device
Mib MediaGateway
Description This group contains the provisioning data for the MultiParty component.
Mib MediaGateway
Description This attribute specifies the maximum number of simultaneous speakers that may
be heard by any other party on the conference bridge.
Mib MediaGateway
Default 2
Description This group contains the operational data for the MultiParty component.
Mib MediaGateway
Description This attribute indicates the maximum number of Conference Bridges or Lawful
Intercept Replicators supported on this Media Gateway.
Mib MediaGateway
Default No default
Description This group contains the operational data for the MultiParty component specific to
conferencing.
Mib MediaGateway
Description This attribute indicates the number of conference bridges currently in use.
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This group contains the operational data for the MultiParty component specific to
the lawful intercept distribution function.
Mib MediaGateway
Description This attribute indicates the number of lawful intercept replicators currently in use.
Mib MediaGateway
Default No default
Description This attribute counts failed lawful intercept replicator setup requests.
Mib MediaGateway
Default No default
Description This attribute counts successful lawful intercept replicator setup requests.
Mib MediaGateway
Default No default
Description This attribute counts all lawful intercept replicator setup requests.
Mib MediaGateway
Default No default
The value of this attribute is set at the end of the collection interval.
The value of this attribute is reset to the current number of bridges in use at the
beginning of each collection interval.
The value of this attribute is reset to the current number of lawful intercept
replicators in use at the beginning of each collection interval.
Scope Device
This component represents enabling of the Echo Cancellation functionality for all
calls on the Media Gateway.
Mib MediaGateway
Description This group contains the provisioning data for the EchoCancellation (Ecan)
component.
Mib MediaGateway
Description This attribute specifies whether comfort noise generation for the echo cancellation
feature is enabled or disabled.
Mib MediaGateway
Values disabled
enabled
Default enabled
Description This attribute specifies the maximum tail path delay that will be allowed by the
echo canceller.
Mib MediaGateway
Units msec
Default 64
Description This attribute specifies the fixed delay offset for the echo cancellation tail length.
The value of this attribute is ignored when the tailCoverage attribute is set to a
value of 128.
Mib MediaGateway
Units msec
Default 0
Description This attribute specifies the minimum echo return loss that can be expected on the
line.
Mib MediaGateway
Units dB
Default 3
Scope Device
This component represents the voice quality features available to calls associated
with the parent VoiceProfile component while operating in Transcoder Free
Operation (TrFO) mode.
The voice quality settings specified in this component are only applied to calls
that are operating in TrFO mode.
Mib MediaGateway
Description This group contains the provisioning data for the TranscoderFreeOperation (Trfo)
component.
Mib MediaGateway
Description This attribute specifies the enabling or disabling of Automatic Gain Control
(AGC) in the egress direction for calls operating in Transcoder Free Operation
(TrFO) mode. The egress direction refers to the direction in which packets depart
from the packet core network.
This voice quality feature should be enabled if the operator desires to control
variations in call volume in the egress direction for calls operating in TrFO mode.
Mib MediaGateway
Values disabled
enabled
sameAsNormal
Default sameAsNormal
Mib MediaGateway
Values disabled
enabled
enabledLowPass
sameAsNormal
Default sameAsNormal
Description This attribute specifies the enabling or disabling of Mobile Echo Control (MEC)
for calls operating in Transcoder Free Operation (TrFO) mode.
This voice quality feature should be enabled if the operator desires to detect and
suppress acoustic echoes originating from the mobile user equipment.
The operator may desire to disable this functionality if external third-party voice
quality equipment that performs a similar function is used in the network, as
performing mobile echo control more than once in the network may degrade voice
quality.
Mib MediaGateway
Values disabled
enabled
sameAsNormal
Default sameAsNormal
Scope Device
Mib Vgs
Description This group contains operational context attributes for the CallStatistics
component.
Mib Vgs
Description This attribute indicates the average context duration since the last card reset. The
context duration is the time measured between context creation and context
deletion.
Mib Vgs
Units msec
Default No default
Description This attribute indicates the maximum context duration since the last card reset.
The context duration is the time measured between context creation and context
deletion.
Mib Vgs
Units msec
Default No default
Description This attribute indicates the minimum context duration since the last card reset.
The context duration is the time measured between context creation and context
deletion.
Mib Vgs
Units msec
Default No default
Description This group contains the operational DS0 Utilization Statistics attributes for the
CallStatistics component.
Mib Vgs
Description This attribute indicates the average DS0 channel utilization on this card since the
last card reset.
A busy channel is one that is neither idle nor blocked. The number of busy
channels are divided by the configured channel capacity to arrive at the DS0
utilization. Channels are configured in the Nsta/n Vgs Tag component.
Mib Vgs
Units %
Default No default
Description This attribute indicates the maximum DS0 channel utilization on this card since
the last card reset.
A busy channel is one that is neither idle nor blocked. The number of busy
channels are divided by the configured channel capacity to arrive at the utilization.
Mib Vgs
Units %
Default No default
Description This attribute counts the number of DS0 channels that have been activated. This
parameter is used to derive the Erlangs.
Mib Vgs
Default No default
Description This group contains the operational GlobalTextTelephony (Gtt) attributes for the
CallStatistics component.
Mib Vgs
Description This attribute counts the Global Text Telephony (GTT) calls set up on this Nsta/n
Vgs component. This attribute is incremented when the call is set up.
Mib Vgs
Default No default
Description This attribute indicates the current number of Global Text Telephony (GTT) calls
present on this Nsta/n Vgs component.
Mib Vgs
Default No default
Description This attribute counts the number of Global Text Telephony (GTT) calls that have
failed Cellular Text telephone Modem (CTM) negotiation on this Nsta/n Vgs
component. This attribute is incremented when the call terminate.
Mib Vgs
Default No default
Description This group contains the operational attributes for the CallStatistics component
pertaining to resource utilization.
Mib Vgs
Mib Vgs
Default No default
Description This attribute indicates the number of Nb interface connections that are currently
supporting active calls.
Mib Vgs
Default No default
Description This attribute indicates the number of Public Switched Telephone Network
(PSTN) interface connections that are currently supporting active calls.
Mib Vgs
Default No default
Description This attribute indicates the number of Global System for Mobile communications
(GSM) Access interface connections that are currently supporting active calls.
Mib Vgs
Default No default
Description This attribute counts the connection failures that are due to insufficient packetized
data path throughput when throughputLoadPercent is at or exceeds 100%.The
counter wraps to zero when it exceeds its maximum value.
Mib Vgs
Default No default
Mib Vgs
Default No default
Description This attribute indicates the percentage of Digital Signalling Processors (DSPs)
whose resources are exhausted in support of active calls.
Mib Vgs
Units %
Default No default
Description This attribute indicates the percentage of Digital Signalling Processor (DSP) cores
whose resources are exhausted in support of active calls.
100% indicates that no new calls can be supported by the DSP cores.
Mib Vgs
Units %
Default No default
Description This attribute indicates the percentage of Digital Signalling Processor (DSP)
contexts that are currently supporting active calls.
100% indicates that no new calls can be supported by the DSP contexts.
Mib Vgs
Units %
Default No default
Description This attribute indicates the percentage of Digital Signalling Processor (DSP)
terminations that are currently supporting active calls.
100% indicates that all DSP terminations are supporting active calls and no new
calls can be supported.
Mib Vgs
Units %
Default No default
Description This attribute indicates the percentage of packetized data path throughput
currently in use.
An attribute value of 100% indicates that all packet throughput is completely used
by active calls.
An attribute value that is greater than 100% indicates that the packet throughput is
is over-subscribed and that active calls may suffer packet loss.
Mib Vgs
Units %
Default No default
Description This attribute indicates the percentage of Iu and Nb interface connection resources
currently in use.An attribute value of 100% indicates that all Iu and Nb interface
connection resources are completely used by active calls.
Mib Vgs
Units %
Default No default
Description This attribute indicates the percentage of the overall congestion level of the Media
Gateway resources. This attribute indicates the highest value, upper-limited to
100%, of the following operational attributes:
- contextLoadPercent
- throughputLoadPercent
- the highest value of currentPercentBandwidthUtil for all of the AtmCac
AtmSubnet or IpCac IpSubnet components.
Mib Vgs
Units %
Default No default
(peakDspLoadPct)
Access Read: All
Write: Illegal
Description This attribute indicates the maximum value of dspLoadPercent attribute recorded
since the Media Gateway came into service.
Mib Vgs
Units %
Default No default
Description This attribute indicates the maximum value of coreLoadPercent attribute recorded
since the Media Gateway came into service.
Mib Vgs
Units %
Default No default
Mib Vgs
Units %
Default No default
Mib Vgs
Units %
Default No default
Mib Vgs
Units %
Default No default
Mib Vgs
Units %
Default No default
Mib Vgs
Units %
Default No default
Description This group contains the operational attributes for the CallStatistics component
pertaining to compression.
Mib Vgs
Description This attribute counts codec upspeeds performed by the Transcoding Rate
Adaptation Unit (TRAU).
Mib Vgs
Default No default
Description This attribute indicates the average percentage of time that calls are carrying
Adaptive Multi-Rate (AMR) voice activity on this Media Gateway since restart.
Mib Vgs
Units %
Default No default
Description This attribute indicates the average bandwidth used by calls established on this
Media Gateway since restart.
Mib Vgs
Units bit/s
Default No default
Description This attribute indicates the maximum bandwidth used by calls established on this
Media Gateway since restart.
Mib Vgs
Units bit/s
Default No default
Description This group contains the operational attributes for the CallStatistics component
pertaining to Nb User Plane (Nb UP) Initialization Failures.
Mib Vgs
Description This attribute counts Nb User Plane (Nb UP) initialization failures due to
initialization message reply timeouts.
Mib Vgs
Default No default
Description This attribute counts Nb User Plane (Nb UP) initialization failures due to negative
Nb UP initialization acknowledgements received from the peer Media Gateway.
Mib Vgs
Default No default
Description This attribute counts Nb User Plane (Nb UP) initialization failures due to an Nb
UP mode version mismatch with the peer Media Gateway.
Mib Vgs
Default No default
Description This attribute counts Nb User Plane (Nb UP) initialization failures due to a Radio
Access Bearer (RAB) subflow mismatch with the peer Media Gateway.
Mib Vgs
Default No default
Description This attribute counts Nb User Plane (Nb UP) initialization failures due to a
message format error received from the peer Media Gateway.
Mib Vgs
Default No default
Description This attribute counts upspeed failures due to negotiation message reply timeouts.
Mib Vgs
Default No default
Description This attribute counts upspeed failures due to multiple negative acknowledgements
received from the peer Media Gateway.
Mib Vgs
Default No default
Description This attribute counts upspeed failures for the Global Text Telephony (GTT)
service that requires G.711 for reliable transport.
Mib Vgs
Default No default
Description This attribute counts upspeed failures for the Integrated Digital Enhanced
Network (iDEN) service that requires G.711 for reliable transport.
Mib Vgs
Default No default
Description This attribute counts upspeed failures for the Circuit Switched Data (CSD) service
that requires G.711 for reliable transport.
Mib Vgs
Default No default
Description This group contains the operational attributes for the CallStatistics component
pertaining to Iu User Plane (Iu UP) Initialization statistics.
Mib Vgs
Description This attribute counts total Iu User Plane (Iu UP) passive initializations.
This attribute is incremented when the User Plane initialization is attempted over
the Iu interface of Media Gateway, i.e, when a UP-INITIALIZATION message
is received on the Media Gateway. This includes both successful and failed
initialization attempts.
Mib Vgs
Default No default
Description This attribute counts successful Iu User Plane (Iu UP) passive initializations.
Mib Vgs
Default No default
This attribute indicates the numbers of events during the collection interval.
This attribute indicates the peak value during the collection interval.
This attribute indicates the numbers of events during the collection interval.
Units %
Units bit/s
Units bit/s
Description This attribute counts upspeed failures for the Circuit Switched Data (CSD) service
that requires G.711 for reliable transport.
The value indicates the percentage of Digital Signalling Processors (DSPs) whose
resources are exhausted in support of active calls.
This attribute resets to the current value at the beginning of the collection interval.
Units %
The value indicates the percentage of Digital Signalling Processor (DSP) cores
whose resources are exhausted in support of active calls.
100% indicates that no new calls can be supported by the DSP cores.
This attribute resets to the current value at the beginning of the collection interval.
Units %
The value indicates the percentage of Digital Signalling Processor (DSP) contexts
that support active calls.
100% indicates that no new calls can be supported by the DSP contexts.
This attribute resets to the current value at the beginning of the collection interval.
Units %
100% indicates that all DSP terminations are supporting active calls and that no
new calls can be supported
This attribute resets to the current value at the beginning of the collection interval.
Units %
The value indicates the percentage of packetized data path throughput utilized to
support active calls.
An attribute value of 100% indicates that all packet throughput is completely used
by active calls.
An attribute value that is greater than 100% indicates that the packet throughput is
over-subscribed and that active calls may suffer packet loss.
This attribute resets to the current value at the beginning of the collection interval.
Units %
An attribute value of 100% indicates that all Iu and Nb connection resources are
completely used by active calls.
This attribute resets to the current value at the beginning of the collection interval.
Units %
The value indicates the percentage of the overall congestion level of the Media
Gateway resources.
This attribute indicates the highest value, upper-limited to 100%, of the following
operational attributes:
contextLoadPercent,
throughputLoadPercent,
the highest value of currentPercentBandwidthUtil for all of the AtmCac
AtmSubnet or IpCac IpSubnet components.
This attribute resets to the current value at the beginning of the collection interval.
Units %
Units msec
Units msec
Units msec
Units %
Units %
This attribute counts the numbers of events during the collection interval.
This attribute is incremented when the User Plane initialization is attempted over
the Iu interface of Media Gateway, i.e, when a UP-INITIALIZATION message
is received on the Media Gateway. This includes both successful and failed
initialization attempts.
Scope Device
This component represents the configurable parameters for the Message Transfer
Part Layer 2 (MTP2) transport.
Mib MediaGateway
Description This group contains the provisionable attributes for the Mtp2Profile component.
Mib MediaGateway
Description This attribute specifies the variant of the Message Transfer Part Layer 2 (MTP2)
protocol that applies to the component.
The values of the protocol timer attributes must be provisioned within the range
applicable to the protocol variant specified by this attribute.
Mib MediaGateway
Values itu
ansi
Default itu
Description This attribute specifies the value of the Alignment Ready timer defined in ITU-
T recommendation Q.703.
This timer is started when the link reaches the Alignment Ready state.
This timer stops upon entering the In Service state. Reception of a Fill-In Signal
Unit (FISU) or a Message Signal Unit (MISU) while in the Alignment Ready
state causes the state transition to the In Service state.
The value of this timer must be between 40 and 50 seconds for the ITU variant of
the protocol and between 12 and 16 seconds for the ANSI variant.
Mib MediaGateway
Units seconds
Default 45
Description This attribute specifies the value of the Not Aligned timer defined in ITU-T
recommendation Q.703. It is used during initial alignment.
This timer is started when the link enters the Not Aligned state which begins
sending status indication O.
The value of this timer must be between 5 and 150 seconds for the ITU variant of
the protocol and between 5 and 30 seconds for the ANSI variant.
Mib MediaGateway
Units seconds
Default 60
Description This attribute specifies the value of the Aligned timer defined in ITU-T
recommendation Q.703. It is used during initial alignment.
This timer is started when the link enters the Aligned state which begins
sending status indication N or E, depending on whether the link is in normal
or emergency alignment mode respectively.
The value of this timer must be between 1000 and 2000 milliseconds for the ITU
variant of the protocol and between 5000 and 14000 milliseconds for the ANSI
variant.
Mib MediaGateway
Units msec
Default 1500
Description This attribute specifies the value of the Proving Period timer for normal
alignment as defined in ITU-T recommendation Q.703. It is used during initial
alignment.
It is started when the link enters the Proving state. In normal alignment mode,
proving must last for a period specified by this timer before the link can enter the
Aligned Ready state.
Expiry of this timer indicates a successful proving period unless the proving
period has been previously aborted up to four times.
A higher value for this timer ensures a more stable link, but increases the time
taken to bring the link in service.
The value of this timer must be between 7500 and 9500 milliseconds for the ITU
variant of the protocol and between 2000 and 2550 milliseconds for the ANSI
variant.
Mib MediaGateway
Units msec
Default 8500
Description This attribute specifies the value of the Proving Period timer for emergency
alignment as defined in ITU-T recommendation Q.703. It is used during initial
alignment.
It is started when the link enters the Proving state. In emergency alignment
mode, proving must last for a period specified by this timer before the link can
enter the Aligned Ready state.
Expiry of this timer indicates a successful proving period unless the proving
period has been previously aborted up to four times.
A higher value for this timer ensures a more stable link, but increases the time
taken to bring the link in service.
The value of this timer must be between 400 and 600 milliseconds for the ITU
variant of the protocol and between 500 and 700 milliseconds for the ANSI
variant.
Mib MediaGateway
Units msec
Default 500
Description This attribute specifies the value of the Sending SIB timer defined in ITU-T
recommendation Q.703. It is used for congestion control.
The value of this timer determines the interval at which the receiving end of a
signalling link, which detects a congestion situation returns a status indication B
to the remote transmitting end of the link. This causes the remote end of the link
This attribute has the same value ranges for both ANSI and ITU variants of the
protocol.
Mib MediaGateway
Units msec
Default 100
Description This attribute specifies the value of the Remote Congestion timer defined in
ITU-T recommendation Q.703.
This timer is stopped when the congestion abates at the signalling point, as
indicated by a message in the retransmit buffer being acknowledged.
The value of this timer must be between 3000 and 6000 milliseconds for the ITU
variant of the protocol and between 1000 and 6000 milliseconds for the ANSI
variant.
Mib MediaGateway
Units msec
Default 4500
Description This attribute specifies the value of the Excessive delay of acknowledgment
timer defined in ITU-T recommendation Q.703. It is used during normal sending
and receiving of Message Signal Units (MSU).
This timer starts when the first MSU is placed in the retransmit buffer and is
pending acknowledgment.
This timer is stopped after the last MSU in the retransmit buffer is acknowledged.
This timer is restarted after each acknowledgment when the retransmit buffer is
non-empty. It is also restarted each time a link status indication unit B is
received.
This attribute has the same value ranges for both ANSI and ITU variants of the
protocol.
Mib MediaGateway
Units msec
Default 1250
Description This attribute specifies a list of Nsta/n Vgs Mtp2/n components linked to this
profile.
Mib MediaGateway
Default No default
Scope Device
This component represents the Message Transfer Part Layer 2 (MTP2) transport
layer between the Media Gateway and either the Public Switched Telephone
Network (PSTN) or the 2G Radio Access Network (RAN).
Mib MediaGateway
Description This group contains the provisionable attributes for the Mtp2 component.
Mib MediaGateway
Criticality Process
Description This attribute specifies the link to the DS1Chan or E1Chan component that in turn
specifies the timeslot for the Message Transfer Part Layer 2 (MTP2) transport.
The DS1Chan or E1Chan component must reside on the same card as this
component.
The DS1Chan or E1Chan component used by the Mtp2 must contain only one
timeslot in their timeslots attribute.
Mib MediaGateway
Default No default
Criticality Process
Description This attribute specifies a link to the Message Transfer Part Layer 2 (MTP2) user.
It must specify an Nsta/n Vgs M2ua As/n Iid/n component.
The Iid/n component must reside on the same card as this component.
Mib MediaGateway
Default No default
Description This attribute specifies a link to the Nsta/n Vgs Mtp2Profile/n component, which
in turn specifies the configurable parameters for this Message Transfer Part Layer
2 (MTP2) transport.
Mib MediaGateway
Default No default
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib MediaGateway
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
provide services for its users. To enter this state, issue an Unlock command to this
component.
Mib MediaGateway
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib MediaGateway
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib MediaGateway
Values idle
active (activ)
busy
Default idle
Description This group contains the operational attributes for the Mtp2 component.
Mib MediaGateway
Description This attribute counts timeouts of the Alignment Ready timer (T1) represented
by the attribute alignmentReadyTimer (defined in the Nsta/n Vgs Mtp2Profile/n
component).
Mib MediaGateway
Default No default
Description This attribute counts timeouts of the Not Aligned timer (T2) represented by the
attribute notAlignedTimer (defined in the Nsta/n Vgs Mtp2Profile/n component).
Mib MediaGateway
Default No default
Description This attribute counts timeouts of the Aligned timer (T3) represented by the
attribute alignedTimer (defined in the Nsta/n Vgs Mtp2Profile/n component).
Mib MediaGateway
Default No default
Description This attribute counts the number of times congestion was detected by the
MonitoredCommunicationsProtocol dynamic subcomponent at the local end of
the signalling link.
Mib MediaGateway
Default No default
Description This attribute counts the number of congestion indications transmitted to the
remote end of the signalling link. The congestion is detected locally by the
MonitoredCommunicationsProtocol dynamic subcomponent and is transmitted to
the remote end if it does not abate within the time interval specified by the
sendingSibTimer (T5) attribute of the linked Nsta/n Vgs Mtp2Profile/n
component.
Mib MediaGateway
Default No default
Description This attribute counts congestion indications received from the remote end of the
signalling link.
Mib MediaGateway
Default No default
Description This attribute counts timeouts of the T7 Timer represented by the attribute
ackTimer (defined in the Nsta/n Vgs Mtp2Profile/n component).
Mib MediaGateway
Default No default
It does not include failures which occur during the alignment process.
Mib MediaGateway
Default No default
Description This attribute counts Message Signal Units (MSU) transmitted. This includes the
number of MSUs retransmitted, indicated by the attribute msuRetransmits.
Mib MediaGateway
Default No default
Description This attribute counts Message Signal Units (MSU) retransmitted because of
negative acknowledgments.
Mib MediaGateway
Default No default
Description This attribute counts the number of Message Signal Units (MSU) received. This
includes the MSUs with errors, indicated by the attribute msuErrors.
Mib MediaGateway
Default No default
Description This attribute counts ingress signal units discarded because of sequence number,
length or Cyclic Redundancy Check (CRC) errors.
Mib MediaGateway
Default No default
Description This attribute counts layer 3 payload octets transmitted within the Message Signal
Units (MSU).
Mib MediaGateway
Default No default
Description This attribute counts layer 3 payload octets received within the Message Signal
Units (MSU).
Mib MediaGateway
Default No default
It does not include failures which occur during the alignment process.
Scope Application
Mib MediaGateway
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib MediaGateway
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib MediaGateway
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib MediaGateway
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib MediaGateway
Values idle
active (activ)
busy
Default idle
Mib MediaGateway
Description This attribute counts the communication failures between the neighbors being
monitored.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages sent to the neighbor but were not
received by the neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages that were sent by the neighbor but
were not received by this component. This is detected by a gap in the Message
Numbers received in payload messages from the neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Request messages sent by this
component to the neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Request messages received by this
component.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Response messages sent by this
component.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Response messages received by this
component in response to the Monitor Enable Request message.
Mib MediaGateway
Default No default
Description This attribute counts the Heartbeat messages sent by this component to the
neighbor.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
Mib MediaGateway
Default No default
Description This attribute counts the Heartbeat messages received by this component.
The value of this attribute is incremented when the Heartbeat message is received.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages sent by this component to the
neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages received by this component.
Mib MediaGateway
Default No default
Description This attribute counts the Sequencing Gap messages sent by this component.
Mib MediaGateway
Default No default
(seqGapsRx)
Access Read: All
Write: Illegal
Description This attribute counts the Sequencing Gap messages received by this component.
Mib MediaGateway
Default No default
Description This attribute counts the messages received by this component that are not
recognized by the MonitoredCommunicationProtocol (MCP).
Mib MediaGateway
Default No default
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Mib MediaGateway
Default No default
The value of the Heartbeat timer is negotiated between the monitored parent
components.
Mib MediaGateway
Units msec
Default No default
Description This attribute indicates the number of time-outs of the Heartbeat timer allowed
before marking the communication with the neighbor as down.
The value of the Heartbeat retries is negotiated between the monitored parent
components.
Mib MediaGateway
Default No default
negotiated between the monitored parent components. The value of the Heartbeat
timer and retries can be determined from the operational attributes heartbeatTimer
and heartbeatRetries respectively.
- if communication monitoring is not established between the two neighbors.
Monitor Enable Request messages are sent to the neighbor when the Heartbeat
timer expires and if the Monitor Enable Response message is not received prior to
the predetermined number of Heartbeat timer expiries, then it is assumed that
monitoring communication could not be established and the value of this attribute
is incremented.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
The value of this attribute is incremented when the Heartbeat message is received.
(msgsDiscarded)
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Scope Device
This component represents the Message Transfer Part Layer 2 User Adaptation
(M2UA) layer.
Mib MediaGateway
Description This group contains the provisioning data for the M2ua component.
Mib MediaGateway
Criticality Process
Description This attribute specifies a link to the local Stream Control Transmission Protocol
(SCTP) port used by the Message Transfer Part Layer 2 User Adaptation (M2UA)
application.
Changing the value of this link will cause this process to restart.
Mib MediaGateway
Default No default
Description This attribute specifies the frequency for sending Message Transfer Part Layer 2
User Adaptation (M2UA) heartbeat messages to peer nodes.
The heartbeat timer T(beat) has two purposes. It is used to determine how often to
send out heartbeat messages. It is also used to determine how long to wait for
heartbeat acknowledgement (2 *T(beat)) before considering the peer to be
unavailable.
Mib MediaGateway
Units seconds
Default 30
Description This group contains the three OSI State attributes and the six OSI Status
attributes. The descriptions generically indicate what each attribute implies about
the component. Note that not all the values and state combinations described here
are supported by every component which reuses this group. For component-
specific information and the valid state combinations, refer to the appropriate
NTP.
Mib MediaGateway
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib MediaGateway
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib MediaGateway
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
The OSI Status attributes, if supported by the component, may provide more
details, qualifying the state of the component.
Mib MediaGateway
Values idle
active (activ)
busy
Default idle
Description If supported by the component, this attribute indicates the OSI Availability status
of the component. Note that, even though it is defined as a multi-valued set, at
most one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value inTest indicates that the resource is undergoing a test procedure. If
adminState is locked or shuttingDown, the normal users are precluded from using
the resource and controlStatus is reservedForTest. Tests that do not exclude
additional users can be present in any operational or administrative state but the
reservedForTest condition should not be present.
The value failed indicates that the component has an internal fault that prevents it
from operating. The operationalState is disabled.
The value dependency indicates that the component cannot operate because some
other resource on which it depends is unavailable. The operationalState is
disabled.
The value powerOff indicates the resource requires power to be applied and it is
not powered on. The operationalState is disabled.
The value offLine indicates the resource requires a routine operation (either
manual, automatic, or both) to be performed to place it on-line and make it
available for use. The operationalState is disabled.
The value degraded indicates the service provided by the component is degraded
in some way, such as in speed or operating capacity. Usually, the resource remains
available for service. The operationalState is almost always enabled. There is one
exception where an operationalState of disabled is used in conjunction with
degraded for a component which represents a rolled up view of a set of other
components.
The value notInstalled indicates the resource is not present. The operationalState
is disabled.
Mib MediaGateway
Set of inTest
failed
dependency (depend)
powerOff (pwrOff)
offLine
offDuty
degraded (degrad)
notInstalled (notIn)
logFull
migrating
Default No default
Description If supported by the component, this attribute indicates the OSI Procedural status
of the component. Note that, even though it is defined as a multi-valued set, at
most one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value initializing indicates that initialization has been initiated but is not yet
complete. The operationalState may be enabled or disabled.
The value reporting indicates the resource has completed some processing
operation and is notifying the results. The operationalState is enabled.
Mib MediaGateway
Default No default
Description If supported by the component, this attribute indicates the OSI Control status of
the component. Note that, even though it is defined as a multi-valued set, at most
one value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value subjectToTest indicates the resource is available but tests may be
conducted simultaneously at unpredictable times, which may cause it to exhibit
unusual characteristics.
The value suspended indicates that the service has been administratively
suspended.
Mib MediaGateway
Default No default
Description If supported by the component, this attribute indicates the OSI Alarm status of the
component. Note that, even though it is defined as a multi-valued set, at most one
value is shown to the user.
When no values are in the set, this indicates that either the attribute is not
supported or that none of the status conditions described below is present.
The value underRepair indicates the component is currently being repaired. The
operationalState is enabled or disabled.
The value critical indicates one or more critical alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
The value major indicates one or more major alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
The value minor indicates one or more minor alarms are outstanding against the
component. Other, less severe, alarms may also be outstanding. The
operationalState is enabled or disabled.
Mib MediaGateway
Default No default
Description If supported by the component, this attribute indicates the OSI Standby status of
the component.
The value notSet indicates that either the attribute is not supported or that none of
the status conditions described below is present. Note that this is a non-standard
value, used because the original specification indicated this attribute was set-
valued and thus, did not provide a value to indicate that none of the other three are
applicable.
The value hotStandby indicates that the resource is not providing service but will
be immediately able to take over the role of the resource to be backed up, without
initialization activity, and containing the same information as the resource to be
backed up.
The value coldStandby indicates the resource is a backup for another resource but
will not be immediately able to take over the role of the backed up resource and
will require some initialization activity.
Mib MediaGateway
Default notSet
Description This attribute indicates the OSI Unknown status of the component.
The value false indicates that all of the other OSI State and Status attribute values
can be considered accurate.
The value true indicates that the actual state of the component is not known for
sure.
Mib MediaGateway
Values false
true
Default false
Description This group contains the operational data for the M2ua component.
Mib MediaGateway
Description This attribute counts connection requests refused by the Message Transfer Part
Layer 2 User Adaptation (M2UA) layer.
The most likely cause for the connection to be refused is that the requestors IP
address or port information is not configured on this Media Gateway.
Mib MediaGateway
Default No default
The most likely cause for the connection to be refused is that the requestors IP
address or port information is not configured on this Media Gateway.
Scope Device
This component represents the peer Application Server (AS) that establishes a
Stream Control Transmission Protocol (SCTP) association with this Message
Transfer Part Layer 2 User Adaptation (M2UA) application.
Mib MediaGateway
Description This group contains the provisionable data for the ApplicationServer component.
Mib MediaGateway
Description This attribute specifies the amount of time to buffer outgoing messages when the
Application Server Process (ASP) becomes inaccessible.
If this timer expires before the ASP returns to service, the messages are dropped
and the Application Server (AS) transitions into the down state.
A value of 0 indicates that buffering should not occur, and the AS should
immediately transition into the down state when the ASP becomes inaccessible.
Note that higher values for this attribute will require more memory to be reserved
for message buffering.
Mib MediaGateway
Units seconds
Default 2
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib MediaGateway
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib MediaGateway
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib MediaGateway
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib MediaGateway
Values idle
active (activ)
busy
Default idle
Properties Operational
Description This group contains the operational data for the ApplicationServer component.
Mib MediaGateway
Description This attribute indicates the peer Application Server (AS) state as determined by
the local Message Transfer Part 2 User Adaptation (M2UA) application.
Mib MediaGateway
Values inactive
active
pending
down
Default No default
Description This attribute indicates the number of Interface Identifiers (IID) currently in an
active state.
This value is initially zero and increases up to a maximum of the number of Iid
components provisioned under this component.
Mib MediaGateway
Default No default
Scope Device
This component represents the Interface Identifier (IID), the identifier of the
physical Layer 2 SS7 link.
The instance value is an integer used as the IID in MTP2 User Adaptation Layer
(M2UA) communication with the Application Server (AS). The instance number
must match the IID provisioned on the AS.
Each IID can support only one SS7 link to a given interface.
Mib MediaGateway
Description This group contains the provisioning data for the InterfaceIdentifier component.
Mib MediaGateway
Criticality Component
Description This attribute specifies a link to the link layer entity that this Message Transfer
Part Layer 2 User Adaptation (M2UA) application is backhauling over IP.
This attribute may specify either an Nsta/n Vgs Mtp2/n component or a SaalNni/n
component.
Changing this attribute will cause this component to be deactivated and restarted.
Mib MediaGateway
Default No default
Description This group contains the operational data for the InterfaceIdentifier component.
Mib MediaGateway
Mib MediaGateway
Values idle
normalProving
emerProving
active
lpo
rpo
congested
error
Default No default
Description This group contains the operational data for the InterfaceIdentifier component
pertaining to Message Transfer Part Layer 2 User Adaptation (MAUP) messages.
Mib MediaGateway
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute counts the number of Data Retrieval Complete Indication messages
sent.
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
COLLECTED STATS
NarrowbandServicesTrunkOverATM VoiceGateway
M2ua ApplicationServer InterfaceIdentifier Default
Description The statistics record generated by the NarrowbandServicesTrunkOverATM
VoiceGateway M2ua ApplicationServer InterfaceIdentifier component.
dataRetrievalConfirmsSent
Description This attribute counts Data Retrieval Confirm messages sent.
Scope Application
Mib MediaGateway
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib MediaGateway
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib MediaGateway
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib MediaGateway
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib MediaGateway
Values idle
active (activ)
busy
Default idle
Mib MediaGateway
Description This attribute counts the communication failures between the neighbors being
monitored.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages sent to the neighbor but were not
received by the neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages that were sent by the neighbor but
were not received by this component. This is detected by a gap in the Message
Numbers received in payload messages from the neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Request messages sent by this
component to the neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Request messages received by this
component.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Response messages sent by this
component.
Mib MediaGateway
Default No default
Description This attribute counts the Monitor Enable Response messages received by this
component in response to the Monitor Enable Request message.
Mib MediaGateway
Default No default
Description This attribute counts the Heartbeat messages sent by this component to the
neighbor.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
Mib MediaGateway
Default No default
Description This attribute counts the Heartbeat messages received by this component.
The value of this attribute is incremented when the Heartbeat message is received.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages sent by this component to the
neighbor.
Mib MediaGateway
Default No default
Description This attribute counts the payload messages received by this component.
Mib MediaGateway
Default No default
Description This attribute counts the Sequencing Gap messages sent by this component.
Mib MediaGateway
Default No default
Description This attribute counts the Sequencing Gap messages received by this component.
Mib MediaGateway
Default No default
Description This attribute counts the messages received by this component that are not
recognized by the MonitoredCommunicationProtocol (MCP).
Mib MediaGateway
Default No default
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Mib MediaGateway
Default No default
The value of the Heartbeat timer is negotiated between the monitored parent
components.
Mib MediaGateway
Units msec
Default No default
Description This attribute indicates the number of time-outs of the Heartbeat timer allowed
before marking the communication with the neighbor as down.
The value of the Heartbeat retries is negotiated between the monitored parent
components.
Mib MediaGateway
Default No default
COLLECTED STATS
NarrowbandServicesTrunkOverATM
VoiceGateway M2ua ApplicationServer
InterfaceIdentifier
MonitoredCommunicationProtocol Default
Description The statistics record generated by the NarrowbandServicesTrunkOverATM
VoiceGateway M2ua ApplicationServer InterfaceIdentifier
MonitoredCommunicationProtocol component.
enableRequestsTx (enableReqsTx)
Description This attribute counts the Monitor Enable Request messages sent by this
component to the neighbor.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
The value of this attribute is incremented when the Heartbeat message is received.
Description This attribute counts the Sequencing Gap messages received by this component.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Scope Device
This component represents the peer Application Server Process (ASP) that
establishes a Stream Control Transmission Protocol (SCTP) association with this
Message Transfer Part Layer 2 User Adaptation (M2UA) application.
Mib MediaGateway
Description This group contains the provisionable data for the ApplicationServerProcess
component.
Mib MediaGateway
Criticality Component
Description This attribute specifies the Internet Protocol (IP) address of the remote
Application Server Process (ASP).
If the value of the localRole attribute is set to client, this is the destination towards
which a Stream Control Transmission Protocol (SCTP) association is established.
If the value of the localRole attribute is server, this is the address from which a
connection is expected.
Mib MediaGateway
Values IP address
Default No default
Criticality Component
Description This attribute specifies the Stream Control Transmission Protocol (SCTP) port of
the remote Application Server Process (ASP).
Mib MediaGateway
Default 2904
Description This attribute specifies whether this node should behave as a server, receiving
connections from the remote Application Server Process (ASP), or as a client,
initiating connections towards the remote ASP.
Mib MediaGateway
Values server
client
Default server
Description This attribute specifies the delayed acknowledgement timer for the Stream
Control Transmission Protocol (SCTP) association used by this Application
Server Process (ASP).
This controls the maximum interval between the sending of SCTP Selective
Acknowledgement (SACK) chunks during idle communication periods.
Mib MediaGateway
Units msec
Default 200
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib MediaGateway
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib MediaGateway
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib MediaGateway
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib MediaGateway
Values idle
active (activ)
busy
Default idle
Description This group contains the operational data for the ApplicationServerProcess
component pertaining to Stream Control Transmission Protocol (SCTP) messages.
Mib MediaGateway
Description This attribute counts M-SCTP Establish Indications received for this Application
Server Process (ASP).
This counter is incremented only when the value of the localRole attribute is set to
server.
Mib MediaGateway
Default No default
Description This attribute counts M-SCTP Establish Requests sent for this Application Server
Process (ASP).
This counter is incremented only when the value of the localRole attribute is set to
client.
Mib MediaGateway
Default No default
Description This attribute counts M-SCTP Establish Requests that failed to successfully
establish a Stream Control Transmission Protocol (SCTP) association with the
remote Application Server Process (ASP).
This counter is incremented only when the value of the localRole attribute is set to
client.
Mib MediaGateway
Default No default
Description This attribute counts M-SCTP Release Indications received for this Application
Server Process (ASP).
This counter is incremented only when the value of the localRole attribute is set to
server.
Mib MediaGateway
Default No default
Description This attribute counts M-SCTP Restart Indications received for this Application
Server Process (ASP).
This counter is incremented only when the value of the localRole attribute is set to
server.
Mib MediaGateway
Default No default
Description This group contains the operational data for the ApplicationServerProcess
component that pertains to the Application Server Process (ASP) state machine
and traffic management.
Mib MediaGateway
Description This attribute counts Application Server Process (ASP) Up (UP) messages
received.
Mib MediaGateway
Default No default
Description This attribute counts Application Server Process (ASP) Down (DOWN) messages
received.
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute counts Application Server Process (ASP) Down Acknowledgement
(DOWN ACK) messages sent.
Mib MediaGateway
Default No default
Description This attribute counts Application Server Process (ASP) Active (ACTIVE)
messages received.
Mib MediaGateway
Default No default
Description This attribute counts Application Server Process (ASP) Inactive (INACTIVE)
messages received.
Mib MediaGateway
Default No default
Description This attribute counts Application Server Process (ASP) Active Acknowledgement
(ACTIVE ACK) messages sent.
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute counts Heartbeat Acknowledgement (BEAT ACK) messages sent.
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This group contains the operational data for the ApplicationServerProcess
component pertaining to errors during traffic management.
Mib MediaGateway
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute counts "Invalid Version" errors sent. This corresponds to error code
0x1 defined in RFC 3331.
Mib MediaGateway
Default No default
Description This attribute counts "Invalid Version" errors received. This corresponds to error
code 0x1 defined in RFC 3331.
Mib MediaGateway
Default No default
Description This attribute counts "Invalid Interface Identifier" errors sent. This corresponds to
error code 0x2 defined in RFC 3331.
This error occurs when the Application Server Process (ASP) references an
Interface Identifier (IID) that is not locally configured.
Mib MediaGateway
Default No default
Description This attribute counts "Invalid Interface Identifier" errors received. This
corresponds to error code 0x2 defined in RFC 3331.
This error occurs when the remote Application Server Process (ASP) does not
recognize the Interface Identifier (IID) that it has received.
Mib MediaGateway
Default No default
Description This attribute counts the following errors sent that are defined in RFC 3331:
- "Unsupported Message Class" (error code 0x3)
- "Unsupported Message Type" (error code 0x4)
- "Unsupported Traffic Handling Mode" (error code 0x5).
Mib MediaGateway
Default No default
Description This attribute counts the following errors received that are defined in RFC 3331:
- "Unsupported Message Class" (error code 0x3)
- "Unsupported Message Type" (error code 0x4)
- "Unsupported Traffic Handling Mode" (error code 0x5).
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute counts protocol errors detected by the remote Application Server
Process (ASP).
Mib MediaGateway
Default No default
This corresponds to error code 0x9 defined in RFC 3331. This error is sent if a
management message is received on a stream other than "0".
Mib MediaGateway
Default No default
This corresponds to error code 0x9 defined in RFC 3331. Receipt of this error
indicates that the remote node received a message on an unexpected Stream
Control Transmission Protocol (SCTP) stream.
Mib MediaGateway
Default No default
Description This attribute counts the times the Message Transfer Part Layer 2 User Adaptation
(M2UA) application was unable to send a Stream Control Transmission Protocol
(SCTP) message to the remote Application Server Process (ASP).
The most likely cause of a send failure is congestion on the remote node.
Messages that the SCTP layer is unable to send are discarded.
Mib MediaGateway
Default No default
COLLECTED STATS
NarrowbandServicesTrunkOverATM VoiceGateway
M2ua ApplicationServer
ApplicationServerProcess Default
Description The statistics record generated by the NarrowbandServicesTrunkOverATM
VoiceGateway M2ua ApplicationServer ApplicationServerProcess component.
Description This attribute counts Heartbeat Acknowledgement (BEAT ACK) messages sent.
This error occurs when the Application Server Process (ASP) references an
Interface Identifier (IID) that is not locally configured.
This error occurs when the remote Application Server Process (ASP) does not
recognize the Interface Identifier (IID) that it has received.
This corresponds to error code 0x9 defined in RFC 3331. This error is sent if a
management message is received on a stream other than "0".
This corresponds to error code 0x9 defined in RFC 3331. Receipt of this error
The most likely cause of a send failure is congestion on the remote node.
Messages that the SCTP layer is unable to send are discarded.
This counter is incremented only when the value of the localRole attribute is set to
server.
This counter is incremented only when the value of the localRole attribute is set to
client.
This counter is incremented only when the value of the localRole attribute is set to
client.
This counter is incremented only when the value of the localRole attribute is set to
server.
This counter is incremented only when the value of the localRole attribute is set to
server.
Scope Device
The component provides per-association statistics that are not cleared when the
association is released, but maintained over time.
Mib MediaGateway
Description This group contains the operational data for the SctpAssoc component pertaining
to the Stream Control Transmission Protocol (SCTP) communication.
Mib MediaGateway
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
This count includes the Stream Control Transmission Protocol (SCTP) message
headers and chunk headers but does not include the IP header.
Mib MediaGateway
Default No default
This count includes the Stream Control Transmission Protocol (SCTP) message
headers and chunk headers but does not include the IP header.
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute indicates the current number of outbound streams for this Stream
Control Transmission Protocol (SCTP) association.
Mib MediaGateway
Default No default
Description This attribute indicates the current number of inbound streams for this Stream
Control Transmission Protocol (SCTP) association.
Mib MediaGateway
Default No default
Description This attribute indicates the reason for the most recent Stream Control
Transmission Protocol (SCTP) association failure.
Mib MediaGateway
Values none
farEndAbort
farEndShutdown
communicationTimeout
maxUnackedMsgsLimit
Default No default
Description This attribute indicates the date and Universal Time Coordinated (UTC) time at
which the last Stream Control Transmission Protocol (SCTP) association failure
Mib MediaGateway
Default No default
Description This attribute indicates the Smoothed Round-Trip Time (SRTT) as defined in RFC
2960.
Mib MediaGateway
Units msec
Default No default
Description This group contains the operational data for the SctpAssoc component pertaining
to errors and diagnostics in the Stream Control Transmission Protocol (SCTP)
communication.
Mib MediaGateway
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute counts "Restart of an association with new addresses" errors sent.
Mib MediaGateway
Default No default
Description This attribute counts "Restart of an association with new addresses" errors
received.
Mib MediaGateway
Default No default
Description This attribute counts "User Initiated Abort" indications sent by the local Stream
Control Transmission Protocol (SCTP) user.
Mib MediaGateway
Default No default
Description This attribute counts "User Initiated Abort" indications received from the peer
Stream Control Transmission Protocol (SCTP) user.
Mib MediaGateway
Default No default
Description This attribute counts incoming packets that were discarded due to checksum
verification failure.
Mib MediaGateway
Default No default
Mib MediaGateway
Default No default
Description This attribute counts chunks reported to the far end in "Gap Ack" reports. This
provides an indication of the number of chunks that were locally received out of
order.
Mib MediaGateway
Default No default
Description This attribute counts chunks reported by the far end in "Gap Ack" reports. This
provides an indication of the number of chunks that were received out of order by
the far end.
Mib MediaGateway
Default No default
Description This attribute counts chunks reported to the far end in "Duplicate TSN" reports.
This provides an indication of the number of duplicate data chunks that were
locally received.
Mib MediaGateway
Default No default
Description This attribute counts chunks reported by the far end in "Duplicate TSN" reports.
This provides an indication of the number of duplicate data chunks that were
received by the far end.
Mib MediaGateway
Default No default
COLLECTED STATS
NarrowbandServicesTrunkOverATM
VoiceGateway M2ua ApplicationServer
ApplicationServerProcess
SctpAssociationDefault
Description The statistics record generated by the NarrowbandServicesTrunkOverATM
VoiceGateway M2ua ApplicationServer ApplicationServerProcess
SctpAssociation component.
This count includes the Stream Control Transmission Protocol (SCTP) message
headers and chunk headers but does not include the IP header.
This count includes the Stream Control Transmission Protocol (SCTP) message
headers and chunk headers but does not include the IP header.
errorChunksSent
Description This attribute counts Operation Error (ERROR) chunks sent.
Mib Vgs
Scope Device
The ATM Call Admission Control (CAC) application monitors the aggregate
network bandwidth utilization for ATM Adaptation Layer 2 (AAL2) connections
established from this Voice Services Processor (VSP) card to destinations in this
subnet. If a bandwidth limit is assigned and the available bandwidth is exhausted,
CAC will deny new connection requests to destinations in this subnet.
Mib Vgs
Description This group contains the provisionable data for the AtmSubnet component.
Mib Vgs
Criticality Component
Description This attribute specifies the prefix digits of the remote Asynchronous Transfer
Mode Adaptation Layer 2 (AAL2) endpoint Network Service Access Point
(NSAP) address.
The default value is a null string, meaning that it matches any address. When the
value is set to null, this component represents the default network address and is
associated with remote addresses that do not match any other AtmSubnet
component. Only one AtmSubnet may be assigned the default address.
The value must be unique among the AtmSubnet components under the parent
AtmCac component. Overlapping address ranges are not allowed. Two address
prefixes are considered overlapping if the shorter prefix matches the initial digits
of the longer prefix.
Mib Vgs
Default No default
Description This attribute specifies the maximum external network bandwidth available for
Asynchronous Transfer Mode Adaptation Layer 2 (AAL2) connections to
destinations within the subnet represented by this component. The limit applies to
bearer connections originating from or terminating to this Voice Services
Processor (VSP) card.
A new connection attempt is rejected if adding the new connection would exceed
the bandwidth limit.
Mib Vgs
Units kbit/s
Default unlimited
Description This group contains the operational data for the AtmSubnet and IpSubnet
components pertaining to Asynchronous Transfer Mode (ATM) and Internet
Protocol (IP) Call Admission Control (CAC).
Mib Vgs
Description This attribute indicates the current network bandwidth allocated to connections
originating or terminating within this subnet. The value is rounded down to the
nearest kilobit.
Mib Vgs
Units kbit/s
Default No default
Description This attribute indicates the current percentage of available network bandwidth
allocated to connections originating or terminating within this subnet. Utilization
is expressed as a percentage of the provisioned
networkBandwidthAvailablePerVsp attribute.
Mib Vgs
Units %
Default No default
Description This attribute counts connection attempts rejected as the result of having
insufficient bandwidth available in this subnet.
Mib Vgs
Default No default
Description This attribute counts codec upspeeds from Adaptive Multi-Rate (AMR) to
G.711 (64 kbit/s) for connections within this subnet. This includes unilateral
upspeeds and codec modification requests from the Media Gateway Controller
(MGC).
Mib Vgs
Default No default
Units kbit/s
Units kbit/s
Scope Application
Description Q2630/n
This component represents the Q.2630 Signalling component that is used for
establishing and maintaining the bearer connections between this Media Gateway
and the peer nodes such as Radio Network Controllers (RNCs) and other Media
Gateways.
Mib Q2630
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Q2630
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Q2630
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Q2630
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Q2630
Values idle
active (activ)
busy
Default idle
Description This group contains the provisioning data for the Q2630 component pertaining to
communication with the client and peer.
Mib Q2630
Criticality Process
Description This attribute specifies the Logical Processor on which this component and its
subcomponents are provisioned.
Mib Q2630
Default No default
Description This group contains the provisioning data for the Q2630 component pertaining to
timers related to protocol operations.
Mib Q2630
Description This attribute specifies the value of the timer Timer_ERQ defined in the ITU-T
recommendation Q.2630. This timer is started when an ESTABLISH REQUEST
message is sent to the Q.2630 peer entity.
This timer value specifies the time to wait for a response message (for example, a
ESTABLISH CONFIRM message) from the peer Q.2630 entity and is stopped
when the expected message is received.
The number of retries that can be attempted is specified by the value of the
provisionable attribute establishRequestRetries. If the response message is not
received in the allowed number of retries, then the value of the
establishReqRetryExhausts attribute is incremented.
Mib Q2630
Units seconds
Default 5
Description This attribute specifies the number of ESTABLISH REQUEST message retries to
be performed by the Q.2630 entity when a response message is not received from
the peer Q.2630 entity.
The time that the Q.2630 entity waits for a response before attempting a retry is
specified by the value of the provisionable attribute establishRequestTimer.
Mib Q2630
Default 0
Description This attribute specifies the value of the timer Timer_REL defined in the ITU-T
recommendation Q.2630. This timer is started when a RELEASE REQUEST
message is sent to the Q.2630 peer entity.
This timer value specifies the time to wait for a response message (for example, a
RELEASE CONFIRM message) from the peer Q.2630 entity and is stopped when
the expected message is received.
The number of retries that can be attempted is specified by the value of the
provisionable attribute releaseRequestRetries. If the response message is not
received in the allowed number of retries, then the value of the
releaseReqRetryExhausts attribute is incremented.
Mib Q2630
Units seconds
Default 4
Description This attribute specifies the number of RELEASE REQUEST message retries to be
performed by the Q.2630 entity when a response message is not received from the
peer Q.2630 entity.
The time that the Q.2630 entity waits for a response before attempting a retry is
specified by the value of the provisionable attribute releaseRequestTimer.
Mib Q2630
Default 0
Description This attribute specifies the value of the timer Timer_RES defined in the ITU-T
recommendation Q.2630. This timer is started when a RESET REQUEST
message is sent to the Q.2630 peer entity.
This timer value specifies the time to wait for a response message (for example, a
RESET CONFIRM message) from the peer Q.2630 entity and is stopped when
the expected message is received.
Mib Q2630
Units seconds
Default 5
Description This attribute specifies the value of the timer Timer_BLO defined in ITU-T
recommendation Q.2630. This timer is started when a BLOCK REQUEST
message is sent to the Q.2630 peer entity.
This timer value specifies the time to wait for a response message (for example, a
BLOCK CONFIRM message) from the peer Q.2630 entity and is stopped when
the expected message is received.
The number of retries that can be attempted is specified by the value of the
provisionable attribute blockRequestRetries. If the response message is not
received in the allowed number of retries, then the value of the
blockReqRetryExhausts attribute is incremented.
Mib Q2630
Units seconds
Default 30
Description This attribute specifies the number of BLOCK REQUEST message retries to be
performed by the Q.2630 entity when a response message is not received from the
peer Q.2630 entity.
The time that the Q.2630 entity waits for a response before attempting a retry is
specified by the value of the provisionable attribute blockRequestTimer.
Mib Q2630
Default 0
Description This attribute specifies the value of the timer Timer_UBL defined in ITU-T
recommendation Q.2630. This timer is started when an UNBLOCK REQUEST
message is sent to the Q.2630 peer entity.
This timer value specifies the time to wait for a response message (for example,
an UNBLOCK CONFIRM message) from the peer Q.2630 entity and is stopped
when the expected message is received.
The number of retries that can be attempted is specified by the value of the
provisionable attribute unblockRequestRetries. If the response message is not
received in the allowed number of retries, then the value of the
unblockReqRetryExhausts attribute is incremented.
Mib Q2630
Units seconds
Default 30
Description This attribute specifies the number of UNBLOCK REQUEST message retries to
be performed by the Q.2630 entity when a response message is not received from
the peer Q.2630 entity.
The time that the Q.2630 entity waits for a response before attempting a retry is
specified by the value of the provisionable attribute unblockRequestTimer.
Mib Q2630
Default 0
Description This attribute specifies the value of the timer Timer_MOD defined in the ITU-T
recommendation Q.2630. This timer is started when a MODIFY REQUEST
message is sent to the Q.2630 peer entity.
This timer value specifies the time to wait for a response message (for example, a
MODIFY ACKNOWLEDGE message) from the peer Q.2630 entity and is
stopped when the expected message is received.
The number of retries that can be attempted is specified by the value of the
provisionable attribute modifyRequestRetries. If the response message is not
received in the allowed number of retries, then the value of the
modifyReqRetryExhausts attribute is incremented.
Mib Q2630
Units seconds
Default 5
Description This attribute specifies the number of MODIFY REQUEST message retries to be
performed by the Q.2630 entity when a response message is not received from the
peer Q.2630 entity.
The time that the Q.2630 entity waits for a response before attempting a retry is
specified by the value of the provisionable attribute modifyRequestTimer.
Mib Q2630
Default 0
Description This group contains the operational data for the Q2630 component pertaining to
timers related to protocol operations.
Mib Q2630
Description This attribute counts the number of times the timer Timer_ERQ has expired.
The timer duration may be set by changing the value of the provisionable attribute
establishRequestTimer.
Mib Q2630
Default No default
Description This attribute counts the number of times the ESTABLISH REQUEST retry
mechanism (specified by the value of the provisionable attribute
establishRequestRetries) failed to get the expected response from the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the number of times the timer Timer_REL has expired.
The timer duration may be set by changing the value of the provisionable attribute
releaseRequestTimer.
Mib Q2630
Default No default
Description This attribute counts the number of times the RELEASE REQUEST retry
mechanism (specified by the value of the provisionable attribute
releaseRequestRetries) failed to get the expected response from the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the number of times the timer Timer_RES has expired.
The timer duration may be set by changing the value of the provisionable attribute
resetRequestTimer.
Mib Q2630
Default No default
Description This attribute counts the number of times the timer Timer_BLO has expired.
The timer duration may be set by changing the value of the provisionable attribute
blockRequestTimer.
Mib Q2630
Default No default
Description This attribute counts the number of times the BLOCK REQUEST retry
mechanism (specified by the value of the provisionable attribute
blockRequestRetries) failed to get the expected response from the Q.2630 peer
entity.
- The duration is set too short. The duration may be set by changing the value of
the provisionable attribute blockRequestTimer.
Mib Q2630
Default No default
Description This attribute counts the number of times the timer Timer_UBL has expired.
The timer duration may be set by changing the value of the provisionable attribute
unblockRequestTimer.
Mib Q2630
Default No default
Description This attribute counts the number of times the UNBLOCK REQUEST retry
mechanism (specified by the value of the provisionable attribute
unblockRequestRetries) failed to get the expected response from the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the number of times the timer Timer_MOD has expired.
The timer duration may be set by changing the value of the provisionable attribute
modifyRequestTimer.
Mib Q2630
Default No default
Description This attribute counts the number of times the MODIFY REQUEST retry
mechanism (specified by the value of the provisionable attribute
modifyRequestRetries) failed to get the expected response from the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This group contains the operational data for the Q2630 component pertaining to
the messages sent and received from the peer.
Mib Q2630
Description This attribute counts the ESTABLISH REQUEST messages sent to the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the ESTABLISH REQUEST messages received from the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the ESTABLISH CONFIRM messages sent to the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the ESTABLISH CONFIRM messages received from the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the RELEASE CONFIRM messages sent to the Q.2630 peer
entity with the cause indicating that the connection could not be established.
The cause sent in the RELEASE CONFIRM message is described in the Q.2630
ITU-T specification.
Mib Q2630
Default No default
Description This attribute counts the RELEASE CONFIRM message received from the
Q.2630 peer entity with the cause indicating that the connection could not be
established.
Mib Q2630
Default No default
Description This attribute counts the MODIFY REQUEST messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the MODIFY REQUEST messages received from the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the MODIFY ACKNOWLEDGE messages sent to the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the MODIFY ACKNOWLEDGE messages received from
the Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the MODIFY REJECT messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the MODIFY REJECT messages received from the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the RELEASE REQUEST messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the RELEASE REQUEST messages received from the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the RELEASE CONFIRM messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the RELEASE CONFIRM messages received from the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the RELEASE CONFIRM messages sent to the Q.2630 peer
entity with the cause indicating that a failure occurred in the Release procedure.
The cause sent in the RELEASE CONFIRM message is described in the Q.2630
ITU-T specification.
Mib Q2630
Default No default
Description This attribute counts the RELEASE CONFIRM messages received from the
Q.2630 peer entity with the cause indicating that a failure occurred in the Release
procedure.
Mib Q2630
Default No default
Description This attribute counts the RESET REQUEST messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the RESET REQUEST messages received from the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the RESET CONFIRM messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the RESET CONFIRM messages received from the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the RESET CONFIRM messages sent to the Q.2630 peer
entity with the cause indicating that a failure occurred in the Reset procedure.
The cause sent in the RESET CONFIRM message is described in the Q.2630
ITU-T specification.
Mib Q2630
Default No default
Description This attribute counts the RESET CONFIRM messages received from the Q.2630
peer entity with the cause indicating that a failure occurred in the Reset procedure.
The cause received in the RESET CONFIRM message is described in the Q.2630
ITU-T specification.
Mib Q2630
Default No default
Description This attribute counts the BLOCK REQUEST messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the BLOCK REQUEST messages received from the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the BLOCK CONFIRM messages sent to the Q.2630 peer
entity.
Mib Q2630
Default No default
Description This attribute counts the BLOCK CONFIRM messages received from the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the BLOCK CONFIRM messages sent to the Q.2630 peer
entity with the cause indicating that a failure occurred in the Block procedure.
The cause sent in the BLOCK CONFIRM message is described in the Q.2630
ITU-T specification.
Mib Q2630
Default No default
Description This attribute counts the BLOCK CONFIRM messages received from the Q.2630
peer entity with the cause indicating that a failure occurred in the Block
procedure.
The cause received in the BLOCK CONFIRM message is described in the Q.2630
ITU-T specification.
Mib Q2630
Default No default
Description This attribute counts the UNBLOCK REQUEST messages sent to the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the UNBLOCK REQUEST messages received from the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the UNBLOCK CONFIRM messages sent to the Q.2630
peer entity.
Mib Q2630
Default No default
Description This attribute counts the UNBLOCK CONFIRM messages received from the
Q.2630 peer entity.
Mib Q2630
Default No default
Description This attribute counts the UNBLOCK CONFIRM messages sent to the Q.2630
peer entity with the cause indicating that a failure occurred in the Unblock
procedure.
The cause sent in the UNBLOCK CONFIRM message is described in the Q.2630
ITU-T specification.
Mib Q2630
Default No default
Description This attribute counts the UNBLOCK CONFIRM messages received from the
Q.2630 peer entity with the cause indicating that a failure occurred in the Unblock
procedure.
Mib Q2630
Default No default
Description This attribute counts the CONFUSION messages sent to the Q.2630 peer entity, in
response to unrecognized messages and messages with unrecognized or invalid
parameters received.
Mib Q2630
Default No default
Mib Q2630
Default No default
Description This group contains the operational data for the Q2630 component pertaining to
its usage.
Mib Q2630
Description This attribute indicates the currently established connections between this
component and the peer.
Mib Q2630
Default No default
Description This attribute indicates the currently existing AAL2 (Asynchronous Transfer
Mode Adaptation Layer 2) bearer paths, both blocked and unblocked, between
this and the peer.
Mib Q2630
Default No default
Description This attribute indicates the locally blocked bearer paths between this Media
Gateway and the peer. A bearer path (for example, switched virtual channel)
supports a collection of user connections (for example, voice or fax call) between
two Media Gateways. New, non-test connections cannot be established on a
blocked path.
A path may be blocked because of maintenance actions at either this node or the
peer. A locked MgcIf component on this Media Gateway will block all paths
emanating from this Media Gateway. Correspondingly, a locked MgcIf component
at the peer will cause only those paths between this and that peer to become
blocked.
Mib Q2630
Default No default
Description This attribute indicates the remotely blocked bearer paths between this Media
Gateway and the peer. A bearer path (for example, switched virtual channel)
supports a collection of user connections between two Media Gateways. New,
non-test connections (for example, voice or fax calls) cannot be established on a
blocked path.
A path may be blocked because of maintenance actions at either this node or the
peer. A locked MgcIf component on this Media Gateway will block all paths
emanating from this Media Gateway. Correspondingly, a locked MgcIf component
at the peer will cause only those paths between this and that peer to become
blocked.
Mib Q2630
Default No default
Description This group contains the operational data for the Q2630 component pertaining to
the messages to and from the client.
Mib Q2630
Description This attribute counts the messages that the Q2630 component has received from
the Q2630Client component.
Mib Q2630
Default No default
Description This attribute counts the messages that the Q2630 component has sent to the
Q2630Client component.
Mib Q2630
Default No default
Description This group contains the operational data for the Q2630 component pertaining to
error scenarios.
Mib Q2630
Description This attribute counts Unallocated (unassigned) number errors received. This
corresponds to cause code 1 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts Unallocated (unassigned) number errors sent. This
corresponds to cause code 1 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts No route to destination errors received. This corresponds
to cause code 3 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts No route to destination errors sent. This corresponds to
cause code 3 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Mib Q2630
Default No default
Description This attribute counts Temporary failure errors received. This corresponds to
cause code 41 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute of Temporary failure errors sent. This corresponds to cause code
41 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts Network out of order errors received. This corresponds to
cause code 38 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts Requested circuit/channel not available errors received.
This corresponds to cause code 44 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts Requested circuit/channel not available errors sent. This
corresponds to cause code 44 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts Resource unavailable, unspecified errors received. This
corresponds to cause code 47 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts Resource unavailable, unspecified errors sent. This
corresponds to cause code 47 defined in ITU-T Q.2630.1.
Mib Q2630
Default No default
Description This attribute counts protocol errors detected by the peer. This corresponds to the
following cause codes defined in ITU-T Q.2630.1:
93 - AAL parameters cannot be supported
95 - Invalid message, unspecified
96 - Mandatory information element is missing
97 - Message type non-existent or not implemented
99 - Information element/parameter non-existent or not implemented
100 - Invalid information element contents
110 - Message with unrecognized parameter, discarded
Mib Q2630
Default No default
Description This attribute counts protocol errors detected locally. This corresponds to cause
codes defined in ITU-T Q.2630.1:
93 - AAL parameters cannot be supported
95 - Invalid message, unspecified
96 - Mandatory information element is missing
97 - Message type non-existent or not implemented
Mib Q2630
Default No default
The cause sent in the RELEASE CONFIRM message is described in the Q.2630
ITU-T specification.
The cause sent in the RELEASE CONFIRM message is described in the Q.2630
ITU-T specification.
The cause sent in the RESET CONFIRM message is described in the Q.2630
ITU-T specification.
The cause received in the RESET CONFIRM message is described in the Q.2630
ITU-T specification.
The cause sent in the BLOCK CONFIRM message is described in the Q.2630
ITU-T specification.
The cause received in the BLOCK CONFIRM message is described in the Q.2630
ITU-T specification.
The cause sent in the UNBLOCK CONFIRM message is described in the Q.2630
ITU-T specification.
The timer duration may be set by changing the value of the provisionable attribute
establishRequestTimer.
The timer duration may be set by changing the value of the provisionable attribute
releaseRequestTimer.
- The number of retries is set too low. The number of retries may be set by
changing the value of the provisionable attribute releaseRequestRetries.
- The duration is set too short. The duration may be set by changing the value of
the provisionable attribute releaseRequestTimer.
The timer duration may be set by changing the value of the provisionable attribute
resetRequestTimer.
The timer duration may be set by changing the value of the provisionable attribute
blockRequestTimer.
- The duration is set too short. The duration may be set by changing the value of
the provisionable attribute blockRequestTimer.
The timer duration may be set by changing the value of the provisionable attribute
unblockRequestTimer.
The timer duration may be set by changing the value of the provisionable attribute
modifyRequestTimer.
Scope Application
Mib Q2630
Mib Q2630
Criticality Process
Changing this attribute will cause the application using the MTP3 layers services
to be restarted.
Mib Q2630
Default No default
Description This group contains the spare counters that can be dynamically patched.
Mib Q2630
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Q2630
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Q2630
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Q2630
Default No default
Scope Device
This component represents the address of the peer ATM Adaptation Layer 2
(AAL2) end station. The end station may be either a peer Media Gateway or a
Radio Network Controller (RNC). This address is required for Q.2630 messages
over broadband Message Transfer Part Layer 3 (MTP3b).
Mib Q2630
Description This group contains the provisioning data for the PeerAddress component.
Mib Q2630
Criticality Component
Description This attribute specifies the Asynchronous Transfer Mode End Station Address
(AESA) of the peer.
Mib Q2630
Default No default
Criticality Component
basic: The point code is provisioned as a decimal number in the range 1..16383. A
value of 0 is not valid.
segmented: The point code is provisioned as three integers, separated by dots. The
first integer must be in the range 0..7, the second integer must be in the range
0..255, and the third integer must be in the range 0..7. A value of 0.0.0 is not
valid.
Mib Q2630
Default No default
Criticality Component
Description This attribute specifies the Nsta/x Vgs VoiceProfile/y component this instance is
linked to.
Mib Q2630
Default No default
Description This attribute specifies the Asynchronous Transport Mode (ATM) connections
owned by this component.
Mib Q2630
Default No default
Scope Application
This component represents the Served User and the Layer Management Service
Access Points, specified by the Q.2630 ITU-T specification.
Mib Q2630
Description This group contains the operational data for the Q2630Client component.
Mib Q2630
Description This attribute counts the ERROR INDICATION messages sent to the Layer
Management of Q.2630.
Mib Q2630
Default No default
Description This attribute counts the ADD PATH messages received from the Layer
Management of Q.2630.
Mib Q2630
Default No default
Description This attribute counts the REMOVE PATH messages received from the Layer
Management of Q.2630.
Mib Q2630
Default No default
Description This attribute counts the messages received with unknown or invalid Information
Element (IE), or missing mandatory IEs, or invalid IE content from the Served
User or the Layer Management of Q.2630.
Mib Q2630
Default No default
Description This attribute counts the messages that the Q2630Client component was unable to
forward to the Q2630 component.
Mib Q2630
Default No default
Description This attribute counts the messages received by the Q2630Client component from
the Q2630 component.
Mib Q2630
Default No default
Description This attribute counts the messages sent by the Q2630Client component to the
Q2630 component.
Mib Q2630
Default No default
Scope Application
Mib Q2630
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Q2630
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Q2630
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Q2630
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Q2630
Values idle
active (activ)
busy
Default idle
Mib Q2630
Description This attribute counts the communication failures between the neighbors being
monitored.
Mib Q2630
Default No default
Description This attribute counts the payload messages sent to the neighbor but were not
received by the neighbor.
Mib Q2630
Default No default
Description This attribute counts the payload messages that were sent by the neighbor but
were not received by this component. This is detected by a gap in the Message
Numbers received in payload messages from the neighbor.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Request messages sent by this
component to the neighbor.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Request messages received by this
component.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Response messages sent by this
component.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Response messages received by this
component in response to the Monitor Enable Request message.
Mib Q2630
Default No default
Description This attribute counts the Heartbeat messages sent by this component to the
neighbor.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
Mib Q2630
Default No default
Description This attribute counts the Heartbeat messages received by this component.
The value of this attribute is incremented when the Heartbeat message is received.
Mib Q2630
Default No default
Description This attribute counts the payload messages sent by this component to the
neighbor.
Mib Q2630
Default No default
Description This attribute counts the payload messages received by this component.
Mib Q2630
Default No default
Description This attribute counts the Sequencing Gap messages sent by this component.
Mib Q2630
Default No default
Description This attribute counts the Sequencing Gap messages received by this component.
Mib Q2630
Default No default
Description This attribute counts the messages received by this component that are not
recognized by the MonitoredCommunicationProtocol (MCP).
Mib Q2630
Default No default
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Mib Q2630
Default No default
The value of the Heartbeat timer is negotiated between the monitored parent
components.
Mib Q2630
Units msec
Default No default
Description This attribute indicates the number of time-outs of the Heartbeat timer allowed
before marking the communication with the neighbor as down.
The value of the Heartbeat retries is negotiated between the monitored parent
components.
Mib Q2630
Default No default
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
Description This attribute counts the Heartbeat messages received by this component.
The value of this attribute is incremented when the Heartbeat message is received.
Description This attribute counts the messages received by this component that are not
recognized by the MonitoredCommunicationProtocol (MCP).
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Scope Application
Mib Q2630
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Q2630
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Q2630
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Q2630
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Q2630
Values idle
active (activ)
busy
Default idle
Mib Q2630
Description This attribute counts the communication failures between the neighbors being
monitored.
Mib Q2630
Default No default
Description This attribute counts the payload messages sent to the neighbor but were not
received by the neighbor.
Mib Q2630
Default No default
Description This attribute counts the payload messages that were sent by the neighbor but
were not received by this component. This is detected by a gap in the Message
Numbers received in payload messages from the neighbor.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Request messages sent by this
component to the neighbor.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Request messages received by this
component.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Response messages sent by this
component.
Mib Q2630
Default No default
Description This attribute counts the Monitor Enable Response messages received by this
component in response to the Monitor Enable Request message.
Mib Q2630
Default No default
Description This attribute counts the Heartbeat messages sent by this component to the
neighbor.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
Mib Q2630
Default No default
Description This attribute counts the Heartbeat messages received by this component.
The value of this attribute is incremented when the Heartbeat message is received.
Mib Q2630
Default No default
Description This attribute counts the payload messages sent by this component to the
neighbor.
Mib Q2630
Default No default
Description This attribute counts the payload messages received by this component.
Mib Q2630
Default No default
Description This attribute counts the Sequencing Gap messages sent by this component.
Mib Q2630
Default No default
Description This attribute counts the Sequencing Gap messages received by this component.
Mib Q2630
Default No default
Description This attribute counts the messages received by this component that are not
recognized by the MonitoredCommunicationProtocol (MCP).
Mib Q2630
Default No default
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Mib Q2630
Default No default
The value of the Heartbeat timer is negotiated between the monitored parent
components.
Mib Q2630
Units msec
Default No default
Description This attribute indicates the number of time-outs of the Heartbeat timer allowed
before marking the communication with the neighbor as down.
The value of the Heartbeat retries is negotiated between the monitored parent
components.
Mib Q2630
Default No default
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
The value of this attribute is incremented when the Heartbeat message is received.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Component Gips and its subcomponents are presented below, beginning with
the Instance and Groups descriptions.
Scope Application
Description GprsIpServer/n
Mib WirelessGips
Description This group contains the attribute for a components Customer Identifier (CID).
Refer to the attribute description for a detailed explanation of CIDs.
Mib WirelessGips
Every component has a CID. If a component has a cid attribute, the components
CID is the provisioned value of that attribute; otherwise the component inherits
the CID of its parent. The top-level component has a CID of 0.
Every operator session also has a CID, which is the CID provisioned for the
operators user ID. An operator will see only the stream data for components
having a matching CID. Also, the operator will be allowed to issue commands for
only those components which have a matching CID.
Mib WirelessGips
Default 0
Description This group contains the provisionable attributes for the ifEntry.
Mib WirelessGips
Description The desired state of the interface. The up state indicates the interface is
operational. The down state indicates the interface is not operational. The testing
state indicates that no operational packets can be passed.
Mib WirelessGips
Values up
down
testing
Default up
Criticality Component
Description This is the index for the IfEntry. Its value is automatically initialized during the
provisioning process.
Mib WirelessGips
Default No default
Description This group contains the provisionable attributes of the GprsIpServer component.
Mib WirelessGips
Description This attribute specifies the Virtual Router Protocol Port that the GprsIpServer
associates with.
Mib WirelessGips
Default No default
Description This attribute specifies the Logical Processor that the GprsIpServer and its
subcomponents are provisioned on.
Mib WirelessGips
Default No default
Description This attribute specifies the default value inserted into the Time-
To-Live field of the IP header of datagrams originated at this entity.
This is the value used to build the IP header unless it is overridden by an
application.
Mib WirelessGips
Default 64
Description This attribute specifies the maximum time that the received fragments of IP
packets are held while awaiting reassembly at the GprsIpServer.
Mib WirelessGips
Units seconds
Default 5
Description This attribute specifies whether the UDP checksum is generated and checked.
Mib WirelessGips
Values no
yes
Default no
Description This group contains the GPRS Internet Protocol (IP) related statistical attributes.
Mib WirelessGips
Description This attribute counts all the incoming datagrams destined to an address for which
there is no IpAddress subcomponent. This includes fragmented packets. The
counter wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the input datagrams discarded due to errors in their IP
headers, including bad checksums, version number mismatch, address errors
which have not already been filtered by the IP forwarder. The counter wraps to
zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Scope Application
should not be the virtual router protocol port logical interface address, the subnet
address, or the subnet broadcast address.
Mib WirelessGips
Description This group contains the Internet Protocol (IP) related statistical attributes.
Mib WirelessGips
Description This attribute counts all the incoming datagrams, including those counted in
inErrors and inUnknownProtocols. The counter wraps to zero when it exceeds the
maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the input datagrams discarded due to errors in their IP
headers, version number mismatch, other format errors, and time-to-live exceeded
which have not already been filtered by the Virtual Routers IP forwarder. The
counter wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the locally-addressed datagrams received successfully but
discarded because of an unknown or unsupported protocol. The counter wraps to
zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the input datagrams successfully delivered to the IP user-
protocols (including Internet Control Message Protocol (ICMP)). The counter
wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the datagrams which the local IP user-protocols (including
Internet Control Message Protocol (ICMP)) supplied to IP in requests for
transmission. The counter wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the IP packet reassembly time-outs at the receiving
GprsIpServer. The counter wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the IP packets with the reassembly bit set. The counter wraps
to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the IP packets successfully reassembled by the GprsIpServer.
The counter wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the number of times the GprsIpServer is unable to assemble
IP-fragments for any reason. The counter wraps to zero when it exceeds the
maximum value.
Mib WirelessGips
Default No default
Scope Application
Mib WirelessGips
Description This group contains all UDP related statistical attributes supported by the
GprsIpServer.
Mib WirelessGips
Description This attribute counts the UDP datagrams delivered to UDP users. The counter
wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the UDP datagrams sent from the UDP stack. The counter
wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the UDP datagrams received for which there was no
associated application at the destination port. The counter wraps to zero when it
exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the received UDP datagrams that could not be delivered for
reasons other than the lack of an application at the destination port. The counter
wraps to zero when it exceeds the maximum value.
Mib WirelessGips
Default No default
Scope Application
This component represents a UDP port. GPRS applications link to this port.
Mib WirelessGips
Description This group contains the provisionable attribute to bind GPRS application to this
UDP port.
Mib WirelessGips
Mib WirelessGips
Values Link
Default No default
Scope Application
Mib WirelessGips
Description This group contains the Internet Control Message Protocol (ICMP) related
statistical attributes.
Mib WirelessGips
Description This attribute counts the Internet Control Message Protocol (ICMP) messages
received by the GprsIpServer. The counter wraps to zero when it exceeds the
maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) messages
received by the GprsIpServer, but determined as having ICMP specific errors such
as bad ICMP checksums or bad length. The counter wraps to zero when it exceeds
the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) time
exceeded messages received by the GprsIpServer. The counter wraps to zero
when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) time
exceeded messages sent by the GprsIpServer. The counter wraps to zero when it
exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) echo request
messages received by the GprsIpServer. The counter wraps to zero when it
exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) echo reply
messages sent by this GprsIpServer. The counter wraps to zero when it exceeds
the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) timestamp
request messages received by this GprsIpServer. The counter wraps to zero when
it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) timestamp
reply messages sent by this GprsIpServer. The counter wraps to zero when it
exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) destination
unreachable messages received by the GprsIpServer. The counter wraps to zero
when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) destination
unreachable messages sent out by this GprsIpServer. The counter wraps to zero
when it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) parameter
problem messages received by the GprsIpServer. The counter wraps to zero when
it exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) parameter
problem messages sent by this GprsIpServer. The counter wraps to zero when it
exceeds the maximum value.
Mib WirelessGips
Default No default
Description This attribute counts the Internet Control Message Protocol (ICMP) source
quench messages received by the GprsIpServer. The counter wraps to zero when
it exceeds the maximum value.
Mib WirelessGips
Default No default
Scope Application
Mib WirelessGips
Mib WirelessGips
Description Indicate which algorithm was used to calculate the timeout value used for
retransmitting unackowledged octet.
Mib WirelessGips
Values other
constant
rsre
vanJacobson
Default No default
Mib WirelessGips
Units msec
Default 0
Mib WirelessGips
Units msec
Default No default
Description Limit on number of connections the TCP can support. The value is always -1
which indicates that the number of connections supported is dynamic (limited by
memory in the system).
Mib WirelessGips
Default -1
Description The number of times TCP connections have made a direct transition to the
synSent state from the closed state.
Mib WirelessGips
Default No default
Description The number of times TCP connections have made a direct transition to the
synRcvd state from the listen state.
Mib WirelessGips
Default No default
Description The number of times TCP connections have made a direct transition to the closed
state from either the synSent state or the synRcvd state, plus the number of times
TCP connections have made a direct transition to the listen state from the
synRcvd state.
Mib WirelessGips
Default No default
Description The number of times TCP connections have made a direct transition to the closed
state from either the established state or the closedWait state.
Mib WirelessGips
Default No default
Description The number of TCP connections for which the current state is either established
or closedWait.
Mib WirelessGips
Default No default
Description The number of segments received, including those received in error. This count
includes segments received on currently established connections.
Mib WirelessGips
Default No default
Description The number of segments sent, including those on current connections but
excluding those containing only retransmitted octets.
Mib WirelessGips
Default No default
Description The number of segments retransmitted that is, the number of TCP segments
transmitted containing one or more previously transmitted octets.
Mib WirelessGips
Default No default
Description Total number of segments received in error, for example bad TCP checksum.
Mib WirelessGips
Default No default
Mib WirelessGips
Default No default
Scope Application
This component represents a TCP port. GPRS applications using TCP link to this
port.
Mib WirelessGips
Description This group contains the provisionable attribute to bind a GPRS application to this
TCP port.
Mib WirelessGips
Description This attribute specifies the GPRS application which is to use this TCP port
number.
Mib WirelessGips
Default No default
Scope Application
The component defines an entry in the TCP connection table. Each entry
Mib WirelessGips
Description This group contains columnar entries for each end-point on the TCP.
Mib WirelessGips
Description This attribute reflects the current state of this Tcp connection.
Mib WirelessGips
Values closed
listen
synSent
synReceived
established
closeWait
finWait1
closing
lastAck
finWait2
timeWait
delete
Default No default
Appendix F: Component
MessageTransferPartLayer3 (Mtp3) F
This appendix contains CDL descriptions for component
MessageTransferPartLayer3 (Mtp3) and its subcomponents. All the attributes
specific to the MG18 release, including operational, collected statistic, and
provisionable attributes, are included. Additional CDL information for
components and attributes common to the Multiservice Switch (formerly
known as Passport) family can be found in the following documents:
NN10600-060_Overview, Nortel Multiservice Switch 7400/15000/20000
Components Overview
the NN10600-060 series of NTPs that reference components
alphabetically.
Component Mtp3 and its subcomponents are presented below, beginning with
the Instance and Groups descriptions.
Scope Application
Description MessageTransferPartLayer3/n
This component represents the Message Transport Part Layer 3 (MTP3) layer of
the SS7 stack.
Mib Ss7Mtp3
Mib Ss7Mtp3
Description This attribute specifies the Logical Processor that this component and its
subcomponents are provisioned on.
Mib Ss7Mtp3
Default No default
Criticality Process
Description This attribute specifies a link to Gips IpAddr UDP Port on an IP Server. This
determines the IP Address and UDP port that all MTP layer 3 users use to address
this MTP layer 3 component.
Check Prov will fail if this attribute does not specify a Gips IpAddr Udp Port
component.
Mib Ss7Mtp3
Default No default
Criticality Process
For the SS7 stack on the Iu interface this attribute must be set to mtp3b.
Changing the value of this attribute causes all the linksets associated with the
MTP3 layer to be restarted.
Mib Ss7Mtp3
Values mtp3
mtp3b
Default mtp3b
Criticality Process
Description This attribute specifies the point code of the node that the MTP3 layer manages.
basic: The point code is provisioned as a decimal number in the range 1..16383. A
value of 0 is not valid.
segmented: The point code is provisioned as three integers, separated by dots. The
first integer must be in the range 0..7, the second integer must be in the range
0..255, and the third integer must be in the range 0..7. A value of 0.0.0 is not
valid.
This attribute must not specify a point code identical to that specified by the
adjPointCode attribute (defined in the Mtp3/n Ls/n component) or the
destPointCode attribute (defined in the Mtp3/n Rs/n component).
Changing the value of this attribute causes all the linksets associated with this
MTP3 layer to be restarted.
Mib Ss7Mtp3
Default No default
Criticality Process
This attribute determines the value that is filled in the Network Indicator field of
the messages sent to the remote end.
This attribute must match what the peer MTP3 layer on the remote end expects in
the messages.
Changing the value of this attribute causes all the linksets associated with this
MTP3 layer to be restarted.
Each meaning of each valid value for networkIndicator is described in SS7 Mtp3
specification Q.704.
Mib Ss7Mtp3
Values international
internationalSpare
national
nationalSpare
Default international
Description This attribute specifies the value of the timer T1 defined in ITU-T
recommendation Q.704. This timer value determines how long to wait for a failed
link to become available when changeover is required, but there is no alternate
link. It is used to avoid message mis-sequencing on changeover.
This timer is started when a link goes down and a changeover is required, but
changeover messages cannot be exchanged on an alternate link.
Upon timer expiration, it sends all the retrieved (layer 2) and buffered (layer 3)
messages down the new link and marks changeover as complete.
Mib Ss7Mtp3
Units msec
Default 500
Description This attribute specifies the value of the timer T2 defined in ITU-T
recommendation Q.704.
This timer is started when MTP layer 3 receives a Backward Sequence Number of
the next signalling unit to be Transmitted (BSNT) from a link in the changeover
process.
This timer is stopped when the link becomes available, or when a changeover
message is received while waiting for an ack.
Mib Ss7Mtp3
Units msec
Default 700
Description This attribute specifies the timer value for the timer T3 defined in ITU-T
recommendation Q.704. It provides time controlled diversion-delay to avoid mis-
sequencing on changeback.
This timer is started when a link is in changeback and the signalling point at the
remote end of newly available link is not accessible via an alternative link.
Mib Ss7Mtp3
Units msec
Default 500
Description This attribute specifies the timer value for the timer T4 defined in ITU-T
recommendation Q.704.
This timer is started when a link is in changeback and the Signalling Point (SP) at
the remote end of the newly available link is accessible via an alternative link.
This timer is stopped when a link has attempted changeback for the first time and
receives a changeback ack for every changeback declaration sent.
Mib Ss7Mtp3
Units msec
Default 500
Description This attribute specifies the timer value for the timer T5 defined in ITU-T
recommendation Q.704. It creates a delay to avoid oscillation of initial alignment
failure and link restart.
The timer is started when a link does not changeback in the first attempt with
firstAttemptChangeBackAckTimer.
The timer is stopped when a link is in the second attempt of changeback and
receives a changeback ack for every changeback declaration sent.
Mib Ss7Mtp3
Units msec
Default 500
Description This attribute specifies the timer value for the timer T12 defined in ITU-T
recommendation Q.704.
The timer is stopped when the link uninhibit is acknowledged by the remote end.
Upon timer expiry, the uninhibit is started again for a maximum of one more time.
If it fails this time, the uninhibit is cancelled.
Mib Ss7Mtp3
Units msec
Default 800
Description This attribute specifies the timer value for the timer T13 defined in ITU-T
recommendation Q.704.
The timer is started when this end initiates a link force uninhibit.
Upon timer expiry, the uninhibit is started again one more time. If it fails this
time, the uninhibit is cancelled.
Mib Ss7Mtp3
Units msec
Default 800
Description This attribute specifies the value of the timer T14 defined in ITU-T
recommendation Q.704. This timer waits for inhibition acknowledgement.
The timer is stopped when the local link inhibit is denied or successful.
Mib Ss7Mtp3
Units seconds
Default 2
Description This attribute specifies the value of the timer T17 defined in ITU-T
recommendation Q.704. It creates a delay to avoid oscillation of initial alignment
failure and link restart.
Mib Ss7Mtp3
Units msec
Default 800
Description This attribute specifies the value of the timer T22 (Local inhibit test timer) defined
in ITU-T recommendation Q.704.
This timer is started when a link becomes locally inhibited. Upon timer expiry, if
the link is still unavailable and locally inhibited, the timer is restarted, and a local
inhibit test message is sent to the remote end.
Mib Ss7Mtp3
Units seconds
Default 180
Description This attribute specifies the value of the timer T23 (Remote inhibit test timer)
defined in ITU-T recommendation Q.704.
This timer is started when a link becomes remote inhibited. Upon timer expiry, if
the link is still unavailable and remotely inhibited, the timer is restarted, and a
remote inhibit test message is sent to the remote end
Mib Ss7Mtp3
Units seconds
Default 180
Description This attribute specifies the value of the Supervision timer to wait for a signalling
link test acknowledgement message.
This timer is started every time a Signalling Link Test Controller (SLTC) sends
out a test message.
The timer is stopped when the SLTC receives an acknowledge message from the
peer MTP3 layer.
Upon timer expiration, if this is the first attempt, this timer is restarted and a
second attempt is made. If the timer expires after the second attempt, the MTP3
layer is informed of a broken link.
Mib Ss7Mtp3
Units seconds
Default 4
Description This attribute specifies the value of the Interval timer defined in ITU-T
recommendation Q.707 for sending signalling link test messages.
The timer is started when a link comes in service, and each time the timer expires
if the link is still good.
The timer is stopped when the link fails, as determined by the sltAckTimer.
Upon timer expiry, another test message is sent to the peer and the timer is
restarted.
Mib Ss7Mtp3
Units seconds
Default 30
Description This attribute specifies the value for the timer T6 defined in ITU-T Q.704. This
timer introduces a delay to avoid mis-sequencing on controlled rerouting.
This timer is started when a signalling route toward a given destination becomes
available and the controlled rerouting procedure is invoked.
Mib Ss7Mtp3
Units msec
Default 800
Description This attribute specifies the value for the timer T10 defined in ITU-T Q.704.
The timer is stopped when the destination becomes accessible via the receipt of a
Transfer-Allowed (TFA) message.
Mib Ss7Mtp3
Units seconds
Default 30
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Ss7Mtp3
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Ss7Mtp3
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Ss7Mtp3
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Ss7Mtp3
Values idle
active (activ)
busy
Default idle
Mib Ss7Mtp3
Description This attribute counts the timeouts of timer T2, specified by the attribute
changeoverAckTimer.
Mib Ss7Mtp3
Default No default
Description This attribute counts the timeouts of timer T4, specified by the attribute
firstAttemptChangebackAckTimer.
Mib Ss7Mtp3
Default No default
Description This attribute counts the timeouts of timer T5, specified by the attribute
secondAttemptChangebackAckTimer.
Mib Ss7Mtp3
Default No default
Description This attribute counts the timeouts of timer T13, specified by the attribute
forceUninhibitAckTimer.
Mib Ss7Mtp3
Default No default
Description This group contains the spare counters that can be dynamically patched.
Mib Ss7Mtp3
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Scope Application
Mib Ss7Mtp3
This verb causes the specified Linkset component to immediately enter the OSI
locked administrative state. Traffic flow ceases on the newly locked Linkset and is
diverted to another Linkset within a Routeset. All the Link components
representing the links in the Linkset are disabled.
Mib Ss7Mtp3
Criticality Component
Description This attribute specifies the point code of the node that this node directly connects
to through this linkset.
basic: The point code is provisioned as a decimal number in the range 1..16383. A
value of 0 is not valid.
segmented: The point code is provisioned as three integers, separated by dots. The
first integer must be in the range 0..7, the second integer must be in the range
0..255, and the third integer must be in the range 0..7. A value of 0.0.0 is not
valid.
This attribute must not specify a point code identical to that specified by the
origPointCode attribute (defined in the Mtp3/n component) or the destPointCode
attribute (defined in the Mtp3/n Rs/n component).
Changing the value of this attribute causes all the linksets associated with the
MTP3 layer to be restarted.
Mib Ss7Mtp3
Default No default
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Ss7Mtp3
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Ss7Mtp3
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Ss7Mtp3
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Ss7Mtp3
Values idle
active (activ)
busy
Default idle
Description This group contains the spare counters that can be dynamically patched.
Mib Ss7Mtp3
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Scope Application
Mib Ss7Mtp3
This command requests that the signalling link represented by this component be
locally inhibited, as per the ITU-T recommendation Q.704.
The Inhibit will be denied locally if the requested link is the last available link in
the linkset, or if an uninhibit on the requested is in progress. The Inhibit can also
be denied by the remote end.
If the link is inhibited successfully, all the traffic carried on the linkset will be
distributed among the other links in the linkset.
This command requests that the signalling link represented by this component be
uninhibited, as per the ITU-T recommendation Q.704.
The Uninhibit will be denied locally if the requested link has not been inhibited
from this end, or if an inhibit on the link is in progress.
If the link is uninhibited successfully, the link will be made available for traffic.
This verb causes the specified Link component to immediately enter the OSI
locked administrative state. Traffic flow ceases on the newly locked Link and is
diverted to the remaining unlocked Links of the LinkSet.
The Lock command fails if executed on the last unlocked Link of a LinkSet. The
last unlocked Link of a LinkSet must be locked using the force option.
Options:
-force
If this option is specified, the Link is locked even if it is the only unlocked Link in
the LinkSet.
Mib Ss7Mtp3
Criticality Component
Description This attribute specifies the link layer entity that provides data link layer services
for this link. This attribute contains the name of a SaalNni/n component instance.
Changing the value specified by this attribute causes a loss of service for this
component.
Mib Ss7Mtp3
Default No default
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Ss7Mtp3
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Ss7Mtp3
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Ss7Mtp3
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Ss7Mtp3
Values idle
active (activ)
busy
Default idle
Mib Ss7Mtp3
Description This attribute counts the Protocol Data Units (PDUs) received from layer 2.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Protocol Data Units (PDUs) with payload received from
layer 2.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Protocol Data Units sent to layer 2.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Protocol Data Units (PDUs) with payload sent to layer 2.
Mib Ss7Mtp3
Default No default
Description This attribute counts the number of invalid Protocol Data Units received from
Layer 2.
Mib Ss7Mtp3
Default No default
Description This group contains the spare counters that can be dynamically patched.
Mib Ss7Mtp3
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute indicates the number of Protocol Data Units (PDUs) received from
layer 2 over the collection interval.
Description This attribute indicates the number of Protocol Data Units (PDUs) with payload
received from layer 2 over the collection interval.
Description This attribute indicates the number of Protocol Data Units (PDUs) sent to layer 2
over the collection interval.
Description This attribute indicates the number of Protocol Data Units (PDUs) with payload
sent to layer 2 over the collection interval.
Description This attribute indicates the number of number of invalid Protocol Data Units
received over the collection interval.
Description This attribute indicates the number of signalling link test message failure
conditions over the collection interval.
Description This attribute indicates the number of link changeover conditions over the
collection interval.
Scope Application
Mib Ss7Mtp3
Properties Operational
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Ss7Mtp3
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Ss7Mtp3
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Ss7Mtp3
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Ss7Mtp3
Values idle
active (activ)
busy
Default idle
Properties Operational
Mib Ss7Mtp3
Description This attribute counts the communication failures between the neighbors being
monitored.
monitoring communication could not be established and the value of this attribute
is incremented.
Mib Ss7Mtp3
Default No default
Description This attribute counts the payload messages sent to the neighbor but were not
received by the neighbor.
Mib Ss7Mtp3
Default No default
Description This attribute counts the payload messages that were sent by the neighbor but
were not received by this component. This is detected by a gap in the Message
Numbers received in payload messages from the neighbor.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Monitor Enable Request messages sent by this
component to the neighbor.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Monitor Enable Request messages received by this
component.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Monitor Enable Response messages sent by this
component.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Monitor Enable Response messages received by this
component in response to the Monitor Enable Request message.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Heartbeat messages sent by this component to the
neighbor.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Heartbeat messages received by this component.
The value of this attribute is incremented when the Heartbeat message is received.
Mib Ss7Mtp3
Default No default
Description This attribute counts the payload messages sent by this component to the
neighbor.
Mib Ss7Mtp3
Default No default
Description This attribute counts the payload messages received by this component.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Sequencing Gap messages sent by this component.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Sequencing Gap messages received by this component.
received from the neighbor is identified, a Sequence Gap message is sent. The
value of this attribute is incremented when this message is received. The Sequence
Gap message shows the start and end of the gap in the Messages Numbers.
Mib Ss7Mtp3
Default No default
Description This attribute counts the messages received by this component that are not
recognized by the MonitoredCommunicationProtocol (MCP).
Mib Ss7Mtp3
Default No default
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Mib Ss7Mtp3
Default No default
The value of the Heartbeat timer is negotiated between the monitored parent
components.
Mib Ss7Mtp3
Units msec
Default No default
Description This attribute indicates the number of time-outs of the Heartbeat timer allowed
before marking the communication with the neighbor as down.
The value of the Heartbeat retries is negotiated between the monitored parent
components.
Mib Ss7Mtp3
Default No default
timer expires and if the Monitor Enable Response message is not received prior to
the predetermined number of Heartbeat timer expiries, then it is assumed that
monitoring communication could not be established and the value of this attribute
is incremented.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
The value of this attribute is incremented when the Heartbeat message is received.
Description This attribute counts the payload messages sent by this component to the
neighbor.
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Scope Application
This component identifies a list of routes that are using this linkset to reach a
destination signalling point. One linkset can be used by more than one route.
Mib Ss7Mtp3
Description This group contains the provisionable attributes of the Ss7RouteInfo component.
Mib Ss7Mtp3
Criticality Component
Description This attribute specifies a list of links to routes that use this linkset to reach one of
several destination signalling points.
The attribute specifies the Mtp3/n Rs/n Route/n components associated with this
linkset.
Mib Ss7Mtp3
Default No default
Scope Application
The SS7 specifications define which users are required to use a given service
indicator.
Only one application can use a particular MTP layer 3 service indicator.
Mib Ss7Mtp3
Mib Ss7Mtp3
Description This attribute specifies a link to the application using the service represented by
this service indicator.
Mib Ss7Mtp3
Default No default
Description This group contains the spare counters that can be dynamically patched.
Mib Ss7Mtp3
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib Ss7Mtp3
Default No default
Scope Application
A routeset is a grouping of routes that are used to transfer signalling between this
node and a specific destination signalling point. Routes under this component
represent quasi-associated links (A-links).
Mib Ss7Mtp3
Description This group contains the provisionable attributes of the Ss7Routeset component.
Mib Ss7Mtp3
Criticality Component
Description This attribute specifies the point code of the destination node that is reached via
this routeset.
basic: The point code is provisioned as a decimal number in the range 1..16383. A
value of 0 is not valid.
segmented: The point code is provisioned as three integers, separated by dots. The
first integer must be in the range 0..7, the second integer must be in the range
0..255, and the third integer must be in the range 0..7. A value of 0.0.0 is not
valid.
This attribute must not specify a point code identical to that specified by the
origPointCode (defined in the Mtp3/n component) or the adjPointCode (defined
in the Mtp3/n Ls/n component).
Changing the value of this attribute causes this routeset and associated routes to
be restarted.
Mib Ss7Mtp3
Default No default
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Ss7Mtp3
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Ss7Mtp3
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Ss7Mtp3
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Ss7Mtp3
Values idle
active (activ)
busy
Default idle
Scope Application
This component represents a Message Transfer Part Layer 3 (MTP3) route that
conveys signalling information between two signalling points using a specific
adjacent signalling point.
Mib Ss7Mtp3
Description This group contains the provisionable attributes of the Ss7Route component.
Mib Ss7Mtp3
Criticality Component
Description This attribute specifies a link to the Mtp3/n Ls/n RInfo component representing a
route to an adjacent node. This linkset may be used to reach the destPointCode.
The value of the adjPointCode attribute (defined in the Mtp3/n Ls/n component)
must not be equal to the value of the destPointCode attribute (defined in the Mtp3/
n Rs/n component).
Changing the value of this attribute causes the old route to be removed and a new
route added to the routeset.
Mib Ss7Mtp3
Default No default
Criticality Component
Description This attribute specifies the route priority in relation to the other routes defined
under the routeset. If two routes are defined with equal priority then load sharing
Changing the value of this attribute causes the old route to be removed and a new
route added to the routeset.
Mib Ss7Mtp3
Default 1
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib Ss7Mtp3
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib Ss7Mtp3
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib Ss7Mtp3
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib Ss7Mtp3
Values idle
active (activ)
busy
Default idle
Description This group contains the operational data for the Ss7Route component.
Mib Ss7Mtp3
Description This attribute counts the Transfer-Prohibited (TFP) messages received for this
route.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Transfer-Allowed (TFA) messages received for this
route.
Mib Ss7Mtp3
Default No default
Description This attribute counts the Signalling-Route-Set-Test (SRST) messages sent to this
route while prohibited from use. The sending of the SRST message is controlled
by the T10 timer specified by the routeSetTestRepeatTimer attribute (defined in
the Mtp3 component).
Mib Ss7Mtp3
Default No default
Description This attribute indicates the amount of time the route has been unavailable due a
transfer-prohibited condition.
Mib Ss7Mtp3
Units msec
Default No default
Description This attribute counts the Transfer-Prohibited (TFP) messages received for this
route.
Description This attribute counts the Transfer-Allowed (TFA) messages received for this
route.
Description This attribute counts the Signalling-Route-Set-Test (SRST) messages sent to this
route while prohibited from use. The sending of the SRST message is controlled
by the T10 timer specified by the routeSetTestRepeatTimer attribute (defined in
the Mtp3 component).
Scope Application
Description SaalNni/n
This component represents the SAAL-NNI layer that provides an adaptation layer
to run signalling traffic over ATM using AAL5.
Mib SaalNni
Mib SaalNni
Criticality Process
Description This attribute specifies a link to Gips IpAddr UDP Port component on an IP
Server. This determines the Ip Address and UDP port that the SAAL NNI user
uses to address the SaalNni component.
Mib SaalNni
Default No default
Criticality Process
Description This attribute specifies a link to the SAAL-NNI user. It may specify either an
Mtp3/n Ls/n Link/n component or an Nsta/n Vgs M2ua As/n Iid/iid component.
Mib SaalNni
Default No default
Description This attribute specifies a list of components started on the same hardware as this
Saal instance. The specified components are started on all Lp instances with
which this Saal instance is associated via the atmConnection attribute of its Nap
subcomponent.
At this time, this attribute is used to specify the Gips component that will serve
this Saal instance. In the future up to 10 components can be linked to a Saal
instance and thereby started on its hardware.
Mib SaalNni
List of Link
List Size 10
Default No default
Description This group contains the provisionable attributes needed by the SSCOP sub-layer
of SAAL-NNI.
Mib SaalNni
Description This attribute specifies the maximum number of Signalling Data PDUs that can be
sent without sending a POLL PDU, as defined in ITU-T recommendation Q.2110.
Mib SaalNni
Default 500
Description This attribute specifies the time between transmissions of BGN, END, RS
and ER PDUs, as defined in ITU-T recommendation Q.2110.
Upon timer expiry the PDU will be retransmitted. The PDU is transmitted a
maximum of maxCc times.
If the timer expires maxCc times, the link will be released, and the and the number
of times this happens will be indicated by the attribute maxCcReached.
Mib SaalNni
Units msec
Default 200
If the number of unacknowledged transmissions exceeds this value, the link will
be released, and the number of times this happens will be indicated by the
attribute maxCcReached.
Mib SaalNni
Default 4
Description This attribute specifies the time between sending of POLL PDUs when there is no
activity on the link, as defined in ITU-T recommendation Q.2110.
The timer is started when either the pollTimer or the keepAliveTimer expires and
there are no PDUs queued for sending.
The timer is stopped when a data request (SD PDU) is ready to be sent.
The value of keepAliveTimer should be set to a value greater that pollTimer and
greater than the round-trip delay of a PDU.
Mib SaalNni
Units msec
Default 100
Description This attribute specifies the time interval during which at least one STAT PDU
should be received.
Upon timer expiry, the link is released, that is, brought out of service. Layer 3 will
then attempt to bring it back to service.
The value of the noResponseTimer must not be less than the sum of the
keepAliveTimer and one round-trip delay of a Protocol Data Unit (PDU).
Mib SaalNni
Units msec
Default 1500
Description This attribute specifies the time between sending of POLL PDUs when the link
has traffic, as defined in ITU-T recommendation Q.2110.
The timer is started when the link enters the Data Transfer Ready State.
Upon expiry, a POLL PDU is sent and pollTimer is restarted if the link has traffic.
Mib SaalNni
Units msec
Default 100
Description This attribute specifies the idle time after receipt of a STAT PDU, as defined in
ITU-T recommendation Q.2110.
The value of the idleTimer must be greater that the sum of the pollTimer and the
maximum round trip delay of a PDU.
Mib SaalNni
Units msec
Default 100
Description This group contains provisionable attributes needed by the SSCF sub layer of
SAAL-NNI.
Mib SaalNni
Description This attribute allows the operator to place the link into one of the link proving
modes defined in ITU-T recommendation Q.2140.
When this attribute is set to neutral, the layer that uses SAAL_NNI (MTP3)
selects the proving mode, but when the attribute is set to normal or emergency,
instructions from the entity which uses SAAL-NNI are ignored.
Mib SaalNni
Values normal
neutral
emergency
Default neutral
Description This attributes specifies the time between the link release action and the next link
re-establish action during alignment, as defined in ITU-T recommendation
Q.2140.
Mib SaalNni
Units seconds
Default 5
Description This attributes specifies the total time to attempt alignment and is defined in ITU-
T recommendation Q.2140.
This timer is started when a start request is received. If the link is put in service
before the expiry of this timer, no action is performed.
If the SAAL-NNI layer receives a stop indication from the layer 3, or a release
request from layer management.
Upon timer expiration, link establishment is cancelled and link is taken out of
service. Layer 3 will attempt to bring the link back in service.
The value of this timer can be adjusted if link proving fails due to an inability to
send the target number proving PDUs indicated by the attribute
targetProvingPdus. The current number of proving PDUs sent successfully is
indicated by the attribute currentProvingPdus.
Mib SaalNni
Units seconds
Default 30
Description This attribute specifies the time interval between the sending of protocol data
units (PDUs) from one SAAL-NNI layer to another SAAL-NNI layer during the
connection establishment proving stage. The value of the provingPduTimer
attribute is used only when one of the following conditions is true:
The value of the provingPduTimer attribute should be selected such that the total
time for the connection establishment proving stage (provingPduTimer *
provingPduCount) is less than the value of the alignmentAcceptTimer attribute.
Mib SaalNni
Units msec
Default 10
Description This attribute specifies the target number of protocol data units (PDUs) to be sent
from one SAAL-NNI layer to another SAAL-NNI layer during the connection
establishment proving stage. The value of the provingPduCount attribute is used
only when one of the following conditions is true:
The value of the provingPduCount attribute should be selected such that the total
time for the connection establishment proving stage (provingPduTimer *
provingPduCount) is less than the value of the alignmentAcceptTimer attribute.
Mib SaalNni
Default 1000
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib SaalNni
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib SaalNni
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib SaalNni
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib SaalNni
Values idle
active (activ)
busy
Default idle
Mib SaalNni
Description This attribute indicates the proving state of the link. The different states are:
notStarted - Proving has not started.
incomplete - Proving is in progress, but not completed yet.
completeSuccess - Proving has been completed successfully.
completeFailed - This proving attempt failed.
Mib SaalNni
Values notStarted
inComplete
completeSuccess
completeFailed
Default No default
Description This attribute indicates the target number of proving PDUs to be sent across the
link during the proving period.
The current number of proving PDUs that have been sent is indicated by the
attribute currentProvingPdus.
Mib SaalNni
Default No default
Description This attribute indicates the number of proving PDUs that are yet to be sent across
the link during this proving period.
The target number of proving PDUs that must be sent is indicated by the attribute
targetProvingPdus.
Mib SaalNni
Default No default
Description This attribute counts the number of times the signalling link has been released
because the number of unacknowledeged transmissions of BGN, END, ER or
RS Protocol Data Units (PDUs) has exceeded the value provisioned in the
attribute maxCc.
Mib SaalNni
Default No default
Description This attribute counts the expiries of the No Response timer, specified by the
attribute noResponseTimer.
Mib SaalNni
Default No default
Mib SaalNni
Default No default
Mib SaalNni
Default No default
Mib SaalNni
Default No default
Description This attribute counts the payload PDU octets received over the collection interval.
Mib SaalNni
Default No default
Description This attribute counts the in-service link outages. It does not include failures which
occur during the alignment process.
Mib SaalNni
Default No default
Description This group contains the spare counters that can be dynamically patched.
Mib SaalNni
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib SaalNni
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib SaalNni
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib SaalNni
Default No default
Scope Application
Mib SaalNni
Mib SaalNni
Criticality Process
Description This attribute specifies a link to an AtmIf Vcc Nep component which provides
access to an ATM network. The SaalNni process is started on the Lp or Lp pair
associated with the AtmIf that is the parent of the specified Nep component.
Mib SaalNni
Default No default
Description This group contains the spare counters that can be dynamically patched.
Mib SaalNni
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib SaalNni
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib SaalNni
Default No default
Description This attribute does not count anything and is not displayed under normal operating
circumstances. It is included here to provide a mechanism by which custom
counters can be set up at runtime through a patch.
Mib SaalNni
Default No default
Scope Application
Mib SaalNni
Description This group contains the three OSI State attributes. The descriptions generically
indicate what each state attribute implies about the component. Note that not all
the values and state combinations described here are supported by every
component which reuses this group. For component-specific information and the
valid state combinations, refer to the appropriate NTP.
Mib SaalNni
Description This attribute indicates the OSI Administrative State of the component.
The value locked indicates that the component is administratively prohibited from
providing services for its users. A Lock -force or Lock command has been
previously issued for this component. When the value is locked, the value of
usageState must be idle.
Mib SaalNni
Default unlocked
Description This attribute indicates the OSI Operational State of the component.
The value enabled indicates that the component is available for operation. Note
that if adminState is locked, it would still not be providing service.
The value disabled indicates that the component is not available for operation. For
example, something is wrong with the component itself, or with another
component on which this one depends. If the value is disabled, the usageState
must be idle.
Mib SaalNni
Default disabled
Description This attribute indicates the OSI Usage State of the component.
The value idle indicates that the component is not currently in use.
The value active indicates that the component is in use and has spare capacity to
provide for additional users.
The value busy indicates that the component is in use and has no spare operating
capacity for additional users at this time.
Mib SaalNni
Values idle
active (activ)
busy
Default idle
Mib SaalNni
Description This attribute counts the communication failures between the neighbors being
monitored.
Mib SaalNni
Default No default
Description This attribute counts the payload messages sent to the neighbor but were not
received by the neighbor.
Mib SaalNni
Default No default
Description This attribute counts the payload messages that were sent by the neighbor but
were not received by this component. This is detected by a gap in the Message
Numbers received in payload messages from the neighbor.
Mib SaalNni
Default No default
Description This attribute counts the Monitor Enable Request messages sent by this
component to the neighbor.
Mib SaalNni
Default No default
Description This attribute counts the Monitor Enable Request messages received by this
component.
Mib SaalNni
Default No default
Description This attribute counts the Monitor Enable Response messages sent by this
component.
Mib SaalNni
Default No default
Description This attribute counts the Monitor Enable Response messages received by this
component in response to the Monitor Enable Request message.
Mib SaalNni
Default No default
Description This attribute counts the Heartbeat messages sent by this component to the
neighbor.
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
Mib SaalNni
Default No default
Description This attribute counts the Heartbeat messages received by this component.
The value of this attribute is incremented when the Heartbeat message is received.
Mib SaalNni
Default No default
Description This attribute counts the payload messages sent by this component to the
neighbor.
Mib SaalNni
Default No default
Description This attribute counts the payload messages received by this component.
Mib SaalNni
Default No default
Description This attribute counts the Sequencing Gap messages sent by this component.
Mib SaalNni
Default No default
Description This attribute counts the Sequencing Gap messages received by this component.
Mib SaalNni
Default No default
Description This attribute counts the messages received by this component that are not
recognized by the MonitoredCommunicationProtocol (MCP).
Mib SaalNni
Default No default
Description This attribute counts the messages that were discarded to avoid overflowing of the
neighbor.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
Mib SaalNni
Default No default
The value of the Heartbeat timer is negotiated between the monitored parent
components.
Mib SaalNni
Units msec
Default No default
Description This attribute indicates the number of time-outs of the Heartbeat timer allowed
before marking the communication with the neighbor as down.
The value of the Heartbeat retries is negotiated between the monitored parent
components.
Mib SaalNni
Default No default
If no messages are sent by this component for the duration of the heartbeat timer,
then a Heartbeat message is sent to the neighbor and the value of this attribute is
incremented. The heartbeat timer is not provisionable and is set by the neighbors
being monitored.
The value of this attribute is incremented when the Heartbeat message is received.
The number of messages that the neighbor can handle without overflowing is
identified from the Available Capacity field in the messages received from the
neighbor.
If the value of the Available Capacity field is zero, payload messages to be sent to
the neighbor are discarded and the value of this counter is incremented.
GSM / UMTS
R4 Media Gateway
OAM and Troubleshooting Guide
Nortel CONFIDENTIAL
The information contained herein is the property of Nortel and is strictly confidential. Except as expressly authorized in writing by
Nortel, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to
know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it
uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by
Nortel, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress in
engineering and manufacturing may warrant.
* Nortel, the Nortel logo, the Globemark HOW the WORLD SHARES IDEAS, and Unified Networks are trademarks of Nortel.
DMS, DMS-HLR, DMS-MSC, MAP, and SuperNode are trademarks of Nortel. GSM is a trademark of GSM MOU Association.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Document number: 411-2231-331
Product release: MGW18
Document version: Standard 02.06
Date: May 2006
Originated in the United States of America