Support Support Downloads Knowledge Base Service Request Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[SRX] The message, 'error: bad next-hop' is seen when IP Monitoring is configured

0

0

Article ID: KB31164 KB Last Updated: 04 Mar 2017Version: 2.0
Summary:

This article explains why the message, 'error: bad next-hop' is seen IP monitoring is configured.

Symptoms:

After committing, the following message is returned:

set services ip-monitoring policy TEST then preferred-route route 0/0 next-hop fe-0/0/2.0
commit
error: bad next-hop, fe-0/0/2.0 is not point-to-point
error: configuration check-out failed
Cause:

Since 12.1X46-D15, the interface type checks for next-hop. Only a P2P (point to point) interface is supported. As a result, an error message is shown when an invalid configuration is committed.

Prior to 12.1X46-D15, even if there is no error message returned, the IP Monitoring does not work as expected.

Solution:

Use the peer IP address instead of the interface name.

Example:
set services ip-monitoring policy TEST then preferred-route route 0/0 next-hop 1.1.1.2

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Security Alerts and Vulnerabilities

Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search