Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All
     
     

    Setting Up an IP/MPLSView Connection to the Router Network

    To set up a connection to a router for the network management features of IP/MPLSView, you can manually add a static route into the routing table as explained below. The server should be connected to the routers for telnet collection.

    This procedure can be used to verify, add, and remove routes to the router network. First try to ping a router in your network by typing ping router-IP-address”, substituting router-IP-address with the IP address of a router in your network. If the ping is successful, you are already connected. Otherwise proceed with the following steps:

    Open a console window and switch to super user by using the su command if you are not already user ID root .

    1. To check what routes are listed in the current routing table, use the following command:
      # /bin/netstat -rn
    2. To add a route to a network through a gateway, use the route add command.

      For example:

      ip route add router-network-address via gateway-address dev interface

      Substitute the router-network-address and the gateway-address with the proper values:

      # /usr/sbin/ip route add X.X.X.X/X via X.X.X.X dev interface

      In this example, X.X.X.X/X is the network number and netmask for the static route and X.X.X.X and interface are the IP address and interface for the default gateway.

      The X.X.X.X address does not have to be the default gateway IP address. In most cases, X.X.X.X is an IP address in a different subnet, and interface is the interface that is connected to, or can reach, that subnet.

      For example, if 172.16.0.0 is the router network subnet and 192.168.34.22 is the gateway to the router network, enter the following command:

      # /usr/sbin/ip route add 172.16.0.0 via 192.168.34.22 dev eth0
    3. To add a route to a specific router as opposed to a network, use the same command but omit the -net keyword.

      Note that if a preexisting route to the same destination is listed before the one you add, your new route is not used. To remove a preexisting route:

      # /usr/sbin/route delete router-network-IP-address gateway-to-router-ntwk-IP
    4. To remove all the current routes before installing new ones:
      # /usr/sbin/route flush
    5. To make the routes persistent so that they are still available after rebooting the system, use the route -p command (if the -p option is available). This adds routes to the /etc/inet/static_routes file. For example:
      # route -p add -net x.x.x.x -netmask 255.255.0.0 x.x.x.x

      Note that the -p option is not available for all installations. In that case, another option is to create a script file listing all the route commands, one route command per line, including the route flush command as the first line. The script should be executable. If it is not, use the chmod +x filename command and execute the script as the root user to test it. Then as the root user, call the script at the end of the /etc/rc2 file.

    6. To set up a default route, enter the following command:
      # /usr/sbin/route add default gateway-to-router-network-IP

      In this example, substitute gateway-to-router-network-IP with the gateway to the router network and ensure that it also is not overridden by an incorrect route.

      To avoid losing the default route when rebooting the machine, create or edit the /etc/defaultrouter file with the IP address of the gateway.

      For additional information, read the reference manual pages for the defaultrouter and route commands.

    This procedure can be used to troubleshoot the connection to the router network. If the server has an interface card, verify that the interface card is full duplex rather than half duplex. To verify the duplex:

    1. Find the names of the interfaces.
      ifconfig -a

      The command returns the name of the interfaces. For example, nge0.

    2. Use the nnd command to verify the duplex setting.
      ndd /dev/nge0 link_duplex

      The command returns 0 if the link is down, 1 if it is half duplex, and 2 if it is full duplex. If the command returns 1, read your hardware manual for instructions on how to configure the interface to be full duplex.

    3. If the server has more than one interface card, the server might be acting as a router, which might cause connectivity problems. In this case, create the /etc/notrouter file as the root user using the following command:
      # /usr/bin/touch /etc/notrouter
    4. If ping and traceroute still do not work, verify that there is no firewall between the IP/MPLSView server and the router network.
    5. If the routers cannot be reached directly due to a firewall, use a Remote Collection Server.
     
     

    Modified: 2016-09-28