Was actually looking at the IOS software when I received this. Here is the
version information. This version of IOS was provided by cisco on a replacement
set of memory chips(bad memory when this unit was shipped to us). Telco check
is next... lord knows they are not the most together set of individuals up
here.
It was however the tracebacks that raised a flag with me and started my on the
IOS route... Any newer software versions that are more stable and should be
upgraded to?
Here is the sh ver output
Cisco Internetwork Operating System Software
IOS (tm) 5300 Software (C5300-I-M), Version 12.1(5)T5, RELEASE SOFTWARE (fc1)
TAC Support: http://www.cisco.com/cgi-bin/ibld/view.pl?i=support
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 26-Feb-01 18:06 by ccai
Image text-base: 0x60008958, data-base: 0x6091E000
ROM: System Bootstrap, Version 12.0(2)XD1, EARLY DEPLOYMENT RELEASE SOFTWARE
(fc1)
BOOTFLASH: 5300 Software (C5300-BOOT-M), Version 12.0(4)T1, RELEASE SOFTWARE
(fc1)
as0 uptime is 4 hours, 16 minutes
System returned to ROM by reload at 06:24:24 EDT Thu Aug 2 2001
System restarted at 06:24:59 EDT Thu Aug 2 2001
System image file is "flash:2:c5300-i-mz.121-5.T5"
cisco AS5300 (R4K) processor (revision A.32) with 65536K/16384K bytes of memory.
Processor board ID 24710079
R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache
Bridging software.
X.25 software, Version 3.0.0.
Primary Rate ISDN software, Version 1.1.
Backplane revision 2
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x30,
Board Hardware Version 3.2, Item Number 800-2544-04,
Board Revision B0, Serial Number 24710079,
PLD/ISP Version 0.0, Manufacture Date 25-Feb-2001.
1 Ethernet/IEEE 802.3 interface(s)
1 FastEthernet/IEEE 802.3 interface(s)
52 Serial network interface(s)
48 terminal line(s)
8 Channelized T1/PRI port(s)
128K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash partition 1 (Read/Write)
8192K bytes of processor board System flash partition 2 (Read/Write)
4096K bytes of processor board Boot flash (Read/Write)
Configuration register is 0x2102
>-----Original Message-----
>From: Young, Jason [mailto:Jason.Young@anheuser-busch.com]
>Sent: Thursday, August 02, 2001 9:48 AM
>To: 'Dave'; cisco-nsp@puck.nether.net
>Subject: RE: [nsp] configuring 2 D channels(T1) for 2 or more T1's on
>as5300
>
>
>
>Your config looks reasonable to me. Either the telco has not set it up
>with NFAS
>at all or NFAS the way you expected (which is a very real and common
>possibility), or your version of IOS is broken in this regard (which is also
>possible, considering the tracebacks).
>
>You should not expect to see a Serial1:23 interface. A NFAS group is treated as
>exactly one configurable element, controlled by a single D channel. You don't
>need to configure the backup D channel. It assumes the same config as the
>primary if it becomes active.
>
>If you want further troubleshooting help, send us a "show version"
>output. Also,
>send the output of "debug isdn events" and "debug isdn q931" as these PRIs are
>coming up with the NFAS config - i.e., shut down the PRIs, turn those
>debugs on,
>reconfigure them, no shut them and record the output.
>
>You may want to open a TAC case and ask about those tracebacks. It's generally
>not a good thing to be getting tracebacks. You may be running a
>bleeding-edge or
>broken IOS that you shouldn't be.
>
>Jason Young
>CNS - Network Design, Anheuser-Busch
>(314)577-4597
>
>
>
>> -----Original Message-----
>> From: Dave [mailto:dave@nexusinternetsolutions.net]
>> Sent: Thursday, August 02, 2001 5:42 AM
>> To: Young, Jason; cisco-nsp@puck.nether.net
>> Subject: RE: [nsp] configuring 2 D channels(T1) for 2 or more T1's on
>> as5300
>>
>>
>> Problem being experienced is when we switch from standard to
>> nfas we lose dialup
>> connecticity... ie the as5300 no longer responds to calls.
>>
>> We are not getting a d channel interface (serial 1:23)
>> created for the second
>> t1, and in reverting back to the original (potentially
>> seperate or related
>> issue) we received the following
>>
>> Aug 2 06:22:26.966 EDT: %CSM-5-PRI: delete PRI at slot 0,
>> unit 0, channel 23
>> with index 0i timeslots 1-
>> Aug 2 06:22:41.470 EDT: %ALIGN-3-SPURIOUS: Spurious memory
>> access made at
>> 0x600C1D00 reading 0x11DA
>> Aug 2 06:22:41.470 EDT: %ALIGN-3-TRACE: -Traceback= 600C1D00 600C01B0
>> 60022F086001B82C 60017A5C 60019700 6001B304 602E376C
>> Aug 2 06:22:41.470 EDT: %ALIGN-3-TRACE: -Traceback= 600C1D04 600C01B0
>> 60022F086001B82C 60017A5C 60019700 6001B304 602E376C24
<clipped>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:48 EDT