Preview Tool

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

Last Modified

Jan 14, 2017

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases


Description (partial)


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. 


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

Using the below command syntax: 

Router static
address family ipv4 unicast Gig0/0/1/0 

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 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.