AB291A Fabric Clustering System Support Guide (12-port Switch), April 2004
Table Of Contents
- About This Document
- 1 Introduction to Technology
- 2 Hardware Overview
- 3 Installation Planning
- 4 Installing HP Fabric Clustering System
- 5 Administration and Management
- HP-UX Host Administration and Management
- Switch Administration and Management
- CLI Overview
- Using the CLI
- Advanced Switch Setup
- Configuration, Image, and Log Files
- Configuration, Image, and Log File Overview
- File Management
- Listing Configuration, Image, and Log Files
- Viewing Configuration Files
- Viewing Log Files
- Saving Configuration Files
- Saving for System Reboot
- Saving the Backup Configuration
- Specifying the Configuration to Use at
- Saving and Copying Files
- Downloading Files to the System
- Deleting Configuration, Image, and Log Files
- Managing Log Files
- Understanding the Log Format
- Uploading Log Files
- Administering the System
- 6 Monitoring and Troubleshooting
- A Specifications
- B HP 12-Port 4X Fabric Copper Switch Commands
- Show Commands
- show arp ethernet
- show arp IB
- show authentication
- show backplane
- show boot-config
- show card
- show card-inventory
- show clock
- show config
- show fan
- show host
- show ib
- show ib sm configuration
- show ib sm multicast
- show ib sm neighbor
- show ib sm node subnet-prefix
- show ib sm partition
- show ib sm port
- show ib sm service
- show ib sm switch
- show ib-agent channel-adapter
- show ib-agent summary
- show ib-agent switch
- show ib-agent switch linear-frd-info
- show ib-agent switch all mcast-info lid
- show ib-agent switch all node-info
- show ib-agent switch all pkey-info
- show ib-agent switch port-info
- show ib-agent switch sl-vl-map
- show ib-agent switch switch-info
- show interface ib
- show interface ib sm
- show interface ib sm statistics
- show interface mgmt-ethernet
- show interface mgmt-ib
- show interface mgmt-serial
- show ip
- show location
- show logging
- show ntp
- show power-supply
- show running-status
- show sensor
- show snmp
- show system-services
- show terminal
- show trace
- show user
- show version
- IP Commands
- HP Fabric Clustering System Commands
- Administrative Commands
- action
- boot-config
- broadcast
- card
- clock
- configure
- copy
- delete
- dir
- disable
- enable
- exec
- exit
- ftp-server enable
- gateway
- help
- history
- hostname
- install
- interface
- interface mgmt-ethernet
- interface mgmt-ib
- ip
- location
- login
- logging
- logout
- more
- ntp
- ping
- radius-server
- reload
- shutdown
- snmp-server
- telnet
- terminal length
- terminal time-out
- trace
- type
- username
- who
- write
- Show Commands
- C How to Use Windows HyperTerminal
- Glossary

Chapter 5
Administration and Management
Switch Administration and Management
72
Configuration, Image, and Log File Overview
The following sections describe how to use the important files in the HP Fabric Clustering System Switch OS
file system.
The file system uses three basic file types:
• Configuration files
• Image Files
• Log Files
Configuration Files
A configuration file is a text file that stores a list of CLI commands. The main configuration file is called
startup-config. This file stores all of the CLI commands necessary to completely configure a box from a
factory, default state. This configuration file can be copied, backed up, and modified.
Whenever configuration changes are made via the CLI, a CLI command is temporarily saved in a virtual
configuration file called running-config. If the administrator wishes to save these changes permanently,
this file is “copied” into the startup-config file.
Any number of configuration files can be stored. For convenience and rapid configuration, files can also
maintain a partial list of CLI commands. These can also be copied into running-config for immediate use or
startup-config for persistent use across reboots.
Image Files
Image files are stored in the system flash memory as a single complete file with a “.img” extension. Each
image file contains all the operating software (application software and firmware/microcode) needed by the
various cards that can be installed into the system.
The system cannot use an image file directly to boot-up to system. The image file must first be installed. The
installation process automatically unbundles the image file and distributes the software components to each
card in the system. Users do not have to be aware of individual software components. The user simply
executes one CLI command to install an image file. Information on the install command can be found at
“install” on page 266.
When an image file is installed, the image file is expanded into a “system image”. The system image is what
the user will refer to in order to specify what software version the system show use to boot-up each card in the
system.
The system only has enough flash memory to store:
• one image file (active)
• one system image (inactive)
• one recovery image
Occasionally, the user will have to manually delete either an image file or a system image from the system to
make room for new software. Detailed information on the delete command can be found at “delete” on
page 254.
• Active Image
The term “Active Image” refers to the current System Image. An installed, or “active” image has gone
through the entire upgrade process. The System-Image usually has a slash (/) in its name. Do not modify
or delete the installed system-image.










