Wednesday, December 31, 2008

MPLS Ebooks

MPLS Fundamentals


Download Link:

Selecting MPLS VPN Services

Selecting MPLS VPN Services helps you analyze migration options, anticipate migration issues, and properly deploy IP/MPLS VPNs. Detailed configurations illustrate effective deployment while case studies present available migration options and walk you through the process of selecting the best option for your network.

Selecting MPLS VPN Services By Chris Lewis and Steve Pickavance




Download Link
MPLS and VPN Architectures, Volume II

MPLS and VPN Architectures, Volume II, begins with a brief refresher of the MPLS VPN Architecture. Part II describes advanced MPLS VPN connectivity including the integration of service provider access technologies (dial, DSL, cable, Ethernet) and a variety of routing protocols (IS-IS, EIGRP, and OSPF), arming the reader with the knowledge of how to integrate these features into the VPN backbone.

By Ivan Pepelnjak, Jim Guichard, and Jeff Apcar


Download Link
MPLS and Next-Generation Networks: Foundations for NGN and Enterprise Virtualization

Understand the business case for deploying MPLS-based services and solutions
  • Provides network managers and architects a precise MPLS primer
  • Defines MPLS service problems and their associated solutions
  • Includes ROI models for MPLS-based solutions
  • Discusses pros and cons of various options for each MPLS service
By Azhar Sayeed and Monique J. Morrow

Download Link

MPLS Dumps & Labs

Download Link:

MPLS Actual Test updated on 06/10/08




Download Link:

MPLS

MPLS Overview:
Multi-Protocol Label Switching (MPLS) defines a mechanism for packet forwarding in network routers. It was originally developed to provide faster packet forwarding than traditional IP routing, although improvements in router hardware have reduced the importance of speed in packet fowarding. However, the flexibility of MPLS has led to it becoming the default way for modern networks to achieve Quality of Service (QoS), next generation VPN services, and optical signaling.

Traditional IP networks are connectionless: when a packet is received, the router determines the next hop using the destination IP address on the packet alongside information from its own forwarding table. The router's forwarding tables contain information on the network topology. They use an IP routing protocol, such as OSPF, IS-IS, BGP, RIP or static configuration, to keep their information synchronized with changes in the network.

MPLS also uses IP addresses, either v4 or v6, to identify end points and intermediate switches and routers. This makes MPLS networks IP-compatible and easily integrated with traditional IP networks. However, unlike traditional IP, MPLS flows are connection-oriented and packets are routed along pre-configured Label Switched Paths (LSPs).

How does MPLS work?
MPLS works by tagging packets with an identifier (a label) to distinguish the LSPs. When a packet is received, the router uses this label (and sometimes also the link over which it was received) to identify the LSP. It then looks up the LSP in its own forwarding table to determine the best link over which to forward the packet, and the label to use on this next hop.
A different label is used for each hop, and it is chosen by the router or switch performing the forwarding operation. This allows the use of very fast and simple forwarding engines, as the router can select the label to minimize processing.

Ingress routers at the edge of the MPLS network use the packet's destination address to determine which LSP to use. Inside the network, the MPLS routers use only the LSP labels to forward the packet to the egress router.

In the diagram above, LSR (Label Switched Router) A uses the destination IP address on each packet to select the LSP, which determines the next hop and initial label for each packet (21 and 17). When LSR B receives the packets, it uses these labels to identify the LSPs, from which it determines the next hops (LSRs D and C) and labels (47 and 11). The egress routers (LSRs D and C) strip off the final label and route the packet out of the network.

As MPLS uses only the label to forward packets, it is protocol-independent, hence the term "Multi-Protocol" in MPLS. Packet forwarding has been defined for all types of layer-2 link technologies, with a different label encoding used in each case.

MPLS Protocols

MPLS defines only the forwarding mechanism; it uses other protocols to establish the LSPs. Two separate protocols are needed to perform this task: a routing protocol and a signaling protocol.

MPLS Routing Protocols:

The routing protocol distributes network topology information through the network so that the LSP can be calculated. An interior gateway protocol, such as OSPF or IS-IS, is normally used, as MPLS networks typically cover a single administrative domain.

However, these routing protocols only distribute network topology. When traffic engineering is required to establish LSPs with guaranteed QoS characteristics and backup LSPs that avoid any single point of failure, the traffic engineering (TE) extensions to these protocols are used. These extensions distribute QoS and Shared Risk Link Groups (SRLGs) information on each link in the network. This information enables the route calculator to determine routes through the network with guaranteed QoS parameters, and backup LSPs that traverse different links from the primary path.

Mechanisms to extend this traffic engineering to inter-area and inter-carrier routing are still being agreed. Our White Paper on "Inter-Area Routing, Path Selection and Traffic Engineering" provides a detailed discussion of this topic.

MPLS Signaling Protocols
The signaling protocol informs the switches along the route which labels and links to use for each LSP. This information is used to program the switching fabric. One of two main signaling protocols is used, depending on the network requirements.
  • RSVP-TE is used where traffic engineering is required. LDP is used when traffic engineering is not required, as it needs less management.

BGP is also used as a combined routing and MPLS signaling protocol in some situations. An example of this is BGP/MPLS VPNs.


Advanced MPLS Applications:

Optical MPLS

The concept of a label has been extended in Generalized MPLS (GMPLS). In GMPLS, the label no longer needs to be carried as an identifier on the data flow, but may be implicit. For example, time-slots (in SONET/SDH) and wavelengths (in DWDM) can be labels. In these cases, the label switching operations translate to operations such as "switch this incoming wavelength onto this outgoing wavelength."


GMPLS is therefore ideal for optical networking, and many extensions to the protocols have been defined, including user-to-network interfaces and network-to-network interfaces.


MPLS in Hierarchical Networks


MPLS is ideal for hierarchical networks, where lower-layer switching entities (for example packets) are aggregated into a higher-layer entity, for example a time-slot, and then once again into a wavelength and a whole fiber. MPLS allows a label stack to be defined so that switches can switch higher-layer aggregations and ignore the lower levels of the label stack. When the flow arrives at a switch capable of handling lower-layer entities, the switch strips off the outer label and examines the next lower level in the stack.


One example of the use of label stacking is in BGP/MPLS VPNs, where a two-deep label stack is used.

A transport label is used to route aggregated VPN traffic to the destination edge router in the provider's network. This is conventional MPLS, using either RSVP-TE or LDP signaling.

Once at the destination edge router, the transport label is stripped off and the second label examined. This label identifies the specific VPN to which the flow belongs. These VPN labels are signaled in extensions to the BGP protocol.

Tuesday, December 30, 2008

CCNA 640-802 Dumps

Pass4sure Practice Exams for Cisco CCNA 640-802 are written to the highest standards of technical accuracy, using only certified subject matter experts and published authors for development.

You can pass the CCNA 640-802 certification exam by using the dumps listed below...................Please keep in mind practice makes man perfect (Labs should be practiced before taking the exams).

Pass4Sure Solutions:

Pass4Sure 640-802 version 3.22 Q-402

Pass4Sure 640-802 V 3.22 (Doubtful Question Explanation)

Pass4Sure 640-802 version 3.20 Q-394

Pass4Sure 640-802 Version 3.15 Q-347

Pass4Sure 640-802 Version 3.10 Q-254

Pass4Sure 640-802 Version 2.95 Q-254

Pass4Sure 640-802 Version 2.93 Q-254

If you have any type of missing main class error, follow the link and download JRE.

Enjoy

Cisco Router Password Recovery Procedure

Step-by-Step Procedure:

-----------------------------------
Attach a terminal or PC with terminal emulation to the console port of the router. Use the following terminal settings:
9600 baud rate No parity 8 data bits 1 stop bit No flow control
Type show version and record the setting of the configuration register. Click here to see output of a show version command.
The configuration register setting is usually 0x2102 or 0x102.
Using the switch, turn off the router and then turn it on.
Press Break on the terminal keyboard within 60 seconds of the powerup to put the router into ROMMON.
If the break sequence doesn't work, try CTRL+BREAK or use the terminal program to send the break as an ascii code.
Type o/r 0x2142 at the > prompt to boot from Flash without loading the configuration.
Type i at the > prompt.
The router reboots but ignores its saved configuration.
Type no after each setup question or press Ctrl-C to skip the initial setup procedure.
Type enable at the Router> prompt.
You'll be in enable mode and see the Router# prompt.
Important Type config mem or copy start running to copy the nonvolatile RAM (NVRAM) into memory. Do not type config term.
Type wr term or show running.
The show running and wr term commands show the configuration of the router. In this configuration you see under all the interfaces the shutdown command, which means all interfaces are currently shutdown. Also, you can see the passwords either in encrypted or unencrypted format.
Type config term and make the changes.
The prompt is now hostname(config)#.
Type enable secret .
Issue the no shutdown command on every interface that is used. If you issue a show ip interface brief command, every interface that you want to use should be "up up".
Type config-register 0x2102, or the value you recorded in step 2.
Press Ctrl-z to leave the configuration mode.
The prompt is now hostname#.
Type write mem or copy running startup to commit the changes.
Example of Password Recovery on a Cisco 2500
The example shown here is password recovery on a Cisco 2500.
Router>en
Password:
Password:
Password:
% Bad secrets
Router>show version
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JS-L), Version 12.0(7)T, RELEASE SOFTWARE (fc2)
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Mon 06-Dec-99 17:10 by phanguye
Image text-base: 0x0306C4E0, data-base: 0x00001000
ROM: System Bootstrap, Version 5.2(8a), RELEASE SOFTWARE
BOOTFLASH: 3000 Bootstrap Software (IGS-RXBOOT), Version 10.2(8a), RELEASE SOFTWARE (fc1)
Router uptime is 5 minutes
System returned to ROM by power-on
System image file is "flash:/c2500-js-l.120-7.T"
cisco 2500 (68030) processor (revision D) with 8192K/2048K bytes of memory.
Processor board ID 02315272, with hardware revision 00000000
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
1 Ethernet/IEEE 802.3 interface(s)
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read ONLY)
Configuration register is 0x2102
Router>
!--- The router was just powercycled and during bootup a
!--- break sequence was sent to the router.
!
Abort at 0x10EA83C (PC)
>o/r 0x2142
>i
System Bootstrap, Version 5.2(8a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
2500 processor with 8192 Kbytes of main memory
F3: 13626872+197596+780568 at 0x3000060
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JS-L), Version 12.0(7)T, RELEASE SOFTWARE (fc2)
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Mon 06-Dec-99 17:10 by phanguye
Image text-base: 0x0306C4E0, data-base: 0x00001000
cisco 2500 (68030) processor (revision D) with 8192K/2048K bytes of memory.
Processor board ID 02315272, with hardware revision 00000000
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
1 Ethernet/IEEE 802.3 interface(s)
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read ONLY)
--- System Configuration Dialog ---
Would you like to enter the initial configuration dialog? [yes/no]:
!--- Ctrl-C pressed
!
Press RETURN to get started!
00:00:08: %LINK-3-UPDOWN: Interface Ethernet0, changed state to up
00:00:08: %LINK-3-UPDOWN: Interface Serial0, changed state to up
00:00:08: %LINK-3-UPDOWN: Interface Serial1, changed state to up
00:00:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:00:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:01:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed state to up
00:01:29: %LINK-3-UPDOWN: Interface Ethernet0Translating "Router"...domain server (255.255.255.255)
, changed state to up
00:01:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:01:31: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JS-L), Version 12.0(7)T, RELEASE SOFTWARE (fc2)
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Mon 06-Dec-99 17:10 by phanguye
00:01:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:01:33: %LINK-5-CHANGED: Interface Ethernet0, changed state to administratively down
00:01:33: %LINK-5-CHANGED: Interface Serial0, changed state to administratively down
00:01:33: %LINK-5-CHANGED: Interface Serial1, changed state to administratively down
00:01:33: %LINK-5-CHANGED: Interface TokenRing0, changed state to administratively down
00:01:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed state to down
00:01:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:01:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface TokenRing0, changed state to down
Router>en
Router#copy start run
Destination filename [running-config]?
1278 bytes copied in 10.448 secs (127 bytes/sec)
Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#enable secret Cisco
Router(config)#int e0
Router(config-if)#no shut
*Mar 1 00:04:12.863: %LINK-3-UPDOWN: Interface Ethernet0, changed state to up
*Mar 1 00:04:13.947: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed state to up
Router(config-if)#int s0
Router(config-if)#no shut
*Mar 1 00:04:18.107: %LINK-3-UPDOWN: Interface Serial0, changed state to up
*Mar 1 00:04:19.167: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
Router(config-if)#int s1
Router(config-if)#no shut
Router(config-if)#
*Mar 1 00:04:27.055: %LINK-3-UPDOWN: Interface Serial1, changed state to up
*Mar 1 00:04:28.071: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
Router(config-if)#exit
Router(config)#config-register 0x2102
Router(config)#^Z
Router#wr mem
*Mar 1 00:05:09.035: %SYS-5-CONFIG_I: Configured from console by console
Building configuration...
[OK]
Router#
Router#
Disclaimer: The customer acknowledges that the examples provided in this document are solely for illustrative purposes. Further, the customer both understands and agrees that the information in the examples may need to be modified to assure proper functioning on his/her own computer system(s).
Verio is not liable for any negative consequences arising from the improper use or modification of the provided examples.

Wednesday, December 17, 2008

CCDA Study Material

CCDA Certification:

Cisco Certified Design Associate (CCDA®) indicates a foundation level knowledge of network design for Cisco converged networks. CCDA certified professionals can design routed and switched network infrastructures and services involving LAN, WAN, and broadband access for businesses and organizations.


Download Link:

CCDA Study Material


(thanks)

CIPT Dumps

Exam: 642-446
Title: Implementing Cisco Unified Communications Manager Part 1 CIPT-1 V6.0
Actual Test Updated on: 15-10-2008

Exam: 642-456
Title: Implementing Cisco Unified Communications Manager Part 2 CIPT-1 V6.0
Actual Test Updated on: 21-07-2008

Download Links:

CIPT Part1

CIPT Part2

Friday, December 12, 2008

CCNA LABs

Pass4Sure CCNA 640-802 Preparation LABs:

Download link:

P4S CCNA Preparation Labs

EIGRP (New):

After adding RTR_2 router, no routing updates are being exchanged between RTR_1 and the new location. All other inter connectivity and internet access for the existing locations of the company are working properly.

The task is to identify the fault(s) and correct the router configuration to provide full connectivity between the routers.
Access to the router CLI can be gained by clicking on the appropriate host.
All passwords on all routers are cisco.

IP addresses are listed in the chart below.


Solution to the Simulation:
Check the running configuration of all the routers and routing protocol information and note the anomalies where sighted/found ......
RTR_A#show run
!
interface FastEthernet0/0
ip address 192.168.60.97 255.255.255.240
!
interface FastEthernet0/1
ip address 192.168.60.113 255.255.255.240
!
interface Serial0/0
ip address 192.168.36.14 255.255.255.252
clockrate 64000
!
router eigrp 212
network 192.168.36.0
network 192.168.60.0
no auto-summary
!
RTR_A#show ip route
!
192.168.36.0/30 is subnetted, 1 subnets
C 192.168.36.12 is directly connected, Serial 0/0
192.168.60.0/24 is variably subnetted, 5 subnets, 2 masks
C 192.168.60.96/28 is directly connected, FastEthernet0/0
C 192.168.60.112/28 is directly connected, FastEthernet0/1
D 192.168.60.128/28 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/0
D 192.168.60.144/28 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/0
D 192.168.60.24/30 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/0
D* 198.0.18.0 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/0
!
--------------------
RTR_2#show run
!
!
interface FastEthernet0/0
ip address 192.168.77.34 255.255.255.252
!
interface FastEthernet0/1
ip address 192.168.60.65 255.255.255.240
!
interface FastEthernet1/0
ip address 192.168.60.81 255.255.255.240
!
!
router eigrp 22
network 192.168.77.0
network 192.168.60.0
no auto-summary
!
RTR_2#show ip route
!
192.168.60.0/28 is variably subnetted, 2 subnets
C 192.168.60.80 is directly connected, FastEthernet1/0
C 192.168.60.64 is directly connected, FastEthernet0/1
192.168.77.0/30 is subnetted, 1 subnets
C 192.168.77.32 is directly connected, FastEthernet0/0
!
----------------------
RTR_B#show run
!
interface FastEthernet0/0
ip address 192.168.60.129 255.255.255.240
!
interface FastEthernet0/1
ip address 192.168.60.145 255.255.255.240
!
interface Serial0/1
ip address 192.168.60.26 255.255.255.252
!
router eigrp 212
network 192.168.60.0
!
RTR_B#show ip route
!
192.168.60.0/24 is variably subnetted, 5 subnets, 2 masks
C 192.168.60.24/30 is directly connected, Serial0/1
C 192.168.60.128/28 is directly connected, FastEthernet0/0
C 192.168.60.144/28 is directly connected, FastEthernet0/1
D 192.168.60.96/28 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1
D 192.168.60.112/28 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1
192.168.36.0/30 is subnetted, 1 subnets
D 192.168.36.12 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1
D* 198.0.18.0 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1
!
--------------------
RTR_1#show run
!
!
interface FastEthernet0/0
ip address 192.168.77.33 255.255.255.252
!
interface Serial1/0
ip address 198.0.18.6 255.255.255.0
!
!
interface Serial0/0
ip address 192.168.36.13 255.255.255.252
clockrate 64000
!
interface Serial0/1
ip address 192.168.60.25 255.255.255.252
clockrate 64000
!
!
router eigrp 212
network 192.168.36.0
network 192.168.60.0
network 192.168.85.0
network 198.0.18.0
no auto-summary
!
ip classless
ip default-network 198.0.18.0
ip route 0.0.0.0 0.0.0.0 198.0.18.5
ip http server
RTR_1#show ip route
!
192.168.36.0/30 is subnetted, 1 subnets
C 192.168.36.12 is directly connected, Serial 0/0
192.168.60.0/24 is variably subnetted, 5 subnets, 2 masks
C 192.168.60.24/30 is directly connected, Serial0/1
D 192.168.60.128/28 [ 90/21026560 ] via 192.168.60.26, 00:00:57, Serial 0/1
D 192.168.60.144/28 [ 90/21026560 ] via 192.168.60.26, 00:00:57, Serial 0/1
D 192.168.60.96/28 [ 90/21026560 ] via 192.168.36.14, 00:00:57, Serial 0/0
192.168.77.0/30 is subnetted, 1 subnets
C 192.168.77.32 is directly connected, FastEthernet0/0
C 192.0.18.0/24 is directly connected, Serial 1/0
*S 0.0.0.0 via 198.0.18.5
!
---------------
Explanation, Fault Identification and Correction
Step1: Simulation understanding
Identify the faults in configuration on RTR_1 and RTR_2.
As the SIM specifies all other inter connectivity and internet access for the existing locations of the company are working properly.
Routing Protocols used in the SIM is EIGRP with AS 212 as provided by exhibit.
Faults Identified:
  1. Wrong AS (EIGRP 22) provided at RTR_2 (New router),
  2. RTR_1 does not advertise the new network between RTR_1 and RTR_2 into EIGRP.
We need to correct the above two configuration mistakes to have full connectivity
Correction:
Step2:
Correcting the EIGRP AS to 212 & Advertise the routes
Wrong AS (EIGRP 22) provided at RTR_2 (New router). All routers that want to exchange routes within EIGRP needs to be in same Autonomous System.
First we need to remove the current wrong EIGRP AS 22 from Router RTR_2
Click on Host-F to get CLI of RTR_2
RTR_2>enable
Password : cisco (Provided in the simulation)
RTR_2#conf t
RTR_2(conf)#
Removing the wrong EIGRP routing process with AS 22
RTR_2(conf)#no router eigrp 22
The above statement removes all the EIGRP configuration configured for AS 22
Adding the correct EIGRP configuration. Start the EIGRP routing process with AS 212
RTR_2(conf)#router eigrp 212
Advertise the directly connected networks into EIGRP on RTR_2
Fa 0/0 - 192.168.77.34
Fa 1/0 - 192.168.60.81
Fa 0/1 - 192.168.60.65

RTR_2(config-router)#network 192.168.60.0
RTR_2(config-router)#network 192.168.77.0
RTR_2(config-router)#no auto-summary
RTR_2(config-router)#end
Note: Necessary step, save the changes made to router RTR_2
RTR_2#copy run start
Step 3:
RTR_1 does not advertise the new network between RTR_1 and RTR_2 into EIGRP.
Click on Host-G to get CLI of RTR_1
The network 192.168.77.0 is used between RTR_1 Fa0/0 - RTR_2 Fa 0/0.
This network needs to be advertise into EIGRP routing process at RTR_1
RTR_1>enable
Password : cisco (Provided in simulation)
RTR_1#conf t
RTR_1(conf)#
Enter EIGRP routing process for AS 212
RTR_1(conf)#router eigrp 212
The network 192.168.77.0 is used between RTR_1 Fa0/0 - RTR_2 Fa 0/0 .
Advertise this network into EIGRP
RTR_1(config-router)#network 192.168.77.0
RTR_1(config-router)#end
Important save the changes made to router
RTR_1RTR_1#copy run start
From RTR_2 CLI ping RTR_1 Serial 1/0 IP address 198.0.18.6
RTR_2#ping 198.0.18.6
!!!!!
A successful ping shows the new RTR_2 will have full connectivity with other routers.
(Thanks)

Saturday, December 6, 2008

CCNP Labs

The following LABs are for your practice, make sure you have done all the labs before appearing in the certification online exams.

Download Links
-----------------------
BSCI LABs

BCMSN LABs

ISCW LABs

ONT LABs

--------------------------
(thanks)

Wednesday, December 3, 2008

CCNA 640-802 Study Material

Associate

The first step in general Cisco Career Certifications begins either with CCENT as an interim step to Associate level, or directly with CCNA for network operations or CCDA for network design. Think of the Associate level as the apprentice or foundation level of networking certification.


CCENT
CCNA
CCDA
CCNA Voice
CCNA Wireless
CCNA Security


Study Material

ICND1 (640-822)
ICND2 (640-816)
CCNA Portable Command Guide 2008
CCNA 640-802: Sybex Study Guide 6th Edition

Monday, December 1, 2008

CCNP CBTs



CBT Nuggets Exam-Pack: 642-901 BSCI (Building Scalable Cisco Internetworks) :

The BSCI series, at its core, is all about routing. You'll immerse yourself in the features and functionalities of Cisco routers. This includes deploying, managing, and optimizing the performance of Cisco routers. Major topics in this series include EIGRP, OSPF, IS-IS, Advanced Routing, BGP, Multicast, and IPv6.

Download Links

Bsci.part1.rar





CBT Nuggets Exam-Pack: 642-812 BCMSN (Building Converged Cisco Multilayer Switched Networks)


BCMSN is all about deploying, managing, and optimizing Cisco switches. You'll learn the role of switches in your Cisco network, including smart network design for today's networking needs. Major topics in this series include VLANs, STP, Ether Channel, Layer 3 Switching, Redundancy, Wireless LANs, Campus VoIP, and Campus Security.


Download Links


CBT Nuggets Exam-Pack: 642-825 ISCW (Implementing Secure Converged Wide Area Networks)

In the ISCW series you'll learn how to create and manage secure, robust remote access solutions. In today's world of frequent telecommuting and distant offices throughout the globe, this topic is getting bigger than ever. Major topics you'll learn include understanding WAN technologies, Multiprotocol Label Switching, configuring IPSec VPNs, and securing your network.
Download Links

CBT Nuggets Exam-Pack: 642-845 ONT (Optimizing Converged Cisco Networks)

The ONT series covers how to configure your network to support rich media traffic including Voice over IP and video conferencing. The throughput and quality of service required for these technologies is higher than normal data traffic, and requires these advanced skills. Major topics in this series include understanding and implementing VoIP technologies, managing Quality of Service, and the special considerations for supporting convergence technologies on wireless networks.

Download Links
(thank)