[nsp] router reboots due to bus error

[Josh Duffek]

Look in the "sh region" for 0x104 and see if it is in there.  If not then it
is probably a software error.  I'm not the best person to talk to about bus
errors so you should probably read up here:
http://www.cisco.com/warp/public/122/crashes_buserror_troubleshooting.shtml
...or open a TAC case, incase you determine it is a hardware problem then
you could get the RMA done right then.

joshd.

----- Original Message -----
From: "Drix Tabligan" <drix@pilnet.com>
To: <cisco-nsp@puck.nether.net>
Sent: Tuesday, November 12, 2002 2:02 AM
Subject: [nsp] router reboots due to bus error


> Hi, I'm new at this...
>
> I have an existing setup shown below:
>
>
>                                       [internet2]
>                                              |
> [internet1]-a-[router1] -b-[router2]-c-[router3]---[app servers]
>                                              |                  |
>                                              |           [internet3]
>                                              |
>                                      [app servers]
>
> Router1 - Cisco7513 / RSP4 Version 12.1(8a)E IOS
> Router2 - Cisco7200 / NPE200 Version 12.2(6b) IOS
> Router3 - Cisco7576 / RSP2 Version 12.2(6a) IOS
>
> All three routers are in different locations with their own corresponding
> internet connections. All are running BGP within and with the Internet
using
> our own portable address /19 space for the whole network. No fancy
> configurations and standard v.35 serial interfaces, Fast Ethernets and
> Ethernets. Links "a" and "b" are stable. Link "c" has medium probability
of
> failure. In order to address the problem, I tried to configure a GRE
tunnel
> from "router3" via "internet3" to "router2" via "internet2". Source and
> destination addresses are the interface addresses given by our upstream
> providers. Tunnel comes up ok with both sides of the connection showing
> "Tunnel up Protocol up". After assigning ip addresses to both ends of the
> connection, pinging the ip address of the other end causes "router3" to
> reboot. Reason for reboot "System returned to ROM by bus error at PC
> 0x603B3884, address 0x104". Is this any known bug on the IOS for
"router3".
> I'm nearing the situation where I might be upgrading IOS for "router3" in
> order to see if it will solve the problem. Any help would be greatly
> appreciated or suggestions on what version of IOS to upgrade to would be
> great also.
>
> Thanks in advance.
>
> Drix Tabligan
> XcelerateCenter.com
>
>
>
>
>
> _______________________________________________
> cisco-nsp mailing list  real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>