My Short Notes on NSX Part-1

Hi Guys, I am back again with my NSX studies and I will share my short notes here, which will have no format but I believe this will help you. What is an SDDC?  # A DC platform that can be dynamically configured to meet the needs of any and all application workloads, all operating at a peak level of efficiency and automation. # All infrastructure is virtualized and delivered as a service, and the control of this DC is entirely automated by software. #  This solves the problem of services provisioning, maybe from 8-10 weeks to 30 mins and including firewall & Load Balancer etc…with 1 week around. # Virtualize scale-up and scale-out application. #  Zero downtime live migration over distance & cross boundaries. #  Continuous availability for the production of virtual machines. #  SDDC can be programmatically provisioned. #  SDDC consists of three components majorly i.e Network, Storage & Compute to host the business-critical application. #  SDDC vision

read more My Short Notes on NSX Part-1

EEM Script in Cisco Routers

What is EEM? EEM (Embedded Event manager) is a software component of Cisco IOS, XR, and NX-OS. EEM gives you high abilities to admin your Cisco device by tracking and monitoring events that take place on your Cisco device and then apply action you already decided early, EEM by giving you this ability, it allows you to automate many tasks. EEM Types: There are two EEM independent pieces (types): Applets and Scripting -> Applets are a collection of CLI commands -> Scripts are actions coded up in TCL (interpreter language) Here we will find some examples for applets and let’s put in our minds that we can have Only one event per applet with single or  Multiple actions run in sequence. EEM Event detectors: EEM uses Event detectors to understand that event occurred, some of these detectors are: SNMP:-Monitoring SNMP objects. Syslog:-Responds to various syslog messages, allowing for matching on regular expressions. Counter: Monitoring and responding to the interface counter when crossing threshold settings. CLI

read more EEM Script in Cisco Routers

BGP Route Reflector

Good Morning Guys, This is a very old post of mine, and actually, this was the first post of mine back in 2013. Since I am migrating to my new website, hence I am republishing it here but I will never delete that post in my old blog. Here you Go…… Route reflectors do one very important thing in an iBGP network, and that’s to disable the iBGP ‘split-horizon rule’. iBGP Split-Horizon rule says that if I am a router running iBGP and I learn a route from another iBGP peer, I will never advertise that route to another iBGP peer. i.e x-R1——–R2——–R3 All the routers above are running iBGP. R1 has a network x….It will advertise network x to R2. However, R2 will never tell R3 of network x, because of the iBGP Split-Horizon rule. This has severely hampered the propagation of routes in our network. There are two ways of solving this. One, you could create a full

read more BGP Route Reflector

EIGRP Stub Router Concept

Stub-router, when we listen to this we immediately get the feeling like some LSAs are filtered, some summary route, etc. But in the EIGRP Stub router concept is different; here stub router concept came into the picture to avoid EIGRP Stuck In Active (SIA). The Router which is configured as a stub router will inform it’s neighbor that I am the last router of the network, I do not have any neighbor connected with me. Little confusing? Okay, let me try to explain it with some topology. Now, what will be the output in the test and control router if we do not configure Stub router as a stub? It will receive all the routes, let us verify. Configuration: Control_Router#sh run | s eigrp router eigrp 50 network 0.0.0.0 no auto-summary Stub_Router#sh run | s eigrp router eigrp 50 network 10.10.10.2 0.0.0.0 network 10.10.10.6 0.0.0.0 no auto-summary Test_Router#sh run | s eigrp router eigrp 50 network 0.0.0.0 no auto-summary Output:

read more EIGRP Stub Router Concept