After a week of waiting (why this is taking so long? this wasn’t a particularly pleasant week), I finally got my number.
Brand new JNCIE-DC #31 !!!
The main note about the lab – time management is the most important thing on the exam. Don’t rush to the keyboard, read and understand all the tasks and it’s interdependencies. Have a plan regarding order of tasks – not all tasks can be completed in order in which they written. Don’t be affraid to skip some tasks if it takes a long time.
I am quite pleased with the level of my preparation for the lab – there were no unexpected or incomprehensible tasks. General feeling about JNCIE-DC lab – this is interesting, pretty complex but fair exam. Lot of tasks on various themes, I think all themes from blueprint are covered in the lab in some ways.
As the proctor told me, the main difficulty of this exam is that it’s something new, and people are afraid of a new and unexpected. I want to tell you – don’t be afraid! If you’re interested in learning a Juniper way of building Data Center networks, and also want to earn one more pretty Continue reading
The post Worth Reading: Supporting new DNS RR types appeared first on rule 11 reader.
Today we published a new Privacy Policy covering usage of our web sites as well as our collecting and maintaining Personal Data of our members, attendees to our events and subscribers of our various communications.
Tedium is the enemy of productivity. The fastest way for a task to not be done is to make it long, boring, and somewhat complicated. People who feel that something is tedious or repetitive are the ones more likely to marginalize a task. And I think I speak for the entire industry when I say that there is no task more tedious and boring than documentation. So how can we fix it?
I’m not a huge fan of documentation. When I decide on a plan of action, I rarely write it down step-by-step unless I’m trying to train someone. Even then, it looks more like notes with keywords instead of a narrative to follow. It’s a habit that has been borne out of years of firefighting in networks and calls to “do it faster”. The essential items of a task are refined and reduced until all that remains is the work and none of the ancillary items, like documentation.
Based on my previous life as a network engineer, I can honestly say that I’m not alone in this either. My old company made lots of money doing network discovery engagements. Sometimes these came because the Continue reading
Network Interconnections is one of the most important topics for the operator network as it directly related with the cost of the sending traffic out from their networks. I published a network interconnection video on my Facebook page. I explain the peering types, settlement free peering , paid peering , remote peering , IP […]
The post Network Interconnections Video by Orhan Ergun appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
Companies need to ask themselves some questions before deciding on a cloud model.
Some networking practitioners start their network automation journey with the Python or Ansible dilemma. Engineers and architects usually want to understand the bigger picture first, and figure out the potential showstoppers and roadblocks. One of them left this feedback on the Network Automation 101 webinar:
A must-have overview of fundamental Network Automation concepts. I wouldn't face an automation project without understanding these concepts first.