CCIE RS Lab blog – Week 33

Hours Studied – 12, little short of what I was hoping

Sunday

I started off with flash cards again early in the morning. For labbing, I started a little later than I wanted, but worked on CA22. The start of this was very similar to CA21. The L2 was easy to work through. The L3 was very confusing as there was a lot of back and forth and additions of multiple VRF’s. After about 3 hours I lost focus and decided to call it a day. I believe the lack of focus came from the poor nights sleep.

While reflecting on how I was doing I remembered that I am not following the strategy I would do in the actual lab. For the next coming labs I will be implementing the practical lab techniques I would like to perfect.

With a fresh head I am going to revisit this lab as it was more challenging and I’d like to be able to dissect what is being asked and when.

Monday

Monday was my first day back to work and boy were there a lot of emails to get through….

I am back to my normal labbing time at night. An afternoon coffee didn’t seem to help keep me awake to get more than 1.5 hours of labbing in before I couldn’t focus anymore.

I worked on CA20 and it was getting very specific in what it wanted for OSPF which showed a lot of gaps that I had in some of the nuances of this protocol that I want to explore further.

I saved all my configurations and plan to load it up before work on Tuesday to see if some sleep will help.

Tuesday

I tried doing some labbing in the morning continuing with CA20. I wasn’t able to get very far due to other things coming up.

Wednesday

Same as Tuesday… Re-evaluated what’s possible for during the week. I’ll be doing smaller pointed labs.

Thursday

I got into the office early and worked on TA05. This lab was, meh. Not all that challenging and the solutions given go against what I’ve been taught. I’ve been on the assumption of never remove config and that was the 360 solution multiple times.

Friday

I only had time for flashcards

Saturday

I worked on my first graded lab, pre-assessment on Cisco 360. This lab was fairly straight forward in what it was asking. There was only 1 part that stumped me and I ended up just ignoring the restriction and at least getting connectivity.

The grade came back and I got a 73/100, 80 was considered passing. I am happy with this score and after going through where I missed, there were a couple of typos (5 instead of a 6), the redistribution thing I did on purpose and then some messed up math on subnetting.

Nothing was over surprising on what I screwed up on and where I need to focus my attention to. Since this assessment didn’t take as long as I expected I loaded up an INE troubleshooting lab which went ok.

CCIE RS Random Lab Generator

I’ve been looking for a way to easily randomize a blueprint topic to lab as it’s been getting daunting on what thing to do next. One of my Routergod friends (Thanks Dustin!) mentioned using Anki as this tool to do the randomization. 

I took my existing excelsheet of the blueprint, changed some formating around and imported it into a new Anki flashcard deck and set it for 5 cards each day (may adjust as I use). I figure I can’t be the only one with this issue and wanted to share with the community.

If you have any suggestions for improvement please let me know if a comment below!

CCIE RS – L2 WAN Circuit Technology – MLPPP

Multilink PPP

  • Provides load balancing functionality over multiple WAN links
  • RFC 1990
  • Allows packets to be fragmented and sent at same time over multiple p2p links

Link Fragmentation and Interleaving (LFI)

  • Type of Cisco QoS
  • Prevent small delay sensitive packets from having to wait on longer, delay insensitive packets to be completely serialized out an interface
  • Fragments larger packets
  • Ppp multilink interleave
  • Ppp multilink fragment-delay [#]

Configuration

Interface multilink [#]
Ip address
Ppp multilink
Ppp multilink group [#]

CCIE RS – Written – L2 – Implement and Troubleshoot VLANs

CCIE RS – Written – L2 – Implement and Troubleshoot VLANs

VLAN – Virtual LAN

  • Administratively defined subset of switch ports that are in the same broadcast domain
  • Broadcast domain – devices that can receive broadcast sent by another device
  • Best Practice – 1 to 1 relationship between IP subnet and VLAN

Configuration

  • Vlan [id]
  • Under interface > switchport access vlan [id]
  • Modify VLAN operational state (L2 only)
    • Can be suspended globaly for entire VTP or to local switch
    • Vlan [id] > state suspend (global) | shutdown (local)

Access Ports

Belongs and carries traffic for only 1 VLAN 

Configuration

interface > switchport access vlan [#]


VLAN Database

  • Vlan 0 – Reserved, not available for use
  • Vlan 1 – Default vlan for all access ports
    • Cannot be deleted or pruned
  • Vlan 4095 – Reserved, not available for use

Switch#sh vlan

VLAN Name                             Status    Ports
—- ——————————– ——— ——————————-
1    default                          active    Gi0/0, Gi0/1, Gi0/2
1002 fddi-default                     act/unsup
1003 token-ring-default               act/unsup
1004 fddinet-default                  act/unsup
1005 trnet-default                    act/unsup 

VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
—- —– ———- —– —— —— ——– —- ——– —— ——
1    enet  100001     1500  –      –      –        –    –        0      0   
1002 fddi  101002     1500  –      –      –        –    –        0      0   
1003 tr    101003     1500  –      –      –        –    –        0      0   
1004 fdnet 101004     1500  –      –      –        ieee –        0      0   
1005 trnet 101005     1500  –      –      –        ibm  –        0      0   

Primary Secondary Type              Ports
——- ——— —————– ——————————————

Switch#


Normal VLAN

1 – 1001

  • Can be advertised with VTPv1 and 2
  • Configured in vlan database, global config
  • Details stored in vlan.dat
  • Can be pruned

1002 – 1005 Special uses

  • Cannot be pruned
  • 1002 fddi-default
  • 1003 token-ring-default
  • 1004 fddinet-default
  • 1005 trnet-default

Extended VLAN

1006 – 4094

VTPv1 and 2 must be in transparent mode


Voice VLAN

Enables access ports to carry traffic from an IP Phone

  • Portfast is automatically enabled when voice vlan is configured
    • Not disabled if voice vlan is removed

Configure how the Cisco IP Phone carries voice traffic:

  • vlan-id —Configure the phone to forward all voice traffic through the specified VLAN. By default, the Cisco IP Phone forwards the voice traffic with an IEEE 802.1Q priority of 5. Valid VLAN IDs are 1 to 4094.
  • dot1p —Configure the phone to use IEEE802.1p priority tagging for voice traffic and to use the default native VLAN (VLAN 0) to carry all traffic. By default, the Cisco IP Phone forwards the voice traffic with an IEEE 802.1p priority of 5.
  • none —Allow the phone to use its own configuration to send untagged voice traffic.
  • untagged —Configure the phone to send untagged voice traffic.