DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Configuring the Simple Network Management Protocol (SNMP)

Removing an incorrect routing entry

Suppose that due to a configuration error, a system in another part of the building has an offending entry in its routing table and is causing communication problems with hosts in other company offices. The network administrator can use SNMP commands to correct the incorrect routing entry remotely.

The following example shows how the administrator might proceed. In the example, the setany command line is split with a backslash for clarity. It should be typed in as one line to the shell.

In addition to the new next hop, the administrator specifies the type of route. In this case, the route is an indirect or remote route (type 4), that was reported by snmpstat as rem.

Correcting routing entries

   # snmpstat -r paris public | grep 10.0.118.0
   10.0.118.0   volga-cities    2   rem    rip    net1
   

# setany paris public ipRouteNextHop.10.0.118.0 \ -a 10.0.246.1 ipRouteType.10.0.118.0 -i 4

Name: ipRouteNextHop.10.0.118.0 Value: 10.0.246.1

Name: ipRouteType.10.0.118.0 Value: 4

The administrator could also have deleted the route by setting its ipRouteType to invalid (type 2). This is useful if a routing protocol reacquires the route information automatically.

See also:



Next topic: Obtaining remote system contacts
Previous topic: Using SNMP to correct problems

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003