To do this, Get Info on the affected device andĬheck the "Ignore Interface Errors" or "Ignore Interface The error reports are bogus, you can instruct Intermapper to ignore theĭiscards and/or errors.
As a workaround, if you've satisfied yourself that. If packets aren't being dropped, it's anotherĬlue that the values reported by SNMP are incorrect. Run a ping test through the device that's reporting the errors.ĭiscarded, you'll see a higher than normal packet rate of dropped packets. SNMP Console to see if the same errors are reported there. You can monitor these same variables with your Probes page to compute its error & discard figures. Monitors the ifInDiscards and ifInErrors MIB variables (and the corresponding ifOutxxxx variables) listed on the Network and Server To check out the particular MIB variables for the device. To test Intermapper's accuracy, use another SNMP console. #Does intermapper have any api capabilities upgrade
You can check with your vendor to see if there'sĪ firmware upgrade that addresses the problem. Telnetting in, using a web browser, etc.) to see if errors are being reported
Use the vendor's own network monitoring tool (by. Normal that the affected devices are operating normally, without problems, Manufacturers' own monitoring tools will report zero errors. It'sĬommon that when Intermapper reports errors (from its SNMP queries), the The most likely reason that Intermapper shows a high rate of discardsįrom a device is that the device is actually reporting these errors. Shows a message like this: Reason: Discards = 738: sc0 They are usually orange on the map, and the status window We frequently hear of devices that appear to have high levels of discardsĪnd/or errors. My switches are always orange and showing lots of errors (or discards). Send E-Mail to information about the type of device and the trouble you're having. Look for any messages related to that device. From the Help Menu's Diagnostics submenu choose Server Log, or from the Window menu's Logs submenu, choose Debug. If you still can't make the router work with Intermapper, try the following: IP addresses discovered using the IP discovery feature are fixed by dialog, enter an IP address in dotted-decimal notation. Use this procedure to set the Read-Only community string for one or more devices From the Monitor menu, choose Set Community. Select the devices for which you want to. You can open the Show Info window on a device as described Existing UUID is associated with a different URL". I get an error message: "This Intermapper Server already appears to be associated with the Intermapperĭatabase. Out how many devices I'm monitoring with Intermapper. Does Intermapper support unnumbered IP links?. Some network ovals have more than one IP. There are two separate network ovals on my. 
My switches are always orange and showing. Parent (read-only)ĭevice ID of the parent probe group this device's id if this device is a probe group 0 if the device is not part of a probe group. 
Timestamp of last modification to this device. DataRetentionPolicy (read-only)ĭata retention policy for IM Database CustomerNameReference (read-only)Ĭustomer-supplied device name reference, for linking to an external database. SnmpAdminString (entPhysicalModelName of chassis). SnmpAdminString (entPhysicalMfgName of chassis). SnmpAdminString (entPhysicalSerialNum of chassis). SNMPVersionInt (read-only)ġ, 2, 3 - SNMP versions. These values have been updated in 5.0 to match the values used by the database in the probekind field of the devices table. # Retrieve all vertices from Intermapper, Net::Intermapper::Vertice instances
My $vertices_ref = $intermapper->vertices # Retrieve all interfaces from Intermapper, Net::Intermapper::Interface instances My $interfaces_ref = $intermapper->interfaces My %interfaces = $intermapper->interfaces # Retrieve all maps from Intermapper, Net::Intermapper::Map instances # Retrieve all devices from Intermapper, Net::Intermapper::Device instances # Returns hash or hashref, depending on context # Retrieve all users from Intermapper, Net::Intermapper::User instances # cache - Boolean to enable smart caching or force network queries # modifyport - TCP port for modifying information. # port - TCP port for querying information. # ssl - SSL enabled (1 - default) or disabled (0) # username - Username of Administrator user # hostname - IP or hostname of Intermapper 5.x and 6.x server My $intermapper = Net::Intermapper->new(hostname=>"10.0.0.1", username=>"admin", password=>"nmsadmin") Net::Intermapper::Device - Interface with the HelpSystems Intermapper HTTP API - Devices SYNOPSIS use Net::Intermapper
0 kommentar(er)
