This documentation is archived and is not being maintained.

What's New in AutoDiscovery and Layout Automation for Microsoft Visio 2002

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.
 

Microsoft Corporation

April 2002

Applies to:
   Microsoft Visio Professional 2002
   Microsoft Visio Enterprise Network Tools 2002
   Microsoft Visio Enterprise 2000

Summary: This article describes the new objects, properties, and methods available in the Microsoft Network Object Model (6 printed pages).

Contents

Introduction
New Objects
New Properties
New Methods

Introduction

The Microsoft® Network Object Model (NOM) is a set of objects used to model data networks. It allows you to create sophisticated network models for applications, including asset management, reporting, and more. The NOM objects and interfaces serve as an object-oriented interface to a relational database, allowing the network models to be saved and retrieved.

Expand your use of NOM with more than 40 new objects, methods, and properties. These new features include representations of spanning trees, logical disks, shared resources, and more. The following tables describe the new objects, methods, and properties.

New Objects

The following new objects have been added to the Network Object Model.

Table 1. New objects

New objectPropertiesDescription
LogicalDisks collectionN/AA collection of VNOMLogicalDisk objects that are associated with a VNOMNetworkElement object and represent the disks associated with a device.
Services collectionN/AA collection of VNOMService objects that represents the services provided by a VNOMNetworkElement, such as Dynamic Host Configuration Protocol (DHCP) or time.
SharedResources collectionN/AA collection of VNOMSharedResource objects that represent the shared resources associated with a VNOMNetworkElement, such as shared drives or printers.
SpanningTreePorts collectionN/AA collection of VNOMSpanningTreePort objects that represent the many-to-many relationship between VNOMSpanningTree and VNOMNetworkPort objects.
SpanningTrees collectionN/AA collection of VNOMSpanningTree objects that represent the spanning trees associated with a VNOMVlan object.
VlanPorts collectionN/AA collection of VNOMVlanPort objects that represent the many-to-many relationships between VNOMVlan and VNOMNetworkPort objects.
VNOMLogicalDisk objectRemoveable

Size

Represents a logical disk installed on a device. A logical disk represents the defined and available partitions that are visible to the user interacting with the device.
VNOMNetworkMediumN/ARepresents a physical network segment on the enterprise network.
VNOMOperatingSystemOSType

PatchLevel

TotalVirtualMemory

Represents the concept of an operating system.
VNOMServiceN/ARepresents the concept of a service provided by a VNOMNetworkElement, such as Dynamic Host Configuration Protocol (DHCP) and time services.
VNOMSharedResourceN/ARepresents the concept of a shared resource on the enterprise network. Examples of such objects include shared printers (that are not SNMP-manageable) and shared drives on a network.
VNOMSpanningTreeBridgeID

DesignatedRootID

RootCost

RootPort

Represents the concept of a spanning tree on the enterprise network.
VNOMVlanDomain

DomainVlanID

LocalVlanID

Represents a virtual LAN (Vlan) on the enterprise network.
VNOMVlanPortN/ARepresents the relationship between network ports and Vlans.

New Properties

The following new properties have been added to the Network Object Model.

Table 2. New properties

New propertyObjectDescription
BridgeIDVNOMSpanningTreeRepresents the bridge ID of this spanning tree.
DesignatedBridgeIDVNOMSpanningTreePortRepresents the bridge identifier of the bridge, which this port considers as the designated bridge for this port's segment.
DesignatedPortVNOMSpanningTreePortRepresents the port identifier of the port on the designated bridge for this port's segment.
DesignatedPortCostVNOMSpanningTreePortRepresents the 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.
DesignatedRootIDVNOMSpanningTreeRepresents the bridge identifier of the root.
DiscoveryIDAllThe discovery iteration in which the device was found.
DomainVNOMVlanRepresents the name of the virtual LAN (Vlan) domain.
DomainVlanIDVNOMVlanRepresents the Vlan identifier on the domain.
Dot1dBaseBridgeAddressVNOMNetworkElementRepresents the media access control address that uniquely identifies this device.
DuplexVNOMNetworkPortRepresents the transmission duplex of the port (for example, half or full).
FileSystemVNOMLogicalDiskRepresents the file system of logical disk, such as NTFS.
FirmwareVersionVNOMCardRepresents the version of the card's firmware.
LocalVlanIDVNOMVlanRepresents the virtual LAN (Vlan) identifier on the associated device.
OSTypeVNOMOperatingSystemRepresents the type of the operating system.
PatchLevelVNOMOperatingSystemRepresents the current patch level of the operating system.
PathCostVNOMSpanningTreePortRepresents the assigned cost associated with this link in the network.
PortSwitchIndexVNOMCardRepresents the physical switch number of the card.
RemoveableVNOMLogicalDiskRepresents a flag indicating if the logical disk is removable.
RootCostVNOMSpanningTreeRepresents the path cost to root from this bridge (0 if root).
RootPortVNOMSpanningTreeRepresents the port with least cost to root (0 if root).
SizeVNOMLogicalDiskRepresents the size in bytes of the logical disk.
SoftwareVersionVNOMCardRepresents the version of the Card's software.
StateVNOMSpanningTreePortRepresents the 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).
Title2AllProvides an alternate title when called on VnomPhysicalInterface. This property is used in Layer 2 code.

New Methods

The following new methods have been added to the Network Object Model.

Table 3. New methods

New methodsObjectDescription
AddSelectLessThanOrEqualRetrieveCriteriaAdds a search criteria with the less-than operator.
GetInterfaceByIndexVNOMNetworkElement

VNOMPhysicalInterface

Returns the VNOMPhysicalInterface object with the index associated with this NetworkElement.
GetInterfacesonSubNetworkByOIDVNOMNetworkElement

VNOMNetworkInterface

VNOMNetworkInterfaceCollection

VNOMSubNetwork

Takes the OID of a sub-network and returns a VNOMNetworkInterfaceCollection object containing the NetworkInterfaces on that sub-network.
GetTotalElementsByClassVNOMEnterpriseReturns the number of elements of the specified VNOMDeviceClass in the database.
GetTotalInterfacesByClassVNOMEnterpriseReturns the number of interfaces on elements of the VNOMDeviceClass in the database.
GetTotalObjectsByTypeVNOMEnterpriseReturns the number of objects of the VNOMDeviceType in the database.
Show: