Platform Help >> System Management >> System Settings

System Settings

This function helps you configure the system settings for the platform.

Operation Procedure

1. Click the System tab to enter the System page, and click the System Settings link to enter the System Settings page.
2. Make proper settings, and click OK.

Precautions

• Only administrators are permitted to configure the system settings.

Parameters

• Operator Idle Timeout: An online operator automatically logs out after a period without any operation. This period is the operator idle timeout. The operator must log in again to perform any other operations.
• Same Operator Logs in Simultaneously: Whether the same operator is permitted to log in to the system simultaneously. If not, when an operator logs in, the same operator already online is logged off.
• Lock Duration for Three Consecutive Login Failures: When an operator has failed to log in with the same IP for three consecutive times, the operator will be forbidden to log in with the same IP within the lock duration.
• Device Info Display: Specifies how to display the device label in the device list.
• Interface Info Display: Specifies how to display the device interface, if both interface description and interface alias is displayed, this parameter is not in effect.
• Lifetime of Deleted Users: The Deleted Users is preserved for this period. When the lifetime is exceeded, they are deleted permanently.
• Display Access Passwords in : Configure the system to display the password set for SNMP, Telnet, SSH, or SOAP access in plain text or ciphertext.
• Task History Lifetime (1-730 days): Maximum days that a task history record can be kept in the system. The system periodically deletes expired task history records.The system deletes expired task history records at 01:30 every day.
• Max. Concurrent Logins with Same Account: Configure this parameter when multiple operators are allowed to use the same account to log in to the system at the same time. After receiving a login request with an account whose concurrent login limit has been reached, the system randomly kicks out an existing login to allow the new login.
• Send Alarm After Three Consecutive Login Failures: This feature enables the system to trigger an alarm after three consecutive login failures of one operator at the same IP address. To enable this feature, navigate to the Alarm > Trap Management > Trap to Alarm page, and then enable the rule named Trap-to- Alarm Rule for Three Consecutive Login Failure Events.
• Allow only super administrator to modify the other operators in the administrator group:If you select Yes, only the super administrator can modify the other operators in the administrator group. If you select No, operators except the super administrator in the administrator group can modify the information of each other.
• Automatically Synchronize Port Groups: If you select Yes, all port groups are synchronized at 1:00 AM every day. If you select No, synchronization is not performed.
• Web Manager Configuration: Specify whether to allow users to use the local system server as the proxy to access the Web NMS of the devices managed by INC when direct access is not available. To enable this feature, select Yes from the Enable Web Proxy list, and then set the protocol (HTTP or HTTPS) and port number to be used. By default, this feature is disabled and the Web Manager Configuration area and the Enable Web Proxy parameter are not displayed on the system settings page. To display the Web Manager Configuration area and the Enable Web Proxy parameter, open the configuration file commonCfg.properties in the client\conf directory of the INC installation directory, set of supportWebProxy to true, save the file, and then refresh the system settings page.
• Ping Configuration: The system polls all the devices through the Ping operation at the configured interval. The operator can set the timeout and retry as required. If all the pings time out, the system sets the status of device alarm as critical.
• Default Device Connection Configuration: The system can communicate with managed devices through SNMP or Telnet. An operator can separately set the SNMP port and Telnet port based on the network conditions.
• NNMi Configuration: Enables the system to communicate with the NNMi server. If a task is scheduled to import devices from NNMi, the system obtains and imports device information from the NNMi server at the specified time. To schedule a task, open file client\conf\platAppContext.xml in the installation path, search for the platNNMiDeviceImportTrigger field, change the cronExpression attribute of the field, and restart the system. The attribute supports the following parameters: second, minute, hour, date of a month, month of a year, and day of a week. An asterisk (*) means All? A question mark (?) means Not set? By default, the task is executed at 01:10 every day, which corresponds to the cronExpression value 0 10 1 * * ?.
• Internet Connection Configuration: Specifies how the system connects to the Internet. The default value is Direct Connect. If proxy is used, you must input the proxy server address and port. If the proxy server requires authentication, you must input the user name and password.This configuration applies only to the SMS and email functions.
• Interface Up/Down Alarm Filter: Filters interface Up/Down traps received by the system or created by the system for ease of management. You can set the filter to:
  1. Alarms for PC-Connected Links: Sets whether to filter interface Up/Down alarms for the interfaces connected to PCs.
  2. Alarms for Server-Connected Links: Sets whether to filter interface Up/Down alarms for interfaces connected to servers or located on servers.
  3. Alarms for Disconnected Links: Sets whether to filter interface Up/Down alarms for interfaces that have no physical network connections.
  By default, no interface Up/Down alarms are filtered. The settings apply to interface Up/Down alarms both received from monitored devices and created by the system. For example, if the filter is set to filter traps for server-connected links, The system neither receives interface Up/Down traps from monitored devices nor creates interface Up/Down traps for server-connected links. This filter setup is globally effective. You can set filters specific to interfaces, which have priority over the global filter setting. If the customer want to add PCs into the system, they can enable "filter for alarms for PC-connected links". If the customer do not want to add PCs into the system because each PC uses an expensive system node license, they can enable "filter for alarms for disconnected links".
• Device Label Configuration: The default device label for adding device to the system. You can set the DNS or sysname as device label. If both is invalid ,device IP address is set to be the device label.
  1. Update Existing Device Labels: update Existing Device Labels.
  2. Update Device Label When Sysname Changes: If device sysname is changed, the device label in the system is updated to be the device sysname.
• Device Location Configuration: Select the synchronization options for device location changes.
• Interface Alias Configuration: Select the synchronization options for device location changes.
• DNS Server Setting: Unify the configurations of the DNS server IP address for related services, such as the terminal name resolution policy in terminal access management.
• Layer 2 Topology Configuration:
  1. Enable STP Link Calculation: Specifies whether to use STP to calculate the physical topology between devices. In a network with STP transparent transmission enabled, disable this feature. By default, this feature is enabled.
  2. Enable MAC Intersection Check Among Neighbor Interfaces: Specifies whether to enable MAC intersection check among neighbor interfaces when links are calculated according to the LLDP, NDP, and CDP neighbor information. When a network has loops and cannot use STP to calculate links, it must use LLDP, NDP, and CDP to calculate links. In this case, disable this feature. By default, this feature is disabled.
  3. Enable Inter-Routing Interface Link Calculation: Specifies whether to calculate the physical links between two routing interfaces based on the neighbor information. When the routing interfaces of two devices are directly connected, the routing interfaces may have the LLDP/NDP/CDP neighbor information. By default, this feature is abled.
  4. Enable Real-Time Location Extension: Specifies whether to enable the third-party devices to support real-time location. By default, only Intelbras devices support real-time location. Use this feature with caution, because enabling the third-party devices to support real-time location seriously degrades the Layer 3 topology performance. By default, this feature is disabled.
  5. Enable DismanPing: The DismanPing test enables devices to maintain the latest MAC address table entries of neighboring devices by periodically broadcasting DismanPing packets, and allows the system to precisely draw the Layer 2 topology.
  6. Enable Forged Ping Packets: For a device where DismanPing is not enabled, this feature periodically sends forged ping packets to the device to trigger the device to send broadcast ARP messages. This feature solves the problem that some device links are lost within a period of time because MAC address entries age out. This feature improves the accuracy of the links drawn based on MAC address learning. By default, this feature is enabled.
  7. Enable NetBIOS to Detect Host Names:With this function enabled, the system uses NetBIOS to obtain host names if no host names are obtained through DNS and DHCP.
• Layer 3 Topology Settings:
  1. Display Layer 3 Links Between Virtual Interfaces:Select whether or not to display links between virtual interfaces on devices in the Layer 3 topology. If you select No, the system does not display the link between two interfaces when at least one of them is a virtual interface.
• Forward the system Operation Logs in Syslogs: Specifies whether to enable forwarding of the system operations logs in Syslogs. To enable the feature, you must first configure the Syslog Server IP and Syslog Server Port, and then enable the feature. After the configuration, the system operations logs are sent in Syslogs to the specified Syslog server. By default, the feature is disabled.
  
  • Syslog format: <+integer+>+time+space+host name+space+%%component name+ /+operation result (integer type)+ /OPERLOG:+operator name+(operator host IP)+[component]+operation description+space+[operation result (integer type)].For example,<189>Dec 03 11:16:28 2021 RDVDI-C13328V %%jserver/6/OPERLOG:admin(0:0:0:0:0:0:0:1)[Device Resource]Manage device "25(10.114.115.25)". [Success]
• To configure browsers to save login usernames and passwords:
  1. Specify whether to configure browsers to save login usernames and passwords. If you select Yes, the browsers automatically save the login username and password when users log in to the system. If you select No, the browsers do not save the login username and passwords. By default, Yes is selected. When you log in to the system, a dialog box appears to ask you whether to save your username and password.
  2. If you do not want the browser to save your username and password, select No. If you select Yes, the browsers save the login usernames and passwords even if the browsers are not configured to save login usernames and password. To make the feature of not allowing browsers to save login usernames and passwords take effect, please manually clear the passwords saved in browsers.
  3. The method of manually clearing passwords saved by browsers depends on your browser type.
     a. Firefox: Select Firefox > Options > Options or select Tools > Options. In the Security tab, click Saved Passwords. Select the sites for which you want to clear the passwords, and click Remove.
     b. Chrome: Select Settings. Click Show advanced settings. Click Clear browsing data in the Privacy area. On the dialog box that appears, select Clear saved passwords and click Clear browsing data.
• Alarm Statistics SMS Configuration:
1. Enable Alarm Statistics SMS: Specifies whether to enable alarm statistics SMS.
2. SMS Transmission Interval (minutes): Specifies the interval at which the SMS is transmitted.
3. Level Triggering System Failures: When the number of unrecovered alarms at this level or higher is not 0, the SMS for system failures is sent. Otherwise, the SMS for correct system operations is sent. If this field is empty, the SMS for system failures is sent by default.
4. Phone Number: Phone number used for receiving SMS. Include the country or region code in the phone number when necessary.
5. SMS for Correct System Operations: Contents in the SMS when the system is operating correctly.
6. SMS for System Failures: Contents in the SMS when the system fails.
• Alarm SMS Message Title: Title of the alarm SMS message.
• Alarm SMS Message Content: Content of the alarm SMS message, which can be the alarm name or the alarm content.
• Maintained Object Trap-to-Alarm Upgrade Configuration: Specifies whether to upgrade traps to alarms for devices and links that are being maintained. This setting takes effect also for devices and links maintained on APM.
• Maintained Object Alarm Forwarding Configuration: Specifies whether to forward alarms for devices and links that are being maintained. This setting takes effect also for devices and links maintained on APM.
• The alarm mail forwarding configuration includes the following parameters:
  1. Enable Alarm Acknowledgement Mails: With Yes selected for this option, each alarm notification mail contains an alarm acknowledgement link. You can click the acknowledgement link to acknowledge the corresponding alarm in INC.
  2. Enable Public IP: With Yes selected for this option, you need to configure the public IP address for INC. Then, the acknowledgement link in each alarm notification mail contains the public IP address. You can click the acknowledgement link to acknowledge the corresponding alarm in INC configured with the public IP address within the firewall.
  3. Mail Sender: Specify the sender for alarm notification mails. The default is NMS_FaultDM.
• Auto Forwarding Recovered Alarm Configuration:Specify whether to automatically forward recovered alarms. With Yes selected for this option, the recovered alarms are automatically forwarded according to the configured alarm forwarding rules.
• Configure Repeated Alarm Count: If you enable repeated alarm count, the repeated alarms are aggregated into one alarm. You can view the number of alarm repetitions in the Repeat Count column of the alarm list. The system determines syslog alarms as repeated only when both their Parameter List values and key parameters are exactly the same. The system determines other types of alarms as repeated when their key parameters are the same.
• Mail Notification: If this feature is enabled, the specified users are notified by mails before license expiration. To use this feature, configure the mail server first.
  1. Mail Recipient: Mail addresses that receive notification mails. You can add up to five mail addresses.
  2. Notify Me before: How many days before license expiration that the system begins to send notification mails.
• License Expiration Alarm Notification Settings:
  1. Send Alarms Before License Expiration: Select whether and when to send license expiration alarms before license expiration. The system supports sending alarms 20 days, 15 days, 10 days, 7 days, or 3 days before license expiration.
  2. Send Alarm on License Expiration Date: Select whether to send an alarm on the date the license expires.
  3. Send Daily Alarms After License Expiration: Select whether to send an alarm each day after the license expires.
  4. Click Alarm. From the navigation tree, select Trap Management > Trap to Alarm. Select the trap-to-alarm rule named License Expiration Event Alarm Upgrade Rule.
• Alarm Notification Settings for HTTPS Certificate Expiration:
  1. Select whether and when to send HTTPS certificate expiration alarms before HTTPS certificate expiration. The system supports sending alarms 30 days, 15 days, 10 days, 7 days, or 3 days before HTTPS certificate expiration.
  2. Click Alarm. From the navigation tree, select Trap Management > Trap to Alarm. Select the trap-to-alarm rule named HTTPS Certificate Expiring .
• Write operation logs into the system foreground log file: Select whether to write the user operation logs into the system foreground log file (file imcforeground.log in the \client\log directory of the INC installation path). By default, this feature is disabled and the operation logs are only displayed on the operation log list page.
• Routing information obtaining period configuration: By default, the system retrieves the routing information of managed devices at intervals of 12 hours and displays the information on the Resource > Device Routes page. You can edit the interval as needed.
• The scheduled offline device deletion configuration contains the following parameters:
  1. Enable Scheduled Offline Device Deletion: Enables or disables scheduled offline device deletion.
  2. Offline Device Management Policy: Deletes or unmanages the offline devices.
  3. Offline Device Hold Time: When the hold time of an offline device expires, the system will delete or unmanage the device according to the offline device management policy.
• ClearPass Server Configuration:
  1. Enable: Select whether to enable the ClearPass server.
  2. IP address: Enter the IP address of the ClearPass server.
  3. Username: Enter a user name for accessing the ClearPass server.
  4. Password: Enter the user's password.
  5. Client ID: Enter the client ID.
  6. Grant Type: Select the grant type. Options are client credentials and username and password credentials.
  7. Client Secret: Enter the client secret.
• Local system server CPU, memory, and disk alarm threshold configuration: Set the CPU, memory, and disk usage ratio-based alarm thresholds for the local system server.
• System Login Verification Code Configuration: If you select the Enable option, you must enter a verification code to log in to the system. If you clear the Enable option, you do not need to enter a verification code.
  NOTE: As from version INC PLAT 7.3 (E0706P01), you cannot use the enableValidationCode parameter in the commonCfg.properties configuration file to specify whether to use a verification code to log in to the system. The file is located at the \client\conf\ directory in the system installation path.
• Maintenance Notification Settings:
  1. Notify before maintenance expiration (days): Compare the current time of the installed system with the maintenance expiration time. The default is 30 days.
  2. Do not notify again after notification is closed (1-30 days): Specify the frequency of maintenance notification messages. The default is 30 days.
• Aruba MM Server Settings:Used to test whether the parameters are correct.
  1. URL Protocol: Protocol used to access the Aruba MM server.
  2. Access Address: IP address used to access the Aruba MM server.
  3. Port Number (1-65535): Port number used to access the Aruba MM server.
  4. Username: Username used to access the Aruba MM server.
  5. Password: Password used to access the Aruba MM server.
  6. Login Parameter Verification URL: URL used to verify the configured parameters.
  7. Page to be Opened After Successful Login: The specified page will open after you click Log In if the configured parameters are correct.