Home > Articles > Networking > Network Design & Architecture

  • Print
  • + Share This
This chapter is from the book

Managing System Files

Directories can be created on bootflash: and external flash memory (slot0:, usb1:, and usb2:); you can also navigate through these directories and use them for files. Files can be created and accessed on bootflash:, volatile:, slot0:, usb1:, and usb2: file systems. Files can be accessed only on the system: file systems. Debug file system can be used for debug log files specified in the debug logfile command. System image files, from remote servers using FTP, Secure Copy (SCP), Secure Shell FTP (SFTP), and TFTP can also be downloaded.

File Systems

Table 1-1 outlines the parameters for the syntax for specifying a local file system, which is:

filesystem:[//module/]

Table 1-1. Syntax for Specifying a Local File System

File System Name

Module

Description

Bootflash

sup-active

sup-local

Internal CompactFlash memory located on the active supervisor module used for storing image files, configuration files, and other miscellaneous files. The initial default directory is bootflash.

Bootflash

sup-standby

sup-remote

Internal CompactFlash memory located on the standby supervisor module used for storing image files, configuration files, and other miscellaneous files.

slot0

Not applicable

External CompactFlash memory installed in a supervisor module used for storing system images, configuration files, and other miscellaneous files.

volatile

Not applicable

Volatile random-access memory (VRAM) located on a supervisor module used for temporary or pending changes.

Nvram

Not applicable

Nonvolatile random-access memory (NVRAM) located on a supervisor module used for storing the startup-configuration file.

Log

Not applicable

Memory on the active supervisor that stores logging file statistics.

system

Not applicable

Memory on a supervisor module used for storing the running-configuration file.

debug

Not applicable

Memory on a supervisor module used for debug logs.

usb1

Not applicable

External USB flash memory installed in a supervisor module used for storing image files, configuration files, and other miscellaneous files.

usb2

Not applicable

External USB flash memory installed in a supervisor module used for storing image files, configuration files, and other miscellaneous files.

Example 1-9 demonstrates some file system commands and how to copy a file.

Example 1-9. File System Commands/Copying a File

N7010-1# dir bootflash:
        311     Jun 20 05:15:05 2009  MDS20090619155920643.lic
        309     Jun 20 05:15:56 2009  MDS20090619155929839.lic
    2470887     Aug 01 08:13:35 2009  dp42
    8533440     Apr 17 23:17:14 2009  lacp_tech_all.log
     308249     Aug 01 09:08:39 2009  libcmd.so
        134     Jun 19 23:06:53 2009  libglbp.log
        175     Jun 20 04:14:22 2009  libotm.log
      49152     Jun 19 22:50:53 2009  lost+found/
   87081184     Jan 02 06:21:20 2008  congo-s1-dk9.4.0.2.bin
   87755113     Dec 11 13:35:25 2008  congo-s1-dk9.4.0.4.bin
   92000595     Apr 16 21:55:19 2009  congo-s1-dk9.4.1.4.bin
   92645614     Apr 08 06:08:35 2009  congo-s1-dk9.4.1.5.bin
   92004757     Jun 02 04:29:19 2009  congo-s1-dk9.4.1.5E2.bin
   99851395     Aug 03 05:17:46 2009  congo-s1-dk9.4.2.0.601.bin
  100122301     Aug 12 04:42:13 2009  congo-s1-dk9.4.2.1.bin
    9905740     Jan 02 06:21:29 2008  congo-s1-epld.4.0.2.img
    9730124     Dec 11 13:42:30 2008  congo-s1-epld.4.0.4.img
   23584768     Jan 02 06:21:26 2008  congo-s1-kickstart.4.0.2.bin
   23785984     Dec 11 13:34:37 2008  congo-s1-kickstart.4.0.4.bin
   24718848     Apr 16 21:52:40 2009  congo-s1-kickstart.4.1.4.bin
   25173504     Apr 08 06:00:57 2009  congo-s1-kickstart.4.1.5.bin
   23936512     Aug 03 05:03:13 2009  congo-s1-kickstart.4.1.5E2.bin
   25333248     Aug 03 05:18:37 2009  congo-s1-kickstart.4.2.0.601.bin
   25234944     Aug 12 04:40:52 2009  congo-s1-kickstart.4.2.1.bin
      12558     Aug 01 08:51:22 2009  shrun
     916893     Apr 17 23:23:03 2009  stp_tech.og
       4096     Dec 11 14:04:50 2008  vdc_2/
       4096     Dec 11 14:04:50 2008  vdc_3/
       4096     Dec 11 14:04:50 2008  vdc_4/
     592649     Apr 17 23:18:16 2009  vpc_tech.log
        942     Jul 10 09:45:27 2009  wireshark
Usage for bootflash://sup-local
  982306816 bytes used
  827592704 bytes free
 1809899520 bytes total
N7010-1# dir bootflash://sup-remote
      12349     Dec 05 02:15:33 2008  7k-1-vdc-all.run
       4096     Apr 04 06:45:28 2009  eem/
      18180     Apr 02 23:47:26 2009  eem_script.cfg
   99851395     Aug 03 05:20:20 2009  congo-s1-dk9.4.2.0.601.bin
  100122301     Aug 12 04:46:18 2009  congo-s1-dk9.4.2.1.bin
      19021     Apr 03 21:04:50 2009  eem_script_counters.cfg
      19781     Apr 05 23:30:51 2009  eem_script_iptrack.cfg
      29104     Jun 19 22:44:51 2009  ethpm_act_logs.log
          0     Jun 19 22:44:51 2009  ethpm_syslogs.log
        175     Jun 20 04:14:37 2009  libotm.log
      49152     Jun 19 22:38:45 2009  lost+found/
   87755113     Apr 07 23:54:07 2009  congo-s1-dk9.4.0.4.bin
   92000595     Apr 16 21:55:19 2009  congo-s1-dk9.4.1.4.bin
   92645614     Apr 08 06:08:35 2009  congo-s1-dk9.4.1.5.bin
   92004757     Jun 02 04:29:19 2009  congo-s1-dk9.4.1.5E2.bin
   10993389     Mar 22 04:55:13 2009  congo-s1-epld.4.1.3.33.img
   23785984     Apr 07 23:47:43 2009  congo-s1-kickstart.4.0.4.bin
   24718848     Apr 16 21:52:40 2009  congo-s1-kickstart.4.1.4.bin
   25173504     Apr 08 06:00:57 2009  congo-s1-kickstart.4.1.5.bin
   23936512     Jun 02 04:26:35 2009  congo-s1-kickstart.4.1.5E2.bin
   25333248     Aug 03 05:19:26 2009  congo-s1-kickstart.4.2.0.601.bin
   25234944     Aug 12 04:45:24 2009  congo-s1-kickstart.4.2.1.bin
        310     Sep 19 03:58:55 2008  n7k-rhs-1.lic
      12699     Jan 23 14:02:52 2009  run_vpc_jan22
      11562     Mar 13 07:52:42 2009  startup-robert-cfg
      16008     Mar 12 02:02:40 2009  startup-vss-cfg
      17315     Mar 19 06:24:32 2009  startup-vss-cfg_roberto_mar18
         99     Apr 04 06:51:15 2009  test1
       9991     Jun 19 23:12:48 2009  vdc.cfg
       4096     Jan 22 13:37:57 2009  vdc_2/
       4096     Jan 22 00:40:57 2009  vdc_3/

       4096     Sep 11 12:54:10 2008  vdc_4/
     111096     Dec 20 04:40:17 2008  vpc.cap
          0     Feb 03 08:02:14 2009  vpc_hw_check_disable
      18166     Apr 03 03:24:22 2009  vpc_vss_apr02
      18223     Apr 02 22:40:57 2009  vss_vpc_apr2

Usage for bootflash://sup-remote
  863535104 bytes used
  946364416 bytes free
 1809899520 bytes total
N7010-1# copy bootflash://sup
bootflash://sup-1/        bootflash://sup-active/   bootflash://sup-remote/
bootflash://sup-2/        bootflash://sup-local/    bootflash://sup-standby/

N7010-1# copy bootflash://sup-local/congo-s1-epld.4.0.4.img bootflash://sup-
remote/congo-s1-epld.4.0.4.img
N7010-1# dir bootflash://sup-remote
      12349     Dec 05 02:15:33 2008  7k-1-vdc-all.run
       4096     Apr 04 06:45:28 2009  eem/
      18180     Apr 02 23:47:26 2009  eem_script.cfg
      19021     Apr 03 21:04:50 2009  eem_script_counters.cfg
      19781     Apr 05 23:30:51 2009  eem_script_iptrack.cfg
      29104     Jun 19 22:44:51 2009  ethpm_act_logs.log
          0     Jun 19 22:44:51 2009  ethpm_syslogs.log
        175     Jun 20 04:14:37 2009  libotm.log
      49152     Jun 19 22:38:45 2009  lost+found/
   87755113     Apr 07 23:54:07 2009  congo-s1-dk9.4.0.4.bin
   92000595     Apr 16 21:55:19 2009  congo-s1-dk9.4.1.4.bin
   92645614     Apr 08 06:08:35 2009  congo-s1-dk9.4.1.5.bin
   92004757     Jun 02 04:29:19 2009  congo-s1-dk9.4.1.5E2.bin
   99851395     Aug 03 05:20:20 2009  congo-s1-dk9.4.2.0.601.bin
  100122301     Aug 12 04:46:18 2009  congo-s1-dk9.4.2.1.bin
    9730124     Aug 12 22:02:57 2009  congo-s1-epld.4.0.4.img
   10993389     Mar 22 04:55:13 2009  congo-s1-epld.4.1.3.33.img
   23785984     Apr 07 23:47:43 2009  congo-s1-kickstart.4.0.4.bin
   24718848     Apr 16 21:52:40 2009  congo-s1-kickstart.4.1.4.bin
   25173504     Apr 08 06:00:57 2009  congo-s1-kickstart.4.1.5.bin
   23936512     Jun 02 04:26:35 2009  congo-s1-kickstart.4.1.5E2.bin
   25333248     Aug 03 05:19:26 2009  congo-s1-kickstart.4.2.0.601.bin
   25234944     Aug 12 04:45:24 2009  congo-s1-kickstart.4.2.1.bin
        310     Sep 19 03:58:55 2008  n7k-rhs-1.lic
      12699     Jan 23 14:02:52 2009  run_vpc_jan22
      11562     Mar 13 07:52:42 2009  startup-robert-cfg
      16008     Mar 12 02:02:40 2009  startup-vss-cfg
      17315     Mar 19 06:24:32 2009  startup-vss-cfg_roberto_mar18
         99     Apr 04 06:51:15 2009  test1

       9991     Jun 19 23:12:48 2009  vdc.cfg
       4096     Jan 22 13:37:57 2009  vdc_2/
       4096     Jan 22 00:40:57 2009  vdc_3/
       4096     Sep 11 12:54:10 2008  vdc_4/
     111096     Dec 20 04:40:17 2008  vpc.cap
          0     Feb 03 08:02:14 2009  vpc_hw_check_disable
      18166     Apr 03 03:24:22 2009  vpc_vss_apr02
      18223     Apr 02 22:40:57 2009  vss_vpc_apr2

Usage for bootflash://sup-remote
  873283584 bytes used
  936615936 bytes free
 1809899520 bytes total
N7010-1#

Configuration Files: Configuration Rollback

The configuration rollback feature enables you to take a snapshot, or checkpoint, of the Cisco NX-OS configuration and then reapply that configuration to your device at any point without having to reload the device. Rollback allows any authorized administrator to apply this checkpoint configuration without requiring expert knowledge of the features configured in the checkpoint.

You can create a checkpoint copy of the current running configuration at any time. Cisco NX-OS saves this checkpoint as an ASCII file that you can use to roll back the running configuration to the checkpoint configuration at a future time. You can create multiple checkpoints to save different versions of your running configuration.

When you roll back the running configuration, you can trigger the following rollback types:

  • Atomic: Implement the rollback only if no errors occur. This is the default rollback type.
  • Best-effort: Implement a rollback and skip any errors.
  • Stop-at-first-failure: Implement a rollback that stops if an error occurs.

When you are ready to roll back to a checkpoint configuration, you can view the changes that will be applied to your current running configuration before committing to the rollback operation. If an error occurs during the rollback operation, you can choose to cancel the operation or ignore the error and proceed with the rollback. If you cancel the operation, Cisco NX-OS provides a list of changes already applied before the error occurred. You need to clean up these changes manually.

Configuration rollback limitations are as follows:

  • Allowed to create up to ten checkpoint copies per VDC.
  • You are not allowed to apply a checkpoint file of one VDC into another VDC.
  • You are not allowed to apply a checkpoint configuration in a nondefault VDC if there is a change in the global configuration portion of the running configuration compared to the checkpoint configuration.
  • The checkpoint filenames must be 75 characters or less.
  • You are not allowed to start a checkpoint filename with the word auto.
  • You cannot name a checkpoint file with summary or any abbreviation of the word summary.
  • Only one user can perform a checkpoint, rollback, or copy the running configuration to the startup configuration at the same time in a VDC.
  • After execution of write erase and reload commands, checkpoints are deleted. You can use the clear checkpoint database command to clear out all checkpoint files.
  • Rollback fails for NetFlow if during rollback you try to modify a record that is programmed in the hardware.
  • Although rollback is not supported for checkpoints across software versions, users can perform rollback at their own discretion and can use the best-effort mode to recover from errors.
  • When checkpoints are created on bootflash, differences with the running-system configuration cannot be performed before performing the rollback, and the system reports "No Changes."

Example 1-10 demonstrates how to create a configuration rollback.

Example 1-10. Creating a Configuration Rollback

N7010-1# checkpoint changes
...........Done
N7010-1# show diff rollback-patch checkpoint changes running-config
Collecting Running-Config
Generating Rollback Patch
Rollback Patch is Empty
N7010-1# conf t
Enter configuration commands, one per line. End with CNTL/Z.
N7010-1(config)# no snmp-server user nxos-admin
N7010-1(config)# exit
N7010-1# show diff rollback-patch checkpoint changes running-config
Collecting Running-Config
Generating Rollback Patch
!!
no username nxos-admin sshkey ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAQEA6+TdX+ABH/mq1gQbfhhsjBmm65ksgfQb3Mb3qbwUbNlcAa6fjJCGdHu
f3kJ
ox/hjgPDChJOd-
kUXHjESlV59OhZP/NHlBrBq0TGRr+hfdAssD3wG5oPkywgM4+bR/ssCzoj6jVG41tGmfPip4pr3dqsMzR21
DXSK
K/tdj7bipWKy1wSkYQzZwatIVPIXRqTJY7L9a+JqVIJEA0QlJM1l0wZ5YbxccB2GKNKCM2x2BZl4okVgl80
CCJg
7vmn+8RqIOQ5jNAPNeb9kFw9nsPj/r5xFC1RcSKeQbdYAjItU6cX1TslRnKjlWewCgIa26dEaGdawMVuftg
u0uM
97VCOxZPQ==
no username nxos-admin
N7010-1# rollback running-config checkpoint changes
Note: Applying config in parallel may fail Rollback verification
Collecting Running-Config
Generating Rollback Patch
Executing Rollback Patch
Generating Running-config for verification
Generating Patch for verification
N7010-1# show snmp user nxos-admin
______________________________________________________________
                  SNMP USER
______________________________________________________________

User                          Auth  Priv(enforce) Groups
____                          ____  _____________ ______
nxos-admin                    sha   des(no)       network-operator

You can also enable specific SNMP traps:
N7010-1(config)# snmp-server enable traps eigrp
N7010-1(config)# snmp-server enable traps callhome
N7010-1(config)# snmp-server enable traps link
N7010-1(config)# exit
N7010-1#

Operating System Files

Cisco NX-OS Software consists of three images:

  • The kickstart image, contains the Linux kernel, basic drivers, and initial file system.
  • The system image contains the system software, infrastructure, Layers 4 through 7.
  • The Erasable Programmable Logic Device (EPLD) image: EPLDs are found on the Nexus 7000 currently shipping I/O modules. EPLD images are not released frequently,\; even if an EPLD image is released, the network administrator is not forced to upgrade to the new image. EPLD image upgrades for I/O modules disrupt traffic going through the I/O module. The I/O module powers down briefly during the upgrade. The EPLD image upgrades are performed one module at a time.

On the Nexus 7000 with dual-supervisor modules installed, NX-OS supports in-service software upgrades (ISSU). NX-OS ISSU upgrades are performed without disrupting data traffic. If the upgrade requires EPLD to be installed onto the line cards that causes a disruption of data traffic, the NX-OS software warns you before proceeding so that you can stop the upgrade and reschedule it to a time that minimizes the impact on your network.

NX-OS ISSU updates the following images:

  • Kickstart image
  • System image
  • Supervisor module BIOS
  • Data module image
  • Data module BIOS
  • Connectivity management processor (CMP) image
  • CMP BIOS

The ISSU process performs a certain sequence of events, as outlined here:

  1. Step 1. Upgrade the BIOS on the active and standby supervisor modules and the line cards (data cards/nonsupervisor modules).
  2. Step 2. Bring up the standby supervisor module with the new kickstart and system images.
  3. Step 3. Switch over from the active supervisor module to the upgraded standby supervisor module.
  4. Step 4. Bring up the old active supervisor module with the new kickstart image and the new system image.
  5. Step 5. Upgrade the CMP on both supervisor modules.
  6. Step 6. Perform nondisruptive image upgrade for line card (data cards/nonsupervisor modules), one at a time.
  7. Step 7. ISSU upgrade is complete.
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020