User's Manual
Table Of Contents
- Table of Contents
- Section 1 Introduction
- 1.1 Intended Audience
- 1.2 Related Materials
- 1.3 New in this Release
- 1.4 Safety Notices
- 1.5 Sicherheitshinweise
- 1.6 Notes informatives relatives à la sécurité
- 1.7 Communications Statements
- 1.8 Laser Safety Information
- 1.9 Electrostatic Discharge Sensitivity (ESDS) Precautions
- 1.10 Accessible Parts
- 1.11 Pièces Accessibles
- 1.12 Zugängliche Teile
- 1.13 General Public License
- 1.14 Technical Support
- Section 2 General Description
- Section 3 Planning
- Section 4 Installation
- 4.1 Site Requirements
- 4.2 Installing a Switch
- 4.2.1 Mount the Switch
- 4.2.2 Install SFP Transceivers
- 4.2.3 Connect the Workstation to the Switch
- 4.2.4 Configure the Workstation
- 4.2.5 Install SANsurfer Switch Manager
- 4.2.5.1 SANsurfer Management Suite Disk - Windows Installation
- 4.2.5.2 SANsurfer Management Suite Disk - Linux Installation
- 4.2.5.3 SANsurfer Management Suite Disk - Solaris Installation
- 4.2.5.4 SANsurfer Switch Manager Installation Disk - Windows Installation
- 4.2.5.5 SANsurfer Switch Manager Installation Disk - Linux Installation
- 4.2.5.6 SANsurfer Switch Manager Installation Disk - Solaris Installation
- 4.2.6 Start SANsurfer Switch Manager
- 4.2.7 Connect the Switch to AC Power
- 4.2.8 Configure the Switch
- 4.2.9 Cable Devices to the Switch
- 4.3 Install Firmware
- 4.4 Powering Down a Switch
- Section 5 Diagnostics/Troubleshooting
- 5.1 POST Diagnostics
- 5.2 Chassis Diagnostics
- 5.3 Recovering a Switch
- 5.3.1 Maintenance - Exit
- 5.3.2 Maintenance - Image Unpack
- 5.3.3 Maintenance - Reset Network Config
- 5.3.4 Maintenance - Reset User Accounts to Default
- 5.3.5 Maintenance - Copy Log Files
- 5.3.6 Maintenance - Remove Switch Config
- 5.3.7 Maintenance - Remake Filesystem
- 5.3.8 Maintenance - Reset Switch
- 5.3.9 Maintenance - Show Firmware Versions
- 5.3.10 Maintenance - Set Active Image
- Appendix A Specifications
- Appendix B Command Line Interface
- B.1 Logging On to a Switch
- B.2 User Accounts
- B.3 Working with Switch Configurations
- B.4 Commands
- Admin Command
- Alias Command
- Config Command
- Date Command
- Fallback Command
- Hardreset Command
- Help Command
- History Command
- Hotreset Command
- Image Command
- Lip Command
- Passwd Command
- Ping Command
- Ps Command
- Quit Command
- Reset Command
- Set Command
- Set Config Command
- Set Log Command
- Set Port Command
- Set Setup Command
- Show Command
- Show Config Command
- Show Log Command
- Show Perf Command
- Show Setup Command
- Shutdown Command
- Test Command
- Uptime Command
- User Command
- Whoami Command
- Zone Command
- Zoneset Command
- Zoning Command
- Glossary
- Index

5 – Diagnostics/Troubleshooting
POST Diagnostics
5-8 59042-06 A
0
4. Display the active zone set on each switch using the Zoning Active
command or the Active Zoneset tab of the SANsurfer Switch Manager
topology display. Compare the zone membership between the two active
zone sets. Are they the same?
Yes - Contact your authorized maintenance provider.
No - Deactivate one of the active zone sets or edit the conflicting zones
so that their membership is the same. Reset the port. If the condition
remains, contact your authorized maintenance provider.
5.1.2.2
Excessive Port Errors
The switch monitors a set of port errors and generates alarms based on
user-defined sample windows and thresholds. These port errors include the
following:
CRC errors
Decode errors
ISL connection count
Login errors
Logout errors
Loss-of-signal errors
Port threshold alarm monitoring is disabled by default. Refer to the
SANbox2-8c/16 Switch Management User’s Guide for information about
managing port threshold alarms.
If the count for any of these errors exceeds the rising trigger for three consecutive
sample windows, the switch generates an alarm and disables the affected port,
changing its operational state to “down”. Port errors can be caused by the
following:
Triggers are too low or the sample window is too small
Faulty Fibre Channel port cable
Faulty SFP
Faulty port
Fault device or HBA
Note: This can be caused by merging two fabrics whose active
zone sets have two zones with the same name, but
different membership.