sikandar CCIE: 2013

Sunday, December 15, 2013

IPV6 Video Trainings (playlist)

Wednesday, October 23, 2013

Metro Ethernet

METROETHERNET

A metropolitan-area Ethernet, Ethernet MAN, or metro Ethernet network is a metropolitan area network (MAN) that is based on Ethernetstandards.

It is commonly used to connect subscribers to a larger service network or the Internet.

Businesses can also use metropolitan-area Ethernet to connect their own offices to each other.

Advantages

· An Ethernet interface is much less expensive

· Ethernet also supports high bandwidths with fine granularity

· Ethernet-based access network is that it can be easily connected to the customer network, due to the prevalent use of Ethernet in corporate and, more recently, residential networks.

ME 3400 ,catalyst 3750 , ME3800X, ME 4900,

Metro Ethernet (ME) Classification

1. Point-to-point (PtP)

a. A single point-to-point Ethernet circuit provisioned between two User Network Interfaces (UNIs).

b. Also referred as Ethernet Line Service Type (E-Line)

2. Multipoint-to-multipoint (MPtMP)

a. A single multipoint-to-multipoint Ethernet circuit provisioned between two or more UNIs.

b. Also referred as Ethernet LAN Service Type (E-LAN)

Within these two service types, Metro Ethernet services can be created by assigning values to a set of attributes grouped according to the following:

} User Node Interface (UNI)

} Network Node Interface (NNI)

} Ethernet virtual connection (EVC)

Ethernet virtual connection (EVC)

Association of two or more UNIs that limits the exchange of service frames to UNIs within the EVC.

User Node Interface (UNI)

By default, UNI interface is in shutdown status, this you can use for access ports and all UNI interfaces even they are in the same VLAN but cannot access with each other.

Network Node Interface (UNI)

By default, NNI interface is in no shutdown status.
NNI port you can use for trunk ports, It use to connect two switches.
NNI can communicate with UNI, NNI can communicate with NNI too.

Tuesday, October 22, 2013

CCNAx 200-120 Routing and Switching Self Paced video Training includes everything you will need to fully prepare for your CCNA R/S certification

The new CCNA 200-120 exam already replaced the old CCNA 640-802 exam from October 2013 .
In this course you will get introduced to Cisco world of networking with complete new CCNAx 2.0 (200-120)
trained by expert dual CCIE certified with 10 + years of training and working experience in production networks.

The New CCNAx v 2.0 updates includes

Troubleshooting Routing
Troubleshooting Switching
IPv6 Routing
DHCP
Introduction to WAN technologies like VSAT,MPLS,VPN,Metro Ethernet,
HSRP,VRRP, GLBP
external Authentication methods
updated software on Cisco routers and switches.

Start with very basic network understanding of all technologies and further getting in to more depth as per new CCNAx v 2.0 (200-120) Syllabus

Learn at your own pace.
downloadable full vidoes any time
No monthly charges
full access to all videos any time online on udemy.com.

New CCNAx 200-120 Self Paced Video training now available on

https://www.udemy.com/newccnax-200-120

The Discount Code for Free subscription for my CCNAx 200-120 course has already reached its limit in short time

So you can avail for just 10$ (60% discount )

https://www.udemy.com/newccnax-200-120/?couponCode=sikandar

Clicking on the above link which takes you to my Course on udemy page where should see the course for Just 10$

Saturday, June 29, 2013

CCNA RS video Training

Downloadable files for CCNA RS video Training which i uploaded on 4shared...

http://www.4shared.com/folder/l_XWPcNG/CCNA_CCNP_sikandar_videos.html

Saturday, June 22, 2013

EIGRP LAB : BASIC EIGRP PROCESS

VERIFYING EIGRP PROCESS

R1#sh ip int brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 10.1.1.1 YES NVRAM up up

Serial1/0 1.1.1.1 YES NVRAM up up

R1#

R2#sh ip int b

Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 20.1.1.1 YES NVRAM up up

Serial1/0 1.1.1.2 YES NVRAM up up

R1#ping 1.1.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 28/76/140 ms

R1#

R1#debug eigrp packets

EIGRP Packets debugging is on

(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK, STUB, SIAQUERY, SIAREPLY)

R1(config)# router eigrp 100

R1(config-router)# network 10.0.0.0

R1(config-router)# network 1.0.0.0

R1(config-router)# end

R1#

*Mar 1 00:03:29.179: EIGRP: Sending HELLO on FastEthernet0/0

*Mar 1 00:03:29.183: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:03:30.075: EIGRP: Sending HELLO on Serial1/0

*Mar 1 00:03:30.075: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:03:33.651: EIGRP: Sending HELLO on FastEthernet0/0

*Mar 1 00:03:33.655: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:03:34.671: EIGRP: Sending HELLO on Serial1/0

*Mar 1 00:03:34.671: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:03:38.235: EIGRP: Sending HELLO on FastEthernet0/0

*Mar 1 00:03:38.235: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:03:39.295: EIGRP: Sending HELLO on Serial1/0

*Mar 1 00:03:39.299: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

The hello packets are unanswered by the other routers because EIGRP is not yet running on R2

R1#sh ip eigrp interfaces

IP-EIGRP interfaces for process 100

Xmit Queue Mean Pacing Time Multicast Pending

Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes

Fa0/0 0 0/0 0 0/1 0 0

Se1/0 0 0/0 0 0/15 347 0

R2#debug eigrp packets

EIGRP Packets debugging is on

(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK, STUB, SIAQUERY, SIAREPLY)

R2#

R2(config)#router eigrp 100

R2(config-router)#network 20.0.0.0

R2(config-router)#network 1.0.0.0

R2(config-router)#end

*Mar 1 00:14:15.375: EIGRP: Sending HELLO on FastEthernet0/0

*Mar 1 00:14:15.375: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:14:15.487: EIGRP: Sending HELLO on Serial1/0

*Mar 1 00:14:15.491: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:14:15.611: EIGRP: Received HELLO on Serial1/0 nbr 1.1.1.1

*Mar 1 00:14:15.615: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0

*Mar 1 00:14:15.619: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 1.1.1.1 (Serial1/0) is up: new adjacency

*Mar 1 00:14:15.623: EIGRP: Enqueueing UPDATE on Serial1/0 nbr 1.1.1.1 iidbQ un/rely 0/1 peerQ un/rely 0/0

*Mar 1 00:14:15.627: EIGRP: Received UPDATE on Serial1/0 nbr 1.1.1.1

*Mar 1 00:14:15.631: AS 100, Flags 0x1, Seq 5/0 idbQ 0/0 iidbQ un/rely 0/1 peerQ un/rely 0/0

*Mar 1 00:14:15.635: EIGRP: Requeued unicast on Serial1/0

*Mar 1 00:14:15.635: EIGRP: Enqueueing UPDATE on Serial1/0 iidbQ un/rely 0/1 serno 1-2

*Mar 1 00:14:15.639: EIGRP: Forcing multicast xmit on Serial1/0

*Mar 1 00:14:15.643: EIGRP: Enqueueing UPDATE on Serial1/0 nbr 1.1.1.1 iidbQ un/rely 0/0 peerQ un/rely 0/1 serno 1-2

*Mar 1 00:14:15.655: EIGRP: Sending HELLO on Serial1/0

*Mar 1 00:14:15.655: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

*Mar 1 00:14:15.663: EIGRP: Sending UPDATE on Serial1/0 nbr 1.1.1.1

*Mar 1 00:14:15.663: AS 100, Flags 0x1, Seq 1/5 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/2

*Mar 1 00:14:15.771: EIGRP: Received UPDATE on Serial1/0 nbr 1.1.1.1

*Mar 1 00:14:15.775: AS 100, Flags 0x8, Seq 6/1 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/2

*Mar 1 00:14:15.779: EIGRP: Enqueueing ACK on Serial1/0 nbr 1.1.1.1

*Mar 1 00:14:15.783: Ack seq 6 iidbQ un/rely 0/1 peerQ un/rely 1/1

*Mar 1 00:14:15.791: EIGRP: Suppressed ACK 6 to 1.1.1.1 on Serial1/0

*Mar 1 00:14:15.795: EIGRP: Sending UPDATE on Serial1/0 nbr 1.1.1.1

*Mar 1 00:14:15.795: AS 100, Flags 0x8, Seq 2/6 idbQ 0/0 iidbQ un/rely 0/1 peerQ un/rely 0/1 serno

R2#undebug all

The debug output displays the EIGRP hello, update, and ACK packets. Because EIGRP uses Reliable Transport Protocol (RTP) for update packets, you see routers replying to update packets with the ACK packet. You can turn off debugging with the undebug allcommand.

R2#sh ip eigrp neighbors

IP-EIGRP neighbors for process 100

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 1.1.1.1 Se1/0 12 00:09:24 101 909 0 7

Note:

In the output, the “H” column on the left lists the order in which a peering session was established with the specified neighbor. The order uses sequential numbering, starting with 0. The “H” stands for “handle,” which is an internal number used by the EIGRP implementation to refer to a particular neighbor.

R2#sh ip route eigrp

D 10.0.0.0/8 [90/2172416] via 1.1.1.1, 00:09:40, Serial1/0

R2#ping 10.1.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 24/38/56 ms

R2#