Skip to main content

Cisco-R1# reload in/at A Life Saver !

We are well aware of how tricky can our life get when we are making some changes into our network device configuration and suddenly the ssh access gets disconnected , which can be more interesting if the device is remote . We will  either need to reboot the device physically going to the location  to gain our old configuration  or be very precise by using this life saver command in Cisco devices which I will be discussing about. This mechanism provides a safeguard against inadvertent loss of connectivity between a network device and the user or management application due to configuration changes.

Scheduling a reboot prior to the configuration changes can actually be a life saver for lot of administrators around. So, if I make any errors while configuring the device and loose connectivity the device will automatically reboot after the certain set remaining time and  load back my old configuration from which I will be able to access back to my device.  Reload command in Cisco device permits a schedule reboot by making use of  "in" and "at".
  •  at : at a specific time/date.
  •  in : after a certain time interval.
Let me first talk about how we can make use of the "at" 
You can well have a look at my above snapshot where I have used "at" mentioning the specific date and time interval.  Once i confirm the time and date my router will get rebooted at that specific date and time. 

The more interesting out of two is the use of 'in' which I use it most of the time while making some major configuration changes in Cisco device remotely. The 'in' will reload the device after a certain time interval. 

The time to get reloaded can also be verified by making use of the command 'show reload'
 

The reload scheduled set can also be aborted .


There are other technique as well which I will be discussing about in my other blogs. Thank you for reading it out. Feedbacks will be well appreciated !


Comments

Post a Comment

Popular posts from this blog

SAN Switch Zoning with Brocade

Zoning in Brocade SAN Switch Let's begin with resetting the switch completely. In my environment I have two brocade SAN Switch connecting to 2 Dell R940 server configured with VMware. The SAN switch will be having connectivity between Dell Unity 500 storage and Dell R940 servers. Multipathing will be done between the server and storage with the help of SAN Switch. Multipathing, also called SAN multipathing or I/O multipathing, is the establishment of multiple physical routes between a server and the storage device that supports. It results in better fault tolerance and performance enhancement. DESIGN The idea behind zoning is that intended WWPN talk with each other . This is more like ACL in the world of Ethernet. To see the devices which are logged into the switch the following commands can be executed. SAN-A:admin> switchshow switchName: SAN-A switchType: 118.1 switchState: Online switchMode: Native switchRole: Principal switchDomain: 1 switchId: ...

Device Mapper Multipath with LVM in Oracle Linux

This blog describes you the step by step procedure for configuring multipath in liunx using Device Mapper and will also help you understanding what Device Mapper is. Simply stating Device Mapper is an interface to Linux Kernel which helps us to configure multiple I/O path between the server and the storage arrays.  Device Mapper interface allows the linux kernel to communicate with LVM Logical Volumes, EVMS Volumes , Software RAID, multipath and many other solutions. Multipathing is a must for all those mission critical applications as we all know that data is the most important thing in an enterprise network . Let me now share the installation process for multipathing. Installing Device Mapper #yum install device-mapper-multipath -y #rpm -qa | grep device-mapper Enabling Multipath #cp /usr/sare/doc/device-mapper-multipath - */multipath.conf   /etc/multipath.conf #mpathconf -enable -user_firendly_names n #modprobe dm_multipath #lsmod | grep dm_multip...

SSL Decryption FortiGate

  We have pretty much heard about SSL decryption and of malware hiding inside an encrypted traffic. A large amount of traffic in the internet is pretty much encrypted which basically means that bad things like malware, virus, ransomware can hide inside this encrypted traffic. If majority of these traffic are encrypted our Firewalls are not able to analyze these traffic which can easily infect our organization and the investment which we have done in these firewalls are wasted. There does come around a solution for this and as my topic suggest SSL Decryption also know as Deep Packet Inspection as by some IT folks. The image that I have attached down below clearly suggest about what I am trying to explain. Using deep packet inspection, the firewall simply decrypts the encrypted traffic happening  between client and server, inspects the content to find the threats and block them , then forwards it to the destination re-encrypting it . We will need to first setup the SSL/SSH in...