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 18.104.22.168 22.214.171.124 volga-cities 2 rem rip net1The 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.
# setany paris public ipRouteNextHop.126.96.36.199 \ -a 188.8.131.52 ipRouteType.184.108.40.206 -i 4
Name: ipRouteNextHop.220.127.116.11 Value: 18.104.22.168
Name: ipRouteType.22.214.171.124 Value: 4