|
Lab Instructions & Reference Information Document last updated on: Monday July 02, 2007 12:33:18 AM -0400 *Please contact support@networkforce.com for all questions. Due to resource limitation, Email reply may not be in real-time. Table of Content
Appendixes:
1.
How to remotely operate the lab
"telnet nflab.dyndns.org" from your PC Username:
you@your-email-address.com (enter your "Email
Address" registered with our
WebStore) *HOWEVER, if you can not log on to the lab using your email, please try: Username: "guest1"
Step 2 - Power-on the lab devices: From "D17" command line, just type the hostname "power". Login: guest1 ### this is the
default
login for every lab customer "power" is the host name configured for the power control unit in the lab. We use an APC SmartSwitch to remotely control the power electricity in the lab.
Click here for a step-by-step
Power-on example given in Appendixes). Step 3 - Start working on the lab devices: Start the reverse-telnet TTY
connections from the terminal router into all lab devices' console ports. You can find
out the lab devices' host names on "D17" by using command "show
hosts". If you need helps on "reverse-telnet",
please refer to the step-by-step example given in Appendixes. The following are a few useful tips concerning the lab: 1.1 After turning on the power in the lab, please
wait at least 3 minutes for all devices to boot up and initialize. Then you'll
be able to see the devices' login prompts. 1.2 Because we require each lab customers to power-off
the entire lab at the end of each lab session, you will need to power-on all the lab equipment when starting your own
lab session. 1.3
Lab Routers /
Switches console ports are physically connected to "D17" Terminal TTY lines in the following
order: D1
---------------------------------- TTY line 1 of "D17" 1.4 Please do NOT leave any passwords on any lab
routers/switches at the end of your lab session. It may require our lab
administrator to be physically present in the lab in order to recover the
password. Our lab administrators do NOT put passwords on any lab devices either, except
"D17" Terminal Router. 1.5 Use "show
clock"
on the terminal router ""D17"" to find out currently
what time it is at the lab location so that you can tell when you start it
or will finish the lab session. It is configured to show you the New
York Local Time that the lab uses. 1.6 If two lab customers happen to run into each other in the terminal
router "D17" at the
same time (this is very rare but…), two customers may communicate using
the terminal commands such as “who”
(to find out who’s currently logged in) and "send *" (to send terminal messages to other lab customers in
the lab). Using "Ctrl Z"
to send out messages when finished. FYI, these commands are only available in
"enable" mode. By default, each lab customer has limited access to
certain “enable” mode commands). If issues
still can’t be resolved, please don't forget to use the last resort to email us (normally this is not needed). Our lab
admin sometimes will communicate with you using the same commands. 2. How to use Frame Relay in the lab Encapsulation
= FRAME-RELAY
"atm" or “D12” - Cisco LS1010 ATM Switch – Recommended
Sample Configuration: ! 4. How to use ISDN in the lab 4.2 "D2" interface BRI 0 is
connected to Port-1 of the ISDN simulator with the following default setting: SPID1=0835866101; dial string
1 18008358661 *Either
1 of these 2 dial # will work Reloading
the router will help clear any wrong ISDN setting cached
on the switch. 4.3 "D3" interface BRI 0 is
connected to Port-2 of the ISDN simulator with the following default settings: SPID1=0835866201; dial string
1 18008358662 *Either
1 of these 2 dial # will work 4.4 Additional ISDN Tips: *Please try NOT to use LDN but apply the following
settings: D3: D3:
5.
How to use VoIP in the lab 5.1 To simulate a phone call
being made from a PBX for testing purposes, try the following command: 5.2 Testing your VoIP configurations using the modem "AT" commands. Please note that the VoIP voice / phone (vic-2fxs) modules are wired as illustrated below: voice-port
1/0/0 of D2 ------- Modem ------- Phone1 And
the modems' DB25 serial ports are connected to TTY port of "D17" so
that our lab customers will be able to test VoIP
configurations by reverse-telnet into 1 of the lab modems then manually issue
some modem " AT " commands from the modem to dial out to another
phones (VoIP peers) in the lab r6-2610 via VoIP protocol. If the VoIP
configuration is correct, you should "see" some phone ringing /
calling activities by using VoIP-related
"debug"
or "show" command.
5.3
To make the
modem reverse-telnet work, we have applied the following
settings on the
TTY line 13, 14 and 15 on Terminal Router "D17": ! 5.4 You can reverse-telnet into the modems attached on those TTY lines by using the IP host names (phone1, phone2 and phone3) that have already been configured on the Terminal Router "D17". 5.5 When you see "open", you may try to type "at" then hit "enter" key. It will return "ok" to your console. If you can't see anything on your screen, type " at&f " to reset the modem back to the factory default settings, then try again. Finally you can issue "atdt 21234" to dial the other phone. 21234 is only an example of the dial string. You will use whatever dial string you would configure with "atdt" command to reach the other VoIP Voice Peer. To hand up, simply type "+++" or "ath". You can get some basic commands on http://www.modem.com/. 5.6 It is easy to exit out of the modem reverse-telnet mode by pressing "ctrl-shift-6" then "x" key. After you get back to "D17", you may issue a command "where" then "disconnect" to tear down the reverse-telnet session if you need to. You don't have to "disconnect" though. 6.1 Performing Password Recovery on all lab Cisco routers/Switches (except
Catalyst
3550
Switches and
PIX
firewall) is made possible just by sending "Break" key over your remote telnet session. You have to Telnet from the "HyperTerminal" program of Microsoft
Windows then
send "Ctrl-Break" (possibly a little bit
different key combinations on laptops) during routers' reboot process. We have
also tested okay on sending "Break" key over the "Tera Term
Pro" terminal program (there is an option on the top menu to choose
"Control" then "Send break"). 6.2
Do NOT start sending "Break" key right
away when the router is just rebooted. You might want to give it a few more
seconds before carrying out "Ctrl-Break".
Please remotely
reboot lab devices if problems occur during password recovery. This will enable
you to work on most of the troubleshooting scenarios without the need of being
physically next to the lab equipment. Again, this will NOT work on
Catalyst
3550
Switches and
PIX
firewall. And DO NOT try this on your Terminal Router "D17" or you will lose
the connection to the entire lab. 6.3
Knowing how to send "Break" key is only a part of password recovery procedure. You must precisely perform
the entire password recovery procedure defined on Cisco.com website. Here is
the URL for reference:
http://www.cisco.com/warp/public/474/
(this URL can be changed). 6.4
You might need
to
upgrade your HyperTerminal software
to allow "Telnet" to run. Or you may
download Tera Term Pro for free.
If you are experiencing connection problems, you may use the following instructions to verify, identify or troubleshoot the suspicious issues. 7.1 If you are unable to establish connection to our lab during your lab session, please wait for 5 minutes (or more) then try again since we are using Dynamic DNS services. 7.2 Based on our experiences in the past, in most cases, there is nothing wrong with our lab settings or connection to the outside Internet. Many users first suspected problems on our lab side but it turned out to be some ISP related issues (either the user's direct ISP or other ISP on the path). Network Force lab setting has always been tested by many lab customers accessing from all over the world. 7.3 Based on our experiences in the past, some ISPs (or some corporate networks) were found to use MEGA-PROXY (or Firewall) to screen/filter all their incoming or outgoing Internet traffic. Depending on the Proxy or Firewall screening rules in place, your connection can be frequently interrupted, slowed down, timed out or even dropped. So you are advised to test from different ISPs to determine where the real problems are. 7.4 To optimize your connection speed on a dial up phone line via a modem, please close all browser sessions, email programs or any other bandwidth-consuming applications. 7.5 If you are connecting to Internet via cable
modem, xDSL or something even faster, please use this
URL to determine current bandwidth available to your PC:
http://www.2wire.com/?p=154
(or find "Speed Meter" on their web page) 7.6 If you suspect on some routing issues occurring,
you should be able to PING or TRACEROUTE ("tracert" from MS Windows PC) to our lab host name "nflab.dyndns.org", assuming PING or TRACEROUTE ICMPs is not being blocked by any firewalls
or router ACLs at your end. Network Force does not block PING or TRACEROUTE to the
Terminal Router in the lab. If you are unable
to perform PING or TRACEROUTE from you PC, please try to telnet into "route-server.cerf.net" (a publicly accessible BGP router sponsored by
AT&T) then run PING or TRACEROUTE from there. Please note that the AT&T BGP
router's Telnet VTY lines are limited.
*Please note that
NOT every ISP or website will allow 8. Step-by-step demo of lab power-on procedure How to Power-On the lab devices ? Here is a step-by-step example Note: the following RED words are the actual commands that you will type in when prompted You can Telnet into the terminal router in the lab by entering "telnet nflab.dyndns.org" from your PC (More details on how to Telnet into the lab). After Telnet into the terminal router "D17" in the lab, you just type "power" to start... -------------------------------------------------------------------------------
D17#power
Trying power (96.91.4.67, 2017)... Open
(**press "ENTER" key, if you
don't see any prompt after entering "power" at D17)
(**You will be locked out of "power" after 3 failed logon attempts. Try back after 3 minutes)
Login :
guest1
*** Main Menu
1. Outlets 2. Network Configuration 3. SNMP Configuration 4. Ping Application 5. Password Configuration 6. Console Configuration 7. Advanced 8. Factory Settings 9. Logout
Selection :
1
*** Outlets
1. Master : 2. Outlet 1 : OFF D1->D6 3. Outlet 2 : OFF D7->D12 4. Outlet 3 : OFF 5. Outlet 4 : OFF 6. Outlet 5 : OFF 7. Outlet 6 : OFF 8. Outlet 7 : OFF 9. Outlet 8 : OFF
Selection :
1
*** Master :
1. PDU Name : On/Off All Devices 2. Auto Power On : Immediate 3. Reboot Duration : 10 Seconds 4. Master Control : No action 5. Accept Changes :
Selection :
4
*** Master :
1. No action 2. Sequence All On 3. Immediate All On 4. Immediate All Off 5. Immediate Reboot 6. Sequenced Reboot
Selection :
2
*** Master :
1. PDU Name : On/Off All Devices 2. Auto Power On : Immediate 3. Reboot Duration : 10 Seconds 4. Master Control : Sequence All On 5. Accept Changes : Pending
Selection :
5
*** Master :
1. PDU Name : On/Off All Devices 2. Auto Power On : Immediate 3. Reboot Duration : 10 Seconds 4. Master Control : No action 5. Accept Changes : Success
Selection : (press
Esc
key to exit if "Success" is
shown under "5. Accept Changes")
*** Outlets
1. Master : 2. Outlet 1 : ON D1->D6 3. Outlet 2 : ON D7->D12 4. Outlet 3 : ON 5. Outlet 4 : ON 6. Outlet 5 : ON 7. Outlet 6 : ON 8. Outlet 7 : ON 9. Outlet 8 : ON
Selection : (press
Esc
key to exit)
*** Main Menu
1. Outlets 2. Network Configuration 3. SNMP Configuration 4. Ping Application 5. Password Configuration 6. Console Configuration 7. Advanced 8. Factory Settings 9. Logout
Selection :
9
Login : (to exit back to D17, press Ctrl-Shift-6 (3 keys together) then x key)
D17#
where
Conn Host Address Byte Idle Conn
Name
* 1 power 96.91.4.67 0 2 power
D17#disconnect
1
(**after powered on,
you would want to disconnect TTY line to "Power" before working on each lab
router's console port. Otherwise, you may not be able to line up TTY line 1 to
D1 router console in the lab)
Closing connection to poweD2 [confirm] D17# D17#where % No connections open D17#
**Now, you can reverse-telnet
into each lab router's console port, starting from D1 (lined up with D17's TTY
1), D2 (TTY 2), D3 (TTY 3)...
9. Step-by-step demo of
reverse-telnet via terminal router
Here is a sample output of Reverse-Telnet session showing the exact process
step-by-step: =========================================================== D17>show
clock 15:14:07.941
DST D17>where %
No connections open D17>sh hosts !!!! these hosts and their "reverse telnets" are Default
domain is not set Name/address
lookup uses static mappings Host
Port Flags
Age Type
Address(es) D9
2009 (perm, OK) 23 IP 222.222.222.222 |