Administration of the Avaya G350 Media Gateway - Avaya Support
Share Embed Flag
Download ePaper

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support Administration of the Avaya G350 Media Gateway - Avaya Support

downloads.avaya.com
from downloads.avaya.com More from this publisher
13.07.2015 Views

Configuring RMON monitoringRMON CLI commandsUse the following commands to configure RMON. For more information about thesecommands, see Avaya G350 Media Gateway CLI Reference, 555-245-202.●●●●●●●Use the rmon alarm command to create an RMON alarm entry.Use the rmon event command to create an RMON event entry.Use the rmon history command to create an RMON history entry.Use the show rmon alarm command to display all RMON alarm entries.Use the show rmon event command to display RMON event entries.Use the show rmon history command to display RMON alarm entries.Use the show rmon statistics command to display RMON statistics.RMON configuration examplesThis section provides RMON configuration examples.The following example creates an RMON alarm entry:G350-003(super)# rmon alarm 1 1.3.6.1.2.1.16.1.1.1.5.16777216 20 deltarising-threshold 10000 32 falling-threshold 1000 32 risingOrFallingrootalarm 1 was created successfullyThe following example creates an RMON event entry:G350-003(super)# rmon event 32 log description “Change of device”owner rootevent 32 was created successfullyThe following example creates an RMON history entry with an index of 80 on port 24 of themodule in slot 6, recording activity over 60 intervals (buckets) of 20 seconds each.G350-003(super)# rmon history 80 6/24 interval 20 buckets 60 owner roothistory index 80 was created successfullyThe following example displays information about an RMON alarm entry:G350-003(super)# show rmon alarm 1alarmalarm 1 is active, owned by rootMonitors ifEntry.1.16777216 every 20 secondsTaking delta samples, last value was 0156 Administration of the Avaya G350 Media Gateway

RMON configuration examplesRising threshold is 10000, assigned to event # 32Falling threshold is 1000, assigned to event # 32On startup enable rising or_falling alarmsThe following example displays information about an RMON event entry:G350-003(super)# show rmon event 32eventEvent 32 is active, owned by rootDescription is Change of deviceEvent firing causes log,last fired 12:36:04The following example displays information about an RMON history entry:G350-003(super)# show rmon history 80historyEntry 80 is active, owned by rootMonitors the port 6/24 every 20 secondsRequested # of time intervals, ie buckets, is 60Granted # of time intervals, ie buckets, is 60Sample # 2 began measuring at 0:21:16Received 4081 octets, 41 packets,0 broadcast and 10 multicast packets,0 undersize and 0 oversize packets,0 fragments and 0 jabbers,0 CRC alignment errors and 0 collisions,# of dropped packet events (due to a lack of resources): 0Network utilization is estimated at 0The following example displays RMON statistics for a port:G350-003(super)# show rmon statistics 6/24Statistics for port 6/24 is active, owned by MonitorReceived 6952909 octets, 78136 packets,26 broadcast and 257 multicast packets,0 undersize and 0 oversize packets,0 fragments and 0 jabbers,0 CRC alignment errors and 0 collisions,# of dropped packet events (due to a lack of resources): 0# of packets received of length (in octets):64:18965, 65-127:295657, 128-255:4033,256-511:137, 512-1023:156, 1024-1518:0,Issue 3 January 2005 157

Configuring RMON monitoringRMON CLI commandsUse <strong>the</strong> following commands to configure RMON. For more information about <strong>the</strong>secommands, see <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> CLI Reference, 555-245-202.●●●●●●●Use <strong>the</strong> rmon alarm command to create an RMON alarm entry.Use <strong>the</strong> rmon event command to create an RMON event entry.Use <strong>the</strong> rmon history command to create an RMON history entry.Use <strong>the</strong> show rmon alarm command to display all RMON alarm entries.Use <strong>the</strong> show rmon event command to display RMON event entries.Use <strong>the</strong> show rmon history command to display RMON alarm entries.Use <strong>the</strong> show rmon statistics command to display RMON statistics.RMON configuration examplesThis section provides RMON configuration examples.The following example creates an RMON alarm entry:<strong>G350</strong>-003(super)# rmon alarm 1 1.3.6.1.2.1.16.1.1.1.5.16777216 20 deltarising-threshold 10000 32 falling-threshold 1000 32 risingOrFallingrootalarm 1 was created successfullyThe following example creates an RMON event entry:<strong>G350</strong>-003(super)# rmon event 32 log description “Change <strong>of</strong> device”owner rootevent 32 was created successfullyThe following example creates an RMON history entry with an index <strong>of</strong> 80 on port 24 <strong>of</strong> <strong>the</strong>module in slot 6, recording activity over 60 intervals (buckets) <strong>of</strong> 20 seconds each.<strong>G350</strong>-003(super)# rmon history 80 6/24 interval 20 buckets 60 owner roothistory index 80 was created successfullyThe following example displays information about an RMON alarm entry:<strong>G350</strong>-003(super)# show rmon alarm 1alarmalarm 1 is active, owned by rootMonitors ifEntry.1.16777216 every 20 secondsTaking delta samples, last value was 0156 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!