Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring Inband Management with Dynamic Routing

 

Use this procedure to set up dynamic inband management, including specifying which ODCC channels are used to carry management traffic, and configuring IS-IS on a BTI7800.

Note

Dynamic inband management is supported starting with release 4.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 dynamic inband management, be aware of the following:

  • As a gateway in a dynamic inband management network, the BTI7800 supports the following:

    • A maximum of 64 nodes

    • Only one Network Entity Title (NET)

    • A maximum of 20 neighbors/interfaces

    • A maximum of 1000 routes

    • A maximum of 1000 entries in the IS-IS database

  • 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 is usually 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 the ODCC channel on 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 channel ODCC
  5. Repeat step 3 and 4 for each OSC interface carrying management traffic.

    Use a different virtual management interface each time. For example:

    bti7800(config)# interface mgt:2 type virtual

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

  6. 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.

  7. Configure and enable IS-IS on the gateway BTI7800.

    A NET is required when specifying the gateway BTI7800. For example, on the gateway NE:

    bti7800(config)# router isis 1 net 49.0001.0000.0000.1111.00 administrative-status up
    Note

    Enabling IS-IS on the gateway BTI7800 automatically enables IS-IS on each virtual management interface created at step 3 and provisions the sysmgt interface (eth1). The sysmgt interface cannot be disabled or removed after IS-IS is provisioned on the gateway BTI7800.

  8. Enable IS-IS on the eth1 interface.
    bti7800(config)# system mgmt dynamic
  9. Use show commands to verify your configuration.
    1. To show the virtual management interface, use the show isis interface detail command.

    2. To show the current routes, use the show ip route command.

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

    4. To show the management interface statistics, use the show isis counters command.

Configuration Example: Dynamic Inband Management (Same Subnet)

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

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

Figure 1: Dynamic Inband Management Network (Same Subnet)
Dynamic 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.133:

NE-133# show running-config system

Configuration Example: Dynamic 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 3-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: Dynamic Inband Management Network (Different Subnets)
Dynamic Inband Management Network (Different Subnets)

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
Release History Table
Release
Description
Dynamic inband management is supported starting with release 4.1.