- Table of Contents
-
- H3C Fixed Port Campus Switches Configuration Examples-6W105
- 00-Applicable hardware and software versions
- 01-Login Management Configuration Examples
- 02-RBAC Configuration Examples
- 03-Software Upgrade Examples
- 04-ISSU Configuration Examples
- 05-Software Patching Examples
- 06-Ethernet Link Aggregation Configuration Examples
- 07-Port Isolation Configuration Examples
- 08-Spanning Tree Configuration Examples
- 09-VLAN Configuration Examples
- 10-VLAN Tagging Configuration Examples
- 11-DHCP Snooping Configuration Examples
- 12-Cross-Subnet Dynamic IP Address Allocation Configuration Examples
- 13-IPv6 over IPv4 Tunneling with OSPFv3 Configuration Examples
- 14-IPv6 over IPv4 GRE Tunnel Configuration Examples
- 15-GRE with OSPF Configuration Examples
- 16-OSPF Configuration Examples
- 17-IS-IS Configuration Examples
- 18-BGP Configuration Examples
- 19-Policy-Based Routing Configuration Examples
- 20-OSPFv3 Configuration Examples
- 21-IPv6 IS-IS Configuration Examples
- 22-Routing Policy Configuration Examples
- 23-IGMP Snooping Configuration Examples
- 24-IGMP Configuration Examples
- 25-MLD Snooping Configuration Examples
- 26-IPv6 Multicast VLAN Configuration Examples
- 27-ACL Configuration Examples
- 28-Traffic Policing Configuration Examples
- 29-GTS and Rate Limiting Configuration Examples
- 30-Traffic Filtering Configuration Examples
- 31-AAA Configuration Examples
- 32-Port Security Configuration Examples
- 33-Portal Configuration Examples
- 34-SSH Configuration Examples
- 35-IP Source Guard Configuration Examples
- 36-Ethernet OAM Configuration Examples
- 37-CFD Configuration Examples
- 38-DLDP Configuration Examples
- 39-VRRP Configuration Examples
- 40-BFD Configuration Examples
- 41-NTP Configuration Examples
- 42-SNMP Configuration Examples
- 43-NQA Configuration Examples
- 44-Mirroring Configuration Examples
- 45-sFlow Configuration Examples
- 46-OpenFlow Configuration Examples
- 47-MAC Address Table Configuration Examples
- 48-Static Multicast MAC Address Entry Configuration Examples
- 49-IP Unnumbered Configuration Examples
- 50-MVRP Configuration Examples
- 51-MCE Configuration Examples
- 52-Attack Protection Configuration Examples
- 53-Smart Link Configuration Examples
- 54-RRPP Configuration Examples
- 55-BGP Route Selection Configuration Examples
- 56-IS-IS Route Summarization Configuration Examples
- 57-VXLAN Configuration Examples
- 58-DRNI Configuration Examples
- 59-IRF 3.1 Configuration Examples
- 60-PTP Configuration Examples
- 61-S-MLAG Configuration Examples
- 62-Puppet Configuration Examples
- 63-802.1X Configuration Examples
- 64-MAC Authentication Configuration Examples
- 65-ISATAP Tunnel and 6to4 Tunnel Configuration Examples
- 66-BIDIR-PIM Configuration Examples
- 67-Congestion Avoidance and Queue Scheduling Configuration Examples
- 68-Basic MPLS Configuration Examples
- 69-MPLS L3VPN Configuration Examples
- 70-MPLS OAM Configuration Examples
- 71-EVPN-DCI over an MPLS L3VPN Network Configuration Examples
- 72-DRNI and EVPN Configuration Examples
- 73-Multicast VPN Configuration Examples
- 74-MPLS TE Configuration Examples
- 75-Control Plane-Based QoS Policy Configuration Examples
- 76-Priority Mapping and Queue Scheduling Configuration Examples
- 77-ARP Attack Protection Configuration Examples
- 78-IRF Software Upgrade Configuration Examples
- 79-IRF Member Replacement Configuration Examples
- 80-Layer 3 Multicast on Multicast Source-Side DR System Configuration Examples
- 81-EVPN Multicast Configuration Examples
- 82-Priority Marking and Queue Scheduling Configuration Examples
- 83-EAA Configuration Examples
- 84-GRE Tunnel Access to MPLS L3VPN Configuration Examples
- 85-MC-NAT Configuration Examples
- 86-M-LAG Configuration Examples (Applicable to M-LAG Versions)
- 87-MOD Configuration Examples
- 88-MPLS L2VPN Configuration Examples
- 89-VPLS Configuration Examples
- 90-SR-MPLS Configuration Examples
- 91-VCF Fabric Configuration Examples
- 92-NetStream Configuration Examples
- 93-Configuration Example for Software Upgrade with Zero Packet Loss by Using GIR in VXLAN M-LAG Network
- 94-Configuration Example for Software Upgrade with Zero Packet Loss by Using GIR in VXLAN DRNI Network
- Related Documents
-
83-EAA Configuration Examples
Contents
Example: Configuring an EAA TCL monitoring policy
Applicable hardware and software versions
Example: Configuring an EAA CLI monitoring policy
Applicable hardware and software versions
Example: Configuring EAA and track entry association
Applicable hardware and software versions
Introduction
This document describes typical configurations for EAA.
Prerequisites
The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.
This document assumes you are familiar with EAA features. For the same requirement, the implementation effects of TCL and CLI monitoring strategies are consistent. You can choose either strategy based on preference.
Example: Configuring an EAA TCL monitoring policy
Network configuration
Configure a TCL monitoring policy for the device to execute the following actions when the incoming traffic on Ten-GigabitEthernet1/0/1 reaches or exceeds 500 Mbps:
· Generate logs for traffic that exceeds the range.
· Display the current CPU state and save it to a file.
· Display the state of Ten-GigabitEthernet1/0/1 and save it to a file.
If the subsequent incoming traffic reaches or exceeds 200Mbps, monitoring will restart. When the incoming traffic on the interface is detected to exceed 500Mbps again, the aforementioned operations are executed again.
Applicable hardware and software versions
Table 1 Applicable hardware and software versions
Product |
Software version |
S6812 series S6813 series |
Release 6628Pxx |
S6550XE-HI series |
Release 8106Pxx |
S6525XE-HI series |
Release 8106Pxx |
S5850 series |
Release 8106Pxx |
S5570S-EI series |
Release 11xx |
S5560X-EI series |
Release 6628Pxx |
S5560X-HI series |
Release 6628Pxx |
S5500V2-EI series |
Release 6628Pxx |
MS4520V2-30F |
Release 6628Pxx |
MS4520V2-30C MS4520V2-54C |
Release 6628Pxx |
MS4520V2-28S MS4520V2-24TP |
Release 63xx |
S6520X-HI series S6520X-EI series |
Release 6628Pxx |
S6520X-SI series S6520-SI series |
Release 6628Pxx |
S5000-EI series |
Release 6628Pxx |
MS4600 series |
Release 6628Pxx |
ES5500 series |
Release 6628Pxx |
S5560S-EI series S5560S-SI series |
Release 63xx |
S5500V3-24P-SI S5500V3-48P-SI |
Release 63xx |
S5500V3-SI series (excluding S5500V3-24P-SI and S5500V3-48P-SI) |
Release 11xx |
S5170-EI series |
Release 11xx |
S5130S-HI series S5130S-EI series S5130S-SI series S5130S-LI series |
Release 63xx |
S5120V2-SI series S5120V2-LI series |
Release 63xx |
S5120V3-EI series |
Release 11xx |
S5120V3-36F-SI S5120V3-28P-HPWR-SI S5120V3-54P-PWR-SI |
Release 11xx |
S5120V3-SI series (excluding S5120V3-36F-SI, S5120V3-28P-HPWR-SI, and S5120V3-54P-PWR-SI) |
Release 63xx |
S5120V3-LI series |
Release 63xx |
S3600V3-EI series |
Release 11xx |
S3600V3-SI series |
Release 11xx |
S3100V3-EI series S3100V3-SI series |
Release 63xx |
S5110V2 series |
Release 63xx |
S5110V2-SI series |
Release 63xx |
S5000V3-EI series S5000V5-EI series |
Release 63xx |
S5000E-X series S5000X-EI series |
Release 63xx |
E128C E152C E500C series E500D series |
Release 63xx |
MS4320V2 series MS4320V3 series MS4300V2 series MS4320 series MS4200 series |
Release 63xx |
WS5850-WiNet series |
Release 63xx |
WS5820-WiNet series WS5810-WiNet series |
Release 63xx |
WAS6000 series |
Release 63xx |
IE4300-12P-AC & IE4300-12P-PWR IE4300-M series IE4320 series |
Release 63xx |
IE4520 series |
IE4520 series |
S5135S-EI series |
Release 6810 and later versions |
Procedures
Editing the TCL script
# Use Notepad to edit the test.tcl file as follows:
# Define the monitored event. Configure interface Ten-GigabitEthernet1/0/1 to focus on inbound traffic. When the inbound traffic reaches or exceeds 500 Mbps, configure the device to execute the specified action. The condition to re-enable polling is when the interface traffic reaches or exceeds 200Mbps.
::comware::rtm::event_register interface ten-gigabitethernet1/0/1 monitor-obj rcv-bps start-op ge start-val 500000000 restart-op ge restart-val 200000000 user-role network-admin
# Configure the action to take when the monitored event occurs: Send log message XGE1/0/1 input rate exceeded 500000000bps with priority level 1 and device number local1.
::comware::rtm::action syslog priority 1 facility local1 msg "XGE1/0/1 input rate exceeded 500000000bps"
# Create the execution action for the monitored event.
::comware::create-cli
# Configure the device to execute the display cpu-usage command to display CPU usage statistics and save the information in XGE0_info.txt when the event occurs.
::comware::write-cli cli0 "display cpu-usage >> XGE0_info.txt"
# Configure the device to execute the display interface ten-gigabitetherne 1/0/1 command to display the current operating state and related information of Ten-GigabitEthernet1/0/1 and save the information in XGE0_info.txt when the event occurs.
::comware::write-cli cli0 "display interface ten-gigabitethernet1/0/1 >> XGE0_info.txt"
::comware::write-cli cli0 "end"
Configuring the device
# Configure the IP address of Ten-GigabitEthernet1/0/1.
<Device> system-view
[Device] interface ten-gigabitethernet 1/0/1
[Device-Ten-GigabitEthernet1/0/1] port link-mode route
[Device-Ten-GigabitEthernet1/0/1] ip address 192.168.100.66 255.255.255.0
[Device-Ten-GigabitEthernet1/0/1] quit
[Device] quit
# Download test.tcl to the device through TFTP.
<Device> tftp 192.168.100.14 get test.tcl
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 189 100 189 0 0 7900 0 --:--:-- --:--:-- --:--:-- 12600
# Create and enable a TCL monitoring policy, and bind the policy to TCL script test.tcl.
<Device> system-view
[Device] rtm tcl-policy test test.tcl
[Device] quit
Verifying the configuration
# Use the display rtm policy registered command to view the policy named test with the type Tcl.
<Device> display rtm policy registered
Total number: 1
Type Event TimeRegistered PolicyName
TCL INTERFACE May 05 06:46:20 2019 test
# When the inbound traffic on interface Ten-GigabitEthernet1/0/1 reaches or exceeds 500 Mbps, check all files and folder information in the device for the existence of XGE0_info.txt.
<Device> dir
Directory of cfa0:
0 -rw- 3227 Nov 19 2019 17:28:36 1.cfg
1 -rw- 2296 Apr 26 2019 18:55:08 5660_data.ak
2 -rw- 2304 Apr 26 2019 18:54:56 5660_security.ak
3 -rw- 2298 Apr 26 2019 18:55:16 5660_voice.ak
4 -rw- 3227 Nov 19 2019 17:15:19 STARTUP110.CFG
5 drw- - Mar 10 2019 04:10:10 diagfile
6 -rw- 567 Jul 17 2019 14:25:00 dsakey
7 -rw- 223 Jul 17 2019 14:25:00 ecdsakey
8 -rw- 278 Jul 17 2019 14:25:00 XGE0_info.txt
9 -rw- 735 Jul 17 2019 14:25:00 hostkey
10 -rw- 492 Nov 18 2019 16:40:50 ifindex.dat
11 -rw- 276 Apr 23 2019 19:00:00 lauth.dat
12 drw- - Jul 17 2019 11:26:34 license
13 drw- - Apr 24 2019 12:39:38 logfile
14 -rw- 18839552 Nov 14 2019 16:42:12 msr56-cmw710-boot-r000706.bin
15 -rw- 1150976 Nov 14 2019 16:43:00 msr56-cmw710-data-r000706.bin
16 -rw- 47470592 Nov 14 2019 16:42:24 msr56-cmw710-system-r000706.bin
17 -rw- 2975744 Nov 14 2019 16:42:56 msr56-cmw710-voice-r000706.bin
18 -rw- 70445056 Nov 14 2019 17:41:08 msr56.ipe
19 -rw- 70445056 Nov 14 2019 16:40:00 msr56NN.ipe
20 drw- - Aug 21 2019 16:23:10 pkey
21 -rw- 189 Nov 19 2019 17:49:34 test.tcl
22 drw- - Mar 10 2019 04:10:10 seclog
23 -rw- 591 Jul 17 2019 14:25:00 serverkey
24 -rw- 3227 Nov 18 2019 16:40:50 startup.cfg
507492 KB total (298412 KB free)
# Use the TFTP method to copy file XGE0_info.txt to the TFTP server.
<Device> tftp 192.168.100.14 put XGE0_info.txt
# View file XGE0_info.txt to display the current state of the CPU and interface Ten-GigabitEthernet1/0/1.
Unit CPU usage:
15% in last 5 seconds
14% in last 1 minute
13% in last 5 minutes
Ten-GigabitEthernet1/0/1
Current state: UP
Line protocol state: UP
Description: Ten-GigabitEthernet1/0/1 Interface
Bandwidth: 1000000 kbps
Maximum transmission unit: 1500
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
Internet address: 192.168.100.66/24 (primary)
IP packet frame type: Ethernet II, hardware address: 5cdd-7000-a07c
IPv6 packet frame type: Ethernet II, hardware address: 5cdd-7000-a07c
Loopback is not set
Media type is twisted pair, port hardware type is 1000_BASE_T
Port priority: 0
1000Mbps-speed mode, Full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 9216
Last link flapping: 0 hours 0 minutes 14 seconds
Last clearing of counters: Never
Peak input rate: 4 bytes/sec, at 2019-09-21 15:09:37
Peak output rate: 1 bytes/sec, at 2019-09-21 15:09:37
Last 300 seconds input rate: 568710000.25 bytes/sec, 64970 bits/sec, 4.96 packets/sec
Last 300 seconds output rate: 568710000.25 bytes/sec, 64970 bits/sec, 4.96 packets/sec Input (total): 1703 packets, 2336882000 bytes
0 unicasts, 0 broadcasts, 4 multicasts, 0 pauses
Input (normal): 1703 packets, - bytes
0 unicasts, 0 broadcasts, 4 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 1706 packets, 2337062000 bytes
0 unicasts, 5 broadcasts, 0 multicasts, 0 pauses
Output (normal): 1706 packets, - bytes
0 unicasts, 5 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier
Configuration files
· Script text for test.tcl:
::comware::rtm::event_register interface ten-gigabitethernet1/0/1 monitor-obj rcv-bps start-op ge start-val 500000000 restart-op ge restart-val 200000000 user-role network-admin
::comware::rtm::action syslog priority 1 facility local1 msg "XGE1/0/1 input rate exceeded 500000000bps"
::comware::create-cli
::comware::write-cli cli0 "display cpu-usage >> XGE0_info.txt"
::comware::write-cli cli0 "display interface ten-gigabitethernet1/0/1 >> XGE0_info.txt"
::comware::write-cli cli0 "end"
· Device:
#
interface Ten-GigabitEthernet1/0/1
port link-mode route
ip address 192.168.100.66 255.255.255.0
#
rtm tcl-policy test test.tcl
#
Example: Configuring an EAA CLI monitoring policy
Network configuration
Configure a CLI monitoring policy for the device to execute the following actions when the incoming traffic on Ten-GigabitEthernet1/0/1 reaches or exceeds 500 Mbps:
· Generate logs for traffic that exceeds the range.
· Display the current CPU state and save it to a file.
· Display the state of Ten-GigabitEthernet1/0/1 and save it to a file.
If the subsequent incoming traffic reaches or exceeds 200Mbps, monitoring will restart. When the incoming traffic on the interface is detected to exceed 500Mbps again, the aforementioned operations are executed again.
Applicable hardware and software versions
Table 2 Applicable hardware and software versions
Product |
Software version |
S6812 series S6813 series |
Release 6628Pxx |
S6550XE-HI series |
Release 8106Pxx |
S6525XE-HI series |
Release 8106Pxx |
S5850 series |
Release 8106Pxx |
S5570S-EI series |
Release 11xx |
S5560X-EI series |
Release 6628Pxx |
S5560X-HI series |
Release 6628Pxx |
S5500V2-EI series |
Release 6628Pxx |
MS4520V2-30F |
Release 6628Pxx |
MS4520V2-30C MS4520V2-54C |
Release 6628Pxx |
MS4520V2-28S MS4520V2-24TP |
Release 63xx |
S6520X-HI series S6520X-EI series |
Release 6628Pxx |
S6520X-SI series S6520-SI series |
Release 6628Pxx |
S5000-EI series |
Release 6628Pxx |
MS4600 series |
Release 6628Pxx |
ES5500 series |
Release 6628Pxx |
S5560S-EI series S5560S-SI series |
Release 63xx |
S5500V3-24P-SI S5500V3-48P-SI |
Release 63xx |
S5500V3-SI series (excluding S5500V3-24P-SI and S5500V3-48P-SI) |
Release 11xx |
S5170-EI series |
Release 11xx |
S5130S-HI series S5130S-EI series S5130S-SI series S5130S-LI series |
Release 63xx |
S5120V2-SI series S5120V2-LI series |
Release 63xx |
S5120V3-EI series |
Release 11xx |
S5120V3-36F-SI S5120V3-28P-HPWR-SI S5120V3-54P-PWR-SI |
Release 11xx |
S5120V3-SI series (excluding S5120V3-36F-SI, S5120V3-28P-HPWR-SI, and S5120V3-54P-PWR-SI) |
Release 63xx |
S5120V3-LI series |
Release 63xx |
S3600V3-EI series |
Release 11xx |
S3600V3-SI series |
Release 11xx |
S3100V3-EI series S3100V3-SI series |
Release 63xx |
S5110V2 series |
Release 63xx |
S5110V2-SI series |
Release 63xx |
S5000V3-EI series S5000V5-EI series |
Release 63xx |
S5000E-X series S5000X-EI series |
Release 63xx |
E128C E152C E500C series E500D series |
Release 63xx |
MS4320V2 series MS4320V3 series MS4300V2 series MS4320 series MS4200 series |
Release 63xx |
WS5850-WiNet series |
Release 63xx |
WS5820-WiNet series WS5810-WiNet series |
Release 63xx |
WAS6000 series |
Release 63xx |
IE4300-12P-AC & IE4300-12P-PWR IE4300-M series IE4320 series |
Release 63xx |
IE4520 series |
IE4520 series |
S5135S-EI series |
Release 6810 and later versions |
Restrictions and guidelines
· For a policy, you can configure only one trigger event and one running time. When you repeatedly execute the event or running-time commands, the most recently configured and committed changes take effect.
· If the number of the newly configured action matches an existing action number, execute the commit command for the most recent configuration to take effect.
· After configuring the event, action, user role, and running time for the CLI monitoring policy, you must execute the commit command to enable the policy and activate its configurations.
Procedures
# Configure the IP address of Ten-GigabitEthernet1/0/1.
<Device> system-view
[Device] interface ten-gigabitethernet 1/0/1
[Device-Ten-GigabitEthernet1/0/1] port link-mode route
[Device-Ten-GigabitEthernet1/0/1] ip address 192.168.100.66 255.255.255.0
[Device-Ten-GigabitEthernet1/0/1] quit
# Create CLI policy 1.
[Device] rtm cli-policy 1
# Configure the monitored event. Configure the device to execute the specified action when the inbound traffic on interface Ten-GigabitEthernet1/0/1 reaches or exceeds 500 Mbps. The condition to re-enable polling is when the interface traffic reaches or exceeds 200Mbps.
[Device-rtm-1] event interface ten-gigabitethernet 1/0/1 monitor-obj rcv-bps start-op ge start-val 500000000 restart-op ge restart-val 200000000
# Configure the action to take when the monitored event occurs: Send log message XGE1/0/1 input rate exceeded 500000000bps with priority level 1 and log recording tool local1.
[Device-rtm-1] action 1 syslog priority 1 facility local1 msg "XGE1/0/1 input rate exceeded 500000000bps"
# Configure the device to execute the display cpu-usage command to display CPU usage statistics and save the information in XGE0_info.txt when the event occurs.
[Device-rtm-1] action 2 cli display cpu-usage >> XGE0_info.txt
# Configure the device to execute the display interface ten-gigabitetherne 1/0/1 command to display the current operating state and related information of Ten-GigabitEthernet1/0/1 and save the information in XGE0_info.txt when the event occurs.
[Device-rtm-1] action 3 cli display interface ten-gigabitethernet 1/0/1 >> XGE0_info.txt
# Set the policy running time to 30 seconds.
[Device-rtm-1] running-time 30
# Specify user role network-admin for the execution of CLI monitoring policy 1.
[Device-rtm-1] user-role network-admin
# Enable CLI monitoring policy 1.
[Device-rtm-1] commit
[Device-rtm-1] quit
Verifying the configuration
# Use the display rtm policy registered command to view policy 1 with the type CLI.
<Device> display rtm policy registered
Total number: 1
Type Event TimeRegistered PolicyName
CLI INTERFACE May 04 00:12:40 2019 1
# When the inbound traffic on interface Ten-GigabitEthernet1/0/1 reaches or exceeds 500 Mbps, check all files and folder information in the device for the existence of XGE0_info.txt.
<Device> dir
Directory of cfa0:
0 -rw- 3227 Nov 19 2019 17:28:36 1.cfg
1 -rw- 2296 Apr 26 2019 18:55:08 5660_data.ak
2 -rw- 2304 Apr 26 2019 18:54:56 5660_security.ak
3 -rw- 2298 Apr 26 2019 18:55:16 5660_voice.ak
4 -rw- 3227 Nov 19 2019 17:15:19 STARTUP110.CFG
5 drw- - Mar 10 2019 04:10:10 diagfile
6 -rw- 567 Jul 17 2019 14:25:00 dsakey
7 -rw- 223 Jul 17 2019 14:25:00 ecdsakey
8 -rw- 278 Jul 17 2019 14:25:00 XGE0_info.txt
9 -rw- 735 Jul 17 2019 14:25:00 hostkey
10 -rw- 492 Nov 18 2019 16:40:50 ifindex.dat
11 -rw- 276 Apr 23 2019 19:00:00 lauth.dat
12 drw- - Jul 17 2019 11:26:34 license
13 drw- - Apr 24 2019 12:39:38 logfile
14 -rw- 18839552 Nov 14 2019 16:42:12 msr56-cmw710-boot-r000706.bin
15 -rw- 1150976 Nov 14 2019 16:43:00 msr56-cmw710-data-r000706.bin
16 -rw- 47470592 Nov 14 2019 16:42:24 msr56-cmw710-system-r000706.bin
17 -rw- 2975744 Nov 14 2019 16:42:56 msr56-cmw710-voice-r000706.bin
18 -rw- 70445056 Nov 14 2019 17:41:08 msr56.ipe
19 -rw- 70445056 Nov 14 2019 16:40:00 msr56NN.ipe
20 drw- - Aug 21 2019 16:23:10 pkey
21 -rw- 189 Nov 19 2019 17:49:34 test.tcl
22 drw- - Mar 10 2019 04:10:10 seclog
23 -rw- 591 Jul 17 2019 14:25:00 serverkey
24 -rw- 3227 Nov 18 2019 16:40:50 startup.cfg
507492 KB total (298412 KB free)
# Use the TFTP method to copy file XGE0_info.txt to the TFTP server.
<Device> tftp 192.168.100.14 put XGE0_info.txt
# View file XGE0_info.txt to display the current state of the CPU and interface Ten-GigabitEthernet1/0/1.
Unit CPU usage:
15% in last 5 seconds
14% in last 1 minute
13% in last 5 minutes
Ten-GigabitEthernet1/0/1
Current state: UP
Line protocol state: UP
Description: Ten-GigabitEthernet1/0/1 Interface
Bandwidth: 1000000 kbps
Maximum transmission unit: 1500
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
Internet address: 192.168.100.66/24 (primary)
IP packet frame type: Ethernet II, hardware address: 5cdd-7000-a07c
IPv6 packet frame type: Ethernet II, hardware address: 5cdd-7000-a07c
Loopback is not set
Media type is twisted pair, port hardware type is 1000_BASE_T
Port priority: 0
1000Mbps-speed mode, Full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 9216
Last link flapping: 0 hours 0 minutes 14 seconds
Last clearing of counters: Never
Peak input rate: 4 bytes/sec, at 2019-09-21 15:09:37
Peak output rate: 1 bytes/sec, at 2019-09-21 15:09:37
Last 300 seconds input rate: 568710000.25 bytes/sec, 64970 bits/sec, 4.96 packets/sec
Last 300 seconds output rate: 568710000.25 bytes/sec, 64970 bits/sec, 4.96 packets/sec Input (total): 1703 packets, 2336882000 bytes
0 unicasts, 0 broadcasts, 4 multicasts, 0 pauses
Input (normal): 1703 packets, - bytes
0 unicasts, 0 broadcasts, 4 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 1706 packets, 2337062000 bytes
0 unicasts, 5 broadcasts, 0 multicasts, 0 pauses
Output (normal): 1706 packets, - bytes
0 unicasts, 5 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier
Configuration files
#
interface Ten-GigabitEthernet1/0/1
port link-mode route
ip address 192.168.100.66 255.255.255.0
#
rtm cli-policy 1
event interface Ten-GigabitEthernet1/0/1 monitor-obj rcv-bps start-op ge start-val 500000000 restart-op ge restart-val 200000000
action 1 syslog priority 1 facility local1 msg "XGE1/0/1 input rate exceeded 500000000bps"
action 2 cli display cpu-usage >> XGE0_info.txt
action 3 cli display interface ten-gigabitethernet 1/0/1 >> XGE0_info.txt
running-time 30
user-role network-admin
#
Example: Configuring EAA and track entry association
Network configuration
Device A has established BGP sessions with Device D and Device E. Normally, traffic from Device D and Device E to the Internet is forwarded through Device A. Configure EAA and track entry association to achieve the following: When the state of interface Ten-GigabitEthernet1/0/1 connecting Device A to Device C changes to Down, Device A automatically detects the port down event and blocks BGP sessions with Device D and Device E. Consequently, traffic from Device D and Device E to the external network can be rerouted through Device B.
Applicable hardware and software versions
Table 3 Applicable hardware and software versions
Product |
Software version |
S6812 series S6813 series |
Release 6628Pxx |
S6550XE-HI series |
Release 8106Pxx |
S6525XE-HI series |
Release 8106Pxx |
S5850 series |
Release 8106Pxx |
S5570S-EI series |
Release 11xx |
S5560X-EI series |
Release 6628Pxx |
S5560X-HI series |
Release 6628Pxx |
S5500V2-EI series |
Release 6628Pxx |
MS4520V2-30F |
Release 6628Pxx |
MS4520V2-30C MS4520V2-54C |
Release 6628Pxx |
MS4520V2-28S MS4520V2-24TP |
Release 63xx |
S6520X-HI series S6520X-EI series |
Release 6628Pxx |
S6520X-SI series S6520-SI series |
Release 6628Pxx |
S5000-EI series |
Release 6628Pxx |
MS4600 series |
Release 6628Pxx |
ES5500 series |
Release 6628Pxx |
S5560S-EI series S5560S-SI series |
Release 63xx |
S5500V3-24P-SI S5500V3-48P-SI |
Release 63xx |
S5500V3-SI series (excluding S5500V3-24P-SI and S5500V3-48P-SI) |
Release 11xx |
S5170-EI series |
Release 11xx |
S5130S-HI series S5130S-EI series S5130S-SI series S5130S-LI series |
Release 63xx |
S5120V2-SI series S5120V2-LI series |
Release 63xx |
S5120V3-EI series |
Release 11xx |
S5120V3-36F-SI S5120V3-28P-HPWR-SI S5120V3-54P-PWR-SI |
Release 11xx |
S5120V3-SI series (excluding S5120V3-36F-SI, S5120V3-28P-HPWR-SI, and S5120V3-54P-PWR-SI) |
Release 63xx |
S5120V3-LI series |
Release 63xx |
S3600V3-EI series |
Release 11xx |
S3600V3-SI series |
Release 11xx |
S3100V3-EI series S3100V3-SI series |
Release 63xx |
S5110V2 series |
Release 63xx |
S5110V2-SI series |
Release 63xx |
S5000V3-EI series S5000V5-EI series |
Release 63xx |
S5000E-X series S5000X-EI series |
Release 63xx |
E128C E152C E500C series E500D series |
Release 63xx |
MS4320V2 series MS4320V3 series MS4300V2 series MS4320 series MS4200 series |
Release 63xx |
WS5850-WiNet series |
Release 63xx |
WS5820-WiNet series WS5810-WiNet series |
Release 63xx |
WAS6000 series |
Release 63xx |
IE4300-12P-AC & IE4300-12P-PWR IE4300-M series IE4320 series |
Release 63xx |
IE4520 series |
IE4520 series |
S5135S-EI series |
Release 6810 and later versions |
Procedures
# View the current state and statistics of the BGP peers.
<DeviceA> display bgp peer ipv4
BGP local router ID: 1.1.1.1
Local AS number: 100
Total number of peers: 3 Peers in established state: 3
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
10.2.1.2 200 13 16 0 0 00:16:12 Established
10.3.1.2 300 13 16 0 0 00:10:34 Established
10.3.2.2 300 13 16 0 0 00:10:38 Established
# Configure a track item to monitor the state of Ten-GigabitEthernet1/0/1.
<DeviceA> system-view
[DeviceA] track 1 interface ten-gigabitethernet 1/0/1
# Configure a TCL monitoring policy for Device A to automatically detect Ten-GigabitEthernet1/0/1 down events and prevent BGP sessions from being established with Device D and Device E.
[DeviceA] rtm cli-policy test
[DeviceA-rtm-test] event track 1 state negative
[DeviceA-rtm-test] action 0 cli system-view
[DeviceA-rtm-test] action 1 cli bgp 100
[DeviceA-rtm-test] action 2 cli peer 10.3.1.2 ignore
[DeviceA-rtm-test] action 3 cli peer 10.3.2.2 ignore
[DeviceA-rtm-test] user-role network-admin
[DeviceA-rtm-test] commit
[DeviceA-rtm-test] quit
Verifying the configuration
# Disable Ten-GigabitEthernet1/0/1.
[DeviceA] interface ten-gigabitethernet 1/0/1
[DeviceA-Ten-GigabitEthernet1/0/1] shutdown
# View the state and statistics of BGP peers. Verify that the number of BGP peers is 0.
<DeviceA> display bgp peer ipv4
BGP local router ID: 1.1.1.1
Local AS number: 100
Total number of peers: 0 Peers in established state: 0
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
Configuration files
#
rtm cli-policy test
event track 1 state negative
action 0 cli system-view
action 1 cli bgp 100
action 2 cli peer 10.3.1.2 ignore
action 3 cli peer 10.3.2.2 ignore
user-role network-operator
user-role network-admin
#
track 1 interface ten-gigabitethernet 1/0/1
#