HP 6125G Configuration Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Switch
  5. 6125G
  6. Configuration manual

HP 6125G Configuration Manual

Network management and monitoring configuration guide
Hide thumbs Also See for 6125G:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Installation Manual
HP 6125 Blade Switch Series
Network Management and Monitoring

Configuration Guide

Part number: 5998-3162
Software version: Release 2103
Document version: 6W100-20120907

Advertisement

Table of Contents
loading

Related Manuals for HP 6125G

Summary of Contents for HP 6125G

  • Page 1: Configuration Guide

    HP 6125 Blade Switch Series Network Management and Monitoring Configuration Guide Part number: 5998-3162 Software version: Release 2103 Document version: 6W100-20120907...
  • Page 2 HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

  • Page 3: Table Of Contents

    Contents Using ping, tracert, and system debugging ··············································································································· 1   Ping ····················································································································································································· 1   Using a ping command to test network connectivity ···························································································· 1   Ping example ···························································································································································· 1   Tracert ················································································································································································ 3   Prerequisites ······························································································································································ 4   Using a tracert command to identify failed or all nodes in a path ····································································· 5  ...
  • Page 4 Default output rules of system information ·········································································································· 36   System information format ···································································································································· 37   Information center configuration task list ····················································································································· 40   Outputting system information to the console ············································································································· 40   Configuring a system information output rule for the console ·········································································· 40  ...
  • Page 5 History group configuration example ·························································································································· 71   Alarm group configuration example ···························································································································· 73   Configuring port mirroring ········································································································································ 76   Introduction to port mirroring ········································································································································ 76   Terminologies of port mirroring ··························································································································· 76   Port mirroring classification and implementation ······························································································· 77  ...
  • Page 6 Configuring voice tests ······································································································································· 109   Configuring DLSw tests ······································································································································· 111   Configuring the collaboration function ······················································································································ 112   Configuring threshold monitoring ······························································································································· 113   Configuration prerequisites ································································································································ 113   Configuration guidelines ···································································································································· 113   Configuration procedure ···································································································································· 113   Configuring the NQA statistics collection function ···································································································...
  • Page 7 Index ········································································································································································ 149  ...

  • Page 8: Using Ping, Tracert, And System Debugging

    Using ping, tracert, and system debugging Use the ping, tracert, and system debugging utilities to test network connectivity and identify network problems. Ping The ping utility sends ICMP echo requests (ECHO-REQUEST) to the destination device. Upon receiving the requests, the destination device responds with ICMP echo replies (ECHO-REPLY) to the source device. The source device outputs statistics about the ping operation, including the number of packets sent, number of echo replies received, and the round-trip time.
  • Page 9 Figure 1 Network diagram Test procedure # Use the ping command on Device A to test connectivity to Device C. <DeviceA> ping 1.1.2.2 PING 1.1.2.2: 56 data bytes, press CTRL_C to break Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=205 ms Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms...

  • Page 10: Tracert

    1.1.1.1 Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms Record Route: 1.1.2.1 1.1.2.2 1.1.1.2 1.1.1.1 Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms Record Route: 1.1.2.1 1.1.2.2 1.1.1.2 1.1.1.1 --- 1.1.2.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/11/53 ms The test procedure with the ping –r command (see...

  • Page 11: Prerequisites

    Figure 2 Network diagram Tracert uses received ICMP error messages to get the IP addresses of devices. As shown in Figure tracert works as follows: The source device (Device A) sends a UDP packet with a TTL value of 1 to the destination device (Device D).

  • Page 12: Using A Tracert Command To Identify Failed Or All Nodes In A Path

    icmp-extensions compliant command on the devices. For more information about this command, see Layer 3—IP Services Command Reference. For an IPv6 network: Enable sending of ICMPv6 timeout packets on the intermediate devices (the devices between the • source and destination devices). If the intermediate devices are HP devices, execute the ipv6 hoplimit-expires enable command on the devices.

  • Page 13: Debugging A Feature Module

    Figure 3 Relationship between the protocol and screen output switch Debugging a feature module Output of debugging commands is memory intensive. To guarantee system performance, enable debugging only for modules that are in an exceptional condition. When debugging is complete, use the undo debugging all command to disable all the debugging functions.

  • Page 14: Ping And Tracert Example

    Ping and tracert example Network requirements As shown in Figure 4, Device A failed to Telnet Device C. Determine whether Device A and Device C can reach each other. If they cannot reach each other, locate the failed nodes in the network. Figure 4 Network diagram Test procedure Use the ping command to test connectivity between Device A and Device C.
  • Page 15 Use the debugging ip icmp command on Device A and Device C to verify that they can send and receive the specific ICMP packets, or use the display ip routing-table command to verify the availability of active routes between Device A and Device C.

  • Page 16: Configuring Ntp

    Configuring NTP Overview NTP is typically used in large networks to dynamically synchronize time among network devices. It guarantees higher clock accuracy than manual system clock setting. In a small network that does not require high clock accuracy, you can keep time synchronized among devices by changing their system clocks one by one.

  • Page 17: Ntp Message Format

    Prior to system clock synchronization between Device A and Device B, the clock of Device A is set • to 10:00:00 am while that of Device B is set to 1 1:00:00 am. Device B is used as the NTP time server, so Device A synchronizes to Device B. •...
  • Page 18 used in environments where network management is needed. Because NTP control messages are not essential for clock synchronization, they are not described in this document. A clock synchronization message is encapsulated in a UDP message in the format shown in Figure Figure 6 Clock synchronization message format The main fields are described as follows:...

  • Page 19: Operation Modes

    Root Delay—Roundtrip delay to the primary reference source. • • Root Dispersion—The maximum error of the local clock relative to the primary reference source. Reference Identifier—Identifier of the particular reference source. • Reference Timestamp—The local time at which the local clock was last set or corrected. •...
  • Page 20 Symmetric peers mode Figure 8 Symmetric peers mode In symmetric peers mode, devices that operate in symmetric active mode and symmetric passive mode exchange NTP messages with the Mode field 3 (client mode) and 4 (server mode). Then the device that operates in symmetric active mode periodically sends clock synchronization messages, with the Mode field in the messages set to 1 (symmetric active).

  • Page 21: Ntp Configuration Task List

    Multicast mode Figure 10 Multicast mode In multicast mode, a server periodically sends clock synchronization messages to the user-configured multicast address, or, if no multicast address is configured, to the default NTP multicast address 224.0.1.1, with the Mode field in the messages set to 5 (multicast mode). Clients listen to the multicast messages from servers.

  • Page 22: Configuring The Client/Server Mode

    Configuring the client/server mode For devices operating in client/server mode, make configurations on the clients. If you specify the source interface for NTP messages by specifying the source interface source-interface option, NTP uses the primary IP address of the specified interface as the source IP address of the NTP messages.

  • Page 23: Configuring The Broadcast Mode

    Step Command Remarks By default, no symmetric-passive peer is specified. The ip-address argument must be a unicast address, rather than a broadcast address, a multicast address, or the IP address of the ntp-service unicast-peer local clock. [ vpn-instance vpn-instance-name ] { ip-address | peer-name } After you specify the source Specify a symmetric-passive...

  • Page 24: Configuring The Multicast Mode

    Step Command Remarks A broadcast server can Configure the device to ntp-service broadcast-server synchronize broadcast clients only operate in NTP broadcast [ authentication-keyid keyid | when its clock has been server mode. version number ] * synchronized. Configuring the multicast mode The multicast server periodically sends NTP multicast messages to multicast clients, which send replies after receiving the messages and synchronize their local clocks.

  • Page 25: Disabling An Interface From Receiving Ntp Messages

    When the device responds to an NTP request received, the source IP address of the NTP response is always the destination IP address of the NTP request. Configuration guidelines • The source interface for NTP unicast messages is the interface specified in the ntp-service unicast-server or ntp-service unicast-peer command.

  • Page 26: Configuring The Dscp Value For Ntp Messages

    Symmetric active/passive mode—After you specify a symmetric-passive peer on a symmetric active • peer, static associations are created on the symmetric-active peer, and dynamic associations are created on the symmetric-passive peer. • Broadcast or multicast mode—Static associations are created on the server, and dynamic associations are created on the client.

  • Page 27: Configuration Prerequisites

    Configuration prerequisites Before you configure the NTP service access-control right to the local device, create and configure an ACL associated with the access-control right. For more information about ACLs, see ACL and QoS Configuration Guide. Configuration procedure To configure the NTP service access-control right to the local device: Step Command Remarks...

  • Page 28: Displaying And Maintaining Ntp

    Step Command Remarks By default, NTP authentication is Enable NTP authentication. ntp-service authentication enable disabled. By default, no NTP authentication ntp-service authentication-keyid key is configured. Configure an NTP keyid authentication-mode md5 authentication key. Configure the same authentication [ cipher | simple ] value key on the client and server.

  • Page 29: Ntp Configuration Examples

    Task Command Remarks display ntp-service sessions Display information about [ verbose ] [ | { begin | exclude | Available in any view NTP sessions. include } regular-expression ] Display brief information display ntp-service trace [ | { begin | about the NTP servers from the exclude | include } Available in any view...

  • Page 30: Configuring The Ntp Symmetric Mode

    Clock stratum: 3 Reference clock ID: 1.0.1.11 Nominal frequency: 64.0000 Hz Actual frequency: 64.0000 Hz Clock precision: 2^7 Clock offset: 0.0000 ms Root delay: 31.00 ms Root dispersion: 1.05 ms Peer dispersion: 7.81 ms Reference time: 14:53:27.371 UTC Sep 19 2005 (C6D94F67.5EF9DB22) The output shows that Device B has synchronized to Device A because it has a higher stratum than Device A.
  • Page 31 <DeviceB> system-view [DeviceB] ntp-service unicast-server 3.0.1.31 Display the NTP status of Device B after clock synchronization. [DeviceB] display ntp-service status Clock status: synchronized Clock stratum: 3 Reference clock ID: 3.0.1.31 Nominal frequency: 100.0000 Hz Actual frequency: 100.0000 Hz Clock precision: 2^18 Clock offset: -21.1982 ms Root delay: 15.00 ms Root dispersion: 775.15 ms...

  • Page 32: Configuring Ntp Broadcast Mode

    Configuring NTP broadcast mode Network requirements • As shown in Figure 13, configure Switch C as a reference source, with the stratum level 2. Configure Switch C to operate in broadcast server mode and send broadcast messages from • VLAN-interface 2. •...

  • Page 33: Configuring Ntp Multicast Mode

    Clock status: synchronized Clock stratum: 3 Reference clock ID: 3.0.1.31 Nominal frequency: 64.0000 Hz Actual frequency: 64.0000 Hz Clock precision: 2^7 Clock offset: 0.0000 ms Root delay: 31.00 ms Root dispersion: 8.31 ms Peer dispersion: 34.30 ms Reference time: 16:01:51.713 UTC Sep 19 2005 (C6D95F6F.B6872B02) The output shows that Switch A has synchronized to Switch C because it has a higher stratum than Switch C.
  • Page 34 Configuration procedure Set the IP address for each interface as shown in Figure 14. (Details not shown.) Configure Device C: # Configure Device C to operate in multicast server mode and send multicast messages through VLAN-interface 2. [DeviceC] interface vlan-interface 2 [DeviceC-Vlan-interface2] ntp-service multicast-server Configure Device D: # Configure Device D to operate in multicast client mode and receive multicast messages on...

  • Page 35: Configuring Ntp Client/Server Mode With Authentication

    [DeviceB] interface vlan-interface 2 [DeviceB-Vlan-interface2] pim dm [DeviceB-Vlan-interface2] quit [DeviceB] vlan 3 [DeviceB-vlan3] port gigabitethernet 1/0/1 [DeviceB-vlan3] quit [DeviceB] interface vlan-interface 3 [DeviceB-Vlan-interface3] igmp enable [DeviceB-Vlan-interface3] igmp static-group 224.0.1.1 [DeviceB-Vlan-interface3] quit [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] igmp-snooping static-group 224.0.1.1 vlan 3 Configure Device A: <DeviceA>...
  • Page 36 Enable NTP authentication on both Device A and Device B. • Figure 15 Network diagram Configuration procedure Set the IP address for each interface as shown in Figure 15. (Details not shown.) Configure Device B: <DeviceB> system-view # Enable NTP authentication on Device B. [DeviceB] ntp-service authentication enable # Set an authentication key.

  • Page 37: Configuring Ntp Broadcast Mode With Authentication

    ************************************************************************** [12345] 1.0.1.11 127.127.1.0 -75.5 31.0 16.5 note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured Total associations : The output shows that an association has been set up Device B and Device A. Configuring NTP broadcast mode with authentication Network requirements •...
  • Page 38 # Configure Device B to operate in broadcast client mode and receive NTP broadcast messages on VLAN-interface 2. [DeviceB] interface vlan-interface 2 [DeviceB-Vlan-interface2] ntp-service broadcast-client Configure Device C: # Configure Device C to operate in NTP broadcast server mode and use VLAN-interface 2 to send NTP broadcast packets.
  • Page 39 The output shows that NTP authentication is enabled on Device B, but not enabled on Device C. Therefore, Device B cannot synchronize to Device C. # Enable NTP authentication Device C. Configure an NTP authentication key, with the key ID 88 and key value 123456, and specify the key as a trusted key.
  • Page 40 The output shows that configuring NTP authentication on Device C does not affect Device A and Device A still synchronizes to Device C.

  • Page 41: Configuring The Information Center

    Configuring the information center This chapter describes how to configure the information center. Overview The information center collects and classifies system information as follows: Receives system information including log, trap, and debugging information from source modules. • • Outputs the information to different information channels, according to output rules. Outputs information to different destinations, based on channel-to-destination associations.

  • Page 42: Classification Of System Information

    Classification of system information System information falls into the following types: Log information • Trap information • Debugging information • System information levels The system information is classified into eight severity levels, from 0 through 7 in descending order. The device outputs the system information with a severity level that is higher than or equal to the specified level.

  • Page 43: Outputting System Information By Source Module

    Information Default channel Default output Description channel number name destination Receives trap information, a buffer inside the trapbuffer Trap buffer device for recording information. Receives log information, a buffer inside the logbuffer Log buffer device for recording information. snmpagent SNMP module Receives trap information.

  • Page 44: System Information Format

    TRAP DEBUG Output Modules Enabled/ Enabled/ Enabled/ destination allowed Severity Severity Severity disabled disabled disabled default (all Informa- Log buffer Enabled Disabled Debug Disabled Debug modules) tional SNMP default (all Informatio Disabled Debug Enabled Disabled Debug module modules) default (all Enabled Debug Enabled...
  • Page 45 PRI (priority) The priority is calculated by using this formula: facility*8+level, where: • facility is the facility name, ranging from local0 to local7 (16 to 23 in decimal integers) and defaults to local7. It can be configured with info-center loghost. It is used to identify different log sources on the log host, and to query and filter logs from specific log sources.
  • Page 46 Sysname (host name or host IP address) If the system information that is sent to a log host is in the UNICOM format, and the info-center • loghost source command is configured, or vpn-instance vpn-instance-name is provided in the info-center loghost command, the field is displayed as the IP address of the device that generates the system information.

  • Page 47: Information Center Configuration Task List

    IP address of the log sender • content This field provides the content of the system information. Information center configuration task list Task Remarks Outputting system information to the console Optional Outputting system information to the monitor terminal Optional Outputting system information to a log host Optional Outputting system information to the trap buffer Optional...

  • Page 48: Enabling System Information Output To The Console

    Step Command Remarks Optional. Configure the timestamp info-center timestamp { debugging By default, the timestamp format for format. | log | trap } { boot | date | none } log, trap and debugging information is date. Enabling system information output to the console To enable the display of system information on the console in user view: Step Command...

  • Page 49: Enabling System Information Output To The Monitor Terminal

    Step Command Remarks info-center source { module-name | Configure a system default } channel { channel-number Optional. information output | channel-name } [ debug { level "Default output rules of system rule for the monitor severity | state state } * | log { level information."...

  • Page 50: Outputting System Information To The Trap Buffer

    Step Command Remarks Optional. Specify the source IP By default, the source IP address of info-center loghost source address for the log output log information is the primary interface-type interface-number information. IP address of the matching route's egress interface. Configure the format of Optional.

  • Page 51: Outputting System Information To The Log Buffer

    Step Command Remarks Optional. Configure the timestamp info-center timestamp { debugging | The time stamp format for system format. log | trap } { boot | date | none } information is date by default. Outputting system information to the log buffer The log buffer only receives log information, and discards trap and debug information.

  • Page 52: Outputting System Information To The Web Interface

    Step Command Remarks Optional. Enable the information info-center enable center. Enabled by default. Optional. Name the channel with info-center channel channel-number a specified channel Table 2 for default channel name channel-name number. names. Configure the channel Optional. through which system info-center snmp channel By default, system information is information can be...

  • Page 53: Configuring Synchronous Information Output

    Step Command Remarks info-center source { module-name | Configure a system default } channel { channel-number | Optional. formation output channel-name } [ debug { level severity | "Default output rules of system rule for the Web state state }* | log { level severity | state information."...

  • Page 54: Displaying And Maintaining Information Center

    Step Command Remarks Enter Layer 2 Ethernet interface interface-type interface view, or VLAN interface-number interface view. By default, all interfaces generate Disable the interface from link up and link down logging generating link up or link undo enable log updown information when the state down logging information.
  • Page 55 Configuration procedure Before the configuration, make sure that the device and the log host can reach each other. Configure the device: # Enable the information center. <Sysname> system-view [Sysname] info-center enable # Specify the host 1.2.0.1/16 as the log host. Use channel loghost to output log information (optional, loghost by default), and use local4 as the logging facility.

  • Page 56: Outputting Log Information To A Linux Log Host

    # kill -HUP 147 # syslogd -r & Now, the system can record log information into the log file. Outputting log information to a Linux log host Network requirements Configure the device to send log information that has a severity level of at least informational to the Linux log host at 1.2.0.1/16.

  • Page 57: Outputting Log Information To The Console

    In this configuration, local5 is the name of the logging facility that the log host uses to receive logs. The information level is info. The Linux system records the log information that has a severity level of at least informational to the file /var/log/Device/info.log. NOTE: Be aware of the following issues while editing the file /etc/syslog.conf: Comments must be on a separate line and must begin with a pound sign (#).
  • Page 58 # Configure an output rule to output to the console ARP and IP log information that has a severity level of at least informational. (The source modules that are allowed to output information depend on the switch model.) [Sysname] info-center source arp channel console log level informational state on [Sysname] info-center source ip channel console log level informational state on [Sysname] quit # Enable the display of log information on a terminal.

  • Page 59: Configuring Snmp

    Configuring SNMP This chapter provides an overview of the Simple Network Management Protocol (SNMP) and guides you through the configuration procedure. Overview SNMP is an Internet standard protocol widely used for a management station to access and operate the devices on a network, regardless of their vendors, physical characteristics and interconnect technologies. SNMP enables network administrators to read and set the variables on managed devices for state monitoring, troubleshooting, statistics collection, and other management purposes.

  • Page 60: Snmp Operations

    A MIB view represents a set of MIB objects (or MIB object hierarchies) with certain access privilege and is identified by a view name. The MIB objects included in the MIB view are accessible while those excluded from the MIB view are inaccessible. A MIB view can have multiple view records each identified by a view-name oid-tree pair.
  • Page 61 Step Command Remarks Enter system view. system-view Optional. By default, the SNMP agent is disabled. You can also enable the SNMP Enable the SNMP agent. snmp-agent agent by using any command that begins with snmp-agent except the snmp-agent calculate-password and snmp-agent ifmib long-ifindex enable commands.

  • Page 62: Configuring Snmpv1 Or Snmpv2C Basic Parameters

    Step Command Remarks snmp-agent usm-user v3 user-name group-name [ [ cipher ] authentication-mode { md5 | sha } Add a user to the SNMPv3 auth-password [ privacy-mode group. { 3des | aes128 | des56 } priv-password ] ] [ acl acl-number | acl ipv6 ipv6-acl-number ] * Configure the maximum Optional.
  • Page 63 Step Command Remarks Optional. By default, the MIB view ViewDefault is predefined and its OID is 1. Each view-name oid-tree pair represents a view record. If you Create or update a snmp-agent mib-view { excluded | included } specify the same record with MIB view.

  • Page 64: Switching The Nm-Specific Interface Index Format

    Switching the NM-specific interface index format A network management (NM)-specific ifindex identifies an interface and is provided by the SNMP managed device to the NMS. A network management-specific ifindex takes one of the following two formats: 16-bit NM-specific ifindex—The system dynamically assigns 16-bit NM-specific ifindex values to •...

  • Page 65: Configuring Snmp Logging

    Step Command Remarks Switch the format of an Optional. undo snmp-agent ifmib NM-specific ifindex from By default, an NM-specific ifindex long-ifindex enable 32-bit to 16-bit. is in 16-bit format. Configuring SNMP logging IMPORTANT: Disable SNMP logging in normal cases to prevent a large amount of SNMP logs from decreasing device performance.

  • Page 66: Configuring The Snmp Agent To Send Traps To A Host

    To generate linkUp or linkDown traps when the link state of an interface changes, you must enable the linkUp or linkDown trap function globally by using the snmp-agent trap enable [ standard [ linkdown | linkup ] * ] command and on the interface by using the enable snmp trap updown command. After you enable a trap function for a module, whether the module generates traps also depends on the configuration of the module.

  • Page 67: Displaying And Maintaining Snmp

    Step Command Remarks snmp-agent target-host trap address udp-domain { ip-address | ipv6 ipv6-address } [ udp-port If the trap destination is a host, the port-number ] [ dscp dscp-value ] Configure a target host. ip-address argument must be the IP [ vpn-instance vpn-instance-name ] address of the host.

  • Page 68: Snmp Configuration Examples

    Task Command Remarks Display basic information about display snmp-agent trap queue [ | { begin | Available in any view the trap queue. exclude | include } regular-expression ] Display the modules that can send display snmp-agent trap-list [ | { begin | traps and their trap status (enable Available in any view exclude | include } regular-expression ]...

  • Page 69: Snmpv3 Configuration Example

    # Enable SNMP traps, set the NMS at 1.1.1.2 as an SNMP trap destination, and use public as the community name. (To make sure the NMS can receive traps, specify the same SNMP version in the snmp-agent target-host command as is configured on the NMS.) [Agent] snmp-agent trap enable [Agent] snmp-agent target-host trap address udp-domain 1.1.1.2 params securityname public v1...
  • Page 70 Figure 25 Network diagram Configuration procedure Configure the agent: # Configure the IP address of the agent and make sure the agent and the NMS can reach each other. (Details not shown.) # Assign the NMS read and write access to the objects under the snmp node (OID 1.3.6.1.2.1.11), and deny its access to any other MIB object.

  • Page 71: Snmp Logging Configuration Example

    Request binding: 1: 1.3.6.1.2.1.11.29.0 Response binding: 1: Oid=snmpOutTraps.0 Syntax=CNTR32 Value=18 Get finished # Try to get the device name from the agent. The get attempt fails because the NMS has no access right to the node. Send request to 1.1.1.1/161 ... Protocol version: SNMPv3 Operation: Get Request binding:...
  • Page 72 # Enable displaying log messages on the configuration terminal. (This function is enabled by default. Skip this step if you are using the default.) <Agent> terminal monitor <Agent> terminal logging # Enable the information center to output system information with severity level equal to or higher than informational to the console port.

  • Page 73: Configuring Rmon

    Configuring RMON This chapter describes how to configure RMON. Overview Remote Monitoring (RMON) is an enhancement to SNMP for remote device management and traffic monitoring. An RMON monitor, typically the RMON agent embedded in a network device, periodically or continuously collects traffic statistics for the network attached to a port, and when a statistic crosses a threshold, logs the crossing event and sends a trap to the management station.

  • Page 74: Alarm Group

    History group The history group defines that the system periodically collects traffic statistics on interfaces and saves the statistics in the history record table (ethernetHistoryTable). The statistics include bandwidth utilization, number of error packets, and total number of packets. The history statistics table record traffic statistics collected for each sampling interval. The sampling interval is user-configurable.

  • Page 75: Configuring The Rmon Statistics Function

    Private alarm group The private alarm group calculates the values of alarm variables and compares the results with the defined threshold for a more comprehensive alarming function. The system handles the private alarm entry (as defined by the user) in the following ways: Periodically samples the private alarm variables defined in the private alarm formula.

  • Page 76: Configuring The Rmon Alarm Function

    You can configure multiple history control entries for one interface, but must make sure their entry • numbers and sampling intervals are different. The device supports up to 100 history control entries. • You can successfully create a history control entry, even if the specified bucket size exceeds the •...

  • Page 77: Displaying And Maintaining Rmon

    Step Command Remarks • Create an entry in the alarm table: rmon alarm entry-number alarm-variable sampling-interval { absolute | delta } rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 [ owner text ] Create an entry in the Use at least one alarm table or private •...

  • Page 78: Ethernet Statistics Group Configuration Example

    Ethernet statistics group configuration example Network requirements Configure the RMON statistics group on the RMON agent in Figure 28 to gather cumulative traffic statistics for GigabitEthernet 1/0/1. Figure 28 Network diagram Configuration procedure # Configure the RMON statistics group on the RMON agent to gather statistics for GigabitEthernet 1/0/1.
  • Page 79 Figure 29 Network diagram Configuration procedure # Configure the RMON history group on the RMON agent to gather traffic statistics every one minute for GigabitEthernet 1/0/1. Retain up to eight records for the interface in the history statistics table. <Sysname> system-view [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] rmon history 1 buckets 8 interval 60 owner user1 # Display the history data collected for GigabitEthernet 1/0/1.

  • Page 80: Alarm Group Configuration Example

    fragments , jabbers collisions , utilization Sampled values of record 5 : dropevents , octets : 898 packets , broadcast packets multicast packets : 6 , CRC alignment errors : 0 undersize packets : 0 , oversize packets fragments , jabbers collisions , utilization Sampled values of record 6 :...
  • Page 81 Figure 30 Network diagram Configuration procedure # Configure the SNMP agent with the same SNMP settings as the NMS at 1.1.1.2. This example uses SNMPv1, read community public, and write community private. <Sysname> system-view [Sysname] snmp-agent [Sysname] snmp-agent community read public [Sysname] snmp-agent community write private [Sysname] snmp-agent sys-info version v1 [Sysname] snmp-agent trap enable...
  • Page 82 etherStatsUndersizePkts , etherStatsOversizePkts etherStatsFragments , etherStatsJabbers etherStatsCRCAlignErrors : 0 , etherStatsCollisions etherStatsDropEvents (insufficient resources): 0 Packets received according to length: 65-127 : 413 128-255 : 35 256-511: 0 512-1023: 0 1024-1518: 0 # Query alarm events on the NMS. (Details not shown.) On the RMON agent, alarm event messages are displayed when events occur.

  • Page 83: Configuring Port Mirroring

    Configuring port mirroring Introduction to port mirroring Port mirroring is the process of copying the packets passing through a port to the monitor port connecting to a monitoring device for packet analysis. Terminologies of port mirroring Mirroring source The mirroring source can be one or more monitored ports. Packets (called "mirrored packets") passing through them are copied to a port connecting to a monitoring device for packet analysis.

  • Page 84: Port Mirroring Classification And Implementation

    Port mirroring classification and implementation According to the locations of the mirroring source and the mirroring destination, port mirroring falls into local port mirroring and remote port mirroring. Local port mirroring In local port mirroring, the mirroring source and the mirroring destination are on the same device. A mirroring group that contains the mirroring source and the mirroring destination on the device is called a "local mirroring group".
  • Page 85 Figure 32 Layer 2 remote port mirroring implementation On the network shown in Figure The source device does the following: Copies the packets received on the source port GigabitEthernet 1/0/1 to the egress port GigabitEthernet 1/0/2. Forwards the packets to the intermediate device, which then broadcasts the packets in the remote probe VLAN.

  • Page 86: Configuring Local Port Mirroring

    Configuring local port mirroring Local port mirroring configuration task list Configure a local mirroring group and then configure one or more source ports and a monitor port for the local mirroring group. Complete these tasks to configure local port mirroring: Task Remarks Creating a local mirroring group...

  • Page 87: Configuring The Monitor Port For The Local Mirroring Group

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number [ mirroring-group group-id ] By default, a port does not serve as a Configure the current mirroring-port { both | inbound | source port for any local mirroring port as a source port.

  • Page 88: Configuring Layer 2 Remote Port Mirroring

    Configuring Layer 2 remote port mirroring Layer 2 remote port mirroring configuration task list Configuring Layer 2 remote port mirroring is to configure remote mirroring groups. To do that, configure the remote source group on the source device and configure the cooperating remote destination group on the destination device.
  • Page 89 Configuring source ports for the remote source group If you use system view, you can use a list to configure multiple source ports for a mirroring group at one time. If you use interface view, you can assign only the current port to the group as a source port, so you must repeat the step for each additional port.

  • Page 90: Configuring A Remote Destination Group (On The Destination Device)

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, a port does not serve as the Configure the current port as mirroring-group group-id egress port for any remote source the egress port. monitor-egress group. NOTE: A mirroring group contains only one egress port.
  • Page 91 Step Command Remarks Enter system view. system-view By default, no remote Create a remote destination mirroring-group group-id destination group exists on a group. remote-destination device. Configuring the monitor port for the remote destination group You can configure the monitor port for a mirroring group in system view, or assign the current port to a mirroring group as the monitor port in interface view.

  • Page 92: Displaying And Maintaining Port Mirroring

    When you remove the configuration of a remote probe VLAN, an active mirroring group becomes inactive. Configuration procedure: Step Command Remarks Enter system view. system-view Configure the By default, no remote probe VLAN is mirroring-group group-id remote probe configured for a remote destination remote-probe vlan rprobe-vlan-id VLAN.
  • Page 93 Configure local port mirroring in source port mode to enable the server to monitor the bidirectional • traffic of the marketing department and the technical department. Figure 33 Network diagram Configuration procedure Create a local mirroring group: # Create local mirroring group 1. <DeviceA>...

  • Page 94: Layer 2 Remote Port Mirroring Configuration Example

    Layer 2 remote port mirroring configuration example Network requirements On the Layer 2 network shown in Figure Device A connects to the marketing department through GigabitEthernet 1/0/1 and connects to • the trunk port GigabitEthernet 1/0/1 of Device B through the trunk port GigabitEthernet 1/0/2. Device C connects to the server through GigabitEthernet 1/0/2 and connects to the trunk port GigabitEthernet 1/0/2 of Device B through the trunk port GigabitEthernet 1/0/1.
  • Page 95 [DeviceA-GigabitEthernet1/0/2] quit Configure Device B (the intermediate device): # Create VLAN 2 as the remote probe VLAN. <DeviceB> system-view [DeviceB] vlan 2 # Disable MAC address learning for the remote probe VLAN. [DeviceB-vlan2] mac-address mac-learning disable [DeviceB-vlan2] quit # Configure GigabitEthernet 1/0/1 as a trunk port that permits the packets of VLAN 2 to pass through.
  • Page 96 After the configurations are completed, you can monitor all the packets received and sent by the marketing department on the server.

  • Page 97: Configuring Traffic Mirroring

    Configuring traffic mirroring Introduction to traffic mirroring Traffic mirroring copies the specified packets to the specified destination for packet analyzing and monitoring. It is implemented through QoS policies. In other words, you define traffic classes and configure match criteria to classify packets to be mirrored and then configure traffic behaviors to mirror packets that fit the match criteria to the specified destination.

  • Page 98: Configuring Traffic Mirroring Of Different Types

    Configuring traffic mirroring of different types In a traffic behavior, you can configure only one type of traffic mirroring. Mirroring traffic to a port Step Command Remarks Enter system view. system-view By default, no traffic behavior exists. Create a behavior and enter traffic behavior For more information about the traffic behavior view.

  • Page 99: Applying A Qos Policy

    Applying a QoS policy For more information about applying a QoS policy, see ACL and QoS Configuration Guide. Apply a QoS policy to a port By applying a QoS policy to an interface, you can mirror the traffic in a specified direction on the interface.

  • Page 100: Displaying And Maintaining Traffic Mirroring

    For more information about the qos apply policy command, see ACL and QoS Command Reference. Displaying and maintaining traffic mirroring Task Command Remarks display traffic behavior user-defined Display user-defined traffic behavior Available in any [ behavior-name ] [ | { begin | exclude | configuration information.

  • Page 101: Qos Policy

    Configuration procedure Monitor the traffic sent by the technology department to access the Internet: # Create ACL 3000 to allow packets from the technology department (on subnet 192.168.2.0/24) to access the Internet. <DeviceA> system-view [DeviceA] acl number 3000 [DeviceA-acl-adv-3000] rule permit tcp source 192.168.2.0 0.0.0.255 destination-port eq www [DeviceA-acl-adv-3000] quit # Create traffic class tech_c, and configure the match criterion as ACL 3000.
  • Page 102 # Create QoS policy mkt_p, and associate traffic class mkt_c with traffic behavior mkt_b in the QoS policy. [DeviceA] qos policy mkt_p [DeviceA-qospolicy-mkt_p] classifier mkt_c behavior mkt_b [DeviceA-qospolicy-mkt_p] quit # Apply QoS policy mkt_p to the outgoing packets of GigabitEthernet 1/0/2. [DeviceA] interface GigabitEthernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] qos apply policy mkt_p outbound Verify the configurations.

  • Page 103: Configuring Nqa

    Configuring NQA Overview Network Quality Analyzer (NQA) can perform various types of tests and collect network performance and service quality parameters such as delay jitter, time for establishing a TCP connection, time for establishing an FTP connection, and file transfer rate. With the NQA test results, you can diagnose and locate network faults, be aware of network performance in time and take proper actions to correct any problems.
  • Page 104 The application module takes actions when the tracked object changes its state. • The following describes how a static route is monitored through collaboration. NQA monitors the reachability to 192.168.0.88. When 192.168.0.88 becomes unreachable, NQA notifies the track module of the change. The track module notifies the state change to the static routing module The static routing module sets the static route as invalid.

  • Page 105: Nqa Concepts

    The counting for the average or accumulate threshold type is performed per test, but the counting for the consecutive type is performed after the test group starts. Triggered actions • The following actions may be triggered: none—NQA only records events for terminal display. It does not send trap information to the network management server.

  • Page 106: Nqa Probe Operation Procedure

    NQA client and server A device with NQA test groups configured is an NQA client, and the NQA client initiates NQA tests. An NQA server makes responses to probe packets destined to the specified destination address and port number. Figure 37 Relationship between the NQA client and NQA server Not all test types require the NQA server.

  • Page 107: Configuring The Nqa Server

    Task Remarks Configuring FTP tests Configuring HTTP tests Configuring UDP jitter tests Configuring SNMP tests Configuring TCP tests Configuring UDP echo tests Configuring voice tests Configuring DLSw tests Configuring the collaboration function Optional. Configuring threshold monitoring Optional. Configuring the NQA statistics collection function Optional.

  • Page 108: Creating An Nqa Test Group

    Step Command Remarks Enter system view. system-view Optional. Enable the NQA client. nqa agent enable Enabled by default. Creating an NQA test group Create an NQA test group before you configure NQA tests. To create an NQA test group: Step Command Remarks Enter system view.

  • Page 109: Configuring Dhcp Tests

    Step Command Remarks Optional. Configure the string to be filled in the data field of each data-fill string By default, the string is the hexadecimal ICMP echo request. number 00010203040506070809. Optional. Apply ICMP echo tests to the vpn-instance By default, ICMP echo tests apply to the specified VPN.

  • Page 110: Configuring Dns Tests

    Step Command Remarks Enter system view. system-view Enter NQA test group nqa entry admin-name view. operation-tag Configure the test type as DHCP, and enter test type type dhcp view. By default, no interface is configured to operation interface perform DHCP tests. Specify an interface to interface-type perform DHCP tests.
  • Page 111 Before you start FTP tests, configure the FTP server. For example, configure a username and password that are used to log in to the FTP server. For more information about FTP server configuration, see Fundamentals Configuration Guide. Follow these guidelines when you configure FTP tests: When you execute the put command, the NQA client creates a file named file-name of fixed size •...

  • Page 112: Configuring Http Tests

    Configuring HTTP tests HTTP tests of an NQA test group are used to test the connection between the NQA client and an HTTP server, and the time required to obtain data from the HTTP server. HTTP tests enable you to detect the connectivity and performance of the HTTP server.
  • Page 113 Real-time services such as voice and video have high requirements on delay jitters. UDP jitter tests of an NQA test group obtain uni/bi-directional delay jitters. The test results help you verify whether a network can carry real-time services. A UDP jitter test performs the following procedure: The source sends packets to the destination port at regular intervals.

  • Page 114: Configuring Snmp Tests

    Step Command Remarks Configure the interval for Optional. sending probe packets during probe packet-interval each UDP jitter probe packet-interval 20 milliseconds by default. operation. Configure the interval the NQA client must wait for a Optional. probe packet-timeout response from the server packet-timeout 3000 milliseconds by default.

  • Page 115: Configuring Tcp Tests

    Step Command Remarks Optional. Configure the source IP By default, no source IP address is specified. address of SNMP source ip ip-address The source IP address must be the IP address of packets. a local interface. The local interface must be up. Otherwise, no probe packets can be sent out.

  • Page 116: Configuring Udp Echo Tests

    Configuring UDP echo tests UDP echo tests of an NQA test group are used to test the connectivity and round-trip time of a UDP packet from the client to the specified UDP port on the NQA server. UDP echo tests require cooperation between the NQA server and the NQA client. Before you start UDP echo tests, configure a UDP listening service on the NQA server.
  • Page 117 IMPORTANT: Do not perform voice tests on known ports, ports from 1 to 1023. Otherwise, the NQA test might fail or the corresponding services of these ports might be unavailable. Voice tests of an NQA test group are used to test voice over IP (VoIP) network status, and collect VoIP network parameters so that users can adjust the network.

  • Page 118: Configuring Dlsw Tests

    Step Command Remarks By default, no destination port number is Configure the destination configured. port of voice probe destination port port-number The destination port must be the same as that packets. of the listening service on the NQA server. Optional. codec-type { g711a | g711u Configure the codec type.

  • Page 119: Configuring The Collaboration Function

    Before you start DLSw tests, enable the DLSw function on the peer device. To configure DLSw tests: Step Command Remarks Enter system view. system-view Enter NQA test group nqa entry admin-name view. operation-tag Configure the test type as DLSw, and enter test type dlsw type view.

  • Page 120: Configuring Threshold Monitoring

    Configuring threshold monitoring Configuration prerequisites Before you configure threshold monitoring, complete the following tasks: Configure the destination address of the trap message by using the snmp-agent target-host • command. For more information about the snmp-agent target-host command, see Network Management and Monitoring Command Reference. •...
  • Page 121 Step Command Remarks • Enable sending traps to the network management server under specified conditions: reaction trap { probe-failure consecutive-probe-failures | test-complete | test-failure cumulate-probe-failures } • Configure a reaction entry for monitoring the probe duration of a test (not supported in UDP jitter and voice tests): reaction item-number checked-element probe-duration threshold-type { accumulate accumulate-occurrences | average | consecutive consecutive-occurrences }...

  • Page 122: Configuring The Nqa Statistics Collection Function

    Configuring the NQA statistics collection function NQA groups tests completed in a time period for a test group, and calculates the test result statistics. The statistics form a statistics group. To view information about the statistics groups, use the display nqa statistics command.

  • Page 123: Configuring Optional Parameters For An Nqa Test Group

    Step Command Remarks Enter system view. system-view Enter NQA test group nqa entry admin-name view. operation-tag type { dhcp | dlsw | dns | ftp | http | icmp-echo | snmp | Enter NQA test type view. tcp | udp-echo | udp-jitter | voice } Enable the saving of the By default, history records of the NQA test...

  • Page 124: Configuring A Schedule For An Nqa Test Group

    Step Command Remarks Optional. By default, the interval between two consecutive tests for a test group is 0 Configure the interval between milliseconds. Only one test is performed. two consecutive tests for a test frequency interval If the last test is not completed when the group.

  • Page 125: Configuration Guidelines

    Configuration guidelines Follow these guidelines when you schedule an NQA test group: After an NQA test group is scheduled, you cannot enter the test group view or test type view. • System adjustment does not affect started or completed test groups. It only affects test groups that •...

  • Page 126: Nqa Configuration Examples

    NQA configuration examples ICMP echo test configuration example Network requirements As shown in Figure 38, configure NQA ICMP echo tests to test whether the NQA client (Device A) can send packets through a specific next hop to the specified destination (Device B) and test the round-trip time of the packets.

  • Page 127: Dhcp Test Configuration Example

    # Enable the saving of history records and configure the maximum number of history records that can be saved for a test group. [DeviceA-nqa-admin-test-icmp-echo] history-record enable [DeviceA-nqa-admin-test-icmp-echo] history-record number 10 [DeviceA-nqa-admin-test-icmp-echo] quit # Start ICMP echo tests. [DeviceA] nqa schedule admin test start-time now lifetime forever # Stop the ICMP echo tests after a period of time.
  • Page 128 Figure 39 Network diagram Configuration procedure # Create a DHCP test group, and specify interface VLAN-interface 2 to perform NQA DHCP tests. <DeviceA> system-view [DeviceA] nqa entry admin test [DeviceA-nqa-admin-test] type dhcp [DeviceA-nqa-admin-test-dhcp] operation interface vlan-interface 2 # Enable the saving of history records. [DeviceA-nqa-admin-test-dhcp] history-record enable [DeviceA-nqa-admin-test-dhcp] quit # Start DHCP tests.

  • Page 129: Dns Test Configuration Example

    DNS test configuration example Network requirements As shown in Figure 40, configure NQA DNS tests to test whether Device A can translate the domain name host.com into an IP address through the DNS server and test the time required for resolution. Figure 40 Network diagram Configuration procedure Before you make the configuration, make sure the devices can reach each other.

  • Page 130: Ftp Test Configuration Example

    Packet(s) arrived late: 0 # Display the history of DNS tests. [DeviceA] display nqa history admin test NQA entry (admin admin, tag test) history record(s): Index Response Status Time Succeeded 2011-01-10 10:49:37.3 FTP test configuration example Network requirements As shown in Figure 41, configure NQA FTP tests to test the connection with a specific FTP server and the time required for Device A to upload a file to the FTP server.

  • Page 131: Http Test Configuration Example

    [DeviceA] display nqa result admin test NQA entry (admin admin, tag test) test results: Destination IP address: 10.2.2.2 Send operation times: 1 Receive response times: 1 Min/Max/Average round trip time: 173/173/173 Square-Sum of round trip time: 29929 Last succeeded probe time: 2011-01-22 10:07:28.6 Extended results: Packet loss in test: 0% Failures due to timeout: 0...

  • Page 132: Udp Jitter Test Configuration Example

    [DeviceA-nqa-admin-test-http] url /index.htm # Configure the HTTP version 1.0 to be used in HTTP tests. (Version 1.0 is the default version, and this step is optional.) [DeviceA-nqa-admin-test-http] http-version v1.0 # Enable the saving of history records. [DeviceA-nqa-admin-test-http] history-record enable [DeviceA-nqa-admin-test-http] quit # Start HTTP tests.

  • Page 133: Destination Port

    Configuration procedure Before you make the configuration, make sure the devices can reach each other. Enable the NQA server, and configure a listening service to listen to IP address 10.2.2.2 and UDP port 9000 on Device B. <DeviceB> system-view [DeviceB] nqa server enable [DeviceB] nqa server udp-echo 10.2.2.2 9000 Configure Device A: # Create a UDP jitter test group.
  • Page 134 Positive SD average: 10 Positive DS average: 10 Positive SD square sum: 754 Positive DS square sum: 460 Min negative SD: 1 Min negative DS: 6 Max negative SD: 13 Max negative DS: 22 Negative SD number: 4 Negative DS number: 5 Negative SD sum: 38 Negative DS sum: 52 Negative SD average: 10...

  • Page 135: Snmp Test Configuration Example

    Negative SD square sum: 46994 Negative DS square sum: 3030 One way results: Max SD delay: 46 Max DS delay: 46 Min SD delay: 7 Min DS delay: 7 Number of SD delay: 410 Number of DS delay: 410 Sum of SD delay: 3705 Sum of DS delay: 3891 Square sum of SD delay: 45987 Square sum of DS delay: 49393...

  • Page 136: Tcp Test Configuration Example

    # Start SNMP tests. [DeviceA] nqa schedule admin test start-time now lifetime forever # Stop the SNMP tests after a period of time. [DeviceA] undo nqa schedule admin test # Display the results of the last SNMP test. [DeviceA] display nqa result admin test NQA entry (admin admin, tag test) test results: Destination IP address: 10.2.2.2 Send operation times: 1...

  • Page 137: Udp Echo Test Configuration Example

    # Create a TCP test group. <DeviceA> system-view [DeviceA] nqa entry admin test [DeviceA-nqa-admin-test] type tcp # Configure TCP probe packets to use 10.2.2.2 as the destination IP address and port 9000 as the destination port. [DeviceA-nqa-admin-test-tcp] destination ip 10.2.2.2 [DeviceA-nqa-admin-test-tcp] destination port 9000 # Enable the saving of history records.
  • Page 138 Figure 46 Network diagram Configuration procedure Before you make the configuration, make sure the devices can reach each other. Enable the NQA server, and configure a listening service to listen to IP address 10.2.2.2 and UDP port 8000 on Device B. <DeviceB>...

  • Page 139: Voice Test Configuration Example

    # Display the history of UDP echo tests. [DeviceA] display nqa history admin test NQA entry (admin admin, tag test) history record(s): Index Response Status Time Succeeded 2011-01-22 10:36:17.9 Voice test configuration example Network requirements As shown in Figure 47, configure NQA voice tests to test the delay jitter of voice packet transmission and voice quality between Device A and Device B.
  • Page 140 Last succeeded probe time: 2011-01-13 09:49:31.1 Extended results: Packet loss in test: 0% Failures due to timeout: 0 Failures due to disconnect: 0 Failures due to no connection: 0 Failures due to sequence error: 0 Failures due to internal error: 0 Failures due to other errors: 0 Packet(s) arrived late: 0 Voice results:...

  • Page 141: Dlsw Test Configuration Example

    Failures due to no connection: 0 Failures due to sequence error: 0 Failures due to internal error: 0 Failures due to other errors: 0 Packet(s) arrived late: 0 Voice results: RTT number: 4000 Min positive SD: 1 Min positive DS: 1 Max positive SD: 360 Max positive DS: 1297 Positive SD number: 1030...

  • Page 142: Nqa Collaboration Configuration Example

    Configuration procedure Before you make the configuration, make sure the devices can reach each other. # Create a DLSw test group, and configure DLSw probe packets to use 10.2.2.2 as the destination IP address. <DeviceA> system-view [DeviceA] nqa entry admin test [DeviceA-nqa-admin-test] type dlsw [DeviceA-nqa-admin-test-dlsw] destination ip 10.2.2.2 # Enable the saving of history records.

  • Page 143: Verifying The Configuration

    Figure 49 Network diagram Configuration procedure Assign each interface an IP address. (Details not shown.) Configure a static route, whose destination address is 10.2.1.1, and associate the static route with track entry 1 on Device A. <DeviceA> system-view [DeviceA] ip route-static 10.1.1.2 24 10.2.1.1 track 1 On Device A, create an NQA test group: # Create an NQA test group with the administrator name being admin and operation tag being test.
  • Page 144 Reaction: 1 # Display brief information about active routes in the routing table on Device A. [DeviceA] display ip routing-table Routing Tables: Public Destinations : 5 Routes : 5 Destination/Mask Proto Cost NextHop Interface 10.1.1.0/24 Static 60 10.2.1.1 Vlan3 10.2.1.0/24 Direct 0 10.2.1.2 Vlan3...

  • Page 145: Configuring Sflow

    Configuring sFlow Sampled Flow (sFlow) is a traffic monitoring technology used to collect and analyze traffic statistics. As shown in Figure 50, the sFlow system involves an sFlow agent embedded in a device and a remote sFlow collector. The sFlow agent collects interface counter information and packet information and encapsulates the sampled information into sFlow packets.

  • Page 146: Configuring The Sflow Agent And Sflow Collector

    Configuring the sFlow agent and sFlow collector Step Command Remarks Enter system system-view view. Optional Not specified by default. The device periodically checks the existence of the sFlow agent address. If the sFlow agent has no IP address configured, the device automatically Specify the IP selects an interface IP address for the sFlow sflow agent { ip ip-address | ipv6...

  • Page 147: Configuring Counter Sampling

    NOTE: The switch does not support the flow sampling mode determine. Configuring counter sampling Step Command Remarks Enter system view. system-view Enter Layer 2 interface interface interface-type view. interface-number Set the interval for sflow counter interval seconds Counter sampling is disabled by default. counter sampling.
  • Page 148 Configuration procedure Configure the sFlow agent and sFlow collector: # Configure the IP address of vlan-interface 1 on Device as 3.3.3.1/16. <Device> system-view [Device] interface vlan-interface 1 [Device-Vlan-interface1] ip address 3.3.3.1 16 [Device-Vlan-interface1] quit # Specify the IP address for the sFlow agent. [Device] sflow agent ip 3.3.3.1 # Specify sFlow collector ID 2, IP address 3.3.3.2, the default interface number, and description of netserver for the sFlow collector.

  • Page 149: Troubleshooting Sflow Configuration

    The output shows that GigabitEthernet 1/0/1 enabled with sFlow is active, the counter sampling interval is 120 seconds, the Flow sampling interval is 4000, all of which indicate sFlow operates normally. Troubleshooting sFlow configuration Symptom The remote sFlow collector cannot receive sFlow packets. Analysis •...

  • Page 150: Configuring Ipc

    Configuring IPC This chapter provides an overview of IPC and describes the IPC monitoring commands. Overview Inter-Process Communication (IPC) provides a reliable communication mechanism among processing units, typically CPUs. IPC is typically used on a distributed device or in an IRF fabric to provide reliable inter-card or inter-device transmission.

  • Page 151: Packet Sending Modes

    Figure 52 Relationship between a node, link and channel Packet sending modes IPC uses one of the following modes to send packets for upper layer application modules: • Unicast—One node sends packets to another node. Multicast—One node sends packets to multiple nodes. This mode includes broadcast, a special •...

  • Page 152: Displaying And Maintaining Ipc

    Displaying and maintaining IPC Task Command Remarks display ipc node [ | { begin | Display IPC node information. exclude | include } Available in any view regular-expression ] display ipc channel { node node-id Display channel information for a | self-node } [ | { begin | exclude | Available in any view node.

  • Page 153: Support And Other Resources

    Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers • • Technical support registration number (if applicable) Product serial numbers •...

  • Page 154: Conventions

    Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
  • Page 155 Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
  • Page 156 Index A C D E H I N O P R S T Displaying and maintaining information center,47 Displaying and maintaining IPC,145 Alarm group configuration example,73 Displaying and maintaining NQA,1 18 Applying a QoS policy,92 Displaying and maintaining NTP,21 Displaying and maintaining port mirroring,85 Displaying and maintaining RMON,70...
  • Page 157 Ping,1 SNMP configuration task list,53 Ping and tracert example,7 Switching the NM-specific interface index format,57 Port mirroring configuration examples,85 System debugging,5 Related information,146 Tracert,3 Traffic mirroring configuration example,93 Traffic mirroring configuration task list,90 sFlow configuration example,140 Troubleshooting sFlow configuration,142 sFlow configuration task list,138 SNMP configuration examples,61...

This manual is also suitable for:

6125 blade switch series

Table of Contents