Hi - to modify the default (which I agree, I don't think disco classify's some of these correctly... i.e. as IP Switches when the are not). requires some redesign the classification of Wireless LAN controllers, you'll need too:
1. Consider adding a new CI (probably subclassed off Network Gear or similar...). Or research existing classes to that you/not already have
2. Create SNMP OID classifier for the specific OID # of the make/model of device you are interested in.
Example:
TIP: When disco returns the Topic=SNMP payload Queue=input, it'll have the specific OID of that device (assuming you have set up SNMP credentials to query the device) Examine the XML payload for the SnmpObjectID. you'll need this to create the correct SNMP OID classifier
3. Create SNMP classifier to A) put the discovered device into your wireless controller class and B) associate that SNMP classifier with the SNMP OID (created step2)
Example for IP switch... but the concept is the same.
4. Create pattern custom pattern to interrogate the controller via SNMP and collect the data into your CI class
5. on the SNMP classifier, on triggers probe tab, set your new pattern to be launched when the classifier runs. Similar to this:
I've gone thru this for Aruba wireless controllers, researching the problem, and found:
-
lots of existing OOB OIDs w/mfg=Aruba all classify as IP Switch out of the box.
"Bad SNMP OIDs 1.3.6.1.4.1.14823.1.2.* causes unsupported Aruba Access Point devices to classified as Network Switch" -
KB0993417 acknowledges this problem (i.e. classifying as IP Switch when it shouldn't be)
-
SNOW doesn’t have Out of the Box wireless controller class
-
+50 incorrect OIDs per KB0993417
I leveraged John Frandsen's excellent article here, INCLUDING and handy update set to build out something similar.
I know it may not satisfy your point about "easiest way to create a "Wireless Lan Controller" class ".... 🙂 But this is how SNMP discovery works.
I hope all this helps some?
Dave
