Browse Prior Art Database

DATA CENTER SWITCHING - BACKUP AND RESTORATION OF NETWORK DEVICES USING DEVICE PERSONALITY

IP.com Disclosure Number: IPCOM000246277D
Publication Date: 2016-May-23
Document File: 7 page(s) / 32K

Publishing Venue

The IP.com Prior Art Database

Related People

Connor Lange: AUTHOR [+4]

Abstract

A method is provided to backup, restore, and deploy a given set of installed software, user data, connectivity information, and device configuration. The backup can create an archive (above) on bootflash or backup to a remote server. The restoration and deployment can be done as part of a PowerOn Auto Provisioning process, or as a standalone process.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 33% of the total text.

Page 01 of 7

DATA CENTER SWITCHING - BACKUP AND RESTORATION OF NETWORK DEVICES USING DEVICE PERSONALITY

 AUTHORS: Connor Lange Marcos Pacheco Parag Deshpande

Vishal Jain

CISCO SYSTEMS, INC.

ABSTRACT

    A method is provided to backup, restore, and deploy a given set of installed software, user data, connectivity information, and device configuration. The backup can create an archive (above) on bootflash or backup to a remote server. The restoration and deployment can be done as part of a PowerOn Auto Provisioning process, or as a standalone process.

DETAILED DESCRIPTION

     Network devices have run-time state and user data, but backing up and restoring this information is not a completely automated, all-in-one process as part of the network operating system running on the network devices. Run-time state of network devices comprises configuration, the connectivity to hosts or other switches (e.g., Cisco Discovery Protocol (CDP) neighbors) the software version and any installed third party applications. A way to back up and then eventually restore to one of the last good states of the system is needed.

    Presented herein is a technique that allows users to backup the configuration (including network connectivity information), installed software, connectivity information, and user data on a network device. The user data is tracked based on input from the user(s), since not all data on the device may be of interest. The installed software and Nexus patches are automatically detected, and meta-data about them is collected so that they can be restored later. All of the user data and meta-data, along with the running-configuration or startup-configuration, is rolled into a single archive file that the user can then use to completely restore all tracked state and user data. This archive

Copyright 2016 Cisco Systems, Inc.
1


Page 02 of 7

file may be either stored on the device's flash memory or on a remote server. The backup process can be executed manually, or as part of a scheduled action.

    As part of the restoration process, the device would either be rolled back to the last known good personality state (the standalone method), or a new device personality would be deployed. All software (software packages via Linux RPM Package Managers), installed patches (Nexus operating system patches given to customers), configuration, connectivity data, and user data are included in this restoration.

    The following is a more detailed example as it relates the NXOS operating system on a Cisco network device.

    The configuration below can be used to create a back up of the personality locally on the network device.

cal6# personality backup [filesystem:[//module/]][directory/]filename

For example, personality backup bootflash:personality1.tar

personality backup scp://root@2.1.1.1/var/lib/tftpboot/pers.tar

Switch Personality:

    The User may specify whether switch personality should be derived from running state of the system or the committed (startup) state.

    The configuration and pa...