Cisco CCNA 640-801 Certification

Wednesday, July 05, 2006

Cisco Internet Protocol Journal
The Internet Protocol Journal, which is a free publication by Cisco Systems, publishes the publication quarterly and there's some interesting things you can read about. I've dug and found the issue from September 2005. Although it's not brand new now, it's new if you haven't read it. The link below is a link to download the Internet Protocol Journal September 2005 issue. It's about 36 pages long. The big feature is on IPv4 and running out of addresses. Of course, IP (internet protocol) version 6 (IPv6) more than solves the problem of not enough addresses. It provides enough addresses for every person to have as many IP addresses as hairs they have on their head. That's what I heard from an expert at the CCNA Prepcenter in one of the videos there.

More on Cisco's publication 'Internet Protocol Journal' can be found at www.cisco.com/ipj

Wednesday, June 14, 2006

CREATE VLANS, ASSOCIATE WITH PORTS

To create VLANs on a Cisco switch, it's rather simple. Keep in mind by default, VLAN 1 is the default VLAN that traffic is carried for vlan updates, etc. By default the mode is VTP server where vlans can be added, deleted. Other modes could be client where you can't add or remove vlans, or transparent. All ports are part of VLAN 1 by default. Also optional is specifying vtp domain name and a password. Then, the fun comes by assigning ports to the appropriate vlans you want it to be a part of.

Switch > enable
Switch # vlan database
Switch (vlan)# vtp server
Switch (vlan)# vlan 2 name cisco
Switch (vlan)# vlan 3 name ibm
Switch (vlan)# vlan 4 name hp
Switch (vlan)# vlan 5 name dell
Switch (vlan)# vtp domain ccna
Switch (vlan)# vtp password ccna
Switch (vlan)# exit
Switch # configure terminal
Switch (config)# interface fa0/2
Switch (config-if)# switchport mode access
Switch (config-if)# switchport access vlan 2
Switch (config-if)# interface fa0/3
Switch (config-if)# switchport mode access
Switch (config-if)# switchport access vlan 3
Switch (config-if)# interface fa0/4
Switch (config-if)# switchport mode access
Switch (config-if)# switchport access vlan 4
Switch (config-if)# interface fa0/5
Switch (config-if)# switchport mode access
Switch (config-if)# switchport access vlan 5

Saturday, May 27, 2006

Make your own network cables!

Instead of paying a whopping $7 or more for your RJ-45 network cables, I would recommend making your own. It's more time consuming of course but if you buy a bulk of cable, you can save some money. I've created several of my own when taking the 1st semester of CCNA (1st class of CCNA, also sometimes called semester 1, 2, 3, 4, etc) I didn't get a chance to really make all of the types of network RJ-45 (RJ stands for registered jack, RJ-11 is your standard telephone cable) cables and wanted to learn and try it some more. I went out and bought a crimp tool for $30 at CompUSA, a 250ft (or 76.2 meters) length of stranded CAT5e bulk cable at Staples for $70, and later a Fluke 620 cable tester off of EBay for around $125. Now, if I had done it again I would have searched online stores for cheaper prices as far as a crimp tool, I know they are as low as $10 on buy it now EBay auctions. Also, bulk cable can be bought for probably $20 less for the length of cable I bought at Staples.

Straight-through

Straight through cables are the most used networking cables. They are used between a router to a switch, a switch to a PC, a router to a PC. (In Cisco world though, a router to a PC requires a crossover cable) There are a total of 8 pins for straight-through and only 4 are actually used. 2 for transmit, and 2 for receive.

Click here to view a chart with the pinouts for a straight-through cable.

Crossover

Crossover cables are used to connect similiar devices together such as a router to a router, switch to switch, PC to PC, as well as a switch to a hub. In the Cisco networking world, a router to a PC requires a crossover cable. Of course, they are looking at Cisco routers primarily, and some of the home networking routers act as a switch and router both.

Click here to view a chart on the pinouts on making a crossover cable.

Rollover

The last but not least is the rollover cable. If you learn any Cisco technology, your guaranteed to learn about this type of networking cable. That is because a rollover cable is used to connect to a console port of a Cisco router or switch to a DB9-RJ45/DB25-RJ45 adapter of the PC. A 9 or 25 pin serial port which is a COM port will be used. What is a console port? A console port allows you to manage a Cisco router or switch from a PC. This enables you to access the router or switch from a PC. Alternatives to access a Cisco router or switch is remotely via Telnet, or dialing in via Aux port on the device. At first though, a brand new Cisco router or switch isn't configured with any IP addresses or anything so you have to connect via the console port.

Click here to view a chart on the pinouts of a rollover cable.

Thursday, May 18, 2006

Any questions on CCNA? Feel free to email them to ciscoccna640801 at gmail.com. Please keep in mind I will not give you answers to exact questions I saw on the exam due to the Cisco Confidential agreement I signed before taking the exam. It's against the rules. I may give you an idea on possible topics you COULD see on the exam. There's topics and such you should know and be familiar with on the exam which is shareable. The general topics are on Cisco's website anyhow. Also, no braindumps please, braindumps are links to sites that have cheatsheets and such. Cisco doesn't tolerate it and neither do I.

I continue to hang out at Certcities forums. It's a great place to discuss certification related info and there's some helpful folks there. You can discuss Cisco, CompTIA, Novell, Microsoft, Oracle, and more. There's also a miscellaneous section where you can post things, and a general career and salary forum. It's a good place to visit.

What's it stand for?
Below I've gathered some of the well known computer/networking related certs out there today and what they stand for. These are not all of the certs out there, several vendors such as HP, Adobe, and others have their own certs.

CCNA Cisco Certified Network Associate
CCNP Cisco Certified Network Professional
CCDA Cisco Certified Design Associate
CCDP Cisco Certified Design Professional
CCSP Cisco Certified Security Professional
CQS Cisco Qualified Specialist
CCIP Cisco Certified Internetwork Professional
CCVP Cisco Certified Voice Professional
CCIE Cisco Certified Internetwork Expert

CNA Certified Novell Administrator
CNE Certified Novell Engineer
MCNE Master Certified Novell Engineer
CLE Certified Novell Linux Engineer
CLP Certified Novell Linux Professional

MCP Microsoft Certified Professional
MCP +I Microsoft Certified Professional + Internet
MCSA Microsoft Certified Systems Administrator
MCSE Microsoft Certified Systems Engineer
MCSE +I Microsoft Certified Systems Engineer + Internet

A +
Network +
Server +
Security +
i-Net +
Linux +

RHCE RedHat Certified Engineer
RHCT RedHat Certified Technician
RHCA RedHat Certified Architect
Linux + (by CompTIA)
LCA Linux Certified Administrator
LCE Linux Certified Engineer
MLCE Master Linux Certified Engineer

OCA AD Oracle Certified Associate -- Application Developer
OCA DBA Oracle Certified Associate -- Database Administrator
OCA Web Admin Oracle Certified Associate -- Web Application Server Administrator
OCP DBO Oracle Certified Professional -- Database Operator
OCP AD Oracle Certified Professional -- Application Developer
OCP DBA Oracle Certified Professional -- Database Administrator
OCP Java Dev Oracle Certified Professional -- Java Developer

Sunday, May 07, 2006

862!

I passed the CCNA exam this past Thursday!

Tuesday, May 02, 2006

ISDN REFERENCE POINTS

TE1 = Terminal endpoint 1. Devices have a native ISDN interface.

TE2 = Terminal endpoint 2. A device that requires a TA to connect to ISDN service provider.

TA = Terminal adapter. Converts EIA/TIA-232, V.35, & other signals into BRI signals.

NT1 = Network termination 1. Converts BRI signals into a form used by the ISDN digital line. An NT1 terminates the local loop.

NT2 = Network termination 2. Aggregates & switches all ISDN lines at a customer service site using a customer switching device.

R = Connection point between a non-ISDN compatible device & a terminal adapter (TA).

S = Connection point into customer switching device (NT2). Enables calls between customer equipment.

T = outbound connection from the NT2 to the ISDN network. This reference point is electrically identical to the S interface.

U = Connection point between NT1 & the ISDN network.

CISCO HIERARCHIAL MODEL

Access Layer = where users connect to network

Access Layer functions:

Connectivity into distribution layer
Shared bandwidth
MAC address filtering
Segmentation
Point where users connect to network
Security by allowing ACLs to optimize user needs

Examples of Access Layer switches:

Cisco Catalyst 1900 series
Cisco Catalyst 2950 series

Distribution Layer = performs routing, filtering, & WAN access

Distribution Layer functions:

Routing traffic
Aggregation point for lower layer devices
Definition of broadcast domains/multicast domain
Medias type translation (Ethernet, Token Ring)
Security & filtering
VLAN routing

Examples of Distribution Layer switches:

Cisco Catalyst 5000 series
Cisco Catalyst 6000 series

Core Layer = switches traffic as fast as possible, Internet access uses this layer, no filtering should be done on this layer.

Core Layer functions:

Switches traffic as fast as possible

Examples of Core Layer switches:

Cisco Catalyst 6500 series
Cisco Catalyst 8500 series

Thursday, April 27, 2006

Configure Dynamic NAT

Define Static Route (example)
ISP (config)# ip route 64.64.64.64 255.255.255.128 s0/0

Define pool of usable public IP addresses for router
Router (config)# ip nat pool ccna 64.64.64.70 64.64.64.126 netmask 255.255.255.128

Create ACL to have private IP addresses translated to public
Router (config)# access-list 1 permit 10.0.0.0 0.0.0.255

Link ACL to pool
Router (config)# ip nat inside source list 1 pool ccna

Define in & out interfaces
Router (config)# int fa0/0
Router (config-if)# ip nat inside
Router (config-if)# exit
Router (config)# int s0/0
Router (config-if)# ip nat inside

Configure PAT (overloading)

Define static route
ISP (config)# ip route 64.64.64.64 255.255.255.128 s0/0

Define pool (optional)
Router (config)# ip nat pool ccna 64.64.64.70 64.64.64.126 netmask 255.255.255.128

Define ACL for private IP addresses to be translated
Router (config)# access-list 1 permit 10.0.0.0 0.0.0.255

Link ACL to outside public interface
Router(config)# ip nat inside source list 1 interface s0/0 overload

(optional) Link ACL to pool
Router (config)# ip nat inside source list 1 pool ccna overload

Define interfaces
Router (config)# int fa0/0
Router (config-if)# ip nat inside
Router (config-if)# exit
Router (config)# int s0/0
Router (config-if)# ip nat outside

Configure Static NAT

Define static route
ISP (config)# ip route 64.64.64.64 255.255.255.128 s0/0

Create static mapping
Router (config)# ip nat inside source static 172.16.10.5 64.64.64.65

Define interfaces
Router (config)# int fa0/0
Router (config-if)# ip nat inside
Router (config-if)# exit
Router (config)# int s0/0
Router (config-if)# ip nat outside

NAT Terminology

*Inside local address = IP address assigned to a host on inside, private network. (usually a private IP address)

*Inside global address = IP address that is routable & represents one or more inside local IP addresses to the outside world.

*Outside local address = IP address of outside host as it appears to inside, private network. (usually a private IP address)

*Outside global address = IP address assigned to a host on outside network by host's owner. Usually a routable IP address.

NAT Benefits

Conserves IP addresses
Hides internal network (security)
Eliminates readdressing overhead

NAT Disadvantages

Increases delay
Loss of end-to-end IP traceability
Some applications won't function

Wednesday, April 26, 2006

CISCO IOS EDITING COMMANDS

CTRL + A = move cursor to beginning of line
CTRL + E = move cursor to end of line
CTRL + K = delete everything to right of cursor
CTRL + F (or right arrow) = move cursor forward one character
CTRL + B (or left arrow) = move cursor back one character
CTRL + Z = moves you to priviliged EXEC mode
ESC + B = move cursor back one word
ESC + F = move cursor forward one word
CTRL + D = deletes single character
CTRL + Shift + 6 +X = suspend multiple telnet sessions

PING COMMAND SYMBOLS & MEANINGS
. timeout
! success
? unknown packet type
C congestion experience packet was received
U destination unreachable error received
I user interrupted test
& ICMP time exceeded message received. Routing loop may have occured.

TRACEROUTE COMMAND SYMBOLS & MEANINGS
* probe timed out
A administratively prohibited. Firewall or router might be blocking probe & other traffic. Check access-control lists.
Q source quench. Device along path may be receiving too much traffic.
H ICMP unreachable message received. Routing loop may have occured.

Traceoute uses TTL (time to live) values to generate messages from each router along the path.

Monday, April 17, 2006

Common Port Numbers of applications & protocols

I've written below some common and reserved port numbers to different applications and protocols found on the Internet today.

20 - FTP data
21 - FTP (uses TCP)
23 - Telnet (uses TCP)
25 - SMTP (uses TCP)
53 - DNS (uses TCP and or UDP)
67 - BOOTP (server), DHCP (uses UDP)
68 - BOOTP (client), DHCP (uses UDP)
69 - TFTP (uses UDP)
80 - HTTP (uses TCP)
110 - POP3
143 - IMAP
161 - SNMP (uses UDP)
179 - BGP
520 - RIP (uses UDP)

Thursday, April 13, 2006

Frame Relay

Configuring Frame-Relay with subinterfaces

Router (config)# int s0/0
Router (config-if)# encapsulation frame-relay
Router (config-if)# no shutdown
Router (config-if)# int s0/0.25 point-to-point
Router (config-subif)# ip address 192.168.1.1 255.255.255.252
Router (config-subif)# frame-relay interface-dlci 25
Router (config-subif)# no shutdown

There are two different subinterfaces that can be configured: Point-to-point and Multipoint. Point-to-point has a single PVC that connects from one router to the other and each subinterface is in its own subnet. Multipoint basically has the router as the center of several different routers. All other routers connect to each other through this router and all routers are in the same subnet. It's recommended to turn off split horizon on Multipoint for other routers/interfaces to see each other and function properly. Use 'no ip split-horizon' command.

Configure Frame Relay LMI Type

Router (config)# int s0/0
Router (config-if)# frame-relay lmi-type ansi
Router (config-if)# no shutdown

As of Cisco IOS 11.2, LMI is autosensed. The default is 'cisco'. Other types include 'q933a' and 'ansi'. LMIs are used to manage and maintain connections between the Frame Relay switch and the CPE device (the router). The CPE router (customer's router) sends keepalive messages to the Frame Relay switch every 10 seconds by default.

Configure a Frame Relay Map

Router (config)# int s0/0
Router (config-if)# no frame-relay inverse-arp
Router (config-if)# frame-relay map ip 192.168.1.1 25 broadcast
Router (config-if)# no shutdown

The above allows you to statically configure DLCI & mapping, Inverse ARP needs to be turned off when doing it this way. Inverse ARP is on by default. The 'broadcast' at the end of the command is optional, with it included in the comand it will allow broadcasts to be forwarded and is necessary if you are using a dynamic routing protocol like RIP, OSPF, EIGRP, etc.

Thursday, March 30, 2006

Subnetting. Don't you love subnetting? You can't run from it. It's a vital topic on the CCNA exam and in a networking career. It takes a bit of practice to get good at it. It's good to write out the different subnet masks and usable hosts and subnets. Let's think of subnetting with no subnet zero in this instance for now. If you know binary, subnetting will be easier. Truthfully, you should already know binary. There are 8 bits in a byte and with IP addresses being 32-bit, 4 octets. Between the . is considered one octet and so forth. There are some links on the right side of my page that explain how to subnet very well. Check them out.

CLASS A	SUBNET MASK	USEABLE SUBNETS	USEABLE HOSTS
/8	255.0.0.0	N/A	N/A
/9	255.128.0.0	N/A	N/A
/10	255.192.0.0	2	4,194,302
/11	255.224.0.0	6	2,097,150
/12	255.240.0.0	14	1,048,574
/13	255.248.0.0	30	524,286
/14	255.252.0.0	62	262,142
/15	255.254.0.0	126	131,070
/16	255.255.0.0	254	65,534
/17	255.255.128.0	510	32,766
/18	255.255.192.0	1,022	16,382
/19	255.255.224.0	2,046	8,190
/20	255.255.240.0	4,094	4,094
/21	255.255.248.0	8,190	2,046
/22	255.255.252.0	16,382	1,022
/23	255.255.254.0	32,766	510
/24	255.255.255.0	65,534	254
/25	255.255.255.128	131,070	126
/26	255.255.255.192	262,142	62
/27	255.255.255.224	524,286	30
/28	255.255.255.240	1,048,574	14
/29	255.255.255.248	2,097,150	6
/30	255.255.255.252	4,194,302	2

CLASS B	SUBNET MASK	USEABLE SUBNETS	USEABLE HOSTS
/16	255.255.0.0	N/A	N/A
/17	255.255.128.0	N/A	N/A
/18	255.255.192.0	2	16,382
/19	255.255.224.0	6	8,190
/20	255.255.240.0	14	4,094
/21	255.255.248.0	30	2,046
/22	255.255.252.0	62	1,022
/23	255.255.254.0	126	510
/24	255.255.255.0	254	254
/25	255.255.255.128	510	126
/26	255.255.255.192	1,022	62
/27	255.255.255.224	2,046	30
/28	255.255.255.240	4,094	14
/29	255.255.255.248	8,190	6
/30	255.255.255.252	16,382	2

CLASS C	SUBNET MASK	USEABLE SUBNETS	USEABLE HOSTS
/24	255.255.255.0	N/A	N/A
/25	255.255.255.128	N/A	N/A
/26	255.255.255.192	2	62
/27	255.255.255.224	6	30
/28	255.255.255.240	14	14
/29	255.255.255.248	30	6
/30	255.255.255.252	62	2

Click here for a friendlier chart in a spreadsheet form as a pdf.

11000000.10000111.00100000.11111111

What's the above binary in decimal?

Answer: 192.135.32.255

What type of class is this IP address? Class A, B, or C?

Answer: Class C

Is it one of the Private IP address range defined by the RFC 1918?

Answer: No

With a subnet mask of 255.255.255.192, how many possible subnets are possible in a Class C?

Answer: 4 (2 usable)

With a subnet mask of 255.255.255.192, how many possible subnets are possible in a Class B?

Answer: 1024 (1022 usable)

What are the private IP address ranges defined in RFC 1918?

Answer:
Class A 10.0.0.0 - 10.255.255.255 /8
Class B 172.16.0.0 - 172.31.255.255 /16
Class C 192.168.0.0 - 192.168.255.255 /24

Those above are some simple questions. Enjoy.

Saturday, March 18, 2006

Configure PPP

Router (config)# int s0/0
Router (config-if)# encapsulation ppp

Configure PPP with PAP authentication

Router (config)# username madrid password cisco
Router (config)# int s0/0
Router (config-if)# encapsulation ppp
Router (config-if)# ip address 192.168.1.1 255.255.255.252
Router (config-if)# ppp authentication pap
Router (config-if)# ppp pap sent-username madrid password cisco

Configure PPP with CHAP authentication

Router (config)# username madrid password cisco
Router (config)# int s0/0
Router (config-if)# encapsulation ppp
Router (config-if)# ip address 192.168.1.1 255.255.255.252
Router (config-if)# ppp authentication chap

R1#debug ppp authentication
PPP authentication debugging is on

00:30:43: Se0/0 PPP: Using default call direction
00:30:43: Se0/0 PPP: Treating connection as a dedicated line
00:30:45: Se0/0 CHAP: O CHALLENGE id 2 len 23 from "R1"
00:30:45: Se0/0 CHAP: I CHALLENGE id 14 len 23 from "R2"
00:30:45: Se0/0 CHAP: O RESPONSE id 14 len 23 from "R1"
00:30:45: Se0/0 CHAP: I RESPONSE id 2 len 23 from "R2"
00:30:45: Se0/0 CHAP: O SUCCESS id 2 len 4
00:30:45: Se0/0 CHAP: I SUCCESS id 14 len 4

R1#debug ppp authentication (authentication fails below in this output)
PPP authentication debugging is on

00:35:20: Se0/0 PPP: Using default call direction
00:35:20: Se0/0 PPP: Treating connection as a dedicated line
00:35:22: Se0/0 CHAP: O CHALLENGE id 3 len 23 from "R1"
00:35:22: Se0/0 CHAP: I CHALLENGE id 15 len 23 from "R2"
00:35:22: Se0/0 CHAP: O RESPONSE id 15 len 23 from "R1"
00:35:22: Se0/0 CHAP: I RESPONSE id 3 len 23 from "R2"
00:35:22: Se0/0 CHAP: O FAILURE id 3 len 25 msg is "MD/DES compare failed"
00:35:24: Se0/0 CHAP: O CHALLENGE id 4 len 23 from "R1"
00:35:24: Se0/0 CHAP: I CHALLENGE id 16 len 23 from "R2"
00:35:24: Se0/0 CHAP: O RESPONSE id 16 len 23 from "R1"
00:35:24: Se0/0 CHAP: I RESPONSE id 4 len 23 from "R2"
00:35:24: Se0/0 CHAP: O FAILURE id 4 len 25 msg is "MD/DES compare failed"
00:35:26: Se0/0 CHAP: O CHALLENGE id 5 len 23 from "R1"
00:35:26: Se0/0 CHAP: I CHALLENGE id 17 len 23 from "R2"
00:35:26: Se0/0 CHAP: O RESPONSE id 17 len 23 from "R1"
00:35:26: Se0/0 CHAP: I RESPONSE id 5 len 23 from "R2"
00:35:26: Se0/0 CHAP: O FAILURE id 5 len 25 msg is "MD/DES compare failed"
00:35:28: Se0/0 CHAP: O CHALLENGE id 6 len 23 from "R1"
00:35:28: Se0/0 CHAP: I CHALLENGE id 18 len 23 from "R2"
00:35:28: Se0/0 CHAP: O RESPONSE id 18 len 23 from "R1"
00:35:28: Se0/0 CHAP: I RESPONSE id 6 len 23 from "R2"
00:35:28: Se0/0 CHAP: O FAILURE id 6 len 25 msg is "MD/DES compare failed"
00:35:30: Se0/0 CHAP: O CHALLENGE id 7 len 23 from "R1"
00:35:30: Se0/0 CHAP: I CHALLENGE id 19 len 23 from "R2"
00:35:30: Se0/0 CHAP: O RESPONSE id 19 len 23 from "R1"
00:35:30: Se0/0 CHAP: I RESPONSE id 7 len 23 from "R2"
00:35:30: Se0/0 CHAP: O FAILURE id 7 len 25 msg is "MD/DES compare failed"
00:35:32: Se0/0 CHAP: O CHALLENGE id 8 len 23 from "R1"
00:35:32: Se0/0 CHAP: I CHALLENGE id 20 len 23 from "R2"
00:35:32: Se0/0 CHAP: O RESPONSE id 20 len 23 from "R1"
00:35:32: Se0/0 CHAP: I RESPONSE id 8 len 23 from "R2"
00:35:32: Se0/0 CHAP: O FAILURE id 8 len 25 msg is "MD/DES compare failed"
00:35:34: Se0/0 CHAP: O CHALLENGE id 9 len 23 from "R1"
00:35:34: Se0/0 CHAP: I CHALLENGE id 21 len 23 from "R2"
00:35:34: Se0/0 CHAP: O RESPONSE id 21 len 23 from "R1"
00:35:34: Se0/0 CHAP: I RESPONSE id 9 len 23 from "R2"
00:35:34: Se0/0 CHAP: O FAILURE id 9 len 25 msg is "MD/DES compare failed"
00:35:36: Se0/0 CHAP: O CHALLENGE id 10 len 23 from "R1"
00:35:36: Se0/0 CHAP: I CHALLENGE id 22 len 23 from "R2"
00:35:36: Se0/0 CHAP: O RESPONSE id 22 len 23 from "R1"
00:35:36: Se0/0 CHAP: I RESPONSE id 10 len 23 from "R2"
00:35:36: Se0/0 CHAP: O FAILURE id 10 len 25 msg is "MD/DES compare failed"
00:35:38: Se0/0 CHAP: O CHALLENGE id 11 len 23 from "R1"
00:35:38: Se0/0 CHAP: I CHALLENGE id 23 len 23 from "R2"
00:35:38: Se0/0 CHAP: O RESPONSE id 23 len 23 from "R1"
00:35:38: Se0/0 CHAP: I RESPONSE id 11 len 23 from "R2"
00:35:38: Se0/0 CHAP: O FAILURE id 11 len 25 msg is "MD/DES compare failed"
00:35:40: Se0/0 CHAP: O CHALLENGE id 12 len 23 from "R1"
00:35:40: Se0/0 CHAP: I CHALLENGE id 24 len 23 from "R2"
00:35:40: Se0/0 CHAP: O RESPONSE id 24 len 23 from "R1"
00:35:40: Se0/0 CHAP: I RESPONSE id 12 len 23 from "R2"
00:35:40: Se0/0 CHAP: O FAILURE id 12 len 25 msg is "MD/DES compare failed"
00:35:42: Se0/0 CHAP: O CHALLENGE id 13 len 23 from "R1"
00:35:42: Se0/0 CHAP: I CHALLENGE id 25 len 23 from "R2"
00:35:42: Se0/0 CHAP: O RESPONSE id 25 len 23 from "R1"
00:35:42: Se0/0 CHAP: I RESPONSE id 13 len 23 from "R2"
00:35:42: Se0/0 CHAP: O FAILURE id 13 len 25 msg is "MD/DES compare failed"
00:35:44: Se0/0 CHAP: O CHALLENGE id 14 len 23 from "R1"
00:35:44: Se0/0 CHAP: I CHALLENGE id 26 len 23 from "R2"
00:35:44: Se0/0 CHAP: O RESPONSE id 26 len 23 from "R1"
00:35:44: Se0/0 CHAP: I RESPONSE id 14 len 23 from "R2"
00:35:44: Se0/0 CHAP: O FAILURE id 14 len 25 msg is "MD/DES compare failed"
R1#
00:35:46: Se0/0 CHAP: O CHALLENGE id 15 len 23 from "R1"
00:35:46: Se0/0 CHAP: I CHALLENGE id 27 len 23 from "R2"
00:35:46: Se0/0 CHAP: O RESPONSE id 27 len 23 from "R1"
00:35:46: Se0/0 CHAP: I RESPONSE id 15 len 23 from "R2"
00:35:46: Se0/0 CHAP: O FAILURE id 15 len 25 msg is "MD/DES compare failed"u
00:35:48: Se0/0 CHAP: O CHALLENGE id 16 len 23 from "R1"
00:35:48: Se0/0 CHAP: I CHALLENGE id 28 len 23 from "R2"
00:35:48: Se0/0 CHAP: O RESPONSE id 28 len 23 from "R1"
00:35:48: Se0/0 CHAP: I RESPONSE id 16 len 23 from "R2"
00:35:48: Se0/0 CHAP: O FAILURE id 16 len 25 msg is "MD/DES compare failed

R2#debug ppp negotiation
PPP protocol negotiation debugging is on

00:25:40: %LINK-3-UPDOWN: Interface Serial1, changed state to up
00:25:40: Se1 PPP: Treating connection as a dedicated line
00:25:40: Se1 PPP: Phase is ESTABLISHING, Active Open
00:25:40: Se1 LCP: O CONFREQ [Closed] id 2 len 10
00:25:40: Se1 LCP: MagicNumber 0x10930261 (0x050610930261)
00:25:40: Se1 LCP: I CONFREQ [REQsent] id 21 len 10
00:25:40: Se1 LCP: MagicNumber 0x10923B01 (0x050610923B01)
00:25:40: Se1 LCP: O CONFACK [REQsent] id 21 len 10
00:25:40: Se1 LCP: MagicNumber 0x10923B01 (0x050610923B01)
00:25:40: Se1 LCP: I CONFACK [ACKsent] id 2 len 10
00:25:40: Se1 LCP: MagicNumber 0x10930261 (0x050610930261)
00:25:40: Se1 LCP: State is Open
00:25:40: Se1 PPP: Phase is UP
00:25:40: Se1 IPCP: O CONFREQ [Closed] id 2 len 10
00:25:40: Se1 IPCP: Address 192.168.1.2 (0x0306C0A80102)
00:25:40: Se1 CDPCP: O CONFREQ [Closed] id 2 len 4
00:25:40: Se1 IPCP: I CONFREQ [REQsent] id 2 len 10
00:25:40: Se1 IPCP: Address 192.168.1.1 (0x0306C0A80101)
00:25:40: Se1 IPCP: O CONFACK [REQsent] id 2 len 10
00:25:40: Se1 IPCP: Address 192.168.1.1 (0x0306C0A80101)
00:25:40: Se1 CDPCP: I CONFREQ [REQsent] id 2 len 4
00:25:40: Se1 CDPCP: O CONFACK [REQsent] id 2 len 4
00:25:40: Se1 IPCP: I CONFACK [ACKsent] id 2 len 10
00:25:40: Se1 IPCP: Address 192.168.1.2 (0x0306C0A80102)
00:25:40: Se1 IPCP: State is Open
00:25:40: Se1 CDPCP: I CONFACK [ACKsent] id 2 len 4
00:25:40: Se1 CDPCP: State is Open
00:25:40: Se1 IPCP: Install route to 192.168.1.1
00:25:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state
to up

R2#debug ppp packet
PPP packet display debugging is on
R2#
00:23:53: Se1 PPP: I pkt type 0xC021, datagramsize 16
00:23:53: Se1 LCP: I ECHOREQ [Open] id 1 len 12 magic 0x10900C1D
00:23:53: Se1 LCP: O ECHOREP [Open] id 1 len 12 magic 0x109119D t
00:23:56: Se1 PPP: I pkt type 0x0021, datagramsize 56
00:24:01: Se1 LCP: O ECHOREQ [Open] id 3 len 12 magic 0x109119D4
00:24:01: Se1 PPP: I pkt type 0xC021, datagramsize 16
00:24:01: Se1 LCP: I ECHOREP [Open] id 3 len 12 magic 0x10900C1D
00:24:01: Se1 LCP: Received id 3, sent id 3, line up
00:24:03: Se1 PPP: I pkt type 0xC021, datagramsize 16
00:24:03: Se1 LCP: I ECHOREQ [Open] id 2 len 12 magic 0x10900C1D
00:24:03: Se1 LCP: O ECHOREP [Open] id 2 len 12 magic 0x109119D4
00:24:11: Se1 LCP: O ECHOREQ [Open] id 4 len 12 magic 0x109119D4
00:24:11: Se1 PPP: I pkt type 0xC021, datagramsize 16
00:24:11: Se1 LCP: I ECHOREP [Open] id 4 len 12 magic 0x10900C1D
00:24:11: Se1 LCP: Received id 4, sent id 4, line up
00:24:12: Se1 PPP: O pkt type 0x0021, datagramsize 56
00:24:13: Se1 PPP: I pkt type 0xC021, datagramsize 16
00:24:13: Se1 LCP: I ECHOREQ [Open] id 3 len 12 magic 0x10900C1D
00:24:13: Se1 LCP: O ECHOREP [Open] id 3 len 12 magic 0x109119D4

Configure EIGRP

Router (config)# router eigrp 100
Router (config-router)# network 192.168.1.0
Router (config-router)# no auto-summary
Router (config-router)# eigrp log-neighbor-changes

The above is an example of configuring EIGRP. A very simple process it is. No auto-summary will sove soem problems often caused as EIGRP summarizes networks at the classful boundary by default. Discontiguous subnets could have problems if summarization is not turned off. EIGRP log-neighbor-changes logs neighbor changes, it's good to have it on for troubleshooting purposes especially.

Enable manual summarization of EIGRP on interface

Router (config)# int s0/0
Router (config-if)# ip summary-address eigrp 100 10.10.0.0 255.255.0.0

RouterA#sh ip eigrp topology
IP-EIGRP Topology Table for AS(100)/ID(198.198.1.255)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status

P 150.150.0.0/16, 1 successors, FD is 2169856
via Rstatic (2169856/0)
P 195.168.1.34/32, 1 successors, FD is 2169856
via Rconnected (2169856/0)
P 195.168.1.32/30, 1 successors, FD is 2169856
via Connected, Serial0/0
P 195.168.1.33/32, 0 successors, FD is Inaccessible
via 195.168.1.34 (2681856/2169856), Serial0/0

R1#show ip eigrp traffic
IP-EIGRP Traffic Statistics for process 123
Hellos sent/received: 2320/2208
Updates sent/received: 13/14
Queries sent/received: 0/2
Replies sent/received: 2/0
Acks sent/received: 11/10
Input queue high water mark 1, 0 drops
SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0

R1#debug eigrp packet
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK, STUB, SIAQUERY, S
IAREPLY)
R1#
01:47:45: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:47:45: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
R1#
01:47:46: EIGRP: Received HELLO on Ethernet0/0 nbr 20.0.0.1
01:47:46: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0
01:47:46: EIGRP: Sending HELLO on Ethernet0/0
01:47:46: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:47:47: EIGRP: Sending HELLO on Serial0/0
01:47:47: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:47:49: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:47:49: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
R1#
01:47:50: EIGRP: Received HELLO on Ethernet0/0 nbr 20.0.0.1
01:47:50: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0
01:47:51: EIGRP: Sending HELLO on Ethernet0/0
01:47:51: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:47:52: EIGRP: Sending HELLO on Serial0/0
01:47:52: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:47:54: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:47:54: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:47:55: EIGRP: Received HELLO on Ethernet0/0 nbr 20.0.0.1
01:47:55: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0
R1#
01:47:56: EIGRP: Sending HELLO on Ethernet0/0
01:47:56: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:47:57: EIGRP: Sending HELLO on Serial0/0
01:47:57: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:47:59: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:47:59: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:47:59: EIGRP: Received HELLO on Ethernet0/0 nbr 20.0.0.1
01:47:59: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0
R1#
01:48:00: EIGRP: Sending HELLO on Ethernet0/0
01:48:00: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:01: EIGRP: Sending HELLO on Serial0/0
01:48:01: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:04: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:04: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:48:04: EIGRP: Received HELLO on Ethernet0/0 nbr 20.0.0.1
01:48:04: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0
01:48:04: EIGRP: Sending HELLO on Ethernet0/0
01:48:04: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:06: EIGRP: Sending HELLO on Serial0/0
01:48:06: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:08: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:08: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:48:09: EIGRP: Received HELLO on Ethernet0/0 nbr 20.0.0.1
01:48:09: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0
01:48:09: EIGRP: Sending HELLO on Ethernet0/0
01:48:09: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:11: EIGRP: Sending HELLO on Serial0/0
01:48:11: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:13: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:13: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:48:14: EIGRP: Sending HELLO on Ethernet0/0
01:48:14: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
01:48:14: EIGRP: Received QUERY on Serial0/0 nbr 192.168.1.2
01:48:14: AS 123, Flags 0x0, Seq 12/10 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rel
y 0/0
01:48:14: EIGRP: Enqueueing ACK on Serial0/0 nbr 192.168.1.2
01:48:14: Ack seq 12 iidbQ un/rely 0/0 peerQ un/rely 1/0
01:48:14: EIGRP: Sending ACK on Serial0/0 nbr 192.168.1.2
01:48:14: AS 123, Flags 0x0, Seq 0/12 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
1/0
01:48:14: EIGRP: Enqueueing REPLY on Serial0/0 nbr 192.168.1.2 iidbQ un/rely 0/1
peerQ un/rely 0/0 serno 13-13
01:48:14: EIGRP: Requeued unicast on Serial0/0
01:48:14: EIGRP: Sending REPLY on Serial0/0 nbr 192.168.1.2
01:48:14: AS 123, Flags 0x0, Seq 11/12 idbQ 0/0
R1# iidbQ un/rely 0/0 peerQ un/rely 0/1 serno 13-13
01:48:14: EIGRP: Received ACK on Serial0/0 nbr 192.168.1.2
01:48:14: AS 123, Flags 0x0, Seq 0/11 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/1
R1#
01:48:16: EIGRP: Sending HELLO on Serial0/0
01:48:16: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:17: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:17: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:48:18: EIGRP: Sending HELLO on Ethernet0/0
01:48:18: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:20: EIGRP: Sending HELLO on Serial0/0
01:48:20: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:22: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:22: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:48:23: EIGRP: Sending HELLO on Ethernet0/0
01:48:23: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:25: EIGRP: Sending HELLO on Serial0/0
01:48:25: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:27: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:27: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:48:28: EIGRP: Sending HELLO on Ethernet0/0
01:48:28: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:29: EIGRP: Sending HELLO on Serial0/0
01:48:29: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:32: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:32: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
01:48:33: EIGRP: Sending HELLO on Ethernet0/0
01:48:33: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:34: EIGRP: Sending HELLO on Serial0/0
01:48:34: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
R1#
01:48:36: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:36: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0
R1#
01:48:37: EIGRP: Sending HELLO on Ethernet0/0
01:48:37: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
01:48:38: EIGRP: Sending HELLO on Serial0/0
01:48:38: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
01:48:38: EIGRP: Received UPDATE on Serial0/0 nbr 192.168.1.2
01:48:38: AS 123, Flags 0x0, Seq 13/11 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rel
y 0/0
01:48:38: EIGRP: Enqueueing ACK on Serial0/0 nbr 192.168.1.2
01:48:38: Ack seq 13 iidbQ un/rely 0/0 peerQ un/rely 1/0
01:48:38: EIGRP: Sending ACK on Serial0/0 nbr 192.168.1.2
01:48:38: AS 123, Flags 0x0, Seq 0/13 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
1/0
01:48:38: EIGRP: Enqueueing UPDATE on Serial0/0
R1# iidbQ un/rely 0/1 serno 14-14
01:48:38: EIGRP: Enqueueing UPDATE on Serial0/0 nbr 192.168.1.2 iidbQ un/rely 0/
0 peerQ un/rely 0/0 serno 14-14
01:48:38: EIGRP: Sending UPDATE on Serial0/0 nbr 192.168.1.2
01:48:38: AS 123, Flags 0x0, Seq 12/13 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rel
y 0/1 serno 14-14
01:48:38: EIGRP: Received ACK on Serial0/0 nbr 192.168.1.2
01:48:38: AS 123, Flags 0x0, Seq 0/12 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/1
01:48:38: EIGRP: Serial0/0 multicast flow blocking cleared
R1#
01:48:41: EIGRP: Received HELLO on Serial0/0 nbr 192.168.1.2
01:48:41: AS 123, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely
0/0

R1#debug eigrp fsm
EIGRP FSM Events/Actions debugging is on
01:40:11: DUAL: rcvupdate: 192.168.1.0/30 via Connected metric 4294967295/429496
7295
01:40:11: DUAL: Find FS for dest 192.168.1.0/30. FD is 10511872, RD is 10511872
01:40:11: DUAL: 0.0.0.0 metric 4294967295/4294967295 not found Dmin is 4
294967295
01:40:11: DUAL: Dest 192.168.1.0/30 entering active state.
01:40:11: DUAL: Set reply-status table. Count is 1.
01:40:11: DUAL: Not doing split horizon
01:40:11: %DUAL-5-NBRCHANGE: IP-EIGRP 123: Neighbor 192.168.1.2 (Serial0/0) is d
own: interface down
01:40:11: DUAL: linkdown: start - 192.168.1.2 via Serial0/0
01:40:11: DUAL: Destination 10.0.0.0/24
01:40:11: DUAL: Destination 20.0.0.0/24
01:40:11: DUAL: Find FS for dest 20.0.0.0/24. FD is 10537472, RD is 10537472
01:40:11: DUAL: 192.168.1.2 metric 4294967295/4294967295 not found Dmin
is 4294967295
01:40:11: DUAL: Dest 20.0.0.0/24 (No peers) not entering active state.
01:40:11: DUAL: Removing dest 20.0.0.0/24, nexthop 192.168.1.2
01:40:11: DUAL: No routes. Flushing dest 20.0
R1(config-if)#.0.0/24
01:40:11: DUAL: Destination 192.168.1.0/30
01:40:11: DUAL: Clearing handle 0, count now 0
01:40:11: DUAL: Freeing reply status table
01:40:11: DUAL: Find FS for dest 192.168.1.0/30. FD is 4294967295, RD is 4294967
295 found
01:40:11: DUAL: Removing dest 192.168.1.0/30, nexthop 0.0.0.0
01:40:11: DUAL: No routes. Flushing dest 192.168.1.0/30
01:40:11: DUAL: linkdown: finish
01:40:21: %LINK-3-UPDOWN: Interface Serial0/0, changed state to up
R1#
01:40:21: DUAL: dest(192.168.1.0/30) not active
01:40:21: DUAL: rcvupdate: 192.168.1.0/30 via Connected metric 10511872/0
01:40:21: DUAL: Find FS for dest 192.168.1.0/30. FD is 4294967295, RD is 4294967
295 found
01:40:21: DUAL: RT installed 192.168.1.0/30 via 0.0.0.0
01:40:21: DUAL: Send update about 192.168.1.0/30. Reason: metric chg
01:40:21: DUAL: Send update about 192.168.1.0/30. Reason: new if
R1#
01:40:22: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed sta
te to up
R1#
01:40:24: %DUAL-5-NBRCHANGE: IP-EIGRP 123: Neighbor 192.168.1.2 (Serial0/0) is u
p: new adjacency
R1#
01:40:26: DUAL: dest(20.0.0.0/24) not active
01:40:26: DUAL: rcvupdate: 20.0.0.0/24 via 192.168.1.2 metric 10537472/281600
01:40:26: DUAL: Find FS for dest 20.0.0.0/24. FD is 4294967295, RD is 4294967295
found
01:40:26: DUAL: RT installed 20.0.0.0/24 via 192.168.1.2
01:40:26: DUAL: Send update about 20.0.0.0/24. Reason: metric chg
01:40:26: DUAL: Send update about 20.0.0.0/24. Reason: new if

Friday, March 17, 2006

Configure RIP v1 on router

Router (config)# router rip
Router (config-router)# network 192.168.1.0
Router (config-router)# network 192.168.2.0
Router (config-router)# end

Configure RIP v2 on router (RIP v2 is classless sends subnet info in updates)

Router (config)# router rip
Router (config-router)# version 2
Router (config-router)# network 192.168.1.0
Router (config-router)# end

Configuring RIP timers

Router (config)# router rip
Router (config-router)# timers basic 30 180 180 240 360
Router (config-router)# end

Adjust the timers above, those values above are the defaults for RIP. Routing updates: 30 seconds, Invalid timer: 180 seconds, Hold-down timer: 180 seconds, Flush timer: 240 seconds, Sleep time: 360 seconds

Configure number of paths for load balancing for RIP

Router (config-router)# maximum-paths 6

The above allows you to define the number of paths for load balancing, 6 is the maximum, 4 is the default value.

Here's the debug information associated with rip, the 'debug ip rip' command entered.

R1#debug ip rip
RIP protocol debugging is on

00:17:32: RIP: ignored v1 update from bad source 20.0.0.1 on Ethernet0/0
00:17:32: RIP: received v1 update from 192.168.1.2 on Serial0/0
00:17:32: 20.0.0.0 in 1 hops
00:17:48: RIP: sending v1 update to 255.255.255.255 via Ethernet0/0 (10.0.0.1)
00:17:48: RIP: build update entries
00:17:48: network 20.0.0.0 metric 2
00:17:48: network 192.168.1.0 metric 1
00:17:48: RIP: sending v1 update to 255.255.255.255 via Serial0/0 (192.168.1.1)
00:17:48: RIP: build update entries
00:17:48: network 10.0.0.0 metric 1
00:18:00: RIP: ignored v1 update from bad source 20.0.0.1 on Ethernet0/0
00:18:00: RIP: received v1 update from 192.168.1.2 on Serial0/0
00:18:00: 20.0.0.0 in 1 hops
00:18:15: RIP: sending v1 update to 255.255.255.255 via Ethernet0/0 (10.0.0.1)
00:18:15: RIP: build update entries
00:18:15: network 20.0.0.0 metric 2
00:18:15: network 192.168.1.0 metric 1
00:18:15: RIP: sending v1 update to 255.255.255.255 via Serial0/0 (192.168.1.1)
00:18:15: RIP: build update entries
00:18:15: network 10.0.0.0 metric 1
00:18:28: RIP: ignored v1 update from bad source 20.0.0.1 on Ethernet0/0
00:18:28: RIP: received v1 update from 192.168.1.2 on Serial0/0
00:18:28: 20.0.0.0 in 1 hops

Configure a DHCP Pool

Router (config)# ip dhcp pool ccna
Router (dhcp-config)# network 10.0.0.0 255.255.255.0
Router (dhcp-config)# default-router 10.0.0.1
Router (dhcp-config)# dns-server 10.0.0.2
Router (dhcp-config)# netbios-name-server 10.0.0.3
Router (dhcp-config)# domain-name ccna.org
Router (dhcp-config)# lease 1 10 20
Router (dhcp-config)# exit
Router (config)# ip dhcp excluded-address 10.0.0.1 10.0.0.4

The above is an example of configuring a DHCP pool on a Cisco router. For the line that says 'lease' 1 is day, 10 is hours, 20 is minutes. For ip dhcp excluded-address line, 10.0.0.1 is lowest, than 10.0.0.4 is highest, basically hosts set up for the DHCP process will start giving out addresses starting at 10.0.0.5 - 10.0.0.254.

Configure DHCP Helper Address

Router (config)# int fa0/0
Router (config-if)# ip helper-address 10.0.0.2

The above will forward broadcasts to 10.0.0.2

Below is some helpful debug information.

CCNA2610#debug ip dhcp server events

02:43:37: DHCPD: returned 172.16.0.6 to address pool ccna.
CCNA2610#
02:43:48: DHCPD: assigned IP address 172.16.0.6 to client 0100.112f.9a0f.6c.
CCNA2610#
02:44:04: DHCPD: returned 172.16.0.6 to address pool ccna.
CCNA2610#
02:44:11: DHCPD: checking for expired leases.
02:44:11: DHCPD: dhcpd_age_bindings could not lock semaphore.
02:44:12: DHCPD: assigned IP address 172.16.0.6 to client 0100.112f.9a0f.6c.

Saturday, March 11, 2006

OSPF

OSPF (Open Shortest Path First) is a link state routing protocol. It sends triggered updates which are immediate updates sent when there is a change detected in the topology. It only sends information that has changed, it doesn't send it's entire routing table like distance vector protocols such as RIP and IGRP. OSPF has more to it than RIP or IGRP, and is therefore more complex. In can be used in large networks and is an open standard. EIGRP is Cisco proprietary.

OSPF facts:

Link-state protocol
Administrative distance is 110
Uses cost as metric (which is based on bandwidth)
OSPF reference bandwidth 10/8 bandwidth
Uses Multicast addresses -- 224.0.0.5 (all OSPF routers) & 224.0.0.6 (all DR/BDR routers)
Supports VLSM (variable length subnet masks)

DR = Designated Router
BDR = Backup Designated Router

Read more about the DR & BDR election process in such sources as CCNA 3&4 Companion Guide by Cisco Press. In Point-to-point and Point-to-multipoint networks, there is no DR election. On Broadcast multiaccess (Ethernet, Token Ring, FDDI) & Nonbroadcast multiaccess (Frame Relay, X.25, SMDS) there is a election.

OSPF default priority = 1
Router will not be elected DR = 0
Tie in election = 255

OSPF router uses highest local IP address as OSPF router ID. If loopback is configured it is used as router ID no matter what. You can change the election process with 'ip ospf priority' command. The below is an example of how to do such a task.

Modifying OSPF priority

Router (config)# int e0/0
Router (config-if)# ip ospf priority 50

In OSPF, a higher bandwidth means a lower cost which OSPF prefers. Higher means lower cost and will use that instead. Lower value of cost means better. Also, changing the bandwidth rate on an interface will force OSPF to recalculate the cost of the link.

--------------------------
OSPF DEFAULT COSTS
56k Serial link 1785
T1 link 64
10Mbps Ethernet 10
100 Mbps Ethernet, FDDI 1
Gigabit Ethernet or higher 1
--------------------------

Modifying OSPF Cost

Router (config)# int s0/0
Router (config-if)# ip ospf cost 300

In CCNA, OSPF is only discussed in Area 0, not Area 1 or other areas. Therefore, Area 0 is all that should be concerned about at this point. With OSPF, when you are advertising your networks, you must use wildcard masks, the subnet mask being inversed. Similiar as to with ACLs (access-control lists). The below is an example on how to configure OSPF. This should be the first step over modifiying other OSPF parameters. OSPF uses what they call process ID, which is basically like AS (autonomous system) numbers in IGRP and EIGRP. The process ID in OSPF can be any value between 1-65535.

Basic configuration of OSPF in Area 0

Router # configure terminal
Router (config)# router ospf 1
Router (config-router)# network 192.168.1.0 0.0.0.3 area 0
Router (config-router)# network 10.0.0.0 0.0.0.255 area 0
Router (config-router)# end
Router # copy run start

Modifying OSPF Timers

Router # configure terminal
Router (config) int s0/0
Router (config-if)# ip ospf hello-interval 20
Router (config-if)# ip ospf dead-interval 80

By default, OSPF sends hello packets every 10 seconds. The dead interval timer is 40 seconds. Timers on both ends of the link should be the same, otherwise problems will occur and the routers won't be able to become neighbors. On Broadcast OSPF networks such as Ethernet or Token Ring, hello packets are sent every 10 seconds, dead interval timer is set at 40 seconds. On Non-broadcast OSPF networks such as Frame Relay, hellos are sent every 30 seconds, with dead interval timer being 120 seconds.

OSPF Packet Type:
Type 1 - Hello
Type 2 - Database description packet (DBD)
Type 3 - Link State Request
Type 4 - Link State Update
Type 5 - Link State Acknowledgement (LSACK)

Above, those are the 5 different OSPF packets. Type 1 packet which is a hello packet, is used to create and maintain adjacency information with neighbors. Type 2 packet describes the contents of an OSPF router's link-state database. This blog is not to note every single detail, just some key points here and there, and primarily used to show how to type certain commands and debug info.

The following below are the different 'states' in OSPF in order:

Down
Init
Two-way
Exstart
Exchange
Loading
Full adjacency

OSPF Databases - Adjacencies database, Link-state database (topological database), Forwarding database (routing table)

Configuring OSPF Authentication (no encryption, Simple authentication)

Router (config)# router ospf 1
Router (config-router)# area 0 authentication
Router (config-router)# exit
Router(config)# int e0/0
Router(config-if)# ip ospf authentication-key nick

Configuring OSPF Authentication using MD5 Encryption (encryption is used)

Router (config)# router ospf 1
Router (config-router)# area 0 authentication message-digest
Router (config-router)# exit
Router (config)# int e0/0
Router (config-if)# ip ospf message-digest-key 1 md5 nick

OSPF authentication using the MD5 hash algorithm is recommended for security reasons. When using OSPF encryption authentication, the Key-id which in the above is 1, must be the same on the neighboring router. The same goes for the key password which above is nick.

Propagate Default Route in OSPF

Router (config)# ip route 0.0.0.0 0.0.0.0 192.168.1.2
Router (config)# router ospf 1
Router (config-router)# default-information originate

The above will set the default route and propagate it to all OSPF routers.

Below are some different show commands used with OSPF.

R2#show ip ospf
Routing Process "ospf 1" with ID 200.10.1.255
Supports only single TOS(TOS0) routes
Supports opaque LSA
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
External flood list length 0
Area BACKBONE(0)
Number of interfaces in this area is 2
Area has no authentication
SPF algorithm executed 5 times
Area ranges are
Number of LSA 4. Checksum Sum 0x1FB5B
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0

R2#show ip ospf int
Ethernet0 is up, line protocol is up
Internet Address 10.0.0.2/24, Area 0
Process ID 1, Router ID 200.10.1.255, Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 200.10.1.255, Interface address 10.0.0.2
Backup Designated router (ID) 200.10.2.255, Interface address 10.0.0.1
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:05
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 2, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 200.10.2.255 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
Serial0 is up, line protocol is up
Internet Address 192.168.1.1/24, Area 0
Process ID 1, Router ID 200.10.1.255, Network Type POINT_TO_POINT, Cost: 1562
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:03
Index 2/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 192.168.1.2
Suppress hello for 0 neighbor(s)

R2#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface
200.10.2.255 1 FULL/BDR 00:00:36 10.0.0.1 Ethernet0
192.168.1.2 1 FULL/ - 00:00:35 192.168.1.2 Serial0

R1#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface
200.10.1.255 1 FULL/DR 00:00:32 10.0.0.2 Ethernet0/0

R2#show ip ospf neighbor detail
Neighbor 200.10.2.255, interface address 10.0.0.1
In the area 0 via interface Ethernet0
Neighbor priority is 1, State is FULL, 6 state changes
DR is 10.0.0.2 BDR is 10.0.0.1
Options is 0x42
Dead timer due in 00:00:33
Index 2/2, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Neighbor 192.168.1.2, interface address 192.168.1.2
In the area 0 via interface Serial0
Neighbor priority is 1, State is FULL, 6 state changes
DR is 0.0.0.0 BDR is 0.0.0.0
Options is 0x42
Dead timer due in 00:00:32
Index 1/1, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec

R2#show ip ospf database

OSPF Router with ID (200.10.1.255) (Process ID 1)

Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link count
192.168.1.2 192.168.1.2 536 0x80000011 0x5129 3
200.10.1.255 200.10.1.255 421 0x80000003 0xD0F6 3
200.10.2.255 200.10.2.255 417 0x80000006 0x2D37 1

Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum
10.0.0.2 200.10.1.255 421 0x80000001 0xAC05

Below are some debug OSPF commands.

R2#debug ip ospf packet
OSPF packet debugging is on
R2#
00:02:40: OSPF: rcv. v:2 t:1 l:48 rid:192.168.1.2
aid:0.0.0.0 chk:70E6 aut:0 auk: from Serial0
00:02:41: OSPF: rcv. v:2 t:1 l:44 rid:200.10.2.255
aid:0.0.0.0 chk:3195 aut:0 auk: from Ethernet0
00:02:50: OSPF: rcv. v:2 t:1 l:48 rid:192.168.1.2
aid:0.0.0.0 chk:70E6 aut:0 auk: from Serial0
00:02:50: OSPF: rcv. v:2 t:2 l:32 rid:200.10.2.255
aid:0.0.0.0 chk:DBAC aut:0 auk: from Ethernet0
00:02:50: OSPF: rcv. v:2 t:2 l:52 rid:200.10.2.255
aid:0.0.0.0 chk:ED99 aut:0 auk: from Ethernet0
00:02:50: OSPF: rcv. v:2 t:3 l:60 rid:200.10.2.255

R2#debug ip ospf adj
OSPF adjacency events debugging is on

00:10:55: OSPF: Build router LSA for area 0, router ID 200.10.1.255, seq 0x80000
005
00:10:56: %LINK-3-UPDOWN: Interface Ethernet0, changed state to up
00:10:57: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed sta
te to up
00:11:01: OSPF: 2 Way Communication to 200.10.2.255 on Ethernet0, state 2WAY
00:11:01: OSPF: Backup seen Event before WAIT timer on Ethernet0
00:11:01: OSPF: DR/BDR election on Ethernet0
00:11:01: OSPF: Elect BDR 200.10.1.255
00:11:01: OSPF: Elect DR 200.10.2.255
00:11:01: OSPF: Elect BDR 200.10.1.255
00:11:01: OSPF: Elect DR 200.10.2.255
00:11:01: DR: 200.10.2.255 (Id) BDR: 200.10.1.255 (Id)
00:11:01: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x1FAF opt 0x42 flag 0
x7 len 32
00:11:04: OSPF: Rcv DBD from 200.10.2.255 on Ethernet0 seq 0x16FE opt 0x42 flag
0x7 len 32 mtu 1500 state EXSTART
00:11:04: OSPF: NBR Negotiation Done. We are the SLAVE
00:11:04: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x16FE opt 0x42 flag 0
x2 len 92
00:11:04: OSPF: Rcv DBD from 200.10.2.255 on Ethernet0 seq 0x16FF opt 0x42 flag
0x3 len 112 mtu 1500 state EXCHANGE
00:11:04: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x16FF opt 0x42 flag 0
x0 len 32
00:11:04: OSPF: Database request to 200.10.2.255
00:11:04: OSPF: sent LS REQ packet to 10.0.0.1, length 24
00:11:04: OSPF: Rcv DBD from 200.10.2.255 on Ethernet0 seq 0x1700 opt 0x42 flag
0x1 len 32 mtu 1500 state EXCHANGE
00:11:04: OSPF: Exchange Done with 200.10.2.255 on Ethernet0
00:11:04: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x1700 opt 0x42 flag 0
x0 len 32
00:11:04: OSPF: We are not DR to build Net Lsa for interface Ethernet0
00:11:04: OSPF: Synchronized with 200.10.2.255 on Ethernet0, state FULL
00:11:05: OSPF: Build router LSA for area 0, router ID 200.10.1.255, seq 0x80000
006
00:11:10: OSPF: We are not DR to build Net Lsa for interface Ethernet0
00:11:10: OSPF: Build network LSA for Ethernet0, router ID 200.10.1.255
00:11:11: OSPF: Neighbor change Event on interface Ethernet0
00:11:11: OSPF: DR/BDR election on Ethernet0
00:11:11: OSPF: Elect BDR 200.10.1.255
00:11:11: OSPF: Elect DR 200.10.2.255
00:11:11: DR: 200.10.2.255 (Id) BDR: 200.10.1.255 (Id)

R2#debug ip ospf events
OSPF events debugging is on

00:13:41: OSPF: Rcv hello from 200.10.2.255 area 0 from Ethernet0 10.0.0.1
00:13:41: OSPF: 2 Way Communication to 200.10.2.255 on Ethernet0, state 2WAY
00:13:41: OSPF: Backup seen Event before WAIT timer on Ethernet0
00:13:41: OSPF: DR/BDR election on Ethernet0
00:13:41: OSPF: Elect BDR 200.10.1.255
00:13:41: OSPF: Elect DR 200.10.2.255
00:13:41: OSPF: Elect BDR 200.10.1.255
00:13:41: OSPF: Elect DR 200.10.2.255
00:13:41: DR: 200.10.2.255 (Id) BDR: 200.10.1.255 (Id)
00:13:41: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x5CF opt 0x42 flag 0x
7 len 32
00:13:41: OSPF: End of hello processing
00:13:46: OSPF: Retransmitting DBD to 200.10.2.255 on Ethernet0
00:13:46: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x5CF opt 0x42 flag 0x
7 len 32
00:13:46: OSPF: Rcv DBD from 200.10.2.255 on Ethernet0 seq 0x191B opt 0x42 flag
0x7 len 32 mtu 1500 state EXSTART
00:13:46: OSPF: NBR Negotiation Done. We are the SLAVE
00:13:46: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x191B opt 0x42 flag 0
x2 len 112
00:13:46: OSPF: Rcv DBD from 200.10.2.255 on Ethernet0 seq 0x191C opt 0x42 flag
0x3 len 92 mtu 1500 state EXCHANGE
00:13:46: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x191C opt 0x42 flag 0
x0 len 32
00:13:46: OSPF: Database request to 200.10.2.255
00:13:46: OSPF: sent LS REQ packet to 10.0.0.1, length 12
00:13:46: OSPF: Rcv DBD from 200.10.2.255 on Ethernet0 seq 0x191D opt 0x42 flag
0x1 len 32 mtu 1500 state EXCHANGE
00:13:46: OSPF: Exchange Done with 200.10.2.255 on Ethernet0
00:13:46: OSPF: Send DBD to 200.10.2.255 on Ethernet0 seq 0x191D opt 0x42 flag 0
x0 len 32
00:13:46: OSPF: Synchronized with 200.10.2.255 on Ethernet0, state FULL
00:13:50: OSPF: Rcv hello from 192.168.1.2 area 0 from Serial0 192.168.1.2
00:13:50: OSPF: End of hello processing
00:13:51: OSPF: Rcv hello from 200.10.2.255 area 0 from Ethernet0 10.0.0.1
00:13:51: OSPF: Neighbor change Event on interface Ethernet0
00:13:51: OSPF: DR/BDR election on Ethernet0
00:13:51: OSPF: Elect BDR 200.10.1.255
00:13:51: OSPF: Elect DR 200.10.2.255
00:13:51: DR: 200.10.2.255 (Id) BDR: 200.10.1.255 (Id)
00:13:51: OSPF: End of hello processing
00:14:00: OSPF: Rcv hello from 192.168.1.2 area 0 from Serial0 192.168.1.2
00:14:00: OSPF: End of hello processing
00:14:01: OSPF: Rcv hello from 200.10.2.255 area 0 from Ethernet0 10.0.0.1
00:14:01: OSPF: End of hello processing
00:14:10: OSPF: Rcv hello from 192.168.1.2 area 0 from Serial0 192.168.1.2
00:14:10: OSPF: End of hello processing
00:14:11: OSPF: Rcv hello from 200.10.2.255 area 0 from Ethernet0 10.0.0.1
00:14:11: OSPF: End of hello processing

Wednesday, March 08, 2006

I've gathered some hands-on examples of configuring different things Cisco related. The following are examples of configuring such things as router passwords, hostnames, assigning IP address to interfaces, etc.

Example of configuring Cisco router passwords & hostname

Router > enable
Router # configure terminal
Router (config)# hostname Detroit
Detroit (config)# enable password cisco
Detroit (config)# enable secret class
Detroit (config)# line console 0
Detroit (config-line)# logging synchronous
Detroit (config-line)# password cisco
Detroit (config-line)# login
Detroit (config-line)# exit
Detroit (config)# line vty 0 4
Detroit (config-line)# password cisco
Detroit (config-line)# login
Detroit (config-line)# exit
Detroit (config)# line aux 0
Detroit (config-line)# password cisco
Detroit (config-line)# login
Detroit (config-line)# exit
Detroit # copy run start

The above shows an example of configuring passwords and a hostname for the router. Use copy run start to save the new config into NVRAM. Logging synchronous is used so when something happens like an interface goes down and a message comes on, your typing won't be interrupted. Use 'enable' from user mode to enter priviliged mode, then configure terminal to enter global config mode. To encrypt all passwords, use 'service password-encryption' command from the global config mode. By default, the enable secret password is encrypted already. To turn off service password-encryption of having all passwords other than enable secret encrypted, use 'no service password-encryption' from global config mode.

Example of Configuring Serial & Ethernet/Fast Ethernet Interfaces

Router > enable
Router # configure terminal
Router (config)# int s0/0
Router (config-if)# description This is the serial interface
Router (config-if)# ip address 192.168.1.1 255.255.255.0
Router (config-if)# clockrate 56000
Router (config-if)# bandwidth 1544
Router (config-if)# no shutdown
Router (config-if)# int fa0/0
Router (config-if)# description This is the ethernet interface for the network
Router (config-if)# ip address 10.0.0.1 255.255.255.0
Router (config-if)# no shutdown
Router (config-if)# exit
Router # copy run start

The following above assumes the device is a DCE and needs to provide clocking to the other end, the DTE device. Also, as you can see, the description is above as well and enables you to describe the interface or where it connects to, etc. Bandwidth can also be specified and on serial interfaces the default is already 1544, 1.544 mbps. Also, remember to save your configuration to NVRAM, so if you turn off the router later and power it back on, everything will be restored from NVRAM. (Non-volatile random access memory, retains information even while power is off)
DCE = Data Communications Equipment
DTE = Data Termination Equipment

The image “http://www.seinfeld.cjb.cc/computerstuff/ccnanetacadlogo.jpg” cannot be displayed, because it contains errors.

The image “http://www.seinfeld.cjb.cc/computerstuff/ccnanetacadlogo.jpg” cannot be displayed, because it contains errors.

I have gathered more things such as very helpful activities from CCNA semesters 2-4. These can be downloaded through the Cisco Networking Academy tools section. Keep in mind CCNA 1 semester doesn't involve many hands-on labs on configuring routers, switches, subnetting is the big thing in the 1st semester that you need to know. I have uploaded them to webspace I have at cjb.cc (which also offers free websites with a nice cjb.cc domain name) and the following contain a whole bunch of different lab activities per semester. Check them out!

CCNA 2 semester activities
CCNA 3 semester activities
CCNA 4 semester activities

Below are some practice questions from each semester developed by the Cisco Networking Academy.

CCNA 1 practice questions
CCNA 2 practice questions
CCNA 3 practice questions
CCNA 4 practice questions

Also check out the Subnet Reference (Requires Adobe Acrobat Reader) that I have made.

Tuesday, March 07, 2006

Networking can be laid out in 7 different layers. Different things happen at each layer. The following are the 7 layers of what is called the OSI (Open Systems Interconnect) Model:

Layer 7 - Application layer (examples: FTP, HTTP, SMTP, Telnet)
Layer 6 - Presentation layer (examples: JPEG, MIDI)
Layer 5 - Session layer (examples: NETBIOS, DECnet)
Layer 4 - Transport layer (examples: TCP, UDP, SPX)
Layer 3 - Network layer (examples: IP, IPX, Appletalk, ARP, RARP, routers)
Layer 2 - Data-link layer (examples: PPP, VTP, CDP, switches, bridges, NIC)
Layer 1 - Physical layer (examples: V.35, DSL, hubs, repeaters, modems)

The CCNA program covers so much material. I created this blog because I felt like sharing more CCNA stuff with the general public, and whomever expresses an interest in Cisco technology, particularly the CCNA curriculum.

I've taken the CCNA exam and not been successful. It is not an easy exam.

CCNA 640-801 quick facts:

Price: USD $125.00
Questions: 55-65
Duration of exam: 90 minutes
Languages: English, Japanese
Expires: Yes, after 3 years

Categories of test taken from the link here and also below.

Planning & Designing

Design a simple LAN using Cisco Technology
Design an IP addressing scheme to meet design requirements
Select an appropriate routing protocol based on user requirements
Design a simple internetwork using Cisco technology
Develop an access list to meet user specifications
Choose WAN services to meet customer requirements

Implementation & Operation

Configure routing protocols given user requirements
Configure IP addresses, subnet masks, and gateway addresses on routers and hosts
Configure a router for additional administrative functionality
Configure a switch with VLANS and inter-switch communication
Implement a LAN
Customize a switch configuration to meet specified network requirements
Manage system image and device configuration files
Perform an initial configuration on a router
Perform an initial configuration on a switch
Implement access lists
Implement simple WAN protocols

Troubleshooting

Utilize the OSI model as a guide for systematic network troubleshooting
Perform LAN and VLAN troubleshooting
Troubleshoot routing protocols
Troubleshoot IP addressing and host configuration
Troubleshoot a device as part of a working network
Troubleshoot an access list
Perform simple WAN troubleshooting

Technology

Describe network communications using layered models
Describe the Spanning Tree process
Compare and contrast key characteristics of LAN environments
Evaluate the characteristics of routing protocols
Evaluate TCP/IP communication process and its associated protocols
Describe the components of network devices
Evaluate rules for packet control
Evaluate key characteristics of WANs

Above are CCNA categories you are graded on. That may not be all the things tested on but general concepts.

I invite you to try some very basic activities from things I have gathered below.

Configure Router Passwords
Configure a Serial Interface
Configure an Ethernet Interface

Any questions or comments are welcome.