Showing posts with label Interview. Show all posts
Showing posts with label Interview. Show all posts

Sunday, August 8, 2021

" How to better prepare for interviews "

 


- Every interviewer and every company has patterns & biases, the sooner you find it out, better off you would be.

- There are only two types of interviews, in first case you take everything in control as much as possible from the beginning to the end. To get to that level - invest more time learning about: Mental Models, Human Psychology & Biases, Story Telling, Presentation Skills & Marketing. In second case - the person on other side of the table takes control and take you for a ride.

- Preparing for interviews is a serious business for people serious about their career or at least cracking the interviews.

- While most interviewee care and think more about what they can get from given company and role, flip the question in terms of what you can offer and will bring new on the table - with the later mindset you will perform much better.

- At the end of an interview, make sure you ask questions to better understand your role, work culture, particular expectations that the hiring manager may have, what systems and methods they have in place to measure and rate employee performance but more importantly business performance in terms of business line you will be part of.

HTH...

A Network Artist ðŸŽ¨

Sunday, May 4, 2014

Time To Get Rid Of 7 IP Networking Myths - Based On Recent Interviews I Did





In last 6 months I got opportunity to work closely with HR teams from different regions within company and must have interviewed well over 200 People which gave me good opportunity to talk to so many candidates ranging from CCNA to CCIE & even Multiple CCIEs.

During this whole process I came across couple of Myths related to IP Networking which I would want to share so that together we can spread more awareness among other Engineers & Clients.


Myth 1 : vPC eliminates STP into the Network.

Well vPC tweaks STP behavior quite a bit for it’s operation but STP is still running in backend as fail safe. Even more vPC Primary switch send regular STP BPDUs by default over vPC member ports. Well the only solution to get rid of STP completely today from Cisco’s perspective is implementing Fabric Path.


Myth 2 : EIGRP is a better protocol for Cisco only network since it has better convergence features such as Feasible Successor if compare to OSPF. Same thought people have when comparing ISIS with OSPF.

Well convergence in itself is domain now from IP Networking perspective or perhaps always was. It’s just people these days talk more about it as requirements have grown tight in last 5 years because of Next Generation Network Requirements and more sensitive applications.

Most routing protocols don’t spend too much time for re-calculation once the primary path gets failed. The most contributing factor in convergence is detection of failure rather. A simple example would be to have two EIGRP neighbors connected through multiple links including a Ethernet connection through L2 Switch which is currently primary path. If link between L2 switch & Router 2 fails, Router 1 will notice the failure only after dead timer expire and than will run DUAL for recalculation depending upon it has Feasible successor or not. So in this case it’s not going to be any different than OSPF or IS-IS.


Myth 3 : OTV is the best solution for VMotion over Data Center Interconnect (DCI) or any Layer 2 extension requirements.

Well It depends. The part of equation here is VMotion requirements itself. For Hot VMotion the end to end delay requirements is less than or equal to 5 msec which in new ESXi version got relaxed to 10 msec I guess. So if the delay is higher and you have Hot VMotion requirements, OTV won’t do any good as DCI. Also choosing DCI Technology Between OTV and others like MPLS Martini Style, VPLS etc has lot to do with Scale related to number of MAC Addresses to be learned & Exchanged.


Myth 4 : One major benefit of using MPLS is that Router Switches packets faster since it uses LIB


Well it use be true in history but ever since the introduction of Hardware based forwarding in platforms and platforms having great amount of CPU and Memory, it’s not true any longer.


Myth 5 : Nexus 2000 is a Switch

Well it can’t perform local switching between 2 ports which might be even in Same VLAN. All the switching is still performed by Parent Switch (7k or 5k) based on VN Tags.


Myth 6 – Once the EIGRP SIA Timer Expires, The Neighbors are bounced

Well Cisco solved this problem I guess almost 10 years back with implementation of SIA Query & Replies. It’s just of those things which are not documented in most Cisco Press Books J covering EIGRP


Myth 7 – Traceroute is part of ICMP Suite

Well traceroute is an application but not a protocol or part of any protocol suite in itself. Traceroute has different implementations using ICMP, TCP & UDP by different vendors.


HTH...
Deepak Arora
Evil CCIE

Wednesday, May 29, 2013

GNS As Network Interview Tool - Test 1 (Layer-2)

Recently I was interviewing lots of people for a Level-2 Engineer profile. The requirement  was for one of my Enterprise client NOC. The client simply asked me to ensure only quality Engineers get through this. So I decided to change my regular interview pattern this time. I designed a Series of hands on test for this purpose. So here is the Test-1. Though I wrote this for level-2 Engineers to ensure even a rusty CCNP Engineer can qualify this but even I expect a Good CCNA Engineer to pass this easily.




Guidelines
ü  All VLANs are preconfigured.
ü  All passwords are preconfigured.
ü  Verify VLAN database using “ sh vlan-switch brief “ command.
ü  Don’t configure any local user account.
ü  Don’t change default console settings.
ü  Use dummy username “abc” for ssh testing.
ü  There are some configuration faults which you may need to find and fix.
ü  Don’t reload the device without checking with Interviewer.
ü  The given time for test is 35 Mins.
Tasks

Ø  1. Configure all inter switch links as 802.1Q Trunks.
Ø  2. Make sure SW-1 is Root Bridge for VLAN 10 , SW-2 is Root Bridge for VLAN 20 , SW-3 is Root Bridge for VLAN 30
Ø  3. Confi gure the inter switch links between R1 & R2 , R1 & R3 so that none of the link is in spanning tree block state.
Ø  4. Make sure all switches are able to telnet each other. Use password as " cisco " whenever required. Management IPs are as Followed:
SW-1 > 1.1.1.1/24
SW-2 > 1.1.1.2/24
SW-3 > 1.1.1.3/24
Ø  5. Configure SW-1 so that it allows SSH connection for management in INBOUND direction. Make sure when you SSH from SW-2/SW-3, you are able to get SSH login Prompt.
 Example:

 

Ø  6. Enable SNMP environmental monitor traps on SW-2 to ensure traps are generated for High Temperature & Fan failures for example. The traps should be sent out to NMS Address “1.1.1.250”. Use community value as “ cisco “ if required.
Ø  7. Create a SPAN (AKA Port Mirroring) session with source interface as Fa1/5 on SW3. The SPAN Destination is Fa1/6

GNS Initials & Topology - http://www.4shared.com/rar/Zhou26u3/L2_Section.html

HTH...
Deepak Arora
Evil CCIE