Sometimes AutoDiscovery assigns the wrong shape to a device. How does AutoDiscovery decide which shape to use?
AutoDiscovery relies primarily upon the SNMP sysObjectID (see RFC 1213) value retrieved during the discovery process to determine a device’s class or type, matching a device’s sysObjectID to an internal list of published sysObjectIDs. If a match is found, AutoDiscovery assigns the device class associated with that sysObjectID. If an unknown sysObjectID is returned, AutoDiscovery attempts to discern the device class by examining the SNMP sysDescription value for words like hub, router, switch, server, and so on. AutoDiscovery also queries to see if other standard Management Information Bases (MIB) reside on the device. For example, the presence of a Frame Relay (RFC 1513) MIB suggests the device is a router, whereas the presence of a Bridge (RFC 1493) MIB indicates the device is a bridge or switch. A standard SNMP MIB exists for hosts (RFC 1514) as well. AutoDiscovery maps a device to a Visio Network Equipment (VNE) shape if the VNE library is installed on your system prior to running A
Related Questions
- Sometimes AutoDiscovery assigns the wrong shape to a device. How does AutoDiscovery decide which shape to use?
- I have a Brother MFC device and when I scan multiple pages, Paper Valet™ only shows the last page. Whats wrong?
- When syncing a Palm PDA device, it says the port is used by another application. Whats wrong?
- When syncing a Palm PDA device, it says the port is used by another application. Whats wrong?
- The device shows connected, but I am not able to use Internet. What is wrong?
- The device shows connected, but I am not able to use Internet. What is wrong?
