Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > 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