|
|
|
Question : Problem: what is the upgrade path for a cisco as5300 to make it v.92 compatible?
|
|
here are the details:
as53-p01#sh ver
Cisco Internetwork Operating System Software
IOS (tm) 5300 Software (C5300-IS-M), Version 12.1(4), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Wed 30-Aug-00 04:18 by cmong
Image text-base: 0x60008948, data-base: 0x60CB2000
ROM: System Bootstrap, Version 12.0(2)XD1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
BOOTFLASH: 5300 Software (C5300-BOOT-M), Version 12.1(4), RELEASE SOFTWARE (fc1)
as53-p01 uptime is 2 weeks, 4 days, 2 hours, 37 minutes
System returned to ROM by reload
System image file is "flash:c5300-is-mz.121-4.bin"
cisco AS5300 (R4K) processor (revision A.32) with 65536K/16384K bytes of memory.
Processor board ID 14052418
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 1.80, Item Number 800-2544-3,
Board Revision A0, Serial Number 14052418,
PLD/ISP Version 0.0, Manufacture Date 26-Jun-1999.
1 Ethernet/IEEE 802.3 interface(s)
1 FastEthernet/IEEE 802.3 interface(s)
196 Serial network interface(s)
192 terminal line(s)
8 Channelized T1/PRI port(s)
128K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)
8192K bytes of processor board Boot flash (Read/Write)
Configuration register is 0x2102
AND
as53-p01#sh mo 1/1
Mdm Typ Status Tx/Rx G Duration RTS CTS DCD DTR
1/1 V.90 Idle 50666/26400 1 03:16:04 x x x
Modem 1/1, Mica Hex Modem (Managed), Async2, TTY2
Firmware Rev: 2.7.2.0
Modem config: Incoming
Protocol: LAP-M, Compression: V.42bis both
Management config: Status polling
RX signals: -23 dBm
Last clearing of "show modem" counters never
232 incoming completes, 8 incoming failures
0 outgoing completes, 0 outgoing failures
0 failed dial attempts, 0 ring no answers, 0 busied outs
0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
0 no carriers, 0 link failures, 0 resets, 0 recover oob
0 recover modem, 0 current fail count
0 protocol timeouts, 1 protocol errors, 0 lost events
0 ready poll timeouts
Transmit Speed Counters:
Connection Speeds 75 300 600 1200 2400 4800
# of connections 0 0 0 0 0 0
Connection Speeds 7200 9600 12000 14400 16800 19200
# of connections 2 0 0 1 1 4
Connection Speeds 21600 24000 26400 28000 28800 29333
# of connections 4 7 34 0 25 1
Connection Speeds 30667 31200 32000 33333 33600 34000
# of connections 1 8 0 0 5 0
Connection Speeds 34667 36000 37333 38000 38400 38667
# of connections 1 3 2 0 0 4
Connection Speeds 40000 41333 42000 42667 44000 45333
# of connections 3 1 0 2 12 20
Connection Speeds 46000 46667 48000 49333 50000 50667
# of connections 1 11 16 16 3 20
Connection Speeds 52000 53333 54000 54667 56000
# of connections 17 7 0 0 0
Receive Speed Counters:
Connection Speeds 75 300 600 1200 2400 4800
# of connections 0 0 0 0 0 1
Connection Speeds 7200 9600 12000 14400 16800 19200
# of connections 1 1 5 8 12 23
Connection Speeds 21600 24000 26400 28000 28800 29333
# of connections 51 65 54 0 11 0
Connection Speeds 30667 31200 32000 33333 33600 34000
# of connections 0 0 0 0 0 0
Connection Speeds 34667 36000 37333 38000 38400 38667
# of connections 0 0 0 0 0 0
Connection Speeds 40000 41333 42000 42667 44000 45333
# of connections 0 0 0 0 0 0
Connection Speeds 46000 46667 48000 49333 50000 50667
# of connections 0 0 0 0 0 0
Connection Speeds 52000 53333 54000 54667 56000
# of connections 0 0 0 0 0
So far I've heard that it's simply a ios+firmware upgrade (but hte IOS and Firmware that I need won't fit on my flash)
but I've also heard that it's not possible. anyone do this?
|
Answer : Problem: what is the upgrade path for a cisco as5300 to make it v.92 compatible?
|
|
Sorry of course you posted the firmware already! (I must practice my reading skills!!)
You need the 2.7.2.0 to 2.9.2.0 update, talk to Cisco but I think this is a card update.
M :o)
|
|
|
|
|
