MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 10 (ciscoExperiment). 23 (ciscoAtm2MIB). 1 (ciscoatm2MIBObjects). 1 (ciscoatmSigStatTable). 1 (ciscoatmSigStatEntry). 5 (ciscoatmSigSSCOPConEvents)
OID : 1.3.6.1.4.1.9.10.23.1.1.1.5
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoExperiment. ciscoAtm2MIB. ciscoatm2MIBObjects. ciscoatmSigStatTable. ciscoatmSigStatEntry. ciscoatmSigSSCOPConEvents
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.9.10.23.1.1.1.5
Module CISCO-ATM2-MIB (CISCO)
NomciscoatmSigSSCOPConEvents
Accesreadonly
Statuscurrent
DescriptionSSCOP 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.
SyntaxeCounter32 (SNMPv2-SMI)