CISCO-VTP-MIB

         Added import of NOTIFICATION-GROUP
    
Source file
CISCO-VTP-MIB
Last revised
Identity
ciscoVtpMIB
Base OID
1.3.6.1.4.1.9.9.46
Imported Objects
CISCO-SMI ciscoMgmt
IF-MIB ifIndex InterfaceIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Gauge32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DateAndTime DisplayString RowStatus TestAndIncr TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the ciscosb MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-VTP-MIB' -M '/opt/observium/mibs/ciscosb:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-VTP-MIB::ciscoVtpMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-VTP-MIB' -M '/opt/observium/mibs/ciscosb:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-VTP-MIB::ciscoVtpMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (103)
.1.3.6.1.4.1.9.9.46
.1.3.6.1.4.1.9.9.46.1
.1.3.6.1.4.1.9.9.46.1.1
Enumeration
.1.3.6.1.4.1.9.9.46.1.1.1
Integer32
.1.3.6.1.4.1.9.9.46.1.1.2
.1.3.6.1.4.1.9.9.46.1.1.3
.1.3.6.1.4.1.9.9.46.1.2
.1.3.6.1.4.1.9.9.46.1.2.1
.1.3.6.1.4.1.9.9.46.1.2.1.1
.1.3.6.1.4.1.9.9.46.1.2.1.1.1
Enumeration
.1.3.6.1.4.1.9.9.46.1.2.1.1.10
Enumeration
.1.3.6.1.4.1.9.9.46.1.2.1.1.11
OctetString
.1.3.6.1.4.1.9.9.46.1.2.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.46.1.2.1.1.3
.1.3.6.1.4.1.9.9.46.1.2.1.1.4
.1.3.6.1.4.1.9.9.46.1.2.1.1.5
.1.3.6.1.4.1.9.9.46.1.2.1.1.6
.1.3.6.1.4.1.9.9.46.1.2.1.1.7
.1.3.6.1.4.1.9.9.46.1.2.1.1.8
.1.3.6.1.4.1.9.9.46.1.2.1.1.9
.1.3.6.1.4.1.9.9.46.1.3
.1.3.6.1.4.1.9.9.46.1.3.1
.1.3.6.1.4.1.9.9.46.1.3.1.1
.1.3.6.1.4.1.9.9.46.1.3.1.1.1
.1.3.6.1.4.1.9.9.46.1.3.1.1.10
.1.3.6.1.4.1.9.9.46.1.3.1.1.11
.1.3.6.1.4.1.9.9.46.1.3.1.1.12
Enumeration
.1.3.6.1.4.1.9.9.46.1.3.1.1.13
Integer32
.1.3.6.1.4.1.9.9.46.1.3.1.1.14
Integer32
.1.3.6.1.4.1.9.9.46.1.3.1.1.15
.1.3.6.1.4.1.9.9.46.1.3.1.1.16
Enumeration
.1.3.6.1.4.1.9.9.46.1.3.1.1.2
.1.3.6.1.4.1.9.9.46.1.3.1.1.3
OctetString
.1.3.6.1.4.1.9.9.46.1.3.1.1.4
Integer32
.1.3.6.1.4.1.9.9.46.1.3.1.1.5
OctetString
.1.3.6.1.4.1.9.9.46.1.3.1.1.6
Integer32
.1.3.6.1.4.1.9.9.46.1.3.1.1.7
Integer32
.1.3.6.1.4.1.9.9.46.1.3.1.1.8
Enumeration
.1.3.6.1.4.1.9.9.46.1.3.1.1.9
.1.3.6.1.4.1.9.9.46.1.4
.1.3.6.1.4.1.9.9.46.1.4.1
.1.3.6.1.4.1.9.9.46.1.4.1.1
Enumeration
.1.3.6.1.4.1.9.9.46.1.4.1.1.1
Enumeration
.1.3.6.1.4.1.9.9.46.1.4.1.1.2
.1.3.6.1.4.1.9.9.46.1.4.1.1.3
.1.3.6.1.4.1.9.9.46.1.4.1.1.4
.1.3.6.1.4.1.9.9.46.1.4.2
.1.3.6.1.4.1.9.9.46.1.4.2.1
.1.3.6.1.4.1.9.9.46.1.4.2.1.1
.1.3.6.1.4.1.9.9.46.1.4.2.1.10
.1.3.6.1.4.1.9.9.46.1.4.2.1.11
.1.3.6.1.4.1.9.9.46.1.4.2.1.12
.1.3.6.1.4.1.9.9.46.1.4.2.1.13
Enumeration
.1.3.6.1.4.1.9.9.46.1.4.2.1.14
Integer32
.1.3.6.1.4.1.9.9.46.1.4.2.1.15
Integer32
.1.3.6.1.4.1.9.9.46.1.4.2.1.16
.1.3.6.1.4.1.9.9.46.1.4.2.1.17
Enumeration
.1.3.6.1.4.1.9.9.46.1.4.2.1.2
.1.3.6.1.4.1.9.9.46.1.4.2.1.3
OctetString
.1.3.6.1.4.1.9.9.46.1.4.2.1.4
Integer32
.1.3.6.1.4.1.9.9.46.1.4.2.1.5
OctetString
.1.3.6.1.4.1.9.9.46.1.4.2.1.6
Integer32
.1.3.6.1.4.1.9.9.46.1.4.2.1.7
Integer32
.1.3.6.1.4.1.9.9.46.1.4.2.1.8
Enumeration
.1.3.6.1.4.1.9.9.46.1.4.2.1.9
.1.3.6.1.4.1.9.9.46.1.5
.1.3.6.1.4.1.9.9.46.1.5.1
.1.3.6.1.4.1.9.9.46.1.5.1.1
.1.3.6.1.4.1.9.9.46.1.5.1.1.1
.1.3.6.1.4.1.9.9.46.1.5.1.1.2
.1.3.6.1.4.1.9.9.46.1.5.1.1.3
.1.3.6.1.4.1.9.9.46.1.5.1.1.4
.1.3.6.1.4.1.9.9.46.1.5.1.1.5
.1.3.6.1.4.1.9.9.46.1.5.1.1.6
.1.3.6.1.4.1.9.9.46.1.5.1.1.7
.1.3.6.1.4.1.9.9.46.1.5.1.1.8
.1.3.6.1.4.1.9.9.46.1.6
.1.3.6.1.4.1.9.9.46.1.6.1
.1.3.6.1.4.1.9.9.46.1.6.1.1
.1.3.6.1.4.1.9.9.46.1.6.1.1.1
OctetString
.1.3.6.1.4.1.9.9.46.1.6.1.1.10
OctetString
.1.3.6.1.4.1.9.9.46.1.6.1.1.11
OctetString
.1.3.6.1.4.1.9.9.46.1.6.1.1.12
Enumeration
.1.3.6.1.4.1.9.9.46.1.6.1.1.13
Enumeration
.1.3.6.1.4.1.9.9.46.1.6.1.1.14
.1.3.6.1.4.1.9.9.46.1.6.1.1.15
Enumeration
.1.3.6.1.4.1.9.9.46.1.6.1.1.16
.1.3.6.1.4.1.9.9.46.1.6.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.46.1.6.1.1.3
OctetString
.1.3.6.1.4.1.9.9.46.1.6.1.1.4
.1.3.6.1.4.1.9.9.46.1.6.1.1.5
.1.3.6.1.4.1.9.9.46.1.6.1.1.6
.1.3.6.1.4.1.9.9.46.1.6.1.1.7
.1.3.6.1.4.1.9.9.46.1.6.1.1.8
.1.3.6.1.4.1.9.9.46.1.6.1.1.9
.1.3.6.1.4.1.9.9.46.1.6.2
.1.3.6.1.4.1.9.9.46.2
.1.3.6.1.4.1.9.9.46.2.0
.1.3.6.1.4.1.9.9.46.2.1
Integer32
.1.3.6.1.4.1.9.9.46.2.1.1
.1.3.6.1.4.1.9.9.46.3
.1.3.6.1.4.1.9.9.46.3.1
.1.3.6.1.4.1.9.9.46.3.2
Dependencies (7) 5 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIciscosb
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. CISCO-VTP-MIBciscosbselected
Type Definitions (4)
Integer32 range: 1..255
Integer32 range: 0..4095
Enumeration
ethernet(1)
fddi(2)
tokenRing(3)
fddiNet(4)
trNet(5)
deprecated(6)
Bits
vtpmanageable(0)
internal(1)
reserved(2)
rspan(3)
dynamicGvrp(4)
Conformance Groups (10)
A collection of objects providing basic status and control
of a VTP implementation.
.1.3.6.1.4.1.9.9.46.3.2.1
A collection of objects providing VTP statistics.
.1.3.6.1.4.1.9.9.46.3.2.4
A collection of objects providing information on trunk
ports.
.1.3.6.1.4.1.9.9.46.3.2.5
A collection of objects providing information on VLAN
pruning.
.1.3.6.1.4.1.9.9.46.3.2.7
A collection of object providing information on whether
VLAN pruning is enabled.
.1.3.6.1.4.1.9.9.46.3.2.10
Additional functionality added to the
vlanTrunkPortTable.
.1.3.6.1.4.1.9.9.46.3.2.11
The object required to indicate the version of VTP in
use by a management domain.
.1.3.6.1.4.1.9.9.46.3.2.12
A collection of objects for monitoring VLAN information.
.1.3.6.1.4.1.9.9.46.3.2.13
A collection of objects for editing VLAN information in VTP
Servers.
.1.3.6.1.4.1.9.9.46.3.2.14
Additional functionality added to the
vlanTrunkPortTable.
.1.3.6.1.4.1.9.9.46.3.2.15
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.46.3.1.1
The compliance statement for VTP implementations.
Required groups
mandatory vtpBasicGroup
mandatory vtpVlanInfoGroup
mandatory vtpStatsGroup
mandatory vtpTrunkPortGroup
optional vtpVlanInfoEditGroup This group must be implemented by VTP Servers.
VTP Clients need not implement these objects, and
must not allow VLANs to be created, modified, or
destroyed using these objects.
Object refinements
ObjectAccessSyntaxDescription
managementDomainRowStatus readonly
active(1)
Write access is not required, and only one
of the six enumerated values for the
RowStatus textual convention need be
supported, specifically: active(1).
vlanTrunkPortRowStatus readonly
active(1)
Write access is not required, and only one
of the six enumerated values for the
RowStatus textual convention need be
supported, specifically: active(1).
vlanTrunkPortManagementDomain readonly
Write access is not required.
vlanTrunkPortEncapsulationType readonly
Write access is not required.
vlanTrunkPortNativeVlan readonly
Write access is not required.
Notifications / Traps (7)
NameOIDDescription
.1.3.6.1.4.1.9.9.46.2.0.1
A configuration revision number error notification
signifies that a device has incremented its
vtpConfigRevNumberErrors counter.

Generation of this notification is suppressed if the
vtpNotificationsEnabled has the value 'false'.

The device must throttle the generation of consecutive
vtpConfigRevNumberError notifications so that there is at
least a five-second gap between notification of this type.
When notification are throttled, they are dropped, not
queued for sending at a future time. (Note that
'generating' a notification means sending to all configured
recipients.)
.1.3.6.1.4.1.9.9.46.2.0.2
A configuration digest error notification signifies that a
device has incremented its vtpConfigDigestErrors counter.

Generation of this notification is suppressed if the
vtpNotificationsEnabled has the value 'false'.

The device must throttle the generation of consecutive
vtpConfigDigestError notifications so that there is at least
a five-second gap between notification of this type. When
notification are throttled, they are dropped, not queued for
sending at a future time. (Note that 'generating' a
notification means sending to all configured recipients.)
.1.3.6.1.4.1.9.9.46.2.0.3
A VTP Server disabled notification is generated when the
local system is no longer able to function as a VTP Server
because the number of defined VLANs is greater than
vtpMaxVlanStorage.

Generation of this notification is suppressed if the
vtpNotificationsEnabled has the value 'false'.
.1.3.6.1.4.1.9.9.46.2.0.4
A VTP MTU tooBig notification is generated when a VLAN's
MTU size is larger than can be supported either:

- by one or more of its trunk ports:
the included vtpVlanState has the value
'mtuTooBigForTrunk' and the included
vlanTrunkPortManagementDomain is for the first (or only)
trunk port,
or

- by the device itself:
vtpVlanState has the value 'mtuTooBigForDevice' and any
instance of vlanTrunkPortManagementDomain is included.

Devices which have no trunk ports do not send vtpMtuTooBig
notifications.

Generation of this notification is suppressed if the
vtpNotificationsEnabled has the value 'false'.
.1.3.6.1.4.1.9.9.46.2.0.5
A VTP ring number configuration conflict notification is
generated if, and only at the time when, a device learns of
a conflict between:

a) the ring number (vtpVlanPortLocalSegment) being used on a
token ring segment attached to the port identified by
ifIndex, and

b) the VTP-obtained ring number (vtpVlanRingNumber) for the
VLAN identified by vtpVlanIndex.

When such a conflict occurs, the bridge port is put into an
administrative down position until the conflict is resolved
through local/network management intervention.

This notification is only applicable to VLANs of type
'tokenRing'.
.1.3.6.1.4.1.9.9.46.2.0.6
A VTP version one device detected notification is
generated by a device when:

a) a management domain has been put into version 2 mode
(as accessed by managementDomainVersionInUse).
b) 15 minutes has passed since a).
c) a version 1 PDU is detected on a trunk on the device
that is in that management domain which has a lower
revision number than the current configuration.
.1.3.6.1.4.1.9.9.46.2.0.7
A vlanTrunkPortDynamicStatusChange notification is
generated by a device when the value of
vlanTrunkPortDynamicStatus object has been changed.