CSS - how to log dying status

[sthon-dbsys]

how can i log the dying status ??

I tried:

logging subsystem keepalive level debug-7

logging host <hostip> facility 7 log-level debug-7

without success.

using WebNS: 7.20 Build 305

thanks in advance

[sagdas]

Hey,

Try this.

logging subsystem netman level debug-7

Regards,

Sagar

[sthon-dbsys]

ok,

I´ll try it and wait for the next dying status change.

[sthon-dbsys]

here the log,

nothing to see from the dying log change:

muecss01-24# show service nolta

Name: nolta Index: 26

Type: Local State: Dying

Rule ( 172.29.xx.xx ANY ANY )

Session Redundancy: Disabled

Redirect Domain:

Redirect String:

Keepalive: (TCP-80 30 5 60 )

Last Clearing of Stats Counters: 07/05/2004 11:55:17

Mtu: 1500 State Transitions: 4

Total Local Connections: 0 Total Backup Connections: 0

Current Local Connections: 0 Current Backup Connections: 0

Total Connections: 0 Max Connections: 65534

Total Reused Conns: 0

Weight: 1 Load: 2

DFP: Disable

muecss01-24#

muecss01-24#

muecss01-24# show log sys.log tail 50

JUL 23 13:29:13 1/1 2142 KAL-7: kal_ActiveIcp: kalIndex = 26

JUL 23 13:29:13 1/1 2143 KAL-7: ICP KAL START keepalive 26 !

JUL 23 13:29:13 1/1 2144 NETMAN-2: Enterprise:Service Transition:nolta -> down

JUL 23 13:31:50 1/1 2145 NETMAN-5: Enterprise:Service Transition:nolta -> alive

JUL 23 13:33:39 1/1 2146 KAL-7: kal_RemoveServiceToKal: keepalive = 26 serviceIndex = 26

JUL 23 13:33:39 1/1 2147 KAL-7: kal_SuspendIcp: kalIndex = 26

JUL 23 13:33:39 1/1 2148 KAL-7: ICP KAL STOP keepalive 26 !

JUL 23 13:33:39 1/1 2149 KAL-7: CREATING keepalive for service nolta !

JUL 23 13:33:39 1/1 2150 KAL-7: kal_AddServiceToKal: keepalive = 26 serviceIndex = 26

JUL 23 13:33:39 1/1 2151 KAL-7: kal_ActiveIcp: kalIndex = 26

JUL 23 13:33:39 1/1 2152 KAL-7: ICP KAL START keepalive 26 !

JUL 23 13:33:39 1/1 2153 KAL-7: kal_SingleServiceNotify: kalIndex = 26 kalSvcEvent=4

here also the configured log level:

logging subsystem syssoft level error-3

logging subsystem keepalive level debug-7

logging subsystem netman level debug-7

any ideas ???

[Gilles Dufour]

NETMANN level 4 will log status down

NETMANN level 5 will log status alive

Other status do not log a NETMANN message.

But you can use the KAL level 7 to see the keepalive going dying - dying is kalSvcEvent 4.

3 is alive and 5 is down.

KAL-7: kal_SingleServiceNotify: kalIndex = 26 kalSvcEvent=4

Regards,

Gilles.