- Table of Contents
-
- 13-Network Management and Monitoring Command Reference
- 00-Preface
- 01-System maintenance and debugging commands
- 02-NQA commands
- 03-iNQA commands
- 04-NTP commands
- 05-PoE commands
- 06-SNMP commands
- 07-RMON commands
- 08-NETCONF commands
- 09-EAA commands
- 10-Process monitoring and maintenance commands
- 11-Sampler commands
- 12-Mirroring commands
- 13-NetStream commands
- 14-IPv6 NetStream commands
- 15-sFlow commands
- 16-Information center commands
- 17-GOLD commands
- 18-Packet capture commands
- 19-VCF fabric commands
- 20-CWMP commands
- 21-SmartMC commands
- 22-SQA commands
- 23-eMDI commands
- 24-Performance management commands
- 25-Event MIB commands
- 26-EPS agent commands
- 27-Cloud connection commands
- 28-EPA commands
- 29-KPI data collection commands
- Related Documents
-
Title | Size | Download |
---|---|---|
29-KPI data collection commands | 192.74 KB |
Available data for KPI data collection
kpi file aging threshold remain-disk-size
kpi file aging threshold total-file-size
KPI data collection commands
Available data for KPI data collection
Table 1 Available data for KPI data collection
Class |
Module |
Object |
Indicator |
Indicator description |
Device-state |
DEV |
Card |
Device_restarts |
Number of device reboots. |
IRF |
Device |
IRF_splits |
Number of IRF splits. |
|
IRF |
Device |
IRF_dual-active_count |
Number of dual-master IRF fabrics. |
|
DEV |
Card |
LPU_failures |
Number of LPU failures. |
|
DEV |
Card |
MPU_state |
State of the MPU: · 0—The MPU is not present. · 1—The MPU is operating correctly. · 2—The MPU has failed. |
|
DEV |
Card |
MPU_failures |
Number of MPU failures. |
|
DEV |
Card |
SFU_state |
State of the SFU: · 0—The SFU is not present. · 1—The SFU is operating correctly. · 2—The SFU has failed. |
|
DEV |
Card |
SFU_failures |
Number of SFU failures. |
|
DEV |
Subcard |
Subslot_failure |
Number of subcard failures. |
|
FWD |
Device |
Inc_H_S_entries |
Inconsistent hardware and software entries. |
|
FAN |
Device |
Fan_state |
Fan tray state: · 0—Normal. · 1—Faulty. |
|
POWER |
Device |
Power_state |
Power supply state: · 0—Normal. · 1—Faulty. |
|
POE |
Device |
PoE_state |
PoE power supply state: · 0—Normal. · 1—Faulty. |
|
TEMP |
Device |
Card_temperature |
Card temperature: · 0—Normal. · 1—Faulty. |
|
FS |
Device |
File_exceptions |
Number of save operation failures due to file system error. |
|
DEV |
Device |
Process_abnormal_reboot |
Number of process reboot failures. |
|
DEV |
Device |
Process_normal_reboot |
Number of successful process reboots. |
|
Device-resource |
FWD-RES |
Card |
ARP_entry_usage |
Ratio of the real-time ARP entry count to the upper ARP entry count limit. |
FWD-RES |
Card |
ARP_threshold_ratio |
Ratio of the real-time ARP entry count to the ARP table usage threshold. |
|
FWD-RES |
Card |
MAC entry usage |
Ratio of the real-time MAC entry count to the upper MAC entry count limit. |
|
FWD-RES |
Card |
MAC_threshold_ratio |
Ratio of the real-time MAC entry count to the MAC table usage threshold. |
|
FWD-RES |
Card |
FIB_entry_usage |
Ratio of the real-time FIB entry count to the upper FIB entry count limit. |
|
FWD-RES |
Card |
FIB_threshold_ratio |
Ratio of the real-time FIB entry count to the FIB table usage threshold. |
|
FWD-RES |
Card |
ND entry usage |
Ratio of the real-time ND entry count to the upper ND entry count limit. |
|
FWD-RES |
Card |
ND_threshold_ratio |
Ratio of the real-time ND entry count to the ND table usage threshold. |
|
FWD-RES |
Card |
IPv4L2multicast_usage |
Ratio of the real-time IPv4 Layer 2 multicast entry count to the upper IPv4 Layer 2 multicast entry count limit. |
|
FWD-RES |
Card |
IPv4L2multicast_ratio |
Ratio of the real-time IPv4 Layer 2 multicast entry count to the IPv4 Layer 2 multicast entry count threshold. |
|
FWD-RES |
Card |
IPv6L2multicast_usage |
Ratio of the real-time IPv6 Layer 2 multicast entry count to the upper IPv6 Layer 2 multicast entry count limit. |
|
FWD-RES |
Card |
IPv6L2multicast_ratio |
Ratio of the real-time IPv6 Layer 2 multicast entry count to the IPv6 Layer 2 multicast entry count threshold. |
|
FWD-RES |
Card |
IPv4L3multicast_usage |
Ratio of the real-time IPv4 Layer 3 multicast entry count to the upper IPv4 Layer 3 multicast entry count limit. |
|
FWD-RES |
Card |
IPv4L3multicast_ratio |
Ratio of the real-time IPv4 Layer 3 multicast entry count to the IPv4 Layer 3 multicast entry count threshold. |
|
FWD-RES |
Card |
IPv6L3multicast_usage |
Ratio of the real-time IPv6 Layer 3 multicast entry count to the upper IPv6 Layer 3 multicast entry count limit. |
|
FWD-RES |
Card |
IPv6L3multicast_ratio |
Ratio of the real-time IPv6 Layer 3 multicast entry count to the IPv6 Layer 3 multicast entry count threshold. |
|
ACL-RES |
Card |
ACL_usage |
Ratio of the real-time ACL entry count to the upper ACL entry count limit. |
|
ACL-RES |
Card |
ACL_threshold_ratio |
Ratio of the real-time ACL entry count to the ACL entry count threshold. |
|
STOR-RES |
Card |
Storage_usage |
Ratio of the used storage space to the total storage space. |
|
STOR-RES |
Card |
Storage_threshold_ratio |
Ratio of the used storage space to the storage space usage threshold. |
|
DEV-RES |
Card |
CPU_usage |
Ratio of the used CPU capacity to the total CPU capacity. |
|
DEV-RES |
Card |
CPU_threshold_ratio |
Ratio of the used CPU capacity to the CPU usage threshold. |
|
DEV-RES |
Card |
Memory_usage |
Ratio of the used memory to the total memory. |
|
DEV-RES |
Card |
Memory_threshold_ratio |
Ratio of the used memory to the memory usage threshold. |
|
Net-performance |
LOOP-DCT |
Device |
L2 loop_state |
Layer 2 loop state: · 0—The Layer 2 loop is operating correctly. · 1—Layer 2 loop has failed. |
IF-CI |
Interface |
Port_congestion |
Number of packets dropped due to traffic congestion. |
|
IF-ERROR |
Interface |
Port_error |
Number of packets dropped due to error packets. |
|
CPCAR |
Device |
CPCAR_loss |
Number of dropped packets due to traffic policing configured on the control panel. |
|
STP-SWT |
Device |
STP_switchovers |
Number of STP switchovers. |
|
LACP-SWT |
Device |
LACP_switchovers |
Number of link aggregation switchovers. |
|
IRF-SWT |
Device |
IRF_switchovers |
Number of IRF switchovers. |
|
M-LAG-SWT |
Device |
M-LAG_switchovers |
Number of M-LAG switchovers. |
|
RRPP-SWT |
Device |
RRPP_switchovers |
Number of RRPP switchovers. |
|
VRRP-SWT |
Device |
VRRP_switchovers |
Number of VRRP switchovers. |
|
IF-USAGE |
Device |
Port_BW_usage |
Bandwidth usage for all ports. |
|
Port-state |
PORT-ST |
Device |
Down_ports |
Number of physical interfaces in down state. |
PORT-ST |
Device |
Port_flappings |
Number of port flappings. |
|
TRAN-ST |
Device |
Opti-module_health |
This indicator is not supported in the current software version. Transceiver module health. |
|
Net-connection |
RPNCS |
Device |
ISIS_peer_status |
IS-IS neighbor connection state: · 0—The IS-IS neighbor connection is operating correctly. · 1—The IS-IS neighbor connection has failed. |
RPNCS |
Device |
OSPF_peer_status |
OSPF neighbor connection state: · 0—The OSPF neighbor connection is operating correctly. · 1—The OSPF neighbor connection has failed. |
|
RPNCS |
Device |
OSPv3_peer_status |
OSPFv3 neighbor connection state: · 0—The OSPFv3 neighbor connection is operating correctly. · 1—The OSPFv3 neighbor connection has failed. |
|
RPNCS |
Device |
BGP_peer_status |
BGP neighbor connection state: · 0—The BGP neighbor connection is operating correctly. · 1—The BGP neighbor connection has failed. |
|
MCRCS |
Device |
Multicast_connection_status |
Multicast route connection state: · 0—The multicast route connection is operating correctly. · 1—The multicast route connection has failed. |
|
DHCPCS |
Device |
DHCPv4_server_state |
Statistics about DHCPv4 server address allocation failures. |
|
DHCPCS |
Device |
DHCPv6_server_state |
Statistics about DHCPv6 server address allocation failures. |
|
DHCPCS |
Device |
DHCPv4_server_switching |
Number of DHCPv4 server switchovers. |
|
DHCPCS |
Device |
DHCPv6_server switching |
Number of DHCPv6 server switchovers. |
|
DHCPCS |
Device |
DHCPv4_entry failures |
Number of DHCPv4 entry establishment failures. |
|
DHCPCS |
Device |
DHCPv6_entry failures |
Number of DHCPv6 entry establishment failures. |
|
Net-securit y |
AAA |
Device |
1X_AuthN_status |
State of 802.1X authentication: · 0—802.1X authentication succeeded. · 1—802.1X authentication failed. An attack might exist. |
AAA |
Device |
1X_Usr&Pwd_status |
State of the username and password for 802.1X authentication: · 0—The username and password are correct. · 1—The username and password are incorrect. |
|
AAA |
Device |
MAC_AuthN_status |
State of MAC authentication: · 0—MAC authentication succeeded. · 1—MAC authentication failed. An attack might exist. |
|
AAA |
Device |
MAC_Usr&Pwd_status |
State of the username and password for MAC authentication: · 0—The username and password are correct. · 1—The username and password are incorrect. |
|
AAA |
Device |
Portsec_AuthN_status |
State of the port security authentication: · 0—The authentication succeeded. · 1—The authentication failed. An attack might exist. |
|
AAA |
Device |
Portsec_Usr&Pwd_status |
State of the port security access username and password: · 0—The username and password are correct. · 1—The username and password are incorrect. |
|
AAA |
Device |
StaticUser_AuthN_status |
State of the static user authentication: · 0—The authentication succeeded. · 1—The authentication failed. An attack might exist. |
|
AAA |
Device |
StaticUser_Usr&Pwd_status |
State of the static username and password: · 0—The username and password are correct. · 1—The username and password are incorrect. |
|
ATTACK |
Device |
All-type_attacks |
Number of all types of attacks. |
|
TCP |
Device |
TCP_attacks |
Number of TCP attacks. |
|
ARP-ATK |
Device |
ARP_attacks |
Number of ARP attacks. |
|
ND-ATK |
Device |
ND_attacks |
Number of ND attacks. |
|
AAA |
Device |
Illegal_user_detections |
Number of illegal user detections. |
display external-kpi data
Use display external-kpi data to display the key performance indicator (KPI) data of service modules and objects for the remote device.
Syntax
display external-kpi data [ device-ip ip-address [ module module-name [ object object-name ] ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
device-ip ip-address: Specifies a remote device by its IP address.
module module-name: Specifies a module by its name. For more information, see Table 1.
object object-name: Specifies an object by its name. Objects are physical entities to which the indicators belong, such as devices, cards, or subcards. The value for the object-name argument varies by object type. Available values include:
· device—Specifies a device. Indicators for this object describe the overall condition of the device.
· chassis.x/slot.y—Specifies a card. Indicators for this object describe the performance of the card. The value for x is 0, and y represents the slot number of the card. (In standalone mode.)
· chassis.x/slot.y—Specifies a card. Indicators for this object describe the performance of the card. x represents the member ID of the IRF member device, and y represents the slot number of the card. (In IRF mode.)
· chassis.x/slot.y/subslot.z—Specifies a subcard. Indicators for this object describe the performance of the subcard. The value for x is 0, y represents the slot number of the card, and z represents the subcard ID. (In standalone mode.)
· chassis.x/slot.y/subslot.z—Specifies a subcard. Indicators for this object describe the performance of the subcard. x represents the member ID of the IRF member device, y represents the slot number of the card, and z represents the subcard ID. (In IRF mode.)
· interface-typeinterface-number—Specifies an interface by its type and number. Indicators for this object describe the running status of the physical interface.
Examples
# Display the KPI data for the remote device with IP address 192.168.1.1.
<Sysname> display external-kpi data device-ip 192.168.1.1
Device IP : 192.168.1.1
Slot : 0
Module : DEV
Object : chassis.2/slot.0
Indicator Value Latest collect time
MPU_state 0 2022-10-16 16:32:05
Module : FWD
Object : device
Indicator Value Latest collect time
Inc_H_S_entries 0 2022-10-16 16:32:05
Module : FAN
Object : device
Indicator Value Latest collect time
Fan_state 0 2022-10-16 16:32:06
Slot : 1
Module : DEV
Object : chassis.2/slot.0
Indicator Value Latest collect time
MPU_state 0 2022-10-16 16:32:05
Module : FWD
Object : device
Indicator Value Latest collect time
Inc_H_S_entries 0 2022-10-16 16:32:05
Module : FAN
Object : device
Indicator Value Latest collect time
Fan_state 0 2022-10-16 16:32:06
Table 2 Command output
Field |
Description |
Device IP |
IP address of the remote device. |
Module |
Module name. For more information, see Table 1. |
Slot |
Slot on which the object resides. |
Object |
Object for KPI data collection. |
Indicator |
Indicator for KPI data collection. For more information, see Table 1. |
Value |
Value for the indicator. |
Latest collect time |
Most recent time when the indicator value was collected. |
display kpi data
Use display kpi data to display the KPI data for service modules and objects within a time range on the storage media.
Syntax
display kpi data module module-name object object-name from time1 date1 to time2 date2 [ file file-path ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
module module-name: Specifies a module by its name. For more information, see Table 1.
object object-name: Specifies an object by its name. Objects are physical entities to which the indicators belong, such as devices, cards, or subcards. The value for the object-name argument varies by object type. Available values include:
· device—Specifies a device. Indicators for this object describe the overall condition of the device.
· chassis.x/slot.y—Specifies a card. Indicators for this object describe the performance of the card. The value for x is 0, and y represents the slot number of the card. (In standalone mode.)
· chassis.x/slot.y—Specifies a card. Indicators for this object describe the performance of the card. x represents the member ID of the IRF member device, and y represents the slot number of the card. (In IRF mode.)
· chassis.x/slot.y/subslot.z—Specifies a subcard. Indicators for this object describe the performance of the subcard. The value for x is 0, y represents the slot number of the card, and z represents the subcard ID. (In standalone mode.)
· chassis.x/slot.y/subslot.z—Specifies a subcard. Indicators for this object describe the performance of the subcard. x represents the member ID of the IRF member device, y represents the slot number of the card, and z represents the subcard ID. (In IRF mode.)
· interface-typeinterface-number—Specifies an interface by its type and number. Indicators for this object describe the running status of the physical interface.
from time1 date1: Specifies the start time and date for KPI data collection. The time1 argument specifies the time of the day in hh:mm:ss format (24-hour clock). Its value is in the range of 00:00:00 to 23:59:59. The date1 argument specifies a date in MM/DD/YYYY or YYYY/MM/DD format. MM is the month of the year in the range of 1 to 12, DD is the day of the month with the range varying by MM, and YYYY is the year in the calendar in the range of 2000 to 2035.
to time2 date2: Specifies the end time and date for KPI data collection. The time2 argument has the same format and value range as the time1 argument. The date2 argument has the same format and value range as the date1 argument. The end time must be later than the start time.
file file-path: Specifies the KPI cache file path on the storage media. If you do not specify this option, the command displays the KPI data in all cache files.
Examples
# Display the KPI data for the DEV-RES module and chassis.0/slot.2 object in the specified time range.
<Sysname> display kpi data module DEV-RES object chassis.0/slot.2 from 16:35:05 2022/4/1 to 16:41:06 2022/4/1
Module : DEV-RES
Object : chassis.0/slot.2
Slot : 2
Indicator Value Latest collect time
CPU_usage 0.7 2022-04-01 16:41:05
Memory_usage 0.7 2022-04-01 16:39:05
Table 3 Command output
Field |
Description |
Module |
Module name. For more information, see Table 1. |
Slot |
Slot on which the object resides. |
Object |
Object for KPI data collection. |
Indicator |
Indicator for KPI data collection. For more information, see Table 1. |
Value |
Value for the indicator. |
Latest collect time |
Most recent time when the indicator value was collected. |
display kpi module-info
Use display kpi module-info to display KPI data collection information for service modules.
Syntax
display kpi module-info [ module-name ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
module-name: Specifies a module by its name. For information about the module names, see Table 1. If you do not specify this argument, the command displays KPI data collection information for all available service modules.
verbose: Displays detailed KPI data collection information about the module. If you do not specify this keyword, the command displays brief KPI data collection information about the module.
Examples
# Display brief KPI data collection information for the DEV-RES module.
<Sysname> display kpi module-info DEV-RES
Module : DEV-RES
Class : Device-resource
KPI Collect : Enabled
Collect interval : 300 seconds
Collect times : 2
# Display detailed KPI data collection information for the DEV-RES module.
<Sysname> display kpi module-info DEV-RES verbose
Module : DEV-RES
Class : Device-resource
KPI Collect : Enabled
Collect interval : 300 seconds
Collect times : 2
Slot : 2
Object : chassis.0/slot.2
Indicator Value Latest collect time
CPU_usage 0.7 2022-03-29 14:36:52
Memory_usage 0.7 2022-03-29 14:36:52
Slot : 3
Object : chassis.0/slot.3
Indicator Value Latest collect time
CPU_usage 0.7 2022-03-29 14:36:52
Memory_usage 0.7 2022-03-29 14:36:52
Table 4 Command output
Field |
Description |
|
Module |
Module name. For more information, see Table 1. |
|
Class |
KPI class to which the module belongs. For more information, see Table 1. |
|
KPI Collect |
State of KPI data collection: · Enabled—KPI data collection is enabled for the module. · Disabled—KPI data collection is disabled for the module. |
|
Collect interval |
KPI data collection interval, in seconds. |
|
Collect times |
Number of KPI data collections. |
|
Slot |
Slot on which the object resides. |
|
Object |
Object name. |
|
Indicator |
Indicator for KPI data collection. For more information, see Table 1. |
|
Value |
Value for the indicator. |
|
Latest collect time |
Most recent time when the indicator value was collected. |
kpi copy-file to active-mpu
Use kpi copy-file to active-mpu to copy the KPI data on the standby MPU to the active MPU.
Syntax
kpi copy-file to active-mpu
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
After an MPU active/standby switchover on the device, the new active MPU cannot automatically obtain the KPI data from the old active MPU (current standby MPU). To ensure service continuity, you must use this feature to copy the KPI data on the old active MPU to the new active MPU.
Examples
# Copy the KPI data on the standby MPU to the active MPU.
<Sysname> system-view
[Sysname] kpi copy-file to active-mpu
kpi file save-interval
Use kpi file save-interval to specify the interval for saving KPI files to the storage media.
Use undo kpi file save-interval to restore the default.
Syntax
kpi file save-interval interval
undo kpi file save-interval
Default
KPI files are saved to the storage media at an interval of 1440 minutes.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
interval: Specifies the interval for saving KPI files to the storage media, in the range of 60 to 65535 minutes.
Examples
# Set the interval for saving KPI files to the storage media to 60 minutes.
<Sysname> system-view
[Sysname] kpi file save-interval 60
kpi file aging threshold remain-disk-size
Use kpi file aging threshold remain-disk-size to set the free storage media capacity threshold for triggering KPI file aging.
Use undo kpi file aging threshold remain-disk-size to restore the default.
Syntax
kpi file aging threshold remain-disk-size size
undo kpi file aging threshold remain-disk-size
Default
The free storage media capacity threshold for triggering KPI file aging is 128 MB.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
size: Specifies the free storage media capacity threshold in the range of 128 to 65535 MB.
Usage guidelines
When the free storage media capacity is less than the specified threshold, the device automatically deletes the earliest saved KPI files until the free capacity is greater than or equal to the specified threshold.
Examples
# Set the free storage media capacity threshold for triggering KPI file aging to 1000 MB.
<Sysname> system-view
[Sysname] kpi file aging threshold remain-disk-size 1000
kpi file aging threshold total-file-size
Use kpi file aging threshold total-file-size to set the KPI file size threshold for triggering KPI file aging.
Use undo kpi file aging threshold total-file-size to restore the default.
Syntax
kpi file aging threshold total-file-size size
undo kpi file aging threshold total-file-size
Default
The KPI file size threshold for triggering KPI file aging is 128 MB.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
size: Specifies the KPI file size threshold in the range of 32 to 2048 MB.
Usage guidelines
When the total KPI file size on the storage media exceeds the specified threshold, the device automatically deletes the earliest saved KPI files until the total KPI file size is less than or equal to the specified threshold.
Examples
# Set the KPI file size threshold for triggering KPI file aging to 500 MB.
<Sysname> system-view
[Sysname] kpi file aging threshold total-file-size 500
kpi file directory
Use kpi file directory to specify the KPI file directory.
Syntax
kpi file directory dir-name
Default
KPI files are stored in the flash:/kpi directory.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
dir-name: Specifies a directory, a string of 1 to 64 characters.
Examples
# Set the KPI file directory to flash:/.
<Sysname> system-view
[Sysname] kpi file directory flash:/
EAI commands
Available indicators for EAI
Table 5 Available indicators for EAI
Class |
Module |
Object |
Indicator |
Indicator description |
Device-resource |
FWD-RES |
Card |
ARP_entry_usage |
Ratio of the real-time ARP entry count to the upper ARP entry count limit. |
FWD-RES |
Card |
MAC_entry_usage |
Ratio of the real-time MAC entry count to the upper MAC entry count limit. |
|
FWD-RES |
Card |
FIB_entry_usage |
Ratio of the real-time FIB entry count to the upper FIB entry count limit. |
|
FWD-RES |
Card |
ND_entry_usage |
Ratio of the real-time ND entry count to the upper ND entry count limit. |
|
FWD-RES |
Card |
IPv4L2multicast_usage |
Ratio of the real-time IPv4 Layer 2 multicast entry count to the upper IPv4 Layer 2 multicast entry count limit. |
|
FWD-RES |
Card |
IPv6L2multicast_usage |
Ratio of the real-time IPv6 Layer 2 multicast entry count to the upper IPv6 Layer 2 multicast entry count limit. |
|
FWD-RES |
Card |
IPv4L3multicast_usage |
Ratio of the real-time IPv4 Layer 3 multicast entry count to the upper IPv4 Layer 3 multicast entry count limit. |
|
FWD-RES |
Card |
IPv6L3multicast_usage |
Ratio of the real-time IPv6 Layer 3 multicast entry count to the upper IPv6 Layer 3 multicast entry count limit. |
|
ACL-RES |
Card |
ACL_usage |
Ratio of the real-time ACL entry count to the upper ACL entry count limit. |
|
STOR-RES |
Card |
Storage_usage |
Ratio of the used storage space to the total storage space. |
|
DEV-RES |
Card |
CPU_usage |
Ratio of the used CPU capacity to the total CPU capacity. |
|
DEV-RES |
Card |
Memory_usage |
Ratio of the used memory to the total memory. |
eai artificial intelligence
Use eai artificial intelligence to enter the Embedded Artificial Intelligence (EAI) view.
Syntax
eai artificial intelligence
Default
EAI monitoring and prediction are disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
You can enable EAI monitoring and prediction only in EAI view. Based on the collected history KPI data, EAI predicts the indicator values by using intelligent algorithms. EAI helps the administrator analyze the trend of key indicators on the device and proactively prevent possible failures.
Examples
# Enter EAI view.
<Sysname> system-view
[Sysname] eai artificial intelligence
eai monitoring enable
Use eai monitoring enable to enable EAI monitoring.
Use undo eai monitoring enable to disable EAI monitoring.
Syntax
eai monitoring enable
undo eai monitoring enable
Default
EAI monitoring is disabled.
Views
EAI view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
Based on the collected history KPI data, the device dynamically generates reasonable alarm thresholds and recovery thresholds for the indicators in Table 5.
· When an indicator value is out of the alarm threshold range, the device logs the threshold violation event and reports it to an NMS through SNMP.
· When the indicator value restores to be within the alarm threshold range, the device records the recovery event and reports it to an NMS through SNMP.
Examples
# Enable EAI monitoring.
<Sysname> system-view
[Sysname] eai artificial intelligence
[Sysname-eai] eai monitoring enable
Related commands
display eai monitoring
eai prediction enable
Use eai prediction enable to enable EAI prediction.
Use undo eai prediction enable to disable EAI prediction.
Syntax
eai prediction enable
undo eai prediction enable
Default
EAI prediction is disabled.
Views
EAI view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
Enabled with this feature, the device dynamically calculates and predicts the indicator values 30 days later based on the history KPI data.
· When the predicted indicator value is out of the alarm threshold range, the device logs the threshold violation event and reports it to an NMS through SNMP.
· When the predicted indicator value restores to be within the alarm threshold range, the device logs the recovery and reports it to an NMS through SNMP.
This feature can help the administrator analyze the trend of key indicators on the device and proactively prevent possible failures.
Examples
# Enable EAI prediction.
<Sysname> system-view
[Sysname] eai artificial intelligence
[Sysname-eai] eai prediction enable
display eai prediction
display eai monitoring
Use display eai monitoring to display EAI monitoring information.
Syntax
display eai monitoring
Views
Any view
Predefined user roles
network-admin
mdc-admin
Examples
# Display EAI monitoring information.
<Sysname> display eai monitoring
Indicator : CPU_usage
Module : DEV-RES
Monitoring status: On
Chassis : 0 Slot : 2 CPU : 0
Object : chassis.0/slot.2
Value : 0.4 Status : Normal
Limit : [0.30, 0.80] Recover : [0.40, 0.70]
Chassis : 0 Slot : 3 CPU : 0
Object : chassis.0/slot.3
Value : 0.5 Status : Normal
Limit : [0.35, 0.85] Recover : [0.40, 0.70]
Table 6 Command output
Field |
Description |
Indicator |
Indicator name. |
Monitoring status |
Enabling status of EAI monitoring: · On—EAI monitoring is enabled. · Off—EAI monitoring is disabled. |
Chassis |
Chassis number. |
Slot |
Slot number. |
CPU |
CPU number. |
Module |
Module name. |
Object |
Object name. |
Value |
Indicator value. |
Status |
State of the indicator: · Normal—The indicator is within the range of the lower limit to the upper limit. · Above upper limit—The indicator exceeds the upper limit. · Below lower limit—The indicator drops below the lower limit. |
Limit |
Alarm threshold range dynamically generated for the indicator, in the format of [lower limit, upper limit]. |
Recover |
Recovery threshold range dynamically generated for the indicator, in the format of [lower limit, upper limit]. |
display eai prediction
Use display eai prediction to display EAI predicted information and history KPI data.
Syntax
display eai prediction
Views
Any view
Predefined user roles
network-admin
mdc-admin
Examples
# Display EAI predicted information and history KPI data.
<Sysname> display eai prediction
Indicator : CPU_usage
Module : DEV-RES
Object : chassis.0/slot.1/subslot.0
Chassis : 0 Slot : 1 CPU : 0
No History value Collect time
--------------------------------------------------------
1 0.7 2022-03-22 17:36:39
2 0.7 2022-03-22 17:28:39
3 0.7 2022-03-22 17:30:39
4 0.7 2022-03-22 17:32:39
5 0.7 2022-03-22 17:34:39
--------------------------------------------------------
Predicted value in 30 days: 0.7
Table 7 Command output
Field |
Description |
|
Chassis |
Chassis number. |
|
Slot |
Slot number. |
|
CPU |
CPU number. |
|
Module |
Module name. |
|
Object |
Object name. |
|
Indicator |
Indicator type. |
|
No |
Number of the entry. |
|
History value |
Most recent five collected indicator values. |
|
Collect time |
Time when the most recent five collections happened. |
|
Predicted value in 30 days |
Predicted indicator value in 30 days. |