From: Scott Morris (smorris@xxxxxxxxxxxxxx)
Date: Mon Oct 23 2000 - 20:14:32 GMT-3
1. "no exec" can help filter out the "garbage" syndrome. That means that
any character coming IN to the comm server will NOT be used to trigger an
exec session. If you think about how your're connected, to the console port
of the other devices, many messages get logged to the console ports, so you
don't want each one making the term-server think about something. So "no
exec" tells it to ignore incoming messages and not think about them.
2. 8 A/S ports usually. The 2509's and 2511's are great examples! With a
2509-RJ model (8 RJ-45 ports), you can simple plug in those cisco rolled
cables into the ports, and you're ready to go. With the 2511, you have
octopus cables which then connect into the console ports of other units.
Those are Cisco's 8/16 port versions.
If you're really feeling adventurous, and want to connect LOTS of equipment,
there is a NM-32A/S module for the 3600 series routers that will connect to
32 devices through octopus cables. So on a 3660, you can handle 192 console
port connections! That's one hell of a lab! :)
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jack Heney
Sent: Monday, October 23, 2000 6:05 PM
To: ccielab@groupstudy.com
Subject: Lab server configuration
>From Cisco's Networkers 2000 CCIE prep seminar:
When connecting to the rack via RS@#@, an incorrect communications server
configuration can cost considerable time during the day.
COMMUNICATIONS SERVER:
hostname RtrA
!
line 1 8
no exec
modem callout
transport input all
ATTACHED ROUTER:
hostname RtrB
!
line con 0
exec-timeout 0 0
Two quick questions:
1. Why "no exec" on the comm server?
2. Is the comm server simply a router with 8 async serial ports? What sort
of cable is used to connect these to the attached routers' console ports
(I'm assuming its a rollover rj-45 with an adapter on the comm server)?
Thanks,
Jack
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:29 GMT-3