CISCO-VTP-MIB Table View

The table containing information on the management domains
in which the local system is participating.  Devices which
support only one management domain will support just one row
in this table, and will not let it be deleted nor let other
rows be created.  Devices which support multiple management
domains will allow rows to be created and deleted, but will
not allow the last row to be deleted. If the device does 
not support VTP, the table is read-only.

This table contains information on the VLANs which
currently exist.

A vtpInternalVlanTable entry contains
information on an existing internal
VLAN. It is internally created by the
device for a specific application program 
and hence owned by the application.  
It cannot be modified or deleted by (local 
or network) management.

This table provides the means to control the editing of the
VLANs for a particular management domain.  Each and every
entry in this table augments its corresponding entry in the
managementDomainTable; thus, an entry in this table is
created/deleted only as a by-product of creating/deleting an
entry in the managementDomainTable.

The table which contains the information in the Edit
Buffers, one Edit Buffer per management domain.  The
information for a particular management domain is
initialized, by a 'copy' operation, to be the current global
VLAN information for that management domain.  After
initialization, editing can be performed to add VLANs,
delete VLANs, or modify their global parameters.  The
information as modified through editing is local to this
Edit Buffer.  An apply operation using the
vtpVlanEditOperation object is necessary to instanciate the
modified information as the new global VLAN information for
that management domain.
          
To use the Edit Buffer, a manager acts as follows:
          
1. ensures the Edit Buffer for a management domain is empty,
i.e., there are no rows in this table for this management
domain.
          
2. issues a SNMP set operation which sets
vtpVlanEditOperation to 'copy', and vtpVlanEditBufferOwner
to its own identifier (e.g., its own IP address).
          
3. if this set operation is successful, proceeds to edit the
information in the vtpVlanEditTable.
          
4. if and when the edited information is to be instantiated,
issues a SNMP set operation which sets vtpVlanEditOperation
to 'apply'.
          
5. issues retrieval requests to obtain the value of
vtpVlanApplyStatus, until the result of the apply is
determined.
          
6. releases the Edit Buffer by issuing a SNMP set operation
which sets vtpVlanEditOperation to 'release'.
          
Note that the information contained in this table is not
saved across agent reboots.

Ths table contains the VLAN local shutdown
information within management domain.

A table of VTP statistics.

The table containing information on the local system's VLAN
trunk ports.

This table contains information related to the discovery
of the VTP members in the designated management
domain. This table is not instantiated when 
managementDomainVersionInUse is version1(1), version2(3)
or none(3).

The table containing information of discovered VTP members
in the management domain in which the local system is
participating. This table is not instantiated when 
managementDomainVersionInUse is version1(1), version2(2) or
none(3).

This table contains information of the VTP
databases. It is not instantiated when
managementDomainVersionInUse is version1(1), 
version2(3) or none(3).

The table contains the authentication information of VTP
in which the local system participates.
          
The security mechanism of VTP relies on a secret key
that is used to alter the MD5 digest of the packets
transmitted on the wire.  The secret value is
created from a password that may be saved in plain text
in the configuration or hidden from the configuration.
          
The device creating or modifying the VTP configuration
signs it using the MD5 digest generated from the secret
key before advertising it. Other devices in the domain
receive this configuration use the same secret key
to accept it if correctly signed or drop it otherwise.
          
The user has the option to hide the password from the
configuration. Once the password is hidden, the secret
key generated from the password is shown in the 
configuration instead, and there is no other way to 
show the password in plain text again but clearing 
it or resetting it. 
          
In an un-trusted area, the password on a device can 
be configured without being unveiled. After that,
it has to be provided again by setting the same 
value to vtpDatabaseTakeOverPassword if the user 
wants to take over the whole VTP management domain
of the database type.
          
When managementDomainVersionInUse is version3(4), the 
authentication mechanism is common to all VTP
database type.