Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Missing Topology Routing Poller for Juniper NetScreen devices

Missing Topology Routing Poller for Juniper NetScreen devices

Table of contents

Issue:

Juniper NetScreen devices are not identified in the network topology.

Cause:

Orion Core is checking 1.3.6.1.2.1.4.1 OID in Topology Routing Poller Discovery. However, Juniper NetScreen does not set this ipforwarding OID correctly and returns a response (2) showing it as an endpoint rather than a gateway.

Remedy:

From the ScreenOS 6.3 release, you can fix this by typing the following into the CLI:
   set snmp rfc1213 ipforwarding enable
For further information see the following Juniper Network knowledge base article, How to modify the behavior of the firewall response for the 'ipForwarding' SNMP OID on ScreenOS devices.
Last modified

Tags

Classifications

Public