Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Deployment Precautions
- If a network device needs to be managed by iMaster NCE-Campus again (for example, by a new iMaster NCE-Campus controller), you typically need to run the reset saved-configuration command to clear device configurations. For S series switches, running this command clears only the configuration files saved on them, which may cause re-management exceptions. For example, you cannot STelnet to a network device through iMaster NCE-Campus. In this scenario, run the reset netconf db-configuration command to clear the configuration files and database information saved on the network device.
- After iMaster NCE-Campus delivers fabric configurations to network devices, you can view the fabric configuration status on iMaster NCE-Campus. If the configuration status is displayed as failed, locate and rectify the fault until the configuration status is displayed as successful.
- After a network device comes online on iMaster NCE-Campus, if an Eth-Trunk interface is added to the network device through the CLI, you need to synchronize the interface setting on iMaster NCE-Campus. The configuration procedure is as follows:
- Choose . On the Device Management tab page, click the desired network device to access the management portal.
- Choose Basic Information > List, select the Eth-trunk interface to add, and click Synchronize.
- In a faulty device replacement scenario, if the original device is connected to an upstream device through an Eth-Trunk, the new device can go online on iMaster NCE-Campus through the following methods:
- Onboard the new device using a single physical link and restore the Eth-Trunk after the new device comes online.
- Enable the Eth-Trunk auto-negotiation function on the Eth-Trunk interface of the upstream device.
- Run commands on the new device to configure the required Eth-Trunk interface before onboarding the new device.
- If aggregation or access switches at a site are deployed in such a way that preset network plan data of the switches is imported to the site before they are brought online on the controller, the Eth-Trunk interfaces on upstream devices are preconfigured with the Eth-Trunk auto-negotiation function by default after the Eth-Trunk information is imported to the site using the network plan import template. This is to ensure that downstream devices can go online on iMaster NCE-Campus through Eth-Trunks.
- In the virtualization solution, if standalone WACs connect to a core switch in off-path mode on the WLAN, the direct link between the master and backup WACs deployed in VRRP hot standby (HSB) mode must be used as the link for VRRP packet forwarding.
- You need to disable Auto Permit on Uplink Interface when configuring the management VLAN auto-negotiation function if this is the following case: parameters are configured on the uplink interface of a device using the local CLI or web system before configuring the management VLAN auto-negotiation function, for example, running the command for connecting an uplink interface of the core switch to iMaster NCE-Campus.
- In the centralized gateway scenario of the virtualization solution, if the native WAC is used, you can configure required authentication profiles on the Site Configuration tab page of iMaster NCE-Campus and deliver them to the native WAC. In this case, the authentication domain names bound to the authentication profiles are automatically generated.
- APs may have different PKI certificates due to different delivery time. As a result, APs may use different port numbers to report performance data. If some APs on the network cannot report performance data to iMaster NCE-Campus or iMaster NCE-CampusInsight, run the display pki certificate local realm default command to check whether the local certificate information is Issuer: C=CN, O=Huawei, CN=Huawei Enterprise Network Product CA.