Home

Poweron and Poweroff Esxi instance from CLI using a Python script

2 Comments

Hi,

I have to agree that to start a esxi node i was depending heavily on a windows VM and then was using a VSphere client to connect to a Esxi 5.5.

In a typical day all of my VM’s are hosted on Esxi and am not any advanced user of esxi by any stretch of Imagination.

It came down to a point where i had to manually click close to 8 VMS in order to boot up and all this was sort of irriatating for me, so i wrote a very basic script which can do this for me. Most of the experienced VM admins have been doing this for very long, for someone like me or anyone who is new to Esxi this is going to help.

Here is the code for the script, all you need to do is to copy to your lab esxi, obviously if any one using production esxi they already know how to manage this.

https://github.com/yukthr/auts/tree/master/vmware_scripts

Requirement – I have 5 Vm-machines and i would like  to start them via script and also power them off.

First things, list the Vm-instances

 

 

Now that we have it, let explore the script to poweron the specific instances, again power-off is exacty similar

https://github.com/yukthr/auts/blob/master/vmware_scripts/vmware_poweron.py

Basically, Below program is tryin to boot a list of VMs provided in vm, if you want to use this, modify the vm list with the appropriate local Vm number from getallvms output

Am aware there are many network engineers who are starting to realize the power of Esxi over Bare Eve-ng, both have their own advantages anyways, but anyone starting with Esxi, this is not at all a Bad Idea !

 

Regards

Rakesh M

Advertisements

Integrating the configuration build – Next steps

Leave a comment

Hi,

The last post link below, I got introduced to a CI System and basics of it.

https://r2079.wordpress.com/2018/04/03/using-travis-ci-continuous-
integration-with-github/

This post goes further in actually using the CI system.

All the code is hosted here

https://github.com/yukthr/auts.git

-> Requirement is very simple

This is a very basic program which introduces anyone to Jinja2 and
 yaml syntaxing 


Problem  - Have two interfaces ge-0/0/0 and ge-0/0/1, we have to use 
Yaml / Jinja2 and Pyez to develop the configurational 
syntax for this and later on a CI system need to validate the build. 

The code hosted in Github above.
intf.yml    - will have all the interfaces 
template.j2 - will have the appropriate Jinja2 
template.py - will have the python program combining these two

So, we write the code 





Finally build the CI file, but here we also buld the dependencies 
because when CI starts to validate it needs to have all the 
appropriate software installed. It amuses me to the point, 
it spins up the VM and then install the dependencies and then

it validates our code. I have come a long way from manual 
verificaitons / lab testing / CI testing now




This is how dependency file looks like






so when I submit the code via a simple git push,
 i see this happening on the CI automatically



















I would target more posts to get other CI systems
 onboard especially Jenkins2 and then deploy the
 successful build back to git or a server.




Regards

Rakesh M

Using Travis CI (Continuous Integration) with GitHub

2 Comments

Hi ,

Am Planning to write a in detail usage of how we can leverage
Aws cloud - ansible - github - travis-(ci/cd) with in our networking 
deployment space. As of now, I will quickly author how you can 
leverage the usage of Travis CI in our 
experimental space. 

You can find more about Travis CI - Here - .org of travis will 
help to run Opensource Projects 

https://travis-ci.org/

I am using AWS cloud desktop to do the changes to the code, 
get it pushed to git-hub and then integrate everything 
if Travis CI passes the checks 

To let you know the workflow in a very simpler way 

-> You write any code or config related to networks on AWS cloud 
desktop
-> push the code into git-hub in a branch later to be integrated 
into Master Branch
-> Setup Travis to automatically run some pre-defined tests 
-> If all successful, we will merge the code into our master branch 

-> Lets write a very basic code in a branch and push to git-hub 

 




The github page has been integrated with Travis-CI 

 




Travis CI peforms the required checks, here it just 
checks for syntax, obvious this can be exetended for many things 
but as of now we will just see if it can execute 
the program (all of this is performed in automatic container)



Let me change the syntax from print to printf, 
travis should automatically fail the test 






Lets correct the printf to print, 
and we should be able to merge the branch to the master, 
you can also see the CI results directly from the branch





  




This post aims at using a CI system to have us validate the checks. 
I would cover a detailed post and a course on CI and Git
 and using Unit-tests to validate networking related changes. 


-Rakesh



Filtering EVPN Routes with PyEZ

Leave a comment

Hi,

From the previous EVPN Blog post, the next logical thing was to do is to filter out EVPN routes from the device and have them analyzed for a task.

I have made the program to analyze Type 2 and Type 3 routes

Things to take-away:

-> Understand what module has what advantages – For example OP here has route-table level calls which can extract routing information from the device, while Device has the specific usecase of opening a connection to the device.

-> Understand there are many more efficient ways of doing the same thing, but goal here is to make the script work, there is no impact on the Device as the script parses the data offline once we get it, so even if there was a better way, just do the things the way you want.

Below is the sample program which is written to analyze the routes from vQFX series

 

 

Am not a Programmer by any stretch of imagination as you can see my code ;), but this helps and gets my tasks done, if any one of you want to download this here is the below github link

https://github.com/r2079/JDC/blob/master/evpn_pyez.py

 

Regards

Rakesh M

 

 

VxLan – Short Story Lab

Leave a comment

Hi,

Note: Its perfectly possible to do VXLAN/EVPN on VQFX and VMX, all you have to do is to setup a good lab over ESXI or if you want you can do it over Eve-ng emulator. I personally did it via ESXI.

Am not covering the petty BGP configuration of Full-Mesh and Evpn-BGP configuration, its very simple, this post mainly Aims at show-casing the quick and short way of setting up EVPN/VXLAN in Vqfx and over vMX

On the way to some DC Lab Practise, I wanted to quickly show you guys how to lab up Vxlan on Vqfx and Vmx.

Intention – I was reading on VxLan and as most of my learning comes around seeing things first and understanding the later, I felt uncomfortable too soon reading at the Documentation, I wanted to learn it by doing.

Here is the topology

 

 

Goal – Build Vxlan / Evpn with a very small set-up to under the workings.

First things first

-> In order to build any VxLan, you need to have some underlay and some overlay. Our underlay is BGP (It can be anything you see, as long as it can exchange Loopback Space and establish IP connectivity between all nodes)

->Overlay – Where your Lan information is carried through a specific Control plane which you have defined.

Lets examine the underlay

 

Now lets examine the overlay

This is how you will configure Vqfx

 

Finally, the way to check.

Ping may be perfect, but we will do a check on vqfx

 

Next Post would aim to cover some Pyez aspects of verificaiton

 

Regards

Rakesh M

 

 

 

 

 

 

 

MC-LAG

12 Comments

MC-Lag

 

Everyone  mostly know what MC-Lag does, for the benefit its a variant of LAG where the Down stream Devices share LAG interface on two Physical devices instead of One, I know its confusing let see a  sample topology

 

 

Vqfx1 will see the upstream as 1 ae1 instead of two different VMX devices, this has its own advantage and the entire discussion is something out of scope of this blog post.

 

Blog Post Goal – Demonstrate MC-Lag on VMX and Quickly highlight the options Common and different in MC-LAG, a ready reference for someone going for an exam or a implementation.

 

Take-Away’s

-> ICCP is the protocol between the nodes

 

  • Uses TCP/IP to replicates control plane and forwarding traffic between peers
  • One stand-by and one active (active responsible status control)
  • ICCP messages exchange configuration information to ensure both peers use correct LACP Parameters
  • ICL-PL (interface between Mx1 and Mx2 ex) supports Multiple MC-Lag Between the peers so its recommended to be a AE.

 

-> ICL-PL HA

 

  • A Keep-alive message is exchanged between MC-LAG peers which is recommended to be the management connection
  • If ICL-PL fails, keep alive is still through the management connection and in that scenario, the stand-by brings down its local member link to avoid split-brain scenarios

 

-> MC-LAG Modes

 

  • Active/Stand-by & Active-Active (QFX Only supports Active/Active MC-LAG Mode)
  • A/A supports traffic distribution and if one link fails, the traffic will be through ICL-PL connection as ICL-PL will have all the VLANS allowed
  • All Mac-Addresses are shared among MC-LAG Peers using ICCP
  • Mcast Flooding happens on all the links if MC-LAG peers are members of VLANS associated with traffic
  • IRB routing is possible

 

Phase-1 - Setting up ICCP (ICL Peers)

Two things here

 

-> If you are operating at VMX level, if you want this to work

     – Configure Static ARP for IRB else ICCP will not establish

     – Configure LACP Session-ID else LACP will not form

     – I have seen LACP session getting initiated with different ID’s at different flaps which resulted in AE0 Flaps.

 

 

When Observed from vQFX, since its Active-standby, one interface will be attached, while the other is in distributing 

 

Values common on both the Peers

Mc-ae-id <1>

Mode active-active

lacp active

lacp admin-key <1>

lacp system-id <01:01:01:01:01:01>

 

Different on Both the peers

Chassis-id 0

Status-control active

 

Regards
Rakesh

My DC Virtual Lab Setup – Insights

1 Comment

Hi,

I have been getting a lot of requests offline and online on the lab setup I use, I have to say I have tested many things and finally settled with Vmware ESXi 5.5. Eve-ng was good but not good enough when spawned with multiple instances of qemu, maybe because my host operating system might be slow enough for it.

I will cover the connectivity for two VMX devices but the logic Remains same for any device connectivity.

What I have Already

-> Vmware Esxi5.5

-> Dell R810

-> Insane amount of time to waste :), I hope you won’t fall into the same path.

 

You need to have the OVA files, all settings are straightforward, don’t even worry about Memory allocations yet, there is time for that and also the networking part, import the OVA

There will be two OVA images

Vfp – forwarding plane

VCP – Control Plane

General import – No Rocket science – Don’t worry about any settings as of now

 

This is how my VCP looks like – Again don’t worry about any networking here, catch here – VCP has only two networking Adapters – One for Fxp0 which is the first one and the other is the internal Interface for VCP and VFP

 

 

Let’s take a look at VFP – I might have given over-exaggerated RAM but it’s completely unnecessary, I had RAM to be burnt but honestly, it doesn’t make any difference.

 

Take Away – Network Adapter 2 is the important one which connects VMX-VCP and both of them have to be on the same network, again don’t worry too much about networking now.  Rest all you get the idea once we explore the connectivity aspect

******The Most important Thing do not mix the network for Network Adapter 2 with any of the other Networking Adapters in this router or any Router for that matter, you are bound to pay a lot of time to figure out why things are not going your way.

 

Let’s explore the networking

 

The one above is the final part as you can see I have created a virtual-switch and put VCP and VFP interfaces in the virtual-switch, and there are no other interfaces present here, which should be important.

Let’s explore the data Plane interface connectivity

 

 

In this case, this connects Xe-0/0/0 to Xe-0/0/0 and thus completes the connectivity.

 

Qfx10k is almost same in implementation except for the fact that VMX Data plane interfaces start from Network Adapter 3 while QFX10K interfaces would start from Network Adapter 4.

 

Feel free to ping me if you have any queries

 

Rakesh

 

 

Older Entries Newer Entries