No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R009C00 Operation Guide 09

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Adding Devices to eSight

Adding Devices to eSight

Before eSight can monitor and manage quality of service (QoS) of devices, you need to add devices to it.

Process

Step

Description

1. Set protocol parameters on the device: SNMP

SNMP parameters: They are used to add devices to eSight.

For details about how to configure the SNMP protocol on the device, see Configuring the SNMP Protocol on Devices.

2. Run commands on the device: QoS

The QoS commands are used to obtain QoS data of the device.

For details about how to run the QoS commands, see Configuring QoS Commands on the Device.

3. Add devices to eSight.

Select a proper device addition mode based on the site requirements.

For details about how to add devices to eSight, see Adding Devices to eSight.

Configuring QoS Commands on the Device

The QoS commands are used to obtain QoS data on the device for QoS management.

The following uses Huawei S5720-52X-PWR-SI-AC V200R011C10 as an example to describe the configuration. For other device models, see the device configuration manual.

<Device> system-view
[Device] traffic classifier c1 operator and// Create a traffic classifier, and specify that rules under the classifier are in AND relationship. You are advised to configure this command based on the site requirements. 
<Device-classifier-c1> if-match any//Define the matching rule of the traffic classifier c1 to match all data packets. You are advised to configure this command based on the site requirements.
<Device-classifier-c1> quit
[Device] traffic behavior b1//Run the traffic behavior to create traffic behavior.
[Device-behavior-b1] car cir 1000 green pass remark-8021p 7 yellow pass remark-dscp 20 red discard//Configure CAR supervision actions for traffic behavior b1 as follows: commit an information rate of 1000 kbit/s, allow green and yellow packets to pass, reset the 802.1p priority of green packets to 7, reset the DSCP value of yellow packets to 20, and discard red packets. You are advised to configure this command based on the site requirements. 
[Device-behavior-b1] remark dscp 56//Reset the DSCP priority of IP packets to 56. You are advised to configure this command based on the site requirements. 
[Device-behavior-b1] statistic enable//Enable the traffic statistics function in the QoS template.
<Device-behavior-b1> quit
[Device] traffic policy p1//Run the traffic policy command to create a traffic policy.
NOTE:

To make the created traffic policy take effect, you must apply the policy globally, to the interface, or to the VLAN.

  • Applying the traffic policy to an interface
    [Device-trafficpolicy-p1] classifier c1 behavior b1//Configure the required traffic behavior for the specified traffic classifier in the traffic policy, and associate the traffic classifier c1 with traffic behavior b1. 
    <Device-trafficpolicy-p1> quit 
    [Device] interface gigabitethernet 0/0/1
    [Device-GigabitEthernet0/0/1] traffic-policy p1 inbound //Apply the traffic policy p1 at the inbound direction of the GE0/0/1 interface.
    <Device-GigabitEthernet0/0/1> quit
  • Applying the traffic policy to a VLAN
    [Device-trafficpolicy-p1] classifier c1 behavior b1//Configure the required traffic behavior for the specified traffic classifier in the traffic policy, and associate the traffic classifier c1 with traffic behavior b1. 
    [Device-trafficpolicy-p1] quit 
    [Device] vlan 100 
    [Device-vlan100] traffic-policy p1 inbound//Apply the traffic policy p1 at the inbound direction of VLAN 100.
    [Device-vlan100]quit 
  • Applying the traffic policy to an SSID template
    [Device-trafficpolicy-p1] classifier c1 behavior b1//Configure the required traffic behavior for the specified traffic classifier in the traffic policy, and associate the traffic classifier c1 with traffic behavior b1. 
    [Device-trafficpolicy-p1] quit 
    [Device] wlan 
    [Device-wlan-view] ssid-profile name test
    [Device-wlan-ssid-prof-test] traffic-policy p1 inbound//Apply the traffic policy at the inbound direction of the SSID template test. 
    [Device-wlan-ssid-prof-test] quit
    NOTE:

    Only the S5720HI supports this command.

  • Applying the traffic policy to a VLANIF interface
    [Device-trafficpolicy-p1] classifier c1 behavior b1//Configure the required traffic behavior for the specified traffic classifier in the traffic policy, and associate the traffic classifier c1 with traffic behavior b1. 
    [Device-trafficpolicy-p1] quit
    [Device] interface vlanif 100
    [Device-Vlanif100] traffic-policy p1 inbound//Apply the traffic policy at the inbound direction of VLANIF 100.
    [Device-Vlanif100] quit
    NOTE:

    Only the S5720EI, S5720HI, S6720EI, and S6720S-EI support this command.

  • Applying the traffic policy globally
    [Device-trafficpolicy-p1] classifier c1 behavior b1//Configure the required traffic behavior for the specified traffic classifier in the traffic policy, and associate the traffic classifier c1 with traffic behavior b1. 
    [Device-trafficpolicy-p1] quit
    [Device] traffic-policy p1 global inbound//Apply the traffic policy at the global inbound direction.
NOTE:

Dynamically updating the traffic classifiers and traffic behaviors in a traffic policy makes the traffic policy ineffective for a short time.

In a traffic policy, one traffic classifier can be bound to only one traffic behavior. Each traffic policy supports a maximum of 256 pairs of traffic classifiers and traffic behaviors.

After a traffic policy is applied, you cannot directly delete the traffic policy or the traffic classifier and traffic behavior bound to the traffic policy. In addition, you cannot modify the matching order of the rules in the traffic policy. However, you can modify the logic operator of traffic classifiers in the traffic policy, matching rules of the traffic classifier, traffic action in the traffic behavior, and binding between the traffic classifier and traffic behavior.

Download
Updated: 2019-05-17

Document ID: EDOC1100011877

Views: 284654

Downloads: 544

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next