Mailing List Archive

The quite echos of this list are still here, but I have not idea about this problem.


—
Regards,
Darryl Sladden
Senior TME Manager, Wireless and Location
Cisco
408-219-8485

From: cisco-nas <cisco-nas-bounces@puck.nether.net> on behalf of Joseph Mays <mays@win.net>
Date: Monday, June 5, 2017 at 1:08 PM
To: "cisco-nas@puck.nether.net" <cisco-nas@puck.nether.net>
Subject: [cisco-nas] Windows 10 with AS5400

I kind of never expected to have another question for this list. I'm not even sure it's still operational. But I guess we'll see.

We have two AS5400's providing dialup services, one in Kentucky, and one across the river in Indiana. The one in Kentucky has no problems at all.

Recently, a user in Indiana switched to Windows 10, and found that her dialup connection there no longer worked. She gets connected and logged in, but then gets 80-90% packet loss. She still has her Windows 8 computer, and that still works fine with her dialup connection. We went over with a windows 10 unit, a windows 7 unit, and a linux box, and tried dialup up with all three. The windows 7 and linux boxed worked fine, the windows 10 unit had the same problem she did.

We then tried calling another user in Indiana whom we thought had switched to Windows 10 a while ago. Turns out, he told us, that his dialup connection never worked with Windows 10, so he switched back to Windows 8.5.

Our memory is that a year ago we were helping a partner in Canada who had some dialup services with an AS5400, and he found that Windows 10 users didn't work for him with it, but he just figured it was something with Windows 10 and didn't worry about it.

Like I said, Windows 10 works fine with the AS5400 in Kentucky, so I tried isolating differences between those boxes, to the point of making them identical with IOS, modem setup strings, modem firmware, etc. No difference. In fact, it made things worse. Many people were failing to connect, including the woman with the initial problem. Now the Indiana box is back to the way it was, and just that woman who is trying to use Windows 10 has her problem of getting connected then being unable to do anything.

Here is the box in Indiana.
indyvoipMG#show ver
Cisco Internetwork Operating System Software
IOS (tm) 5400 Software (C5400-JS-M), Version 12.2(15)T17, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Sat 13-Aug-05 07:51 by kehsiao
Image text-base: 0x6000895C, data-base: 0x61900000

ROM: System Bootstrap, Version 12.0(20000106:234457) [tombnyg-rommon_1_6 106], DEVELOPMENT SOFTWARE REV 1.6
BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.2(7b), RELEASE SOFTWARE (fc1)

indyvoipMG uptime is 2 days, 2 hours, 59 minutes
System returned to ROM by reload at 13:05:26 EDT Sat Jun 3 2017
System restarted at 13:06:13 EDT Sat Jun 3 2017
System image file is "flash:c5400-js-mz.122-16.T17.bin"

cisco AS5400 (R7K) processor (revision T) with 262144K/65536K bytes of memory.
Processor board ID JAB03510786
R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
Last reset from IOS reload
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,
Board Hardware Version 3.21, Item Number 800-5171-01,
Board Revision 017, Serial Number JAB03510786,
PLD/ISP Version 2.2, Manufacture Date 5-Jan-2000.
Processor 0xFF, MAC Address 0x03096F816
Backplane HW Revision 1.0, Flash Type 5V
2 FastEthernet/IEEE 802.3 interface(s)
178 Serial network interface(s)
108 terminal line(s)
36 Channelized T1/PRI port(s)
1 Channelized T3 port(s)
512K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)
8192K bytes of processor board Boot flash (Read/Write)

Configuration register is 0x2102

Here is the box in Kentucky.
ArmoryPl-AS5400>show ver
Cisco Internetwork Operating System Software
IOS (tm) 5400 Software (C5400-JS-M), Version 12.3(3i), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Fri 12-Aug-05 22:07 by ssearch
Image text-base: 0x6000895C, data-base: 0x61900000

ROM: System Bootstrap, Version 12.2(1r)1, RELEASE SOFTWARE (fc1)
BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.1(1)XD1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc2)

ArmoryPl-AS5400 uptime is 6 days, 6 hours, 58 minutes
System returned to ROM by error - a Software forced crash, PC 0x60453E04 at 09:06:58 EDT Tue May 30 2017
System restarted at 09:07:56 EDT Tue May 30 2017
System image file is "flash:c5400-js-mz.123-3i.bin"

cisco AS5400 (R7K) processor (revision T) with 524288K/131072K bytes of memory.
Processor board ID JAE09054U8M
R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
Last reset from warm-reset
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,
Board Hardware Version 3.34, Item Number 800-5171-02,
Board Revision C0, Serial Number JAE09054U8M,
PLD/ISP Version 2.2, Manufacture Date 26-Jan-2005.
Processor 0x14, MAC Address 0x012801C6694
Backplane HW Revision 1.0, Flash Type 5V
2 FastEthernet/IEEE 802.3 interface(s)
428 Serial network interface(s)
432 terminal line(s)
64 Channelized T1/PRI port(s)
2 Channelized T3 port(s)
512K bytes of non-volatile configuration memory.
65536K bytes of processor board System flash (Read/Write)
16384K bytes of processor board Boot flash (Read/Write)

Configuration register is 0x2102

Hi Joseph,
you can try reducing MTU size of windows machine in registry.

Do Wireshark in working & non working and see the difference..

Regards
Arun

On Jun 5, 2017 4:09 PM, "Joseph Mays" <mays@win.net> wrote:

> I kind of never expected to have another question for this list. I'm not
> even sure it's still operational. But I guess we'll see.
>
> We have two AS5400's providing dialup services, one in Kentucky, and one
> across the river in Indiana. The one in Kentucky has no problems at all.
>
> Recently, a user in Indiana switched to Windows 10, and found that her
> dialup connection there no longer worked. She gets connected and logged in,
> but then gets 80-90% packet loss. She still has her Windows 8 computer, and
> that still works fine with her dialup connection. We went over with a
> windows 10 unit, a windows 7 unit, and a linux box, and tried dialup up
> with all three. The windows 7 and linux boxed worked fine, the windows 10
> unit had the same problem she did.
>
> We then tried calling another user in Indiana whom we thought had switched
> to Windows 10 a while ago. Turns out, he told us, that his dialup
> connection never worked with Windows 10, so he switched back to Windows 8.5.
>
> Our memory is that a year ago we were helping a partner in Canada who had
> some dialup services with an AS5400, and he found that Windows 10 users
> didn't work for him with it, but he just figured it was something with
> Windows 10 and didn't worry about it.
>
> Like I said, Windows 10 works fine with the AS5400 in Kentucky, so I tried
> isolating differences between those boxes, to the point of making them
> identical with IOS, modem setup strings, modem firmware, etc. No
> difference. In fact, it made things worse. Many people were failing to
> connect, including the woman with the initial problem. Now the Indiana box
> is back to the way it was, and just that woman who is trying to use Windows
> 10 has her problem of getting connected then being unable to do anything.
>
> Here is the box in Indiana.
>
> indyvoipMG#show ver
> Cisco Internetwork Operating System Software
> IOS (tm) 5400 Software (C5400-JS-M), Version 12.2(15)T17, RELEASE SOFTWARE
> (fc1)
> Technical Support: http://www.cisco.com/techsupport
> Copyright (c) 1986-2005 by cisco Systems, Inc.
> Compiled Sat 13-Aug-05 07:51 by kehsiao
> Image text-base: 0x6000895C, data-base: 0x61900000
>
> ROM: System Bootstrap, Version 12.0(20000106:234457) [tombnyg-rommon_1_6
> 106], DEVELOPMENT SOFTWARE REV 1.6
> BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.2(7b), RELEASE SOFTWARE
> (fc1)
>
> indyvoipMG uptime is 2 days, 2 hours, 59 minutes
> System returned to ROM by reload at 13:05:26 EDT Sat Jun 3 2017
> System restarted at 13:06:13 EDT Sat Jun 3 2017
> System image file is "flash:c5400-js-mz.122-16.T17.bin"
>
> cisco AS5400 (R7K) processor (revision T) with 262144K/65536K bytes of
> memory.
> Processor board ID JAB03510786
> R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
> Last reset from IOS reload
> Bridging software.
> X.25 software, Version 3.0.0.
> SuperLAT software (copyright 1990 by Meridian Technology Corp).
> TN3270 Emulation software.
> Primary Rate ISDN software, Version 1.1.
> Manufacture Cookie Info:
> EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,
> Board Hardware Version 3.21, Item Number 800-5171-01,
> Board Revision 017, Serial Number JAB03510786,
> PLD/ISP Version 2.2, Manufacture Date 5-Jan-2000.
> Processor 0xFF, MAC Address 0x03096F816
> Backplane HW Revision 1.0, Flash Type 5V
> 2 FastEthernet/IEEE 802.3 interface(s)
> 178 Serial network interface(s)
> 108 terminal line(s)
> 36 Channelized T1/PRI port(s)
> 1 Channelized T3 port(s)
> 512K bytes of non-volatile configuration memory.
> 32768K bytes of processor board System flash (Read/Write)
> 8192K bytes of processor board Boot flash (Read/Write)
>
> Configuration register is 0x2102
>
> Here is the box in Kentucky.
>
> ArmoryPl-AS5400>show ver
> Cisco Internetwork Operating System Software
> IOS (tm) 5400 Software (C5400-JS-M), Version 12.3(3i), RELEASE SOFTWARE
> (fc1)
> Copyright (c) 1986-2005 by cisco Systems, Inc.
> Compiled Fri 12-Aug-05 22:07 by ssearch
> Image text-base: 0x6000895C, data-base: 0x61900000
>
> ROM: System Bootstrap, Version 12.2(1r)1, RELEASE SOFTWARE (fc1)
> BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.1(1)XD1, EARLY
> DEPLOYMENT RELEASE SOFTWARE (fc2)
>
> ArmoryPl-AS5400 uptime is 6 days, 6 hours, 58 minutes
> System returned to ROM by error - a Software forced crash, PC 0x60453E04
> at 09:06:58 EDT Tue May 30 2017
> System restarted at 09:07:56 EDT Tue May 30 2017
> System image file is "flash:c5400-js-mz.123-3i.bin"
>
> cisco AS5400 (R7K) processor (revision T) with 524288K/131072K bytes of
> memory.
> Processor board ID JAE09054U8M
> R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
> Last reset from warm-reset
> Bridging software.
> X.25 software, Version 3.0.0.
> SuperLAT software (copyright 1990 by Meridian Technology Corp).
> TN3270 Emulation software.
> Primary Rate ISDN software, Version 1.1.
> Manufacture Cookie Info:
> EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,
> Board Hardware Version 3.34, Item Number 800-5171-02,
> Board Revision C0, Serial Number JAE09054U8M,
> PLD/ISP Version 2.2, Manufacture Date 26-Jan-2005.
> Processor 0x14, MAC Address 0x012801C6694
> Backplane HW Revision 1.0, Flash Type 5V
> 2 FastEthernet/IEEE 802.3 interface(s)
> 428 Serial network interface(s)
> 432 terminal line(s)
> 64 Channelized T1/PRI port(s)
> 2 Channelized T3 port(s)
> 512K bytes of non-volatile configuration memory.
> 65536K bytes of processor board System flash (Read/Write)
> 16384K bytes of processor board Boot flash (Read/Write)
>
> Configuration register is 0x2102
>
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
>

Hiya Joseph,

Good to see some activity on this mailer ... I suppose this is the first
in a year or two ... it's nice to see that some of the good ol' AS5400s
are still in service out there.

Let me hazard a guess as to what the problem reported below is ... as
we've seen this sort of complaint a bit recently. Windows 10 recently
came out with an update called "Creators Update". It seems to have some
kind of bug / design problem with path MTU discovery. See for example
this thread:

https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/wifi-issues-with-creators-update/4a20ba4f-33dc-4397-9823-e12dcb2607ba

The simple workarounds are:

* turn down the MTU on the client adapter, to maybe 1300 or 1400 B.
(Simple for me to day, maybe not simple for the client.)
o or disable Receive Segment Coalescing on the client (I believe
that this is the feature that causes the problem.)
* on the infrastructure side, if a router in the affected network path
is a Cisco IOS router, then turn on TCP MSS Adjust (set it to 1250
or 1360 or so.)


I suppose maybe you could turn down the interface MTU for your dialup
users (this is negotiated in LCP, right), and that might be a nice easy
effective workaround too.

Hope this helps,

Aaron

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

On 6/5/2017 1:08 PM, mays@win.net (Joseph Mays) wrote:
> I kind of never expected to have another question for this list. I'm
> not even sure it's still operational. But I guess we'll see.
> We have two AS5400's providing dialup services, one in Kentucky, and
> one across the river in Indiana. The one in Kentucky has no problems
> at all.
>
> Recently, a user in Indiana switched to Windows 10, and found that her
> dialup connection there no longer worked. She gets connected and
> logged in, but then gets 80-90% packet loss. She still has her Windows
> 8 computer, and that still works fine with her dialup connection. We
> went over with a windows 10 unit, a windows 7 unit, and a linux box,
> and tried dialup up with all three. The windows 7 and linux boxed
> worked fine, the windows 10 unit had the same problem she did.
>
> We then tried calling another user in Indiana whom we thought had
> switched to Windows 10 a while ago. Turns out, he told us, that his
> dialup connection never worked with Windows 10, so he switched back to
> Windows 8.5.
> Our memory is that a year ago we were helping a partner in Canada who
> had some dialup services with an AS5400, and he found that Windows 10
> users didn't work for him with it, but he just figured it was
> something with Windows 10 and didn't worry about it.
>
> Like I said, Windows 10 works fine with the AS5400 in Kentucky, so I
> tried isolating differences between those boxes, to the point of
> making them identical with IOS, modem setup strings, modem firmware,
> etc. No difference. In fact, it made things worse. Many people were
> failing to connect, including the woman with the initial problem. Now
> the Indiana box is back to the way it was, and just that woman who is
> trying to use Windows 10 has her problem of getting connected then
> being unable to do anything.
>
> Here is the box in Indiana.
>
> indyvoipMG#show ver
> Cisco Internetwork Operating System Software
> IOS (tm) 5400 Software (C5400-JS-M), Version 12.2(15)T17, RELEASE
> SOFTWARE (fc1)
> Technical Support: http://www.cisco.com/techsupport
> Copyright (c) 1986-2005 by cisco Systems, Inc.
> Compiled Sat 13-Aug-05 07:51 by kehsiao
> Image text-base: 0x6000895C, data-base: 0x61900000
> ROM: System Bootstrap, Version 12.0(20000106:234457)
> [tombnyg-rommon_1_6 106], DEVELOPMENT SOFTWARE REV 1.6
> BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.2(7b), RELEASE
> SOFTWARE (fc1)
> indyvoipMG uptime is 2 days, 2 hours, 59 minutes
> System returned to ROM by reload at 13:05:26 EDT Sat Jun 3 2017
> System restarted at 13:06:13 EDT Sat Jun 3 2017
> System image file is "flash:c5400-js-mz.122-16.T17.bin"
> cisco AS5400 (R7K) processor (revision T) with 262144K/65536K bytes of
> memory.
> Processor board ID JAB03510786
> R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
> Last reset from IOS reload
> Bridging software.
> X.25 software, Version 3.0.0.
> SuperLAT software (copyright 1990 by Meridian Technology Corp).
> TN3270 Emulation software.
> Primary Rate ISDN software, Version 1.1.
> Manufacture Cookie Info:
> EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,
> Board Hardware Version 3.21, Item Number 800-5171-01,
> Board Revision 017, Serial Number JAB03510786,
> PLD/ISP Version 2.2, Manufacture Date 5-Jan-2000.
> Processor 0xFF, MAC Address 0x03096F816
> Backplane HW Revision 1.0, Flash Type 5V
> 2 FastEthernet/IEEE 802.3 interface(s)
> 178 Serial network interface(s)
> 108 terminal line(s)
> 36 Channelized T1/PRI port(s)
> 1 Channelized T3 port(s)
> 512K bytes of non-volatile configuration memory.
> 32768K bytes of processor board System flash (Read/Write)
> 8192K bytes of processor board Boot flash (Read/Write)
> Configuration register is 0x2102
>
> Here is the box in Kentucky.
>
> ArmoryPl-AS5400>show ver
> Cisco Internetwork Operating System Software
> IOS (tm) 5400 Software (C5400-JS-M), Version 12.3(3i), RELEASE
> SOFTWARE (fc1)
> Copyright (c) 1986-2005 by cisco Systems, Inc.
> Compiled Fri 12-Aug-05 22:07 by ssearch
> Image text-base: 0x6000895C, data-base: 0x61900000
> ROM: System Bootstrap, Version 12.2(1r)1, RELEASE SOFTWARE (fc1)
> BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.1(1)XD1, EARLY
> DEPLOYMENT RELEASE SOFTWARE (fc2)
> ArmoryPl-AS5400 uptime is 6 days, 6 hours, 58 minutes
> System returned to ROM by error - a Software forced crash, PC
> 0x60453E04 at 09:06:58 EDT Tue May 30 2017
> System restarted at 09:07:56 EDT Tue May 30 2017
> System image file is "flash:c5400-js-mz.123-3i.bin"
> cisco AS5400 (R7K) processor (revision T) with 524288K/131072K bytes
> of memory.
> Processor board ID JAE09054U8M
> R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
> Last reset from warm-reset
> Bridging software.
> X.25 software, Version 3.0.0.
> SuperLAT software (copyright 1990 by Meridian Technology Corp).
> TN3270 Emulation software.
> Primary Rate ISDN software, Version 1.1.
> Manufacture Cookie Info:
> EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,
> Board Hardware Version 3.34, Item Number 800-5171-02,
> Board Revision C0, Serial Number JAE09054U8M,
> PLD/ISP Version 2.2, Manufacture Date 26-Jan-2005.
> Processor 0x14, MAC Address 0x012801C6694
> Backplane HW Revision 1.0, Flash Type 5V
> 2 FastEthernet/IEEE 802.3 interface(s)
> 428 Serial network interface(s)
> 432 terminal line(s)
> 64 Channelized T1/PRI port(s)
> 2 Channelized T3 port(s)
> 512K bytes of non-volatile configuration memory.
> 65536K bytes of processor board System flash (Read/Write)
> 16384K bytes of processor board Boot flash (Read/Write)
> Configuration register is 0x2102
>
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas

Just got a chuckle from this..

We have a 5300 still fired up but it only gets a hit maybe once every three
months..

Gonna turn it down some day.. just waiting for the word. I think we sent
the guy a letter.

I cant help but wonder how a dialup user would even get updates for
Windows10 (chuckle)..

The dialup world..



Ken

Valley Telecom Group





From: cisco-nas [mailto:cisco-nas-bounces@puck.nether.net] On Behalf Of
Joseph Mays
Sent: Monday, June 05, 2017 1:09 PM
To: cisco-nas@puck.nether.net
Subject: [cisco-nas] Windows 10 with AS5400



I kind of never expected to have another question for this list. I'm not
even sure it's still operational. But I guess we'll see.



We have two AS5400's providing dialup services, one in Kentucky, and one
across the river in Indiana. The one in Kentucky has no problems at all.

Recently, a user in Indiana switched to Windows 10, and found that her
dialup connection there no longer worked. She gets connected and logged in,
but then gets 80-90% packet loss. She still has her Windows 8 computer, and
that still works fine with her dialup connection. We went over with a
windows 10 unit, a windows 7 unit, and a linux box, and tried dialup up with
all three. The windows 7 and linux boxed worked fine, the windows 10 unit
had the same problem she did.

We then tried calling another user in Indiana whom we thought had switched
to Windows 10 a while ago. Turns out, he told us, that his dialup connection
never worked with Windows 10, so he switched back to Windows 8.5.



Our memory is that a year ago we were helping a partner in Canada who had
some dialup services with an AS5400, and he found that Windows 10 users
didn't work for him with it, but he just figured it was something with
Windows 10 and didn't worry about it.

Like I said, Windows 10 works fine with the AS5400 in Kentucky, so I tried
isolating differences between those boxes, to the point of making them
identical with IOS, modem setup strings, modem firmware, etc. No difference.
In fact, it made things worse. Many people were failing to connect,
including the woman with the initial problem. Now the Indiana box is back to
the way it was, and just that woman who is trying to use Windows 10 has her
problem of getting connected then being unable to do anything.

Here is the box in Indiana.

indyvoipMG#show ver

Cisco Internetwork Operating System Software

IOS (tm) 5400 Software (C5400-JS-M), Version 12.2(15)T17, RELEASE SOFTWARE
(fc1)

Technical Support: <http://www.cisco.com/techsupport>
http://www.cisco.com/techsupport

Copyright (c) 1986-2005 by cisco Systems, Inc.

Compiled Sat 13-Aug-05 07:51 by kehsiao

Image text-base: 0x6000895C, data-base: 0x61900000



ROM: System Bootstrap, Version 12.0(20000106:234457) [tombnyg-rommon_1_6
106], DEVELOPMENT SOFTWARE REV 1.6

BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.2(7b), RELEASE SOFTWARE
(fc1)



indyvoipMG uptime is 2 days, 2 hours, 59 minutes

System returned to ROM by reload at 13:05:26 EDT Sat Jun 3 2017

System restarted at 13:06:13 EDT Sat Jun 3 2017

System image file is "flash:c5400-js-mz.122-16.T17.bin"



cisco AS5400 (R7K) processor (revision T) with 262144K/65536K bytes of
memory.

Processor board ID JAB03510786

R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache

Last reset from IOS reload

Bridging software.

X.25 software, Version 3.0.0.

SuperLAT software (copyright 1990 by Meridian Technology Corp).

TN3270 Emulation software.

Primary Rate ISDN software, Version 1.1.

Manufacture Cookie Info:

EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,

Board Hardware Version 3.21, Item Number 800-5171-01,

Board Revision 017, Serial Number JAB03510786,

PLD/ISP Version 2.2, Manufacture Date 5-Jan-2000.

Processor 0xFF, MAC Address 0x03096F816

Backplane HW Revision 1.0, Flash Type 5V

2 FastEthernet/IEEE 802.3 interface(s)

178 Serial network interface(s)

108 terminal line(s)

36 Channelized T1/PRI port(s)

1 Channelized T3 port(s)

512K bytes of non-volatile configuration memory.

32768K bytes of processor board System flash (Read/Write)

8192K bytes of processor board Boot flash (Read/Write)



Configuration register is 0x2102


Here is the box in Kentucky.

ArmoryPl-AS5400>show ver

Cisco Internetwork Operating System Software

IOS (tm) 5400 Software (C5400-JS-M), Version 12.3(3i), RELEASE SOFTWARE
(fc1)

Copyright (c) 1986-2005 by cisco Systems, Inc.

Compiled Fri 12-Aug-05 22:07 by ssearch

Image text-base: 0x6000895C, data-base: 0x61900000



ROM: System Bootstrap, Version 12.2(1r)1, RELEASE SOFTWARE (fc1)

BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.1(1)XD1, EARLY DEPLOYMENT
RELEASE SOFTWARE (fc2)



ArmoryPl-AS5400 uptime is 6 days, 6 hours, 58 minutes

System returned to ROM by error - a Software forced crash, PC 0x60453E04 at
09:06:58 EDT Tue May 30 2017

System restarted at 09:07:56 EDT Tue May 30 2017

System image file is "flash:c5400-js-mz.123-3i.bin"



cisco AS5400 (R7K) processor (revision T) with 524288K/131072K bytes of
memory.

Processor board ID JAE09054U8M

R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache

Last reset from warm-reset

Bridging software.

X.25 software, Version 3.0.0.

SuperLAT software (copyright 1990 by Meridian Technology Corp).

TN3270 Emulation software.

Primary Rate ISDN software, Version 1.1.

Manufacture Cookie Info:

EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,

Board Hardware Version 3.34, Item Number 800-5171-02,

Board Revision C0, Serial Number JAE09054U8M,

PLD/ISP Version 2.2, Manufacture Date 26-Jan-2005.

Processor 0x14, MAC Address 0x012801C6694

Backplane HW Revision 1.0, Flash Type 5V

2 FastEthernet/IEEE 802.3 interface(s)

428 Serial network interface(s)

432 terminal line(s)

64 Channelized T1/PRI port(s)

2 Channelized T3 port(s)

512K bytes of non-volatile configuration memory.

65536K bytes of processor board System flash (Read/Write)

16384K bytes of processor board Boot flash (Read/Write)



Configuration register is 0x2102

Thanks for the response! Trying all the client-side suggestions. WRT this, though...
a.. on the infrastructure side, if a router in the affected network path is a Cisco IOS router, then turn on TCP MSS Adjust (set it to 1250 or 1360 or so.)
All the routers in the network path on our system are network routers. Are you suggesting I turn this on for all of them, or just on the AS5400 that answers the dialup connection?

I meant to say they are all cisco routers.

From: Joseph Mays
Sent: Thursday, June 08, 2017 3:46 PM
To: cisco-nas@puck.nether.net
Subject: Re: [cisco-nas] Windows 10 with AS5400

Thanks for the response! Trying all the client-side suggestions. WRT this, though...
a.. on the infrastructure side, if a router in the affected network path is a Cisco IOS router, then turn on TCP MSS Adjust (set it to 1250 or 1360 or so.)
All the routers in the network path on our system are network routers. Are you suggesting I turn this on for all of them, or just on the AS5400 that answers the dialup connection?


--------------------------------------------------------------------------------
_______________________________________________
cisco-nas mailing list
cisco-nas@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nas

Joseph,

As a matter of course, I always just set adjust-mss to 1300 (or whatever
my fancy is that day) on all edge routers, i.e. the routers that are
clients' first-hop gateways.

You might not want to set it on your more core routers, because this
could impact performance. (On the other hand, it might benefit
performance, if it allows you to avoid doing fragmentation [.and even
worse, reassembly, if your routers are tunnel endpoints that do that
sort of thing.])

Now, if you *only* see this problem on your dialup clients, then I
suppose you could be conservative and set it only on your 5400s. But I
can tell you that I absolutely see this problem affecting Windows 10
Creators Update clients in other topologies (e.g. Wi-Fi, which is my
bailiwick nowadays.)

Best regards,

Aaron

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

On 6/8/2017 2:46 PM, mays@win.net (Joseph Mays) wrote:
> I meant to say they are all cisco routers.
> *From:* Joseph Mays
> *Sent:* Thursday, June 08, 2017 3:46 PM
> *To:* cisco-nas@puck.nether.net
> *Subject:* Re: [cisco-nas] Windows 10 with AS5400
> Thanks for the response! Trying all the client-side suggestions. WRT
> this, though...
>
> * on the infrastructure side, if a router in the affected network
> path is a Cisco IOS router, then turn on TCP MSS Adjust (set it to
> 1250 or 1360 or so.)
>
> All the routers in the network path on our system are network routers.
> Are you suggesting I turn this on for all of them, or just on the
> AS5400 that answers the dialup connection?
>
> ------------------------------------------------------------------------
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
>
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas

Thanks for the input Juergen ... it's good to get feedback from the
"real world".

I will note that, in Cisco Unified Wireless, our access points can
perform MSS adust ... and, starting in the 8.5 release later this year,
we will set it to 1250 by default. (On the theory that that should work
well in virtually all topologies, with minimal performance degradation
vs. an MSS of say 1400.)

Cheers,

Aaron

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

On 6/9/2017 12:02 AM, cnsp@marenda.net (Juergen Marenda) wrote:
>
> Hi,
>
> Remember to set it on both/all interfaces, WANs and LANs
>
> (don't know weather it’s a bug or feature, but it helped).
>
> I tend to use (very conservative) 2**10+2**8 = 1280 since that fits
> most environments
>
> (L2TP relayed PPPoE Broadband access with IPsec Tunnel for example)
>
> and is a “well known” value cause of display resolutions ;-)
>
> I don’t set it in the core, only on edge and CPEs since the core
>
> should not be loaded with traffic inspection or tcp-handshake-interaction
>
> but forward packets fast.
>
> My 0.01 $,
>
> Juergen.
>
> *Von:*cisco-nas [mailto:cisco-nas-bounces@puck.nether.net] *Im Auftrag
> von *Aaron Leonard
> *Gesendet:* Freitag, 9. Juni 2017 00:16
> *An:* Joseph Mays; cisco-nas@puck.nether.net
> *Betreff:* Re: [cisco-nas] Windows 10 with AS5400
>
> Joseph,
>
> As a matter of course, I always just set adjust-mss to 1300 (or
> whatever my fancy is that day) on all edge routers, i.e. the routers
> that are clients' first-hop gateways.
>
> You might not want to set it on your more core routers, because this
> could impact performance. (On the other hand, it might benefit
> performance, if it allows you to avoid doing fragmentation [.and even
> worse, reassembly, if your routers are tunnel endpoints that do that
> sort of thing.])
>
> Now, if you *only* see this problem on your dialup clients, then I
> suppose you could be conservative and set it only on your 5400s. But
> I can tell you that I absolutely see this problem affecting Windows 10
> Creators Update clients in other topologies (e.g. Wi-Fi, which is my
> bailiwick nowadays.)
>
> Best regards,
>
> Aaron
>
> ------------------------------------------------------------------------
>
> On 6/8/2017 2:46 PM, mays@win.net <mailto:mays@win.net> (Joseph Mays)
> wrote:
>
> I meant to say they are all cisco routers.
>
> *From:*Joseph Mays
>
> *Sent:*Thursday, June 08, 2017 3:46 PM
>
> *To:*cisco-nas@puck.nether.net <mailto:cisco-nas@puck.nether.net>
>
> *Subject:*Re: [cisco-nas] Windows 10 with AS5400
>
> Thanks for the response! Trying all the client-side suggestions.
> WRT this, though...
>
> * on the infrastructure side, if a router in the affected
> network path is a Cisco IOS router, then turn on TCP MSS
> Adjust (set it to 1250 or 1360 or so.)
>
> All the routers in the network path on our system are network
> routers. Are you suggesting I turn this on for all of them, or
> just on the AS5400 that answers the dialup connection?
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net <mailto:cisco-nas@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nas
>
>
>
>
> _______________________________________________
>
> cisco-nas mailing list
>
> cisco-nas@puck.nether.net <mailto:cisco-nas@puck.nether.net>
>
> https://puck.nether.net/mailman/listinfo/cisco-nas
>

On Mon, 5 Jun 2017, Ken Lotts wrote:

> Just got a chuckle from this..
>
> We have a 5300 still fired up but it only gets a hit maybe once every three
> months..
>
> Gonna turn it down some day.. just waiting for the word. I think we sent
> the guy a letter.

hah! just shut this puppy down..

cas1-pel uptime is 11 years, 36 weeks, 2 days, 7 hours, 5 minutes
System returned to ROM by reload at 05:25:58 SAT Wed Oct 12 2005
System restarted at 05:26:44 SAT Wed Oct 12 2005
System image file is "flash:c5300-is-mz.123-13a.bin"

its been fun and thanks to aaron for his help over the years.

j.

_______________________________________________
cisco-nas mailing list
cisco-nas@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nas

Shame to see these guys go ... the 5300 was one of my proudest
accomplishments at Cisco ... the first all-Cisco (including the MICA
modems from DTD in Chelmsford) access server ... the first one that
actually had enough horsepower to handle a full load (CPU from the 4700
router).  The modems started off shaky but ended up rock solid.  (Even
though admittedly Carla never cared for them too much.)

We still have a 5300 on a PRI in RTP for dialout.  (I still help out
with modem cases from time to time, as there's no call to invest time to
train anyone else on these things.)  I actually trained in V.90 at 48000
bps on Tuesday - pretty sweet!

Cheers,

Aaron

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

On 8/24/2017 8:33 AM, jc@isnet.net (jc) wrote:
> On Mon, 5 Jun 2017, Ken Lotts wrote:
>
>> Just got a chuckle from this..
>>
>> We have a 5300 still fired up but it only gets a hit maybe once every three
>> months..
>>
>> Gonna turn it down some day.. just waiting for the word. I think we sent
>> the guy a letter.
> hah! just shut this puppy down..
>
> cas1-pel uptime is 11 years, 36 weeks, 2 days, 7 hours, 5 minutes
> System returned to ROM by reload at 05:25:58 SAT Wed Oct 12 2005
> System restarted at 05:26:44 SAT Wed Oct 12 2005
> System image file is "flash:c5300-is-mz.123-13a.bin"
>
> its been fun and thanks to aaron for his help over the years.
>
> j.
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas

_______________________________________________
cisco-nas mailing list
cisco-nas@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nas

Hi,

On Thu, Aug 24, 2017 at 12:07:03PM -0700, Aaron Leonard wrote:
> Shame to see these guys go ... the 5300 was one of my proudest
> accomplishments at Cisco ... the first all-Cisco (including the MICA
> modems from DTD in Chelmsford) access server ...

Well done!

I still have a few in production :-) (you might remember) - modem and
ISDN/X.75 dial-in, running an "autocommand telnet ..." to a unix server
that pretends to have proper serial modems talking to a custom
application.

Not really near the capacity that box *could* do (rarely more than 7-8
concurrent calls), though.

Rock-solid indeed, except for the "some X.75 callers cause an input queue
wedge" (so a reboot every 4 weeks or so is needed, when serial0:0 is
finally "full"), and recently we lost a flash module... but recovery
was nice and pleasant as the boot flash has a near-full IOS, so
"just swap the main flash, telnet to boot IOS, re-flash flash:, reboot,
done" :-)

gert

--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert@greenie.muc.de
fax: +49-89-35655025 gert@net.informatik.tu-muenchen.de

Hi,

A great walk down memory lane. I learned my trade by being a Product Manager and Technical Marketing Engineering of the AS5300,AS5350, AS5400, AS 5400XM,AS5800, AS5850.

These product made the world a smaller place and I am proud to have been a part of them.

Wow, 11 year up time on AS5300, NICE!



—
Regards,

Darryl Sladden

Senior TME Manager, Wireless and Location

Cisco

408-219-8485

On 8/24/17, 12:15 PM, "cisco-nas on behalf of Gert Doering" <cisco-nas-bounces@puck.nether.net on behalf of gert@greenie.muc.de> wrote:

Hi,

On Thu, Aug 24, 2017 at 12:07:03PM -0700, Aaron Leonard wrote:
> Shame to see these guys go ... the 5300 was one of my proudest
> accomplishments at Cisco ... the first all-Cisco (including the MICA
> modems from DTD in Chelmsford) access server ...

Well done!

I still have a few in production :-) (you might remember) - modem and
ISDN/X.75 dial-in, running an "autocommand telnet ..." to a unix server
that pretends to have proper serial modems talking to a custom
application.

Not really near the capacity that box *could* do (rarely more than 7-8
concurrent calls), though.

Rock-solid indeed, except for the "some X.75 callers cause an input queue
wedge" (so a reboot every 4 weeks or so is needed, when serial0:0 is
finally "full"), and recently we lost a flash module... but recovery
was nice and pleasant as the boot flash has a near-full IOS, so
"just swap the main flash, telnet to boot IOS, re-flash flash:, reboot,
done" :-)

gert

--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert@greenie.muc.de
fax: +49-89-35655025 gert@net.informatik.tu-muenchen.de


_______________________________________________
cisco-nas mailing list
cisco-nas@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nas