Configuring Device Management

Context

On a large or midsize campus network, the core switch needs to interconnect with iMaster NCE-Campus for management through commands. Figure 4-5 shows the data for configuring the interconnection.

Figure 4-5 Interconnection between the core switch and iMaster NCE-Campus

• Ensure that the IP address of the interface connecting the core switch to iMaster NCE-Campus is in a different network segment from the southbound network plane of iMaster NCE-Campus.
• Ensure that the route for mutual communication between the core switch and iMaster NCE-Campus has been configured. The following configuration example does not provide the route configuration.

Procedure

1. Configure the VLAN and interface address for connecting the core switch to iMaster NCE-Campus.

   <Core> system
   [Core] vlan batch 4080
   [Core] interface gigabitethernet 1/2/0/1
   [Core-GigabitEthernet1/2/0/1] port link-type trunk
   [Core-GigabitEthernet1/2/0/1] port trunk allow-pass vlan 4080
   [Core-GigabitEthernet1/2/0/1] quit
   [Core] interface vlanif 4080
   [Core-Vlanif4080] ip address 192.168.0.1 24
   [Core-Vlanif4080] quit

2. Configure the core device to be managed by iMaster NCE-Campus through NETCONF in either of the following ways:
   • Call Home mode

     [Core] netconf
     [Core-netconf] source ip 192.168.0.1
     [Core-netconf] callhome imaster-campus
     [Core-netconf-callhome-imaster-campus] ip address 192.168.10.10 port 10020   //  iMaster NCE-Campus communicates with the core switch using NETCONF through the fixed port number 10020.
     [Core-netconf-callhome-imaster-campus] quit
     [Core-netconf] quit

   • Management VLAN

     [Core] netconf
     [Core-netconf] management-vlan 4080
     [Core-netconf] controller ip-address 192.168.10.10 port 10020
     [Core-netconf] quit

Context

To manage a native WAC on iMaster NCE-Campus, simply ensure that the switch integrating the native WAC function is managed by iMaster NCE-Campus.

To manage a standalone WAC on iMaster NCE-Campus, you need to configure the interconnection between them using commands. Figure 4-6 illustrates the interconnection between standalone WACs and iMaster NCE-Campus.

Figure 4-6 Interconnection between standalone WACs and iMaster NCE-Campus

• Ensure that the IP address of the interface that connects the standalone WAC to iMaster NCE-Campus is in a different network segment from the southbound network plane of iMaster NCE-Campus.
• Ensure that the route for mutual communication between the standalone WAC and iMaster NCE-Campus has been configured. The following configuration example does not provide the route configuration.
• If two standalone WACs work in hot standby (HSB) mode to ensure wireless service reliability, the standby standalone WAC also needs to be configured to connect to the southbound network plane of iMaster NCE-Campus. This approach is to ensure that the new active standalone WAC can be managed by iMaster NCE-Campus after an active/standby switchover.

Procedure

1. Configure the active device WAC 1 to be managed by iMaster NCE-Campus by configuring WAC 1 to work in cloud mode.

   [WAC1] ac-mode cloud
   [WAC1] cloud-mng controller ip-address 192.168.10.10 port 10020
   [WAC1] quit

2. Configure the standby device WAC 2 to be managed by iMaster NCE-Campus by configuring WAC 2 to work in cloud mode.

   [WAC2] ac-mode cloud
   [WAC2] cloud-mng controller ip-address 192.168.10.10 port 10020
   [WAC2] quit

Context

To onboard aggregation and access switches, it is recommended that the core switch that has been managed by iMaster NCE-Campus be used as the management subnet gateway of the aggregation and access switches.

• Enable the management VLAN auto-negotiation function, so that aggregation and access switches can obtain the management VLAN automatically after an auto-negotiated management VLAN is specified on the core switch.
• Enable the DHCP server function on the gateway interface of the management subnet on the core switch and configure DHCP Option 148 to carry the iMaster NCE-Campus address, so that the aggregation and access switches can be dynamically assigned management IP addresses and obtain the iMaster NCE-Campus address.
• In the centralized gateway solution, the core switch typically functions as the native WAC to manage APs. You can configure DHCP Option 43 to carry the WAC address. In this case, APs share the same management subnet with aggregation and access switches, and can be dynamically assigned management IP addresses and obtain the WAC address.

A large number of aggregation and access switches may need to be managed, and fixed management IP addresses may be required for accessing the aggregation and access switches during subsequent O&M. If this is the case, you can plan multiple management VLANs and management subnets as needed and configure static management IP addresses for aggregation and access switches after these switches come online through management VLAN auto-negotiation.

Configuration Tasks

Reference Links for iMaster NCE-Campus Operations

• Configuring a Management VLAN
• Configuring a Subnet
• Configuring Physical Interfaces