Does anybody know why NPM 11.0 thinks a Checkpoint firewall is an autonomous access point?
what makes you think that is what NPM thinks?
a) are you monitoring it using SNMP?
=> what is the sysObjectID
=> what is the Vendor
=> what is the MachineType
b) on https://your-server/Orion/Admin/ViewsByDeviceType.aspx
=> what is the View you have associated with the Checkpoint Machine Type?
c) on https://your-server/Orion/Admin/ListViews.aspx
-> find the view you have associated with the device type (step
-> what is the 'title' of that view
d) if you do 'List resources' does it show wireless controller?
e) for checkpoitn firewalls also have builtin wireless support?
(some of the odd cisco routers we have have wireless support because that was what we had on the shelf when they were deployed)
When I click on the node it actuallys says Wireless Autonomous AP -
This firewall does not have wireless support.
Device is tied to correct resources and does not show wireless when the resources are listed.
run SNMPwalk to that checkpoint firewall router
Open C:\Program Files (x86)\SolarWinds\Orion and run SNMPWalk.exe
- Enter IP address of Node, Community String
- Click Scan and then save the resulting text file
- open the notepad file search this OID - 1.3.6.1.2.1.1.2
- see what it shows. if it returns for another OID, post it here or check your Firewall documentation for that OID - what does it mean.
What are the answers on questions a) and b) from Richard?
Sorry. Friday was a very busy day. I just assumed it was under the CheckPoint Technology Object Type. The view was the problem.
I didn't look at the Net-SNMP Object Type only the Checkpoint Technology Object Type.
thanks for your help.
You deleted an reply that might have been useful to other readers.
SysObjectID = 1.3.6.1.4.1.8072.3.2.10
[soapbox]
NET-SNMP is an open source extensible snmp agent that is commonly embedded in network equipment.
It is a one-line in the configuration for for the device to report a unique sysObjectID for the actual hardware.
I have everything from cheap wireless bridges to devices costing over $400K reporting themselves as 'net-SNMP'
it bugs the heck out of me that manufacturers can't take the 30 minutes to define an equipment MIB, uniquely identify their product, and to then put that in the configuration file on the hardware.
With NPM (and many other network management software) this value is used to derive/drive the vendor, Machinetype, and thence the views displayed for the device.
If you have a device that is not actually a linux server running net-snmp you compiled/installed yourself please file a bug report with the vendor telling them to define a device MIB and assign a unique sysObjectID to each type of hardware they sell.
[/Sopabox]
