When you telnet to a router it starts an exec session on the router that you telnet to and starts a telnet session on the router that you telnet from. The show sessions command shows how many sessions have been established from the exec session in which it executes. In the lab at step 19 you telnet to the Birmingham router. This starts an exec session on the Birmingham router. When you do show sessions it looks for any telnet sessions that have been started from that exec session (on Birmingham) and there are none. When you do Ctrl, SHFT6 and x it suspends the telnet session and puts you back in your original exec session and show sessions does show that there are active telnet sessions.
I believe the key to understanding this is to focus on which exec session is executing the command. If executed in the exec session on the router that you just telnet to then there will not be active sessions. If executed in the exec session on the original router there will be active sessions.
Thank you rick. I am still trying to work this out logically, so let me see if I get this right:
forgoing the "no hostname" sequence in that lab, and going straight into the telnet portion, this is what we get:
GAD>telnet PHX !
PHX>telnet BHM !
BHM>telnet PHX !
PHX>telnet GAD !
Now, I should have:
a session on GAD for phoenix and birmingham,
a session on BHM for phoenix
a session on PHX for bitmingham and gadsen
At least, that is what I believe I should have, and according to the lab, it asks for a number of open sessions - not whether you had one or not. These labs are fairly 'directing' with their questions, so you can pretty much assume what "type" of answer they are looking for. From what I see, I should be able to issue the following command:
!!and I should get a screen similar to the following:
Conn Host Address Byte Idle Conn Name
* 1 172.16.1.10 172.16.1.10 0 0 172.16.1.10
2 172.16.1.11 172.16.1.11 0 12 PHX
but you are saying that it is only going to show what sessions were suspended before I left birmingham the first time? So I can't telnet in, out, then back in, out and back in again and expect to see any sessions? Sorry if I sound confused - but I am! LOL
Having taught Cisco classes for a good amount of time I am aware of their tendency to make labs pretty directing and having looked through the instructions for this lab I agree that it does kind of direct you toward answers. I believe that there are several objectives that they want to achieve in this lab and they include emphasizing that you can telnet to a router, from that router you can telnet to another router, can suspend that telnet session, can telnet to another router (stringing a series of telnet sessions together); that you can have multiple telnet sessions from a single router (and from a single exec session) to multiple destinations; that you can suspend one telnet session and can resume another telnet session.
I also believe that they want to help you understand the concept of an exec session and of a telnet session. You start an exec session when you log into a router. When you successfully telnet to another router it starts an exec session on that router. If you suspend the telnet session, then you return to the original exec session. When you do show session you exhibit the sessions started from that exec session.
As I understand your summary, there will be two exec sessions on BHM (the first session created when you telnet from PHX to BHM and the second when you telnet from GAD to BHM). The first exec session will show a session (because you telnetted from BHM to PHX) and the second exec session will not show any sessions. The point is to understand the concept of multiple exec sessions existing on the router at the same time.
It might be interesting to compare the results of show user (which shows all sessions on a particular router) with the result of show session (which shows any sessions created from a particular exec session).
Thank you again rick. I will try this lab again on friday in the class (where I can chain the 3 routers together) and see what the results of that are. But, I see now what you mean. So, again, thank you. I will leave this message as not totally answered until I can come back in and post the results on friday of redoing the lab with the show users option.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...