Mailing List Archive: Cisco: NAS

[Fwd: Re: Modems not responding on cisco AS5300.]

Index | Next | Previous | View Threaded

Aaron at cisco

Aug 26, 2008, 8:25 AM

Post #1 of 13 (4600 views)
Permalink

[Fwd: Re: Modems not responding on cisco AS5300.]

Oh yeah - CSCsi638651, which we never did figure out. Actually,
anything in 12.3(6x) and before should be good.

Aaron

-------- Original Message --------
Subject: Re: [cisco-nas] Modems not responding on cisco AS5300.
Date: Tue, 26 Aug 2008 10:20:58 +0800
From: Mark Tinka <mtinka [at] globaltransit>
Reply-To: mtinka [at] globaltransit
Organization: Global Transit International
To: cisco-nas [at] puck
CC: Aaron Leonard <Aaron [at] cisco>, Joseph Mays <mays [at] win>, Mike
Andrews <mandrews [at] bit0>
References: <081301c906e2$03cf90c0$0a2118d8 [at] engineering0>
<0b1301c9070d$87bc8ca0$0a2118d8 [at] engineering0> <48B34BE2.7080902 [at] Cisco>

On Tuesday 26 August 2008 08:18:42 Aaron Leonard wrote:

> In any case, the guidance below is still generally
> applicable - i.e. run latest code (2.9.5.0); turn on
> modem recovery.

You also want to run an IOS revision no later than 12.3(5)f.

Anything more recent than this will continuously cause your
modems to go into a BAD state.

Cheers,

Mark.

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

mays at win

Aug 26, 2008, 8:55 AM

Post #2 of 13 (4501 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

The boxes are all running 12.3(16). I'm using the built-in system firmware for the modems. I suppose for the sake of completeness I will include the show ver, show diag and and show run output.

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

as5300_frv_1#show ver
Cisco Internetwork Operating System Software
IOS (tm) 5300 Software (C5300-IS-M), Version 12.3(16), RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 23-Aug-05 19:39 by ssearch
Image text-base: 0x60008AEC, data-base: 0x6161C000

ROM: System Bootstrap, Version 12.0(2)XD1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
BOOTLDR: 5300 Software (C5300-BOOT-M), Version 12.0(4)T1, RELEASE SOFTWARE (fc1)

as5300_frv_1 uptime is 22 hours, 12 minutes
System returned to ROM by reload at 23:33:28 EDT Tue Apr 26 2005
System image file is "flash:c5300-is-mz.123-16.bin"

cisco AS5300 (R4K) processor (revision A.32) with 131072K/16384K bytes of memory.
Processor board ID 21246024
R4700 CPU at 150MHz, Implementation 33, Rev 1.0, 512KB L2 Cache
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
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.1, Item Number 800-2544-03,
Board Revision D0, Serial Number 21246024,
PLD/ISP Version 0.0, Manufacture Date 6-Jul-2000.
1 Ethernet/IEEE 802.3 interface(s)
1 FastEthernet/IEEE 802.3 interface(s)
96 Serial network interface(s)
102 terminal line(s)
4 Channelized T1/PRI port(s)
128K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)
8192K bytes of processor board Boot flash (Read/Write)

Configuration register is 0x2102

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

as5300_frv_1#show diag
Motherboard Info:
Backplane revision 2
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x30,
Board Hardware Version 3.1, Item Number 800-2544-03,
Board Revision D0, Serial Number 21246024,
PLD/ISP Version 0.0, Manufacture Date 6-Jul-2000.
EEPROM format version 0
EEPROM contents (hex):
0x00: 00 01 01 30 03 01 03 20 00 09 F0 03 44 00 32 31
0x10: 32 34 36 30 32 34 00 00 00 00 00 00 00 00 14 00
0x20: 07 06 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FRU NUMBER : AS5300

Slot 0:
Hardware is Quad T1 PRI CSU, 4 ports
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x42,
Board Hardware Version 1.32, Item Number 73-2217-05,
Board Revision B16, Serial Number 09947892,
PLD/ISP Version 0.0, Manufacture Date 15-Sep-1998.
EEPROM format version 0
EEPROM contents (hex):
0x00: 00 01 01 42 01 20 00 49 00 08 A9 05 42 10 30 39
0x10: 39 34 37 38 39 32 00 00 00 00 00 00 00 00 13 62
0x20: 09 0F 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FRU NUMBER : UNKNOWN_BOARD_ID

Slot 1:
Hardware is High Density Modems
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x47,
Board Hardware Version 1.0, Item Number 73-2393-03,
Board Revision A0, Serial Number 21610748,
PLD/ISP Version 5.9, Manufacture Date 8-Aug-2000.
EEPROM format version 0
EEPROM contents (hex):
0x00: 00 01 01 47 01 00 00 49 00 09 59 03 41 00 32 31
0x10: 36 31 30 37 34 38 00 00 00 00 00 00 00 00 14 00
0x20: 08 08 05 09 FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FRU NUMBER : AS53-60-CC2=

Slot 2:
Hardware is High Density Modems
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x47,
Board Hardware Version 1.0, Item Number 73-2393-03,
Board Revision A0, Serial Number 06470466,
PLD/ISP Version 5.9, Manufacture Date 15-Nov-1997.
EEPROM format version 0
EEPROM contents (hex):
0x00: 00 01 01 47 01 00 00 49 00 09 59 03 41 00 30 36
0x10: 34 37 30 34 36 36 00 00 00 00 00 00 00 00 13 61
0x20: 0B 0F 05 09 FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FRU NUMBER : AS53-60-CC2=

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

as5300_frv_1# show run
Building configuration...

Current configuration : 4387 bytes
!
version 12.3
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
no service password-encryption
service linenumber
no service dhcp
!
hostname as5300_frv_1
!
boot-start-marker
boot-end-marker
!
logging buffered 262144 debugging
no logging console
enable secret 5 $1$xNJM$kSL2o69Qxoyt/EgBzemdr0
enable password gr8n00dl3
!
spe 1/0 1/7
firmware location system:/ucode/mica_port_firmware
spe 2/0 2/8
firmware location system:/ucode/mica_port_firmware
!
!
resource-pool disable
clock timezone EST -5
clock summer-time EDT recurring
!
calltracker enable
calltracker history max-size 200
calltracker history retain-mins 60
modem call-record terse
modem recovery maintenance window 120
modem recovery maintenance time 2:00
modem recovery maintenance stop-time 5:00
modem recovery threshold 100
modem link-info poll time 10
no aaa new-model
ip subnet-zero
ip cef
ip ftp source-interface FastEthernet0
ip name-server 216.235.225.2
ip name-server 216.235.225.3
!
virtual-profile if-needed
virtual-profile virtual-template 1
multilink virtual-template 1
multilink bundle-name both
!
isdn switch-type primary-ni
!
!
!
!
!
!
!
!
!
!
iua
AS Kinex3 216.235.226.3 5000
ASP kinex3Ctrlr AS Kinex3 216.24.23.72 9103
!
!
controller T1 0
framing esf
clock source line primary
linecode b8zs
pri-group timeslots 1-23 nfas_d primary nfas_int 0 nfas_group 1 iua Kinex3
!
controller T1 1
framing esf
clock source line secondary 1
linecode b8zs
pri-group timeslots 1-23 nfas_d primary nfas_int 1 nfas_group 2 iua Kinex3
!
controller T1 2
framing esf
linecode b8zs
pri-group timeslots 1-23 nfas_d primary nfas_int 2 nfas_group 3 iua Kinex3
!
controller T1 3
framing esf
linecode b8zs
pri-group timeslots 1-23 nfas_d primary nfas_int 3 nfas_group 4 iua Kinex3
!
!
interface Ethernet0
no ip address
shutdown
!
interface Virtual-Template1
mtu 1514
ip unnumbered FastEthernet0
ip verify unicast reverse-path
ip route-cache flow
timeout absolute 1440 0
peer default ip address pool setup_pool
compress stac
ppp max-bad-auth 4
ppp authentication pap chap callin
ppp multilink
ppp timeout retry 5
ppp timeout idle 1800
!
interface FastEthernet0
ip address 216.235.226.3 255.255.255.0
duplex full
speed 100
!
interface Dchannel0
no ip address
encapsulation ppp
dialer idle-timeout 1800
isdn timer t309 100
isdn timer t321 30000
isdn incoming-voice modem
isdn T303 20000
isdn T203 10000
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
no cdp enable
!
interface Dchannel1
no ip address
encapsulation ppp
dialer idle-timeout 1800
isdn timer t309 100
isdn timer t321 30000
isdn incoming-voice modem
isdn T303 20000
isdn T203 10000
no isdn send-status-enquiry
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
no cdp enable
!
interface Dchannel2
no ip address
encapsulation ppp
dialer idle-timeout 1800
isdn timer t309 100
isdn timer t321 30000
isdn incoming-voice modem
isdn T303 20000
isdn T203 10000
no isdn send-status-enquiry
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
no cdp enable
!
interface Dchannel3
no ip address
encapsulation ppp
dialer idle-timeout 1800
isdn timer t309 100
isdn timer t321 30000
isdn incoming-voice modem
isdn T303 20000
isdn T203 10000
no isdn send-status-enquiry
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
no cdp enable
!
interface Group-Async1
mtu 1514
ip unnumbered FastEthernet0
ip verify unicast reverse-path
encapsulation ppp
timeout absolute 720 0
dialer in-band
dialer idle-timeout 1800
dialer-group 1
async mode interactive
peer default ip address pool setup_pool
ppp max-bad-auth 4
ppp authentication pap callin
ppp multilink
ppp timeout retry 5
group-range 1 96
!
ip local pool setup_pool 216.235.226.10 216.235.226.254
ip classless
ip default-network 0.0.0.0
ip route 0.0.0.0 0.0.0.0 216.235.226.1
no ip http server
!
!
!
!
!
!
!
!
line con 0
line 1 96
access-class 23 in
exec-timeout 0 0
no flush-at-activation
modem Dialin
modem autoconfigure type mica
rotary 1
transport input all
autoselect during-login
autoselect ppp
line 97 102
exec-timeout 0 0
line aux 0
line vty 0 2
exec-timeout 32000 0
password n00dl3s
login
line vty 3 4
password n00dl3s
login
!
end

as5300_frv_1#

achatz at forthnet

Aug 26, 2008, 9:00 AM

Post #3 of 13 (4494 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

Quite strangely, i have 2 AS5300s running 12.3(23) for over a year and i believe (are "Busied Out" calls due to bug?) i
haven't met this problem.

AS5300-1#sh modem sum
Avg Hold Incoming calls Outgoing calls Busied Failed No Succ
Time Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
00:32:34 515632 31270 89 0 0 0 186 0 12 94%

AS5300-2#sh modem sum
Avg Hold Incoming calls Outgoing calls Busied Failed No Succ
Time Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
00:32:14 224905 13652 116 0 0 0 192 0 7 94%

btw, bug-id should be CSCei63851 ;) and it's quite annoying that something like this happened in the middle of an ios
release.
Was it too difficult to find the differences between 12.3(6)d and 12.3(6)e?

--
Tassos

Aaron Leonard wrote on 26/8/2008 6:25 ��:
> Oh yeah - CSCsi638651, which we never did figure out. Actually,
> anything in 12.3(6x) and before should be good.
>
> Aaron
>
> -------- Original Message --------
> Subject: Re: [cisco-nas] Modems not responding on cisco AS5300.
> Date: Tue, 26 Aug 2008 10:20:58 +0800
> From: Mark Tinka <mtinka [at] globaltransit>
> Reply-To: mtinka [at] globaltransit
> Organization: Global Transit International
> To: cisco-nas [at] puck
> CC: Aaron Leonard <Aaron [at] cisco>, Joseph Mays <mays [at] win>, Mike
> Andrews <mandrews [at] bit0>
> References: <081301c906e2$03cf90c0$0a2118d8 [at] engineering0>
> <0b1301c9070d$87bc8ca0$0a2118d8 [at] engineering0> <48B34BE2.7080902 [at] Cisco>
>
>
>
> On Tuesday 26 August 2008 08:18:42 Aaron Leonard wrote:
>
>> In any case, the guidance below is still generally
>> applicable - i.e. run latest code (2.9.5.0); turn on
>> modem recovery.
>
> You also want to run an IOS revision no later than 12.3(5)f.
>
> Anything more recent than this will continuously cause your
> modems to go into a BAD state.
>
> Cheers,
>
> Mark.
>
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nas
>
_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

Aaron at cisco

Aug 26, 2008, 9:23 AM

Post #4 of 13 (4500 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

Tassos,

Thanks for catching the typo - yes, this bug is CSCei63851:

CSCei63851 AS5300: mica modems randomly marked as bad in any version
afer 12.3(6)

The footprint is that the following event will appear in the modem log:

Jul 17 14:32:02.938 UTC-3: Out of Service event:
Cause: Onhook/Offhook failure

At which point the modem is marked Bad.

The regression seems to have gone into IOS right after 12.3(6), before
the next release of mainline IOS hit (which was 12.3(9).) I believe all
rebuilds in 12.3(6) (i.e. 12.3(6a) .. 12.3(6f)) are immune.

The bug doesn't affect *everybody*.

Btw, this is not the o.p.'s issue - in the CSCsi63851 case, when the
modem is marked Bad, subsequent incoming calls cannot land on it.

Aaron

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

> Quite strangely, i have 2 AS5300s running 12.3(23) for over a year and i believe (are "Busied Out" calls due to bug?) i
> haven't met this problem.
>
> AS5300-1#sh modem sum
> Avg Hold Incoming calls Outgoing calls Busied Failed No Succ
> Time Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
> 00:32:34 515632 31270 89 0 0 0 186 0 12 94%
>
> AS5300-2#sh modem sum
> Avg Hold Incoming calls Outgoing calls Busied Failed No Succ
> Time Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
> 00:32:14 224905 13652 116 0 0 0 192 0 7 94%
>
> btw, bug-id should be CSCei63851 ;) and it's quite annoying that something like this happened in the middle of an ios
> release.
> Was it too difficult to find the differences between 12.3(6)d and 12.3(6)e?
>
> --
> Tassos
>
>
> Aaron Leonard wrote on 26/8/2008 6:25 ??:
>
>> Oh yeah - CSCsi638651, which we never did figure out. Actually,
>> anything in 12.3(6x) and before should be good.
>>
>> Aaron
>>
>> -------- Original Message --------
>> Subject: Re: [cisco-nas] Modems not responding on cisco AS5300.
>> Date: Tue, 26 Aug 2008 10:20:58 +0800
>> From: Mark Tinka <mtinka [at] globaltransit>
>> Reply-To: mtinka [at] globaltransit
>> Organization: Global Transit International
>> To: cisco-nas [at] puck
>> CC: Aaron Leonard <Aaron [at] cisco>, Joseph Mays <mays [at] win>, Mike
>> Andrews <mandrews [at] bit0>
>> References: <081301c906e2$03cf90c0$0a2118d8 [at] engineering0>
>> <0b1301c9070d$87bc8ca0$0a2118d8 [at] engineering0> <48B34BE2.7080902 [at] Cisco>
>>
>>
>>
>> On Tuesday 26 August 2008 08:18:42 Aaron Leonard wrote:
>>
>>
>>> In any case, the guidance below is still generally
>>> applicable - i.e. run latest code (2.9.5.0); turn on
>>> modem recovery.
>>>
>> You also want to run an IOS revision no later than 12.3(5)f.
>>
>> Anything more recent than this will continuously cause your
>> modems to go into a BAD state.
>>
>> Cheers,
>>
>> Mark.
>>
>>
>> _______________________________________________
>> cisco-nas mailing list
>> cisco-nas [at] puck
>> https://puck.nether.net/mailman/listinfo/cisco-nas
>>
>>

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

mtinka at globaltransit

Aug 26, 2008, 7:53 PM

Post #5 of 13 (4470 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

On Tuesday 26 August 2008 23:25:17 Aaron Leonard wrote:

> Oh yeah - CSCsi638651, which we never did figure out.
> Actually, anything in 12.3(6x) and before should be good.

Anything at and before 12.3(6)d, to be exact.

At the time I faced the problem, 12.3(6)d was DF.

12.3(5)f is what was available, and it worked toward
resolving this problem.

Today, neither of these is available. The least I can see is
12.3(3)i. But then again, I haven't run an AS5300 in months
(although I have one that I need to resurrect in a few
weeks).

Cheers,

Mark.

Attachments:

signature.asc (0.82 KB)

mtinka at globaltransit

Aug 26, 2008, 7:55 PM

Post #6 of 13 (4481 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

On Tuesday 26 August 2008 23:55:51 Joseph Mays wrote:

> The boxes are all running 12.3(16).

Would you willing to downgrade to 12.3(3)i (currently LD),
as well as installing MICA Portware 2.9.5.0?

Cheers,

Mark.

Attachments:

signature.asc (0.82 KB)

mays at win

Aug 27, 2008, 6:30 AM

Post #7 of 13 (4481 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

Possibly, if I knew where to get it. I don't think I can get IOS going back
that far for an AS5300 from cisco anymore, can I?

----- Original Message -----
From: "Mark Tinka" <mtinka [at] globaltransit>
To: "Joseph Mays" <mays [at] win>
Cc: "Aaron Leonard" <Aaron [at] cisco>; "'cisco-nas'"
<cisco-nas [at] puck>
Sent: Tuesday, August 26, 2008 10:55 PM
Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco AS5300.]

On Tuesday 26 August 2008 23:55:51 Joseph Mays wrote:

> The boxes are all running 12.3(16).

Would you willing to downgrade to 12.3(3)i (currently LD),
as well as installing MICA Portware 2.9.5.0?

Cheers,

Mark.

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

mtinka at globaltransit

Aug 27, 2008, 6:32 AM

Post #8 of 13 (4471 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

On Wednesday 27 August 2008 21:30:56 Joseph Mays wrote:

> Possibly, if I knew where to get it.

www.cisco.com

> I don't think I can
> get IOS going back that far for an AS5300 from cisco
> anymore, can I?

I checked; it's there :-).

Mark.

Attachments:

signature.asc (0.82 KB)

mays at win

Aug 27, 2008, 6:37 AM

Post #9 of 13 (4475 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

Huh. Okay, thanks. I never looked prior to this, because it never occured to
me to back up the (already very old) IOS several revs to see if it helped. I
didn't IOS's that old could be obtained from cisco anymore. I'll check it
out.

----- Original Message -----
From: "Mark Tinka" <mtinka [at] globaltransit>
To: "Joseph Mays" <mays [at] win>
Cc: "Aaron Leonard" <Aaron [at] cisco>; "'cisco-nas'"
<cisco-nas [at] puck>
Sent: Wednesday, August 27, 2008 9:32 AM
Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco AS5300.]

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

Aaron at cisco

Aug 27, 2008, 8:27 AM

Post #10 of 13 (4475 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

Btw, it is possible to dig up old 12.3(6d) or whatever ... that is, you
could open a TAC case and TAC could dig it up for you. (Otoh, the 5300
is past Last Day of Support, so I guess you wouldn't be entitled to open
a case in the first place ...)

Not that I know of any reason offhand to run 12.3(6d) rather than 12.3(3i).

----

> Possibly, if I knew where to get it. I don't think I can get IOS going back
> that far for an AS5300 from cisco anymore, can I?
>
> ----- Original Message -----
> From: "Mark Tinka" <mtinka [at] globaltransit>
> To: "Joseph Mays" <mays [at] win>
> Cc: "Aaron Leonard" <Aaron [at] cisco>; "'cisco-nas'"
> <cisco-nas [at] puck>
> Sent: Tuesday, August 26, 2008 10:55 PM
> Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco AS5300.]
>
> On Tuesday 26 August 2008 23:55:51 Joseph Mays wrote:
>
>
>> The boxes are all running 12.3(16).
>>
>
> Would you willing to downgrade to 12.3(3)i (currently LD),
> as well as installing MICA Portware 2.9.5.0?
>
> Cheers,
>
> Mark.
>

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

mays at win

Aug 29, 2008, 11:28 AM

Post #11 of 13 (4454 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

I am looking at downgrade the IOS as suggested. In the meantime, different
issue on the same box. I'm trying to enter the radius setup, and it's
responding that no "radius-server" anything does not exist as a config
command. I list the commands and radius-server does not show up. But the IOS
is the exact same version we use on another set of boxes and the
radius-server commands work fine there.

----- Original Message -----
From: "Aaron Leonard" <Aaron [at] cisco>
To: "Joseph Mays" <mays [at] win>
Cc: <mtinka [at] globaltransit>; "'cisco-nas'" <cisco-nas [at] puck>
Sent: Wednesday, August 27, 2008 11:27 AM
Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco AS5300.]

> Btw, it is possible to dig up old 12.3(6d) or whatever ... that is, you
> could open a TAC case and TAC could dig it up for you. (Otoh, the 5300
> is past Last Day of Support, so I guess you wouldn't be entitled to open
> a case in the first place ...)
>
> Not that I know of any reason offhand to run 12.3(6d) rather than
> 12.3(3i).
>
> ----
>
>> Possibly, if I knew where to get it. I don't think I can get IOS going
>> back
>> that far for an AS5300 from cisco anymore, can I?
>>
>> ----- Original Message -----
>> From: "Mark Tinka" <mtinka [at] globaltransit>
>> To: "Joseph Mays" <mays [at] win>
>> Cc: "Aaron Leonard" <Aaron [at] cisco>; "'cisco-nas'"
>> <cisco-nas [at] puck>
>> Sent: Tuesday, August 26, 2008 10:55 PM
>> Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco
>> AS5300.]
>>
>> On Tuesday 26 August 2008 23:55:51 Joseph Mays wrote:
>>
>>
>>> The boxes are all running 12.3(16).
>>>
>>
>> Would you willing to downgrade to 12.3(3)i (currently LD),
>> as well as installing MICA Portware 2.9.5.0?
>>
>> Cheers,
>>
>> Mark.
>>
>

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

Aaron at cisco

Aug 29, 2008, 11:40 AM

Post #12 of 13 (4445 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

My guess is that "aaa new-model" is missing. Need that to see the
"radius-server" commands.

----

> I am looking at downgrade the IOS as suggested. In the meantime, different
> issue on the same box. I'm trying to enter the radius setup, and it's
> responding that no "radius-server" anything does not exist as a config
> command. I list the commands and radius-server does not show up. But the IOS
> is the exact same version we use on another set of boxes and the
> radius-server commands work fine there.
>
>
> ----- Original Message -----
> From: "Aaron Leonard" <Aaron [at] cisco>
> To: "Joseph Mays" <mays [at] win>
> Cc: <mtinka [at] globaltransit>; "'cisco-nas'" <cisco-nas [at] puck>
> Sent: Wednesday, August 27, 2008 11:27 AM
> Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco AS5300.]
>
>
>
>> Btw, it is possible to dig up old 12.3(6d) or whatever ... that is, you
>> could open a TAC case and TAC could dig it up for you. (Otoh, the 5300
>> is past Last Day of Support, so I guess you wouldn't be entitled to open
>> a case in the first place ...)
>>
>> Not that I know of any reason offhand to run 12.3(6d) rather than
>> 12.3(3i).
>>
>> ----
>>
>>
>>> Possibly, if I knew where to get it. I don't think I can get IOS going
>>> back
>>> that far for an AS5300 from cisco anymore, can I?
>>>
>>> ----- Original Message -----
>>> From: "Mark Tinka" <mtinka [at] globaltransit>
>>> To: "Joseph Mays" <mays [at] win>
>>> Cc: "Aaron Leonard" <Aaron [at] cisco>; "'cisco-nas'"
>>> <cisco-nas [at] puck>
>>> Sent: Tuesday, August 26, 2008 10:55 PM
>>> Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco
>>> AS5300.]
>>>
>>> On Tuesday 26 August 2008 23:55:51 Joseph Mays wrote:
>>>
>>>
>>>
>>>> The boxes are all running 12.3(16).
>>>>
>>>>
>>> Would you willing to downgrade to 12.3(3)i (currently LD),
>>> as well as installing MICA Portware 2.9.5.0?
>>>
>>> Cheers,
>>>
>>> Mark.
>>>
>>>

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

mays at win

Aug 29, 2008, 11:52 AM

Post #13 of 13 (4453 views)
Permalink

Re: [Fwd: Re: Modems not responding on cisco AS5300.] [In reply to]

Whoops. Brain failure on my part there. Thanks.

----- Original Message -----
From: "Aaron Leonard" <Aaron [at] cisco>
To: "Joseph Mays" <mays [at] win>
Cc: <mtinka [at] globaltransit>; "'cisco-nas'" <cisco-nas [at] puck>
Sent: Friday, August 29, 2008 2:40 PM
Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco AS5300.]

> My guess is that "aaa new-model" is missing. Need that to see the
> "radius-server" commands.
>
> ----
>
>> I am looking at downgrade the IOS as suggested. In the meantime,
>> different
>> issue on the same box. I'm trying to enter the radius setup, and it's
>> responding that no "radius-server" anything does not exist as a config
>> command. I list the commands and radius-server does not show up. But the
>> IOS
>> is the exact same version we use on another set of boxes and the
>> radius-server commands work fine there.
>>
>>
>> ----- Original Message -----
>> From: "Aaron Leonard" <Aaron [at] cisco>
>> To: "Joseph Mays" <mays [at] win>
>> Cc: <mtinka [at] globaltransit>; "'cisco-nas'" <cisco-nas [at] puck>
>> Sent: Wednesday, August 27, 2008 11:27 AM
>> Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco
>> AS5300.]
>>
>>
>>
>>> Btw, it is possible to dig up old 12.3(6d) or whatever ... that is, you
>>> could open a TAC case and TAC could dig it up for you. (Otoh, the 5300
>>> is past Last Day of Support, so I guess you wouldn't be entitled to open
>>> a case in the first place ...)
>>>
>>> Not that I know of any reason offhand to run 12.3(6d) rather than
>>> 12.3(3i).
>>>
>>> ----
>>>
>>>
>>>> Possibly, if I knew where to get it. I don't think I can get IOS going
>>>> back
>>>> that far for an AS5300 from cisco anymore, can I?
>>>>
>>>> ----- Original Message -----
>>>> From: "Mark Tinka" <mtinka [at] globaltransit>
>>>> To: "Joseph Mays" <mays [at] win>
>>>> Cc: "Aaron Leonard" <Aaron [at] cisco>; "'cisco-nas'"
>>>> <cisco-nas [at] puck>
>>>> Sent: Tuesday, August 26, 2008 10:55 PM
>>>> Subject: Re: [cisco-nas] [Fwd: Re: Modems not responding on cisco
>>>> AS5300.]
>>>>
>>>> On Tuesday 26 August 2008 23:55:51 Joseph Mays wrote:
>>>>
>>>>
>>>>
>>>>> The boxes are all running 12.3(16).
>>>>>
>>>>>
>>>> Would you willing to downgrade to 12.3(3)i (currently LD),
>>>> as well as installing MICA Portware 2.9.5.0?
>>>>
>>>> Cheers,
>>>>
>>>> Mark.
>>>>
>>>>
>

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads