Out-of-band device discovery questions

[Timothy Onyskin]

I have a few questions regarding out-of-band device (OOBD) discovery.  I have read the document on ServiceNow's site about how to do it, and we have some out-of-band devices (OOBD) discovered which leads me to these questions:

1.  Why does the OOBD link to a single host though it can support multiple ESX hosts or pSeries servers that have multiple virtual devices sitting on top of them?  Is there a way to make it should a list of all of the physical devices that the OOTD can control (the virtual devices can then be inferred)?

2.  I see that v1 and v2c are supported.  Do we know when v3 will be supported since the CMC and iDrac can support v3?

3.  In the CMDB, the "type" field seems to be populated some of the times and it looks like it is a free-formed text field.  I know it gets this through the SNMP MIB, but is there a place that the administrator of the devices sets that information?  My admins could not find it, but we want to try to get that automatically populated for all devices.

Any information would be helpful and thank you in advance.

[Natascia Heil]

2. SNMP v3 is also supported already

3. Normally fields in the CMDB are normally filled by patterns. Depending on the class the CI belongs to there are fields available in the class. The patterns define, which fields are filled with which information. Admins can extend existing patterns or write their own. So your question cannot be answered generally.

[Timothy Onyskin]

Thank you for these answers.  The ServiceNow documentation for Orlando only said v1 and v2c so I was going by that without testing.

I know they can be extended (haven't done it before), but I was wondering if anyone knew in the OOBD where that could be set since the SNMP queries a specific MIB, but I guess that would be a question more for each vendor.

Any comment on item number 1 from above (am I thinking wrong or does it make sense to have a 1 OOBD to many host)?