Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

I can not see link up/down log with csm s/w 2.2(2a)

hi

We are using one SLB Application Processor Complex

in slot 4 on 6513 switch.

and then We can not see link up down log with csm s/w 2.2(2a).

is it a bug? How can i see link up/down log ?

logging level is debugging.

please help me.

thanks

5 REPLIES
Cisco Employee

Re: I can not see link up/down log with csm s/w 2.2(2a)

the CSM itself does not have links but vlan interface.

Links are on the MSFC.

Are you talking about the MSFC physical interface ?

Could you please clarify what you expect to see.

Anyway, what software do you run on the MSFC ?

Do you have logging buffer or console enable (which one)

Are you on the console or do you telnet to the MSFC ?

Regards,

Gilles.

New Member

Re: I can not see link up/down log with csm s/w 2.2(2a)

I am sorry for my bad explaining.

as a matter of fact customer told me

that link up/down logs do not show up

after they upgraded s/w from catos to native ios.

the upgraded s/w name is c6sup22-jsv-mz.121-13.E9.bin.

and link up/down meant physical interface up/down.

and customer told me that they have a hard time to maintain

cisco router/switch because link up/down logs do not show up.

i hope to know that my customer speaking is true.

thanks

Cisco Employee

Re: I can not see link up/down log with csm s/w 2.2(2a)

Ok - more questions.

Does the customer wants to see the message in the console ? in the buffer ? on a syslog server ? or via snmptrap ?

Can we get the first lines of 'sho log' where we see information about how logging was configured.

Thanks,

Gilles.

New Member

Re: I can not see link up/down log with csm s/w 2.2(2a)

Customer enters the switch using telnet command.

and they used to use show logging command.

and they cannot see link up/down log there.

I attach show logging output below.

DATA_CENTER_1#show logg

DATA_CENTER_1#show logging

Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns)

Console logging: level debugging, 130 messages logged

Monitor logging: level debugging, 0 messages logged

Buffer logging: level debugging, 131 messages logged

Exception Logging: size (4096 bytes)

Trap logging: level informational, 190 message lines logged

Logging to 169.140.145.146, 190 message lines logged

Logging to 169.140.145.142, 190 message lines logged

Logging to 169.140.145.143, 190 message lines logged

Log Buffer (8192 bytes):

7:45: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.103:80 in serverfarm 'E-CAMPUS_80'

Nov 6 22:34:02: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.101:80 in serverfarm 'E-CAMPUS_80'

Nov 6 22:35:12: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.101:80 in serverfarm 'E-CAMPUS_80'

Nov 6 23:30:37: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.103:80 in serverfarm 'E-CAMPUS_80'

Nov 7 00:22:03: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.42:8001 in serverfarm 'MTS-TEST_8001'

Nov 7 00:22:07: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.42:80 in serverfarm 'MES-TEST_80'

Nov 7 00:22:17: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.43:80 in serverfarm 'MES-TEST_80'

Nov 7 00:22:19: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.43:8001 in serverfarm 'MTS-TEST_8001'

Nov 7 07:18:02: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.42:80 in serverfarm 'MES-TEST_80'

Nov 7 07:18:02: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.42:8001 in serverfarm 'MTS-TEST_8001'

Nov 7 07:18:20: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.43:8001 in serverfarm 'MTS-TEST_8001'

Nov 7 07:18:29: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.43:80 in serverfarm 'MES-TEST_80'

Nov 10 14:19:07: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.128.43:7779 in serverfarm 'STS_AP'

Nov 10 14:21:27: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.128.43:7779 in serverfarm 'STS_AP'

Nov 10 14:22:38: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.128.44:7779 in serverfarm 'STS_AP'

Nov 10 14:25:58: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.128.44:7779 in serverfarm 'STS_AP'

Nov 10 17:15:49: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 10 17:21:39: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 10 18:35:18: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.103:80 in serverfarm 'E-CAMPUS_80'

Nov 10 18:39:28: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.103:80 in serverfarm 'E-CAMPUS_80'

Nov 10 18:46:21: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.101:80 in serverfarm 'E-CAMPUS_80'

Nov 10 18:53:20: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.101:80 in serverfarm 'E-CAMPUS_80'

Nov 10 22:08:43: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 10 22:13:13: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 10 22:49:54: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 10 22:51:24: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 12 15:32:42: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.128.43:7779 in serverfarm 'STS_AP'

Nov 12 15:32:52: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.128.43:7779 in serverfarm 'STS_AP'

Nov 12 15:33:11: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.128.44:7779 in serverfarm 'STS_AP'

Nov 12 15:33:31: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.128.44:7779 in serverfarm 'STS_AP'

Nov 13 10:13:10: %SYS-5-CONFIG_I: Configured from console by vty0 (169.140.146.177)

Nov 13 10:22:19: %SYS-5-CONFIG_I: Configured from console by vty0 (169.140.146.177)

Nov 13 12:58:07: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.42:80 in serverfarm 'MES-TEST_80'

Nov 13 12:58:07: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.42:8001 in serverfarm 'MTS-TEST_8001'

Nov 13 13:12:38: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.42:8001 in serverfarm 'MTS-TEST_8001'

Nov 13 13:12:47: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.42:80 in serverfarm 'MES-TEST_80'

Nov 13 16:50:45: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 13 16:58:45: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.54:8001 in serverfarm 'MTS-PATCH_8001'

Nov 13 18:37:09: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.103:80 in serverfarm 'E-CAMPUS_80'

Nov 13 18:38:50: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.131:80 in serverfarm 'MES-MAIN_80'

Nov 13 18:38:52: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.131:8001 in serverfarm 'YARD_8001'

Nov 13 18:39:00: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.131:80 in serverfarm 'MES-MAIN_80'

Nov 13 18:39:02: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.131:8001 in serverfarm 'YARD_8001'

Nov 13 18:39:29: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.132:80 in serverfarm 'MES-MAIN_80'

Nov 13 18:39:31: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.132:8001 in serverfarm 'YARD_8001'

Nov 13 18:40:09: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.132:80 in serverfarm 'MES-MAIN_80'

Nov 13 18:40:11: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.132:8001 in serverfarm 'YARD_8001'

Nov 13 18:43:10: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.103:80 in serverfarm 'E-CAMPUS_80'

Nov 13 18:47:37: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe failed for server 169.140.60.101:80 in serverfarm 'E-CAMPUS_80'

Nov 13 18:57:58: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: TCP health probe re-activated server 169.140.60.101:80 in serverfarm 'E-CAMPUS_80'

DATA_CENTER_1#

Cisco Employee

Re: I can not see link up/down log with csm s/w 2.2(2a)

try the following command on every interface you wish to see the link up/down messages :

logging event link-status

Gilles.

528
Views
0
Helpful
5
Replies