Share via


Layer-2 Data Dictionary for Visio 2000 Enterprise

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

 

Jeff Yarnell
Microsoft Corporation

December 2000

Applies to:

     Microsoft Visio 2000 Enterprise Edition
     Layer-2 Database Schema Version 1.06

Summary: The Layer-2 Data Dictionary helps users and administrators use the layer-2 connectivity database with conventional relational database tools, such as query and report writing applications. (11 printed pages)

Contents

Introduction Data Dictionary    Devices    Interfaces    DevicePorts    SpanningTree    SpanningTreePort    Vlans    PortVlans    Media    LastDiscovery Layer-2 Database Schema Version 1.06

Introduction

The Microsoft®****Visio® AutoDiscovery database is designed to hold network configuration information, most of which is automatically obtained and stored in the database by the AutoDiscovery engine. The AutoDiscovery database is designed to store information about the network devices, as well as information about how they are connected.

While most information is stored in a Microsoft® SQL Server™/Microsoft® Data Engine (MSDE) database, information regarding layer-2 connectivity and protocols is stored in a separate Microsoft® Access database. The layer-2 database is named using the name of the main AutoDiscovery database. However, because it is a Jet database, it has an .MDB extension. For example, the default database created when AutoDiscovery and Layout.vst is used for the first time is ADL. Therefore, the main AutoDiscovery database file is named ADL.MDF, while the layer-2 database is named ADL.MDB.

The Visio AutoDiscovery engine manages the two databases slightly differently. The AutoDiscovery (layer-3) database is updated to reflect the current state of a discovered network device when network AutoDiscovery is performed. Therefore, as network device changes are discovered, their corresponding representation in the database is changed. Depending on the change, database records may be updated, added, or marked as deleted.

On the other hand, the layer-2 database uses an AutoDiscovery session identifier to mark current records. The LastDiscovery table contains information describing the ID (DiscoveryID) and time (DiscoveryDate) of the most recent AutoDiscovery session. When AutoDiscovery is performed, records are either added or updated so that their DiscoveryID value matches that of the current AutoDiscovery session. Therefore, layer-2 database records with a DiscoveryID value less than that of the most recent in the LastDiscovery table should be considered as historical, out-of-date information.

This data dictionary is intended to help users and administrators wishing to use the layer-2 Jet database with conventional relational database tools such as query and report writing applications.

**Caution  **

 

The Visio AutoDiscovery and Layout solution depends upon the integrity of the database schema and contents. End users should not insert records into or delete records from the database.

For more information on the AutoDiscovery (layer-3) database, see AutoDiscovery Data Dictionary for Visio 2000 Enterprise.

Data Dictionary

Devices

Table 1. Devices table

The Devices table contains information about devices discovered on the network by the AutoDiscovery engine.

Column Description Source
DeviceID Unique identifier for a record in the Devices table. Auto-increment, assigned by database engine
IPAddress IP Address that was used to discover this device. AutoDiscovery database
SysContact Name of individual managing the device (user configured data). MIB-II (RFC1213) sysContact
SysName Device name (user configured data). MIB-II (RFC1213) sysName
SysLocation Location of the device (user configured data). MIB-II (RFC1213) sysLocation
SysObjID Vendor specific device type identifier. MIB-II (RFC1213) sysObjectID
DiscoveryNote Text string containing possible device anomalies. AutoDiscovery engine
Dot1BaseBridgeAddress MAC Address that uniquely identifies this device. Bridge MIB (RFC1286) dot1dBaseBridgeAddress
DeviceType Text string determined by the ADL database — a Router, Switch, or Workstation. AutoDiscovery database
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID field in the LastDiscovery table. AutoDiscovery engine

Interfaces

Table 2. Interfaces table

The Interfaces table contains an entry for each physical interface on a given network device.

Column Description Source
InterfaceID Unique identifier for a record in the Interfaces table. Auto-increment, assigned by database engine
IfName Text string containing the name used by the device to represent the interface. IF MIB (RFC 1573) ifName
Description Text string describing the interface. MIB-II (RFC1213) ifDescr
IfIndex Device's unique identifier for the interface. MIB-II (RFC1213) ifIndex
MTU Maximum Transmission Unit for the interface. MIB-II (RFC1213) ifMTU
IPAddressID Index into IPAddressID field in the IPAddress table. AutoDiscovery engine
Speed Bits-per-second transmission value for the interface. MIB-II (RFC1213) ifSpeed
MACAddress Text string containing the MAC address for the interface. MIB-II (RFC1213) ifPhysAddress
DeviceID Refers to the device to which this interface belongs. Index into the DeviceID field in the Devices table. AutoDiscovery engine
MediumID Medium to which this interface belongs. Index into the MediumID in the Media table. AutoDiscovery engine
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID in the LastDiscovery table. AutoDiscovery engine
IsFrameRelay Deprecated. Not applicable

DevicePorts

Table 3. DevicePorts table

The DevicePorts table contains information that represents the ports of a network device, usually a bridge or switch. Ports typically correspond one-to-one with a physical interface.

Column Description Source
DevicePortID Unique identifier for a record in the DevicePorts table. Auto-increment, assigned by database engine
PortIndex Physical port number (usually combined with modules or switch index). From various (vendor specific) MIBs
PortModuleIndex Physical module number (combined with PortIndex, if non-zero). From various (vendor specific) MIBs
PortDuplex Indicates the transmission duplex of the port (for example, half or full). From various (vendor specific) MIBs
Dot1dBasePort Device's unique identifier for the port. Bridge MIB (RFC1286) dot1dBasePort
PortSwitchIndex Physical switch number (combined with PortIndex, if non-zero). From various (vendor specific) MIBs
InterfaceID Index into the InterfaceID field in the Interfaces table. AutoDiscovery engine
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID in the LastDiscovery table. AutoDiscovery engine

SpanningTree

Table 4. SpanningTree table

The SpanningTree table contains information regarding the state of a spanning tree relative to a particular device at the time the AutoDiscovery engine discovered the device.

Column Description Source
DeviceID Index into the DeviceID field in the Devices table. AutoDiscovery engine
VlanID Index into the VlanID field in the Vlans table. AutoDiscovery engine
RootPort Port with least cost to root (0 if root). Bridge MIB (RFC1286) dot1dStpRootPort
RootCost Path cost to root from this bridge (0 if root). MIB-II (RFC1286) dot1dStpRootCost
PortID Index into the DevicePortID field in the DevicePorts table. AutoDiscovery engine
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID in the LastDiscovery table. AutoDiscovery engine
DesignatedRootID Bridge ID of root (could be the same as BridgeID field). Bridge MIB (RFC1286) dot1dStpDesignatedRoot
BridgeID Bridge ID of this spanning tree. Bridge MIB (RFC1286) dot1dStpDesignatedRoot

SpanningTreePort

Table 5. SpanningTreePort table

The SpanningTreePort table contains information about the state of a spanning tree relative to a particular device port at the time the AutoDiscovery engine discovered the device.

Column Description Source
PathCost Contribution of this port to the path cost of paths towards the spanning tree root, which includes this port. Bridge MIB (RFC1286) dot1dStpPortPathCost
PortID Index into the DevicePortID field in the DevicePorts table. AutoDiscovery engine
DesignatedPort Port Identifier of the port on the Designated Bridge for this port's segment. Bridge MIB (RFC1286) dot1dStpPortDesignatedPort
DesignatedPortCost Path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs. Bridge MIB (RFC1286) dot1dStpPortDesignatedCost
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID in the LastDiscovery table. AutoDiscovery engine
PortState Port's current state as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame. If the bridge has detected a port that is malfunctioning, it will place that port into the broken (6) state. For ports that are disabled, this object will have a value of disabled (1). Bridge MIB (RFC1286) dot1dStpPortState
DesignatedRootID Unique Bridge Identifier of the Bridge, recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached. Bridge MIB (RFC1286) dot1dStpPortDesignatedRoot
DesignatedBridgeID Bridge Identifier of the bridge, which this port considers the Designated Bridge for this port's segment. Bridge MIB (RFC1286) dot1dStpPortDesignatedBridge

Vlans

Table 6. Vlans table

The Vlans table contains information about virtual LANs present on the network.

Column Description Source
VlanID Unique identifier for a record in the Vlans table. Auto-increment, assigned by database engine
DomainVlanID VLAN identifier. From various (vendor specific) MIBs
LocalVlanID Local VLAN identifier on this device. From various (vendor specific) MIBs
DomainName Name of the VLAN domain. From various (vendor specific) MIBs
VlanName Name of the VLAN. From various (vendor specific) MIBs
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID in the LastDiscovery table. AutoDiscovery engine

PortVlans

Table 7. PortVlans table

The PortVlans table contains fields that reference a row in the Vlans table and DevicePorts table, thereby enabling a many-to-many relationship between DevicePorts and Vlans.

Column Description Source
VlandID Index into the VlandID field in the Vlans table. AutoDiscovery engine
PortID Index into the DevicePortID field in the DevicePorts table. AutoDiscovery engine
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID in the LastDiscovery table. AutoDiscovery engine

Media

Table 8. Media table

The Media table contains entries representing the connection between two device ports.

Column Description Source
MediumID Unique identifier for a record in the Media table. Auto-increment, assigned by database engine
MediumType Type of media used to connect device ports. MIB-II (RFC1213) ifType (type values defined by Internet Assigned Numbers Authority – see http://www.iana.org)
DiscoveryID ID of last discovery run in which this record was updated. Index into the DiscoveryID in the LastDiscovery table. AutoDiscovery engine

LastDiscovery

Table 9. LastDiscovery table

The LastDiscovery table contains the date at which AutoDiscovery was run and the database version. The table is updated each time the AutoDiscovery engine is run.

Column Description Source
DiscoveryID Unique identifier for a record in the LastDiscovery table Auto-increment, assigned by database engine
DatabaseVersion Current version of this database AutoDiscovery engine
DiscoveryDate Date and time that this discovery run started AutoDiscovery engine

Layer-2 Database Schema Version 1.06

Click to view larger image.