Hi,
I recently acquired as part of a job lot a 2511 access server. I purchased the require CAB-OCTAL-ASYNC cables (albeit not the Cisco brand ones) for it, and they've just arrived. Now I'm not getting anything through those ports connected to a console that is known working with my console cable from my PC.
I don't have any problems setting up reverse telnet sessions to the async lines, but I don't get anything, or only garbage, out of them.
[first connected with console to a router] 2501-1# [switching console cable to the 2511, and plugging cable 5 on port 1 into the console port I just had -- this is just an example, all ports do the same as far as I can tell] 2511#R5 Trying R5 (192.168.3.1, 2005)... Open [nothing, then in response to say, hitting , garbage characters] [ctrl-shift-6 X] 2511# [switch console cable back to 2501-1, check command history] 2501-1#`~~~~ [and more like that]So what appears to be happening is that there *is* physical data going out those cables, and some getting through back, but it is all garbled.
Is this likely to be a configuration issue or a hardware issue? Hardware in question is a bit iffy[1], configuration is good AFAICT[2]. Incidentally, line 17, the Aux, when connected via rollover to a console port, works just fine, including the reverse telnet bits, when I'm not using it to route packets over.
Jasper
[1] This 2511 initially refused to boot with a bad memory error, even with flash and dram simms removed. It was one of the 2511s with 2 megs onboard, which had the error, apparently. After removing those 4 memory chips from the motherboard, it booted again quite happily, using the simm, and I thought I'd fixed the problem. However, earlier today it was again giving memory errors, and stopped doing that only after I'd thumped it once or twice [percussive maintenance]. Also, the AUI interface simply doesn't work. IOW, I'm not that confident about the hardware. The cables I can't be 100 percent sure about, as I haven't (and can't) tested them on a separate machine, but it would be odd for two cables to fail on all 8 ports simultaneously. [2] I've tried it both with the async lines configured as standard, or with explicitly setting speed 9600 databits 8 flow none stopbits 1, only the last of which comes up in the config at all.