CISCO-PTOPO-EXTN-MIB.mib object view, vendor Cisco
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-PTOPO-EXTN-MIB and use it to monitor vendor specific OID's.
CISCO-PTOPO-EXTN-MIB file content
Object view of CISCO-PTOPO-EXTN-MIB:
| Scalar Object |
| cPtopoConnExtEntry |
.1.3.6.1.4.1.9.9.261.1.1.1 |
|
An entry which contains additional information about the
physical network connection contained in the ptopoConnEntry.
It helps specify whether a remote connection endpoint is
connected to the local port in the transmit direction, the
receive direction or both directions.
|
| cPtopoExtCdpEntry |
.1.3.6.1.4.1.9.9.261.1.2.1 |
|
This entry contains objects for configuring discovery of
physical topology information for a local port (identified
by the index of this entry) via CDP.
|
| Tabular Object |
| cPtopoConnExtLinkDirection |
.1.3.6.1.4.1.9.9.261.1.1.1.1 |
|
The remote connection endpoint (identified by
ptopoConnRemoteChassis and ptopoConnRemotePort of this row)
may be connected to the local port (identified by
ptopoConnLocalPort of this row) through either an
unidirectional or bidirectional link. This object is used
to indicate the directionality of the connection and in
the case of unidirectional links this object indicates
whether the remote connection endpoint is on the transmit
or the receive link.
For example, in case of optical interfaces where the
transmitted and received signals travel on 2 different
strands of fiber, it is possible that each fiber terminates
at a different device. For instance, the transmit and
receive fibers of the local port may be connected to
different optical amplifiers. This object could then be
used to indicate whether the remote device is on the
transmit or the receive fiber of the local port.
If the remote connection endpoint is connected to the
transmit fiber of the local port then
cPtopoConnExtLinkDirection is set to 'transmit'.
If the remote connection endpoint is connected to the
receive fiber of the local port then
cPtopoConnExtLinkDirection is set to 'receive'.
If both the transmit and receive fibers of the local port
terminate at the same remote connection endpoint then this
object is set to 'both'. Individual entries for 'transmit'
and 'receive' should not be created in this case. Note that
in the case of a port connected to a broadcast medium,
there can be multiple entries associated with the port,
with this object set to 'both'.
|
| cPtopoExtCdpLocalChassis |
.1.3.6.1.4.1.9.9.261.1.2.1.1 |
|
The entPhysicalIndex value used to identify the chassis
component associated with the local port for which
physical topology information is discovered via CDP.
|
| cPtopoExtCdpLocalPort |
.1.3.6.1.4.1.9.9.261.1.2.1.2 |
|
The entPhysicalIndex value used to identify the port
component associated with the local port for which
physical topology information is discovered via CDP.
|
| cPtopoExtCdpDiscoveryState |
.1.3.6.1.4.1.9.9.261.1.2.1.3 |
|
This object indicates the state of physical topology
discovery via CDP for the local port for which this row
exists.
The agent sets this object to 'cdpDisabled' if
cPtopoExtCdpProxyIf is set to zero and CDP has not been
configured to run on the local port, or if CDP has not
been configured to run on the proxy interface whose
ifIndex is given by the non-zero value in
cPtopoExtCdpProxyIf.
The enumeration 'interfaceDown' indicates that this
interface is down, when cPtopoExtCdpProxyIf is set to
zero, or the proxy interface is down, when
cPtopoExtCdpProxyIf is set to a non-zero value.
After this row has been activated, if CDP is running (on
this or the proxy interface) and no neighbors have been
discovered yet, the agent sets this object to 'waiting'.
The 'discovered' state indicates that one or more
neighbors have been discovered through CDP and the agent
has accordingly created ptopoConnEntry(s) in the
PTOPO-MIB.
|
| cPtopoExtCdpProxyIf |
.1.3.6.1.4.1.9.9.261.1.2.1.4 |
|
Physical topology information for the local port
(identified by cPtopoExtCdpLocalChassis and
cPtopoExtCdpLocalPort of this row) can be discovered
from CDP running on the local port, if it is CDP capable
or from CDP running on a proxy interface. In the case of
optical ports running wavelength division multiplexing,
the physical connector port on which the CDP packet is
transmitted is different from the logical interface
representing the wavelength on which CDP is running. In
such a case, physical topology for the 'external' optical
port can be learned from CDP running on one of the
wavelengths.
This object is set to zero if physical topology information
for the local port is discovered from CDP running on itself.
Otherwise, this object contains the ifIndex value of the CDP
capable interface which is being used as proxy to learn
physical topology information for the local port.
Usage of this object is possible only if the local port
is the 'External Port', as specified in the CDP protocol,
for the proxy interface.
This object may be modified when the associated
cPtopoExtCdpRowStatus object has a value of 'active'.
|
| cPtopoExtCdpRowStatus |
.1.3.6.1.4.1.9.9.261.1.2.1.5 |
|
This object is used to create and delete conceptual rows
in the cPtopoExtCdpTable.
Once this object has been set to 'active' it implies
that physical topology discovery via CDP has been enabled
for the local port for which this row exists.
This object cannot be set to 'active' when any rows that
were manually created for the local port exist in the
ptopoConnTable. After this object is set to 'active',
entries for this local port cannot be manually created in
the ptopoConnTable.
After the entry has been activated, this object cannot be
set to any value other than 'destroy'. The row status
never changes to 'notInService' after reaching the value
'active'.
|
| Table |
| cPtopoConnExtTable |
.1.3.6.1.4.1.9.9.261.1.1 |
|
This table augments the ptopoConnTable with information
about the direction of physical network connections.
|
| cPtopoExtCdpTable |
.1.3.6.1.4.1.9.9.261.1.2 |
|
This table contains a row for each local port (identified
by the index of this table) for which the agent populates
physical topology information (ptopoConnEntry) with neighbor
information dynamically learned from the Cisco Discovery
Protocol (CDP) running on this port or a proxy port.
|
| Object Identifier |
| ciscoPtopoExtnMIB |
.1.3.6.1.4.1.9.9.261 |
|
This MIB module contains extensions to the PTOPO-MIB that
provide support to distinguish between bidirectional and
unidirectional physical topology connections. It also
introduces a table that allows configuration of dynamic
learning of the physical topology through the Cisco
Discovery Protocol (CDP).
|
| ciscoPtopoExtnMIBObjects |
.1.3.6.1.4.1.9.9.261.1 |
| cPtopoExtnConformance |
.1.3.6.1.4.1.9.9.261.3 |
| cPtopoExtnCompliances |
.1.3.6.1.4.1.9.9.261.3.1 |
| cPtopoExtnGroups |
.1.3.6.1.4.1.9.9.261.3.2 |
| Group |
| cPtopoConnExtGroup |
.1.3.6.1.4.1.9.9.261.3.2.1 |
|
The collection of objects which augment the ptopoConnTable
in the PTOPO-MIB.
|
| cPtopoExtCdpGroup |
.1.3.6.1.4.1.9.9.261.3.2.2 |
|
The collection of objects which are required for
configuration of physical topology discovery via CDP.
|
| cPtopoExtCdpProxyGroup |
.1.3.6.1.4.1.9.9.261.3.2.3 |
|
The collection of objects which are used to configure
physical topology learning via CDP with support for use
of CDP running on a proxy interface.
|
