CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB.mib object view, vendor Stratacom
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB and use it to monitor vendor specific OID's.
CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB file content
Object view of CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB:
| Scalar Object |
| persistentXgcpEventsEntry |
.1.3.6.1.4.1.351.150.18.1.1.1.1 |
|
An entry in the persistentXgcpEventsTable. Each
entry consists of persistentXgcpEventNum - Index
to the persistentXgcpEventsTable.
persistentXgcpEventName - Name of the xGCP
event that needs persistent notification
to the call agent for example 't/hd'.
persistentXgcpEventRowStatus -This indicates
whether an xGCP event is added in this entry
or not.
This table is not created implicitly. The user
can add xGCP event or delete an xGCP event.
|
| Tabular Object |
| persistentXgcpEventNum |
.1.3.6.1.4.1.351.150.18.1.1.1.1.1 |
|
This object is a index to persistentXgcpEventsTable.
|
| persistentXgcpEventName |
.1.3.6.1.4.1.351.150.18.1.1.1.1.2 |
|
This object holds the name of the event
for example 't/hd' or 't/hu'.
|
| persistentXgcpEventRowStatus |
.1.3.6.1.4.1.351.150.18.1.1.1.1.3 |
|
This object allows to add or delete an entry.
Modifying an entry is not allowed.
An entry may be created using the 'createAndGo' option.
When the row is successfully created, the RowStatus would
be set to 'active' by the agent. An entry may be deleted
by setting the RowStatus to 'destroy'. Other options
such as `CreateAndWait', 'notInService', 'notReady' will
not be used.
For creating an entry the persistentXgcpEventNum and
persistentXgcpEventName must be provided.
This object tells call control whether or not a particular
xGCP event is added or not, based on this the call control
module will decide whether or not to notify (NTFY) call
agent when a particular xGCP event is received,
without waiting for CA to request for that event.
|
| Table |
| persistentXgcpEventsTable |
.1.3.6.1.4.1.351.150.18.1.1.1 |
|
The persistentXgcpEventsTable contains
configuration information about xGCP events
which involve a persistent notification request.
|
| Object Identifier |
| ciscoWanPersistentXgcpEventsMIB |
.1.3.6.1.4.1.351.150.18 |
|
The MIB module for managing CA(Call Agent) events.
|
| ciscoWanPersistentXgcpEventsMIBObjects |
.1.3.6.1.4.1.351.150.18.1 |
| persistentXgcpEvents |
.1.3.6.1.4.1.351.150.18.1.1 |
| persistentXgcpEventsMIBConformance |
.1.3.6.1.4.1.351.150.18.2 |
| persistentXgcpEventsMIBCompliances |
.1.3.6.1.4.1.351.150.18.2.1 |
| persistentXgcpEventsMIBGroups |
.1.3.6.1.4.1.351.150.18.2.2 |
| Group |
| persistentXgcpEventsMIBGroup |
.1.3.6.1.4.1.351.150.18.2.2.1 |
|
This group contains objects related to
configuration of persistent xGCP events.
|
