Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
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
  1. Issue:
  2. Cause:
  3. Remedy:

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
13:47, 13 Nov 2015

Tags

Classifications

Public
Powered by MindTouch ®