3550-EMI crashs with PIM on VLAN

Aug 29, 2005 3 Replies
3550-EMI crashs with PIM on VLAN open original image

I wonder if the 3550er is able to work as a multicast router on a vlan. The C3550-I5Q3L2-M (Version 12.1(13)EA1c) image crashs with "Unassigned Exception (0xAC1B1C48)!, PC 0x21EE74"



Relevant config: interface f0/X description Customer port switchport switchport mode access switchport access vlan Y ! interface f0/V description IPv6 router switchport switchport mode trunk switchport trunk allowed vlan Y,... ! interface vlan Y ip address 192.168.0.1/30 ip pim ip sap listen !



It worked fine with f0/X as a router port (without vlan), but the vlan was necessary to provide IPv6 to the customer. The IPv6 router is v6 only.



Any idea? Should I disable IGMP snooping on the vlan Y?


Does not help. After six hours ... crashed again:

Cisco Internetwork Operating System Software IOS (tm) C3550 Software (C3550-I5Q3L2-M), Version 12.1(13)EA1c, RELEASE SOFTWARE (fc1) Copyright (c) 1986-2003 by cisco Systems, Inc. Compiled Tue 24-Jun-03 18:49 by yenanh

Unassigned Exception (0xA0000CB)! CPU Register Context: Vector = 0x0A0000CB PC = 0x0021EE74 MSR = 0x40089030 CR = 0x44000048 LR = 0x006B1A74 CTR = 0x001B7938 XER = 0x20000000 R0 = 0x08000048 R1 = 0x01000820 R2 = 0x00000000 R3 = 0x00001100 R4 = 0xFFFFFFFF R5 = 0xD911C50E R6 = 0x00000000 R7 = 0x00033450 R8 = 0x00EF1C68 R9 = 0x7C020378 R10 = 0x00F0081C R11 = 0x00020340 R12 = 0x22000048 R13 = 0xEC4496A0 R14 = 0x00000000 R15 = 0x00000000 R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000 R20 = 0x009C0000 R21 = 0x00B50000 R22 = 0x00000001 R23 = 0xD911C50E R24 = 0x00B50000 R25 = 0x00B50000 R26 = 0x00033450 R27 = 0xFFFFFFFF R28 = 0x010A6FCC R29 = 0x0A0000CB R30 = 0x00000001 R31 = 0x01000910

Stack trace: PC = 0x0021EE74, SP = 0x01000820 Frame 00: SP = 0x01000908 PC = 0x006B1A5C Frame 01: SP = 0x01000970 PC = 0x006CAF24 Frame 02: SP = 0x010009C0 PC = 0x006CC0E8 Frame 03: SP = 0x010009E0 PC = 0x006AA908 Frame 04: SP = 0x00000000 PC = 0x001C6440

Hi,

Cisco's output interpreter recognises it as a software problem and gives a probable bug ID with a 90% match - however the bug ID related to server load balancing so it may not be 100% right.

Are you able to upgrade the IOS to a newer version, say 12.3(9) or 12.3(10) as recommended by the Bug ID?

Regards,

Nick Ersdown

formatting link

I'll try it. Thanx.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required