No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The Management Module Cannot Be Accessed After the Route Is Changed

Publication Date:  2015-06-24 Views:  28 Downloads:  0
Issue Description
Hardware configuration:
A E6000

Software configuration:
The default route of the management module is 10.66.252.130.

Symptom:

The default route of the management module is changed at a site as follows:

1.  Log in to the active management module over Telnet.

2.  Run the route del -net default netmask 0.0.0.0 gw 10.66.252.130 command to delete the default route of the management module.

3.  Run the route add -net default netmask 0.0.0.0 gw 10.66.252.129 command to change the default route of the management module to 10.66.252.129, as shown in Figure 1.

Figure 1 Viewing the changed default route



After the default route of the management module is changed to 10.66.252.129, the management module cannot be accessed.
Handling Process
1.  Connect a client to the active management module and access the management module over the web.

2.  Check the management module route setting, as shown in Figure 2. The default route is not 10.66.252.129.

Figure 2 Management module route setting



3.  Click Refresh on the Route tab of the MM page. The default route is 10.66.252.130.

4.  Log in to the management module over Telnet and run the route command to check the route information. There are two default routes: 10.66.252.130 and 10.66.252.129, as shown in Figure 3.

Figure 3 Refreshed management module route



5.  The management module route can be configured by using the standard smmset commands. For details about the commands, see Note. If you add or delete the management module route on the command-line interface (CLI) or web user interface (WebUI), the route information is stored in /common/flash/route.cfg. When you log in to the management module WebUI to view the management module route or refresh the route page, the management module software reads the /common/flash/route.cfg file again and make the route to take effect. As a result, the route checked on the CLI or WebUI is 10.66.252.130.

6.  On Linux, you can run the route del -net default netmask 0.0.0.0 gw 10.66.252.130 command to delete the default route of the management module and the route add -net default netmask 0.0.0.0 gw 10.66.252.129 command to add a route to the management module. However, the route configuration does not modify the /common/flash/route.cfg file. As a result, the management module does not detect the newly added route 10.66.252.129.

7.  According to analysis in 5 and 6, the management module detects only the route 10.66.252.130. As a result, the management module cannot use the route 10.66.252.129 to connect to the destination network.
Root Cause
The management module cannot detect the route configured by using the route command. As a result, the destination network cannot be connected.

Solution
Delete the route configured by using the route command and use standard management module commands to configure a route for the management module. For details, see Note.

Suggestions
Do not run Linux commands on the management module. Use commands on the CLI to operate the management module. For details, see MM610 Management Module Command Reference.

Note:
View and set the management module route by using the following commands (for details, see MM610 Management Module Command Reference):

View the management module route:

smmget [-l smm ] -d displayroutes

Add a route:

smmset [-l smm] -t ethNumber -d routeadd -v DestIPaddressvalue maskvalue gatewayvalue

Delete the route:

smmset [-l smm] -t ethNumber -d routedelete -v DestIPaddressvalue maskvalue gatewayvalue



END