To configure a routing instance or a VRF instance

Purpose

This procedure describes the base configuration of a routing instance or VRF instance.

Note: The functionalities described in this procedure are device-dependent. Not all functionalities described in this procedure are supported by all devices.

Steps
 
1 

In the navigation tree routing view, expand Network→NE→Routing Instance.

2 

Perform one of the following:

  1. If you are configuring a VRF instance on the following OmniSwitch NEs, go to Step 3 .

    • OS 6850E

    • OS 6855-U24X

    • OS 6860

    • OS 6860E

    • OS 6860N

    • OS 6865

    • OS 6900

    • OS 9700E

    • OS 9800E

    • OS 10K

    Note: SNMPv3 must be used to manage supported OmniSwitch devices when configuring a VRF routing instance.

  2. If you are configuring a routing instance on all other devices, go to Step 5 .

3 

Right-click on an OmniSwitch routing instance icon and choose Create VRF Instance. The Routing Instance (Create) form opens.

4 

Configure the VRF Name parameter and click Apply. The Routing Instance (Edit) form opens. Go to Step 6 .

5 

Right-click on a routing instance icon and choose Properties. The Routing Instance (Edit) form opens.

6 

Edit or view the base routing policies associated with the routing instance if required:

Perform the following steps:

  1. Click Edit Routing Policies. The Routing Policy Manager - Site (Edit) form opens.

  2. Configure the parameters if required.

  3. Click Show Policy. A Routing Policy Show Policy form opens and a CLI session is initiated.

    The Show Policy button only displays if a routing policy has been distributed to the device.

  4. View the policy as required.

  5. Close the form. The Routing Policy Manager - Site (Edit) form reappears.

  6. Click OK if required or close the form. The Routing Instance (Edit) form reappears.

7 

Configure the parameters on the General tab as required.

  1. Select a reassembly group, if required.

  2. If the routing instance is part of a TCP MSS adjustment configuration, select an ISA-BB group and configure the Segment Size parameter.

  3. If the routing instance is part of a home LAN extension configuration, place a check mark in the Enable Home LAN Extension check box.

  4. If the routing instance is part of an ISA service chaining configuration, place a check mark in the Enable ISA Service Chaining check box.

8 

If GRT route leaking is required for VPRN, configure the parameters on the Leak Export Policies tab.

9 

Click on the Protocols tab or Multicast tab to modify the default routing or multicast protocols assigned to the routing instance.

  1. Configure the parameters as required. See Chapter 28, Routing protocol configuration for more information about routing protocol configuration using the GUI.

  2. Click Apply to save the changes.

10 

Click on the OAM tab and perform the following as required:

  1. Assign a test generation option to the routing instance by configuring the Test Generation Options parameters on the Configuration tab as required.

  2. Configure a TWAMP Light Reflector on the routing instance:

    Note: A TWAMP Light reflector is required to conduct a TWAMP Light Test Session. See To configure a TWAMP Light reflector for more information about TWAMP Light reflectors.

    The 7705 SAR does not initiate TWAMP Light Test sessions, but only acts as a TWAMP Light Reflector. The 7705 SAR does not support PM sessions.

    The 7705 SAR-Hm supports TWAMP Light Test sessions and PM sessions.

    Perform the following steps:

    1. Click the TWAMP Light Reflector tab and click Create or select an existing TWAMP Light Reflector and click Properties.The TWAMP Light Reflector (Create|Edit) form opens.

    2. Configure the parameters on the General tab as required.

    3. Click Create in the Reflector Prefixes panel. The Prefix TWAMP Light Reflector (New Instance) form opens.

    4. Configure the parameters as required and click OK. The TWAMP Light Reflector (Create) form reappears.

      Prefixes are added to the reflector to determine which PM Sessions can target the reflector. You should specify the prefix address and length if you require masking. Only those TWAMP Light test sessions with a Source IP matching a prefix will be valid. A maximum of 50 prefixes can be added to a reflector. TWAMP Light sessions without a matching prefix will cause an alarm to be generated.

    5. Close the form. The Routing Instance (Edit) form reappears.

  3. Add a TWAMP Light Session to the routing instance:

    Perform the following steps:

    1. Click on the TWAMP Light Sessions tab and click Add.The TWAMP Light Session (Create) form opens.

    2. Perform To configure a TWAMP Light session OAM diagnostic test from the STM to complete the configuration of the TWAMP-Light Session.

  4. Add a PM Session to the routing instance:

    Perform the following steps:

    1. Click on the PM Sessions tab and click Add. The PM Session, New Create form opens.

    2. Perform To configure a PM session OAM diagnostic test from the STM to complete the configuration of the PM Session.

11 

Click on the Routing tab and perform the following as required:

Perform the following steps:

  1. Configure the required general parameters.

    For 7210 SAS NEs, the value for the Maximum Number of Equal Cost Routes parameter cannot be greater than the value of the Max ECMP Route Destinations (Active) parameter in the system resource profile. See To configure the global system resource profile on a 7210 SAS or 7250 IXR .

    For 7250 IXR NEs, you must configure the system resource profile appropriately. Create ECMP Profiles to provide both an LDP and an IP profile type; see To configure the global system resource profile on a 7210 SAS or 7250 IXR.

    See Chapter 28, Routing protocol configuration for more information about AS and confederation AS parameters for BGP using the GUI.

  2. Configure the Enable Entropy Label parameter, as required.

  3. Configure the required parameters in the LDP Shortcut Enabled panel.

  4. Configure the required parameters in the Maximum Number of Multicast Routes panel.

  5. Assign an ingress multicast information policy to the routing instance in the Multicast Path Management Info Policy panel.

    See To configure an ingress multicast information policy for information about how to configure an ingress multicast information policy. See Step 38 in this procedure to view the data from the operational channels after actual traffic passes through the virtual router/routing instance from a specific multicast source for a specific multicast group.

  6. Configure the required parameters in the TTL Propagate panel.

  7. Configure the required parameters in the LSP BFD panel.

  8. Configure the Single SFM Overload Admin State parameter in the Single SFM Overload panel.

  9. Configure the parameters in the Static Route Hold-Down Time panel.

    The Initial Hold-Down Time, Hold-Down Time Multiplier, and Maximum Hold-Down Time parameters are configurable when you enable the Enable Hold-Down Time parameter.

  10. Configure the IPv4 Max Size and IPv6 Max Size parameters in the Flowspec panel, as required.

12 

Click on the WLAN GW tab as required to view or configure WLAN gateway functionality on 7750 SR devices routing instances.

Note: Prior to completing this step, verify that the WLAN GW parameter on the General tab on the Routing Instance (Create|Edit) form is enabled.

Perform the following steps:

  1. Configure the parameters on the General tab as required.

    The Interim Update parameter must be enabled if the Include Counters and Hold Down Time parameters are to be configured.

  2. Click on the Mobile GW Address Map tab and click Create or select an existing mobile gateway address map. The Mobile Gateway Address Map (Create|Edit) form opens.

  3. Configure the parameters as required.

  4. Click on the Select button to specify a mobile gateway/peer profile policy.

  5. Click Create or choose an existing mobile gateway/peer profile and click Properties. The Mobile Gateway/Peer Profile (Create|Edit) form opens. See To configure a mobile gateway/peer profile for information about how to create a Mobile Gateway/Peer Profile. See Step 27 in this procedure to view WLAN GW Tunnel information from the operational channels after actual traffic passes through the routing instance.

  6. If the WLAN GW is intended for a home LAN extension configuration, click on the Cross Connect tab.

    Configure the required parameters and select a WLAN GW group.

  7. Save your changes and close the form. The Routing Instance (Edit) form reappears.

13 

To configure home LAN extension functionality on the routing instance, click on the Home LAN Extension tab.

Select an ISA WLAN GW group and configure the other parameters.

14 

To configure home ISA service chaining functionality on the routing instance, click on the ISA Service Chaining tab.

  1. On the ISA Groups tab click Create or choose an existing ISA group and click Properties. The Service Chaining ISA Group (Create|Edit) form opens.

  2. Select an ISA-NAT or ISA-WLAN GW group and click OK to close the form.

  3. Click on the VTEP tab and configure the VXLAN VTEP Range, Start and End parameters.

15 

Click on the Interfaces tab if required, to view or configure L3 interfaces assigned to the routing instance. See To create an L3 network interface on a routing instance to complete the configuration of L3 interface.

16 

Click on the Address tab if required, to configure an IP address for the L3 interfaces.

Perform the following steps:

  1. Choose an address in the list and click Click Properties. The IP Address form opens.

  2. Configure the parameters as required.

  3. Save your changes and close the form. The Routing Instance form reappears.

    Note:

    The IP Address, Prefix Length, and Broadcast Address Format cannot be changed for the System interface.

17 

Click on the Static Routes tab if required, to view or configure static routes assigned to the routing instance. See To configure a static route on a routing instance to complete the configuration of the static route.

18 

Click on the Static Route Prefixes tab if required, to view or configure static route prefixes.

Perform the following steps:

  1. Click Create. The Static Route Prefix form opens.

  2. Configure the parameters.

    Routing instances that support BGP large communities can configure up to 12 communities in a static route prefix.

  3. Save your changes and close the form. The Routing Instance form reappears.

19 

Click on the NAT tab if required, to view or configure NAT configurations assigned to the routing instance. See To configure NAT on a routing instance to complete the NAT configuration.

20 

Click on the RSVP Tunnel Interfaces tab if required, to view or configure tunnel interface entries assigned to the routing instance.

Perform the following steps:

  1. Click Create to configure a new entry or select an existing RSVP Interface and click Properties. The RSVP Tunnel Interface (Create|Edit) form opens.

    Note:

    You can alternatively create a RSVP tunnel interface by right-clicking on a routing instance icon in the navigation tree routing view, and choose Create RSVP Tunnel Interface from the menu.

  2. Click Select to choose a Point-to-Multipoint LSP. The Select - RSVP Tunnel Interface form opens. See To create a Point-to-Multipoint LSP for information about how to configure a Point-to-Multipoint LSP.

  3. Choose an RSVP tunnel interface and click OK. The RSVP Tunnel Interface (Create) form reappears.

  4. Configure all other parameters as required.

  5. Save your changes and close the form. The Routing Instance form reappears.

21 

Click on the LDP Tunnel Interfaces tab if required, to view or configure LDP Tunnel Interfaces assigned to the routing instance. Perform the following as required:

  1. Configure a new interface.

    Perform the following steps:

    1. Click Create or select an existing LDP tunnel interface and click Properties. The LDP Tunnel Interface (Create|Edit) form opens.

      Note:

      You can alternatively create a LDP tunnel interface by right-clicking on a routing instance icon in the navigation tree routing view, and choose Create LDP Tunnel Interface from the menu.

      LDP tunnel interfaces can be created using the system address or any local interface address on the root node.

      An LDP tunnel can be created on intermediate nodes (that is, between direct and indirect nodes).

    2. Configure the parameters as required.

      Note:

      When the Root Node parameter is enabled, the LDP tunnel interface you are creating is associated with a root node, and you must specify a unique P2MP ID and Sender Address.

      When the Root Node parameter is not enabled, the LDP tunnel interface you are creating is associated with a leaf node, and you must specify the same P2MP ID and Sender Address as the root node.

      The 7450 ESS only supports LDP tunnel interfaces in Mixed Mode.

      You must enable the OAM Test Root Node parameter to add an interface to an OAM test suite or to create a P2MP LSP Ping test.

    3. Click Apply. The LDP Tunnel Interface (Create) form is refreshed.

    4. Save and close the form or proceed to the next sub-step if required.

  2. Add the interface to an OAM test suite if required.

    Perform the following steps:

    1. Click on the OAM tab and click Add on the Test Suite tab to assign the interface to an OAM test suite. The Select Test Suite form opens.

    2. Click Search and choose the appropriate test suite. See To create an STM test suite for information about how to configure an OAM test suite.

    3. Save the form or proceed to the next sub-step if required.

  3. Create a P2MP LSP Ping test if required.

    Perform the following steps:

    1. Click on the P2MP LSP Ping tab and click Create or select an existing P2MP LSP Ping test and click Properties. The P2MP LSP Ping form is displayed. See To create and run a MPLS P2MP LSP ping OAM diagnostic test from the STM to complete the P2MP LSP Ping test configuration.

    2. Save and close the form or proceed to the next sub-step if required.

  4. Click on the Test Entity Results tab and click Search to view the results of the OAM test suite or P2MP LSP Ping test execution if required.

22 

Click on the Multi-Homing Interface tab if required, to view or create multi-homing interface entries assigned to the routing instance. The Multi-Homing Interface is a loopback interface used in multi-homing resiliency for a pair of protected routers. When active, the Primary interface can be used to advertise reachability information of the alternate router to the rest of the network. The Secondary interface is used to resolve routes advertised by the alternate router in the event that router becomes unavailable. This mechanism applies to both IP and VPN traffic.

Note: You can alternatively create a multi-homing interface by right-clicking on a routing instance icon in the navigation tree routing view and choose Create Multi-homing Interface from the menu.

Multi-homing interfaces are not supported on 7705 SAR-Hm.

Only one Primary and one Secondary multi-homing interface can be created for a router.

You can configure a multi-homing interface on the 7950 XRS, 7750 SR, and 7450 ESS (in mixed mode) network elements. Chassis mode “D” must be enabled.

  1. Click Create or select an existing Mult-Homing Interface and click Properties. The Mult-Homing Interface, (Create|Edit) form opens.

  2. Configure the parameters as required.

  3. Click on the Addresses tab and Click Create or select an existing IP address and click Properties. The IP Address, Routing Instance (Create|Edit) form opens.

  4. Configure the IP Address parameter.

    Note:

    Only IPv4 addresses are supported when creating the multi-homing interface.

  5. Save and close the forms. The Routing Instance form reappears.

23 

Click on the Route Aggregation tab if required, to view or configure route aggregates that can be generated into the virtual router on the routing instance.

Perform the following steps:

  1. Click Create or select an existing route aggregation and click Properties. The Aggregation (Create|Edit) form opens.

  2. Configure the parameters as required.

  3. Save your changes and close the form.

24 

Click on the BGP Confederations tab, if required to view or create BGP confederations on the routing instance. See To configure a BGP confederation to complete the BGP confederation configuration.

25 

Click on the Service Address Ranges tab if required to reserve one or more IP address ranges for use by services, such as IES.

Note: The service prefix configuration is not supported on SROS from NFM-P release 22.2 onwards. Thus, the Service Address Ranges tab will only be available on SROS in the NFM-P releases prior to 22.2.

Perform the following steps:

  1. Click Create or select an existing Service Address Range and click Properties. The Service Address Range (Create|Edit) form opens.

  2. Configure the parameters as required.

  3. Save your changes and close the form. The Routing Instance form reappears.

26 

Click on the GTP tab to configure S11 and uplink interfaces on the routing instance; see To configure GTP on a routing instance.

27 

Click on the WLAN GW Tunnels tab, if required to display WLAN GW Tunnel information from the operational channels after actual traffic passes through the routing instance. The tunnel is dynamically created by the NE to carry traffic from the access point to the WLAN-GW and terminates on the WLAN-GW ISA. The tunnel can be a GRE or VLAN type.

Perform the following steps:

  1. Click Resync WLAN GW Tunnels to retrieve the up-to-date tunnel information from the NE. A warning message displays.

  2. Acknowledge the warning message as required.

  3. Click Search to refresh the data.

28 

Click on the Source Address tab, if required to view or configure an override source IP address or L3 interface for use by a selected IP application on the routing instance.

Perform the following steps:

  1. Click Create or select an existing Source Address and click Properties. The Source Address, (Create|Edit) form opens.

  2. Configure the parameters as required.

    Note:

    If you choose the Interface Index option for the Source Address Termination parameter, the router must have a L3 network interface or an IES L3 access interface previously created on the routing instance to proceed. Click Select to choose an interface. See To create an L3 network interface on a routing instance for information about how to configure a L3 network interface; see To configure an L3 access interface on an IES site for information about how to configure an IES L3 access interface.

    If you choose the IP Address option for the Source Address Termination parameter, you must enter a IPv6 address for the Source IP Address.

  3. Save your changes and close the form. The Routing Instance form reappears.

29 

Click on the Advertisement tab to configure RDNSS advertisement options, if required.

Perform the following steps:

  1. Click Create or select an existing entry and click Properties. The DNS Options form opens.

  2. Configure the required parameters.

  3. Save your changes and close the form.

30 

Click on the Local DHCP server tab if required, to view a list of DHCPv4 or DHCPv6 servers assigned to the routing instance or click Create to configure a new server. See To configure a local DHCPv4 server on a routing instance or To configure a local DHCPv6 server on a routing instance to complete the configuration.

31 

Click on the RADIUS tab and the appropriate sub-tab as required, to view or create a new RADIUS server or a RADIUS proxy server assigned to the routing instance. See To configure a RADIUS server on a routing instance or To configure a RADIUS proxy server on a routing instance to complete the configuration.

32 

Click on the PCP Servers tab if required, to view or create a PCP server assigned to the routing instance. See To configure a NAT PCP server on a base routing instance to complete the configuration.

33 

Click on the PCEP PCC tab if required, to view or configure PCEP PCC attributes. See To configure a PCEP PCC to complete the configuration.

34 

Click on the SR Prefix SID tab if required, to configure a node SID.

Perform the following steps:

  1. Click Create or select an prefix SID and click Properties. The Segment Routing Prefix SID (Create|Edit) form opens.

  2. Configure the required parameters.

  3. Save your changes and close the form.

35 

Click on the Seamless BFD tab if required, to view or configure Seamless BFD peers. See To configure Seamless BFD to complete the configuration.

36 

Click on the IPSec Security Policies tab if required, to view or create VSR or 7705 SAR-Hm IPSec Security Policies.

Perform the following steps:

  1. Click Create or select an existing IPSec Security policy and click Properties. The IPSec Security policy (Create|Edit) form opens.

  2. Configure the required parameters.

  3. Click on the IPsec Security Policy Entries tab, and add one or more security policy entries.

    Use the following steps:

    1. Click Create. The Security Policy Entry (Create) form opens.

    2. Configure the Entry ID parameter.

    3. Configure the parameters in the Local IP Address panel.

    4. Configure the parameters in the Local IPv6 Address panel.

    5. Configure the parameters in the Remote IP Address panel.

    6. Configure the parameters in the Remote IPv6 Address panel.

    7. Save your changes and close the form.

37 

Click on the Origin Validation tab if required, to view or create a new RPKI session for BGP SIDR prefix origin validation assigned to the routing instance. See To configure BGP SIDR prefix origin validation for additional information about configuring BGP SIDR prefix origin validation.

Perform the following steps:

  1. Click Create or select an existing RPKI Session and click Properties. The RPKI Session, Site (Create|Edit) form opens.

  2. Configure the parameters as required.

  3. Click on the Static Routes tab to assign a cache server IP address and click Create. The Origin Validation Static Route Entry form opens

    Note:

    A static VRP entry is only configurable on a base router instance.

  4. Configure the parameters as required.

  5. Save your changes and close the form. The Routing Instance form reappears.

38 

Click on the Mcast Path Mgmt Channel tab if required, to display the data from the operational channels after actual traffic passes through the virtual router/routing instance from a specific multicast source for a specific multicast group. You must click Search to refresh the data. See To view the operational multicast channel properties of an MDA for additional information about how to view the operational multicast channel properties of an MDA.

39 

Click on the Self Generated Traffic tab if required, to configure QoS for SGT. See To configure QoS for self-generated traffic on a routing instance.

40 

Click on the Statistics tab if required, to collect and view performance statistical information about the routing instance for example, routing, DHCPv6 drop, or virtual router ICMPv6 in/out statistics. See the NSP NFM-P Statistics Management Guide for general information about configuring and collecting statistics.

41 

Click on the Deployment tab if required, to monitor the deployment status of the routing instance. See To monitor the deployment status of a network object for information about monitoring the deployment status of a network object.

42 

Click on the Faults tab if required, to view the routing instance alarm information such as the object alarms, affecting alarms, aggregated alarms, and related object alarms.

43 

Click on the Delay Metric tab if required, to associate a link measurement template.

44 

Save your changes and close the form.

End of steps