From: Greg Wendel (gwendel@gmail.com)
Date: Fri Dec 28 2007 - 16:22:49 ART
Clay,
Yes here is another example of the crash. As you can see a ping causes a
crash. I sent the data to the Cisco Output interpreter but it just gave a
couple of unrelated bugs. The RP mapping agent is running the same code on
the same device without any problems.
Rack1SW1#sh ip pim rp map
PIM Group-to-RP Mappings
Group(s) 225.0.0.0/8
RP 150.1.2.2 (?), v2v1
Info source: 150.1.8.8 (?), elected via Auto-RP
Uptime: 00:00:03, expires: 00:02:52
Rack1SW1#
Rack1SW1#sh ip mroute 225.25.25.25
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 225.25.25.25), 01:28:11/00:02:21, RP 150.1.2.2, flags: SJPC
Incoming interface: GigabitEthernet1/0/3, RPF nbr 141.1.37.3
Outgoing interface list: Null
Rack1SW1#
01:29:34: IP(0): s=150.1.8.8 (GigabitEthernet1/0/3) d=224.0.1.40 id=33079,
ttl=13, prot=17, len=74(60), mroute olist null
Rack1SW1#ping 225.25.25.25
01:29:39 UTC Mon Mar 1 1993: Unexpected exception to CPUvector 2000, PC =
47AF8C
-Traceback= 47AF8C 47AFAC A45544 E2B030 E1B27C DB0A94 DB1998 D9F63C D9E42C
D9E690 D9E954 9A37D8 99ADC4
Writing crashinfo to flash:/crashinfo_ext/crashinfo_ext_5
On Dec 28, 2007 2:12 PM, Clay K Auch (clauch) <clauch@cisco.com> wrote:
>
> Did you have an (S,G) entry when you attempted to ping the group?
>
> Clay
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Greg Wendel
> Sent: Friday, December 28, 2007 11:25 AM
> To: Cisco certification
> Subject: Multicast AutoRP over sparse mode causes 3750 crash
>
> While working on Internetwork Expert lab 4 I enabled ip pim sparse mode
> along with the ip pim auto-rp listener command. After that a simple show
> statement caused the 3750 to crash. The version of code is 12.2(35)SE2 .
> Has anyone seen anything similar to the output below?
>
>
>
> Rack1SW1#sh ip auto
>
> Rack1SW1#sh ip pim auto
>
> Rack1SW1#sh ip pim autorp
>
> AutoRP Information:
>
> AutoRP is enabled.
>
>
>
> PIM AutoRP Statistics: Sent/Received
>
> RP Announce: 0/0, RP Discovery: 0/8
>
> Rack1SW1#conf t
>
> Enter configuration commands, one per line. End with CNTL/Z.
>
> Rack1SW1(config)#ip pim auto
>
> Rack1SW1(config)#ip pim autorp lis
>
> Rack1SW1(config)#ip pim autorp listener
>
> Rack1SW1(config)#end
>
> Rack1SW1#sh ip pim autorp
>
> 10:19:51: %SYS-5-CONFIG_I: Configured from console by console
>
> *Rack1SW1#sh ip pim autorp*
>
> AutoRP Information:
>
> AutoRP is enabled.
>
> AutoRP groups over sparse mode interface is enabled
>
>
>
> PIM AutoRP Statistics: Sent/Received
>
> RP Announce: 0/0, RP Discovery: 0/8
>
> Rack1SW1#sh ip pim rp
>
> Group: 225.25.25.25, RP: 150.1.2.2, v2, v1, uptime 00:07:26, expires
> 00:02:26
>
> Rack1SW1#ping 225.25.25.25
>
>
>
>
>
>
>
> 10:20:04 UTC Mon Mar 1 1993: Unexpected exception to CPUvector 2000, PC =
> 47AF8C
>
> -Traceback= 47AF8C 47AFAC A45544 E2B030 E1B27C DB0A94 DB1998 D9F63C D9E42C
> D9E690 D9E954 9A37D8 99ADC4
>
>
>
> Writing crashinfo to flash:/crashinfo_ext/crashinfo_ext_1
>
>
>
> === Flushing messages (10:20:07 UTC Mon Mar 1 1993) ===
>
>
>
> Buffered messages:
>
> ht (c) 1986-2007 by Cisco Systems, Inc.
>
> Compiled Tue 06-Feb-07 05:07 by antonino
>
> 00:00:59: %LINK-5-CHANGED: Interface GigabitEthernet1/0/16, changed state
> to administratively down
>
> 00:00:59: %LINK-5-CHANGED: Interface GigabitEthernet1/0/17, changed state
> to administratively down
>
> 00:00:59: %LINK-5-CHANGED: Interface GigabitEthernet1/0/18, changed state
> to administratively down
>
> 00:00:59: %LINK-5-CHANGED: Interface Vlan1, changed state to
> administratively down
>
> 00:01:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/3, changed state to up
>
> 00:01:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/5, changed state to up
>
> 00:01:02: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to
> up
>
> 00:01:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to
> up
>
> 00:01:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state
> to up
>
> 00:01:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/14, changed state
> to up
>
> 00:01:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state
> to up
>
> 00:01:04: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state
> to up
>
> 00:01:04: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state
> to up
>
> 00:01:04: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/21, changed state
> to up
>
> 00:01:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/13, changed state to up
>
> 00:01:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/14, changed state to up
>
> 00:01:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/15, changed state to up
>
> 00:01:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/20, changed state to up
>
> 00:01:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/19, changed state to up
>
> 00:01:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/21, changed state to up
>
> 00:01:06: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to
> up
>
> 00:01:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/1, changed state to up
>
> 00:01:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan7, changed
> state to up
>
> 00:01:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan77, changed
> state to up
>
> 00:01:41: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on
> GigabitEthernet1/0/3 (not full duplex), with Rack1R3 FastEthernet0/0 (full
> duplex).
>
> 00:02:41: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on
> GigabitEthernet1/0/3 (not full duplex), with Rack1R3 FastEthernet0/0 (full
> duplex).
>
> 00:03:41: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on
> GigabitEthernet1/0/3 (not full duplex), with Rack1R3 FastEthernet0/0 (full
> duplex).
>
> 00:04:41: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on
> GigabitEthernet1/0/3 (not full duplex), with Rack1R3 FastEthernet0/0 (full
> duplex).
>
> 00:05:04: PSECURE: Assert failure: 0: ../switch/psecure/psecure_ifc.c:
> 291:
> psecure_get_vlanid
>
> 00:05:04: -Traceback= 7BAEDC 7BF89C 7B8CDC 7BD0A0 756044 7661E0 350CE8
> C12494 C2E55C 9A37D8 99ADC4
>
> 00:05:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/3, changed state to down
>
> 00:05:06: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to
> down
>
> 00:05:28: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to
> up
>
> 00:05:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet1/0/3, changed state to up
>
> 00:05:42: %SYS-5-CONFIG_I: Configured from console by console
>
> 00:38:29: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 141.1.37.7 on
> interface GigabitEthernet1/0/3 (vrf default)
>
> 00:38:30: %SYS-5-CONFIG_I: Configured from console by console
>
> 00:38:30: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 141.1.7.7 on
> interface Vlan7 (vrf default)
>
> 00:38:57: %PIM-5-NBRCHG: neighbor 141.1.37.3 UP on interface
> GigabitEthernet1/0/3 (vrf default)
>
> 00:49:36: %PIM-5-NBRCHG: neighbor 141.1.37.3 DOWN on interface
> GigabitEthernet1/0/3 (vrf default) non DR
>
> 09:47:25: %PIM-5-NBRCHG: neighbor 141.1.37.3 UP on interface
> GigabitEthernet1/0/3 (vrf default)
>
> 10:19:51: %SYS-5-CONFIG_I: Configured from console by console
>
> Queued messages:
>
> Cisco IOS Software, C3750 Software (C3750-ADVIPSERVICESK9-M), Version 12.2(35)SE2,
> RELEASE SOFTWARE (fc1)
>
> Copyright (c) 1986-2007 by Cisco Systems, Inc.
>
> Compiled Tue 06-Feb-07 05:07 by antonino
>
>
>
> Debug Exception (Could be NULL pointer dereference) Exception (0x2000)!
>
> SRR0 = 0x0115DC00 SRR1 = 0x00029210 SRR2 = 0x0064C334 SRR3 = 0x00021000
>
> ESR = 0x00000000 DEAR = 0x00000000 TSR = 0x8C000000 DBSR = 0x01000000
>
>
>
> CPU Register Context:
>
> Vector = 0x00002000 PC = 0x0047AF8C MSR = 0x00029210 CR = 0x33000098
>
> LR = 0x0047AFAC CTR = 0x00A451D0 XER = 0xE0000000
>
> R0 = 0x00A45544 R1 = 0x0306AB48 R2 = 0x00000000 R3 = 0x00000000
>
> R4 = 0x00000000 R5 = 0x0306AB58 R6 = 0x00000000 R7 = 0x0002BF20
>
> R8 = 0x00000000 R9 = 0x01F20000 R10 = 0x01FB446C R11 = 0x00000044
>
> R12 = 0x000E1F0E R13 = 0x00010000 R14 = 0x00D9E824 R15 = 0x0306AB78
>
> R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x01F20000
>
> R20 = 0x00000000 R21 = 0x0381EF4C R22 = 0x00000000 R23 = 0x00000001
>
> R24 = 0x03C36F54 R25 = 0x021D2F34 R26 = 0x00000064 R27 = 0x07400080
>
> R28 = 0x0000F00E R29 = 0x021D2F34 R30 = 0x039BE9DC R31 = 0x03A1D7D0
>
>
>
> Stack trace:
>
> PC = 0x0047AF8C, SP = 0x0306AB48
>
> Frame 00: SP = 0x0306AB50 PC = 0x03A1D7D0
>
> Frame 01: SP = 0x0306AB70 PC = 0x00A45544
>
> Frame 02: SP = 0x0306ABC8 PC = 0x00E2B030
>
> Frame 03: SP = 0x0306ABF8 PC = 0x00E1B27C
>
> Frame 04: SP = 0x0306AC20 PC = 0x00DB0A94
>
> Frame 05: SP = 0x0306AC70 PC = 0x00DB1998
>
> Frame 06: SP = 0x0306AC90 PC = 0x00D9F63C
>
> Frame 07: SP = 0x0306ACE0 PC = 0x00D9E42C
>
> Frame 08: SP = 0x0306AD08 PC = 0x00D9E690
>
> Frame 09: SP = 0x0306AD40 PC = 0x00D9E954
>
> Frame 10: SP = 0x0306AD48 PC = 0x009A37D8
>
> Frame 11: SP = 0x00000000 PC = 0x0099ADC4
>
>
>
>
>
> Rack1SW1 uptime is 10 hours, 20 minutes, 14 seconds
>
>
>
> cisco WS-C3750G-24T (PowerPC405) processor (revision E0) with
> 118784K/12280K bytes of memory.
>
> Processor board ID CAT0834R22Q
>
>
>
>
>
> Base ethernet MAC Address: 00:12:00:73:5b:00
>
> Xmodem file system is available.
>
> The password-recovery mechanism is enabled.
>
> Initializing Flash...
>
> flashfs[0]: 5 files, 2 directories
>
> flashfs[0]: 0 orphaned files, 0 orphaned directories
>
> flashfs[0]: Total bytes: 15998976
>
> flashfs[0]: Bytes used: 9011200
>
> flashfs[0]: Bytes available: 6987776
>
> flashfs[0]: flashfs fsck took 8 seconds.
>
> ...done Initializing Flash.
> ...................
>
> --
> Gregory Wendel
> Springfield VA, 22153
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Gregory Wendel Springfield VA, 22153
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:32 ARST