[alcatel-nsp] Why this log message?

[Craig Publow]

Filtering these events may not be the best course to take.  The log that
you're applying the filter to is "log 98'   which is the default SAM log,
so I assume SAM is being used here.  If SAM initiated OAM tests are to be
used,  it could be that SAM relies on these events.

Rather than filtering the events,   you can change the log severity via
"onfig log event-control",  aplication-id being  OAM  and event-numbers are
2007 and 2008

configure  log event-control
  - event-control <application-id> [<event-name>|<event-number>] generate
    [<severity-level>] [throttle]
  - event-control <application-id> [<event-name>|<event-number>] suppress
  - no event-control <application-id> [<event-name>|<event-number>]

 <application-id>     :
aps|atm|bgp|cflowd|chassis|debug|dhcp|efm_oam|filter|
                        gsmp|igmp|igmp_snooping|ip|isis|lag|ldp|logger|

mc_redundancy|mirror|mpls|msdp|ntp|oam|ospf|pim|port|
                        ppp|rip|route_policy|rsvp|security|snmp|stp|svcmgr|
                        system|user|vrrp|vrtr
 <event-name>         : [32 chars max]
 <event-number>       : [0..4294967295]
 <generate>           : keyword - specifies action
 <suppress>           : keyword - specifies action
 <severity-level>     : cleared|indeterminate|critical|major|minor|warning
 <throttle>           : keyword - specifies action


-Craig


On Thu, Nov 5, 2009 at 1:32 AM, Ruslan Pustovoitov <rus-p at mostelekom.net>wrote:

> This is the normal behavior.
> Log level can be modified via filter.
>
> >config>log# filter 2 entry 1 match severity ?
> - no severity
> - severity {eq|neq|lt|lte|gt|gte} <severity-level>
>
> <eq|neq|lt|lte|gt|*> : operator
> <severity-level> : cleared|indeterminate|critical|major|minor|warning
>
>
> Robert J. Huey пишет:
>
>
>> Can anyone describe for me why the following message is being logged?
>>
>> 1. Simple ping from OOB MGMT port (A/1) to a node on MGMT network
>>
>> A:7450# ping 192.168.10.22 router management
>> PING 192.168.10.22 56 data bytes
>> 64 bytes from 192.168.10.22: icmp_seq=1 ttl=254 time<10ms.
>> 64 bytes from 192.168.10.22: icmp_seq=2 ttl=254 time<10ms.
>> 64 bytes from 192.168.10.22: icmp_seq=3 ttl=254 time<10ms.
>> 64 bytes from 192.168.10.22: icmp_seq=4 ttl=254 time<10ms.
>>
>> 2. sho log log-id 98
>>
>> 2709384 2009/11/04 23:01:29.40 UTC WARNING: SYSTEM #2008 Base OAM
>> "Test name "CliIcmpPing-16", owner name "TiMOS CLI" managed object
>> deleted"
>>
>> 2709383 2009/11/04 23:01:25.36 UTC WARNING: SYSTEM #2007 Base OAM
>> "Test name "CliIcmpPing-16", owner name "TiMOS CLI" managed object
>> created"
>>
>> Comments: This looks to me like the node creates a process and logs what
>> it's created and deleted. Interesting that the test name is indexed each
>> time a new process is created and destroyed. "CliIcmpPing-16" was
>> "CliIcmpPing-15" on the prior run of the same CLI command.
>>
>> This seems to be more informational than a warning... I'm not sure that we
>> care either way but I never noticed this behavior before. Can the log level
>> or "WARNING" be modified in any way?
>>
>> rgds,
>> --r
>>
>> _______________________________________________
>> alcatel-nsp mailing list
>> alcatel-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>>
>>  _______________________________________________
> alcatel-nsp mailing list
> alcatel-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20091105/f3c7b22a/attachment.html>