Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download PacketStar PSAX Simple Network Management Protocol (SNMP
Document related concepts
Transcript
PacketStar®
PSAX Simple Network
Management Protocol (SNMP)
Trap Reference Guide
Release 9.0.0
for PacketStar® PSAX Multiservice Media Gateways
Issue 1, October 2003
Doc. No.: 255-700-506
Copyright © 2003 by Lucent Technologies. All rights reserved.
For trademark, regulatory compliance, and related legal information, see
the “Copyright and Legal Notices” section.
Copyright and Legal Notices
Copyright
Copyright © 2003 by Lucent Technologies. All rights reserved.
This material is protected by the copyright laws of the United States and
other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except
in accordance with applicable agreements, contracts or licensing, without the
express written consent of the originating organization and the business
management owner of the material.
This document was prepared by the Information Design and Development
Team of Lucent Technologies, PacketStar PSAX products. Offices are located in
Landover, Maryland, USA.
Trademarks
PacketStar, AQueView, Lucent, Lucent Technologies, and the Lucent Technologies logo are registered trademarks of Lucent Technologies in the USA. Other
product and brand names mentioned in this guide are trademarks or registered trademarks of their respective owners. PacketStar, AQueView, Lucent,
Lucent Technologies, and the Lucent Technologies logo are registered trademarks of Lucent Technologies in the USA. Other product and brand names
mentioned in this guide are trademarks or registered trademarks of their
respective owners.
Notices
The information in this document is for informational use only, is subject to
change without notice, and should not be construed as a commitment by
Lucent Technologies, Inc. This document is without warranty of any kind,
either expressed or implied. Lucent Technologies, Inc. assumes no responsibility for any errors, inaccuracies, or omissions. Neither is any liability
assumed for damages resulting from the use of the information or instructions contained herein. Lucent Technologies, Inc. is not responsible for any
damage or loss to your data or equipment resulting either directly or indirectly from use of this document.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
iii
Copyright and Legal Notices
Notices
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
iv
255-700-506
Contents
Copyright and Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
iii
Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-iii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-iii
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-iii
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Purpose of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
PSAX System MIB Version Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
2
Obtaining PSAX SNMP Trap Log Information . . . . . . . . . . . . . . . . . . . . . 2-1
Purpose of this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Description of the PSAX SNMP Trap Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Trap Group ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
System Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Viewing the PSAX SNMP Trap Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Obtaining Trap Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Viewing Trap Message Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Using this Guide for Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
3
Trap Message Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Purpose of this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1
Trap Names and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1
4
MIB Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Purpose of this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1
MIB Object Detailed Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
v
Contents
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
vi
255-700-506
1
Introduction
Purpose of this Document
This document describes the SNMP trap messages and notifications generated
by the PSAX system SNMP agent. Also provided for each of these trap messages are the associated MIB objects for PacketStar® PSAX Multiservice Media
Gateways, Release 9.0.0. In addition, possible causes and corrective actions
are given where that information was available at the time of publication.
Through monitoring trap databases and trap log information, this troubleshooting information is continually updated and improved to provide the
most current and accurate information available.
Document Organization
This guide is organized as follows:
• Section 1 provides an overview of the contents of this document.
• Section 2 provides basic information about the trap log and gives instructions on how to use this guide.
• Section 3 provides descriptions and other characteristics for SNMP traps
generated by the PSAX system. Traps are listed in alphabetical order by trap
name.
• Section 4 provides descriptions for the MIB objects and enumerated types
that are associated with all PSAX system generated traps. MIB objects are
listed in alphabetical order.
PSAX System MIB Version Support
PSAX Multiservice Media Gateways support versions SNMPv1, SNMPv2c,
and SNMPv3 of the Simple Network Management Protocol.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
1-1
Chapter 1 Introduction
PSAX System MIB Version Support
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
1-2
255-700-506
2
Obtaining PSAX SNMP Trap Log
Information
Purpose of this Chapter
This chapter describes the PSAX SNMP Trap Log and how to obtain Trap Log
information using the PSAX system. Instructions on how to view the Trap
Log and extract details about specific PSAX events along with detailed
descriptions of field values and commands are provided via field description
tables and command description tables. Instructions on how to use this guide
for help are also included at the end of this chapter.
Description of the PSAX SNMP Trap Log File
All trap messages generated by the PSAX system are stored in the Trap Log.
The size allocated to the trap log is 128 KB. It can hold approximately 2,080
trap messages. When the trap log has reached its maximum capacity, the
PSAX system will discard previously generated trap messages on a FIFO (first
in, first out) basis to make room for the most recently generated messages.
Trap Group ID
Trap group IDs are assigned to each trap message to identify which specific
component caused the event to occur; the PSAX system, a module, the interface, or a connection. The Trap Group ID and Trap Index Number column of
Table 3-1 indicates whether the event is associated with the PSAX system, a
module, the interface, or a connection. The six event groups, defined in
Table 2-1, are: system event, module event, interface event, connection
event, profile event, and ATM security event.
Table 2-1. Definitions of Trap Group IDs
Trap Group ID
(Column 2 in Table 3-1)
Definition
System Event
A trap group identification indicating that the PSAX system caused
that specific trap message to occur.
Module Event
A trap group identification indicating that a module caused that
specific trap message to occur.
Interface Event
A trap group identification indicating that the interface caused that
specific trap message to occur.
Connection Event
The trap group identification indicating that a connection caused
that specific trap message to occur.
Profile Event
A trap group identification indicating that a profile issue caused
that specific trap message to occur.
ATM Security Event
The trap group identification indicating that an ATM security
related issue caused that specific trap message to occur.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
2-1
Chapter 2 Obtaining PSAX SNMP Trap Log Information
System Indicators
System Indicators
Trap messages are assigned system indicators to signify the severity level of
each trap message. The System Indicator column of Table 3-1 indicates the
severity level of each trap. The five severity levels, defined in Table 2-2, are:
response, information, minor problem, major problem, and critical problem.
Table 2-2. System Indicators for SNMP Trap Messages
System Indicator for the Trap
(Column 3 in Table 3-1)
Definition
System Response
A system-supplied reply to a command a user enters, usually indicating the success or failure of a requested action.
System Information
A system-supplied informational message indicating the completion of a particular process (for example, a maintenance function).
Minor Problem
A notification of a problem that does not affect service or function
of a component of the PSAX system (for example, the failure of a
redundant power supply module).
Major Problem
A notification of a problem that affects service or function of a
component of the PSAX system (for example, failure of a PSAX I/O
module).
Critical Problem
A notification of a problem that affects functioning of the entire
PSAX system (for example, failure of a nonredundant Stratum 3–4
module). Critical problem notifications indicate that all traffic flow
through the system has ceased.
Viewing the PSAX SNMP Trap Log
To access the Trap Log Display window on which you can view the PSAX system SNMP trap messages, perform the steps in the following procedure.
Begin
1 Log onto the PSAX system console session, as described in any PSAX
Multiservice Media Gateway user guide.
2 On the Console Interface Main Menu window (see Figure 2-1), select the
Trap Log Display option.
The Trap Log Display window is displayed (see Figure 2-2). Descriptions
of the commands and fields on this window are provided in Table 2-3
and Table 2-4, respectively.
3 On the Trap Log Display window (see Figure 2-2), view the SNMP trap
messages currently in the PSAX system.
4 Use the PageUp, PageDown, Top, Bottom, and Find commands to
navigate throughout the entire SNMP trap log.
End
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
2-2
255-700-506
Chapter 2 Obtaining PSAX SNMP Trap Log Information
Viewing the PSAX SNMP Trap Log
Figure 2-1. Console Interface Main Menu Window
Figure 2-2. Trap Log Display Window
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
2-3
Chapter 2 Obtaining PSAX SNMP Trap Log Information
Viewing the PSAX SNMP Trap Log
Table 2-3. Commands for the Trap Log Display Window
Command
Function
PgUp
Displays the previous page in the trap log.
PgDown
Displays the next page in the trap log.
Top
Displays the beginning page in the trap
log.
Note: Trap message entries are displayed
in descending order by the log entry
number.
Bottom
Displays the last page in the trap log.
Note: Trap message entries are displayed
in descending order by the log entry
number.
Trap Help
Find . . . “
Displays the Trap Log Diagnostics window
on which you can view the entire text of
the help for one or more trap messages.
“
Searches the trap log with a text string
you enter between the quotation marks.
To find another instance of the same string
(repeat find), press Enter two times.
Go Back to Main Menu
Redisplays the Console Interface Main
Menu window.
Table 2-4. Field Descriptions for the Trap Log Display Window
Field Name
Field Values
Description
Msg Range From:
Default: N/A
Range: Depends on
the number of trap
entries in the table
Format: Numeric
Specifies the lower number of the trap log entry
for which you want to display trap message help.
To display help for several trap messages, enter
the lower log entry number in the Msg Range
From: field and the higher log entry number in
the Msg Range To: field. To display help for just
one trap message, enter the same log entry number in both the Msg Range From: and the Msg
Range To: fields.
Msg Range To:
Default: N/A
Range: Depends on
the number of trap
entries in the table
Format: Numeric
Specifies the higher number of the trap log entry
for which you want to display trap message help.
Trap Message Display Area
Default: N/A
Range: Depends on
the number of trap
entries in the table
Format: alphanumeric
Displays the system assigned trap number, the
trap message description, the date and time the
trap message was written to the file, and the values of any MIB objects that are associated with
the trap message.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
2-4
255-700-506
Chapter 2 Obtaining PSAX SNMP Trap Log Information
Obtaining Trap Message Details
Obtaining Trap Message Details
To obtain additional details and help on trap messages:
• You can view trap message help on the Trap Log Diagnostics window (see
the section, “Viewing Trap Message Help”) or
• You can view the trap message information in Chapter 3 (see the section,
“Using this Guide for Help”).
Viewing Trap Message Help
You can view the help for one or more SNMP trap messages on the Trap Log
Diagnostics window. Perform the steps in the following procedure to view
the help information for a trap message.
Begin
1 On the Trap Log Display window, perform one of the following steps:
a To display help for several trap messages, enter the lower log entry
number in the Msg Range From: field and the higher log entry number in the Msg Range To: field, and select the Trap Help command.
b To display help for just one trap message, enter the same log entry
number in both the Msg Range From: and the Msg Range To: fields,
and select the Trap Help command.
The Trap Log Diagnostics window is displayed (see Figure 2-3). Descriptions of the commands on the Trap Log Diagnostics window are provided
in Table 2-5.
At the top of this window, a message, You Requested Help Message x
through x, is displayed to indicate the range of trap log entry numbers
you specified on the Trap Log Display window.
2 Use the PageUp, PageDown, Top, Bottom, Next Message, and Previous Message commands to navigate the trap help information for the
messages you specified.
3 To return to the Trap Log Display window, press Ctrl + B.
End
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
2-5
Chapter 2 Obtaining PSAX SNMP Trap Log Information
Obtaining Trap Message Details
Figure 2-3. Trap Log Diagnostics Window
Table 2-5. Commands for the Trap Log Diagnostics Window
Command
Function
PgUp
Displays the previous page of the trap
message help.
PgDown
Displays the next page of the trap message
help.
Top
Displays the beginning page of the trap
message help.
Note: Trap message help is displayed in
descending order by the log entry
number.
Bottom
Displays the last page of the trap message
help.
Note: Trap message help is displayed in
descending order by the log entry
number.
Next Message
Displays the help text for the next trap
message in the range selected, at the top
of the display window.
Previous Message
Displays the help text for the previous trap
message in the range selected, at the top
of the display window.
Go Back to Trap Log Display Redisplays the Trap Log Display window.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
2-6
255-700-506
Chapter 2 Obtaining PSAX SNMP Trap Log Information
Obtaining Trap Message Details
Using this Guide for Help
To find a description of a trap message in this guide, perform the steps in the
following procedure.
Begin
1 In Chapter 3, Table 3-1, find the trap message for which you want information.
Trap messages are presented in alphabetical order. For example, you
might want information about the trap message, cardInsertionNotify.
The entry for this message contains the following information:
• The type of event that caused the message (see Table 2-1 for a list and
definitions of these indicators.)
• The system indicator for the trap message (see Table 2-2 for a list and
definitions of these indicators.)
• The MIB objects associated with the trap message
• A description of the trap message indicating the event that occurred to
cause the generation of the trap message.
2 To find out more information about any MIB objects associated with a
trap message, find the object in Chapter 4.
The list of all MIB objects used in the SNMP trap messages is presented in
alphabetical order. Following each MIB object is a list of all trap messages
and enumerated types that are associated with that specific object. The
description of the object includes the type of information the object conveys. If the object has enumerated types, the integer values and definitions of those enumerated types are also listed. For example, the trap
message, cardInsertionNotify, has four associated MIB objects,
cardSlot, cardType, cardProtectionStatus, and cardOperStatus,
which are all enumerated-type objects.
End
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
2-7
Chapter 2 Obtaining PSAX SNMP Trap Log Information
Obtaining Trap Message Details
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
2-8
255-700-506
3
Trap Message Descriptions
Purpose of this Chapter
This chapter describes the SNMP trap notification messages generated by the
PSAX system SNMP agent.
Trap Names and Descriptions
Table 3-1 lists the SNMP trap names, trap group and index numbers, system
indicators, corresponding MIB object names, and descriptions for all SNMP
traps associated with the PSAX Multiservice Media Gateways system software Release 9.0.0. All available possible causes and corrective actions for the
console interface are also provided for these trap messages. For descriptions
of each MIB object associated with the trap names, see Chapter 4.
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
aal2CirAtmSpvcD Interface
Information
eletedNotify
Event, 129
aal2CirAtmSpvcVccIfA
The specified CE-to-ATM
AAL2 SPVC connection configuration has been deleted.
aal2CirAtmSpvcV Interface
Information
ccConfigFailNoEvent, 128
tify
aal2CirAtmSpvcVccIfA, An attempt to configure the
aal2SpvcConfigFailureC specified CE-to-ATM AAL2
ode
SPVC connection has failed.
aal2CirAtmSpvcV Interface
Information
ccConfiguredNo- Event, 127
tify
aal2CirAtmSpvcVccIfA
The specified CE-to-ATM
AAL2 SPVC connection has
been created.
aal2CirAtmSpvcV ConnecResponse
ccSetUpNotify
tion Event,
88
aal2CirAtmSpvcVccIfA
The specified CE-to-ATM
AAL2 SPVC connection has
been successfully established.
Response
aal2CirAtmSpvcV ConnecccTearDownNotion Event,
tify
89
aal2CirAtmSpvcVccIfA
The specified CE-to-ATM
AAL2 SPVC connection has
been torn down.
Response
aal2TrunkConfigR ConneceqFailNotify
tion Event,
75
aal2TrunkConfigIf,
aal2TrunkConfigVpi,
aal2TrunkConfigVci,
pvcFailureReasonCode
The specified PVC VCC
AAL2 trunk could not be set
up.
aal2TrunkConfigS ConnecResponse
etupNotify
tion Event,
74
aal2TrunkConfigIf,
aal2TrunkConfigVpi,
aal2TrunkConfigVci
The specified PVC VCC connection for the specified
AAL2 trunk was successfully
set up.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-1
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
aal2TrunkConfigT ConnecResponse
earDownNotify
tion Event,
73
aal2TrunkConfigIf,
aal2TrunkConfigVpi,
aal2TrunkConfigVci
The specified PVC VCC
AAL2 trunk has been
deleted.
aal2VbrAtmSpvc
DeletedNotify
Interface
Information
Event, 132
aal2VbrAtmSpvcVccIfA The specified VBR-to-ATM
AAL2 SPVC connection has
been deleted.
aal2VbrAtmSpvcV Interface
Information
ccConfigFailNoEvent, 131
tify
aal2VbrAtmSpvcVccIfA, An attempt to configure the
aal2SpvcConfigFailureC specified VBR-to-ATM AAL2
ode
SPVC connection has failed.
aal2VbrAtmSpvcV Interface
Information
ccConfiguredNo- Event, 130
tify
aal2VbrAtmSpvcVccIfA The specified VBR-to-ATM
AAL2 SPVC connection has
been created.
aal2VbrAtmSpvcV ConnecResponse
ccSetUpNotify
tion Event,
90
aal2VbrAtmSpvcVccIfA The specified VBR-to-ATM
AAL2 SPVC connection has
been successfully established.
Response
aal2VbrAtmSpvcV Connection Event,
ccTearDownNotify
91
aal2VbrAtmSpvcVccIfA The specified VBR-to-ATM
AAL2 SPVC connection has
been deleted.
alarmCardAcoChangeNotify
System
Event, 29
Information
alarmCardReasonCode
alarmCardInputChangeNotify
System
Event, 26
Information
alarmCardReasonCode, The input status (1–15)
deviceId
identified by the deviceId
MIB object changed state.
The new state is indicated by
the alarmCardReasonCode
MIB object.
alarmCardOutputChangeNotify
System
Event, 28
Information
alarmCardReasonCode, The output control (1–4)
deviceId
that is identified by the deviceId MIB object changed
state. The new state is indicated by the alarmCardReasonCode MIB object.
Either the Alarm module
ACO switch has been pressed
or the state of the remote
ACO device has been
changed as indicated in the
alarmCardReasonCode MIB
object.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-2
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
ambientTempera- System
tureChangeNotify Event, 52
System
Indicator
Information
MIB Object Name
ambientTemperature
Trap Description
The ambient temperature
has changed by 5 degrees
Celsius since the last trap
message.
Possible Cause: The ambient temperature of the room in which the PSAX system is housed has changed by 5 degrees Celsius since the last time this trap message was generated.
Corrective Action: 1) No action is required if the change in room temperature is
acceptable to the customer. In this case the trap message may be suppressed using
the trap Activation/Deactivation feature. 2) Check the heating and air conditioning in the room. 3) Reorient air vents to blow away from the PSAX system. 4)
Check for a clogged air filter.
apsConfiguration- Interface
ModifyFailNotify Event, 53
Information
OcxPortId, apsFailureReasonCode
An attempt to modify the
specified APS configuration
has failed.
Information
atafConvertNotify Connection Event,
93
atafIf, atafVpi, atafVci,
atafDir, pvcFailureReasonCode
The status of attempting to
monitor a connection or to
discontinue monitoring a
connection.
atmAtmSpvcCon- Interface
figFailNotify
Event, 66
Information
spvcAddrIfA, atmAtm- An attempt to configure an
SpvcVccVpiA, atmAtm- endpoint as an ATM SPVC
SpvcVccVciA, atmAtm- endpoint has failed.
SpvcVccRemoteAtmPor
tAddr, spvcConfigFailureCode
atmAtmSpvcCon- Interface
figuredNotify
Event, 65
Information
spvcAddrIfA, atmAtm- The endpoint has been conSpvcVccVpiA, atmAtm- figured as an ATM SPVC
SpvcVccVciA, atmAtm- endpoint.
SpvcVccRemoteAtmPor
tAddr
atmAtmSpvcDeletedNotify
Interface
Event, 67
Information
spvcAddrIfA, atmAtm- The specified ATM SPVC
SpvcVccVpiA, atmAtm- configuration has been
SpvcVccVciA, atmAtm- deleted.
SpvcVccRemoteAtmPor
tAddr
atmAtmSpvcTfcParamModifyInProgressNotify
Interface
Information
Event, 240
spvcAddrIfA, atmAtm- An attempt to modify an
SpvcVccVpiA, atmAtm- SPVC VCC traffic parameter
SpvcVccVciA, atmAtm- is in progress.
SpvcVccRemoteAtmPor
tAddr
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-3
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
atmAtmSpvcTfc- Interface
Information
ParamModifyFail- Event, 242
Notify
spvcAddrIfA, atmAtm- An attemp to modify an
SpvcVccVpiA, atmAtm- SPVC VCC traffic parameter
SpvcVccVciA, atmAtm- has failed.
SpvcVccRemoteAtmPor
tAddr
atmAtmSpvcTfc- Interface
Information
ParamModifyNo- Event, 241
tify
spvcAddrIfA, atmAtm- An SPVC VCC traffic paramSpvcVccVpiA, atmAtm- eter has been sucessfully
SpvcVccVciA, atmAtm- modified.
SpvcVccRemoteAtmPor
tAddr
atmAtmInterface
SpvcVccSetUpNo- Event, 67
tify
Information
spvcAddrIfA, atmAtmSpvcVccVpiA, atmAtmSpvcVccVciA, atmAtmSpvcVccRemoteAtmPor
tAddr, atmAtmSpvcVccIfB, atmAtmSpvcVccVpiB, atmAtmSpvcVccVciB
The specified SPVC connection between ATM and ATM
endpoints was successfully
established.
atmAtmSpvcVcc- Interface
TearDownNotify Event, 68
Information
spvcAddrIfA, atmAtmSpvcVccVpiA, atmAtmSpvcVccVciA, atmAtmSpvcVccRemoteAtmPor
tAddr, atmAtmSpvcVccIfB, atmAtmSpvcVccVpiB, atmAtmSpvcVccVciB
The specified SPVC connection between ATM and ATM
endpoints has been torn
down.
atmAtmSpvcVpc- ConnecResponse
SetUpNotify
tion Event,
80
spvcAddrIfA, atmAtmSpvcVpcVpiA, atmAtmSpvcVpcRemoteAtmPortAddr,
atmAtmSpvcVpcIfB,
atmAtmSpvcVccVpiB
The specified SPVP connection between ATM and ATM
endpoints has been successfully established.
atmAtmSpvcVpc- ConnecResponse
TearDownNotify tion Event,
81
spvcAddrIfA, atmAtmSpvcVccVpiA, atmAtmSpvcVpcRemoteAtmPortAddr,
atmAtmSpvcVpcIfB,
atmAtmSpvcVpcVpiB
The specified SPVP connection between ATM and ATM
endpoints has been torn
down.
atmAtmSpvpCon- Interface
Information
figuredNotify
Event, 105
spvcAddrIfA, atmAtm- The specified ATM SPVP has
SpvcVpcVpiA, atmAtm- been configured at the ATM
SpvcVpcRemoteAtmSPVC endpoint.
PortAddr
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-4
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
atmAtmSpvpCon- Interface
Information
figFailNotify
Event, 106
spvcAddrIfA, atmAtm- An attempt to configure an
SpvcVpcVpiA, atmAtm- ATM SPVP at the ATM SPVC
SpvcVpcRemoteAtmendpoint has failed.
PortAddr,
spvcConfigFailureCode
atmAtmSpvpDeletedNotify
Interface
Information
Event, 107
spvcAddrIfA, atmAtm- An ATM SPVP configuraSpvcVpcVpiA, atmAtm- tion has been deleted.
SpvcVpcRemoteAtmPortAddr
atmAtmSpvpModifiedNotify
Interface
Information
Event, 108
spvcAddrIfA, atmAtm- The specified ATM SPVP
SpvcVpcVpiA, atmAtm- configuration has been
SpvcVpcRemoteAtmmodified.
PortAddr
atmAtmSpvpModifyFailNotify
Interface
Information
Event, 109
spvcAddrIfA, atmAtm- An attempt to modify the
SpvcVpcVpiA, atmAtm- specified ATM SPVP configSpvcVpcRemoteAtmuration has failed.
PortAddr,
spvcConfigFailureCode
atmBkPvcVccReqFailNotify
ConnecResponse
tion Event,
42
atmPvcVccIfA,
atmPvcVccVpiA,
atmPvcVccVciA,
atmPvcVccIfB,
atmPvcVccVpiB,
atmPvcVccVciB, pvcFailureReasonCode
The DHPVC VCC backup
connection request between
an ATM interface and an
ATM interface has failed.
atmBkPvcVccSetupNotify
ConnecResponse
tion Event,
43
atmPvcVccIfA,
atmPvcVccVpiA,
atmPvcVccVciA,
atmPvcVccIfB,
atmPvcVccVpiB,
atmPvcVccVciB
The DHPVC VCC backup
connection between an
ATM interface and an ATM
interface has been successfully established.
atmBkPvcVccTearDownNotify
ConnecResponse
tion Event,
44
atmPvcVccIfA,
atmPvcVccVpiA,
atmPvcVccVciA,
atmPvcVccIfB,
atmPvcVccVpiB,
atmPvcVccVciB
The DHPVC VCC backup
connection between an
ATM interface and an ATM
interface has torn down.
atmBkPvcVpcReqFailNotify
ConnecResponse
tion Event,
48
atmPvcVpcIfA,
atmPvcVpcVpiA,
atmPvcVpcIfB,
atmPvcVpcVpiB, pvcFailureReasonCode
The DHPVC VPC backup
connection request between
an ATM interface and an
ATM interface has failed.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-5
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
atmBkPvcVpcSetupNotify
ConnecResponse
tion Event,
49
atmPvcVpcIfA,
atmPvcVpcVpiA,
atmPvcVpcIfB,
atmPvcVpcVpiB
The DHPVC VPC backup
connection between an
ATM interface and an ATM
interface has been successfully established.
atmBkPvcVpcTearDownNotify
ConnecResponse
tion Event,
50
atmPvcVpcIfA,
atmPvcVpcVpiA,
atmPvcVpcIfB,
atmPvcVpcVpiB
The DHPVC VPC backup
connection between an
ATM interface and an ATM
interface has been torn
down.
atmImaIntfClearedNotify
Interface
Event, 39
Information
atmImaIntfIndex, atmI- A failure has been cleared in
maIntfStatus
an IMA interface. The atmImaIntfStatus field indicates
the failure that has been
cleared.
atmImaIntfFailNotify
Interface
Event, 37
Information
atmImaIntfIndex, atmI- There has been a failure in
maIntfStatus
the physical IMA interface.
The atmImaIntfStatus field
indicates the reason for the
failure.
atmPvcVccReqFailNotify
Response
Connection Event,
1
atmPvcVccIfA,
atmPvcVccVpiA,
atmPvcVccVciA,
atmPvcVccIfB,
atmPvcVccVpiB,
atmPvcVccVciB, pvcFailureReasonCode
The PVC VCC connection
request between two ATM
interfaces failed.
atmPvcVccSetup- ConnecResponse
Notify
tion Event,
10
atmPvcVccIfA,
atmPvcVccVpiA,
atmPvcVccVciA,
atmPvcVccIfB,
atmPvcVccVpiB,
atmPvcVccVciB
The PVC VCC connection
between two ATM interfaces
has been established.
atmPvcVccTearDownNotify
ConnecResponse
tion Event,
19
atmPvcVccIfA,
atmPvcVccVpiA,
atmPvcVccVciA,
atmPvcVccIfB,
atmPvcVccVpiB,
atmPvcVccVciB
The PVC VCC connection
between two ATM interfaces
has been torn down.
atmPvcVpcReqFailNotify
ConnecResponse
tion Event,
2
atmPvcVpcIfA,
atmPvcVpcVpiA,
atmPvcVpcIfB,
atmPvcVpcVpiB, pvcFailureReasonCode
The PVC VPC connection
request between two ATM
interfaces failed.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-6
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
atmPvcVpcSetup- ConnecResponse
Notify
tion Event,
11
atmPvcVpcIfA,
atmPvcVpcVpiA,
atmPvcVpcIfB,
atmPvcVpcVpiB
The PVC VPC connection
between two ATM interfaces
has been been successfully
established.
atmPvcVpcTearDownNotify
ConnecResponse
tion Event,
20
atmPvcVpcIfA,
atmPvcVpcVpiA,
atmPvcVpcIfB,
atmPvcVpcVpiB
The PVC VPC connection
between two ATM interfaces
has been torn down.
atmSecAgentHangingSANotify
ATM Secu- Information
rity Event,
15
atmSecStatsIntfId, atm- This is a hanging Security
SecStatsVpi,
Agent and must be deleted
atmSecStats Vci,
before continuing.
atmSecFailReasonCode
atmSecInvalidSe- ATM Secu- Information
curityAssociation- rity Event,
13
Notify
atmSecStatsIntfId, atm- One of the virtual SA’s secuSecStatsVpi, atmSecrity associations is not valid.
StatsVci, atmSecFailReasonCode
atmSecManualS- ATM Secu- Information
essionKeyUpdate- rity Event,
14
FailNotify
atmSecManualA manual session key
SkuIntfId, atmSecMan- update has failed.
ualSkuVpi, atmSecManualSkuVci,
atmSecFailReasonCode
atmSecPvcSACf- ATM Secu- Information
gCreateFailNotify rity Event,
1
atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi, atmCntrlPvcSecCfgVci,
atmSecFailReasonCode
An attempt to create a PVC
SA has failed, where atmCntrlPvcSecCfgIntfId identifies
the PVC SA configuration
table, and atmCntrlPvcSecCfgConnType specifies
whether signaling/routing
the PVC.
atmSecPvcSACfgCreatedNotify
ATM Secu- Information
rity Event,
2
atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi, atmCntrlPvcSecCfgVci
An attempt to create a PVC
SA succeeded, where atmCntrlPvcSecCfgIntfId identifies the PVC SA configuration table,
atmCntrlPvcSecCfgConnType specifies whether
signaling or routing the
PVC.
atmSecPvcSACf- ATM Secu- Information
gDeleteFailNotify rity Event,
3
atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi, atmCntrlPvcSecCfgVci,
atmSecFailReasonCode
An attempt to delete a PVC
SA has failed, where atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi, and atmCntrlPvcSecCfgVci identify one
entry in the PVC SA configuration table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-7
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
atmSecPvcSACfgDeletedNotify
Trap Group
ID and Trap
Index
Number
System
Indicator
ATM Secu- Information
rity Event,
4
MIB Object Name
atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi, atmCntrlPvcSecCfgVci
Trap Description
An attempt to delete a PVC
SA succeeded, where atmCntrlPvcSecCfgIntfId identifies the PVC SA configuration table,
atmCntrlPvcSecCfgConnType specifies whether
signaling/routing the PVC.
atmSecPvcSACfg- ATM Secu- Information
LoadFailNotify
rity Event,
16
atmCntrlPvcSecCfgInt- An attempt to load the PVC
fId, atmCntrlPvcSecCf- SA configuration from the
gVpi,atmCntrlPvcSecCf- database file has failed.
gVci,atmSecFailReason
Code
atmSecPvcSACfg- ATM Secu- Information
ModifyFailNotify rity Event,
5
atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi, atmCntrlPvcSecCfgVci,
atmSecFailReasonCode
An attempt to modify a PVC
SA failed, where atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi and atmCntrlPvcSecCfgVci identify one
entry in the PVC SA configuration table.
atmSecPvcSACfg- ATM Secu- Information
ModifiedNotify
rity Event,
6
atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi, atmCntrlPvcSecCfgVci
An attempt to modify a PVC
SA succeeded, where atmCntrlPvcSecCfgIntfId, atmCntrlPvcSecCfgVpi and atmCntrlPvcSecCfgVci identify
one entry in the PVC SA
configuration table.
atmSecSvccRccSACfgCreatedNotify
pnniSvccRccSecCfgPeerGrpId
An attempt to create an
SVCC RCC SA configuration succeeded, where
pnniSvccRccSecCfgPeerGrpId identifies the SVCC
RCC SA configuration table.
atmSecSvcATM Secu- Information
cRccSACfgCreate- rity Event,
FailNotify
7
pnniSvccRccSecCfgPeerGrpId, atmSecFailReasonCode
An attempt to create an
SVCC RCC SA configuration has failed, where
pnniSvccRccSecCfgPeerGrpId identifies the SVCC
RCC SA configuration table.
atmSecSvccRccSACfgDeletedNotify
pnniSvccRccSecCfgPeerGrpId
An attempt to delete an
SVCC RCC SA configuration succeeded, where
pnniSvccRccSecCfgPeerGrpId identifies the SVCC
RCC SA configuration table.
ATM Secu- Information
rity Event,
8
ATM Secu- Information
rity Event,
10
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-8
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
atmSecSvcATM Secu- Information
cRccSACfgDelete- rity Event,
FailNotify
9
pnniSvccRccSecCfgPeerGrpId, atmSecFailReasonCode
An attempt to delete an
SVCC RCC SA configuration has failed, where
pnniSvccRccSecCfgPeerGrpId identifies the SVCC
RCC SA configuration table.
atmSecSvccRccSACfgModifyFailNotify
ATM Secu- Information
rity Event,
11
pnniSvccRccSecCfgPeerGrpId, atmSecFailReasonCode
An attempt to modify an
SVCC RCC SA configuration has failed, where
pnniSvccRccSecCfgPeerGrpId identifies the SVCC
RCC SA configuration table.
atmSecSvccRccSACfgModifiedNotify
ATM Secu- Information
rity Event,
12
pnniSvccRccSecCfgPeerGrpId
An attempt to modify an
SVCC RCC SA configuration succeeded, where
pnniSvccRccSecCfgPeerGrpId identifies the SVCC
RCC SA configuration table.
atmSpvcConfigFailNotify
Interface
Event, 31
Information
atmSpvcVccIfA, atmSpvcVccVpiA, atmSpvcVccVciA, spvcConfigFailureCode
An attempt to configure an
endpoint as the specified
ATM SPVC endpoint has
failed.
atmSpvcConfiguredNotify
Interface
Event, 30
Information
atmSpvcVccIfA, atmSpvcVccVpiA, atmSpvcVccVciA
The endpoint has been successfully configured as an
ATM SPVC endpoint.
atmSpvcDeletedNotify
Interface
Event, 32
Information
atmSpvcVccIfA, atmSpvcVccVpiA, atmSpvcVccVciA
The specified ATM SPVC
configuration has been
deleted.
atmConnecResponse
SpvcVccSetUpNo- tion Event,
tify
59
atmSpvcVccIfA, atmSpvcVccVpiA, atmSpvcVccVciA, atmSpvcVccIfB,
atmSpvcVccVpiB, atmSpvcVccVciB
The specified SPVC connection between ATM and ATM
endpoints has been successfully established.
atmSpvcVccTearDownNotify
atmSpvcVccIfA, atmSpvcVccVpiA, atmSpvcVccVciA, atmSpvcVccIfB,
atmSpvcVccVpiB, atmSpvcVccVciB
The specified SPVC connection between ATM and ATM
endpoints has been deleted.
interfaceIndex, interfaceType
The specified ATM SVC
Interface Assured Data Link
is down.
ConnecResponse
tion Event,
62
atmSvcIntfLayer2 Interface
Down
Event, 52
Information
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-9
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
atmSvcIntfLayer2 Interface
Up
Event, 51
atmTrunkingBrVccConfigFailNotify
System
Indicator
Information
Interface
Information
Event, 125
MIB Object Name
interfaceIndex, interfaceType
Trap Description
The specified ATM SVC
Interface Assured Data Link
is up.
atmTrunkingBrVcThe specified ATM trunking
cRmtIWFId, atmTrunk- bearer VCC configuration
ingBrVccId, atmTrunk- has failed.
ingConfigFailureCode
atmTrunkingInterface
Information
BrVccConfigured- Event, 124
Notify
atmTrunkingBrVcThe specified ATM trunking
cRmtIWFId, atmTrunk- bearer VCC has been configingBrVccId
ured between Local IWF.
atmTrunkingInterface
Information
BrVccDeletedNo- Event, 126
tify
atmTrunkingBrVcThe specified ATM trunking
cRmtIWFId, atmTrunk- bearer VCC has been
ingBrVccId
deleted.
Response
atmTrunkingConnecBrVccSetUpNotify tion Event,
86
atmTrunkingBrVcThe specified ATM trunking
cRmtIWFId, atmTrunk- bearer VCC has been sucingBrVccId
cessfully established.
ConnecResponse
tion Event,
87
The specified ATM trunking
atmTrunkingBrVccRmtIWFId, atmTrunk- Bearer VCC has been torn
down.
ingBrVccId
atmTrunkingBrVccTearDownNotify
atmTrunkingLo- Interface
Information
calIWFConfigFail- Event, 111
Notify
atmTrunkingIWFIdenti- The local IWF has failed.
fier, atmTrunkingConfigFailureCode
atmTrunkingLocalIWFConfiguredNotify
Interface
Information
Event, 110
atmTrunkingIWFIdenti- The local IWF has been confier
figured.
atmTrunkingLo- Interface
Information
calIWFDeleteFail- Event, 115
Notify
atmTrunkingIWFIdenti- The configuration of the
fier, atmTrunkingCon- local IWF cannot be deleted.
figFailureCode
atmTrunkingLocalIWFDeletedNotify
Interface
Information
Event, 114
atmTrunkingIWIdentifier
atmTrunkingLocalIWFModifiedNotify
Interface
Information
Event, 112
atmTrunkingIWFIdenti- The configuration of the
fier
local IWF has been modified.
atmTrunkingLocalIWFModifyFailNotify
Interface
Information
Event, 113
atmTrunkingIWFIdenti- The modification of the local
fier, atmTrunkingCon- IWF has failed.
figFailureCode
atmTrunkingRemoteIWFConfiguredNotify
Interface
Information
Event, 116
atmTrunkingRemoteIWFIdentifier
The configuration of the
local IWF has been deleted.
The specified ATM Trunking
Remote IWF has been configured.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-10
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
atmTrunkingRemoteIWFConfigFailNotify
Trap Group
ID and Trap
Index
Number
System
Indicator
Interface
Information
Event, 117
MIB Object Name
Trap Description
atmTrunkingRemoteI- The specified ATM Trunking
WFIdentifier,
Remote IWF configuration
atmTrunkingConfigFail- has failed.
ureCode
atmTrunkingRe- Interface
Information
moteIWFDeleted- Event, 118
Notify
atmTrunkingRemoteIWFIdentifier
The specified ATM Trunking
Remote IWF has been
deleted.
atmTrunkingRemoteIWFModifiedNotify
atmTrunkingRemoteIWFIdentifier
The specified ATM Trunking
Remote IWF has been modified.
Interface
Information
Event, 119
atmTrunkingRe- Interface
Information
moteIWFModify- Event, 120
FailNotify
atmTrunkingRemoteI- The specified ATM Trunking
WFIdentifier,
Remote IWF has been conatmTrunkingConfigFail- figured.
ureCode
atmTrunkingInterface
Information
SigVccConfigFail- Event, 122
Notify
atmTrunkingSigVcThe specified ATM Trunking
cRmtIWFIdentifier,
signaling VCC configuration
atmTrunkingSigVccIhas failed.
dentifier, atmTrunkingConfigFailureCode
atmTrunkingSigVccConfiguredNotify
Interface
Information
Event, 121
atmTrunkingSigVccRmtIWFIdentifier,
atmTrunkingSigVccIdentifier
The specified ATM Trunking
Signaling VCC has been
configured between Local
IWF.
atmTrunkiSigVccDeletedNotify
Interface
Information
Event, 123
atmTrunkingSigVccRmtIWFIdentifier,
atmTrunkingSigVccIdentifier
The specified ATM Trunking
signaling VCC has been
deleted.
atmTrunkingSigVccSetUpNotify
ConnecResponse
tion Event,
84
atmTrunkingSigVccRmtIWFIdentifier,
atmTrunkingSigVccIdentifier
The specified ATM Trunking
signaling VCC has been successfully established.
atmTrunkingConnecResponse
SigVccTearDown- tion Event,
Notify
85
atmTrunkingSigVccRmtIWFIdentifier,
atmTrunkingSigVccIdentifier
The specified ATM Trunking
signaling VCC has been torn
down.
backplaneCircuit- System
ryFailedNotify
Event, 19
NO OBJECTS
There is no activity on the
cell bus. Please call Technical
Support immediately to
resolve the problem.
Critical
Possible Cause: The problem may be associated with the chassis or the Stratum
3–4 modules.
Corrective Action: Check the Trap Log Display window for events leading up to
this event notification. Also, check the System Information window (from the
Diagnostics Menu) for the status of the Backplane and Cell Bus parameters.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-11
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
backplaneCircuit- System
ryRecoveredNo- Event, 20
tify
System
Indicator
Trap Description
NO OBJECTS
The CPU module is able to
detect activity on the cell
bus.
bridgeAtmBkConnecResponse
PvcVccReqFailNo- tion Event,
tify
51
bridgeAtmPvcVccIfA,
bridgeAtmPvcVccIfB,
bridgeAtmPvcVccVpiB,
bridgeAtmPvcVccVciB,
pvcFailureReasonCode
The DHPVC VCC backup
connection request between
a bridge interface and an
ATM interface has failed.
bridgeAtmBkPvcVccSetupNotify
ConnecResponse
tion Event,
52
bridgeAtmPvcVccIfA,
bridgeAtmPvcVccIfB,
bridgeAtmPvcVccVpiB,
bridgeAtmPvcVccVciB
The DHPVC VCC backup
connection between a bridge
interface and an ATM interface has been successfully
established.
Response
bridgeAtmBkConnecPvcVccTearDown- tion Event,
Notify
53
bridgeAtmPvcVccIfA,
bridgeAtmPvcVccIfB,
bridgeAtmPvcVccVpiB,
bridgeAtmPvcVccVciB
The DHPVC VCC backup
connection between a bridge
interface and an ATM interface has been torn down.
bridgeAtmPvcVc- ConnecResponse
cReqFailNotify
tion Event,
31
bridgeAtmPvcVccIfA,
bridgeAtmPvcVccIfB,
bridgeAtmPvcVccVpiB,
bridgeAtmPvcVccVciB,
pvcFailureReasonCode
The PVC VCC connection
request between a bridge
interface and an ATM interface has failed.
ConnecResponse
tion Event,
32
bridgeAtmPvcVccIfA,
bridgeAtmPvcVccIfB,
bridgeAtmPvcVccVpiB,
bridgeAtmPvcVccVciB
The PVC VCC connection
between a bridge interface
and an ATM interface has
been successfully established.
bridgeAtmPvcVc- ConnecResponse
cTearDownNotify tion Event,
33
bridgeAtmPvcVccIfA,
bridgeAtmPvcVccIfB,
bridgeAtmPvcVccVpiB,
bridgeAtmPvcVccVciB
The PVC VCC connection
between a bridge interface
and an ATM interface has
been torn down.
bridgeBridgePvcReqFailNotify
ConnecResponse
tion Event,
28
bridgeBridgePvcIfA,
bridgeBridgePvcIfB,
pvcFailureReasonCode
The PVC connection request
between two bridge interfaces has failed.
bridgeBridgePvcSetupNotify
ConnecResponse
tion Event,
29
bridgeBridgePvcIfA,
bridgeBridgePvcIfB
The PVC connection
between two bridge interfaces has been successfully
established.
bridgeBridgePvcTearDownNotify
ConnecResponse
tion Event,
30
bridgeBridgePvcIfA,
bridgeBridgePvcIfB
The PVC connection
between two bridge interfaces has been torn down.
cardSlot
The bridge domain number
has been exceeded for the
slot.
bridgeAtmPvcVccSetupNotify
bridgeDomainEx- Interface
ceededForSlotNo- Event, 8
tify
Information
MIB Object Name
Information
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-12
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
bridgeDomainFullNotify
Interface
Event, 7
Information
bridgeDomainNumber
The 15 ports available for
the bridge domain are being
used leaving no space for an
additional port.
bridgeDomainInServiceNotify
Interface
Event, 10
Information
bridgeDomainNumber
The specified bridge domain
is now in service.
bridgeDomainInterface
NumberInUseNo- Event, 9
tify
Information
bridgeDomainNumber
The specified bridge domain
number is currently in use.
bridgeDomainNumberInvalidNotify
Interface
Event, 11
Information
interfaceIndex
This interface contains a non
valid bridge domain number. In order to create a
domain, associate a port
with a domain, or bring an
interface in service, a valid
domain number must be
provided.
bridgeDomainTimingRelationshipNotify
Interface
Event, 16
Information
bridgeDomainNumber,
timingReasonCode
One of the following relationships is violated: (1) 2 *
(BridgeForwardDelay - 1.0
sec) >= BridgeMaxAge (2)
BridgeMaxAge >= 2 *
(BridgeHelloTime + 1.0 sec).
bulkStatsCfgFailNotify
System
Event, 67
Information
pvcFailureReasonCode
A configuration error
occurred.
bulkStatsFtpFailNotify
System
Event, 66
Information
bulkStatsFtpOperation- An FTP failure has occurred.
ErrorStatus
cableStatusOfModule
GroupPortsChan- Event, 26
gedNotify
Information
cableStatusOfGroupedPorts
cardInsertionFail- Module
Notify
Event, 27
Major
cardSlot, cardType, car- The module iserted in the
dInsertionFailureReaindicated slot has failed.
sonCode
cardInsertionNotify
Module
Event, 1
Information
cardSlot, cardType,
cardProtectionStatus,
cardOperStatus
A module of the specified
type has been inserted into
the indicated slot.
cardRemovedOrFailedNotify
Module
Event, 2
Major
cardSlot
The indicated slot has
changed state.
System
Indicator
MIB Object Name
Trap Description
A change in the status of the
indicated cable group has
occurred.
Possible Cause: The module in the indicated slot may have been removed.
Corrective Action: Verify whether a module has been removed from the slot
indicated by checking the Equipment Configuration window and the Trap Log
Display window.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-13
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
ceServiceTypeModifyFailNotify
Interface
Event, 18
System
Indicator
Information
MIB Object Name
Trap Description
portId, interfaceFailure- Configuring unstructured
ReasonCode
CE failed.
Possible Cause: The port has been channelized or CAS has been turned on.
cellTestReqFailNotify
ConnecResponse
tion Event,
34
cellTestIfB, cellTestVpiB, cellTestVcidB,
pvcFailureReasonCode
channelizationModifyFailNotify
Interface
Event, 19
portId, interfaceFailure- Channelizing/unchannelizReasonCode
ing failed.
Information
The PVC connection request
has failed.
Possible Cause: (1) The port has been configured for unstructured CE (2) The
port has CAS turned on.
chassisOverTempAlarmNotify
System
Event, 60
Critical
chassisOverTempAlarm- The temperature of the
ReasonCode
chassis has exceeded 50
degrees Celsius (PSAX 1000
with AC power supply,
PSAX 2300, and PSAX 4500
systems) or 60 degrees Celsius (PSAX 1000 with DC
power supply).
Possible Cause: Occurs if the fans have failed, all the module slots are not covered, the ambient room temperature exceeds environmental specifications, the
chassis air vents are clogged, or the air filter is clogged.
Corrective Action: Replace the failed fans, cover the empty module slots, check
the ambient temperature reported on the Site Configuration menu (in degrees
Celsius) and adjust the room temperature accordingly, clean the chassis air vents,
or replace the air filter. Inspection and cleaning of the vents and filter should be
performed on a regular maintenance schedule, quarterly is recommended
depending on environmental conditions.
cirAtmSpvcConfigFailNotify
Interface
Event, 71
Information
spvcAddrIfA, cirAtmSpvcVccRemoteCePortAddr, spvcConfigFailureCode
An attempt to configure an
endpoint as a CE SPVC endpoint has failed.
cirAtmSpvcConfiguredNotify
Interface
Event, 70
Information
spvcAddrIfA, cirAtmSpvcVccRemoteCePortAddr
The endpoint has been configured as a CES SPVC endpoint.
cirAtmSpvcDelet- Interface
edNotify
Event, 72
Information
spvcAddrIfA, cirAtmSpvcVccRemoteCePortAddr, spvcConfigFailureCode
An attempt to configure an
endpoint as a CE SPVC endpoint has failed.
spvcAddrIfA, cirAtmSpvcVccRemoteCePortAddr, cirAtmSpvcVccIfB,
cirAtmSpvcVccVpiB,
cirAtmSpvcVccVciB
The specified SPVC connection between CE and ATM
endpoints has been successfully established.
cirAtmConnecResponse
SpvcVccSetUpNo- tion Event,
tify
69
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-14
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
cirAtmSpvcVccTe- ConnecResponse
arDownNotify
tion Event,
70
spvcAddrIfA, cirAtmSpvcVccRemoteCePortAddr, cirAtmSpvcVccIfB,
cirAtmSpvcVccVpiB,
cirAtmSpvcVccVciB
The specified SPVC connection between CE and ATM
endpoints has been torn
down.
cirEmAtmBkConnecResponse
PvcVccReqFailNo- tion Event,
tify
36
cirEmAtmPvcVccIfA,
cirEmAtmPvcVccIfB,
cirEmAtmPvcVccVpiB,
cirEmAtmPvcVccVciB,
pvcFailureReasonCode
The DHPVC VCC backup
connection request between
a circuit emulation interface
and an ATM interface has
failed.
cirEmAtmBkPvcVccSetupNotify
ConnecResponse
tion Event,
37
cirEmAtmPvcVccIfA,
cirEmAtmPvcVccIfB,
cirEmAtmPvcVccVpiB,
cirEmAtmPvcVccVciB
The DHPVC VCC backup
connection between a circuit emulation interface and
an ATM interface has been
successfully established.
Response
ConneccirEmAtmBkPvcVccTearDown- tion Event,
38
Notify
cirEmAtmPvcVccIfA,
cirEmAtmPvcVccIfB,
cirEmAtmPvcVccVpiB,
cirEmAtmPvcVccVciB
The DHPVC VCC backup
connection between the circuit emulation interface and
specified ATM interface has
been torn down.
cirEmAtmPvcVccReqFailNotify
Response
Connection Event,
4
cirEmAtmPvcVccIfA,
cirEmAtmPvcVccIfB,
cirEmAtmPvcVccVpiB,
cirEmAtmPvcVccVciB,
pvcFailureReasonCode
The PVC VCC connection
request between the circuit
emulation interface and the
specified ATM interface has
failed.
cirEmAtmPvcVccSetupNotify
ConnecResponse
tion Event,
13
cirEmAtmPvcVccIfA,
cirEmAtmPvcVccIfB,
cirEmAtmPvcVccVpiB,
cirEmAtmPvcVccVciB
The PVC VCC connection
between the circuit emulation interface and the specified ATM interface has been
successfully established.
cirEmAtmPvcVcc- ConnecResponse
TearDownNotify tion Event,
22
cirEmAtmPvcVccIfA,
cirEmAtmPvcVccIfB,
cirEmAtmPvcVccVpiB,
cirEmAtmPvcVccVciB
The PVC VCC connection
between the circuit emulation interface and the specified ATM interface has been
torn down.
cirEmAtmConnecResponse
SpvcVccSetUpNo- tion Event,
tify
57
cirEmAtmSpvcVccIfA,
cirEmAtmSpvcVccIfB,
cirEmAtmSpvcVccVpiB, cirEmAtmSpvcVccVciB
The specified SPVC connection between CE and ATM
endpoints has been successfully established.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-15
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
cirEmAtmSpvcVccTearDownNotify
ConnecResponse
tion Event,
60
System
Indicator
MIB Object Name
cirEmAtmSpvcVccIfA,
cirEmAtmSpvcVccIfB,
cirEmAtmSpvcVccVpiB, cirEmAtmSpvcVccVciB
Trap Description
The specified SPVC connection between CE and ATM
endpoints has been deleted.
cirEmCirConnecResponse
EmPvcReqFailNo- tion Event,
tify
8
cirEmCirEmPvcIfA, cir- The PVC connection request
EmCirEmPvcIfB, pvcbetween two circuit emulaFailureReasonCode
tion interfaces has failed.
cirEmCirEmPvcSetupNotify
ConnecResponse
tion Event,
17
cirEmCirEmPvcIfA, cir- The PVC connection
EmCirEmPvcIfB
between two circuit-emulation interfaces has been successfully established.
cirEmCirEmPvcTearDownNotify
Response
Connection Event,
26
cirEmCirEmPvcIfA, cir- The PVC connection
EmCirEmPvcIfB
between two circuit emulation interfaces has been torn
down.
cirEmSpvcConfig- Interface
FailNotify
Event, 21
Information
interfaceIndex, spvcCo- An attempt to configure an
nfigFailureCode
endpoint as a CE SPVC endpoint has failed.
cirEmSpvcConfig- Interface
uredNotify
Event, 20
Information
interfaceIndex
The endpoint has been configured as a CES SPVC endpoint.
cirEmSpvcDeletedNotify
Interface
Event, 22
Information
interfaceIndex
The specified CE SPVC configuration has been deleted.
completeClockFailedNotify
System
Event, 17
Critical
NO OBJECTS
The Stratum 3–4 modules
have either been removed
or have failed, resulting in
no clock being provided.
Possible Cause: The chassis may have been powered up without installing Stratum 3–4 modules.
Corrective Action: Verify on the Equipment Configuration window whether the
Stratum 3–4 modules are installed. The chassis may reboot without the Stratum
3–4 modules in which case the only way to verify status is through visual inspection of the chassis.
completeClockRe- System
coveredNotify
Event, 18
Information
NO OBJECTS
A Stratum 3–4 module is
now available to provide a
clock source.
compositeClockClearedNotify
Information
NO OBJECTS
The error in the composite
clock has been corrected.
System
Event, 7
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-16
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
compositeClockFailNotify
System
Event, 6
System
Indicator
Critical
MIB Object Name
NO OBJECTS
Trap Description
The composite clock has
failed. Please call Technical
Support immediately to
resolve the problem.
Possible Cause: The problem may be with the timing cable or source.
Corrective Action: Verify the Stratum 3–4 module status in the Stratum Configuration window. Check the field values for the [Primary Stratum Mode], [Backup
Stratum Mode], and Synchronization Source fields. Also check the LED on the
Stratum 3–4 module.
connectionConnecResponse
NamingResultNo- tion Event,
tify
92
connectionNamingResultCode
cRC4ModifyFailN Interface
otify
Event, 35
Information
portId, interfaceFailure- The modification of the
ReasonCode
CRC4 field of an E1 port has
failed.
Information
dhpvcChangeNo- Connectify
tion Event,
79
interfaceIndex atmVpi, Generated when a dual
atmVci, pvcFailureRea- home PVC switches over or
when the nonactive traffic
sonCode
path changes state. For a
switchover, this indicates
the last state and the new
one (i.e., primary to
backup). The pvcFailureReasonCode range is 284 to
289. For a state change, this
indicates the new state on
the non-active connection.
The pvcFailureReasonCode
range is 290 to 293.
differentSystemSoftwareNotify
primarySoftwareVersion, backupSoftwareVersion
System
Event, 44
Critical
The final status of the connection naming request.
The primary and backup
CPU modules are running
different versions of software. This could cause system problems since the
database files will not be
transferred between CPU
modules so a change of CPU
will result.
Possible Cause: The software upgrade was not completed on the CPU with an
older release. One example would be a driver patch being loaded on only one
CPU. Saving the Configuration will not copy the driver over to the standby CPU.
Corrective Action: Verify the version status of the CPU(s) by observing the CPU
software version that displays on the Login window. The Release number will display to four positions: for example, V07.01.C00.01. This Release number should
be compared with the backup CPU.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-17
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
dsp2CardReroutin Module
gFailedNotify
Event, 24
Information
cardSlot, pvcFailureRe- An attempt to reroute a
asonCode
DSP2 module has failed.
dsp2CardReroutin Module
gSucceededNotify Event, 23
Information
cardSlot
A DSP2 module was successfully rerouted. The configuration should be saved
to force updating of the
backup CPU.
dsp2IntfRerouting Interface
Information
SucceededNotify Event, 199
interfaceIndex
A DSP2 interface was successfully rerouted. The configuration should be saved
to force updating of the
backup CPU.
ecdBootFailureNotify
NO OBJECTS
System failed in the Boot
(startup) procedures. Please
call Technical Support
immediately to resolve the
problem.
System
Event, 3
Critical
Possible Cause: May have been caused by corruption from a restored backup
file.
Corrective Action: Depending on the software release, the ecd.def or ecd.db file
in /scsi/current will need to be checked. If the problem is preventing bootup, then
it may be necessary to break into the bootup process to examine the file. Try reinstating the ecd file by restoring it from the backup, or Save Configuration from
the backup CPU.
ermAtmSpvcCon- ConnecInformation
figFailNotify
tion Event,
95
spvcAddrIfA, ermIpIfNo, ermConnSubchNo, ermAtmSpvcRemoteAddr,
spvcConfigFailureCode
An attempt to configure an
ERM ATM SPVC connection has failed.
ermAtmSpvcCon- ConnecInformation
figuredNotify
tion Event,
94
spvcAddrIfA, ermIpIfNo, ermConnSubchNo, ermAtmSpvcRemoteAddr
An ERM ATM SPVC connection has been successfully
configured.
ermAtmSpvcDeletedNotify
ConnecInformation
tion Event,
96
spvcAddrIfA, ermIpIfNo, ermConnSubchNo, ermAtmSpvcRemoteAddr
An ERM ATM SPVC connection has has been deleted.
ermAtmSpvcModifiedNotify
ConnecInformation
tion Event,
97
spvcAddrIfA, ermIpIfNo, ermConnSubchNo, ermAtmSpvcRemoteAddr
An ERM ATM SPVC connection has has been modified.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-18
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
ermAtmSpvcModifyFailNotify
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
ConnecInformation
tion Event,
98
spvcAddrIfA, ermIpIfNo, ermConnSubchNo, ermAtmSpvcRemoteAddr,
spvcConfigFailureCode
An attempt to modify an
ERM ATM SPVC connection has failed.
ermAtmSpvcConnecInformation
SetupNotify
tion Event,
ermAtmSpvcTear- 99
DownNotify
spvcAddrIfA, ermIpIfNo, ermConnSubchNo, ermAtmSpvcRemoteAddr
An ERM ATM SPVC connection is being set up.
ermAtmSpvcTear- ConnecInformation
DownNotify
tion Event,
100
spvcAddrIfA, ermIpIfNo, ermConnSubchNo, ermAtmSpvcRemoteAddr
An ERM ATM SPVC connection is being torn down.
ermClassRuleTrap Interface
Information
Event, 244
ermSlot, ermVpnId,
ermClassTbId, ermClassRuleId, ermClassRuleStatus
Indicates the success or failure of IP class of service rule
operations.
ermClassTbTrap
Interface
Information
Event, 243
ermSlot, ermVpnId,
ermClassTbId, ermClassTbStatus
Indicates the success or failure of an IP classification
operation.
ermFilterTrap
Interface
Information
Event, 207
ermSlot, ermVpnId,
ermFilterId, ermFilterStatus
Indicates the success or failure of an IP filter operation.
ermPppCfgTemplateNotify
Interface
Information
Event, 245
ermSlot, ermVpnId,ermPppConfTemplateIndex, ermPppCfgTemplateResultCode
Indicates the PPP template
operation status.
ermRadiusTrap
Interface
Information
Event, 208
ermSlot, ermVpnId,
Indicates the success or failermRadiusServerIndex, ure of a Radius configuraermRadiusStatus
tion operation.
featureOnOffNotify
System
Event, 73
Information
featureOnOffErrorCode Indicates errors when turning a feature on or off.
fileTransferStatus- System
Notify
Event, 24
Information
percentComplete
The percent completed of
the current upgrade, downgrade, or FTP download in
progress.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-19
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
firmwareDownloadFailedNotify
Module
Event, 5
System
Indicator
Minor
MIB Object Name
Trap Description
fwReleaseSlot, firmThe specified failure
wareDownloadReason- occurred on the indicated
Code
slot during a firmware
download.
Possible Cause: The module may need to be upgraded or may be incompatible
with the default driver. It may need to be upgraded with a different driver.
Corrective Action: Check the status of the I/O module in the indicated slot
number: View the display in the Equipment Configuration window and the module LED. Check the firmware driver status in the Firmware Version Control
menu.
firmwareDownloadSucceededNotify
Module
Event, 4
frAtmBkPvcVccReqFailNotify
Information
fwReleaseSlot
The indicated slot has successfully completed a firmware download.
ConnecResponse
tion Event,
45
frAtmPvcVccIfA, frAtmPvcVccDlciA, frAtmPvcVccIfB, frAtmPvcVccVpiB,
frAtmPvcVccVciB, pvcFailureReasonCode
The DHPVC VCC backup
connection request between
a frame relay interface and
an ATM interface has failed.
frAtmBkPvcVccSetupNotify
ConnecResponse
tion Event,
46
frAtmPvcVccIfA, frAtmPvcVccDlciA, frAtmPvcVccIfB, frAtmPvcVccVpiB,
frAtmPvcVccVciB
The DHPVC VCC backup
connection between a frame
relay interface and an ATM
interface has been successfully established.
frAtmBkPvcVccTearDownNotify
ConnecResponse
tion Event,
47
frAtmPvcVccIfA, frAtmPvcVccDlciA, frAtmPvcVccIfB, frAtmPvcVccVpiB,
frAtmPvcVccVciB
The DHPVC VCC backup
connection between a frame
relay interface and an ATM
interface has been torn
down.
frAtmPvcVccReq- ConnecResponse
FailNotify
tion Event,
6
frAtmPvcVccIfA, frAtmPvcVccDlciA, frAtmPvcVccIfB, frAtmPvcVccVpiB,
frAtmPvcVccVciB, pvcFailureReasonCode
The PVC VCC connection
request between a framerelay interface and an ATM
interface has failed.
frAtmPvcVccSetupNotify
frAtmPvcVccIfA, frAtmPvcVccDlciA, frAtmPvcVccIfB, frAtmPvcVccVpiB,
frAtmPvcVccVciB
The PVC VCC connection
between a frame-relay interface and an ATM interface
has been successfully established.
ConnecResponse
tion Event,
15
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-20
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
frAtmPvcVccTear- ConnecResponse
DownNotify
tion Event,
24
frAtmPvcVccIfA, frAtmPvcVccDlciA, frAtmPvcVccIfB, frAtmPvcVccVpiB,
frAtmPvcVccVciB
The PVC VCC connection
between a frame-relay interface and an ATM interface
has been deleted.
frf5LmiStatusNoti Interface
Information
fy
Event, 232
frf5LmiOperStatus
The LMI protocol status on
FR-SSCS over AAL5.
frFrPvcReqFailNotify
ConnecResponse
tion Event,
7
frFrPvcIfA, frFrPvcDlThe PVC connection request
ciA, frFrPvcIfB, frFrbetween two frame-relay
PvcDlciB, pvcFailureRe- interfaces has failed.
asonCode
frFrPvcSetupNotify
ConnecResponse
tion Event,
16
frFrPvcIfA, frFrPvcDlciA, frFrPvcIfB, frFrPvcDlciB
The PVC connection
between two frame-relay
interfaces has been successfully established.
frFrPvcTearDownNotify
Response
Connection Event,
25
frFrPvcIfA, frFrPvcDlciA, frFrPvcIfB, frFrPvcDlciB
The PVC connection
between two frame-relay
interfaces has been torn
down.
frAtmSpvcConfig- Interface
FailNotify
Event, 61
Information
An attempt to configure the
spvcAddrIfA, frAtmSpvcVccDlciA, spvcCon- endpoint as an FR SPVC
endpoint has failed.
figFailureCode
frAtmSpvcConfig- Interface
uredNotify
Event, 60
Information
spvcAddrIfA, frAtmSpvcVccDlciA
The endpoint has been configure as an FR SPVC endpoint.
frAtmSpvcDeletedNotify
Information
spvcAddrIfA, frAtmSpvcVccDlciA
The specified FR SPVC configuration has been deleted.
frAtmConnecResponse
SpvcVccSetUpNo- tion Event,
tify
65
spvcAddrIfA, frAtmSpvcVccDlciA, frAtmSpvcVccIfB, frAtmSpvcVccVpiB,
frAtmSpvcVccVciB
Notification that a SPVC
connection between FR and
ATM endpoints has been
successfully established.
frAtmSpvcVccTe- ConnecResponse
arDownNotify
tion Event,
66
spvcAddrIfA, frAtmSpvcVccDlciA, frAtmSpvcVccIfB, frAtmSpvcVccVpiB,
frAtmSpvcVccVciB
Notification that a SPVC
connection between FR and
ATM endpoints has been
torn down.
Interface
Event, 62
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-21
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
gr303Aal2PvcCon ConnecCritical
figReqFailNotify tion Event,
76
MIB Object Name
Trap Description
gr303Aal2PvcVccGr303 The GR-303 PVC VCC on
IgId,
AAL2 trunk could not be set
gr303Aal2PvcVccGr303 up.
CallRef,
gr303Aal2PvcVccIfB,
gr303Aal2PvcVccVpiB,
gr303Aal2PvcVccVciB,
gr303Aal2PvcVccAal2Ci
d
Possible Cause: Verify the configuration parameters and status of the GR-303
interface.
Corrective Action: Check the trap log and GR303-to-AAL2 VCC/PVC Connection Table for PVC status. For interface status, check GR303 Interface Group Configuration and DS1 GR303 Interface Configuration windows.
gr303Aal2PvcSet
UpNotify
ConnecInformation
tion Event,
77
gr303Aal2PvcTear ConnecCritical
DownNotify
tion Event,
78
gr303Aal2PvcVccGr303
IgId,
gr303Aal2PvcVccGr303
CallRef,
gr303Aal2PvcVccIfB,
gr303Aal2PvcVccVpiB,
gr303Aal2PvcVccVciB,
gr303Aal2PvcVccAal2Ci
d
A monitor connection
between GR303 call reference and ATM AAL2 Channel Id has been successfully
established.
gr303Aal2PvcVccGr303
IgId,
gr303Aal2PvcVccGr303
CallRef,
gr303Aal2PvcVccIfB,
gr303Aal2PvcVccVpiB,
gr303Aal2PvcVccVciB,
gr303Aal2PvcVccAal2Ci
d
A monitor connection
between GR303 call reference and ATM AAL2 Channel Id has been torn down.
Possible Cause: The problem may be the teardown portion of normal call processing or a physical problem that could be interface related.
Corrective Action: Check the trap log and the GR303-to-AAL2 VCC/PVC Connection Table for PVC status. For interface status, check the GR303 Interface
Group Configuration and DS1 GR303 Interface Configuration windows.
gr303EOCChanD Interface
ownNotify
Event, 98
Information
interfaceIndex,
gr303EOCChannelId
The EOC (LAPD) on the GR303 interface has gone
down.
gr303EOCChanU Interface
Information
pNotify
Event, 100
interfaceIndex,
gr303EOCChannelId
The EOC (LAPD) is functional on the specified GR303 interface.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-22
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
gr303IgCreatedNo Interface
tify
Event, 87
Information
gr303IgId
A GR303IG has been created.
gr303IgCreateFail Interface
Notify
Event, 88
Information
gr303IgId , interfaceFailureReasonCode
An attempt to create a GR303 interface group has
failed. For details see interfaceFailureReasonCode.
gr303IgDeleteNoti Interface
fy
Event, 90
Information
gr303IgId
A GR303IG has been
deleted.
gr303IgInService
Notify
Interface
Event, 93
Information
gr303IgId
A GR303IG is in Service.
gr303IgIntfAdded Interface
Notify
Event, 94
Information
gr303IntfIgId ,
gr303IgIntfId
A DS1 interface has been
added to a GR303IG.
gr303IgIntfAddFa Interface
ilNotify
Event, 95
Information
gr303IntfIgId,
An attempt to add an intergr303IgIntfId, interface- face has failed.
FailureReasonCode
gr303IgIntfDelete Interface
Notify
Event, 96
Information
gr303IntfIgId,
gr303IgIntfId
A DS1 interface has been
deleted from a GR303IG.
gr303IgModifiedN Interface
otify
Event, 89
Information
gr303IgId
A GR303IG has been modified.
gr303IgModifyFai Interface
lNotify
Event, 91
Information
gr303IgId, interfaceFail- An attempt to modify a
ureReasonCode
GR303IG has failed.
gr303IgOutOfSer
viceNotify
Information
gr303IgId
Interface
Event, 92
gr303PPSComma Interface
Critical
ndFailNotify
Event, 103
A GR303IG is out of service.
gr303IgId,
The PPS switching comgr303PPSReasonCode, mand has failed.
gr303PPSSource,
gr303IgPrimaryTMCSta
tus,
gr303IgPrimaryEOCStat
us,
gr303IgBackupTMCStat
us,
gr303IgBackupEOCStat
us
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-23
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
gr303PPSStateCh Interface
Information
angeNotify
Event, 101
gr303IgId,
gr303PPSReasonCode,
gr303PPSSource,
gr303IgPrimaryTMCSta
tus,
gr303IgPrimaryEOCStat
us,
gr303IgBackupTMCStat
us,
gr303IgBackupEOCStat
us
A change in the states of the
primary and secondary
TMC/EOC (lapd) has
occurred.
gr303PPSSwitcho Interface
Information
verNotify
Event, 102
gr303IgId,
gr303PPSReasonCode,
gr303PPSSource,
gr303IgPrimaryTMCSta
tus,
gr303IgPrimaryEOCStat
us,
gr303IgBackupTMCStat
us,
gr303IgBackupEOCStat
us
The result of the PPS switching command which will
indicate the reason code,
initiator and states.
gr303TMCChanD Interface
ownNotify
Event, 97
Information
interfaceIndex,
gr303TMCChannelId
The TMC (LAPD) on the
GR-303 interface has gone
down.
gr303TMCChanU Interface
pNotify
Event, 99
Information
interfaceIndex,
gr303TMCChannelId
The TMC (LAPD) is functional on the specified GR303 interface.
h248CommLinkC System
hangeNotify
Event, 69
Information
h248CommLinkStatusC
ode,
h248CommLinkStatusT
ext
The status of the changes to
a communication link
between the MG and the
MGC.
h248CongestionN System
otify
Event, 70
Information
h248CongestReasonCo
de, h248CongestText
The congestion status of
H248.
h248TermErrorCode,
h248TermErrorText
An indication of the status
for an operation on an
H.248 termination.
h248TermConfig
Notify
Interface
Information
Event, 206
hdsl2ShdslSpanC Profile
onfProfileOpera- Event, 1
tionFailNotify
Information
hdsl2ShdslSpanConfPro An attempt to modify a profileName, profileFailfile has failed.
ureReasonCode
hdsl2ShdslEndpoi Profile
ntAlarmConfPro- Event, 2
fileOperationFailNotify
Information
hdsl2ShdslEndpointAlar An attempt to modify a promConfProfileName,
file has failed.
profileFailureReasonCode
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-24
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
imaGroupStatusChangeNotify
Module
Event, 11
Information
interfaceIndex, imaGr- The indicated SSPPCCC has
pChannelNeState,
had a change in the state of
imaGrpChanthe IMA Group Channel.
nelFeState, imaGrpChannelFailureStatus,
imaGrpChannelSymmetry
imaGrpChannelClearedNotify
Interface
Event, 38
Information
imaGrpChannelId,
imaGrpChannelStatus
A failure has been cleared in
an IMA group. The imaGrpChannelStatus field indicates the failure that has
been cleared.
imaGrpChannelFailNotify
Interface
Event, 36
Information
imaGrpChannelId,
imaGrpChannelStatus
A failure in the IMA group
occurred. The imaGrpChannelStatus field indicates the
reason for the failure.
inactivityTimerExpiredNotify
System
Event, 14
Major
NO OBJECTS
Sent by the Multiservice
Media Gateway system
when the inactivity timer of
the keep-alive protocol
expires; that is, when the
Multiservice Media Gateway
system does not see a message from the signaling
Gateway on the TCP link
during the time period specified by the inactivity timer
value setting
System
Indicator
MIB Object Name
Trap Description
Possible Cause: The link between the Multiservice Media Gateway and the Connection Gateway may be out of service or the Signaling Gateway could be down.
Corrective Action: Verify the value of the inactivity timer. Check the trap log for
events leading up to the trap, such as TCP link failures associated with the Signaling Gateway.
inputPortClockClearedNotify
System
Event, 46
Information
portId
The error in the input port
clock has been corrected.
portId refers to the stratum
lineId when the stratum
synchronization source is
line timing; In the case of T1
bits, E1 sets and composite
clock, it refers to the slot
number of the module that
provides the input clock.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-25
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
inputPortClockFailNotify
System
Event, 45
System
Indicator
Critical
MIB Object Name
NO OBJECTS
Trap Description
The input port clock has
failed.
Corrective Action: Please call Technical Support immediately to resolve the
problem.
interCpuTxferTypeChangeNotify
System
Event, 65
Information
interfaceBandwidthChangeNotify
Interface
Information
Event, 104
interCpuTxferType
The inter CPU file transfer
type has changed.
interfaceIndex, interThe specified interface has
faceFailureReasonCode undergone reduction in
bandwidth. The severity is
critical if the Failure Reason
Code is 67, 68, or 69.
interfaceCreated- Interface
Notify
Event, 1
Information
interfaceIndex, interfaceType
The specified interface has
been created.
interfaceCreateFailNotify
Interface
Event, 55
Information
interfaceIndex, interfaceType, interfaceFailureReasonCode
An attempt to create the
specified interface has failed.
interfaceFailureReasonCode
gives details.
interfaceDeletedNotify
Interface
Event, 2
Information
interfaceIndex
The specified interface has
been deleted.
interfaceInServiceNotify
Interface
Event, 6
Information
interfaceIndex, interfaceType
The specified interface is
now in service.
interfaceModifiedNotify
Interface
Event, 3
Information
interfaceIndex, interfaceType
The specified interface has
been modified.
interfaceModifyFailNotify
Interface
Event, 4
Information
interfaceIndex, interfaceType, interfaceFailureReasonCode
An attempt to modify an
interface has failed.
interfaceNamingResultNotify
Interface
Response
Event, 205
interfaceNamingResult- The final status of the interCode
face naming request.
interfaceOutOfServiceNotify
Interface
Event, 5
interfaceIndex, interfaceType
Major
The specified interface is
now out of service.
Possible Cause: The interface may either have been taken out of service manually, or through an external cause.
Corrective Action: Verify the status of the indicated slot, port, and channel
numbers in the Equipment Configuration window. Also, check the Trap Log Display window for confirmation of status and events leading to the interface status
change.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-26
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
ipAtmAppPvcVccReqFailNotify
ConnecResponse
tion Event,
3
ipAtmAppPvcVccDestAddrA, ipAtmAppPvcVccSubnetMaskA,
ipAtmAppPvcVccIfB,
ipAtmAppPvcVccVpiB,
ipAtmAppPvcVccVciB,
pvcFailureReasonCode
The PVC VCC connection
request between in-band
management and an ATM
interface has failed.
ipAtmAppPvcVccSetupNotify
ConnecResponse
tion Event,
12
ipAtmAppPvcVccDestAddrA, ipAtmAppPvcVccSubnetMaskA,
ipAtmAppPvcVccIfB,
ipAtmAppPvcVccVpiB,
ipAtmAppPvcVccVciB
The PVC VCC connection
between in-band management and an ATM interface
has been successfully established.
ipAtmAppPvcVcc- ConnecResponse
TearDownNotify tion Event,
21
ipAtmAppPvcVccDestAddrA, ipAtmAppPvcVccSubnetMaskA,
ipAtmAppPvcVccIfB,
ipAtmAppPvcVccVpiB,
ipAtmAppPvcVccVciB
The PVC VCC connection
between in-band management and an ATM interface
has been torn down.
ConnecResponse
ipAtmBkAppPvcVccReqFailNo- tion Event,
tify
54
ipAtmAppPvcVccDestAddrA, ipAtmAppPvcVccSubnetMaskA,
ipAtmAppPvcVccIfB,
ipAtmAppPvcVccVpiB,
ipAtmAppPvcVccVciB,
pvcFailureReasonCode
The DHPVC VCC backup
connection request between
an in-band management
interface and an ATM interface has failed.
ipAtmBkAppPvcVccSetupNotify
ConnecResponse
tion Event,
55
ipAtmAppPvcVccDestAddrA, ipAtmAppPvcVccSubnetMaskA,
ipAtmAppPvcVccIfB,
ipAtmAppPvcVccVpiB,
ipAtmAppPvcVccVciB
The DHPVC VCC backup
connection between an inband management interface
and an ATM interface has
been successfully established.
ipAtmBkAppConnecResponse
PvcVccTearDown- tion Event,
Notify
56
ipAtmAppPvcVccDestAddrA, ipAtmAppPvcVccSubnetMaskA,
ipAtmAppPvcVccIfB,
ipAtmAppPvcVccVpiB,
ipAtmAppPvcVccVciB
The DHPVC VCC backup
connection between an inband management interface
and an ATM interface has
been torn down.
ipOrMaskInvalid- System
Notify
Event, 25
ipTypeReasonCode
The indicated IP address is
not valid.
iptResultNotify
Response
ConnecResponse
tion Event,
82
iptGroupId, iptLogiThe final status of an intercalIntfId, iptResultCode face protection request.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-27
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
isdnLapdDownNotify
Interface
Event, 14
Information
interfaceIndex, isdnInt- This trap indicates that
fDChanId
LAPD on the ISDN interface
has gone down.
isdnLapdUpNotify Interface
Event, 15
Information
interfaceIndex, isdnInt- This trap indicates that
fDChanId
LAPD is functional on the
specified ISDN interface.
System
Indicator
MIB Object Name
Trap Description
iuaAspStateChangeNotify
Interface
Information
Event, 183
iuaAspEpId, iuaAsId,
iuaAspId, iuaAspState
A change in the state of an
ASP has occurred. An active
state indicates that the
remote IUA peer at the ASP
is available and traffic is
active. An inactive state
indicates that the remote
IUA peer at the ASP is available but traffic is stopped. A
down state indicates that the
ASP is unavailable and/or
the related SCTP association
is down.
iuaAsStateChangeNotify
Interface
Information
Event, 203
iuaAsId, iuaAsState
A change in the state of an
AS (application server) has
occurred.
iuaClientServerOptionModifyFailNotify
Interface
Information
Event, 181
iuaClientServerOption
An attempt to change the
IUA client/server option has
failed.
iuaErrorNotify
Interface
Information
Event, 204
iuaAspEpId, iuaAsId,
An indication that an IUA
iuaAspId, iuaErrorCode, error event has occurred.
iuaDiagInfo
iuaFailOverInterface
Information
BufferingStartNo- Event, 194
tify
iuaAsId, iuaFailOverBuffSize, iuaTrValue
The IUA failover retransmission buffering has started for
the specified buffer size and
time period.
iuaFailOverBuff- Interface
Information
erOverflowNotify Event, 195
iuaAsId, iuaFailOverBuffSize
The IUA failover retransmission buffer overflows and
buffering has been stopped.
iuaFailOverBuffSizeModifyFailNotify
Interface
Information
Event, 180
iuaFailOverBuffSize
An attempt to change the
IUA failover retransmission
buffer size has failed.
iuaHeartBeatModifyFailNotify
Interface
Information
Event, 178
iuaHeartBeat
An attempt to activate or
deactivate the heartbeat
procedure at the IUA level
has failed.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-28
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
iuaLocalPortMod- Interface
Information
ifyFailNotify
Event, 176
iuaLocalPort
An attempt to change the
IUA local port number has
failed.
iuaRecoveryTimerExpireNotify
Interface
Information
Event, 196
iuaAsId, iuaTrValue
The IUA Recovery Timer has
expired and retransmission
buffering has been stopped.
iuaSctpStateChangeNotify
Interface
Information
Event, 182
iuaAspEpId, iuaAspEpAssocId, iuaAspEpAssocState
A change in the state of the
SCTP association of an ASP
Endpoint has occurred. A
closed state indicates that
the SCTP association has not
been established. An established state indicates that
the SCTP association has
been established.
iuaTBeatValueModifyFailNotify
Interface
Information
Event, 179
iuaTBeatValue
An attempt to change the
IUA HeartBeat timer TBeat
value has failed.
iuaTrValueModifyFailNotify
Interface
Information
Event, 177
iuaTrValue
An attempt to change the
IUA Recovery timer T(r)
value has failed.
NO OBJECTS
Sent by the Multiservice
Media Gateway system
when the keep-alive timer
expires in the LLDOWN
state of the keep-alive protocol; that is, when the Multiservice Media Gateway system does not see a keepalive message from the Connection Gateway on the TCP
link during the time period
specified by the keep-alive
timer setting.
keepAliveTimer- System
ExpiredInLlEvent, 15
DownStateNotify
Major
Possible Cause: The link between the Multiservice Media Gateway and the Connection Gateway may be out of service or the Signaling Gateway could be down.
Corrective Action: Check the trap log for events leading up to the trap, such as
TCP link failures associated with the Signaling Gateway.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-29
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
keepAliveTimerExpiredInOneWayStateNotify
Trap Group
ID and Trap
Index
Number
System
Event, 16
System
Indicator
Major
MIB Object Name
NO OBJECTS
Trap Description
Sent by the Multiservice
Media Gateway system
when the keep-alive timer
expires in the ONE-Way
state of the keep-alive protocol; that is, when the Multiservice Media Gateway system does not see a keepalive message from the Signaling Gateway on the TCP
link during the time period
specified by the keep-alive
timer setting.
Possible Cause: The link between the Multiservice Media Gateway and the Connection Gateway may be out of service or the Signaling Gateway could be down.
Corrective Action: Check trap log for events leading up to the trap, such as TCP
link failures associated with the Signaling Gateway.
limStatusChangedNotify
Module
Event, 12
Information
cardSlot, limStatus
A lim module has been
inserted/recovered or
removed/failed.
lineStatusChangedNotify
Module
Event, 3
Major
portId, lineStatus
The specified port has had a
change in the line status.
Possible Cause: A change in the line status may indicate a problem with the port
or facility.
Corrective Action: Check the trap log for events associated with the indicated
slot and port number. Also, check the integrity of the external facility.
lmiDlciStatusNotify
ConnecResponse
tion Event,
35
interfaceIndexdlciNum- The end-to-end status of the
ber, lmiDlciOperStatus PVC of which this DLCI is a
segment.
lmiIntfStatusNotify
Interface
Event, 13
Information
interfaceIndex, frLmiO- The status of an interface
perStatus
from the LMI perspective.
loginAuthSuccessNotify
System
Event, 63
Information
NO OBJECTS
The console login authentication is successful.
Critical
NO OBJECTS
The console login authentication failed.
loginAuthFailNo- System
tify
Event, 64
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-30
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
moduleRebootNotify
Module
Event, 6
System
Indicator
Major
MIB Object Name
cardSlot, cardType
Trap Description
This trap is generated by
prmComm->cfgMgr
>snmpAgent, when the
heartbeat of an I/O module
is missing for 3 seconds and
then resumes without going
into broadcast mode (i.e.,
I/O module initializing
mode).
Possible Cause: The module has reached a state where control from the CPU is
lost, thus prompting the CPU to reboot it in order to regain control.
Corrective Action: The message will indicate the module type and slot. Check
the slot number in the Equipment Configuration window, and verify the alarm
status. Check the Trap Log Display window for events leading up to the module
reboot.
System
muxReadyConfirmNotReceived- Event, 12
Notify
Major
NO OBJECTS
If the Multiservice Media
Gateway system is configured as TCP client, this trap
is sent if the
MUX_READY_CONF message is not received after
sending the
MUX_READY_IND message
three times. This trap indicates unexpected behavior
on the Multiservice Media
Gateway system to Connection Gateway link.
Possible Cause: The link between the Multiservice Media Gateway and the Connection Gateway may be out of service.
Corrective Action: Check the link between the Multiservice Media Gateway
and the Connection Gateway.
muxReadyConfirmReceivedNotify
System
Event, 11
Information
NO OBJECTS
The MUX (the Multiservice
Media Gateway system) has
received a
MUX_READY_CONF message in response to the
MUX_READY_IND message
when the Multiservice
Media Gateway system is
configured as the TCP client
for the Multiservice Media
Gateway system to Connection Gateway connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-31
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
ntomProtection- Module
GroupCreateFail- Event, 16
Notify
Information
ntomProtectionGroupId, ntomProtectionReasonCode
An attempt to create a protection group has failed.
ntomProtectionGroupCreateNotify
Module
Event, 15
Information
ntomProtectionGroupId The specified protection
group has been successfully
created.
ntomProtectionGroupDeleteNotify
Module
Event, 19
Information
ntomProtectionGroupId The specified protection
group has been deleted.
ntomProtection- Module
GroupModifyFail- Event, 18
Notify
Information
ntomProtectionGroupId , ntomProtectionReasonCode
ntomProtection- Module
GroupModifyNo- Event, 17
tify
Information
ntomProtectionGroupId A protection group has been
modified.
ntomProtectionGroupSlotAdd
Module
Event, 20
Information
ntomProtectionAn additional slot has been
GroupId, cardSlot,
added to a protection group.
ntomProtectionReasonCode
ntomProtectionGroupSlotRemove
Module
Event, 21
Information
ntomProtectionThe specified slot has been
GroupId, cardSlot,
removed from a protection
ntomProtectionReason- group.
Code
ntomProtectionSlotModifyFail
Module
Event, 22
Information
ntomProtectionA failure to execute a comGroupId, cardSlot,
mand on protection slot
ntomProtectionReason- variables has occurred.
Code
ntomProtection- Module
SwitchoverNotify Event, 13
Information
workingCardSlot, protectionCardSlot
A switchover in an N to M
group has occurred. The first
module slot is the working
module and the second is
the protection module.
The final status of OAM
Activation-Deactivation
request.
An attempt to modify a protection group has failed.
oamActDeactResultNotify
ConnecResponse
tion Event,
64
oamActDeactIfB,
oamActDeactVpiB,
oamActDeactVciB,
oamActDeactResultCode
oamTestReqFailNotify
ConnecResponse
tion Event,
63
oamTestIfB,
The OAM loopback test
oamTestVpiB,
request has failed.
oamTestVciB, oamTestFailureReasonCode
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-32
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
ocxAPSStateChangeNotify
Module
Event, 7
Response
ocxAPSPairPortIndex,
A change in the APS state
ocxAPSReasonCode,
machine has occurred.
ocxAPSK1K2Rx,
ocxAPSK1K2Tx, ocxAPSSelectorState, ocxAPSWorkingLineSignalStatus,
ocxAPSProtectionLineSignalStatus
ocxAPSSwitchov- Module
erNotify
Event, 8
Response
ocxAPSPairPortIndex,
A switchover in an APS pair
ocxAPSReasonCode,
has occurred.
ocxAPSK1K2Rx,
ocxAPSK1K2Tx, ocxAPSSelectorState, ocxAPSWorkingLineSignalStatus,
ocxAPSProtectionLineSignalStatus
oldStratumCardNotify
Critical
NO OBJECTS
System
Event, 47
System
Indicator
MIB Object Name
Trap Description
The primary stratum module does not support this
mode of operation being
applied in the stratum configuration. The module must
be upgraded. A default configuration is being applied to
stratum.
Possible Cause: The Stratum 3–4 module has an incorrect chipset.
Corrective Action: Verify that the chipset in the Stratum 3–4 module is correct
for this release of system software.
oneWayMessage- System
WhileInTwoWay- Event, 13
StateNotify
Major
NO OBJECTS
A one way message is
received from the Connection Gateway (CG) when
the Multiservice Media
Gateway system is in the
two way state of the keepalive protocol on the TCP
link between the Multiservice Media Gateway system
and the CG.
Possible Cause: Provisioning mismatch.
Corrective Action: Check provisioning on the Connection Gateway and the
Multiservice Media Gateway.
pgtResultNotify
ConnecResponse
tion Event,
83
pgtGroupId, pgtResultCode
The final status of an interface protection group
request.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-33
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
pnniIntfCfgFailNotify
Interface
Event, 43
Information
interfaceIndex, pnniCode
An attempt to create a PNNI
Interface has failed.
pnniNodeCfgFail- System
Notify
Event, 32
Information
swtchNodeIndx, pnniCode
An attempt to create a PNNI
Node has failed.
pnniNodeCfgNotify
System
Event, 31
Information
swtchNodeIndx, pnniCode
A PNNI Node has been successfully created.
pnniNodeDelFail- System
Notify
Event, 34
Information
swtchNodeIndx, pnniCode
An attempt to delete a PNNI
Node has failed.
pnniNodeISFailNotify
System
Event, 36
Information
swtchNodeIndx, pnniCode
An attempt to bring a PNNI
Node into service has failed.
pnniNodeModFailNotify
System
Event, 33
Information
swtchNodeIndx, pnniCode
An attempt to modify a
PNNI Node has failed.
pnniNodeOOSFailNotify
System
Event, 35
Information
swtchNodeIndx, pnniCode
An attempt to take a PNNI
Node out of service has
failed.
pnniProtLinkUpAndNotAdv
Interface
Event, 41
Information
interfaceIndex, pnniCode
The protocol status of the
PNNI Link is up but not
advertising.
pnniProtLnkStat- Interface
Down
Event, 42
Information
interfaceIndex, pnniCode
The protocol status of the
PNNI Link is down.
pnniProtLnkUpAndAdv
Interface
Event, 40
Information
interfaceIndex, pnniCode
The protocol status of the
PNNI Link is up and advertising.
pnniRtAddrAddByIlmiNotify
System
Event, 41
Information
swtchNodeIndx, interfaceIndex, pnniCode
An end system address has
been dynamically added to
PNNI by ILMI.
pnniRtAddrCfgFailNotify
System
Event, 38
Information
swtchNodeIndx, interfaceIndex, pnniCode
A PNNI Route Address Configuration has failed.
pnniRtAddrCfgNotify
System
Event, 37
Information
swtchNodeIndx, interfaceIndex, pnniCode
A new PNNI Route Address
has been created.
pnniRtAddrDelByIlmiNotify
System
Event, 42
Information
swtchNodeIndx, interfaceIndex, pnniCode
An end system Address has
been dynamically deleted
from PNNI by ILMI.
pnniRtAddrDelFailNotify
System
Event, 40
Information
swtchNodeIndx, interfaceIndex, pnniCode
A PNNI Route Address Deletion has failed.
pnniRtAddrMod- System
FailNotify
Event, 39
Information
swtchNodeIndx, interfaceIndex, pnniCode
An attempt to modify a
PNNI Route Address has
failed.
portMaintenanceTestNotify
Information
portId, portMaintNotification that a port
TestChangeReasonCode maintenance test status has
changed.
Module
Event, 28
System
Indicator
MIB Object Name
Trap Description
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-34
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
portMaintenanceTestFailNotify
Module
Event, 29
Information
portId, portMaintTestFailureReasonCode
Notification that an attempt
to change maintenance test
parameters or a port maintenance test has failed.
portModifiedNotify
Module
Event, 25
Information
portId, portModificationReasonCode
A port parameter has been
modified.
portModifyFailNotify
Module
Event, 9
Information
portId, portFailureReasonCode
An attempt to modify a port
parameter has failed.
Minor
powerSupplyReasonCode
The status of the power supply as indicated by the powerSupplyReasonCode MIB
object.
powerSupplySta- System
tusNotify
Event, 9
System
Indicator
MIB Object Name
Trap Description
Possible Cause: The event may indicate a state change, so check the trap log for
related events, such as removal, insertion, or failure notifications.
Corrective Action: Check the alarm status of the power supplies in the Equipment Configuration window. Also, make a note of any garbled or missing characters that appear in each row corresponding to the power supply. Check the LED
display as well.
referenceClockClearedNotify
System
Event, 5
Information
NO OBJECTS
The error in the backplane
reference clock has been
corrected.
referenceClockFailNotify
System
Event, 4
Critical
NO OBJECTS
The reference clock used for
the operation of the busbased backplane has failed.
If the referenceClockFailNotify does not clear in approximately 30 seconds, by
reporting the referenceClockClearedNotify trap
message, please call Technical Support immediately to
resolve the problem.
Possible Cause: The problem may stem from the Stratum 3–4 modules, power
supplies, or the chassis itself.
Corrective Action: Check the status of the Stratum 3–4 module(s), and power
supplies. Verify the current Stratum 3–4 configuration. If the synchronization
source is freerun, try changing to Line Source or Composite Clock.
remoteDbOperationStatusNotify
System
Event, 57
Information
remoteDbOperationSta- The completion status of the
tus, remoteDbOperaremote database operation.
tionErrorStatus
remoteRebootNo- System
tify
Event, 21
Information
remoteRebootReasonCode
The result of the requested
reboot action.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-35
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
removeConfigFilesNotify
System
Event, 27
Information
removeConfigFiles
The status of the removal of
the configuration files.
sapphireInterfaceAddressAssignFailNotify
System
Event, 58
Information
sapphireIntfAddressFailReasonCode
The assignment of the
CGAPI interface address on
which TCP connect requests
are sent to Softswitch when
the PSAX system, configured as a client, has failed.
saveConfigurationNotify
System
Event, 22
Information
saveConfigurationReasonCode
The result of the requested
save configuration command.
signalingModifyFailNotify
Interface
Event, 12
Information
interfaceIndex, interfaceType, interfaceFailureReasonCode
Signaling has already been
configured for this port, and
to change you must bring all
interfaces out of service,
including the channel specified in interfaceIndex.
snmpCommunityStringsChangedToPublicNotify
System
Event, 30
Critical
NO OBJECTS
An error has been detected
in the agt.pty file and the
community strings have
been changed to be public.
System
Indicator
MIB Object Name
Trap Description
Possible Cause: This may be caused by corruption in the agt.pty file.
Corrective Action: Using the Console interface, log onto the PSAX system and
verify the ReadWrite community string. Try reapplying the correct string, since
this may recreate the agt.pty file.
softwareComponentFailedAndRestartedNotify
System
Event, 72
Major
sysInfoDisplayString
softwareDownloadStatusNotify
System
Event, 10
Information
upgradeSwCopyStatus, The completion status of the
upgradeSwErrorStatus FTP download of a software
upgrade.
stratumActiviModule
tySwitchOverNo- Event, 10
tify
Information
activeStratum
The specified CPU software
component has crashed or
failed and has been restarted
by the system watchdog.
The secondary stratum module is active and has become
the primary module
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-36
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
stratumCardMismatchNotify
System
Event, 48
System
Indicator
Critical
MIB Object Name
NO OBJECTS
Trap Description
The secondary stratum module does not support this
mode of operation being
applied to the primary stratum. The module must be
upgraded.
Possible Cause: Critical: Indicates that the secondary Stratum 3–4 module does
not support this mode of operation being applied to the primary Stratum 3–4
module. The module must be upgraded.
Corrective Action: Check that the standby Stratum 3–4 module is the same
model as the primary, verifying the PEC and the installed chipset on the Stratum
3–4 module.
stratumConfigModifyFailNotify
Module
Event, 14
Information
stratumConfigModifyFailureReasonCode
stratumModeChangeNotify
System
Event, 8
Information
stratumMode, stratum- The current operational staBackupMode
tus of the Stratum 3–4 module has changed as indicated
by the stratumMode MIB
object.
svcRetBackupSta- System
tusChangeNotify Event, 74
Major
svcRetBackupStatus
The reliable data link (RDL)
is up/down and the SVC
retention module (SRM)
warm up is done.
switchAlarmStatusChangeNotify
Critical
switchAlarmStatus
A change in the status of the
alarm on the PSAX system
has occurred as indicated by
the switchAlarmStatus MIB
object.
System
Event, 59
An attempt to modify the
stratum configuration has
failed.
Possible Cause: This alarm is generated when a current level changes. The possible Alarm Status values are: notAvailable, none, minor, major, critical.
Corrective Action: Check the Trap Log Display window to verify the alarm
event notification and observe the events leading up to the alarm generation.
switchFanStatusChangeNotify
System
Event, 62
Critical
switchFanStatus
A change in the status of the
fans on the switch has
occurred.
systemColdStartNotify
System
Event, 1
Information
NO OBJECTS
The PSAX system has successfully completed initialization from a complete
power down stage and is
ready for operation.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-37
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
systemInsuffMemNotify
System
Event, 53
System
Indicator
Information
MIB Object Name
NO OBJECTS
Trap Description
There is insufficient memory
for one or more features to
be turned on.
Possible Cause: Too many features are turned on or, too many I/O modules are
configured.
Corrective Action: Use one or more of the following corrective actions to
increase the free memory on the CPUn module to an amount greater than 2 MBs:
1) Turn off features that are not in use. 2) Remove one or more I/O modules by
unconfiguring all interfaces on the I/O module, then physically removing the
module from the chassis. 3) Upgrade the CPUn module to a CPU4 module. Note:
Any CPUn module that is misconfigured can result in insufficient memory.
systemMemStatusNotify
System
Event, 71
Major
NO OBJECTS
Indicates the system memory status: Normal, in a yellow zone or in a red zone.
The yellow zone indicates
that the system memory is
below 2MB. The red zone
indicates that the system
memory is below 100 KB.
No new configuration or
module insertion is allowed
when the system is in the
yellow zone unless some
memory is freed to return
the system back to normal.
This trap message is sent
every 10 minutes while in
the yellow zone. A trap message will be sent when the
system is back to normal.
While in the red zone, the
system will reboot in 4 seconds in addition to a trap
message being sent.
systemWarmStartNotify
System
Event, 2
Information
NO OBJECTS
The system has successfully
completed initialization
from a user or other system
level interrupt or restart and
is ready for operation.
tasCmprsAnnceNotify
System
Event, 49
Information
tasCmprsAnnceReason- The result of the requested
Code, tasTrapAnnceId
compress announcement
operation.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-38
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
tasContinuityCheckNotify
System
Event, 61
Information
tasContinuityCheckThe result of the requested
ReasonCode, tasTrapcontinuity check initiation
ContinuityCheckIntfIn- operation.
dex
tasmCacheMemAllocFailNotify
System
Event, 56
Information
tasmCacheMemAllocFail, ReasonCode
tasmControlBlockResAllocFailNotify
System
Event, 55
Information
tasmControlBlockAlloc- The configuration of tasm
FailReasonCode
control block resource allocation has failed.
tasMemNotify
System
Event, 51
Information
tasMemReasonCode
The result of the requested
tasm memory initialization
operation.
tasTstLineNotify
System
Event, 50
Information
tasTstLineReasonCode,
tasTrapTstId
The result of the requested
line test initiation operation.
toneAnnceFtpSta- System
tusNotify
Event, 54
Information
toneAnnceFtpStatus,
The completion status of the
toneAnnceFtpErrorSta- FTP download of a tone
tus
announcement file.
ts16UsageModify
FailNotify
Information
interfaceIndex, interNotification that either TS16
faceFailureReasonCode has been in use for data
while trying to change e1
TS16 from CCS to CAS, or
signaling is on for at least
one of the channels while
trying to change e1 TS16
from CAS to CCS.
Interface
Event, 17
System
Indicator
MIB Object Name
Trap Description
The configuration of tasm
cache for announcement
caching allocation has failed.
v5ActiveVariantC Interface
Information
antBeTakeEvent, 187
nOOSWhenIntfIsISNotify
v5IntfId, v5VariantId
The V5.2 Interfaces variant
cannot be taken out of service when the interface is in
service, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table.
v5DLCantBeDelet Interface
Information
edWhenActiveEvent, 192
VariantIsISNotify
v5IntfId, v5VariantId,
v5DLCPathId
The V5.2 Interfaces variant
Data Link cannot be deleted
when the active variant is in
service, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table, and
v5DLCPathId identifies Data
Link configuration table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-39
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
v5DspOverSubscr System
iptionExceeded- Event, 68
Notify
System
Indicator
Information
MIB Object Name
Trap Description
v5TargetDspOverSubscr
iption,
v5CurrentDspOverSubs
cription
The DSP oversubscription of
calls per channel for V5.2
voice calls has exceeded the
maximum user assigned
oversubscription limitation.
Possible Cause: A new configuration to a DSP resource(s) or a DSP resource
chip/module failure.
Corrective Action: Add new DSP module(s) or replace the failed module(s) and
re-assign the DSP selection type from the Site Specific Menu on the DSP Resource
Management Table at a time when the number of voice calls through the chassis
are at a minimum. This will help in lowering the oversubscription calls per channel to the desired level.
v5E1LinkCantBe Interface
Information
DeletedWhenAd- Event, 190
minISNotify
v5IntfId, v5VariantId,
v5E1LinkId
The V5.2 Interfaces variant
E1 link cannot be deleted
when admin status is in service, where v5IntfId identifies the V5.2 Interface configuration table, v5VariantId
identifies the variant table,
and v5E1LinkId identifies
the E1 Link configuration
table.
v5E1LinkCantBeT Interface
Information
akenOOSWhen- Event, 189
ActiveVariantIsISNotify
v5IntfId, v5VariantId,
v5E1LinkId
The V5.2 Interfaces variant
E1 link cannot be taken out
of service when the interface is in service, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5E1LinkId identifies the E1
Link configuration table.
v5E1LinkOperInS Interface
Information
erviceNotify
Event, 171
v5IntfId, v5VariantId,
v5E1LinkId
The V5.2 E1 Links operational status coming in service, where v5IntfId identifies the V5.2 Interface
configuration table,
v5VariantId refers to the
active variant, and
v5E1LinkId identifies the E1
link table
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-40
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5E1LinkOperOu Interface
Information
tOfServiceNotify Event, 170
v5IntfId, v5VariantId,
v5E1LinkId
The V5.2 E1 Links operational status going out of
service, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId refers to the
active variant, and
v5E1LinkId identifies the E1
link table.
v5InterfaceAdmin Interface
Information
InServiceNotify
Event, 139
v5IntfId
The V5.2 Interfaces Administrative status coming in
service, where v5IntfId
identifies the V5.2 Interface
configuration table.
v5InterfaceAdmin Interface
Information
OutOfServiceNo- Event, 138
tify
v5IntfId
The V5.2 Interfaces Administrative status going out of
service, where v5IntfId
identifies the v5Interface
configuration table.
v5InterfaceCantB Interface
Information
eBroughtEvent, 197
ISWhenActiveVariantIsOOS
v5IntfId
The V5.2 Interface cannot be
brought into service when
the active variant is out of
service, where v5IntfId
identifies the V5.2 Interface
configuration table.
v5InterfaceCreate Interface
Information
dNotify
Event, 133
v5IntfId
The V5.2 Interface has been
successfully created, where
v5IntfId identifies the V5.2
Interface configuration
table.
v5InterfaceCreate Interface
Information
FailNotify
Event, 134
v5IntfId, interfaceFailureReasonCode
An attempt to create a V5.2
interface has failed.
v5InterfaceDelete Interface
Information
Notify
Event, 136
v5IntfId
The V5.2 Interface has been
deleted, where v5IntfId
identifies the V5.2 Interface
configuration table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-41
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceDLCre Interface
Information
atedNotify
Event, 162
v5IntfId, v5VariantId,
v5DLCPathId
v5InterfaceDLCre Interface
Information
ateFailNotify
Event, 163
v5IntfId, v5VariantId,
An attempt to create the
v5DLCPathId, interface- Data Link in the V5.2 InterFailureReasonCode
faces variant has failed,
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table, and
v5DLCPathId identifies the
Data Link configuration
table. v5IntfDLAlreadyExists
- Data Link already exists
v5InterfaceDLDel Interface
Information
eteNotify
Event, 164
v5IntfId, v5VariantId,
v5DLCPathId
The Data Link has been
deleted from the V5.2 Interfaces variant, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table, and
v5DLCPathId identifies the
Data Link configuration
table.
v5InterfaceE1Lin
kAddedNotify
v5IntfId, v5VariantId,
v5E1LinkId
The E1 Link has been successfully added to the V5.2
Interface, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table, and
v5E1LinkId identifies the E1
Link configuration table.
Interface
Information
Event, 145
The successful creation of
Data Link to the V5.2 Interfaces variant has occurred,
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table, and
v5DLCPathId identifies the
Data Link configuration
table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-42
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
v5InterfaceE1Lin
kAddFailNotify
Interface
Information
Event, 146
v5IntfId, v5VariantId,
v5E1LinkId, interfaceFailureReasonCode
An attempt to add an E1
link has failed, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5E1LinkId identifies the E1
Link configuration table.
v5IntfE1LinkAlreadyExistsE1 Link already exists,
v5IntfE1LinkCantBeZeroE1 Link Phys Id cannot be
zero,
v5IntfE1LinkChanMustBeO
ne- E1 Link Phys Id must
end with one.
v5InterfaceE1Lin
kBlockedNotify
Interface
Information
Event, 154
v5IntfId, v5VariantId,
v5E1LinkId
Blocking of the V5.2 Interfaces variants E1 Link has
been successful, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5E1LinkId identifies E1
Link configuration table.
v5IntfId, v5VariantId,
v5E1LinkId, interfaceFailureReasonCode
An attempt to delete an E1
link has failed, where
v5IntfId identifies the v5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5E1LinkId identifies the E1
link configuration table.
v5InterfaceOperStatusOOSThe V5 interface admin status is in service but the oper
status is OOS,the user port
cannot be added/deleted.
However, the user port can
be added/deleted after the
admin status is taken OOS.
System
Indicator
v5InterfaceE1Lin Interface
Information
kDeleteFailNotify Event, 209
MIB Object Name
Trap Description
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-43
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
v5InterfaceE1Lin
kDeleteNotify
Interface
Information
Event, 147
System
Indicator
MIB Object Name
Trap Description
v5IntfId, v5VariantId,
v5E1LinkId
An E1Link has been deleted
from the variant, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5E1LinkId identifies the E1
Link configuration table.
v5InterfaceE1Lin Interface
Information
kModifyFailNotify Event, 153
v5IntfId, v5VariantId,
v5E1LinkId, interfaceFailureReasonCode
An attempt to modify one of
the parameters to V5.2
Interfaces variants E1 Link
has failed, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table, and
v5E1LinkId identifies E1
Link configuration table.
v5IntfE1LinkInService - E1
Link in service
v5InterfaceE1Lin
kUnBlockedNotify
v5IntfId, v5VariantId,
v5E1LinkId
The V5.2 Interfaces variants
E1 Link has been successfully unblocked, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5E1LinkId identifies the E1
Link configuration table.
Interface
Information
Event, 155
v5InterfaceLogCC Interface
Information
hanCreatedNotify Event, 159
v5IntfId, v5VariantId,
The logical C-channel has
v5LogCChanCommCCh been successfully added to
anId
the V5.2 Interfaces variant,
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table, and
v5LogCChanCommCChanId
identifies the Logical
CChannel configuration
table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-44
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceLogCC Interface
Information
hanCreateFailNo- Event, 160
tify
v5IntfId, v5VariantId,
v5LogCChanCommCCh
anId, interfaceFailureReasonCode
An attempt to create the logical C-channel in V5.2 Interfaces variant has failed,
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table, and
v5LogCChanCommCChanId
identifies the Logical Cchannel configuration table.
v5IntfLogCChanAlreadyExis
ts - Logical C-channel
already exists
v5InterfaceLogCC Interface
Information
hanDeleteNotify Event, 161
The logical C-channel has
v5IntfId, v5VariantId,
v5LogCChanCommCCh been deleted from the V5.2
Interfaces variant, where
anId
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5LogCChanCommCChanId
identifies the Logical Cchannel configuration table.
v5InterfaceModif Interface
Information
yFailNotify
Event, 137
v5IntfId, interfaceFailureReasonCode
An attempt to modify the
V5.2 Interface has failed,
where v5IntfId identifies the
V5.2 Interface configuration
table. interfaceInServiceIntf already in service.
v5InterfaceModifi Interface
Information
edNotify
Event, 135
v5IntfId
The V5.2 Interface parameters have been successfully
modified, where v5IntfId
identifies the v5Interface
configuration table.
v5InterfaceOperI
nServiceNotify
Interface
Information
Event, 169
v5IntfId
The V5.2 Interfaces operational status has come into
service, where v5IntfId
identifies the V5.2 Interface
configuration table.
v5InterfaceOperO Interface
Information
utOfServiceNotify Event, 168
v5IntfId
The V5.2 Interfaces operational status has gone out of
service, where v5IntfId
identifies the V5.2 Interface
configuration table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-45
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfacePhysC Interface
Information
ChanCreatedNo- Event, 156
tify
v5IntfId, v5VariantId,
v5PhysCChan
The physical C-channel has
been successfully added to
the V5.2 Interfaces variant,
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table, and
v5PhysCChan identifies the
Physical C-channel configuration table.
v5InterfacePhysC Interface
Information
ChanCreateFail- Event, 157
Notify
v5IntfId, v5VariantId,
An attempt to create the
v5PhysCChan, interphysical C-channel in the
faceFailureReasonCode V5.2 Interfaces variant has
failed. Where v5IntfId identifies the V5.2 Interface configuration table, v5VariantId
identifies the variant table,
and v5PhysCChan identifies
the Physical C-channel configuration table.
v5IntfLogCChanAlreadyExis
ts - Logical C-channel corresponding to this Physical Cchannel already exists,
v5IntfPhysCChanAlreadyEx
ists - Physical C-channel
already exists,
v5IntfPhysCChanCantBeZer
o - Physical C-channel cannot end with zero,
v5IntfPhysCChanMustBeEit
her16Or15Or31 - Physical
C-channel must be either
16, 15, or 31.
v5InterfacePhysC Interface
Information
ChanDeleteNotify Event, 158
v5IntfId, v5VariantId,
v5PhysCChan
The physical C-channel has
been deleted from the V5.2
Interfaces variant, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5PhysCChan identifies the
Physical C-channel configuration table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-46
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceProtect Interface
Information
ionSwitchoverEvent, 151
Failed
v5IntfId,
The protection switchover
v5LogCChanCommCCh command initiated either by
anId, v5PhysCChan
AN or LE has failed, where
v5IntfId identifies the V5.2
Interface configuration
table,
v5LogCChanCommCChanId
identifies the V5.2 Logical Cchannel table, v5PhysCChan
identifies the physical Cchannel to be switched.
v5InterfaceProtect Interface
Information
ionSwitchoverNo- Event, 150
tify
v5IntfId,
The protection switchover
v5LogCChanCommCCh command initiated either by
anId, v5PhysCChan
AN or LE has been successfully executed, where
v5IntfId identifies the V5.2
Interface configuration
table,
v5LogCChanCommCChanId
identifies the V5.2 Logical Cchannel table, v5PhysCChan
identifies the physical Cchannel to be switched.
v5InterfaceUserPo Interface
Information
rtActivatedNotify Event, 185
v5IntfId, v5VariantId,
The V5.2 Interfaces ISDN
v5IntfUserPortLEPortId port has been activated,
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table, and
v5IntfUserPortLEPortId
identifies the User Port configuration table.
v5InterfaceUserPo Interface
Information
rtActivationIniti- Event, 186
atedNotify
v5IntfId, v5VariantId,
The V5.2 Interfaces ISDN
v5IntfUserPortLEPortId port activation has been initiated, where v5IntfId identifies the V5.2 Interface configuration table, v5VariantId
identifies the variant table,
and v5IntfUserPortLEPortId
identifies the User Port configuration table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-47
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceUserPo Interface
Information
rtAddedNotify
Event, 165
v5IntfId, v5VariantId,
The User Port has been sucv5IntfUserPortType,
cessfully added to the V5.2
v5IntfUserPortLEPortId Interfaces variant, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table,
v5IntfUserPortLEPortId
identifies the User Port configuration table, and
v5IntfUserPortType identifies the user port table
whether it is PSTN or ISDN
port.
v5InterfaceUserPo Interface
Information
rtAddFailNotify
Event, 166
v5IntfId,
v5VariantId,v5IntfUserP
ortType,
v5IntfUserPortLEPortId,
interfaceFailureReasonCode
An attempt to add the User
Port into the V5.2 Interfaces
variant has failed, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table,
v5IntfUserPortLEPortId
identifies the User Port configuration table,
v5IntfUserPortType identifies the user port table
whether it is a PSTN or ISDN
port.
v5IntfUserPortInvalidTrunk
VccId - Invalid trunk vcc id
v5IntfUserPortInvalidIwfId Invalid IWF id,
v5IntfUserPortDuplicateLesP
ortId - Duplicate LES port id,
v5IntfUserPortDuplicateLes
Cid - Duplicate LES CID,
v5IntfUserPortAlreadyExists
- User port already exists
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-48
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceUserPo Interface
Information
rtBlockedNotify
Event, 172
v5IntfId, v5VariantId,
The V5.2 Interfaces port is
v5IntfUserPortType,
being blocked, where
v5IntfUserPortLEPortId v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table,
v5IntfUserPortLEPortId
identifies User Port configuration table, and
v5IntfUserPortType identifies the user port table
whether it is PSTN or ISDN
port.
v5InterfaceUserPo Interface
Information
rtDeleteFailNotify Event, 200
v5IntfId, v5VariantId,
v5IntfUserPortType,
v5IntfUserPortLEPortId,
interfaceFailureReasonCode
This notification is the result
of a failure to add the user
port in the V5.2 Interface’s
variant. Where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table,
v5IntfUserPortLEPortId
identifies User Port configuration table,
v5IntfUserPortType identifies the user port table
whether it is a PSTN or ISDN
port. interfaceFailureReasonCode: previousUserPortDelIsInProgress(100)- previous deletion in progress.
UserPortDeletionBegin(101)- begin to send
deallocate ti IAD.UserPortDelFailDueToDeAllocationFail(102)- deallocate failed.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-49
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceUserPo Interface
Information
rtDeleteNotify
Event, 167
v5IntfId, v5VariantId,
The User Port has been
v5IntfUserPortType,
deleted from the V5.2 Interv5IntfUserPortLEPortId faces variant, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table,
v5IntfUserPortLEPortId
identifies the User Port configuration table,
v5IntfUserPortType identifies the user port table
whether it is a PSTN or ISDN
port.
Information
v5InterfaceUserPo Interface
rtUnblockDeact- Event, 184
Notify
v5IntfId, v5VariantId, The V5.2 Interfaces ISDN
v5IntfUserPortLEPortId port has been deactivated,
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table, and
v5IntfUserPortLEPortId
identifies the User Port configuration table.
Information
v5InterfaceUserPo Interface
rtUnBlockedNo- Event, 173
tify
The V5.2 Interfaces port is
v5IntfId, v5VariantId,
unblocked, where v5IntfId
v5IntfUserPortType,
v5IntfUserPortLEPortId identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table,
v5IntfUserPortLEPortId
identifies User Port configuration table, and
v5IntfUserPortType identifies the user port table
whether it is a PSTN or ISDN
port.
v5InterfaceVarian Interface
Information
tAddedNotify
Event, 140
v5IntfId, v5VariantId
A variant has been successfully added to the V5.2
Interface, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-50
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceVarian Interface
Information
tAddFailNotify
Event, 141
v5IntfId, v5VariantId,
An attempt to add a variant
interfaceFailureReason- has failed, where v5IntfId
Code
identifies the V5.2 Interface
configuration table and
v5VariantId identifies the
variant table.
v5IntfVariantAlreadyExists Variant already exists
v5InterfaceVarian Interface
Information
tDeleteNotify
Event, 142
v5IntfId, v5VariantId
A variant has been deleted
from the V5.2 interface,
where v5IntfId identifies the
V5.2 Interface configuration
table and v5VariantId identifies the variant table.
v5InterfaceVarian Interface
Information
tInServiceNotify Event, 144
v5IntfId, v5VariantId
The V5.2 Interfaces variant
is in service, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table.
v5InterfaceVarian Interface
Information
tModifyFailNotify Event, 152
v5IntfId, v5VariantId,
An attempt to modify one of
interfaceFailureReason- the parameters in V5.2
Interfaces variant has failed,
Code
where v5IntfId identifies the
V5.2 Interface configuration
table, v5VariantId identifies
the variant table.
v5IntfVariantInService Variant is already in service
v5InterfaceVarian Interface
Information
tOutOfServiceNo- Event, 143
tify
v5IntfId, v5VariantId
The V5.2 Interfaces variant
is out of service, where
v5IntfId identifies the V5.2
Interface configuration table
and v5VariantId identifies
the variant table.
v5InterfaceVarian Interface
tSwitchoverFailed Event
149
v5IntfId, v5VariantId
A failure of the variant
switchover command initiated either by AN or LE has
occurred, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table.
Information
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-51
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceVarian Interface
Information
tSwitchoverNotify Event, 148
v5IntfId, v5VariantId
The variant switchover command initiated either by AN
or LE has been successfully
executed, where v5IntfId
identifies the V5.2 Interface
configuration table,
v5VariantId identifies the
variant table.
v5LesInterfaceOu Interface
Information
tOfServiceNotify Event, 174
v5LesIntfIwfId,
v5LesIntfTrunkId
The LES Interfaces operational status is out of service,
where v5LesIntfIwfId identifies the Remote IWF Id and
v5LesIntfTrunkId identifies
the Trunking Vcc Id.
v5LesInterfaceInS Interface
Information
erviceNotify
Event, 175
v5LesIntfIwfId,
v5LesIntfTrunkId
The LES Interfaces operational status is in service,
where v5LesIntfIwfId identifies the Remote IWF Id and
v5LesIntfTrunkId identifies
the Trunking Vcc Id.
v5PhysCChanCan Interface
Information
tBeDeletedWhen- Event, 191
ActiveVariantIsISNotify
v5IntfId, v5VariantId,
v5PhysCChan
The V5.2 Interfaces variants
physical C-Channel cannot
be deleted when the active
variant is in service, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table, and
v5PhysCChan identifies the
Physical C-Channel configuration table.
v5InterfaceUserPo Interface
Information
rtBccFailNotify
Event, 201
v5IntfId, v5VariantId,
v5IntfUserPortType,
v5IntfUserPortLEPortId,
v5UserPortBCCFailureR
easonCode
The result of failure of allocating a channel in a V5.2
LES Interface. Where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant
table,v5IntfUserPortLEPortI
d identifies User Port configuration table,
v5IntfUserPortType identifies the user port table
whether it is a PSTN or ISDN
port.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-52
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
v5InterfaceUserPo Interface
Information
rtDeleteBeginNo- Event, 202
tify
v5IntfId, v5VariantId,
v5IntfUserPortType,
v5IntfUserPortLEPortId,
v5UserPortBCCFailureR
easonCode
The result of Failure to Deallocate a Chan in the User
Port in the V5.2 LES Interface. Where v5IntfId identifies the V5.2 Interface configuration table, v5VariantId
identifies the variant table,
v5IntfUserPortLEPortId
identifies User Port configuration table,
v5IntfUserPortType identifies the user port table
whether it is PSTN or ISDN
port.
v5UserPortCantB Interface
Information
eDeleteWhenPor- Event, 198
tIsNotBlockedNotify
v5IntfId, v5VariantId,
The V5.2 Interfaces port
cannot be deleted when the
v5IntfUserPortType,
v5IntfUserPortLEPortId port is not blocked, where
v5IntfId identifies the V5.2
Interface configuration
table, v5VariantId identifies
the variant table,
v5IntfUserPortLEPortId
identifies the user port configuration table,
v5IntfUserPortType identifies the user port table
whether it is PSTN or ISDN
port.
v5VariantCantBe Interface
Information
DeletedWhenAd- Event, 188
minISNotify
v5IntfId, v5VariantId
The V5.2 Interfaces Variant
cannot be deleted when the
variant is in service, where
v5IntfId identifies the V5.2
Interface configuration
table, and v5VariantId identifies the variant table.
v5VariantCantBe Interface
Information
DeletedWhenE1Li Event, 193
nkIsISNotify
v5IntfId, v5VariantId
The V5.2 Interfaces variant
cannot be deleted when E1
links are still unblocked,
where v5IntfId identifies the
V5.2 Interface configuration
table, and v5VariantId identifies the variant table.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-53
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
vbrAtmBkPvcVc- ConnecResponse
cReqFailNotify
tion Event,
39
vbrAtmPvcVccIfA,
vbrAtmPvcVccIfB,
vbrAtmPvcVccVpiB,
vbrAtmPvcVccVciB,
pvcFailureReasonCode
The DHPVC VCC backup
connection request between
a variable-bit rate interface
and an ATM interface has
failed.
vbrAtmBkPvcVccSetupNotify
ConnecResponse
tion Event,
40
vbrAtmPvcVccIfA,
vbrAtmPvcVccIfB,
vbrAtmPvcVccVpiB,
vbrAtmPvcVccVciB
The DHPVC VCC backup
connection between a variable-bit rate interface and an
ATM interface has been created.
vbrAtmBkPvcVcc- ConnecResponse
TearDownNotify tion Event,
41
vbrAtmPvcVccIfA,
vbrAtmPvcVccIfB,
vbrAtmPvcVccVpiB,
vbrAtmPvcVccVciB
The DHPVC VCC backup
connection between a variable-bit rate interface and an
ATM interface has been
deleted.
vbrAtmPvcVccReqFailNotify
ConnecResponse
tion Event,
5
vbrAtmPvcVccIfA,
vbrAtmPvcVccIfB,
vbrAtmPvcVccVpiB,
vbrAtmPvcVccVciB,
pvcFailureReasonCode
The PVC VCC connection
request between a variablebit rate interface and an
ATM interface has failed.
vbrAtmPvcVccSetupNotify
ConnecResponse
tion Event,
14
vbrAtmPvcVccIfA,
vbrAtmPvcVccIfB,
vbrAtmPvcVccVpiB,
vbrAtmPvcVccVciB
The PVC VCC connection
between a variable-bit rate
interface and an ATM interface has been successfully
established.
vbrAtmPvcVccTe- ConnecResponse
arDownNotify
tion Event,
23
vbrAtmPvcVccIfA,
vbrAtmPvcVccIfB,
vbrAtmPvcVccVpiB,
vbrAtmPvcVccVciB
The PVC VCC connection
between a variable-bit rate
interface and an ATM interface has been torn down.
vbrAtmSpvcCon- Interface
figFailNotify
Event, 76
Information
spvcAddrIfA, vbrAtmSpvcRemoteVbrPortAddr, spvcConfigFailureCode
An attempt to configure an
endpoint as a TE SPVC endpoint has failed.
vbrAtmSpvcCon- Interface
figuredNotify
Event, 75
Information
spvcAddrIfA, vbrAtmSpvcRemoteVbrPortAddr
The endpoint has been configured as a TE SPVC endpoint.
vbrAtmSpvcDeletedNotify
Interface
Event, 77
Information
spvcAddrIfA, vbrAtmSpvcRemoteVbrPortAddr
A TE SPVC configuration
has been deleted.
vbrAtmSpvcSetUpNotify
ConnecResponse
tion Event,
71
spvcAddrIfA, vbrAtmSpvcRemoteVbrPortAddr, vbrAtmSpvcIfB,
vbrAtmSpvcVpiB,
vbrAtmSpvcVciB
The specified SPVC connection between TE and ATM
endpoints has been successfully established.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-54
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
vbrAtmSpvcTear- ConnecResponse
DownNotify
tion Event,
72
spvcAddrIfA, vbrAtmSpvcRemoteVbrPortAddr, vbrAtmSpvcIfB,
vbrAtmSpvcVpiB,
vbrAtmSpvcVciB
The specified SPVC connection between TE and ATM
endpoints has been torn
down.
vbrAtmConnecResponse
SpvcVccSetUpNo- tion Event,
tify
58
vbrAtmSpvcVccIfA,
vbrAtmSpvcVccIfB,
vbrAtmSpvcVccVpiB,
vbrAtmSpvcVccVciB
The specified SPVC connection between TE and ATM
endpoints has been successfully established.
vbrAtmSpvcVccTearDownNotify
ConnecResponse
tion Event,
61
vbrAtmSpvcVccIfA,
vbrAtmSpvcVccIfB,
vbrAtmSpvcVccVpiB,
vbrAtmSpvcVccVciB
The specified SPVC connection between TE and ATM
endpoints has been torn
down.
vbrSpvcConfigFailNotify
Interface
Event, 26
Information
interfaceIndex, spvcCo- An attempt to configure the
nfigFailureCode
endpoint as a TE SPVC endpoint has failed.
vbrSpvcConfiguredNotify
Interface
Event, 25
Information
interfaceIndex
The endpoint has been configured as a TE SPVC endpoint.
vbrSpvcDeletedNotify
Interface
Event, 27
Information
interfaceIndex
A TE SPVC configuration
has been deleted.
vbrVbrPvcReqFailNotify
Response
Connection Event,
9
vbrVbrPvcIfA,
vbrVbrPvcIfB, pvcFailureReasonCode
The PVC connection request
between two variable-bit
rate interfaces has failed.
vbrVbrPvcSetupNotify
ConnecResponse
tion Event,
18
vbrVbrPvcIfA,
vbrVbrPvcIfB
The PVC connection
between two variable-bit
rate interfaces has been successfully established.
vbrVbrPvcTearDownNotify
ConnecResponse
tion Event,
27
vbrVbrPvcIfA,
vbrVbrPvcIfB
The PVC connection
between two variable-bit
rate interfaces has been torn
down.
versionConfigura- System
tionNotify
Event, 23
Information
versionConfigurationReasonCode
The completion status of the
upgrade or downgrade.
viprArpTrap
Interface
Event, 45
Information
viprSlot, viprRouterId,
arpStatus
The Vipr Task is notifying
Network Management of
the disposition of a previous
ARP Table Request.
viprIpIntfTrap
Interface
Event, 48
Information
viprSlot, viprRouterId,
viprIntfId, ipIntfStatus
The success or failure of IP
Network Interface level
operations.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-55
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
System
Indicator
MIB Object Name
Trap Description
viprPingTrap
Interface
Event, 44
Information
viprSlot, viprRouterId,
ipAddrNumber, pingStatusReasonCode
The Vipr Task is notifying
Network Management of
the disposition of a previous
Ping Request.
viprRoutingTrap
Interface
Event, 46
Information
viprSlot, viprRouterId,
routingStatus
The Vipr Task is notifying
Network Management of
the disposition of a previous
Routing Table Request.
viprRtSrvTrap
Interface
Event, 50
Information
cardSlot, routeSrvStatus The success or failure of Vipr
(Route Server) operations.
viprStatRtTrap
Interface
Event, 54
Information
viprSlot, viprRouterId,
viprRouteId, statRtStatus
The success or failure of
Static Route operations.
viprSubChanTrap Interface
Event, 49
Information
viprSlot, viprRouterId,
viprIntfId, viprSubChnlId, subChanStatus
The success or failure of Sub
Channel level operations.
viprVpnTrap
Interface
Event, 47
Information
viprSlot, viprRouterId,
vpnTrapStatus
The success or failure of VPN
level operations.
virtualIntfCreatedNotify
Interface
Event, 56
Response
virtualIntfConfigIf, virtualIntfConfigVi
The VI has been successfully
created.
virtualIntfDeleteNotify
Interface
Event, 58
Response
virtualIntfConfigIf, virtualIntfConfigVi
The VI has been deleted.
virtualIntfModifiedNotify
Interface
Event, 57
Response
virtualIntfConfigIf, virtualIntfConfigVi
The VI has been modified.
virtualIntfModify- Interface
FailNotify
Event, 59
Response
virtualIntfConfigIf, virtualIntfConfigVi, pvcFailureReasonCode
An attempt to modify the VI
has failed. Overload pvcFailureReasonCode.
virtualUNIIntfCreateFailNotify
Interface
Event, 81
Information
virtualUNIIfIndex, vir- An attempt to create an
tualUNIVUNIId, inter- interface has failed.
faceFailureReasonCode
virtualUNIIntfCreatedNotify
Interface
Event, 80
Response
virtualUNIIfIndex, virtualUNIVUNIId
A virtual UNI has been successfully created.
virtualUNIIntfDeleteNotify
Interface
Event, 83
Response
virtualUNIIfIndex, virtualUNIVUNIId
A virtual UNI has been
deleted.
virtualUNIIntfInServiceNotify
Interface
Event, 86
Information
virtualUNIIfIndex, virtualUNIVUNIId
A virtual UNI is in service.
virtualUNIIntfModifiedNotify
Interface
Event, 82
Response
virtualUNIIfIndex, virtualUNIVUNIId
A virtual UNI has been modified.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-56
255-700-506
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
Table 3-1. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued)
Enterprise-Specific
Trap Name
Trap Group
ID and Trap
Index
Number
virtualUNIIntfModifyFailNotify
Interface
Event, 84
System
Indicator
MIB Object Name
Trap Description
Response
virtualUNIIfIndex, vir- An attempt to modify the
tualUNIVUNIId, inter- Vitual UNI has failed. OverfaceFailureReasonCode load interfaceFailureReasonCode.
Information
virtualUNIIfIndex, virtualUNIVUNIId
A virtual UNI is out of service.
atmVpcPnniIfIndex,
atmVpcPnniVpcId,
interfaceFailureReasonCode
An attempt to create a VPC
interface has failed. See
interfaceFailureReasonCode
for details.
vpcPnniIntfCreat- Interface
Response
edNotify
Event, 233
atmVpcPnniIfIndex,
atmVpcPnniVpcId
A VPC interface has been
created.
vpcPnniIntfDeleteNotify
atmVpcPnniIfIndex,
atmVpcPnniVpcId
A VPC interface has been
deleted.
vpcPnniIntfInSer- Interface
Information
viceNotify
Event, 239
atmVpcPnniIfIndex,
atmVpcPnniVpcId
The VPC is in service.
vpcPnniIntfModi- Interface
Response
fyFailNotify
Event, 237
atmVpcPnniIfIndex,
atmVpcPnniVpcId,
interfaceFailureReasonCode
An attempt to modify a VPC
interface has failed. See
interfaceFailureReasonCode
for details.
vpcPnniIntfModi- Interface
Response
fiedNotify
Event, 235
atmVpcPnniIfIndex,
atmVpcPnniVpcId
A VPC interface has been
modified.
vpcPnniIntInterface
Information
fOutOfServiceNo- Event, 238
tify
atmVpcPnniIfIndex,
atmVpcPnniVpcId
The VPC is out of service.
virtualUNIIntInterface
fOutOfServiceNo- Event, 85
tify
vpcPnniIntfCreateFailNotify
Interface
Information
Event, 234
Interface
Response
Event, 236
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
3-57
Chapter 3 Trap Message Descriptions
Trap Names and Descriptions
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
3-58
255-700-506
4
MIB Objects
Purpose of this Chapter
The following is a list of definitions for the MIB objects that are associated
with the SNMP enterprise-specific trap names. Following each MIB object are
all trap messages and enumerated types that are associated with that specific
object. This list is provided in alphabetical order.
MIB Object Detailed Descriptions
aal2CirAtmSpvcVccIfA
The interface index for side A - the circuit emulation side of a circuit emulation-ATM SPVC
trunking VCC connection. The number value is interpreted as an interface of the form, SSPPCCC,
where SS is the module slot, PP is the port number, and CCC is the channel number.
Associated Traps - aal2CirAtmSpvcVccEntry, aal2CirAtmSpvcVccConfiguredNotify,
aal2CirAtmSpvcVccConfigFailNotify, aal2CirAtmSpvcDeletedNotify,
aal2CirAtmSpvcVccSetUpNotify, aal2CirAtmSpvcVccTearDownNotify,
aal2VbrAtmSpvcVccTearDownNotify
aal2SpvcConfigFailureCode
An identified reason for failure while configuring AAL2 SPVC parameters. The valid range is a
number between 1 and 16.
See Table 4-1 for a mapping between numbers and their enumerated types.
Associated Traps - aal2CirAtmSpvcVccConfigFailNotify, aal2VbrAtmSpvcVccConfigFailNotify
Table 4-1. AAL2 Configure Failure Codes
Number
Value
Enumerated Type
Description
1
generalErrorUnspecified
All other unspecified failure causes.
2
interfaceNotConfiguredAsRequired
The SPVC end point is configured as something
other than CE/TE.
3
pvcAlreadySetupOnInterface
The PVC/SPVC is already setup on the interface.
4
rmtIWFIdOutOfRange
The identifier for the remote IWF is out of range.
5
vccIdError
The VCC ID for the trunk is 0,or this VCC ID is out
of range.
6
cidError
The CID for the trunk or this VCC ID is out of range
or used by someone else.
7
requiredFieldMissing
Mandatory fields are missing.
8
outOfResource
The ATM trunking task or system is out of resources
for this configuration.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-1
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-1. AAL2 Configure Failure Codes (Continued)
Number
Value
Enumerated Type
Description
9
rowStatusError
A Row Status Error occurred with the SNMP command.
10
cePortToTrunkMappingError
There has been a violation to the restrictions of the
mapping between CE port and AAL2 Trunk.
11
trunkBandWidthNotEnough
Insufficient bandwidth on the trunk.
12
trafficParametersNotAcceptable
The combination of traffic parameters are not
acceptable.
13
dspParametersNotAcceptable
The combination of DSP parameters are not acceptable.
14
trunkNotConfiguredAsRequired
The trunk is not configured or is configured incorrectly.
15
dspResourcesUnavailable
The DSP resources have not been allocated or are
unavailable.
16
spvcAlreadySetupOnInterface
An SPVC endpoint has already been setup on the
interface.
aal2TrunkConfigIf
The Interface ID of the ATM side of the AAL2 Trunk.
Associated Traps - aal2TrunkConfigSetupNotify, aal2TrunkConfigTearDownNotify,
aal2TrunkConfigReqFailNotify
aal2TrunkConfigVci
The VCI value for the ATM side of a variable bit rate-ATM PVC VCC connection. The valid range
is a number between 0 and 65535.
Associated Traps - aal2TrunkConfigSetupNotify, aal2TrunkConfigTearDownNotify,
aal2TrunkConfigReqFailNotify
aal2TrunkConfigVpi
The VPI value for the ATM side of an ATM trunk connection. The valid range is a number
between 0 and 4095.
Associated Traps - aal2TrunkConfigSetupNotify, aal2TrunkConfigTearDownNotify,
aal2TrunkConfigReqFailNotify
aal2VbrAtmSpvcVccIfA
The interface index for side A - the VBR(HDLC) side of an AAL2 VBR - ATM SPVC VCC connection. The value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - aal2VbrAtmSpvcVccEntry, aal2VbrAtmSpvcVccConfiguredNotify,
aal2VbrAtmSpvcVccConfigFailNotify, aal2VbrAtmSpvcDeletedNotify,
aal2VbrAtmSpvcVccSetUpNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-2
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
activeStratum
The current status of the backup Stratum module. The valid range is a number between 1 and 2.
See Table 4-2 for a mapping between numbers and their enumerated type.
Associated Traps - stratumActivitySwitchOverNotify
Table 4-2. Active Stratum Codes
Number
Value
Enumerated Type
Description
1
stratumA
Stratum A is active
2
stratumB
Stratum B is active
alarmCardReasonCode
The configuration status of alarm inputs and outputs. Cutoff indicates that the alarm is turned off.
There are two ways to turn off the audible alarm, locally via the pushbutton switch on the alarm
module, and remotely, via the remote alarm cutoff, one of the alarm module inputs. The valid
range is a number between 1 and 8.
See Table 4-3 for a mapping between numbers and their enumerated types.
Associated Traps - alarmCardAcoChangeNotify, alarmCardInputChangeNotify, alarmCardOutputChangeNotify
Table 4-3. Alarm Module Reason Codes
Number
Value
Enumerated Type
Description
1
inputContactClosed
The state of the remote status input changed to Closed.
2
inputContactOpen
The state of the remote status input changed to Open.
3
outputActivated
A control output was set to Activated on the Alarm
Module Configuration window.
4
outputDeactivated
A control output was set to Deactivated on the Alarm
Module Configuration window.
5
audibleLocalAlarmEnable
The audible alarm has been enabled locally.
6
audibleLocalAlarmCutoff
The audible alarm was silenced by pressing the ACO
button on the faceplate of the module.
7
audibleRemoteAlarmEnable
The audible alarm has been enabled remotely.
8
audibleRemoteAlarmCutoff
The audible alarm was silenced by an external contact
closure input at a remote location.
ambientTemperature
The ambient temperature in degree Celsius where the system is kept.
Associated Traps - ambientTemperatureChangeNotify
apsFailureReasonCode
The identified reason of failure for automatic protection switching. The valid range is a number
between 1 and 10.
See Table 4-4 for a mapping between numbers and their enumerated type.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-3
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - apsConfigurationModifyFailNotify
Table 4-4. APS Failure Reason Codes
Number
Value
Enumerated Type
Description
1
protectionCard-notPresent
The protection module does not exist.
2
protectionCardType-notAPS
The protection module type is not APS.
3
protectionCardType-incompatible
The protection module and working module
types are incompatible.
4
protectionCard-notInUnconfiguredState The protection module is already configured.
5
protectionCard-notUnprotected
The protection module is not unprotected.
6
resource-access-failure
An internal failure application occurred.
7
incorrect-APSconfiguration
Correct APS configuration: 1)ocxAPSConfiguration of working port is working and ocxAPSConfiguration of protection port is protection.
2)ocxAPSConfiguration of working and protection ports are unprotected.
8
protectionPort-Active
The protection port must be active when breaking an APS pair.
9
workingPort-localLoop-notAllowed
The working port cannot be configured as local
loop.
10
protectionPort-localLoop-notAllowed
The protection port cannot be configured as
local loop.
arpStatus
The status of Address Resolution Protocol (ARP). The valid range is a number between 1 and 3.
See Table 4-5 for a mapping between numbers and their enumerated type.
Associated Traps - viprArpTrap
Table 4-5. ARP Status Codes
Number
Value
Enumerated Type
Description
1
success
ARP data is Available.
2
noArpEntries
There are no more ARP entries.
3
tryAgain
The request was not honored as it came too soon
(within 1 second). Try again after 1 second and a message will be returned of either Success or Noroutes.
atafDir
Determines which direction should be monitored. The valid range is a number between 1 and 3.
See Table 4-6 for a mapping between numbers and their enumerated type.
Associated Traps - atafConvertNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-4
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-6. ATAF Direction Monitoring Codes
Number
Value
Enumerated Type
Description
1
bothSides
Both directions will be monitored and both input side and output
side monitoring parameters are needed.
2
input
Only the side going into the port toward the backplane is monitored. Only the input side monitoring parameters are needed.
3
output
Only the side going away from the port and away from the backplane is monitored. Only the output side monitoring parameters are
needed.
atafVci
The VCI value for the ATM side of an ATM PVC connection. The valid range is a number between
0 and 65535.
Associated Traps - atafConvertNotify
atafVpi
The VPI value for the ATM side of an ATM PVC connection. The valid range is a number between
0 and 4095.
Associated Traps - atafConvertNotify
atafIf
An interface index for the ATM side of an ATM PVC connection. The number value is interpreted
as an interface of the form, SSPPCCC, where SS is the slot, PP is the port number, and CCC is the
channel number.
Associated Traps - atafConvertNotify
atmAtmSpvcVccIfB
The interface index for side B of an ATM SPVC VCC connection. Number value is interpreted as
an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC
is the channel number.
Associated Traps - atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify
atmAtmSpvcVccVciA
The VCI value for side A of an ATM SPVC VCC connection. The valid range is a number between
0 and 65535.
Associated Traps - atmAtmSpvcConfiguredNotify, atmAtmSpvcConfigFailNotify, atmAtmSpvcDeletedNotify, atmAtmSpvcModifiedNotify, atmAtmSpvcModifyFailNotify, atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify, atmAtmSpvcTfcParamModifyInProgressNotify, atmAtmSpvcTfcParamModifyNotify, atmAtmSpvcTfcaramModifyFailNotify
atmAtmSpvcVccVciB
The VCI value for side B of an ATM SPVC VCC connection. The valid range is a number between
0 and 65535.
Associated Traps - atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-5
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
atmAtmSpvcVccVpiA
The VPI value for side A of an ATM SPVC VCC connection. The valid range is a number between
0 and 4095.
Associated Traps - atmAtmSpvcConfiguredNotify, atmAtmSpvcConfigFailNotify, atmAtmSpvcDeletedNotify, atmAtmSpvcModifiedNotify, atmAtmSpvcModifyFailNotify, atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify, atmAtmSpvcVpcSetUpNotify, atmAtmSpvcVpcTearDownNotify, atmAtmSpvcTfcParamModifyInProgressNotify, atmAtmSpvcTfcParamModifyNotify,
atmAtmSpvcTfcaramModifyFailNotify
atmAtmSpvcVccVpiB
The VPI value for side B of an ATM SPVC VCC connection. The valid range is a number between
0 and 4095.
Associated Traps - atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify
atmAtmSpvcVccRemoteAtmPortAddr
Remote ATM port NSAP address-does not need to be set if atmAtmSpvcVccConnType is passiveSvc.
Associated Traps - atmAtmSpvcConfiguredNotify, atmAtmSpvcConfigFailNotify, atmAtmSpvcDeletedNotify, atmAtmSpvcModifiedNotify, atmAtmSpvcModifyFailNotify, atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify, atmAtmSpvcTfcParamModifyInProgressNotify, atmAtmSpvcTfcParamModifyNotify, atmAtmSpvcTfcaramModifyFailNotify
atmAtmSpvcVpcIfB
The interface index for side B of an ATM SPVC VPC connection. Number value is interpreted as
an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC
is the path number.
Associated Traps - atmAtmSpvcVpcSetUpNotify, atmAtmSpvcVpcTearDownNotify
atmAtmSpvcVpcRemoteAtmPortAddr
Remote ATM port NSAP address-does not need to be set if atmAtmSpvcVpcConnType is passiveSvc.
Associated Traps - atmAtmSpvcVpcSetUpNotify, atmAtmSpvcVpcTearDownNotify, atmAtmSpvpConfiguredNotify, atmAtmSpvpConfigFailNotify, atmAtmSpvpDeletedNotify, atmAtmSpvpModifiedNotify, atmAtmSpvpModifyFailNotify
atmAtmSpvcVpcVpiA
The VPI value for side A of an ATM SPVC VPC connection. The valid range is a number between
0 and 4095.
Associated Traps - atmAtmSpvpConfiguredNotify, atmAtmSpvpConfigFailNotify, atmAtmSpvpDeletedNotify, atmAtmSpvpModifiedNotify, atmAtmSpvpModifyFailNotify
atmCntrlPvcSecCfgIntfId
The slot, port, or channel of a signaling or routing PVC that this ATM security agent configuration
is related to. The SSPPCCC format is used.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-6
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - atmSecPvcSACfgCreateFailNotify, atmSecPvcSACfgCreatedNotify, atmSecPvcSACfgDeleteFailNotify, atmSecPvcSACfgDeletedNotify, atmSecPvcSACfgModifyFailNotify, atmSecPvcSACfgModifiedNotify, atmSecPvcSACfgLoadFailNotify
atmCntrlPvcSecCfgVci
The VCI of a signaling or routing PVC that this ATM security agent configuration is related to.
Associated Traps - atmSecPvcSACfgCreateFailNotify, atmSecPvcSACfgCreatedNotify, atmSecPvcSACfgDeleteFailNotify, atmSecPvcSACfgDeletedNotify, atmSecPvcSACfgModifyFailNotify, atmSecPvcSACfgModifiedNotify, atmSecPvcSACfgLoadFailNotify
atmCntrlPvcSecCfgVpi
The VPI of a signaling or routing PVC that this ATM security agent configuration is related to.
Associated Traps - atmSecPvcSACfgCreateFailNotify, atmSecPvcSACfgCreatedNotify, atmSecPvcSACfgDeleteFailNotify, atmSecPvcSACfgDeletedNotify, atmSecPvcSACfgModifyFailNotify, atmSecPvcSACfgModifiedNotify, atmSecPvcSACfgLoadFailNotify
atmImaIntfIndex
The interface index for the ATM IMA interface. Number value is interpreted as an interface of the
form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel
number.
Associated Traps - atmImaIntfFailNotify, atmImaIntfClearedNotify
atmImaIntfStatus
The return value for the atmImaIntfFailNotify trap. The valid range is a number between 1 and 7.
See Table 4-7 for a mapping between numbers and their enumerated type.
Associated Traps - atmImaIntfFailNotify, atmImaIntfClearedNotify
Table 4-7. ATM IMA Interface Status Codes
Number
Value
Enumerated Type
Description
1
lif
Persistence of LIF defect at the near-end. (Loss of IMA Frame)
2
lods
Persistence of LODS defect at the near-end. (Link Out of Delay Synchronization)
3
txMisConnect
The link is not connected to the same far-end as the other links in
the group.
4
rfi
Persistence of RDI-IMA defect at the near-end. (Remote Failure
Indicator)
5
fault
Implementation specific fault at the near-end.
6
txUnusableFe
Tx link forced to unusable due to far-end behavior.
7
rxUnusableFe
Rx link forced to unusable due to far-end behavior.
atmPvcVccIfA
The interface index for side A of an ATM-to-ATM PVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number,
and CCC is the channel number.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-7
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - atmPvcVccReqFailNotify, atmPvcVccSetupNotify, atmPvcVccTearDownNotify,
atmBkPvcVccReqFailNotify, atmBkPvcVccSetupNotify, atmBkPvcVccTearDownNotify
atmPvcVccIfB
The interface index for side B of an ATM-to-ATM PVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number,
and CCC is the channel number.
Associated Traps - atmPvcVccReqFailNotify, atmPvcVccSetupNotify, atmPvcVccTearDownNotify,
atmBkPvcVccReqFailNotify, atmBkPvcVccSetupNotify, atmBkPvcVccTearDownNotify,
atmPvcVccVciA
The VCI value for side A of an ATM-to-ATM PVC VCC connection. The valid range is a number
between 0 and 65535.
Associated Traps - atmPvcVccReqFailNotify, atmPvcVccSetupNotify, atmPvcVccTearDownNotify,
atmBkPvcVccReqFailNotify, atmBkPvcVccSetupNotify, atmBkPvcVccTearDownNotify
atmPvcVccVciB
The VCI value for side B of an ATM-to-ATM PVC VCC connection. The valid range is a number
between 0 and 65535.
Associated Traps - atmPvcVccReqFailNotify, atmPvcVccSetupNotify, atmPvcVccTearDownNotify,
atmBkPvcVccReqFailNotify, atmBkPvcVccSetupNotify, atmBkPvcVccTearDownNotify
atmPvcVccVpiA
The VPI value for side A of an ATM-to-ATM PVC VCC connection. The valid range is a number
between 0 and 4095.
Associated Traps - atmPvcVccReqFailNotify, atmPvcVccSetupNotify, atmPvcVccTearDownNotify,
atmBkPvcVccReqFailNotify, atmBkPvcVccSetupNotify, atmBkPvcVccTearDownNotify
atmPvcVccVpiB
The VPI value for side B of an ATM-to-ATM PVC VCC connection. The valid range is a number
between 0 and 4095.
Associated Traps - atmPvcVccReqFailNotify, atmPvcVccSetupNotify, atmPvcVccTearDownNotify,
atmBkPvcVccReqFailNotify, atmBkPvcVccSetupNotify, atmBkPvcVccTearDownNotify
atmPvcVpcIfA
The interface index for side A of an ATM-to-ATM PVC VPC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number,
and CCC is the channel number.
Associated Traps - atmPvcVpcReqFailNotify, atmPvcVpcSetupNotify, atmPvcVpcTearDownNotify,
atmBkPvcVpcReqFailNotify, atmBkPvcVpcSetupNotify, atmBkPvcVpcTearDownNotify
atmPvcVpcIfB
The interface index for side B of an ATM-to-ATM PVC VPC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number,
and CCC is the channel number.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-8
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - atmPvcVpcReqFailNotify, atmPvcVpcSetupNotify, atmPvcVpcTearDownNotify,
atmBkPvcVpcReqFailNotify, atmBkPvcVpcSetupNotify, atmBkPvcVpcTearDownNotify
atmPvcVpcVpiA
The VPI value for side A of an ATM-to-ATM PVC VPC connection. The valid range is a number
between 0 and 4095.
Associated Traps - atmPvcVpcReqFailNotify, atmPvcVpcSetupNotify, atmPvcVpcTearDownNotify,
atmBkPvcVpcReqFailNotify, atmBkPvcVpcSetupNotify, atmBkPvcVpcTearDownNotify
atmPvcVpcVpiB
The VPI value for side B of an ATM-to-ATM PVC VPC connection. The valid range is a number
between 0 and 4095.
Associated Traps - atmPvcVpcReqFailNotify, atmPvcVpcSetupNotify, atmPvcVpcTearDownNotify,
atmBkPvcVpcReqFailNotify, atmBkPvcVpcSetupNotify, atmBkPvcVpcTearDownNotify
atmSecFailReasonCode
An identified reason for an ATM security configuration failure. The valid range is a number
between 1 and 28.
See Table 4-8 for a mapping between numbers and their enumerated type.
Associated Traps - atmSecPvcSACfgCreateFailNotify, atmSecPvcSACfgDeleteFailNotify, atmSecPvcSACfgModifyFailNotify, atmSecSvccRccSACfgCreateFailNotify, atmSecSvccRccSACfgDeleteFailNotify, atmSecSvccRccSACfgModifyFailNotify, atmSecInvalidSecurityAssociationNotify, atmSecManualSessionKeyUpdateFailNotify, atmSecAgentHangingSANotify,
atmSecPvcSACfgLoadFailNotify,
Table 4-8. ATM Security Failure Reason Codes
Number
Value
Enumerated Type
Description
1
securityAgentConfigExist
This security agent configuration already exists.
2
securityAgentConfigNotExist
This security agent configuration does not exist.
3
securityAgentConfigAdminInService
This security agent configuration has been administratively brought into service.
4
securityAgentNotExist
This security agent does not exist.
5
securityAgentNotInSecureState
This security agent is not in a secure state.
6
svcAtmUifIsNull
The ATM interface is in a null state.
7
interfaceNotExist
The interface does not exist.
8
interfaceAdminStatusNotDown
No additions or modifications can be made to the
security agent configuration because the interface
admin status is in service.
9
signalingNotEnabled
Signaling is not enabled.
10
securitySupportedOnSignalingRoutingVccOnly
Security is supported on the signaling/routing VCC
only.
11
securitySupportedOnUniPnniInterfaceOnly
Security is supported on the UNI PNNI interface only.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-9
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-8. ATM Security Failure Reason Codes
Number
Value
Enumerated Type
Description
12
securityAgentConfigVpiVciDoNot- The security agent configuration VPI/VCI does not
MatchSignalingVpiVci
match the signaling VPI/VCI.
13
consecutiveBadSduReachUpLimit
The number of consecutive bad SDUs has reached the
maximum limit of 32.
14
inFiveMinutesBadSduReachUpLimit
Within a five minute period, the number of bad SDUs
reached the maximum limit.
15
systemError
A system error has occurred.
16
securityAgentCryptoLibHmacMD5 The security configuration has failed because the MD5
Unavailable
algorithm is not available.
17
securityAgentCryptoLibHmacSHA
1Unavailable
The security configuration has failed because the SHA
algorithm is not available.
18
securityAgentCryptoLibAESUnavailable
The security configuration has failed because the AES
algorithm is not available.
19
securityAgentCryptoLibDESUnavailable
The security configuration has failed because the DES
algorithm is not available.
20
interfaceSignallingDisabled
The security configuration has failed because signaling
is not enabled on the interface.
21
interfaceVpiChanged
The interface VPI has been modified.
22
interfaceVciChanged
The interface VCI has been modified.
23
interfaceBroughtIntoService
The interface has been brought into service.
24
skuAlgoIntegrityAlgoNotInSameCategory
The security key update algorithm does not match
with the integrity algorithm.
25
confidentialitySecurityServiceNot- Confidentiality security service is not supported.
Supported
26
atmSec100NotSupportedOnRoutin The ATM Forum standard af-sec-0100.00 does not
gPvc
support security on routing VCC.
27
createMustHaveValidServiceProfileAndAlgorithms
Valid service profile and algorithm values are necessary to create a security agent.
28
doNotHavePreviouslyConfiguredAlgo
The saved configuration uses a security algorithm that
could not be located on the CPUn.
atmSecManualSkuIntfId
The slot, port, and channel of a PVC/SVC that this ATM security agent statistics is related to. The
SSPPCCC format is used.
Associated Traps - atmSecManualSessionKeyUpdateFailNotify
atmSecManualSkuVci
The VCI of a PVC/SVC that this ATM security agent is associated with.
Associated Traps - atmSecManualSessionKeyUpdateFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-10
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
atmSecManualSkuVpi
The VPI of a PVC/SVC that this ATM security agent is associated with.
Associated Traps - atmSecManualSessionKeyUpdateFailNotify
atmSecStatsIntfId
The slot, port, and channel of a PVC/SVC that this ATM security agent statistics is related to. The
SSPPCCC format is used.
Associated Traps - atmSecInvalidSecurityAssociationNotify, atmSecAgentHangingSANotify
atmSecStatsVci
The VCI of a PVC/SVC that this ATM security agent statistics is related to.
Associated Traps - atmSecInvalidSecurityAssociationNotify, atmSecAgentHangingSANotify
atmSecStatsVpi
The VPI of a PVC/SVC that this ATM security agent statistics is related to.
Associated Traps - atmSecInvalidSecurityAssociationNotify, atmSecAgentHangingSANotify
atmSpvcVccIfA
The interface index for side A of an ATM SPVC VCC connection. Number value is interpreted as
an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC
is the channel number.
Associated Traps - atmSpvcConfiguredNotify, atmSpvcConfigFailNotify, atmSpvcDeletedNotify,
atmSpvcModifiedNotify, atmSpvcModifyFailNotify, cirEmAtmSpvcVccSetUpNotify, vbrAtmSpvcVccSetUpNotify, atmSpvcVccSetUpNotify, cirEmAtmSpvcVccTearDownNotify, vbrAtmSpvcVccTearDownNotify, atmSpvcVccTearDownNotify
atmSpvcVccIfB
The interface index for side B of an ATM SPVC VCC connection. Number value is interpreted as
an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC
is the channel number.
Associated Traps - atmSpvcVccSetUpNotify, atmSpvcVccTearDownNotify
atmSpvcVccVciA
The VCI value for side A of an ATM SPVC VCC connection. The valid range is a number between
0 and 65535.
Associated Traps - atmSpvcConfiguredNotify, atmSpvcConfigFailNotify, atmSpvcDeletedNotify,
atmSpvcModifiedNotify, atmSpvcModifyFailNotify, atmSpvcVccSetUpNotify, atmSpvcVccTearDownNotify
atmSpvcVccVciB
The VCI value for side B of an ATM SPVC VCC connection. The valid range is a number between
0 and 65535.
Associated Traps - atmSpvcVccSetUpNotify, atmSpvcVccTearDownNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-11
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
atmSpvcVccVpiA
The VPI value for side A of an ATM SPVC VCC connection. The valid range is a number between
0 and 4095.
Associated Traps - atmSpvcConfiguredNotify, atmSpvcConfigFailNotify, atmSpvcDeletedNotify,
atmSpvcModifiedNotify, atmSpvcModifyFailNotify, atmSpvcVccSetUpNotify, atmSpvcVccTearDownNotify
atmSpvcVccVpiB
The VPI value for side B of an ATM SPVC VCC connection. The valid range is a number between
0 and 4095.
Associated Traps - atmSpvcVccSetUpNotify, atmSpvcVccTearDownNotify
atmTrunkingBrVccId
The ID of the AAL2 Bear VCC.
Associated Traps - atmTrunkingBrVccConfiguredNotify, atmTrunkingBrVccTearDownNotify,
atmTrunkingBrVccSetUpNotify, atmTrunkingBrVccDeletedNotify
atmTrunkingBrVccRmtIWFId
The IWF ID for the remote IWF.
Associated Traps - atmTrunkingBrVccConfiguredNotify, atmTrunkingBrVccTearDownNotify,
atmTrunkingBrVccSetUpNotify, atmTrunkingBrVccDeletedNotify
atmTrunkingConfigFailureCode
An identified reason for failure while configuring or modifying ATM Trunking parameters. The
valid range is a number between 1 and 28.
See Table 4-9 for a mapping between numbers and their enumerated type.
Associated Traps - atmTrunkingLocalIWFConfigFailNotify, atmTrunkingLocalIWFConfigFailNotify, atmTrunkingLocalIWFModifyFailNotify, atmTrunkingLocalIWFDeleteFailNotify, atmTrunkingRemoteIWFConfigFailNotify, atmTrunkingRemoteIWFModifyFailNotify, atmTrunkingSigVccConfigFailNotify, atmTrunkingBrVccConfigFailNotify
Table 4-9. ATM Trunking Configuration Failure Codes
Number
Value
Enumerated Type
Description
1
localIWFAlreadyConfigured
The local IWF has already been configured, the
parameters cannot be changed or applied again.
2
localIWFAtmAddressError
The ATM address for the local IWF is not valid or this
address has been used by someone else.
3
localIWFIdOutOfRange
The Identification of the local IWF is out of range.
4
maxNumberRmtIWFOutOfRange
The maximum number of remote IWF is out of range.
5
rmtIWFAlreadyConfigured
This remote IWF has already been configured.(with
index atmTrunkingRmtIWFIdentifier)
6
rmtIWFIdOutOfRange
The identifier for the remote IWF is out of range.
7
rmtIWFAtmAddressError
The ATM address for remote IWF is not valid or this
address has been used by someone else.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-12
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-9. ATM Trunking Configuration Failure Codes (Continued)
Number
Value
Enumerated Type
Description
8
vccIdError
The VCC ID for the SigVcc or BrVcc is 0, or this VCC
ID is out of range or it has been used by someone else.
9
vccPvcParameterNotAcceptable
The parameters of PVC side, including slot, port, channel, VPI, VCI, are not acceptable.
10
vccTrafficParameterNotValid
The VCC traffic parameters are not acceptable, including FwPcr01, BwPcr01, FwScr01, FWMbs01,
BwMbs01, BrVccServiceType, BrVccSarType.
11
vccViVuniNotValid
The configuration of Egress Vi/VUNI is not acceptable.
12
vccTrunkParameterNotValid
The parameters for the Trunk is not supported, including BrVccMaxAal2ChanId, BrVccCircuitModeDataSupp, BrVccFrameModeSupp, BrVccFaxModeSupp,
CASPktXportSupp, BrVccDTMFPktXportSupp,
BrVccMFR1PktXportSupp, BrVccMFR2PktXportSupp,
BrVccPCMEncoding, BrVccMaxFrameLength, BrVccIdleChannSuprSupp, BrVccSilenceDetSupp, BrVccCompressionSpec, AudioProfileId, SigVccSignaling.
13
vccTrunkFeatureParameterNotValid
PSAX proprietary feature parameters not supported
including SigVccInactiveTimer, SigVccRetryTimer,
SigVccRetryLimit,BrVccInactiveTimer, BrVccRetryTimer, BrVccRetryLimit,BrVccGr303Supp, BrVccOamStatus.
14
localIwfNotConfigured
The local IWF is not configured.
15
localIwfIdNotMatch
The specified local IWF does not match.
16
localIwfStatus
This operation is not supported because of the status
of local IWF.
17
rmtIwfNotConfigured
The remote IWF is not configured.
18
rmtIwfModeNotCompatible
The mode of the remote IWF is not compatible.
19
rmtIwfStatus
This operation is not support because of the status of
the remote IWF.
20
vccAlreadyConfigured
This VCC has been configured.
21
vccPvcCacReject
The PVC configuration is rejected by CAC Reservation
Function.
22
requiredFieldMissing
Mandatory fields are missing.
23
outOfResource
The ATM trunking task or system is out of resource for
this configuration.
24
rowStatusError
Row Status Error with the SNMP command.
25
generalErrorUnspecified
All other unspecified failure causes.
26
bandwidthUnAvailableForELCP
Bandwidth is not available for ECLP.
27
bandwidthUnAvailableForISDN
Bandwidth is not available for ISDN.
28
pvcInterfaceVpiVciIsInUse
The PVC interface VPI/VCI is in use.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-13
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
atmTrunkingIWFIdentifier
The IWF ID for the local endpoint.
Associated Traps - atmTrunkinglocalIWFConfiguredNotify, atmTrunkingLocalIWFConfigFailNotify, atmTrunkingLocalIWFModifiedNotify, atmTrunkingLocalIWFModifyFailNotify, atmTrunkingLocalIWFDeletedNotify, atmTrunkingLocalIWFDeleteFailNotify
atmTrunkingRemoteIWFIdentifier
The IWF ID for the remote IWF.
Associated Traps - atmTrunkingRemoteIWFConfiguredNotify, atmTrunkingRemoteIWFConfigFailNotify, atmTrunkingRemoteIWFDeletedNotify, atmTrunkingRemoteIWFModifiedNotify,
atmTrunkingRemoteIWFModifyFailNotify
atmTrunkingSigVccIdentifier
The VCC ID assigned by the owner of this signaling VCC.
Associated Traps - atmTrunkingSigVccSetUpNotify, atmTrunkingSigVccTearDownNotify,
atmTrunkingSigVccConfiguredNotify, atmTrunkingSigVccConfigFailNotify, atmTrunkingSigVccDeletedNotify
atmTrunkingSigVccRmtIWFIdentifier
The IWF ID for the remote IWF.
Associated Traps - atmTrunkingSigVccSetUpNotify, atmTrunkingSigVccTearDownNotify,
atmTrunkingSigVccConfiguredNotify, atmTrunkingSigVccConfigFailNotify, atmTrunkingSigVccDeletedNotify
atmVci
The VCI used for the connection.
Associated Traps - dhpvcChangeNotify
atmVpcPnniIfIndex
ATM VPC PNNI interface index. The number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel number.
Associated Traps - vpcPnniIntfCreatedNotify, vpcPnniIntfCreateFailNotify, vpcPnniIntfModifiedNotify, vpcPnniIntfDeleteNotify, vpcPnniIntfModifyFailNotify, vpcPnniIntfOutOfServiceNotify,
vpcPnniIntfInServiceNotify
atmVpcPnniVpcId
A virtual path connection ID. The second index to access the virtual path connection interface.
Associated Traps - vpcPnniIntfCreatedNotify, vpcPnniIntfCreateFailNotify, vpcPnniIntfModifiedNotify, vpcPnniIntfDeleteNotify, vpcPnniIntfModifyFailNotify, vpcPnniIntfOutOfServiceNotify,
vpcPnniIntfInServiceNotify
atmVpi
The VPI used for the connection.
Associated Traps - dhpvcChangeNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-14
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
backupSoftwareVersion
Software version running on the backup CPU module.
Associated Traps - differentSystemSoftwareNotify
bridgeAtmPvcVccIfA
The interface index for side A, the bridge side, of a Bridge-to-ATM PVC VCC connection. Number
value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the
port number, and CCC is the channel number.
Associated Traps - bridgeAtmPvcVccReqFailNotify, bridgeAtmPvcVccSetupNotify, bridgeAtmPvcVccTearDownNotify, bridgeAtmBkPvcVccReqFailNotify, bridgeAtmBkPvcVccSetupNotify,
bridgeAtmBkPvcVccTearDownNotify
bridgeAtmPvcVccIfB
The interface index for side B, the ATM side, of a Bridge-to-ATM PVC VCC connection. Number
value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the
port number, and CCC is the channel number.
Associated Traps - bridgeAtmPvcVccReqFailNotify, bridgeAtmPvcVccSetupNotify, bridgeAtmPvcVccTearDownNotify, bridgeAtmBkPvcVccReqFailNotify, bridgeAtmBkPvcVccSetupNotify,
bridgeAtmBkPvcVccTearDownNotify
bridgeAtmPvcVccVciB
The VCI value for side B, the ATM side, of a Bridge-to-ATM PVC VCC connection. The valid range
is a number between 0 and 65535.
Associated Traps - bridgeAtmPvcVccReqFailNotify, bridgeAtmPvcVccSetupNotify, bridgeAtmPvcVccTearDownNotify, bridgeAtmBkPvcVccReqFailNotify, bridgeAtmBkPvcVccSetupNotify,
bridgeAtmBkPvcVccTearDownNotify
bridgeAtmPvcVccVpiB
The VPI value for side B, the ATM side, of a Bridge-to-ATM PVC VCC connection. The valid range
is a number between 0 and 4095.
Associated Traps - bridgeAtmPvcVccReqFailNotify, bridgeAtmPvcVccSetupNotify, bridgeAtmPvcVccTearDownNotify, bridgeAtmBkPvcVccReqFailNotify, bridgeAtmBkPvcVccSetupNotify,
bridgeAtmBkPvcVccTearDownNotify
bridgeBridgePvcIfA
The interface index for side A of a Bridge-to-Bridge PVC connection. Number value is interpreted
as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and
CCC is the channel number.
Associated Traps - bridgeBridgePvcReqFailNotify, bridgeBridgePvcSetupNotify, bridgeBridgePvcTearDownNotify
bridgeBridgePvcIfB
The interface index for side B of a Bridge-to-Bridge PVC connection. Number value is interpreted
as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and
CCC is the channel number.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-15
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - bridgeBridgePvcReqFailNotify, bridgeBridgePvcSetupNotify, bridgeBridgePvcTearDownNotify
bridgeDomainNumber
The bridge number of the bridge that includes this interface. If the interface is currently not associated with any bridge this will be set to none.
Associated Traps - bridgeDomainFullNotify, bridgeDomainNumberInUseNotify, bridgeDomainInServiceNotify, bridgeDomainTimingRelationshipNotify
bulkStatsFtpOperationErrorStatus
Error status causing an FTP failure. The valid range is a number between 0 and 4.
See Table 4-10 for a mapping between numbers and their enumerated type.
Associated Traps - bulkStatsFtpFailNotify
Table 4-10. Bulk FTP Operation Error Status
Number
Value
Enumerated Type
Description
0
none
No error.
1
unableToMakeFtp- Unable to establish an FTP connection.
Connection
2
unableToWriteFile
Unable to write to the system.
3
unableToOpenFile
Unable to open the input file.
4
unableToCompleteFtp
Unable to complete the FTP process.
cableStatusOfGroupedPorts
The diagnostic field that displays the status of the cables connected to the grouped ports. The
length of the octet string is determined by how many groups of ports are present. Each i’th octet
value represents the status of the cable connected to the i’th group of ports. The value 00 indicates that the cable status is not available. The value 01 indicate that the cables match. The value
02 indicates that the cables are mismatched.
cardInsertionFailureReasonCode
The reason that a module insertion fails.
Associated Traps - cardInsertionFailNotify
Table 4-11. Module Insertion Failure Reason Code
Number
Value
1
Enumerated Type
notEnoughMemory
Description
Upon insertion failure, the module is reset by the CPUn. The module
does not need to be reseated, since it will remain in the state of continuos reboot until the system memory usage returns to normal.
Numerous module insertion and removal trap messages are to be
expected. To identify the reason of the failure, review the trap messages.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-16
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
cardOperStatus
The current operational status of the module. The valid range is a number between 1 and 3.
See Table 4-12 for a mapping between numbers and their enumerated type.
Associated Traps - cardInsertionNotify
Table 4-12. Module Operational Status Codes
Number
Value
Enumerated Type
Description
1
primary
For an I/O module, the status is primary if the module is configured.
For the CPU, it is the principal CPU.
2
standby
For the CPU, it is standby if the CPU is secondary.
3
unknown
For an I/O module, the status is unknown if the module is unconfigured, or removed.
cardProtectionStatus
The current protection status of the module. The valid range is a number between 1 and 3.
See Table 4-13 for a mapping between numbers and their enumerated type.
Associated Traps - cardInsertionNotify
Table 4-13. Module Protection Status Codes
Number
Value
Enumerated Type
Description
1
none
The module is unprotected.
2
protected
The module is under the protection of another module.
3
wrongType
The protection module and the protected module are different types.
cardSlot
The physical slot location. The valid range is a number between 1 and 24.
Associated Traps - cardInsertionNotify, cardRemovedOrFailedNotify, moduleRebootNotify, bridgeDomainExceededForSlotNotify, viprRtSrvTrap, limStatusChangedNotify,
dsp2CardReroutingSucceededNotify, cardInsertionFailNotify
cardType
The type of module in a physical slot. A specific type of module is associated with each number.
The valid range is a number between 1 and 82.
See Table 4-14 for a mapping between numbers and their enumerated type.
Associated Traps - cardInsertionNotify, cardRemovedOrFailedNotify, lineStatusChangedNotify,
moduleRebootNotify, cardInsertionFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-17
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-14. Module Type Codes
Number
Value
Enumerated Type
Description
1
none
No module is present in the slot.
2
taxi
Taxi
3
oC-3c
OC-3c
4
dS3-ATM
2-Port DS3 ATM module
5
dS1-CE
DS1 Circuit Emulation
6
dS1-ATM
DS1 ATM
7
e1-CE
E1 Circuit Emulation
8
e3-ATM
2-Port E3 ATM module
9
highSpeed
2-Port High Speed module
10
mSerial
Multiserial module
11
dSP1
DSP1 Voice Server module
12
tWStation
8-Port Voice 2-Wire Station module
13
tWOffice
4-Port Voice 2-Wire Office module
14
cPU
Central Processing Unit module
15
stratum
Stratum 3–4 module
16
pwrSupply
Power Supply module
17
protectionCard
Protection module
18
e1-ATM
E1 ATM
19
ethernet
Ethernet module
20
enhDS1
6-Port Enhanced DS1/T1 Multiservice module
21
enhE1
6-Port Enhanced E1 Multiservice module
22
oC-3cMMAQ
OC-3c Multimode with AQueMan firmware
23
oC-3cMMTS
OC-3c Multimode with Traffic Shaping firmware
24
oC-3cSMAQ
OC-3c Single-Mode with AQueMan firmware
25
oC-3cSMTS
OC-3c Single-Mode with Traffic Shaping firmware
26
sTM-1SMAQ
STM-1 Single-Mode with AQueMan firmware
27
sTM-1SMTS
STM-1 Single-Mode with Traffic Shaping firmware
28
sTM-1MMAQ
STM-1 Multimode with AQueMan firmware
29
sTM-1MMTS
STM-1 Multimode with Traffic Shaping firmware
30
dS3-FR
1-Port Unchannelized DS3 Frame Relay module
31
dSP2A
DSP2A Voice Server module
32
dS1-IMA
6-Port DS1 IMA module
33
e1-IMA
6-Port E1 IMA module
34
alarm
Alarm module
35
dSP2B
DSP2B Voice Server module
36
aps-OC-3cSM
1-Port OC-3c 1+1 APS Single-Mode module
37
aps-OC-3cMM
1-Port OC-3c 1+1 APS Multimode module
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-18
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-14. Module Type Codes (Continued)
Number
Value
Enumerated Type
Description
38
msp-STM-1SM
1-Port STM-1 1+1 MSP Single-Mode module
39
msp-STM-1MM
1-Port STM-1 1+1 MSP Multimode module
40
cH-DS3
1-Port Channelized DS3 Multiservice module
41
cH-STS1
1-Port Channelized STS-1e, T1 Format module
42
rT-S
Route Server module
43
cC-Server
Continuity Check Server
44
hD-E1
21-Port High-Density E1 Multiservice module
45
hD-DS1
24-Port High-Density DS1 Multiservice module
46
dS3-IMA
1-Port DS3 IMA module
47
dSP2C
DSP2C Voice Server module
48
tasm
Tones and Announcements Server module
49
mD-DS1
12-Port Medium-Density DS1 Multiservice module
50
quadSerial
Quadserial module
51
mD-DS1-IMA
12-Port Medium-Density DS1 IMA module
52
mD-E1-IMA
Medium-Density E1 IMA
53
hD-DS1-IMA
High-Density DS1 IMA
54
hD-E1-IMA
21-Port High-Density E1 IMA module
55
chDS3STS1-3P
3-Port Channelized DS3/STS-1e CES module
56
unstDS3E3-3P
3-Port Unstructured DS3/E3 CES module
57
dS3E3-ATM-3P
3-Port DS3/E3 ATM module
58
oC12c-STM4-MM
1-Port OC-12c/STM-4c Multimode module
59
oC12c-STM4-SM
1-Port OC-12c/STM-4c Single-Mode module
60
dSP2D
DSP2D Voice Server module
61
ethernet-4P
4-Port Ethernet module
62
chDS3STS1-3P-Prot
3-Port Channelized DS3/STS-1e CES Protection module
63
alarm-fan
PSAX 1000 Fan/Alarm module
64
mD-DS1E1DS0A-CES
12-Port Medium-Density DS1/E1/DS0A CES module
65
DSP2E
DSP2E Voice Server module
66
DSP2F
DSP2F Voice Server module
67
eNH-RTR-MOD01
Enhanced Router module
68
dS3E3-ATM-3P-Prot
3-Port DS3/E3 ATM Protection module
69
ch-OC3STM1-SM
1-Port Channelized OC-3/STM-1 CES Single-mode module
70
ch-OC3STM1-MM
1-Port Channelized OC-3/STM-1 CES Multimode module
73
unstDS3E3-3P-Prot
3-Port Unstructured DS3/E3 CES Protection module
74
ch-OC3STM1-UCEATM-SM
1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Single-mode module
75
ch-OC3STM1-UCEATM-MM
1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Multimode module
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-19
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-14. Module Type Codes (Continued)
Number
Value
Enumerated Type
Description
76
dS3-FR-3P
3-Port DS3 Frame Relay module
77
dS3-FR-3P-Prot
3-Port DS3 Frame Relay Protection module
78
hDSL2-SHDSL
8-Port HDSL-2 module
79
chDS3STS1-3P-MS
3-Port Channelized DS3/STS-1e Multiservice module
80
chDS3STS1-3P-Prot-MS 3-Port Channelized DS3/STS-1e Multiservice Protection module
81
oC3c-STM1-SM-2P
2-Port OC-3c/STM-1 ATM Single-Mode module
82
oC3c-STM1-MM-2P
2-Port OC-3c/STM-1 ATM Multimode module
cellTestIfB
The interface index used for testing cell transfer. Number value is interpreted as an interface of
the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel
number.
Associated Traps - cellTestReqFailNotify
cellTestVcidB
Virtual Check ID for testing cell transfer to an I/O module. The valid range is a number between 0
and 65535. If the I/O module interface is frame relay, this field acts as DLCI and the valid range is
a number between 0 and 1023. If the I/O module interface is circuit emulation, then this will
always be 0.
Associated Traps - cellTestReqFailNotify
cellTestVpiB
The VPI value for testing cell transfer to an I/O module. The valid range is a number between 0
and 4095. If the I/O module interface is not ATM, then this will always be zero.
Associated Traps - cellTestReqFailNotify
chassisOverTempAlarmReasonCode
Indicates the presence of the chassis over temperature alarm. The valid range is a number
between 1 and 2.
See Table 4-15 for a mapping between numbers and their enumerated type.
Associated Traps - chassisOverTempAlarmNotify
Table 4-15. Chassis Over Temperature Alarm Reason Codes
Number
Value
Enumerated Type
Description
1
set
The chassis over temperature alarm is set.
2
clear
The chassis over temperature alarm is clear.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-20
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
cirAtmSpvcVccIfB
The interface index for side B, the ATM side, of a circuit emulation-to-ATM SPVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module
slot, PP is the port number, and CCC is the channel number.
Associated Traps - cirAtmSpvcVccSetUpNotify, cirAtmSpvcVccTearDownNotify
cirAtmSpvcVccRemoteCePortAddr
The ATM address supporting the corresponding far-end CES IWF process. If no address is supplied, no attempts to establish the active SVC are initiated.
Associated Traps - cirAtmSpvcConfiguredNotify, cirAtmSpvcConfigFailNotify, cirAtmSpvcDeletedNotify, cirAtmSpvcModifiedNotify, cirAtmSpvcModifyFailNotify, cirAtmSpvcVccSetUpNotify,
cirAtmSpvcVccTearDownNotify
cirAtmSpvcVccVpiB
The VPI value for side B, the ATM side, of a circuit emulation-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 4095.
Associated Traps - cirAtmSpvcVccSetUpNotify, cirAtmSpvcVccTearDownNotify
cirAtmSpvcVccVciB
The VCI value for side B, the ATM side, of a circuit emulation-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 65535.
Associated Traps - cirAtmSpvcVccSetUpNotify, cirAtmSpvcVccTearDownNotify
cirEmAtmPvcVccIfA
The interface index for side A, the circuit emulation side, of a circuit emulation-to-ATM PVC VCC
connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the
module slot, PP is the port number, and CCC is the channel number.
Associated Traps - cirEmAtmPvcVccReqFailNotify, cirEmAtmPvcVccSetupNotify, cirEmAtmPvcVccTearDownNotify, cirEmAtmBkPvcVccReqFailNotify, cirEmAtmBkPvcVccSetupNotify,
cirEmAtmBkPvcVccTearDownNotify
cirEmAtmPvcVccIfB
The interface index for side B, the ATM side, of a circuit emulation-to-ATM PVC VCC connection.
Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - cirEmAtmPvcVccReqFailNotify, cirEmAtmPvcVccSetupNotify, cirEmAtmPvcVccTearDownNotify, cirEmAtmBkPvcVccReqFailNotify, cirEmAtmBkPvcVccSetupNotify,
cirEmAtmBkPvcVccTearDownNotify
cirEmAtmPvcVccVciB
The VCI value for side B, the ATM side, of a circuit emulation-to-ATM PVC VCC connection. The
valid range is a number between 0 and 65535.
Associated Traps - cirEmAtmPvcVccReqFailNotify, cirEmAtmPvcVccSetupNotify, cirEmAtmPvcVccTearDownNotify, cirEmAtmBkPvcVccReqFailNotify, cirEmAtmBkPvcVccSetupNotify,
cirEmAtmBkPvcVccTearDownNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-21
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
cirEmAtmPvcVccVpiB
The VPI value for side B, the ATM side, of a circuit emulation-to-ATM PVC VCC connection. The
valid range is a number between 0 and 4095.
Associated Traps - cirEmAtmPvcVccReqFailNotify, cirEmAtmPvcVccSetupNotify, cirEmAtmPvcVccTearDownNotify, cirEmAtmBkPvcVccReqFailNotify, cirEmAtmBkPvcVccSetupNotify,
cirEmAtmBkPvcVccTearDownNotify
cirEmAtmSpvcVccIfA
The interface index for side A, the circuit emulation side, of a circuit emulation-to-ATM SPVC
VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is
the module slot, PP is the port number, and CCC is the channel number.
Associated Traps - cirEmAtmSpvcVccSetUpNotify, cirEmAtmSpvcVccTearDownNotify
cirEmAtmSpvcVccIfB
The interface index for side B, the ATM side, of a circuit emulation-to-ATM SPVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module
slot, PP is the port number, and CCC is the channel number.
Associated Traps - cirEmAtmSpvcVccSetUpNotify, cirEmAtmSpvcVccTearDownNotify
cirEmAtmSpvcVccVciB
The VCI value for side B, the ATM side, of a circuit emulation-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 65535.
Associated Traps - cirEmAtmSpvcVccSetUpNotify, cirEmAtmSpvcVccTearDownNotify
cirEmAtmSpvcVccVpiB
The VPI value for side B, the ATM side, of a circuit emulation-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 4095.
Associated Traps - cirEmAtmSpvcVccSetUpNotify, cirEmAtmSpvcVccTearDownNotify
cirEmCirEmPvcIfA
The interface index for side A of a circuit emulation-to-circuit emulation PVC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is
the port number, and CCC is the channel number.
Associated Traps - cirEmCirEmPvcReqFailNotify, cirEmCirEmPvcSetupNotify, cirEmCirEmPvcTearDownNotify
cirEmCirEmPvcIfB
The interface index for side B of a circuit emulation-circuit emulation PVC connection. Number
value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the
port number, and CCC is the channel number.
Associated Traps - cirEmCirEmPvcReqFailNotify, cirEmCirEmPvcSetupNotify, cirEmCirEmPvcTearDownNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-22
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
connectionNamingResultCode
Various result codes for the operator’s command for setting/deleting connection naming. The
valid range is a number between 1 and 5.
See Table 4-16 for a mapping between numbers and their enumerated type.
Associated Traps - connectionNamingResultNotify
Table 4-16. Connection Naming Result Codes
Number
Value
Enumerated Type
Description
1
alreadyExistConnectionName
The connection name must be unique.
2
invalidConnectionName
The connection name is too long.
3
insufficientMemory
The connection cannot be named due to insufficient
memory.
4
tryToDeleteEmptyTable
The table is already empty and cannot be deleted.
5
nonexistConnectionForNaming
The connection does not exist.
dlciNumber
The number of the Data Link Connection identifiers (DLCI) being used.
Associated Traps - lmiDlciStatusNotify
deviceId
The device ID is used as the number of external devices. Each device can be an external input
device or control output device.
Associated Traps - alarmCardInputChangeNotify, alarmCardOutputChangeNotify
ermAtmSpvcRemoteAddr
The ATM address of the destination. For passive side connections, the fields will be all zeros.
Associated Traps - ermAtmSpvcConfiguredNotify, ermAtmSpvcConfigFailNotify, ermAtmSpvcDeletedNotify, ermAtmSpvcModifiedNotify, ermAtmSpvcModifyFailNotify, ermAtmSpvcSetupNotify, ermAtmSpvcTearDownNotify
ermClassRuleId
An integer index to uniquely identify this color mapping rule. (1..64) for DSCP classification,
(1..8) for IEEE802.1p classification, and (1..6) for subchannel classification. (e.g., VCC1->CoS1,
VCC2->Cos2, etc. for an ATM VCC connection.)
Associated Traps - ermClassRuleTrap
ermClassRuleStatus
Return codes for the Enhanced Router Module IP classification operations. The valid range is a
number between 1 and 10.
See Table 4-17 for a mapping between numbers and their enumerated type.
Associated Traps - ermClassRuleTrap
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-23
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-17. Enhanced Router Module Class Rule Status Return Codes
Number
Value
Enumerated Type
Description
1
ermClassRuleOK
The class table configuration is ok.
2
ermClassRuleFailure
The class table configuration has failed.
3
ermClassRuleTooMany
Exceeded the maximum number of class tables.
4
ermClassRuleBadId
Impossible class rule ID.
5
ermClassRuleBadClassTbId
Impossible class table ID.
6
ermClassRuleExists
This class table already exists.
7
ermClassRuleBadMin
Illegal class minimum value.
8
ermClassRuleBadMax
Illegal class maximum value.
9
ermClassRuleBadAssignedCos
Illegal assigned class of service.
10
ermClassRuleNotAllowed
This operation is not allowed.
ermClassTbId
An integer index to uniquely identify this classification table for a VPN.
Associated Traps - ermClassTbTrap, ermClassRuleTrap
ermClassTbStatus
Return codes for the Enhanced Router Module IP classification operations. The valid range is a
number between 1 and 7.
See Table 4-18 for a mapping between numbers and their enumerated type.
Associated Traps - ermClassTbTrap
Table 4-18. Enhanced Router Module IP Classification Return Codes
Number
Value
Enumerated Type
Description
1
ermClassTbOK
The class table configuration is ok.
2
ermClassTbFailure
The class table configuration has failed.
3
ermClassTbTooMany
Exceeded the maximum number of class tables.
4
ermClassTbBadId
Impossible class table ID.
5
ermClassTbExists
This class table already exists.
6
ermClassTbBadScheme
Illegal class scheme.
7
ermClassTbNotAllowed
This operation is not allowed.
ermConnSubchNo
A unique connection ID for the connection subchannel in the interface.
Associated Traps - ermAtmSpvcConfiguredNotify, ermAtmSpvcConfigFailNotify, ermAtmSpvcDeletedNotify, ermAtmSpvcModifiedNotify, ermAtmSpvcModifyFailNotify, ermAtmSpvcSetupNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-24
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
ermFilterId
Displays a unique identifier for this filter. Smaller filter identifiers have higher priority than larger
filter identifiers. If the rules are dynamic in nature, it is recommended that you add filter identifiers such as 100, 200, and so on, so that filters can be inserted in between these values.
Associated Traps - ermFilterTrap
ermFilterStatus
The Enhanced Router module filter status. The valid range is a number between 1 and 12.
See Table 4-19 for a mapping between numbers and their enumerated type.
Associated Traps - ermFilterTrap
Table 4-19. Enhanced Router Module Filter Status Return Codes
Number
Value
Enumerated Type
Description
1
ermFilterOK
The filter configuration is OK.
2
ermFilterFailure
The filter configuration has failed.
3
ermFilterTooMany
Exceeded the maximum number of filter rules.
4
ermFilterBadId
Impossible filter ID.
5
ermFilterExists
This filter rule number already exists.
6
ermFilterBadSrcAddr
Illegal source IP address.
7
ermFilterBadSrcMask
Illegal source subnet mask.
8
ermFilterBadDestAddr
Illegal destination IP address.
9
ermFilterBadDestMask
Illegal destination subnet mask.
10
ermFilterBadSrcPortNo
Illegal source port number.
11
ermFilterBadDestPortNo
Illegal destination port number.
12
ermFilterNotAllowed
The operation is not allowed.
ermIpIfNo
A sequential number that uniquely identifies a connection.
Associated Traps - ermAtmSpvcConfiguredNotify, ermAtmSpvcConfigFailNotify, ermAtmSpvcDeletedNotify, ermAtmSpvcModifiedNotify, ermAtmSpvcModifyFailNotify, ermAtmSpvcSetupNotify, ermAtmSpvcTearDownNotify
ermPppCfgTemplateResultCode
Return codes for a PPP configuration template operation. The valid range is a number between 1
and 7.
See Table 4-20 for a mapping between numbers and their enumerated type.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-25
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - ermPppCfgTemplateNotify
Table 4-20. Enhanced Router Module PPP Configuration Template Operation Return Codes
Number
Value
Enumerated Type
Description
1
ermPppTmpltTooMany
Exceeded the maximum configured PPPs allowed.
2
ermPppTmpltVpnPPPNotSupport
This VPN does not support PPP.
3
ermPppTmpltCantLocate
Unable to locate the VPN.
4
ermPppTmpltVpnDelInProgressThe This VPN is in the process of being deleted.
5
ermPppTmpltAlreadyExists
This template already exists.
6
ermPppTmpltFailure
The Enhanced Router Module does not allow the
addition of this configuration.
7
ermPppTmpltAddOK
The configuration was successfully added.
ermPppConfTemplateIndex
A unique ID for the ermPppConfigTemplate at the VPN level.
Associated Traps - ermPppCfgTemplateNotify
ermRadiusServerIndex
A number uniquely identifying each RADIUS Authentication server with which this client communicates.
Associated Traps - ermRadiusTrap
ermRadiusStatus
The Enhanced Router module RADIUS status. The valid range is a number between 1 and 9.
See Table 4-21 for a mapping between numbers and their enumerated type.
Associated Traps - ermRadiusTrap
Table 4-21. Enhanced Router Module Radius Status Return Codes
Number
Value
Enumerated Type
Description
1
ermRadiusOK
The radius configuration is OK.
2
ermRadiusFailure
The radius configuration has failed.
3
ermRadiusTooMany
Exceeded the maximum number of servers.
4
ermRadiusBadIndex
Impossible index.
5
ermRadiusExists
This server index already exists.
6
ermRadiusBadSvrIpAddr
Illegal server IP address.
7
ermRadiusBadSvrPortNo
Illegal server port number.
8
ermRadiusBadSvrSecret
Illegal server secret.
9
ermRadiusNotAllowed
This operation is not allowed.
ermSlot
The slot number of the Enhanced Router module (SS).
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-26
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - ermFilterTrap, ermRadiusTrap, ermClassTbTrap, ermClassRuleTrap, ermPppCfgTemplateNotify
ermVpnId
Identifies the VPN number on the Enhanced Router module.
Associated Traps - ermFilterTrap, ermRadiusTrap, ermClassTbTrap, ermClassRuleTrap, ermPppCfgTemplateNotify
featureOnOffErrorCode
The error code for the feature turn on or off. The valid range is a number between 1 and 3.
See Table 4-22 for a mapping between numbers and their enumerated type.
Associated Traps - featureOnOffNotify
Table 4-22. Feature On/Off Error Codes
Number
Value
Enumerated Type
Description
1
memory-not-enough
Insufficient memory is available for one or more features to be
turned on.
2
sg-not-all-disable
The SG feature in some interfaces is still enabled. To change the
media gateway control type, all SG features must be disabled.
3
only-one-can-be-enable For GR303, V5.2, and H248, only one feature can be enabled at a
time.
firmwareDownloadReasonCode
The suspected reasons why a firmware download would fail. The valid range is a number
between 1 and 19.
See Table 4-23 for a mapping between numbers and their enumerated type.
Associated Traps - firmwareDownloadFailedNotify
Table 4-23. Firmware Download Reason Codes
Number
Value
Enumerated Type
Description
1
cardInService
The module is in service.
2
errorInFile
An error occurred in the database file.
3
otherFailure
Other failure.
4
wrongCardSubType
Incorrect module sub type.
5
driverUnavailable
The driver is not available.
6
driverInvalidHeaderChecksum
The firmware driver file is corrupted.(invalid header
checksum)
7
driverInvalidrecordChecksum
The firmware driver file is corrupted (invalid record
checksum).
8
requestReplyTimeout
Failure to communicate with the I/O module.
(request timeout).
9
completeReplyTimeout
Failure to communicate with the I/O module.
(download complete reply timeout).
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-27
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-23. Firmware Download Reason Codes (Continued)
Number
Value
Enumerated Type
Description
10
mapFileCorrupted
The firmware driver map file is corrupt.
11
mapFileUnavailable
The firmware driver map file is unavailable.
12
mapFileInvalidChecksum
The firmware driver map file is corrupt.
13
mapFileNameImproper
The firmware driver map file name is not valid.
14
cfgFileCorrupted
The configuration file is corrupt.
15
cfgFileUnavailable
The configuration file is unavailable.
16
cfgFileInvalidChecksum
The configuration file checksum is not valid.
17
wrongCardType
The module type is incorrect.
18
removeCardBeforeFinish
The module was removed before completion.
19
ioUnsupported
The module does not support the firmware download.
frAtmPvcVccDlciA
The DLCI value for side A, the frame relay side, of a frame relay-ATM PVC VCC connection. The
valid range is a number between 0 and 1023.
Associated Traps - frAtmPvcVccReqFailNotify, frAtmPvcVccSetupNotify, frAtmPvcVccTearDownNotify, frAtmBkPvcVccReqFailNotify, frAtmBkPvcVccSetupNotify, frAtmBkPvcVccTearDownNotify
frAtmPvcVccIfA
The interface index for side A, the frame relay side, of a frame relay-to-ATM PVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module
slot, PP is the port number, and CCC is the channel number.
Associated Traps - frAtmPvcVccReqFailNotify, frAtmPvcVccSetupNotify, frAtmPvcVccTearDownNotify, frAtmBkPvcVccReqFailNotify, frAtmBkPvcVccSetupNotify, frAtmBkPvcVccTearDownNotify
frAtmPvcVccIfB
The interface index for side B, the ATM side, of a frame relay-to-ATM PVC VCC connection.
Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - frAtmPvcVccReqFailNotify, frAtmPvcVccSetupNotify, frAtmPvcVccTearDownNotify, frAtmBkPvcVccReqFailNotify, frAtmBkPvcVccSetupNotify, frAtmBkPvcVccTearDownNotify
frAtmPvcVccVciB
The VCI value for side B, the ATM side, of a frame relay-to-ATM PVC VCC connection. The valid
range is a number between 0 and 65535.
Associated Traps - frAtmPvcVccReqFailNotify, frAtmPvcVccSetupNotify, frAtmPvcVccTearDownNotify, frAtmBkPvcVccReqFailNotify, frAtmBkPvcVccSetupNotify, frAtmBkPvcVccTearDownNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-28
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
frAtmPvcVccVpiB
The VPI value for side B, the ATM side, of a frame relay-to-ATM PVC VCC connection. The valid
range is a number between 0 and 4095.
Associated Traps - frAtmPvcVccReqFailNotify, frAtmPvcVccSetupNotify, frAtmPvcVccTearDownNotify, frAtmBkPvcVccReqFailNotify, frAtmBkPvcVccSetupNotify, frAtmBkPvcVccTearDownNotify
frAtmSpvcVccDlciA
The DLCI value for side A, the frame relay side, of a frame relay-to-ATM SPVC VCC connection.
The valid range is a number between 0 and 1023.
Associated Traps - frAtmSpvcConfiguredNotify, frAtmSpvcConfigFailNotify, frAtmSpvcDeletedNotify, frAtmSpvcModifiedNotify, frAtmSpvcModifyFailNotify, frAtmSpvcVccSetUpNotify, frAtmSpvcVccTearDownNotify
frAtmSpvcVccIfB
The interface index for side B, the ATM side, of a frame relay-to-ATM SPVC VCC connection.
Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - frAtmSpvcVccSetUpNotify, frAtmSpvcVccTearDownNotify
frAtmSpvcVccVpiB
The VPI value for side B, the ATM side, of a frame relay-ATM SPVC VCC connection. The valid
range is a number between 0 and 4095.
Associated Traps - frAtmSpvcVccSetUpNotify, frAtmSpvcVccTearDownNotify
frAtmSpvcVccVciB
The VCI value for side B, the ATM side, of a frame relay-ATM SPVC VCC connection. The valid
range is a number between 0 and 65535.
Associated Traps - frAtmSpvcVccSetUpNotify, frAtmSpvcVccTearDownNotify
frf5LmiOperStatus
The operational status of the LMI protocol. The valid range is a number between 1 and 2.
See Table 4-24 for a mapping between numbers and their enumerated type.
Associated Traps - frf5LmiStatusNotify
Table 4-24. FRF5 LMI Operational Status Codes
Number
Value
Enumerated Type
Description
1
outOfService
The LMI protocol is out of service.
2
inService
The LMI protocol is in service.
frFrPvcDlciA
The DLCI value for side A of a frame relay-to-frame relay PVC connection. The valid range is a
number between 0 and 1023.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-29
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - frFrPvcReqFailNotify, frFrPvcSetupNotify, frFrPvcTearDownNotify
frFrPvcDlciB
The DLCI value for side B of a frame relay-to-frame relay PVC connection. The valid range is a
number between 0 and 1023.
Associated Traps - frFrPvcReqFailNotify, frFrPvcSetupNotify, frFrPvcTearDownNotify
frFrPvcIfA
The interface index for side A of a frame relay-to-frame relay PVC connection. Number value is
interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port
number, and CCC is the channel number.
Associated Traps - frFrPvcReqFailNotify, frFrPvcSetupNotify, frFrPvcTearDownNotify
frFrPvcIfB
The interface index for side B of a frame relay-to-frame relay PVC connection. Number value is
interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port
number, and CCC is the channel number.
Associated Traps - frFrPvcReqFailNotify, frFrPvcSetupNotify, frFrPvcTearDownNotify
frLmiOperStatus
The operational status of the LMI protocol. The valid range is a number between 1 and 2.
See Table 4-25 for a mapping between numbers and their enumerated type.
Associated Traps - lmiIntfStatusNotify
Table 4-25. LMI Operational Status Codes
Number
Value
Enumerated Type
Description
1
outOfService
The LMI protocol is out of service.
2
inService
The LMI protocol is in service.
fwReleaseSlot
Physical slot location. The valid range is a number between 1 and 16.
Associated Traps - firmwareDownloadSucceededNotify, firmwareDownloadFailedNotify
gr303Aal2PvcVccGr303CallRef
The call reference value to be used in the signaling packets on the GR-303 interface for the AAL2 Channel ID corresponding to this connection. The valid range is a number between 1 and 2048.
Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify,
gr303Aal2PvcTearDownNotify
gr303Aal2PvcVccGr303IgId
The GR-303 interface group ID on the GR-303 side of the connection. The valid range. The valid
range is a number between 0 and 84.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-30
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify,
gr303Aal2PvcTearDownNotify
gr303Aal2PvcVccIfB
The interface index for side B (the ATM side) of a circuit emulation-ATM PVC VCC connection.
Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify,
gr303Aal2PvcTearDownNotify
gr303Aal2PvcVccVpiB
The VPI value for side B (the ATM side) of a circuit emulation-ATM PVC VCC connection. The
valid range is a number between 0 and 4095.
Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify,
gr303Aal2PvcTearDownNotify
gr303Aal2PvcVccVciB
The VCI value for side B (the ATM side) of a circuit emulation-ATM PVC VCC connection. The
valid range is a number between 0 and 65535.
Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify,
gr303Aal2PvcTearDownNotify
gr303Aal2PvcVccAal2Cid
AAL-2 Channel ID used to pack the CE channel in an ATM trunk. This value will be unique per
ATM trunk. The valid range is a number between 0 and 255. The default value is 0.
Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify,
gr303Aal2PvcTearDownNllllotify
gr303EOCChannelId
EOC Channel Number. If EOC Channel is set to 0 there will be no EOC Channel on the corresponding DS1. Generally the TMC channel should be specified on one of the DS1s in a GR-303
interface group and should be on DS0 no. 12. The valid range is a number between 0 and 24. The
default value is 0.
Associated Traps - gr303EOCChanDownNotify, gr303EOCChanUpNotify
gr303IgBackupEOCStatus
Backup EOC channel status. A null value (5) indicates that the backup EOC has not been configured. The valid range is a number between 1 and 5.
See Table 4-26 for a mapping between numbers and their enumerated type.
Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify,
gr303PPSCommandFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-31
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-26. GR-303 Interface Group Backup EOC Status Codes
Number
Value
Enumerated Type
Description
1
standby-OutOfService
The backup EOC channel becoming Standby OOS.
2
standby-InService
The backup EOC channel becoming Standby IS.
3
active-OutOfService
The backup EOC channel becoming Active OOS.
4
active-InService
The backup EOC channel becoming Active IS.
5
null
The backup EOC has not been configured.
gr303IgBackupTMCStatus
Backup TMC channel status. A null value (5) indicates that the backup TMC has not been configured. The valid range is a number between 1 and 5.
See Table 4-27 for a mapping between numbers and their enumerated type.
Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify,
gr303PPSCommandFailNotify
Table 4-27. GR-303 Interface Group Backup TMC Status Codes
Number
Value
Enumerated Type
Description
1
standby-OutOfService
The backup TMC channel is becoming Standby
OOS.
2
standby-InService
The backup TMC channel is becoming Standby IS.
3
active-OutOfService
The backup TMC channel is becoming Active OOS.
4
active-InService
The backup TMC channel is becoming Active IS.
5
null
The backup TMC has not been configured.
gr303IgId
This is used as an index into the GR303IG table which recognizes a GR303 Interface Group.
Associated Traps - gr303IgCreatedNotify, gr303IgCreateFailNotify, gr303IgModifiedNotify,
gr303IgDeleteNotify, gr303IgModifyFailNotify, gr303IgOutOfServiceNotify,
gr303IgInServiceNotify, gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify,
gr303PPSCommandFailNotify
gr303IgIntfId
This is used as an index into the IG interface table which recognizes GR303 Ig interfaces. This is
used as a second index into this table. The valid range is a number between 1 and 28.
Associated Traps - gr303IgIntfAddedNotify, gr303IgIntfAddFailNotify, gr303IgIntfDeleteNotify
gr303IgPrimaryEOCStatus
Primary EOC channel status. The valid range is a number between 1 and 4.
See Table 4-28 for a mapping between numbers and their enumerated type.
Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify,
gr303PPSCommandFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-32
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-28. GR-303 Interface Group Primary EOC Status Codes
Number
Value
Enumerated Type
Description
1
standby-OutOfService
The primary EOC channel is becoming Standby OOS.
2
standby-InService
The primary EOC channel is becoming Standby IS.
3
active-OutOfService
The primary EOC channel is becoming Active OOS.
4
active-InService
The primary EOC channel is becoming Active IS.
gr303IgPrimaryTMCStatus
Primary TMC channel status. The valid range is a number between 1 and 4.
See Table 4-29 for a mapping between numbers and their enumerated type.
Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify,
gr303PPSCommandFailNotify
Table 4-29. GR-303 Interface Group Primary TMC Status Codes
Number
Value
Enumerated Type
Description
1
standby-OutOfService
The primary TMC channel is becoming Standby OOS.
2
standby-InService
The primary TMC channel is becoming Standby IS.
3
active-OutOfService
The primary TMC channel is becoming Active OOS.
4
active-InService
The primary TMC channel is becoming Active IS.
gr303IntfIgId
This identifies the GR-303 interface group in the GR-303 interface configuration table. The valid
range is a number between 1 and 84.
Associated Traps - gr303IgIntfAddedNotify, gr303IgIntfAddFailNotify, gr303IgIntfDeleteNotify
gr303PPSReasonCode
These reason codes are the result of the GR-303 Path Protection Switching (PPS) command issued
by the user. The valid range is a number between 1 and 8.
See Table 4-30 for a mapping between numbers and their enumerated type.
Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify,
gr303PPSCommandFailNotify
Table 4-30. GR-303 PPS Reason Codes
Number
Value
Enumerated Type
Description
1
forced
Forced path protection switching.
2
normal
Normal path protection switching.
3
userCommandFailedinhibited
The user command failed because path protection is prohibited.
4
userCommandFailedPathOos
The user command failed because path protection is out of service.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-33
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-30. GR-303 PPS Reason Codes (Continued)
Number
Value
Enumerated Type
Description
5
userCommandFailedbadPathId
The user command failed because the path ID is
incorrect.
6
userCommandFailedmaxRetry
The user command failed because the maximum
retry limit was met.
7
userCommandFailedinprogress
The user command failed because switching is in
progress.
8
userCommandFailedunknown
The reason for failure is unknown.
gr303PPSSource
Indicates the initiator of the PPS switching. The valid range is a number between 1 and 6.
See Table 4-31 for a mapping between numbers and their enumerated type.
Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify,
gr303PPSCommandFailNotify
Table 4-31. GR-303 PPS Source Codes
Number
Value
Enumerated Type
Description
1
none
PPS switching was not initiated.
2
byIdt
PPS switching was initiated by Idt.
3
byUser
PPS switching was initiated by the user.
4
byLocalAgent
PPS switching was initiated by the local agent.
5
suspendedByIdt
PPS switching was suspended by Idt.
6
suspendedByLocalAgent
PPS switching was suspended by the local agent.
gr303TMCChannelId
TMC Channel Number. If TMC Channel is set to 0 there will be no TMC channel on the corresponding DS1. Generally the TMC channel should be specified on the one of the DS1s in a GR303 interface group and should be on DS0 no. 24. The valid range is a number between 0 and 24.
The default value is 0.
Associated Traps - gr303TMCChanDownNotify, gr303TMCChanUpNotify
h248CommLinkStatusCode
Indicates the status of communication link between MG and MGC. The valid range is a number
between 1 and 2.
See Table 4-32 for a mapping between numbers and their enumerated type.
Associated Traps - h248CommLinkChangeNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-34
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-32. H248 Communication Links Status Codes
Number
Value
Enumerated Type
Description
1
down
The communication link between the MG and the
MGC is broken.
2
up
The communication link between the MG and the
MGC is established.
h248CommLinkStatusText
Provides specific information about the change in the MG and the MGC communication link status.
Associated Traps - h248CommLinkChangeNotify
h248CongestReasonCode
The reason code for the indication of congested components. Bit 6 and up=unused, bit 5=cpuSP,
bit 4=aal2SP, bit 3=ashSP, bit 2=emeSP, bit 1=cmeSP, and bit 0=tmeSP. The value 0 indicates no
congestion. For a value other than 0, check each bit for an indication of the congestion at corresponding sensor points. For example: value =7 =0x7 indicates that congestion is detected at all the
tmeSP, cmeSP, and emeSPs.
Associated Traps - h248CongestionNotify
h248CongestText
Provides text information, such as the level of congestion, to show the congestion status of H248.
Associated Traps - h248CongestionNotify
h248TermErrorText
Provides specific information about the termination error status.
Associated Traps - h248TermConfigNotify
h248TermErrorCode
An error code for an operation on a termination. The valid range is a number between 1 and 5.
See Table 4-33 for a mapping between numbers and their enumerated type.
Associated Traps - h248TermConfigNotify
Table 4-33. H.248 Termination Error Codes
Number
Value
Enumerated Type
Description
1
none
No error occurred.
2
invalidTID
The termination ID contains characters that
are not valid or generators that were formatted incorrectly.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-35
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-33. H.248 Termination Error Codes (Continued)
Number
Value
Enumerated Type
Description
3
duplicateTID
The same TID has been assigned previously.
4
needPseudoTID
A pseudo TID is required.
5
noAvailableTermCB
An attempt to create an interface has failed
due to the lack of available termination control block.
hdsl2ShdslEndpointAlarmConfProfileName
The unique index associated with this profile.
Associated Traps - hdsl2ShdslEndpointAlarmConfProfileOperationFailNotify
hdsl2ShdslSpanConfProfileName
The unique index associated with this profile.
Associated Traps - hdsl2ShdslSpanConfProfileOperationFailNotify
imaGrpChannelFeState
The current operational state of the far-end IMA Group State Machine. The valid range is a number between 1 and 9.
See Table 4-34 for a mapping between numbers and their enumerated type.
Associated Traps - imaGroupStatusChangeNotify
Table 4-34. IMA GRP Channel End State Codes
Number
Value
Enumerated Type
Description
1
notConfigured
This interface is not configured as an IMA group.
2
startUp
This end is in a state of start-up.
3
startUpAck
The IMA group has received and accepted the configuration parameters of the far-end.
4
cfgAbtUnsupportedM
Unsupported IMA Frame Length. The IMA group does
not accept the frame length parameter sent by the farend.
5
cfgAbtIncSymmetry
Incompatible symmetry. The IMA group does not
accept the group symmetry that the far-end is configured for.
6
cfgAbtOther
The IMA group does not accept the configuration
parameters of the far-end, but does not specify the reason.
7
insufficientLinks
There are fewer active transmit or receive links than
the associated group configuration parameter.
8
blocked
The IMA group has been administratively taken out of
service.
9
operational
This end of the IMA group is operational.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-36
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
imaGrpChannelFailureStatus
The current failure status of the IMA group and the reason why the GTSM is in the down state.
The valid range is a number between 1 and 12.
See Table 4-35 for a mapping between numbers and their enumerated type.
Associated Traps - imaGroupStatusChangeNotify
Table 4-35. IMA GRP Channel Failure Status Codes
Number
Value
Enumerated Type
Description
1
noFailure
No failure.
2
startUpNe
The near-end is in the state of start-up.
3
startUpFe
The far-end is in the state of start-up.
4
invalidMValueNe
The near-end frame length is not valid.
5
invalidMValueFe
The far-end frame length is not valid.
6
failedAssymetricNe
The near-end failed due to incompatible symmetry.
7
failedAssymetricFe
The far-end failed due to incompatible symmetry.
8
insuffLinksNe
The near-end reported less than the minimum number of Tx
links are active or less than the minimum number of Rx links
are active.
9
insuffLinksFe
The far-end reported less than the minimum number of Rx
links are active or less than the minimum number of Tx links
are active.
10
blockedNe
The near-end is administratively out-of-service.
11
blockedFe
The far-end is administratively out-of-service.
12
otherFailure
Other failures.
imaGrpChannelId
The interface index - SSPPCCC.
Associated Traps - imaGrpChannelFailNotify, imaGrpChannelClearedNotify
imaGrpChannelNeState
The current operational state of the near-end IMA Group State Machine. The valid range is a
number between 1 and 9.
See Table 4-36 for a mapping between numbers and their enumerated type.
Associated Traps - imaGroupStatusChangeNotify
Table 4-36. IMA GRP Channel End State Codes
Number
Value
Enumerated Type
Description
1
notConfigured
This interface is not configured as an IMA group.
2
startUp
This end is in a state of start-up.
3
startUpAck
The IMA group has received and accepted the configuration parameters of the far-end.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-37
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-36. IMA GRP Channel End State Codes (Continued)
Number
Value
Enumerated Type
Description
4
cfgAbtUnsupportedM
Unsupported IMA Frame Length. The IMA group does
not accept the frame length parameter sent by the farend.
5
cfgAbtIncSymmetry
Incompatible symmetry. The IMA group does not
accept the group symmetry that the far-end is configured for.
6
cfgAbtOther
The IMA group does not accept the configuration
parameters of the far-end, but does not specify the reason.
7
insufficientLinks
There are fewer active transmit or receive links than the
associated group configuration parameter.
8
blocked
The IMA group has been administratively taken out of
service.
imaGrpChannelStatus
The return value for the imaGrpChannelFailNotify trap. The valid range is a number between 1
and 8.
See Table 4-37 for a mapping between numbers and their enumerated type.
Associated Traps - imaGrpChannelFailNotify, imaGrpChannelClearedNotify
Table 4-37. IMA Group Channel Status Codes
Number
Value
Enumerated Type
Description
1
startupFe
The far-end is in a state of start-up.
2
cfgAbort
The far-end tried to use unacceptable configuration parameters.
3
cfgAbortFe
The far-end reported unacceptable configuration parameters.
4
insuffLinks
Less than the minimum number of Tx links are active or less than
the minimum number of Rx links are active.
5
insuffLinksFe
The far-end reported that less than the minimum number of Rx
links or the minimum number of Tx links are active.
6
blockedNe
The near-end is blocked.
7
blockedFe
The far-end reported that it is blocked.
8
timingSynch
A possible configuration mismatch has occurred (CTC and CTC
modes are not the same at both ends of the IMA virtual links).
imaGrpChannelSymmetry
The symmetry of the IMA group. Symmetric configuration: all ports of an IMA group are configured as full-duplex. With a symmetric configuration the operation is symmetric if no link fails; it
is asymmetric if a link fails so that the active forward and backward links between far-end and
near-end are asymmetric. If the configuration is asymmetric, the operation can never be symmetric. The default value is symOperation. The valid range is a number between 1 and 3.
See Table 4-38 for a mapping between numbers and their enumerated type.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-38
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - imaGroupStatusChangeNotify
Table 4-38. IMA GRP Channel Symmetry Codes
Number
Value
Enumerated Type
Description
1
symOperation
symmetric operation
2
asymOperation
asymmetric operation
3
asymConfiguration
asymmetric configuration
interCpuTxferType
Type of inter-CPU file transfer format. The valid range is a number between 0 and 3.
See Table 4-39 for a mapping between numbers and their enumerated type.
Associated Traps - interCpuTxferTypeChangeNotify
Table 4-39. Inter-CPU Transfer Type
Number
Value
Enumerated Type
Description
0
aal5
File transfer by AAL5.
1
ftp
File transfer by FTP.
2
rsh
File transfer by RSH.
3
nfs
File transfer by NFS.
interfaceFailureReasonCode
Identification of cause for failure in changing the status of an interface. The valid range is a number between 1 and 119.
See Table 4-40 for a mapping between numbers and their enumerated type.
Associated Traps - interfaceModifyFailNotify, signalingModifyFailNotify,
ts16UsageModifyFailNotify, ceServiceTypeModifyFailNotify, channelizationModifyFailNotify,
cRC4ModifyFailNotify, interfaceCreateFailNotify, virtualUNIIntfCreateFailNotify, virtualUNIIntfModifyFailNotify, gr303IgCreateFailNotify, gr303IgModifyFailNotify, gr303IgIntfAddFailNotify,
interfaceBandwidthChangeNotify, v5InterfaceCreateFailNotify, v5InterfaceModifyFailNotify,
v5InterfaceVariantAddFailNotify, v5InterfaceE1LinkAddFailNotify,
v5InterfaceVariantModifyFailNotify, v5InterfaceE1LinkModifyFailNotify,
v5InterfacePhysCChanCreateFailNotify, v5InterfaceLogCChanCreateFailNotify,
v5InterfaceDLCreateFailNotify, v5InterfaceUserPortAddFailNotify,
v5InterfaceUserPortDeleteFailNotify, v5InterfaceE1LinkDeleteFailNotify, vpcPnniIntfCreateFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-39
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-40. Interface Failure Reason Codes
Number
Value
Enumerated Type
Description
1
interfaceInService
Most, if not all, modifications require that the
interface be out of service.
2
interfaceNotNew
Some modifications require that the interface
must never have been in service.
3
interfaceExists
Some modifications, such as setting the interface
type, require that no interface exists. The interface type must be unconfigured.
4
bridgeGroupActive
For setting the bridgeDomainNumber in bridge
or router interfaces. To add an interface to a
bridgeGroup, the bridgeGroup must be in service.
5
signallingNotEnabled
For this interface to be created, signaling must be
enabled.
6
firmwareOutOfDate
The firmware for the I/O module does not work
with this interface.
7
t1SigEnableInterfaceNotSupported
The interface is not supported if T1 signaling is
enabled ts16ForData.
8
ts16ForData
ts16 has been set for passing data and the user is
attempting to turn on signaling.
9
dbcesConfigured
Signaling cannot be disabled because this interface is configured as dbces.
10
signalingEnabled
Signaling is on for at least one of the channels
while trying to change e1 TS16 from CAS to
CCS.
11
cmCardTypeNotSupported
CM_NET interface is only supported by DS3 DS1
OCx and SUPER_DS1 modules
12
cmMultipleIntfNotSupported
Only one interface can be configured as
CM_NET.
13
cmIntfInService
The CM_NET interface is in-service.
14
cmInterfaceConfigured
The CM_NET interface is configured.
15
channelizationEnabled
A port cannot be channelized in order to support
unstructured CE.
16
unstructuredCEConfigured
A port which has been channelized cannot be
configured to support unstructured CE.
17
firmwareOutOfDate-ts16CAS-unsupported
ts16CAS is not supported by the firmware.
18
firmwareOutOfDate-interfaceTypeunsupported
The interface type is not supported by the firmware.
19
firmwareOutOfDate-ts16-unsupported
ts16 is not supported by the firmware.
20
invalidPortMap
The applied port map does not pass consistency
checks, therefore, the port map is not valid.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-40
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-40. Interface Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
21
otherInterfacesExisOnThisPort
The ISDN interface needs all 24 channels on the
port. If any of the channels on that interface are
already configured, the ISDN interface cannot be
defined on that port.
22
intfInIMAgroup
The chanId bit in portMap is 1.
23
errorCTC-portTxClkSrc-notLocal
If the imaGrpChannelNeTxClkMode is set to ctc
then all ports should have the transmitClockSource as localTiming.
24
different-LoopbackConfig-on-Ports
All physical ports included in the portMap must
have the same loopback configuration.
25
imaGChanNeTxClkMode-unsupported
The IMA group channel near-end Tx clock mode
is not supported.
26
intfChange-Disallowed-on-APS-ProtectionPort
An interface cannot be manipulated via a protection port in an APS setup.
27
intferfaceCurrentlyNotSupported
The interface type is not currently supported.
28
failure-at-call-handler
An interface creation failure occurred due to the
call handler.
29
unstructuredCE-payloadloop
Unstructured CE should not have payload loopback as a loopback option.
30
channelConfigModeNotConforming
There was a limitation on the channel mode of
the DSP2D module: if a channel is already inService, all the channel modes of the configured
channels must be the same as the channel inService; all the channel modes of unconfigured
channels can only be configured the same as the
channel inService.
31
usageOfReservedTimeSlot
For HD_E1, do not allow any configuration to be
SET on channel number 1 or 17 (base 1) or
channel 0 or 16 (base 0).
32
virtualIntf-and-AtmSignaling-bothCannotBeEnabled
Both virtual interface and signaling cannot be
enabled at the same time.
33
virtualUni-and-AtmSignaling-bothCannotBeEnabled
Both virtual UNI and signaling cannot be
enabled at the same time.
34
virtualUni-notSupported
Virtual UNI is not supported.
35
atmUni-UbrLoadBalSupp-cannotBeEnabled-whenSignalingDisabled
UBR load balancing cannot be enabled when
signaling is disabled.
36
virtualInterface-notSupported
Virtual interface support is only allowed on APS
module types.
37
card-doesNotSupport-UPC
Only some module types support UPC.
38
atmUni-SvcVpiVci-RangeCheck-Failure
Perform a range check, provided atmSignaling is
enabled vciMinSvc is less than or equal to vciMaxSvc and vpiMinSvc is less than or equal to
vpiMaxSvc.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-41
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-40. Interface Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
39
atmUni-SigVpiVci-Within-Svc-Range
atmUni{Vpi,Vci}Sig should not be within SVC
range.
40
atmUni-Ilmi-Svc-Sig-VpiVci-Clash
If the ILMI protocol status and atmUniSignaling
are both enabled then the ILMI VPI/VCI should
not fall in the SVC range and should not be
equal to signaling VPI/VCI.
41
virtualUNI-VpiNotAvailable
VPI is not available for the virtual UNI.
42
virtualUNI-InvalidVUNIId
The virtual UNI index is not valid.
43
intfNotSupported-with-ds1LineType-d4
If the dsx1LineType is DSX1_D4 channel, the
interface type cannot be atmIma.
44
intfNotSupported-with-ds1LineCodingami
If the dsx1LineCoding is DSX1_AMI channel,
the interface type cannot be atmIma.
45
onlyCEsupported-with-msBitStuffingenabled
If msBitStuffing is enabled, only interface type
circuit emulation is supported.
46
vISuppConnTrafficShapingMutuallyExclusive
The VI support flag and traffic shaping flag are
mutually exclusive.
47
tS16onPortNotCAS
Must have CAS on port for the channel to have
a CAS trunk line interface.
48
channelizationDisabled
Channelization should be enabled to have CAS
trunk line.
49
primaryDS1InterfaceNotConfigured
The primary DS1 interface is not configured.
50
primaryTMCChanNotConfigured
The primary timeslot management channel is
not configured.
51
primaryTMCIntfAlreadyConfiguredInAnotherIg
The primary timeslot management channel
interface is already configured in another interface group.
52
primaryTMCIntfCantBeChanged
The primary timeslot management channel
interface cannot be changed.
53
primaryEOCChanNotConfigured
The primary embedded operation channel is not
configured.
54
primaryEOCIntfAlreadyConfiguredInAn- The primary embedded operation channel interotherIg
face is already configured in another interface
group.
55
primaryTMC-EOCIntfShouldBeSame
The primary timeslot management channel and
embedded operation channel interfaces should
be the same.
56
primaryEOCIntfCantBeChanged
The primary embedded operation channel interface cannot be changed.
57
primaryTMC-BackupTMCIntfCantBeSame
The primary and backup timeslot management
channel interfaces cannot be the same.
58
backupDS1InterfaceNotConfigured
The backup DS1 interface is not configured.
59
backupTMCChanNotConfigured
The backup timeslot management channel is not
configured.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-42
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-40. Interface Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
60
backupTMCIntfAlreadyConfiguredInAn- The backup timeslot management channel interotherIg
face is already configured in another interface
group.
61
backupTMCIntfCantBeChanged
The backup timeslot management channel interface cannot be changed.
62
primaryEOC-BackupEOCIntfCantBeSame
The primary and backup embedded operation
channel interfaces cannot be the same.
63
backupEOCChanNotConfigured
The backup embedded operation channel is not
configured.
64
backupEOCIntfAlreadyConfiguredInAn- The backup embedded operation channel interotherIg
face is already configured in another interface
group.
65
backupTMC-EOCIntfShouldBeSame
The backup timeslot management channel and
embedded operation channel interfaces should
be the same.
66
backupEOCIntfCantBeChanged
The backup embedded operation channel interface cannot be changed.
67
newBWBelowCurrentAllocated
The new bandwidth is below the current allocated bandwidth.
68
newBWBelowCurrentAllocated-SvcsBe- The new bandwidth is below the current alloingDeleted
cated bandwidth, SVC is being deleted.
69
newBWBelowCurrentAllocatedDeletePvcs
The new bandwidth is below the current allocated bandwidth, delete PVC.
70
newBWAboveCurrentAllocated
The new bandwidth is above the current allocated bandwidth.
71
primaryInactive-or-SecondaryActive-In- An interface cannot be deleted if it is in an interIntfProtTable
face protection group which is primary/inactive
or secondary/active.
72
onlyCEsupported-with-msLOSDetection-enabled
If msLOSDetection is enabled, only interface
type circuit emulation is supported.
73
nonMuxNotAllowed-with-FaxRelay
DSP2 modules: If channelMode is
CFG_DSP2_FAX_RELAY, aalMode cannot be
D_dsp2AalMode_aal2_non_multiplexed.
74
invalid-DSPmode-and-AALmode-combi- DSP2 modules: The combination of DSP mode
nation
and AAL mode is not allowed.
75
noBandwidth-For-SignalingConns
No bandwidth for signal connections.
76
unsupported-DSPmode
Unsupported DSP mode.
77
unsupported-AALmode
Unsupported AAL mode.
78
interfaceTypeOfVirtualChannelsInOneDomainMustBeSame
All interfaces in any bridge domain group must
have the same interface type.
79
v5IntfVariantInService
The V5.2 interface variant is already in service.
Changes cannot be accepted until it becomes
OOS.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-43
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-40. Interface Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
80
v5IntfVariantAlreadyExists
The V5.2 interface variant already exists. The
same variant cannot be added in the interface.
81
v5IntfE1LinkInService
The V5.2 interface E1 Link is already in service.
Changes cannot be accepted until it becomes
blocked.
82
v5IntfE1LinkAlreadyExists
The V5.2 interface E1 Link already exists. The
same E1 Link cannot be added in the interface.
83
v5IntfE1LinkCantBeZero
E1 Link physical channel ID cannot be set to 0.
84
v5IntfE1LinkChanMustBeOne
E1 Link physical channel ID must be set to 1.
85
v5IntfPhysCChanAlreadyExists
The V5.2 interface physical C-channels already
exists. The same physical C-channel cannot be
added in the interface.
86
v5IntfPhysCChanCantBeZero
Physical C-channel ID cannot be set to 0.
87
v5IntfPhysCChanMustBeEither16Or15O Physical C-channel ID must be either 16,15, or
r31
31.
88
v5IntfLogCChanAlreadyExists
The V5.2 interface Logical C-channel already
exists. The same Logical C-channel cannot be
added in the interface.
89
v5IntfDLAlreadyExists
The V5.2 interface data link already exists. The
same data link cannot be added in the interface.
90
v5IntfUserPortAlreadyExists
The V5.2 interface user port already exists. The
same user port cannot be added in the interface.
91
v5IntfUserPortInvalidTrunkVccId
The V5.2 interface user port cannot be added if
the AAL2 trunk VccId is not valid.
92
v5IntfUserPortInvalidIwfId
The V5.2 interface user port cannot be added if
the AAL2 trunk remote IWFId is not valid.
93
v5IntfUserPortDuplicateLesPortId
The V5.2 interface user port cannot be added if
the LES port ID is the same.
94
v5IntfUserPortDuplicateLesCid
The V5.2 interface user port cannot be added if
the LES CID is the same.
95
v5IntfUserPortInvalidLogCChanId
The V5.2 interface user port cannot be added if
the Logical C-channel ID is not valid.
96
stratumSyncSourceNotCompositeClockD To configure an interface on a ds0a channel, the
S0A
stratum synchronization source should be composite clock DS0A.
97
v5IntfCantHaveMoreThanOneActivePhy The V5.2 interface cannot have more than one
sCChanForPG1
active Physical C-channels for PG1.
98
v5IntfCantHaveMoreThanOneStandbyP
hysCChanForPG1
The V5.2 interface cannot have more than one
Standby Physical C-channels for PG1.
99
sgFeatureNotEnabled
The Signaling Gateway feature on the port has
not been enabled.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-44
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-40. Interface Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
100
internalResourceErrorInSettingBulkStatsFlag
In statsServerInfoGroup the field bulkStatsMaxUsage would specify the maximum number of
bulk stats records that can be supported in the
system. If the limit is reached, the bulk stats flag
cannot be enabled for that interface because
there is no resource left in the system.
101
previousUserPortDelIsInProgress
This port deletion is in progress.
102
UserPortDeletionBegin
Begin to delete this port.
103
v5InterfacePhysCChanCantBeAddedOn
ExistingE1Link
The physical C-channel could not be added on
the existing E1 link.
104
v5InterfaceOperStatusOOS
The V5.2 interface admin status is in service but
oper status is out of service, a user port cannot
be added or deleted. But a user port can be
added or deleted after admin status is taken out
of service.
105
frf5LmiNotSupported
The frf5Lmi feature is not supported on this I/O
module.
106
aini-SvcVpiVci-RangeCheck-Failure
Perform a range check provided atmSignaling is
enabled. vciMinSvc is less than or equal to vciMaxSvc and vpiMinSvc less than or equal to vpiMaxSvc.
107
aini-SigVpiVci-Within-Svc-Range
The atmUni{Vpi,Vci} Sig should not be within
svc range.
108
aini-UbrLoadBalSupp-cannotBeEnabled- UBR load balancing cannot be enabled when
whenSignalingDisabled
signaling is disabled.
109
vpcPnni-VpiNotAvailable
VPI is not available for the VPC.
110
vpcPnni-InvalidVpcId
The VPC index is not valid if it is not same as the
virtual interface ID.
111
notEnoughMemory
Insufficient system memory to create a new
interface.
112
v5IntfUserPortExceedsMaxPstnPort
The V5.2 interface user ports exceed the maximum number of PSTN ports.
113
v5IntfUserPortExceedsMaxIsdnBraPort
The V5.2 interface user ports exceed the maximum number of ISDN ports.
114
v5IntfUserPortExceedsMaxIsdnPraPort
The V5.2 interface user ports exceed the maximum number of ISDN PRA ports.
115
ds0Number-ChannelNumber-Mismatch
The same DS0 number is not included for this
channel number.
116
vi-Not-Enabled
The virtual interface is not enabled at the main
interface level.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-45
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-40. Interface Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
117
vi-Does-Not-Exist
No virtual interface is configured.
118
vi-CellRate-Too-Lo
The cell rate for virtual interfaces is too low.
119
vcQueuing-ConnTrafficShaping-Mutual- The VC queuing and traffic shaping flag cannot
lyExclusive
be enabled simultaneously.
interfaceIndex
The interface index used for identification in traps. Number value is interpreted as an interface of
the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel
number.
Associated Traps - pnniRtAddrCfgNotify, pnniRtAddrCfgFailNotify, pnniRtAddrModFailNotify,
pnniRtAddrDelFailNotify, pnniRtAddrAddByIlmiNotify, pnniRtAddrDelByIlmiNotify, imaGroupStatusChangeNotify, interfaceCreatedNotify, interfaceDeletedNotify, interfaceModifiedNotify,
interfaceModifyFailNotify, interfaceOutOfServiceNotify, interfaceInServiceNotify, bridgeDomainNumberInvalidNotify, signalingModifyFailNotify, lmiIntfStatusNotify, isdnLapdDownNotify, isdnLapdUpNotify, ts16UsageModifyFailNotify, cirEmSpvcConfiguredNotify, cirEmSpvcConfigFailNotify, cirEmSpvcDeletedNotify, cirEmSpvcModifiedNotify, cirEmSpvcModifyFailNotify,
vbrSpvcConfiguredNotify, vbrSpvcConfigFailNotify, vbrSpvcDeletedNotify, vbrSpvcModifiedNotify, vbrSpvcModifyFailNotify, pnniProtLnkUpAndAdv, pnniProtLinkUpAndNotAdv, pnniProtLnkStatDown, pnniIntfCfgFailNotify, atmSvcIntfLayer2Up, atmSvcIntfLayer2Down, interfaceCreateFailNotify, gr303TMCChanDownNotify, gr303EOCChanDownNotify,
gr303TMCChanUpNotify, gr303EOCChanUpNotify, interfaceBandwidthChangeNotify, lmiDlciStatusNotify, dhpvcChangeNotify, dsp2IntfReroutingSucceededNotify
interfaceNamingResultCode
Various result codes for the operator’s command for setting/deleting interface naming. The valid
range is a number between 1 and 5.
See Table 4-41 for a mapping between numbers and their enumerated type.
Associated Traps - interfaceNamingResultNotify
Table 4-41. Interface Naming Result Codes
Number
Value
Enumerated Type
Description
1
alreadyExistInterfaceName
The interface name must be unique.
2
invalidInterfaceName
The interface name is too long.
3
insufficientMemory
Not enough memory is available to name
the interface.
4
tryToDeleteEmptyTable
The table is already empty and cannot be
deleted.
5
nonexistInterfaceForNaming
The interface does not exist.
interfaceType
The interface type used for identification in traps. A specific interface is associated with each
number. The valid range is a number between 1 and 25.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-46
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
See Table 4-42 for a mapping between numbers and their enumerated type.
Associated Traps - interfaceCreatedNotify, interfaceModifiedNotify, interfaceModifyFailNotify,
interfaceOutOfServiceNotify, interfaceInServiceNotify, signalingModifyFailNotify,
atmSvcIntfLayer2Up, atmSvcIntfLayer2Down, interfaceCreateFailNotify
Table 4-42. Interface Type Codes
Number
Value
Enumerated Type
Description
1
atmUni3-0
ATM User Network Interface version 3.0
2
atmUni3-1
ATM User Network Interface version 3.1
3
iispUser
Interim Inter Switch Protocol User Side
4
iispNetwork
Interim Inter Switch Protocol Network Side
5
circuitEmulation
ATM Circuit Emulation
6
frameRelayUni
Frame Relay User Network Interface
7
pri-isdn-user
Integrated Services Digital Network Primary Rate Interface
User Interface
8
pri-isdn-network
Integrated Services Digital Network Primary Rate Interface
Network Interface
9
terminalEmulation
Terminal Emulation
10
dsp
DSP
11
hdlcPassThrough
High Level Data Link Control Pass Through Interface
12
bridge
Ethernet Bridge
13
routing
Ethernet Routing
14
dbCirEm
Dynamic Bandwidth Circuit Emulation
15
frameRelayNni
Frame Relay Network-to-Network Interface
16
dsp2
DSP2
17
atmIma
ATM Inverse Multiplexing over ATM (IMA)
18
atmPnni1-0
ATM Private Network-to-Network Interface Version 1.0
19
atmUni4-0
ATM User Network Interface Version 4.0
20
atmVnnUni3-1
ATM Virtual Network Navigator User Network Interface
Version 3.1
21
casTrunkLine
Channel Associated Signaling Trunk Line Interface
22
toneAnnce
Tone Announcement Interface
23
gr303
GR-303
24
v5
V5.2
25
aini1-0
ATM Inter Network Interface
ipAddrNumber
The IP address of the host/network to be echoed.
Associated Traps - viprPingTrap
ipAtmAppPvcVccDestAddrA
The destination IP address of an in-band management-ATM connection. Value is an IP address.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-47
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - ipAtmAppPvcVccReqFailNotify, ipAtmAppPvcVccSetupNotify, ipAtmAppPvcVccTearDownNotify, ipAtmBkAppPvcVccReqFailNotify, ipAtmBkAppPvcVccSetupNotify,
ipAtmBkAppPvcVccTearDownNotify
ipAtmAppPvcVccIfB
The interface index for side B, the ATM side, of an in-band management ATM connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is
the port number, and CCC is the channel number.
Associated Traps - ipAtmAppPvcVccReqFailNotify, ipAtmAppPvcVccSetupNotify, ipAtmAppPvcVccTearDownNotify, ipAtmBkAppPvcVccReqFailNotify, ipAtmBkAppPvcVccSetupNotify,
ipAtmBkAppPvcVccTearDownNotify
ipAtmAppPvcVccSubnetMaskA
The subnet mask of the destination IP address. Value is an IP address.
Associated Traps - ipAtmAppPvcVccReqFailNotify, ipAtmAppPvcVccSetupNotify, ipAtmAppPvcVccTearDownNotify, ipAtmBkAppPvcVccReqFailNotify, ipAtmBkAppPvcVccSetupNotify,
ipAtmBkAppPvcVccTearDownNotify
ipAtmAppPvcVccVciB
The VCI value for side B, the ATM side, of an in-band management-to-ATM connection. The valid
range is a number between 0 and 65535.
Associated Traps - ipAtmAppPvcVccReqFailNotify, ipAtmAppPvcVccSetupNotify, ipAtmAppPvcVccTearDownNotify, ipAtmBkAppPvcVccReqFailNotify, ipAtmBkAppPvcVccSetupNotify
ipAtmAppPvcVccVpiB
The VPI value for side B, the ATM side, of an in-band management-to-ATM connection. The valid
range is a number between 0 and 4095.
Associated Traps - ipAtmAppPvcVccReqFailNotify, ipAtmAppPvcVccSetupNotify, ipAtmAppPvcVccTearDownNotify, ipAtmBkAppPvcVccReqFailNotify, ipAtmBkAppPvcVccSetupNotify,
ipAtmBkAppPvcVccTearDownNotify
ipIntfStatus
Return codes for the Route Server module’s IP interface operations. The valid range is a number
between 1 and 36.
See Table 4-43 for a mapping between numbers and their enumerated type.
Associated Traps - viprIpIntfTrap
Table 4-43. IP Interface Status Codes
Number
Value
Enumerated Type
Description
1
intOK
The interface is OK.
2
intIntFailure
Memory corruption has occurred.
3
intTooMany
Exceeds the maximum number of interfaces.
4
intBadSlot
The slot number is not valid.
5
intBadId
The interface ID is not valid.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-48
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-43. IP Interface Status Codes (Continued)
Number
Value
Enumerated Type
Description
6
intBadState
State machine confused
7
intBadTimer
Bad timer value: state machine
8
intExists
The interface already exists.
9
intCantFind
Unused
10
intDelInProgress
Deleting interface: must wait
11
intLockedIdle
The interface has been taken out of service.
12
intBadNetMask
Illegal network mask
13
intShutting
Shutting down - must wait
14
intDisabled
Some subsystem not working
15
intNotHostAddr
Host address is missing
16
intBadIpAddr
Illegal IP address
17
intBadRouterId
Illegal VPN/router ID
18
intBadIntfId
Illegal interface ID
19
intCantFindRouter
No corresponding VPN
20
intCantFindIntf
The interface does not exist.
21
intCantOnSameSubnet
The interface already on this subnet.
22
intCantModIntfAddr
Cannot change interface address
23
intCantModIntfMask
Cannot change interface mask
24
intCantModIntfRipVer
Cannot change rip version number
25
peerIpProblem
This peer IP address is already in use.
26
unsupClass
This address class is not supported.
27
netBcast
This address should not be a network broadcast address.
28
netAddr
This address should not be a network address.
29
hostBcast
This address should not be a host broadcast address.
30
noHostAddr
The host portion of the address entered is missing.
31
loopbackAddr
A loop back address should not be specified.
32
noSubChannels
CoS Set: Cannot bring into service without specifying
Subchannels.
33
missingColor
Cannot bring into service without specifying Subchannels
34
classificationNotEnabled
Classification must be enabled on interfaces.
35
oOSNotAllowedSPVCexists
The interface cannot be taken out of service because the
SPVC subChannel exists.
36
intDHCPNotCfgOnVPN
DHCP is not enabled on VPN, therefore, it is not configurable in the interface.
iptGroupId
A user-selected logical number uniquely representing a protection group within a PSAX system.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-49
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - iptResultNotify
iptLogicalIntfId
A user-selected logical interface number.
Associated Traps - iptResultNotify
iptResultCode
Various result codes for the operator’s command for setting/deleting an interface protection
group. The valid range is a number between 1 and 9.
See Table 4-44 for a mapping between numbers and their enumerated type.
Associated Traps - iptResultNotify
Table 4-44. IPT Result Codes
Number
Value
Enumerated Type
Description
1
interfaceProtectioniptAlreadyExistInterface
Expect another interface to be protected.
2
interfaceProtectioniptInvalidInterface
The interface is not valid.
3
interfaceProtectioniptInvalidParams
The parameters are not valid.
4
interfaceProtectioniptTryToDeleteEmptyTable
The table is already empty and cannot be
deleted.
5
interfaceProtectioniptInvalidConfiguation
The configuration is not valid.
6
interfaceProtectioniptSuccessfulSwichOver
The interface has switched over to the secondary interface.
7
interfaceProtectioniptSuccessfulSwichBack
The interface has switched back from the
secondary interface.
8
interfaceProtectioniptFailedSwichOver
The interface has failed to switch over to the
secondary interface.
9
interfaceProtectioniptFailedSwichBack
The interface has failed to switch back from
the secondary interface.
ipTypeReasonCode
The indicator of which IP address had the problem. The valid range is a number between 1 and
32.
See Table 4-45 for a mapping between numbers and their enumerated type.
Associated Traps - ipOrMaskInvalidNotify
Table 4-45. IP Type Reason Codes
Number
Value
Enumerated Type
Description
1
siteEtherIpAddr
The IP address for ethernet access to the site.
2
siteEtherIpMask
The IP mask for ethernet access to the site.
3
siteGatewayAddr
The IP address for gateway access to the site.
4
siteRemoteMgrAddr1
Remote manager IP Address 1, where the trap
will be sent.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-50
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-45. IP Type Reason Codes (Continued)
Number
Value
Enumerated Type
Description
5
siteRemoteMgrAddr2
Remote manager IP Address 2, where the trap
will be sent.
6
siteRemoteMgrAddr3
Remote manager IP Address 3, where the trap
will be sent.
7
siteRemoteMgrAddr4
Remote manager IP Address 4, where the trap
will be sent.
8
siteRemoteMgrAddr5
Remote manager IP Address 5, where the trap
will be sent.
9
inBandPrimaryIpAddress
IP address of the switch when the switch is
accessed over the primary in-band connection.
10
inBandPrimaryIpMask
IP address subnet mask of the primary in-bandmanagement IP address.
11
inBandBackupIpAddress
IP address of the switch when the switch is
accessed over the secondary in-band connection.
12
inBandBackupIpMask
IP address subnet mask of the secondary in-band
management IP address.
13
siteIncorrectGatewaySubnet
Incorrect gateway IP address subnet. The subnet
of the gateway IP address must be either the
same as the subnet of the switch/CPU IP address
or the same as the subnet of the in-band IP
address.
14
siteGatewayInbandAddrMatch
This enumerated type is not in use.
15
siteIncorrectInbandSubnet
This enumerated type is not in use.
16
siteIncorrectEthernetSubnet
The subnet of the CPU IP address is the same as
the in-band IP address.
17
cpuIpSameAsSwitchIpAddr
The CPU IP and switch IP addresses are the
same, this configuration is not valid.
18
cpuIpAddrInvalid
The CPU IP address is not valid.
19
cpuAndIpMaskInvalid
The CPU and IP mask are not valid.
20
switchAndCpuIpSubnetMismatch
The switch IP address and the CPU IP address
are not in the same subnet.
21
switchIpAddrInvalid
The newly configured switch IP address is not a
valid IP address. A valid IP address must belong
to class A, B, or C IP addresses, or is a broadcast
IP address.
22
switchAndIpMaskInvalid
The combination of the switch IP address and
the IP mask are not valid.
23
cpuIpMaskClashWithInbandSubnet
The newly configured IP mask puts the CPU IP
address and the in-band IP address in the same
subnet, which is incorrect.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-51
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-45. IP Type Reason Codes (Continued)
Number
Value
Enumerated Type
Description
24
switchIpMaskClashWithInbandSubnet
The newly configured IP mask puts the switch IP
address and the in-band IP address in the same
subnet, which is incorrect.
25
siteGatewayAddrInvalid
The newly configured gateway IP address is not
a valid IP address. A valid IP address must
belong to class A, B, or C IP addresses, or is a
broadcast IP address.
26
siteGatewayInbandAddrClash
The newly configured gateway IP address is the
same as the in-band IP address, which is incorrect.
27
unableToApplyGatewayIpAddr
Unable to apply the Gateway IP address.
28
unableToSetCpuIpInEPROM
Cannot apply the CPU IP address into EPROM.
29
unableToApplyCpuIpAddr
Unable to apply the CPU IP address.
30
unableToApplySwitchIpAddr
Cannot set the switch IP address into EPROM.
31
unableToRevertBackToCpuIpAddr
Unable to revert back to the CPU IP address.
32
gatewayAndCpuIpSubnetMismatch
This enumerated type is not in use.
isdnIntfDChanId
D-channel Number - if the D-channel number is 0 no LAPD will run on this PRI-ISDN interface.
The valid range is a number between 0 and 24. The default value is 0.
Associated Traps - isdnLapdDownNotify, isdnLapdUpNotify
iuaAsId
Application Server Identification Value.
Associated Traps - iuaAspStateChangeNotify, iuaFailOverBufferingStartNotify, iuaFailOverBufferOverflowNotify, iuaRecoveryTimerExpireNotify, iuaAsStateChangeNotify
iuaAspId
Application Server Process Identification. Presented when ASP ID is given through ASP UP message.
Associated Traps - iuaAspStateChangeNotify, iuaErrorNotify
iuaAspState
The current Application Server Process state. Based on ASPM messages.
See Table 4-46 for a mapping between numbers and their enumerated type.
Associated Traps - iuaAspStateChangeNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-52
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-46. IUA Application Server Process State Codes
Number
Value
Enumerated Type
Description
1
active
The remote IUA peer at the ASP is available and
traffic is active
2
inactive
The remote IUA peer at the ASP is available but
traffic is stopped
3
down
The ASP is unavailable and/or the related SCTP
association is down.
iuaAspEpAssocId
Association Identification. The value identifying the association for that endpoint. This value is
extracted from the SCTP association ID value returned by SCTP when the association is established to that endpoint.
Associated Traps - iuaSctpStateChangeNotify
iuaAspEpAssocState
The state of this SCTP association.
See Table 4-47 for a mapping between numbers and their enumerated type.
Associated Traps - iuaSctpStateChangeNotify
Table 4-47. IUA Association State Codes
Number
Value
Enumerated Type
Description
1
closed
The SCTP association has not been established.
2
established
The SCTP association has been established.
iuaAspEpId
Application Server Process Endpoint Identification Value.
Associated Traps - iuaSctpStateChangeNotify, iuaAspStateChangeNotify, iuaErrorNotify
iuaAsState
The current Application Server state. The valid range is a number between 1 and 4. See
Table 4-48 for a mapping between numbers and their enumerated type.
Associated Traps - iuaAsStateChangeNotify
Table 4-48. IUA Application Server State Codes
Number
Value
1
Enumerated Type
active
Description
The AS is available and traffic is active.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-53
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-48. IUA Application Server State Codes (Continued)
Number
Value
Enumerated Type
Description
2
inactive
The AS is available but no traffic is active.
3
down
The AS is unavailable.
4
pending
The operational status of the last remaining
active ASP in the AS has changed from
active to inactive or is down.
iuaClientServerOption
The role of SG for initiating the SCTP associations. The valid range is a number between 1 and 2.
See Table 4-49 for a mapping between numbers and their enumerated type.
Associated Traps - iuaClientServerOptionModifyFailNotify
Table 4-49. Client/Server Option Codes
Number
Value
Enumerated Type
Description
1
server
Wait for SCTP association establishment.
2
client
Initiate SCTP association establishment.
iuaDiagInfo
Diagnostic information of the IUA protocol.
Associated Traps - iuaErrorNotify
iuaErrorCode
An error code indicating the reason for the IUA error message. The valid range is a number
between 1 and 15.
See Table 4-50 for a mapping between numbers and their enumerated type.
Associated Traps - iuaErrorNotify
Table 4-50. IUA Error Codes
Number
Value
Enumerated Type
Description
1
invalidVersion
The version is not valid.
2
invalidInterfaceId
The interface identifier is not valid.
3
unsupportedMsgClass
The message class is not supported.
4
unsupportedMsgType
The message type is not supported.
5
unsupportedTrafficMode
The traffic handling mode is not supported.
6
unexpectedMsg
The message was not expected.
7
protocolError
A protocol error has occurred.
8
unsupportedIIdType
The interface identifier type is not supported.
9
invalidStreamId
The stream identifier is not valid.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-54
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-50. IUA Error Codes (Continued)
Number
Value
Enumerated Type
Description
10
unassignedTEI
The Terminal Endpoint Identifier (TEI) is
not assigned.
11
unrecognizedSAPI
The Service Access Point Identifier (SAPI) is
not recognized.
12
invalidTEISAPI
The TEI and SAPI combination is not valid.
13
managementBlocking
Refused due to management blocking.
14
aspIdRequired
An ASP identifier is required.
15
invalidASPId
The ASP identifier is not valid.
iuaFailOverBuffSize
Size of the failover retransmission buffer. Recommended value is 64 KB. Only valid when buffering is enabled.
Associated Traps - iuaFailOverBufferingStartNotify, iuaFailOverBufferOverflowNotify, iuaFailOverBuffSizeModifyFailNotify
iuaHeartBeat
Activates or deactivates the heartbeat procedure at the IUA level. The valid range is a number
between 1 and 2.
See Table 4-51 for a mapping between numbers and their enumerated type.
Associated Traps - iuaHeartBeatModifyFailNotify
Table 4-51. IUA Heartbeat Codes
Number
Value
Enumerated Type
Description
1
on
Heartbeat is enabled.
2
off
Heartbeat is disabled. No BEAT messages are
sent but BEAT messages received are
responded.
iuaLocalPort
Identifies the port of the IUA service. The SCTP Registered User Port Number Assignment for IUA
is 9900.
Associated Traps - iuaLocalPortModifyFailNotify
iuaTBeatValue
Initial value of the heartbeat timer TBeat. Recommended value is 1000 milliseconds.
Associated Traps - iuaTBeatValueModifyFailNotify
iuaTrValue
Initial value of the recovery timer T(r). Recommended value is 3000 milliseconds. Buffering is
disabled when T(r) is set to value of 0.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-55
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - iuaTrValueModifyFailNotify, iuaFailOverBufferingStartNotify, iuaRecoveryTimerExpireNotify
limStatus
The current status of the LIM module. The LIM status will be reported by the working module
and by the protection module if protection is enabled. The valid range is a number between 1 and
3. The default value is noAlarm.
See Table 4-52 for a mapping between numbers and their enumerated type.
Associated Traps - limStatusChangedNotify
Table 4-52. Line Interface Module Status Codes
Number
Value
Enumerated Type
Description
1
noAlarm
The LIM module is present and functioning
properly.
2
failed
The LIM module is not present or has failed.
3
unSupp
The LIM module is not supported for the I/O
module (i.e front facing ports). This is also
for modules in slots that do not support LIM
modules (e.g., slot 13, 14, 15 in a
PSAX 4500).
lineStatus
The bit map of the status of a line connected to a port.
Associated Traps - lineStatusChangedNotify
ds1LineStatus
This variable indicates the Line Status of the interface. It contains loopback, failure, received
alarm, and transmitted alarm information. The dsx1LineStatus is a bit map represented as a sum,
therefore, it can represent multiple failures (alarms) and a LoopbackState simultaneously.
ds1NoAlarm should be set if and only if no other flag is set. If the ds1LoopbackState bit is set, the
loopback in effect can be determined from the ds1LoopbackConfig object. The valid range is a
number between 1 and 8192.
See Table 4-53 for a mapping between numbers and their enumerated type.
Table 4-53. DS1 Line Status Codes
Number
Value
Enumerated Type
Description
1
dsx1NoAlarm
No alarm present
2
dsx1RcvFarEndLOF
Far-end LOF (that is, yellow alarm)
4
dsx1XmtFarEndLOF
Near-end sending LOF indication
8
dsx1RcvAIS
Far-end sending AIS
16
dsx1XmtAIS
Near-end sending AIS
32
dsx1LossOfFrame
Near-end LOF (red alarm)
64
dsx1LossOfSignal
Near-end loss of signal
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-56
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-53. DS1 Line Status Codes
Number
Value
Enumerated Type
Description
128
dsx1LoopbackState
Near-end is looped
256
dsx1T16AIS
E1 TS16 AIS
512
dsx1RcvFarEndLOMF
Far-end sending TS16 LOMF
1024
dsx1XmtFarEndLOMF
Near-end sending TS16 LOMF
2048
dsx1RcvTestCode
Near-end detects a test code
4096
dsx1OtherFailure
Any other line status not shown in this table
8192
dsx1RmtLoopback
Far end loopback
ds0aLineStatus
This variable indicates the Line Status of the interface. The dsx1LineStatus is a bit map represented as a sum, therefore, it can represent multiple failures (alarms) and a LoopbackState simultaneously. ds0aNoAlarm should be set if and only if no other flag is set. If the ds0aLoopbackState
bit is set, the loopback in effect can be determined from the ds0aLoopbackConfig object. The valid
range is a number between 1 and 16.
See Table 4-54 for a mapping between numbers and their enumerated type.
Table 4-54. DS0A Line Status Codes
Bit Value
Alarm
Description
1
NoAlarm
No alarm is present.
2
LossOfSignal
Near-end loss of signal.
4
RcvAIS
Near-end receiving all 1’s.
8
RcvTestCode
Near-end detects a test code specified by the user.
16
OtherFailure
Any other line status not defined here.
The following table shows line status alarms for the 12-Port MD
DS1/E1/DS0A CES module (DS1 mode):
Table 4-55. DS1 Line Status Alarms
Bit Value
Alarm
Description
1
NoAlarm
No alarm present
2
RcvFarEndLOF
The PSAX system is receiving an RAI alarm. The RAI
(yellow) alarm is usually sent by the far-end device
when an LOS, AIS, or LOF condtion is detected on its
receive port.
4
XmtFarEndLOF
Near-end sending LOF indication
8
RcvAIS
Far-end sending AIS (red alarm)
16
XmtAIS
Near-end sending AIS
32
LossOfFrame
Near-end LOF
64
LossOfSignal
Near-end loss of signal
128
LoopbackState
Near-end is looped
256
T16AIS
E1 TS16 AIS (not valid for DS1)
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-57
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-55. DS1 Line Status Alarms
Bit Value
Alarm
Description
512
RcvFarEndLOMF
Far-end sending TS16 LOMF (not valid for DS1)
1024
XmtFarEndLOMF
Near-end sending TS16 LOMF (not valid for DS1)
2048
RcvTestCode
Near-end detects a test code
4096
OtherFailure
Any other line status not shown in this table
8192
RmtLoopback
Far-end loopback
The following table shows line status alarms for the 12-Port MD
DS1/E1/DS0A CES module (E1 mode):
Table 4-56. E1 Line Status Alarms
Bit Value
Alarm
Description
1
NoAlarm
No alarm present
2
RcvFarEndLOF
The PSAX system is receiving an RAI alarm. The RAI
(yellow) alarm is usually sent by the far-end device
when an LOS, AIS, or LOF condtion is detected on its
receive port.
4
XmtFarEndLOF
Near-end sending LOF indication
8
RcvAIS
Far-end sending AIS (red alarm)
16
XmtAIS
Near-end sending AIS
32
LossOfFrame
Near-end LOF
64
LossOfSignal
Near-end loss of signal
128
LoopbackState
Near-end is looped
256
T16AIS
E1 TS16 AIS
512
RcvFarEndLOMF
Far-end sending TS16 LOMF
1024
XmtFarEndLOMF
Near-end sending TS16 LOMF
2048
RcvTestCode
Near-end detects a test code
4096
OtherFailure
Any other line status not shown in this table
ds3LineStatus
Line status codes for DS3 modules. The valid range is a number between 1 and 16.
See Table 4-57 for a mapping between numbers and their enumerated type.
Table 4-57. DS3 Module Line Status Codes
Bit Value
Alarm
Description
1
dsx3NoAlarm
No alarm present
2
dsx3RcvRAIFailure
Receiving yellow/remote alarm indication
4
dsx3XmitRAIAlarm
Transmitting yellow/remote alarm indication
8
dsx3RcvAIS
The PSAX system detected an AIS error on its receiving port.
16
dsx3XmitAIS
Transmitting AIS failure state
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-58
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-57. DS3 Module Line Status Codes (Continued)
Bit Value
Alarm
Description
32
dsx3LOF
Receiving LOF failure state.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to DirectMapping, this line
status indicates an error condition on the DS3 framing.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, this line status indicates
an error condition on either the DS3 framing or the Plcp framing.
64
dsx3LOS
Receiving LOS failure state
128
dsx3LoopbackState
Looping the received signal
256
dsx3RcvTestCode
Receiving a test pattern
512
dsx3OtherFailure
Any other line status not shown in this table
1024
dsx3RcvRmtAIS
Receiving FEAC AIS code from remote. The far-end device has
sent an FEAC AIS code to the PSAX system to indicate that the
far-end device has detected an AIS condition on its receiving
port.
2048
dsx3RcvRmtOOF
Receiving FEAC OOF code from remote. The far-end device has
sent an FEAC OOF code to the PSAX system to indicate that the
far-end device has detected an OOF condition on its receiving
port.
4096
dsx3RcvRmtLOS
Receiving FEAC LOS code from remote. The far-end device has
sent an FEAC LOS code to the PSAX system to indicate that the
far-end device has detected an LOS condition on its receiving
port.
8192
dsx3RcvRmtIdle
The PSAX system detected a DS3 idle signal on its receiving port.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, the PSAX system:
1) Displays the values RcvRmtIdle and RcvLCD in the Line
Status field. 2) Transmits a Plcp yellow alarm. 3) Takes the interface out of service because of the Plcp Framing.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this channel is set to DirectMapping, the
PSAX system:
1) Displays the value RcvRmtIdle in the Line Status field.
2) Leaves the interface in service.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-59
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-57. DS3 Module Line Status Codes (Continued)
Bit Value
Alarm
Description
16384
dsx3RmtLoopback
Far end remote loopback
32768
dsx3RcvLCD
The PSAX system detected a receiving loss of cell delineation signal on its receiving port.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to DirectMapping, this line
status indicates that the PSAX system has received 7 consecutive
cells with either single bit or multi-bit errors in the header. This
condition will not clear until the PSAX system has received 6
consecutive cells with no header errors.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, this error condition
may be displayed whenever there is an error condition on either
the DS3 framing or the Plcp framing.
65536
dsx3RcvIdle
Receiving Idle from remote.
The following bit map table describes line status codes for the 2-Port DS3
ATM module. This code is displayed in the Line Status field on the DS3 Configuration and the DS3 Port and Channel Configuration windows.
Table 4-58. 2-Port DS3 ATM Module Line Status Codes
Bit Value
Alarm
Description
1
dsx3NoAlarm
No alarm present.
2
dsx3RcvRAIFailure
Receiving yellow/remote alarm indication
4
dsx3XmitRAIAlarm
Transmitting yellow/remote alarm indication
8
dsx3RcvAIS
The PSAX system detected an AIS error on its receiving port.
16
dsx3XmitAIS
Transmitting AIS failure state
32
dsx3LOF
Receiving LOF failure state.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to DirectMapping, this line
status indicates an error condition on the DS3 framing.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, this line status indicates
an error condition on either the DS3 framing or the Plcp framing.
64
dsx3LOS
Receiving LOS failure state
128
dsx3LoopbackState
Looping the received signal
256
dsx3RcvTestCode
Receiving a test pattern
512
dsx3OtherFailure
Any other line status not shown in this table
1024
dsx3RcvRmtAIS
Receiving FEAC AIS code from remote. The far-end device has
sent an FEAC AIS code to the PSAX system to indicate that the
far-end device has detected an AIS condition on its receiving
port.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-60
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-58. 2-Port DS3 ATM Module Line Status Codes (Continued)
Bit Value
Alarm
Description
2048
dsx3RcvRmtOOF
Receiving FEAC OOF code from remote. The far-end device has
sent an FEAC OOF code to the PSAX system to indicate that the
far-end device has detected an OOF condition on its receiving
port.
4096
dsx3RcvRmtLOS
Receiving FEAC LOS code from remote. The far-end device has
sent an FEAC LOS code to the PSAX system to indicate that the
far-end device has detected an LOS condition on its receiving
port.
8192
dsx3RcvRmtIdle
The PSAX system detected a DS3 idle signal on its receiving port.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, the PSAX system:
1) Displays the values RcvRmtIdle and RcvLCD in the Line
Status field. 2) Transmits a Plcp yellow alarm. 3) Takes the interface out of service because of the Plcp Framing.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this channel is set to DirectMapping, the
PSAX system:
1) Displays the value RcvRmtIdle in the Line Status field.
2) Leaves the interface in service.
16384
dsx3RmtLoopback
Far end remote loopback
32768
dsx3RcvLCD
The PSAX system detected a receiving loss of cell delineation signal on its receiving port.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to DirectMapping, this line
status indicates that the PSAX system has received 7 consecutive
cells with either single bit or multi-bit errors in the header. This
condition will not clear until the PSAX system has received 6
consecutive cells with no header errors.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, this error condition
may be displayed whenever there is an error condition on either
the DS3 framing or the Plcp framing.
65536
dsx3RcvIdle
Receiving Idle from remote.
e1LineStatus
This variable indicates the Line Status of the interface. It contains loopback, failure, received
’alarm’ and transmitted ’alarm’ information. The e1LineStatus is a bit map represented as a sum,
therefore, it can represent multiple failures (alarms) and a LoopbackState simultaneously.
e1NoAlarm should be set if and only if no other flag is set. If the e1LoopbackState bit is set, the
loopback in effect can be determined from the e1LoopbackConfig object. The valid range is a
number between 1 and 8192.
See Table 4-59 for a mapping between numbers and their enumerated type.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-61
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-59. Enhanced E1 Line Status Codes
Bit Value
Alarm
Description
1
e1NoAlarm
No alarm present
2
e1RcvFarEndLOF
Far-end LOF (yellow alarm)
4
e1XmtFarEndLOF
Near-end sending LOF indication
8
e1RcvAIS
Far-end sending AIS
16
e1XmtAIS
Near-end sending AIS
32
e1LossOfFrame
Near-end LOF (red alarm)
64
e1LossOfSignal
Near-end loss of signal
128
e1LoopbackState
Near-end is looped
256
e1T16AIS
E1 TS16 AIS
512
e1RcvFarEndLOMF
Far-end sending TS16 LOMF
1024
e1XmtFarEndLOMF
Near-end sending TS16 LOMF
2048
e1RcvTestCode
Near-end detects a test code
4096
e1OtherFailure
Any other line status not shown in this table
8192
e1RmtLoopback
Far end loopback
e3LineStatus
Line status codes for E3 modules. The valid range is a number between 1 and 512.
See Table 4-60 for a mapping between numbers and their enumerated type
The following bit map table describes line status codes for the 2-Port E3 ATM
module. This code is displayed in the Line Status field on the E3 Configuration and the E3 Port and Channel Configuration windows.
Table 4-60. E3 Line Status Codes
Bit Value
Alarm
Description
1
e3NoAlarm
No alarm present
2
e3RcvRAIFailure
Receiving yellow/remote alarm indication
4
e3XmitRAIAlarm
Transmitting yellow/remote alarm indication
8
e3RcvAIS
The PSAX system detected an AIS error on its receiving port
16
e3XmitAIS
Transmitting AIS failure state
32
e3LOF
Receiving LOF failure state
64
e3LOS
Receiving LOS failure state
128
e3LoopbackState
Looping the received signal
256
e3RcvTestCode
Receiving a test pattern
512
e3OtherFailure
Any other line status not shown in this table
ethernetLineStatus
Line status codes of Ethernet modules. The valid range is a number between 1 and 16.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-62
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
See Table 4-61 for a mapping between numbers and their enumerated type.
Table 4-61. Ethernet Module Line Status Codes
Bit Value
Line Status
Description
1
Down
Indicates that no cable is connected to this port. The
status will remain to be Down until a correct Ethernet
cable is plugged into this port.
2
10baseT-FullDuplex
Indicates the line status that was auto-negotiated or
preconfigured for this port. The line speed is 10 Mbps
and the line is full duplex, which means that the port
can send and receive data simultaneously.
4
10baseT-HalfDuplex
Indicates the line status that was auto-negotiated or
preconfigured for this port. The line speed is 10 Mbps
and the line is half duplex, which means that the port
can only send or receive data during a given time
period.
8
100baseT-FullDuplex
This is the line status that was auto-negotiated or preconfigured for this port. The line speed is 100 Mbps and
the line is full duplex, which means that the port can
send and receive data simultaneously.
16
100baseT-HalfDuplex
This is the line status that was auto-negotiated or preconfigured for this port. The line speed is 100 Mbps and
the line is half duplex, which means that the port can
only send or receive data during a given time period.
ocxLineStatus
Line status codes for optical modules. The valid range is a number between 1 and 4096.
See Table 4-62 for a mapping between numbers and their enumerated type.
Table 4-62. Optical Modules Line Status Codes
Bit Value
Alarm
Description
1
ocxNoAlarm
No alarm present
2
ocxRcvRAIFailure
Receiving yellow/remote alarm indication
4
ocxXmitRAIAlarm
Transmitting yellow/remote alarm indication
8
ocxRcvAIS
Receiving AIS failure state
16
ocxXmitAIS
Transmitting AIS failure state
32
ocxLOF
Receiving LOF failure state
64
ocxLOS
Receiving LOS failure state
128
ocxLoopbackState
Looping the received signal
256
ocxRcvTestCode
Receiving a test pattern
512
ocxOtherFailure
Any other line status not shown in this table
1024
ocxLCD
Receiving loss of cell delineation
2048
ocxLRDI
Receiving line RDI failure state
4096
ocxPRDI
Receiving path RDI failure state
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-63
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
sts1LineStatus
The following bit map table describes line status codes for the 1-Port Channelized STS-1e, T1 Format module. This code is displayed in the Line Status
field on the DS3 Configuration and the DS3 Port and Channel Configuration
windows.
Table 4-63. 1-Port Channelized STS-1e, T1 Format Module Line Status Codes
Bit Value
Alarm
Description
1
dsx3NoAlarm
No alarm present
2
dsx3RcvRAIFailure
Receiving yellow/remote alarm indication
4
dsx3XmitRAIAlarm
Transmitting yellow/remote alarm indication
8
dsx3RcvAIS
The PSAX system detected an AIS error on its receiving port.
16
dsx3XmitAIS
Transmitting AIS failure state
32
dsx3LOF
Receiving LOF failure state.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to DirectMapping, this
line status indicates an error condition on the DS3 framing.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, this line status
indicates an error condition on either the DS3 framing or the
Plcp framing.
64
dsx3LOS
Receiving LOS failure state
128
dsx3LoopbackState
Looping the received signal
256
dsx3RcvTestCode
Receiving a test pattern
512
dsx3OtherFailure
Any other line status not shown in this table
1024
dsx3RcvRmtAIS
Receiving FEAC AIS code from remote. The far-end device
has sent an FEAC AIS code to the PSAX system to indicate
that the far-end device has detected an AIS condition on its
receiving port.
2048
dsx3RcvRmtOOF
Receiving FEAC OOF code from remote. The far-end device
has sent an FEAC OOF code to the PSAX system to indicate
that the far-end device has detected an OOF condition on its
receiving port.
4096
dsx3RcvRmtLOS
Receiving FEAC LOS code from remote. The far-end device
has sent an FEAC LOS code to the PSAX system to indicate
that the far-end device has detected an LOS condition on its
receiving port.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-64
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-63. 1-Port Channelized STS-1e, T1 Format Module Line Status Codes (Continued)
Bit Value
Alarm
Description
8192
dsx3RcvRmtIdle
The PSAX system detected a DS3 idle signal on its receiving
port.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, the PSAX system:
1) Displays the values RcvRmtIdle and RcvLCD in the Line
Status field. 2) Transmits a Plcp yellow alarm. 3) Takes the
interface out of service because of the Plcp Framing.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this channel is set to DirectMapping,
the PSAX system:
1) Displays the value RcvRmtIdle in the Line Status field.
2) Leaves the interface in service.
16384
dsx3RmtLoopback
Far end remote loopback
32768
dsx3RcvLCD
The PSAX system detected a receiving loss of cell delineation
signal on its receiving port.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to DirectMapping, this
line status indicates that the PSAX system has received 7 consecutive cells with either single bit or multi-bit errors in the
header. This condition will not clear until the PSAX system
has received 6 consecutive cells with no header errors.
If the Cell Mapping field on the DS3 Port and Channel Configuration window for this port is set to Plcp, this error condition may be displayed whenever there is an error condition
on either the DS3 framing or the Plcp framing.
twoWireSourceLineStatus
Line status codes for the Voice 2 Wire Office, and Voice 2 Wire Station modules. The valid range is
a number between 1 and 32.
See Table 4-64 for a mapping between numbers and their enumerated type.
Table 4-64. 4-Port Voice 2-Wire Office and 8-Port Voice 2-Wire Station Line Status Codes
Bit Value
Alarm
Description
1
NoAlarm
No alarm is present
2
SignalingFailureState
Signals failure state
4
FacilityLoopBack
Not currently supported
8
Maintenance
Maintenance
16
Out Of Service
Out of Service
32
OtherFailure
Any other line status not shown in this table
lmiDlciOperStatus
The operational status of the LMI protocol. The valid range is a number between 1 and 2.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-65
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
See Table 4-65 for a mapping between numbers and their enumerated type.
Associated Traps - lmiDlciStatusNotify
Table 4-65. LMI DLCI Operational Status Codes
Number
Value
Enumerated Type
Description
1
outOfService
Protocol is out of service.
2
inService
Protocol is in service.
ntomProtectionGroupId
A user selected logical number representing the ntomProtectionGroup.
Associated Traps - ntomProtectionGroupCreateNotify, ntomProtectionGroupCreateFailNotify,
ntomProtectionGroupModifyNotify, ntomProtectionGroupModifyFailNotify, ntomProtectionGroupDeleteNotify, ntomProtectionGroupSlotAdd, ntomProtectionGroupSlotRemove, ntomProtectionSlotModifyFail
ntomProtectionReasonCode
An identified reason why an N to M protection group could not be created, modified, or a command could not be applied. It is also used to indicate if a switchover has taken place and is used to
indicate the status of the protection port. The valid range is a number between 1 and 20.
See Table 4-66 for a mapping between numbers and their enumerated type.
Associated Traps - ntomProtectionSwitchoverNotify, ntomProtectionGroupCreateFailNotify,
ntomProtectionGroupModifyFailNotify, ntomProtectionGroupSlotAdd, ntomProtectionGroupSlotRemove, ntomProtectionSlotModifyFail
Table 4-66. ntom Protection Reason Codes
Number
Value
Enumerated Type
Description
1
ntomSwitchProtectionToActive
The protection module has switched to active.
2
ntomSwitchProtectionToStandby
The protection module has switched to standby.
3
ntomMoreThan1SlotInOneToOneCo More than 1 slot is being configured in the one to
nfig
one configuration.
4
ntomAddedProtectionSlot
A protection slot was added.
5
ntomAddedWorkingSlot
A working slot was added.
6
ntomRemovedProtectionSlot
A slot configured as protection was removed.
7
ntomRemovedWorkingSlot
A slot configured as working was removed.
8
ntomProtectionSlotNotUnConfigured
This protection slot is not fully unconfigured.
9
ntomProtectionGroupNotActive
The specified protection group is not active.
10
ntomProtectionGroupAlreadyActive The specified protection group is already active.
11
ntomProtectionUnsuppConfig
A generic message indicating that the configuration is not supported.
12
ntomProtectionSlotAlreadyPartOfAnotherGrp
The slot configured as protection is already part of
another group.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-66
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-66. ntom Protection Reason Codes (Continued)
Number
Value
Enumerated Type
Description
13
ntomWorkingSlotAlreadyPartOfAn- The slot configured as working is already part of
otherGrp
another group.
14
ntomSlotNotInWorkingMode
The specified slot is not configured as working.
15
ntomNoProtectionResourcesAvailable
There are no protection modules available for protection.
16
ntomWorkingAlreadyBeingProtected
This working module is already being protected.
17
ntomSlotTypesMismatch
The slots in a given group do not match.
18
ntomInvalidGroupId
This group ID is not valid.
19
ntomCardTypeNotSuppForProt
The module inserted in a protection slot is not
supported because the module does not have support for n to m protection.
20
ntomInvalidConfigurationInCurrChassis
Since protection is a scheme which is chassis type
specific, this trap indicates if a particular chassis
can support the configuration.
oamActDeactIfB
The interface index for an OAM CC connection. Number value is interpreted as an interface of
the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel
number.
Associated Traps - oamActDeactResultNotify
oamActDeactVciB
The VCI value for an OAM CC connection. The valid range is a number between 0 and 65535.
Associated Traps - oamActDeactResultNotify
oamActDeactVpiB
The VPI value for an OAM CC connection. The valid range is a number between 0 and 4095.
Associated Traps - oamActDeactResultNotify
oamActDeactResultCode
Various result codes for the operator’s command for OAM Activation-Deactivation. The valid
range is a number between 1 and 98.
See Table 4-67 for a mapping between numbers and their enumerated type.
Associated Traps - oamActDeactResultNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-67
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-67. OAM Activation Deactivation Result Codes
Number
Value
Enumerated Type
Description
1
eteCCActSuccTowardsFarEnd
The end-to-end continuity check activation
request was successfully sent toward the far-end.
2
eteCCActSuccTowardsNearEnd
The end-to-end continuity check activation
request was successfully sent toward the nearend.
3
eteCCActSuccTowardsBothEnd
The end-to-end continuity check activation
request was successfully sent toward both ends.
4
eteCCActDeniedTowardsFarEnd
The end-to-end continuity check activation
request sent toward the far-end is denied.
5
eteCCActDeniedTowardsNearEnd
The end-to-end continuity check activation
request sent toward the near-end is denied.
6
eteCCActDeniedTowardsBothEnd
The end-to-end continuity check activation
request sent toward both ends is denied.
7
eteCCActFailedTowardsFarEnd
The end-to-end continuity check activation
request sent toward the far-end failed.
8
eteCCActFailedTowardsNearEnd
The end-to-end continuity check activation
request sent toward the near-end failed.
9
eteCCActFailedTowardsBothEnd
The end-to-end continuity check activation
request sent toward both ends failed.
10
eteCCDeactSuccTowardsFarEnd
The end-to-end continuity check deactivation
request was successfully sent toward the far-end.
11
eteCCDeactSuccTowardsNearEnd
The end-to-end continuity check deactivation
request was successfully sent toward the nearend.
12
eteCCDeactSuccTowardsBothEnd
The end-to-end continuity check deactivation
request was successfully sent toward both ends.
13
eteCCDeactDeniedTowardsFarEnd
The end-to-end continuity check deactivation
request sent toward the far-end is denied.
14
eteCCDeactDeniedTowardsNearEnd
The end-to-end continuity check deactivation
request sent toward the near-end is denied.
15
eteCCDeactDeniedTowardsBothEnd
The end-to-end continuity check deactivation
request toward both ends is denied.
16
eteCCDeactFailedTowardsFarEnd
The end-to-end continuity check deactivation
request sent toward the far-end failed.
17
eteCCDeactFailedTowardsNearEnd
The end-to-end continuity check deactivation
request sent toward the near-end failed.
18
eteCCDeactFailedTowardsBothEnd
The end-to-end continuity check deactivation
request sent toward both ends failed.
19
segCCActSuccTowardsFarEnd
The segment continuity check activation request
was successfully sent toward the far-end.
20
segCCActSuccTowardsNearEnd
The segment continuity check activation request
was successfully sent toward the near-end.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-68
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-67. OAM Activation Deactivation Result Codes (Continued)
Number
Value
Enumerated Type
Description
21
segCCActSuccTowardsBothEnd
The segment continuity check activation request
was successfully sent toward both ends.
22
segCCActDeniedTowardsFarEnd
The segment continuity check activation request
sent toward the far-end is denied.
23
segCCActDeniedTowardsNearEnd
The segment continuity check activation request
sent toward the near-end is denied.
24
segCCActDeniedTowardsBothEnd
The segment continuity check activation request
sent toward both ends is denied.
25
segCCActFailedTowardsFarEnd
The segment continuity check activation request
sent toward the far-end failed.
26
segCCActFailedTowardsNearEnd
The segment continuity check activation request
sent toward the near-end failed.
27
segCCActFailedTowardsBothEnd
The segment continuity check activation request
sent toward both ends failed.
28
segCCDeactSuccTowardsFarEnd
The segment continuity check deactivation
request was successfully sent toward the far-end.
29
segCCDeactSuccTowardsNearEnd
The segment continuity check deactivation
request was successfully sent toward the nearend.
30
segCCDeactSuccTowardsBothEnd
The segment continuity check deactivation
request was successfully sent toward both ends.
31
oamReqFunctionNotImplemented
The function user issued is not implemented
32
oamReqFailLocRsrcUnavl
The continuity check connections have already
reached the maximum number (255).
33
oamActDeactPrevReqInProgress
This interface is in a wait for response state.
34
oamActDeactInvalidParams
The parameters the user provided are not valid.
35
oamActDeactInvalidIntf
Slot, port, channel, VP, VCI-This interface is not
valid.
36
oamNotSupportedForThisConnection
This connection is not OAM supported.
37
oamCCnotSupportedForThisConnection
This connection is not OAM CC supported.
38
oamPrevActDeactReqFailed
The previous request for activation/deactivation
failed.
39
oamEteLossOfContinuitySet
This end-to-end connection is in a loss of continuity state.
40
oamEteLossOfContinuityCleared
End-to-end loss of continuity state cleared.
41
oamSegLossOfContinuitySet
The segment connection has loss of continuity.
42
oamSegLossOfContinuityCleared
The segment loss of continuity cleared.
43
oamActDeactPMOnlySupportOCx
Performance monitoring only supports the Ocx
interface.
44
oamPMnotSupportedForThisConnection
This connection does not support OAM performance monitoring.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-69
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-67. OAM Activation Deactivation Result Codes (Continued)
Number
Value
Enumerated Type
Description
45
oamPMBRnotSupportedForThisConnection
This connection does not support OAM performance monitoring and backward reporting.
46
etePMActSuccTowardsFarEnd
The end-to-end performance monitoring activation request was successfully sent toward the farend.
47
etePMActSuccTowardsNearEnd
The end-to-end performance monitoring activation request was successfully sent toward the
near-end.
48
etePMActSuccTowardsBothEnd
The end-to-end performance monitoring activation request was successfully sent toward both
ends.
49
etePMActDeniedTowardsFarEnd
The end-to-end performance monitoring activation sent toward the far-end is denied.
50
etePMActDeniedTowardsNearEnd
The end-to-end performance monitoring activation sent toward the near-end is denied.
51
etePMActDeniedTowardsBothEnd
The end-to-end performance monitoring activation sent toward both ends is denied.
52
etePMActFailedTowardsFarEnd
The end-to-end performance monitoring activation sent toward the far-end failed.
53
etePMActFailedTowardsNearEnd
The end-to-end performance monitoring activation sent toward the near-end failed.
54
etePMActFailedTowardsBothEnd
The end-to-end performance monitoring activation sent toward both ends failed.
55
etePMDeactSuccTowardsFarEnd
The end-to-end performance monitoring deactivation request was successfully sent toward the
far-end.
56
etePMDeactSuccTowardsNearEnd
The end-to-end performance monitoring deactivation request was successfully sent toward the
near-end.
57
etePMDeactSuccTowardsBothEnd
The end-to-end performance monitoring deactivation request was successfully sent toward both
ends.
58
etePMBRActSuccTowardsFarEnd
The end-to-end performance monitoring/backward reporting activation request was successfully
sent toward the far-end.
59
etePMBRActSuccTowardsNearEnd
The end-to-end performance monitoring/backward reporting activation request was successfully
sent toward the near-end.
60
etePMBRActSuccTowardsBothEnd
The end-to-end performance monitoring/backward reporting activation request was successfully
sent toward both ends.
61
etePMBRActDeniedTowardsFarEnd
The end-to-end performance monitoring/backward reporting activation request sent toward the
far-end is denied.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-70
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-67. OAM Activation Deactivation Result Codes (Continued)
Number
Value
Enumerated Type
Description
62
etePMBRActDeniedTowardsNearEnd
The end-to-end performance monitoring/backward reporting activation request sent toward the
near-end is denied.
63
etePMBRActDeniedTowardsBothEnd
The end-to-end performance monitoring/backward reporting activation request sent toward
both ends is denied.
64
etePMBRActFailedTowardsFarEnd
The end-to-end performance monitoring/backward reporting activation request sent toward the
far-end failed.
65
etePMBRActFailedTowardsNearEnd
The end-to-end performance monitoring/backward reporting activation request sent toward the
near-end failed
66
etePMBRActFailedTowardsBothEnd
The end-to-end performance monitoring/backward reporting activation request sent toward
both ends failed
67
etePMBRDeactSuccTowardsFarEnd
The end-to-end performance monitoring/backward reporting deactivation request was successfully sent toward the far-end.
68
etePMBRDeactSuccTowardsNearEnd
The end-to-end performance monitoring/backward reporting deactivation request was successfully sent toward the near-end.
69
etePMBRDeactSuccTowardsBothEnd
The end-to-end performance monitoring/backward reporting deactivation request was successfully sent toward both ends.
70
segPMActSuccTowardsFarEnd
The segment performance monitoring activation
request was successfully sent toward the far-end.
71
segPMActSuccTowardsNearEnd
The segment performance monitoring activation
request was successfully sent toward the nearend.
72
segPMActSuccTowardsBothEnd
The segment performance monitoring activation
request was successfully sent toward both ends.
73
segPMActDeniedTowardsFarEnd
The segment performance monitoring activation
request sent toward the far-end is denied.
74
segPMActDeniedTowardsNearEnd
The segment performance monitoring activation
request sent toward the near-end is denied.
75
segPMActDeniedTowardsBothEnd
The segment performance monitoring activation
request sent toward both ends is denied.
76
segPMActFailedTowardsFarEnd
The segment performance monitoring activation
request sent toward the far-end failed.
77
segPMActFailedTowardsNearEnd
The segment performance monitoring activation
request sent toward the near-end failed.
78
segPMActFailedTowardsBothEnd
The segment performance monitoring activation
request sent toward both ends failed.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-71
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-67. OAM Activation Deactivation Result Codes (Continued)
Number
Value
Enumerated Type
Description
79
segPMDeactSuccTowardsFarEnd
The segment performance monitoring deactivation request was successfully sent to the far-end.
80
segPMDeactSuccTowardsNearEnd
The segment performance monitoring deactivation request was successfully sent toward the
near-end.
81
segPMDeactSuccTowardsBothEnd
The segment performance monitoring deactivation request was successfully sent toward both
ends.
82
segPMBRActSuccTowardsFarEnd
The segment performance monitoring/backward
reporting activation request was successfully sent
toward the far-end.
83
segPMBRActSuccTowardsNearEnd
The segment performance monitoring/backward
reporting activation request was successfully sent
toward the near-end.
84
segPMBRActSuccTowardsBothEnd
The segment performance monitoring/backward
reporting activation request was successfully sent
toward both ends.
85
segPMBRActDeniedTowardsFarEnd
The segment performance monitoring/backward
reporting activation request sent toward the farend is denied.
86
segPMBRActDeniedTowardsNearEnd
The segment performance monitoring/backward
reporting activation request sent toward the nearend is denied.
87
segPMBRActDeniedTowardsBothEnd
The segment performance monitoring/backward
reporting activation request sent toward both
ends is denied.
88
segPMBRActFailedTowardsFarEnd
The segment performance monitoring/backward
reporting activation request sent toward the farend failed.
89
segPMBRActFailedTowardsNearEnd
The segment performance monitoring/backward
reporting activation request sent toward the nearend failed.
90
segPMBRActFailedTowardsBothEnd
The segment performance monitoring/backward
reporting activation request sent toward both
ends failed.
91
segPMBRDeactSuccTowardsFarEnd
The segment performance monitoring/backward
reporting deactivation request was successfully
sent toward the far-end.
92
segPMBRDeactSuccTowardsNearEnd
The segment performance monitoring/backward
reporting deactivation request was successfully
sent toward the near-end.
93
segPMBRDeactSuccTowardsBothEnd
The segment performance monitoring/backward
reporting deactivation request was successfully
sent toward both ends.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-72
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-67. OAM Activation Deactivation Result Codes (Continued)
Number
Value
Enumerated Type
Description
94
eteSendPMCell
End-to-end management cell has been sent out to
IO module indicating PM cell needs to be sent.
95
eteReceiveBRErrMessage
A BR message has been forwarded to the CPU
indicating a BR error.
96
receiveBRErrMessage
A backward reporting message has been forwarded to the CPU indicating BR error.
97
receiveFPMErrMessage
A FPM message has been forwarded to the CPU
indicating a FPM error
98
sendPMCell
A management cell has been sent out to the IO
module indicating the PM cell needs to be sent.
oamTestFailureReasonCode
An identified reason why an OAM Loopback Test request has failed. The valid range is a number
between 1 and 7.
See Table 4-68 for a mapping between numbers and their enumerated type.
Associated Traps - oamTestReqFailNotify
Table 4-68. OAM Test Failure Reason Codes
Number
Value
Enumerated Type
Description
1
invalidSPCforOAM
There is no such slot/port/channel in this box.
2
invalidIntfForOAM
There is no such interface that OAM enabled.
3
invalidLocationLength
The length of the Loopback Location ID is not valid.
4
oamNotSupportedForThisConnection
This connection is not OAM enabled, so OAM loopback
is not a valid test.
5
loopbackTestAlreadyRunning
OAM loopback is waiting for a response and is not
expecting another test.
6
loopbackTestNotRunning
The test action is not valid.
7
oamLocalResourcesUnavailable
Memory allocation failed.
oamTestIfB
Interface index used for starting loopback test. Number value is interpreted as an interface of the
form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel
number.
Associated Traps - oamTestReqFailNotify
oamTestVciB
The VCI value under testing for OAM loopback test. The valid range is a number between 0 and
65535.
Associated Traps - oamTestReqFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-73
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
oamTestVpiB
The VPI value under testing for OAM loopback test. The valid range is a number between 0 and
4095.
Associated Traps - oamTestReqFailNotify
ocxAPSK1K2Rx
Rx K1/K2 followed by hex value of K1, K2
Associated Traps - ocxAPSStateChangeNotify, ocxAPSSwitchoverNotify
ocxAPSK1K2Tx
Tx K1/K2 followed by hex value of K1, K2
Associated Traps - ocxAPSStateChangeNotify, ocxAPSSwitchoverNotify
ocxAPSPairPortIndex
APS Pair Port index - SSPP
Associated Traps - ocxAPSStateChangeNotify, ocxAPSSwitchoverNotify
ocxAPSProtectionLineSignalStatus
Line status of the protection port sent in a trap. The valid range is a number between 1 and
32768.
See Table 4-69 for a mapping between numbers and their enumerated type.
Associated Traps - ocxAPSStateChangeNotify, ocxAPSSwitchoverNotify
Table 4-69. OC-xc APS Protection Line Signal Status Codes
Number
Value
Enumerated Type
Description
1
noAlarm
No alarm is present.
2
signalDegradation
The signal bit error rate is higher than the specified threshold.
4
signalFailure
The signal bit error rate is much higher than the specified
threshold.
8
lostCellDelineation
Unable to identify cell boundary.
16
switchByteFailure
Switch bytes(k1,k2) of SONET header have non valid code.
32
ais-l
The line header of SONET frame gives an alarm indication
signal.
64
ais-p
The path header of SONET frame gives an alarm indication
signal.
128
lop
1)A valid STS or VT pointer cannot be obtained by using
the pointer interpretation rules and the pointer word does
not contain all-ones. 2)A consecutive number with the
NDF set to 1001 but not indicating that concatenation is
received.
256
lof
Loss of frame.
512
los
Loss of signal.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-74
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-69. OC-xc APS Protection Line Signal Status Codes (Continued)
Number
Value
Enumerated Type
Description
1024
moduleFailure
Module failure.
2048
lineLoopBack
The port is in a line loop back state.
4096
protocolFailure
Protocol failure.
8192
adminOutOfService
The interface is administratively out of service.
16384
lrdi
Receiving Line RDI.
32768
prdi
Receiving Path RDI.
ocxAPSReasonCode
Enumerated values of the outcome of previous apsPair UserCommand or alarms on the line. The
valid range is a number between 1 and 62.
See Table 4-70 for a mapping between numbers and their enumerated type.
Associated Traps - ocxAPSStateChangeNotify, ocxAPSSwitchoverNotify
Table 4-70. OC-xc APS Reason Codes
Number
Value
Enumerated Type
Description
1
localprotectDoNotRevert
At the near-end protection port, after the working line was switched to the protection line, the
protection line did not revert back to the working line.
8
localprotectManualSw
A switchover by user command occurred at the
near-end protection port.
10
localprotectSD
A signal degradation occurred at the near-end
protection port.
12
localprotectSF
A signal failure occurred at the near- end protection port.
14
localprotectForced
A forced switchover occurred at the near-end
protection port.
15
localprotectLockOut
Did not allow a switchover to occur at the nearend protection port.
17
localworkingDoNotRevert
At the near-end working port, after the working
line was switched to the protection line, the protection line did not revert back to the working
line.
24
localworkingManualSw
A switchover by user command occurred at the
near-end working port.
26
localworkingSD
A signal degradation occurred at the near-end
working port.
28
localworkingSF
A signal failure occurred at the near- end working port.
30
localworkingForced
A forced switchover occurred at the near-end
working port.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-75
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-70. OC-xc APS Reason Codes (Continued)
Number
Value
Enumerated Type
Description
33
remoteprotectDoNotRevert
At the far-end protection port, after the working
line was switched to the protection line, the protection line did not revert back to the working
line.
40
remoteprotectManualSw
A switchover by user command occurred at the
far-end port.
42
remoteprotectSD
A signal degradation occurred at the far-end protection port.
44
remoteprotectSF
A signal failure occurred at the far-end protection port.
46
remoteprotectForced
A forced switchover occurred at the far-end protection port.
47
remoteprotectLockOut
Did not allow switchover to occur at the far-end
protection port.
48
noRequest
No request
49
remoteworkingDoNotRevert
At the far-end working port, after the working
line was switched to the protection line, the protection line did not revert back to the working
line.
56
remoteworkingManualSw
A switchover by user command occurred at the
far-end working port.
58
remoteworkingSD
A signal degradation occurred at the far-end
working port.
60
remoteworkingSF
A signal failure occurred at the far-end working
port.
62
remoteworkingForced
A forced switchover occurred at the far-end
working port.
ocxAPSSelectorState
Working port: active/standby Protection port: standby/active. The valid range is the number 1 or
2.
See Table 4-71 for a mapping between numbers and their enumerated type.
Associated Traps - ocxAPSStateChangeNotify, ocxAPSSwitchoverNotify
Table 4-71. OC-xc APS Selector State Codes
Number
Value
Enumerated Type
Description
1
w-active-p-standby
The working port is active while the protection port is standby.
2
w-standby-p-active
The working port is standby while the protection port is active.
ocxAPSWorkingLineSignalStatus
Line status of the working port sent in a trap. The valid range is a number between 1 and 32768.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-76
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
See Table 4-72 for a mapping between numbers and their enumerated type.
Associated Traps - ocxAPSStateChangeNotify, ocxAPSSwitchoverNotify
Table 4-72. OC-xc APS Working Line Signal Status Codes
Number
Value
Enumerated Type
Description
1
noAlarm
No alarm is present.
2
signalDegradation
The signal bit error rate is higher than the specified threshold.
4
signalFailure
The signal bit error rate is much higher than the specified threshold
8
lostCellDeliniation
Unable to identify cell boundary.
16
switchByteFailure
Switch bytes(k1,k2) of SONET header have non valid code.
32
ais-1
line header of SONET frame gives alarm indication signal
64
ais-p
path header of SONET frame gives alarm indication signal
128
lop
1)A valid STS or VT pointer cannot be obtained by using the pointer
interpretation rules and the pointer word does not contain all-ones.
2)A consecutive number with the NDF set to 1001 but not indicating that concatenation is received.
256
lof
Loss of frame.
512
los
Loss of signal.
1024
moduleFailure
Module failure.
2048
lineLoopBack
The port is in a line loop back state.
4096
protocolFailure
Protocol failure.
8192
adminOutOfService
The interface is administratively out of service.
16384 lrdi
Receiving Line RDI.
32768 prdi
Receiving Path RDI.
ocxPortId
The index to the ocx port table in SSPP format.
Associated Traps - apsConfigurationModifyFailNotify
percentComplete
Used for the trap message fileTransferStatusNotify, and the value equals the percentage of the
upgrade, downgrade, or FTP download completed.
Associated Traps - fileTransferStatusNotify
pgtGroupId
A user-selected logical number uniquely representing a protection group within a PSAX system.
Associated Traps - pgtResultNotify
pgtResultCode
Various result codes for the operator’s command for interface protection. The valid range is a
number between 1 and 9.
See Table 4-73 for a mapping between numbers and their enumerated type.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-77
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - pgtResultNotify
Table 4-73. PGT Result Codes
Number
Value
Enumerated Type
Description
1
interfaceProtectionpgtAlreadyExistInterface
This interface is already in a protection group.
2
interfaceProtectionpgtInvalidInterface
This interface is not valid for a protection
group.
3
interfaceProtectionpgtInvalidParams
The parameters chosen by the user are not
valid.
4
interfaceProtectionpgtryToDeleteEmptyTable
The user is trying to delete an entry from an
empty table.
5
interfaceProtectionpgtSuccessfulSwichOver Interface protection successfully switched
over.
6
interfaceProtectionpgtSuccessfulSwichBack Interface protection successfully switched
back.
7
interfaceProtectionpgtFailedSwichOver
Interface protection failed switched over.
8
interfaceProtectionpgtFailedSwichBack
Interface protection failed switched back.
9
interfaceProtectionpgtInvalidConfiguation
The interface protection configuration is not
valid.
pingStatusReasonCode
The response value - Alive/Not Alive. The valid range is a number between 1 and 2.
See Table 4-74 for a mapping between numbers and their enumerated type.
Associated Traps - viprPingTrap
Table 4-74. Ping Status Reason Codes
Number
Value
Enumerated Type
Description
1
alive
The destination can be reached.
2
not-alive
The destination cannot be reached.
pnniCode
An identified reason code for a PNNI configuration. The valid range is a number between 1 and
22.
See Table 4-75 for a mapping between numbers and their enumerated type.
Associated Traps - pnniNodeCfgNotify, pnniNodeCfgFailNotify, pnniNodeModFailNotify, pnniNodeDelFailNotify, pnniNodeOOSFailNotify, pnniNodeISFailNotify, pnniRtAddrCfgNotify, pnniRtAddrCfgFailNotify, pnniRtAddrModFailNotify, pnniRtAddrDelFailNotify, pnniRtAddrAddByIlmiNotify, pnniRtAddrDelByIlmiNotify, pnniProtLnkUpAndAdv, pnniProtLinkUpAndNotAdv,
pnniProtLnkStatDown, pnniIntfCfgFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-78
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-75. PNNI Codes
Number
Value
Enumerated Type
Description
1
pnniInvEndSysPortId
The end system port ID is not valid.
2
pnniNodeAdmStatNotUp
The aministrative status of the node is not in service.
3
pnniProtLnkStatDown
PNNI link status is down
4
pnniProtLnkStatUpNotAdv
PNNI link status is up but not advertised
5
pnniProtLinkStatUpAdv
PNNI link status is up and advertised
6
pnniIntfAdmStatUp
PNNI interface administrative status is up
7
pnniNodeNotCfg
PNNI node not configured in the switch
8
pnniRtAddrAddedByIlmi
PNNI route added successfully from ILMI
9
pnniRtAddrDelByIlmi
PNNI route deleted successfully from ILMI
10
pnniLvlMismatchInNodeId
Level mismatch in node ID
11
pnniLvlMismatchInPGId
Level mismatch in peer group ID
12
pnniATMAddrInvInNodeId
The ATM address entered in the node ID is not valid.
13
pnniATMAddrInvInPGId
The ATM address entered in the peer group ID is not
valid.
14
pnniIntfAdmStatNotDel
PNNI interface administrative status not deleted
15
pnniNodeAdmStatUp
PNNI node admin status is up
16
pnniNodeRowStatNotActive
The PNNI node row status is not active and cannot be
modified.
17
pnniNewRtAddrAdded
New route added to the PNNI route address table
18
pnniRtAddrMod
The route has been modified in the PNNI address table.
19
pnniAdvtNodeIdNotMine
The advertised node ID does not belong to this PSAX system.
20
pnniFeatureNotSupported
The PNNI feature is not supported.
21
pnniNodeInvalidInNodeIndex
The PNNI node index is not valid.
22
pglInvalidInParentNodeIndx
The parent node index is not valid.
pnniSvccRccSecCfgPeerGrpId
The identification of a PNNI peer group. The ATM security agent configuration for SVC RCC will
be provided per PNNI peer group at one level.
Associated Traps - atmSecSvccRccSACfgCreateFailNotify, atmSecSvccRccSACfgCreatedNotify,
atmSecSvccRccSACfgDeleteFailNotify, atmSecSvccRccSACfgDeletedNotify, atmSecSvccRccSACfgModifyFailNotify, atmSecSvccRccSACfgModifiedNotify,
portFailureReasonCode
Identification of cause for failure in changing the parameters of a port. The valid range is a number between 1 and 10.
See Table 4-76 for a mapping between numbers and their enumerated type.
Associated Traps - portModifyFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-79
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-76. Port Failure Reason Codes
Number
Value
Enumerated Type
Description
1
insufficientModuleBandwidth
Insufficient module bandwidth.
2
localLoopNotAllowedWhenInAPS
Local loop is not allowed when a port is in an
automatic switching pair.
3
msBitStuffingEnabledOnlyForCE
If msBitStuffing is enabled, only interfacetype
circuit emulation is allowed.
4
invalidOption
Option is not valid.
5
hasInterfaceInService
The interface is in-service.
6
unsupportedBaudRate
The baud rate is not supported.
7
msLOSDetectionNotEnabled
msLOSDetection is not enabled.
8
invalidLinkTypeAndDuplexModeCombination
The link type and duplex mode combination
are not valid.
9
berTestUnsupported
The BER test on this module is not supported.
10
speedAdaption-baudRate-incompatible
Baud rate is not allowed when the msSpeedAdaptation field is enabled.
portId
Port ID used for identification in traps. The number value is interpreted as a port of the form,
SSPP, where SS is the module slot and PP is the port number.
Associated Traps - lineStatusChangedNotify, portModifyFailNotify, ceServiceTypeModifyFailNotify, channelizationModifyFailNotify, cRC4ModifyFailNotify, apsConfigurationModifyFailNotify,
portModifiedNotify, portMaintenanceTestNotify, portMaintenanceTestFailNotify, inputPortClockClearedNotify
portMaintTestChangeReasonCode
Indication of the changed status of port maintenance test commands. The valid range is a number
between 1 and 8.
See Table 4-77 for a mapping between numbers and their enumerated type.
Associated Traps - portMaintenanceTestNotify
Table 4-77. Port Maintenance Test Change Reason Codes
Number
Value
Enumerated Type
Description
1
loopControlTurnedOn
The loopback test has started.
2
loopControlTurnedOff
The loopback test has stopped.
3
bertControlTurnedOn
The bit error rate (BER) test has started.
4
bertControlTurnedOff
The bit error rate (BER) test has stopped.
5
bertErrorCountUpdated
The received bit error count is being
updated.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-80
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-77. Port Maintenance Test Change Reason Codes
Number
Value
Enumerated Type
Description
6
bertCountUpdated
The transmitted bit error count is being
updated.
7
rxLoopbackCodeChanged
The RX loopback code has changed.
8
receivedBertPatternChanged
The received BERT pattern has changed.
portMaintTestFailureReasonCode
An identified cause for failure in changing maintenance test parameters. The valid range is a
number between 1 and 3.
See Table 4-78 for a mapping between numbers and their enumerated type.
Associated Traps - portMaintenanceTestFailNotify
Table 4-78. Port Maintenance Test Failure Reason Codes
Number
Value
Enumerated Type
Description
1
canotChangeLoopbackParametersDuringLoopbackTest
Loopback parameters including LoopbackTestMode, TxLoopbackCode, and TxLoopCodeDuration cannot be changed if the
loopback test is in progress.
2
canotChangeLoopbackParametersDuringBerTest
Loopback parameters including LoopbackTestMode, TxLoopbackCode, and TxLoopCodeDuration cannot be changed if the BER
test is in progress.
3
canotChangeBertParametersDuringBerTest
BER parameters including BertPattern,
BertDuration, and UserConfiguredBertPattern cannot be changed if the BER test is in
progress.
portModificationReasonCode
Identification of the change made to the parameters of a port. The valid range is a number
between 1 and 2.
See Table 4-79 for a mapping between numbers and their enumerated type.
Associated Traps - portModifiedNotify
Table 4-79. Port Modification Reason Codes
Number
Value
Enumerated Type
Description
1
channelizationEnabled
A port has been channelized.
2
channelizationDisabled
A port has been unchannelized.
powerSupplyReasonCode
Identification for a change in the status of a power supply. The valid range is a number between
1 and 8.
See Table 4-80 for a mapping between numbers and their enumerated type.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-81
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - powerSupplyStatusNotify
Table 4-80. Power Supply Reason Codes
Number
Value
Enumerated Type
Description
1
overload
overload
2
overloadCleared
overload cleared
3
outputPowerFailed
output power failed
4
outputPowerFailCleared
output power fail cleared
5
inputPowerFailed
input power failed
6
inputPowerFailCleared
input power fail cleared
7
minus48vOutputPowerFai -48V output power failed
led
8
minus48vOutputPowerFai -48V output power fail cleared
lCleared
primarySoftwareVersion
The software version running on the primary CPU.
Associated Traps - differentSystemSoftwareNotify
profileFailureReasonCode
An identified cause for failure in changing the status of a profile. The valid range is a number
between 1 and 7.
See Table 4-81 for a mapping between numbers and their enumerated type.
Associated Traps - hdsl2ShdslSpanConfProfileOperationFailNotify,
hdsl2ShdslEndpointAlarmConfProfileOperationFailNotify
Table 4-81. Profile Failure Reason Codes
Number
Value
Enumerated Type
Description
1
invalidProfileNameLength The length of a profile name should not exceed 32 characters.
2
exceedMaxProfileNumber- The profile table is full, no additional profiles can be creBeingSupported
ated.
3
profileWithSameNameEx- A profile with the same name already exists. Profiles are
ists
distinguished by their name, therefore, profile names must
be unique.
4
DefaultProfileDeletionNo- The default profile cannot be deleted.
tAllowed
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-82
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-81. Profile Failure Reason Codes
Number
Value
Enumerated Type
Description
5
profileSpecifiedByTheNameNotExist
This profile cannot be deleted because it does not exist.
6
profileCurrentlyBeingRef- If a non-default profile is currently referred by one or more
ered
ports, this profile cannot be deleted until its reference is
cleared.
7
unsupportedProfileOpera- The rowStatus profile has two operations that are suption
ported; createAndGo and destroy.
protectionCardSlot
The physical protection slot location. The valid range is a number between 1 and 24.
Associated Traps - ntomProtectionSwitchoverNotify
pvcFailureReasonCode
An identified reason why an ATM PVC connection request failed. The valid range is a number
between 1 and 375.
See Table 4-82 for a mapping between numbers and their enumerated type.
Associated Traps - virtualIntfModifyFailNotify, atmPvcVccReqFailNotify, atmPvcVpcReqFailNotify,
ipAtmAppPvcVccReqFailNotify, cirEmAtmPvcVccReqFailNotify, vbrAtmPvcVccReqFailNotify,
frAtmPvcVccReqFailNotify, frFrPvcReqFailNotify, cirEmCirEmPvcReqFailNotify, vbrVbrPvcReqFailNotify, bridgeBridgePvcReqFailNotify, bridgeAtmPvcVccReqFailNotify, cellTestReqFailNotify,
cirEmAtmBkPvcVccReqFailNotify, vbrAtmBkPvcVccReqFailNotify, atmBkPvcVccReqFailNotify,
frAtmBkPvcVccReqFailNotify, atmBkPvcVpcReqFailNotify, bridgeAtmBkPvcVccReqFailNotify,
ipAtmBkAppPvcVccReqFailNotify, aal2TrunkConfigReqFailNotify, dhpvcChangeNotify,
dsp2CardReroutingFailedNotify, bulkStatsCfgFailNotify, atafConvertNotify
Table 4-82. PVC Failure Reason Codes
Number
Value
Enumerated Type
Description
1
vpiVciUnavailableA2B
The virtual path identifier and virtual channel identifier are unavailable in the direction of A2B.
2
vpiVciUnavailableB2A
The virtual path identifier and virtual channel identifier are unavailable in the direction of B2A.
3
bandwidthUnavailableA2B
Bandwidth is unavailable in the direction of A2B.
4
bandwidthUnavailableB2A
Bandwidth is unavailable in the direction of B2A.
5
qosUnavailableA2B
Quality of service is unavailable in the direction of
A2B.
6
qosUnavailableB2A
Quality of service is unavailable in the direction of
B2A.
7
internalResourceUnavailable
Internal resource is unavailable.
8
cantUseSignalingChnlIgrsA2B
Cannot use signaling channel on the ingress side of
the A2B direction of the connection.
9
cantUseSignalingChnlEgrsA2B
Cannot use signaling channel on the egress side of
the A2B direction of the connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-83
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
10
cantUseSignalingChnlIgrsB2A
Cannot use signaling channel on the ingress side of
the B2A direction of the connection.
11
cantUseSignalingChnlEgrsB2A
Cannot use signaling channel on the egress side of
the B2A direction of the connection.
12
cantUseManagementChnlIgrsA2B
Cannot use management channel on the ingress side
of the A2B direction of the connection.
13
cantUseManagementChnlEgrsA2B Cannot use management channel on the egress side
of the A2B direction of the connection.
14
cantUseManagementChnlIgrsB2A
15
cantUseManagementChnlEgrsB2A Cannot use management channel on the egress side
of the B2A direction of the connection.
16
vcLessThanVcMinIgrsA2B
The virtual channel is less than the virtual channel
identifier minimum on the ingress side of the A2B
direction of the connection.
17
vcLessThanVcMinEgrsA2B
The virtual channel is less than the virtual channel
identifier minimum on the egress side of the A2B
direction of the connection.
18
vcLessThanVcMinIgrsB2A
The virtual channel is less than the virtual channel
identifier minimum on the ingress side of the B2A
direction of the connection.
19
vcLessThanVcMinEgrsB2A
The virtual channel is less than the virtual channel
identifier minimum on the egress side of the B2A
direction of the connection.
20
vcGreaterThanVcMaxIgrsA2B
The virtual channel is greater than the virtual channel identifier maximum on the ingress side of the
A2B direction of the connection.
21
vcGreaterThanVcMaxEgrsA2B
The virtual channel is greater than the virtual channel identifier maximum on the egress side of the A2B
direction of the connection.
22
vcGreaterThanVcMaxIgrsB2A
The virtual channel is greater than the virtual channel identifier maximum on the ingress side of the
B2A direction of the connection.
23
vcGreaterThanVcMaxEgrsB2A
The virtual channel is greater than the virtual channel identifier maximum on the egress side of the B2A
direction of the connection.
24
vpLessThanVpMinIgrsA2B
The virtual path is less than the virtual path identifier
minimum on the ingress side of the A2B direction of
the connection.
25
vpLessThanVpMinEgrsA2B
The virtual path is less than the virtual path identifier
minimum on the egress side of the A2B direction of
the connection.
Cannot use management channel on the ingress side
of the B2A direction of the connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-84
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
26
vpLessThanVpMinIgrsB2A
The virtual path is less than the virtual path identifier
minimum on the ingress side of the B2A direction of
the connection.
27
vpLessThanVpMinEgrsB2A
The virtual path is less than the virtual path identifier
minimum on the egress side of the B2A direction of
the connection.
28
vpGreaterThanVpMaxIgrsA2B
The virtual path is greater than the virtual path identifier maximum on the ingress side of the A2B direction of the connection.
29
vpGreaterThanVpMaxEgrsA2B
The virtual path is greater than the virtual path identifier maximum on the egress side of the A2B direction of the connection.
30
vpGreaterThanVpMaxIgrsB2A
The virtual path is greater than the virtual path identifier maximum on the ingress side of the B2A direction of the connection.
31
vpGreaterThanVpMaxEgrsB2A
The virtual path is greater than the virtual path identifier maximum on the egress side of the B2A direction of the connection.
32
vpGreaterThanVpMaxIispIgrsA2B
The virtual path value is greater than the allowed
upper limit for NNI interfaces. The error is in the
input side of the A2B direction of the connection.
33
vpGreaterThanVpMaxIispEgrsA2B The virtual path value is greater than the allowed
upper limit for NNI interfaces. The error is in the output side of the A2B direction of the connection.
34
vpGreaterThanVpMaxIispIgrsB2A
35
vpGreaterThanVpMaxIispEgrsB2A The virtual path value is greater than the allowed
upper limit for NNI interfaces. The error is in the output side of the B2A direction of the connection.
36
rsvdChnlRangeIgrsA2B
Reserved channel range on the ingress side of the
A2B direction of the connection.
37
rsvdChnlRangeEgrsA2B
Reserved channel range on the egress side of the A2B
direction of the connection.
38
rsvdChnlRangeIgrsB2A
Reserved channel range on the ingress side of the
B2A direction of the connection.
39
rsvdChnlRangeEgrsB2A
Reserved channel range on the egress side of the B2A
direction of the connection.
40
internalSrvcTypeUnavailableA2B
The internal service type is unavailable in the direction of A2B.
41
internalSrvcTypeUnavailableB2A
The internal service type is unavailable in the direction of B2A.
42
unrecognizableBindTypeEgrsA2B
An internal error has occurred in the output side of
the A2B direction of the connection.
The virtual path value is greater than the allowed
upper limit for NNI interfaces. The error is in the
input side of the B2A direction of the connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-85
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
43
unrecognizableBindTypeEgrsB2A
An internal error has occurred in the output side of
the B2A direction of the connection.
44
callWithoutConnections
Call without connections.
45
callDataStructuresUnavailable
Call data structures unavailable.
46
cnctnDataStructuresUnavailable
Internal resource availability error. Specifically no
connection structures are available.
47
nullTrafficParametersRejectedA2B This error code is used when the user specifies 0
when a value is needed. The error is in the A2B
direction.
48
nullTrafficParametersRejectedB2A This error code is used when user specifies 0 when a
value is needed. The error is in the B2A direction.
49
vpiWithinSvcRangeIgrsA2B
The virtual path identifier is within SVC range on the
ingress side of the A2B direction of the connection.
50
vpiWithinSvcRangeEgrsA2B
The virtual path identifier is within SVC range on the
egress side of the A2B direction of the connection.
51
vpiWithinSvcRangeIgrsB2A
The virtual path identifier is within SVC range on the
ingress side of the B2A direction of the connection.
52
vpiWithinSvcRangeEgrsB2A
The virtual path identifier is within SVC range on the
egress side of the B2A direction of the connection.
53
vpiInReservedListA2B
The currently configured virtual path identifier is
present in the reserved list of the A side of the A2B
direction of the connection.
54
vpiInReservedListB2A
The currently configured virtual path identifier is
present in the reserved list of the B side of the B2A
direction of the connection.
55
vpiInPvcListA2B
The virtual path identifier used is already present in
the PVC list for some other connection. The error is
in the Input side of A2B direction.
56
vpiInPvcListB2A
The virtual path identifier used is already present in
the PVC list for some other connection. The error is
in the input side of B2A direction.
57
vpiInReleasedListA2B
The virtual path identifier used is already present in
the released list for some other connection. The error
is in the input side of A2B direction.
58
vpiInReleasedListB2A
The virtual path identifier used is already present in
the released list for some other connection.The error
is in the input side of B2A direction.
59
vciIsNotNullInVpcIgrsA2B
The virtual path identifier used is not 0 in a VPC connection. The error is in the input side of A2B direction.
60
vciIsNotNullInVpcEgrsA2B
The virtual path identifier used is not 0 in a VPC connection. The error is in the output side of A2B direction.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-86
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
61
vciIsNotNullInVpcIgrsB2A
The virtual path identifier used is not 0 in a VPC connection. The error is in the input side of B2A direction.
62
vciIsNotNullInVpcEgrsB2A
The virtual path identifier used is not 0 in a VPC connection. The error is in the output side of B2A direction.
63
vpiInVpcReservedListA2B
The virtual path identifier used is already present in
the reserved list for some other VPC connection. The
error is in the input side of A2B direction.
64
vpiInVpcReservedListB2A
The virtual path identifier used is already present in
the reserved list for some other VPC connection. The
error is in the Input side of B2A direction.
65
vpiVciInReservedListA2B
The virtual path identifier/virtual channel identifier
used is already present in the reserved list for some
other connection. The error is in the input side of
A2B direction.
66
vpiVciInReservedListB2A
The virtual path identifier/virtual channel identifier
used is already present in the reserved list for some
other connection. The error is in the input side of
B2A direction.
67
vpiInVpcPvcListA2B
The virtual path identifier used is already present in
the PVC list for some other VPC connection. The
error is in the input side of A2B direction.
68
vpiInVpcPvcListB2A
The virtual path identifier used is already present in
the PVC list for some other VPC connection. The
error is in the input side of B2A direction.
69
vpiVciInPvcListA2B
The virtual path identifier/virtual channel identifier
used is already present in the PVC list for some other
connection. The error is in the input side of A2B
direction.
70
vpiVciInPvcListB2A
The virtual path identifier/virtual channel identifier
used is already present in the PVC list for some other
connection. The error is in the input side of B2A
direction.
71
vpiInVpcReleasedListA2B
The virtual path identifier used is already present in
the released list for some other VPC connection. The
error is in the input side of A2B direction.
72
vpiInVpcReleasedListB2A
The virtual path identifier used is already present in
the released list for some other VPC connection. The
error is in the input side of B2A direction.
73
vpiVciInReleasedListA2B
The virtual path identifier/virtual channel identifier
used is already present in the released list for some
other connection. The error is in the input side of
A2B direction.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-87
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
74
vpiVciInReleasedListB2A
The virtual path identifier/virtual channel identifier
used is already present in the released list for some
other connection. The error is in the input side of
B2A direction.
75
illegalMulticaseIdA2B
An internal error in which an Illegal MulticastId was
found in the A2B direction.
76
illegalMulticaseIdB2A
An internal Error in which an Illegal MulticastId was
found in the B2A direction.
77
unsupportedConnectionA2B
The connection is not supported in the A2B direction.
78
unsupportedConnectionB2A
The connection is not supported in the B2A direction.
79
connectionsUnavailableInModule
A2B
The connections are unavailable in the module in the
A2B direction.
80
connectionsUnavailableInModuleB The connections are unavailable in the module in the
2A
B2A direction.
81
scrBandwidthUnavailableIgrsA2B
82
scrBandwidthUnavailableEgrsA2B The sustained cell rate bandwidth is unavailable on
the egress side of the A2B direction of the connection.
83
scrBandwidthUnavailableIgrsB2A
84
scrBandwidthUnavailableEgrsB2A The sustained cell rate bandwidth is unavailable on
the egress side of the B2A direction of the connection.
85
pcrBandwidthUnavailableIgrsA2B
86
pcrBandwidthUnavailableEgrsA2B The peak cell rate bandwidth is unavailable on the
egress side of the A2B direction of the connection.
87
pcrBandwidthUnavailableIgrsB2A
88
pcrBandwidthUnavailableEgrsB2A The peak cell rate bandwidth is unavailable on the
egress side of the B2A direction of the connection.
89
vpiVciWithinSvcRangeIgrsA2B
The virtual path identifier and the virtual channel
identifier are within SVC range on the ingress side of
the A2B direction of the connection.
90
vpiVciWithinSvcRangeEgrsA2B
The virtual path identifier and the virtual channel
identifier are within SVC range on the egress side of
the A2B direction of the connection.
The sustained cell rate bandwidth is unavailable on
the ingress side of the A2B direction of the connection.
The sustained cell rate bandwidth is unavailable on
the ingress side of the B2A direction of the connection.
The peak cell rate bandwidth is unavailable on the
ingress side of the A2B direction of the connection.
The peak cell rate bandwidth is unavailable on the
ingress side of the B2A direction of the connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-88
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
91
vpiVciWithinSvcRangeIgrsB2A
The virtual path identifier and the virtual channel
identifier are within SVC range on the ingress side of
the B2A direction of the connection.
92
vpiVciWithinSvcRangeEgrsB2A
The virtual path identifier and the virtual channel
identifier are within SVC range on the egress side of
the B2A direction of the connection.
93
multicastDataStructuresUnavailable
Multicast data structures are unavailable.
94
semaphoreTimeout
An internal error in which semaphore times out.
95
dlciFoundInReservedList
The data link connection identifier is found in the
reserved list.
96
dlciFoundInPvcList
The data link connection identifier is found in the
permanent virtual circuits list.
97
dlciFoundInReleasedList
The data link connection identifier is found in the
released list.
98
invalidDlci
The data link connection identifier is not valid.
99
slotA-OutOfRange
Slot A is out of range.
100
portA-OutOfRange
Port A is out of range.
101
channelA-OutOfRange
Channel A is out of range.
102
moduleA-Uninitialized
Slot of A side has not been initialized because of an
internal error or the module is not seated.
103
physicalPortA-Uninitialized
Port of A side has not been initialized because of an
internal error or the module is not seated.
104
channelA-NotBound
Channel of A side has not been bound to an interface. The cause could be an internal error or the
interface has not been brought into service at least
once or is not configured.
105
moduleA-UnrecognizablePortType An internal error in which the port type is not recognizable for the module on side A.
106
slotB-OutOfRange
The slot on the B side is out of range.
107
portB-OutOfRange
The port on the B side is out of range.
108
channelB-OutOfRange
The channel on the B side is out of range.
109
moduleB-Uninitialized
The slot on the B side has not been initialized. The
cause could be an internal error or the module is not
seated.
110
physicalPortB-Uninitialized
The port on the B side has not been initialized. The
cause could be an internal error or the module is not
seated.
111
channelB-NotBound
The channel on the B side has not been bound to an
interface. The cause could be an internal error or the
interface has not been brought into service at least
once or is not configured.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-89
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
112
moduleB-UnrecognizablePortType An internal error in which port type is not recognizable for the Module on side B.
113
interfaceA-NotAtm
The interface attached to the slot, port, or channel on
the A side is not ATM. It is used when an ATM connection is tried on an interface that is not ATM.
114
interfaceB-NotAtm
The interface attached to the slot, port, or channel on
the B side is not ATM. It is used when an ATM connection is tried on an interface that is not ATM.
115
unrecognizableServiceTypeA2B
The service type is not supported for this connection
in the A2B direction.
116
unrecognizableServiceTypeB2A
The service type is not supported for this connection
in the B2A direction.
117
unrecognizableSarTypeA2B
The SAR (segmentation and reassembly) type is not
supported for this connection in the A2B direction.
118
unrecognizableSarTypeB2A
The SAR (segmentation and reassembly) type is not
supported for this connection in the B2A direction.
119
interfaceA-NotCircuitEmulation
The interface attached to the slot, port, or channel on
the A side is not circuit emulation. It is used when a
circuit emulation connection is tried on an interface
that is not circuit emulation.
120
interfaceB-NotCircuitEmulation
The interface attached to the slot, port, or channel on
the B side is not circuit emulation. It is used when a
circuit emulation connection is tried on an interface
that is not circuit emulation.
121
unrecognizableSilenceDetectionMode
The silence detection type is not valid.
122
unrecognizableEchoCancellationMode
The echo cancelation type is not valid.
123
unrecognizableVoiceCompression- The voice compression type is not valid.
Mode
124
interfaceA-NotVbr
The interface attached to the slot, port, or channel on
the A side is not vbr(i.e hdlc/terminal emulation). It
is used when a VBR connection is tried on an interface that is not VBR.
125
interfaceB-NotVbr
The interface attached to the slot, port, or channel on
the B side is not vbr(i.e hdlc/terminal emulation). It
is used when a VBR connection is tried on an interface that is not VBR.
126
interfaceA-NotFrameRelay
The interface attached to the slot, port, or channel on
the A side is not frame relay. It is used when a frame
relay connection is tried on an interface that is not
frame relay.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-90
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
127
interfaceB-NotFrameRelay
The interface attached to the slot, port, or channel on
the B side is not frame relay. It is used when a frame
relay connection is tried on an interface that is not
frame relay.
128
interfaceA-InHdlcPvcList
The interface attached to the slot, port, or channel on
the A side is already present in the hdlc PVC list for
another connection.
129
interfaceA-InHdlcReleasedList
The interface attached to the slot, port, or channel on
the A side is already present in the hdlc released list
for another connection.
130
interfaceA-InHdlcReservedList
The interface attached to the slot, port, or channel on
the A side is already present in the hdlc reserved list
for another connection.
131
interfaceA-InTerminalEmulationPvcList
The interface attached to the slot, port, or channel on
the A side is already present in the terminal emulation PVC list for another connection.
132
interfaceA-InTerminalEmulationReleasedList
The interface attached to the slot, port, or channel on
the A side is already present in the terminal emulation released list for another connection.
133
interfaceA-InTerminalEmulationReservedList
The interface attached to the slot, port, or channel on
the A side is already present in the terminal emulation reserved list for another connection.
134
interfaceA-InCircuitEmulationPvcList
The interface attached to the slot, port, or channel on
the A side is already present in the circuit emulation
PVC list for another connection.
135
interfaceA-InCircuitEmulationReleasedList
The interface attached to the slot, port, or channel on
the A side is already present in the circuit emulation
released list for another connection.
136
interfaceA-InCircuitEmulationReservedList
The interface attached to the slot, port, or channel on
the A side is already present in the circuit emulation
reserved list for another connection.
137
notNullVpcInNoisyLinkA2BIgrs
The VPC should be 0 for forward error correction
connections on the input side of the A2B direction.
138
notNullVpcInNoisyLinkA2BEgrs
The VPC should be 0 for forward error correction
connections on the output side of the B2A direction.
139
invalidVccInNoisyLinkA2BIgrs
The VCC for forward error correction enabled connection is not valid. The error is in the input side of
A2B direction.
140
invalidVccInNoisyLinkA2BEgrs
The VCC for forward error correction enabled connection is not valid. The error is in the input side of
A2B direction.
141
unsupportedFrwdErrCorrectValue
A2B
A generic message indicating unsupported values for
a forward error correction enabled connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-91
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
142
interfaceB-InHdlcPvcList
The interface attached to the slot, port, or channel on
the B side is already present in the hdlc PVC list for
another connection.
143
interfaceB-InHdlcReleasedList
The interface attached to the slot, port, or channel on
the B side is already present in the hdlc released list
for another connection.
144
interfaceB-InHdlcReservedList
The interface attached to the slot, port, or channel on
the B side is already present in the hdlc reserved list
for another connection.
145
interfaceB-InTerminalEmulationPvcList
The interface attached to the slot, port, or channel on
the B side is already present in the hdlc terminal
emulation PVC list for another connection.
146
interfaceB-InTerminalEmulationReleasedList
The interface attached to the slot, port, or channel on
the B side is already present in the hdlc terminal
emulation released list for another connection.
147
interfaceB-InTerminalEmulationReservedList
The interface attached to the slot, port, or channel on
the B side is already present in the hdlc terminal
emulation reserved list for another connection.
148
interfaceB-InCircuitEmulationPvcList
The interface attached to the slot, port, or channel on
the B side is already present in the circuit emulation
PVC list for another connection.
149
interfaceB-InCircuitEmulationReleasedList
The interface attached to the slot, port, or channel on
the B side is already present in the circuit emulation
released list for another connection.
150
interfaceB-InCircuitEmulationReservedList
The interface attached to the slot, port, or channel on
the B side is already present in the circuit emulation
reserved list for another connection.
151
notNullVpcInNoisyLinkB2AIgrs
The virtual path identifier must be 0 for forward correction enabled connections. This error is in the input
side of the B2A direction.
152
notNullVpcInNoisyLinkB2AEgrs
The virtual path identifier must be 0 for forward correction enabled connections. This error is in the output side of the B2A direction.
153
invalidVccInNoisyLinkB2AIgrs
The virtual path identifier value is not valid with
respect to enabling the forward error correction feature. This error is in the input side of the B2A direction.
154
invalidVccInNoisyLinkB2AEgrs
The virtual path identifier value is not valid with
respect to enabling the forward error correction feature. This error is in the output side of the B2A direction.
155
unsupportedFrwdErrCorrectValue
B2A
The forward error correction type is not valid.
156
interfaceInUse
The interface is being used by another connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-92
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
157
unsupportedFrwdErrCorrectSettings
The forward error correction settings are not supported for some configuration combinations.
158
unsupportedFlowSettings
The flow settings are not supported.
159
frwdErrCorrectResourceInternalError
An internal error occurred with respect to the forward error correction feature.
160
unsupportedConnection
A generic message indicating an error.
161
ipDestAddrSubnetAInReservedList Used for In-band Management Connections. The IP
address is already used for another connection in the
reserved list. This is for the A side.
162
ipDestAddrSubnetAInPvcList
163
ipDestAddrSubnetAInReleasedList Used for In-band Management Connections. The IP
address is already used for another connection in the
released list. This is for the A side.
164
ipDestAddrSubnetBInReservedList Used for In-band Management Connections. The IP
address is already used for another connection in the
reserved list. This is for the B side.
165
ipDestAddrSubnetBInPvcList
166
ipDestAddrSubnetBInReleasedList Used for In-band Management Connections. The IP
address is already used for another connection in the
released list. This is for the B side.
167
notCpuIpInterfaceA
An internal error for getting CPU IP interface
resource.
168
ipResourceUnavailable
An internal error for getting CPU IP resource.
169
fecAutoInSimplexNotValid
Forward error correction is not enabled for simplex
connections.
170
fecResourceUnavailable
Internal error in getting forward error correction
resources.
171
notBridgeInterfaceA
The interface associated with the slot, port, or channel is not a bridge interface. This is used when creating bridge connections and applies to the A side.
172
notBridgeInterfaceB
The interface associated with the slot, port, or channel is not a bridge interface. This is used when creating bridge connections and applies to the B side.
173
invalidBridgePortA2B
The interface associated with the slot, port, or channel is not valid because the port ID is not valid. This
error is in the input side of the A2B direction.
174
invalidBridgePortB2A
The interface associated with the slot, port, or channel is not valid because the port ID is not valid. This
error is in the input side of the B2A direction.
Used for In-band Management Connections. The IP
address is already used for another connection in the
PVC list. This is for the A side.
Used for In-band Management Connections. The IP
address is already used for another connection in the
PVC list. This is for the B side.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-93
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
175
interfaceAInBridgePvcList
The interface associated with the slot, port, or channel is already present in the PVC list and is currently
in use. This refers to the A side.
176
interfaceBInBridgePvcList
The interface associated with the slot, port, or channel is already present in the PVC list and is currently
in use. This refers to the B side.
177
interfaceAInBridgeReleasedList
The interface associated with the slot, port, or channel is already present in the released list and is currently in use. This refers to the A side.
178
interfaceBInBridgeReleasedList
The interface associated with the slot, port, or channel is already present in the released list and is currently in use. This refers to the B side.
179
interfaceAInBridgeReservedList
The interface associated with the slot, port, or channel is already present in the reserved list and is currently in use. This refers to the A side.
180
interfaceBInBridgeReservedList
The interface associated with the slot, port, or channel is already present in the reserved list and is currently in use. This refers to the B side.
181
invalidDlciA
The data link connection identifier value on the A
side is not valid.
182
invalidDlciB
The data link connection identifier value on the B
side is not valid.
183
unrecognizableServiceType
The service type is not supported.
184
moduleAMcstNotSupported
Slot A does not support multicast connections.
185
moduleBMcstNotSupported
Slot B does not support multicast connections.
186
moduleAMultiPortMcstNotSupported
Slot A does not support connections in which more
than 1 port can have 2 parties in a given multicast
group.
187
moduleBMultiPortMcstNotSupported
Slot B does not support connections in which more
than 1 port can have 2 parties in a given multicast
group.
188
bcBeCirCannotBeNullA2B
In Frame Relay connections, all 3, committed burst,
excess burst, and committed information rate cannot
be 0. This refers to the A2B direction.
189
bcBeCirCannotBeNullB2A
In Frame Relay connections, all 3, committed burst,
excess burst, and committed information rate cannot
be 0. This refers to the B2A direction.
190
bcBeOrCirValTooHiA2B
This value of committed burst, excess burst, or committed information rate is too high. This is in reference to the A2B direction.
191
bcBeOrCirValTooHiB2A
This value of committed burst, excess burst, or committed information rate is too high. This is in reference to the B2A direction.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-94
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
192
bcNotValidA2B
Committed burst cannot be 0 if committed information rate is non-zero. This is in reference to the A2B
direction.
193
bcNotValidB2A
Committed burst cannot be 0 if committed information rate is non-zero. This is in reference to the B2A
direction.
194
beNotValidA2B
The excess burst size is too small if the committed
burst and committed information rate is zero. This is
in reference to the A2B direction.
195
beNotValidB2A
The excess burst size is too small if the committed
burst and committed information rate is zero. This is
in reference to the B2A direction.
196
bcOrCirNotValidA2B
The committed burst or committed information rate
size is too small. This is in reference to the A2B direction.
197
bcOrCirNotValidB2A
The committed burst or committed information rate
size is too small. This is in reference to the B2A direction.
198
iWF-NotSupportedModuleA
The interworking function type requested is not supported for module A.
199
iWF-NotSupportedModuleB
The interworking function type requested is not supported for module B.
200
invalidMaxFrSizeA2B
The maximum frame size for rate calculation is not
within the standard range in the A2B direction.
201
invalidMaxFrSizeB2A
The maximum frame size for rate calculation is not
within the standard range in the B2A direction.
202
invalidSARType
The SAR (segmentation and reassembly) type is not
valid.
203
unrecognizableSilenceDetectionM
odeA2B
Silence detection mode is not valid in the A2B direction.
204
unrecognizableEchoCancellationM Echo cancellation mode is not valid in the A2B direcodeA2B
tion.
205
unrecognizableVoiceCompression
ModeA2B
Voice compression mode is not valid in the A2B
direction.
206
unrecognizableCallingToneDetecti
onA2B
Calling tone detection mode is not valid in the A2B
direction.
207
unrecognizableCodingTranslationA Coding rule mode is not valid in the A2B direction.
2B
208
unrecognizableSilenceDetectionM
odeB2A
209
unrecognizableEchoCancellationM Echo cancellation mode is not valid in the B2A direcodeB2A
tion.
Silence detection mode is not valid in the B2A direction.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-95
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
210
unrecognizableVoiceCompression
ModeB2A
Voice compression mode is not valid in the B2A
direction.
211
unrecognizableCallingToneDetecti
onB2A
Calling tone detection mode is not valid in the B2A
direction.
212
unrecognizableCodingTranslationB Coding rule mode is not valid in the B2A direction.
2A
213
dspUnsupportedForMultiCastConns
DSP support is not available for multicast connections.
214
dspResourceUnavailable
DSP resources are not available for the connection
configuration given by the user.
215
destOrSrcCannotBeDSPCard
This is used for backward compatibility for old DSP
modules and this is not allowed if one of the interfaces is a DSP module.
216
internalDSPResourceError
An internal error indicating that the DSP interfaces
are not valid.
217
echoCancellationOnlySupportedForDuplex
Indicates that for echo cancellation to be supported
the connections have to be duplex.
218
cirEmCirEm-ThruPutMismatch
An indication that 2 circuit emulation interfaces with
different bandwidths cannot be connected.
219
vi-Cannot-Be-0
A virtual interface of zero already exists.
220
vi-OOR
The requested virtual interface number is out of
range for duplex connections.
221
vi-Mod-Limit-Exceeded
The number of virtual interfaces per module has
been exceeded.
222
vi-Resource-Unavail
The requested bandwidth for a virtual interface is not
available.
223
vi-Already-Exists
A virtual interface associated with that number has
already been created.
224
vi-Does-Not-Exist
A virtual interface connection no longer exists.
225
vi-0-Non-Ubr-Conn-Not-Supp
A non-UBR connection on virtual interfaces is not
supported for duplex connections.
226
vi-OS-Cannot-Be-0
The virtual interface oversubscription cannot be 0.
Must be at least 1.
227
vi-OS-OOR
The virtual interface oversubscription is not in the
range 1-10.
228
vi-CellRate-Too-Lo
The requested cell rate connection is below the available range.
229
vi-CellRate-Too-Hi
The requested virtual interface cell rate connection
exceeds the available range.
230
intf-CBR-CellRate-Exceeded
The available CBR cell rate has been exceeded.
231
intf-VBR-CellRate-Exceeded
The available VBR cell rate has been exceeded.
232
vi-Conn-CellRate-Exceeded
The requested cell rate exceeds available bandwidth.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-96
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
233
vi-Not-Enabled
The virtual interface feature is not enabled for duplex
connection.
234
vi-Should-Be-0
A UBR connection has been attempted on a virtual
interface with a designation other than VI=0 for a
duplex connection.
235
vi-OOR-A
The requested VI number is out of range for simplex
connections (Side A).
236
vi-OOR-B
The requested VI number is out of range for simplex
connections (Side B).
237
vi-0-Non-Ubr-Conn-Not-SuppA2B A non-UBR connection on virtual interface 0 is not
supported in the A2B direction.
238
vi-0-Non-Ubr-Conn-Not-SuppB2A A non-UBR connection on virtual interface 0 is not
supported in the B2A direction.
239
vi-Should-Be-0-A
A UBR connection has been attempted on a virtual
interface with a designation other than VI=0 for a
simplex connection (Side A).
240
vi-Should-Be-0-B
A UBR connection has been attempted on a virtual
interface with a designation other than VI=0 for a
simplex connection (Side B).
241
vi-Cbr-Bw-Unavailable-Egrs
The requested amount of egress CBR bandwidth is
unavailable for duplex connections.
242
vi-Cbr-Bw-Unavailable-Egrs-A
The requested amount of egress CBR bandwidth is
unavailable for simplex connections (Side A.)
243
vi-Cbr-Bw-Unavailable-Egrs-B
The requested amount of egress CBR bandwidth is
unavailable for simplex connections (Side B.)
244
vi-Vbr-Bw-Unavailable-Egrs
The requested amount of egress VBR bandwidth is
unavailable for a duplex connection.
245
vi-Vbr-Bw-Unavailable-Egrs-A
The requested amount of egress VBR bandwidth is
unavailable for a simplex connection (Side A).
246
vi-Vbr-Bw-Unavailable-Egrs-B
The requested amount of egress VBR bandwidth is
unavailable for a simplex connection (Side B).
247
vi-Not-Enabled-A
The virtual interface feature is not enabled for duplex
connection (Side A).
248
vi-Not-Enabled-B
The virtual interface feature is not enabled for duplex
connection (Side B).
249
pcrLessThanScr
The peak cell rate is less than the sustained cell rate.
250
cnfrmTypeNotValidA2B
Conformance type is not valid in the A2B direction.
251
cnfrmTypeNotValidB2A
Conformance type is not valid in the B2A direction.
252
cnfrmType-ServiceType-Mismatch- A combination of conformance type and service type
A2B
is not supported in the A2B direction.
253
cnfrmType-ServiceType-Mismatch- A combination of conformance type and service type
B2A
is not supported in the B2A direction.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-97
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
254
vuni-Should-Be-0
The virtual UNI should be 0.
255
vuni-Not-Enabled
The virtual UNI is not enabled at the main interface
level.
256
vuni-OOR
The virtual UNI value is out of range.
257
vuni-Already-Exists
The virtual UNI already exists.
258
vuni-Does-Not-Exist
The virtual UNI does not exist.
259
vuni-Does-Not-Match-vi
If VI is enabled at the main interface level and if the
VUNI is non-zero the VI value and VUNI value
should match.
260
vuni-Should-Be-0-A
VUNI should be 0 if the VUNI feature is disabled at
the main interface level. The error in on the A side.
261
vuni-Not-Enabled-A
The VUNI feature is not enabled at the main interface
level. The error in on the A side.
262
vuni-OOR-A
The virtual UNI is out of range. The error is on the A
side.
263
vuni-Already-Exists-A
The virtual UNI already exists. The error is on the A
side.
264
vuni-Does-Not-Exist-A
The virtual UNI does not exist. The error is on the A
side.
265
vuni-Does-Not-Match-vi-A
If VI is enabled at the main interface level and if the
VUNI is non-zero the VI value and VUNI value
should match. The error in on the side A.
266
vuni-Should-Be-0-B
VUNI should be 0 if the VUNI feature is disabled at
the main interface level. The error is on the B side.
267
vuni-Not-Enabled-B
The VUNI feature is not enabled at the main interface
level. The error in on the B side.
268
vuni-OOR-B
The virtual UNI is out of range. The error is on the B
side.
269
vuni-Already-Exists-B
The virtual UNI already exists. The error is on the B
side.
270
vuni-Does-Not-Exist-B
The virtual UNI does not exist. The error is on the B
side.
271
vuni-Does-Not-Match-vi-B
If VI is enabled at the main interface level and if the
VUNI is non-zero the VI value and VUNI value
should match. The error in on the side B.
272
vuni-Vpi-OOR
The VPI value is out of range for the VUNI.
273
vuni-Vpi-OOR-A
The VPI value is out of range for the VUNI. The error
is on the A side.
274
vuni-Vpi-OOR-B
The VPI value is out of range for that VUNI. The error
is on the B side.
275
stdAal2TrunkResourceUnavailable An internal error indicating that the standard AAL2
resource is not available.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-98
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
276
stdAal2Dsp2ResourceUnavailable
Standard AAL2 DSP2 resource is not available.
277
slotStdAal2ResourceUavailable
An internal error in which slot level resources for
standard AAL2 are not available.
278
stdAal2CIDAlreadyInUse
AAL2 CID is already in use.
279
stdAal2TrunkBWUavailableEgrs
Bandwidth at the trunk level is not available on the
output side.
280
stdAal2TrunkBWUavailableIgrs
Bandwidth at the trunk level is not available on the
input side.
281
stdAal2CIDInRsvRange
The AAL2 CID value is in reserved range.
282
stdAal2TrunkNotSetup
Standard AAL2 trunk is not setup. The trunk should
be setup before AAL2 CIDs can be added to the
trunk.
283
aal2CIDOutOfRange
The AAL2 CID value is out of valid range.
284
dhpvcSwitchOver-PrimToBkup
This is not an error trap. This is an informational trap
to indicate that the DHPVC has switched from Primary to Backup conn.
285
dhpvcSwitchOver-PrimToNone
This is not an error trap. This is an informational trap
to indicate that the DHPVC has switched from Primary to none.
286
dhpvcSwitchOver-NoneToPrim
This is not an error trap. This is an informational trap
to indicate that the DHPVC has switched from none
to Primary. That is the primary has recovered.
287
dhpvcSwitchOver-NoneToBkup
This is not an error trap. This is an informational trap
to indicate that the DHPVC has switched from none
to Primary. That is the backup has recovered.
288
dhpvcSwitchOver-BkupToNone
This is not an error trap. This is an informational trap
to indicate that the DHPVC has switched from
Backup to none.
289
dhpvcSwitchOver-BkupToPrim
This is not an error trap. This is an informational trap
to indicate that the DHPVC has switched from none
to Primary. That is the primary has recovered.
290
dhpvcState-Prim-Pass-Fail-BkupAct-NoFail
This is not an error trap. This is an informational trap
to indicate that the DHPVC has had a change in state
but does not result in a switchover. The current state
is Primary is Passive and is not able to pass traffic and
Backup is in Active state and it is also able to pass
traffic.
291
dhpvcState-Prim-Pass-NoFailBkup-Act-NoFail
This is not an error trap. This is an informational trap
to indicate that the DHPVC has had a change in state
but does not result in a switchover. The current state
is Primary is Passive and is able to pass traffic and
Backup is in Active state and it is also able to pass
traffic.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-99
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
292
dhpvcState-Prim-Act-NoFailBkup-Pass-Fail
This is not an error trap. This is an informational trap
to indicate that the DHPVC has had a change in state
but does not result in a switchover. The current state
is Primary is Active and is able to pass traffic and
Backup is in Passive state and it is not able to pass
traffic.
293
dhpvcState-Prim-Act-NoFailBkup-Pass-NoFail
This is not an error trap. This is an informational trap
to indicate that the DHPVC has had a change in state
but does not result in a switchover. The current state
is Primary is Active and is able to pass traffic and
Backup is in Passive state and it is able to pass traffic.
294
pcrGreaterThanLinkSpeedIngrA2B The peak cell rate in the A2B direction is greater than
the input interface on the A2B direction.
295
pcrGreaterThanLinkSpeedIngrB2A The peak cell rate in the B2A direction is greater than
the input interface on the B2A direction.
296
pcrGreaterThanLinkSpeedEgrA2B
The peak cell rate in the A2B direction is greater than
the output interface on the A2B direction.
297
pcrGreaterThanLinkSpeedEgrB2A
The peak cell rate in the B2A direction is greater than
the output interface on the B2A direction.
298
aal2CuTimerOutOfRange
This error code is generated when the aal2CuTimer
value is out of range and the valid range is 0 to 8 (0 40 msec of delay).
299
unrecognizableDigitCollectTypeA2 Unrecognizable digital tone set in connection A2B
B
direction.
300
unrecognizableDigitCollectTypeB2 Unrecognizable digital tone set in connection B2A
A
direction.
301
queueTypeSarTypeMismatchA2B
The queue type and SAR type do not match in the A
to B direction.
302
queueTypeSarTypeMismatchB2A
The queue type and SAR type do not match in the B
to A direction.
303
pcrLessThanOrEqualToMcrA2B(
The PCR is less than or equal to the MCR in the A to
B direction which is not valid. (PCR should be greater
than or equal to the MCR.)
304
pcrLessThanOrEqualToMcrB2A
The PCR is less than or equal to the MCR in the B to
A direction which is not valid. (PCR should be greater
than or equal to the MCR.)
305
connectionDoesNotExist
The connection does not exist.
306
oamStatusMismatch
The OAM status does not match.
307
cnfrmType-SarType-MismatchA2B Conformance type and SAR type do not match in the
A2B direction.
308
cnfrmType-SarType-MismatchB2A
Conformance type and SAR type do not match in the
B2A direction.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-100
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
309
numRsvChannelsAlreadyUsed
This is used when the user has configured the numDspRsvChannels to be non-zero and have used up to
the limit which was reserved.
310
trunkHasNoMonConnsConfigured This is used to indicate to the user that a channel is
being added to a GR-303 trunk without any monitor
connections.
311
dspSlotIdInvalidForManualTrunk
The DSP slot ID is not valid for manual trunk.
312
numDspRsvChannelsOutOfRange
The values of numDspRsvChannels are out of range.
313
unrecognizableVolumeLevelAdjust The volume level adjustments are unrecognizable in
mentsB2A
the B to A direction.
314
unrecognizableTransmitErrorDetection
315
unrecognizableTransmitErrorDetec Unrecognizable transmission error detection in the A
tionA2B
to B direction.
316
unrecognizableTransmitErrorDetec Unrecognizable transmission error detection in the B
tionB2A
to A direction.
317
sourceCardNotDspCardType
The dspSlotSwitchManualTrunkSlotId command has
failed. An indication that the module from which the
trunks have to be shifted is not a DSP module type.
318
destCardNotDspCardType
The dspSlotSwitchManualTrunkSlotId command has
failed. An indication that the module to which the
trunks have to be shifted is not a DSP module type.
319
sourceCardNotInManualConfiguration
The dspSlotSwitchManualTrunkSlotId command
failed. An indication that the module from which
trunks have to be shifted has not been enabled for
manual configuration.
320
destCardNotInManualConfiguration
The dspSlotSwitchManualTrunkSlotId command
failed. An indication that the module to which trunks
have to be shifted has not been enabled for manual
configuration.
321
sarType-CongestDiscardType-Mismatch-A2B
The sarType and congestDiscardType does not match
in the A to B direction.
322
sarType-CongestDiscardType-Mismatch-B2A
The sarType and congestDiscardType does not match
in the B to A direction.
323
bulkStatsCollectionTimePeriodOutOfRange
The minimum value is 60, and the maximum value is
1440.
324
invalidBulkStatsCollectionTimePe- The value of the bulk stats collection time period
riod
should be multiples of 60.
325
internalResourceErrorInSettingBul In the statsServerInfoGroup the field bulkStatsMaxkStatsFlagA2B
Usage would specify the maximum number of bulk
stats records that can be supported in the system. If
the limit is reached, the bulk stats flag cannot be
enabled for that interface because there is no
resource left in the system for the A to B direction.
Unrecognizable transmission error detection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-101
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
326
internalResourceErrorInSettingBul In statsServerInfoGroup the field bulkStatsMaxkStatsFlagB2A
Usage would specify the maximum number of bulk
stats records that can be supported in the system. If
the limit is reached, the bulk stats flag cannot be
enabled for that interface because there is no
resource left in the system for the B to A direction.
327
cirPlusEirGreaterThanLinkSpeedIn The committed information rate plus the excess
grsA2B
information rate are greater than the link speed of
the interface. The error is in the input side of the A2B
direction.
328
cirPlusEirGreaterThanLinkSpeedIn The committed information rate plus the excess
grsB2A
information rate are greater than the link speed of
the interface. The error is in the input side of the B2A
direction.
329
cirGreaterThanLinkSpeedIngrsA2B The committed information rate is greater than the
link speed of the interface. The error is in the input
side of the A2B direction.
330
cirGreaterThanLinkSpeedIngrsB2A The committed information rate is greater than the
link speed of the interface. The error is in the input
side of the B2A direction.
331
cirBandwidthUnavailableIngrsA2B The total committed information rate is greater than
the link speed of the interface. The error is in the
input side of the A2B direction.
332
cirBandwidthUnavailableIngrsB2A The total committed information rate is greater than
the link speed of the interface. The error is in the
input side of the B2A direction.
333
cirBandwidthUnavailableEgrsA2B
The total committed information rate is greater than
the link speed of the interface. The error is in the output side of the A2B direction.
334
cirBandwidthUnavailableEgrsB2A
The total committed information rate is greater than
the link speed of the interface. The error is in the output side of the B2A direction.
335
cirPlusEirBandwidthUnavailableIn The total committed information rate plus the total
grsA2B
excess information rate are greater than the link
speed of the interface multiplied by over subscription.
The error is in the input side of the A2B direction.
336
cirPlusEirBandwidthUnavailableIn The total committed information rate plus the total
grsB2A
excess information rate are greater than the link
speed of the interface multiplied by over subscription.
The error is in the input side of the B2A direction.
337
cirPlusEirBandwidthUnavailableEg The total committed information rate plus the total
rsA2B
excess information rate are greater than the link
speed of the interface multiplied by over subscription.
The error is in the output side of the A2B direction.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-102
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
338
cirPlusEirBandwidthUnavailableEg The total committed information rate plus the total
rsB2A
excess information rate are greater than the link
speed of the interface multiplied by over subscription.
The error is in the output side of the B2A direction.
339
cirGreaterThanLinkSpeedEgrsA2B The committed information rate is greater than the
link speed of the interface. The error is in the ouput
side of the A2B direction.
340
cirGreaterThanLinkSpeedEgrsB2A The committed information rate is greater than the
link speed of the interface. The error is in the output
side of the B2A direction.
341
cirPlusEirGreaterThanLinkSpeedEg The committed information rate plus the excess
rsA2B
information rate are greater than the link speed of
the interface. The error is in the output side of the
A2B direction.
342
cirPlusEirGreaterThanLinkSpeedEg The committed information rate plus the excess
rsB2A
information rate are greater than the link speed of
the interface. The error is in the output side of the
B2A direction.
343
atafMonitoringEnabledSuccessfully The connection to be monitored was successfully
converted to a set of multicast connections.
344
atafMonitoringDisabledSuccessfully
The connection being monitored was successfully
converted back to its original state.
345
atafMonitoringFailed-UnSupp
The connection could not be monitored because of
some unsupported configurations.
346
atafMonitoringFailed-OamEnabled The connection could not be monitored because
OAM is enabled.
347
atafMonitoringFailed-Aal2UnSupp The connection could not be monitored because it is
an AAL2 connection.
348
atafMonitoringFailed-Connection- The connection could not be monitored because the
NotPresent
original connection is not present.
349
atafMonitoringFailed-ConnAlreadyUnderAtaf
350
atafMonitoringFailed-ConnNotDu- The connection could not be monitored because the
plex
original connection is not a duplex connection.
351
trafficShapingOverCBRUnSupp
Traffic shaping over CBR connections are not supported.
352
atafMonitoringFailed-MonIfNotPresent
Monitoring failed because no interface is present on
the monitored side.
353
atafMonitoringFailed-MonIfNotAtm
Monitoring failed because the interface on the monitored side is not an ATM interface.
354
atafMonitoringFailed-MonVpiVciAlreadyUsed
The monitored side VPI/VCI is already in use.
355
vuni-Cbr-Bw-Unavailable-IngrsA2B
Bandwidth for the requested CBR connection is not
available at the virtual UNI ingress A2B side.
The connection is already being monitored.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-103
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-82. PVC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
356
vuni-Cbr-Bw-Unavailable-IngrsB2A
Bandwidth for the requested CBR connection is not
available at the virtual UNI ingress B2A side.
357
vuni-Cbr-Bw-Unavailable-EgrsA2B
Bandwidth for the requested CBR connection is not
available at the virtual UNI egress A2B side.
358
vuni-Cbr-Bw-Unavailable-EgrsB2A
Bandwidth for the requested CBR connection is not
available at the virtual UNI egress B2A side.
359
vuni-Vbr-Bw-Unavailable-IngrsA2B
Bandwidth for the requested VBR connection is not
available at the virtual UNI ingress A2B side.
360
vuni-Vbr-Bw-Unavailable-IngrsB2A
Bandwidth for the requested VBR connection is not
available at the virtual UNI ingress B2A side.
361
vuni-Vbr-Bw-Unavailable-EgrsA2B
Bandwidth for the requested VBR connection is not
available at the virtual UNI egress A2B side.
362
vuni-Vbr-Bw-Unavailable-EgrsB2A
Bandwidth for the requested VBR connection is not
available at the virtual UNI egress B2A side.
363
pcrGreaterThanEgrsLinkSpeedForT The PCR specified for the connection is greater than
S_A2B
the link speed on the egress side of a traffic shaped
connection in the A2B direction.
364
pcrGreaterThanEgrsLinkSpeedForT The PCR specified for the connection is greater than
S_B2A
the link speed on the egress side of a traffic shaped
connection in the B2A direction.
365
vi-Usedby-Vpc-Pnni-CannotDelete
The virtual interface cannot be deleted because VPC
PNNI is using this virtual interface.
366
vi-Usedby-Vuni-Cannot-Delete
The virtual interface cannot be deleted because VUNI
is using this virtual interface.
367
invalidVoiceCompressionModeA2B
The voice compression mode in the A2B direction is
not valid.
368
invalidVoiceCompressionModeB2A
The voice compression mode in the B2A direction is
not valid.
369
invalid-IwfType-For-StdAal2Trunk The interworking type for the standard AAL2 trunk is
not valid.
370
unrecognizable-SecureModeA2B
Unrecognizable secure mode in the A2B direction.
371
unrecognizable-SecureModeB2A
Unrecognizable secure mode in the B2A direction.
372
aal2TrunkNotCreatedByPvcHdlr
The AAL2 Trunk Table is also used to display PVC
trunks created by Aal2 Trunk Hdlr. In such conditions
this trunk should only be deleted by Aal2 Trunk Hdlr
and not by Pvc Hdlr.
373
numChansRsvNotSuppOfGr303Tr
unk
The Num Chans Reserved field should not be above 0
for trunks with GR-303 enabled.
374
vi-Cbr-Bw-Less-Than-Vuni-CbrBw
VI CBR bandwidth is less than VUNI’s CBR bandwidth.
375
vi-Vbr-Bw-Less-Than-Vuni-VbrBw
VI VBR bandwidth is less than VUNI's VBR bandwidth.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-104
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
remoteDbOperationErrorStatus
The result at the finish of a remote database operation. The valid range is a number between 0
and 7.
See Table 4-83 for a mapping between numbers and their enumerated type.
Associated Traps - remoteDbOperationStatusNotify
Table 4-83. Remote Database Operation Error Status
Number
Value
Enumerated Type
Description
0
none
None.
1
unableToMakeFtpConnection Unable to establish the FTP connection.
2
invalidDirectory
The directory is not valid.
3
unableToOpenDatabaseFile
Unable to open database file.
4
unableToCompleteFtp
Unable to complete FTP.
5
databaseSanityFail
The database check fails due to one of the following reasons: file version, file size, CRC (cyclic redundancy
check), software release version, file name.
6
unableToUpdateBackup
Unable to update backup.
7
userAbort
This operation has been canceled by the user.
remoteDbOperationStatus
The current status of the remote database command. The valid range is a number between 1 and
5.
See Table 4-84 for a mapping between numbers and their enumerated type.
Associated Traps - remoteDbOperationStatusNotify
Table 4-84. Remote Database Operation Status
Number
Value
Enumerated Type
Description
1
noActivity
No activity is the initial start state from boot-up.
2
working
Working is set while FTP’ing the announcement.
3
doneSuccessfully
Was successfully completed.
4
doneWithError
Done with error.
5
aborted
Canceled.
remoteRebootReasonCode
The result of a remote reboot request. The valid range is a number between 1 and 47.
See Table 4-85 for a mapping between numbers and their enumerated type.
Associated Traps - remoteRebootNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-105
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-85. Remote Reboot Reason Codes
Number
Value
Enumerated Type
Description
1
ioCard1Reboot-OK
The I/O module in slot 1 was rebooted successfully.
2
ioCard2Reboot-OK
The I/O module in slot 2 was rebooted successfully.
3
ioCard3Reboot-OK
The I/O module in slot 3 was rebooted successfully.
4
ioCard4Reboot-OK
The I/O module in slot 4 was rebooted successfully.
5
ioCard5Reboot-OK
The I/O module in slot 5 was rebooted successfully.
6
ioCard6Reboot-OK
The I/O module in slot 6 was rebooted successfully.
7
ioCard7Reboot-OK
The I/O module in slot 7 was rebooted successfully.
8
ioCard8Reboot-OK
The I/O module in slot 8 was rebooted successfully.
9
ioCard9Reboot-OK
The I/O module in slot 9 was rebooted successfully.
10
ioCard10Reboot-OK
The I/O module in slot 10 was rebooted successfully.
11
ioCard11Reboot-OK
The I/O module in slot 11 was rebooted successfully.
12
ioCard12Reboot-OK
The I/O module in slot 12 was rebooted successfully.
13
ioCard13Reboot-OK
The I/O module in slot 13 was rebooted successfully.
14
ioCard14Reboot-OK
The I/O module in slot 14 was rebooted successfully.
15
ioCard15Reboot-OK
The I/O module in slot 15 was rebooted successfully.
17
ioCard1Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 1.
18
ioCard2Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 2.
19
ioCard3Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 3.
20
ioCard4Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 4.
21
ioCard5Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 5.
22
ioCard6Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 6.
23
ioCard7Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 7.
24
ioCard8Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 8.
25
ioCard9Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 9.
26
ioCard10Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 10.
27
ioCard11Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 11.
28
ioCard12Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 12.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-106
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-85. Remote Reboot Reason Codes (Continued)
Number
Value
Enumerated Type
Description
29
ioCard13Reboot-NoCard In Slot
The I/O module reboot did not occur. No module is
present in slot 13.
30
ioCard14Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 14.
31
ioCard15Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 15.
32
ioCard16Reboot-NoCardInSlot
The I/O module reboot did not occur. No module is
present in slot 16.
33
allIOCardReboot-OK
All I/O module reboots were successful.
34
allIOCardReboot-NoIOCards
All I/O module reboots failed. The I/O Modules are
missing.
35
chassisReboot-Proceeding
The chassis reboot is proceeding.
36
backupCpuReboot-Proceeding
The backup CPU reboot is proceeding.
37
backupCpuReboot-NoBackup
No backup CPU reboot occurred.
38
primaryCpuReboot-Proceeding
The primary CPU reboot is proceeding.
39
primaryCpuSwitchover-Proceeding
The primary CPU switchover is proceeding.
40
primaryCpuSwitchoverNoBackup
No backup of the primary CPU switchover occurred.
41
chassisReboot-Fail-VersionControlInProgress
The chassis reboot failed because of ongoing version
control.
42
backupCpuReboot-Fail-VersionControlInProgress
The backup CPU reboot failed because of ongoing version control.
43
primaryCpuReboot-Fail-VersionControlInProgress
The primary CPU reboot failed because of ongoing version control.
44
primaryCpuSwitchover-Fail-VersionControlInProgress
The primary CPU switchover failed because of ongoing
version control.
45
primaryCpuSwitchover-FailBkCPUDataBaseNotNew
The primary CPU switchover failed. The files from the
primary CPU were unsuccessfully transferred to the
backup CPU.
46
primaryCpuSwitchover-Fail-BkC- The primary CPU switchover failed. The backup CPU
PUBuildNotGood
build is corrupt.
47
primaryCpuSwitchover-FailBkCPU-NotReady
The primary CPU switchover failed. The backup CPU is
not ready.
removeConfigFiles
Indicates the status of a remove configuration files request. The valid range is a number between
1 and 4.
See Table 4-86 for a mapping between numbers and their enumerated type.
Associated Traps - removeConfigFilesNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-107
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-86. Remove Configuration Files Codes
Number
Value
Enumerated Type
Description
1
from-PrimaryCPU
Configuration files removed from primary CPU.
2
from-BackupCPU
Configuration files removed from backup CPU.
3
chassisReboot
Chassis reboot being done after removing configuration files.
4
failed-VersionControlInProgress
Configuration file removal failed due to ongoing version control.
routeSrvStatus
Return codes for basic route server task operations not related to any specific VPN or IP/Connection operation. Valid range is a number between 1 and 4.
See Table 4-87 for a mapping between numbers and their enumerated type.
Associated Traps - viprRtSrvTrap
Table 4-87. Route Server Status Codes
Number
Value
Enumerated Type
Description
1
rsCardOK
Route server OK.
2
rsModInitFail
Route server failed module initialization.
3
rsIntfInitFail
Route server failed interface initialization.
4
rsPortInitFail
Route server failed port initialization.
routingStatus
Valid range is a number between 1 and 3.
See Table 4-88 for a mapping between numbers and their enumerated type.
Associated Traps - viprRoutingTrap
Table 4-88. Routing Status Codes
Number
Value
Enumerated Type
Description
1
success
Routing data is available.
2
failure
Reply from RS module timed-out.
3
tryAgain
Try again after 1 second and the response will be either
Success or Noroutes.
sapphireIntfAddressFailReasonCode
The result of assigning the Sapphire interface address when the PSAX system is Sapphire client.
The valid range is a number between 1 and 5.
See Table 4-89 for a mapping between numbers and their enumerated type.
Associated Traps - sapphireInterfaceAddressAssignFailNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-108
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-89. Sapphire Interface Address Fail Reason Codes
Number
Value
Enumerated Type
Description
1
address-assign-ok
Address assignment succeeded.
2
fail-Ilegal-IP-address
Illegal IP address assigned address does not match.
3
fail-not-match-InBandManagement-Switch-CPU-IPAddress
In-Band Management IP or Switch IP or CPU IP
address
4
fail-Switch-or-CPU-IPAddress-unconfigured
Switch IP or CPU IP address is not configured.
5
fail-InBandManagement-IPAddress-unconfigured
In-Band Management IP Address is not configured.
saveConfigurationReasonCode
The result of a save configuration request. The valid range is a number between 1 and 18.
See Table 4-90 for a mapping between numbers and their enumerated type.
Associated Traps - saveConfigurationNotify
Table 4-90. Save Configuration Reason Codes
Number
Value
Enumerated Type
Description
1
equipment-OK
Save of equipment configuration completed.
2
equipment-Fail-VersionControlIn- Save of equipment configuration failed due to ongoProgress
ing version control operation.
3
equipment-Fail
Save of equipment configuration failed.
4
connections-OK
Save of connection configuration completed.
5
connections-Fail-VersionControlInProgress
Save of connection configuration failed due to ongoing version control operation.
6
connections-Fail
Save of connection configuration failed.
7
routing-OK
Save of routing configuration completed.
8
routing-Fail-VersionControlInProgress
Save of routing configuration failed due to ongoing
version control operation
9
routing-Fail
Save of routing configuration failed.
10
all-OK
Saving of all configurations completed.
11
all-Fail-VersionControlInProgress
Saving of all configurations failed due to ongoing version control operation.
12
all-Fail
Saving of all configurations failed.
13
fileTransferFailed
Saving of configurations to secondary CPU failed.
14
fileTransferCompleted
Saving of configurations to secondary CPU completed.
15
unSupportedOption
Unsupported save option received.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-109
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-90. Save Configuration Reason Codes (Continued)
Number
Value
Enumerated Type
Description
16
fail-backupCpuInitializationInProgress
Save operation failed due to ongoing secondary CPU
initialization.
17
expect2ndCPURebootAfterSave
Notification to expect reboot of secondary CPU after a
save operation.
18
expect2ndCPUCardFailedOrRemo Notification indicating the secondary CPU module has
ved
been removed, has failed, or while rebooting after a
save operation is temporarily unavailable.
spvcAddrIfA
The interface index for side A of an SPVC connection. Number value is interpreted as an interface
of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel number.
Associated Traps - frAtmSpvcConfiguredNotify, frAtmSpvcConfigFailNotify, frAtmSpvcDeletedNotify, frAtmSpvcModifiedNotify, frAtmSpvcModifyFailNotify, atmAtmSpvcConfiguredNotify,
atmAtmSpvcConfigFailNotify, atmAtmSpvcDeletedNotify, atmAtmSpvcModifiedNotify, atmAtmSpvcModifyFailNotify, cirAtmSpvcConfiguredNotify, cirAtmSpvcConfigFailNotify, cirAtmSpvcDeletedNotify, cirAtmSpvcModifiedNotify, cirAtmSpvcModifyFailNotify, vbrAtmSpvcConfiguredNotify, vbrAtmSpvcConfigFailNotify, vbrAtmSpvcDeletedNotify, vbrAtmSpvcModifiedNotify,
vbrAtmSpvcModifyFailNotify, frAtmSpvcVccSetUpNotify, frAtmSpvcVccTearDownNotify, atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify, cirAtmSpvcVccSetUpNotify, cirAtmSpvcVccTearDownNotify, vbrAtmSpvcSetUpNotify, vbrAtmSpvcTearDownNotify, atmAtmSpvcConfiguredNotify, atmAtmSpvcConfigFailNotify, atmAtmSpvcDeletedNotify,
atmAtmSpvcModifiedNotify, atmAtmSpvcModifyFailNotify, atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify, atmAtmSpvcTfcParamModifyInProgressNotify, atmAtmSpvcTfcParamModifyNotify, atmAtmSpvcTfcaramModifyFailNotify, ermAtmSpvcConfiguredNotify
spvcConfigFailureCode
Identification of a cause for failure while configuring or modifying SPVC parameters. The valid
range is a number between 1 and 30.
See Table 4-91 for a mapping between numbers and their enumerated type.
Associated Traps - cirEmSpvcConfigFailNotify, cirEmSpvcModifyFailNotify, vbrSpvcConfigFailNotify, vbrSpvcModifyFailNotify, atmSpvcConfigFailNotify, atmSpvcModifyFailNotify, frAtmSpvcConfigFailNotify, frAtmSpvcModifyFailNotify, atmAtmSpvcConfigFailNotify, atmAtmSpvcModifyFailNotify, cirAtmSpvcConfigFailNotify, cirAtmSpvcModifyFailNotify,
vbrAtmSpvcConfigFailNotify, vbrAtmSpvcModifyFailNotify, atmAtmSpvpConfigFailNotify,
atmAtmSpvpModifyFailNotify, ermAtmSpvcConfiguredNotify, ermAtmSpvcModifyFailNotify
Table 4-91. SPVC Configuration Failure Codes
Number
Value
Enumerated Type
Description
1
noSpvcConfigured
The endpoint has not been configured as SPVC, so SPVC
parameters cannot be modified.
2
spvcAlreadyConfigured
SPVC is already configured, so it cannot be configured
again as SPVC endpoint.
3
noInterfaceConfigured
There is no interface configured.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-110
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-91. SPVC Configuration Failure Codes (Continued)
Number
Value
Enumerated Type
Description
4
interfaceNotConfiguredAsRequired
While configuring it as SPVC endpoint, this interface is
not as desired (e.g., it is not CE, while trying to configure
CES SPVC).
6
notActiveSpvc
If the endpoint is configured with flowType ptToMptA2B
the connType has to be activeSvc.
7
slotA-OutofRange
A-side of SPVC connection has slot number out of range.
8
portA-OutofRange
A-side of SPVC connection has port number out of
range.
9
channelA-OutofRange
A-side of SPVC connection has channel number out of
range.
10
vpiVciWithInSvcRange
A-side of SPVC connection has VPI/VCI configured in the
SVC range of the A-side ATM interface.
11
retryIntervalExceedsTheLimit
Retry interval exceeds 3600 seconds.
12
interfaceNotConfiguredAsCE
SPVC endpoint is configured as something other than
CE.
13
interfaceNotConfiguredAsVbr
SPVC endpoint is configured as something other than TE.
14
interfaceNotConfiguredAsAtm
SPVC endpoint is configured as something other than
ATM.
15
noAddressConfiguredOnTheInterface
Local address not configured for the particular SPVC
being configured.
16
localAddressNotValid
NSAP address format is not valid.
17
vpiVciUnavailable
SPVC already setup on particular VPI/VCI.
18
pvcAlreadySetupOnVpiVci
VPI/VCI being used by another PVC.
19
pvcAlreadySetupOnInterface
redundant, same as 18 above
20
retryIntervalTooSmall
If we retry at intervals less than this, some calls may not
go through.
21
interfaceNotConfiguredAsFr
SPVC endpoint is configured as something other than FR
22
dlciUnavailable
DLCI not available at passive endpoint.
23
pvcAlreadySetupOnDlci
DLCI being used by another PVC.
24
frTrafficParamsUnsupp
FR-ATM traffic mapping failure.
25
dsp2ParamsUnsupp
DSP2 parameters not supported for the call.
26
sarNotConfigReq
SAR type not configured as required.
27
vuniNotMatch(27)
The virtual UNI does not match.
28
ipParamsNotAcceptable
The IP parameters are incorrect.
29
spvcTfcModFacRej
An attempt to modify SPVC traffic parameters has failed
due to FACILITY REJECT.
30
viNotMatch
The VI is not configured or is not valid.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-111
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
statRtStatus
Return codes for the Route Server module static route conditions. The valid range is a number
between 1 and 28.
See Table 4-92 for a mapping between numbers and their enumerated type.
Associated Traps - viprStatRtTrap
Table 4-92. Static Route Codes
Number
Value
Enumerated Type
Description
1
statRtOk
Static route OK
2
statRtIntFailure
Memory corruption
3
statRtMany
Too many static routes
4
statRtSlot
Impossible slot ID
5
statRtBadId
Bad VPN ID
6
statRtBadState
State machine confusion
7
statRtBadTimer
Bad timer value: state machine
8
statRtExists
Static Route already exists
9
statRtCantFind
Unused
10
statRtDelInProgress
Deleting: must wait
11
statRtLockedIdle
Static route taken out of service
12
statRtBadNetMask
Bad network mask
13
statRtCorrelation
Internal correlation error
14
statRtShutting
Shutting down: must wait
15
statRtDisabled
Subsystem failure
16
statRtBadMetric
Illegal metric value
17
statRtBadIPAddr
Bad static route IP address
18
intfRtExists
Static route on different interface
19
statRtBadSlot
Impossible slot ID
20
statRtBadRouterId
Bad VPN/router ID
21
statRtBadRouteId
Illegal static route ID
22
statRtBadRouteNetMask
Bad static route network mask
23
statRtBadRouteIpAddr
Bad interface IP address
24
statRtBadGtwyIpAddr
Bad gateway IP address
25
statRtBadDestIpAddr
Bad destination IP address
26
statRtBadDestNetMask
Bad destination IP mask
27
statRtCantFindRouter
Cannot find VPN
28
statRtCantFindRoute
Cannot find static route
stratumConfigModifyFailureReasonCode
Identifies the cause of a failure in changing the parameters of the stratum module. The valid
range is a number between 1 and 2.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-112
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
See Table 4-93 for a mapping between numbers and their enumerated type.
Table 4-93. Stratum Configuration Modification Failure Reason Codes
Number
Value
Enumerated Type
Description
1
unSupportedOption
The option or configuration is not supported.
2
onlyCompositeClockDS0aAllowedAsDS0aCardIsConfigured
When a DS0A module is configured, the only
option for stratum sync source is
compositeClockDS0A.
stratumMode
The current status of the primary Stratum 3–4 module. The valid range is a number between 1
and 5.
See Table 4-94 for a mapping between numbers and their enumerated type.
Associated Traps - stratumModeChangeNotify
Table 4-94. Stratum 3–4 Module Mode Codes
Number
Value
Enumerated Type
Description
1
synchronized3
The stratum is synchronized with accuracy 4.6 x 10e-6.
2
synchronized4
The stratum is synchronized with accuracy 3.2 x 10e-5.
3
holdover
An operating condition of a clock that has lost its controlling input and is using stored data acquired while in
normal operation, to control its output.
4
freerun
An operating condition of the clock when the clocks
output signals are internally controlled.
5
cardRemoved
The stratum module has been removed.
stratumBackupMode
The current status of the backup Stratum 3–4 module. The valid range is a number between 1 and
5.
See previous table for a mapping between numbers and their enumerated type.
Associated Traps - stratumModeChangeNotify
subChanStatus
Return codes for route server sub channel connections operations. The valid range is a number
between 1 and 34.
See Table 4-95 for a mapping between numbers and their enumerated type.
Associated Traps - viprSubChanTrap
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-113
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-95. Subchannel Status Codes
Number
Value
Enumerated Type
Description
1
scOK
Subchannel OK
2
scIntFailure
Memory corruption
3
scTooMany
Too many subchannels
4
scBadSlot
Impossible slot number
5
scBadId
Bad VPN ID
6
scBadState
State machine confusion
7
scBadTimerVal
Bad timer value: state machine
8
scExists
Subchannel already exists
9
scCantFind
Unused
10
scDelInProgress
Deleting: must wait
12
scLockedIdle
Subchannel taken out of service
13
scSameVc
Connection in use already
14
scFailedSetup
Reference previous trap
15
scShutting
Shutting Down: must wait
16
scDisabled
SubSystem disabled
17
scSetupErr
Subchannel setup error.
18
scRemvErr
Error removing subchannel
19
scBadPortNo
Bad port specified
20
scBadImIpAddr
Bad in-band IP address
21
scBadRouterId
Bad VPN/router ID
22
scBadIntfId
Impossible interface ID
23
scBadChanId
Impossible channel ID
24
scCantFindRouter
Cannot find VPN
25
scCantFindIntf
Cannot find Interface
26
scCantFindChan
Cannot find subchannel
27
scPppPppOEOnSameChan
PPP and PPPoE are enabled on the same channel.
28
scPppWrongMru
Wrong PPP maximum receive unit
29
scPppOpNotAllowed
PPP operation is not allowed.
30
scPppConfigOk
PPP configuration is ok.
31
scPppIntFailure
PPP internal failure.
32
scPppNotSupported
PPP is not supported.
33
scPppOENotSupported
PPPoE is not supported.
34
peerAddressProblem
The peer address should not be configured.
35
@colorCannotBeSet
The color value cannot be set when CoS is disabled.
36
missingColorValue
The color value must be specified.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-114
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-95. Subchannel Status Codes (Continued)
Number
Value
Enumerated Type
Description
37
colorValueConflict
The color value conflicts with another sub channel on
this interface.
38
colorNotLegalOnThisType
The color value cannot be set on the given sub channel
connection type.
39
scPPPTmpltIdNotExists
The template ID does not exist.
svcRetBackupStatus
The backup CPUn status wrt SVC retention. The valid range is a number between 1 and 3.
See Table 4-96 for a mapping between numbers and their enumerated type.
Associated Traps - svcRetBackupStatusChangeNotify
Table 4-96. SVC Retention Backup Status
Number
Value
Enumerated Type
Description
1
no-sync
The CPUns are not synchronized because the
backup CPUn is not present.
2
sync-in-progress
Synchronization is in progress.
3
fully-sync
Both CPUns are fully synchronized.
switchAlarmStatus
The current status of the alarm on the switch. The valid range is a number between 1 and 5.
See Table 4-97 for a mapping between numbers and their enumerated type.
Associated Traps - switchAlarmStatusChangeNotify
Table 4-97. Switch Alarm Status Codes
Number
Value
Enumerated Type
Description
1
notAvailable
The alarm status could not be retrieved.
2
none
No alarm is present.
3
minor
An alarm of the enumerated type is present.
4
major
An alarm of the enumerated type is present.
5
critical
An alarm of the enumerated type is present.
switchFanStatus
The current status of the fans on the switch. The valid range is a number between 1 and 3.
See Table 4-98 for a mapping between numbers and their enumerated type.
Associated Traps - switchFanStatusChangeNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-115
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-98. Switch Fan Status Codes
Number
Value
Enumerated Type
Description
1
notAvailable
The fan status could not be retrieved.
2
alarmSet
The status on the Fan/Alarm module if any of the fans
are not spinning.
3
alarmClear
No alarm is present for the fans.
swtchNodeIndx
Switch Node Index for PNNI.
Associated Traps - pnniNodeCfgNotify, pnniNodeCfgFailNotify, pnniNodeModFailNotify, pnniNodeDelFailNotify, pnniNodeOOSFailNotify, pnniNodeISFailNotify, pnniRtAddrCfgNotify, pnniRtAddrCfgFailNotify, pnniRtAddrModFailNotify, pnniRtAddrDelFailNotify, pnniRtAddrAddByIlmiNotify, pnniRtAddrDelByIlmiNotify
sysInfoDisplayString
Provides a string such as a software component name or other names depending on the circumstance of the trap message.
Associated Traps - softwareComponentFailedAndRestartedNotify
tasCmprsAnnceReasonCode
The result of a TAS Module compress announcement request. The valid range is a number
between 1 and 5.
See Table 4-99 for a mapping between numbers and their enumerated type.
Associated Traps - tasCmprsAnnceNotify
Table 4-99. TAS Module Compression Announcement Reason Codes
Number
Value
Enumerated Type
Description
1
cmprs-success
Compression successfully occurred.
2
cmprs-Fail-equipment-Fail
Compression failed because of an equipment failure.
3
cmprs-Fail-connections-Fail
Compression failed because of a connection
failure.
4
cmprs-Fail-resource-busy
Compression failed due to busy resource.
5
cmprs-Fail-resource-unavail
Compression failed because the resource
was unavailable.
tasContinuityCheckReasonCode
The result of a continuity check request. The valid range is a number between 1 and 6.
See Table 4-100 for a mapping between numbers and their enumerated type.
Associated Traps - tasContinuityCheckNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-116
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-100. TAS Module Continuity Check Reason Codes
Number
Value
Enumerated Type
Description
1
cc-success
Continuity check request has been successfully done.
2
cc-Fail-equipment-Fail
Slot, port, channel, VPI, VCI are not in the range.
3
cc-Fail-connections-Fail
The TASM connection ID is not valid. cc-Fail-resourcebusy: interface is already in use by another function.
4
cc-Fail-resource-busy
The interface is already in use by another function.
5
cc-Fail-resource-unavail
Not enough resource for this continuity check or bandwidth is unavailable or QoS is unavailable.
6
cc-Fail-time-out
The continuity check timed out.
tasmCacheMemAllocFailReasonCode
The result of a tasm control block memory allocation request. The valid range is a number
between 1 and 2.
See Table 4-101 for a mapping between numbers and their enumerated type.
Associated Traps - tasmCacheMemAllocFailNotify
Table 4-101. TAS Module Cache Memory Allocation Reason Codes
Number
Value
Enumerated Type
Description
1
res-alloc-success
The resource allocation was successful.
2
res-alloc-Fail-announcecache-mem-unavail
The resource allocation failed because the announce cache
memory was unavailable.
tasmControlBlockAllocFailReasonCode
The result of a tasm control block memory allocation request. The valid range is a number
between 1 and 4.
See Table 4-102 for a mapping between numbers and their enumerated type.
Associated Traps - tasmControlBlockResAllocFailNotify
Table 4-102. TAS Module Control Block Memory Reason Codes
Number
Value
Enumerated Type
Description
1
res-alloc-success
The resource allocation was successful.
2
res-alloc-Fail-announce-control-blocks-mem-
The resource allocation failed because of insufficient control block memory.
3
res-alloc-Fail-digit-controlblocks-mem-
The resource allocation failed because of insufficient digit
control block memory.
4
res-alloc-Fail-line-test-controlblocks-mem-
The resource allocation failed because of insufficient test
line control block memory.
tasMemReasonCode
The result of a memory initialization request. The valid range is a number between 1 and 2.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-117
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
See Table 4-103 for a mapping between numbers and their enumerated type.
Associated Traps - tasMemNotify
Table 4-103. TAS Module Memory Reason Codes
Number
Value
Enumerated Type
Description
1
mem-init-success
Memory initialization successfully occurred.
2
mem-init-Fail
Memory initialization failed.
tasTrapAnnceId
Announcement ID for trap. SYNTAX INTEGER (001..255)
Associated Traps - tasCmprsAnnceNotify,
tasTrapContinuityCheckIntfIndex
The interface index in SSPPCCC format of TASM module on which continuity check is to be
done.
Associated Traps - tasContinuityCheckNotify
tasTrapTstId
Test ID for trap. SYNTAX INTEGER (001..100)
Associated Traps - tasTstLineNotify
tasTstLineReasonCode
The result of a test line request. The valid range is a number between 1 and 5.
See Table 4-104 for a mapping between numbers and their enumerated type.
Associated Traps - tasTstLineNotify
Table 4-104. TAS Module Test Line Request Codes
Number
Value
Enumerated Type
Description
1
tst-success
The test line was successful.
2
tst-Fail-equipment-Fail
The test line failed because of equipment failure.
3
tst-Fail-invalid-params
The test line failed because the parameters are not valid.
4
tst-Fail-resource-unavail
The test line failed because the resource is unavailable.
5
tst-Fail-resource-busy
The test line failed because the resource is busy.
timingReasonCode
Indicator of the type of relationship violated. The valid range is a number between 1 and 2.
See Table 4-105 for a mapping between numbers and their enumerated type.
Associated Traps - bridgeDomainTimingRelationshipNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-118
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-105. Timing Reason Codes
Number
Value
Enumerated Type
Description
1
invalidForwardDelay-MaxAge
In violation of: 2 * (BridgeForwardDelay 1.0 sec) >= BridgeMaxAge
2
invalidHelloTime-MaxAge
In violation of: BridgeMaxAge >= 2 *
(BridgeHelloTime + 1.0 sec
toneAnnceFtpErrorStatus
The result of the completion of the tone announcement download. Set to a value between 3 and
17 if toneAnnceFtpStatus is doneWithError. Set to none if toneAnnceFtpStatus is doneSuccessfully. Set to userAbort if toneAnnceFtpStatus is canceled. The valid range is a number between 1
and 17.
See Table 4-106 for a mapping between numbers and their enumerated type.
Associated Traps - toneAnnceFtpStatusNotify
Table 4-106. Tone Announcement FTP Error Status Codes
Number
Value
Enumerated Type
Description
1
none
No error
2
userAbort
Canceled by user.
3
invalidIpAddress
The IP address is not valid.
4
invalidAccountName
The account name is not valid.
5
invalidAccountPassword
The account password is not valid.
6
invalidSourceFile
The source file is not valid.
7
invalidDstFileNameFormat
The destination file name format is not
valid when doing FTP.
8
dstFileNameAlreadyExist
The destination file name already exists.
9
tooManyAnnouncementNow
The announcement file has exceeded the
maximum number of announcements that
can be stored in the system.
10
diskSpaceUsageExceed
Exceeds disk space usage.
11
unableToOpenFile
Unable to open input file.
12
unableToMakeFtpConnection
Unable to establish FTP connection.
13
unableToWriteFile
Unable to write to the system.
14
unableToCompleteFtp
Unable to complete FTP.
15
unableToSpawnTask
Unable to spawn task to do the FTP.
16
unableToOpenScsiAnncDir
Unable to open SCSI announcement directory.
17
statFails
Cannot check the input file status.
toneAnnceFtpStatus
The current status of the tone announcement download. The initial start state from boot-up is
noActivity. During the FTP of the announcement, working is set. The final state is one of donePacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-119
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Successfully, doneWithError, or aborted. If the state is doneWithError then toneAnnceFtpErrorStatus will be set to reflect the type of error. The valid range is a number between 1 and 5.
See Table 4-107 for a mapping between numbers and their enumerated type.
Associated Traps - toneAnnceFtpStatusNotify
Table 4-107. Tone Announcement FTP Status Codes
Number
Value
Enumerated Type
Description
1
noActivity
No activity is the initial start state from boot-up.
2
working
Working is set while FTP’ing the announcement.
3
doneSuccessfully
Done successfully.
4
doneWithError
Done with error.
5
aborted
Canceled.
upgradeSwCopyStatus
The current status of the FTP software upgrade download. The valid range is a number between 1
and 5. If the final state is doneWithError then upgradeSwErrorStatus will be set to reflect the
type of error.
See Table 4-108 for a mapping between numbers and their enumerated type.
Associated Traps - softwareDownloadStatusNotify
Table 4-108. Upgrade Software Copy Status Codes
Number
Value
Enumerated Type
Description
1
noActivity
No activity is the initial start state from boot-up.
2
working
Working is set while FTP’ing the upgrade.
3
doneSuccessfully
The final state. It will stay in this state until re-boot or
starting an upgrade.
4
doneWithError
If the state is doneWithError then upgradeSwErrorStatus will be set to reflect the type of error.
5
aborted
Canceled.
upgradeSwErrorStatus
The result of the completion of the FTP software upgrade download. Set to a value 3-27 if
upgradeSwCopyStatus is doneWithError. Set to none if upgradeSwCopyStatus is doneSuccessfully. Set to userAbort if upgradeSwCopyStatus is aborted. The valid range is a number
between 1 and 29.
See Table 4-109 for a mapping between numbers and their enumerated type.
Associated Traps - softwareDownloadStatusNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-120
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-109. Upgrade Software Error Status Codes
Number
Value
Enumerated Type
Description
1
none
No errors occurred.
2
userAbort
User canceled
3
invalidIpAddress
The IP address is not valid.
4
invalidAccountName
The Account name is not valid.
5
invalidAccountPassword
The Account password is not valid.
6
invalidCdromFile
The CD-ROM file is not valid.
7
libraryCRCFail
The calculated CRC (cyclic redundancy check)
based on the current library is inconsistent with
the library CRC saved in the file package.lst.
8
unableToOpenLibraryFile
Unable to open library file.
9
unableToLoadLibraryModule
Unable to load library module.
10
unableToFindTaskSymbolName
Unable to find task symbol name.
11
failureInSpawningTask
Failure in spawning task.
12
failureInCreatingMsgQ
Unable to create vxWorks message queue.
13
failureInCopyingDataFiles
Failure in copying data files.
14
failureToRemoveNextTree
Failure to remove next tree.
15
unableToMakeNextTree
Unable to make next tree.
16
unableToOpenFile
Unable to open file.
17
unableToMakeFtpConnection
Unable to establish FTP connection.
18
unableToWriteFile
Unable to write file.
19
unableToCompleteFtp
Unable to complete FTP.
20
fileCRCFail
The CRC (cyclic redundancy check) on database
file fails.
21
unableToWritePackageList
Unable to write package list.
22
taskSuspendOrDead
Task suspended.
23
unabletoUpdateBackup
Unable to update backup.
24
cpuAbort
CPU canceled.
25
failureToTakeSemaphore
Failure to take semaphore.
26
failureToRemoveFallBackTree
Failure to remove fall back tree.
27
unableToMakeFallBackTree
Unable to make fall back tree.
28
swVersionDoesNotSupportThisHwSetup
The software being loaded does not support the
current hardware setup.
29
diskSpaceInsufficient
The disk does not have enough space to store
another software release for an upgrade or
downgrade.
v5CurrentDspOverSubscription
The current value of the oversubscription of the DSP resources for V5.2 voice calls after the configuration is applied. The calculation of the current oversubscription of the DSP resources in the
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-121
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
chassis is given as follows: The number of DSP resources left in the chassis after configuration
=[{(the number of DSP2D modules * 384) - the number of AAL2 trunks} - (the number of AAL2
trunks * the number of ISDN ports/trunk)](1 DSP resource is needed for ELCP connection per
IAD and 1 DSP resource is required for the D-channel per ISDN port on an IAD) oversubscription
= (the number of B-channels + the number of PSTN ports configured) / (the number of DSP
resources left in the chassis after configuration). The value is given in percentages, so that 25%
indicates that the resources are under subscribed and 800% indicates that the resources are oversubscribed 8 times. Please note that this calculation of the oversubscription is valid only if the
least used algorithm is chosen for the DSP resource allocation scheme.
Associated Traps - v5DspOverSubscriptionExceededNotify
v5DLCPathId
This index identifies the data link communication path. The valid range is a number between
0 and 5.
See Table 4-110 for a mapping between numbers and their enumerated type.
Associated Traps - v5InterfaceDLCreatedNotify, v5InterfaceDLCreateFailNotify,
v5InterfaceDLDeleteNotify, v5DLCantBeDeletedWhenActiveVariantIsISNotify
Table 4-110. V5 Data Link Communication Path ID Codes
Number
Value
Enumerated Type
Description
0
v5DLCPathProtection1
This data link communication path refers to
PROTECTION1 DL protocol.
1
v5DLCPathProtection2
This data link communication path refers to
PROTECTION2 DL protocol.
2
v5DLCPathControl
This data link communication path refers to CONTROL
DL protocol.
3
v5DLCPathLinkControl
This data link communication path refers to LINK
CONTROL DL protocol.
4
v5DLCPathBcc
This data link communication path refers to BCC DL
protocol.
5
v5DLCPathPstn
This data link communication path refers to PSTN DL
protocol.
v5E1LinkId
This is used as a logical link identifier to identify a link.
Associated Traps - v5InterfaceE1LinkAddedNotify, v5InterfaceE1LinkAddFailNotify,
v5InterfaceE1LinkDeleteNotify, v5InterfaceE1LinkModifyFailNotify,
v5InterfaceE1LinkBlockedNotify, v5InterfaceE1LinkUnBlockedNotify,
v5E1LinkOperOutOfServiceNotify, v5E1LinkOperInServiceNotify,
v5E1LinkCantBeTakenOOSWhenActiveVariantIsISNotify,
v5E1LinkCantBeDeletedWhenAdminISNotify, v5InterfaceE1LinkDeleteFailNotify
v5IntfId
This index identifies the v5 Interface configuration table.
Associated Traps - v5InterfaceCreatedNotify, v5InterfaceCreateFailNotify,
v5InterfaceModifiedNotify, v5InterfaceDeleteNotify, v5InterfaceModifyFailNotify,
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-122
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
v5InterfaceAdminOutOfServiceNotify, v5InterfaceAdminInServiceNotify,
v5InterfaceVariantAddedNotify, v5InterfaceVariantAddFailNotify, v5InterfaceVariantDeleteNotify,
v5InterfaceVariantOutOfServiceNotify, v5InterfaceVariantInServiceNotify,
v5InterfaceE1LinkAddedNotify, v5InterfaceE1LinkAddFailNotify, v5InterfaceE1LinkDeleteNotify,
v5InterfaceVariantSwitchoverNotify, v5InterfaceVariantSwitchoverFailed,
v5InterfaceProtectionSwitchoverNotify, v5InterfaceProtectionSwitchoverFailed,
v5InterfaceVariantModifyFailNotify, v5InterfaceE1LinkModifyFailNotify,
v5InterfaceE1LinkBlockedNotify, v5InterfaceE1LinkUnBlockedNotify,
v5InterfacePhysCChanCreatedNotify, v5InterfacePhysCChanCreateFailNotify,
v5InterfacePhysCChanDeleteNotify, v5InterfaceLogCChanCreatedNotify,
v5InterfaceLogCChanCreateFailNotify, v5InterfaceLogCChanDeleteNotify,
v5InterfaceDLCreatedNotify, v5InterfaceDLCreateFailNotify, v5InterfaceDLDeleteNotify,
v5InterfaceUserPortAddedNotify, v5InterfaceUserPortAddFailNotify,
v5InterfaceUserPortDeleteNotify, v5InterfaceOperOutOfServiceNotify,
v5InterfaceOperInServiceNotify, v5E1LinkOperOutOfServiceNotify,
v5E1LinkOperInServiceNotify, v5InterfaceUserPortBlockedNotify,
v5InterfaceUserPortUnBlockedNotify, v5UserPortCantBeDeleteWhenPortIsNotBlockedNotify,
v5InterfaceUserPortDeleteFailNotify, v5InterfaceUserPortBccFailNotify
v5InterfaceUserPortDeleteBeginNotify, v5InterfaceE1LinkDeleteFailNotify
v5IntfUserPortLEPortId
LE port number used to identify the ISDN and PSTN ports on a V5.2 interface.
Associated Traps - v5InterfaceUserPortAddedNotify, v5InterfaceUserPortAddFailNotify,
v5InterfaceUserPortDeleteNotify, v5InterfaceUserPortBlockedNotify,
v5InterfaceUserPortUnBlockedNotify, v5InterfaceUserPortUnblockDeactNotify,
v5InterfaceUserPortActivatedNotify, v5InterfaceUserPortActivationInitiatedNotify,
v5UserPortCantBeDeleteWhenPortIsNotBlockedNotify, v5InterfaceUserPortDeleteFailNotify,
v5InterfaceUserPortBccFailNotify, v5InterfaceUserPortDeleteBeginNotify
v5IntfUserPortType
The port type used to identify whether this port is ISDN or PSTN in a V5.2 interface. The valid
range is a number between 1 and 2.
See Table 4-111 for a mapping between numbers and their enumerated type.
Associated Traps - v5InterfaceUserPortAddedNotify, v5InterfaceUserPortAddFailNotify,
v5InterfaceUserPortDeleteNotify, v5InterfaceUserPortBlockedNotify,
v5InterfaceUserPortUnBlockedNotify, v5UserPortCantBeDeleteWhenPortIsNotBlockedNotify,
v5InterfaceUserPortDeleteFailNotify, v5InterfaceUserPortBccFailNotify,
v5InterfaceUserPortDeleteBeginNotify
Table 4-111. V5 Interface User Port Type Codes
Number
Value
Enumerated Type
Description
1
pstn
This port is PSTN.
2
isdn
This port is ISDN.
v5LesIntfIwfId
This index uniquely identifies the v5 LES Interface table.
Associated Traps - v5LesInterfaceOutOfServiceNotify, v5LesInterfaceInServiceNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-123
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
v5LesIntfTrunkId
This index uniquely identifies the v5 LES Interface table.
Associated Traps - v5LesInterfaceOutOfServiceNotify, v5LesInterfaceInServiceNotify
v5LogCChanCommCChanId
This index identifies the logical C-channel ID in a v5 interface.
Associated Traps - v5InterfaceProtectionSwitchoverNotify,
v5InterfaceProtectionSwitchoverFailed, v5InterfaceLogCChanCreatedNotify,
v5InterfaceLogCChanCreateFailNotify, v5InterfaceLogCChanDeleteNotify
v5PhysCChan
This index identifies the physical channel. Number value is interpreted as SSPPCCC, where SS is
the module slot, PP is the port number, and CCC is the channel number.
Associated Traps - v5InterfaceProtectionSwitchoverNotify,
v5InterfaceProtectionSwitchoverFailed, v5InterfacePhysCChanCreatedNotify,
v5InterfacePhysCChanCreateFailNotify, v5InterfacePhysCChanDeleteNotify,
v5PhysCChanCantBeDeletedWhenActiveVariantIsISNotify
v5TargetDspOverSubscription
The limit of the oversubscription of the DSP resources for the V5.2 voice calls. A trap message will
be sent if the oversubscription goes beyond the limit due to the configuration of the ISDN ports.
The value is given in percentages, so that 25% indicates that the resources will be under subscribed and 800% indicates that the resources can be over subscribed up to 8 times.
Associated Traps - v5DspOverSubscriptionExceededNotify
v5UserPortBCCFailureReasonCode
Identification of the cause for V5 BCC allocate or deallocation failure. The valid range is a number
between 1 and 17.
See the Table 4-112 for a mapping between numbers and their enumerated type.
Associated Traps - v5InterfaceUserPortBccFailNotify
Table 4-112. V5 User Port BCC Failure Reason Codes
Number
Value
Enumerated Type
Description
1
unspecified
A fault not covered by this table has been
found.
2
anFault
An internal IAD failure has been found.
3
anBlocked
An internal IAD blocking has been identified.
4
connPresentOnPstnPortWithDiffCid
The connection already exists on the selected
PSTN port to a different CID.
5
cidUsedOnDiffPstnPortOrIsdnChan
This CID is already used by a different port or
ISDN channel.
6
connPresentOnIsdnChanWithDiffCid
The connect already exists on an ISDN channel
with a different CID.
7
userPortUnavailable
The selected port is not available for service.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-124
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-112. V5 User Port BCC Failure Reason Codes (Continued)
Number
Value
Enumerated Type
Description
8
dataIncompatible
Deallocation failed due to the incompatible
data content.
9
cidIncompatible
Deallocation failed due to the data regarding
AAL2 chan, user port and channel CID does
not match any user port connection.
10
portDataIncomplatible
Deallocation failed due to the data regarding
the user port does not match the IAD user
port.
11
isdnChanDataIncompatible
Deallocation failed due to the data regarding
the user port chan does not match the IAD
user ports.
12
userPortNotProvisioned
The allocation failed due to the identified user
port has not been provisioned.
13
invalidCid
The CID does not match the one available for
use as bearer channels.
14
invalidAal2Trunk
The AAL2 trunk identification in LES interface
does not match any available trunks.
15
invalidIsdnChan
The chan ID does not match the ones available
on the selected ISDN user port.
16
cidBeingUsedAsDchan
The CID is being used as a D-channel or an
ELCP connection.
17
aal2TrunkUnavailable
AAL2 trunk is not available.
v5VariantId
This index identifies the variant table.
Associated Traps - v5InterfaceVariantAddedNotify, v5InterfaceVariantAddFailNotify,
v5InterfaceVariantDeleteNotify, v5InterfaceVariantOutOfServiceNotify,
v5InterfaceVariantInServiceNotify, v5InterfaceE1LinkAddedNotify,
v5InterfaceE1LinkAddFailNotify, v5InterfaceE1LinkDeleteNotify,
v5InterfaceVariantSwitchoverNotify, v5InterfaceVariantSwitchoverFailed,
v5InterfaceVariantModifyFailNotify, v5InterfaceE1LinkModifyFailNotify,
v5InterfaceE1LinkBlockedNotify, v5InterfaceE1LinkUnBlockedNotify,
v5InterfacePhysCChanCreatedNotify, v5InterfacePhysCChanCreateFailNotify,
v5InterfacePhysCChanDeleteNotify, v5InterfaceLogCChanCreatedNotify,
v5InterfaceLogCChanCreateFailNotify, v5InterfaceLogCChanDeleteNotify,
v5InterfaceDLCreatedNotify, v5InterfaceDLCreateFailNotify, v5InterfaceDLDeleteNotify,
v5InterfaceUserPortAddedNotify, v5InterfaceUserPortAddFailNotify,
v5InterfaceUserPortDeleteNotify, v5E1LinkOperOutOfServiceNotify,
v5E1LinkOperInServiceNotify, v5InterfaceUserPortBlockedNotify,
v5InterfaceUserPortUnBlockedNotify, v5InterfaceUserPortUnblockDeactNotify,
v5InterfaceUserPortActivatedNotify, v5InterfaceUserPortActivationInitiatedNotify,
v5ActiveVariantCantBeTakenOOSWhenIntfIsISNotify,
v5VariantCantBeDeletedWhenAdminISNotify,
v5E1LinkCantBeTakenOOSWhenActiveVariantIsISNotify,
v5E1LinkCantBeDeletedWhenAdminISNotify,
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-125
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
v5PhysCChanCantBeDeletedWhenActiveVariantIsISNotify,
v5DLCantBeDeletedWhenActiveVariantIsISNotify,
v5VariantCantBeDeletedWhenE1LinkIsISNotify,
v5UserPortCantBeDeleteWhenPortIsNotBlockedNotify, v5InterfaceUserPortDeleteFailNotify,
v5InterfaceUserPortBccFailNotify, v5InterfaceUserPortDeleteBeginNotify,
v5InterfaceE1LinkDeleteFailNotify
vbrAtmPvcVccIfA
The interface index for side A, the variable bit rate side, of a variable bit rate-to-ATM PVC VCC
connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the
module slot, PP is the port number, and CCC is the channel number.
Associated Traps - vbrAtmPvcVccReqFailNotify, vbrAtmPvcVccSetupNotify, vbrAtmPvcVccTearDownNotify, vbrAtmBkPvcVccReqFailNotify, vbrAtmBkPvcVccSetupNotify, vbrAtmBkPvcVccTearDownNotify
vbrAtmPvcVccIfB
The interface index for side B, the ATM side, of a variable bit rate-to-ATM PVC VCC connection.
Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - vbrAtmPvcVccReqFailNotify, vbrAtmPvcVccSetupNotify, vbrAtmPvcVccTearDownNotify, vbrAtmBkPvcVccReqFailNotify, vbrAtmBkPvcVccSetupNotify, vbrAtmBkPvcVccTearDownNotify
vbrAtmPvcVccVciB
The VCI value for side B, the ATM side, of a variable bit rate-to-ATM PVC VCC connection. The
valid range is a number between 0 and 65535.
Associated Traps - vbrAtmPvcVccReqFailNotify, vbrAtmPvcVccSetupNotify, vbrAtmPvcVccTearDownNotify, vbrAtmBkPvcVccReqFailNotify, vbrAtmBkPvcVccSetupNotify, vbrAtmBkPvcVccTearDownNotify
vbrAtmPvcVccVpiB
The VPI value for side B, the ATM side, of a variable bit rate-to-ATM PVC VCC connection. The
valid range is a number between 0 and 4095.
Associated Traps - vbrAtmPvcVccReqFailNotify, vbrAtmPvcVccSetupNotify, vbrAtmPvcVccTearDownNotify, vbrAtmBkPvcVccReqFailNotify, vbrAtmBkPvcVccSetupNotify, vbrAtmBkPvcVccTearDownNotify,
vbrAtmSpvcIfB
The interface index for side B, the ATM side, of a variable bit rate-to-ATM SPVC VCC connection.
Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - vbrAtmSpvcSetUpNotify, vbrAtmSpvcTearDownNotify
vbrAtmSpvcRemoteVbrPortAddr
Remote VBR port NSAP address implementing IWF, not meaningful if passive type of connection.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-126
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - vbrAtmSpvcConfiguredNotify, vbrAtmSpvcConfigFailNotify, vbrAtmSpvcDeletedNotify, vbrAtmSpvcModifiedNotify, vbrAtmSpvcModifyFailNotify, vbrAtmSpvcSetUpNotify,
vbrAtmSpvcTearDownNotify
vbrAtmSpvcVccIfA
The interface index for side A, the variable bit rate side, of a variable bit rate-to-ATM SPVC VCC
connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the
module slot, PP is the port number, and CCC is the channel number.
Associated Traps - vbrAtmSpvcVccSetUpNotify, vbrAtmSpvcVccTearDownNotify
vbrAtmSpvcVccIfB
The interface index for side B, the ATM side, of a variable bit rate-to-ATM SPVC VCC connection.
Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot,
PP is the port number, and CCC is the channel number.
Associated Traps - vbrAtmSpvcVccSetUpNotify, vbrAtmSpvcVccTearDownNotify
vbrAtmSpvcVccVciB
The VCI value for side B, the ATM side, of a variable bit rate-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 65535.
Associated Traps - vbrAtmSpvcVccSetUpNotify, vbrAtmSpvcVccTearDownNotify
vbrAtmSpvcVccVpiB
The VPI value for side B, the ATM side, of a variable bit rate-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 4095.
Associated Traps - vbrAtmSpvcVccSetUpNotify, vbrAtmSpvcVccTearDownNotify
vbrAtmSpvcVciB
The VCI value for side B, the ATM side, of a variable bit rate-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 65535.
Associated Traps - vbrAtmSpvcSetUpNotify, vbrAtmSpvcTearDownNotify
vbrAtmSpvcVpiB
The VPI value for side B, the ATM side, of a variable bit rate-to-ATM SPVC VCC connection. The
valid range is a number between 0 and 4095.
Associated Traps - vbrAtmSpvcSetUpNotify, vbrAtmSpvcTearDownNotify
vbrVbrPvcIfA
The interface index for side A of a variable bit rate-to-variable bit rate PVC connection. Number
value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the
port number, and CCC is the channel number.
Associated Traps - vbrVbrPvcReqFailNotify, vbrVbrPvcSetupNotify, vbrVbrPvcTearDownNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-127
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
vbrVbrPvcIfB
The interface index for side B of a variable bit rate-to-variable bit rate PVC connection. Number
value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the
port number, and CCC is the channel number.
Associated Traps - vbrVbrPvcReqFailNotify, vbrVbrPvcSetupNotify, vbrVbrPvcTearDownNotify
versionConfigurationReasonCode
Indicated status and results of version changing. The valid range is a number between 1 and 41.
See the Table 4-113 for a mapping between numbers and their enumerated type.
Associated Traps - versionConfigurationNotify
Table 4-113. Version Configuration Reason Codes
Number
Value
Enumerated Type
Description
1
upgrade-Start
The upgrade has started.
2
upgrade-Completed
The upgrade has been completed.
3
upgrade-Fail
The upgrade failed.
4
downgrade-Start
The downgrade has started.
5
downgrade-Completed
The downgrade has been completed.
6
downgrade-Fail
The downgrade failed.
7
upgrade-Fail-NoVersion
The upgrade failed, no version.
8
upgrade-Fail-VersionControlInProgress
The upgrade failed, version control is in
progress.
9
downgradeFail-NoVersion
The downgrade failed, no version.
10
downgrade-Fail-VersionControlInProgress
The downgrade failed, version control is in
progress
11
upgrade-InProgress
The upgrade is in progress.
12
downgrade-InProgress
The downgrade is in progress.
13
upgrade-sanityCheck-InProgress
The upgrade sanity check is in progress.
14
downgrade-sanityCheck-InProgress
The downgrade sanity check is in progress.
15
upgrade-sanityCheck-Completed
The upgrade sanity check is completed.
16
downgrade-sanityCheck-Completed
The downgrade sanity check is completed.
17
upgrade-Fail-SanityCheckFail
The upgrade failed due to sanity check failure.
18
downgrade-Fail-SanityCheckFail
The downgrade failed due to sanity check failure.
19
upgrade-Fail-BkCPUFailedToRespond
The upgrade failed since the backup CPU failed
to respond.
20
downgrade-Fail-BkCPUFailedToRespond
The downgrade failed since the backup CPU
failed to respond.
21
upgrade-Fail-UserAbort
The upgrade failed since the user canceled.
22
downgrade-Fail-UserAbort
The downgrade failed since the user canceled.
23
synch-Start
Synchronization has started.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-128
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Table 4-113. Version Configuration Reason Codes (Continued)
Number
Value
Enumerated Type
Description
24
synch-InProgress
Synchronization is in progress.
25
synch-Completed
Synchronization is completed.
26
synch-Fail
Synchronization failed.
27
synch-Fail-NoBkCPU
Synchronization failed since there is no backup
CPU.
28
synch-Fail-SameVersion
Synchronization failed due to the same version.
29
synch-Fail-FileCRCFailed
Synchronization failed due to file CRC failure.
30
synch-Fail-VersionControlInProgress
Synchronization failed since version control is
in progress.
31
synch-Fail-UserAbort
Synchronization failed since user canceled.
32
synch-Fail-SanityCheckFail
Synchronization failed due to sanity check failure.
33
synch-Fail-BkCPUFailedToRespond
Synchronization failed since the backup CPU
failed to respond.
34
synch-sanityCheck-InProgress
Synchronization sanity check is in progress.
35
synch-sanityCheck-Completed
Synchronization sanity check is completed.
36
failedToAbort
Failed to cancel.
37
firmware-Download-Complete
The firmware download, as a result of a software upgrade, on all present modules has been
completed.
38
transferConfig-Completed
Copying database files from the current software release to the fallback software release
has been completed.
39
transferConfig-Fail-NoFallback
Copying database files from the current software release to the fallback software release
has failed because no fallback release was
found.
40
transferConfig-Fail-Invalid-Key
The database operation authentication key
provided by the user to transfer database files
from the current software release to the fallback software release is not valid.
41
diskSpaceInsufficient
The disk does not have enough space to store
another software release for an upgrade or
downgrade.
viprIntfId
A unique ID for the Interface in a router instance.
Associated Traps - viprIpIntfTrap, viprSubChanTrap
viprRouteId
The unique ID to the routing table entry. The valid range is a number between 0 and 1024.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-129
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - viprStatRtTrap
viprRouterId
A unique ID for the Router instance in a router module.
Associated Traps - viprPingTrap, viprArpTrap, viprRoutingTrap, viprVpnTrap, viprIpIntfTrap, viprSubChanTrap, viprStatRtTrap
viprSlot
The slot number of the Route Server module (SS).
Associated Traps - viprPingTrap, viprArpTrap, viprRoutingTrap, viprVpnTrap, viprIpIntfTrap, viprSubChanTrap, viprStatRtTrap
viprSubChnlId
A unique ID for the subchannel in the interface.
Associated Traps - viprSubChanTrap
virtualIntfConfigIf
The interface index for side A of an ATM-to-ATM PVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number,
and CCC is the channel number.
Associated Traps - virtualIntfCreatedNotify, virtualIntfModifiedNotify, virtualIntfDeleteNotify,
virtualIntfModifyFailNotify
virtualIntfConfigVi
The VI value. The default value is 1 because 0 cannot be configured. The valid range is a number
between 0 and 1024.
Associated Traps - virtualIntfCreatedNotify, virtualIntfModifiedNotify, virtualIntfDeleteNotify,
virtualIntfModifyFailNotify
virtualUNIIfIndex
This is the first index to the Virtual UNI Interface table. The interface index will be of the form
SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel number.
Associated Traps - virtualUNIIntfCreatedNotify, virtualUNIIntfCreateFailNotify, virtualUNIIntfModifiedNotify, virtualUNIIntfDeleteNotify, virtualUNIIntfModifyFailNotify, virtualUNIIntfOutOfServiceNotify, virtualUNIIntfInServiceNotify
virtualUNIVUNIId
Virtual UNI number, second index to access the virtual UNI interface. The valid range is a number
between 1 and 255. The default value is 1.
Associated Traps - virtualUNIIntfCreatedNotify, virtualUNIIntfCreateFailNotify, virtualUNIIntfModifiedNotify, virtualUNIIntfDeleteNotify, virtualUNIIntfModifyFailNotify, virtualUNIIntfOutOfServiceNotify, virtualUNIIntfInServiceNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-130
255-700-506
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
vpnTrapStatus
Return codes for the Route Server module virtual private network (VPN) level operations. The
valid range is a number between 1 and 27.
See Table 4-114 for a mapping between numbers and their enumerated type.
Associated Traps - viprVpnTrap
Table 4-114. VPN Trap Status Codes
Number
Value
Enumerated Type
Description
1
vpnAddOk
The VPN creation is OK.
2
vpnInternalFailure
A memory corruption failure occurred.
3
vpnTooMany
Exceeded the maximum number of VPNs.
4
vpnBadSlot
Impossible slot number.
5
vpnBadId
The VPN ID must be between 1 and 6.
6
vpnBadState
The VPN state machine is confused.
7
vpnBadTimerVal
Bad timer value: state machine
8
vpnAlreadyExists
The VPN already exists.
9
vpnCantLocate
Cannot find referenced VPN.
10
vpnDelInProgress
Deletion in progress -must wait.
11
vpnLockedIdle
The VPN has been taken out of service.
12
vpnGeneralFailure
Reference the previous trap for a reason.
13
vpnNotAllowed
The operation is not allowed.
14
vpnShutting
Shutting down VPN -must wait.
15
vpnDisabled
Some VPN subsystem is not working.
16
vpnModifyOk
Modification of the operation is OK.
17
vpnConfigParamError
Parameter Error on this VPN
18
vpnPppNotSupported
Cannot Support PPP on this VPN
19
vpnRadiusNotSupported
Cannot Support Radius on this VPN
20
dhcpConfigProblem
The DHCP configuration parameters are incorrect or
DHCP is not supported.
21
exceededRoutes
The amount of routes requested exceeds the limit.
22
exceededARP
The amount of ARP entries exceeds the limit.
23
exceededIntfs
The amount of interfaces requested exceeds the limit.
24
noOSPFsupport
OSPF is not supported.
25
pppResourceProb
The PPP configuration parameters are incorrect or PPP
is not supported.
26
radiusResourceProb
The RADIUS configuration parameters are incorrect or
RADIUS is not supported.
27
notSupportedOnVPN
This feature is not supported on this VPN.
workingCardSlot
The physical working module slot location. The valid range is a number between 1 and 24.
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
255-700-506
Release 9.0.0
4-131
Chapter 4 MIB Objects
MIB Object Detailed Descriptions
Associated Traps - ntomProtectionSwitchoverNotify
PacketStar® PSAX Simple Network Mangement Protocol (SNMP) Reference Guide, Issue 1
Release 9.0.0
4-132
255-700-506
Copyright © 2003 Lucent Technologies
All rights reserved.
Printed in the USA.
Part No.: 203M0A9001TP1
Printed on paper with 100%
total recycled content.
Please recycle.
