Page 2
All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope.
1 SNMP Configuration........................1 1.1 Introduction to SNMP............................2 1.1.1 SNMP Overview............................2 1.1.2 SNMP Features Supported by the S9300&S9300E..................4 1.2 Configuring a Device to Communicate with an NM Station by Running SNMPv1..........7 1.2.1 Establishing the Configuration Task......................7 1.2.2 Configuring Basic SNMPv1 Functions.....................8 1.2.3 (Optional) Controlling the NM Station's Access to the Device...............10...
Page 6
S9300&S9300E Terabit Routing Switch Configuration Guide - Network Management Contents 2.2 LLDP Feature Supported by the S9300&S9300E....................48 2.3 Configuring LLDP............................51 2.3.1 Establishing the Configuration Task.......................51 2.3.2 Enabling Global LLDP..........................52 2.3.3 (Optional) Disabling LLDP on an Interface....................52 2.3.4 (Optional) Configuring an LLDP Management Address................53 2.3.5 (Optional) Configuring the TLV in the LLDPDU...................54...
Page 7
3.6.9 Example for Configuring the Configuration Synchronization Function for an HGMP Cluster....190 3.6.10 Example for Configuring Security Features for an HGMP Cluster............200 4 NTP Configuration........................211 4.1 Introduction to NTP............................212 4.2 NTP Supported by the S9300&S9300E......................214 4.3 Configuring Basic NTP Functions.........................216 4.3.1 Establishing the Configuration Task.....................216 4.3.2 Configuring the NTP Primary Clock.....................217 4.3.3 Configuring the Time Interval to Update Client Clock.................217...
Page 8
6 NQA Configuration........................257 6.1 Introduction to NQA............................260 6.2 Comparisons Between NQA and Ping......................260 6.3 NQA Server and NQA Clients........................261 6.4 NQA Supported by the S9300&S9300E......................261 6.5 Configuring the ICMP Test..........................262 6.5.1 Establishing the Configuration Task.....................262 6.5.2 Configuring ICMP Test Parameters......................263 6.5.3 Checking the Configuration........................265...
Page 12
6.35.32 Example for Configuring the LSP Trace Test for Checking the CR-LSP Hotstandby Tunnel..494 7 NetStream Configuration......................500 7.1 Overview of NetStream..........................502 7.2 NetStream Features Supported by the S9300&S9300E.................503 7.3 Collecting IPv4 Traffic Statistics........................504 7.3.1 Establishing the Configuration Task.....................504 7.3.2 Configuring the NetStream Function on an Interface................504 7.3.3 (Optional) Configuring the Version of Exported Packets..............505...
Page 14
8.6.2 Examples for Configuring RMON2......................550 9 Traffic Distribution Configuration..................554 9.1 Traffic Distribution Overview........................555 9.2 Traffic Distribution Features Supported by the S9300&S9300E..............555 9.3 Configuring Traffic Distribution Based on the Eth-Trunk................556 9.3.1 Establishing the Configuration Task.....................556 9.3.2 Setting the Load Balancing Mode of an Eth-Trunk................557 9.3.3 (Optional) Configuring Unidirectional Single-fiber Communication...........558...
Page 15
Contents 10.5.1 Example for Capturing Packets......................575 11 sFlow Configuration.......................578 11.1 sFlow Overview............................579 11.2 sFlow Features Supported by the S9300&S9300E..................579 11.3 Configuring sFlow............................580 11.3.1 Establishing the Configuration Task....................580 11.3.2 Configuring sFlow Agent and sFlow Collector Information...............582 11.3.3 Configuring an sFlow Sampling Mode....................583 11.3.4 Checking the Configuration.........................584...
Trap Reports an event to the NM station. 1.1.2 SNMP Features Supported by the S9300&S9300E This section compares SNMP versions in terms of their support for features and usage scenarios. Use it as a reference when you select the SNMP version during network deployment.
Page 24
The parameter securityname identifies the alarm sender, which will help you learn the alarm source. l If the NM station and managed device are both Huawei products, the parameter private- netmanager can be configured to add more information to alarms, such as the alarm type, alarm sequence number, and alarm sending time.
To allow a specified module on the managed device to report alarms to the NM station, follow the procedure described in Configuring the Trap Function. If the NM station and managed device are both Huawei products, follow the procedure described in Enabling the SNMP Extended Error Code Function to allow the device to send more types of error codes.
This section describes how to enable the extended SNMP error code function when both the NM station and managed device are Huawei products. After this function is enabled, more types of error codes are provided to help you locate and rectify faults more quickly and accurately.
Page 32
The parameter securityname identifies the alarm sender, which will help you learn the alarm source. l If the NM station and managed device are both Huawei products, the parameter private- netmanager can be configured to add more information to alarms, such as the alarm type, alarm sequence number, and alarm sending time.
Configuring the Trap FunctionConfiguring the Trap Function. If the NM station and managed device are both Huawei products, follow the procedure described in Enabling the SNMP Extended Error Code Function to allow the device to send more types of error codes.
This section describes how to enable the extended SNMP error code function when both the NM station and managed device are Huawei products. After this function is enabled, more types of error codes are provided to help you locate and rectify faults more quickly and accurately.
Page 41
To enable SNMPv3 to send trap messages, set securityname to an existing user name and ensure that the user has the right to send trap messages. l If the NM station and managed device are both Huawei products, the parameter private- netmanager can be configured to add more information to alarms, such as the alarm type, alarm sequence number, and alarm sending time.
To allow a specified module on the managed device to report alarms to the NM station, follow the procedure described in Configuring the Trap Function. If the NM station and managed device are both Huawei products, follow the procedure described in Enabling the SNMP Extended Error Code Function to allow the device to send more types of error codes.
This section describes how to enable the extended SNMP error code function when both the NM station and managed device are Huawei products. After this function is enabled, more types of error codes are provided to help you locate and rectify faults more quickly and accurately.
The Link Layer Discovery Protocol (LLDP) is a Layer 2 discovery protocol defined in the IEEE 802.1ab standard. 2.2 LLDP Feature Supported by the S9300&S9300E This section describes the usage scenarios of the LLDP feature and TLV types supported by the S9300&S9300E.
LLDP Management Address The LLDP management address (short for management address) is used by the NMS to identify the S9300&S9300E and implement network management. A management address identifies a device. It makes the network topology clear and facilitates network management. The management address is carried in the Management Address Type-Length-Value (TLV) field of an LLDP packet to be transmitted to neighbor devices.
S9300&S9300E. Usage Scenario The LLDP feature of the S9300&S9300E is applicable to three types of networks. The network where an interface has only one neighbor The interfaces between two switches or the interfaces between a switch and a media endpoint (ME) are directly connected, so each interface has only one neighbor.
Page 65
Configuration Guide - Network Management 2 LLDP Configuration TLV Types Supported by the S9300&S9300E Besides the mandatory TLVs Chassis ID TLV, Port ID TLV, Time to Live TLV, and End of LLDPDU, the S9300&S9300E supports the following optional TLVs. Basic TLV Type Description...
If you disable the LLDP-MED TLVs and use the all keyword, the MAC/PHY Configuration/Status TLVs are not disabled automatically. l Only the S9300&S9300ELI S9300&S9300EHI support the EEE TLV. l Only the G24TFA board supports the EEE function. Step 4 Run: lldp dot3-tlv power {802.1ab | 802.3at }...
The system view is displayed. Step 2 Run: snmp-agent trap enable feature-name lldptrap The LLDP trap function is enabled. By default, the LLDP trap function is disabled on the S9300&S9300E. ----End 2.3.8 Checking the Configuration Prerequisites All configurations are complete.
Page 77
Chassis ID :00e0- fc33-0011 System name :SwitchA System description :Quidway Huawei Versatile Routing Platform Software VRP (R) Software, Version 5.110 (S9300 V200R001C00) Copyright (c) 2000-2011 Huawei Technologies Co., System capabilities supported :bridge System capabilities enabled :bridge LLDP Up time :2011/2/13...
Page 78
:HUAWEI, Quidway Series, GigabitEthernet1/0/1 Interface System name :SwitchB System description :Quidway Huawei Versatile Routing Platform Software VRP (R) Software, Version 5.110 (S9300 V200R001C00) Copyright (c) 2000-2011 Huawei Technologies Co., Ltd System capabilities supported :bridge System capabilities enabled :bridge Management address type...
Page 79
MED Device information Device class :Network Connectivity HardwareRev :LE01MCUA VER.A FirmwareRev SoftwareRev :Version 5.110 V200R001C00 SerialNum Manufacturer name :HUAWEI TECH CO., LTD Model name Asset tracking identifier :NA Media policy type :Unknown Unknown Policy :Yes VLAN tagged Media policy VlanID...
Page 82
S9300&S9300E Terabit Routing Switch Configuration Guide - Network Management 2 LLDP Configuration Software VRP (R) Software, Version 5.110 (S9300 V200R001C00) Copyright (c) 2000-2011 Huawei Technologies Co., System capabilities supported :bridge System capabilities enabled :bridge LLDP Up time :2011/2/13 18:31:37 MED system information...
Page 83
:HUAWEI, Quidway Series, GigabitEthernet1/0/1 Interface System name :SwitchB System description :Quidway Huawei Versatile Routing Platform Software VRP (R) Software, Version 5.110 (S9300 V200R001C00) Copyright (c) 2000-2011 Huawei Technologies Co., Ltd System capabilities supported :bridge System capabilities enabled :bridge Management address type...
Page 84
:HUAWEI, Quidway Series, GigabitEthernet1/0/1 Interface System name :SwitchC System description :Quidway Huawei Versatile Routing Platform Software VRP (R) Software, Version 5.110 (S9300 V200R001C00) Copyright (c) 2000-2011 Huawei Technologies Co., Ltd System capabilities supported :bridge System capabilities enabled :bridge Management address type...
Page 85
MED Device information Device class :Network Connectivity HardwareRev :LE02SRUB VER.B FirmwareRev SoftwareRev :Version 5.110 V200R001C00 SerialNum Manufacturer name :HUAWEI TECH CO., LTD Model name Asset tracking identifier :NA Media policy type :Unknown Unknown Policy :Undefined VLAN tagged Media policy VlanID...
Page 88
Chassis ID :00e0- fc33-0011 System name :SwitchA System description :Quidway Huawei Versatile Routing Platform Software VRP (R) Software, Version 5.110 (S9300 V200R001C00) Copyright (c) 2000-2011 Huawei Technologies Co., System capabilities supported :bridge System capabilities enabled :bridge LLDP Up time :2011/4/13...
HGMP Configuration About This Chapter By running the Huawei Group Management Protocol (HGMP), you can appoint a switch as the administrator switch to create a cluster and add a large number of Ethernet switches to the cluster. The administrator is used to perform unified management and configuration over these switches, which simplifies maintenance and engineering.
IP addresses for them one by one. This leads to the waste of IP addresses. The Huawei Group Management Protocol (HGMP) is developed to manage a group of Ethernet switches. By running HGMP, you can appoint a switch as the administrator in a cluster to perform integrated management and configurations over other switches added to the cluster.
Member: member switch 3.2 HGMP Features Supported by the S9300&S9300E This part describes the HGMP features supported by the S9300&S9300E. Neighbor Discovery Protocol (NDP) is used to collect information about the directly connected neighbors, including the device model, software version, hardware version, connection interface, member number, private IP address used for communication within a cluster, and hardware platform.
NOTE Currently, the S9300&S9300E cannot function as a standby switch. An administrator switch is the management device in a cluster. To ensure the communication between devices in and out of the cluster, you need to assign a public IP address to the administrator switch.
Page 104
The cluster function is enabled. By default, the HGMP cluster function is disabled. Creating a cluster A cluster can be created manually or automatically on the S9300&S9300E. NOTE If the administrator switch is rebooted after the HGMP cluster is created, member switches need to be re-added into the cluster.
Page 117
The cluster view is displayed. Run: cluster-packet-extend enable Communication Between Huawei Devices and Non-Huawei Devices is enabled. – To configure the management VLAN for the interface of the administrator switch, you should run the port trunk allow-pass vlan command rather than the port default vlan command if the cluster-packet-extend enable command needs to be used.
Page 124
Create a management VLAN on all devices. Enable NDP and NTDP to ensure that each device can detect the topology structure of the network through NTDP. Choose the administrator switch, and then create a cluster named HUAWEI on the administrator switch.
Page 129
3 HGMP Configuration After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 139
3 HGMP Configuration After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 149
[Administrator-1-cluster] build HUAWEI [HUAWEI_0.Administrator-1-cluster] After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 158
10.0.0.0/8, in which the IP address assigned to the administrator switch is 10.0.0.1/8. [Administrator-1] cluster [Administrator-1-cluster] ip-pool 10.0.0.1 8 # Create a cluster named HUAWEI on the administrator switch. [Administrator-1-cluster] build HUAWEI Issue 01 (2012-03-15) Huawei Proprietary and Confidential...
Page 159
3 HGMP Configuration [HUAWEI_0.Administrator-1-cluster] After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 169
3 HGMP Configuration After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 180
3 HGMP Configuration After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 190
[Administrator-1-cluster] build HUAWEI [HUAWEI_0.Administrator-1-cluster] After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 200
[Administrator-1-cluster] build HUAWEI [HUAWEI_0.Administrator-1-cluster] After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 211
3 HGMP Configuration After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
Page 220
[Administrator-1-cluster] build HUAWEI [HUAWEI_0.Administrator-1-cluster] After the previous configuration, check information about the cluster to which the device belongs. You can find that the device name is changed, the cluster name is HUAWEI, and the management VLAN ID is 10. [HUAWEI_0.Administrator-1-cluster] display cluster Cluster name:"HUAWEI"...
This part describes the application and working principles of NTP. 4.2 NTP Supported by the S9300&S9300E This part describes NTP operating modes supported by the S9300&S9300E. 4.3 Configuring Basic NTP Functions This section describes how to configure basic NTP functions, including the NTP operating modes.
4.2 NTP Supported by the S9300&S9300E This part describes NTP operating modes supported by the S9300&S9300E. The switch supports the following NTP working modes Unicast Client/Server Mode...
The interface on the switch is disabled from receiving NTP packets. ----End 4.3.9 (Optional) Setting the Maximum Number of Dynamic NTP Sessions Context Do as follows on the S9300&S9300E that functions as a client. Procedure Step 1 Run: system-view The system view is displayed.
NTP supports two security mechanisms: access authority and NTP authentication. Access authority Access authority is a type of simple security method provided by the S9300&S9300E to protect local NTP services. The S9300&S9300E provides four access authority levels. When an NTP access request packet reaches the local end, it is matched in an order from the minimum access authority to the maximum access authority.
Page 266
S9300&S9300E. On the S9300&S9300E, run the tracert command. The destination IP address is the IP address of the log host and other parameters adopt the default values. The S9300&S9300E sends a UDP datagram to the log host, with the TTL value being 1 and the destination UDP port number being 33434.
This section describes the execution of the ping and tracert commands. 5.3.1 Establishing the Configuration Task Application Environment The Customer Edge (CE) connected to the S9300&S9300E cannot access the Internet. You need to run the ping and tracert commands to check network connectivity. Pre-configuration Tasks Before performing ping and tracert operations, complete the following tasks: Checking the physical connections between the CE and the S9300&S9300E...
Only some of the parameters are specified in the preceding tracert command. For details on more parameters, refer to the S9300&S9300E Terabit Routing Switch Command Reference. The output of the tracert command displays a list of gateways traversed between the source and the destination hosts.
Debugging affects the performance of the system. After debugging, run the undo debugging all command to disable it immediately. If you run the ping or the tracert command on the two S9300&S9300Es but the ping or tracert operation fails, you can run the following command respectively on each S9300&S9300E to further locate the fault after confirming that the physical link between the two S9300&S9300Es is normal.
The NQA function of the S9300&S9300E is controlled by the license. Generally, the NQA commands can be run on a new S9300&S9300E, but the NQA function cannot take effect. To make the NQA function of an S9300&S9300E effective, contact the Huawei regional office to buy the license.
Page 273
6.14 Configuring the Jitter Test This section describes how to configure a jitter test to check jitter on the network. You can perform a jitter test only when both the client and the server are Huawei devices. 6.15 Configuring the MAC Ping Test This section describes how to perform the MAC ping test with NQA.
This helps them analyze network performance in time. NQA on the S9300&S9300E meets the preceding requirements. NQA measures the performance of each protocol running on the network and helps network...
6.4 NQA Supported by the S9300&S9300E This part describes NQA test types and scheduling modes supported by the S9300&S9300E. Issue 01 (2012-03-15) Huawei Proprietary and Confidential...
6.14 Configuring the Jitter Test This section describes how to configure a jitter test to check jitter on the network. You can perform a jitter test only when both the client and the server are Huawei devices. 6.14.1 Establishing the Configuration Task Before configuring a jitter test, familiarize yourself with the applicable environment, complete the pre-configuration tasks, and obtain the required data.
In the jitter test, you can set the number of packets to be sent consecutively in each test instance. Through this setting, the actual traffic of a kind of packet during a time period can be simulated. The devices at the two ends of the tested link can be both Huawei devices or not. Pre-configuration Tasks Before configuring an ICMP jitter test, configure a reachable route between the NQA client and the server.
Page 347
Step 7 Run: mtrace-last-hop-address ipv4 ip-address The IP address of the last-hop switch is specified. If non-Huawei devices are deployed in the multicast network, this step is mandatory. Step 8 Run: source-address ipv4 ip-address The source IP address of the IGMP Tracert-Request packet is configured. The address must be the address of the local interface.
Page 417
S9300&S9300E Terabit Routing Switch Configuration Guide - Network Management 6 NQA Configuration NOTE For information about clock synchronization, see "NTP" in the S9300&S9300E Terabit Routing Switch Feature Description - Network Management. Figure 6-12 Networking diagram for configuring the Jitter test SwitchA...
Page 423
Step 2 Configure LDP on Switch A, Switch B, and Switch C. (The detailed procedure is not mentioned here.) For the configuration of LDP, refer to the S9300&S9300E Terabit Routing Switch Configuration Guide - MPLS. Step 3 # Configure Switch A.
Page 426
Step 2 Configure LDP on Switch A, Switch B, and Switch C. (The detailed procedure is not mentioned here.) For the configuration of LDP, refer to the S9300&S9300E Terabit Routing Switch Configuration Guide - MPLS. Step 3 Configure Switch A as the NQA client.
Page 429
Step 2 Configure MPLS RSVP-TE on Switch A, Switch B, and Switch C. (The detailed procedure is not mentioned here.) For the configuration of MPLS RSVP-TE, refer to the S9300&S9300E Terabit Routing Switch Configuration Guide - MPLS. Step 3 Set up a TE tunnel from Switch A to Switch C. (The detailed procedure is not mentioned here.) Step 4 Create an NQA test on Switch A.
Page 433
Step 3 Configure a TE tunnel on Switch A to connect Switch C. The configuration details are not mentioned here. For the configuration of MPLS RSVP-TE, refer to the S9300&S9300E Terabit Routing Switch Configuration Guide - MPLS. Step 4 Create an NQA test on Switch A.
Page 460
Step 1 Configure a dynamic single-hop PW. Configure a dynamic single-hop PW on the MPLS backbone network. For the detailed configuration procedure, see "PWE3 Configuration" in the S9300&S9300E Terabit Routing Switch Configuration Guide - VPN. Step 2 Configure a PWE3 Ping test of the single-hop PW.
Page 465
Step 1 Configure a dynamic multi-hop PW. Configure a dynamic multi-hop PW on the MPLS backbone network. For the detailed configuration procedure, see "PWE3 Configuration" in the S9300&S9300E Terabit Routing Switch Configuration Guide - VPN. Step 2 Configure a PWE3 Ping test on a multi-hop PW.
Page 470
Step 1 Configure a dynamic single-hop PW. Configure a dynamic single-hop PW on the MPLS backbone network. For the detailed configuration procedure, see "PWE3 Configuration" in the S9300&S9300E Terabit Routing Switch Configuration Guide - VPN. Step 2 Configure a PWE3 Trace test of the single-hop PW.
Page 475
Step 1 Configure a dynamic multi-hop PW. Configure a dynamic multi-hop PW on the MPLS backbone network. For the detailed configuration procedure, see "PWE3 Configuration" in the S9300&S9300E Terabit Routing Switch Configuration Guide - VPN. Step 2 Configure a PWE3 Trace test of the multi-hop PW.
NQA Server 10.1.1.1/24 10.1.1.2/24 30.1.1.1/24 NOTE For the information about clock synchronization, see "NTP" in the S9300&S9300E Terabit Routing Switch Feature Description - Network Management. Configuration Roadmap The configuration roadmap is as follows: Configure a Jitter test. Configure the NQA thresholds.
Page 503
VPN instances. For configuration details, refer to the chapter "IPv4 Multicast VPN Configuration" in the S9300&S9300E Configuration Guide - IP Multicast. Step 3 Configure identical share-group address, MTI, and switch-address-pool range of Switch-MDT for the same VPN instance on each PE.
Context NOTE After the NetStream function is enabled on an S9300&S9300E, you cannot configure the IP source trail function on this S9300&S9300E. To configure the IP source trail function, you must disable the NetStream function of the S9300&S9300E. Currently, only the enhanced boards support the NetStream function.
Aging depending on the inactive time of the original traffic After the inactive aging time is set, the traffic is aged if the S9300&S9300E does not receive any packet of the traffic in a certain period. Then the statistics collection is ended and the result is sent to the NSC.
By default, the suppression ratio on interfaces is 1000. The suppression ratio is used for packet sampling. After the suppression ratio is set, the S9300&S9300E does not sample the packets that are filtered out in the suppression. Step 5 (Optional) Run: ip netstream sampler fix-packets packet-interval { inbound | outbound } The fixed-packets sampling ratio is set on the interface.
If two aging modes, that is, inactive aging time of the original traffic and the FIN flag of TCP packets, are configured on the S9300&S9300E at the same time, the traffic is aged when one of the two aging conditions is met.
By default, the suppression ratio on interfaces is 1000. The suppression ratio is used for packet sampling. After the suppression ratio is set, the S9300&S9300E does not sample the packets that are filtered out in the suppression. Step 5 (Optional) Run: ipv6 netstream sampler fix-packets packet-interval { inbound | outbound } The fixed-packets sampling ratio is set on the interface.
If two aging modes, that is, inactive aging time of the original traffic and the FIN flag of TCP packets, are configured on the S9300&S9300E at the same time, the traffic is aged when one of the two aging conditions is met.
By default, the suppression ratio on interfaces is 1000. The suppression ratio is used for traffic sampling. After the suppression ratio is set, the S9300&S9300E does not sample the packets that are filtered out in the suppression. Step 5 (Optional) Run: ip netstream sampler fix-packets packet-interval { inbound | outbound } The fixed-packets sampling ratio on the interface is set.
A record is created and the record view is displayed. ----End 7.6.3 Configuring Aggregation Key Words of Records Context Do as follows on the S9300&S9300E where the Flexible NetStream feature needs to be configured. Procedure Step 1 Run: system-view The system view is displayed.
The traffic statistics sent to the NSC contain the indexes of the inbound interface and outbound interface on the S9300&S9300E. ----End 7.6.5 Configuring NetStream and Setting the Packet Sampling Ratio Context Do as follows on the S9300&S9300E where the Flexible NetStream feature needs to be configured. Procedure Step 1 Run: system-view The system view is displayed.
Ensuring that interfaces work normally Setting the IP address of the interface Enabling the NetStream function on the S9300&S9300E Setting the version of the exported packets of NetStream original traffic to v9 Setting the version of the enabled aggregation traffic to v9 Data Preparation To complete the configuration, you need the following data.
This part describes working principles of and differences between RMON and RMON2. 8.2 RMON and RMON2 Suported by the S9300&S9300E This part describes the support for RMON and RMON2 on the S9300&S9300E. 8.3 Configuring RMON This section describes how to monitor the network status and traffic through RMON.
NM Station collects only information on four groups (alarm, event, history, and statistics) and not the complete information on the RMON MIB. Currently, the S9300&S9300E implements the monitoring and statistics collection function only on the Ethernet interfaces of network devices.
The S9300&S9300E does not apply this mechanism because it will not generate the alarms for a long period. For the S9300&S9300E, the alarms are re-generated if the smapling value turns to the noraml threshold.
Page 550
The RMON Performance-MIB has one table: prialarmTable. In the S9300&S9300E, to save system resources, each entry is given a specific time span. The time span indicates the period for an entry to keep the invalid state. The entry is deleted when the time span goes down to 0.
The short sampling interval enables a monitor to probe the sudden changes of traffic modes, and the long sampling interval is applicable if the interface status is relatively stable. Currently, the S9300&S9300E reserves up to 10 pieces of the latest records for each history control entry.
When an RMON fault occurs, run the following debugging command in the user view to locate the fault. For the description about the debugging commands, refer to the S9300&S9300E Terabit Routing Switch Debugging Reference. Perform the configuration in the user view.
This section describes basic concepts of traffic distribution. 9.2 Traffic Distribution Features Supported by the S9300&S9300E This section describes the traffic distribution features supported by the S9300&S9300E. 9.3 Configuring Traffic Distribution Based on the Eth-Trunk This section describes how to configure traffic distribution based on the Eth-Trunk.
9.2 Traffic Distribution Features Supported by the S9300&S9300E This section describes the traffic distribution features supported by the S9300&S9300E. During traffic distribution, the concealment and security of the traffic distribution device on the network must be ensured. Therefore, the traffic distribution device needs to provide the following...
The S9300&S9300E provides easy query of the outbound interface of traffic. According to the entered quintuple information, the S9300&S9300E obtains the outbound interface of traffic matching the quintuple information.
Configuration Guide - Network Management 9 Traffic Distribution Configuration Procedure Configure static routes. For details, see the IP Static Route Configuration in the S9300&S9300E Terabit Routing Switch Configuration Guide - IP Routing. ----End 9.4.3 Configuring ECMP Context Because of high link bandwidth on the backbone network, a packet analysis device cannot analyze or process a large amount of traffic.
This will help you complete the configuration task quickly and accurately. 10.4 Capturing Packets Sent to the CPU Before capturing packets sent to the CPU on an S9300&S9300E switch, familiarize yourself with the applicable environment, complete the pre-configuration tasks, and obtain the data required for configuration.
S9300&S9300E Capturing Service Packets When a fault occurs on an S9300&S9300E switch, you can configure the packet capture function. The switch then captures packets matching the specified rules, and sends captured packet information to a TFTP or FTP server or saves information in the CF card for you to analyze.
The system limits the rate of captured packets. The default rate limit is 64 kbit/s. If the rate of packets exceeds the limit, some packets may be discarded. If captured packet information fails to be sent to the TFTP or FTP server, the S9300&S9300E switch saves captured packet information locally.
Page 589
Pre-configuration Tasks Before capturing packets sent to the CPU, complete the following tasks: Ensuring that routes are reachable between the S9300&S9300E and the FTP or TFTP server Data Preparation To packets sent to the CPU, you need the following data.
S9300&S9300E Terabit Routing Switch Configuration Guide - Network Management 10 Packet Capture Configuration If captured packet information fails to be sent to the TFTP or FTP server, the S9300&S9300E switch saves captured packet information locally. ----End 10.5 Configuration Examples This section provides an example of packet capture configuration.
11.1 sFlow Overview This section describes sFlow concepts and process. 11.2 sFlow Features Supported by the S9300&S9300E This section describes the sFlow features supported by the S9300&S9300E. 11.3 Configuring sFlow This section describes how to configure sFlow. 11.4 Configuration Examples The section provides an sFlow configuration example.
0 to N. When the random value is smaller than the threshold, the sFlow agent samples packets. The actual sampling ratio is n/(N+1). The S9300&S9300E supports only random sampling. In flow sampling, an sFlow agent can sample packets in one direction or in both directions on an interface.