Login
- 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-PTP commands
- 06-Network synchronization commands
- 07-SNMP commands
- 08-RMON commands
- 09-NETCONF commands
- 10-EAA commands
- 11-Process monitoring and maintenance commands
- 12-Sampler commands
- 13-Mirroring commands
- 14-NetStream commands
- 15-IPv6 NetStream commands
- 16-sFlow commands
- 17-Information center commands
- 18-GOLD commands
- 19-Packet capture commands
- 20-VCF fabric commands
- 21-CWMP commands
- 22-SmartMC commands
- 23-SQA commands
- 24-eMDI commands
- 25-Performance management commands
- 26-Event MIB commands
- 27-EPS agent commands
- 28-Cloud connection commands
- 29-EPA commands
- 30-Packet trace commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 24-eMDI commands | 124.50 KB |
eMDI commands
alarm suppression times
Use alarm suppression times to set the eMDI alarm logging threshold, that is, the number of consecutive alarms to be suppressed before logging the event.
Use undo alarm suppression times to restore the default.
Syntax
alarm suppression times times-value
undo alarm suppression times
Default
The eMDI alarm logging threshold is 3.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
times-value: Specifies the number of consecutive alarms to be suppressed before logging the event, in the range of 0 to 60. To disable eMDI alarm logging, set this argument to 0.
Usage guidelines
A started eMDI instance monitors its data flow and periodically collects statistics on lost and out-of-order packets.
· If a statistic is equal to or greater than the alarm threshold, the instance triggers an alarm. When the number of consecutive alarms of the same type exceeds the logging threshold, the device sends an alarm log message to the information center.
· If a statistic is less than the alarm threshold, the instance records an alarm removal event. When the number of consecutive alarm removal events of the same type exceeds the logging threshold, the device sends an alarm-removed log message to the information center.
For more information about the information center, see "Configuring information center."
To change the eMDI alarm logging threshold for an eMDI instance that is already started, you must stop the instance first by executing the stop command.
Examples
# Set the eMDI alarm logging threshold to 5.
[Sysname] emdi
[Sysname-emdi] instance eMDI1
[Sysname-emdi-instance-eMDI1] flow ipv4 tcp source 10.0.0.1 destination 10.2.2.2
[Sysname-emdi-instance-eMDI1] alarm suppression times 5
Related commands
flow ipv4 tcp
flow ipv4 udp
alarm threshold
Use alarm threshold to set alarm thresholds for an eMDI instance.
Use undo alarm threshold to restore the defaults.
Syntax
alarm { dplr | rtp-lr | rtp-ser | uplr } threshold threshold-value
undo alarm { dplr | rtp-lr | rtp-ser | uplr } threshold
Default
The alarm thresholds for an eMDI instance are all 100.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
dplr: Sets the alarm threshold for the downstream TCP packet loss rate.
rtp-lr: Sets the alarm threshold for the RTP packet loss rate.
rtp-ser: Sets the alarm threshold for the RTP packet sequence error rate.
uplr: Sets the alarm threshold for the upstream TCP packet loss rate.
threshold-value: Specifies the alarm threshold value, which is the number of lost or out-of-order packets among 100000 packets. The value range is 1 to 100000.
Usage guidelines
A started eMDI instance monitors its data flow and periodically collects statistics on lost and out-of-order packets.
· If a statistic is equal to or greater than the alarm threshold, the instance triggers an alarm. When the number of consecutive alarms of the same type exceeds the logging threshold, the device sends an alarm log message to the information center.
· If a statistic is less than the alarm threshold, the instance records an alarm removal event. When the number of consecutive alarm removal events of the same type exceeds the logging threshold, the device sends an alarm-removed log message to the information center.
For more information about the information center, see "Configuring information center."
To modify alarm thresholds for an eMDI instance that is already started, you must stop the instance first by executing the stop command.
Examples
# Set the downstream TCP packet loss rate to 1/100 for eMDI instance eMDI1.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI1
[Sysname-emdi-instance-eMDI1] flow ipv4 tcp source 10.0.0.1 destination 10.2.2.2
[Sysname-emdi-instance-eMDI1] alarm dplr threshold 1000
Related commands
flow ipv4 tcp
flow ipv4 udp
description
Use description to configure a description for an eMDI instance.
Use undo description to restore the default.
Syntax
description text
undo description
Default
An eMDI instance does not have a description.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 255 characters.
Usage guidelines
You can use this command to add, delete, or modify the description for a running instance.
Examples
# Set the description to eMDI1 for eMDI instance eMDI1.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI1
[Sysname-emdi-instance-eMDI1] description eMDI1
display emdi instance
Use display emdi instance to display eMDI instance information.
Syntax
display emdi instance [ name instance-name | id instance-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
name instance-name: Specifies an eMDI instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an instance, this command displays information about all instances.
id instance-id: Specifies an eMDI instance by its ID. If you do not specify an instance, this command displays information about all instances.
verbose: Displays detailed instance information. If you do not specify this keyword, the command displays brief instance information.
Examples
# Display brief information about eMDI instance eMDI1.
<Sysname> display emdi instance name eMDI1
Status Protocol Type Source IP/Port Destination IP/Port
Active TCP Static 1.1.1.1/2001 2.2.2.2/2010
# Display brief information about all eMDI instances.
<Sysname> display emdi instance
Brief information about all instances:
ID Name Type Instance status Protocol
1 eMDI1 Static Active TCP
2 - Dynamic Inactive UDP
# Display detailed information about eMDI instance eMDI1, which monitors a TCP data flow.
<Sysname> display emdi instance name eMDI1 verbose
Instance name : eMDI1
ID : 1
Instance status : Active
Protocol : TCP
Type : Static
Destination IP : 2.2.2.2
Destination port : 2010
Source IP : 1.1.1.1
Source port : 2001
VLAN ID : 45
VXLAN ID : -
Monitoring period : 10 sec
Monitoring periods that passed : 30
Lifetime : 10 hours
Running time : 8 hours 20 min 30 sec
Normal periods : 29
Abnormal periods : 1
UPLR : 1000
DPLR : 1000
# Display detailed information about eMDI instance 2, which monitors a UDP data flow.
<Sysname> display emdi instance id 2 verbose
Instance name : -
ID : 2
Instance status : Inactive
Protocol : UDP
Type : Dynamic
Destination IP : 2.2.2.2
Destination port : 2010
Source IP : 1.1.1.1
Source port : 2001
VLAN ID : 45
VXLAN ID : -
Payload type : -
Clock rate : 90000 Hz
Monitoring period : 10 sec
Monitoring periods that passed : 30
Lifetime : 10 hours
Running time : 8 hours 20 min 30 sec
Normal periods : 29
Abnormal periods : 1
RTP-LR : 100
RTP-SER : 100
FEC window : 100
FEC threshold : 5
Table 1 Command output
|
Field |
Description |
|
Status Instance status |
Instance status: · Active. · Inactive. |
|
Protocol |
Transport layer protocol of the data flow: · TCP. · UDP. |
|
Type |
Instance creation method: · Static—The eMDI instance was manually configured at the CLI. · Dynamic—The eMDI instance was created by other features. |
|
Source IP/Port Source Port |
Source IP address and source port of the data flow. |
|
Destination IP/Port Destination Port |
Destination IP address and destination port of the data flow. |
|
ID |
Instance ID. |
|
Name/Instance name |
Instance name. |
|
VLAN ID |
VLAN ID of the data flow. |
|
VXLAN ID |
VXLAN ID of the data flow. |
|
Monitoring period |
Instance monitoring period, in seconds. |
|
Monitoring periods that passed |
Number of passed monitoring periods. If the device did not receive packets of the data flow within some monitoring periods, the number of passed monitoring periods is greater than the total number of normal periods and abnormal periods. |
|
Lifetime |
Instance lifetime. |
|
Running time |
Instance running time. The value of this field might be slightly greater than the value of the lifetime field in the following situations: · The instance lifetime has expired but the current monitoring period has not. The instance will run until the current monitoring period expires. · The instance lifetime is long and the instance running time is reaching or has already reached the instance lifetime. |
|
Normal periods |
Number of periods when both the number of lost packets and the number of out-of-order packets were within the alarm thresholds. |
|
Abnormal periods |
Number of periods when the number of lost or out-of-order packets exceeded the alarm threshold. |
|
UPLR |
Alarm threshold for the upstream TCP packet loss rate. |
|
DPLR |
Alarm threshold for the downstream TCP packet loss rate. |
|
Payload type |
RTP packet payload type of the UDP data flow to be monitored. |
|
Clock rate |
RTP packet clock frequency of the UDP data flow to be monitored, in Hz. |
|
RTP-LR |
Alarm threshold for the RTP packet loss rate. |
|
RTP-SER |
Alarm threshold for the RTP sequence error rate. |
|
FEC window |
Sliding window size for UDP data flow quality monitoring. |
|
FEC threshold |
FEC packet loss threshold for UDP data flow quality monitoring. |
display emdi resource
Use display emdi resource to display eMDI instance resource information.
Syntax
display emdi resource
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display eMDI instance resource information.
<Sysname> display emdi resource
Specifications(Slot 1):
Max instances : 100
Max UDP instances : 100
Max TCP instances : 100
Max static instances : 100
Max dynamic instances : 100
Configuration(Slot 1):
Configured instances : 0
Running instances : 0
Running UDP instances : 0
Running TCP instances : 0
Running static instances : 0
Running dynamic instances : 0
Specifications and configuration(Slot 2):
Max instances : 100
Running instances : 0
Table 2 Command output
|
Field |
Description |
|
Specifications |
Supported eMDI specifications. |
|
Max instances |
Maximum number of instances that can run at the same time. |
|
Max UDP instances |
Maximum number of UDP instances that can run at the same time. |
|
Max TCP instances |
Maximum number of TCP instances that can run at the same time. |
|
Max static instances |
Maximum number of static instances that can run at the same time. |
|
Max dynamic instances |
Maximum number of dynamic instances that can run at the same time. |
|
Configuration |
Current eMDI configuration. |
|
Configured instances |
Number of configured instances. |
|
Running instances |
Total number of running instances. Total number of running instances = Number of running UDP instances + Number of running TCP instances = Number of running static instances + Number of running dynamic instances. |
|
Running UDP instances |
Number of running instances that monitors UDP data flows. |
|
Running TCP instances |
Number of running instances that monitors TCP data flows. |
|
Running static instances |
Number of running static instances. |
|
Running dynamic instances |
Number of running dynamic instances. |
|
Specifications and configuration |
Supported eMDI specifications and current eMDI configuration. |
Related commands
emdi
display emdi statistics
Use display emdi statistics to display monitoring statistics for an eMDI instance.
Syntax
display emdi statistics { instance-name instance-name | instance-id instance-id } [ number number ] [ abnormal | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
instance-name instance-name: Specifies an eMDI instance by its name, a case-sensitive string of 1 to 31 characters.
instance-id instance-id: Specifies an eMDI instance by its ID.
number number: Displays statistics for the specified number of monitoring periods. The number argument is in the range of the 1 to 60. The default value is 3.
abnormal: Displays statistics for periods with lost or out-of-order packets. If you do not specify this keyword, the command displays statistics for both normal periods and abnormal periods.
verbose: Displays detailed monitoring statistics for the data flow. If you do not specify this keyword, the command displays brief monitoring statistics.
Usage guidelines
The device stores only the monitoring statistics within the most recent 60 monitoring periods for each eMDI instance.
If you specify both the abnormal keyword and the number number option, this command displays statistics for the specified number of abnormal periods.
Examples
# Display brief monitoring statistics for eMDI instance eMDI1.
<Sysname> display emdi statistics instance-name eMDI1
Instance name : eMDI1
Instance ID : 1
Monitoring period: 10 sec
Protocol : TCP
Unit for DPLR and UPLR is 1/100000
Timestamp Status Rate(bps) DPLR UPLR DRTT(us) URTT(us)
2019/09/17 16:17:20 Normal 4539000 0 0 2694 2315
2019/09/17 16:17:10 Abnormal 4865656 46786 0 3656 3711
2019/09/17 16:17:00 Abnormal 4865656 12362 4568 69564 26965
# Display brief monitoring statistics for the most recent two monitoring periods of eMDI instance eMDI2.
<Sysname> display emdi statistics instance-name eMDI2 number 2
Instance name : eMDI2
Instance ID : 2
Monitoring period: 10 sec
Protocol : UDP
Unit for RTP-LR, RTP-SER and RTP-ELF is 1/100000
Timestamp Status RTP-LR RTP-SER Jitter(us) RTP-LP RTP-ELF
2019/09/17 16:17:20 Normal 0 0 4294 0 0
2019/09/17 16:17:10 Abnormal 36533 25365 6729 15 12566
# Display detailed monitoring statistics for eMDI instance eMDI3.
<Sysname> display emdi statistics instance-name eMDI3 verbose
Instance name : eMDI3
Instance ID : 3
Monitoring period : 10 sec
Protocol : UDP
Timestamp : 2019-09-17 17:02:00
Service module : Slot 1
Inbound interface : Ten-GigabitEthernet1/0/1
Flow status : Abnormal
Received packets : 3850
Rate : 128 pps
Received bytes : 5390000
Rate : 1437333 bps
Lost packets : 32261
RTP-LR : 89338/100000
Packet out of sequence : 0
RTP-SER : 0/100000
RTP-LP : 5
RTP-ELF : 2/100000
Maximum jitter : 8815 us
Average jitter : 8540 us
Minimum jitter : 8262 us
Timestamp : 2019-09-17 17:01:50
Service module : Slot 1
Inbound interface : Ten-GigabitEthernet1/0/1
Flow status : Normal
Received packets : 3736
Rate : 128 pps
Received bytes : 5145000
Rate : 1237333 bps
Lost packets : 31481
RTP-LR : 81569/100000
Packet out of sequence : 0
RTP-SER : 0/100000
RTP-LP : 5
RTP-ELF : 2/100000
Maximum jitter : 7885 us
Average jitter : 7564 us
Minimum jitter : 7242 us
Timestamp : 2019-09-17 17:01:40
Service module : Slot 1
Inbound interface : Ten-GigabitEthernet1/0/1
Flow status : Normal
Received packets : 3736
Rate : 128 pps
Received bytes : 5145000
Rate : 1237333 bps
Lost packets : 31481
RTP-LR : 81569/100000
Packet out of sequence : 0
RTP-SER : 0/100000
RTP-LP : 5
RTP-ELF : 2/100000
Maximum jitter : 7885 us
Average jitter : 7564 us
Minimum jitter : 7242 us
# Display detailed monitoring statistics for the most recent monitoring period of eMDI instance eMDI4.
<Sysname> display emdi statistics instance-name eMDI4 number 1 verbose
Instance name : eMDI4
Instance ID : 4
Monitoring period : 10 sec
Protocol : TCP
Timestamp : 2019-09-17 17:02:00
Service module : Slot 1
Inbound interface : Ten-GigabitEthernet1/0/1
Flow status : Abnormal
Received packets : 95
Rate : 9 pps
Received bytes : 12510
Rate : 10008 bps
UPLC : 0
UPLR : 0/100000
DPLC : 0
DPLR : 0/100000
URTT : 35 us
DRTT : 8354549 us
Service module : Slot 2
Inbound interface : GigabitEthernet2/0/1
Flow status : Abnormal
Received packets : 95
Rate : 9 pps
Received bytes : 12510
Rate : 10008 bps
UPLC : 0
UPLR : 0/100000
DPLC : 0
DPLR : 0/100000
URTT : 35 us
DRTT : 8354549 us
# Display statistics for abnormal periods of eMDI instance eMDI5.
<Sysname> display emdi statistics instance-name eMDI5 abnormal
Instance name : eMDI5
Instance ID : 5
Monitoring period : 10 sec
Protocol : TCP
Timestamp : 2019-09-17 17:02:00
Service module : Slot 1
Inbound interface : Ten-GigabitEthernet1/0/1
Flow status : Abnormal
Received packets : 95
Rate : 9 pps
Received bytes : 12510
Rate : 10008 bps
UPLC : 0
UPLR : 0/100000
DPLC : 0
DPLR : 0/100000
URTT : 35 us
DRTT : 8354549 us
Timestamp : 2019-09-17 17:00:00
Service module : Slot 1
Inbound interface : Ten-GigabitEthernet1/0/1
Flow status : Abnormal
Received packets : 95
Rate : 9 pps
Received bytes : 12510
Rate : 10008 bps
UPLC : 0
UPLR : 0/100000
DPLC : 0
DPLR : 0/100000
URTT : 35 us
DRTT : 8354549 us
Timestamp : 2019-09-17 16:58:00
Service module : Slot 1
Inbound interface : Ten-GigabitEthernet1/0/1
Flow status : Abnormal
Received packets : 95
Rate : 9 pps
Received bytes : 12510
Rate : 10008 bps
UPLC : 0
UPLR : 0/100000
DPLC : 0
DPLR : 0/100000
URTT : 35 us
DRTT : 8354549 us
Table 3 Command output
|
Field |
Description |
|
Monitoring period |
Monitoring period of the eMDI instance, in seconds. |
|
Protocol |
Transport layer protocol of the data flow: · TCP. · UDP. |
|
Timestamp |
Time when the statistics were recorded. |
|
Status Flow status |
Flow status: · Normal. · Abnormal. |
|
Rate |
Packet input rate, in bps or pps. If no packets of the data flow were received within the monitoring period, this field displays a hyphen (-). |
|
DPLR |
Downstream packet loss rate, in units of one hundred thousandth. |
|
UPLR |
Upstream packet loss rate, in units of one hundred thousandth. |
|
DRTT |
Average downstream round trip time, in microseconds. |
|
URTT |
Average upstream round trip time, in microseconds. |
|
RTP-LR |
RTP packet loss rate, in units of one hundred thousandth. |
|
RTP-SER |
RTP packet sequence error rate, in units of one hundred thousandth. |
|
Jitter |
RTP packet jitter, in microseconds. |
|
RTP-LP |
Maximum number of continuously lost RTP packets. |
|
RTP-ELF |
RTP effective loss factor for Forward Error Correct (FEC), in units of one hundred thousandth. |
|
Service module |
Number of the slot where the instance resides. |
|
Inbound interface |
Inbound interface of the packets. |
|
Received packets |
Number of received packets. |
|
Received bytes |
Bytes of received TCP or UDP packets. |
|
Lost packets |
Number of lost packets. |
|
Packet out of sequence |
Number of out-of-order packets. |
|
Maximum jitter |
Maximum jitter in microseconds. |
|
Average jitter |
Average jitter in microseconds. |
|
Minimum jitter |
Minimum jitter in microseconds. |
|
UPLC |
Number of lost upstream packets. |
|
DPLC |
Number of lost downstream packets. |
emdi
Use emdi to enable eMDI and enter its view.
Use undo emdi to restore the default.
Syntax
emdi
undo emdi
Default
eMDI is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
The undo emdi command disables eMDI and deletes all eMDI settings.
Examples
# Enable eMDI and enter its view.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi]
fec
Use fec to specify the sliding window size and packet loss threshold for a UDP data flow to be monitored.
Use undo fec to restore the default.
Syntax
fec { window window-size | threshold threshold-value } *
undo fec
Default
The sliding window size and packet loss threshold for a UDP data flow are 100 and 5, respectively.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
window window-size: Specifies the sliding window size in packets, in the range of 10 to 1000.
threshold threshold-value: Specifies the packet loss threshold in packets, in the range of 1 to 100.
Usage guidelines
This command enables you to monitor the packet loss conditions of the UDP data flow. After each window slide, the system identifies whether the number of lost data packets in the window within the monitoring period is greater than the threshold. If yes, the system increases RTP-ELF by 1. The window sliding stops when the monitoring period expires. If the total number of packet loss windows is greater than 0 within a monitoring period, a video fault exists.
This command is intended for a UDP data flow. Before executing this command, you must specify the UDP data flow for the eMDI instance to monitor.
The packet loss threshold must be smaller than the sliding window size.
To modify the FEC settings for an eMDI instance that is already started, you must stop the instance first by executing the stop command.
Examples
# Set the sliding window size and packet loss threshold for eMDI instance eMDI1 to 10 and 5, respectively.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI1
[Sysname-emdi-instance-eMDI1] flow ipv4 udp source 10.0.0.1 destination 10.2.2.2
[Sysname-emdi-instance-eMDI1] fec window 10 threshold 5
Related commands
flow ipv4 udp
flow ipv4 tcp
Use flow ipv4 tcp to specify a TCP data flow to be monitored.
Use undo flow to restore the default.
Syntax
flow ipv4 tcp source source-ip-address destination destination-ip-address [ destination-port destination-port-number | source-port source-port-number | vlan vlan-id | vni vxlan-id ] *
undo flow
Default
No TCP data flow is specified for an eMDI instance.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
source source-ip address: Specifies the source IP address of the data flow in dotted-decimal notation.
destination destination-ip-address: Specifies the destination IP address of the data flow in dotted-decimal notation.
destination-port destination-port-number: Specifies the destination port number of the data flow, in the range of 1 to 65535.
source-port source-port-number: Specifies the source port number of the data flow, in the range of 1 to 65535.
vlan vlan-id: Specifies the VLAN ID of the data flow, in the range of 1 to 4094.
vni vxlan-id: Specifies the VXLAN ID of the data flow, in the range of 0 to 16777215.
Usage guidelines
You can specify a data flow by using any combination of the following items: source IP address, destination IP address, source port number, destination port number, VLAN ID, and VXLAN ID. Using more items defines a more granular data flow and provides more helpful monitoring data and analysis results.
For a VXLAN data flow, all parameters except VXLAN ID are used to match the fields in the inner packet header.
An eMDI instance can monitor only one data flow. A data flow can be monitored by only one eMDI instance.
If you execute this command multiple times when the eMDI instance is not started, the most recent configuration takes effect.
To modify the data flow configuration for an instance that is already started, you must stop the instance first by executing the stop command.
The undo flow command also restores the default eMDI alarm settings.
Examples
# Configure eMDI instance eMDI2 to monitor the TCP data flow from 10.0.0.1 to 10.0.0.2.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI2
[Sysname-emdi-instance-eMDI2] flow ipv4 tcp source 10.0.0.1 destination 10.0.0.2
flow ipv4 udp
Use flow ipv4 udp to specify a UDP data flow to be monitored.
Use undo flow to restore the default.
Syntax
flow ipv4 udp source source-ip-address destination destination-ip-address [ destination-port destination-port-number | source-port source-port-number | vlan vlan-id | vni vxlan-id | pt pt-value | clock-rate clock-rate-value ] *
undo flow
Default
No UDP data flow is specified for an eMDI instance.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
source source-ip address: Specifies the source IP address of the data flow in dotted-decimal notation.
destination destination-ip-address: Specifies the destination IP address of the data flow in dotted-decimal notation.
destination-port destination-port-number: Specifies the destination port number of the data flow, in the range of 1 to 65535.
source-port source-port-number: Specifies the source port number of the data flow, in the range of 1 to 65535.
vlan vlan-id: Specifies the VLAN ID of the data flow, in the range of 1 to 4094.
vni vxlan-id: Specifies the VXLAN ID of the data flow, in the range of 0 to 16777215.
pt pt-value: Specifies the RTP packet payload type of the data flow, in the range of 25 to 71 or 77 to 127.
clock-rate clock-rate-value: Specifies the RTP packet clock frequency. The available values include 8000 Hz, 16000 Hz, and 90000 Hz. The default value is 90000 Hz. The specified RTP packet clock frequency must be the sampling frequency of the data flow. If not, the calculated jitter values cannot reflect the actual situation.
Usage guidelines
You can specify a data flow by using any combination of the following items: source IP address, destination IP address, source port number, destination port number, VLAN ID, and VXLAN ID. Using more items defines a more granular data flow and provides more helpful monitoring data and analysis results.
For a VXLAN data flow, all parameters except VXLAN ID are used to match the fields in the inner packet header.
An eMDI instance can monitor only one data flow. A data flow can be monitored by only one eMDI instance.
If you execute this command multiple times when the eMDI instance is not started, the most recent configuration takes effect.
To modify the data flow configuration for an instance that is already started, you must stop the instance first by executing the stop command.
The undo flow command also restores the default eMDI alarm settings and FEC settings.
Examples
# Configure eMDI instance eMDI1 to monitor the UDP data flow from 10.0.0.1 to 10.0.0.2.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI1
[Sysname-emdi-instance-eMDI1] flow ipv4 udp source 10.0.0.1 destination 10.0.0.2
instance
Use instance to create an eMDI instance and enter its view, or enter the view of an existing eMDI instance.
Use undo instance to delete an eMDI instance.
Syntax
instance instance-name
undo instance instance-name
Default
No eMDI instance exists.
Views
eMDI view
Predefined user roles
network-admin
mdc-admin
Parameters
instance-name: Specifies the name for the eMDI instance, a case-sensitive string of 1 to 31 characters.
Usage guidelines
eMDI instances are fundamental elements of the eMDI feature. Each eMDI instance monitors one data flow as defined by its parameters, including the lifetime, monitoring period, and alarm thresholds.
A data flow can be monitored by only one eMDI instance.
To view the maximum number of eMDI instances that the device can run at the same time, execute the display emdi resource command.
Examples
# Create an eMDI instance named eMDI1.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI1
Related commands
display emdi resource
lifetime
Use lifetime to specify the eMDI instance lifetime.
Use undo lifetime to restore the default.
Syntax
lifetime { seconds seconds | minutes minutes | hours hours | days days }
undo lifetime
Default
The eMDI instance lifetime is 1 hour.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
seconds seconds: Specifies the lifetime in seconds. The value range is 300 to 604800.
minutes minutes: Specifies the lifetime in minutes. The value range is 5 to 10080.
hours hours: Specifies the lifetime in hours. The value range is 1 to 168.
days days: Specifies the lifetime in days. The value range is 1 to 7.
Usage guidelines
An eMDI instance starts to operate after you use the start command to start it, and it stops when its lifetime expires.
To change the lifetime for an eMDI instance that is already started, you must stop the instance first by executing the stop command.
Examples
# Set the lifetime to 300 seconds for eMDI instance eMDI1.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI1
[Sysname-emdi-instance-eMDI1] lifetime seconds 300
monitor-period
Use monitor-period to specify the monitoring period for an eMDI instance.
Use undo monitor-period to restore the default.
Syntax
monitor-period period-value
undo monitor-period
Default
The monitoring period for an eMDI instance is 60 seconds.
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Parameters
period-value: Specifies the monitoring period, which can be 10, 30, or 60 seconds.
Usage guidelines
The eMDI instance obtains monitoring data from the device periodically.
To change the monitoring period for an eMDI instance that is already started, you must stop the instance first by executing the stop command.
Examples
# Set the monitoring period to 10 seconds for eMDI instance eMDI1.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI1
[Sysname-emdi-instance-eMDI1] monitor-period 10
reset emdi statistics
Use reset emdi statistics to clear eMDI statistics.
Syntax
reset emdi statistics [ instance-name instance-name | instance-id instance-id-value ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
instance instance-name: Specifies an instance by its name, a case-sensitive string of 1 to 31 characters.
instance-id instance-id: Specifies an instance by its ID. If you do not specify this option, this command displays information about all instances.
Usage guidelines
If you do not specify the instance instance-name or instance-id instance-id option, this command clears statistics about all static instances.
The dynamic instance is identified only by its ID. With the instance instance-name option specified, this command clears statistics about the specified static instance.
With the instance-id instance-id option specified, this command clears statistics about the specified instances whatever the instance is static or dynamic.
Examples
# Clear statistics about eMDI instance eMDI1.
<Sysname> reset emdi statistics instance-name eMDI1
Related commands
display emdi statistics
start
Use start to start an eMDI instance.
Syntax
start
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
A started eMDI instance automatically stops upon a master/subordinate or active/standby switchover. You must execute this command again to start the instance.
To modify the configuration for an eMDI instance that is already started, stop the instance first by executing the stop command.
Examples
# Start eMDI instance eMDI2.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI2
[Sysname-emdi-instance-eMDI2] flow ipv4 udp source 10.0.0.1 destination 10.0.0.2
[Sysname-emdi-instance-eMDI2] start
Related commands
flow ipv4 tcp
flow ipv4 udp
stop
Use stop to stop an eMDI instance.
Syntax
stop
Views
eMDI instance view
Predefined user roles
network-admin
mdc-admin
Examples
# Stop eMDI instance eMDI2.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] instance eMDI2
[Sysname-emdi-instance-eMDI2] stop
stop all
Use stop all to stop all eMDI instances.
Syntax
stop all
Views
eMDI view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
This command stops all running static instances.
Examples
# Stop all eMDI instances.
<Sysname> system-view
[Sysname] emdi
[Sysname-emdi] stop all
