cisco-stun-mib.mib object
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 2025 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 2025 can import MIB file cisco-stun-mib and use it to monitor vendor specific OID's.
cisco-stun-mib file content
Object view of cisco-stun-mib:
| Scalar Object |
| stunIPAddr |
.1.3.6.1.4.1.9.9.30.1.1.1 |
|
The configured IP address used for all serial tunnelling
in this router.
|
| stunGroupEntry |
.1.3.6.1.4.1.9.9.30.1.2.1.1 |
|
Status and parameter values for a group.
|
| stunPortEntry |
.1.3.6.1.4.1.9.9.30.1.3.1.1 |
|
Status and parameter values for a STUN port.
|
| stunRouteEntry |
.1.3.6.1.4.1.9.9.30.1.4.1.1 |
|
The information regarding a single STUN address.
|
| Tabular Object |
| stunGroupIndex |
.1.3.6.1.4.1.9.9.30.1.2.1.1.1 |
|
The configured STUN group number.
|
| stunProtocolType |
.1.3.6.1.4.1.9.9.30.1.2.1.1.2 |
|
The protocol type for this STUN group.
|
| stunPortGroupIndex |
.1.3.6.1.4.1.9.9.30.1.3.1.1.1 |
|
The group number to which the stun port
belongs. Frames will only be routed to other
ports (on this or another router) in the same
stun group. This group must match a stunGroupIndex
in the stunGroupTable.
|
| stunPortDefaultPeerType |
.1.3.6.1.4.1.9.9.30.1.3.1.1.2 |
|
The type of identification of the default partner
for unrecognized addresses. If there
is no default route then the stunRouteType
field of stunPortDefaultRemote is 'other'.
If ip then the value is in stunRouteIP; if serial or
serialDirect then the value is in stunRouteSerial.
|
| stunPortDefaultPeerIP |
.1.3.6.1.4.1.9.9.30.1.3.1.1.3 |
|
The ip address of the remote default STUN partner,
for unrecognized addresses.
0.0.0.0 is returned if the default route type is not ip.
|
| stunPortDefaultPeerSerialInterface |
.1.3.6.1.4.1.9.9.30.1.3.1.1.4 |
|
If stunRouteType is serial then this is the
serial interface index of the point-to-point
link to the remote partner;
if stunRouteType is serialDirect then the
partner is in the local STUN.
if stunRouteType is ip then this field is
0.
|
| stunRouteStationAddress |
.1.3.6.1.4.1.9.9.30.1.4.1.1.1 |
|
The poll address of the station. 256 indicates the ALL parameter
on the STUN ROUTE command, which is the route for all
unrecognized addresses.
|
| stunRouteType |
.1.3.6.1.4.1.9.9.30.1.4.1.1.2 |
|
The type of identification of the remote partner.
|
| stunRouteRemoteIP |
.1.3.6.1.4.1.9.9.30.1.4.1.1.3 |
|
The ip address of the remote STUN partner.
0.0.0.0 if partner type is not ip.
|
| stunRouteSerialInterface |
.1.3.6.1.4.1.9.9.30.1.4.1.1.4 |
|
The local interface index to the remote partner.
0 is returned if the partner type is not direct or frameRelay.
|
| stunRoutePriority |
.1.3.6.1.4.1.9.9.30.1.4.1.1.5 |
|
The priority with which this station's traffic will
be routed across the network.
|
| stunRoutePeerState |
.1.3.6.1.4.1.9.9.30.1.4.1.1.6 |
|
The state of the peer connection through the
STUN tunnel.
|
| stunRouteLocalAck |
.1.3.6.1.4.1.9.9.30.1.4.1.1.7 |
|
Indicates if the STUN connection is locally acknowledged.
TRUE-> STUN connection is locally acknowledged
FALSE-> STUN connection is not locally acknowledged
|
| stunRouteRxPackets |
.1.3.6.1.4.1.9.9.30.1.4.1.1.8 |
|
Count of frames received from the serial
interface with this station's address.
|
| stunRouteTxPackets |
.1.3.6.1.4.1.9.9.30.1.4.1.1.9 |
|
Count of frames transmitted at the serial
interface with this station's address.
|
| stunRouteRxBytes |
.1.3.6.1.4.1.9.9.30.1.4.1.1.10 |
|
Count of bytes received from the serial
interface with this station's address.
|
| stunRouteTxBytes |
.1.3.6.1.4.1.9.9.30.1.4.1.1.11 |
|
Count of bytes transmitted at the serial
interface with this station's address.
|
| Table |
| stunGroupTable |
.1.3.6.1.4.1.9.9.30.1.2.1 |
|
A table of entries representing STUN groups configured on the
router. Each STUN-enabled interface is assigned to a STUN
group, and packets can only travel between STUN-enabled
interfaces in the same group.
|
| stunPortTable |
.1.3.6.1.4.1.9.9.30.1.3.1 |
|
A list of STUN-enabled interfaces (ports).
|
| stunRouteTable |
.1.3.6.1.4.1.9.9.30.1.4.1 |
|
A table containing information about specific SDLC
addresses. There is one table entry for each SDLC
address configured by the STUN ROUTE command.
|
| Trap |
| stunPeerStateChangeNotification |
.1.3.6.1.4.1.9.9.30.2.0.1 |
|
This notification indicates that the state of a STUN route
has transitioned to active (connected or direct) or inactive
(dead or closed).
|
| Object Identifier |
| ciscoStunMIB |
.1.3.6.1.4.1.9.9.30 |
|
The MIB module for serial Tunneling.
Overview of STUN MIB
MIB description
The STUN MIB provides the configuration and operational information
on Cisco's serial tunnelling implementation. The following entities
are managed:
1) Global STUN information
2) STUN groups
3) STUN ports
4) STUN routes
The following example configuration shows how the STUN MIB returns
STUN information, from either CISCO A or CISCO B.
HOST == SDLC == Cisco A == IP Network == Cisco B == SDLC == SDLC
line line device
1) The STUN global entry identifies the IP address by which the
router is known to other STUN peers.
2) The STUN group table identifies the STUN group number and protocol
type that Cisco A and Cisco B use to route SDLC traffic over the
IP network. The table contains an entry for each STUN group
defined on the router.
3) The STUN port table identifies the serial interface to the SDLC
line for which the router is doing serial tunnelling. The MIB also
identifies the STUN group this interface is defined for, and
identifies the default routing for unrecognized SDLC addresses.
There is a port entry for each STUN-enabled interface on the router.
4) The STUN route table has an entry for each address defined for
routing within the STUN group, and an entry for the default routing
if the 'stun route all' command is configured. The route entry
includes identification of the STUN peer, priority, state, whether
local acknowledgment is enabled, and packet and byte counters.
|
| stunObjects |
.1.3.6.1.4.1.9.9.30.1 |
| stunGlobal |
.1.3.6.1.4.1.9.9.30.1.1 |
| stunGroups |
.1.3.6.1.4.1.9.9.30.1.2 |
| stunPorts |
.1.3.6.1.4.1.9.9.30.1.3 |
| stunRoutes |
.1.3.6.1.4.1.9.9.30.1.4 |
| stunNotificationPrefix |
.1.3.6.1.4.1.9.9.30.2 |
| stunNotifications |
.1.3.6.1.4.1.9.9.30.2.0 |
| stunMibConformance |
.1.3.6.1.4.1.9.9.30.3 |
| stunMibCompliances |
.1.3.6.1.4.1.9.9.30.3.1 |
| stunMibGroups |
.1.3.6.1.4.1.9.9.30.3.2 |
| Group |
| stunGlobalGroup |
.1.3.6.1.4.1.9.9.30.3.2.1 |
|
A collection of objects providing global STUN information.
|
| stunGroupGroup |
.1.3.6.1.4.1.9.9.30.3.2.2 |
|
A collection of objects providing information about
STUN groups .
|
| stunPortGroup |
.1.3.6.1.4.1.9.9.30.3.2.3 |
|
A collection of objects providing information about
STUN enabled interfaces.
|
| stunRouteGroup |
.1.3.6.1.4.1.9.9.30.3.2.4 |
|
A collection of objects providing information about
STUN defined routes.
|
