Header Only - DO NOT REMOVE - Extreme Networks

Adding Unsupported or Third Party Devices to NetSight Console


Userlevel 3
Article ID: 10261

Products
NetSight Atlas Console, version 1.0 and higher

Solution
How to place a previously unknown (identified with a question mark) device into the Device Tree under its own folder:
    1. Open MIB tools on the device and query sysObjectID=1.3.6.1.2.1.1.2. Make note of the raw and formatted values.
    2. Formulate a device properties block for the device in question: <sysObjectID Raw Value>=<sysObjectID Formatted Value> <sysObjectID Formatted Value>=<sysObjectID Raw Value> <sysObjectID Formatted Value>.family=<product family name desired> <sysObjectID Formatted Value>.name=<product name desired> <sysObjectID Formatted Value>.treeicon=<treeicon desired - see more below> <sysObjectID Formatted Value>.mapicon=<mapicon desired - see more below>
    The Treeicon defines what icon to use in NetSight's device tree. The available values are: 0 = Unknown 1 = SNMP 2 = Router 3 = Switch 4 = VPN 5 = Wireless 6 = Ping[/code] The Mapicon defines what icon to use in NetSight's maps. Choose a file (there are many) from the NetSight image directory. Generic choices compatible with the stated Treeicons might be: unknown.gif snmp.gif, pc.gif, ethernetPC.gif, analyzer.gif, generic32x32.gif router.gif switch.gif, wanBridge.gif vpnConcentricUp.gif New_Wireless_for_Console_Map.gif pingOnly.gif[/code] Note: The stock image directory for version 1.x is located at ~\Resources\images, for 2.x is located at ~\client\Resources\images, and for 3.x is generated by a .dll so is thus not directly viewable or updateable. In version 3.x, users may as desired add their own images to NetSight directory ~\appdata\System\images, then restart the server to push any changes to connected clients. Here are some examples of device properties as defined by past customers: 1.3.6.1.4.1.9.1.5=enterprises.9.1.5 enterprises.9.1.5=1.3.6.1.4.1.9.1.5 enterprises.9.1.5.family=Other enterprises.9.1.5.name=Cisco Systems enterprises.9.1.5.treeicon=2 enterprises.9.1.5.mapicon=generic32X32.gif 1.3.6.1.4.1.52.4.15.1.3.1.2=rbtwsSwitch8200 rbtwsSwitch8200=1.3.6.1.4.1.52.4.15.1.3.1.2 rbtwsSwitch8200.family=RoamAbout rbtwsSwitch8200.name=8200 rbtwsSwitch8200.treeicon=5 rbtwsSwitch8200.mapicon=New_Wireless_for_Console_Map.gif 1.3.6.1.4.1.207.1.4.78=at-8024M at-8024M=1.3.6.1.4.1.207.1.4.78 at-8024M.family=Allied Telesyn at-8024M.name=8024M at-8024M.treeicon=3 at-8024M.mapicon=generic32X32.gif 1.3.6.1.4.1.318.1.3.2.13=SmartUPS5000 SmartUPS5000= 1.3.6.1.4.1.318.1.3.2.13 SmartUPS5000.family=APC SmartUPS5000.name=SmartUPS5000 SmartUPS5000.treeicon=1 SmartUPS5000.mapicon=generic32x32.gif 1.3.6.1.4.1.1916.2.17=alpine3808 alpine3808=1.3.6.1.4.1.1916.2.17 alpine3808.family=Extreme alpine3808.name=Alpine3808 alpine3808.treeicon=3 alpine3808.mapicon=switch.gif 1.3.6.1.4.1.2334.1.1.20=enterprises.2334.1.1.20 enterprises.2334.1.1.20=1.3.6.1.4.1.2334.1.1.20 Packetshaper.family=Packeteer Packetshaper.name=Packetshaper 7500 Packetshaper.treeicon=2 Packetshaper.mapicon=generic32x32.gif[/code]
    3. Apply the new device information into NetSight:
    In NetSight Console 1.x, edit the file ~\Resources\deviceTypes.properties (in the NetSight install directory), adding your new definition in any order. Then, stop and restart the client so that the new information is read in. This must be done on each client system.
    In NetSight Console 2.x, edit the file ~\client\Resources\deviceTypes.properties (in the NetSight install directory), adding your new definition in any order. Then, stop and restart the client so that the new information is read in. This must be done on each client system.
    In NetSight Console 3.x, edit the file ~\appdata\System\deviceTypes\mydeviceTypes.properties (in the NetSight install directory), adding your new definition in any order. Then, stop and restart the server so that the new information is read in. Once this is set up on the server it will be pushed out to each client.

0 replies

Be the first to reply!

Reply