Creating a Site
- Create a site.
- Choose Create and set parameters as prompted. from the main menu. On the page that is displayed, click
- Set the site name to test_ap and set Device type to AP.
- Click OK.
- Repeat the preceding steps to create site 2 test_mix and set Device type to FW and LSW.
- After Device type is set, you can only add device types but cannot replace device types. For example, if only APs are deployed at a site, you can add firewalls to the site. However, you cannot change a site that contains only APs to a site that contains only firewalls. When the LSW is used as the WAC, you need to select both LSW and WAC.
- When creating a site, you can select Clone from an existing site to clone the configuration of a site for use with the new site, reducing repeated configurations. Currently, this function is available for the following features: Domain name, time zone, NTP, SNMP, local account, login restriction, TACAS, LLDP, HTTP service, public key-free upon first authentication of SSH client, STA location information reporting, AP identity key, IPv6, NETCONF, global CLI, global security compliance, global NAT (FW), ASPF, DNS, VLANIF (local Internet access), global interface management, SSID, global radio, Portal authentication, security policy, traffic policy, authentication and authorization policy, online control policy for users, portal page pushing rule, monitoring configuration, OUI for voice devices, VLAN information, wireless security, attack defense, global IoT, Bluetooth, DHCP, storm suppression, MAC blacklist/whitelist, NAT logging, and SA upgrade policy.
- Add devices.
On the tenant network site, you can use the CloudCampus APP to record the ESNs of cloud-managed devices on iMaster NCE-Campus. In this case, skip this step.
- Choose .
- On the Device Management tab page, click Add Device.
- Select Manually add. This mode applies to scenarios where a small number of devices at the same site need to be added.
- Set the protocol type to NETCONF protocol.
- Select the name of an existing site.
- Select Device Model to add devices.
- In the Device information area, click Add, set the type, model, quantity, and role, and then click OK.
- In the device list, enter device ESNs, and click OK.
- If Device Model is selected for device addition, the devices can go online after their ESNs are entered.
- If a device cannot be added because its ESN is occupied, contact the system administrator or MSP administrator to delete the device ESN.
- Click OK. For a device that has gone online, you can click its name to view the device status. In addition, you can also reboot the device or access its CLI through the controller.
- Create a stack.To manage a stack on the live network on iMaster NCE-Campus, you need to set up the stack locally using commands and then create the stack on iMaster NCE-Campus. The procedure is as follows:
- Choose .
- Click the Device Group tab, click Stack, and then click Create Stack.
- Enter Stack name and select the site where the stack is located.
- Set Stack Role. The role configured here is the same as that configured when devices are added.
- Set the mode for adding stack member devices.
- Synchronize from detected stacks: The system automatically detects the stacks that have been set up on devices. You need to manually add member switches to a stack.
- Manual creation: Click Add to add devices to the stack.
- Only switches of the same series can form a stack.
- All the switches that need to set up a stack must be added to the stack before they go online. Otherwise, the stack may fail to go online.
- (Optional) Click
of a device in the Member list to adjust the slot ID and priority. Click
to save the modification.
The slot ID is in the range from 0 to 8 and cannot be the same as that of any member device in the stack. The slot ID of a stack consisting of modular switches can be 1 or 2.
The priority is in the range from 1 to 255 and the default value is 100. A larger value indicates a higher priority.
If switches have set up a stack and have services configured, it is recommended that the slot IDs and priorities of stack members specified on iMaster NCE-Campus be the same as those configured on the stack members. Otherwise, iMaster NCE-Campus redelivers the slot IDs and priorities, which results in a stack restart. You can run the following commands to check original stack information:
Run the display esn command to check the ESNs and the corresponding slot IDs of member switches.
For a stack of fixed switches, run the display stack command to check the stack priorities and corresponding slot IDs of member switches.
- Click OK.
- When a stack goes online, iMaster NCE-Campus checks the status of the member switches in the stack, and delivers configurations only after all the member switches in the stack go online. This prevents the configuration delivery failure in the scenario where some member switches go offline.
- If one of the member switches in a stack goes offline after the stack goes online, the stack configuration cannot be performed.
- After a stack goes online, a member switch on which an uplink interface of the stack resides is removed from the stack and then added to the stack again. In this case, if the slot number of the member switch is changed, the member switch may fail to go online. To ensure that other member switches in the stack can go online, the stack must have other available uplinks before this member switch is removed from the stack.
- When a master/standby switchover occurs in a stack, the member switches in the stack will go online again.