Guest

Preview Tool

Cisco Bug: CSCtf32885 - Msg should be logged for static routes indicating next hop out of subnet

Last Modified

Feb 13, 2018

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

3.8.0.ROUT

Description (partial)

Symptom:

When a static route is configured with explicit next hop address and interface provided a log 
message should be created when the ip address of the next hop is not in the subnet associated
with the provided interface. 

Conditions:

For example when the ip address for 10.1.1.1 does not exist in the subnet for Gig0/0/1/0. 

Using the below command syntax: 

Router static
address family ipv4 unicast 
192.168.1.0/24 Gig0/0/1/0 10.1.1.1 

A log message should be provided indicating that the subnet on the interface and provided next 
hop do not match. 

IE: Warning: Next hop configured does not exist on interface in static route.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.