From there we can try a targeted walk to see if they exist in the device as well as check DcDebug for Discover logging to see what PM is seeing. The next step would be to go take a look at the Metric Family / Vendor Certification to see what the required fields are. Now you can see the Virtual Interface Monitoring Profile (which contains the Virtual Interface Metric Family) will be associated to All Routers. You can create a custom collection as well if you want to contain only the CheckPoint devices instead of all routers but for my example I will add it to Routers: Go to Monitoring Profiles on the left and click the new button at the bottom:Īfter that is created now you need to add it to a collection in the Collections section just like you would when adding Network Interface. So for my example device it is showing as a router, if I wanted to get Virtual Interfaces to it I would need to create a new Monitoring Profile as Virtual Interface is not in one by default. You can see what device types a device is on the details tab of Monitored Devices:Īnd then on the Monitoring Profiles tab you can see further details as well as if you click a collection you can see what Monitoring Profiles are associated to it: Do you have the Virtual Interface Metric Family associated to a Monitoring Profile that is associated to a Collection that the device in question is a part of? It is sort of a following the bouncing ball kind of thing.

Checkpoint firewalls