Minggu, 17 Februari 2008

VPN: Virtual Private Network

Virtual Private Network (VPN) refers to simulating a private network over the public Internet by encrypting communications between the two private end-points. This provides the same connectivity , QOS and privacy you would find on a typical private network. Typically, VPNs cab be categorized as follows:

Traditional VPNs

· Frame Relay VPN (Layer 2)

· ATM VPN (Layer 2)

CPE-based VPNs

· L2TP and PPTP VPN (Layer 2)

· IPsec VPN (Layer 3)

Provider Provisioned VPNs (PP-VPNs)

· BGP/MPLS VPNs (Layer 2 and 3, RFC 2547bis)

Session based VPN

· SSL VPN (Layer 4 +)

· SOCKS VPN (Layer 4 +)

The traditional VPN technologies have been widely deployed in the field by Service Providers and Enterprises. However, due to their high cost and less features, new VNP technologies such as IPsec VPN, SSL VPN and MPLS VPN are becoming more and more popular. These new VPN technologies are fully compatible with TCP/IP, the choice of technology for data routing and transportation of the world.

The key technology for VPN is the security of data over a public network. The three types of security: authentication, encryption and encapsulation, forms the foundation of virtual private networking. However, authentication, encryption and encapsulation can be performed by many different technologies. In addition, these three sets of technologies can be combined in different ways.

For data encapsulation in VPN, many tunneling technologies are developed, such as Layer 2 Tunneling Protocol (L2TP), Layer 2 Forward protocol (L 2F ) and Point to Point Tunneling Protocol (PPTP). PPTP provides remote users encrypted, multi-protocol access to a corporate network over the Internet. Network layer protocols, such as IPX and NetBEUI, are encapsulated by the PPTP for transport over the Internet. However, PPTP can support only one tunnel at a time for each user. Therefore, its proposed successor, L2TP (a hybrid of PPTP and another protocol, L 2F ) can support multiple, simultaneous tunnels for each user. PPTP and L2TP are the layer 2 VPN technologies from CPE (customer premise equipment) to CPE.

Internet Protocol Security (IPSec), the most widely deployed VPN technology, is a set of authentication and encryption protocols developed by the Internet Engineering Task Force (IETF), to address data confidentiality, integrity, authentication and key management in the IP networks. The IPSec protocol typically works on the edges of a security domain, which encapsulates a packet by wrapping another packet around it. It then encrypts the entire packet. This encrypted stream of traffic forms a secure tunnel across an otherwise unsecured IP network. IPsec is the primary layer 3 VPN technology providing a CPE to CPE tunnel.

SSL/TLS, a technology popularly used for secured communication of web traffic (HTTPS), can also be also used for VPN. SSL VPNs use the highly mature and widespread SSL/TLS protocol to handle the tunnel creation and cryptographic elements necessary to create a VPN. SSL/TLS is much easier to implement than IPSec and provides a simple and well-tested platform. The RSA handshake (or DH) is used exactly as IKE in IPSec, and the SSL crypto library is used to secure the symmetric tunnel after that, again using similar encryption techniques to those protecting IPSec tunnels. This tunnel can pass arbitrary traffic, just like an IPSec VPN.

The VPN technologies popular among service providers are the border gateway protocol/multiprotocol label switching (BGP/MPLS) VPN. BGP/MPLS VPN is introduced t o solve the scal ability problems in the traditional ATM and Frame Relay VPNs. In addition, the MPLS VPN, a connectionless VPN, is fully compatible with the TCP/IP technologies and the Internet world, which has significantly lower cost of deployment and operations. The BGP/MPLS VPN standard is defined in the IETF RFC 2547bis to provide Layer 3 VPN solutions using BGP to carry route information over a MPLS core. This Layer 3 MPLS-VPN solution achieves all of the security of the Layer 2 approach, while adding enhanced scalability inherent in the use of Layer 3 routing technology.

SOCKS version 5 (SOCKS 5) is a circuit-level proxy protocol that was designed to facilitate authenticated firewall traversal. SOCKS v5 supports a broad range of authentication, encryption, tunneling and key management schemes, as well as a number of features not possible with IPSec, PPTP or other VPN technologies. When SOCKS is used in conjunction with other VPN technologies, it's possible to have a more complete security solution than any individual technology could provide. A user may, for example, incorporate IPSec and SOCKS together. IPSec could be used to secure the underlying network transport, while SOCKS could be used to enforce user-level and application-level access control.

OSI 7 Layers

OSI 7 Layers Reference Model For Network Communication

Open Systems Interconnection (OSI) model is a reference model developed by ISO (International Organization for Standardization) in 1984, as a conceptual framework of standards for communication in the network across different equipment and applications by different vendors. It is now considered the primary architectural model for inter-computing and internetworking communications. Most of the network communication protocols used today have a structure based on the OSI model. The OSI model defines the communications process into 7 layers, which divides the tasks involved with moving information between networked computers into seven smaller, more manageable task groups. A task or group of tasks is then assigned to each of the seven OSI layers. Each layer is reasonably self-contained so that the tasks assigned to each layer can be implemented independently. This enables the solutions offered by one layer to be updated without adversely affecting the other layers.

The OSI 7 layers model has clear characteristics. Layers 7 through 4 deal with end to end communications between data source and destinations. Layers 3 to 1 deal with communications between network devices.

On the other hand, the seven layers of the OSI model can be divided into two groups: upper layers (layers 7, 6 & 5) and lower layers (layers 4, 3, 2, 1). The upper layers of the OSI model deal with application issues and generally are implemented only in software. The highest layer, the application layer, is closest to the end user. The lower layers of the OSI model handle data transport issues. The physical layer and the data link layer are implemented in hardware and software. The lowest layer, the physical layer, is closest to the physical network medium (the wires, for example) and is responsible for placing data on the medium.

The specific description for each layer is as follows:

Layer 7:Application Layer

Defines interface to user processes for communication and data transfer in network

Provides standardized services such as virtual terminal, file and job transfer and operations

Layer 6:Presentation Layer

Masks the differences of data formats between dissimilar systems

Specifies architecture-independent data transfer format

Encodes and decodes data; Encrypts and decrypts data; Compresses and decompresses data

Layer 5:Session Layer

Manages user sessions and dialogues

Controls establishment and termination of logic links between users

Reports upper layer errors

Layer 4:Transport Layer

Manages end-to-end message delivery in network

Provides reliable and sequential packet delivery through error recovery and flow control mechanisms

Provides connectionless oriented packet delivery

Layer 3:Network Layer

Determines how data are transferred between network devices

Routes packets according to unique network device addresses

Provides flow and congestion control to prevent network resource depletion

Layer 2:Data Link Layer

Defines procedures for operating the communication links

Frames packets

Detects and corrects packets transmit errors

Layer 1:Physical Layer

Defines physical means of sending data over network devices

Interfaces between network medium and devices

Defines optical, electrical and mechanical characteristic

The OSI 7 layer model is defined by ISO in document 7498, The protocols defined by ISO based on the OSI 7 layer mode are as follows:

Application

ACSE: Association Control Service Element


CMIP: Common Management Information Protocol


CMIS: Common Management Information Service


CMOT: CMIP over TCP/IP


FTAM: File Transfer Access and Management


ROSE: Remote Operation Service Element


RTSE: Reliable Transfer Service Element Protocol


VTP: ISO Virtual Terminal Protocol


X.400: Message Handling Service (ISO email transmission service) Protocols


X.500: Directory Access Service Protocol (DAP)

Presentation Layer

ISO-PP: OSI Presentation Layer Protocol


ASN.1: Abstract Syntax Notation One

Session Layer

ISO-SP: OSI Session Layer Protocol

Transport Layer

ISO-TP: OSI Transport Protocols: TP0, TP1, TP2, TP3, TP4

Network Layer

ISO-IP: CLNP: Connectionless Network Protocol


CONP: Connection-Oriented Network Protocol


ES-IS: End System to Intermediate System Routing Exchange protocol


IDRP: Inter-Domain Routing Protocol


IS-IS: Intermediate System to Intermediate System

Data Link

HDLC: High Level Data Link Control protocol


LAPB: Link Access Procedure Balanced for X.25

Jumat, 15 Februari 2008

Frame Relay in Brief

Frame-Relay is typically less expensive than point to point circuits because you only pay for the connectivity between your site and the carrier's point of presence (POP). This connection between your site and the carrier's POP is known as the local loop. However, in point to point circuits, you pay for local loops on each end and the mileage between the carrier's POP's. Therefore frame-relay is less expensive over longer distances.

There are several components to a Frame-Relay network. First you must determine the port speed you need at each location. Port speeds start out at 56K or 64K and go up in 64K increments to T1 (1.544 Mbps) or T3 (45 Mbps) speeds. You must then determine how to route your PVC's (Permanent Virtual Circuits) and the CIR (Committed Information Rate) for each PVC. The CIR is the amount of guaranteed throoughput you need. Some carriers will allow you to specify a 0 Kbps CIR, where others require you to specify at least a 2, 4 or 8 Kbps CIR. The CIR can be specified from 0 Kbps all the way up to the port speed. If you have applications such as voice or critical data that need guaranteed bandwidth you will want to specify a high enough CIR to allow these applications the throughput they need to operate properly.

Frame-Relay Network Terminology :
Port Speed - This is the speed of the frame-relay port that you connect to at the carrier's POP. This is also the spped that you transmit and receive data between your router and the Frame-Relay network.


PVC
- PVC stands for Permanent Virtual Circuit. This is a predefined path through the carrier's frame-relay network from one location to another. A majority of frame-relay networks are designed with one cetral site with a single PVC going to each remote site as shown in the diagram below. Other frame-relay networks have PVC's in a mesh configuration to connect all of the sites. Each PVC has a commited information rate (CIR) that guarantees the data throughput on the PVC.

Local Loop - The connection between your site and the carriers POP (Point Of Presence)

CIR - CIR stands for Committed Information Rate. This is the data rate or throughput that is guaranteed by the carrier on each PVC. The CIR on each PVC should be set based on your network throughput requirements. The CIR is ussually some fraction of the port speed but can be as high as the port speed itself.
Note : Some carriers may not allow a 0kbps CIR. The sum of the CIR's for each PVC on a port should not exceed the port speed.

Bursting - Bursting is when you send data over and above the CIR. This data is data that is flagged by the network as discard eligible and will have to be resent if discarded by the network. Your frame-relay carrier can discard these packets if their network is busy or congested. you can only burst or transmit data at speeds up to the port speed. Most frame-relay carriers will provide a guarantee on the percentage of burst traffic that will get through their network. This guarantee can sometimes be 98% or higher.

Carrier POP - The carrier OPO or Point of Presence is where you connect into the communication carriers network. Each carrier usually has one or two POP's in each major city. Many carrier's have what are called remote POP's or virtual POP's in smaller cities that clients can connect into. This connection between your site and the carrier's POP is called the local loop.

Over Subscription - This is when sum of the speed of the PVC's or the CIR's coming into a site exceed the port speed for that site. For example, you have four site A,B,C,D. Site A is the main site, it has a port speed of 256Kbps. You also have sites B,C, adn D with all with port speed of 128 Kbps with PVC's back to site A. You have the potential to send 384kbps to a site that can only accept 256 Kbps of data, this is known as over subscription. Site A will only be able to receive 256 Kbps of data, the rest of the packets will be discarded adn have to be resent. It is common to design Frame-Relay networks with some over-subscription of bandwidth.
Note : Some carriers may not allow over subscription based on the sum of PVC or CIR speeds on a particular port.



Kamis, 14 Februari 2008

TCP/IP Intro

Introduction

In the two decades since their invention, the heterogeneity of networks has expanded further with the deployment of Ethernet, Token Ring, Fiber Distributed Data Interface (FDDI), X.25, Frame Relay, Switched Multimegabit Data Service (SMDS), Integrated Services Digital Network (ISDN), and most recently, Asynchronous Transfer Mode (ATM). The Internet protocols are the best proven approach to internetworking this diverse range of LAN and WAN technologies.

The Internet Protocol suite includes not only lower-level specifications, such as Transmission Control Protocol (TCP) and Internet Protocol (IP), but specifications for such common applications as electronic mail, terminal emulation, and file transfer. Figure 1 shows the TCP/IP protocol suite in relation to the OSI Reference model. Figure 2 shows some of the important Internet protocols and their relationship to the OSI Reference Model. For information on the OSI Reference model and the role of each layer, please refer to the document Internetworking Basics.

The Internet protocols are the most widely implemented multivendor protocol suite in use today. Support for at least part of the Internet Protocol suite is available from virtually every computer vendor.

TCP/IP Technology

This section describes technical aspects of TCP,IP, related protocols, and the environments in which these protocols operate. Because the primary focus of this document is routing (a layer 3 function), the discussion of TCP (a layer 4 protocol) will be relatively brief.

TCP

TCP is a connection-oriented transport protocol that sends data as an unstructured stream of bytes. By using sequence numbers and acknowledgment messages, TCP can provide a sending node with delivery information about packets transmitted to a destination node. Where data has been lost in transit from source to destination, TCP can retransmit the data until either a timeout condition is reached or until successful delivery has been achieved. TCP can also recognize duplicate messages and will discard them appropriately. If the sending computer is transmitting too fast for the receiving computer, TCP can employ flow control mechanisms to slow data transfer. TCP can also communicates delivery information to the upper-layer protocols and applications it supports. All these characteristics makes TCP an end-to-end reliable transport protocol. TCP is specified in RFC 793

Figure 1 – TCP/IP Protocol Suite in Relation to the OSI Reference Model

Figure 2 – Important Internet Protocols in Relation to the OSI Reference Model

Refer to the TCP section of Internet Protocols for more information.

IP

IP is the primary Layer 3 protocol in the Internet suite. In addition to internetwork routing, IP provides error reporting and fragmentation and reassembly of information units called datagrams for transmission over networks with different maximum data unit sizes. IP represents the heart of the Internet Protocol suite.

Note: The term IP in the section refers to IPv4 unless otherwise stated explicitly.

IP addresses are globally unique, 32-bit numbers assigned by the Network Information Center. Globally unique addresses permit IP networks anywhere in the world to communicate with each other.

An IP address is divided into two parts. The first part designates the network address while the second part designates the host address.

The IP address space is divided into different network classes. Class A networks are intended mainly for use with a few very large networks, because they provide only 8 bits for the network address field. Class B networks allocate 16 bits, and Class C networks allocate 24 bits for the network address field. Class C networks only provide 8 bits for the host field, however, so the number of hosts per network may be a limiting factor. In all three cases, the left most bit(s) indicate the network class. IP addresses are written in dotted decimal format; for example, 34.0.0.1. Figure 3 shows the address formats for Class A, B, and C IP networks.

Figure 3 – Address Formats for Class A, B, and C IP Networks

IP networks also can be divided into smaller units called subnetworks or "subnets." Subnets provide extra flexibility for the network administrator. For example, assume that a network has been assigned a Class A address and all the nodes on the network use a Class A address. Further assume that the dotted decimal representation of this network's address is 34.0.0.0. (All zeros in the host field of an address specify the entire network.) The administrator can subdivide the network using subnetting. This is done by "borrowing" bits from the host portion of the address and using them as a subnet field, as depicted in Figure 4.

Figure 4 – "Borrowing" Bits

If the network administrator has chosen to use 8 bits of subnetting, the second octet of a Class A IP address provides the subnet number. In our example, address 34.1.0.0 refers to network 34, subnet 1; address 34.2.0.0 refers to network 34, subnet 2, and so on. The number of bits that can be borrowed for the subnet address varies. To specify how many bits are used to represent the network and the subnet portion of the address, IP provides subnet masks. Subnet masks use the same format and representation technique as IP addresses. Subnet masks have ones in all bits except those that specify the host field. For example, the subnet mask that specifies 8 bits of subnetting for Class A address 34.0.0.0 is 255.255.0.0. The subnet mask that specifies 16 bits of subnetting for Class A address 34.0.0.0 is 255.255.255.0. Both of these subnet masks are pictured in Figure 5, Subnet masks can be passed through a network on demand so that new nodes can learn how many bits of subnetting are being used on their network.

Figure 5 – Subnet Masks



Traditionally, all subnets of the same network number used the same subnet mask. In other words, a network manager would choose an eight-bit mask for all subnets in the network. This strategy is easy to manage for both network administrators and routing protocols. However, this practice wastes address space in some networks. Some subnets have many hosts and some have only a few, but each consumes an entire subnet number. Serial lines are the most extreme example, because each has only two hosts that can be connected via a serial line subnet.

As IP subnets have grown, administrators have looked for ways to use their address space more efficiently. One of the techniques that has resulted is called Variable Length Subnet Masks (VLSM). With VLSM, a network administrator can use a long mask on networks with few hosts and a short mask on subnets with many hosts. However, this technique is more complex than making them all one size, and addresses must be assigned carefully.

Of course in order to use VLSM, a network administrator must use a routing protocol that supports it. Cisco routers support VLSM with Open Shortest Path First (OSPF), Integrated Intermediate System to Intermediate System (Integrated IS-IS), Enhanced Interior Gateway Routing Protocol (Enhanced IGRP), and static routing. Refer to IP Addressing and Subnetting for New Users for more information about IP addressing and subnetting.

On some media, such as IEEE 802 LANs, IP addresses are dynamically discovered through the use of two other members of the Internet protocol suite: Address Resolution Protocol (ARP) and Reverse Address Resolution Protocol (RARP). ARP uses broadcast messages to determine the hardware (MAC layer) address corresponding to a particular network-layer address. ARP is sufficiently generic to allow use of IP with virtually any type of underlying media access mechanism. RARP uses broadcast messages to determine the network-layer address associated with a particular hardware address. RARP is especially important to diskless nodes, for which network-layer addresses usually are unknown at boot time.

Routing in IP Environments

An "internet" is a group of interconnected networks. The Internet, on the other hand, is the collection of networks that permits communication between most research institutions, universities, and many other organizations around the world. Routers within the Internet are organized hierarchically. Some routers are used to move information through one particular group of networks under the same administrative authority and control. (Such an entity is called an autonomous system.) Routers used for information exchange within autonomous systems are called interior routers, and they use a variety of interior gateway protocols (IGPs) to accomplish this end. Routers that move information between autonomous systems are called exterior routers; they use the Exterior Gateway Protocol (EGP) or Border Gateway Protocol (BGP). Figure 6 shows the Internet architecture.

Figure 6 – Representation of the Internet Architecture


Routing protocols used with IP are dynamic in nature. Dynamic routing requires the software in the routing devices to calculate routes. Dynamic routing algorithms adapt to changes in the network and automatically select the best routes. In contrast with dynamic routing, static routing calls for routes to be established by the network administrator. Static routes do not change until the network administrator changes them.

IP routing tables consist of destination address/next hop pairs. This sample routing table from a Cisco router shows that the first entry is interpreted as meaning "to get to network 34.1.0.0 (subnet 1 on network 34), the next stop is the node at address 54.34.23.12":

R6-2500# show ip route
   Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
   D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
   N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
   E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
   i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
   ia - IS-IS inter area, * - candidate default, U - per-user static route
   o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
         34.0.0.0/16 is subnetted, 1 subnets
O               34.1.0.0 [110/65] via 54.34.23.12, 00:00:51, Serial0
   54.0.0.0/24 is subnetted, 1 subnets
C               54.34.23.0 is directly connected, Serial0
R6-2500#

As we have seen, IP routing specifies that IP datagrams travel through an internetwork one router hop at a time. The entire route is not known at the outset of the journey. Instead, at each stop, the next router hop is determined by matching the destination address within the datagram with an entry in the current node's routing table. Each node's involvement in the routing process consists only of forwarding packets based on internal information. IP does not provide for error reporting back to the source when routing anomalies occur. This task is left to another Internet protocol—the Internet Control Message Protocol (ICMP).

ICMP performs a number of tasks within an IP internetwork. In addition to the principal reason for which it was created (reporting routing failures back to the source), ICMP provides a method for testing node reachability across an internet (the ICMP Echo and Reply messages), a method for increasing routing efficiency (the ICMP Redirect message), a method for informing sources that a datagram has exceeded its allocated time to exist within an internet (the ICMP Time Exceeded message), and other helpful messages. All in all, ICMP is an integral part of any IP implementation, particularly those that run in routers. See the Related Information section of this document for more information on ICMP.







Rabu, 13 Februari 2008

Using Dynamips for CCIE LAB

Since the beginning of networking related certification one of the recurring problems that have faced candidates is getting access to hardware to familiarize themselves with how network operating systems work. Traditionally candidates have been limited to hunting for great deals on old or refurbished equipment to buy, renting equipment time from rack rental vendors, using severely limited router simulator programs, or testing configurations on live customer networks and praying that the help desk's phone doesn't ring. Today candidates now have an additional option for creating a Cisco IOS testbed, an emulation program known as "Dynamips".

Started in August of 2005 by Christophe Fillot, Dynamips is a Linux and Windows based application that is used to emulate the hardware of the Cisco 7200 and 3600 series routing platforms. Unlike traditional router "simulators" Dynamips allows you to boot real Cisco IOS software images and build complex network topologies to test the functionality of IOS on your desktop PC. As of November 2006 Dynamips currently supports Ethernet, Serial, ATM, and POS interfaces for the 7200 series routers and Ethernet, Serial, and Etherswitch modules for the 3600 series routers. Best of all Dynamips is open-source and free to download!

To run Dynamips first you must install libpcap or winpcap depending on your platform. Windows users will need to install winpcap 4.0 or later which is currently in beta.

Next download the appropriate Linux or Windows executables for Dynamips. To do this I would recommended to download the Dynagen installer package, a front end written by Greg Anuzelli which uses an INI-like configuration file to provision the Dynamips emulator.

Next you'll need a Cisco IOS software image for a 7206, 3620, 3640, or 3660 router depending on which platform you will be emulating. IOS can be downloaded from http://www.cisco.com for users with a valid service contract. Once you have downloaded the appropriate IOS image it is recommended that you extract the image to save time in the Dynamips booting process. This can be accomplished with programs such as gunzip for Linux or WinRAR for Windows.

Next you need to build a Dynagen .net file to provision the Dynamips emulator, or you can download prebuilt ones to emulate the Internetwork Expert Routing & Switching and Service Provider topologies from here:

Click here to download the Internetwork Expert Topologies for Dynagen

Note that these files may need minor modification to specify your working directories and the names and locations of your Cisco IOS images. Also included in the Internetwork Expert topologies for Dynagen is a router instance that is designated as a Terminal Server (Access Server). This instance can be used like a Cisco 2511 series router to reverse telnet to the console ports of the virtual Dynamips router instances, similar to how the Terminal Server is used in the CCIE Lab Exam.

To use the Terminal Server instance first create a Loopback interface on your PC with the IP address 169.254.0.1/16. For Windows clients see http://support.microsoft.com/kb/839013 for instructions how to add a Loopback interface in Windows. Once the Loopback is created reboot your PC and then run the Dynamips shortcut "Network Device List" located on the desktop. This output will show you the hardware address for the Loopback which will look something like {4065B11C-2A6C-4FD2-8204-A12A9A8328A4}. Next edit the .net file for the appropriate Internetwork Expert topology, and under the [[Router TermServ]] entry edit the line E0/0 = NIO_gen_eth:\Device\NPF_{4065B11C-2A6C-4FD2-8204-A12A9A8328A4} to insert the hardware address of your Loopback. If successful you should be able to ping the IP address of the Terminal Server (169.254.0.2) from your local PC when the Dynamips instance for it is booted.

Next boot the Dynamips hypervisor. For Windows users this will be the "Dynamips Server" shortcut on your desktop that was created by the Dynagen installer package. Next run the appropriate .net file for Dynagen, and "start" your devices from the Dynagen command line. Once booted the Dynamips router processes can be telneted to with any terminal emulation software such as SecureCRT, PuTTY, HyperTerminal, or command line telnet.

Note that as the number of device you boot in Dynamips increases as do the processor, memory, and disk space requirements of your desktop. Currently I am able to boot all the devices in the Internetwork Expert Topology .net files in Windows with an AMD 64 X2 Dual Core 4400+ processor with 2Gb of RAM and about 2Gb of disk space in the devices' working directory.

As the project matures more functionality is sure to be added. For more information on the project visit the following sites:

Dynamips: http://www.ipflow.utc.fr/index.php/Cisco_7200_Simulator
Dynagen: http://dyna-gen.sourceforge.net/
Hacki's Forum: http://7200emu.hacki.at/

Taken from www.internetworkexpert.com

How to be a CCNA

Cisco Certified Networking Associate is a base for starting your career with Cisco.
"This exam tests a candidate's knowledge and skills required to install, operate, and troubleshoot a small to medium size enterprise branch network"

The following are the topics covered in 640-802
  • Building a Simple Network
  • Ethernet Local Area Networks
  • Wireless Local Area Networks
  • Exploring the Functions of Routing
  • Wide Area Networks
  • Network Environment Management
A.How to start preparing

You might consider to have the following to ensure a smooth self study
  • Study Guides (Todd Lammele's CCNA Study Guide or a Cisco Press 640-802 Study Guide)
  • CBT for a better understanding of concepts (CCNA Video Mentor for 640-802 or/and CBT Nuggets)
  • A Simulator or Emulator to train in a virtual device (Boson/Dynamips)
  • Dumps for virtual tests(Testinside/P4S/Testking)
Mentioned above are those people have been using for quite sometime and found to be worthy enough. Alright, now that you have gathered the materials required, lets move on to the next step..

B. Course of Action
    1. Read one topic at a time. Try to understand completely.
    2. It is good to relate topics to what you have learned. The more you to try to relate, you discover new concepts. That will help you to understand newer topics easily
    3. Try simulating the concepts learned. Only then, new doubts arise and more clarity sought.
    4. Passing the exam will just make you yet another paper certified associate. You need to have the knowledge to work with your certification.
    5. Learning is a never ending process. Never lose hope if you don't understand/ get the right way in the first attempt. We are always there to help you out.
    6.After completing your subject, sit down and work out the virtual tests. Try the latest dumps and browse forums to find out what people have experienced.
C.Cisco Exam policies
    Registering for exams
    Gather information required for exam registration
    Pearson Vue is the Cisco authorized test delivery partner. You can register online, by telephone, or by walk in (where available).
http://www.cisco.com/web/learning/le3/le11/learning_about_registering_for_exams.html
    The D Day
    Be aware of the code of conduct required at the Testing Centre
    Read the questions thoroughly before answering them
    Manage your time and do not miss out on the simulations. They contribute to a good score.
    Retaking the exam
    Candidates may only take a beta exam once.
    Candidates who fail an exam must wait a period of five (5) calendar days, beginning the day after the failed attempt, before they may retest for the same exam.
    Once passed, a candidate must wait a minimum of 180 days before taking the same exam with an identical exam number.
    Candidates who violate these policies are in violation of the agreement.
The cost of CCNA exam is USD 150. Your Cert is valid for three years and you may choose to do a CC*P or continue to have CCNA be taking a recertification

Good luck
*thanks to the dirizhor*

CCNP TV Invitation

CCNP TV: BCMSN - Implementing Multiple Spanning Tree Protocol, February 28, 2007

Join more than 40,000 CCNP Prep Center users for an hour long monthly online TV talk show.

Sign up now: Attendance space is limited, so visit www.cisco.com/go/prep-ccnp and click “Register Now” under the Prep Center TV heading to reserve your space today.

Date: Thursday, February 28, 2007
Time: 11 a.m. Eastern Time, 8 a.m. Pacific Time, and 16:00 GMT
Title: Multiple Spanning Tree Protocol

The program will focus on the following objectives and is designed to provide information that will assist in passing the Cisco Certified Network Professional exam. After the presentation, we’ll be taking live calls from the audience during the Q&A session. You may also submit questions electronically.

Objectives:

During the show, Cisco Experts will discuss:

  • Motivation behind 802.1s MSTP
  • Comparison of MSTP Instances to PVST
  • MST Region, what is it? What needs to Match?
  • MST BPDUs and MRecords
  • MST and CST interaction
  • MST configurationss
  • MST verification

To learn more, visit the www.cisco.com/go/prep-ccnp page.