It’s makes me a sad engineer when I walk into a mess like this, it only makes the troubleshooting a nightmare.
I’ve used GNS# for a number of years, one thing that I notice is the error in the terminal settings for SecureCRT. Granted, GNS3 does come with putty installed however I’v been fan of SecureCRT since 2008. This video will help you make the necessary changes needed to allow ScureCRT 64 and 32 bit to work with GNS3. If you find the below video a bit blurry, go to YouTube and view it at 720 HD in full screen. Looks great. http://youtu.be/-dmrTneMGhA?hd=1
Here’s the correct code for SecureCRT 64bit.
C:\progra~1\vandyk~1\SecureCRT\SecureCRT.EXE /script C:\progra~2\gns3\securecrt.vbs /arg %d /T /telnet %h %p
Use this for the 32bit version
C:\progra~2\vandyk~1\SecureCRT\SecureCRT.EXE /script C:\progra~2\gns3\securecrt.vbs /arg %d /T /telnet %h %
To see the system information: systeminfo
Display Connection Configuration: ipconfig /all
Display DNS Cache Info Configuration: ipconfig /displaydns
Clear DNS Cache: ipconfig /flushdns
Release All IP Address Connections: ipconfig /release
Renew All IP Address Connections: ipconfig /renew
Re-Register the DNS connections: ipconfig /registerdns
Change/Modify DHCP Class ID: ipconfig /setclassid
Network Connections: control netconnections
Test Connectivity: ping supto.net
Displays the TCP/IP protocol sessions: netstat
Display Local Route: route
Display Resolved MAC Addresses: arp
Display Name of Computer Currently on: hostname
Display DHCP Class Information: ipconfig /showclassid
Name Server Lookup: nslookup google.com
Access and maintain a Microsoft File/Printer Sharing environment: net
For Traces the route: tracert supto.net (press ctrl+break to came out of this command)
Combines functions of Ping and Tracert : pathping /?
Used to retrieve the information about a user on a network: finger
In this scenario we are asked to validate a flapping interface.
1] Find the serial interface and verify that it is up/up
attga43c3#sho ip int br | include 10.112.210.45
Serial9/1/1/20:0 10.112.210.45 YES manual up
2] Display the interface and note the errors
attga43c3#sho int s9/1/1/20:0
Serial9/1/1/20:0 is up, line protocol is up
Hardware is cyBus 2CT3+
Description: MNX | MYHOME SERVICES | MYHOUSE | GA | DHEC.123456..ATI | 23853 | 1305937 | 1364629 | USA | MIS |
Internet address is 10.112.210.45/30
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:05, output 00:00:05, output hang never
Last clearing of “show interface” counters never
Input queue: 0/1000/0/0 (size/max/drops/flushes); Total output drops: 5
Queueing strategy: VIP-based fair queuing
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
6534487 packets input, 3035189030 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 1 giants, 0 throttles
116987 input errors, 7228 CRC, 51274 frame, 0 overrun, 0 ignored, 58484 abort
5877595 packets output, 2144676741 bytes, 0 underruns
0 output errors, 0 collisions, 170 interface resets
0 output buffer failures, 0 output buffers swapped out
166 carrier transitions no alarm present
Timeslot(s) Used: 1-24, Transmitter delay is 0 flags, transmit queue length 5
3] Find the VRF and ping the VRF interface.
attga43c3#sho ip vrf interface | include 10.112.210.45
Serial9/1/1/20:0 220.127.116.11 1612 <— VRF
4] Run an extended Ping to the VRF
Router3#ping vrf 1612
Target IP address: 10.112.210.46
Repeat count : 5000
Datagram size : 1500
Timeout in seconds : 1
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5000, 1500-byte ICMP Echos to 10.112.210.46, timeout is 1 seconds:
In the above ping I wanted to really hammer the heck out of circuit. In this example we see that the circuit is clocking massive input errors and no output. Instead of me writing what I did to correct this, I’m going to leave this post open for the reader to comment what they think I did. Note the bold errors and circuit type.
Just a short note to you all know what has been happening for the last three months and why there hasn’t been any new content posted to the site.
It’s been a busy three months , took the ROUTE exam , work projects then changing job roles.
I recently picked up the CCIE Routing and Switching Certification Guide, (4th edition). SO I will be pouring of that soon.
I have about a donzen GNS labs that I want to add to the site along with my commentary, problems I had with GNS3 and issues I ran into to make them work.
I be writing up my own guide on how to setup GNS3 for the Mac Pro using Lion OS and lastly I plan to the move the site theme to a Thesis theme, been playing around with this of and on for the last month or so. So far I think it will allow allot more flexibility to how I can display content on the site.
This is what I have plan for August, by then the dust in the new office will be settled and I can start adding more content to the site.
PuTTY does not write its settings to a file, for people who wish to install this on an USB stick poses a challenge. When you run putty on a system that never ran it before, it will not have any of your saved settings. Only solution (that i know of) is to merged your registry settings with the system you running it on. (a bit intrusive.) So in just seven easy steps you can now have your PuTTY settings on your USB drive.
From your Windows start panel, click on “run”
Type “regedit” in the your run box.
Press “CTRL-F” (this will bring up the search box)
In the search box type “SimonTatham” (no space)
Click off Values and Data
You should now have the SimonTatham highlighted in your registry
Right click and select “Export”
I saved mine to the desktop and named it something that I would not forget what it it.
Once you have the file you can move it to your USB key and import or merge
it to which ever system you are working on.
That’s it, you’re done!
I found this sheet on the internet a few years back. If anyone knows the URL send it to me and I’ll link it. The sheet as help me perform some basic troubleshooting on the Juniper J2300 in our lab. The 2300 came with an elaborate GUI interface however I more comfortable diving knee deep into the CLI.
|Cisco Command||Juniper Command||What does it do?|
|show run||sh configuration||Show running configuration|
|show version||show version||Show version|
|show IP interface brief||show interface terse||displays the status of interfaces configured for IP|
|show interface #||show interfaces # detail||displays the interface configuration, status and statistics.|
|show controller #||show interfaces # extensive||displays information about a physical port device|
|show interface | incl (proto|Desc)||show interfaces description||displays the interface configuration, status and statistics|
|show IP route||show route||displays summary information about entries in the routing table|
|show IP BGP summary||show BGP summary||displays the status of all Border Gateway Protocol (BGP) connections|
|show IP BGP net mask||show route protocol BGP prefix||will show you how that route is being advertised, look for the first line|
|show IP BGP net mask longer-prefixes||show route range prefix||will show you how that route is being advertised, look for the first line|
|show IP BGP regexp AS-regexp||show route aspath-regexp “AS-regexp”||displays routes matching the autonomous system (AS) path regular expression|
|show IP BGP neighbors neigh received-routes||show route receive-protocol BGP neigh
show route source-gateway neigh protocol BGP
|Shows whether a neighbor supports the route refresh capability|
|show IP BGP neighbor neigh advertised-routes||show route advertising-protocol BGP neigh||Shows whether a neighbor supports the route refresh capability|
|show clns neighbors||show ISIS adjacency||displays both ES and IS neighbors|
|show clns interface||show ISIS interface||shows specific information about each interface|
|show IP route ISIS||show ISIS routes||displays the current state of the the routing table|
|show ISIS topology||show ISIS spf||displays a list of all connected routers in all areas|
|show IP OSPF interface||show OSPF neighbor||shows neighbor ID, Priority, IP, & State if the neighbor router, dead time.|
|show IP OSPF interface||show OSPF interface||shows neighbor id, prior, state, dead time, address and interface|
|show IP route OSPF||show OSPF route||display the current state of the routing table|
|show IP OSPF database||show OSPF database||display list of information related to the OSPF database for a specific communication server|
|show version||show version, show system uptime||display the system hardware config., software version, and name and source of configuration files and boot images|
|show diags||show chasis hardware||displays power-on diagnostics status|
|show processes cpu||show system process||displays utilization statistics|
|show tech-support||request support info||displays the current software image, configuration, controllers, counters, stacks, interfaces, memory and buffers|
|show logging||show log messages||display the state of logging to the syslog|
|show route-map name||show policy name||displayall route-maps configured or only the one specified|
|show IP prefix-list name||show policy name||display information about a prefix list or prefix list entries|
|show IP community-list list||configure,
show policy-options community name
|display routes that are permitted by BGP community list|
|show environment all||show chassis environment||displays temperature and voltage information on the console|
|ping dest||ping dest rapid (for cisco like output)
ping dest (for unix like output)
|to check to see if a destination is alive|
|ping (setting source int)||ping dest bypass-routing||to check to see if a destination is alive|
|terminal monitor||monitor start messages||Change console terminal settings|
|terminal no monitor||monitor stop||Change console terminal settings|
|terminal length 0||set cli screen-length 0||sets the length for displaying command output|
- Has full time IPSEC
- Eliminates the need for broadcast.
- Uses UNICAST (one to one)
- Uses MULTICAST FF01: (one to many)
- Uses ANYCAST (one to closest)
- Eliminates the need for HSRP/VRRP
- NAT is not longer used
- No more private addresses (the old v6 unique site local address is eliminated)
- Uses Global scope address 2000::/3 (internet2 address 2001::/16)
- Uses Link Local FE80: layer 2 auto generated
- Think 169.254.0.0
- (MAC – FFFE – MAC) = last 64 bits (48 bit MAC Address + 16 bit FFEE IPV6 )
- Smaller Harder size ( more secure)
- No need for a DHCP (uses auto generated prefix from the router)
- Easier localhost address ::1 oppose to V4’s 127.0.0.1
- IPv6 has eight blocks of 16 bits for a total of 128 (called hextets)
IPV4 RFC 791, September 1981 http://tools.ietf.org/pdf/rfc791.pdf
IPV6 Original RFC 1884, December 1995 (Now obsolete) http://tools.ietf.org/pdf/rfc1884.pdf
Revised July 1998 RFC 2373 (Now obsolete) http://tools.ietf.org/pdf/rfc2373.pdf
Revised April 2003 RFC 3513 (Now obsolete) http://tools.ietf.org/pdf/rfc3513.pdf
Current RFC 4291, February 2006 RFC 4291 http://tools.ietf.org/pdf/rfc4291.pdf
V 4’s 4.2 billion address pales in comparison to what V6 offers.
V6 has 340,282,366,920,938,463,463,374,607,431,768,211,456 available numbers
Three hundred and forty undecillion, two hundred and eighty-two decillion, three hundred and sixty-six nonillion, nine hundred and twenty octillion, nine hundred and thirty-eight septillion, four hundred and sixty-three sextillion, four hundred and sixty-three quintillion, three hundred and seventy-four quadrillion, six hundred and seven trillion, four hundred and thirty-one billion, seven hundred and sixty-eight million, two hundred and eleven thousand, four hundred and fifty-six.
http://www.thefreedictionary.com/undecillion < hear the pronunciation here.
The above is meant as a reference, information is not static.
Below is a list of troubleshooting commands I comprised over the years while working for a “major telecommunications internet provider”. The commands helped me to easily isolate most MPLS issues that I came across.
show ip vrf interfaces | i <IP>
show run | run vrf <NUMBER>
show ip route vrf <NUMBER>
show ip bgp vpnv4 vrf <NUMBER>
show ip bgp vpnv4 vrf <NUMBER> summary
show ip bgp vpnv4 vrf <NUMBER> neigh <IP> policy
show ip bgp vpnv4 vrf <NUMBER> neighbor < IP> route
show ip bgp vpnv4 vrf <NUMBER> neighbor <IP> advertised-routes
show ip bgp vpnv4 vrf <NUMBER> neighbor <IP> advertised-routes | i <NETWORK IP>
show ip route vrf <NUMBER> < IP>
show ip b v v <NUMBER> <IP>
tr vrf <NUMBER> <IP>
ping vrf <NUMBER> <IP>
Have you ever ran into this? Or even seen it? Windows XP Task Manager has a mode called “Tiny footprint” MS Support Page
The mode is meant to allow people who want to, display their CPU meter. this comes in handy when running six or more routers in GNS3, you want to make sure that your CPU is not being pegged.
To the left we have our normal task manager window. If you were to double click any where on the boarder the task manager will change to the image on the right What happens is by double clicking the boarder causes the menu tabs to disappear. When I first saw this I thought something was wrong with my windows. I even rebooted my computer but before panicked further I went researched it on
As you can see, it makes it very easy to keep eye on your processors.
Microsoft’s Website. You can still navigate the menus by holding <TAB> + <SHIFT> and selecting “< or >“ your arrows keys. If you never seen this before it can be nerve wracking.