- Preface
- Software Licensing
- The Cisco IOS command-line interface (CLI)
- Configuring Interfaces
- Switch Alarms
- Initial Switch Configuration (IP address assignments and DHCP autoconfiguration)
- How to Setup and Use the Cisco Configuration Engine
- How to Create and Manage Switch Clusters
- Performing Switch Administration
- Configuring Precision Time Protocol (PTP)
- Configuring PROFINET
- Common Industrial Protocol (CIP)
- Configuring SDM Templates
- Configuring Switch-Based Authentication
- Configuring IEEE 802.1x Port-Based Authentication
- MACsec
- Web-Based Authentication
- Configuring Smartports Macros
- Configuring SGACL Monitor Mode and SGACL Logging
- Configuring SGT Exchange Protocol over TCP (SXP) and Layer 3 Transport
- Configuring VLANs
- VLAN Trunking Protocol (VTP)
- Configuring Voice VLAN
- How to Configure Spanning Tree Protocol (STP)
- Configuring MSTP
- Configuring Optional Spanning-Tree Features
- Configuring Resilient Ethernet Protocol
- Configuring the FlexLinks and the MAC Address-Table Move Update
- Configuring DHCP
- Dynamic Address Resolution Protocol (ARP)
- Configuring IP Source Guard
- How to Configure Internet Group Management Protocol (IGMP) and Multicast VLAN Registration (MVR)
- Configuring Port-Based Traffic Control
- Configuring LLDP, LLDP-MED, and Wired Location Service
- Configuring SPAN and RSPAN
- One-to-one (1:1) Layer 2 Network Address Translation (NAT)
- How to Configure CDP
- Configuring UniDirectional Link Detection (UDLD)
- Configuring RMON
- Configuring System Message Logging
- Configuring Simple Network Management Protocol (SNMP)
- Network Security with ACLs
- Configuring Quality of Service (QoS)
- Configuring Static IP Unicast Routing
- Configuring IPv6 Host Functions
- Configuring Link State Tracking
- Configuring IP multicast routing
- Configuring Multicast Source Discovery Protocol (MSDP)
- Configuring Multicast Listener Discovery (MLD) snooping
- Configuring HSRP and VRRP
- Configuring IPv6 access control lists (ACLs)
- Configuring Embedded Event Manager (EEM)
- IP Unicast Routing
- IPv6 Unicast Routing
- Unicast Routing Overview
- Configuring Cisco IOS IP SLAs Operations
- Configuring Dying-Gasp
- How to Configure Enhanced Object Tracking
- Configuring MODBUS TCP
- Configuring Ethernet CFM
- Working with the Flash File System
- How to Configure EtherChannels
- Troubleshooting
- How to use a Secure Digital (SD) flash memory module (SD card)
Using an SD Card
This document explains how to use a Secure Digital (SD) flash memory module (SD card).
This document contains these sections:
■
Inserting and Removing an SD Card
Overview
The SD card can be used instead of the internal flash memory of the switch to update or restore configuration settings. In addition, the SD card can be used to boot the switch. You can also copy IOS software and switch configuration settings from a PC or from the switch to the SD card, and then use the SD card to copy this software and settings to other switches.
When an SD card is formatted on the switch, the card is formatted with the Disk Operating System Filing System (DOSFS), a platform-independent industry-standard file system that is supported on various Cisco switches and routers.
The switch does not support third-party SD cards or SD High Capacity (SDHC) cards. Attempting to operate the switch with a non-supported card causes the following message to be displayed:
severely degrade performance of the system.
Please use supported SD flash cards only.
If the write-protect switch on the SD card is in the lock position, the switch can read data on the card and boot from the card, but updates and files cannot be written to the card.
Inserting and Removing an SD Card
To put an SD card in the switch, make sure that the card is oriented properly, and press it into the SD card slot on the switch until the card is seated. To remove the card, press it to release it, then pull it out of the slot.
The SD card is hot-swappable, but it should not be removed from the switch during the boot process or while sdflash write is in progress.
When an SD card is inserted, a syslog message similar to the following is logged:
When an SD card is removed, a syslog message similar to the following is logged:
SD Card Operation
The SD card can be accessed by either the switch boot-loader or by the IOS. The following sections describe the operations that can be performed by the controlling software:
Boot Loader Operation
The following boot loader commands can be executed on the SD card:
■boot—Load and boot an executable IOS image
■cat—Concatenate (type) file or files
■dir—List files in directories
■fsck—Check file system consistency
■more—Concatenate (display) file
■rmdir—Delete empty directories
■sd_init—Initialize sd flash file systems
Important: The switch can be booted from its internal flash memory or from an SD card. The SD card takes precedence over internal flash memory. If an SD card is installed in the switch, the switch attempts to boot in the following order:
1. From the IOS image that is specified in the SD card system boot path
2. From the first IOS image in the SD card
3. From the IOS image that is specified in the internal flash memory system boot path
IOS Operation
You can insert or remove an SD card while the IOS is running. If you insert a supported Cisco SD card while the IOS is running, the switch validates the Cisco embedded string in the Product Name (PNM) field and displays the product number and the flash capacity of the SD card. If you remove an SD card while the IOS is running, the switch displays a warning message to alert you that the SD card has been removed.
If syslog is enabled, the system also sends a message when the SD card is inserted or removed.
When an SD card is installed in a switch, the following IOS commands operate as described:
■ write command—Saves the running configuration. If the system boots from an SD card and you run a write command, the system saves the running configuration to the SD card, if the card is still installed. If the SD card has been removed, the system saves the running configuration to the internal flash memory and displays this message:
If the system boots from the internal flash memory and you then insert an SD card and run the write command, the system saves the running configuration to the internal flash memory.
■ boot command—Lets you change the system boot parameters.
If the system boots from an SD card and you run a boot command, the following behavior applies:
–If the SD card is installed and the system boot path or configuration file path points to the SD card, the system boot path or configuration file path is saved to the SD card
–If the SD card is installed and the system boot path or configuration file path points to the internal flash memory, the system boot path or configuration file path is saved to the internal flash memory
–If the SD card has been removed and the system boot path or configuration file path points to the SD card, the system boot path or configuration file path is not saved and the following message displays:
WARNING: The BOOT/config file path points to the
SD flash card and the SD flash card is not present.
The environment variable(s) is not saved.
NOTE: This warning message is displayed only once.
If the system boots from the internal flash memory and you then insert an SD card and run the boot command, the following behavior applies:
–If the system boot path or configuration file path points to the internal flash memory, the system boot path or configuration file path is saved to the internal flash memory
–If the system boot path or configuration file path points to the SD card, the system boot path or configuration file path is saved to the SD card and the following message is displayed:
WARNING: The BOOT/config file path points to the
SD flash card. The environment variable(s) is
saved onto the SD flash card.
NOTE: This warning message is displayed only once.
— If the SD card has been removed and the system boot path or configuration file path points to the SD card, the system boot path or configuration file path is not saved and the following message is displayed:
WARNING: The BOOT/config file path points to the
SD flash card and the SD flash card is not present.
The environment variable(s) is not saved.
NOTE: This warning message is displayed only once.
n sync command—Copies the IOS image directory (which includes the IOS image file, FPGA image files, Device Manager files, and Profinet/CIP configuration files), the config.text IOS configuration file, the vlan.dat VLAN configuration file, and IOS boot parameters from the internal flash memory to the SD card or from the SD card to the internal flash memory. This command verifies that the IOS image is appropriate for the switch model and that enough destination flash memory is present, and aborts the sync process if a potential problem is detected. The sync command obtains the source IOS image directory path and source IOS configuration files path from the IOS boot parameters on the source flash device that is specified in the sync command. By default, this command overwrites the destination IOS image directory and IOS configuration files. The “save-old-files” option can be used to override this default behavior. If the running configuration has not been saved and you run the sync command, the switch provides the option for you to save the running configuration before the command executes.
–Switch# sync flash: sdflash: —Sync IOS image directory, configuration files, and boot parameters from internal flash memory to SD card.
–Switch# sync sdflash: flash: —Sync IOS image directory, configuration files, and boot parameters from SD card to internal flash memory.
–Switch# sync flash: sdflash: ios-image-name IOS_image_path —Sync the designated IOS image directory, configuration files, and boot parameters from internal flash memory to SD card. For example, IOS_image_path might be f lash:/ie2000-universalk9-mz.150-2.EA1/ie2000-universalk9-mz.150-2.EA1.bin.
–Switch# sync sdflash: flash: ios-image-name IOS_image_path —Sync the designated IOS image directory, configuration files, and boot parameters from SD card to internal flash memory. For example, IOS_image_path might be f lash:/ie2000-universalk9-mz.150-2.EA1/ie2000-universalk9-mz.150-2.EA1.bin.
–Switch# sync flash: sdflash: skip config.text vlan.dat —Sync only IOS image directory from internal flash memory to SD card.
–Switch# sync sdflash: flash: skip config.text vlan.dat —Sync only IOS image directory from SD card to internal flash memory.
–Switch# sync flash: sdflash: skip ios-image —Sync only IOS configuration files from internal flash memory to SD card.
–Switch# sync sdflash: flash: skip ios-image —Sync only IOS configuration files from SD card to internal flash memory.
SD Card Alarms
The switch supports the following SD card alarms:
■SD Card Alarm—Enabled when the SD card is removed and cleared when the SD card is inserted
■SD Card Unsupported Alarm—Enabled when an unsupported SD card is detected
■SD Card Corrupt Alarm—Enabled when an SD card DOSFS corruption is detected
■SD Card Files Corrupt Alarm—Enabled when the IOS image specified in the SD Card system boot path is corrupted
It takes approximately 2 minutes to trigger the alarm relay (LED output) after an SD card is inserted or removed.
You also can configure alarms and traps that are associated with the SD card alarm to be sent to syslog and the SNMP server.
Enabling SD Card Alarms
SD card alarms are disabled by default.
To use alarms, enter the alarm facility sd-card enable global configuration command to enable alarms, then enter the alarm f acility sd-card global configuration commands to associate the alarm to the relay:
Switch(config)# alarm facility sd-card enable
Switch(config)# alarm facility sd-card notifies
Switch(config)# alarm facility sd-card sysm
Clearing an SD Card Alarm
To clear the last SD card alarm warning state, enter the following command:
Feedback