Exam on Aaron's Worthless Words

CCIE R&S Written -- Epic Fail (Again Again)

Wed, 07 Aug 2013 00:00:00 +0000

On Friday, and for the fourth time, I took the CCIE R&S Written exam (350-001). For the third time, though, I failed. Let me tell you, I am absolutely devastated. I worked my buns off for the past few weeks, but I’m obviously missing some important piece to put me over the top.

Not only was I disappointed with my overall score, I was disappointed by my score in some of the focus areas. For God’s sake, I made a 50% on each of the routing and switching sections, which is just absolutely embarrassing. I mean, this is my bread and butter here. This is what I do all day every day, and I could only muster a 50%?

JNCIS - Epic Win!

Fri, 15 Feb 2013 00:00:00 +0000

I quit my job…by design. I start a new gig on Tuesday and am getting back to the world of Cisco. As a last nod to Juniper, I decided to use an exam voucher I had and take the JNCIS-ENT exam. Easy pass.

The content was right along with the exam objectives, so there were no surprises. Most of the topics are things I’ve done a thousand times on the job. There were some things, though, that were beyond my experience. IS-IS was the big one. The very first question I got was about IS-IS metrics, and I had absolutely no clue what the answer was. Nor did I have any clue about the other IS-IS questions. I went 0-for-3 on those guys. The only other problematic topic was HA, which didn’t really surprised me. I was able to answer the VRRP questions, but I’ve never done any GRES, ISSUe, RTG, etc., at any point in my career. It wasn’t surprising that I didn’t do too well on those. Everything else was cake, and I only missed 6 questions in my comfort zone.

JNCIA - Epic Win!

Fri, 10 Feb 2012 00:00:00 +0000

Maybe not epic, but a win nonetheless.

My boss is over all the network guys in the company, and that includes guys that support different divisions and departments. He told me he was tired of waking up at 2am every morning to fix a problem the other groups can’t handle, so he’s working to get the junior guys motivated to learn for themselves. One technique he’s implemented is to force them to get their CCNAs and JNCIAs by June. Since he made it part of the job description, that means that everyone above the Analysts has to meet those requirements, too. I made the deadline with plenty of time to spare.

CCIE R&S Written - Epic Fail

Tue, 19 Jul 2011 00:00:00 +0000

It’s been a long time, eh? I’ve spent the last month or so with my nose down in a book and my mouse in a Google+ Hangout window studying my rear off for the CCIE R&S Written. Too bad I didn’t pass it.

The exam consisted of 77 questions over a 2 hour window. That’s plenty of time to finish; I think I had 48 minutes left when I was through, so time wasn’t a problem. There were only 2 or 3 questions where I was totally lost, so the technology wasn’t a problem. The big problem, like always, was the usual crap questions that are in these exams. Some didn’t provide all the required information. Some were impractical examples of deployments you would never use in the field. Some were on deprecated technologies. Hell, I had one that involved CatOS. Really? CatOS? Since I only failed by about 2 questions (like I always do), these shenanigans are magnified in my mind. It really irks me how these exams are being done; foggy questions don’t really measure ability.

IIUC Update - Passed!

Wed, 09 Feb 2011 00:00:00 +0000

I passed the IIUC yesterday, so now I’m a CCNA Voice. It’s kind of belittling to get a CCNA-level certification at this point in my career, but I didn’t want to be completely left behind, so I figured I should move into some voice stuff before I’m left in the dust.

The exam was probably the best Cisco exam I’ve ever taken. Of all the exams I’ve taken in the last few years, this is the only one that didn’t have questions with huge misspellings or grammatical errors. I was really taken aback at that since a good portion of the questions from some of my recent CCNP exams were plain unreadable. I think I remember leaving a comment on one IIUC question about the word “an” being left out of a description, but that was no big deal. I’m not that obesessive-compulsive.

IIUC Notes - Inbound Dial Peer Matching

Wed, 19 Jan 2011 00:00:00 +0000

More IIUC notes. As always, feel free to correct as needed.

To match inbound calls to a dial peer, CME (and CUCM?) uses the following steps.

Match DNIS (the dialed number) with the incoming called-address config in the dial peer
Match the ANI (the calling number or caller ID) with the answer-address config in the dial peer
Match the ANI with the destination-pattern config in the dial peer
Match an incoming POTS call to the port config in the dial peer
Match dial peer 0

Matching dial peer 0 is bad, and it took me an inquiry on Twitter and a buddy to realize why. Here are a few highlights as to why. I believe the full scope of the badness of dial peer 0 is really beyond the IIUC exam.

Stubby Post - Changes to CCNA Voice, CCVP, and CCSP

Wed, 20 Oct 2010 00:00:00 +0000

I don’t usually cover news from Cisco, but they’ve changed some certification stuff around again, and I thought I would bring it up. This time they’ve changed the CCNA Voice, CCVP, and CCSP, so, if you’ve on those tracks, be careful what you’re studying!

CCNA Voice

Circle 28 February 2011 on your calendars. That’s when the CCNA Voice track gets a shakeup. The IIUC (640-460) exam will be no more, and passing CVOICE (642-436) will no longer be a valid way to get the cert. After the big day, you’ll have to take ICOMM (640-461). This seems to be a much broader exam instead of having the enterprise and commercial focuses in CVOICE and IIUC, respectively. Look out for both CME- and CUCM-based topics including a troubleshooting section.

CME Exercise #1

Thu, 07 Oct 2010 00:00:00 +0000

I tried something like this earlier this year with STP. It got rave reviews (from my mother), so I figured I try it again.

Below is a list of requirements for configuring a router as a call processor. In a lab or in your head, configure the router to support the features as listed. This isn’t a contest or anything like that. If you get it right, a virtual thumbs up is all I can afford to give you. There are some licensing issues for running this stuff in GNS3/dynamips, so I can’t help you out on that. I’ll just hint that GNS3 and dynamips will bind to real networks and that copies of a compatible IP softphone are available.

IIUC Notes - Voice Ports and Dial Peers

Mon, 04 Oct 2010 00:00:00 +0000

More of my IIUC study notes. As always, feel free to correct. I really need to have a real post, don’t I?

show voice port summary

Shows the voice ports available for use

R1#show voice port summary
                                          IN       OUT
PORT           CH   SIG-TYPE   ADMIN OPER STATUS   STATUS   EC
============== == ============ ===== ==== ======== ======== ==
50/0/1         1      efxs     up    up   on-hook  idle     y
50/0/1         2      efxs     up    up   on-hook  idle     y
50/0/2         1      efxs     up    up   on-hook  idle     y
50/0/2         2      efxs     up    up   on-hook  idle     y
50/0/3         1      efxs     up    up   on-hook  idle     y
50/0/4         1      efxs     up    up   on-hook  idle     y
50/0/5         1      efxs     up    up   on-hook  idle     y

An ephone-dn shows up as efxs, so all these are ephone-dns.
Channels are numbered 0-23; timeslots are numbered 1-24

FXS Ports

IIUC Notes - More Phone Features

Sat, 02 Oct 2010 00:00:00 +0000

Here are some more notes from my IIUC studies. As always, corrections requested.

Paging

Broadcasts messages to a group for a one-way communication
Paging groups are used to limit which phones get the broadcast
Paging can be unicast or multicast
- Unicast groups limited to 10 members
- Multicast requires mcast support on the network
Paging configurations can be unicast, multicast, or multiple-group

! Unicast Paging
! When 1044 is dialed, ephone 1 is paged
R1(config)#ephone-dn 44
R1(config-ephone-dn)#number 1044
R1(config-ephone-dn)#paging
R1(config-ephone-dn)#exit
R1(config)#ephone 1
R1(config-ephone)#paging-dn 44

IIUC Notes - Phone Features

Fri, 01 Oct 2010 00:00:00 +0000

Here are some more notes from my IIUC studies. As always, corrections requested.

Local Directory

Allows users to look up names
Allows names to show up when dialing or receiving a call
Most phones have a directory button; some have a menu options for the directory

R1(config)#ephone-dn 1
R1(config-ephone-dn)#name Roger Smith

Directory entries can be added manually

R1(config-telephony)#directory entry 1 1700 Corporate Fax
R1(config-telephony)#directory entry 2 1701 HR Fax

By default, sorting is done alphabetically by first name.
Sorting can be changed

R1(config-telephony)#directory last-name-first

IIUC Notes - Getting Phones on the LAN

Thu, 30 Sep 2010 00:00:00 +0000

More study notes. Correct if wrong, though I hope I get some of it right since I already since I’m an R&S guy. :$

**Switchport Configuration
**

switchport mode access: This config makes the port an access port that carries the primary and voice VLAN traffic
switchport mode trunk: This config akes the port a trunk unconditionally, but it will still send DTP messages
switchport nonegotiate: This config keeps the port from sending DTP messages.
switchport mode dynamic auto: If the port receives DTP messages, it will become a trunk. If not, it will be an access port.
switchport mode dynamic desirable: The port actively sends DTP messages trying to become a trunk. This is the default configuration on a Cisco switch.

Cisco IP Phone Boot Process

IIUC Notes - Assigning Ephone-dns to Ephone Buttons

Thu, 23 Sep 2010 00:00:00 +0000

These are some of my notes on my IIUC studies. Since I am a novice as voice stuff, please let me know what I get wrong.

An ephone is a representation of a phone. It’s basically a structure of features that a phone will have.

Configuration in CME:

R1(config)#ephone 34 <– This is just a tag and has nothing to do with an extension or phone
R1(config-ephone)#mac-address 1111.2222.3333 <– Assigns this ephone to the phone with that MAC address

IIUC Notes - Powering Cisco Phones

Tue, 21 Sep 2010 00:00:00 +0000

Feel free to correct anything that is wrong or incomplete.

Power over Ethernet (PoE)
- Can provide power to a Cisco phone, access point, security camera, etc., through the network cabling, eliminating the need to plug the phone into the wall for power.
- Generic term for providing power on the Ethernet cable
- Provides centralized power that can be put on a UPS
- Allows devices to be located away from power outlets
- Removes cabling clutter at the user’s desk
- Can be provided through PoE-enabled switches, power panels or inline couplers (power injectors)
- Oversubscription is common
  - If every device on a switch asks for full power, the switch may not be able to handle the load.
- Of course, devices can be powered with a power brick at the desk
802.3af

IIUC Notes - VoIP Structures

Tue, 21 Sep 2010 00:00:00 +0000

Feel free to correct. No need to sugar-coat it; I’m pretty new at this stuff. :)

Advantages of VoIP
- Reduces costs of communications: Eliminates/reduces long distance and international call tolls
- Reduces costs of cabling: No need for second network of phone lines
- Integrates all voice into one large network: All your remote offices can be implemented/maintained/controlled centrally
- Provides mobility: Moves, adds, and changes (MACs) are (nearly) eliminated since your phone is just a network node
- Allows use of IP Softphones
- Unifies emails, voice mails, and faxes: All these can be treated as a single box for user messages
- Increases productivity: Ringing multiple devices at the same time eliminates phone tag. <— pushing it, eh?
- Enhances communications: Applications can be launched/updated from a voice call through application servers
- Provides open, compatible standards: You can connect different vendor devices into the same VoIP network. <— I’ve never seen that happen
Cisco VoIP Structure

IIUC Notes - Old School Voice Stuff

Wed, 08 Sep 2010 00:00:00 +0000

These are the notes I’ve taken as I read through the study materials. Feel free to correct anything you see.

Analog phone signaling
- Misc
  - Ground = positive = tip
  - Battery = negative = ring
  - Signaling uses specific frequencies for specific events
- Loop start signaling
  - When a circuit in the phone is completed (i.e., you take it off-hook), the CO detects it and provides services.
  - Susceptible to glare, where the phone requests dialtone at the same time that the CO sends a call.
    - Can connect two different calls if in a business with multiple lines
- Ground start signaling
  - The circuit is temporarily completed to signal the CO for services
  - Doesn’t connect any call to any phone directly
  - Used in PBXes.
- Supervisory signaling
  - On-hook: Circuit is open
  - Off-hook: Circuit is completed
  - Ringing: AC current generated by CO to tell the phone to ring
- Informational signaling
  - Gives information for the caller to use
  - Dial tone
  - Busy
  - Ringback: the ring you hear when you call
  - Confirmation: the call is being attempted
  - Congestion: no lines available to make the call
  - Receiver off-hook
  - Reorder: can’t make the call
  - No such number: can’t find the endpoint
- Address signaling
  - Used to send digits
  - Dual-tone multifrequency (DTMF): uses two electrical signals to indicate a digit; touch tone
  - Pulse: flashes the circuit to indicate a digit; rotary dial
- Disadvantages of analog signaling
  - Attenuation
  - Repeaters can’t differentiate between call and noise
  - One cable pair for each call; think about a pair for each call taking place in Manhattan right now
Digitizing voice

Some Cisco Testing Advice

Sat, 24 Jul 2010 00:00:00 +0000

If you follow the blog, you know I’ve had quite an adventure getting my CCNP. Finally, this past Monday, after what seemed liked years of struggling, I finished up my ROUTE test and got the email telling me I’d made it. I’ve learned a lot over the course, but, more than the technical details, I learned more about how to prepare for the exams. It’s too bad I hit the moment of enlightenment after I reached the end of the line. Well, at least this line; there will be others very soon.

ROUTE Notes - Further IGP Redistribution

Sun, 18 Jul 2010 00:00:00 +0000

As always, corrections are requested.

Study Questions

I’ve got IGRP and EIGRP both configured with the same AS number. What’s special about this configuration?

If both use the same AS number, then they automatically redistribute their routes into each other without using the redistribute command.

When redistributing one IGP into another, where’s a good place to filter routes?

There’s no one good place, but at the router(s) that’s doing the redistribution is a good start. There’s no need to send an IGP a bunch of routes it doesn’t need.