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 loggingFilters and severity levelsYou can use filtering options to reduce the number of collected and transmitted messages. Thefiltering options are based on message classification by application and severity. For a specifiedsink, you can define the threshold severity for message output for each application. Messageswith a severity lower than the defined threshold are sent to the specified sink, and those with ahigher severity than the defined threshold are not sent.Table 4 lists the eight available severity levels.To configure a filter that will eliminate all messages for the specified application, type noneinstead of a severity level.The sinks have the following default severity levels:● Session — warning●Table 4: Severity levelsSeverity level Code DescriptionEmergency 0 System is unusableAlert 1 Immediate action requiredCritical 2 Critical conditionError 3 Error conditionWarning 4 Warning conditionNotification 5 Normal but significant conditionInformational 6 Informational message onlyDebugging 7 Message that only appears during debuggingLog file — informational● Syslog — warningFilters are defined per application. Table 5: Logging applications on page 69 lists theapplications for which you can define filters.68 Administration of the Avaya G350 Media Gateway

Filters and severity levelsTable 5: Logging applications 1 of 2Applicationbootcascadecliconfigconsoledhcpsfanfilesysipsecisakmplagpoepolicyppppppoeqosroutersnmpstpsupplyswitchfabricsystemthresholdusb-modemvlanDescriptionSystem startup failuresStack CASCADE mechanismCLIConfiguration changesSerial modem messagesDHCP server packageCooling systemFile system problem (flash)VPN packageISAKMP protocolLink Aggregation packagePower over EthernetPolicy packagePPP protocolPPP over EthernetQoS messagesCore routing system failuresSNMP agentSpanning tree packagePower supply systemSwitch fabric failuresOperating system failuresRMON alarmsUSB modem messagesVLAN package1 of 2Issue 3 January 2005 69

Configuring loggingFilters and severity levelsYou can use filtering options to reduce <strong>the</strong> number <strong>of</strong> collected and transmitted messages. Thefiltering options are based on message classification by application and severity. For a specifiedsink, you can define <strong>the</strong> threshold severity for message output for each application. Messageswith a severity lower than <strong>the</strong> defined threshold are sent to <strong>the</strong> specified sink, and those with ahigher severity than <strong>the</strong> defined threshold are not sent.Table 4 lists <strong>the</strong> eight available severity levels.To configure a filter that will eliminate all messages for <strong>the</strong> specified application, type noneinstead <strong>of</strong> a severity level.The sinks have <strong>the</strong> following default severity levels:● Session — warning●Table 4: Severity levelsSeverity level Code DescriptionEmergency 0 System is unusableAlert 1 Immediate action requiredCritical 2 Critical conditionError 3 Error conditionWarning 4 Warning conditionNotification 5 Normal but significant conditionInformational 6 Informational message onlyDebugging 7 Message that only appears during debuggingLog file — informational● Syslog — warningFilters are defined per application. Table 5: Logging applications on page 69 lists <strong>the</strong>applications for which you can define filters.68 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>

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

Saved successfully!

Ooh no, something went wrong!