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

    Configure a Static Route to the NSM Server

    Purpose

    When your M Series or MX Series device and the NSM server are in different subnets, you can install a static route on the device to connect to the NSM server. The static route is installed in the routing table only when the route is active; that is, the list of next-hop routers configured for that route contains at least one next hop on an operational interface.

    Action

    To configure a static route, follow these steps:

    1. Log on to the M Series or MX Series device and, in configuration mode, go to the following hierarchy level:
      [edit]user@host# edit routing-options
    2. Configure a static route to the NSM server with the retain option so that the static route remains in the forwarding table when the routing protocol process shuts down normally:
      [edit routing-options]user@host# set static route destination-prefix next-hop address retain
    3. Configure the no-readvertise option so that the route is not eligible for readvertisement by dynamic routing protocols:
      [edit routing-options]user@host# set static route destination-prefix next-hop address no-readvertise
    4. Verify the configuration:
      user@host# show
    5. Commit the configuration:
      user@host# commit
    6. Verify the connection to the NSM server:
      user@host# run ping destination

    Sample Output

    user@host> edit 
    Entering configuration mode
    
    [edit]
    user@host# edit routing-options
    
    [edit routing-options]
    user@host# set static route 192.193.60.181/32 next-hop 192.193.76.254
    
    [edit routing-options]
    user@host# set static route 192.193.60.181/32 retain
    
    [edit routing-options]
    user@host# set static route 192.193.60.181/32 no-readvertise 
    
    [edit routing-options]
    user@host# show
    static {
        }
        route 192.193.60.181/32 {
            next-hop 192.193.76.254;
            retain;
            no-readvertise;
        }
    }
    
    [edit routing-options]
    user@host# commit 
    commit complete
    
    [edit routing-options]
    user@host# run ping 192.193.60.181 
    PING 192.193.60.181 (192.193.60.181): 56 data bytes
    64 bytes from 192.193.60.181: icmp_seq=0 ttl=64 time=23.050 ms
    64 bytes from 192.193.60.181: icmp_seq=1 ttl=64 time=18.129 ms
    64 bytes from 192.193.60.181: icmp_seq=2 ttl=64 time=0.304 ms
    ^C
    --- 192.193.60.181 ping statistics ---
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 0.304/13.828/23.050/9.771 ms
    

    Meaning

    The sample output shows that a static route (192.193.60.181/32) to the NSM server is configured and committed, and that there is a connection between the router and the server because the ping command shows that three packets were transmitted and received.

    Published: 2013-01-02