From: Tracy Blackmore (TracyB@xxxxxxxxx)
Date: Mon Oct 23 2000 - 07:44:48 GMT-3
Jack;
The "no exec" keeps the console port from activating a session on the
comm. server. Without this, every message sent to the console would
activate the session and you would have to clear it manually before you
could log in.
Yes, the comm. server is a router with async ports. Roll-over cables
for some models and oct-cables for others (all RJ-45 on the managed router
side)
Tracy W. Blackmore
T.S. Lad Consulting
1026 E Stanford Ave.
Gilbert, AZ., 85234
(480)558-0472
-----Original Message-----
From: Jack Heney [mailto:jheneyccie@hotmail.com]
Sent: Monday, October 23, 2000 3: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