Call Toll-Free 1.888.765.8301
And Speak With A Live Telecom Consultant!
Real-Time Telecom Price Quote Tool:
Service Type:
Your Name:
Company:
Email:
Installation Phone Number: ()-


For HughesNet Satellite Internet Services
Call Toll Free: 1-877-247-5156


Cisco CCNA / CCNP Dwelling Lab Tutorial: Configuring An Access Server

As your CCNA / CCNP residence lab expands, an access server such because the Cisco 2509 or 2511 is likely one of the best investments you may make.  On this article, we’ll take a look at the basic configuration for an access server and talk about how to hook up with the opposite routers and switches in your pod via the AS.

This is a part of a configuration from one among my access servers:

ip host FRS 2006 100.1.1.1

ip host SW2 2005 100.1.1.1

ip host SW1 2004 100.1.1.1

ip host R2 2002 100.1.1.1

ip host R1 2001 100.1.1.1

ip host R3 2003 100.1.1.1

interface Loopback0

 ip handle 100.1.1.1 255.255.255.255

 no ip directed-broadcast

That is an IP Host desk, and this is what makes your complete AS setup work.  Your PC will connect to the access server, and the access server is in turn physically connected to your different routers and switches through an octal cable.  One end of the octal cable splices off into eight separate cables, every terminated with an Rj-45 connector.  That connector will likely be placed into the console port of one in every of your home lab devices.  On this configuration, I’ve connector 1 related to the console port of R1, connector 2 to R2, connector 3 to R3, connector 4 to Sw1, and so forth.  (The connectors are physically numbered as well.)
Mallard Ducks: Most Popular Duck Species
The IP Host desk entries listed here are linked to the loopback deal with shown.  The loopback might be any handle, but it surely should match the handle in the IP Host table.  This lets you create reverse telnet sessions to the routers and switches.

To open the reverse telnet classes upon opening a connection to the AS, sort the complete name of the device and press the enter key twice.  A connection to that device will now be seen, as shown here:

Access_Serverr1

Making an attempt R1 (100.1.1.1, 2001)… Open

R1

To get back to the entry server, use the key combination <CTRL-SHIFT-6> adopted by pressing the “x” key.  Keep doing this till you’ve got opened a connection to each router and swap in your pod.

As soon as you’ve got opened the strains, you’ll not use the full device identify to connect to the house lab devices.  You must press only the quantity comparable to the reverse telnet session you opened.  For instance, on this configuration I opened telnet session 1 to R1, session 2 to R2, and session 3 to R3.  As soon as I opened those sessions, I simply use those numbers to reconnect to the units, as proven here:

Access_server1

[Resuming connection 1 to r1 ... ]

R1

Access_server2

[Resuming connection 2 to r2 ... ]

R2

Access_server3

[Resuming connection 3 to r3 ... ]

R3

For those who type the total hostname once more after initially opening the connection, you will see this message:

Access_serverr1

Trying R1 (100.1.1.1, 2001)…

% Connection refused by distant host

The connection is refused because you already have an open connection to that router.

There’s one more necessary part of an entry server config your CCNA / CCNP residence lab will want:

line 1 8

 no exec

 transport enter all

The line numbers could differ in line with your access server, but “no exec” is essential here.  This may cease rogue EXEC sessions from refusing connections that it should not be refusing. Without this command, you’ll generally see “connection refused by distant host” while you shouldn’t be.  That message is the most typical error you may see on an entry server, and it is there because you already have an open connection or you left “no exec” out of your configuration. “No exec” is not obligatory, however it’ll assist you keep your sanity!

Me and you can easily to  make translation  this article with free translation software