Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring Inband Management with Static Routing

 

Use this procedure to set up static inband management, including specifying which OSC channels are used to carry management traffic and configuring the static routes required to route the traffic.

Note

Static inband management is supported starting with release 2.1.1.

Prerequisites

  • The ROADM network and OSC channels have been set up. See ROADM Solutions.

  • The overlay management network has been designed. This design involves specifying which links in the optical network carry management traffic, and how management traffic is routed. It also identifies the BTI7800 acting as the gateway between the inband and out-of-band management networks.

When configuring default routes, be aware of the following:

  • The default gateway specified by the system gateway-address command refers to a gateway reachable through the management Ethernet interface only (eth1). This is typically set only on the gateway NE.

  • The metric specified by the system gateway-metric command refers to the metric for the above default gateway. When you set a default route using the mgt static command, ensure that both this metric and the metric specified in the mgt static command are set according to which default route/gateway you want to take precedence.

  • Ensure the subnet length is set correctly when configuring the shared IP management address in a network where all NEs are in the same management subnet. On non-gateway NEs, the subnet length should be set to /30.

  1. Enter configuration mode.
    bti7800# config
  2. Display the OSC channels on the NE.

    For example (output truncated for clarity):

    bti7800(config)# do show dol osc
  3. Create a virtual management interface.
    bti7800(config)# interface mgt:1 type virtual
  4. Associate the virtual management interface to an OSC interface.

    The OSC interfaces to associate are typically the OSC line interfaces that lead to other BTI7800s that you want to manage.

    bti7800(config-interface-mgt:1)# l1-interface osc:1/5/0/L1
  5. Repeat step 3 and step 4 for each OSC interface carrying management traffic.

    Use a different mgt interface each time. For example:

    bti7800(config)# interface mgt:2 type virtual

    A maximum of 20 mgt interfaces can be created on the system.

  6. Specify the static and default routes in the overlay management network.

    Set up routes for each mgt interface. For example:

    bti7800(config)# mgt static 10.1.1.100/32 interface mgt:1
  7. Repeat step 6 until all static and default routes are defined for all mgt interfaces in the system.
  8. If the NEs in the inband network are on the same subnet, enable proxy ARP on the gateway BTI7800. The gateway BTI7800 is the NE that routes traffic between the management Ethernet interface and the inband network.

    For example, on the gateway NE:

    bti7800(config)# system proxy-arp enable

    By enabling proxy ARP, the gateway NE responds to ARPs on the management Ethernet interface on behalf of the NEs in the inband management network.

  9. Use show commands to verify your configuration.
    1. To show the management interface, use the show interface mgt: n command.

    2. To show the management static routes, use the show mgt static command.

    3. To show the management interface statistics, use the show interface virtual counters command.

If you need to change the shared management IP address, see Configuring the Shared Management IP Address and Subnet.

Configuration Example: Static Inband Management (Same Subnet)

This section contains a configuration example for setting up an inband management network where all network elements are in the same management subnet.

Figure 1 shows a 4-node optical network where the NE at 10.1.1.112 acts as the gateway between the external management network and the inband management network.

Figure 1: Static Inband Management Network (Same Subnet)
Static Inband Management Network (Same Subnet)

NE at 10.1.1.112:

NE-112# show running-config system

NE at 10.1.1.122:

NE-122# show running-config system

NE at 10.1.1.132:

NE-132# show running-config system

NE at 10.1.1.142:

NE-142# show running-config system

Configuration Example: Static Inband Management (Different Subnets)

This section contains a configuration example for setting up an inband management network where all network elements are in different subnets.

Figure 2 shows a 4-node optical network where the NE at 10.1.1.112 acts as the gateway between the external management network and the inband management network.

Figure 2: Static Inband Management Network (Different Subnets)
Static Inband Management Network (Different Subnets)

Router:

  • The router must be configured with static routes to 10.1.2.122, 10.1.3.132, and 10.1.4.142.

NE at 10.1.1.112:

NE-112# show running-config system

NE at 10.1.2.122:

NE-122# show running-config system

NE at 10.1.3.132:

NE-132# show running-config system

NE at 10.1.4.142:

NE-142# show running-config system
Release History Table
Release
Description
Static inband management is supported starting with release 2.1.1.