tag:blogger.com,1999:blog-13125888104784290082024-02-16T06:34:16.961+02:00CCIE in 2 months - Is it possible?<b>CCIE in 2 months - Is it possible?</b><br>
This is a journey to passing the <b>CCIE SP Lab</b> exam in a period of <b>2 months</b>.<br>
This is my latest and hardest challenge, after completing my previous journey in just <a href="http://ccie-in-3-months.blogspot.gr/">3 months</a>.<br>
It started on 14th of December 2013 and ended at 10th of February 2014.<br>
Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.comBlogger50125tag:blogger.com,1999:blog-1312588810478429008.post-36021763992763304752014-02-12T19:24:00.000+02:002014-02-16T16:00:15.269+02:00The chronicle of successI want to start with a simple but important statement [and i hope i am not sued for breaking the NDA]: If there is one thing i enjoyed from the lab [how can someone enjoy a CCIE lab?], that is the appearance of IPv6 in so many tasks! It's refreshing to see it being used in so many imaginative ways.
Anyway, this is my complete story...
24/Oct/2013 - The experiment
It all started on 24th of Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com8tag:blogger.com,1999:blog-1312588810478429008.post-73512907817677066472014-02-10T21:57:00.003+02:002014-02-11T16:57:38.406+02:00...wtf was that?This must have been the nastiest, wickedest, tightest, weirdest, unfriendliest, and fullest of devices exam ever encountered. If someone was able to count the number of configuration lines and outputs produced in only 8 hours in so many devices in such a unsuitable working environment, he would be shocked by that number. You have very little time to think your options about any possible answers, Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com3tag:blogger.com,1999:blog-1312588810478429008.post-42472927113842107262014-02-09T22:30:00.000+02:002014-02-11T22:39:59.683+02:00Lab Week #9
From 03/Feb/2014 to 09/Feb/2014
This was the ninth (and last) week of my lab preparation. Besides focusing on topics which needed a boost, i did a review of all topics according to my NTS, i recorded most of them to my mp3 player and i also created a (300 page!) pdf from all of them (i still can't believe the size of that).
Total average has increased from 74% to 77,3%, with noticeable Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-10143469872610373042014-02-07T13:38:00.002+02:002014-02-07T13:45:25.787+02:00Countdown continues...3 days left...This is my last post before flying to Brussels (tomorrow) and having the lab exam (on Monday). I'm going to spend the next two days solely on reading & hearing my notes, plus a quick verification of some corner cases on Rack Rentals later today.
I feel quite confident about most topics, but there are some minor ones that i would prefer to have tested a little bit more. Unfortunately my work Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-19937342583308222182014-02-06T23:59:00.000+02:002014-02-06T23:59:08.344+02:00Lab Week #8
From 27/Jan/2014 to 02/Feb/2014
This was the eighth week of my lab preparation; just one week remains before the lab exam. I focused mostly on things that i felt i needed more practice (i.e. Multicast, mVPN) and i also checked various subjects that i needed to refresh my knowledge (i.e. QoS & Frame-Relay).
Total average has increased from 70,3% to 74,0%, with noticeable difference in MPLSTassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-33019268069518301872014-02-06T23:57:00.000+02:002014-02-15T14:25:10.419+02:00NTS: Advanced Multicast
Advanced Multicast
RPF (Reverse Path Forwarding)
In an RPF check, the
router looks in a routing table to determine its RPF interface, which
is the interface closest to the root (the source or the RP). The RPF
interface is also the incoming interface for the multicast data. RPF
checks happen in the control-plane (PIM, MSDP) and in the data-plane
(multicast data).
The routing table used Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com1tag:blogger.com,1999:blog-1312588810478429008.post-49025476030851812092014-02-06T22:58:00.000+02:002014-02-16T13:22:37.283+02:00NTS: Advanced MPLS-TE
Advanced MPLS-TE
FRR (Fast ReRoute) extensions for RSVP-TE are defined in RFC 4090.
Inter-Area MPLS TE is described in RFC 4105.
Inter-AS MPLS TE is described in RFC 4216.
LSP Protection
path protection - long term
local protection (FRR) - short term
link protection
node protection
Backup tunnels are usually used for a short period of time, until the head-end recomputes and signals aTassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com1tag:blogger.com,1999:blog-1312588810478429008.post-26592671526981239962014-02-06T22:12:00.000+02:002014-02-15T14:29:44.489+02:00NTS: PPP/Serial/POS
PPP/Serial/POS
PPP (Point-to-Point Protocol) is defined in RFC 1661.
PPPoE (PPP over Ethernet) is described in RFC 2516.
Serial
Don't forget to to set the clock rate (i.e. 64000) on the DCE interface (usually the one on the service provider router).
PPP
You can use "no peer neighbor route" in order to disable creating a /32 for the peer address.
Multilink PPP
R1 (IOS)
interface Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-49325514513876016752014-02-06T22:02:00.000+02:002014-02-15T14:32:28.162+02:00NTS: L3VPN Redistribution
L3VPN Redistribution
Configuration Steps
Configure the VRFs
Configure the RDs
Configure the import/export RTs
Assign the PE=>CE interfaces to VRFs
Configure IGP/BGP between PE-CE
Configure MP-BGP between PEs
Mutually redistribute between MP-BGP and the PE-CE IGP
BGP<=>RIP
RIP=>BGP
RIP metric => BGP MED (auto)
RIP=>BGP=>RIP
RIP metric => BGP MED => RIP metricTassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-37219119418952168592014-02-06T21:22:00.000+02:002014-02-15T14:44:37.607+02:00NTS: VRF
VRF
VRF Basic Configuration
IOS
ip vrf VPN-A rd 100:1
route-target export 100:1
route-target import 100:1
!
vrf definition VPN-B
rd 100:2
address-family ipv4
route-target export 100:2
route-target import 100:2 exit-address-family address-family ipv6
route-target export 100:2
route-target import 100:2
Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-3516194062438390052014-02-06T19:59:00.000+02:002014-02-15T14:46:01.432+02:00NTS: CsC
CsC
CsC (Carrier supporting Carrier) is defined in RFC 4364.
Control-Plane
The Customer Carrier PEs run BGP VPNv4 in order to exchange VPN labels
The Customer Carrier routers run IGP+LDP (or iBGP+Label) in order to exchange all their internal BGP next-hops and their labels
The CsC-PEs and CsC-CEs run eBGP (or IGP) in order to exchange BGP next-hop prefixes
The CsC-PEs and CsC-CEs run eBGPTassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-3289903137221285432014-02-06T19:46:00.000+02:002014-02-11T17:41:08.315+02:00NTS: QoS
QoS
Congestion Management
WFQ (Weighted Fair Queuing)
fair-queue
CQ (Custom Queuing)
custom-queue
PQ (Priority Queuing)
priority-queue
CBWFQ (Class-Based WFQ)
MQC & bandwidth
LLQ (Low Latency Queuing)
MQC & priority
Congestion Avoidance
Tail-Drop
default
WRED (Weighted Random Early Detection)
random-detect
Class-Based WRED
MQC & random-detect
Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-7005927457953925402014-02-06T19:13:00.000+02:002014-02-15T15:01:34.887+02:00NTS: BFD
BFD
BFD (Bidirectional Forwarding Detection) is defined in RFC 5880.
BFD for one-hop IPv4/IPv6 is defined in RFC 5881.
BFD for multi-hop is defined in RFC 5883.
BFD for MPLS LSPs is defined in RFC 5884.
Common BFD applications
Control plane liveliness detection
Tunnel endpoint liveliness detection
Trigger mechanism for IP/MPLS FRR
MPLS date plane failure detection
BFD advantages
Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-72986848914868984782014-02-06T16:36:00.000+02:002014-02-16T12:39:08.764+02:00NTS: RSVP/MPLS-TE
RSVP/MPLS-TE
MPLS-TE (MPLS Traffic Engineering) Requirements are described in RFC 2702.
RSVP (Resource Reservation Protocol) is defined in RFC 2205.
RSVP-TE (RSVP Traffic Engineering extension) is defined in RFC 3209.
OSPFv2 extensions for TE are defined in RFC 3630.
OSPFv3 extensions for TE are defined in RFC 5329.
ISIS extensions for TE are defined in RFC 5305.
RSVP
RSVP messages areTassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com1tag:blogger.com,1999:blog-1312588810478429008.post-28746092967991749142014-02-06T16:16:00.000+02:002014-02-15T16:05:54.697+02:00NTS: BGP
BGP
BGP (Border Gateway Protocol) is defined in RFC 4271.
Uses TCP port 179.
The router with the highest router-id is used as the TCP client.
Best Path Selection
table.tableizer-table {
border: 1px solid #CCC; font-family: Arial, Helvetica, sans-serif
font-size: 12px;
}
.tableizer-table td {
padding: 4px;
margin: 3px;
border: 1px solid #ccc;
}
.tableizer-table th {
Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-56874697911911010782014-02-06T15:19:00.000+02:002014-02-15T16:40:07.434+02:00NTS: OSPFv2/OSPFv3
OSPFv2/OSPFv3
OSPFv2 (Open Shortest Path First v2) is defined in RFC 2328.
OSPFv3 is defined in RFC 5340.
OSPFv2 as PE/CE protocol is defined in RFC 4577.
OSPF is protocol 89.
Sends updates to multicast 224.0.0.5 (all OSPF routers) and 224.0.0.6 (all DR routers)
Adjacencies
Adjacency can be formed between different networks if "ip unnumbered" is used on both sides.
If multiple "Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-71121176998290326892014-02-06T15:16:00.000+02:002014-02-15T16:42:23.924+02:00NTS: EIGRP
EIGRP
EIGRP (Enhanced Interior Gateway Routing Protocol) is described in draft-savage-eigrp.
EIGRP is protocol number 88.
Packets are sent to multicast 224.0.0.10 (IPv4) or FF02::A (IPv6).
Metrics
bandwidth
minimum bandwidth (kbps) => 10^7 / bandwidth
delay
total route delay (tens of microseconds) => delay/10
reliability
likelihood of successful packet transmission (0-255Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-2327860855943191522014-02-06T14:56:00.000+02:002014-02-15T16:43:03.247+02:00NTS: RIP/RIPng
RIP/RIPng
RIPv1 (Routing Information Protocol v1) is defined in RFC 1058.
RIPv2 is defined in RFC 2453.
RIPng (RIP for IPv6) is defined in RFC 2080.
RIP uses UDP port 520.
Metric = hop count (1-16) - use offset-list to modify
Admin distance is 120.
RIP v1
If the advertised prefix is part of a directly connected network, the subnet mask of that connected interface is used as Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-89791013789347579462014-02-06T14:45:00.000+02:002014-02-15T16:50:23.388+02:00NTS: Frame-Relay
Frame-Relay
Multiprotocol Interconnect over Frame-Relay is defined in RFC 2427.
PPP over Frame Relay is defined in RFC 1973.
FECN/BECN
FECN (Forward Explicit Congestion Notification)
If set to 1, it indicates that congestion was experienced in the direction of the frame transmission, so the destination is informed of that congestion.
BECN (Backwards Explicit Congestion Notification)
Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-87332185051140919662014-02-06T14:07:00.000+02:002014-02-16T13:23:12.924+02:00NTS: Other
Other
These topics are not considered critical because they aren't usually used as a base for something else, but they can easily give you some points if configured correctly.
Having a general idea is probably enough, as long as you know where to look in the documentation for the details.
MAC accounting
Use it to collect statistics about traffic per mac address.
IOS
interface Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-33203644395775888832014-02-06T13:47:00.000+02:002014-02-15T17:07:41.760+02:00NTS: IS-IS
IS-IS
IS-IS (Intermediate System to Intermediate System) is defined in ISO 10589 and in RFC 1142 and RFC 1195.
IS-IS Multi-Instance is defined in RFC 6822.
IS-IS PDU types
LAN Hello
Serial (Point-to-Point) Hello
Link State PDU (LSP)
Complete Sequence Number PDU (CSNP)
Partial Sequence Number PDU (PSNP)
IS-IS LSPs are like OSPF LSAs.
CSNPs are generated:
by the DIS in order for Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-51830847879746392172014-02-06T13:24:00.000+02:002014-02-15T17:09:05.339+02:00NTS: Inter-AS MPLS L3VPN
Inter-AS MPLS L3VPN
Inter-AS MPLS L3VPN Options are defined in RFC 4364.
Inter-AS Options
Inter-AS Option A (Back-to-Back VRF)
one logical/physical interface per VRF in the interconnection
one PE-CE eBGP/IGP session per VRF between ASBRs
IP traffic between ASBRs
no need for common RDs/RTs between ASNs
2 LSPs and 1 IP path from one PE to the other PE
Inter-AS Option B (MP-eBGP Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-72629363876702092832014-02-06T13:09:00.000+02:002014-02-15T17:29:50.598+02:00NTS: Advanced BGP
Advanced BGP
BGP (Border Gateway Protocol) is defined in RFC 4271.
MP-BGP (Multi-Protocol BGP) is defined in RFC 4760.
Labeled BGP (BGP+Label) is defined in RFC 3107.
enforce-first-as
When enabled, updates received from an eBGP peer that does not list its ASN at the
beginning of the as-path in the incoming update are denied (in order to prevent spoofing).
It's enabled by default.
IOS
Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-36445883324975029732014-02-06T11:44:00.000+02:002014-02-15T18:07:16.313+02:00NTS: UNI-ENI Vlans vs Private Vlans
UNI-ENI Vlans vs Private Vlans
UNI-ENI Vlans (or just UNI Vlans)
Types
Isolated Vlans
Community Vlans
Characteristics
Configuration happens under the Vlan
Port configuration doesn't include Vlan type
Each port can include many UNI-ENI Vlans
Apply to access, trunk, tunnel ports
There is only local significance per switch
L3 config applies to each Vlan separately
MAC addresses are Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com0tag:blogger.com,1999:blog-1312588810478429008.post-55097732792290852972014-02-06T11:37:00.000+02:002014-02-15T18:09:18.927+02:00NTS: MPLS/LDP
MPLS/LDP
LDP (Label Distribution Protocol) is defined in RFC 5036.
MPLS (Multi-Protocol Label Switching) architecture is defined in RFC 3031.
MPLS Label Stack Encoding is defined in RFC 3032.
LDP messages
LDP Discovery (to directly connected neighbors)
Multicast UDP to 244.0.0.2:646
targeted LDP Discovery (to non-directly connected neighbors)
Unicast UDP to x.x.x.x:646
LDP Session/Tassoshttp://www.blogger.com/profile/04512662084752743003noreply@blogger.com2