- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Custom device support bundle. 'devicemap' usage within definition.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2019 10:48 AM
Hi Everyone.
I have a significant number of 'net-SNMP' vendor devices, and would like to refine into separate classes (devicetypes).
It appears the 'devicemap' tag within the DSB will allow me to do so.
The question is, to accomplish this, which of the tags, 'mibenterprise', 'devicetype', or 'devicetypemodels' do I include?
What is required and/or recommended, and what is not necessary to refine the 'net-SNMP' OID futher using sysDescription field ('devicemap' tag).
Thanks in advance for any direction you can provide.
Jim
Re: Custom device support bundle. 'devicemap' usage within definition.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2019 06:07 AM
Hi Jim,
I believe your requirement is to get IPC Unigy Voice Recording servers/devices (also called 'turrets') typed as 'Turrets' based on the sysDesc. This can done by using the following tags:
The <devicemap> tag defines the following attributes:
devicetype - The type of device that will be assigned when matching the other attributes
identification - The value of sysDescr to match
sysServices - Optional value of sysServices to match
ipForwarding - Optional value of ipForwarding to match
cdpCapabilities - Optional value of CDP cache capabilities from neighbor devices to match
lldpCapabilities - Optional value of LLDP capabilities from neighbor devices to match
<devicemap devicetype="WOC" identification="%Citrix CloudBridge%" ipForwarding="not-forwarding" />
The <devicetypemodels> tag defines an association between sysObjectID values and the device type to be associated to those devices. The tag defines the following attributes:
devicetype - The type of device that will be assigned when matching the sysObjectID
sysObjectID - The value of sysObjectID to match
<devicetypemodels devicetype="Firewall" sysObjectID="1.3.6.1.4.1.12356.101.1.636" />
-----------------------------------------------------------------------------------------------------------------
Your DSB should look something like the following. Note: Identation of the tags is important for the DSB to work properly.
<?xml version="1.0"?>
<dsb name="IPC_xxxxx" version="201902090000" author="Infoblox" netmri="7.*">
<devicesupport dataset="System" action="INCLUDE" vendor="IPC" sysversion="xxxxx" model="xxxx" />
.................
...........
.........
<devicesupport dataset="ARP" action="EXCLUDE" vendor="IPC" sysversion="xxxxx" model="xxxx" />
<devicesupport dataset="Config" action="INCLUDE" vendor="IPC" sysversion="xxxxx" model="xxxx" />
<!-- Support for devicetype identification -->
<!-- Use the <devicetypemodels> tag to blindly map the sysObj ID to 'Turret' and that will make sure all the device with this sysobj ID will be typed as Turret -->
<devicetypemodels devicetype="Turret" sysObjectID="1.3.6.1.4.1.9.1.1469" />
<!-- OR use the following <devicemap> tag to determine device type based on sysDescription --->
<devicemap devicetype="Turret" identification="%hello_world%" />
</dsb>
-----------------------------------------------------------------------------------------------------------------
Hope this helps.
-Kishore