|
Doug_Kenline
20 posts
 |
Ok I finished my 3rd four-hour lab today. All half-rack lab sessions. First two sessions on blocka. Third session on blockb. One observation I had is this. If you are only using half of the rack, for example block A, or block B. Then one of your first steps would be to admin down and secure every port that you do not control both ends of the link on. It seems to me that if I am on block B for example, then I have no control over the configurations on Switch 1 or Switch 3. Therefore it seems that the only prudent thing to do would be to shutdown all interfaces leading to either one of those devices. And I suppose it would be safe to say that this would just be the thing to do when planning out your lab strategy. For example, determine which ports and which devices will be used in your lab. Then shutdown and secure all other ports before even starting your lab. Then it would be nice to go ahead and log in to each network element that will be involved in your lab. Get the console windows layed out on your desktop so you can easily move quickly back and forth between the network elements that are involved in your lab. Like in my lab that I was trying to do today. I figured I would use Router 2 and Router 6. And Switch 2 and Switch 4. I shut down and secured all unused ports. So I had 4 network elements involved in my lab. So I got 4 console sessions going and layed them out on my desktop like this here. (Still trying to figure out how to post a picture here at PacketLife community forum.) Now that would be great if those console sessions would just sit there like a rock for the duration of your lab. Unfortunately, my console sessions keep disappearing on me. Disconnecting. Causing me to have to telnet back in, login with username and password, and then readjust the console window on my desktop so it fits back in nice where it was before the dang thing disconnected on me and disappeared. I put the exec-timeout 0 0 under just the vty lines before and I asked about it here and think I heard that I should try putting it under the console 0 line as well. So I tried that but still getting disconnected console sessions. Some sessions seem to hang for a long time and others go away while you're over working on something else. Here's how I had it. R2#show run ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 exec-timeout 0 0 login ! R6#sho run ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 exec-timeout 0 0 login ! S2#sho run ! line con 0 exec-timeout 0 0 line vty 0 4 exec-timeout 0 0 login line vty 5 15 exec-timeout 0 0 login ! S4#show run ! line con 0 exec-timeout 0 0 line vty 0 4 exec-timeout 0 0 login line vty 5 15 exec-timeout 0 0 login ! But the sessions kept disconnecting on me anyway. Next time I'll try ssh. And also next time I'll try to keep a closer eye on how long the session holds before going away. But I did get some good labbing done nonetheless. So my lab of the day was Etherchannel lab. Now it came to my mind that there could be a finite list of every conceivable lab that could be envisioned to be done on half a rack of equipment, for example, block A or block B. Perhaps as a community we could gradually compile such a list along with detailed instructions to go along with each and every 1/2 rack lab scenario. The scenarios could be arranged in order of complexity from admining up a router port, to something that might even challenge a CCIE. So there is my first question for this lab community. How complex of labs could be conceived of with this limited half-rack of equipment? Could we title these lab scenarios to make them much like a graded mock lab? So if a student here were to say repeat every possible lab scenario 100 times he would be well prepared for yes, even, the dreaded CCIE Lab!? Or would 1/2 rack just not be quite able to whip up enough complexity to rank at that level? Might need the entire rack of equipment, block A AND block B, to generate CCIE Lab complexity level lab scenarios? Not sure but at this time I am just trying to concentrate on simpler one-half-rack lab scenarios. Not having the time to write up that list at the moment I will start out with Half Rack Lab Number 00000001.
The Block B Etherchannel Lab Scenario.
Complexity Level: beginner, ccna, bcmsn
Time to complete: 1 hour
Objective: bring up the 4 network elements shown in figure A-1.
shut down and secure any ports that are not used in your topology.
assign ip addresses to router ports
get extended pings going from each router to the other router
watch those extended pings while you dink around with the trunk
you see the trunk consists of 3 fastethernet links
you see the links like this....
S2#sho ip int brief Interface IP-Address OK? Method Status Protocol Vlan1 unassigned YES NVRAM administratively down down FastEthernet0/1 unassigned YES unset administratively down down FastEthernet0/2 unassigned YES unset down down FastEthernet0/3 unassigned YES unset administratively down down FastEthernet0/4 unassigned YES unset down down FastEthernet0/5 unassigned YES unset administratively down down FastEthernet0/6 unassigned YES unset down down FastEthernet0/7 unassigned YES unset administratively down down FastEthernet0/8 unassigned YES unset administratively down down FastEthernet0/9 unassigned YES unset administratively down down FastEthernet0/10 unassigned YES unset administratively down down FastEthernet0/11 unassigned YES unset administratively down down FastEthernet0/12 unassigned YES unset administratively down down FastEthernet0/13 unassigned YES unset administratively down down FastEthernet0/14 unassigned YES unset administratively down down FastEthernet0/15 unassigned YES unset administratively down down FastEthernet0/16 unassigned YES unset administratively down down FastEthernet0/17 unassigned YES unset administratively down down FastEthernet0/18 unassigned YES unset administratively down down FastEthernet0/19 unassigned YES unset up up FastEthernet0/20 unassigned YES unset up up FastEthernet0/21 unassigned YES unset up up FastEthernet0/22 unassigned YES unset administratively down down FastEthernet0/23 unassigned YES unset administratively down down FastEthernet0/24 unassigned YES unset administratively down down GigabitEthernet0/1 unassigned YES unset administratively down down GigabitEthernet0/2 unassigned YES unset administratively down down Only fastethernet 0/2 and 0/19 - 21 are a part of this lab. I just hadn't shut down 0/4 and 0/6 yet above. And like this. S2#show int status Port Name Status Vlan Duplex Speed Type Fa0/1 notconnect 1 auto auto 10/100BaseTX Fa0/2 notconnect 1 auto auto 10/100BaseTX Fa0/3 notconnect 1 auto auto 10/100BaseTX Fa0/4 notconnect 1 auto auto 10/100BaseTX Fa0/5 notconnect 1 auto auto 10/100BaseTX Fa0/6 notconnect 1 auto auto 10/100BaseTX Fa0/7 notconnect 1 auto auto 10/100BaseTX Fa0/8 notconnect 1 auto auto 10/100BaseTX Fa0/9 notconnect 1 auto auto 10/100BaseTX Fa0/10 connected 1 a-full a-100 10/100BaseTX Fa0/11 notconnect 1 auto auto 10/100BaseTX Fa0/12 notconnect 1 auto auto 10/100BaseTX Fa0/13 connected trunk a-full a-100 10/100BaseTX Fa0/14 connected trunk a-full a-100 10/100BaseTX Fa0/15 connected trunk a-full a-100 10/100BaseTX Fa0/16 connected trunk a-full a-100 10/100BaseTX Fa0/17 connected trunk a-full a-100 10/100BaseTX Fa0/18 connected trunk a-full a-100 10/100BaseTX Fa0/19 connected trunk a-full a-100 10/100BaseTX Fa0/20 connected trunk a-full a-100 10/100BaseTX Fa0/21 connected trunk a-full a-100 10/100BaseTX Fa0/22 notconnect 1 auto auto 10/100BaseTX Fa0/23 notconnect 1 auto auto 10/100BaseTX Fa0/24 notconnect 1 auto auto 10/100BaseTX Gi0/1 notconnect 1 auto auto unknown Gi0/2 notconnect 1 auto auto unknown Only fastethernet 0/2 and 0/19 - 21 are a part of this lab. I just hadn't shut down the other ports yet above. I turned off the dynamic trunking stuff on my router port and secured the port with switchport mode access. The before and after shots are shown below. Before... S2#show int fastEthernet 0/2 switchport Name: Fa0/2 Switchport: Enabled Administrative Mode: dynamic desirable Operational Mode: static access Administrative Trunking Encapsulation: negotiate Operational Trunking Encapsulation: native Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Administrative Native VLAN tagging: enabled Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk Native VLAN tagging: enabled Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk associations: none Administrative private-vlan trunk mappings: none Operational private-vlan: none Trunking VLANs Enabled: ALL Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Protected: false Unknown unicast blocked: disabled Unknown multicast blocked: disabled Appliance trust: none After... S2#sho int fastEthernet 0/2 switchport Name: Fa0/2 Switchport: Enabled Administrative Mode: static access Operational Mode: static access Administrative Trunking Encapsulation: negotiate Operational Trunking Encapsulation: native Negotiation of Trunking: Off Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Administrative Native VLAN tagging: enabled Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk Native VLAN tagging: enabled Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk associations: none Administrative private-vlan trunk mappings: none Operational private-vlan: none Trunking VLANs Enabled: ALL Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Protected: false Unknown unicast blocked: disabled Unknown multicast blocked: disabled Appliance trust: none All my fastethernet ports on the trunk side were set up just like Fast 0/19. S2#show int fastEthernet 0/19 switchport Name: Fa0/19 Switchport: Enabled Administrative Mode: dynamic desirable Operational Mode: trunk Administrative Trunking Encapsulation: negotiate Operational Trunking Encapsulation: isl Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Administrative Native VLAN tagging: enabled Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk Native VLAN tagging: enabled Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk associations: none Administrative private-vlan trunk mappings: none Operational private-vlan: none Trunking VLANs Enabled: ALL Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Protected: false Unknown unicast blocked: disabled Unknown multicast blocked: disabled Appliance trust: none So long story short, I tried to bundle these three 100 Mbps links together into an etherchannel. I ended up with a problem. S2#sho int status Port Name Status Vlan Duplex Speed Type Fa0/1 disabled 2 auto auto 10/100BaseTX Fa0/2 connected 1 a-full a-100 10/100BaseTX Fa0/3 disabled 2 auto auto 10/100BaseTX Fa0/4 disabled 2 auto auto 10/100BaseTX Fa0/5 disabled 2 auto auto 10/100BaseTX Fa0/6 disabled 2 auto auto 10/100BaseTX Fa0/7 disabled 2 auto auto 10/100BaseTX Fa0/8 disabled 2 auto auto 10/100BaseTX Fa0/9 disabled 2 auto auto 10/100BaseTX Fa0/10 disabled 2 auto auto 10/100BaseTX Fa0/11 disabled 2 auto auto 10/100BaseTX Fa0/12 disabled 2 auto auto 10/100BaseTX Fa0/13 disabled 2 auto auto 10/100BaseTX Fa0/14 disabled 2 auto auto 10/100BaseTX Fa0/15 disabled 2 auto auto 10/100BaseTX Fa0/16 disabled 2 auto auto 10/100BaseTX Fa0/17 disabled 2 auto auto 10/100BaseTX Fa0/18 disabled 2 auto auto 10/100BaseTX Fa0/19 err-disabled 1 auto auto 10/100BaseTX Fa0/20 err-disabled 1 auto auto 10/100BaseTX Fa0/21 err-disabled 1 auto auto 10/100BaseTX Fa0/22 disabled 2 auto auto 10/100BaseTX Fa0/23 disabled 2 auto auto 10/100BaseTX Fa0/24 disabled 2 auto auto 10/100BaseTX Gi0/1 disabled 2 auto auto unknown Gi0/2 disabled 2 auto auto unknown Po1 err-disabled 1 auto auto S4#show int status Port Name Status Vlan Duplex Speed Type Fa0/1 disabled 1 auto auto 10/100BaseTX Fa0/2 disabled 1 auto auto 10/100BaseTX Fa0/3 disabled 1 auto auto 10/100BaseTX Fa0/4 disabled 1 auto auto 10/100BaseTX Fa0/5 disabled 1 auto auto 10/100BaseTX Fa0/6 connected 1 a-full a-100 10/100BaseTX Fa0/7 disabled 1 auto auto 10/100BaseTX Fa0/8 disabled 1 auto auto 10/100BaseTX Fa0/9 disabled 1 auto auto 10/100BaseTX Fa0/10 disabled 1 auto auto 10/100BaseTX Fa0/11 disabled 1 auto auto 10/100BaseTX Fa0/12 disabled 1 auto auto 10/100BaseTX Fa0/13 disabled 1 auto auto 10/100BaseTX Fa0/14 disabled 1 auto auto 10/100BaseTX Fa0/15 disabled 1 auto auto 10/100BaseTX Fa0/16 notconnect 1 auto auto 10/100BaseTX Fa0/17 notconnect 1 auto auto 10/100BaseTX Fa0/18 notconnect 1 auto auto 10/100BaseTX Fa0/19 disabled 1 auto auto 10/100BaseTX Fa0/20 disabled 1 auto auto 10/100BaseTX Fa0/21 disabled 1 auto auto 10/100BaseTX Fa0/22 disabled 1 auto auto 10/100BaseTX Fa0/23 disabled 1 auto auto 10/100BaseTX Fa0/24 disabled 1 auto auto 10/100BaseTX Gi0/1 disabled 1 auto auto unknown Gi0/2 disabled 1 auto auto unknown Po1 notconnect unassigned auto auto S2#show run ! interface FastEthernet0/19 switchport mode dynamic desirable channel-group 1 mode on ! interface FastEthernet0/20 switchport mode dynamic desirable channel-group 1 mode on ! interface FastEthernet0/21 switchport mode dynamic desirable channel-group 1 mode on ! S4#show run ! interface FastEthernet0/16 switchport mode dynamic desirable channel-group 1 mode on ! interface FastEthernet0/17 switchport mode dynamic desirable channel-group 1 mode on ! interface FastEthernet0/18 switchport mode dynamic desirable channel-group 1 mode on !
S2#show int port-channel 1
Port-channel1 is down, line protocol is down (err-disabled)
Hardware is EtherChannel, address is 000f.345f.1695 (bia 000f.345f.1695)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:07:54, output 00:07:54, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
19190 packets input, 2833370 bytes, 0 no buffer
Received 106 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 106 multicast, 0 pause input
0 input packets with dribble condition detected
19057 packets output, 2817298 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
S4#show int port-channel 1
Port-channel1 is down, line protocol is down (notconnect)
Hardware is EtherChannel, address is 0000.0000.0000 (bia 0000.0000.0000)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
S2#show int fastEthernet 0/19 switchport Name: Fa0/19 Switchport: Enabled Administrative Mode: dynamic desirable Operational Mode: down (suspended member of bundle Po1) Administrative Trunking Encapsulation: negotiate Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Administrative Native VLAN tagging: enabled Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk Native VLAN tagging: enabled Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk associations: none Administrative private-vlan trunk mappings: none Operational private-vlan: none Trunking VLANs Enabled: ALL Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Protected: false Unknown unicast blocked: disabled Unknown multicast blocked: disabled Appliance trust: none
S2#show etherchannel port-channel
Channel-group listing:
----------------------
Group: 1
----------
Port-channels in the group:
---------------------------
Port-channel: Po1
------------
Age of the Port-channel = 0d:00h:29m:07s
Logical slot/port = 1/0 Number of ports = 0
GC = 0x00000000 HotStandBy port = null
Port state = Port-channel Ag-Not-Inuse
Protocol = -
Port security = Disabled
Time since last port bundled: 0d:00h:29m:07s Fa0/21
Time since last port Un-bundled: 0d:00h:28m:18s Fa0/21
Long story short, I was just trying to do a lab write-up. I watched Chris Bryant 5 part Etherchannel videos here. I tried to shut and no shut all of the ports but it wasn't seeming to work. Then I ran out of time but I think I'll get it working next time. Now I have to go and see if I can get myself some more rack time. I see it's filling up pretty fast now. |
|
thepickle
1 post
 |
hey doug, It can be really annoying when those telnet sessions dump... tcp-keepalives may help. http://www.cisco.com/en/US/tech/tk801/tk36/technologies_tech_note09186a00801365f3.shtml and for the FEC trunks... did you try using dot1q vs. ISL encapsulation? thanks for your detailed post and good luck with your efforts File Attachments |
|
owd_mon
2 posts
 |
Hi Doug, Currently studying for the BCMSN like yourself, and have completed my first 2 hours rack rental - thanks to Stretch and all other parties involved for all their efforts in creating and maintaing the racks. Found the experience on the multilayer switches great - need a lot more practice though. I have a couple of 2950 switches and an handful of 2500 series routers which allow me to practice most of the course material. Would love to have a multilayer switch in my rack but out of my price range at the moment. Like yourself I logged onto all the units I was going to use and arranged them on my desktop. Again like yourself, I had sessions disconnecting. Secondly, like yourself I believe you need to have tasks to acheive to make the rental beneficial. The main thrust of my lab work was routing on the switches - assigning IP addresses to VLANS, creating VLAN access control lists. I would appreciate any lab ideas. I do not like the idea of hiring both racks at the same time, but the opportunity to work with more than 2 switches appeals to me. I would thus be able to test some of the Spanning Tree subject matter . For example create a MST region using two of the switches and see the interaction with PVST running on the other switches - I need to clarify the finer details of how this lab would work. Again any suggestions would be appreciated. But would I hire out both racks at the same time? Sorry to hear about the issues you are having re rommon. I am having this issue with a 1751 router. I believe this could be due to issues with flash memory. I dont have time to realy investigate and as this is not an important issue for me at the moment as I have other kit available I have not investigated. |
|
Doug_Kenline
20 posts
|
Thanks guys. I didn't get to try that tcpkeepalive yet pickle. Got on again for 4 hours on blockb. Brought up console on all 6 devices. Lost 4 windows over the course of my lab but was just concentrating on the 2 switches so I didn't bother with the session timeout issue. I do want to give that a try though and I will next time. Thanks. owd_mon I have hired out both blocks for next Sunday night 7 pm to 11 pm so I will see what I can think of to do with 4 switches. Thanks. Update: And yes I did get that etherchannel working. I got in and did the same thing and had the same problem. Then I just couldn't figure it out so I said why the heck is the dang thing working on my dynamips lab with only one single trunk link but it won't work on the real equipment with the 3 fastethernet trunk links. So I shutdown two of the links and did a shut/no shut on the last remaining link and the dang thing came up and then I added in the other two links and there was the port-channel 1 up/up with bandwidth of 300000 kbps. I had also hardcoded the trunk encapsulation to dot1q and hardcoded the switchport mode to trunking. It had been sitting at the default of dynamic desireable. Maybe that also had something to do with it. Will definitely try again Sunday night because I have both blocks scheduled and want to make the 6 three-member etherchannels and then take a look at Spanning Tree Protocol. |
|
cmcisco
5 posts
|
I did try out both commands tcp-keepalives-in & tcp-keepalives-out. They didn't work as expected. Telnet sessions are still be disconnected after idling for a while. I think it might be something to do with the configuration on the console server Opengear CM4116. Doug, please try these two commands by yourself see if they work. Just in case I didn't configure them right. |
|
cmcisco
5 posts
|
Updates regarding session disconnection: I found that the terminal software SecureCRT has anti-idle function. It may be a solution. I will try it during my next lab time. |
|
Doug_Kenline
20 posts
|
Ok I had both blocks of equipment last night for 4 hours. I brought up several sessions and configured them as you see below in hopes of having all of the console sessions stay up for the duration of the lab. R1#show run ! service tcp-keepalives-in service tcp-keepalives-out ! line con 0 exec-timeout 0 0 line aux 0 exec-timeout 0 0 line vty 0 4 exec-timeout 0 0 login ! However, this did not work and the console sessions began to disappear one by one after about maybe 15 minutes I would say. Which I suppose is not that big of a deal, it just seems to me that there should be some way to keep the console sessions from timing out. So then I just went about my labbing with the understanding that the console session would eventually timeout and there was no use in worrying about it. Just log back in when you need that particular network element. So I worked with the four switches and was able to bring up the 6 etherchannel links with no problem. Then on one of the etherchannel links I changed the protocol to PAgP and on another etherchannel I changed the protocol to LACP. And that worked so I was happy about that. Then I did some show commands on spanning tree and vtp. And then I made three of the switches to be VTP clients and one switch the VTP server. Then I created a new VLAN on the server and verified that it did appear on all of the clients. So that was about it. I started thinking that my time might be better spent just studying the book towards the BCMSN exam. So I logged out of the rack and went back to the book. The lab is good but I seem to like having more structure to what I am doing. I don't mind just going in and trying to think up something to do but sometimes I think that my time might be better spent doing practice exams and reading well structured study material. I guess if during my studies I think of something that I could do on the lab then I will schedule some more time. Until then I think I will focus on reading and taking practice exams. Buenos tardes Amigos. |
|
dan
5 posts
|
Hi Doug, I've been using CMD windows + OpenSSH + WinTabber for accessing the lab. Although the free version of WinTabber only allows 4 "Tabs" it is much easier to use the keyboard to move between "Tabs" using CTRL + "Tab". OpenSSh is useful for it's security but in this case more for the ability to use a single line to access the lab devices. I've simply got the following in a text file on the desktop : "ssh -p 3010 blockb@packetlife.dnsalias.net" I also copy the session password in to the text file. So putting it all together: Before session starts 1.Open 4x CMD windows 2.Open WinTabber and add the 4x CMD boxes in to the application 3. Paste "ssh -p 3010 blockb@packetlife.dnsalias.net" in to each of the CMD boxes 4. Modify the command to suit the device you are accessing by changing the Port (3010 in example) + the relevent username by changing the a or b before the @ 5. Rename tabs as you see fit 6. CTRL + C the password from the text file When session starts 7. Hit enter in the first CMD box and paste the password in (saves typing it in - you may have to use the right click menu to paste it in) 8. Do the same for the remaining tabs. If you session disconnects simply up arrow press enter and paste back in the password. This is a nice way to save much tying just to log in to the rack and should hopefully save you a bit of time should you be prematurely disconnected. I take full responsibility for this ideas useful/time-saving or uselessness/lameness. There may well be better tools that are more efficient. In fact i think i remember someone wrote a script to have all this up are ready automatically. Was originally done for GNS3 i think ... hmm... i'll have a look. Hope this is some use ;-) |
|
dan
5 posts
|
Hi again, I read the rest of your posts. Re: Connection problems. When you are logging in to the equipment you are logging in to the console port. The only time you log in to the vty (telnet) lines of a router/switch is when you are physically on the network. This environment (lab/rack) is a closed system and has no outside connectivity. So you don't need to worry about the vty lines. The line as below: line con 0 exec-timeout 0 0 <---- The exec-timeout is just going to time out your exec session i.e Privilaged mode. This is when the Privelaged mode curser? i.e Router# reverts back to user mode i.e Router> where you can only use user commands and will have to type enable to go back to privelaged mode. (of course this won't happen here as you set it "0 0" or simpy don't time out my session) This won't have any bearing on your (remote) sessions disconnecting The TCP keep-alives won't matter as this lab/rack is managed out of band via the console ports and the lab is a closed system. I suspect that it is simply your internet connection. It could well be a multitude of things. More than likely something you don't have control over.I guess it will something to do with that vast expanse of cable which is the internet. Could be packet loss, could be a firewall saving memory by trimming it's state table. Probably just something deleting any idle session after X minutes. Your sessions may hang as well depending on the flow of packets on you providers network or stretch's for that matter or infact anything in between. I would recommend tying out something similar to what i suggested in the above post. Hopefully it will make things a bit easier or at-least reduce the typing ;-) |
Viewing 1 - 9 of 9
- 1