topic RE: Switch rebooted,Working fine. in ExtremeSwitching (EXOS/Switch Engine)

Switch rebooted,Working fine.

ComraDe — Sun, 02 Nov 2014 18:51:00 GMT

The switch got rebooted and no idea why its happend...

11/02/2014 04:41:22.11 Input voltage to External Power Supply in slot 2 is on. Output enabled. 11/02/2014 04:41:22.11 External Power Supply in slot 2 is present.

11/02/2014 04:41:22.11 Input voltage to Internal Power Supply in slot 2 is on. Output enabled.

11/02/2014 04:41:22.11 Internal Power Supply in slot 2 is present.

RE: Switch rebooted,Working fine.

Ravisekar__Raja — Sun, 02 Nov 2014 21:19:00 GMT

Hi,

Check the syslog and read the logs exactly befor for the restart. Reason for restart should be power disturbance, process crash log, any loose connections. Check in internal memory that whether you have any core dump file which will be generated during process crash log.

RE: Switch rebooted,Working fine.

ComraDe — Sun, 02 Nov 2014 21:19:00 GMT

Thanks Ravi....

RE: Switch rebooted,Working fine.

PARTHIBAN_CHINN — Mon, 03 Nov 2014 01:09:00 GMT

Show debug system-dump Show log messages nvram The above two commands will tell Us if the switch rebooted due to core dump or Hardware errors if any. Could you paste the outputs of these two commands ?

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 01:33:00 GMT

Whether it will affect any traffic..while executing i mean...?

RE: Switch rebooted,Working fine.

PARTHIBAN_CHINN — Mon, 03 Nov 2014 10:19:00 GMT

These commands are not service impacting.

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 11:04:00 GMT

> show debug system-dump ===============================================

Slot-1 system dump information

===============================================

core_dump_info storage: 8/3072 used [empty]

failure: kernel oops

reason: Oops

time: Wed Dec 19 04:27:02 2012

where: Oops:0

$0 : z0=00000000 at=10001f00 v0=c2bbf104 v1=00000000

$4 : a0=00000000 a1=20000000 a2=806f9f18 a3=c2f24f44

$8 : t0=02000000 t1=00010000 t2=8010c398 t3=00000004

$12: t4=7fff6bb8 t5=00000003 t6=00022000 t7=00000000

$16: s0=0000000b s1=c2bbf52c s2=0001869f s3=c3479dd0

$20: s4=00000000 s5=c3149a10 s6=c3479dd0 s7=c3149ac0

$24: t8=00000000 t9=c277f7fc

$28: gp=806f8000 sp=806f9f18 s8=c347ba0c ra=c2bc09cc

Hi : 00000025

Lo : 999999a3

epc : c277f800 rpacket_setup+0x3b4/0xb14 [linux_bcm_diag_full] Tainted: P

Status: 10001f02

Cause : 00808008

806f9f18: 00000000 c2f24f44 02458c5e 2661b7b9 02458c5e 00000000 02458c5e 00000001

806f9f38: 8342b7e0 00000000 00000039 00000001 00000000 fffffbff 81201138 87067684

806f9f58: 00000000 c160c130 30001f03 001da342 015af470 00001ce0 8ee85da0 801692c4

806f9f78: 00000000 804b57c0 00000002 804b57f4 804b6c60 00000039 804b6c94 8342b7e0

806f9f98: 80710000 801694e0 00000000 00000000 00000000 00000000 00000000 806f9fd0

806f9fb8: 2ac78000 00400000 87067680 81201138 ffffffbf 80107138 00000000 00000000

806f9fd8: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 806f8000

806f9ff8: 88359c70 80108bc0 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa018: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa038: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa058: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa078: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa098: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa0b8: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa0d8: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

806fa0f8: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad

log: ... iled, (error -15)

log: <1>CPU 0 Unable to handle kernel paging request at virtual address 20000260, epc == c277f800, ra == c2bc09cc

Version #1 SMP Tue Apr 26 20:09:50 PDT 2 by release-manager@biltsurf.extrem Release 2.6.28.9cougar

Call Trace:

@[] rpacket_setup+0x3b4/0xb14 [linux_bcm_diag_full]

[] gmodule_get+0x130/0x1d0 [linux_kernel_bde]

Build directory: /home/release-manager/v12_5_3_9/cougar

--------------------------------

Kernel Panic.

time: Wed Dec 19 04:27:04 2012

Reason: Fatal exception in interrupt

Caller: 0x8010d6b4 (die+0x124/0x144)

Version #1 SMP Tue Apr 26 20:09:50 PDT 2 by release-manager@biltsurf.extrem Release 2.6.28.9cougar

Build directory: /home/release-manager/v12_5_3_9/cougar

> show log messages nvram

11/03/2014 02:00:30.78 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 02:00:28.78 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 02:00:26.55 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 02:00:24.47 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 02:00:21.60 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:20.22 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:18.21 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:16.20 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:15.89 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:14.13 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:13.88 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:12.10 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:11.87 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:09.86 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:07.85 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:04.07 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:02.06 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:58:00.05 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:57:58.04 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:57:56.04 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:57:36.07 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:57:34.07 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:57:32.00 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:57:29.97 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:57:27.96 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:15.35 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:13.34 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:11.33 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:10.90 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:09.32 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:08.85 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:08.20 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:07.32 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:06.84 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:06.13 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:04.40 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:04.12 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:02.32 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:56:02.01 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:55:59.64 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:55:21.54 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:55:19.54 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:55:17.49 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:55:15.48 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:55:13.42 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:51:08.68 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:51:06.67 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:51:04.67 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:51:02.62 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:51:00.62 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:25.31 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:23.32 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:21.30 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:20.36 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:19.28 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:18.34 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:17.28 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:16.34 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:14.28 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:12.28 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:11.65 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:09.63 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:07.62 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:05.61 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:48:03.60 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:47:34.48 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:47:32.46 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:47:30.44 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:47:28.43 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:47:26.42 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:21.14 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:19.91 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:19.10 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:17.86 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:17.10 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:15.86 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:15.06 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:13.80 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:12.96 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:11.78 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:11.65 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:08.99 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:06.98 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:04.97 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:46:02.91 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:45:21.71 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:45:19.70 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:45:17.68 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:45:15.66 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:45:13.65 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:40:32.22 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:40:30.21 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:40:28.16 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:40:26.13 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:40:24.09 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:27.96 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:25.92 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:23.91 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:22.53 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:21.90 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:20.87 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:20.53 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:19.89 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:18.87 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:18.53 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:16.86 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:16.51 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:14.85 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:14.50 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:38:12.84 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:37:38.45 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:37:36.41 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:37:34.40 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:37:32.40 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:37:30.38 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:36:27.97 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:36:25.97 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:36:23.97 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:36:21.95 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:36:19.83 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:36:15.17 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

11/03/2014 01:36:13.14 Login failed through SNMPv1/v2c - bad community name (10.111.12.151)

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 11:40:00 GMT

Hi Parthiban,Please note that my switches in stack and the slot 2 got rebooted...

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 13:00:00 GMT

Hi ,

I have been thinking that the logs which i have shared above is from Slot 1....Since its on stack how do i get the logs from slot 2..???

RE: Switch rebooted,Working fine.

PARTHIBAN_CHINN — Mon, 03 Nov 2014 13:25:00 GMT

Log in to slot 1 from the cli telnet slot 2 Then u should be able to run same commands Also if you know the time stamp for reboot Please collect show log match time stamp

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 13:26:00 GMT

===============================================

Slot-2 system dump information

===============================================

core_dump_info storage: 8/3072 used [empty]

--------------------------------

System memory depleted.

time: Sun Nov 2 04:32:52 2014

Global Memory Stats:

MemTotal: 254656 kB

MemFree: 2036 kB

Buffers: 16 kB

Cached: 6120 kB

Active(anon): 84272 kB

Inactive(anon): 84324 kB

Active(file): 2896 kB

Inactive(file): 2964 kB

HighTotal: 0 kB

HighFree: 0 kB

LowTotal 254656 kB

LowFree: 2036 kB

Committed_AS: 937060 kB

Top Processes by RSS:

cliMaster: 34632 kB

snmpMaster: 74800 kB

hal: 11828 kB

etmon: 3596 kB

xmld: 2676 kB

epm: 1172 kB

emsServer: 1888 kB

cfgmgr: 1412 kB

snmpSubagent: 1436 kB

vlan: 1496 kB

fdb: 1260 kB

eaps: 1716 kB

rtmgr: 1232 kB

mcmgr: 1484 kB

bgp: 1552 kB

acl: 1032 kB

Top Slab Caches by Memory Consumption:

size-512: 4632 kB

size-524288: 2048 kB

size-8192: 2208 kB

jffs2_refblock: 1684 kB

skbuff_head_cache: 1844 kB

size-262144: 1280 kB

size-131072: 1024 kB

size-65536: 832 kB

UNIX: 644 kB

filp: 684 kB

size-2048: 664 kB

sock_inode_cache: 636 kB

dentry: 592 kB

vm_area_struct: 516 kB

size-32768: 384 kB

size-1024: 424 kB

--------------------------------

System memory depleted.

time: Sun Nov 2 04:32:59 2014

Global Memory Stats:

MemTotal: 254656 kB

MemFree: 1976 kB

Buffers: 16 kB

Cached: 6124 kB

Active(anon): 83508 kB

Inactive(anon): 83568 kB

Active(file): 2920 kB

Inactive(file): 3044 kB

HighTotal: 0 kB

HighFree: 0 kB

LowTotal 254656 kB

LowFree: 1976 kB

Committed_AS: 937060 kB

Top Processes by RSS:

cliMaster: 34632 kB

snmpMaster: 74800 kB

hal: 11820 kB

etmon: 3596 kB

xmld: 2676 kB

epm: 1172 kB

emsServer: 1888 kB

cfgmgr: 1412 kB

snmpSubagent: 1436 kB

vlan: 1496 kB

fdb: 1260 kB

eaps: 1716 kB

rtmgr: 1232 kB

mcmgr: 1484 kB

bgp: 1552 kB

acl: 1032 kB

Top Slab Caches by Memory Consumption:

size-512: 4676 kB

size-524288: 2048 kB

size-8192: 2208 kB

jffs2_refblock: 1684 kB

skbuff_head_cache: 1852 kB

size-262144: 1280 kB

size-131072: 1024 kB

size-65536: 832 kB

UNIX: 644 kB

filp: 684 kB

size-2048: 660 kB

sock_inode_cache: 636 kB

dentry: 592 kB

vm_area_struct: 516 kB

size-32768: 384 kB

size-1024: 424 kB

--------------------------------

System memory depleted.

time: Sun Nov 2 04:33:04 2014

Global Memory Stats:

MemTotal: 254656 kB

MemFree: 1976 kB

Buffers: 16 kB

Cached: 6124 kB

Active(anon): 83380 kB

Inactive(anon): 86128 kB

Active(file): 3036 kB

Inactive(file): 3084 kB

HighTotal: 0 kB

HighFree: 0 kB

LowTotal 254656 kB

LowFree: 1976 kB

Committed_AS: 937060 kB

Top Processes by RSS:

cliMaster: 34632 kB

snmpMaster: 74800 kB

hal: 11820 kB

etmon: 3596 kB

xmld: 2676 kB

epm: 1172 kB

emsServer: 1888 kB

cfgmgr: 1412 kB

snmpSubagent: 1436 kB

vlan: 1496 kB

fdb: 1260 kB

eaps: 1716 kB

rtmgr: 1232 kB

mcmgr: 1484 kB

bgp: 1552 kB

acl: 1032 kB

Top Slab Caches by Memory Consumption:

size-512: 4720 kB

size-524288: 2048 kB

size-8192: 2208 kB

jffs2_refblock: 1684 kB

skbuff_head_cache: 1876 kB

size-262144: 1280 kB

size-131072: 1024 kB

size-65536: 832 kB

UNIX: 644 kB

filp: 684 kB

size-2048: 660 kB

sock_inode_cache: 636 kB

dentry: 592 kB

vm_area_struct: 516 kB

size-32768: 384 kB

size-1024: 424 kB

RE: Switch rebooted,Working fine.

PARTHIBAN_CHINN — Mon, 03 Nov 2014 13:58:00 GMT

Hello it looks like memory depletion. Stop unnecessary snmp polling to the switch. Add ACL to allow snmp access from specifi source. From the logs there is lot of snmp failures. From show memory it's clear that snmp process is high. For a temporary workaround you can restart Process snmpmaster ... The reboot will occur only when free memory goes below 20 mb.

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 14:02:00 GMT

Does it have any permenent solution..?

Adding ACL would help to resolve the issue..?

RE: Switch rebooted,Working fine.

PARTHIBAN_CHINN — Mon, 03 Nov 2014 14:18:00 GMT

Yes we can get a permanent solution . We have to raise this issue to tac . Show tech all Show memory ( 5 times) With one hour interval

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 16:51:00 GMT

Hi Parthiban,

There is a doubt in this.......

You have mentioned if the memory free goes below 20 MB it will get rebooted.As per the below log the free memory is 2MB...and SNMP process hitting 74 MB......so how it will affect now....reboot again...

Stats: MemTotal: 254656 kB

MemFree: 2036 kB

Buffers: 16 kB

Cached: 6120 kB

Active(anon): 84272 kB

Inactive(anon): 84324 kB

Active(file): 2896 kB

Inactive(file): 2964 kB

HighTotal: 0 kB

HighFree: 0 kB

LowTotal 254656 kB

LowFree: 2036 kB

Committed_AS: 937060 kB

Top Processes by RSS:

cliMaster: 34632 kB

snmpMaster: 74800 kB

RE: Switch rebooted,Working fine.

PARTHIBAN_CHINN — Mon, 03 Nov 2014 18:10:00 GMT

Less than 20 mb there will be alert when it hits 2 mb it will reboot

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 18:10:00 GMT

I have configured all my SNMP configurations on slot 1 then why slot 2 hitting high on SNMP process and reboot..?...Can you help me here...

RE: Switch rebooted,Working fine.

ComraDe — Mon, 03 Nov 2014 18:25:00 GMT

Thanks for your prompt reply...Let me check whether i can restrict SNMP by using ACL and restart the process....

RE: Switch rebooted,Working fine.

ComraDe — Wed, 05 Nov 2014 19:06:00 GMT

I have configured all my SNMP configurations on slot 1 then why slot 2 hitting high on SNMP process and reboot..?...Can anybody help me here...

RE: Switch rebooted,Working fine.

PARTHIBAN_CHINN — Wed, 05 Nov 2014 19:38:00 GMT

There are reasons for snmpmaster process high . I would suggest to open a tac case for this issue to be investigated