Tenant Administrator O&M
- Logging In to iMaster NCE-Campus as a Tenant Administrator
- Homepage Management
- License Management
- Viewing License Information (Global Perpetual Mode)
- Viewing License Information (Global Subscription Mode + License Redistribution Enabled)
- Viewing License Information (Tenant Subscription Mode + License Redistribution Enabled)
- Activating and Authorizing Licenses (Tenant Subscription Mode + License Redistribution Disabled)
- Authorizing an MSP to Maintain Tenant Services
- User Account Management
- Device Management and Maintenance
- Viewing and Exporting Device Information
- Device Management Settings
- Creating an Automatic Discovery Task
- Synchronizing Device Information to the Registration Center
- Changing the Administrator Password and BootROM Password of Devices at New Sites
- Changing the Administrator Password and BootROM Password of Devices at Existing Sites
- Enabling or Disabling Local CLI-based Device Configuration
- Restarting a Device Within One Click
- Viewing WAC Group Information
- Replacing a Device
- Device Upgrade
- Restoring Devices to Deployment Configurations Within One Click
- Restoring Devices to Factory Defaults Within One Click
- Viewing AP Login and Logout Logs
- Replacing Device Certificates
- Changing the Device Time
- Remotely Logging In to the Device CLI
- Logging In to a Device's Web System
- Upgrading the Signature Database on Devices
- Activating a Device License
- Delivering Commands to AP-IoT Devices
- Configuration File Management
- Fundamentals
- Backing Up Configuration Files
- Importing a Device Configuration File
- Exporting a Device Configuration File
- Restoring a Configuration File on a Device
- Configuring the Running Configuration as the Startup Configuration
- Configuring a Configuration File Backup Task
- Viewing Configuration Changes
- Configuring Backup Parameters
- SNMP-Managed Device Management and Maintenance
- Configuring the CA Service
- Certificate Management
- Configuring Southbound FTP Parameters
- Configuring an Authentication Component
- Third-Party Server Configuration
- Configuring an SMS Server
- Configuring Interconnection with a Syslog Server
- Configuring Interconnection with a DNS Server
- Configuring Interconnection with a File Server
- Managing Notified Users
- Configuring Terminal Data Reporting
- Configuring Devices to Report Logs to the Syslog Center
- Interconnecting with an HWTACACS Server
- Synchronizing Data to iMaster NCE-CampusInsight
- Configuring Data Reporting
- Alarm Management
- Configuring Alarm or Event Rules
- Configuring a Masking Rule
- Configuring Severity and Type Redefinition Rules
- Configuring Name Redefinition Rules
- Synchronizing Alarms
- Configuring Correlation Rules
- Configuring Intermittent/Toggling Alarm Handling Rules
- Configuring Auto Acknowledgement Rules
- Configuring Alarm or Event Name Groups
- Customized Monitoring
- Monitoring and Viewing Alarms or Events
- Handling Alarms
- Configuring the Email Notification Function for Alarms
- Configuring Alarm or Event Rules
- Log Management
- File Management
- Viewing Configuration Results
- Device Monitoring
- Terminal Monitoring
- Service Quality Monitoring
- WLAN Management
- Fault Detection and Location
- Report
- Viewing the URL Auditing Result
- Issuing Commands Using a Template
Logging In to iMaster NCE-Campus as a Tenant Administrator
Context
A tenant administrator can use a browser to log in to iMaster NCE-Campus to perform system management and maintenance operations. The following web browsers are supported:
- Google Chrome 57 or later
- Microsoft Edge 20 or Microsoft Edge 40
Procedure
- Open a browser.
- Enter https://iMaster NCE-Campus server IP address:port number in the address box, and press Enter.
- The IP address of the iMaster NCE-Campus server is Northbound management IP specified when you install iMaster NCE-Campus.
- The port number is 18008. The port number used for the login must be the same as that specified during the installation.
- The method for logging in to an authentication component is the same as that for logging in to iMaster NCE-Campus.
- Ignore the security certificate warning and access the login page.
When you log in to iMaster NCE-Campus using a browser, the browser performs unidirectional authentication on iMaster NCE-Campus based on the ER certificate. The Huawei ER certificate has been pre-configured during iMaster NCE-Campus installation. This certificate is used only for temporary communication and is not for commercial use. You can apply for a new ER certificate to update the preconfigured ER certificate to improve iMaster NCE-Campus communication security. You are advised to periodically update the certificate to prevent system security risks caused by certificate expiration. After the ER certificate is updated, the message indicating a security certificate error will not be displayed.
- Google Chrome: Choose Advanced > Proceed to ... (unsafe).
- Google Chrome: Choose Advanced > Proceed to ... (unsafe).
- Enter a tenant administrator username and password, and click Log In.
- (Optional) Upon the first login, change the password as prompted. Skip this step if it is not your first login.
- For security purposes, do not save your password in the browser.
- If the system administrator has configured an email server and the MSP administrator does not set an email address for the tenant administrator during tenant account creation, an email address needs to be bound to the tenant administrator account upon the tenant's first login.
- If the system administrator has not configured an email server, no email address needs to be bound to the tenant administrator account upon the tenant's first login.
- When a sub-tenant administrator account created by the root tenant administrator logs in to iMaster NCE-Campus for the first time, no email address needs to be bound to the sub-tenant administrator account.
- (Optional) Perform two-factor authentication. If a mobile number has been set for the tenant administrator account, click Obtain Verification Code and enter the received verification code. You can log in to iMaster NCE-Campus after the verification succeeds. This step is not required if username and password authentication is selected when the MSP administrator creates the tenant administrator.
- (Optional) Sign the privacy statement.
If the MSP administrator selects a privacy statement when creating a root tenant administrator, the root tenant administrator needs to sign the privacy statement when logging in to iMaster NCE-Campus for the first time. Otherwise, the login will fail.
If the root tenant administrator has signed the privacy statement, the sub-tenant administrators created by this root tenant administrator need to sign the privacy statement as well when logging in to iMaster NCE-Campus for the first time. Otherwise, the login will fail.
- (Optional) Set a device administrator password and a password used to enter the BootROM menu of devices on iMaster NCE-Campus. This step is required only upon your first login.
After a device goes online at a new site, the two passwords set here will automatically apply to the device. This ensures device security.
If the system administrator disables The device BootROM password can be configured, tenants cannot change the BootROM password. For details about how to disable tenants from changing the BootROM password, see Configuring a BootROM Password Policy.
Homepage Management
Homepage Overview
Context
After logging in to iMaster NCE-Campus for the first time, a tenant administrator can configure services through Typical Application Scenarios or General Process Entry.
Procedure
- Log in to iMaster NCE-Campus as a tenant administrator.
- On the homepage, you can view device go-online and go-offline logs, user online duration, and feature configuration status. In addition, you can configure services as needed using Deployment Scenario and Auxiliary Tools.
- Select a scenario in the Deployment Scenario area as required. Then you can configure services step by step on the displayed page.
- Click the Smart configuration tool icon to access the command configuration tool. For details about how to use this tool, see Command Configuration Tool.
- Select a scenario in the Deployment Scenario area as required. Then you can configure services step by step on the displayed page.
Customizing the Monitoring Dashboard
Context
A tenant administrator can customize the monitoring information displayed on the
page.Procedure
- Choose from the main menu.
- Click
in the upper right corner.
- Click portlets to customize the information displayed on the Overview page or cancel previous customizations. If
is displayed in the lower-right corner of a portlet, the corresponding information will be displayed on the Overview page. If
is not displayed, the portlet information will not be displayed on the Overview page.
The dark area can be customized to display the site status, terminal packet loss rate, and AQM distribution, whereas the light area can be customized to display the map, trend of online Wi-Fi users, device status, worst 5 applications by AQM, worst 5 links by LQM, top 5 applications by traffic, top 5 links by traffic, abnormal cloud managed devices, alarms, task information and site signing information.
Viewing Monitoring Dashboard Information
Procedure
- Log in to iMaster NCE-Campus as a tenant administrator.
- Choose from the main menu.
- Check the site status, terminal packet loss rate, and AQM distribution.
- View site distribution and status on the map.
- Select one or more values from the Status drop-down list box in the upper left corner to filter sites by status.
- Click a site icon to view the status of devices at the site.
- Select one or more values from the Status drop-down list box in the upper left corner to filter sites by status.
- Check the trend of online Wi-Fi users, device status, worst 5 applications by AQM, and worst 5 links by LQM.
- Check the top 5 applications by traffic, top 5 links by traffic, and abnormal devices.
- Check alarms, tasks, and site signing information.
Configuring a Map URL
Context
If site locations are identified on a map, iMaster NCE-Campus can display monitoring data of each site on this map. Currently, iMaster NCE-Campus supports Amap and Google Maps. To implement the map function, you need to purchase a license, obtain the API address, and configure the map URL.
After purchasing the map service, a tenant administrator can configure the map URL independently.
The map URLs configured by the tenant administrator, MSP administrator, and system administrator take effect in descending order of priority. For example, if the system, MSP, and tenant administrators each have configured a map URL, the URL configured by the tenant administrator is used preferentially.
Prerequisites
Related services have been purchased from the map service provider and the API address and key of the map have been obtained.
Procedure
- Choose from the main menu.
- Access the Map Settings page to configure a map URL.
- If neither the system administrator nor the MSP administrator has configured a map URL, click Configure Map. On the Basic Settings page, set API address and Key, select Instructions for Use, and click Next Step.
- If the system administrator or MSP administrator has configured a map URL, click
to change the values of API address and Key, select Instructions for Use, and click Next Step.
- If neither the system administrator nor the MSP administrator has configured a map URL, click Configure Map. On the Basic Settings page, set API address and Key, select Instructions for Use, and click Next Step.
- Access the Setting the view angle page.
- If Default viewing angle is set to All Sites, you can view locations of all sites on the map by default after logging in to iMaster NCE-Campus.
- If Default viewing angle is set to Customize, you can set a viewing angle. After the configuration is complete, you can view locations of the sites in the custom viewing angle on the map by default after logging in to iMaster NCE-Campus.
- If Default viewing angle is set to All Sites, you can view locations of all sites on the map by default after logging in to iMaster NCE-Campus.
- Click OK.
Google Maps Key Application Procedure
- Access the Google Maps official website at https://developers.google.com/maps/documentation/javascript/get-api-key.
- Register a Google account and log in.
- Create a Google Maps project.
- Choose Set up in Cloud Console from the navigation pane. Under Creating a project, click Create new project.
- Enter project information and click CREATE to create a project.
- Choose Set up in Cloud Console from the navigation pane. Under Creating a project, click Create new project.
- Apply for an API key.
- Choose Set up in Cloud Console from the navigation pane. Under Enabling APIs, click Enable the Maps JavaScript API.
- Select the created project and click ENABLE to enable the Maps JavaScript API function.
- On the Credentials tab page, click CREATE CREDENTIALS and click API key.
- Obtain the API key.
- Choose Set up in Cloud Console from the navigation pane. Under Enabling APIs, click Enable the Maps JavaScript API.
- (Optional) Remove the Google Maps watermark.
There is a watermark on Google Maps by default. You need to pay fees if you want to remove the watermark from the map.
- Choose Set up in Cloud Console from the navigation pane. Under Creating budgets and setting alerts, click Go to the Billing page.
- Click ADD BILLING ACCOUNT.
- Enter personal information.
- Click START MY FREE TRIAL.
- Choose Set up in Cloud Console from the navigation pane. Under Creating budgets and setting alerts, click Go to the Billing page.
Parameter Description
Parameter |
Description |
---|---|
API address |
Map URL.
|
Key |
Key applied for from the map service provider. |
License Management
License Mode |
License Redistribution |
Application Scenario |
Role |
Operation |
---|---|---|---|---|
Global permanent |
Not supported |
On-premises scenario |
System administrator |
Import license files of iMaster NCE-Campus and iMaster NCE-CampusInsight. |
MSP administrator |
View the license information. |
|||
Tenant administrator |
View the license information. |
|||
Global subscription |
Disabled |
MSP-owned cloud scenario (MSP administrators do not need to centrally manage licenses.) |
System administrator |
|
MSP administrator |
N/A |
|||
Tenant administrator |
N/A |
|||
Enabled |
MSP-owned cloud scenario (MSP administrators need to centrally manage licenses.) |
System administrator |
|
|
MSP administrator |
Distribute licenses to tenant administrators. |
|||
Tenant administrator |
View the license information. |
|||
Tenant subscription |
Disabled |
Huawei public cloud Scenario (MSP administrators do not need to centrally manage tenant licenses.) |
System administrator |
Disable the license split function when creating an MSP administrator. |
MSP administrator |
Apply for license activation codes from the Electronic Software Delivery Platform (ESDP). |
|||
Tenant administrator |
Purchase license activation codes from MSPs, and import the codes to iMaster NCE-Campus and iMaster NCE-CampusInsight. |
|||
Enabled |
Huawei public cloud Scenario (MSP administrators need to centrally manage tenant licenses.) |
System administrator |
Enable the license split function when creating an MSP administrator. |
|
MSP administrator |
Apply for license activation codes from the ESDP, and import the codes to iMaster NCE-Campus and iMaster NCE-CampusInsight. |
|||
Tenant administrator |
View the license information. |
Viewing License Information (Global Perpetual Mode)
Context
If the system administrator has imported licenses, tenant administrators can view the license information.
Prerequisites
The system administrator has imported licenses.
Procedure
- Choose
to view detailed information about the license files that have been imported. from the main menu. Click
- Click the License Information tab to view the license information.
- Select NCE-Campus from the Product name drop-down list to view the detailed information about controller licenses.
- Select CampusInsight from the Product name drop-down list to view the detailed information about iMaster NCE-CampusInsight licenses.
- Select NCE-Campus from the Product name drop-down list to view the detailed information about controller licenses.
Viewing License Information (Global Subscription Mode + License Redistribution Enabled)
Context
For global subscription licenses, if an MSP has allocated license resources to tenants, the tenants can view their own license resource status and consumption information without the need to activate licenses.
Procedure
- Choose from the main menu, and view the license resource status and consumption information.
- Click Expiration Notification, enable Receive expiration notification, and configure the email addresses of recipients. Notification emails will be sent to the specified email addresses when a license is about to expire.
- The system administrator must configure an email server before enabling Receive expiration notification. Otherwise, Receive expiration notification cannot be enabled. For details, see Configuring an Email Server.
- A maximum of five email addresses can be configured. Email addresses need to be separated with line breaks.
- If a license resource item is about to expire in less than 30 days, the system will send notification emails at 02:25 every day.
- If license expiration notification is configured, the license expiration email is sent only to the email addresses specified in Notified object. In this case, you are advised to specify the email address of the tenant administrator in Notified object.
Viewing License Information (Tenant Subscription Mode + License Redistribution Enabled)
Context
For tenant subscription licenses, if an MSP has allocated licenses to tenants, the tenants cannot activate the licenses, but can only view the status and consumption information about the licenses.
Prerequisites
The MSP has allocated licenses to tenants. For details, see Activating and Allocating a License (Tenant Subscription Mode + License Redistribution Enabled).
Procedure
- Log in to iMaster NCE-Campus as a tenant administrator and choose from the main menu to view the license status and consumption information.
Activating and Authorizing Licenses (Tenant Subscription Mode + License Redistribution Disabled)
Context
If the system administrator does not enable the license split function when creating an MSP administrator, tenants need to purchase license activation codes from the MSP and import the activation codes to activate licenses.
- After logging in to iMaster NCE-Campus for the first time, the system administrator needs to set the license mode to Tenant Subscription Mode.
- This operation applies only to the Huawei public cloud scenario.
- Tenants purchase license activation codes from the MSP.
- Coding mode: 8806
- License consumption by time: After license expiration, iMaster NCE-Campus stops providing services.
- License form: Number of devices x Number of available days
- Example: A subscription license is similar to that of a monthly package. If a customer purchases a "10 device x day" license for S5700-LI series devices with 8 ports, one device of this model can be used for 10 days, two devices of this model can be used for 5 days, and so on. The total number of license units must be 10.
- Deduction time: The system deducts and settles license resources at 02:00 every day.
Prerequisites
- A tenant account has been registered.
- The tenant has logged in to iMaster NCE-Campus using the tenant account.
- The tenant has purchased license activation codes from the MSP.
- If the tenant needs to import activation codes of iMaster NCE-CampusInsight licenses through iMaster NCE-Campus, synchronize iMaster NCE-CampusInsight licenses to iMaster NCE-Campus before interconnecting iMaster NCE-Campus to CampusInsight. For details, see Configuring Interconnection with iMaster NCE-CampusInsight.
Procedure
- Choose from the main menu.
- Import either activation codes or entitlement IDs to activate licenses.
Since the first-time registration of a device, the device starts to consume license resources no matter whether the device is online or offline, or reports alarms. License deduction starts at 02:00 every day, and each device consumes one license unit every day.
If the tenant subscription mode is configured and license redistribution is disabled, iMaster NCE-Campus provides common series license resources of 90 days (can be shared between devices) by default.
- Click Import Activation Code.
- Multiple activation codes need to be separated with line breaks.
- A maximum of 10 activation codes can be entered.
- After configuring interconnection between iMaster NCE-Campus and iMaster NCE-CampusInsight, you can import activation codes of iMaster NCE-CampusInsight licenses to iMaster NCE-Campus.
- Click Import Auth ID.
- Multiple entitlement IDs need to be separated with line breaks.
- A maximum of 10 entitlement IDs can be entered.
- Click Import Activation Code.
- View the license status.
- (Optional) Click Recalculate Expiration Time and set a unified expiration time of license resources.
The function of recalculating the license expiration time is not applicable to common series resources.
Under a tenant, the expiration time of device licenses with the same device type is automatically recalculated when settlement is performed on a daily basis.
Under a tenant, the expiration time of device licenses with different device types is not automatically recalculated. To recalculate the expiration time of such licenses, perform this step.
This function allows you to configure a unified expiration time for resource items with different expiration time for easy management and resource integration. This operation cannot be rolled back.
For example, there are three types of license resource items, including AR100 series: 10 device-days with 5 RMB per device-day; AR1200 series: 20 device-days with 10 RMB per device-day; and indoor AP series: 20 device-days with 20 RMB per device-day. Assume that iMaster NCE-Campus manages five AR100 series devices and 10 AR1200 series devices. You can click Recalculate Expiration Time to integrate license resources. The formulas are as follows: 10 x 5 + 20 x 10 + 20 x 20 = 650, 5 x 5 + 10 x 10 = 125 (consumption of all devices in a day), 650/125 = 5 R 25 (remainder 25). According to the calculation result, the license resources for AR100 and AR1200 series devices will expire in five days. The remaining 25 RMB will be added to the new license resource pool to be integrated in the next calculation.
This function enables resource allocation to be more flexible. Resources that are in arrears can be integrated so that they can be used normally.
- Click Expiration Notification, enable Receive expiration notification, and configure the email addresses of recipients. Notification emails will be sent to the specified email addresses when a license is about to expire.
- The system administrator must configure an email server before enabling Receive expiration notification. Otherwise, Receive expiration notification cannot be enabled. For details, see Configuring an Email Server.
- A maximum of five email addresses can be configured. Email addresses need to be separated with line breaks.
- If a license resource item is about to expire in less than 30 days, the system will send notification emails at 02:25 every day.
- If license expiration notification is configured, the license expiration email is sent only to the email addresses specified in Notified object. In this case, you are advised to specify the email address of the tenant administrator in Notified object.
- Check the daily consumption of license resources.
- Click
to view the detailed information about license activation codes or entitlement IDs.
After a license is loaded successfully, you can view the software ID for SnS charging and authentication.
Authorizing an MSP to Maintain Tenant Services
After a tenant applies for managed services from an MSP, the MSP can directly maintain services of this tenant. If the tenant does not want an MSP to maintain tenant services or has authorized the MSP to maintain tenant services, skip operations in this section.
Prerequisites
You have logged in to iMaster NCE-Campus using a tenant account that authorizes an MSP to maintain tenant services.
Procedure
- Access the authorization information page.
Choose
from the main menu. - Enable Authorize MSP in the Authorization Information area and set the authorization scope.
- Authorize the MSP to manage tenant services based on the workgroup. The MSP administrator has the rights of the selected workgroups after logging in to iMaster NCE-Campus in MSP-operated mode.
- Authorize the MSP to manage tenant services based on the role. The MSP administrator has rights of the selected roles after logging in to iMaster NCE-Campus in MSP-operated mode.
- Authorize the MSP to manage tenant services based on the workgroup. The MSP administrator has the rights of the selected workgroups after logging in to iMaster NCE-Campus in MSP-operated mode.
User Account Management
Configuring Account Policies and Password Policies
Context
The system administrator has configured account policies and password policies. Tenant administrators can modify these policies as needed.
Procedure
- Configure account policies.
Account policies have been configured on iMaster NCE-Campus by default. Tenant administrators can modify the account policies, such as account length policy and account login policy.
Choose Account Policy, to configure account policies.
from the main menu, and click - Configure password policies.
Password policies have been configured on iMaster NCE-Campus by default. Tenant administrators can modify the password policies as needed, for example, password complexity requirements, the password change interval, and character limitations.
Choose Password Policy, to configure password policies.
from the main menu, and clickFor security purposes, configure all password policies provided by iMaster NCE-Campus.
If PCI authentication is required, modify account and password policies as follows:- Enable Disable unused accounts, and set Maximum number of consecutive idles days of account to 90. An account is disabled if the account has not logged in to the system at all for more than 90 days.
- Set Invalid password monitoring period (min) to 30 in the Account Lockout Trigger Conditions area. In this case, if an account fails to log in to the system for five consecutive times within 30 minutes, the account is locked for 30 minutes.
- Set Number of historical passwords that cannot be reused to 4.
Creating a User Role
You can create user roles as needed if default user roles preset in the system cannot meet your requirements.
Context
Users with the same operation rights can be managed by role. After an account is attached to a role, the account has all rights of this role.
Procedure
- Choose Role tab. from the main menu, and click the
- Click Create. Enter the role name and select function rights for the role.
By default, the following roles are preset for tenants. These roles cannot be deleted or modified.
- Monitor: A monitor can view tenant services and configurations.
- Open Api Operator: An open API operator can use open API services and related configurations.
- Tenant Administrator: A tenant administrator can perform operations on tenant services and related configurations.
- Operator: An operator can manage system service running.
The Operator role is unavailable for tenant administrators created on iMaster NCE-Campus running V300R019C00.
- CLI Operator: A user attached with this role has the permission to import device commands using a command template. For details, see Issuing Commands Using a Template.
Issuing commands is supported only on the WAN. The CLI Operator role is available only in EVPN tunnel mode.
In the Select function list, each function node has a fixed name but the node order in the list varies depending on the iMaster NCE-Campus version. Figures in this section are for reference only.
- You are advised to create roles and grant function rights based on the following table. You can also create roles as needed.
Role Type
Rights
Management
Global management personnel, with all rights.
Monitoring
Global monitoring personnel, with all monitoring rights.
Configuration
Network configuration personnel, with rights to configure the network, traffic policies, and security policies.
Maintenance
O&M personnel, with rights to maintain devices and manage files and logs.
- For a management role: Select all functions.
- For a monitoring role, select Monitoring and all functions under it.
- For a configuration role, select Design, Provision, System, Admission, Policy, ServiceConsisitency Group, along with all functions under them.
- For a maintenance role, select Maintenance and all functions under it.
- For a management role: Select all functions.
- Click OK.
Creating a Sub-Tenant Administrator Account
Context
A tenant administrator created by an MSP administrator has all rights of a tenant, and is called a root tenant administrator.
To ensure system security, the root tenant administrator can create multiple sub-tenant administrators and attach roles to each sub-tenant administrator so that the sub-tenant administrator can have corresponding rights of the roles.
A tenant administrator can set the maximum number of concurrent online users. The value ranges from 0 to 999. The value 0 indicates that the maximum number of concurrent online users is not limited. To ensure system performance, the maximum number of concurrent online users is limited to 5000.
Procedure
- Choose from the main menu.
- Click Create, and set parameters on the Create User page.
For security purposes, keep the password secure and change it periodically.
- Manually configure a password when creating an account.
Set Password create mode to Manual and then set a password for the account. If Modify password first login is set to Yes, the user will be prompted to change the password when using this account to log in to iMaster NCE-Campus for the first time, and can successfully log in after changing the password.
- Create a password via email.
Set Password create mode to Email. After the account is created, the system sends a URL to your email box. You can click the URL to configure a password for the user account.
- If you choose to configure a password via email, configure an email server before creating an account. Otherwise, the system fails to send a URL to the specified email address. For details, see Configuring an Email Server
- If the password for a user account is configured via email, the user does not need to change the password upon the first login to iMaster NCE-Campus.
Table 4-119 Description of parameters on the Create User pageParameter
Description
Account
User account used for login.
User type
The following two user types are available:
- Local: Local users can log in to iMaster NCE-Campus only from the web UI.
- Third-party user: A third-party system user can invoke the northbound API /controller/v2/tokens to log in to iMaster NCE-Campus.NOTE:
- A third-party user can log in to iMaster NCE-Campus only by invoking the API.
- A local user can log in to iMaster NCE-Campus only through the web UI.
- After an upgrade, local users and third-party users can log in to iMaster NCE-Campus either by calling the API or through the web UI.
Password create mode
Mode in which a password is created. The options are Manual and Email.
Password
Initial login password of the newly created administrator.
NOTE:- The two parameters are configurable only when User Type is set to Local.
- If Password create mode is set to Email, set a valid email address. After the account is created, the system sends a URL to the mailbox. The user can click the URL to configure a password.
- If Password create mode is set to Email, the user does not need to change the password when logging in to iMaster NCE-Campus for the first time.
Confirm Password
Modify password first login
Whether to change the password upon first login.
Email address
When resetting passwords, users can receive new random passwords generated automatically through emails.
Mobile number
When resetting passwords, users can receive new random passwords generated automatically through SMS messages.
Role
Role to be attached to the user.
- Manually configure a password when creating an account.
- On the Managed Object page, select the sites to be managed by the sub-tenant administrator, and click Next.
If a sub-tenant administrator is authorized to managed selected sites, the administrator cannot view the following menus after logging in to iMaster NCE-Campus since the administrator does not have the permission to manage all resources:
- (Optional) Configure access control.
On the Access Control page, click Create, configure the range of IP addresses that can be used to log in to iMaster NCE-Campus, and click Next.
- Click OK.
Follow-up Procedure
- Modify account information, reset the password, and disable or enable the account.
- Choose from the main menu.
- In the Operation column, click
to modify account information, click
to reset the password, or click
to disable the account. If the account has been disabled, click
to enable the account.
- Delete an account.
- Choose from the main menu.
- Select an account, and click Delete.
- Transfer workgroup administrator rights.
If the administrator of a workgroup is changed, an upper-level administrator can transfer the workgroup administrator rights to another administrator.
Workgroup administrators can transfer their rights only to the administrators created by themselves. Before transferring rights of a workgroup administrator, ensure that the workgroup administrator has created an administrator account.
- This operation can only be performed on level-1 sub-workgroups of the workgroup to which the current user belongs and cannot be performed on the workgroups of level 2 or higher.
- If workgroup administrators remain online after their rights are transferred, they will be forced offline and has no rights.
- Choose User tab. from the main menu. Click the
- Click Select, select the desired workgroup, and click OK.
Select a desired account and click Hand Over to enable this account to become the new workgroup administrator.
The new account must be an administrator account created by the old workgroup administrator account.
If the
icon is moved to the right of the new administrator account, the rights are transferred successfully.
- Configure a user group.
User groups are used to interconnect iMaster NCE-Campus with third-party services, such as the Active Directory Federation Services (ADFS), NetIQ, LDAP server, AD server, and RADIUS server.
Choose User Group tab, and click Create to create a user group.
from the main menu. Then, click theClick Next and select objects to be managed by the user group if Select all resources is disabled.
- Perform personalized settings.
Personalized settings improve iMaster NCE-Campus access security. The personalized settings apply only to the current tenant administrator account.
- Set the number of concurrent online users.
- Choose from the main menu.
- On the Basic Information tab page, click
and set Max. concurrent users. The value 0 indicates there is no limit on the maximum number of concurrent online users.
- Change the user password.
- Choose from the main menu.
- On the Basic Information tab page, click
next to the password. In the dialog box that is displayed, set a new password.
- Modify the IP address range that can be used by the current account to log in to iMaster NCE-Campus.
- Choose from the main menu.
- On the Access Control tab page, create Create, set a start IP address and an end IP address, and click OK. If the IP address range list is empty, login is allowed from any IP address.
- Set an idle timeout interval for the current tenant administrator account.
iMaster NCE-Campus supports the idle timeout interval setting to prevent unauthorized operations when the administrator is away. If an administrator does not perform any operation within a specified period of time, the administrator will be logged out automatically and needs to log in to iMaster NCE-Campus again.
Choose Idle Timeout Settings, set Idle duration (min), and click OK.
from the main menu, click - Check online users.
Choose Online User tab, and view online users.
from the main menu, click the
- Set the number of concurrent online users.
- Check whether you have signed a privacy statement.
- Choose from the main menu.
- On the Basic Information tab page, check whether you have signed the privacy statement.
- If Sign privacy statement is Not signed, you have not signed the privacy statement.
- If Sign privacy statement is Signed, you have signed the privacy statement.
- Withdraw a privacy statement.To withdraw your consent to the privacy statement, click Cancel next to Sign privacy statement and click OK in the Warning dialog box that is displayed.
You will be logged out if you withdraw the consent to the privacy statement. In addition, your mobile number and email address will be deleted. This may affect your login or password retrieval. Exercise caution when performing this operation.
Configuring an Authentication Mode for Tenant Administrators
When a tenant administrator logs in to iMaster NCE-Campus, iMaster NCE-Campus will authenticate the administrator in the following three modes.
- Local authentication: By default, iMaster NCE-Campus authenticates a tenant administrator in local authentication mode.
- LDAP server authentication: This mode is available when iMaster NCE-Campus interconnects with an LDAP server. For details, see Interconnection with an LDAP Authentication Server.
Choose from the main menu to configure the authentication mode.
Accounts on the LDAP server must be different from local accounts.
Interconnection with an LDAP Authentication Server
Members of an LDAP user group can log in to iMaster NCE-Campus through the LDAP authentication server.
General LDAP Mode
Obtaining an LDAP Certificate
To enable users on the LDAP server to log in to iMaster NCE-Campus you need to configure parameters for interconnection between iMaster NCE-Campus and the LDAP server.
Prerequisites
- The LDAP server must communicate with iMaster NCE-Campus.
If the LDAP server is connected to iMaster NCE-Campus through IPv6, you need to manually configure an IPv6 address that is on the same network segment as the IP address of iMaster NCE-Campus Service plane on the LDAP server.
- The LDAP server has been installed. The domain name has been configured, and a user and user group have been created.
A new user name cannot be the same as the iMaster NCE-Campus system account and cannot contain spaces or the following special characters: #%&'+|/();<=>?\. Otherwise, the new user cannot be identified by iMaster NCE-Campus and cannot log in to iMaster NCE-Campus.
Procedure
- Access the <LDAP server installation directory>\OpenLDAP\secure\certs directory.
- Edit the server.pem file and delete the RSA PRIVATE KEY content, that is, delete all content from -----BEGIN RSA PRIVATE KEY----- to -----END RSA PRIVATE KEY-----.
- Save the server.pem file to obtain the LDAP certificate server.pem.
Configuring iMaster NCE-Campus
Configuring iMaster NCE-Campus involves configuring the SSL connection certificate, LDAP interconnection parameters, and creating user groups and mapping rules.
Context
To use an LDAP account to log in to iMaster NCE-Campus, you need to connect iMaster NCE-Campus to the LDAP authentication server.
Prerequisites
An SSL certificate has been obtained.
Data Plan
The certificates imported using the iMaster NCE-Campus certificate management tool must meet the following requirements:
- The certificate name (including the file name extension) contains a maximum of 65 characters.
- Certificates in Base64-encoded X.509 v3 format are supported. Do not use certificates in DER-encoded binary format.
- The certificates must use the signature hash algorithm with higher security than SHA256.
- The certificates must use a signature algorithm with an RSA key longer than 2048 bits.
- The certificate validity period cannot be longer than 50 years or shorter than 90 days.
- The certificate effective date must be earlier than the current system date. Otherwise, an error message is displayed indicating that the certificate does not take effect.
- The certificate expiration date must be later than the current system date. Otherwise, an error message is displayed indicating that the certificate has expired.
- The file size must be greater than 0 KB and less than 50 KB.
- A maximum of 128 certificates can be uploaded.
Parameter |
Data (Example) |
Description |
|
---|---|---|---|
Authentication server configuration |
Server IP address type |
IPv4 |
IP address type of the LDAP server, IPv4 or IPv6. |
Server IP |
10.186.145.199 |
IP address of the LDAP server, which can be an IPv6 address. |
|
Server Port |
636 |
SSL is enabled for port 636 on the LDAP server. |
|
DN prefix |
uid= |
Characters prior to the user name in the DN of a login user. |
|
DN suffix |
ou=ab, ou=aaa_group, dc=AAA, dc=com |
Characters following the user name in the DN of a login user. |
|
User Name |
ldap_user |
Account created on the LDAP server. |
|
Password |
- |
Password of the account created on the LDAP server. Set the password as required. |
|
Creating a user group |
Name |
LDAPGroup1 |
Mapping user group on the LDAP server. |
Role |
Operator and auditor |
Multiple permissions can be selected for a user group. |
|
Creating a group mapping rule |
Rule Name |
rule1 |
Name of a user group mapping rule. |
Value |
GLDAPTest |
User group name created on the LDAP server. |
|
User group |
LDAPGroup1 |
Permissions to manage accounts on iMaster NCE-Campus. |
Procedure
- Import the AD-LDAP server certificate.
- Choose from main menu.
- Choose Service Certificate Management from the navigation pane. On the Services page, click AD-LDAP.
- Click the Trust Certificate tab and click Import. On the displayed page, enter the certificate information, select the desired LDAP server certificate, and click Submit to upload the certificate to iMaster NCE-Campus.
- Create a user group to be associated with the user group on the LDAP server.
- Choose . from the main menu
- Click the User Group tab, and click Create.
- Set user group information. For example, set the user group name to LDAPGroup1 and the role to Tenant Administrator.
- Click Next. On the Managed Object page, select the objects to be managed by the user group. Select one or more sites from the To Be Selected are and click
to add the selected sites to the Selected area.
- Click OK.
- Choose from the main menu.
- Set Authentication mode to LDAP. Then, set Mode to General LDAP in the Server Settings area, and set parameters for interconnection between iMaster NCE-Campus and the LDAP server.
You can select SSL encryption or no encryption for LDAP server authentication. For security purposes, use SSL encryption.
To enable SSL encryption, toggle on Enable SSL and select a certificate management policy.
- Create a user group mapping rule. Map the users on the LDAP server to the corresponding user group on iMaster NCE-Campus.
- Expand Advanced Settings, toggle on User-defined user group mapping rule, and click Create.
- Configure a user group mapping rule. All users in the user group GLDAPTest on the LDAP server are mapped to LDAPGroup1 on iMaster NCE-Campus. The users have the same permissions as the user group LDAPGroup1.
- Click OK.
- Click Test, set User Name and Password, and click Test.
- If the test is successful, close the Test window.
- If the test fails, rectify the fault accordingly.
- Click Apply to make the configuration take effect. A message is displayed indicating that the configuration is saved successfully.
After LDAP authentication is enabled, administrator users are authenticated locally whereas third-party system access users and remote users are authenticated on the LDAP server.
Local users cannot log in to iMaster NCE-Campus.
Configuration Verification
Log out the current tenant administrator account and log in to iMaster NCE-Campus using a member user account of the GLDAPTest user group on the LDAP server. If the login succeeds, the interconnection is successful.
To view a member user account in the GLDAPTest user group on the LDAP server, use the LDAP Admin account to connect to the LDAP server, right-click GLDAPTest, and right-click Properties.
Parameter Description
Parameter |
Description |
---|---|
Authentication Mode |
Select LDAP. |
Server IP address type |
IP address type of the LDAP server:
|
Server IP address |
IP address of the LDAP server. |
Server port |
By default, the SSL protocol is enabled on port 636 and disabled on port 389. |
Report server exception alarm |
Whether to report an alarm when the LDAP server is abnormal.
|
Enable SSL |
Whether to enable the SSL protocol when iMaster NCE-Campus connects to the LDAP server. By default, the SSL protocol is enabled. NOTE:
|
Mode |
Select General LDAP. |
DN prefix |
Example: cn= |
DN suffix |
Example: dc=example or dc=com. |
Base DN |
Base DN used by a user. |
Object class name |
Name of a user class in the corresponding LDAP server schema. |
Unique identifier |
Unique identifier, which identifies a user name. |
User country code attribute |
Attribute name used to identify the country code of a mobile number. |
User mobile number attribute |
Attribute name used to identify a mobile number. |
User mobile number format |
Attribute name used to identify a mobile number format. The default value is a mobile number without a country code. |
User group identifier |
User group identifier, which identifies the group to which a user belongs. |
Base DN |
Base DN used by a user group. |
Object class name |
Name of a user group class in the corresponding LDAP server schema. |
Unique identifier |
Attribute used to identify a user name. |
Member identifier |
Attribute name of a user group member. |
Delimiter |
Separator of user groups in the corresponding LDAP server schema. |
Authentication bypass |
After authentication bypass is enabled, the account and password of an LDAP user are saved on the local server. If the LDAP server is faulty, the LDAP user can log in to iMaster NCE-Campus by performing a local authentication. |
Parameter |
Description |
---|---|
User-defined user group mapping rule |
Rule to map an LDAP user group to one or more user groups on iMaster NCE-Campus. |
Rule name |
Name of a user group mapping rule. |
Description |
Description of the mapping rule. |
User group |
Mapping user group on the LDAP server. |
Value |
Name of the user group on the LDAP server. |
Windows AD Mode
Creating and Exporting the AD Certificate
To enable users on an AD server to log in to iMaster NCE-Campus, you need to configure interconnection between iMaster NCE-Campus and the AD server.
Prerequisites
- The AD server is able to communicate with iMaster NCE-Campus.
If the AD server is connected to iMaster NCE-Campus through IPv6, you need to manually configure an IPv6 address that is on the same network segment as the IP address of iMaster NCE-Campus Service plane on the AD server.
- The AD server has been installed. The domain name has been configured, and a user and user group have been created.
A new user name cannot be the same as the iMaster NCE-Campus system account and cannot contain spaces or the following special characters: #%&'+|/();<=>?\. Otherwise, the new user cannot be identified by iMaster NCE-Campus and cannot log in to iMaster NCE-Campus.
- If you do not create a certificate for the first time, uninstall the AD server root certificate and domain certificate. For details, see How Do I Uninstall the Root AD Certificate and Domain Certificate?.
Procedure
The following example uses the Windows Server 2008 R2 Standard operating system.
- Install the Active Directory certificate service.
- Click
to open the server manager.
- Right-click Roles and click Add Roles.
- Choose Server Roles, and ensure that Active Directory Domain Services and DNS Server are displayed as Installed.
- Select Active Directory Certificate Services and click Next.
- Choose AD CS > Role Service, select Certification Authority Web Enrollment, and click Next.
- Choose AD CS > Setup Type, retain the default setting, and click Next.
- Choose AD CS > CA Type, retain the default setting, and click Next.
- Choose AD CS > Private Key, retain the default setting, and click Next.
- Choose Private Key > Cryptography. Set Select the hash algorithm for signing certificates issued by this CA to SHA256.
- Choose Private Key > CA Name, and configure the CA name. You can modify common name for the CA (for example, Huawei-WIN-GRC97HN6VCE-CA) and distinguished name suffix (for example, DC=Huawei,DC=com).
- Choose Private Key > Validity Period, change the validity period of the root certificate, and click Next.
- Choose AD CS > Certificate Database, specify the certificate path and retain the default setting, and click Next.
- Confirm the installation configuration and click Install.
- Click Close.
- Click
- Check the CA configuration and ensure that the domain certificate has been enrolled successfully.
- On the Run page, enter inetmgr in the Open text box to open the IIS process.
- Check that the CA web enrollment service generates an application Certsrv in the IIS default site.
- In the navigation tree, choose CertSrv. In the Browse Application area on the right, click Browse *:80 (http) to view the web registration page of the CA.
- Export the certificate issued by the CA to the AD server.
- On the Run page, enter mmc in the Open text box to open the root node of the console.
- Choose .
- Select Certificates and click Add.
- Select Computer account.
- Retain the default settings and click Finish.
- Click OK.
- Choose to view the certificate.
- Request domain certificates.
- Right-click in the blank space and choose from the shortcut menu.
- Click Next.
- Choose Active Directory Enrollment Policy and click Next.
- Select Domain Controller and Domain Controller Authentication. Click Enroll.
- Click Finish when the enrollment is successful.
- Requesting domain certificates is successful.
- Right-click the certificate and choose .
- On the Certificate Export Wizard page, retain the default setting, and click Next.
- Select Base-64 encoded X.509(.CER), and click Next.
- Specify the certificate file name and storage path, and click Next.
- Confirm the configuration and click Finish. If a message is displayed indicating that the certificate is successfully exported, click OK.
- View the exported certificate in the storage path specified in 3.l.
Configuring iMaster NCE-Campus
Configuring iMaster NCE-Campus involves configuring the SSL connection certificate, AD interconnection parameters, and creating user groups and mapping rules.
Context
To use an AD account to log in to iMaster NCE-Campus, you need to connect iMaster NCE-Campus to the AD authentication server.
Prerequisites
An SSL certificate has been created or obtained.
Data Plan
The certificates imported using the iMaster NCE-Campus certificate management tool must meet the following requirements:
- The certificate name (including the file name extension) contains a maximum of 65 characters.
- Certificates in Base64-encoded X.509 v3 format are supported. Do not use certificates in DER-encoded binary format.
- The certificates must use the signature hash algorithm with higher security than SHA256.
- The certificates must use a signature algorithm with an RSA key longer than 2048 bits.
- The certificate validity period cannot be longer than 50 years or shorter than 90 days.
- The certificate effective date must be earlier than the current system date. Otherwise, an error message is displayed indicating that the certificate does not take effect.
- The certificate expiration date must be later than the current system date. Otherwise, an error message is displayed indicating that the certificate has expired.
- The file size must be greater than 0 KB and less than 50 KB.
- A maximum of 128 certificates can be uploaded.
Parameter |
Data (Example) |
Description |
|
---|---|---|---|
Authentication server configuration |
Server IP address type |
IPv4 |
IP address type of the AD server, IPv4 or IPv6. |
Server IP |
192.168.4.107 |
IP address of the AD server, which can be an IPv6 address. |
|
Server Port |
636 |
SSL is enabled for port 636 on the AD server. |
|
AD Domain Name |
Huawei.com |
Domain name for configuring the AD server. |
|
Base DN |
dc=Huawei,dc=com |
Base DN to be synchronized to iMaster NCE-Campus on the AD server. |
|
User Name |
ad_user |
Account created on the AD server. |
|
Password |
Huawei@123 |
Password of the account created on the AD server. |
|
Creating a user group |
Name |
ADGroup1 |
Mapping user group on the AD server. |
Role |
Operator and auditor |
Multiple permissions can be selected for a user group. |
|
Creating a group mapping rule |
Rule Name |
rule1 |
Name of a user group mapping rule. |
Value |
GADTest |
User group name created on the AD server. |
|
User group |
ADGroup1 |
Permissions to manage accounts on iMaster NCE-Campus. |
Procedure
- Import the AD-LADP server certificate.
- Choose from main menu.
- Choose Service Certificate Management from the navigation pane. On the Services page, click AD-LDAP.
- Click the Trust Certificate tab and click Import. On the displayed page, enter the certificate information, select the desired LDAP server certificate, and click Submit to upload the certificate to iMaster NCE-Campus.
- Create a user group to be associated with the user group on the AD server.
- Choose from the main menu.
- Click the User Group tab, and click Create.
- Set user group information. For example, set the user group name to ADGroup1 and the role to Tenant Administrator.
- Click Next. On the Managed Object page, select the objects to be managed by the user group. Select one or more sites from the To Be Selected are and click
to add the selected sites to the Selected area.
- Click OK.
- Choose from the main menu.
- Set Authentication mode to LDAP. Then, set Mode to Windows AD in the Server Settings area, and configure parameters for interconnection between iMaster NCE-Campus and the AD server.
You can select SSL encryption or no encryption for AD server authentication. For security purposes, use SSL encryption.
To enable SSL encryption, toggle on Enable SSL and select a certificate management policy.
- Create a user group mapping rule. Map the user group on the AD server to the corresponding user group on iMaster NCE-Campus.
- Expand Advanced Settings, toggle on User-defined user group mapping rule, and click Create.
- Configure a user group mapping rule. All users in the user group GADTest on the AD server are mapped to ADGroup1 on iMaster NCE-Campus. The users have the same permissions as the user group ADGroup1.
- Click OK.
- Click Test, set User Name and Password, and click Test.
- If the test is successful, close the Test window.
- If the test fails, rectify the fault accordingly.
- Click Apply to make the configuration take effect. A message indicating that the configuration is saved is displayed.
Configuration Verification
Log out the current tenant administrator and log in to iMaster NCE-Campus using a member user account of the GADTest user group on the AD server. If the login succeeds, the interconnection is successful.
To view member user accounts in the GADTest user group on the AD server, use the LDAP Admin account to connect to the AD server, choose
on the AD server. Right-click GADTest and click Properties and Members in sequence.Parameter Description
Parameter |
Description |
---|---|
Authentication Mode |
Select LDAP. |
Server IP address type |
IP address type of the AD server:
|
Server IP address |
IP address of the AD server. |
Server port |
By default, the SSL protocol is enabled for port 636 and disabled for port 389. |
Report server exception alarm |
Whether to report an alarm when the AD server is abnormal.
|
Enable SSL |
Whether to enable the SSL protocol when iMaster NCE-Campus connects to the AD server. By default, the SSL protocol is enabled. NOTE:
|
Mode |
Select Windows AD. |
AD domain name |
Domain name for configuring the AD server. |
Base DN |
Base DN used by the user. |
Object class name |
Name of a user class in the corresponding LDAP server schema. |
Unique identifier |
Attribute used to identify a user name. |
User country code attribute |
Attribute name used to identify the country code of a mobile number. |
User mobile number attribute |
Attribute name used to identify a mobile number. |
User mobile number format |
Attribute name used to identify a mobile number format. The default value is a mobile number without a country code. |
User group identifier |
Attribute name of the group to which a user belongs. |
Base DN |
Base DN used by a user group. |
Object class name |
Name of a user group class in the corresponding LDAP server schema. |
Unique identifier |
Attribute used to identify a user group name. |
Member identifier |
Attribute name of a user group member. |
Delimiter |
Separator of user groups in the corresponding LDAP server schema. |
Authentication bypass |
After authentication bypass is enabled, the account and password of an LDAP user are saved on the local server. If the LDAP server is faulty, the LDAP user can log in to iMaster NCE-Campus by performing a local authentication. |
Parameter |
Description |
---|---|
User-defined user group mapping rule |
Rule to map an AD user group to one or more user groups in iMaster NCE-Campus. |
Rule name |
Name of a user group mapping rule. |
Description |
Description of the mapping rule. |
User group |
Mapping user group on the AD server. |
Value |
Name of the user group on the AD server. |
Configuring a Workgroup
Context
If an MSP administrator configures workgroups to manage tenants, tenants cannot authorize the MSP to maintain tenant services based on user roles. If tenants require the MSP to maintain their services, they can authorize the MSP to manage services based on workgroups.
Tenant administrators can create workgroups, assign different rights to workgroup administrators, and authorize MSP workgroup administrators to manage tenant workgroups.
When an MSP is authorized to manage tenant services, MSP workgroup administrators only have the permission to manage services of tenant workgroups authorized by tenant administrators.
Procedure
- Log in to iMaster NCE-Campus as the root tenant administrator.
- Choose Role tab, and click Create to create a workgroup administrator role. from the main menu, click the
- Choose Create, set parameters, and click Next. from the main menu, click Table 4-126 Basic information about a workgroup
Parameter
Description
Workgroup name
Name of a workgroup, which identifies the purpose of the workgroup.
Number of users
Number of administrator accounts in a workgroup, including administrator accounts in the sub-workgroups of the workgroup.
Number of workgroups
Number of sub-workgroups that can be created in the workgroup.
Description
Workgroup description.
Role
User roles available for users in the workgroup.
- By default, the following roles are supported: Tenant administrator, Operator, Monitor, and Open API operator.
The operation rights of these roles are described as follows:
- Monitor: A monitor can view tenant services and configurations.
- Open Api Operator: An open API operator can use open API services and related configurations.
- Tenant Administrator: A tenant administrator can perform operations on tenant services and related configurations.
- Operator: An operator can manage system service running.
- When creating a workgroup, you need to use the administrator account to create roles. Otherwise, roles cannot be selected when a sub-workgroup is created in the workgroup.
- By default, the following roles are supported: Tenant administrator, Operator, Monitor, and Open API operator.
- Configure the workgroup administrator and click Next.
For security purposes, keep the password secure and change it periodically.
- Manually configure a password when creating the workgroup administrator.
Set Password create mode to Manual and configure a password for the workgroup administrator.
- Create a password via email.
Set Password create mode to Email. After the account is created, the system sends a URL to your email box. You can click the URL to configure a password for the workgroup administrator.
- If you choose to configure a password via email, configure an email server before creating an account. Otherwise, the system fails to send a URL to the specified email address. For details, see Configuring an Email Server
- If the password for the workgroup administrator is configured via email, the administrator does not need to change the password upon the first login to iMaster NCE-Campus.
- Manually configure a password when creating the workgroup administrator.
- Select managed objects, that is, the sites or logic networks that can be managed by the workgroup, and then click OK.
If a sub-tenant administrator is authorized to managed selected sites, the administrator cannot view the following menus after logging in to iMaster NCE-Campus since the administrator does not have the permission to manage all resources:
- (Optional) Authorize tenant workgroup administrator rights to the MSP administrator.
Choose
from the main menu.In the Authorization Information area, enable Authorize MSP, and select the workgroup that needs to be authorized to the MSP administrator for service management.
Log in to iMaster NCE-Campus as an MSP administrator, create an MSP workgroup, and select an MSP-managed tenant workgroup as a managed object. The MSP workgroup administrator can only manage services of the authorized tenant workgroup after logging in to iMaster NCE-Campus.
Follow-up Procedure
- Modify a workgroup.
- Log in to iMaster NCE-Campus as a tenant administrator and choose from the main menu.
- Click
in the Operation column in the row of the target workgroup to modify the workgroup.
- Delete a workgroup.
- Log in to iMaster NCE-Campus as a tenant administrator and choose from the main menu.
- Select the target workgroup and click Delete.
- Only sub-workgroups can be deleted, and the workgroup to which the current user belongs cannot be deleted.
- Deleting a workgroup will delete information about sub-workgroups at all levels, as well as users, roles, and user groups of the workgroup.
- Deleting a workgroup is a risky operation. Exercise caution when performing this operation.
- Transfer workgroup administrator rights.
If the administrator of a workgroup is changed, an upper-level administrator can transfer the workgroup administrator rights to another administrator.
Workgroup administrators can transfer their rights only to the administrators created by themselves. Before transferring rights of a workgroup administrator, ensure that the workgroup administrator has created an administrator account.
- This operation can only be performed on level-1 sub-workgroups of the workgroup to which the current user belongs and cannot be performed on the workgroups of level 2 or higher.
- If workgroup administrators remain online after their rights are transferred, they will be forced offline and has no rights.
- Choose User tab. from the main menu. Click the
- Click Select, select the desired workgroup, and click OK.
Select a desired account and click Hand Over to enable this account to become the new workgroup administrator.
The new account must be an administrator account created by the old workgroup administrator account.
If the
icon is moved to the right of the new administrator account, the rights are transferred successfully.
Modifying Tenant Information
Personalized tenant information can be modified, such as the enterprise name and logo, on iMaster NCE-Campus.
Procedure
- Access the Tenant Information page.
Choose
from main menu. - Modify the tenant name, address, email address, contact number, or description. You can also click the Upload to replace the enterprise logo. Then, click Save.
Information customized by an administrator will be displayed on the pages available to that administrator. For example, after an administrator replaces the enterprise logo and refreshes the page, the new logo is displayed in the upper left corner of the page.
When customizing an enterprise logo, you are advised to use an image with a size of 150 x 30 pixels to achieve the optimal display effect. The image can be in the JPG, PNG, or BMP format, with a size no more than 100 KB.
Modifying Account Information
Modifying the User Password and Access Control Settings
On iMaster NCE-Campus, you can change your password and access control settings. After first login to iMaster NCE-Campus, you need to change the default password to ensure security of iMaster NCE-Campus. Regularly changing the password can prevent malicious password theft and protect the system against unauthorized access.
Leaving a password unchanged for a long time increases the risk of the password being stolen or cracked. Regularly changing the password effectively resolves this problem and is therefore strongly recommended.
Prerequisites
You have logged in to iMaster NCE-Campus.
Procedure
- Change the default password.
You will be redirected to the password change page when you log in to iMaster NCE-Campus for the first time.
- On the Change Password page, enter the old password and a new password, and confirm the new password.
- Click OK.
- Change the user password.
- Choose from the main menu.
- On the Basic Information tab page, click
next to the password. In the dialog box that is displayed, set a new password.
- Modify the IP address range that can be used by the current account to log in to iMaster NCE-Campus.
- Choose from the main menu.
- On the Access Control tab page, create Create, set a start IP address and an end IP address, and click OK. If the IP address range list is empty, login is allowed from any IP address.
Configuring and Verifying an Email Address
Prerequisites
You have logged in to iMaster NCE-Campus.
Procedure
- Choose from the main menu.
- Configure and verify an email address.
- If no email address is configured during account creation, you can specify an email address for the account. Click
next to Email address. In the dialog box that is displayed, configure an email address, and then click Obtain Verification Code.
- If an email address has been set during account creation, you must verify the email address. Click Verify next to Email address. In the dialog box that is displayed, enter the configured email address, and then click Obtain Verification Code.
- A verification code will be valid for 10 minutes. If you do not enter the verification code within 10 minutes, you need to obtain a new one.
- For security purposes, do not disclose the verification code.
- If no email address is configured during account creation, you can specify an email address for the account. Click
- Log in to the mailbox to obtain the verification code. Enter the code in Email verification code, and then click OK.
Configuring a Mobile Number and SMS Authentication for Two-Factor Authentication
Two-factor authentication (2FA) is a security check process. It strengthens security by requiring two identity credentials to verify user identity before granting access to the system. 2FA secures user logins from attackers exploiting weak or stolen passwords. In addition, login notifications can also warn users of unauthorized access to their accounts.
iMaster NCE-Campus supports 2FA based on verification codes in SMS messages. In this mode, when logging in to iMaster NCE-Campus, a user needs to enter a regular username and password, and then is required to enter a verification code which is sent to the user's mobile phone via SMS.
Context
- Configure a mobile number. After logging in to iMaster NCE-Campus, you need to bind a mobile number to your account. After you enter a mobile number, iMaster NCE-Campus checks whether the format of the mobile number meets the requirements (1 to 20 digits) and verify that the mobile number is not bound to another account. If the mobile number meets the preceding requirements, you can apply for a verification code. The mobile number can be changed after being configured.
- Enable SMS verification upon login. After configuring a mobile number, you need to enable SMS verification upon login to implement 2FA. Before enabling SMS verification upon login, ensure that a mobile number has been configured.
When you attempt to obtain an SMS verification code, you may not receive any SMS message due to poor network signals or mobile phone issues. If this occurs, you can obtain a new verification code 1 minute later. A verification code will be valid for 5 minutes. If you obtain a new verification code before the current verification code expires for more than five consecutive times and the verification fails each time, your account will be locked for 10 minutes.
Prerequisites
An SMS server has been configured. For details, see Configuring an SMS Server.
Procedure
- Choose from the main menu.
- Click
next to Mobile number. In the dialog box that is displayed, complete the verification as prompted. Then the specified mobile number is bound to the current account.
- Click Modify next to SMS verification upon login. In the window that is displayed, enable SMS verification upon login and complete the verification using an SMS verification code.
Configuring a Date Format and a Time Zone for Administrator Clients
Context
By default, the time on an administrator client is the same as that on controller servers.
To display the time based on the time zone where the client resides, you can modify the date format and time zone settings on iMaster NCE-Campus.
Prerequisites
You have logged in to iMaster NCE-Campus.
Procedure
- Choose Date and Time Zone Settings tab. from the main menu, and click the
- Set Date format and Client time zone, and click Apply.
- After the settings take effect, the date in the system is displayed in the configured format. The time on the client is displayed based on the configured time zone.
- The settings take effect only for the current user.
- (Optional) Click Default Settings to restore the date format and client time zone to the default values.
Configuring a Time Format for Administrator Clients
Prerequisites
You have logged in to iMaster NCE-Campus.
Procedure
- Choose Time Format Settings tab. from the main menu, and click the
- Set Date format, and click Apply.
- HH or hh indicates the hour, mm indicates the minute, ss indicates the second, and tt indicates the morning or afternoon.
- hh:mm:ss tt indicates the 12-hour format, and HH:mm:ss indicates the 24-hour format.
- The settings take effect only for the current user.
- (Optional) Click Default Settings to restore the time format to the default value.
Device Management and Maintenance
Viewing and Exporting Device Information
Prerequisites
New devices have been added to iMaster NCE-Campus and target sites.
Procedure
- Choose Device tab. from the main menu, and click the
- Devices discovered by NETCONF are called cloud managed devices whereas devices discovered by SNMP are called traditional devices.
- For stacked switches, only the management IP address of the master member switch is displayed.
- Deleting a device will interrupt services. Exercise caution when performing this operation.
- Click
on the right of the Operation column to customize the fields to be displayed in the device list.
- Export device information and download it to the local host.
- Select desired devices and click Export to export information about the selected devices.
- If you do not select any device and click Export, information about all devices will be exported.
- Select desired devices and click Export to export information about the selected devices.
- Click a device name in the list to check the detailed device information. For details, see Device Monitoring.
Device Management Settings
Creating an Automatic Discovery Task
iMaster NCE-Campus can automatically search for devices that meet specific criteria and add them to the system. This reduces manual intervention and operation costs.
Procedure
- Choose .
- On the Device tab page, choose , and then click Create Discovery Task. You can either select or not select a site when adding devices.
- In the Basic Settings area on the Set Parameters page, set the IP protocol version, start IP address, end IP address, and subnet where devices to be added.
- In the Task Settings area, set the task name, user group to which email notifications are sent, execution frequency, and task description.
- If you set Frequency to Hourly, Daily, Weekly, or Monthly but do not select Instant execution, the automatic discovery task will not run immediately after being created.
- If you select Automatically add discovered devices and click Next, the system will automatically go to the Results page.
- In the Protocol Settings area, select a protocol type.
- Click Next. The Discover Devices page is displayed. The system starts to discover devices.
- Add the discovered devices to the system.
- To add all discovered devices, click Add All.
- To add some discovered devices, select desired devices and click Add Selected.
- On the Add Devices page, check the devices you have added.
- Click Next. The Results page is displayed.
The result of the automatic discovery task is displayed. Click Success or Fail in the Discovered Devices or Added Devices area to view details in the lower pane.
Related Tasks
- On the Management Settings tab page, choose Discovery Task Management from the navigation pane and click the Task List tab. On the Task List tab page, you can start, create, modify, delete, and view automatic discovery tasks.
- On the Management Settings tab page, choose Discovery Task Management from the navigation pane and click the Exclusion List tab. On the Exclusion List tab page, you can add and delete excluded subnets or IP addresses.
- When configuring an excluded subnet, set start and end IP addresses in the Add to Exclusion List dialog box.
- When configuring an excluded IP address, set a start IP address in the Add to Exclusion List dialog box.
Synchronizing Device Information to the Registration Center
Context
The registration center checks device ESNs to identify potential errors that may occur when users manually enter device information. When an uploaded ESN is the same as an existing ESN, device information fails to be synchronized to the registration center. In this case, check the device information based on the MAC address, and synchronize device information to the registration center only when both the device ESN and MAC address are correct.
Prerequisites
The function of synchronizing device information to the registration center has been enabled. This function is enabled by default when a tenant administrator adds devices.
Procedure
- Choose from the main menu, click the Management Settings tab, and choose Registration Center Synchronization from the navigation pane to check whether information about a device fails to be synchronized.
If a device is added based on the device type (no ESN recorded in the system), the device is not displayed on the Registration Center Synchronization page before the device ESN is entered.
- If device information fails to be synchronized, click Resynchronize to synchronize the device information to the registration center again.
If the ESN of a device is the same as that of an existing device in the registration center, click Verify MAC Address in the Operation column of the device to confirm and enter the MAC address that matches the ESN.
Changing the Administrator Password and BootROM Password of Devices at New Sites
Context
When logging in to iMaster NCE-Campus for the first time, a tenant administrator needs to set the administrator password and BootROM password for new devices.
After devices at a site go online, their administrator password and BootROM password will be automatically reset to those specified by the tenant administrator. To ensure device security, the tenant administrator needs to change the two passwords periodically on iMaster NCE-Campus.
Procedure
- Choose Management Settings tab, and choose Device Password Configuration from the navigation pane. from the main menu, click the
- Configure the device administrator password and BootROM password and click Apply.
This configuration takes effect only for new sites. After devices at a new site go online, their administrator password and BootROM password will be automatically set to those specified on this page. The two passwords of devices at existing sites remain unchanged. To change the administrator password and BootROM password of devices at existing sites, see Changing the Administrator Password and BootROM Password of Devices at Existing Sites.
- Only switches and APs support the BootROM password configuration.
- If the system administrator disables The device BootROM password can be configured, tenant administrators cannot change BootROM passwords of devices. For details about how to disable tenants from changing BootROM passwords of devices, see Configuring a BootROM Password Policy.
Changing the Administrator Password and BootROM Password of Devices at Existing Sites
Context
If devices are added using a template, the administrator password and BootROM password of the devices will not be set to those configured by the tenant administrator after the devices go online. Instead, the passwords configured in the template will take effect.
To ensure device security, the tenant administrator needs to change the two passwords periodically on iMaster NCE-Campus.
For devices at a site that has bound to a site template, you can change the device administrator password only in the site template. For details, see Configuring a LAN-side Site Template.
Procedure
- Choose Device Administrator. from the main menu, choose from the navigation pane, and expand
- Click
in the Operation column in the row of the desired user to change the administrator password.
- This configuration takes effect only on devices at the selected site.
- The device administrator password cannot be changed on devices after it is specified on iMaster NCE-Campus.
- Click Create to create a device administrator.
- Click Set next to BootROM password to set the BootROM password for switches and APs.
- Only switches and APs support BootROM password configuration.
- If the system administrator disables The device BootROM password can be configured, tenant administrators cannot change BootROM passwords of devices. For details about how to disable tenants from changing BootROM passwords of devices, see Configuring a BootROM Password Policy.
Enabling or Disabling Local CLI-based Device Configuration
Context
By default, users can log in to devices and configure them through the local CLI. However, if a user logs in to the local CLI of an online device and configures or modifies device services using commands, the configurations may conflict with those delivered by iMaster NCE-Campus, resulting in service exceptions.
To prevent such problems, tenant administrators can disable local CLI-based device configuration. After this function is disabled, users can run commands only listed in Table 4-127 on the device CLI.
- Among switches running V100R019C10, only the following switch models support this function:
- S5735-L12T4S-A, S5735-L12P4S-A, S5735-L24T4S-A, S5735-L24P4S-A, S5735-L24T4X-A, S5735-L24P4X-A, S5735-L32ST4X-A, S5735-L48T4S-A, S5735-L48T4X-A, S5735-L48P4X-A
- S5720-12TP-LI-AC, S5720-12TP-PWR-LI-AC, S5720-28TP-LI-AC, S5720-28TP-PWR-LI-AC, S5720-28TP-PWR-LI-ACL, S5720-28P-LI-AC, S5720-28P-PWR-LI-AC, S5720-52P-LI-AC, S5720-52P-PWR-LI-AC, S5720-16X-PWH-LI-AC, S5720-28X-LI-AC, S5720-28X-LI-DC, S5720-28X-LI-24-SAC, S5720-28X-LI-24S-DC, S5720-28X-PWR-LI-AC, S5720-28X-PWR-LI-ACF, S5720-28X-PWH-LI-AC, S5720-52X-LI-AC, S5720-52X-LI-DC, S5720-52X-PWR-LI-AC, S5720-52X-PWR-LI-ACF, S5720-52X-LI-48S-AC
- Switches running V100R020 and later versions support this function.
Prerequisites
The MSP administrator has authorized tenant administrators to enable or disable local CLI-based device configuration. For details, see Authorizing Tenant Administrators to Enable or Disable Local CLI-based Device Configuration.
Procedure
- Choose Management Settings tab, and choose Local CLI-based Device Configuration from the navigation pane. from the main menu, click the
- Enable Local CLI-based switch configuration and click Apply. This function is enabled by default and users can configure devices through the device CLI. With this function disabled, when logging in to a device using the CLI, a user can run commands listed in Table 4-127 only.Table 4-127 Commands that can be run
View
Command
System view
interface Ethernet
interface GigabitEthernet
interface MultiGE
interface XGigabitEthernet
interface 40GE
interface 100GE
reset trace instance
save trace information
trace
undo trace
acl
undo acl
pki
undo pki
observe-port
undo observe-port
traffic-mirror
undo traffic-mirror
traffic-statistic
undo traffic-statistic
capture-packet
undo capture-packet
http server load
undo http server load
lldp enable
undo lldp enable
arp snooping enable
undo arp snooping enable
display
quit
return
diagnose
reset cloud-mng work-mode
netconf register abort
undo netconf register abort
ping
tracert
stelnet ip-address
sftp
NOTE:The following SFTP-related commands cannot be run:
sftp client-source
sftp client-transfile
sftp ipv4
sftp ipv6
sftp server enable
mad restore
Ethernet interface view
GE interface view
MultiGE interface view
XGE interface view
40GE interface view
100GE interface view
traffic-mirror
undo traffic-mirror
traffic-statistic
undo traffic-statistic
port-mirroring
undo port-mirroring
display
quit
return
negotiation auto
undo negotiation auto
speed
undo speed
duplex
undo duplex
virtual-cable-test
arp snooping enable
undo arp snooping enable
lldp enable
undo lldp enable
ACL view
All commands in this view
FTP client view
All commands in this view
PKI entity view
All commands in this view
PKI realm view
All commands in this view
WLAN view
All commands in this view
NETCONF view
All commands in this view
Restarting a Device Within One Click
Prerequisites
New devices have been added to iMaster NCE-Campus and target sites.
Procedure
Restarting a device will cause service interruptions and cause unsaved pre-configurations on this device to be lost. Save configurations before restarting a device.
- Choose Device tab. from the main menu, and click the
- Use either of the following methods to restart devices:
- To restart devices in batches, select the online devices that you want to restart and click More > Restart.
- To restart a single device, click a device name and click Reboot Device in the upper right corner on the device details page.
- To restart devices in batches, select the online devices that you want to restart and click More > Restart.
- On the page that is displayed, click OK.
Viewing WAC Group Information
Prerequisites
A WAC group has been created. For details, see Creating a WAC Group.
Procedure
- Choose from the main menu.
- Select a WAC group from the list to view information about the selected WAC group.
Replacing a Device
Context
Tenant administrators can replace faulty or obsolete devices and synchronize configurations of old devices to new devices on iMaster NCE-Campus to ensure normal service running.
Prerequisites
A new device has been added to iMaster NCE-Campus. For distributed APs and central APs, only devices in offline or unregistered state can be used for replacement.
- The model of the new device must be the same as that of the old device.
- After device replacement, iMaster NCE-Campus delivers configurations of the old device to the new device. However, the configurations delivered through the device CLI cannot be automatically delivered. You need to log in to the device CLI to perform configurations again. It is recommended that you periodically back up device configuration files. For details, see Configuring a Configuration File Backup Task.
- After a switch is replaced, iMaster NCE-Campus delivers the configurations of the old switch to the new switch and then restarts the new switch.
Procedure
- Choose from the main menu.
- Find the device to be replaced in the device list, and click
next to the device in the Operation column.
- On the Device Replacement page, select a device in the New device area and click OK to replace the old device with the new device. The system will synchronize the device information, including the site, location, and configurations, from the old device to the new device.
Device Upgrade
Precautions
- Obtain software packages required during an upgrade from https://support.huawei.com/. Software packages obtained through any other means is considered illegal and forbidden to be used.
- Read the release notes of the target version to obtain information about the target version.
- The upgrade must be performed by trained engineers only.
- Ensure stable power supply for an upgrade. Power-off during an upgrade will cause unexpected results.
- Disable the auto-saving function for your device before upgrading it. Otherwise, software packages may fail to be loaded.
- During software package loading, ensure that the communication between the device and SFTP server is normal. Otherwise, the upgrade may fail.
- When upgrading a device, do not perform any other operations on the device, such as removing or inserting a board and replacing the main control board. Otherwise, the upgrade may be rolled back, causing service interruptions or an upgrade failure.
- During software package loading and device upgrade, the database synchronization between the active and standby main control boards is disabled. Therefore, do not make any configuration changes. Otherwise, the upgrade may be rolled back or the changes made during software package loading may be lost.
- If the NEs to be upgraded are not included in the same upgrade task, ensure that the NEs on the same route but in different tasks are activated from the remote device to the near NE in connection with the gateway NE (GNE).
Upgrading/Downgrading NETCONF-Managed Devices
Context
System, MSP, and tenant administrators can use a file upload tool to upload device software packages or patch packages to the built-in file server of iMaster NCE-Campus. A tenant administrator can customize upgrade/downgrade policies to enable automatic device upgrade/downgrade or upgrade/downgrade devices manually.
You can upgrade all devices or some devices in either of the following ways:
- Upgrade devices based on the device model. In this mode, all devices of the same model at a site will be upgraded in batches.
- Select the devices to be upgraded based on the device name.
- iMaster NCE-Campus has a limited southbound egress bandwidth. If you upgrade a large number of devices on iMaster NCE-Campus at the same time, the "The download fails." message may be displayed for some devices that need to wait for a long period. If this occurs, try again later.
- Devices will be restarted during system software upgrades and cold patch upgrades, resulting in service interruptions. Therefore, you are advised to upgrade device system software or install cold patches during off-peak hours.
- Device restart can result in loss of unsaved pre-configurations. Therefore, you need to select the corresponding site and save device configurations before an upgrade.
- When you upgrade switches with different models of the same series in a stack based on the device model, only the model of the master member of the stack can be displayed. The model of the standby member is not displayed by default.
- If the version of the device software package or patch package is earlier than the current version, a downgrade operation is performed.
- Third-party file servers can be used to upgrade only ARs, LSWs, and APs. ARs running V200R019C00 and later versions as well as APs and LSWs running V200R019C10 and later versions can be upgraded through third-party file servers.
Prerequisites
Since RSA and CBC algorithms have security risks, these algorithms are disabled by default. If an upgrade plan contains devices running versions earlier than V300R019C00SPC300, contact the administrator to enable RSA and CBC algorithms. For details, see 2.
By default, iMaster NCE-Campus verifies device ESNs in device certificates. If an upgrade plan contains devices running V300R19C00SPC300 or an earlier version, contact the system administrator to disable ESN verification for device certificates. If this function is required at a later time, apply for new device certificates to replace existing ones. For details, see 3.
HTTP/2 channels are required by devices to report their data to iMaster NCE-Campus. When establishing an HTTP/2 channel with a device, iMaster NCE-Campus will check whether the actual device certificate is the same as that on itself. If a switch running V200R008C00 or an earlier version needs to be managed, ensure that the following operations have been performed to set DEVICE_OLD_CERT_ENABLE(enable device old cert or not) to true on the management plane. For details, see Step 4.
- Log in to the management plane.
- Choose RSA_ENABLE to true, and click OK. from the main menu, choose , set
RSA is a weak encryption algorithm. Confirm with customers before enabling this algorithm.
- Choose ESN_CHECK_ENABLE to false, and click OK. from the main menu, choose , set
- Choose Product > Software Management > Deploy Product Software from the main menu, click More > Modify Configurations, set DEVICE_OLD_CERT_ENABLE(enable device old cert or not) to true, and click OK.
- Click
to check whether the configuration is successful.
- Wait for 3 to 5 minutes, choose Service tab, search for FIProxyService, and check whether FIProxyService is restarted successfully. The device can be upgraded only when FIProxyService is in normal state. from the main menu, click the
Procedure
- Upload software packages or patch packages to iMaster NCE-Campus.
- If you use the iMaster NCE-Campus built-in file server to upgrade devices, upload the desired system software packages or patches to iMaster NCE-Campus on the controller web UI. For details, see Managing Files.
- If a third-party file server is used to upgrade devices, perform the following operations to upload the desired system software packages or patches to the third-party file server.
- Prepare a third-party file server.
- Configure interconnection between iMaster NCE-Campus and the third-party file server. For details, see Configuring Interconnection with a File Server.
- On iMaster NCE-Campus, record the information about system software packages and patches uploaded to the file server. For details, see Managing Files.
If the system administrator or MSP administrator has uploaded an appropriate system software package or patch file or has recorded the file information for the target device, skip this step.
- Choose Upgrade Preparations page then is displayed. You can view device information of a site on the page. The number in red next to the site indicates the recommended number of devices to be upgraded at the site. You can set Filter Criteria to view upgrade information about a specified site and device. from the main menu. The
- Select a site and click Plan Upgrade. The upgrade schedule page then is displayed.
Configure the upgrade time, including Time mode, Time to Download Upgrade Files and Software Update Restart Time.
- If Time mode is set to Device Time, ensure that the time zone configured for the site on the controller is the same as the actual time zone of the site where the device to upgrade is located. Otherwise, the upgrade may fail to be performed at the expected time.
- When a patch is uninstalled from a device, a scheduled task for uninstalling a patch cannot be configured.
- Select a file server. If you plan to use the file upload tool to upload system software packages, set File server to Built-in file server. If you plan to upload files through a third-party file server, select the name of third-party file server.
- Configure the upgrade target version.
- Select the upgrade method. If Device Model is selected, all devices of the same model at the site will be upgraded in a batch. Configure the upgrade target version. Specifically, select Upgrade Software Version and Upgrade Patch Version, or click Upgrade all to the latest version. You can decide whether to uninstall patches.
- If Device Name is selected, all devices are displayed and you can select devices to upgrade. Configure the upgrade target version. Specifically, select Upgrade Software Version and Upgrade Patch Version, or click Upgrade all to the latest version. You can decide whether to uninstall patches.
- To roll back patches, set Uninstall Patch to Uninstall.
- To install patches, set Uninstall Patch to Do not uninstall.
- Select the upgrade method. If Device Model is selected, all devices of the same model at the site will be upgraded in a batch. Configure the upgrade target version. Specifically, select Upgrade Software Version and Upgrade Patch Version, or click Upgrade all to the latest version. You can decide whether to uninstall patches.
- Click OK. The Summary Of Change page is displayed. Then, click OK. The upgrade plan is configured successfully.
- When a device is being upgraded and you modify parameters in the Software Update Restart Time area, the modification will not take effect.
- A device does not restart for the patch to take effect during a hot patch upgrade. The hot patch takes effect at the time specified by Software Update Restart Time in the upgrade plan.
- If you log in to a device through the CLI and delete the device patch, the current patch version on the iMaster NCE-Campus web UI will not be updated immediately. The patch version will be updated on the web UI after you bring the device offline and then online. The following figure shows an example.
- On the Perform the Upgrade page, you can view the upgrade result, upgrade details, upgrade progress, and upgrade failure causes. If a device fails to be upgraded, you can check the upgrade failure cause and rectify the fault. Then select the device and click Upgrade Again to re-upgrade the device.
- If a device fails to be upgraded, move the cursor over the failure cause to view details. If the failure cause is one of the following, the system automatically upgrades the device again after the fault is rectified. If the failure cause is not listed in the following, you need to manually upgrade the device again.
- The file server is unreachable or no upgrade file exists. Check the network between the device and file server. Specifically, ping the IP address or telnet the port 18020/18021 of the file server. If the network connectivity is normal, log in to the file server and check whether the file server is normal, and check whether the required file exists on the file server. In addition, file download fails if the ESN contained in the device certificate is different from the actual device ESN. In such cases, check the device certificate to see whether the device certificate matches the device ESN. For details, see Viewing the Device ESN and Certificate.
- The file download progress fails to be obtained on the device. The system will re-deliver the file in five minutes.
- System software backup is ongoing on the device. The device will be automatically upgraded when the backup is complete.
- Communication fails. Check whether the device can properly send and receive packets and try again later after the fault is rectified.
- Communication is abnormal. Check whether the device can properly send and receive packets and try again later after the fault is rectified.
After a device is successfully upgraded, you need to check whether the device configuration is successfully delivered. Specifically, choose Configuration Result tab page. If Configuration Status is Success, the configuration has been successfully delivered.
from the main menu and check Configuration Status on the displayed - (Optional) Select the device that needs to be rolled back and click Rollback. If the upgrade fails or the version is incorrect after the upgrade, you can roll back the device system software to its source version.
- This function is supported only on switches running V200R019C10SPC500 or a later version.
- Before rolling back a device, ensure that the system software installed before the upgrade is not deleted from the device.
If the rollback fails, rectify the fault based on the failure cause and then perform a rollback again. The possible failure causes include:
- Inner error.
- No rollback info.
- Rollback files not exist.
- Verify rollback files fail.
- Set rollback files fail.
- Reboot fail.
- Operation not supported.
Viewing the Device ESN and Certificate
- Log in to the target device using CLI.
- Run the display esn command to check the device ESN.
- Run the display pki certificate realm default command to check the device certificate. Check whether the ESN in the certificate is the same as that obtained in the previous step.
Upgrading SNMP-Managed Devices
Context
Upgrading devices can help fix bugs in the current version, enhance functions, or support new functions. You can upgrade SNMP-managed devices in batches on iMaster NCE-Campus.
When a patch is uninstalled from a device, a scheduled task for uninstalling a patch cannot be configured.
Prerequisites
- An SFTP server has been configured during iMaster NCE-Campus installation. The default password for logging in to the SFTP server has been configured.
- The default password for logging in to the SFTP server has been changed. For details, see Configuring Southbound FTP Parameters.
- An SNMP-managed device has been added to iMaster NCE-Campus and is online.
Procedure
- Choose
, and click SNMP Protocol. The page for upgrading SNMP-managed devices then is displayed. from the main menu, click
- Click Create, enter a project name, and click OK to create an upgrade project.
- Perform the following operations on the Prepare for the Upgrade page.
- Click Import Software Packages, select the device system software package used for upgrade, click Upload to upload it to the SFTP server, and click OK.
After the system software package is uploaded successfully, set NE Type, File Type, and Software Version, and click OK.
- Click Import Check Packages, select the desired check package and signature file, and click OK to upload the files to the SFTP server.
- Select the system software package used for upgrade and the corresponding check package, select the desired NE configuration file, and click Next.
- Click Import Software Packages, select the device system software package used for upgrade, click Upload to upload it to the SFTP server, and click OK.
- On the Plan for the Upgrade page, click Create to configure an upgrade template based on the default template, that is, select check items involved in the default template as needed.
Table 4-128 lists available default upgrade templates.
Table 4-128 Default upgrade templatesDevice Type
Default Template Name
Application Scenarios
Switch
Default patch upgrade template for the S1720, S1730, S5700, S6300, and S6700
Patch upgrade in all paths of the S1720, S1730, S5700, S6300, and S6700
Default version upgrade template for the S1720, S1730, S5300, S5700, S6300, and S6700
Version upgrade in all paths of the S1720, S1730, S5300, S5700, S6300, and S6700
Default cluster upgrade template for the S9300 and S12700
Cluster upgrade in all paths of the S9300 and S12700
Default patch upgrade template for the S7700, S9300, S9700, and S12700
Patch upgrade in all paths of the S7700, S9300, S9700, and S12700
Default single-chassis upgrade template for the S7700, S9300, S9700, and S12700
Single-chassis upgrade in all paths of the S7700, S9300, S9700, and S12700
AR
Software default template
Software default template for AR routers
Patch default template
Patch default template for AR routers
Firewall
By default, the V5-V5 Dual version is upgraded.
(V500R001-V500R001, V500R002-V500R002, V500R002, V500R002-V500R005, V500R005-V500R005)
Supporting Dual Machine Equipment (USG6100,USG6300,USG6500,USG6600,USG9500,SeMG9811-X,EUDEMON200E-N,EUDEMON1000E-N,EUDEMON8000E-X)Version upgrade
By default, the V5-V5 version is upgraded.
(V600R006-V600R006, V600R006-V600R007, V600R007-V600R007)
Supporting Equipment (USG6100,USG6300,USG6500,USG6600,USG9500,SeMG9811-X,EUDEMON200E-N,EUDEMON1000E-N,EUDEMON8000E-X,ANTIDDOS8000)Version upgrade
By default, the V5-V5 version is upgraded.
(V500R001-V500R001, V500R002-V500R002, V500R002, V500R002-V500R005, V500R005-V500R005)
Supporting Equipment (USG6100, USG6300, USG6500, USG6600, USG9500, SeMG9811-X, EUDEMON200E-N, EUDEMON1000E-N, EUDEMON8000E-X, ANTIDDOS8000)Version upgrade
By default, the V6-V6 version is upgraded.
(V600R006-V600R006, V600R006-V600R007, V600R007-V600R007)
Supporting Equipment (USG6100E,USG6300E,USG6500E,USG6600E,USG6700E,EUDEMON200E-G,EUDEMON1000E-G,ANTIDDOS1800,ANTIDDOS8000)Version upgrade
Patch default template V5 (V500R001, V500R002, V500R005)
Supporting Equipment (USG6100, USG6300, USG6500, USG6600, USG9500, SeMG9811-X, EUDEMON200E-N, EUDEMON1000E-N, EUDEMON8000E-X, ANTIDDOS8000)Patch upgrade
Patch default template V6 (V600R006, V600R007)
Supporting Equipment (USG6100E, USG6300E, USG6500E, USG6600E, USG6700E, EUDEMON200E-G, EUDEMON1000E-G, ANTIDDOS1800, ANTIDDOS8000)Patch upgrade
- Click Next, configure a rollback template, and click OK. If the upgrade fails, the system automatically rolls back devices to the specified source version based on the rollback template.
- On the Perform the Upgrade page, click Create, select the desired upgrade template and devices to be upgraded, and click OK.
If a large number of devices need to be upgraded, click Batch Input to import the devices in batches.
- Select the desired upgrade task and click Start.
- After the upgrade is complete, click the task name to view the upgrade result.
- If some devices fail to be upgraded, click Task Report to export the upgrade task report, check the failure cause, rectify the fault, and upgrade the devices again.
Switch Upgrade
Model |
---|
S1720 series |
S1730 series |
S5300 series |
S5700 series |
S6300 series |
S6700 series |
S7700 series |
S9300 series |
S9700 series |
S12700 series |
AR Upgrade
Model |
---|
AR129CVW |
AR129CGVW-L |
AR161EW |
AR1220E |
AR2220E |
AR651C |
AR651 |
AR651W |
AR657W |
AR617VW-LTE4EA |
AR617VW |
AR611W-LTE4CN |
AR611W |
AR6120 |
AR6121 |
AR6300 |
AR6140-9G-2AC |
Firewall Upgrade
Model |
---|
USG6100 |
USG6300 |
USG6500 |
USG6600 |
USG9500 |
USG6100E |
USG6300E |
USG6500E |
USG6600E |
USG6700E |
EUDEMON200E-N |
EUDEMON200E-G |
EUDEMON1000E-N |
EUDEMON1000E-G |
SEMG9811-X |
ANTIDDOS1800 |
ANTIDDOS8000 |
ANTIDDOS12000 |
EUDEMON8000E-X |
EUDEMON9000E-X |
Restoring Devices to Deployment Configurations Within One Click
Context
When bringing a device offline or replacing a device, you can restore the device to its deployment configurations to facilitate fast reset to its deployment state.
Only ARs support this function.
Procedure
- Choose from the main menu.
- Select the device to be reset, and click More > Restore Deployment Configurations.
- In the displayed High Risk dialog box, click Yes.
Restoring a device to its deployment configurations will cause the device to go offline. As a result, the device fails to be managed by iMaster NCE-Campus.
Restoring Devices to Factory Defaults Within One Click
Context
When bringing a device offline or replacing a device, you can restore the device to its factory defaults within one click.
- Only switches running V200R011C10SPC550 and later versions support this function.
- The firewalls, ARs, WACs, Fit APs, and stacks do not support this function.
Procedure
- Choose from the main menu.
- Select the device to be reset, and click More > Restore Factory Defaults.
- In the displayed CAUTION dialog box, select I have fully understand possible risks, and click Yes.
Viewing AP Login and Logout Logs
Context
Tenant administrators can query the login and logout logs of an AP, including failure causes.
Procedure
- Choose from the main menu.
- Click the name of the desired AP. The Single Device Info page is displayed.
- Click the Event Logs tab to view the AP's login and logout logs.
Replacing Device Certificates
Context
A device certificate is a digital file that has the digital signature assigned by a CA and includes information about the public key owner, public key issuer, validity period, and specific extension information. A Secure Sockets Layer (SSL) channel can be set up between a device and a server using a device certificate to ensure security for information transmission between the two ends.
When the current device certificate expires or cannot meet security requirements, a new certificate must be installed to ensure security.
After certificates are replaced, devices will automatically restart. Otherwise, the replaced certificates do not take effect. Since devices go offline during the restart, ensure that services will not be affected during certificate replacement.
Procedure
- Log in to iMaster NCE-Campus as a tenant administrator. Choose from the main menu, click the Device Certificate Management tab, select the device whose certificate needs to be replaced, and click Certificate Signing Request to export the certificate request file of the device (into a .csr file).
- A certificate request file cannot be exported for multiple times. Otherwise, the previously exported certificate request files become invalid. If you have used a certificate request file exported earlier to apply for a certificate, the applied certificate will also become invalid.
- For details about how to determine whether a device certificate is an old certificate, see How Do I Determine Whether a Device Certificate Is an Old Certificate.
- Upload the request file to the PKI website to apply for a new certificate, and obtain the pem public key file. To apply for this public key file, contact Huawei engineers.
- Upload the device certificate and click Upload Certificate. In the displayed dialog box, select the certificate file and click OK.
- The certificate to upload must be named by the device ESN. Otherwise, the certificate cannot be uploaded.
- On the Device Certificate Management page, wait until the new certificate status changes to Uploaded, and click Submit to replace the certificate. After the certificate is delivered, iMaster NCE-Campus sends a restart command to the device. If the new certificate status is Delivery success after the device restart, the certificate is successfully replaced.
For details about new certificate statuses, see Table 4-132.
Table 4-132 New certificate statusesNew Certificate Status
Description
Not uploaded
The new certificate has not been uploaded to the device.
Uploaded
The new certificate has been uploaded to the device.
Delivering
iMaster NCE-Campus is delivering the new certificate to the device.
Delivery failure
iMaster NCE-Campus fails to deliver the new certificate to the device. You need to replace the certificate again.
Delivery success
iMaster NCE-Campus has successfully delivered the certificate to the device. Certificate replacement is successful.
Changing the Device Time
Context
The Network Time Protocol (NTP) defines the time synchronization mechanism. It synchronizes the time between distributed servers and clients.
When the time of all the devices on a network need to be synchronized, it is almost impossible for an administrator to manually change the system clock through the CLI. This is because the workload is heavy and clock accuracy cannot be ensured. NTP can quickly synchronize the clocks of devices on the network and ensure high precision.
Procedure
- Choose from the main menu.
- Choose Basic Info area, configure the time zone and NTP server for devices. . In the
Remotely Logging In to the Device CLI
Context
A tenant administrator can remotely log in to the CLI of an online device from iMaster NCE-Campus and perform operations in the CLI.
After network devices are managed by iMaster NCE-Campus, if you need to clear configuration on the devices using commands, for example, if a management subnet changes, or the network devices need to be managed by iMaster NCE-Campus of a new version, running the reset saved-configuration command clears only the configuration files saved on the network devices. As such, you cannot remotely log in to the network devices using STelnet.
When clearing configuration on S series switches, in addition to the reset saved-configuration command, run the following command to clear configuration files and database data saved on the devices.
- Versions earlier than V200R019C00SPC500: Run the reset cloud-mng db-configuration command in the user view.
- V200R019C00SPC500 and later versions: Run the reset netconf db-configuration command in the user view.
- This operation is not supported for devices at a site created based on configuration files.
Procedure
- Choose from the main menu.
- Click the name of the desired device to access the Single Device Info page.
- Click Command Line in the upper right corner of the page to remotely log in to the CLI of the device.If the login fails and the following error information is displayed, rectify the fault and log in again.
- IP/port did not match: The IP address or port is incorrect.
- Authentication fail: The authentication fails.
- Disconnected by device: The device is disconnected.
- Unable to open channel: The SSH channel fails to be set up.
- Connection Reset By Peer: A network exception occurs.
The following figure shows an example.
- After remotely logging in to a device's CLI, do not modify the configurations delivered by iMaster NCE-Campus to the device. Otherwise, services will be affected.
- Do not run commands to change the level of logs to be printed to debug.
- In any scenario, the interval for clicking Command Line must be greater than one minute.
- Before exiting the MSP operating mode, you need to close the CLI window (if the remote CLI login function is enabled). If you exit the MSP operating mode and then close the CLI window of a device, you will fail to log in to the CLI of the device again. In this case, you can use either of the following solutions:
- Wait for 10 minutes after which iMaster NCE-Campus will automatically clear the data and then open the CLI again.
- Log out and then use the MSP account to log in to the device CLI again.
- In the CLI, if parameter names and their values are not in the same column due to abnormal line breaks, add any font in the monospaced font family to the operating system font library.
- If you remotely log in to the CLI of another device from the CLI of a cloud managed device, you can press Shift+Backspace to delete unnecessary information when entering commands in the CLI.
- If authentication without a password is configured on iMaster NCE-Campus cluster nodes, the function of remotely logging in to the device CLI from iMaster NCE-Campus will be unavailable.
- VXLAN-capable switches do not support remote login to the device CLI.
- Only the following models of AR support remote login to the device CLI:
AR-Sc-U-BC, AR-Se-U-BC, AR-Sa-U-BC, AR-So-U-BC, AR-Sc-Lc-BC, AR-Se-L-BC, AR-Sa-La-BC, AR-So-Lo-BC, AR-Sc-Lc-MC, AR-Se-L-MC, AR-Sa-La-MC, AR-So-Lo-MC, AR-Sc-MC, AR-Se-MC, AR161EW, AR169EGW-L, AR169EW, AR161, AR161W, AR161F, AR161FW, AR161FGW-L, AR168F, AR169F, AR169FGW-L, AR1220C, AR1220EVW, AR1220E, AR2220, AR2220E, AR2204-51GE, AR2204-27GE, AR2204XE, AR2240, AR2240C, AR3260, AR3670, AR1000V, AR1610-X6, AR651W-X4, AR651-X8, AR651, AR651C, SRG3360, AR2204-51GE-P, AR2204-51GE-R, AR2204-27GE-P.
- (Optional) Click Export Screen Display to export command outputs.
Logging In to a Device's Web System
Prerequisites
If you need to log in to the web system of a WAC through iMaster NCE-Campus, ensure that you have run the following command on the WAC to configure an interface for interconnection with iMaster NCE-Campus. Otherwise, you may fail to log in to the WAC's web system.
http secure-server server-source -i Vlanif 11 //The VLANIF interface is used for the WAC to communicate with iMaster NCE-Campus. VLANIF 11 is used as an example here.
Procedure
- Choose from the main menu.
- Click the name of the desired device to access the Summary page.
- Click Device Configuration in the upper right corner of the page to remotely log in to device's web system.
When you click Device Configuration, the SSH proxy tunnel function is automatically enabled. After you close the web system, the SSH proxy tunnel function is automatically disabled after some time.
- A tenant administrator cannot log in to the web systems of two devices at the same time.
- This function is supported on firewalls and WACs.
- This function is supported on the AR6280 and AR651C.
- This function is supported on the following switch models:
- S12700 series switches
- S12700-E series switches
- S7700 series switches
- S5720-56C-HI-AC
- S5720-32C-HI-24S-AC
- S5720-56C-PWR-HI-AC
- S5720-56C-PWR-HI-AC1
- S5730-36C-HI
- S5730-36C-PWH-HI
- S5730-44C-HI
- S5730-44C-PWH-HI
- S5730-60C-HI
- S5730-60C-PWH-HI
- S5730-68C-HI
- S5730-68C-PWH-HI
- S5730-36C-HI-24S
- S5730-44C-HI-24S
- S5730-60C-HI-48S
- S5730-68C-HI-48S
- S5731-H24T4XC
- S5731-H48T4XC
- S5731-H24P4XC
- S5731-H48P4XC
- S6720-30L-HI-24S
- S6720-50L-HI-48S
- S6730-H48X6C
- S6730-H24X6C
Upgrading the Signature Database on Devices
Service awareness (SA) identifies the protocols and applications running on networks through deep packet identification and classification. An SA signature database contains application identification rules and information about application names and description. Devices load the SA signature database to obtain related data for application identification.
As applications keep changing and increasing, devices need to periodically upgrade the application signature database to improve the application identification accuracy. This section describes how to load an SA signature database from iMaster NCE-Campus to devices.
The following APs do not support SA signature database upgrade:
AP2050DN, AP2050DN-E, AP2050DN-S, AP4050DN-E, AP4050DN-HD, AP6150DN, AP7050DE, AP8030DN, AP8130DN, R230D, R240D, R250D, R250D-ER, R251D, R251D-E, R450D, AP200EC, AD9431DN-24X, AP4130DN, AP2030DN, AP6010DN-AGN, AP3010DN-AGN, AP2010DN, AP6510DN-AGN, AP5030DN-S.
Signature Database Upgrade Process
Control server: allocates and manages download servers, and checks whether download servers and signature database files are available. The default domain name of a control server is sec.huawei.com. All control servers are owned by Huawei and deployed with security and high reliability.
Release server: distributes signature database files to download servers.
Download server: stores signature database files. iMaster NCE-Campus downloads signature database files from download servers. Download servers are deployed by region, including China, Asia, Europe, and America.
- iMaster NCE-Campus: downloads signature database files from download servers to a local file server.
Figure 4-15 shows the signature database upgrade process.
iMaster NCE-Campus sends a signature database upgrade request to the control server to request the IP address of a download server. The communication between them is encrypted and no other data processor is involved.
iMaster NCE-Campus communicates with the control server using HTTPS (port 443) or HTTP (port 80). If iMaster NCE-Campus upgrades the signature database through a proxy server, only HTTP can be used.
After verification succeeds, the control server sends the IP address of a download server to iMaster NCE-Campus.
- iMaster NCE-Campus requests signature database files from the download server.The protocol and port used by iMaster NCE-Campus to communicate with the download server varies.
If iMaster NCE-Campus uses HTTPS and port 443 to communicate with the control server, iMaster NCE-Campus uses the same protocol and port number to communicate with the download server.
If iMaster NCE-Campus uses HTTP to communicate with the control server:
If iMaster NCE-Campus directly connects to the upgrade center, it connects to the download server using FTP in passive mode. The FTP control channel port number is 21, and the data channel port number is dynamically allocated from 10001 to 15000.
If iMaster NCE-Campus connects to a proxy server, it connects to the download server using HTTP and port 80.
- The download server sends encrypted signature database files to iMaster NCE-Campus.
HTTPS is recommended, because it is securer than HTTP. When using HTTP, strictly restrict the matching conditions of security policies.
- A device request signature database files from iMaster NCE-Campus. The requested data includes the device model, device version, device ESN, signature database type, signature database version, and country/region (optional).
- iMaster NCE-Campus sends signature database files to the device based on the device request.
Prerequisites
- The configuration of the signature database server has been completed. For details, see Configuring the Signature Server.
- The latest signature database files have been downloaded to iMaster NCE-Campus. For details, see Upgrading the Signature Database on iMaster NCE-Campus.
Procedure
- Choose from the main menu.
- Select the site for which the signature database needs to be upgraded and click Create New Policy. On the Create New Policy page that is displayed, configure a policy for upgrading the signature database at a specific time every week or immediately, and click OK.
- All tenants share one set of signature database files.
- ARs support the upgrade of two types of signature databases: SA_H30071001(1600+) and SA_H30071000(6000+).
- After a device is added to a site, you are advised to upgrade the signature database on the device to ensure that the version of the signature database on the device is the same as that on iMaster NCE-Campus.
- During the upgrade, click
to view the upgrade progress.
Before an upgrade, the system checks whether the version of the local signature database is the latest version and performs an upgrade if the version is not the latest. The new signature database is saved to the file server for devices to download, and is also saved to the database for devices to use for application query. The old signature database is automatically deleted if it is not used by any site. If the old signature database is still used by a site, this signature database is retained in the database and on the file server.
- To view the upgrade details, click the Upgrade Details tab.
Activating a Device License
Context
Tenant administrators can activate a device license on iMaster NCE-Campus.
Pre-configuration Tasks
The tenant administrator has uploaded a device license file to iMaster NCE-Campus. For details, see Managing Files.
Procedure
- Choose from the main menu.
- Select the device license to be activated, and click Active.
Parameter Description
Parameter |
Description |
---|---|
Device Name |
Name of the device for which you want to activate the license. |
ESN |
Device ESN. |
Site Name |
Site to which the device belongs. |
Activation status |
License activation status. The options are as follows:
|
Last activated license |
License activated last time. |
License Status |
Current status of the device license. The options are as follows:
|
Activation time |
Time when the license is activated. |
Expiration Time |
Time when the license expires. |
InactiveLicense |
License file that has been downloaded to the device, but not activated. |
Delivering Commands to AP-IoT Devices
Context
Third-party IoT cards can be installed on APs. To configure and maintain third-party IoT services, you can deliver commands to the IoT cards through iMaster NCE-Campus.
- Currently, commands can be delivered only to BOE SES-Imagotag IoT cards.
- You can obtain the commands that can be delivered to IoT cards from the card supplier. If a command is incorrect, this command may fail to be executed or the card may function improperly. Exercise caution when delivering commands to IoT cards.
Procedure
- Choose from the main menu. The device monitoring page is displayed.
- Choose to view IoT card information.
The meanings of icons in the Operation column are as follows:
: Reset IoT card network configurations.
: Restart the IoT card.
: Restore the IoT card to its factory defaults.
: Switch flash partitions of the IoT card.
- Deliver a command to IoT cards to configure IoT services.
- To deliver a command to a single IoT card, select the desired IoT card and click Deliver commands.
In the dialog box that is displayed, click OK. Enter the command to be delivered and click OK.
- Click All deliver commands to deliver a command to all online IoT cards at a site.
In the dialog box that is displayed, click OK. Enter the command to be delivered and click OK.
- To deliver a command to a single IoT card, select the desired IoT card and click Deliver commands.
- Click the Command Delivery Results tab and check whether the command is successfully delivered. If the command fails to be delivered, contact technical support or the IoT card supplier to rectify the fault based on the failure cause in the Failure Cause column.
Click View in the Detail column to view command delivery details.
Configuration File Management
Fundamentals
Definition
Configuration file management refers to the operations of backing up, restoring, baselining, viewing, importing, exporting, and comparing configuration files of managed devices, as well as configuring current configurations as startup configurations, using the configuration file management component.
Benefits
With the configuration file management function, you can back up device configuration files in a timely manner, improving service security and reliability. If the configuration file of a device is damaged due to a fault, the backup configuration file can be uploaded to the device to quickly restore the device configuration data. In addition, you can view configuration changes. After configuration files on devices are backed up, the system automatically compares the differences and obtains the configuration change information, helping users understand the configuration changes on the network in time.
Application Scenarios
- Backing up configuration files: Device configuration files change with device service changes and expansion. Timely device configuration file backup improves service security and reliability.
- Restoring configuration files: If a fault occurs on a device, the backup configuration file can be uploaded to the device to quickly restore the device configuration data.
- Importing configuration files: You can import local configuration files to iMaster NCE-Campus and restore the imported configuration files on devices.
- Exporting configuration files: You can export backup configuration files from devices to the local PC for you to view.
- Configuring the current configuration as the startup configuration: You can run commands to modify the current configuration of a device, but the modified configuration will be lost after the device restarts. To enable the new configuration to take effect after a restart, you can save the current configuration in the configuration file before restarting the device.
- Viewing configuration changes: You can compare two configuration files to view differences between them.
- SNMP-managed devices support all scenarios whereas NETCONF-managed devices support selective scenarios, as listed in Table 4-134.
Table 4-134 Scenarios supported by NETCONF-managed devices
Device (Site)
Startup Configuration Backup
Running Configuration Backup
Restore to Start
Restore to Running
Running to Startup
WAC (at sites created in configuration file mode)
No
Yes
Yes
No
No
Switch (at sites created in configuration file mode)
No
Yes
Yes
No
No
AR (at sites created in configuration file mode)
No
No
No
No
No
AP (at sites created in configuration file mode)
No
Yes
No
No
No
WAC (at sites created in default mode)
No
Yes
No
No
No
Switch (at sites created in default mode)
No
Yes
No
No
No
AP (at sites created in default mode)
No
Yes
No
No
No
AR (at sites created in default mode)
No
No
No
No
No
Firewall (at sites created in default or configuration file mode)
No
No
No
No
No
Fundamentals
Figure 4-16 shows the fundamentals of backing up configuration files on iMaster NCE-Campus.
- The administrator performs backup operations using the configuration file management function.
- The configuration file management service delivers a command to the device to back up the configuration files and notifies the device of the backup path.
- After receiving the command, the device uploads its configuration files to iMaster NCE-Campus using SFTP.
- The configuration file management service checks the backup status. After the backup is complete, the administrator can view the backup result.
Dependency and Limitation
- Only SFTP can be used to back up and restore configuration files. Before backing up and restoring configuration files, enable the SSH client function on the device.
- In normal cases, it takes about 30 minutes to back up or restore configuration files of 200 devices at the same time. It is time-consuming to deliver a large amount of device configuration data. Therefore, back up or restore configuration files during off-peak hours to avoid affecting network services.
- If the current configuration file is incorrect during device configuration file restoration, the device services may be interrupted. Before restoration, ensure that the configurations in the current file are correct to prevent network services from being interrupted in the case of misoperations.
- When a stack member changes (for example, a stack member is added or deleted) or a standalone device is added to a stack, the system clears all configuration files, backup tasks, and configuration change information related to the device.
Backing Up Configuration Files
Context
After a device is configured and brought online, you are advised to back up the device configuration file promptly to avoid loss of important service configuration data.
Prerequisites
Southbound FTP parameters have been set. For details, see Configuring Southbound FTP Parameters.
Procedure
- Choose . from the main menu
- Choose Configuration File from the navigation pane.
- In the configuration file, select one or more devices and click Backup.
If the latest backup time and latest backup file are displayed, the configuration file is backed up successfully.
- NETCONF-managed devices support backup of only running configurations, instead of startup configurations.
- SNMP-managed devices support backup of both running and startup configurations.
- Currently, configuration files of only APs, WACs, and switches can be backed up.
- Click the name of the configuration file to view the backup file details, including the device name, device IP address, file name, and file content.
- Click Back to return to the configuration file list.
Importing a Device Configuration File
Context
You can import local configuration files to iMaster NCE-Campus. To restore configuration files on devices, you can restore the imported local configuration files on the devices.
Before importing local configuration files, ensure that the configuration files are correct.
Procedure
- Choose . from the main menu
- Choose Configuration File from the navigation pane.
- In the configuration file list, click
in the Operation column.
- Click
and select a local configuration file. You can decide whether to select Set File As Baseline.
Files in .txt, .conf, or .cfg format can be imported. The size of a single file cannot exceed 2 MB.
- Click OK to return to the configuration file list.
If the latest import time and the imported file are displayed in the list, the configuration file is imported successfully.
Exporting a Device Configuration File
Context
You can export important configuration files to a local PC as required.
Procedure
- Choose . from the main menu
- Choose Configuration File from the navigation pane.
- Export configuration files.
- Export latest configuration files one by one.
In the configuration file list, click
in the Operation column of a record to export the latest running configuration or startup configuration.
- Export historical configuration files one by one.
- In the configuration file list, click
in the Operation column of a device that has a backup file.
- Click
in the Operation column of a record to export the running or startup configurations.
- In the configuration file list, click
- Export selected device configuration files in batches.
Select one or more records to be exported, click
, choose Export > Export Selected NE Configs, and click Export.
- Export all device configuration files in batches.
Click
, choose Export > Export All NE Configs, and click Export.
- Export latest configuration files one by one.
Restoring a Configuration File on a Device
Context
- Restoring a configuration file on a single device
For a single device, restore the backup configuration file or the configuration file uploaded from the local PC to the device. If there are multiple configuration files, you can select a file as needed. You can also set one of the configuration files as the baseline file and restore the baseline file to the device.
- Restoring configuration files on devices in batches
For one or more devices, restore the specified baseline file to the devices. Before batch restoration, you need to set a configuration file as the baseline file.
Procedure
- Choose . from the main menu
- Choose Configuration File from the navigation pane.
- NETCONF-managed devices can be restored to startup configurations only, and cannot be restored to running configurations.
- SNMP-managed devices can be restored to both startup and running configurations.
- Configuration files of APs, WACs, and LSWs at sites created in default mode can be backed up, but cannot be restored.
- Configuration files of APs, WACs, and LSWs at sites created in configuration file mode can be backed up. Only configuration files of WACs, LSWs and the AR1610-X6 can be restored.
- Restore configuration files.
- If the current configuration file is incorrect during device configuration file restoration, the device services may be interrupted. Before restoration, ensure that the configurations in the current file are correct to prevent network services from being interrupted in the case of misoperations.
- If you restore the configuration to the running configuration, the restoration operation takes effect immediately. If you restore the configuration to the startup configuration, the restoration operation takes effect after the device restarts.
- During configuration file restoration, deleted and modified records are restored on the device. However, configuration data that exists on the device but not included in the backup configuration file remains unchanged.
Operation
Description
Restoring a configuration file on a single device
- Configuring a baseline file: Click
in the Operation column of a device and select a configuration file. Then, click
to set the configuration file as the baseline file.
- Restoring a configuration file: Click
in the Operation column of a device and select a configuration file to be restored. Then, click
and choose To Running or To Startup.
Restoring configuration files on devices in batches
- Restoring baseline files in batches
- Configuring a baseline file: Click
in the Operation column of a device and select a configuration file. Then, click
to set the configuration file as the baseline file.
- Click Back. In the configuration file list, select one or more devices, click Recover, and select To Running or To Startup.
Configuring the Running Configuration as the Startup Configuration
Context
You can configure the running configuration on a device as the configuration for next startup.
You can modify the running configuration of a device through commands. The configuration is temporary and can be modified again. You can save the running configuration on one or more devices to configuration files and configure them as startup configurations so that configurations are still valid after the devices restart.
Procedure
- Choose . from the main menu
- Choose Configuration File from the navigation pane.
- In the configuration file list, select one or more devices, click
in the upper right corner, and choose Running to startup.
On NETCONF-managed devices, the running configuration cannot be configured as the startup configuration.
Configuring a Configuration File Backup Task
Context
In addition to manual configuration file backup, the system also provides the function of automatically backing up configuration files periodically. In a backup task, you can specify the devices where configuration files need to be backed up and the time when the backup is performed.
- NETCONF-managed devices support backup of only running configurations but not startup configurations.
- SNMP-managed devices support backup of both running and startup configurations.
- Only APs, WACs, and LSWs support backup of configuration files.
Procedure
- Choose . from the main menu
- Choose Backup Task from the navigation pane.
- Click Create and configure a backup task.
- Click OK. If the information about the created task is displayed in the task list, the task is created successfully.
Viewing Configuration Changes
Context
iMaster NCE-Campus allows you to compare the latest backup configuration file with the configuration file previously backed up, including adding, deleting, and modifying lines. You can view details about configuration changes.
Procedure
- Choose . from the main menu
- Choose Config Changes from the navigation pane.
- In the list, view the device name and IP address, configuration change time, file type, and number of lines (added, deleted, or modified) in the file.
- Click
to view configuration change details.
Configuring Backup Parameters
Context
You need to configure the following backup parameters:
- Max. backup files
This parameter indicates the maximum number of startup configuration files or backup configuration files on a device. When the number of backup configuration files exceeds the upper limit, the earliest backup configuration file is deleted by default.
- Alarm burst mode
The policy for periodically saving configuration files must be configured on a device. Before saving the configuration file periodically, the device checks the current configuration file. If the configuration file is different from the one that is saved last time or two files are the same, but the configuration file has been modified, the device saves the configuration file periodically. When detecting the alarm that the device periodically saves the configuration file, iMaster NCE-Campus automatically backs up the device's configuration file.
The Huawei S5700 series Ethernet switch V200R019C00 is used as an example. Run the following command to configure the switch to periodically save the configuration file. For the operations for other device types, see the device configuration manuals.
The Huawei S5700 series Ethernet switch V200R019C00 is used as an example. You need to run the following command to configure the switch to periodically save its configuration file. For operations on other device types, see corresponding device configuration guides.
set save-configuration [ interval interval | cpu-limit cpu-usage | delay delay-interval ] *
This function is not supported on NETCONF-managed devices.
- Change burst alarm
After the running configuration of a device is backed up or configured as the startup configuration, if the configuration file is different from that backed up last time, iMaster NCE-Campus automatically sends a configuration change alarm. If no difference is found, the latest configuration file that is successfully backed up will be overwritten.
- Backup strategy
A backup policy can be configured to back up only the running configuration, only the startup configuration, or both running and startup configurations.
Procedure
- Choose . from the main menu
- Choose Backup Parameters from the navigation pane.
- Set backup parameters.
By default, Alarm Burst Mode and Change Burst Alarm are disabled. You are advised to enable these functions.
- Click Apply.
SNMP-Managed Device Management and Maintenance
Device Management
Viewing Information About an SNMP-managed Device
Context
After SNMP-managed devices are added to eSight, you can view device resources, device panels, current and historical device alarms, and device resource details.
Procedure
- Choose from the main menu and click the name of an SNMP-managed device.
- View device details.
- Resource overview
Choose
from the navigation pane to view device resource information, such as device alarms, interface operating status, power operating status, fan operating status, average CPU usage, average memory usage, responding time, unreachable percentage in a day, top 5 interfaces by rate, configuration file changes, and link relationships. You can modify device names, as well as refreshing and synchronizing device data. - Device panel
Choose
from the navigation pane. You can view the information about the device panel, zoom in or zoom out the panel, refresh the panel information, and display or hide legends. - Current alarms
Choose More to acknowledge, clear, or export alarms.
from the navigation pane to view current device alarms. You can also click - Historical alarms
Choose More to export alarm remarks.
from the navigation pane to view historical device alarms. You can also click - Device resources
Choose
from the navigation pane, and click different tabs to view details about the device's chassis, cards, subcards, and interfaces.
- Resource overview
Configuring an SNMP-managed Device
Context
After an SNMP-managed device goes online, you can manage the device interfaces, compare device configuration files, re-configure protocol parameters, view and synchronize device VLAN information, set device polling parameters, and configure WLAN services.
Procedure
- Choose from the main menu and click the name of an SNMP-managed device.
- Configure the selected SNMP-managed device.
- Managing device interfaces
Choose
from the navigation pane to manage the device's interfaces.- View: Click an interface name in the list to view the interface details.
- Enable: Select the interface to be enabled and click Enable. After the operation is successful, the interface transitions to the Up state.
- Disable: Select the interface to be disabled and click Disable. After the operation is successful, the interface transitions to the Down state.
- Modify Remark: Select the interface whose remarks need to be modified, click Modify Remark, modified the remarks, and click OK.
- Synchronize: Select the interface whose information needs to be synchronized and click Synchronize to synchronize the interface information to iMaster NCE-Campus.
- Comparing device configuration files
Choose
from the navigation pane to compare configuration files. - Setting protocol parameters
- Set SNMP parameters. Specifically, choose Protocol Parameters> SNMP Parameters from the navigation pane to modify SNMP settings.
- Set STelnet parameters. Specifically, choose Protocol Parameters> STelnet Parameters from the navigation pane to modify STelnet settings used by iMaster NCE-Campus to connect the selected device.
- Set SNMP parameters. Specifically, choose Protocol Parameters> SNMP Parameters from the navigation pane to modify SNMP settings.
- Synchronizing device VLAN information
- Choose Device VLAN > Device VLAN from the navigation pane to check device VLAN information. Click Synchronize to synchronize the device VLAN information.
- Choose Device VLAN > Port VLAN from the navigation pane to view information about VLANs configured on interfaces. Click Synchronize to synchronize the information about VLANs configured on interfaces.
- Choose Device VLAN > VLAN IF from the navigation pane to view VLANIF interface information. Click Synchronize to synchronize the VLANIF information.
- Choose Device VLAN > Device VLAN from the navigation pane to check device VLAN information. Click Synchronize to synchronize the device VLAN information.
- Choose WLAN Feature > AP from the navigation pane to view information about APs connected to the selected device. You can also restart the APs or restore the APs to their factory defaults.
- Managing device interfaces
Managing Device Resources
Context
After SNMP-managed devices are brought online, you can manage the chassis, cards, subcards, interfaces, and electronic labels of the devices.
Procedure
- Choose from the main menu.
- Manage different types of device resources.
- Managing chassis
- Choose Frame from the navigation pane. iMaster NCE-Campus displays the number of chassis of different device types and in different states in graphics. Chassis details are provided in a list.
- Perform the following operations to manage a chassis.
- Click
in the Operation column to configure remarks for a chassis.
- Click
in the Operation column to switch to the panel of the corresponding device.
- Select one or more records from the list, and then choose Export > Export Select > Export to CSV to export information about the selected chassis to an Excel or CSV file. or
- Choose Export > Export All > Export to CSV to export information about all chassis to an Excel or CSV file.
- Click
- Managing cards on devices
- Choose Board from the navigation pane. iMaster NCE-Campus displays the number of cards in different states, power supply states, and fan states in graphics. Card details are provided in a list.
- Perform the following operations to manage a device card:
- Click
in the Operation column to configure remarks for a card.
- Click
in the Operation column to switch to the panel of the corresponding device.
- Select one or more records from the list, and then choose Export > Export Select > Export to CSV to export the card information to an Excel or CSV file. or
- Choose Export > Export All > Export to CSV to export information about all cards to an Excel or CSV file.
- Click
- Managing subcards on devices
- Choose Subcard from the navigation pane. iMaster NCE-Campus displays the number of subcards in different states, power supply states, and fan states in graphics. Subcard details are provided in a list.
- Perform the following operations to manage a subcard:
- Click
in the Operation column to configure remarks for a subcard.
- Click
in the Operation column to switch to the panel of the corresponding device.
- Select one or more records from the list, and then choose Export > Export Select > Export to CSV to export the subcard information to an Excel or CSV file. or
- Choose Export > Export All > Export to CSV to export information about all subcards to an Excel or CSV file.
- Click
- Managing interfaces on devices
- Choose Port from the navigation pane. iMaster NCE-Campus displays the number of interfaces with different rates and in different states in graphics. Interface details are provided in a list.
- Perform the following operations to manage an interface:
- Click
in the Operation column to configure remarks for an interface.
- Click
in the Operation column to switch to the panel of the corresponding device.
- Select one or more records from the list, and then choose Export > Export Select > Export to CSV to export the interface information to an Excel or CSV file. or
- Choose Export > Export All > Export to CSV to export information about all interfaces to an Excel or CSV file.
- Click
- Managing electronic labels of devices
- Choose Electronic Labels from the navigation pane. iMaster NCE-Campus lists the detailed electronic label information.
- Perform the following operations to manage the electronic label of a device:
- Click Obtain Electronic Label. Select the desired device based on the NE type and subnet name. Click OK. If Electronic labels obtained completely is displayed, the electronic label is obtained successfully.
- Select one or more records from the list, and then choose Export > Export Select > Export to CSV to export the electronic label information to an Excel or CSV file. or
- Choose Export > Export All > Export to CSV to export information about all electronic labels to an Excel or CSV file.
- Configuring polling parameters
- Choose
- Choose
- Choose
- Managing chassis
Configuring Device Performance Monitor Task
Fundamentals
Context
iMaster NCE-Campus can collect, analyze, and display performance data (such as CPU usage and memory usage) of ICT resources (such as networks and devices), helping administrators learn about the health status and performance trend of the resources.
iMaster NCE-Campus allows administrators to learn about real-time performance statistics and performance trends of ICT resources, identify performance issues, and take effective measures, ensuring the optimal running status of resources.
Application Scenarios
Administrators can configure monitoring policies to monitor performance indicators of ICT resources on a daily basis and customize monitoring policies to monitor performance indicators of key resources.
- Configuring a monitoring policy
The system provides predefined monitoring groups and monitoring policies. Administrators can also create monitoring groups and monitoring policies based on the site requirements to monitor performance indicators of key resources and provide performance data for key events (for example, holiday) or health services.
- Viewing monitoring statistics
Administrators can learn the ICT resource performance by viewing real-time performance statistics, and understand the performance trends by collecting and analyzing historical performance statistics. The system allows administrators to view the device mapping information, management scale, and load information of Performance Monitoring to understand key information of Performance Monitoring.
Functions
Administrators can manage monitored resources by group, and configure monitoring policies to collect and analyze resource performance data through Performance Monitoring.
Function |
Description |
---|---|
Configuring a monitoring group |
Groups resources based on the resource type to filter resources during monitoring policy configuration and performance data viewing. |
Configuring a monitoring policy |
Configures a performance monitoring policy which includes monitored objects, performance indicators, performance data collection periods, and alarm thresholds. |
KPIs
- Management scale
If an indicator needs to be collected for a resource every 5 minutes, one collection unit is required. For example, if the receive rate needs to be collected for an interface every 5 minutes, one collection unit is required. The number of collection units is also related to the collection period.
- A shorter collection period requires more collection units. For example, if the receive rate needs to be collected for an interface every 30 seconds, 10 collection units are required.
- A longer collection period requires fewer collection units. For a collection task whose collection period is longer than 5 minutes, the collection scale is 5 minutes. For example, if the receive rate of an interface is collected every 5 minutes, the number of collection units is 1; if the receive rate of an interface is collected every 15 minutes, the number of collection units is also 1.
- Storage period of monitoring data
The storage period of performance data needs to be evaluated based on the storage capacity of the system. It is recommended that the storage period be smaller than or equal to seven days for raw data and be smaller than 90 days for aggregated data.
Table 4-136 Storage period of monitoring dataMonitoring Data Type
Description
Storage Period
Raw global settings
Raw data is real performance data collected from devices, is updated based on the collection period.
The default value is 7 days and can be changed.
Hourly aggregated global settings
Hourly-aggregated monitoring data is generated and updated by Performance Monitoring every hour after data calculation (such as calculating the sum, average value, maximum value, and minimum value).
The default value is 30 days and can be changed.
Daily aggregated global settings
Daily-aggregated monitoring data is generated and updated by Performance Monitoring every 24 hours after data calculation (such as calculating the sum, average value, maximum value, and minimum value).
The default value is 365 days and can be changed.
- Periodic tasks
To ensure consistency with service data and prevent performance data differences caused by exceptions such as node faults, the system periodically synchronizes monitoring policies, performance data collection tasks, monitored objects, and domain information of monitored objects. If the number of used collection units is close to or exceeds the maximum, you are advised to set the inspection period of the monitoring task to a value greater than or equal to 12 hours, ensuring that performance data collection is not affected by frequent periodic synchronization.
Table 4-137 Periodic tasksType
Description
Inspection Period
Periodic inspection of data collection tasks
Delivers performance data collection tasks to each service, and inspects the performance data collection tasks of each service and performance monitoring.
The default value is 12 hours and can be changed.
Periodic inspection of task status
Delivers requests to each service. Each service reports the status of all performance data collection tasks. Inspects the status of performance data collection tasks of each service and performance monitoring.
The default value is 12 hours and can be changed.
Periodic inspection of monitored resources
Inspects information about all resources, including the resource name, IP address, and group.
The default value is 12 hours and can be changed.
Periodic inspection of monitoring policies
Inspects monitored objects in monitoring policies, including the increase and decrease of monitored objects and whether monitored objects are in the management scale.
The default value is 12 hours and can be changed.
Implementation
Figure 4-17 shows the implementation of Performance Monitoring.
- ICT resources report resource information to Performance Monitoring.
- An administrator configures monitoring groups and monitoring policies.
- Performance Monitoring periodically delivers performance data collection tasks to ICT resources based on the configured monitoring policies.
- ICT resources report performance data to Performance Monitoring.
- The administrator views key running information about Performance Monitoring and collected performance data on Performance Monitoring.
- When a performance indicator of a resource exceeds the threshold, Performance Monitoring sends the alarm information to Alarms.
Configuring Performance Monitoring
(Optional) Configuring a Monitoring Group
Context
This section describes how to configure a monitoring group to filter monitored resources when configuring a monitoring policy or viewing performance data. The system provides monitoring groups for predefined services. Administrators can also create monitoring groups as needed.
Procedure
- Choose from the main menu.
- Choose Monitoring Group from the navigation pane.
- Hover your mouse over
to display the resource type switch panel and then select the required resource type. For example, choose Network > Device.
- (Optional) By default, the system provides Preset Group Organization and group organizations for each service. You can also create group organizations as required and later you can create monitoring groups in these group organizations.
Click
next to Group Organization, enter information about the group organization, and click OK.
By default, Preset Group Organization includes all monitored objects.
- Create a monitoring group.
Select a group organization and click Create.
- Configure the group information, add an object, and click OK.
- Add monitored objects to the monitoring group by rule:
- Move the cursor over
, and click
,
, or
to configure a rule for adding monitored objects.
- After a rule is configured, iMaster NCE-Campus automatically adds the resources that match the rule to the monitoring group. If resources added to iMaster NCE-Campus for management comply with the rule, iMaster NCE-Campus automatically adds the resources to the group.
- Move the cursor over
- Manually add monitored objects to the monitoring group:
Click Edit. In the displayed Select Resources dialog box, manually select objects you want to monitor and add them to the group.
- Add monitored objects to the monitoring group by rule:
Related Tasks
For details about other operations related to monitoring groups, see Table 4-138.
Operation |
Description |
---|---|
Modifying a group organization |
Select a group organization to be modified and click NOTE:
The default group organization named Preset Group Organization cannot be modified. |
Deleting a group organization |
If a group organization is no longer needed, you can select it and click NOTE:
|
Modifying a monitoring group |
Select the organization to which the monitoring group belongs. Click NOTE:
|
Deleting a monitoring group |
If a monitoring group is no longer needed, select the group and click NOTE:
|
Configuring a Monitoring Policy
Context
The system provides service-predefined monitoring policies. Administrators can also create or modify monitoring policies as needed to monitor performance indicators of key resources and provide performance data for key events (for example, holiday) or health services. A monitoring policy includes monitored objects, monitoring indicators, collection periods, and performance alarm thresholds.
Prerequisites
ICT resources have been added to iMaster NCE-Campus for management.
Procedure
- Choose from the main menu.
- Create a monitoring policy. After a monitoring policy is created, performance data collection is started by default.
- Choose Monitoring Strategy from the navigation pane.
- Move the cursor to
to display the resource type switch panel. Select a resource type, for example, Network > Device.
- On the Monitoring Strategy page, click Create Monitoring Strategy. The page for configuring a monitoring policy is displayed.
- Configure a monitoring policy by referring to Table 4-139, and click OK.
Table 4-139 Monitoring policy configurations
Configuration Item
Description
Configuration Operation
Basic information
Configuring the name and description of the monitoring policy
Enter the name and description of the monitoring policy.
Configuring the collection period of the monitoring policy
Select the interval for performance data collection.
Configuring whether the monitoring policy is shareable
- Yes
- Service-predefined monitoring policies can be modified by all users with the performance monitoring permission (except for the sharing setting, which can be modified only by system administrators).
- Other monitoring policies can be modified only by users who have at least one same role as the users who submit the policies.
- No
- Service-predefined monitoring policies cannot be modified by any users with the performance monitoring permission. They can be modified only by the system administrator.
- Other monitoring policies can be modified only by users who submit the policies and system administrators.
Monitored object
Configuring resources to be monitored
Click Select Monitoring Object. On the Select Resources page, select resources, and then click OK.
- Select resources by monitoring group: You can select a monitoring group from the current monitoring group or its upper-level monitoring group.
When you select a group, all resources in the group are selected by default.
If resources added to iMaster NCE-Campus for management comply with the rule of the group, iMaster NCE-Campus automatically adds the resources to the group as monitored objects.
- Select resources by resource type: You can select resources based on the resource type or its upper-level resource type.
NOTE:A maximum of 100 resources or monitoring groups can be selected.
Monitoring indicators
Configuring indicators to be monitored
Click Select Indicators. On the Select Indicators page, select indicators to be monitored and click OK.
- Yes
- Click
corresponding to a monitoring indicator, set the conditions for generating and clearing performance threshold alarms, and click OK.
After the configurations are complete, alarm thresholds of monitoring indicators are displayed in the monitoring policy.
If the performance indicator is greater than 80% for two out of four times, a critical alarm is generated. If the performance indicator is smaller than or equal to 70% for three out of four times, the critical alarm is cleared.
- Statistics period indicates the number of times performance data is collected.
- When configuring alarm thresholds of different severities, you need to ensure that the threshold for generating alarms of the same severity is harder to meet than that for clearing the alarms.
- The threshold for clearing alarms with a higher severity must be harder to meet than that for generating alarms with a lower severity.
- After the monitoring policy is configured and the collection period starts, view the monitoring information on the device details page. For details, seeViewing Information About an SNMP-managed Device.
Related Tasks
For details about other operations related to monitoring policies, see Table 4-140.
Operation |
Description |
---|---|
Modifying a monitoring policy |
Click |
Copying a monitoring policy |
Click |
Disabling a monitoring policy |
If a monitoring policy is not used temporarily, click |
Deleting a monitoring policy |
If the monitoring policy is no longer required, click |
Command Configuration Tool
Creating and Delivering Templates
Context
You can create and deliver a command template to configure services on SNMP-managed devices in batches.
The command configuration tool applies only to SNMP-managed devices, instead of cloud managed devices.
Procedure
- Log in to iMaster NCE-Campus as a tenant administrator and click Smart configuration tool on the homepage.
- Choose Template Deploy from the navigation pane.
- Create a user template.
- Click New Template on the right.
A tenant can create a maximum of 100 templates. A template is a set of configuration commands and can be used to configure same services for different devices in batches.
- Configure the template name, description, and commands to be delivered as needed.
- The template content cannot exceed 200 lines.
- Avoid delivering the reboot command. After a device restarts, iMaster NCE-Campus cannot check whether the command is successfully executed.
- When using the command configuration tool to configure commands to be delivered, you need to consider the view of the commands to be executed. The quit command cannot be executed in the system view.
- The protocol stack of iMaster NCE-Campus automatically executes some user interaction commands and you do not need to deliver these commands again. If the commands are repeatedly executed, the command execution will fail.
- Templates can contain variables, which can be anonymized, to improve template reusability and security.
- Variable format: ${Variable name}, for example, ${ipAddress}. ipAddress is used as the variable name. Users can set the value of ${ipAddress}.
- If you need to anonymize key information, select Anonymize. Then, the system anonymizes the information based on the anonymization policy.
- A variable name can contain digits and letters.
- After the configuration is complete, click Confirm.
- You can view created templates in the template list and deliver template task configurations.
- To modify command parameters in a template or the name of a template, click
on the right of the template.
- To delete a template, select the template and click
on the right.
- You can view created templates in the template list and deliver template task configurations.
- Click New Template on the right.
- Deliver a configuration task.
- Select the template to be delivered and click
on the right.
- On the parameter configuration page, you can modify command parameters. If you do not need to modify the parameters, click Next.
- On the device selection page, click Add to select the devices to which the template is to be delivered and click OK.
To delete a device, select the device and click
on the right or click Clear to deselect all devices.
- Click Next. The task configuration page is displayed.
- Configure the task name, task description, and task type as required.
- If you need to deliver the configuration task immediately, select Run Immediately.
- If you need to deliver the configuration task at a specified time, select Once and configure an execution time.
- If you need to deliver the configuration task at a specified time within a specified period, select Periodic and configure an execution time.
- Click Deploy and select I have understood the consequence of the operation and confirm to perform the operation.
- Click OK to deliver the template.
- Select the template to be delivered and click
- Create a user template.
Configuring a Command Delivery Task
Context
You can manage all delivery tasks on the Configuration Task page in a unified manner. For example, you can view and delete tasks, and modify, enable, or disable periodic tasks. You can also view historical task delivery records and modify commands to re-deliver failed tasks.
Procedure
- Log in to iMaster NCE-Campus as a tenant administrator and click Smart configuration tool on the homepage.
- Choose Deploy Tasks from the navigation pane.
- Manage delivered tasks.
- For a configuration task that does not need to be executed, select the task and click Delete on the right.
- For a periodic configuration task, select the task and click Enable or Disable on the right to manage the task.
- Each tenant can manage a maximum of 50 configuration tasks.
- Only periodic configuration tasks can be enabled or disabled.
- View configuration tasks.
- Click
in the Operation column on the right to view details about a task.
- Click
in the Operation column on the right to view the execution status and result of a task.
A maximum of 20 delivery records can be saved for a task. If the number of delivery records exceeds 20, iMaster NCE-Campus deletes the earliest delivery record.
- Click
- Modify configuration tasks.
- Click
in the Operation column on the right to modify the task description, execution time, and devices to which the task needs to be delivered.
- Modify task information.
On the task modification page, you can modify the task description and execution time.
- Modify the devices to which the task needs to be delivered.
Operation
Description
Click Add or Clear.
Manage a device.
In the device list, click
on the right.
Modify configuration commands for the device.
Click
in the Operation column on the right.
Delete a device.
- Modify task information.
- Click
- Manage delivered tasks.