| ciscoatmSigSSCOPConEvents |
.1.3.6.1.4.1.9.10.23.1.1.1.5 |
|
SSCOP Connection Events Counter. This
counter counts the sum of the following errors:
1) SSCOP Connection Disconnect Counter
The abnormal occurrence of this event is
characterized by the expiry of Timer_NO_RESPONSE.
(This event is communicated to the layer management
with MAA-ERROR code P. See ITU-T Q.2110 [13].)
2) SSCOP Connection Initiation Failure
This condition indicates the inability to establish
an SSCOP connection. This event occurs whenever the
number of expiries of the connection control timer
(Timer_CC) exceeds the MaxCC or upon receipt of a
connection reject message BGREJ PDU. (This event is
communicated to layer management with MAA-ERROR
code O. See ITU-T Q.2110.)
3) SSCOP Connection Re-Establ/Resynch
This event occurs upon receipt of a BGN PDU or RESYNC
PDU.
|
| ciscoatmSigSSCOPErrdPdus |
.1.3.6.1.4.1.9.10.23.1.1.1.6 |
|
SSCOP Errored PDUs Counter. This counter counts the
sum of the following errors:
1) Invalid PDUs.
These are defined in SSCOP and consist of PDUs
with incorrect length (MAA-ERROR code U),
undefined PDU type code or not 32-bit aligned.
2) PDUs that result in MAA error codes and are
discarded
See Errors A-M and Q-T defined in ITU-T Q.2110 [13].
|
| ciscoatmSigDetectSetupAttempts |
.1.3.6.1.4.1.9.10.23.1.1.1.7 |
|
Call Setup Attempts Counter. This counter counts
the number of call setup attempts(both successful
and unsuccessful) detected on this interface.
|
| ciscoatmSigEmitSetupAttempts |
.1.3.6.1.4.1.9.10.23.1.1.1.8 |
|
Call Setup Attempts Counter. This counter counts the
number of call setup attempts(both successful and
unsuccessful) transmitted on this interface.
|
| ciscoatmSigDetectUnavailRoutes |
.1.3.6.1.4.1.9.10.23.1.1.1.9 |
|
Number of Route Unavailability detected on this
interface. This counter is incremented when a RELEASE,
RELEASE COMPLETE (only when not preceded by a RELEASE
mesg for the same call), ADD PARTY REJECT, or STATUS
message that contains one of the following cause code
values is received (Note: These cause values apply to
both UNI3.0 and UNI3.1):
Cause Value Meaning
1 unallocated (unassigned) number
2 no route to specified transit network
3 no route to destination
88 incompatible destination
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigEmitUnavailRoutes |
.1.3.6.1.4.1.9.10.23.1.1.1.10 |
|
Number of Route Unavailability transmitted from this
interface. This counter is incremented when a RELEASE,
RELEASE COMPLETE (only when not preceded by a RELEASE
mesg for the same call), ADD PARTY REJECT, or STATUS
message that contains one of the following cause code
values is transmitted (Note: These cause values apply
to both UNI3.0 and UNI3.1):
Cause Value Meaning
1 unallocated (unassigned) number
2 no route to specified transit network
3 no route to destination
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigDetectUnavailResrcs |
.1.3.6.1.4.1.9.10.23.1.1.1.11 |
|
Number of Resource Unavailability detected on this
interfrace. This counter is incremented when a
RELEASE, RELEASE COMPLETE (only when not preceded by a
RELEASE mesg for the same call), ADD PARTY REJECT, or
STATUS message that contains one of the following cause
code values is received (Note: These cause values apply
to both UNI3.0 and UNI3.1 unless otherwise stated):
Cause Value Meaning
35 requested VPCI/VCI not available
37 user cell rate not available (UNI3.1
only)
38 network out of order
41 temporary failure
45 no VPCI/VCI available
47 resource unavailable, unspecified
49 Quality of Service unavailable
51 user cell rate not available (UNI3.0
only)
58 bearer capability not presently
available
63 Service or option not available,
unspecified
92 too many pending add party requests
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigEmitUnavailResrcs |
.1.3.6.1.4.1.9.10.23.1.1.1.12 |
|
Number of Resource Unavailability transmitted from
this interfrace. This counter is incremented when a
RELEASE, RELEASE COMPLETE (only when not preceded by a
RELEASE mesg for the same call), ADD PARTY REJECT, or
STATUS message that contains one of the following cause
code values is transmitted (Note: These cause values
apply to both UNI3.0 and UNI3.1 unless otherwise
stated):
Cause Value Meaning
35 requested VPCI/VCI not available
37 user cell rate not available (UNI3.1
only)
38 network out of order
41 temporary failure
45 no VPCI/VCI available
47 resource unavailable, unspecified
49 Quality of Service unavailable
51 user cell rate not available (UNI3.0
only)
58 bearer capability not presently
available
63 Service or option not available,
unspecified
92 too many pending add party requests
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigDetectCldPtyEvents |
.1.3.6.1.4.1.9.10.23.1.1.1.13 |
|
Number of Called Party Responsible For Unsuccessful
Call detected on this interface. This counter is
incremented when a RELEASE, RELEASE COMPLETE (only when
not preceded by a RELEASE mesg for the same call), ADD
PARTY REJECT, or STATUS message that contains one of
the following cause code values is received (Note:
These cause values apply to both UNI3.0 and UNI3.1):
Cause Value Meaning
17 user busy
18 no user responding
21 call rejected
22 number changed
23 user rejects all calls with calling
line id restriction (CLIR)
27 destination out of order
31 normal, unspecified
88 incompatible destination
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
Note: Cause Value #30 'response to STATUS ENQUIRY'
was not included in this memo since it did not apply
to a hard failure.
|
| ciscoatmSigEmitCldPtyEvents |
.1.3.6.1.4.1.9.10.23.1.1.1.14 |
|
Number of Called Party Responsible For Unsuccessful Call
transmitted from this interface. This counter is
incremented when a RELEASE, RELEASE COMPLETE (only
when not preceded by a RELEASE mesg for the same call),
ADD PARTY REJECT, or STATUS message that contains one
of the following cause code values is
transmitted (Note: These cause values apply to both
UNI3.0 and UNI3.1):
Cause Value Meaning
17 user busy
18 no user responding
21 call rejected
22 number changed
23 user rejects all calls with calling
line id restriction (CLIR)
27 destination out of order
31 normal, unspecified
88 incompatible destination
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
Note: Cause Value #30 'response to STATUS ENQUIRY'
was not included in this memo since it did not apply
to a hard failure.
|
| ciscoatmSigDetectMsgErrors |
.1.3.6.1.4.1.9.10.23.1.1.1.15 |
|
Number of Incorrect Messages detected on this
interface. The Incorrect Messages Counter reflects any
sort of incorrect information in a message. This
includes:
- RELEASE, RELEASE COMPLETE, ADD PARTY REJECT,
and STATUS messages transmitted, that contain any of
the Cause values listed below.
- Ignored messages. These messages are dropped
because the message was so damaged that it could
not be further processed. A list of dropped
messages is compiled below:
1. Message with invalid protocol discriminator
2. Message with errors in the call reference I.E.
- Bits 5-8 of the first octet not equal to
'0000'
- Bits 1-4 of the first octet indicating a
length other than 3 octets
- RELEASE COMPLETE message received with a
call reference that does not relate to a
call active or in progress
- SETUP message received with call reference
flag incorrectly set to 1
- SETUP message received with a call
reference for a call that is already
active or in progress.
3. Message too short
The following cause values are monitored by this
counter (Note: These cause values apply to both UNI3.0
and UNI3.1 unless otherwise stated):
Cause Value Meaning
10 VPCI/VCI unacceptable (UNI3.0 only)
36 VPCI/VCI assignment failure (UNI3.1 only)
81 invalid call reference value
82 identified channel does not exist
89 invalid endpoint reference
96 mandatory information element is missing
97 message type non-existent or not
implemented
99 information element non-existent or not
implemented
100 invalid information element contents
101 message not compatible with call state
104 incorrect message length
111 protocol error, unspecified
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigEmitMsgErrors |
.1.3.6.1.4.1.9.10.23.1.1.1.16 |
|
Number of Incorrect Messages detected on this
interface. The Incorrect Messages Counter reflects any
sort of incorrect information in a message. This
includes:
- RELEASE, RELEASE COMPLETE, ADD PARTY REJECT,
and STATUS messages transmitted or
received, that contain any of the Cause values
listed below.
- Ignored messages. These messages are dropped
because the message was so damaged that it could
not be further processed. A list of dropped
messages is compiled below:
1. Message with invalid protocol discriminator
2. Message with errors in the call reference I.E.
- Bits 5-8 of the first octet not equal to
'0000'
- Bits 1-4 of the first octet indicating a
length other than 3 octets
- RELEASE COMPLETE message received with a
call reference that does not relate to a
call active or in progress
- SETUP message received with call reference
flag incorrectly set to 1
- SETUP message received with a call
reference for a call that is already
active or in progress.
3. Message too short
The following cause values are monitored by this
counter (Note: These cause values apply to both UNI3.0
and UNI3.1 unless otherwise stated):
Cause Value Meaning
10 VPCI/VCI unacceptable (UNI3.0 only)
36 VPCI/VCI assignment failure (UNI3.1 only)
81 invalid call reference value
82 identified channel does not exist
89 invalid endpoint reference
96 mandatory information element is missing
97 message type non-existent or not
implemented
99 information element non-existent or not
implemented
100 invalid information element contents
101 message not compatible with call state
104 incorrect message length
111 protocol error, unspecified
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigDetectClgPtyEvents |
.1.3.6.1.4.1.9.10.23.1.1.1.17 |
|
Number of Calling Party Events detected on this
interface. This counter monitors error events that
occur due to the originating user doing something
wrong. This counter is incremented when a RELEASE,
RELEASE COMPLETE (only when not preceded by a RELEASE
mesg for the same call), ADD PARTY REJECT, or STATUS
message that contains one of the following cause code
values is received (Note: These cause values apply to
both UNI3.0 and UNI3.1):
Cause Value Meaning
28 invalid number format (address incomplete)
43 access information discarded
57 bearer capability not authorized
65 bearer capability not implemented
73 unsupported combination of traffic
parameters
78 AAL parameters cannot be supported (UNI3.1
only)
91 invalid transit network selection
93 AAL parameters cannot be supported (UNI3.0
only)
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigEmitClgPtyEvents |
.1.3.6.1.4.1.9.10.23.1.1.1.18 |
|
Number of Calling Party Events transmitted from this
interface. This counter monitors error events that
occur due to the originating user doing something
wrong. This counter is incremented when a RELEASE,
RELEASE COMPLETE (only when not preceded by a RELEASE
mesg for the same call), ADD PARTY REJECT, or STATUS
message that contains one of the following cause code
values is transmitted (Note: These cause values apply
to both UNI3.0 and UNI3.1):
Cause Value Meaning
28 invalid number format (address incomplete)
43 access information discarded
57 bearer capability not authorized
65 bearer capability not implemented
73 unsupported combination of traffic
parameters
78 AAL parameters cannot be supported (UNI3.1
only)
91 invalid transit network selection
93 AAL parameters cannot be supported (UNI3.0
only)
NOTE: For this counter, RELEASE COMPLETE
messages that are a reply to a previous RELEASE
message and contain the same cause value, are
redundant (for counting purposes) and should not
be counted.
|
| ciscoatmSigDetectTimerExpireds |
.1.3.6.1.4.1.9.10.23.1.1.1.19 |
|
Number of Timer Expiries detected on this interface.
The Timer Expiries Counter provides a count of network
timer expiries, and to some extent, host or switch
timer expiries. The conditions for incrementing this
counter are:
- Expiry of any network timer
- Receipt of a RELEASE or RELEASE COMPLETE
message with Cause #102, 'recovery on
timer expiry'.
NOTE: For this counter, RELEASE COMPLETE messages
that are a reply to a previous RELEASE message and
contain the same cause value, are redundant (for
counting purposes) and should not be counted.
|
| ciscoatmSigEmitTimerExpireds |
.1.3.6.1.4.1.9.10.23.1.1.1.20 |
|
Number of Timer Expiries transmitted from this
interface. The Timer Expiries Counter provides a count
of network timer expiries, and to some extent, host or
switch timer expiries. The conditions for incrementing
this counter are:
- Expiry of any network timer
- Receipt of a RELEASE or RELEASE COMPLETE
message with Cause #102, 'recovery on
timer expiry'.
NOTE: For this counter, RELEASE COMPLETE messages
that are a reply to a previous RELEASE message and
contain the same cause value, are redundant (for
counting purposes) and should not be counted.
|
| ciscoatmSigDetectRestarts |
.1.3.6.1.4.1.9.10.23.1.1.1.21 |
|
Number of Restart Activity errors detected on this
interface. The Restart Activity Counter provides a
count of host, switch, or network restart activity.
This counter is incremented when receiving a RESTART
message.
|
| ciscoatmSigEmitRestarts |
.1.3.6.1.4.1.9.10.23.1.1.1.22 |
|
Number of Restart Activity errors transmitted from
this interface. The Restart Activity Counter provides
a count of host, switch, or network restart activity.
This counter is incremented when transmitting a RESTART
message.
|
| ciscoatmSigInEstabls |
.1.3.6.1.4.1.9.10.23.1.1.1.23 |
|
Number of SVC VCCs established at this signalling
entity for incoming connections.
|
| ciscoatmSigOutEstabls |
.1.3.6.1.4.1.9.10.23.1.1.1.24 |
|
Number of SVC VCCs established at this signalling
entity for outgoing connections.
|
| ciscoatmSigSupportClgPtyNumDel |
.1.3.6.1.4.1.9.10.23.1.2.1.1 |
|
This object indicates whether the Calling Party Number
Information Element is transferred to the called party
address. The value of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmSigSupportClgPtySubAddr |
.1.3.6.1.4.1.9.10.23.1.2.1.2 |
|
This object indicates whether to accept and transfer
the Calling Party Subaddress Information Element from
the calling party to the called party. Calling party
subaddress information shall only be transferred to the
called party if calling party number delivery is
enabled (i.e., atmSigSupportClgPtyNumDel =
'enabled(1)'. The value of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmSigSupportCldPtySubAddr |
.1.3.6.1.4.1.9.10.23.1.2.1.3 |
|
This object indicates whether to accept, transfer, and
deliver the Called Party Subaddress Information Element
from the calling party to the called party. The value
of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmSigSupportHiLyrInfo |
.1.3.6.1.4.1.9.10.23.1.2.1.4 |
|
This object indicates whether to accept, transfer, and
deliver the Broadband High Layer Information Element
from the calling party to the called party. The value
of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmSigSupportLoLyrInfo |
.1.3.6.1.4.1.9.10.23.1.2.1.5 |
|
This object indicates whether to accept, transfer, and
deliver the Broadband Low Layer Information Element
from the calling party to the called party. The value
of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmSigSupportBlliRepeatInd |
.1.3.6.1.4.1.9.10.23.1.2.1.6 |
|
This object indicates whether to accept, transfer, and
deliver the Broadband Repeat Indicator with two or
three instances of the Broadband Low Layer Information
Element for low layer information selection from the
calling party to the called party. This object shall
only be transferred if atmSigSupportLoLyrInfo =
'enabled(1)'. The value of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmSigSupportAALInfo |
.1.3.6.1.4.1.9.10.23.1.2.1.7 |
|
This object indicates whether to accept, transfer, and
deliver the ATM Adaptation Layer Parameters Information
Element from the calling party to the called party.
The value of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmSigSupportUnknownIe |
.1.3.6.1.4.1.9.10.23.1.2.1.8 |
|
This object indicates whether to accept, transfer, and
deliver the unknown Information Element from the
calling party to the called party, when the IE instruction
field flag is set to zero.When the IE action flag is set to
one, the IE action indicator should be followed regardless
of this configuration.
The value of this object can be:
- enabled(1) This Information Element is transferred
to the called party
- disabled(2) This Information Element is NOT
transferred to the called party.
|
| ciscoatmInterfaceConfMaxSvpcVpi |
.1.3.6.1.4.1.9.10.23.1.3.1.16 |
|
The maximum VPI that the signalling stack on the ATM
interface is configured to support for allocation to
switched virtual path connections.
|
| ciscoatmInterfaceCurrentMaxSvpcVpi |
.1.3.6.1.4.1.9.10.23.1.3.1.17 |
|
The maximum VPI that the signalling stack on the ATM
interface may currently allocate to switched virtual
path connections. This value is the minimum of
ciscoatmInterfaceConfMaxSvpcVpi, and the
ciscoatmInterfaceConfMaxSvpcVpi of the interface's
UNI/NNI peer.
If the interface does not negotiate with its peer to
determine the maximum VPI that can be allocated to
SVPCs on the interface, then the value of this object
must equal ciscoatmInterfaceConfMaxSvpcVpi.
|
| ciscoatmInterfaceConfMaxSvccVpi |
.1.3.6.1.4.1.9.10.23.1.3.1.18 |
|
The maximum VPI that the signalling stack on the ATM
interface is configured to support for allocation to
switched virtual channel connections.
|
| ciscoatmInterfaceCurrentMaxSvccVpi |
.1.3.6.1.4.1.9.10.23.1.3.1.19 |
|
The maximum VPI that the signalling stack on the ATM
interface may currently allocate to switched virtual
channel connections. This value is the minimum of
ciscoatmInterfaceConfMaxSvccVpi, and the
ciscoatmInterfaceConfMaxSvccVpi of the interface's
UNI/NNI peer.
If the interface does not negotiate with its peer to
determine the maximum VPI that can be allocated to
SVCCs on the interface, then the value of this object
must equal ciscoatmInterfaceConfMaxSvccVpi.
|
| ciscoatmInterfaceConfMinSvccVci |
.1.3.6.1.4.1.9.10.23.1.3.1.20 |
|
The minimum VCI that the signalling stack on the ATM
interface is configured to support for allocation to
switched virtual channel connections.
|
| ciscoatmInterfaceCurrentMinSvccVci |
.1.3.6.1.4.1.9.10.23.1.3.1.21 |
|
The minimum VCI that the signalling stack on the ATM
interface may currently allocate to switched virtual
channel connections. This value is the maximum of
ciscoatmInterfaceConfMinSvccVci, and the
ciscoatmInterfaceConfMinSvccVci of the interface's
UNI/NNI peer.
If the interface does not negotiate with its peer to
determine the minimum VCI that can be allocated to
SVCCs on the interface, then the value of this object
must equal ciscoatmInterfaceConfMinSvccVci.
|
