Rmon configuration example (logging information), Network requirements, Configuration procedure – H3C Technologies H3C S5120 Series Switches User Manual

Page 597

Advertising
background image

1-7

RMON Configuration Example (Logging Information)

Network requirements

As shown in

Figure 1-1

, Agent is connected to a configuration terminal through its console port and to

Server through Ethernet cables.

Create an entry in the RMON Ethernet statistics table to gather statistics on GigabitEthernet 1/0/1, and

enable logging after received bytes exceed the specified threshold.

Figure 1-1 Network diagram for RMON

Configuration procedure

# Configure RMON to gather statistics for interface GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface GigabitEthernet 1/0/1

[Sysname-Ethernet1/1] rmon statistics 1 owner user1-rmon

[Sysname-Ethernet1/1] quit

# Display RMON statistics for interface GigabitEthernet 1/0/1.

<Sysname> display rmon statistics GigabitEthernet 1/0/1

Statistics entry 1 owned by user1-rmon is VALID.

Interface : Ethernet1/1<ifIndex.3>

etherStatsOctets : 21657 , etherStatsPkts : 307

etherStatsBroadcastPkts : 56 , etherStatsMulticastPkts : 34

etherStatsUndersizePkts : 0 , etherStatsOversizePkts : 0

etherStatsFragments : 0 , etherStatsJabbers : 0

etherStatsCRCAlignErrors : 0 , etherStatsCollisions : 0

etherStatsDropEvents (insufficient resources): 0

Packets received according to length:

64 : 235 , 65-127 : 67 , 128-255 : 4

256-511: 1 , 512-1023: 0 , 1024-1518: 0

# Create an event to start logging after the event is triggered.

<Sysname> system-view

[Sysname] rmon event 1 log owner 1-rmon

# Configure an alarm group to sample received bytes on GigabitEthernet 1/0/1. When the received

bytes exceed the upper or below the lower limit, logging is enabled.

[Sysname] rmon alarm 1 1.3.6.1.2.1.16.1.1.1.4.1 10 delta rising-threshold 1000 1

falling-threshold 100 1 owner 1-rmon

Advertising