Skip to main content

Automation Crux

Search This Blog

Hacker Rank Free API Certification Solution #Hackerrank #API #Free #Cert...

on December 08, 2020

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Popular Posts

How to Use ngrok: Easily Share Your Local Server

This blog will help you to share your localhost server with anyone, anywhere, using ngrok to create a secure tunnel to your local machine. Demonstrating your application’s latest features to project managers or clients isn’t easy unless they’re sitting a few desks away. It may be possible to commit the changes and deploy to a public staging server, but that process can be impractical if you’re just seeking an opinion about a widget color or demonstrating the futility of their ridiculous suggestion! Ideally, you need some way to share access to your localhost server. ngrok provides that solution. We’ll show you how to set it up for any purpose, and leave you with the best ngrok alternatives (just in case). What is ngrok? Your development machine may be connected to a secure network behind a firewall. To work around access restrictions, ngrok runs a small client process on your machine which creates a private connection tunnel to the cloud service. Your localhost developme

EVE-NG Cloud NAT - Dynamically nat lab devices behind the eve primary ip

This post explains how to configure EVE-NG as a DHCP server ( isc-dhcp-server ) assigning IPs to lab devices that are then dynamically NATed behind the primary EVE management IP address ( iptables masquerade ) to provide Internet breakout. EVE has 10 bridges that are associated on a one-to-one basis to each physical NIC or vNIC. In the CLI these are called PNETs and in the GUI clouds. For example, cloud0 is mapped to pnet0 that is associated to eth0 which is the management NIC you use to connect to EVE. root@hme-ubt-eve01:~# brctl show bridge name bridge id STP enabled interfaces pnet0 8000.005056a39b79 no eth0 pnet1 8000.005056a34db2 no eth1 pnet2 8000.005056a346b5 no eth2 pnet3 8000.000000000000 no pnet4 8000.000000000000 no pnet5 8000.000000000000 no pnet6 8000.000000000000 no pnet7 8000.000000000000 no pnet8 8000.000000000000 no pnet

Automating upgrade of Cisco Switches using Ansible

What's a Challenge ??? Upgrading 1–15 switches can be done manually. But what about 250+ switches including different models and versions? it is challenging and time-consuming. A simple humane error can cause troubleshooting for many hours. This post will explain the procedure and steps to automate this process using Ansible. At the end of this implementation, the following benefits can be achieved, Automated verifications Reduced engineering hours and involvement No need manual interventions Automated configuration backup Scalable inventory for future automation Build your inventory first… Before everything, an inventory supported for Ansible should be developed for the infrastructure. Here following YAML template is used to build the inventory. all: children: switches: children: Prod_Sites: Prod_Sites: children: ABC: DEF: GHI: vars: ansible_connection: network_cli ansible_network_os: ios

Powered by Blogger