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

    Importing GRE Tunnel Information from Router Configuration Files

    Use these procedures if you have Cisco GRE tunnels configured in your network.

    If you wish to perform this task, you should have a set of router configuration files with GRE tunnels configured.

    Generic Routing Encapsulation (GRE) Tunnels can be either imported from the router configuration files, or created from the IP/MPLSView Graphical Interface for what-if studies. Afterwards, the GRE tunnel path and details can be viewed, as well as the details and paths of the demands routed over the GRE tunnel. The GRE tunnel can also be referenced as the next hop of a static routing table.

    The following GRE statements are parsed during the config import:


    Cisco


    interface Tunnel<id>
    ip address <ip-address> <mask>
    tunnel source (ip-address|type number)
    tunnel destination ip-address {hostname | ip-address}

    Juniper


    [edit interfaces interface-name unit logical-unit-number tunnel] level:
    gr-1/2/0 {
    unit 0 {
    tunnel {
    source <ip-address>;
    destination <ip-address>;
    }
    }
    }

    IP/MPLSView maps these statements into entries in the intfmap (interface), tunnel, and bblink file.


    Example intfmap entry


    0.0.0.0/0,ATL,Tunnel4,active, ,,0, , , ,,,,,,,,,,,,0,,
    0.0.0.0/0,BOS,Tunnel5,active, ,,0, , , ,,,,,,,,,,,,0,,

    Example tunnel entry


    #Tunnel Src Destination BW Type_Field
    Tunnel4 ATL 172.16.1.2 0 R,A2Z,GRE,SOURCE=172.16.1.6,MASK=0000ffff 7,7
    Tunnel5 BOS 172.16.1.6 0 R,A2Z,GRE,SOURCE=172.168.1.2,MASK=0000ffff 7,7

    In the tunnel entry, note that the tunnel source of Tunnel4 matches the destination IP address of Tunnel5, and the tunnel source of Tunnel5 matches the destination IP address of Tunnel4.


    Example bblink entry


    #Linkname NodeA NodeZ Vendor Count TrunkType [MISC]
    ATL_TUNNEL4 ATL BOS DEF 1 GRELINK C1=Tunnel4 C2=Tunnel5 # UP
    #!

    Each GRELINK entry references one GRE tunnel interface for the A to Z direction using C1=<interface> and one GRE tunnel interface for the Z to A direction using C2=<interface>. By default, the status of a link of type GRELINK will be down/deleted if one of the tunnels fails to be routed. If both tunnels are routed, the GRE link is considered to be up, and traffic over a GRELINK will then be routed over the links traversed by the GRE tunnel.

    In some cases, however, the software fails to route the GRE tunnel due to incomplete information. In those cases, the GRELINK may actually be up but there is no information to determine whether the tunnels are successfully placed. For example, the the config files for the routers necessary to route the GRE tunnel may be missing if they belong to another service provider. To avoid setting the GRELINK status to down in this scenario, set virtualgrelink=0 in the dparam file to treat GRELINKs as normal links.

    To import the router configuration files, select File>Import Data and follow the Import Network Wizard. Alternatively, you may run the getipconf program in text mode.

    After importing the config files, view the Integrity Checks report by selecting Report > Report Manager and then selecting the Configuration Report>Summary of Integrity Checks Report item.

    The “Asymmetric GRE tunnels” integrity check will appear if there is a GRE tunnel defined at one end of the tunnel but not the other. Additionally, the “Inconsistent GRE tunnels protocol” integrity check will appear if the IGP protocol defined on one end of the GRE tunnel is different than the IGP protocol defined on the other end. These integrity checks are included under the TUNNEL category. To view the details of an integrity check, right-click on the row and select Display item(s) for this msg ID/Category.

    Modified: 2016-11-08