Connectrix DS-24M2 Fibre Channel Switch User Guide · Connectrix DS-24M2 User Guide iii Laser Compliance Statement Laser transceivers used in the DS-24M2 are tested and certified

Connectrix DS-24M2Fibre Channel Switch

USER GUIDEP/N 069001203

REV A02

EMC CorporationCorporate Headquarters: Hopkinton, MA 01748-9103(800) 424-EMC2http://www.EMC.com

ii

Copyright © 2002, 2003 EMC Corporation. All rights reserved.Printed April 2003

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

Regulatory Agency Information

Connectrix systems have been extensively tested and certified to meet UL1950, CSA 22.2 No 950, IEC 60950/EN60950; Safety of Information Technology Equipment including Electrical Business Equipment, FCC Rules Part 15 Subpart B; CISPR22 Class A; European EMC Directive 89/336/EEC on, electromagnetic compatibility. The Connectrix DS-24M2 is a Stationary Pluggable Type B system.This class A digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.Warning! This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.Achtung!Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.Attention!Ceci est un produit de Classe A. Dans un environnement domestique, ce produit risque de créer des interférences radioélectriques, il appartiendra alors à l'utilisateur de prendre les mesures spécifiques appropriées.

This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules, which are designed to provide reasonable protection against such radio frequency interference.Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference.Any modifications to this device - unless expressly approved by the manufacturer - can void the user’s authority to operate this equipment under part 15 of the FCC rules.

Connectrix DS-24M2 User Guide

Laser Compliance Statement

Laser transceivers used in the DS-24M2 are tested and certified in the United States to conform to Title 21 of the Code of Federal Regulations (CFR), Subchapter J, Parts 1040.10 and 1040.11 for Class 1 laser products. Elsewhere, the transceivers are tested and certified to be compliant with International Electrotechnical Commission IEC825-1 and European Norm EN60825-1 and EN60825-2 regulations for Class 1 laser products.Class 1 laser products are not considered hazardous. The transceivers are designed such that there is never human access to laser radiation above a Class 1 level during normal operation or prescribed maintenance conditions.

Trademark Information

Connectrix DS-24M2 User Guide iii

iv

Contents

Preface........................................................................................................................... xxi

Warnings and Cautions ...................................................................................... xxvii

Chapter 1 Switch Operating FeaturesOverview........................................................................................... 1-2DS-24M2 Description ...................................................................... 1-3

FlexPort Feature ........................................................................ 1-3Other Features ........................................................................... 1-3Front Panel................................................................................. 1-4CTP ............................................................................................. 1-6Rear Panel .................................................................................. 1-6

Connectrix Service Processor ......................................................... 1-8Embedded Web Server............................................................. 1-8

Hardware Features .......................................................................... 1-9Performance Features............................................................... 1-9Switch Management............................................................... 1-10High-Availability Features .................................................... 1-11Connectivity Features ............................................................ 1-12Security Features..................................................................... 1-12Serviceability Features ........................................................... 1-13

Hardware Operations.................................................................... 1-15Updating Firmware................................................................ 1-15Switch Operational States...................................................... 1-15IML............................................................................................ 1-16IPL ............................................................................................. 1-17

Connectrix DS-24M2 User Guide v

Contents

Chapter 2 Operating the SwitchPower Procedures ............................................................................ 2-2

Power the Switch On ............................................................... 2-2FRU LEDs and Connectors............................................................. 2-4

LEDs ........................................................................................... 2-4Connectors................................................................................. 2-6

Chapter 3 Product Manager OverviewProduct Manager Overview........................................................... 3-2Using the Product Manager ........................................................... 3-5

Using Dialog Boxes .................................................................. 3-5Logging Into the Connectrix Manager .................................. 3-6Opening the Product Manager ............................................. 3-10Closing the Product Manager ............................................... 3-11Closing the Connectrix Manager.......................................... 3-11

Product Manager Menu Bar......................................................... 3-12Product Manager Views................................................................ 3-17

Hardware View....................................................................... 3-17Port List View.......................................................................... 3-18Node List View ....................................................................... 3-19Performance View .................................................................. 3-20FRU List View ......................................................................... 3-20

User Rights ..................................................................................... 3-21User Rights for Specific Functions ....................................... 3-22

Chapter 4 Monitoring and Managing the SwitchUsing the Hardware View.............................................................. 4-2

Identifying FRUs ...................................................................... 4-2Monitoring Switch Operation................................................. 4-2Obtaining Hardware Information.......................................... 4-9Using Menu Options.............................................................. 4-14

Using the Port List View............................................................... 4-17Displaying Port Properties .................................................... 4-19Menu Options ......................................................................... 4-19

Using the Node List View............................................................. 4-21Displaying Node Properties.................................................. 4-23Displaying Port Properties .................................................... 4-23Defining Nicknames .............................................................. 4-24

Using the Performance View ....................................................... 4-25Bar Graph Display.................................................................. 4-26Port Statistics ........................................................................... 4-27

Connectrix DS-24M2 User Guidevi

Contents

Menu Options......................................................................... 4-31Using the FRU List View.............................................................. 4-33Port Operational States................................................................. 4-35Alerts............................................................................................... 4-37

Link Incident Alerts ............................................................... 4-37Threshold Alerts..................................................................... 4-38

Chapter 5 Configuring the SwitchConfiguring Switch Identification ................................................ 5-2Configuring Operating Parameters.............................................. 5-4

Switch Parameters.................................................................... 5-5Fabric Parameters..................................................................... 5-8

Configuring Switch Binding........................................................ 5-12Activating Switch Binding and Selecting Port Types ....... 5-12Editing the Switch Membership List................................... 5-14Switch Binding: Rules and Guidelines ............................... 5-15Zoning with Switch Binding Enabled................................. 5-16

Configuring Ports.......................................................................... 5-17Port Parameters ...................................................................... 5-19Adding FlexPorts ................................................................... 5-22Configuring Port Binding ..................................................... 5-22

Configuring the SNMP Agent..................................................... 5-24Configuring Management Server Control................................. 5-27Configuring Feature Keys............................................................ 5-28Configuring the Date and Time .................................................. 5-31Configuring Threshold Alerts ..................................................... 5-33

Creating New Alerts.............................................................. 5-34Modifying Alerts.................................................................... 5-39Activating or Deactivating Alerts........................................ 5-40Deleting Alerts........................................................................ 5-40

Exporting a Configuration Report.............................................. 5-41Report Data ............................................................................. 5-41Export Procedure ................................................................... 5-41

Enabling the Embedded Web Server.......................................... 5-43Enabling Telnet .............................................................................. 5-44

Chapter 6 Using LogsUsing Logs........................................................................................ 6-2

Button Function........................................................................ 6-2Expanding Columns................................................................ 6-3Sorting Entries .......................................................................... 6-3

viiConnectrix DS-24M2 User Guide

Contents

Audit Log.......................................................................................... 6-4Event Log .......................................................................................... 6-6Hardware Log .................................................................................. 6-8Link Incident Log............................................................................. 6-9Threshold Alert Log ...................................................................... 6-11

Chapter 7 Using Maintenance FeaturesRunning Port Diagnostics............................................................... 7-2Collecting Maintenance Data......................................................... 7-3Executing an IPL .............................................................................. 7-4Setting the Online State................................................................... 7-6Managing Firmware Versions........................................................ 7-7Enabling E-Mail Notification ......................................................... 7-8Enabling Call-Home Notification.................................................. 7-9Backing Up and Restoring the Configuration ........................... 7-10

Backup...................................................................................... 7-11Restore...................................................................................... 7-11Automatic Backup to Zip Disk ............................................. 7-12Using QuikSync ...................................................................... 7-14

Resetting the Configuration ......................................................... 7-16Note on IP Address ................................................................ 7-16Procedure................................................................................. 7-16

Appendix A Using SNMP to Manage the SwitchIntroduction .................................................................................... A-2

Supported MIBs....................................................................... A-2SNMP Tree Structure............................................................... A-3SNMP Commands................................................................... A-4Traps .......................................................................................... A-4Protocol Definition .................................................................. A-5Configuring an SNMP Agent ................................................ A-5V7.01 MIB Support .................................................................. A-5

MIB-II Support ............................................................................... A-7The System Group................................................................... A-8The Interfaces Group .............................................................. A-9The Address Translation Group/Table .............................. A-13The IP Group.......................................................................... A-14The ICMP Group ................................................................... A-20The TCP Group...................................................................... A-22The UDP Group ..................................................................... A-25The SNMP Group .................................................................. A-26

Connectrix DS-24M2 User Guideviii

Contents

Fabric Element MIB Support ..................................................... A-29Predefined Types................................................................... A-30MIB Objects Defined in the Fabric Element MIB.............. A-32Module Table ......................................................................... A-32FxPort Configuration Table ................................................. A-34FxPort Operation Table ........................................................ A-37FxPort Physical Level Table................................................. A-38FxPort Fabric Login Table .................................................... A-40FxPort Error Table ................................................................. A-43Class 1 Accounting Table ..................................................... A-44Class 2 Accounting Table ..................................................... A-44Class 3 Accounting Table ..................................................... A-45FxPort Capability Table........................................................ A-46

Fibre Alliance MIB (fcmgmt.mib) ............................................. A-49Type Definitions .................................................................... A-49Connectivity Unit Group ..................................................... A-50fcConnUnitTable ................................................................... A-51Firmware Table...................................................................... A-57Sensor Table ........................................................................... A-58The Port Table........................................................................ A-60The Event Table ..................................................................... A-69Link Table ............................................................................... A-71Port Statistics Table ............................................................... A-74Name Server Table ................................................................ A-81Trap Registration Group...................................................... A-83The TrapRegTable ................................................................. A-83Trap Types .............................................................................. A-85

Connectrix Private Enterprise MIB (fceos.mib) ...................... A-86System Group ........................................................................ A-88FRU Table (Module Group)................................................. A-90Port Table (Port Group) ....................................................... A-91Port Binding Table ................................................................ A-96Zoning Variables ................................................................... A-96Active Zone Table ................................................................. A-97Active Member Table ........................................................... A-97Threshold Alert Table........................................................... A-98Enterprise Specific Traps ..................................................... A-99Port State Descriptions ....................................................... A-100

ixConnectrix DS-24M2 User Guide

Contents

Appendix B Configuring Network AddressesConfiguring Network Addresses ................................................ B-2

Appendix C Configuring the Switch from the Embedded Web ServerIntroduction .................................................................................... C-2

Management Support — Connectrix Manager vs. Embedded Web Server ............................................................................... C-3Required Browsers .................................................................. C-5Opening the Web Server Application................................... C-5

Configuring Switch Ports ............................................................. C-7Configuring Switch Identification ............................................... C-9Configuring the Date and Time ................................................. C-11Configuring Switch Parameters ................................................ C-12Configuring Fabric Parameters ................................................. C-14Configuring Network Information ........................................... C-17Configuring Management .......................................................... C-19

Configuring SNMP Trap Message Recipients ................... C-19Enabling/Disabling the CLI ................................................ C-21Configuring the Open Systems Management Server....... C-21

Configuring Zoning .................................................................... C-22Configuring User Names and Passwords ................................ C-25Configuring Port Binding ........................................................... C-26Configuring Feature Keys .......................................................... C-28

Appendix D Command Line InterfaceTelnet Sessions ................................................................................ D-2

Ethernet Connection Loss ...................................................... D-2CLI Overview ................................................................................. D-3

Entering CLI Commands ....................................................... D-4login......................................................................................... D-11logout ...................................................................................... D-12commaDelim .......................................................................... D-13Handling Command Line Interface Errors........................ D-14Using CLI Help ...................................................................... D-14Commenting Scripts.............................................................. D-15

The config Branch ........................................................................ D-16config.enterpriseFabMode.setState..................................... D-16config.features.installKey..................................................... D-17config.features.enterpriseFabMode .................................... D-17config.features.openSysMS .................................................. D-18config.features.show ............................................................. D-18

Connectrix DS-24M2 User Guidex

Contents

config.ip.ethernet .................................................................. D-19config.ip.show ....................................................................... D-20config.port.blocked ............................................................... D-20config.port.name ................................................................... D-21config.port.speed................................................................... D-21config.port.type ..................................................................... D-22config.port.show ................................................................... D-23config.openSysMS.setState .................................................. D-23config.security.FabricBinding ............................................. D-24config.security.fabricBinding.activatePending................. D-24config.security.fabricBinding.addMember ....................... D-25config.security.fabricBinding.clearMemList ..................... D-25config.security.fabricBinding.deleteMember.................... D-26config.security.fabricBinding.replacePending.................. D-26config.security.fabricbinding.setState................................ D-27config.security.fabricBinding.showActive ........................ D-28config.security.fabricBinding.showPending..................... D-28config.security.portBinding.bound .................................... D-29config.security.portBinding.wwn....................................... D-30config.security.portBinding.show ...................................... D-31config.security.switchBinding.addMember...................... D-32config.security.switchBinding.deleteMember .................. D-32config.security.switchBinding.setState .............................. D-33config.security.switchBinding.show .................................. D-35config.security.userRights.administrator .......................... D-35config.security.userRights.operator ................................... D-36config.security.userRights.show......................................... D-37config.snmp.addCommunity .............................................. D-37config.snmp.authTraps ........................................................ D-38config.snmp.deleteCommunity .......................................... D-39config.snmp.show................................................................. D-39config.switch.......................................................................... D-40config.switch.domainRSCN ................................................ D-40config.switch.insistDomainId ............................................. D-41config.switch.edTOV............................................................ D-41config.switch.interopMode.................................................. D-42config.switch.prefDomainId................................................ D-42config.switch.priority ........................................................... D-43config.switch.raTOV............................................................. D-44config.switch.rerouteDelay.................................................. D-44config.switch.show ............................................................... D-45config.switch.zoningRSCN.................................................. D-46config.system.contact ........................................................... D-47

xiConnectrix DS-24M2 User Guide

Contents

config.system.date................................................................. D-48config.system.description..................................................... D-48config.system.location .......................................................... D-49config.system.name............................................................... D-49config.system.show ............................................................... D-49config.zoning.......................................................................... D-50config.zoning.setDefZoneState............................................ D-50config.zoning.activateZoneSet............................................. D-51config.zoning.deactivateZoneSet ........................................ D-51config.zoning.replaceZoneSet.............................................. D-51config.zoning.clearZoneSet.................................................. D-52config.zoning.addZone......................................................... D-52config.zoning.deleteZone..................................................... D-53config.zoning.renameZoneSet ............................................. D-53config.zoning.addWwnMem............................................... D-54config.zoning.addPortMem ................................................. D-54config.zoning.clearZone ....................................................... D-55config.zoning.deleteWwnMem ........................................... D-55config.zoning.deletePortMem ............................................. D-56config.zoning.renameZone .................................................. D-56config.zoning.showPending ................................................ D-57config.zoning.showActive.................................................... D-57

maint .............................................................................................. D-59maint.port.beacon.................................................................. D-59maint.port.reset...................................................................... D-59maint.system.beacon............................................................. D-60maint.system.clearSysError ................................................. D-60maint.system.ipl..................................................................... D-61maint.system.resetConfig..................................................... D-61maint.system.setOnlineState................................................ D-61

perf ................................................................................................. D-63perf.class2 ............................................................................... D-63perf.class3 ............................................................................... D-64perf.clearStats ......................................................................... D-65perf.errors ............................................................................... D-66perf.link................................................................................... D-67perf.thresholdAlerts .............................................................. D-68perf.thresholdAlerts.counter.addAlert............................... D-70perf.thresholdAlerts.counter.addPort ................................ D-71perf.thresholdAlerts.counter.deleteAlert........................... D-72perf.thresholdAlerts.counter.removePort.......................... D-72perf.thresholdAlerts.counter.setCounter ........................... D-73perf.thresholdAlerts.counter.setParams ............................ D-73

Connectrix DS-24M2 User Guidexii

Contents

perf.thresholdAlerts.counter.show .................................... D-75perf.ThreshAlerts.counter.showStatisticTable.................. D-75perf.thresholdAlerts.setState ............................................... D-76perf.traffic............................................................................... D-77

show .............................................................................................. D-78show.eventLog ...................................................................... D-78show.features......................................................................... D-79show.frus................................................................................ D-80show.ip.ethernet.................................................................... D-81show.loginServer .................................................................. D-82show.nameServer.................................................................. D-83show.nameServerExt ............................................................ D-85sshow.port.config.................................................................. D-86show.port.info ....................................................................... D-87show.port.status .................................................................... D-88show.port.technology........................................................... D-91show.security.fabricBinding................................................ D-92show.security.portBinding .................................................. D-92show.security.switchBinding .............................................. D-93show.switch ........................................................................... D-94show.system........................................................................... D-96show.thresholdAlerts.alert .................................................. D-97show.thresholdAlerts.log..................................................... D-99show.zoning......................................................................... D-100

Appendix E SpecificationsSpecifications .................................................................................. E-2

Appendix F Customer SupportOverview of Detecting and Resolving Problems ....................... F-2Troubleshooting the Problem ....................................................... F-3Before Calling the Customer Support Center ............................ F-4Documenting the Problem ............................................................ F-5Reporting a New Problem ............................................................ F-6Sending Problem Documentation ................................................ F-7

Glossary........................................................................................................................ g-1

Index ............................................................................................................................... i-1

xiiiConnectrix DS-24M2 User Guide

Contents

Connectrix DS-24M2 User Guidexiv

Figures

1-1 DS-24M2, Front View ................................................................................... 1-41-2 DS-24M2, Rear View .................................................................................... 1-61-3 Switch Management ................................................................................... 1-112-1 AC Power Cords ........................................................................................... 2-22-2 Front Panel LEDs and Connectors ............................................................. 2-42-3 Rear Panel LEDs and Connectors .............................................................. 2-43-1 Connectrix Service Processor and Remote Workstation Configuration 3-43-2 Typical Dialog Box ....................................................................................... 3-53-3 Connectrix Manager Login Window ......................................................... 3-73-4 Connectrix Manager Products View .......................................................... 3-83-5 Product Manager Window ........................................................................ 3-103-6 Product Manager Menu Bar ...................................................................... 3-123-7 Product Manager View Selector Tabs ..................................................... 3-173-8 Product Manager Hardware View ........................................................... 3-174-1 Monitoring Hardware Operation Using the Hardware View ............... 4-64-2 Clear Threshold Alert(s) Window ........................................................... 4-164-3 Port List View .............................................................................................. 4-174-4 Clear Threshold Alert(s) Window ........................................................... 4-204-5 Node List View ........................................................................................... 4-214-6 Define Nickname Dialog Box ................................................................... 4-244-7 Performance View ...................................................................................... 4-254-8 Clear Threshold Alert(s) Window ........................................................... 4-324-9 FRU List View ............................................................................................. 4-334-10 Clear Link Incident Alert Window .......................................................... 4-385-1 Configure Identification Dialog Box .......................................................... 5-25-2 Set Online State Window ............................................................................. 5-45-3 Configure Switch Parameters Dialog Box ................................................. 5-55-4 Configure Fabric Parameters Dialog Box .................................................. 5-85-5 Switch Binding — State Change Dialog Box .......................................... 5-125-6 Switch Binding — Membership List ........................................................ 5-14

Connectrix DS-24M2 User Guide xv

xv

Figures

5-7 DS-24M2 Port Numbering ......................................................................... 5-175-8 Configure Ports Dialog Box ....................................................................... 5-175-9 Bound WWN Mismatch Warning ............................................................ 5-185-10 Bind WWN Dialog Box .............................................................................. 5-225-11 Configure SNMP Dialog Box ..................................................................... 5-255-12 Configure Open Systems Management Server Window ...................... 5-275-13 Set Online State Window ........................................................................... 5-285-14 Configure Feature Key Window ............................................................... 5-295-15 New Feature Key Dialog Box .................................................................... 5-295-16 Enable Feature Key Dialog Box ................................................................. 5-305-17 Configure Date and Time Dialog Box ...................................................... 5-315-18 Configure Threshold Alerts Window ...................................................... 5-345-19 New Threshold Alerts Window — First Screen ..................................... 5-355-20 New Threshold Alerts Window — Second Screen ................................ 5-365-21 New Threshold Alerts Window — Third Screen ................................... 5-375-22 New Threshold Alerts Window — Summary Screen ............................ 5-385-23 Configure Threshold Alerts Window — Activate Alert ....................... 5-395-24 Export Configuration Report Window .................................................... 5-426-1 Save Window ................................................................................................. 6-26-2 Audit Log ....................................................................................................... 6-46-3 Event Log ........................................................................................................ 6-66-4 Hardware Log ................................................................................................ 6-86-5 Link Incident Log .......................................................................................... 6-96-6 Threshold Alert Log .................................................................................... 6-117-1 Set Online State Window ............................................................................. 7-67-2 Backup and Restore Configuration Window .......................................... 7-117-3 QuikSync Icon in Windows System Tray ................................................ 7-147-4 Iomega QuikSync Dialog Box .................................................................... 7-147-5 Iomega QuikSync Dialog Box (Advanced Tab) ...................................... 7-15A-1 MIB Tree ........................................................................................................ A-3A-2 SNMP MIB-II Support ................................................................................. A-7A-3 Fibre Channel Fabric Element MIB Supported ...................................... A-29A-4 Private Enterprise MIB Support ............................................................... A-86B-1 Connection Description Dialog Box .......................................................... B-3B-2 Connect To Dialog Box ................................................................................ B-4B-3 Com 1, 2 Properties Dialog Box ................................................................. B-4B-4 HyperTerminal Window ............................................................................. B-5C-1 User Name and Password Dialog Box ...................................................... C-5C-2 Embedded Web Server — View Window ................................................ C-6C-3 Embedded Web Server— Configure Ports Window .............................. C-7C-4 Embedded Web Server — Configure Switch Identification .................. C-9C-5 Embedded Web Server — Configure Switch Date/Time .................... C-11C-6 Embedded Web Server — Configure Switch Parameters .................... C-12

i Connectrix DS-24M2 User Guide

Figures

C-7 Embedded Web Server — Configure Fabric Parameters ..................... C-15C-8 Embedded Web Server — Configure Switch Network ........................ C-17C-9 Embedded Web Server — Configure SNMP .......................................... C-20C-10 CLI Enabled/Disabled Message .............................................................. C-21C-11 Embedded Web Server — Configure Zone Set ...................................... C-22C-12 Embeded Web Server — Configure Zone ............................................... C-23C-13 Embedded Web Server — Modify Zone ................................................. C-24C-14 Embedded Web Server — Configure Security ....................................... C-25C-15 Embedded Web Server — Configure Port Binding ............................... C-27C-16 Embedded Web Server — Feature Installation ...................................... C-29F-1 Problem Detection and Resolution Process .............................................. F-2

Connectrix DS-24M2 User Guide xvii

Figures

xviii Connectrix DS-24M2 User Guide

Tables

2-1 LEDs ............................................................................................................... 2-52-2 Connectors ..................................................................................................... 2-63-1 User Rights for Product Manager Functions .......................................... 3-224-1 Operating Status - Alert Panel and Switch Status ................................... 4-54-2 Legend for Figure 4-1 ................................................................................... 4-74-3 Port States .................................................................................................... 4-357-1 Data Default Values ................................................................................... 7-17A-1 System Group ............................................................................................... A-8A-2 Interfaces Group .......................................................................................... A-9A-3 Interfaces Table ............................................................................................ A-9A-4 Address Translation Table ....................................................................... A-13A-5 IP Group Table ........................................................................................... A-14A-6 IP Address Table ........................................................................................ A-16A-7 IP Routing Table ........................................................................................ A-16A-8 IP Address Translation Table .................................................................. A-19A-9 Additional IP Objects ................................................................................ A-19A-10 ICMP Group Table .................................................................................... A-20A-11 TCP Group Table ....................................................................................... A-22A-12 TCP Connection Table .............................................................................. A-24A-13 Additional TCP Objects ............................................................................ A-25A-14 UDP Group ................................................................................................. A-25A-15 UDP Listener Table ................................................................................... A-25A-16 SNMP Group .............................................................................................. A-26A-17 Fabric Element Management MIB: Predefined Types ......................... A-30A-18 Fabric Element MIB Objects ..................................................................... A-32A-19 Fabric Element MIB Modules .................................................................. A-32A-20 FxPort Configuration Table ..................................................................... A-34A-21 FxPort Operation Table ............................................................................ A-37A-22 FxPort Physical Level Table ..................................................................... A-38A-23 FxPort Fabric Login Table ........................................................................ A-40

Connectrix DS-24M2 User Guide xix

Tables

xx

A-24 FxPort Error Table ..................................................................................... A-43A-25 Class 2 Accounting Table ......................................................................... A-44A-26 Class 3 Accounting Table ......................................................................... A-45A-27 FxPort Capacity Table ............................................................................... A-46A-28 FibreAlliance MIB Type Definitions ....................................................... A-49A-29 Connectivity Unit Group ......................................................................... A-50A-30 fcConnUnitTable ....................................................................................... A-51A-31 Firmware Table .......................................................................................... A-57A-32 Sensor Table ............................................................................................... A-58A-33 Port Table .................................................................................................... A-60A-34 Event Table ................................................................................................. A-69A-35 Link Table ................................................................................................... A-72A-36 Port Statistics Table ................................................................................... A-74A-37 Name Server Table .................................................................................... A-81A-38 Trap Registration Group .......................................................................... A-83A-39 Trap Registration Table ............................................................................ A-83A-40 Trap Types .................................................................................................. A-85A-41 Private Enterprise MIB Table .................................................................. A-87A-42 System Group Variables ........................................................................... A-88A-43 FRU Table ................................................................................................... A-90A-44 Port Table .................................................................................................... A-91A-45 Port Binding Table .................................................................................... A-96A-46 Zoning Variables ....................................................................................... A-96A-47 Active Zone Table ..................................................................................... A-97A-48 Active Zone Member Table ..................................................................... A-97A-49 Threshold Alert Table ............................................................................... A-98A-50 Enterprise-Specific Traps ......................................................................... A-99A-51 Port State Descriptions ........................................................................... A-100C-1 Management Support Table ....................................................................... C-3D-1 CLI Command Tree Navigation Conventions ........................................ D-5D-2 CLI Command Tree .................................................................................... D-6D-3 Threshold Alert Counters ........................................................................ D-690-1 E-20-2 E-20-3 E-30-4 E-30-5 E-40-6 E-4


Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the Connectrix product line, EMC periodically releases new versions of hardware and software. Therefore, some functions described in this guide may not be supported by all versions of Connectrix currently in use.

If your Connectrix unit does not offer a function described in this guide, please contact your EMC representative for a hardware, software, or microcode update.

Audience This Guide describes how to operate and manage the Connectrix DS-24M2 fabric switch. It is intended for data center administrators, LAN administrators, operations personnel, and customer support personnel who must monitor and manage product operation.

Organization This publication is organized as follows:

◆ Chapter 1, Switch Operating Features, describes switch hardware components and their operating features. It also describes management and serviceability features available on the switches through such network components as the Connectrix service processor, user workstations, and SNMP management stations.

◆ Chapter 2, Operating the Switch, provides procedures for using the switch operator panel, using hardware LEDs, and switching the unit power off and on.

◆ Chapter 3, Product Manager Overview, provides an introduction and overview of the DS-24M2 Product Manager. It is intended as a quick reference for using features available through the main Product Manager window.

Connectrix DS-24M2 User Guide xxi

xxii

Preface

◆ Chapter 4, Monitoring and Managing the Switch, describes how to monitor and manage DS-24M2 operation using the Product Manager. This includes status indicators, menu options, dialog boxes, and performance and error data available through the Hardware View, Port List View, FRU List View, Node List View, and Performance View.

◆ Chapter 5, Configuring the Switch, describes how to use the options available through the Product Manager Configure menu.

◆ Chapter 6, Using Logs, describes the log options that are available through the Product Manager Logs menu.

◆ Chapter 7, Using Maintenance Features, describes how to use the options available through the Product Manager Maintenance menu.

◆ Appendix A, Using SNMP to Manage the Switch, provides details on SNMP support for the DS-24M2 and provides a list of MIB and SNMP trap definitions.

◆ Appendix B, Configuring Network Addresses, describes the procedure for configuring unique addresses for each switch.

◆ Appendix C, Configuring the Switch from the Embedded Web Server, describes the procedure for configuring the DS-24M2 from the Embedded Web Server.

◆ Appendix D, Command Line Interface, describes the commands that an administrator or operator can enter over a Telnet session, as an alternative to using the Connectrix Manager or Embedded Web Server.

◆ Appendix E, Specifications, lists the physical characteristics and operating environment of the DS-24M2.

◆ Appendix F, Customer Support, describes the EMC process for detecting and resolving software problems, and provides essential questions that you should answer before contacting the EMC Customer Support Center.

◆ The Glossary defines terms, abbreviations, and acronyms used in this manual.

◆ An Index also provided.


Preface

RelatedDocumentation

Related documents include:

◆ Connectrix Manager v7.01 User Guide, P/N 069001219

◆ Connectrix v7.01 Enterprise Storage Network System Planning Guide, P/N 069001218

◆ Connectrix DS-16M Fibre Channel Switch User Guide, P/N 069001080

◆ Connectrix DS-16M2 Fibre Channel Switch User Guide, P/N 069001205

◆ Connectrix DS-32M Fibre Channel Switch User Guide, P/N 069001081

◆ Connectrix DS-32M2 Fibre Channel Switch User Guide, P/N 069001206

◆ Connectrix ED-64M Fibre Channel Director User Guide, P/N 069001096

◆ Connectrix ED-64M 2 Gb Fibre Channel Director User Guide, P/N 069001204

◆ Connectrix ED-140M Fibre Channel Director User Guide, P/N 069001202

Conventions Used inthis Guide

EMC uses the following conventions for notes, cautions, and warnings.

A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.

WARNING

A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the message.

Connectrix DS-24M2 User Guide xxiii

xxiv

Preface

Typographical ConventionsEMC uses the following type style conventions in this guide:

Where to Get Help For questions about technical support, call your local sales office or service provider.

If you have a valid EMC service contract, contact EMC Customer Service at:

Follow the voice menu prompts to open a service call and select the applicable product support.

AVANT GARDE Keystrokes

Palatino,bold

◆ Dialog box, button, icon, and menu items in text◆ Selections you can make from the user interface,

including buttons, icons, options, and field names

Palatino,italic

◆ New terms or unique word usage in text ◆ Command line arguments when used in text◆ Book titles

Courier, italic

Arguments used in examples of command line syntax.

Courier System prompts and displays and specific filenames or complete paths. For example:

working root directory [/user/emc]:

c:\Program Files\EMC\Symapi\db

Courier, bold

◆ User entry. For example:symmpoll -p

◆ Options in command line syntax

United States: (800) 782-4362 (SVC-4EMC)

Canada: (800) 543-4782 (543-4SVC)

Worldwide: (508) 497-7901


Preface

Sales and CustomerService Contacts

For the list of EMC sales locations, please access the EMC home page at:

http://www.EMC.com/contact/

For additional information on the EMC products and services available to customers and partners, refer to the EMC Powerlink Web site at:

http://powerlink.EMC.com

Your Comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a message to [email protected] with your opinions of this guide.

Connectrix DS-24M2 User Guide xxv

xxvi

Preface


The following warnings and cautions pertain throughout this guide.

WARNING Trained service personnel only.

This EMC product has more than one power supply cord. To reduce the risk of electric shock, disconnect all power supply cords before servicing.

Ground circuit continuity is vital for safe operation of the machine. Never operate the machine with grounding conductors disconnected. Remember to reconnect any grounding conductors removed for or during any installation procedure.

ATTENTION Resérvé au personnel autorisé.

Cet appareil EMC comporte plus d'un cordon d'alimentation. Afin de prévenir les chocs électriques, débranchez tous les cordons d'alimentation avant de faire le dépannage.

Un circuit de terre continu est essentiel en vue du fonctionnement sécurisé de l'appareil. Ne mettez jamais l'appareil en marche lorsque le conducteur de mise à la terre est débranché.

WARNUNG Nur für authorisiertes Fachpersonal.

Dieses EMC Produkt verfügt über mehrere elektrische Netzanschlüsse. Zur Vermeidung eines elektrischen Schlages sind vor Servicearbeiten an der Stromversorgung alle Netzanschlüsse zu trennen.

Kontinuierliche Erdung ist notwendig während der gesamten Betriebsdauer des Gerätes. Es ist unzulässig das Gerät ohne Erdung

Warnings andCautions

Connectrix DS-24M2 User Guide xxvii

xxvii

Warnings and Cautions

zu betreiben. Gerät muss geerdet werden, bevor es am Stromnetz angeschlossen wird.

Additional Warningsand Cautions

Before attempting to service EMC hardware described in this document, observe the following additional Warnings and Cautions:

WARNING

The hardware enclosurecontains no user-serviceable parts, so it should not be moved or opened for any reason by untrained persons. If the hardware needs to be relocated or repaired, only qualified personnel familiar with safety procedures for electrical equipment and EMC hardware should access components inside the unit or move the unit.

WARNING

This product operates at high voltages. To protect against physical harm, power off the system whenever possible while servicing.

WARNING

In case of fire or other emergency involving the EMC product, isolate the product’s power and alert appropriate personnel.

CAUTION!Trained personnel are advised to exercise great care at all times when working on the EMC hardware.Remember to:

◆ Remove rings, watches, or other jewelry and neckties before you begin any procedures.

◆ Use caution near any moving part and any part that may start unexpectedly such as fans, motors, solenoids, etc.

◆ Always use the correct tools for the job.

◆ Always use the correct replacement parts.

◆ Keep all paperwork, including incident reports, up to date, complete, and accurate.

i Connectrix DS-24M2 User Guide


Static Precautions EMC incorporates state-of-the-art technology in its designs, including the use of LSI and VLSI components. These chips are very susceptible to damage caused by static discharge and need to be handled accordingly.

CAUTION!Before handling printed circuit boards or other parts containing LSI and/or VLSI components, observe the following precautions:

◆ Store all printed circuit boards in antistatic bags.

◆ Use a ground strap whenever you handle a printed circuit board.

◆ Unless specifically designed for non-disruptive replacement, never plug or unplug printed circuit boards with the power on. Severe component damage may result.

Connectrix DS-24M2 User Guide xxix

xxx



1Invisible Body Tag

This chapter introduces the operating features of the EMC Connectrix DS-24M2 2 Gb/s fabric switch, including hardware features and components. It describes operator controls, management, service, and operation features, and hardware operations. Also provided is an overview of creating multiswitch fabrics with multiple switches.

◆ Overview.............................................................................................1-2◆ DS-24M2 Description.........................................................................1-3◆ Connectrix Service Processor ...........................................................1-8◆ Hardware Features ............................................................................1-9◆ Hardware Operations......................................................................1-15

Switch OperatingFeatures

Switch Operating Features 1-1

1

1-2

Switch Operating Features

OverviewThe Connectrix™ DS-24M2 (shown in Figure 1-1 on page 1-4) is a 24-port Fibre Channel switch that provides high-performance connections between computers, storage devices, and other peripherals in an Open Systems Fibre Channel switched network.

The DS-24M2 can transfer data at up to 2.125 Gb/s (gigabits per second) through each port at distances up to 300 meters (500 meters if the port is set to 1 Gb/s) using 50/125-micron multimode fiber-optic cable with shortwave laser transceivers and up to 20 kilometers using 9/125 micron single-mode fiber-optic cable with longwave laser transceivers.

The DS-24M2 is managed and controlled through one of these:

◆ The Connectrix Manager and DS-24M2 Product Manager applications installed on the Connectrix service processor in an EC-1200 cabinet. (Multiple switches and the Connectrix service processor communicate on a LAN through one or more 10Base-T Ethernet hubs.)

◆ An EMC® CLARiiON® cabinet or customer system with an Internet connection to the Embedded Web Server interface installed on the switch.

The DS-24M2 can be installed on a table or desk top, mounted in an EMC EC-1200 equipment cabinet, or mounted in any standard 19-inch equipment rack.

The DS-24M2 implements Fibre Channel technology that provides high-performance scalable bandwidth (2 Gb/s), highly available operation, and high device population.


1Switch Operating Features

DS-24M2 DescriptionThe DS-24M2 provides a modular design that enables fast replacement of field-replaceable units (FRUs). FRUs accessed from the front include small form-factor pluggable (SFP) LC transceivers. FRUs accessed from the rear include two power supplies and five cooling fan modules.

FlexPort Feature Customers can purchase a FlexPort feature, which allows dynamically upgrading a DS-24M2 from 8 ports to 16 ports to 24 ports.

For more information on enabling the FlexPort feature:

1. Login into PowerLink at: http://powerlink.emc.com.

2. Click the Services tab.

3. Select Asset Management Application under License Asset Management.

4. Reference the Help section under the M-series products.

Other Features Key features of the DS-24M2 include:

◆ 24 ports of non-blocking 2 Gb/s Fibre Channel switching in a 1U form factor:

• F_Ports (fabric ports) to provide direct connectivity for up to 24 switched fabric devices.

• FL_Ports (fabric loop ports) to provide arbitrated loop connectivity and fabric attachment for FC-AL devices. Each FL_Port can theoretically support the connection of 126 FC-AL devices.

• E_Ports (expansion ports) to provide interswitch link (ISL) connectivity to fabric directors and switches.

◆ Redundant power and cooling units.

◆ Hot-replaceable optics, power, and cooling units.

◆ Online microcode upgrades.

◆ Management, maintenance, and serviceability features through Connectrix Manager.

DS-24M2 Description 1-3

1

1-4


◆ E_Port compatibility with installed base of ED-140Ms, ED-64Ms, ED-1032s, and DS-xxMs (DS-16M, DS-16M2, DS-24M2, DS-32M, DS-32M2).

◆ LC-based Fibre Channel connector system.

◆ Embedded Web Server.

◆ Mounting in EC-1200, CLARiiON, or customer-supplied rack.

◆ Up to 12 DS-24M2s in a single EC-1200, providing up to 288 departmental-class ports per cabinet.

◆ Web browser, CLI, and SNMP support.

◆ Support for all operating systems, HBAs, and drivers supported by the Connectrix ED-1032 in the current EMC Support Matrix.

Front Panel Figure 1-1 illustrates the front view of the DS-24M2. From left to right, the switch front panel includes:

◆ Green power and amber system error LEDs.

◆ An Ethernet LAN connector.

◆ An IML button.

◆ 24 SFP transceivers that function as G_Ports (generic ports). Green and amber LEDs to the left of each port connector indicate operating status. Refer to Port States on page 4-35 for details.

Figure 1-1 DS-24M2, Front View

Power and SystemError LEDs

The LEDs indicate operational or failed status. Refer to LEDs on page 2-4 for details.

Ethernet Connector The front panel provides a 10/100 Mbps RJ-45 twisted-pair connector that attaches to an Ethernet LAN to provide communication with the Connectrix service processor or an SNMP management workstation.

Ethernet Connector Port LEDs

Power LED

Error LED SFP Transceivers (24)

IML Button



IML Button If you press and hold the IML button for three seconds, the switch performs an Initial Machine Load (IML), which takes approximately 30 seconds and:

◆ Resets the microprocessor and functional logic for the control processor (CTP) subsystem, causing a firmware reload from flash memory.

◆ Resets the Ethernet LAN interface (which causes the connection to the Connectrix service processor to drop momentarily until the connection automatically recovers).

◆ Resets the ports (which causes all Fibre Channel connections to drop momentarily until the connections automatically recover).

The IML button is flush-mounted to protect against inadvertent activation.

CAUTION!Use the IML button only if directed by a procedural step or your next level of support. An IML is not intended for casual use and should be performed only if the CTP subsystem is suspect. Do not use this button to reset a failed port unless directed to do so.

Fibre Channel Ports The front panel provides 24 G_Ports that transmit or receive data at either 1.0625 or 2.125 Gb/s. Each G_Port can function as any one of these:

◆ F_Port (fabric port), providing direct connectivity to switched fabric devices.

◆ FL_Port (fabric loop port), providing arbitrated loop connectivity and fabric attachment for FC-AL devices. Each FL_Port can theoretically support the connection of 126 FC-AL devices.

◆ E_Port (expansion port), providing interswitch link (ISL) connectivity to fabric directors and switches.


1

1-6


CTP The Control Processor (CTP) initializes and configures the switch after the switch is plugged in or reset. The CTP contains the microprocessor and associated logic that coordinate switch operation. The CTP provides PowerPC (PPC) and application-specific integrated circuit (ASIC) subsystems that:

◆ Execute switch firmware and the underlying operating system.

◆ Provide port communication functions.

◆ Provide nonvolatile memory for storing firmware (two memory regions), switch configuration information, persistent operating parameters, and memory dump files. Because two firmware versions can be stored on the CTP, firmware is upgraded concurrently.

◆ Provide connections to Fibre Channel ports and enable frame transmission between switch ports without software intervention.

◆ Provide connections to an RS-232 maintenance port and 10/100 Mbps Ethernet port.

The CTP is not a FRU. If the CTP fails and cannot be rebooted with the reset button, the entire switch must be replaced.

Rear Panel The switch rear panel (Figure 1-2) includes two power supply modules and an RS-232 maintenance port.

Figure 1-2 DS-24M2, Rear View

Maintenance Port

Power Supply Module 1

Power Supply LED Power Supply LED




Power Supplies The switch contains two power supply assemblies with internal cooling fans. The redundant, load-sharing power supply assemblies step down and rectify facility input power to provide 3.3 volts direct current (VDC), 5 VDC, and 12 VDC to the control processor (CTP). The power supplies also provide input filtering, overvoltage protection, and overcurrent protection.

Either power supply can be replaced while the switch is operational. Each power supply has a separate connection to the CTP card to allow for independent AC power sources. The power supplies are input rated at 90 to 264 volts alternating current (VAC).

Three cooling fans integrated in each power supply assembly (six fans total) provide cooling for the power supplies and CTP, as well as redundancy for continued operation if a single fan fails. Fans are removed and replaced as part of the integrated power supply.

Maintenance Port The rear panel provides a 9-pin D-type subminiature maintenance port that provides a connection for a local terminal or dial-in connection for a remote terminal.

The maintenance port is typically used by authorized maintenance personnel, and can be used to configure switch network addresses, such as the IP address, subnet mask, and gateway address.


1

1-8


Connectrix Service ProcessorThe Connectrix service processor is a notebook PC that provides a central point of control for up to 48 LAN-connected Connectrix Switches and/or Directors. The service processor is mounted inside the front door of the EC-1200 cabinet.

Installation, configuration, and management of the switch requires either a Connectrix service processor or Internet access to the Embedded Web Server in the DS-24M2.

EMC recommends using the Connectrix Manager to manage the switch.

The Connectrix service processor is dedicated to operation of the Connectrix Manager and Product Manager applications, which provide a graphical user interface (GUI) to monitor and manage Connectrix products. Refer to the Product Manager Overview on page 3-2 for additional information about the Connectrix Manager and Product Manager applications.

The Connectrix service processor and Connectrix Manager application are a dedicated hardware and software solution that should not be used for other tasks. EMC tests the Connectrix Manager application installed on the Connectrix service processor, but does not test other third-party software for compatibility . Modifications to the Connectrix service processor hardware or installation of additional software (including patches or service packs) may interfere with normal operation.

Embedded Web Server

Using a browser-capable PC with an internet connection to the switch, you can monitor and manage the switch through the Web Server interface embedded in the switch firmware. The interface provides a GUI similar to the Product Manager application, and supports switch configuration, statistics monitoring, and basic operation.

Refer to Appendix C for detailed information on configuring the switch from the Web Server.

.



Hardware FeaturesThe DS-24M2 is an enterprise-class Fibre Channel switch that provides high performance, high-availability connectivity, and enterprise-class manageability for an Open Systems environment. The DS-24M2 provides 24 Fibre Channel G_Ports for attachment to device N_Ports or NL_Ports, or switch E_Ports, through fiber-optic links. The switches provide full-duplex, bidirectional data transfer at 1.0625 or 2.125 Gb/s for all ports.

Performance Features

The DS-24M2 provides these performance features:

◆ High bandwidth — Each port provides full-duplex serial data transfer at a rate of up to 2.125 Gb/s.

◆ High-availability —The switch’s design provides a redundant configuration of critical hardware components with automatic failure detection and notification.

◆ Low latency — The latency is less than two microseconds between transmission of a frame at a source port to receipt of a frame at the corresponding destination port (with no port contention).

◆ Low communication overhead — Fibre Channel protocol provides efficient use of transmission bandwidth, reduces interlocked handshakes across the communication interface, and efficiently implements low-level error recovery mechanisms. This results in little communication overhead in the protocol and a switch Bit Error Rate (BER) better than one bit error per trillion (10-12) bits.

◆ Local control — Actions taking place at a device N_Port seldom affect operation of other ports, therefore servers need to maintain little or no information about other connected devices in a Storage Area Network.

Hardware Features 1-9

1

1-10


Switch Management

Management access to the switch is provided through an Ethernet LAN connection to the CTP subsystem. The following management access methods are provided:

◆ Management through the Connectrix Manager and DS-24M2 Product Manager application — These Java-based GUIs reside on the Connectrix service processor under control of the Microsoft Windows 2000 or Windows NT 4.0 operating system and can also be installed on remote user workstations. Refer to Product Manager Overview on page 3-2 for information about the interfaces.

◆ Remote connection to the Connectrix service processor through the local Connectrix Manager and Product Manager — This allows up to nine concurrent users (eight remote users and one local) to manage and monitor switches controlled by the Connectrix service processor.

◆ Management using SNMP — An SNMP agent is implemented through the Product Manager application, allowing administrators on SNMP management workstations to access switch management information using any standard network management tool. Administrators can assign IP addresses and corresponding community names for up to six SNMP workstations functioning as SNMP trap message recipients.

◆ Management through the Internet using the Embedded Web Server interface installed on the switch — This interface supports configuration, statistics monitoring, and basic operation of the switch, but does not offer all the capabilities of the DS-24M2 Product Manager application. Administrators launch the Web Server from a remote PC by entering the switch’s IP address as the URL, then entering a user name and password at a login screen. The PC browser then becomes a management console.



Figure 1-3 illustrates the switch management access methods.

Figure 1-3 Switch Management

High-Availability Features

Dual power supplies and spare unused ports ensure high availability.

◆ Power supplies — The switch has two power supplies that share the electrical operating load. If one power supply fails, the other supply handles the full load. Separate receptacles at the rear of the switch provide facility input power to each supply. For full redundancy, input power for each receptacle should come from a different source.

◆ Concurrent firmware upgrade — The CTP subsystem provides two nonvolatile memory regions. Because two firmware versions can be stored in the CTP, firmware can be upgraded and activated without disrupting switch operation.

E-Mail Server

Connectrix Manager Client Workstations

SNMPManagement

Station

Connectrix Manager ServerRunning on

Connectrix Service Processor

Switch/Hub

10/100 Mb/sCorporate LAN


1

1-12


Connectivity Features

The DS-24M2 and the Product Manager applications support these Fibre Channel connectivity features:

◆ Extended distance support — Through repeaters or Dense Wave Division Multiplexing (DWDM) equipment, switch ports can be configured for extended-distance operation. The DS-24M2's maximum BB_credit value is 12, and only on ports 0 through 3. Therefore, use port 0, 1, 2, or 3 for 10 km LW optics.

◆ Port blocking — System administrators can block or unblock any switch port through the Product Manager application. Blocking a port prevents an attached device from logging in to the switch or communicating with any attached device. A blocked port continuously transmits an offline sequence (OLS).

◆ Zoning — System administrators can partition attached devices into restricted-access zones. A zone contains a set of devices that can access each other. A zone member can be a port or the WWN of the device attached to a port. (EMC recommends that zones contain only WWNs.) Ports and devices spread throughout switches in a multiswitch fabric can be grouped into the same zone.

Members of a zone can see each other, but members in different zones cannot. HBAs with EMC-approved device drivers will discover only those storage devices in their zone.

◆ State change notification — The DS-24M2 supports a state change notification function that allows attached N_Ports to request notification when other N_Ports change operational state.

Security Features The Connectrix Manager and Product Manager applications offer these security features:

◆ Password protection — Users must provide a user name and password to login to the Connectrix service processor and access managed switches. Administrators can configure user names and passwords for up to 16 users and can authorize or prohibit management permissions for each user.

◆ Remote user restrictions — Remote user access to the switches can be either disabled or restricted to configured IP addresses.

◆ SNMP workstation restrictions — SNMP workstations can only access MIB variables managed by the SNMP agent in the switch. SNMP workstations must belong to SNMP communities



configured through the Product Manager application. If configured, the agent can send authorization failure traps when unauthorized SNMP workstations attempt to access the switch.

◆ Audit log tracking — Configuration changes to the switch are recorded in an audit log stored on the Connectrix service processor. Users can display the audit log through the Product Manager application. Log entries include the date and time of the configuration change, a description of the change, and the source of the change.

◆ Port blocking — System administrators can block or unblock any switch port to restrict device access to the switch.

◆ E_Port/F_Port control function — The administrator can configure the G_port for F_port operation only. If the port extends the link outside the data center, this feature prevents the remote user from connecting a switch and making the port an E_port.

◆ Zoning — System administrators can create zones that provide switch access control to increase network security, differentiate between operating systems, and prevent data loss or corruption. Zoning can be implemented in conjunction with server-level access control and storage device access control.

Serviceability Features

The Connectrix Manager and DS-24M2 Product Manager applications offer these serviceability features:

◆ LEDs on FRUs and the front of the switch, provide visual indicators of hardware status or malfunctions.

◆ System alerts, event logs, audit logs, link incident logs, and hardware logs that display switch, Ethernet link, and Fibre Channel link status at the Connectrix service processor or a remote workstation.

◆ Diagnostic software that performs power-on self tests (POSTs) and port diagnostics (internal loopback, and external loopback tests.)

◆ Automatic notification of significant system events (to support personnel or administrators) through e-mail messages or the call-home feature.

◆ An external modem for support personnel to dial in to the Connectrix service processor for event notification and to perform remote diagnostics.


1

1-14


◆ An RS-232 maintenance port at the rear of the switch (port access is password protected) that enables installation or service personnel to:

• Change the switch’s MAC address, IP address, subnet mask, and gateway address.

• Enable or disable the LAN data rate auto-negotiate feature. The default is enabled.

• Set Fibre Channel port operation to half duplex or full duplex. The default is full-duplex operation.

◆ Redundant FRUs (SFP LC transceivers and power supplies) that can be removed or replaced without disrupting switch or Fibre Channel link operation.

◆ A modular design that enables quick removal and replacement of FRUs without tools.

◆ Concurrent port maintenance. SFP transceivers can be added or replaced, and fiber optic cables can be attached to ports without interrupting other ports or switch operation.

◆ Beaconing to assist service personnel in locating a specific port or switch. When port beaconing is enabled, the amber LED associated with the port flashes. When unit beaconing is enabled, the system error indicator on the front bezel flashes. Beaconing does not affect port or switch operation.

◆ SNMP management using the Fibre Alliance MIB that runs on the Connectrix service processor. Up to 12 authorized management workstations can be configured through the Connectrix Manager application to receive unsolicited SNMP trap messages. The trap messages indicate operational state changes and failure conditions.

◆ SNMP management using the Fibre Channel Fabric Element MIB (Version 2.0), TCP/IP MIB-II definition (RFC 1213), or a DS-24M2 MIB that runs on each switch. Up to six authorized management workstations can be configured through the Product Manager application to receive unsolicited SNMP trap messages. The trap messages indicate operational state changes and failure conditions.

◆ Data collection through the Product Manager application to help isolate system problems. The data includes a memory dump file and audit, hardware, and engineering logs.



Hardware OperationsThis section introduces hardware operations that affect the DS-24M2.

Updating Firmware The Connectrix service processor’s fixed disk can contain a library of firmware versions for downloading to any DS-24M2 managed by the Connectrix service processor. Refer to Managing Firmware Versions on page 7-7 for instructions on changing switch firmware.

Because the CTP contains two nonvolatile memory regions, firmware can be loaded (sent) to the switch without disrupting port operation.

Switch Operational States

The switch can have one of the following operational states:

◆ On line — When the switch is in the online state, all of the unblocked ports are allowed to log in to the fabric and begin communicating. Devices can connect to the switch if the port is not blocked and can communicate with another attached device if both devices are in the same zone or if the default zone is enabled.

◆ Off line — When the switch is in the offline state, all the installed ports are off line. The ports transmit OLS and cannot accept a login for connection from an attached device. All ports in the switch, including E_Ports, are placed off line, regardless of whether they were blocked or unblocked, and the switch is removed from a multiswitch fabric.

The operational state of the switch can be changed from the Product Manager through the Set Online State option. Refer to Setting the Online State on page 7-6 for details.

Hardware Operations 1-15

1

1-16


IML When the IML button is pressed and held for three seconds, the switch performs an Initial Machine Load (IML) that takes about 30 seconds. This operation:

◆ Resets the microprocessor and functional logic for the CTP and loads firmware from flash memory.

◆ Resets ports (including failed ports) (which causes all Fibre Channel connectors to drop momentarily until the connections automatically recover).

◆ Resets the Ethernet interface on the CTP, causing the connection to the Connectrix service processor to drop momentarily. The alert symbol on the Product View on the Connectrix Manager changes to a gray square until the connection is re-established.

◆ Automatically enables changes made to the active zone set if these changes were not enabled before the IML.

◆ Keeps all fabric services databases intact, making the operation transparent to attached devices. These databases contain such information as current fabric logins, name server registrations, and other data.

◆ A reset causes the link between the DS-24M2 and the Connectrix service processor to drop momentarily. The following occurs in the Product Manager window:

• As the network connection drops, the status table on the Hardware view turns yellow.

• The Status field in the table displays No Link and the State field displays the reason why the link did not occur.

• The Link Loss Status table appears.

• A gray square appears in the alert panel.

• The FRUs illustrated in the Hardware view disappear, and then reappear as the connection is re-established.



IPL

CAUTION!An IPL is not intended for ordinary or casual use and should be performed only if the active CTP is suspect or if directed by next-level support or documentation. An IPL interrupts the link between the Connectrix service processor and switch.

To perform an IPL (Initial Program Load), select IPL from the Product Manager Maintenance menu. The IPL functions like an IML, except that an IPL:

◆ Restarts the operational firmware on the CTP, executes abbreviated power on self tests (POSTs) and then, if no POST errors are encountered, resumes the active role that it had before the IPL.

◆ Resets the Ethernet interface on the CTP subsystem, causing the connection to the Connectrix service processor to drop momentarily. The status icon for the switch in the Product View will change to a gray square until the connection is reestablished.

◆ Stops normal switching functions for ports. (Functions resume after the IPL.)

After the IPL:

◆ All fabric services databases containing information about current Fabric logins, name server registrations, and other data remain intact, making the operation transparent to attached devices.

◆ The switch returns to the online state, even if it was off line before the operation.

◆ All ports configured as blocked will remain blocked.

Hardware Operations 1-17

1

1-18



2Invisible Body Tag

This chapter describes the operation of the DS-24M2 and identifies the controls and indicators.

◆ Power Procedures ..............................................................................2-2◆ FRU LEDs and Connectors ...............................................................2-4

Operating the Switch

Operating the Switch 2-1

2

2-2


Power Procedures

Power the Switch On The DS-24M2 has no AC power switches. To power the switch on, plug either AC power cord (shown in Figure 2-1) into an AC power source.

Figure 2-1 AC Power Cords

Power-On Self-Tests When the unit is powered on, power-on self tests (POSTs) run to ensure correct operation of switch logic. These tests reside in flash memory on the Control Processor (CTP). They verify correct operation of the CTP, ports, LEDs, and other hardware components.

During POSTs, several tests occur in sequence. As they occur:

1. The green power (PWR) LED on the front panel illuminates.

2. The amber system error (ERR) LED on the front panel blinks momentarily while the switch is tested.

3. The green LEDs at the top of the Ethernet connector blink while the port is tested.

4. The green/blue and amber LEDs associated with Fibre Channel ports blink momentarily while the ports are tested.

After successful POSTs, the green power LED remains illuminated and all other front panel LEDs go dark. If any of the following occurs, contact EMC Customer Support:

◆ The amber system error LED remains on.

◆ The green power LED is off.

ConnectorConnector


2Operating the Switch

◆ The amber LED for either power supply on the rear of the unit is on (and the power cord on that power supply is plugged into a working AC power source).

Powering the SwitchOff

You do not need to power the switch off to remove FRUs or to connect fiber-optic cables to and from ports. However, you must switch off the power to relocate the switch.

Powering the switch off and on (power cycle) resets all hardware components and interrupts port operation. When powering the unit on, all logic is reset.

Follow these steps to power the switch off:

CAUTION!Warn administrators and users currently operating devices that are attached to the switch that it is going off line and that communications will be disrupted. Also, request that the devices affected by an interruption of data flow be set off line.

1. Set the switch off line using the Set Online State option from the Product Manager (refer to the above warning before setting the switch off line).

2. Disconnect the power cord for each power supply from its AC source.

Power Procedures 2-3

2

2-4


FRU LEDs and Connectors

LEDs LEDs on hardware components indicate operational status. Figure 2-2 and Figure 2-3 show LED locations and Table 2-1 describes their functions.

Figure 2-2 Front Panel LEDs and Connectors

Figure 2-3 Rear Panel LEDs and Connectors

Ethernet Connector Port LEDs

Power LED

Error LED SFP Transceivers (24)

IML Button

Maintenance Port


Power Supply LED Power Supply LED



2Operating the Switch

Table 2-1 LEDs

LED Color State Function

Power Green On The switch is receiving power.

Off The switch may not be receiving AC power. Check the AC power source and power cords.

Error Amber On The switch has detected an event requiring immediate operator attention, such as a FRU failure. The LED remains illuminated as long as an event is active.

Off Someone has selected Clear System Error Light from the Product Manager application.

Blinking Unit beaconing is enabled (and there is no error; even if beaconing is enabled, the LED will illuminate continously if there is a failure).

Ethernet Connector

Green See Function

Two LEDs at the top of the Ethernet connector indicate LAN speed:◆ Left LED on = 10 Mbps◆ Right LED on = 100 Mbps

Port Green/Blue

On The port is connected with the attached end device and is ready to communicate. The LED illuminates in green to indicate 1.0625 Gb/s port operation and blue to indicate 2.125 Gb/s operation.

Off The port is off line.

Blinking There is active Fibre Channel traffic on the port.

Amber On The port has failed.

Off The port is operational.

Blinking The port is running diagnostics or port beaconing has been enabled from the Product Manager. (Refer to Port Operational States on page 4-35.)

Power Supply

Amber On The power supply has failed or has lost AC power.

Off The power supply is operational.

FRU LEDs and Connectors 2-5

2

2-6


Connectors The DS-24M2 contains a variety of connectors used to connect the switch to the Connectrix service processor, customer LAN, and attached devices. Figure 2-1 on page 2-2 and Figure 2-2 on page 2-4 show connector locations, and Table 2-2 describes their functions.

Table 2-2 Connectors

Connector Function

RJ-45 100Base-T Ethernet

Connects the switch to the same 100 Mbps LAN as the Connectrix service processor. All data to and from the switch and Connectrix service processor is transported on this link.

Port Connects the switch to user devices and other switches.

AC power Supplies AC power to the two supplies, providing single-phase connections with input rated up to 264 VAC.


3Invisible Body Tag

This chapter is an introduction and overview of the DS-24M2 Product Manager application. It is intended as a quick reference for using features available through the main Product Manager window.

◆ Product Manager Overview .............................................................3-2◆ Using the Product Manager..............................................................3-5◆ Product Manager Menu Bar ...........................................................3-12◆ Product Manager Views..................................................................3-17◆ User Rights........................................................................................3-21

Product ManagerOverview

Product Manager Overview 3-1

3

3-2

Product Manager Overview

Product Manager Overview The Product Manager for the DS-24M2 is a Java-based graphical user interface (GUI) that provides in-depth management, configuration, and monitoring functions for individual switches and their field-replaceable units (FRUs). Although each Product Manager is accessed from the Connectrix Manager, it is a separate application.

In contrast to the Product Manager, the Connectrix Manager enables administrators to monitor operational status for all products and Fibre Channel fabrics managed by a Connectrix service processor. The Connectrix Manager also provides tools to administer user and product access to the Connectrix Manager and Product Manager. (Refer to the Connectrix Manager User Guide.)

The Product Manager provides graphical views of switch hardware components and component status. By positioning the cursor on icons, graphics, panels, and other visual elements in these views and clicking the mouse/touchpad, you can quickly manage and monitor the switch on your network.

Using the Product Manager, you can:

◆ Back up and restore configuration data.

◆ Clear the system error indicator.

◆ Configure extended distance buffering for ports.

◆ Configure Fibre Channel operating parameters for the switch.

◆ Configure individual ports with a port name describing the node attached to the port.

◆ Configure link incident (LIN) alerts.

◆ Configure port binding (if the Port Binding feature is enabled).

◆ Configure Nicknames to display instead of WWNs for switches and attached devices.

◆ Configure SNMP trap recipients and community names.

◆ Configure Open Systems Management Server features (if installed).

◆ Configure switch binding if optional Enterprise Fabric Extensions feature is installed.

◆ Configure an interoperability mode for multiswitch fabrics.


3Product Manager Overview

◆ Configure the switch name, location, description, and contact person.

◆ Configure threshold alerts for ports.

◆ Enable LIN alerts on ports.

◆ Control individual Fibre Channel ports by blocking/unblocking operation, enabling LIN alerts, enabling port binding, and setting data speeds.

◆ Display FRU properties such as the FRU name, physical position in the switch, active failed state, part number, and serial number.

◆ Display information for individual Fibre Channel ports, such as the port name, port number, Fibre Channel address, operational state, type of port, and login data.

◆ Display information on nodes attached to ports.

◆ Display port performance and statistics.

◆ Display product data for the switch, such as the system name, description, contact person, location, status, model number, firmware and Engineering Change (EC) level, and manufacturer.

◆ Enable beaconing for ports and the switch.

◆ Monitor the operational status of the switch and each of its hardware field-replaceable units.

◆ Perform an Initial Program Load (IPL).

◆ Perform maintenance tasks for the switch, including maintaining firmware levels, administering the call-home feature, accessing the switch logs, and collecting data to support failure analysis.

◆ Reset port operation.

◆ Run port diagnostics.

◆ Set the date and time on the switch.

Access the switch Product Manager by double-clicking a switch Product icon on the Connectrix Manager window (in either the Products view or the Fabrics view).

You can install the Connectrix Manager Client application onto a remote workstation using any standard Web browser. For instructions on installing the Client, refer to the appendix titled Configuring Remote Workstations in the Connectrix Manager User Guide.

Product Manager Overview 3-3

3

3-4


Figure 3-1 Connectrix Service Processor and Remote Workstation Configuration

E-Mail Server

Connectrix Manager Client Workstations

SNMPManagement

Station

Connectrix Manager ServerRunning on

Connectrix Service Processor

Switch/Hub

10/100 Mb/sCorporate LAN



Using the Product ManagerThis section provides a general overview of the Connectrix Manager and its functions. For details on performing specific tasks and using specific dialog boxes, refer to the appropriate chapters in this manual.

Using Dialog Boxes Dialog boxes, such as the one in Figure 3-2, appear when you select options from the pop-up menus.

The terms dialog box and window are sometimes used interchangeably.

Figure 3-2 Typical Dialog Box

To enter data into an empty field, click in the field and begin typing when the cursor appears at insertion point.

To change or remove data that already exists in a field, drag the cursor (or double-click on the data) to highlight the characters you want to change/delete; then type in the new data. (It should overwrite the highlighted characters; if not, use the DELETE or BACKSPACE key to remove characters.

Clicking one of these buttons in a dialog box initiates the described function (not all buttons appear in all dialog boxes):

◆ OK — Saves the data you entered and closes the dialog box.

◆ Activate — Saves the data you entered and closes the dialog box, unless there is a Close button, in which case Activate saves the information without closing the box.

◆ Close — Closes the dialog box and saves the data you entered.

◆ Cancel — Cancels the operation and closes the dialog box without saving the information you entered.

Using the Product Manager 3-5

3

3-6


Keyboard Navigation Keyboard navigation is an alternative to mouse navigation. Use the methods described in this section to navigate using your keyboard.

Logging Into the Connectrix Manager

To open the Product Manager, you must first log into the Connectrix Manager:

1. The Connectrix Manager starts automatically when the Connectrix service processor is powered on or rebooted.

If you need to start the Client application on a remote workstation, follow the appropriate steps:

a. Windows 95, Windows 98, Windows NT, or Windows 2000.

b. These steps assume the Connectrix Manager is in your home directory. If you saved it to a different location, enter the appropriate directory names.

OS Steps

Windows a a. If necessary, switch the Connectrix service processor on.

b. On the Windows desktop,double-click the Connectrix Manager icon:

Solaris or Linux

a. In the Terminal window, type the following and press ENTER: b

[root@evtcom2 /root]# cd /home

b. Type [root@evtcom2 /root]# cd EFCM and press ENTER.

c. Type [root@evtcom2 /root]# ./ConnectrixManager and press ENTER.

HP/UX or AIX

a. In the Terminal window, type the following and press ENTER: b

[root@evtcom2 /root]# cd /home

b. Type [root@evtcom2 /root]# cd EFCM and press ENTER.

c. Type [root@evtcom2 /root]# ConnectrixManager and press ENTER.



2. On the Connectrix Manager Login window (Figure 3-3), enter your user name and password. (User names and passwords are case-sensitive. )

If user names have not been established, use the default user name (Administrator) and password (password).

Figure 3-3 Connectrix Manager Login Window

3. The default address that appears in the Connectrix field is the address of the last service processor or server accessed. Click the arrow to the right of the field display the network addresses of all Connectrix service processors that were accessed from your PC/workstation.

Select an address or, if you want to connect to a Connectrix service processor that is not listed, enter the name or IP address.

4. Click Login.

If the connection is successful, the Connectrix Manager opens to the Products view (Figure 3-4). (The other main view is the Fabrics view, which is described in the Connectrix Manager User Guide.)

Version: 06.03.00.x


3

3-8


Figure 3-4 Connectrix Manager Products View

The Products view provides a graphical overview of all the products that can be managed and monitored through the Connectrix Manager. In a full-screen environment on an 800 x 600 resolution monitor, this panel displays up to 48 product icons.

110.22.140.78



Product Icons Information in each product icon includes the following:

Object descriptions:

◆ Switch data speed: 2 Gb/s.

◆ Attention indicator — A yellow triangle means that product requires attention. Open the Product Manager application for the director by double-clicking on the icon to find out more information.

◆ Product name or network address — You can determine which appears by right-clicking on the open area away from the product icons and selecting Display Options from the pop-up menu.

Whichever identifier appears, you can display a pop-up window with the other identifier by moving the cursor over the product icon.

◆ Status indicator (the color-coded symbol behind the product illustration):

• A red and yellow diamond means that the product has failed and requires immediate service.

• A yellow triangle means that the product is degraded, but is still performing as designed.

• A green circle means that the product is fully operational.

• A grey square means that the Connectrix Manager cannot determine product status.

• If an alert symbol does not display behind the product, the product is not managed by the Connectrix service processor to which you are logged in.

The most critical status reflected by a product in the view is also reflected in the Products status box in the left corner of the Connectrix Manager window.

Switch Speed (Gb/s) Attention Indicator

Product Name or Network Address

Number of Ports

Product Illustration

Status Indicator

MySwitch 5


3

3-10


Opening the Product Manager

You can open the Product Manager for a product in any of these ways:

◆ Double-click the product icon in the Connectrix Manager window, in either the Products or Fabrics view

◆ Right-click the product icon, and select Open on the pop-up menu.

◆ Click the product icon to highlight it; then press CTRL-O or click the Open Product icon on the Connectrix Manager toolbar:

The Product Manager opens to the Hardware view (Figure 3-5).

Figure 3-5 Product Manager Window

OpenProduct

120.20.150.10

ABC 123Windows Title BarMenu Bar

View Selector

Main Panel

Status Indicator

ABC 123



The Connectrix Manager window is still available as a separate window. You can drag the Product Manager window away from the Connectrix Manager window and view both windows on your PC desktop (or minimize one or both to icons if desired). You can have up to four Product Manager windows open concurrently.

For more information on the Products view, refer to these sections:

◆ Product Manager Menu Bar on page 3-12

◆ Product Manager Views on page 3-17

Closing the Product Manager

To close the Product Manager, select Close from the Product menu.

Closing the Connectrix Manager

To log out of the Connectrix Manager (so you can log in again using a diferent user name and password), select Logout from the Connectrix Manager Product menu.

To close the Connectrix Manager application, select Exit from the Connectrix Manager Product menu.


3

3-12


Product Manager Menu Bar

Figure 3-6 Product Manager Menu Bar

The menu bar consists of these menus:

◆ Product:

• Port — Contains the following items; refer to Port Menu on page 4-15 for descriptions:

– Port Properties

– Port Technology

– Block Port

– Enable Beaconing

– Port Diagnostics

– Clear Link Incident Alert(s)

– Reset Port

– Port Binding

– Clear Threshold Alert(s)

• FRU — Contains a FRU Properties entry; refer to Displaying FRU Properties on page 4-9 for a description.

• Clear System Error Light — Turns off the amber system error LED, located below the power LED on the front of the switch.

• Enable Unit Beaconing — Causes a system error light on the front of the switch to blink, to help users locate the actual unit in an equipment room. (You can enable unit beaconing only if the system error light is off, signifying that there are no outstanding errors.)

• Properties — Displays such information as the switch name, description, location, and contact person. Refer to Displaying Switch Properties on page 4-13.

• Close — Closes the Product Manager window.

Menu BarDS-24M2: ABC123

ABC 123DS-24M2 Status



◆ Configure:

• Identification — Allows you to specify information that will appear in the identification table at the top of the Hardware view and in the Connectrix Manager Products view (if the Products view is configured to display names)

Refer to Configuring Switch Identification on page 5-2.

• Operating Parameters — Allows you to set the following operating parameters (described in greater detail under Configuring Operating Parameters on page 5-4):

The DS-24M2 does not support configurable BB_Credits (buffer-to-buffer credits):

– Ports 0 through 3 are set to 12 BB_Credits each.– Ports 4 through 23 are set to 5 BB_Credits each.

• Switch Binding — allows you to activate switch binding according to a specific connection policy., and to create a list of switches and devices that you want to allow exclusively to attach to switch ports.

Switch Binding is an optional feature that you can enable through the Configure Feature Key dialog box. For details, refer to Configuring Switch Binding on page 5-12.

This function is available only if Enterprise Fabric Extensions is installed.

Switch Parameters

Preferred Domain ID

Insistent

Rerouting Delay

Domain RSCNs

Suppress RSCNs on zone set activations

Fabric Parameters

R_A_TOV

E_D_TOV

Switch Priority

Interop Mode (Homogeneous Fabric or Open Fabric 1.0)

Product Manager Menu Bar 3-13

3

3-14


• Ports — Allows you to configure a port name, block or unblock operation, configure LIN alerts, enable Fabric Address Notification, define a Fibre Channel port type, set the port speed, enable port binding, and specify a bound WWN.

Refer to Configuring Ports on page 5-18.

• SNMP Agent — Allows you to configure network addresses and community names for up to six SNMP trap recipients.

Refer to Configuring the SNMP Agent on page 5-24.

• Management Server — Allows you to configure the open systems inband management program to function with the switch. (The Open Systems Management Server feature must be installed in order to perform this procedure.)

Refer to Configuring Management Server Control on page 5-27.

• Features — Allows you to validate an installed feature for use.

Refer to Configuring Feature Keys on page 5-28.

• Date/Time — Allows you to set the date and time on the switch, and to set the switch to synchronize with the date and time on the Connectrix service processor.

Refer to Configuring the Date and Time on page 5-31.

• Threshold Alerts — Allows you to configure threshold alerts for ports. A threshold alert notifies users when the transmit (Tx) or receive (Rx) throughput reaches specified values for specific director ports or port types (E_Port, F_Port, FL_Port).

Refer to Configuring Threshold Alerts on page 5-33.

• Export Configuration Report — Allows you to save an ASCII text file containing all current user-definable configuration options in a printable format.

Refer to Exporting a Configuration Report on page 5-41.

• Enable Web Server — Allows you to to enable the Embedded Web Server interface on the switch.

Refer to Enabling the Embedded Web Server on page 5-43.

• Enable Telnet — Allows you to enable Telnet access to the switch.

Refer to Enabling Telnet on page 5-44.



◆ Logs:

• Audit Log — Provides a record of all configuration changes made on the switch. Refer to Audit Log on page 6-4.

• Event Log — Provides a record of significant events that have occurred on the director, such as hardware failures, degraded operation, and port problems. Refer to Event Log on page 6-6.

• Hardware Log — Displays information on FRUs inserted and removed from the switch. Refer to Hardware Log on page 6-8.

• Link Incident Log — Displays the most recent incidents with their date and time, port number, and description of the incident.

Refer to Link Incident Log on page 6-9.

• Threshold Alert Log — Provides notifications of threshold alerts, including date and time each alert occurred, port for which the alert is configured, and type of alert (transmit throughput, receive throughput, or both).

Refer to Threshold Alert Log on page 6-11.

◆ Maintenance:

• Port Diagnostics — Is used by service personnel to run internal and external loopback tests on ports.

• Data Collection — Allows you to collect maintenance data into a file. This file is used by support personnel to diagnose system problems. Refer to Collecting Maintenance Data on page 7-3.

• IPL — Allows you to initiate an Initial Program Load on the switch Refer to Executing an IPL on page 7-4.

• Set Online State — Allows you to change the online state of the switch to off line or on line. Refer to Setting the Online State on page 7-6.

• Firmware Library — Displays all firmware versions currently installed on the Connectrix service processor that can be downloaded to the switch. Refer to Managing Firmware Versions on page 7-7.

• Enable E-Mail Notification — Allows you to enable e-mail notification for the switch. Refer to Enabling E-Mail Notification on page 7-8.

Product Manager Menu Bar 3-15

3

3-16


• Enable Call Home Notification — Allows you to enable the call-home function for the switch. Refer to Enabling Call-Home Notification on page 7-9.

• Backup & Restore Configuration — Allows you to save the product configuration stored on the switch to the Connectrix service processor hard disk or to restore the product configuration from the Connectrix service processor (to a switch with the same IP address as the one that was backed up). Refer to Backing Up and Restoring the Configuration on page 7-10.

• Reset Configuration — Allows you to reset all switch configuration data back to the factory defaults. Refer to Resetting the Configuration on page 7-16.

◆ Help:

• Contents — Displays online help for the Product Manager.

• About — Displays the version number for the Product Manager and copyright information.



Product Manager Views

Figure 3-7 Product Manager View Selector Tabs

The Product Manager offers four main views, accessible by clicking the tabs.

Hardware View The Hardware view (Figure 3-8) is the default view that appears in the main panel when you open the Product Manager.

For details on navigating and monitoring via the Hardware view, refer to Chapter 4.

Figure 3-8 Product Manager Hardware View

DS-24M2: ABC123


View Tabs

DS-24M2 : ABC 123

ABC 123

Product Manager Views 3-17

3

3-18


In the Hardware view, color-coded indicators reflect the status of actual LEDs on the switch FRUs. The status indicator at the lower left displays a symbol to represent the most degraded status currently reported by any of the switch FRUs. For example, for a port failure, indicated by a red and yellow diamond on a port, a yellow triangle appears on the alert panel to indicate a degraded condition.

For an explanation of the various alert symbols, refer to Table 4-1 on page 4-5.

Displaying Propertiesand Options

Double-clicking anywhere on the switch except on a FRU displays a Switch Properties window. Double-clicking on the power supply or cooling fan module displays a FRU Properties window containing detailed information on the hardware component.

Right-clicking anywhere on the switch except on a FRU displays a list of options for the switch. Refer to Using Menu Options on page 4-14 for more information.

For reference, here are the menu options:

◆ Switch Properties

◆ Enable Unit Beaconing

◆ Clear System Error Light

◆ IPL Switch

◆ Set Switch Date and Time

◆ Set Switch Online State

Port List View Clicking the Port List tab on the Product Manager window (refer to Figure 3-7 on page 3-17) displays a table listing:

◆ # — Port number

◆ Name — Port name

◆ Block Config — Blocked/unblocked configuration

◆ State — Operating state

◆ Type — Port type

◆ Operating speed

◆ Alert — Identification of any ports with outstanding alert conditions



Other options available on the Port List view allow you to:

◆ Block/unblock ports

◆ Display port properties

◆ Display port technology: connector and transceiver types, distance, media, and speed

◆ Configure port binding

◆ Run port diagnostics

◆ Enable port beaconing

◆ Clear Link Incident Alert(s)

◆ Clear Threshold Alert(s)

◆ Reset the port

For details on these menu options, refer to Port Menu on page 4-15. For details on navigating and monitoring using the Port List view, refer to Using the Performance View on page 4-25.

Node List View Clicking the Node List tab on the Product Manager window (refer to Figure 3-7 on page 3-17) displays a table of information about all node attachments or N_Ports that have logged into existing F_Ports on the switch. Only N_Ports appear in the Node List view after nodes have logged in to the fabric.

The columns that appear in the table include:

◆ Port — Port number where the node is attached

◆ Address — Fibre Channel address of the node

◆ Node Type :

• N_Port — The switch port is operating as an F_Port

• NL_Port — The switch port is operating as an FL_Port

◆ Port WWN — WWN of the attached node (device)

◆ Unit Type — Type of connected device

◆ BB_Credit — Value used by the attached node

For details on navigating and monitoring via the Node List view, refer to Using the Node List View on page 4-21.

Product Manager Views 3-19

3

3-20


Performance View Clicking the Performance tab on the Product Manager window (refer to Figure 3-7 on page 3-17) displays a graphical display of performance for all ports. (Figure 4-7 on page 4-25 shows an example of the Performance view. )

The top portion of the Performance view displays bar graphs that show the level of transmit/receive activity for each port. This information is updated every five seconds. Each bar graph also shows the percentage link utilization for the port.

The bottom portion of the Performance view displays cumulative statistical information for the port selected in the bar graph. Values are displayed for transmit and receive traffic, class 2 and 3 statistics, operational statistics, and error categories.

For more information about the Performance view, refer to Using the Performance View on page 4-25.

FRU List View Clicking the FRU List tab on the Product Manager window (shown in Figure 3-7 on page 3-17) displays a table with information about each of the FRUs installed in the switch. All data is dynamic and is updated automatically.

Figure 4-9 on page 4-33 shows an example of the FRU List view. For details on navigating and monitoring via the FRU List view, refer to Using the FRU List View on page 4-33.



User RightsThe Connectrix Manager’s system administrator can assign levels of access, or user rights, to Product Manager users through the Connectrix Manager application.

Note that the Connectrix Manager’s system administrator only has view rights while operating in a specific Product Manager application. Conversely, a Product Manager’s product administrator only has view rights while operating in the Connectrix Manager application.

Detailed instructions concerning the assignment of user rights for both the Connectrix Manager and Product Manager applications appear in the Connectrix Manager User Guide.

Any of these levels of user rights can be assigned to specific users:

◆ System Administrator

◆ Product Administrator

◆ Operator

◆ Maintenance

◆ View

By default, all users have View rights, which allow viewing configurations, but not changing them. View rights cannot be removed.

Users with System Administrator rights can make all control and configuration changes implemented through the Connectrix Manager application.

User Rights 3-21

3

3-22


User Rights for Specific Functions

Table 3-1 itemizes the specific functions available to Product Manager users that have been assigned user rights of Product Administrator, Operator, and/or Maintenance. If a user does not have the right to perform a specific operation, a not authorized error box appears when the operation is attempted.

Table 3-1 User Rights for Product Manager Functions

Product Manager RightsProduct Administrator Operator Maintenance

Backup/Restore Configuration X X

Block Port X X X

Change Online State X X

Clear Audit Log X

Clear Audit Log X

Clear Event Log X

Clear Hardware Log X X

Clear LIN Alert X X

Clear LIN Log X

Clear System Error Light X

Configure Date/Time X X X

Configure Feature Key X

Configure Identification X

Configure Management Server X

Configure Switch Parameters X

Configure Fabric Parameters X

Configure Port Binding X X

Configure Ports X X

Configure SNMP X

Configure Switch Binding X

Configure Zoning X



Data Collection X

Date/Time Sync Configuration X X X

Enable Call Home Notification X

Enable E-Mail Notification X

Export Configuration Report X X X

IPL X X

Manage Firmware X

Port Diagnostics X

Port Beaconing X X X

Set Online State X X X

Reset Configuration X

Reset Statistics Counters (Performance View)

X X

Reset Port X

Unit Beaconing X X X

View Event Log X X

View Firmware X

View Hardware Log X X X

View LIN Log X X X

View SNMP X X

View Threshold Alert Log X X X

Table 3-1 User Rights for Product Manager Functions (continued)

Product Manager RightsProduct Administrator Operator Maintenance

User Rights 3-23

3

3-24



4Invisible Body Tag

This chapter describes how to use the features available in the various Product Manager views to monitor and manage switch operation. The views are accessible from the tabs shown here:

◆ Using the Hardware View ................................................................4-2◆ Using the Port List View .................................................................4-17◆ Using the Node List View...............................................................4-21◆ Using the Performance View..........................................................4-25◆ Using the FRU List View.................................................................4-33◆ Port Operational States ...................................................................4-35◆ Alerts..................................................................................................4-37

Monitoring andManaging the Switch

DS-24M2: ABC123


View Tabs

Monitoring and Managing the Switch 4-1

4

4-2

Monitoring and Managing the Switch

Using the Hardware ViewThe Hardware view is the default view when you open the Product Manager. Using this graphical view of the switch, you can view alert symbols and simulated LEDs, display data, monitor status, and obtain vital product information for the switch and its hardware components.

To display the Hardware view from some other view in the Product Manager, click the Hardware tab.

Identifying FRUs Move the cursor over parts of the switch graphic in the Hardware view to display pop-up labels identifying each hardware component and its slot position in the chassis relative to identical components installed in the switch.

FRUs include:

◆ Power supply module containing two internal power supplies

◆ Ports (small form factor LC transceivers)

Monitoring Switch Operation

This section describes the DS-24M2 Status table and status symbol (shown below), which indicate the operating status of the switch:

Status Refer to Table 4-3 on page 4-35 for the meaning of the text in the Status table and the corresponding symbol in the lower left corner of the Product Manager window.

Status Table

Status Symbol

ABC 123

ABC 123


4Monitoring and Managing the Switch

State The State field displays one of the following:

◆ OFFLINE — When the switch is off line, all ports are off line. The ports cannot accept a login from an attached device or cannot connect to other switches.

Refer to Setting the Online State on page 7-6 for instructions on setting the switch on line or off line.

◆ Online — All unblocked ports are able to connect with devices. Note that the switch automatically goes on line after a power-up, IML (Initial Machine Load), or IPL (Initial Program Load).

Refer to Setting the Online State on page 7-6 for instructions on setting the switch on line or off line.

◆ Coming online — This is a transitional state that occurs just before the switch goes on line. This state normally only happens briefly, unless there is a problem reaching the online state.

◆ Going offline — This is a transitional state that occurs just before the switch goes off line. This state normally only happens briefly, unless there is a problem reaching the offline state.

Name, Description,Location

Refer to Configuring Switch Identification on page 5-2 for details on setting these parameters.

No Link Status If the Ethernet network connection between the Connectrix service processor and the switch is down, the Hardware view displays the front and rear of the unit without FRUs. The DS-24M2 Status table at the top of the Hardware view changes to display the status (No Link) and reason with a yellow background. The Name, Description, and Location fields are blank.

A Reason field in the DS-24M2 Status table displays one of the following reasons when there are no links.

◆ Never Connected — Could be either of these causes:

• A network connection was never established between the switch and the Connectrix service processor

• The CTP subsystem failed.

Check the IP addresses, the Ethernet LAN physical connection between the switch and Connectrix service processor, and other network connection conditions.

Using the Hardware View 4-3

4

4-4


◆ Link Timeout — The network connection that was established between the switch and Connectrix service processor has been lost. Check the IP addresses, the Ethernet LAN physical connection between the switch and Connectrix service processor, IP addresses, and other network components.

◆ Protocol Mismatch — The switch and the Connectrix service processor are not at compatible software release levels. Update the Connectrix Manager software version.

◆ Duplicate Session — A link has previously been established between the switch and another instance of the Connectrix service processor. Connect to the previously established Connectrix service processor from the Connectrix Manager login screen.

◆ Unknown Network Address — The address defined for the switch in the Connectrix Manager could not be found in the Domain Name Server (DNS). Either the name was mistyped when the switch was added to the Connectrix Manager, or the name was not available from the DNS. Check the network IP address for the switch definition in the Connectrix Manager by right-clicking the product icon and selecting Properties. The IP address appears in the Network Address field.

◆ Incorrect Product Type — The product at the configured network address is not a switch. Verify address, configuration, and product type.



Status Symbol The status symbol in the lower left of the Hardware view indicates the overall operating status of the switch. The status depends on specific hardware component failures, which are indicated by status symbols that appear over component graphics in the Hardware view.

Table 4-1 shows the alert panel symbols and their meanings.

Table 4-1 Operating Status - Alert Panel and Switch Status

Alert Panel SymbolOperator Panel Text Switch Status Table Text Meaning

Green Circle: Online or Offline

Fully Operational All components and installed ports are operational; no failures.

Yellow Triangle: Degraded Redundant Failure A redundant component has failed, such as a power supply, and the backup component has taken over operation.

Minor Failure A failure occurred which has decreased the switch operational ability. Normal switching operations are not affected.• One or more ports failed, but at least

one port is still operational.• A fan has failed or is not rotating

sufficiently.

Red Diamond on Yellow Background:

Failed NOT OPERATIONAL A critical failure prevents the switch from performing fundamental switching operations.• All fans failed.• All installed ports failed.• Both power supplies failed.

Gray Square: N/A Never ConnectedLink TimeoutProtocol MismatchDuplicate SessionUnknown Network AddressIncorrect Product Type

Switch status is unknown. This occurs if the Ethernet network connection between the Connectrix service processor and the switch cannot be established or if the CTP fails. Refer to No Link Status on page 4-3 for details on the status table text.


4

4-6


Operation MonitoringExample

Determine hardware component operating status and states by the simulated LED indicators and status symbols that appear on hardware components. These simulated LEDs and alert symbols reflect the state of the actual hardware as changes occur. Corresponding or additional descriptions of hardware status and states also display when you click on components to display Properties windows.

Figure 4-1 illustrates the DS-24M2 Hardware view with examples of symbols and LED indicators that can help you monitor hardware operation. The numbers in circles are keyed to descriptions in Table 4-2 on page 4-7. For more details on the meanings of symbols and indicators, refer to Table 4-3 on page 4-35.

Figure 4-1 Monitoring Hardware Operation Using the Hardware View

ABC 123

ABC 123

1

6

3 4 52

7

NOT OPERATIONAL

OFFLINE



Table 4-2 Legend for Figure 4-1

Port attention indicator — A yellow triangle alert symbol can indicate any of these:

◆ A link incident occurred.◆ The port is not operational.◆ The port is in a non-standard mode of operation.

For a link incident, the status table at the top of the Hardware view changes to reflect the reason for the alert. You can also note the reason by displaying the Port Properties window for the port.

Port LED indicator — A green or blue indicator and an amber indicator to the left of each port connector simulates LED operation on the actual switch port. When the green/blue indicator illuminates, the port is on line and operating at 1 Gb/s (if green) or 2 Gb/s (if blue). When the amber indicator illuminates continuously (not blinking), the port has failed.

Port failure indicator — A red and yellow diamond on a port connector indicates that the port has failed.

Beaconing — When a amber LED indicator appears by a port and an attention indicator appears below the port connector, beaconing is enabled on the ports.

1

2

3

4


4

4-8


Not Installed — The port optics are not installed, or the feature that provides additional port functionality is not enabled.

Power, System Error, and Unit Beaconing indicators — The green/blue and amber indicators on the far left of the front view simulates the power and system error LEDs on the actual switch.

◆ Power indicator — The green/blue indicator simulates the power LED on the switch. When the indicator illuminates, the switch is connected to facility AC power and operational. The indicator will be on if either power supply is operating.

◆ System Error indicator — The amber indicator simulates the system error light on the switch. When this indicator illuminates, an event has occurred requiring immediate attention, such as a system, fan, power supply, or port failure. View details of system errors by selecting Event Log from the Product Manager Logs menu. The indicator in the Hardware View and the LED on the actual unit remains illuminated until you clear the event by right-clicking on the switch graphic (away from any hardware component) and selecting Clear System Error Light from the pop-up menu.

If the amber indicator flashes, this indicates that unit beaconing has been enabled for the switch. Enable or disable unit beaconing by right-clicking on the switch graphic (away from any hardware components) and selecting Enable Unit Beaconing from the pop-up menu.

Power Supply status — Each AC power connector indicates the location of an internal power supply. An amber LED indicator is located in the upper left corner of each AC power connector. The indicator illuminates if the power supply has failed and requires service. The indicator is off if the power supply is active.

If a red and yellow diamond appears on a power connector, the internal power supply for that connector has failed. In this case, the green/blue indicator at the top left of the connector does not illuminate. When the green/blue indicator is on and no alert symbol appears, the power supply is operational.

The switch operates with one power supply; however, you should replace a failed power supply as soon as possible to retain redundancy.

Table 4-2 Legend for Figure 4-1 (continued)

5

6

7



Obtaining Hardware Information

This section explains how to access the FRU Properties, Port Properties, and Switch Properties windows.

Displaying FRUProperties

You can display a FRU Properties window for a power supply (AC connector) in any of these ways:

◆ Double-click the FRU in the Hardware view.

◆ Select the FRU in the Hardware view; then select FRU and FRU Properties from the Product menu.

◆ Double-click on a row in the FRU List view.

The FRU Properties window shows:

◆ FRU name

◆ Slot position relative to identical FRUs installed in the unit

◆ State: active or failed

◆ Part number

◆ Serial number

Displaying PortProperties

You can display a Port Properties window in any of these ways:

◆ In the Hardware view, do either of these:

• Double-click a port.

• Right-click a port and click Port Properties on the pop-up menu.

◆ In the Port List view, do either of these:

• Double-click a row.

• Right-click a row and click Port Properties on the pop-up menu.

◆ In the Node List view, right-click a port’s row and click Port Properties on the pop-up menu.

◆ In the Performance view, right-click a port’s bar graph and click Port Properties on the pop-up menu.

The Port Properties window shows the following for the selected port. Refer to Configuring Ports on page 5-17 for more information on some of these parameters.

◆ Port Number — The physical port number.

◆ Port Name — A user-defined name or description.


4

4-10


◆ Type:

• G_Port— A configurable port type that restricts a port to operate either as an F_Port or E_Port.

• E_Port — A port that connects to another switch’s E_Port over an ISL.

• F_Port — A port that connects to a fabric-enabled device.

• FL_Port — A port that connects to a private loop device.

• Fx_Port — A configurable port type that restricts a port to operate either as an F_Port or FL_Port.

• Gx_Port — A configurable port type that restricts a port to operate either as an F_Port, FL_Port, or E_Port.

◆ Operating Speed — The current data speed for the port: 1 Gb/sec, 2 Gb/sec, or Not Established. Not Established appears if Negotiate was set for the port through the Configure Ports dialog box and the data speed has not been resolved between the port and the attached device, or if the port and device are not communicating.

◆ Port WWN — The port’s 16-digit World Wide Name (WWN).

◆ Block Configuration — Blocked or unblocked.

◆ LIN Alerts Configuration — Indicates whether LIN alerts are enabled (the default setting) or disabled.

◆ FAN Configuration — Indicates whether Fabric Address Notification (FAN) is on or off when the port is operating as an FL_Port.

◆ Beaconing — The beaconing status for the port (enabled or disabled) . To enable or disable beaconing, right-click the port and click the box to the left of Enable Beaconing to add or remove a checkmark.

◆ Link Incident — Description of the last link incident that occurred on the port.

◆ Operational State:• Beaconing• Inactive• Invalid Attachment• Link Incident• Link Reset• No Light• Not Operational



• Online• Offline• Port Failure• Segmented E_Port• Testing

Table 4-3 on page 4-35 describes the operational states.

◆ Reason — Reason for invalid attachment, E_Port segmentation, or inactive state.

E_Port segmentation can occur only when the switch is connected to another switch or director. If the port is not segmented, this field displays Segment not defined.

• Invalid attachment messages:

– 01 Unknown — Invalid attachment reason cannot be determined.

– 02 ISL connection not allowed on this port — Port is configured as an F_Port, but is connected to another switch.

– 03 ELP rejected by the attached switch — This switch transmitted an ELP (exchange link protocol) frame that was rejected by the switch at the other end of the ISL.

– 04 Incompatible switch at the other end of the

ISL — The Interop Mode for this switch is set to Open Fabric and the switch at the other end of the ISL is configured for McDATA Fabric. (Refer to Configuring Operating Parameters on page 5-4.)

– 05 External loopback adapter connected to the

port — A loopback plug is connected to the port. – 06 N_Port connection not allowed on this port —

The port is configured as an E_Port, but attaches to a node device.

– 07 Non-McDATA switch at other end of the ISL — The cable is connected to a non-EMC switch and the Interop Mode for this switch is set to McDATA Fabric.

– 08 ISL connection not allowed on this port — The port is configured as an F_Port, but attaches to another switch.


4

4-12


– 10 Port binding violation - unauthorized WWN — The WWN entered to configure port binding is not valid or a Nickname was used that is not configured through the Product Manager or Fabric Manager for the attached device.

– 11 Unresponsive node connected to port — Possible causes are: •Hardware problem on switch or on a connected node

where ELP frames are not delivered, the response is not received, or a fabric login in (FLOGI) cannot be received. There may be problems in the switch SBAR.

•Faulty or dirty cable connection.

•Faulty host bus adapters that do not send out an FLOGI within a reasonable timeframe.

• Reasons for segmentation:

– Incompatible operating parameters; for example, R_A_TOV or E_D_TOV might be inconsistent.

– Duplicate Domain IDs. – Incompatible zoning configurations.– Build fabric protocol error.– No switch in fabric is capable of being principal switch.– No response from an attached switch.

• Reason for an inactive state: optics speed conflict. An inactive state occurs if you set the port’s data speed to 2 Gb/sec for a 2 Gb/s port module, and then replace the port module with a 1 Gb/s module. To activate the port in this case, replace the module with a module that supports 2 Gb/s.

◆ Threshold Alert — If a threshold alert exists for the port, an alert indicator (yellow triangle) appears by the Threshold Alert field, and the configured name for the last alert received appears in the field.



Displaying SwitchProperties

To display a Switch Properties window, double-click the front view of the switch away from any ports (or right-click the switch away from any ports and click Properties on the pop-up menu).

The Switch Properties window displays:

◆ Switch name, description, location, and contact, as configured through the Configure Identification dialog box

◆ Fibre Channel WWN identifier for the switch

◆ Product type number

◆ Product model number

◆ Product manufacturer

◆ Product serial number

◆ Engineering change (EC) level

◆ Firmware level

◆ Management Style: Open Systems

◆ Preferred Domain ID (set through the Configure Operating Parameters dialog box)

◆ Active Domain ID (the actual Domain ID assigned to the switch)

◆ Fibre Channel Address Domain

◆ CTP state (active or inactive)

◆ Switch Speed: 2 Gb/s

◆ Switch Binding — Enabled if the optional Enterprise Fabric Extensions features are installed and enabled; otherwise, disabled.


4

4-14


Using Menu Options Right click on various parts of the Hardware view to display pop-up menu options for displaying status and information and for controlling the switch and various hardware components.

Switch Menu Right-click on any area of the switch illustration where a hardware component is not installed to display the following menu options:

◆ Switch Properties — Displays switch parameters. Refer to Displaying Switch Properties on page 4-13.

◆ Enable Unit Beaconing — Click the checkbox to toggle unit beaconing on or off. When the checkbox is checked, unit beaconing is on, and the system error light on the actual switch blinks to help users locate the unit in an equipment room. (The amber indicator on the Hardware view also blinks when beaconing is enabled. )

When you click the checkbox to remove the checkmark, unit beaconing is off and the amber LED goes out.

You can enable beaconing only if the system error light is off, meaning there are no system errors.

◆ Clear System Error Light — Turns off the amber system error light, located below the green/blue power LED on the switch. (This also turns off the amber system error light indicator in the Hardware view.)

◆ IPL Switch — Initiates an IPL on the switch.

Refer to Executing an IPL on page 7-4.

CAUTION!An IPL is not intended for ordinary or casual use and should be performed only when directed by your support personnel.

◆ Set Switch Date and Time — Sets the date/time. You can also configure the switch to synchronize its date and time to the Connectrix service processor. Refer to Configuring the Date and Time on page 5-31 for the procedure.

◆ Set Switch Online State —Displays the current state (off line or on line) and provides a button for changing the state. Refer to Setting the Online State on page 7-6 for more information.



CAUTION!Before setting the switch off line, warn administrators and users currently operating attached devices that the switch is going off line and that there will be a disruption of port operation. Also, request that the devices affected by an interruption of data flow be set off line.

Port Menu While in the Hardware view, right-click on any port to display the following menu options:

◆ Port Properties — Displays a Port Properties window, described under Displaying Port Properties on page 4-9.

◆ Port Technology — Displays a Port Technology window, which contains displays the following information:

• Port number

• Connector type: Always LC Connector

• Transceiver: Longwave Laser or Shortwave Laser.

• Distance: General distance range for port transmission. This can be either short to long distances for the longwave laser LC transceiver or short distances for the shortwave laser LC transceivers.

• Media: The Fibre Channel mode and optic size. For the longwave laser LC transceiver, this would be singlemode 9 micron. For the shortwave laser LC transceiver, this would be multimode 50-micron or 62.5-micron.

• Speed: 2 GBit/1 GBit.

◆ Block Port — Click to display a checkmark and block port transmission If the port is blocked, a node attached to the port is prevented from logging into the switch or communicating with other devices attached to switch ports. A blocked port continuously transmits offline sequences (OLS). Click to remove the checkmark and unblock the port. If unblocked, a node attached to the port can communicate with the switch and communicate with other nodes attached to the switch.

◆ Enable Beaconing — Click this to make the amber LED by the port blink on the actual switch and the amber indicator blink for the port in the Hardware view. This enables users to locate the


4

4-16


unit where the port is located. When a blinking amber LED indicator appears by a port, an attention indicator appears below the port's connector in the Hardware view.

◆ Port Diagnostics — This option is used by service personnel to run internal and external loopback tests on the port.

◆ Clear Link Incident Alert(s) — Click this to clear the attention indicators on the Hardware view, the Port List view, and the Performance view. In addition, the procedure clears the alert description in the Port Properties window. If there are no link incident alerts set for a port, no actions occur. Although you can manually clear link incidents, they may also be cleared by actions outside of the user interface, such as when rebooting the Connectrix service processor.

◆ Reset Port — Click to display a confirmation window; then click Yes to reset the port. If a switch is attached to the port and is on line, this operation sends a link reset to the attached switch, otherwise this action disables port beaconing for the port, and if the port is in a failed state, such as after failing a loopback test, the reset restores the port to an operational state, clearing the service required (amber) LED. The reset does not affect other ports in the switch.

◆ Port Binding — Allows you to enable or disable port binding. For details, refer to Configuring Ports on page 5-17.

◆ Clear Threshold Alert(s) — Allows you to clear threshold alerts. Select the appropriate option to clear alerts for the selected port only or all ports on the switch. This clears all attention indicators that notify users of threshold alerts in dialog boxes and views. This action also restarts the notification interval and the cumulative minutes for utilization % interval.

Figure 4-2 Clear Threshold Alert(s) Window

For more information on threshold alerts, refer to Configuring Threshold Alerts on page 5-33.



Using the Port List ViewTo display the Port List view (Figure 4-3), select the Product Manager Port List tab.

Figure 4-3 Port List View

The Port List view displays the following information on all ports that can be installed in the switch. All information is updated automatically.

◆ # — Port number: 0 through 23.

◆ Name — Port name as configured through the Configure Ports dialog box.

◆ Block Config — Blocked/unblocked configuration of the port as set through one of these:

• The Configure Ports dialog box.

• The Block Port option available through:

– Port right-click menus in the hardware view– Port row right-click menus in the Port List view

DS-24M2: S34-A

2

22

22

22

22

22

22

2

22

Using the Port List View 4-17

4

4-18


– Port bar graph right-click menus in the Performance viewPossible states are:

• Blocked — Devices communicating with the port are prevented from logging into the switch or communicating with other devices attached to switch ports. A blocked port continuously transmits OLS.

• Unblocked — Devices communicating with the port can log in to the switch and communicate with devices attached to any other unblocked port in the same zone.

◆ State — Can be any of the following:

• No Light• Online• Offline• Beaconing• Link Reset• Not Operational• Not Installed• Invalid Attachment• Port Failure• Segmented E_Port• Link Incident• Testing• Inactive

For more information on these states and corresponding alert symbol and LED indicator operations in the Hardware view, refer to Port Operational States on page 4-35.

◆ Type:

• E Port if another E_Port is attached

• F Port if an N_Port is attached

• FL Port if an NL_Port is attached

• G Port if the port is capable of acting as either an F_Port or an E_Port, but nothing is currently attached

• Fx Port if the port is an unconfigured Fx_Port, which is a configurable port type that restricts a port to operate either as an F_Port or FL_Port.

• Gx Port if the port is an unconfigured Gx_Port, which is a configurable port type that restricts a port to operate either as an F_Port, FL_Port, or E_Port.



◆ Operating Speed — The current data speed for the port: 1 Gb/sec, 2 Gb/sec, or Not Established. Not Established appears if Negotiate was set for the port through the Configure Ports dialog box and the data speed has not been resolved between the port and the attached device, or if the port and device are not communicating.

◆ Alert — Displays a yellow triangle if a link incident occurs on the port or if the port's LED is beaconing. red and yellow diamonds appear for port failures or for ports requiring service. Double-click the row to display the reason for the alert in the Port Properties window.

Displaying Port Properties

To display a Port Properties window for a port, double-click the port’s row (or right-click the row and click Port Properties on the pop-up menu). Refer to Displaying Port Properties on page 4-9 for descriptions of the port properties.

Menu Options Right-click a row to display a pop-up menu with the following port-related options. Refer to the pages shown for more information

◆ Port Properties — Refer to Displaying Port Properties on page 4-9.

◆ Port Technology — Refer to Port Menu on page 4-15.

◆ Block Port — Refer to Port Menu on page 4-15.

◆ Enable Beaconing — Refer to Port Menu on page 4-15.

◆ Port(s) Diagnostics — Is used by service personnel to run an internal loopback and external loopback test on the port.

◆ Clear Link Incident Alert — Refer to Port Menu on page 4-15.

◆ Reset Port — Refer to Port Menu on page 4-15.


◆ Clear Threshold Alert(s) — Allows you to clear threshold alerts. Select the appropriate option to clear alerts for the selected port only or all ports on the director. This clears all attention indicators that notify users of threshold alerts in dialog boxes and views. This action also restarts the notification interval and the cumulative minutes for utilization % interval.

Using the Port List View 4-19

4

4-20






Using the Node List ViewTo display the Node List view (Figure 4-5), select the Product Manager Node List tab.

This view displays information about all node attachments to any F_Ports on the switch, sorted by port number. All data is updated automatically as devices log in and log out.

Figure 4-5 Node List View

Information that appears for each node includes:

◆ Port # — Port number: 0 through 23.

◆ Address — Displays the Fibre Channel address of the node.

◆ Node Type — N_Port or NL_Port.

◆ Port WWN — Port World Wide Name of the attached node (N_Port). The WWN is prefixed by the manufacturer’s name of the host bus adapter that attaches to the device.

DS24M2: S34-A

Using the Node List View 4-21

4

4-22


If a nickname is assigned to the WWN and Display Options is set to Nickname, the nickname appears instead of the WWN. (Refer to Defining Nicknames on page 4-24.)

To change a node’s display between the WWN and nickname:

a. Right-click the port’s row.

b. On the pop-up menu, move the cursor over Display Options.

c. Click the desired option on the pop-up sub-menu.

◆ Unit Type — Attached device, (if the device provides this information):

The unit type comes directly from the device sense ID when the device attaches to the port during login. If the connection is lost to the device, the type appears as unspecified, since the device is no longer logged in to the port. When the device logs back in, the unit type is updated.

◆ BB_Credit — The buffer-to-buffer credit that the attached node has available.

Unknown

Other

Hub

Switch

Gateway

Converter

HBA

Proxy-agent

Storage device

Host

Storage subsystem

Module

Software driver



Displaying Node Properties

To display a Node Properties window for the attached node, double-click the node’s row (or right-click the row and click Node Properties on the pop-up menu).

Information for the node includes:

◆ Port Number — Physical port number on the switch to which the node is connected

◆ Node Type — N_Port or NL_Port

◆ Fibre Channel Address — 3-byte Fibre Channel address of the node

◆ Port WWN — Port World Wide Name of the attached device

◆ Port Nickname — Nickname (if configured) for the port WWN

◆ Node WWN — Node World Wide Name (if configured) of the attached device

◆ Node Nickname — Nickname (if configured) for the node WWN.

◆ Unit Type — The device connected to the port

◆ Node Port Number — Node port connected to the switch.

◆ Buffer-to-Buffer Credit — Buffer-to-buffer credit that the attached node has available.

◆ Class of Service — Can be Class 2, Class 3, or both.

◆ Data Field Size — Largest size of Fibre Channel frame the node will process. The size is negotiated with the attached device.

Displaying Port Properties

To display a Port Properties window for the port connected to a node, right-click the node’s row; then click Port Properties on the pop-up menu. Refer to Displaying Port Properties on page 4-9 for descriptions of the port properties.

Using the Node List View 4-23

4

4-24


Defining Nicknames To define or change a nickname:

1. Right-click the node’s row; then click Define Nickname on the pop-up menu. This displays the dialog box in Figure 4-6.

Figure 4-6 Define Nickname Dialog Box

2. Enter a nickname, up to 32 alphanumeric characters. Spaces, hyphens, and underscores are allowed.

Nicknames for N_Ports should describe those ports. For example, a Windows NT Exchange server might have the nickname NT Exch HBA 1, and a WWN of a Symmetrix port might have the nickname Symm 0415 FA 1A.

3. Click OK to save the nickname.

Displaying Nicknames To change a node’s display between the WWN and nickname:

1. Right-click the node’s row in the Node List view.

2. On the pop-up menu, move the cursor over Display Options.

3. Click the desired option on the pop-up sub-menu.



Using the Performance ViewTo display the Performance view (Figure 4-7), select the Product Manager Performance tab. This view displays a bar graph for each port. The lower portion of the view displays statistical values for a selected port.

Figure 4-7 Performance View

DS-24M2: S34-A

Using the Performance View 4-25

4

4-26


As shown in Figure 4-7, the default view displays only the first 16 ports. You can display more ports in any of these ways:

◆ Drag the scroll bar at the upper right to display subsequent rows one at a time.

◆ Click the Down arrow at the left side of the window (shown below) to expand the port display to show all ports. (This hides the Statistics Values table.)

◆ Move the cursor over the double lines to the right of the arrows (shown in the previous item). When the cursor changes to an Up/Down arrow, hold down the mouse button and drag the Statistics values portion of the screen down.

Bar Graph Display The Performance view provides a graphical display of performance for all ports. Each bar graph in the upper portion of the main panel displays the percentage of link utilization for the port. This information is updated every five seconds. Each bar graph shows the percentage of link utilization for the port; a red arrow marks the highest utilization since the opening of the Performance view. (If the system detects activity on a port, it represents minimal activity with one bar.)

When a port is logged in, moving the cursor over its bar graph displays a pop-up message:

◆ If the port is not logged in, the message displays the port’s current operational state. (Refer to Table 4-3 on page 4-35.)

◆ If the port is an F_Port and is logged in, the message displays the attached port’s WWN or nickname.

◆ If the port is an E_Port and is logged in, the message says E_Port.

Click hereto expandor collapseport display

DS-24M2: S34-A



Port Statistics To select and display more detailed performance information for a port, click the port’s bar graph. A darker background highlights the bar graph for that port, and the lower portion of the Performance view displays the statistics values for the port. The Statistics Values tables contain cumulative port statistics and error statistics.

Click a category in the left frame of the statistics area to display only statistics for that category, or click All to display values for all categories.

There are no thresholds for these values. You can determine that a problem exists by the rate that the value changes. BB_Credit starvation can occur if data is sent to a device faster than the device can process the frames. Such a suituation can back up into ISLs, degrading performance.

Refresh/Clear The two buttons located at the right end of the title bar on the Statistics Values table are:

◆ Refresh — Updates the data in the statistics tables and enables you to compare values at any given time. Note that you can also refresh data by clicking the port’s bar graph.

◆ Clear — Clears all counters to zero. Selecting this button displays a Clear Port Statistics window. The user can select options to clear statistics on a selected port only or all ports on the product. Confirming the request clears the statistics counters. Note that this also clears counters for other Product Manager users.

An entry identifying when the statistics were cleared and by whom is saved in the Audit Log.

As a general rule, you should clear all counts after the system is stabilized. When looking at the Performance View, keep track of the approximate time interval when errors accumulate, to judge the presence and severity of a problem. Also, recognize that there is a link recovery hierarchy implemented in Fibre Channel to handle some level of expected anomalies. In general, be concerned only with error counts that increment very quickly.


4

4-28


Class 2 Statistics These statistics relate to Class 2 frames:

◆ Received Frames — The number of Class 2 frames received by this F_Port from its attached N_Port.

◆ Transmitted Frames — The number of Class 2 frames transmitted by this F_Port to its attached N_Port.

◆ Busied Frames — The number of F_BSY frames generated by this F_Port against Class 2 frames. This can occur if frames are received before the switch completes initialization or if the switch is servicing so many reequests that it cannot process a new request.

The port generates frames if the switch is not ready to accept commands. This might indicate temporary congestion.

◆ Rejected Frames — The number of F_RJT frames generated by this F_Port against Class 2 frames.

These frames usually occur because of errors at the attached device. The device is expected to correct the error based on the reject code, then retry its request. If the device is able to recover, there is no cause for concern. If the device cannot recover, further troubleshooting may be necessary.

There are no thresholds for this value. Typically, F_RJT frames occur because the destination is not available due to the device’s action.

◆ Four Byte Words Rx — The number of 4-byte words received.

◆ Four Byte Words Tx — The number of 4-byte words transmitted.

Class 3 Statistics These statistics relate to Class 3 frames:

◆ Received Frames — The number of Class 3 frames received by this F_Port from its attached N_Port.

◆ Transmitted Frames — The number of Class 3 frames transmitted by this F_Port to the attached N_Port.

◆ Discarded Frames — The number of Class 3 frames discarded, including multicast frames with bad D_IDs.

The switch increments this count when it discards a frame that cannot be routed. This occurs most frequently when a destination becomes unavailable without the source realizing it.



There are no thresholds for this value. Typically, this occurs when the destination is not available due to the destination device’s action.

◆ Four Byte Words Rx — The number of 4-byte words received.

◆ Four Byte Words Tx — The number of 4-byte words transmitted.

Error Statistics Error statistics show whether or not a port is operating correctly. Use this data to isolate problems with port and link operations:

◆ Link failures — The number of link failures. A link failure is recorded in response to a not operational sequence (NOS), protocol timeout, or port failure. A yellow triangle appears in the Hardware view to indicate a link incident. A red and yellow diamond appears to indicate a port failure.

◆ Sync losses — The number of loss-of-synchronization errors, which occur if the attached device is reset or disconnected from the port. A yellow triangle appears in the Hardware view to indicate a link incident.

◆ Signal losses — The number of loss-of-signal errors, which occur if the attached device is reset or disconnected from the port. A yellow triangle appears in the Hardware view to indicate a link incident.

◆ Primitive sequence errors — The number of primitive sequence protocol errors. A yellow triangle appears in the Hardware view to indicate a link incident.

◆ Discarded frames — The total number of frames discarded. A received frame cannot be routed and is discarded if the frame times out (insufficient buffer-to-buffer credit) or the destination device is not logged in to the switch.

◆ Invalid transmission words — The number of times that the switch detected invalid transmission words from the attached device. This indicates that a frame or primitive sequence arrived at the switch’s port corrupted. This corruption can be due to the attached device performing a reset, plugging or unplugging the link, bad optics at either end of the cable, bad cable, or a dirty or poor connection. Moving the connection around or replacing cables can isolate the problem.

Some number of invalid transmission words are expected and acceptable. Invalid transmission words within a frame are used to produce the bit-error threshold link incident. If one or more


4

4-30


invalid transmission words are detected in 12 separate 1.5-second samples within five minutes, a bit-error threshold link incident is generated.

◆ CRC errors — The number of invalid cyclic redundancy checks. Failed CRC validation indicates that the frame arrived at the switch’s port corrupted. Frame corruption can be caused by device disconnection, an optical transceiver failure at the device, a bad fiber-optic cable, or a poor cable connection.

◆ Delimiter errors — The number of times that the switch detected an unrecognized start-of-frame (SOF), an unrecognized end-of-frame (EOF) delimiter, or an invalid class of service. This indicates that the frame arrived at the switch’s port corrupted. This corruption can be due to plugging/unplugging the link, bad optics at either end of the cable, bad cable, or dirty or poor connections. Moving the connection around or replacing cables can isolate the problem.

◆ Address ID errors — The number of address identifier errors. A received frame had an unavailable or invalid Fibre Channel destination address, or an invalid Fibre Channel source address. This typically indicates that the destination device is unavailable.

◆ Frames too short — The number of received frames that exceeded the Fibre Channel frame maximum size or were less than the Fibre Channel minimum size, indicating the frame arrived at the director’s port corrupted. Frame corruption may be caused by device disconnection, an optical transceiver failure at the device, a bad fiber-optic cable, or a poor cable connection.

Operational Statistics Operational Statistics are:

◆ Offline sequences Rx — The number of offline sequences that the port has received.

◆ Offline sequences Tx — The number of offline sequences that the port has transmitted.

◆ Link resets — The number of link reset protocol frames received/transmitted by this port from/to the attached device. The director transmits a link reset to initiate the link reset protocol or recover from a link timeout. This occurs normally to establish BB_Credit or on any port in order to recover lost BB_Credit. The director receives a link reset from an attached device if the device wishes to initiate the link reset or recover from a link timeout.



Traffic Statistics The Traffic Statistics table show two sets of values: Receive and Transmit. The bar graphs displays the larger of the two values:

◆ Link utilization % —The percentage of the maximum link utilization (100%) currently being used. Link utilization is calculated over one-second intervals. (Each port can transmit or receive data at 100 MB/s.)

There are separate values for transmit (Tx) and receive link utilization (Rx). The larger of these two values appears on the bar graph.

◆ Frames Rx — The number of frames that the port has received.

◆ Frames Tx — The number of frames that the port has transmitted.

◆ Four byte words Rx — The number of words that the port has received.

◆ Four byte words Tx — The number of words that the port has transmitted.

Menu Options Right-clicking a bar graph displays a pop-up menu with the following port-related options. Refer to the pages shown for more information:

◆ Port Properties — Refer to Displaying Port Properties on page 4-9.

◆ Port Technology — Refer to Port Menu on page 4-15.

◆ Block Port — Refer to Port Menu on page 4-15.

◆ Enable Beaconing — Refer to Port Menu on page 4-15.

◆ Diagnostics — Is used by service personnel to run an internal loopback and external loopback test on the port.

◆ Clear Link Incident Alert — Refer to Port Menu on page 4-15.

◆ Reset Port — Refer to Port Menu on page 4-15.


◆ Clear Threshold Alert(s) — Allows you to clear threshold alerts. Select the appropriate option to clear alerts for the selected port only or all ports on the director. This clears all attention indicators that notify users of threshold alerts in dialog boxes and views. This action also restarts the notification interval and the cumulative minutes for utilization % interval.


4

4-32






Using the FRU List ViewTo display the FRU List view (Figure 4-9), select the Product Manager FRU List tab. This view displays information about all installed FRUs on the switch. All data is updated automatically as the software detects changes.

This view does not list optics as FRUs. Display the Port List view to obtain the status of optics.

Figure 4-9 FRU List View

DS-24M2 : S34-A

Using the FRU List View 4-33

4

4-34


Information on the FRU List view for each FRU includes:

◆ FRU:

• CTP (Control Processor).

• PWR (power supply module).

The CTP is an internal component; if it fails completely, the entire switch must be replaced.

◆ Position — Slot position of FRU in the unit relative to identical FRUs also installed in the unit.

There are one CTP subsystem and two power supplies (0 and 1)

◆ Status:

• Active — Always appears unless the FRU has failed.

• Failed — Appears if the FRU is not functional.

◆ Part Number — Part number of the FRU.

◆ Serial Number — Serial number of the FRU.



Port Operational StatesTable 4-3 describes the port states and the LED indicators and alert symbols that appear in the Hardware view and Port List view.

Table 4-3 Port States

Port Indicators

Alert Symbol Port State DescriptionGreen/Blue Amber

On Off None On line The attached device has successfully connected to the switch and is ready to communicate, or is in the process of communicating with other attached devices. As long as the port remains in the online state, the green port LED remains illuminated. On the actual port, the LED blinks when there is active Fibre Channel traffic.

On Off Yellow triangle Invalid attachment

The reasons for this state appear in the Reason field of the Port Properties window.

Segmented E_Port

The E_Port is segmented, preventing the two fabrics from joining. (This occurs only when two switchs are connected to each other.) Display the Port Properties window to view the segmentation reason.

On Blinking Yellow triangle Testing and/or Beaconing

The port is beaconing. When beaconing is enabled, the amber LED on the actual port blinks every two seconds to help users find the port. Among other reasons, is enabled if the port is executing an external loopback test.

Off

Off On Red and yellow diamond

Port failure The switch port has failed and requires service. The amber LED for the port remains illuminated.

Off Off None Off line The switch port was configured as blocked and is transmitting the Fibre Channel OLS to the attached device.

No light No signal (light) is being received on the switch port. This is a normal condition when no cable is plugged into the port or when the power of the device attached to the other end of the link is off.

Port Operational States 4-35

4

4-36


Off Off Yellow triangle Off line The switch port was configured as unblocked and is receiving the Fibre Channel OLS, indicating that the attached device is off line.

Link incident A link incident occurred on the port.

Link reset The switch and the attached device are performing a link reset operation to recover the link connection. Ordinarily, this is a transient state that should not persist.

Not operational

The switch port is receiving a Fibre Channel NOS (not operational sequence), indicating that the attached device is not operational.

Inactive The switch port is in an inactive state. Reasons for this state appear in the Reason field of the Port Properties dialog box.Note that if port optics have also failed, the amber LED will be on.

Not Installed The port optics are not installed or the feature that provides additional port function is not enabled.

Table 4-3 Port States (continued)

Port Indicators

Alert Symbol Port State DescriptionGreen/Blue Amber



AlertsThe system can generate two types of alerts:

◆ Link incident alerts, which are generated because of a problem.

◆ Threshold alerts, which are generated when throughput reaches a predetermined level.

Link Incident Alerts A link incident (LIN) is a problem detected on a fiber-optic link; for example, loss of light, or invalid sequences. When a LIN occurs, a LIN alert is sent to the Link Incident Log in the Product Manager. LIN alerts warn you that there is a link incident detected through a port connection that may require operator intervention to correct.

If LIN alerts are enabled for a port, an alert causes a yellow triangle to appear next to the port connector in the Hardware view, and in the Alert column in the Port List view.

Double-clicking on the port in the Hardware view or Port List view displays the Port Properties window. If LIN alerts are enabled for the port, the window contains a short description of the latest incident in the Link Incident field. (If there are no active incidents, None appears.)

To receive e-mail notification of LIN alerts, do all of these:

◆ Enable LIN alerts in the Configure Ports dialog box.

◆ Configure e-mail notification through the Connectrix Manager.

◆ Enable e-mail notification through the Product Manager Maintenance menu.

E-mail notification of LIN alerts is available to all users; no user rights are imposed.

Refer to Link Incident Log on page 6-9 for more information on the type of link errors that are logged.

Alerts 4-37

4

4-38


Clearing Link IncidentAlerts

Although you can clear the yellow triangle from the Hardware view and the alert description in the Port Properties window manually, they may also be cleared by actions outside of your control (such as on Connectrix service processor reboot).

You can clear the yellow triangle from the Hardware view and the description in the Link Incident field manually. Right-click the port and select Clear Link Incident Alert(s) from the menu. In the Clear Link Incident Alert(s) window (Figure 4-10), select an option and click OK.(If there are no link incident alerts enabled for a port, no actions occur.) Be aware that clearing the incident indicator clears it for everyone using the system.

Figure 4-10 Clear Link Incident Alert Window

Threshold Alerts A threshold alert notifies Product Manager users when the transmit (Tx) or receive (Rx) throughput reaches specific values for switch ports or port types (E_Ports or F_Ports).

Threshold alerts occur as the following in the Product Manager:

• An attention indicator (yellow triangle) that appears on the port card in the Hardware view.

• An attention indicator (yellow triangle) that appears in the Alert column of the Port List view.

• An attention indicator (yellow triangle) that appears by the Threshold Alerts field in the Port Properties window.

• Detailed threshold alert data recorded in the Threshold Alert Log.



5Invisible Body Tag

This chapter describes the options that appear in the drop-down menu when you select Configure on the Product Manager’s menu bar.

◆ Configuring Switch Identification ...................................................5-2◆ Configuring Operating Parameters.................................................5-4◆ Configuring Switch Binding...........................................................5-12◆ Configuring Ports.............................................................................5-17◆ Configuring the SNMP Agent........................................................5-24◆ Configuring Management Server Control....................................5-27◆ Configuring Feature Keys...............................................................5-28◆ Configuring the Date and Time .....................................................5-31◆ Configuring Threshold Alerts ........................................................5-33◆ Exporting a Configuration Report.................................................5-41◆ Enabling the Embedded Web Server.............................................5-43◆ Enabling Telnet .................................................................................5-44

Configuring the Switch

Configuring the Switch 5-1

5

5-2


Configuring Switch IdentificationThis section describes the procedure for configuring parameters that identify the switch in various displays.

To configure identification for the switch, follow these steps:

1. Click Configure on the Product Manager menu bar and select Identification on the drop-down menu.

This displays the Configure Identification dialog box (Figure 5-1).

Figure 5-1 Configure Identification Dialog Box

2. Configure the parameters as follows:

• Name — Enter a name for the switch, up to 24 alphanumeric characters. Note, however, that typical screen sizes generally limit the display to 17 characters when the name appears under the product icon on Connectrix Manager screens.

If Network Address is specified for the Connectrix Manager display option, the full product name appears in a pop-up box if flyover is enabled and you move the cursor over the product icon.

As an example, the name could reflect the director’s Ethernet network domain name service (DNS) host name.

This name will appear in the following locations:

– Switch icon label in the Connectrix Manager Products view, if the display options are set to display product names

– Product Manager window title panel– Identification table at the top of the Hardware view– Switch Properties window


5Configuring the Switch

• Description — Enter a description that will further identify the switch. The entry can be longer than 24 characters; however, the size of user’s display determines how much of a lengthy entry will appear.

This description will appear in the following locations:

– Identification table at the top of the Hardware view– Switch Properties window

• Location — Enter information that describes the location of the switch. The entry can be longer than 24 characters; however, the size of the user’s display determines how much of a lengthy entry will appear.

This location information will appear in the following locations:

– Identification table at the top of the Hardware view– Switch Properties window

• Contact — Enter identifying information about a contact person, such as a phone number, title, and/or e-mail address. The entry can be longer than 24 characters; however, the size of the user’s display determines how much of a lengthy entry will appear.

This contact information will appear in the Switch Properties window.

• Set Name as Nickname — If this box is checked, the name in the Name field will become a nickname for the switch’s WWN. Click the box to add or remove a checkmark.

If this option is enabled, the nickname appears instead of the WWN in Product Manager views.

3. Click Activate to save the data and close the dialog box.

4. If you are finished configuring the switch, back up the configuration data. For more information, refer to Backing Up and Restoring the Configuration on page 7-10.

Configuring Switch Identification 5-3

5

5-4


Configuring Operating ParametersUse the procedures in this section to configure parameters on the switch for operation over Fibre Channel. These parameters are stored in NV-RAM on the switch.

Ordinarily, you do not need to change these values from their defaults. The only exception is the Preferred Domain ID. Change this value if the switch will participate in a multiswitch fabric.

To configure operating parameters for the switch:

1. Set the switch off line:

CAUTION!Setting the switch off line terminates all Fibre Channel connections.

a. Click Maintenance on the Product Manager menu bar and select Set Online State on the drop-down menu.

This displays the window in Figure 5-2.

Figure 5-2 Set Online State Window

b. Click Set Offline.

2. Click Configure on the Product Manager menu bar and select Operating Parameters, then Switch Parameters, from the drop-down menus.

3. Configure the switch parameters as necessary. Refer to Switch Parameters on page 5-5 for descriptions of the parameters.

4. Click Activate to save the configuration and close the dialog box.

5. Click Configure on the Product Manager menu bar and select Operating Parameters, then Fabric Parameters, from the drop-down menus.



6. Configure the fabric parameters as necessary. Refer to Fabric Parameters on page 5-8 for descriptions of the parameters:

7. Click Activate to save the configuration and close the dialog box.

8. Set the switch on line.


b. On the Set Online State window, click Set Online.

9. Back up the configuration data when you are finished configuring the switch. For more information, refer to Backing Up and Restoring the Configuration on page 7-10.

Switch Parameters The switch parameters are described below:

Figure 5-3 Configure Switch Parameters Dialog Box

Preferred Domain ID Use this field to set a unique Domain ID for each director and switch in the fabric. Fibre Channel addresses in the switch include this Preferred Domain ID, which creates a unique identification for the port in the fabric.

Set a Preferred Domain ID value in the range 1 through 31. (The default value is 1.)

CAUTION!The Domain ID must be unique for each director/switch in a fabric. If two directors/switches have the same Domain ID, the E_Ports (and the fabric) become segmented.

Configuring Operating Parameters 5-5

5

5-6


When a director/switch comes on line with a preferred domain ID, it requests an ID from the fabric’s principal switch (indicating its preferred value as part of the request). If the requested domain ID is not allocated to the fabric, the domain ID is assigned to the requesting director/switch. If the requested domain ID is already allocated, an unused domain ID is assigned.

Insistent

This option is supported only if the Enterprise Fabric Extensions feature is installed, and is required if Enterprise Fabric Mode is enabled. (Refer to the Connectrix Manager Version 7.01 User Guide for more information on these features.)

If this option is enabled (checked), the Preferred Domain ID will become the active domain identification when the fabric initializes. Click the checkbox to remove or add a checkmark. (The default state is no checkmark.)

The Fabric Binding feature (described in the Connectrix Manager Version 7.01 User Guide) requires a static and unique domain identification, because the feature's fabric membership list identifies switches by WWN and Domain ID.

If a duplicate preferred domain ID is used, and then insisted, warnings occur when directors/switches are added to a fabric membership list.

Note the following:

◆ If Fabric Binding or Enterprise Fabric Mode is enabled, the Insistent Domain ID option is enabled automatically.

◆ Disabling the Insistent option while the switch is on line disables both Enterprise Fabric Mode and Fabric Binding. (You can disable the option while the switch is off line without affecting Enterprise Fabric Mode or Fabric Binding.)

◆ If you enable the Insistent option while the switch is on line, the Preferred Domain ID changes to the current active domain ID if the IDs are different.



Rerouting Delay This option is applicable only if the switch is in a multiswitch fabric, and must be enabled if Enterprise Fabric Mode (an optional Enterprise Fabric Extensions feature) is enabled.

Enabling (checking) this option ensures that frames are delivered in order through the fabric to their destination. Click the checkbox to remove or add a checkmark. (The default state is disabled.)

If there is a change to the fabric topology that creates a new path (for example, a new switch is added to the fabric), frames may be routed over this new path if its hop count is less than a previous path with a minimum hop count. This may result in frames being delivered to a destination out of order since frames sent over the new, shorter path may arrive ahead of older frames still in route over the older path.

If the rerouting delay is enabled, traffic ceases in the fabric for the time specified for E_D_TOV. This delay allows frames sent on the old path to exit to their destination before new frames begin traversing the new path.

Domain RSCNs This option must be enabled if Enterprise Fabric Mode (an optional Enterprise Fabric Extensions feature) is enabled.

If this option is enabled (checked), Domain RSCNs (register for state change notifications ) are sent between end devices in a fabric to provide additional connection information to host bus adapters (HBAs) and storage devices.

Click the checkbox to remove or add a checkmark. (The default state is disabled.)

As an example, this information might be that a logical path has been broken because of a physical event, such as a fiber-optic cable being disconnected from a port. Consult with your HBA and storage device vendor to determine if enabling Domain RSCNs will cause problems with your HBA or storage products.

Suppress RSCNs onZone Set Activations

If this option is disabled (unchecked), fabric-format RSCNs are sent to ports on the director following any change to the fabric’s active zone set.

Click the checkbox to remove or add a checkmark.

In most cases, you should leave this parameter at the default state of disabled, so attached devices can receive notification of zoning changes in the fabric. However, some HBAs might log out, and then log back in to the fabric when they receive an RSCN, thereby


5

5-8


disrupting Fibre Channel traffic. Consult your HBA vendor and your EMC representative to determine if fabric-format RSCNs will cause problems with your HBA or storage products.

Fabric Parameters The fabric parameters are described below:

Figure 5-4 Configure Fabric Parameters Dialog Box

Unlike other Connectrix M-series switches, the DS-24M2 does not support configurable BB_Credits (buffer-to-buffer credits):

◆ Ports 0 through 3 are set to 12 BB_Credits each.

◆ Ports 4 through 23 are set to 5 BB_Credits each.

R_A_TOV Configure resource allocation time-out value (R_A_TOV) in tenth-of-a-second increments. This variable works with the error detect time-out value (E_D_TOV) variable to control the director’s behavior when an error condition occurs. Resources are allocated to a circuit when errors are detected and are not released for reuse until the time set by the R_A_TOV value expires. Set a value in the range 10 through 1200 (tenths of a second, or 1 through 120 seconds). (The default value is 100 tenths, or 10 seconds)

Set the same value for R_A_TOV on all directors and switches in a multiswitch fabric. If the value is not the same on all units, the fabric segments. Also, the value for R_A_TOV must be greater than the value configured for E_D_TOV.



E_D_TOV Adjust the E_D_TOV in tenth-of-a-second increments. An error condition occurs when an expected response is not received within the time limit set by this value. Set a value in the range 2 through 600 (tenths of a second; in other words, 0.2 through 60 seconds). (The default value is 20 tenths, or 2 seconds.)

EMC recommends leaving the timeout values at their defaults. These are the defaults used for all HBA and Symmetrix microcode testing for both benign and fault injection cases.

Switch Priority Every multiswitch fabric contains one principal switch, which assumes domain address manager functionality, and controls the allocation and distribution of Domain IDs for all switches in the fabric (including itself).

The Switch Priority settings for all switches in the fabric determine the selection of the principal switch. Valid settings are:

◆ Principal◆ Default◆ Never Principal

EMC recommends leaving the setting for each director/switch at Default

A principal switch is selected through negotiation during the Build Fabric process that follows any of these occurrences:

◆ Multiple directors/switches are interconnected to form a fabric.

◆ A director/switch is removed from the fabric.

◆ A director/switch with Management Style set to Open Systems and Interop Mode set to McDATA 1.0 is added to the fabric. (The management style on the DS-24M2 is always Open Systems.)

◆ An ISL is removed.

The principal switch is determined as follows:

◆ If one (and only one) director/switch is set to Principal, it becomes the principal switch. This switch remains the principal switch as long as it is on line in the fabric, even if someone changes another switch’s Switch Priority to Principal.

◆ If more than one director/switch is set to Principal, the director/switch with the lowest WWN number among those set to Principal becomes the principal switch.


5

5-10


The Switch Priority setting for every other switch/director (including any others that were previously set to Principal) automatically changes to Default.

In some two-tier fabrics (consisting of backbone and edge switches), EMC recommends configuring all backbone switches as Principal, to provide backup in the event of a failure. (This prevents an edge switch from becoming principal.) For more information, consult your EMC representative.

◆ If no director/switch is set to Principal but one or more are set to Default, the director/switch with the lowest WWN number among those set to Default becomes the principal switch.

The Switch Priority setting for every other switch/director remains unchanged.

◆ If all directors/switches are set to Never Principal, no director/switch can be principal. In this case, all of the ISLs will segment, with reason code 05 (no switch is capable of becoming a principal switch).

If all but one director/switch in the fabric is set to Never Principal, and the principal switch goes off line, all remaining ISLs will segment, with reason code 05.

If the principal switch was selected by WWN, adding a switch with a lower WWN does not change the principal if the newly added switch is set to Open Fabric 1.0 Interop Mode. (Refer to Interop Mode on page 5-11.) This is because adding such a switch does not cause a Build Fabric process. The next time a Build Fabric occurs, however, the switch with the lowest WWN will become principal.

In some logs, Switch Priority settings map to numbers: Principal = 1, Default = 254, Never Principal = 255.



Interop Mode Select one of the following options:

◆ McDATA Fabric 1.0 — if all switches in the fabric are in this list:

– ED-1032– ED-64M– ED-140M– DS-16M– DS-16M2– DS-24M2– DS-32M– DS-32M2

◆ Open Fabric 1.0 — if one or more switches in the fabric are not in the above list.


5

5-12


Configuring Switch BindingUsing switch binding, you can specify which devices and switches can attach to the switch ports. This provides security in environments that include a large number of devices, by ensuring that only the intended set of devices attach to the switch.

Configuring switch binding involves these operations:

◆ Activating switch binding.

◆ Determining the port types (E_Ports and/or F_Ports) to which you want to restrict access. In a separate operation (described in the next list item), you select which specific ports within the selected port type(s) will be restricted.

◆ Create/modify a Switch Membership List to specify which connected devices will be allowed/denied access to the switch.

Activating Switch Binding and Selecting Port Types

From the Hardware view Configure menu:

1. Select Switch Binding, Change State to display the dialog box shown in Figure 5-5.

Figure 5-5 Switch Binding — State Change Dialog Box

2. If the Enable Switch Binding checkbox is checked, switch binding is enabled. Click the box to add or remove a checkmark.



3. Once you have enabled switch binding, you can specify the port types that will be affected. Select an option under Connection Policy (or leave it at the default setting of Restrict All Ports).

4. Click Activate to activate switch binding.

When the switch binding feature is first installed and has not been activated, the membership list is empty. Activating switch binding while the switch is on line populates the membership list depending on the connection policy.

If you activate switch binding while the switch is off line, the membership list is not automatically populated.

If you previously enabled switch binding and edited the membership list, enabling switch binding (while the switch is either on line or off line) populates with membership list with WWNs that you previously allowed in the list.

5. Follow the steps under Editing the Switch Membership List to specify which connected devices will have access to the switch.

Selection Result

Restrict E_Ports All switches connected to E_Ports on the DS-24M2 will be prohibited access to the DS-24M2 except those switches you add to the Switch Membership List (described under Editing the Switch Membership List on page 5-14). No devices connected to F_Ports on the DS-24M2 will be prohibited.

Restrict F_Ports All devices connected to F_Ports on the DS-24M2 will be prohibited access to the DS-24M2 except those devices you add to the Switch Membership List. No switches connected to E_Ports on the DS-24M2 will be prohibited.

Restrict All Ports All switches and devices connected to E_Ports and F_Ports on the DS-24M2 will be prohibited access to the DS-24M2 except those switches and devices you add to the Switch Membership List.

Configuring Switch Binding 5-13

5

5-14


Editing the Switch Membership List

From the Hardware view Configure menu:

1. Select Switch Binding, Edit Membership List to display a screen similar to Figure 5-6.

Figure 5-6 Switch Binding — Membership List

If nicknames are configured for WWNs (through the Connectrix Manager) and you want these to appear instead of WWNs in this window, click Display Options. On the Display Options dialog box, select Nickname and click OK.



2. The Node List on the left lists the WWNs of all switches/devices connected to the switch, and the Switch Membership List on the right lists all switches/devices that are allowed access to the switch.

• To prohibit connection to a switch port from a WWN currently in the Membership List, select the WWN/nickname in the Membership List and click Remove.

• To allow connection to a port not in the list, select the WWN/nickname in the Node List and click Add.

• To add a WWN/nickname for a device/switch not currently connected to the switch, click Detached Node. On the Add Detached Node dialog box, enter the appropriate WWN or nickname (if configured through the Connectrix Manager) and click OK.

3. Click Activate to activate the changes and close the dialog box.

Switch Binding: Rules and Guidelines

In order for switch binding to function, specific operating parameters and optional features must be enabled. Also, there are specific requirements for disabling these parameters and features when the switch is off line or on line. Be aware of the following:

◆ You can enable or disable switch binding whether the switch is off line or on line.

◆ Enabling Enterprise Fabric Mode automatically enables switch binding.

◆ If the switch is on line, you cannot disable switch binding if Enterprise Fabric Mode is enabled.

If the switch is off line, you can disable switch binding, but this also disables Enterprise Fabric Mode (if it was enabled).

◆ You can add WWNs/nicknames to the Switch Membership List whether or not switch binding is enabled.

◆ If the switch is on line and switch binding is not enabled, all switches/devices attached to the switch are automatically added to the Switch Membership List.

◆ You can remove WWNs/nicknames from the Switch Membership List if any of the following is true:

• The switch is off line.

• Switch binding is disabled.

Configuring Switch Binding 5-15

5

5-16


• The switch/device with the WWN/nickname is not connected to the switch.

• Switch binding is not enabled for the same port type as enabled for the Connection Policy in the Switch Binding State Change dialog box. For example, you can remove the WWN/nickname for a switch attached to an E_Port if the Connection Policy was enabled to restrict F_Ports only.

• The switch/device with the WWN/nickname is connected to a port that is blocked.

• The switch/device with the WWN/nickname is a detached node (not currently connected to the switch).

Zoning with Switch Binding Enabled

Enterprise Fabric Extensions has no effect on existing zoning configurations. However, if a device WWN is in a specific zone but the WWN is not in the Switch Membership List, the device cannot log in to the switch port and cannot connect to other devices in the zone with switch binding enabled.



Configuring PortsUse the procedures in this section to configure identification and operating parameters for ports on the switch. Port configuration data is stored in NV-RAM on the switch.

When adding and/or configuring ports, refer to Figure 5-7 for the physical locations of the ports.

Figure 5-7 DS-24M2 Port Numbering

Follow these steps to configure ports:

1. Click Configure on the Product Manager menu bar and select Ports on the drop-down menu.

This displays the Configure Ports dialog box (Figure 5-8).

Figure 5-8 Configure Ports Dialog Box

22 20 18 16 14 12 10 8 6 4 2 0

23 21 19 17 15 13 11 9 7 5 3 1

Configuring Ports 5-17

5

5-18


2. Configure the port parameters, referring to Port Parameters on page 5-19.

3. Click Activate to activate changes and close the dialog box.

If the format for a WWN or nickname in the Bound WWN column is invalid, an error message appears.

If the Port Binding column is checked for a port and the WWN or nickname in the Port Binding column does not match the device actually connected to the port, a warning (Figure 5-9) appears, listing all ports that have a mismatch.

Figure 5-9 Bound WWN Mismatch Warning

If you click Continue, all the listed nodes will be logged off, and the switch ports will attach to the repective devices identified in the Bound WWN column.




Port Parameters The port parameters are described below:

Port # This is the physical port number: 0 through 23. You cannot edit this field.

Name Port names appear in several Product Manager windows. Enter a name here to identify the end device connected to the port. For example, if the server name is XYZ, you might use XYZ Server.

To identify port numbers for which you want to provide names, move the cursor over the ports in the Hardware view. As you move over a port, a pop-up window identifies the slot number where the port is installed.

If you want to delete all port names from the switch, right-click anywhere in the Name column; then click Clear All Port Names on the pop-up menu.

Blocked This setting determines whether port operation is enabled (if the box is checked) or disabled. Click a checkbox to add or remove a checkmark.

To block or unblock all ports in the switch, right-click anywhere in the Blocked column; then click Unblock All Ports or Block All Ports on the pop-up menu.

LIN Alerts This setting determines whether link incident (LIN) alerts will be noted (if the box is checked) in these locations:

◆ in the Alert column of the Port List view

◆ by a yellow triangle next to the port connector in the Hardware view

◆ in the Link Incident field of the Port Properties window

Click a checkbox to add or remove a checkmark. The default setting is checked (LIN Alerts enabled).

To enable or disable LIN Alerts on all ports in the switch, right-click anywhere in the LIN Alerts column; then click Clear All LIN Alerts or Set All LIN Alerts on the pop-up menu.

LINs are always logged in the Link Incident Log, regardless of the configuration.

Refer to Link Incident Alerts on page 4-37 for more information.


5

5-20


FAN This setting determines whether Fabric Address Notification for loop devices is enabled (if the box is checked) or disabled on a port. Click a checkbox to add or remove a checkmark.

Type Select each port’s type (G_Port, F_Port, E_Port, Fx_Port, or Gx_Port) in this column from the drop-down list.

To set all ports in the switch to the same type, right-click anywhere in the Type column; then click Set All to <port type> on the pop-up menu.

Speed This sets the data rate for the port. Click this column on a port’s row to display a drop-down list; then click the desired type:

◆ 2 Gb/sec

◆ 1 Gb/sec

◆ Negotiate — Allows the port to negotiate the data speed with an attached device.

Set the speed to 2 Gb/sec only on ports that support this speed.

EMC recommends that only 2 Gb/s optics be installed in DS-24M2s. If a 1 Gb/s optic is inserted and the port speed is configured for 1 Gb/sec, the optic will operate. However, if the port speed is configured for either 2 Gb/sec or Negotiate, the Port List view will report the port state status as Inactive and the port will not be operational.

To set all ports to the same setting, right-click the Speed column in any row, and select a setting from the drop-down list:

◆ Set All To 1 Gb/sec

◆ Set All To 2 Gb/sec

◆ Set All To Negotiate

When you change a port’s speed and click Activate on the dialog box, a confirmation message states that this setting will temporarily disrupt port data transfers.

Port Binding This setting determines whether port binding is enabled (if the box is checked) or disabled on a port. Click a checkbox to add or remove a checkmark.

Port binding is allowed only for a port that is either a G_Port, F_Port, or E_Port.



◆ If enabled — The only device that can attach to the port is the one specified by the WWN or nickname in the Bound WWN column. (If the Bound WWN column is blank, no device can connect to the port.)

◆ If disabled — Any device can attach to the port, even if a WWN or nickname is specified in the Bound WWN column.

You can also enable or disable binding through right-click menus (described later in this section) or through a Bind WWN dialog box (described under Configuring Port Binding on page 5-22.)

Binding to the Attached DeviceTo bind a port to the device that is logged in to the port, right-click the port’s Port Binding column; then click Bind Port to Attached WWN on the pop-up menu. The Bound WWN column will display that device’s WWN.

Setting All PortsTo set binding configuration for all ports in the switch at the same time, right-click anywhere in the Port Binding column; then click the desired option:

◆ Bind All WWNs — Enables Port Binding for all ports. Each port will be bound to the device with the WWN/Nickname entered in the Bound WWN column for that port.

◆ Unbind All WWNs — Disables Port Binding for all ports, allowing any device in the fabric to attach to any port in the switch.

◆ Bind All Ports to Attached WWN — Binds each port to the device currently logged in to to that port. The Bound WWN column will display that device’s WWN/nickname.

◆ Bind Port To Attached WWN — Binds the port to the device currently logged in to that port. The Bound WWN column will display that device’s WWN/nickname.

◆ Clear All Bound WWNs — Deletes all WWNs/nicknames from the Bound WWN column.

Bound WWN This is a World Wide Name (WWN) or nickname configured through the Fabric Manager application. (A WWN must be in the proper format: xx.xx.xx.xx.xx.xx.xx.xx.)

The device identified in this column will have exclusive attachment to the port if port binding is enabled.


5

5-22


Adding FlexPorts The DS-24M2 ships from the factory with at least eight optics, installed in ports 0 through 7. When adding an additional eight optics optics, install them in ports 8 through 15. Then, when adding the final eight optics, install them in ports 16 through 23.

To enable the optics, you must install the appropriate FlexPort feature key. Once you have obtained the correct feature key from the EMC Powerlink Web site (http://powerlink.emc.com), follow the steps under Configuring Feature Keys on page 5-28.

Configuring Port Binding

To specify a WWN or nickname that can then be bound to a port, right-click the port in the Hardware view; then click Port Binding on the pop-up menu.

This displays the Bind WWN dialog box (Figure 5-10).

Figure 5-10 Bind WWN Dialog Box

Configure the parameters as follows, then click Activate:

◆ Port Binding — Click to add or remove a checkmark. If the box is checked, port binding is enabled for the port. (You can also enable or disable binding through the Configure Ports dialog box.)

If port binding is enabled, only the device whose WWN or nickname is entered in the WWN field can attach to the port. (If the WWN field does not contain a valid WWN or nickname, no device can attachh to the port.) If port binding is disabled (the box is not checked), any device can attach to the port, even if a WWN or nickname is specified in the WWN field.

◆ Attached WWN — This is the device currently logged in to the switch port. If this item is selected and port binding is enabled, this device has exclusive use of the port.

DS-24M2: Bind WWN



If no device is logged in, no WWN appears on the Attached WWN line. If the user then enables port binding, the port will be bound to a WWN of 0, essentially preventing any device from logging in until binding is disabled,or the bound WWN is updated to a new WWN setting.

◆ WWN — This entry allows you to enter a WWN (in the format xx.xx.xx.xx.xx.xx.xx.xx) or nickname of a device that will be bound to the port. If port binding is enabled, this device has exclusive use of the port, even if another device is logged in. (If binding is not enabled, this WWN/nickname will be stored.)

If port binding is enabled and no attached node matches the WWN/nickname in the WWN field, a warning (Figure 5-9 on page 5-18) appears. If you click Continue at that warning, any node that is logged in will be logged out. If the device identified in the WWN field logs in, it will become bound to the port and will be able to communicate.


5

5-24


Configuring the SNMP AgentUse the procedures in this section to:

◆ Configure the SNMP agent that runs on the switch and implements the following MIBs:

• MIB-II• Fabric Element MIB• Switch private MIB (refer to Appendix A)• FibreAlliance MIB

◆ Configure network addresses and community names for up to six SNMP trap recipients.

An SNMP trap recipient is a network management station that receives messages for specific events that occur on the switch.

◆ Define SNMP community names that SNMP managers use for reading variables.

◆ Authorize write permissions for writable MIB variables.

The SNMP configuration is stored in NV-RAM on the switch.

SNMP managers may request, but will not receive, traps and SNMP data through SNMP management stations that are not configured with community names.

To configure traps and assign community names, follow these steps:

1. Click Configure on the Product Manager menu bar and select SNMP Agent on the drop-down menu.

This displays the Configure SNMP dialog box (Figure 5-11).



Figure 5-11 Configure SNMP Dialog Box

2. If the box beside Enable Authorization Traps is checked, traps will be sent to SNMP management stations when unauthorized stations try to access SNMP information from the director.

Click the box to add or remove a checkmark.

3. Click a field in the Community Name column to select the row. Enter the SNMP community name for the trap recipient, up to 32 characters. This also defines community names used by SNMP managers to read MIB variables from or write MIB variables to the switch.

Refer to the note under Configuring the SNMP Agent on page 5-24 for more information about assigning community names.

4. If a Write Authorization checkbox is checked, the trap recipient (SNMP management station) is granted authorization to modify the SNMP variables sysContact, sysName, sysLocation, and fcFPortPhysAdminStatus.

Click the box to add or remove a checkmark.

5. Click in a Trap Recipient field and enter an IP address for a trap recipient (SNMP management station).

6. If you wish to override the default UDP (User Datagram Protocol) trap port number (162), enter any legal UDP port number (1—65535) in the UDP Port Number column.

7. Click Activate to activate the data and close the dialog box.

Configuring the SNMP Agent 5-25

5

5-26





Configuring Management Server ControlThis section describes the procedure to configure a management server (assuming the Management Server feature is installed).

In the current Connectrix release, the Open Systems Management Server feature is available only through RPQ.

The Open System Management Server (OSMS) is a keyed feature that allows host control and inband management of the switch through a management application that resides on an open-systems interconnection (OSI) device. This device, attached to a switch port, communicates with the switch or through Fibre Channel common transport (FC-CT) protocol.

The Open Systems Management Server feature must be installed in order to perform this procedure.

To configure the Open Systems Management Server:

1. Click Configure on the Product Manager menu bar and select Management Server, Open Systems Management Server from the drop-down menus.


Figure 5-12 Configure Open Systems Management Server Window

2. If the box next to Host Control Prohibited is checked, the host management program cannot change configuration and connectivity parameters on the switch. Clicking the checkbox when it contains a checkmark removes the checkmark and allows write authorization.

3. Click Activate to activate changes and close the dialog box.

4. If you are finished configuring the switch, you can back up the configuration data. For more information, refer to Backing Up and Restoring the Configuration on page 7-10.

Configuring Management Server Control 5-27

5

5-28


Configuring Feature KeysA feature key is a string of alphanumeric characters that validates an installed feature for use. Each feature key is encoded with a director’s serial number; therefore, it can be configured only on the director to which it is assigned.

A feature key is necessary to enable the Open Systems Management Server (OSMS). This can be acquired only through an RPQ.

To configure a feature key, follow these steps:

1. If you are adding a FlexPort feature key, first install the optics in the appropriately numbered positions.

2. The next step depends on whether other feature keys are already installed and enabled:

• If no, proceed to step 3.

• If yes, you must set the switch off line:

CAUTION!Setting the switch off line terminates all Fibre Channel connections.




b. Click Set Offline.

3. Click Configure on the Product Manager menu bar and select Features on the drop-down menu.




Figure 5-14 Configure Feature Key Window

4. Click New to add a new feature key.

This displays the New Feature Key dialog box (Figure 5-15).

Figure 5-15 New Feature Key Dialog Box

5. The feature key is a string of alphanumeric characters with dashes. The key is case-sensitive, and must be entered exactly as printed in the documentation you received for the feature.

Enter the feature key and click OK.

If an Invalid feature key message appears, verify that you have entered the key correctly. If you need to verify that you have the correct key, check the serial number of the switch in the Switch Properties window, and compare it to the serial number listed in the documentation provided with your feature key.

To display the Switch Properties window, click on the director, away from any FRUs.

6. After you sucessfully enter a feature key (and press OK), the Enable Feature Key dialog box Figure 5-16 appears.

Configuring Feature Keys 5-29

5

5-30


Figure 5-16 Enable Feature Key Dialog Box

The left side contains a list of features that are active on the director. The right side contains a list of features that come with the new feature key. All of the features that are active are included in the new feature list.

7. Click Activate to activate the new feature key.

All current features are replaced with new features. Therefore, any feature in the current list that is not on the new list will be removed from the switch.

Activating the feature key causes an IPL of the switch, during which the Ethernet connection between the Connectrix service processor and the switch is momentarily interrupted. This will not disrupt Fibre Channel traffic.

8. If the switch is off line, set it on line:


b. On the Set Online State window, click Set Online.


Open Systems Management Server



Configuring the Date and TimeUse the procedures in this section to display and change the date and time set on the switch. You must set the current date and time on the switch so the various logs display the correct time stamps.

1. Click Configure on the Product Manager menu bar and select Date/Time on the drop-down menu.

This displays the Configure Date and Time dialog box (Figure 5-17).

Figure 5-17 Configure Date and Time Dialog Box

If the Periodic Date/Time Synchronization checkbox is checked, the Connectrix service processor periodically synchronizes the switch time to the service processor time, and the time is automatically corrected for daylight savings time..

If the Periodic Date/Time Synchronization checkbox is not checked, you can set the Connectrix service processor date and time manually.

To disable periodic date/time synchronization, click the checkbox to remove the check mark, then click Activate. To reenable periodic date/time synchronization, click the checkbox to display the checkbox, then click Activate.

Click Activate to synchronize the date and time at the next update period. Click Sync Now to synchronize the date and time immediately.

Configuring the Date and Time 5-31

5

5-32


2. Perform one of the following steps:

• To immediately synchronize the switch date and time with the Connectrix service processor, click Sync Now. Make sure that Periodic Date/Time Synchronization is enabled (checked).

If you click Activate, the date and time synchronize at the next update period.

• To synchronize the switch date and time with a specific date and time that you enter:


a. Make sure that Periodic Date/Time Synchronization is disabled (not checked).

b. Click in a Date or Time field that you want to change.

c. Delete characters and enter new ones as required or highlight the existing character by dragging the cursor over the character and typing the new character.

Enter the hour in the range 0 to 23. Enter minutes and seconds in the range 0 to 59.

d. Click Activate to set the date and time on the switch.



Configuring Threshold AlertsA threshold alert notifies users when the transmit (Tx) or receive (Rx) throughput reaches specified values for specific switch ports or port types, (E_Ports or F_Ports).

You are notified of a threshold alert in four ways:

◆ An attention indicator (yellow triangle) that appears on the port in the Hardware view.

◆ An attention indicator (yellow triangle) that appears in the Alert column of the Port List view.

◆ An attention indicator (yellow triangle) that appears by the Threshold Alerts field in the Port Properties window.

◆ Detailed threshold alert data is recorded in the Threshold Alert Log.

Use the Threshold Alerts option on the Configure menu to configure the following:

◆ Name for the alert

◆ Type of threshold for the alert (Rx, Tx, or either)

◆ Active or inactive state of the alert

◆ Threshold criteria:

• Percent traffic capacity utilized. This is the percent of the port’s throughput capacity achieved by the measured throughput. This setting constitutes the threshold value. For example, the value of 50 means that the port’s threshold is reached when throughput is 50 percent of capacity.

• Time interval during which throughput is measured and alert notification can occur.

• The maximum cumulative time that the throughput percentage threshold can be exceeded during the set time interval before an alert is generated.

◆ Ports for which you are configuring threshold alerts

You can configure up to 16 alerts, and any number of alerts can be active at one time.

Configuring Threshold Alerts 5-33

5

5-34


Creating New Alerts Follow these steps to create a new threshold alert:

1. Click Configure on the Product Manager menu bar and select Threshold Alerts on the drop-down menu.

This displays the Configure Threshold Alerts window (Figure 5-18).

Figure 5-18 Configure Threshold Alerts Window

If alerts are configured, they appear in table format (as shown in Figure 5-23 on page 5-39), showing the name of the alert, type of alert (Rx, Tx, or Rx or Tx), and alert state (Active or Inactive).

2. Click New.

This displays the New Threshold Alert window (Figure 5-19).

24M2:



Figure 5-19 New Threshold Alerts Window — First Screen

3. Enter a name, 1 to 64 characters. All characters in the ISO Latin-1 character set, excluding control characters, are allowed.

4. Select one of the following from the drop-down Threshold Type list:

• Rx Throughput. An alert will occur if the threshold set for receive throughput is reached.

• Tx Throughput. An alert will occur if the threshold set for transmit throughput is reached.

• Rx or Tx Throughput. An alert will occur if the threshold set for either receive or transmit throughput is reached.

5. Click Next.

A new window (Figure 5-20) appears, with additional parameters. The name configured for the alert appears at the top of the window.

(Click Previous if you need to return to the previous window.)


5

5-36


Figure 5-20 New Threshold Alerts Window — Second Screen

6. Enter a percentage for % utilization, 1 through 100. If throughput reaches this percentage of port capacity, a threshold alert occurs.

7. Enter the amount of cumulative minutes in which the % utilization should exist during the notification interval before an alert is generated. You can also select At any time if you want an alert to occur whenever the set % utilization is reached. The valid range is 1 through the interval set in step 8.

8. Enter the interval (in minutes) during which throughput is measured. The valid range is 5 to 70,560 minutes. When throughput reaches the threshold value and remains constant for the specified time, an alert is generated.

9. Click Next.

A new window appears for selecting ports for the alerts.



Figure 5-21 New Threshold Alerts Window — Third Screen

10. Select either Port Type or Port List.

• If you select Port Type, selecting E_Ports, F_Ports, or FL_Ports will cause this alert to generate for all ports configured as E_Ports, F_Ports, or FL_Ports respectively.

• If you select Port List, you can select individual ports by clicking the checkbox by each port number or set all ports. Selecting Set All Ports places a checkmark by each port number. Selecting Clear All Ports clears the checkmarks by each port number.

11. Click Next.

A final window appears to provide a summary of your alert configuration. To make any changes, use the Previous/Next buttons to move backwards and forwards through the configuration windows.


5

5-38


Figure 5-22 New Threshold Alerts Window — Summary Screen

12. Click Finish.

The Configure Threshold Alerts window (Figure 5-23) appears, listing the name, type, and state of the alert that you just configured.

13. At this point, the alert is not active. To activate the alert, select the alert information that displays in the Configure Threshold Alerts table and select Activate.



Figure 5-23 Configure Threshold Alerts Window — Activate Alert

Modifying Alerts Use the following steps to modify an existing threshold alert configuration.


This displays the Configure Threshold Alerts window (Figure 5-18 on page 5-34).

2. Select the alert that you want to modify by clicking the alert information in the table.

3. If the alert is active, select Deactivate; then select the alert information in the table again.

4. Select Modify.

If the alert is active, an error message displays prompting you deactivate the alert.

5. An initial Modify Threshold window appears, where you can change the threshold type. Select a threshold type from the drop-down list.


5

5-40


6. Select Next when you are done. A Modify Threshold window appears, where you can change the % utilization, cumulative minutes for the threshold to occur before notification, and the time interval for measuring throughput and for alert notification.

7. Make appropriate changes, then continue through the Modify Threshold windows, making changes as necessary, until the summary screen appears displaying the alert configuration.

8. Perform either of the following steps:

• To change any parameters, select Previous/Next to display the desired Modify Threshold window.

• Select Finish when you are done.

Activating or Deactivating Alerts

Follow these steps to activate or deactivate existing threshold alerts. In the active state, notifications are generated for the alert. In the inactive state, notifications do not occur.


This displays the Configure Threshold Alerts window (Figure 5-18 on page 5-34). The port’s current state, deactive or active, is listed under the State column.

2. To change the state, select the alert next to the alert information in the table.

3. If the alert is active, select Deactivate. If the alert is inactive, select Activate.

Deleting Alerts Follow these steps to delete existing threshold alerts:


This displays the Configure Threshold Alerts window (Figure 5-18 on page 5-34).

2. Select the alert that you want to delete by selecting the alert information in the table.

3. Select Delete.

4. A message displays asking you to confirm the deletion. Select Yes.



Exporting a Configuration ReportUse this option to save an ASCII file of all configuration data currently saved in switch NV_RAM to your hard drive or a diskette. Use any desktop publishing application to open the ASCII file for viewing or printing.

This file cannot be used to set configuration parameters through the Product Manager.

Report Data Data in the file includes:

◆ Product identification — Data input into the Configure Identification dialog box.

◆ Operating parameters — Data input into the Operating Parameters dialog box.

◆ Port parameters — Data input into the Configure Ports dialog box.

◆ SNMP parameters — Data input into the Configure SNMP dialog box.

◆ Active zoning configuration — This specifies the active zone and zone members, if set, and whether the default zone is enabled or disabled.

Export Procedure To export a configuration report:

1. Click Configure on the Product Manager menu bar and select Export Configuration Report on the drop-down menu.

This displays the Export Configuration Report dialog box (Figure 5-24).

Exporting a Configuration Report 5-41

5

5-42


Figure 5-24 Export Configuration Report Window

2. Select the folder where you want to save the file.

3. Type in a file name and extension in the File name field.

4. Click Save. This saves the file to the specified folder as an ASCII text file.

Drive ListGo Up One Level Home

Create New Folder

ListDetails



Enabling the Embedded Web ServerSelect this option from the Configure menu to enable or disable remote access to the Embedded Web Server interface on the switch. (Refer to Appendix C for more information on using the Web Server.)

EMC recommends using the Connectrix Manager to manage the switch. However, the Embedded Web Server can be used if the Connectrix Manager is not available.

If the Enable Web Server box is checked, access to the interface is enabled. Clicking the box adds/removes a checkmark.

DS-24M2s are normally installed inside the Connectrix cabinet and connected to the private Ethernet LAN inside the cabinet. A DS-24M2 can be installed outside the Connectrix cabinet and still be managed by Connectrix Manager; however, this requires that the switch be configured with a public IP address to which the Connectrix service processor is also connected.

If the Embedded Web Server (rather than Connectrix Manager) is used to manage the switch, the switch must also be configured with a public IP address.

If you configure a DS-24M2 to reside on a public LAN and you do not plan to use theEmbedded Web Server interface, you should disable it in Connectrix Manager. If you do plan to use the Embedded Web Server, change the default passwords in order to prevent others from logging in to the switch via the Embedded Web Server. (Refer to Configuring User Names and Passwords on page C-25 for information on changing the Embedded Web Server passwords.)

Enabling the Embedded Web Server 5-43

5

5-44


Enabling TelnetSelect this option from the Configure menu to enable or disable Telnet access to the switch. Telnet access allows users at remote workstations to use the command line interface or perform other tasks on the switch. (Refer to Appendix D for more information about the command line interface.)

If the Enable Telnet box is checked, Telnet access is enabled. Clicking the box adds/removes a checkmark.

DS-24M2s are normally installed inside the Connectrix cabinet and connected to the private Ethernet LAN inside the cabinet. A DS-24M2 can be installed outside the Connectrix cabinet and still be managed by Connectrix Manager; however, this requires that the switch be configured with a public IP address to which the Connectrix service processor is also connected.

If you configure a DS-24M2 to reside on a public LAN and you do not plan to use the command line interface (CLI), you should disable it in Connectrix Manager. If you do plan to use the CLI, change the default password in order to prevent others from logging in to the switch via the CLI. (Refer to login on page D-11 for information on changing the CLI passwords.)


6Invisible Body Tag

This chapter describes the DS-24M2 logs.

◆ Using Logs ..........................................................................................6-2◆ Audit Log ............................................................................................6-4◆ Event Log ............................................................................................6-6◆ Hardware Log.....................................................................................6-8◆ Link Incident Log...............................................................................6-9◆ Threshold Alert Log......................................................................... 6-11

Using Logs

Using Logs 6-1

6

6-2

Using Logs

Using LogsThe Audit, Event, Hardware, Link Incident, and Threshold Alert logs store up to 1000 entries each. The most recent entry appears at the top of the log. After 1000 entries are stored, new entries overwrite the oldest entries.

Access the logs from the Product Manager Logs menu.

Button Function Button function is the same for all logs:

◆ Clear — Clears all entries in the log for all users. A warning requests you to confirm that you want to clear all entries in the log.

◆ Refresh — Reads the current data and refreshes the screen with the new display.

◆ Close — Closes the log and displays the Product Manager window.

◆ Export — Displays a Save window (Figure 6-1).

Figure 6-1 Save Window

Click Home to return to the files in your home directory. The folders listed in the display area of the Save window will then be those that are stored in your home directory. If you choose, you can create a folder for your home directory and save the file there.

Drive ListGo Up One Level Home

Create New Folder

ListDetails


6Using Logs

To save a log file in ASCII format to a location on your system’s hard drive or to a diskette, use the following steps. You can open this file in any desktop publisher for viewing or printing.

a. Click Export on the log window.

b. In the Save dialog box, select the folder where you want to save the file.

c. Type in a file name and extension into the File name field.

d. Click Save. The file is saved to the specified folder as an ASCII text file.

Expanding Columns You can expand columns in logs as follows:

1. Move over the line separating two column headings until a double arrow appears.

2. Hold down the left mouse button and widen the column as necessary.

Sorting Entries Sort log entries in columns by clicking a column heading. A Down arrow in the header indicates sorting in descending order. An Up arrow indicates sorting in ascending order. Click once to sort. Click again to reverse the sort.

Using Logs 6-3

6

6-4

Using Logs

Audit LogThe Audit Log displays a history of all configuration changes applied to the switch from any source such as Product Manager, SNMP management stations, Web Server interface, host, or another switch.

Figure 6-2 Audit Log

The log provides this information:

◆ Date/Time — The date and time of the change on the switch.

Some actions, such as backing up configuration data and enabling automatic date/time synchronization, are performed only by the Connectrix service processor without switch interaction. These actions are indicated by the string Connectrix Manager following the audit log’s stamp of the Connectrix service processor’s date and time. If the string Connectrix Manager does not appear, the time stamp is from the switch.

◆ Action — User action that caused the configuration change, such as offline status, port name change, or change of address.

DS-24M2 - Test 35: Audit Log

140.150.60.70

140.150.60.70

165.150.122.65

165.150.122.65

144.96.120.120

140.150.60.70

140.150.60.70

144.96.120.120

144.96.120.120

144.96.120.120

144.96.120.120

144.96.120.120

144.96.120.120

144.96.120.120

140.150.60.70


6Using Logs

◆ Source — Identifies the user making the change through the switch Product Manager and IP or DNS host name address of the remote user ’s workstation:

• Maintenance Port: Change was made by a user connected to the maintenance port.

• Connectrix Manager: Change was made by an Product Manager user.

• SNMP: Change was made by a remote SNMP management station.

• Fabric: Change was initiated by another switch/director in the fabric that is not managed by this Connectrix service processor.

• Web Server: Change was made by a user through the Embedded Web Server interface.

• Fibre Channel Host: Change was made in band by a Fibre Channel host through the open systems management server.

• Telnet: Change was made through a Telnet connection.

◆ Identifier - Identifies the user making the change according to the source:

• Maintenance Port: No entry appears.

• Connectrix Manager: Includes <user>@<address>, where <user> is the Product Manager user name, and <address> is the network address of the workstation (remote user workstation or Connectrix service processor).

• SNMP: Contains the network address of the SNMP management station.

• Fabric: No entry appears.

• Web Server: Includes <user>@<address>, where <user> is the Web Server user name and <address> is the network address of the Web user.

• Fibre Channel Host: No entry appears.

• Telnet: Change was made through a Telnet connection.

Audit Log 6-5

6

6-6

Using Logs

Event LogThe Event Log provides a record of significant events that have occurred on the switch, such as hardware failures, degraded operation, and port problems.

Figure 6-3 Event Log

All detected firmware faults and hardware failures are sent to the Connectrix service processor for recording in the event log. The log provides a maximum of 1000 log entries before it wraps and overwrites the oldest entries.

Each log entry includes the following:

◆ Date/Time — The date and time of the event on the switch.

◆ Event — A unique code that identifies the event. The same code that appears in the Product Manager Event Log also appears in the operator panel Event Log.

DS-32M2 - Test 35: Event Log


6Using Logs

Event codes include:

◆ Description — A short description of the event.

◆ Severity — A class of severity that identfies the importance of the event:

◆ FRU-Position — (if applicable) An acronym representing the FRU type followed by a number representing the FRU chassis position. (Moving the cursor across the FRUs in the Hardware View displays the position numbers.)

◆ Event Data — Up to 32 bytes of supplementary information for the event in hexadecimal format.

000 – 199 System events

200 – 299 Power supply events

300 – 399 Fan module events

400 – 499 CTP events

500 – 599 Port events

0 = Informational

2 = Minor

3 = Major

4 = Severe (not operational)

CTP = Control processor

FAN = Single fan module

PWR = Power supply module

Event Log 6-7

6

6-8

Using Logs

Hardware LogThe Hardware log displays information on FRUs that have been inserted and/or removed.

Figure 6-4 Hardware Log

Each log entry includes the following:

◆ Date/Time — Date and time of the insertion/removal of the FRU.

◆ FRU — Name of the inserted/removed FRU:

◆ Position — Physical position relative to identical components in the switch.

◆ Action — Inserted or Removed.

◆ Part Number — Part number of the component.

◆ Serial Number — Serial number of the component.

CTP = Control processor

PWR = Power supply module


6Using Logs

Link Incident LogThe Link Incident log displays the 1000 most recent link incidents with the date each incident occurred, the time it occurred, and the port on which the incident took place. The information in this log is useful to maintenance personnel for isolating port problems (particularly E_Port segmentation problems) and repair verification.

Figure 6-5 Link Incident Log

Link Incident Log 6-9

6

6-10

Using Logs

Each log entry contains:

◆ Date/Time — The date and time of the incident.

◆ Port — The number of the port on which the incident occurred.

◆ Link Incident — A short description of the incident. The following events may cause a link incident to be written to the log.

• Implicit incident — The attached node detects a condition that may cause problems on the link.

• Bit-error threshold exceeded — The number of code violation errors has exceeded threshold of 12 errors in a 5-minute window per port..

• Loss-of-Signal or Loss-of-Synchronization — This occurs if a cable is unplugged from an attached node.

Loss-of-synchronization condition has persisted for longer than the resource allocation time out value (R_A_TOV).

• Not-operational (NOS) primitive sequence received — A NOS was recognized.

• Primitive sequence timeout:

– Link reset protocol timeout occurred.– Timeout occurred for an appropriate response while in

NOS receive state and after NOS is no longer recognized.• Invalid primitive sequence received for the current link

state — Either a link reset or a link reset response primitive sequence was recognized while waiting for the offline sequence.


6Using Logs

Threshold Alert LogThis log provides details of threshold alert notifications. Besides the date and time that the alert occurred, the log also displays details about the alert as configured through the Configure Threshold Alert(s) option under the Configure menu. (Refer to Configuring Threshold Alerts on page 5-33.)

Figure 6-6 Threshold Alert Log

Each log entry contains:

◆ Date/Time — The date and time of the alert.

◆ Name — Name for the alert as configured through the Configure Threshold Alerts window.

◆ Port — Port number where the alert occurred.

◆ Type — The type of alert: transmit (Tx) or receive (Rx).

Threshold Alert Log 6-11

6

6-12

Using Logs

◆ Utilization % — Percent usage of traffic capacity. This is the percent of the port’s throughput capacity achieved by the measured throughput. This setting constitutes the threshold value and is configured through the Configure Threshold Alerts window. For example, a value of 25 means that threshold occurs when throughput reaches 25 percent of the port’s capacity.

◆ Alert Time — The maximum cumulative time that the throughput threshold percentage must exist before an alert is generated. This is set through the Configure Threshold Alerts window.

◆ Interval — The time interval during which the throughput is measured and an alert can generate. This is set through the Configure Threshold Alerts window.


7Invisible Body Tag

Invisible Body Tag

This chapter describes the options that appear on the Product Manager Maintenance menu.

◆ Running Port Diagnostics .................................................................7-2◆ Collecting Maintenance Data ...........................................................7-3◆ Executing an IPL ................................................................................7-4◆ Setting the Online State .....................................................................7-6◆ Managing Firmware Versions ..........................................................7-7◆ Enabling E-Mail Notification............................................................7-8◆ Enabling Call-Home Notification ....................................................7-9◆ Backing Up and Restoring the Configuration .............................7-10◆ Resetting the Configuration ...........................................................7-16

Using MaintenanceFeatures

Using Maintenance Features 7-1

7

7-2

Using Maintenance Features

Running Port DiagnosticsThe Port Diagnostics option is for use by service personnel to run internal and external loopback tests on a port.


7Using Maintenance Features

Collecting Maintenance DataThe Collect Maintenance Data option is used by service personnel to collect maintenance data that can help diagnose system problems.

Store this data on the Connectrix service processor hard disk or send it to another network PC using file transfer protocol (FTP). You can also save the maintenance data to a Zip disk and mail it to the technical support personnel.

Collecting Maintenance Data 7-3

7

7-4


Executing an IPL

CAUTION!The Ethernet connection between the Connectrix service processor and switch is interrupted momentarily during an IPL.

An IPL is not intended for ordinary or casual use and should be performed only if the active CTP is suspected to be faulty. Do not use this option unless directed by your support representative or if you need to reset a failed CTP.

If it is necessary to execute an IPL on the switch, follow these steps:

1. Click Maintenance on the Product Manager menu bar and select IPL on the drop-down menu.

2. A window appears, asking you to confirm the IPL. Click Yes.

Performing an IPL causes the Ethernet connection between the switch and Connectrix service processor to drop momentarily and the following to occur in the Product Manager window:

◆ As the network connection drops, the DS-24M2 Status table on the Hardware view turns yellow.

◆ The Status field in the table displays No Link and the State field displays the reason for no link.

◆ A grey square appears in the alert panel. Refer to Table 4-1 on page 4-5 for an explanation of this alert symbol.

◆ The FRUs in the illustration in the Hardware view do not appear. They will reappear as the connection is reestablished.

An IPL initiates the following functions in the switch:

◆ Restarts the operational firmware on the CTP subsystem, executes abbreviated power on system tests (POSTs) and then, if no POST errors are encountered, resumes the active role that it had before the IPL.

◆ Resets the Ethernet interface on the CTP subsystem, causing the connection to the Connectrix service processor to drop momentarily. The status icon for the switch in the Connectrix Manager Products view changes to a gray square until the connection is reestablished.



◆ Stops normal switching functions for ports. (Functions resume after the IPL.)

After the IPL:

◆ All Fabric services databases containing information about current Fabric logins, name server registrations, and other data remain intact, making the operation transparent to attached devices.

◆ The switch returns to the online state, even if it was offline before the operation.

◆ All ports configured as blocked remain blocked.

◆ Modifications made to an active zone set configuration that have not been enabled are automatically enabled.

Executing an IPL 7-5

7

7-6


Setting the Online StateUse the procedure in this section to display the current switch operating state (on line or off line) and change the state as required. Refer to Switch Operational States on page 1-15 for more information on the operating states.

CAUTION!Before setting the switch off line, warn administrators and users currently operating devices that are attached to the switch that it is going off line and that there will be a disruption of communications. Make sure the administrators of all attached devices quiesce Fibre Channel traffic through the switch.

Follow these steps to set the switch on line or off line:

1. Display the Set Online State window (Figure 7-1) from the Hardware view by one of these methods:

• Click Maintenance on the Product Manager menu bar and select Set Online State on the drop-down menu.

• Right-click on the switch and click Set Switch Online State on the pop-up menu.


2. Click Set Offline/Online.

3. When a warning box requests you to confirm, click OK.

As the switch goes off line, OFFLINE appears in the State field of the DS-24M2 Status table in the Hardware view. LED indicators on all ports with attached devices stay green, but the switch is sending offline sequences (OLS) to these devices.



Managing Firmware VersionsFirmware refers to the internal operating code for the switch. You can maintain up to eight firmware versions on the Connectrix service processor for downloading to an switch.

This option is for use by service personnel.

Managing Firmware Versions 7-7

7

7-8


Enabling E-Mail NotificationE-mail addresses and the SMTP (Simple Mail Transfer Protocol) Server address for e-mail notification of switch events must be configured through the Connectrix Manager application. Refer to the Connectrix Manager User Guide for instructions on configuring e-mail.

E-mail recipients are configured in the Connectrix Manager through the Configure E-Mail dialog box. A valid SMTP address is configured in this dialog box.

Use the Enable E-Mail Notification function on the Product Manager to enable e-mail notification for events that occur on a selected switch. The default state is disabled.

To enable or disable e-mail notification, click Maintenance on the Product Manager menu bar and select Enable E-Mail Notification on the drop-down menu. When the box to the left of Enable E-Mail Notification is checked, notification is enabled.

To change the enabled/disabled state of e-mail notification, click the box to remove/add the checkmark.



Enabling Call-Home NotificationThe call-home feature enables the Connectrix service processor to automatically dial out to the EMC Support Center to report system problems. The support center server accepts calls from the Connectrix service processor, logs reported events, and notifies one or more support center representatives.

CAUTION!Do not change the call-home settings; these functions are for EMC Service Personnel. Changing these settings incorrectly could prevent the Connectrix Manager from properly calling home to the EMC Support Center in the event of an incident.

Enabling Call-Home Notification 7-9

7

7-10


Backing Up and Restoring the ConfigurationUse the Backup and Restore Configuration option to back up the NV-RAM configuration. This option backs up the configuration data to a file on the Connectrix service processor hard drive.

The restore function writes the data back to NV-RAM on the switch.

Only a single copy of the configuration is kept on the service processor; performing a restore overwrites the existing configuration.

In addition to the Backup and Restore Configuration option, the Iomega QuikSync application backs up configuration and other critical data from the Connectrix service processor automatically. As long as a Zip disk remains in the Zip drive of the Connectrix service processor and the user remains logged in to the Windows NT operating system, data is backed up to the Zip disk whenever the directory contents change or you reboot the Connectrix service processor.

For more information on the QuikSync backup, refer to Automatic Backup to Zip Disk on page 7-12.

The purpose of the backup is primarily for single-CTP systems, where a backup is needed in order to restore to a replacement CTP card. However, you can also use this feature for a special-purpose configuration or for temporary testing of a configuration.

You cannot modify the location or file name of the saved configuration. Also, you can restore the configuration only to a switch with the same IP address.



Backup Follow these steps to perform a backup:

1. Click Maintenance on the Product Manager menu bar and select Backup & Restore Configuration on the drop-down menu.


Figure 7-2 Backup and Restore Configuration Window

Following is a list of configurations that are backed up to the Connectrix service processor:

• Identification data (switch name, description, and location).

• Port configuration data (port names, blocked states, and extended distance settings).

• Operating parameters for the fabric (described under Configuring Operating Parameters on page 5-4).

• SNMP configuration (trap recipients, community names, and write authorizations).

• Zoning configuration (active zone set and default zone state).

2. To back up data, click Backup.

3. When a message confirms that the backup is complete, click OK.

If the backup fails, a message informs you.

Restore 1. Set the switch off line before performing the restore function. (Refer to Setting the Online State on page 7-6.)

2. Click Restore on the Backup and Restore Configuration window to restore the backed up configuration to the NV-RAM on the switch.

A confirmation window indicates that the restore will overwrite any existing configuration already on the switch. The window also displays the date of the restored backup.

Backing Up and Restoring the Configuration 7-11

7

7-12


Click OK. The restore operation initiates an IPL.

3. When the restore finishes, set the switch back on line.

Automatic Backup to Zip Disk

As long as a Zip drive (with a disk in it) is connected to the Connectrix service processor and the user remains logged in to the Windows NT operating system, data is backed up, critical information from both the Product Manager and Connectrix Manager applications automatically backs up to the Zip disk when the data directory contents change or when you reboot the Connectrix service processor.

Connectrix Manager maintains a mirror image of its configuration data on the D:\ drive of the service processor. The automatic backup to the Zip disk occurs only when you log in to the service processor or when the service processor is rebooted. If you want the automatic backup to occur all of the time (which is recommended), the best way to accomplish this is to not log out of the service processor, but rather to lock the workstation by pressing CTRL-ALT-DEL and selecting Lock Workstation.

The application used for this function is Iomega QuikSync, a separate application installed on the Connectrix service processor. QuikSync is configured to automatically mirror the contents of the EfcData directory to the Zip drive when the contents are changed or when you reboot the Connectrix service processor. This directory contains all Connectrix Manager and Product Manager data, so it can be copied back to a newly restored Connectrix service processor to fully recover the preferred operating environment.

The mirroring operation will only occur while a user is logged in to Windows NT on the Connectrix service processor PC (independent of the Connectrix Manager login).

The data contained in the EfcData directory and mirrored to the Zip disk includes the following:

◆ All Connectrix Manager configuration including:

• Product definitions

• User names, encrypted passwords, and user rights.

• Nicknames

• Session options

• Connectrix Manager SNMP configurations

• E-mail configuration



◆ All log files (both Connectrix Manager log files and individual Product Manager log files).

◆ Zoning library (all zone sets and zone definitions).

◆ Firmware library.

◆ Call-home configuration (including phone numbers and dialing options).

◆ Configuration data saved to the EfcData directory through the Backup & Restore Configuration option on the Product Manager Maintenance menu.

The QuikSync application will not backup certain Windows NT configurations that need to be reconfigured on a newly restored Connectrix service processor, including the following:

◆ Windows NT user names and passwords.

◆ TCP/IP network configuration (such as IP address, gateway address, and DNS names).

The QuikSync application will be included on the Connectrix management Applications CD. It is automatically installed on the Connectrix service processor during the Connectrix service processor install process. A blank Zip disk is required for each Connectrix service processor and is included with the Connectrix service processor deliverables.

Restoring Data fromthe Zip Disk

To restore data to the Connectrix service processor, copy the EfcData directory from the Zip disk to the root directory on the C drive (C:\).


7

7-14


Using QuikSync QuikSync is functioning to back up data when the QuikSync icon appears in the system tray in the right corner of the Windows taskbar (Figure 7-3). This icon spins when data is writing to the Zip disk.

Figure 7-3 QuikSync Icon in Windows System Tray

If an icon does not display, you must enable the application using the procedure outlined in Enabling QuikSync on page 7-14.

Enabling QuikSync 1. From the Windows taskbar, click Start, Programs, Iomega QuikSync, QuikSync.

This displays the Iomega QuikSync dialog box (Figure 7-4).

Figure 7-4 Iomega QuikSync Dialog Box

2. To enable QuikSync, select On and click OK.



QuikSync Settings Do not change the default settings for automatic backup of the EfcData directory. If you feel that QuikSync is not functioning properly, check the settings using the following steps:

1. Open the QuikSync dialog box using one of these steps:

• From the Windows taskbar, click Start, Programs, Iomega QuikSync, QuikSync.

• Double-click the QuikSync icon in the Windows status area, located on the right side of the taskbar.

• Right-click the QuikSync icon and click Settings on the pop-up menu.

2. Verify that the dialog box is configured exactly as it appears in Figure 7-4.

The d:\EfcData\ directory is a mirror of c:\EfcData\. Do not change this location in the Source field.

3. Click the Advanced tab to display the dialog box in Figure 7-5.

Figure 7-5 Iomega QuikSync Dialog Box (Advanced Tab)

4. Verify that the dialog box is configured exactly as it appears in Figure 7-5.

5. Click OK.


7

7-16


Resetting the Configuration

You must have maintenance authorization rights to access this feature.

This feature is used to reset all configuration data for the switch to factory default values.

This operation will not reset the password of the Embedded Web Server.

If you have enabled features that add additional port function since the director was shipped from the factory, these features will be disabled (factory default) when the configuration is reset. Only those ports that were enabled at the factory will function. You must enable the additional port function features again. (Refer to Configuring Feature Keys on page 5-28.)

Note on IP Address This procedure resets the IP address the factory default value. If you have changed the value, you might not recover the Ethernet connection between the switch and Connectrix service processor. In this case you must re-enter LAN addressing (such as IP and gateway addresses) through a terminal attached to the maintenance port.

Before using the Reset Configuration option, record the switch’s current IP address, which appears below the switch’s icon in the Connectrix Manager Products view (with the display option set to Network Address). You can also find the current IP address through the Embedded Web Server interface.

After resetting the configuration, reset LAN addressing to the desired values through the maintenance port or the Embedded Web Server interface.

Procedure 1. Click Maintenance on the Product Manager menu bar and select Reset Configuration on the drop-down menu.

CAUTION!This operation will reset all switch configuration data and non-volatile settings to factory default values. All optional features will also be disabled. The switch must be off line to continue.



2. Set the switch off line. For instructions, refer to Setting the Online State on page 7-6.

3. To continue the reset operation, click Reset on the Reset Configuration dialog box. If you want to cancel the operation, click Cancel.

Since the IP address is reset, you may not recover the Ethernet connection to the switch if you have changed the switch‘s IP addressing from the default value. In this case you must re-enter the LAN parameters using the operator panel if you want to continue using the Product Manager.

Table 7-1 lists the default configuration settings.

Table 7-1 Data Default Values

Configuration Description Default

Identification Switch Name NULL string

Switch Description “Fibre Channel Switch”

Switch Contact “End User Contact (please configure)”

Switch Location “End User Contact (please configure)”

Ports Port Names NULL strings

Port Blocked States Unblocked

LIN Alerts Disabled

Switch Addressing IP Address 10, mac[3], mac[4], mac[5] converted to word32. MAC addresses are set in hexidecimal; IP addresses in decimal. A MAC address of 08 00 88 20 00 57 wil be reset to an IP address of 10.32.0.87.

Subnet Mask 255.0.0.0

Gateway Address 0.0.0.0

MAC Address PROM value

Resetting the Configuration 7-17

7

7-18


Operating Parameters

Preferred Domain ID 1

R_A_TOV 10 seconds (100 tenths)

E_D_TOV 2 seconds (20 tenths)

Switch Priority Default

Rerouting Delay Disabled

SNMP SNMP Communities “public” — 5 NULL strings

SNMP Write Authorizations

Read only per community

Trap Recipient IP Addressees

0 for each

UDP Port 162

SNMP Authorization Trap State

5

Management Server Active Equal Saved State

Disabled

Remote Offline Control State

Disabled

Zoning Number of Zone Members

0

Number of Zones 0

Number of Zone Sets 0

Zone Names None

Zone Sets Names None

Zone Members None

Default Zone State Enabled

Active Zone Set State Disabled

Active Zone Set Name NULL string

Table 7-1 Data Default Values (continued)

Configuration Description Default


AInvisible Body Tag

This appendix describes Connectrix support for the Simple Network Management Protocol (SNMP).

◆ Introduction .......................................................................................A-2◆ MIB-II Support ..................................................................................A-7◆ Fabric Element MIB Support .........................................................A-29◆ Fibre Alliance MIB (fcmgmt.mib) .................................................A-49◆ Connectrix Private Enterprise MIB (fceos.mib) ..........................A-86

Using SNMP to Managethe Switch

Using SNMP to Manage the Switch A-1

A

A-2

Using SNMP to Manage the Switch

IntroductionSNMP (Simple Network Management Protocol) is a mechanism for managing a network through agents on the managed devices throughout the network, using commands from a management station, as well as traps (status change notifications) sent to the management station by the managed devices.

Access to the switch-resident SNMP agent is through the switch Product Manager.

SNMP is a TCP/IP (Transmission Control Protocol/Internet Protocol) that uses UDP (User Datagram Protocol) or other protocols such as UDP/IP to exchange messages between SNMP agents in managed devices and the management station residing on the same network. Since SNMP does not rely on the underlying communication protocols, it can be made available over other protocols.

SNMP is based on the Structure of Management Information (SMI) standard. SMI defines the syntax rules for identifying, organizing, and defining variables (also called objects) in a Management Information Base (MIB). A MIB is a hierarchical tree of groups and variables. Operators at a network management station enter a command that contains supported variables from the MIB.

Supported MIBs Supported MIBs include:

◆ MIB-II (Internet MIB) as described in RFC 1213 — Supported by all switches and directors. Refer to MIB-II Support on page A-7.

◆ FibreAlliance (FCMGMT) MIB, version 3.1 — Supported by the Connectrix service processor, as well as all switches and directors. You can download this MIB from the Connectrix service processor.

◆ Fibre Channel Fabric Element (FCFE), version 1.10: supported by all switches and directors. Refer to Fabric Element MIB Support on page A-29.

◆ Connectrix Private Enterprise MIB. Refer to Connectrix Private Enterprise MIB (fceos.mib) on page A-86.

All groups and variables in the supported MIBs are read-only by SNMP management stations unless noted otherwise.


AUsing SNMP to Manage the Switch

You can download all of these MIBs from the Connectrix Manager’s web page. The URL for the web page depends on the Connectrix service processor’s host name on your network.

SNMP Tree Structure Each group is a branch and each variable is a leaf within the MIB tree. The tree begins with the root. Figure A-1 shows the MIB tree hierarchy down to the levels supported in Connectrix switches and directors.

Figure A-1 MIB Tree

root

iso (1)

org (3)

dod (6)

mgmt (2) experimental (3) enterprises (4)

internet (1)

FibreAllianceMIB (2)

Fabric ElementMIB (42)

Connectrix MIB(fceos.mib) (289)

MIB-II (1)

Introduction A-3

A

A-4


SNMP Commands An administrator at a management station requests information from an agent by sending a variation of a single command:

◆ get — Retrieves the value of variables at the agent.

◆ set — Sets the value of variables at the agent.

Each group and variable in a MIB is assigned a numerical address. You can enter commands with variables specified as a name or a number. For example:

get {root, iso, org, dod, internet, mgmt, mib-2, system}

or

get {root, 1, 3, 6, 1, 2, 1, 1}

Traps Traps are unsolicited status reports, or status change indicators a managed object sends to a network manager. The destination address for traps is a configuration item for each managed agent.

The Connectrix SNMP implemenation supports standard generic traps and enterprise-specific traps.

Unsolicited SNMP trap messages are transmitted to authorized management workstations:

◆ When SNMP notifications are configured in the switch Product Manager, unsolicited SNMP trap messages can be transmitted to up to six authorized management workstations.

◆ When SNMP notifications are configured in the Connectrix Manager, unsolicited trap messages can be transmitted to up to 12 authorized management workstations.

Unsolicited SNMP trap messages signal operational state changes and failure conditions. Generic SNMP traps include:

◆ coldStart — Reports that the SNMP agent is reinitializing due to a power-on reset.

◆ warmStart — Reports that the agent is reinitializing due to an Initial Machine Load (IML) or Initial Program Load (IPL).

◆ authorizationFailure — Reports access by an unauthorized SNMP manager.



Protocol Definition The SNMP agent supports the SNMPv1 protocol and data formats as defined in RFCs 1157 and 1155 respectively. The SNMPv2C protocol is not supported.

Configuring an SNMP Agent

Use the Identification and SNMP Agent options on the Configure menu to configure the following parameters:

◆ Identification:

• sysContact (contact person)

• sysName (switch’s name)

• sysLocation (location)

• fcFPortPhysAdminStatus (administrative status of an F_Port)

◆ SNMP Agent:

• SNMPv1 communities (up to six)

• Trap recipients (one per community)

• Write authorization for sysContact, sysName, sysLocation, fcFPortPhysAdminStatus.

• Enable authorization traps. This enables traps to be sent when unauthorized stations try to access switch SNMP information.

• Override default user datagram (UDP) port numbers for trap recipients.

The first three parameters can also be configured using the SNMPv1 SET command with an appropriate community.

V7.01 MIB Support The MIB files are provided in standard ASN.1 syntax and can be installed into the MIB database of any SNMPv2-compliant Network Management Station. The files are available for download from the HTTP server of the Connectrix service processor.

FibreAlliance MIB V3.1 FibreAlliance MIB V3.1 (fcmgmt.mib) has not changed with the 7.01 release.

This MIB is implemented by the SNMP agent that runs on the service processor PC and in the ED-xxM and DS-xxM products. Use the Configure option in the Connectrix Manager application to configure access to this MIB from authorized SNMP Network Management Stations.

Introduction A-5

A

A-6


SNMP Framework MIB SNMP Framework MIB (snmp-framework.mib) is needed to successfully compile and install the FibreAlliance MIB on the Network Management Station.

No changes were made to this MIB with the 7.01 release.

Fibre Channel FabricElement MIB and

TCP/IP MIB-II

Fibre Channel Fabric Element MIB V1.10 April 24 2000 (fcfe.mib) and standard TCP/IP MIB-II (rfc1213.mib) are implemented by the SNMP agent that runs on the switch. Use the Configure option in the corresponding Connectrix Product Manager to configure access to these MIBs from authorized SNMP Network Management Stations. Configuration must be done separately for each individual switch requiring SNMP access.


ED-1032 EnterpriseMIB

ED-1032 Enterprise-specific MIB V1.7 (ed-1032.mib) is implemented by the SNMP agent that runs on the ED-1032 Fibre Channel Director.


Connectrix EnterpriseMIB

Connectrix Enterprise-specific MIB V2.0 (fceos.mib) is implemented by the SNMP agent that runs on Connectrix M-series Fibre Channel switch products.




MIB-II Support

Figure A-2 SNMP MIB-II Support

The switch agent supports eight groups specified in MIB-II:

◆ System Group — Provides general information about the managed system:{iso, org, dod, internet, mgmt, mib-2, system}

◆ Interfaces Group — Supports three interfaces: software loopback driver, Ethernet driver, and Fibre Channel IP driver:{iso, org, dod, internet, mgmt, mib-2, interface}

◆ Address Translation Group — This group is implemented, but the corresponding table might be empty:{iso, org, dod, internet, mgmt, mib-2, at}

◆ IP Group:{iso, org, dod, internet, mgmt, mib-2, ip}

◆ ICMP Group:{iso, org, dod, internet, mgmt, mib-2, icmp}

◆ TCP Group:{iso, org, dod, internet, mgmt, mib-2, tcp}

◆ UDP Group:{iso, org, dod, internet, mgmt, mib-2, udp}

◆ SNMP Group — Maintains statistics on the SNMP agent implementation:{iso, org, dod, internet, mgmt, mib-2, SNMP}

mib-2 (1)

mgmt (2)

interface (2) snmp (11)system (1) ip (4)at (3) tcp (6)icmp (5) udp (7)

MIB-II Support A-7

A

A-8


The System Group

Table A-1 System Group

MIB-2 Object Name Type Access Description

sysDescr DisplayString(0..255) R A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating system, and networking software. This description must contain only printable ASCII characters.

sysObjectID Object Identifier R The vendor’s authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining the type of hardware being managed. For example, if vendor ABC, Inc. was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its ABC Router.

sysUpTime TimeTicks R The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

sysContact DisplayString (0..255) R The textual identification of the contact person for this managed node, together with information on how to contact this person.

sysName DisplayString (0..255) R/W An administratively assigned name for this managed node. By convention, this is the node's fully qualified domain name.

sysLocation DisplayString (0..255) R/W The physical location of this node (for example, telephone closet, 3rd floor).

sysDescr DisplayString(0..255) R A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating system, and networking software. This description must contain only printable ASCII characters.



The Interfaces Group

The Interfaces Table The Interfaces table contains information on the entity's interfaces. Each interface is thought of as being attached to a subnetwork. Note that this term should not be confused with subnet, which refers to an addressing partitioning scheme used in the Internet suite of protocols.

Table A-2 Interfaces Group


ifNumber INTEGER R The number of network interfaces (regardless of their current state) present on this system.

Table A-3 Interfaces Table


ifIndex INTEGER R A unique value for each interface. Its value ranges between 1 and the value of ifNumber. The value for each interface must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization

ifDescr DisplayString(0..255)

R A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the hardware interface.

MIB-II Support A-9

A

A-10


ifType INTEGER R Values:other(1), none of the followingregular1822(2),hdh1822(3),ddn-x25(4),rfc877-x25(5),ethernet-csmacd(6),iso88023-csmacd(7),iso88024-tokenBus(8),iso88025-tokenRing(9),iso88026-man(10),starLan(11),proteon-10Mbit(12),proteon-80Mbit(13),hyperchannel(14),fddi(15),lapb(16),sdlc(17),ds1(18), T-1e1(19), european equiv. of T-1basicISDN(20),primaryISDN(21), proprietary serialpropPointToPointSerial(22),ppp(23),softwareLoopback(24),eon(25), -- CLNP over IP [11]ethernet-3Mbit(26),nsip(27), -- XNS over IPslip(28), -- generic SLIPultra(29), -- ULTRA technologiesds3(30), -- T-3sip(31), -- SMDSframe-relay(32)

ifMtu INTEGER R The size of the largest datagram which can be sent/received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface.

Table A-3 Interfaces Table (continued)




ifSpeed Gauge R An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth

ifPhysAddress PhysAddress R The interface's address at the protocol layer immediately `below' the network layer in the protocol stack. For interfaces which do not have such an address (for example, a serial line), this object should contain an octet string of zero length

ifAdminStatus INTEGER R/W The desired state of the interface. The testing(3) state indicates that no operational packets can be passed

ifOperStatus INTEGER R The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed

ifLastChange TimeTicks R The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.

ifInOctets Counter R The total number of octets received on the interface, including framing characters

ifInUcastPkts Counter R The number of subnetwork-unicast packets delivered to a higher-layer protocol

ifInNUcastPkts Counter R The number of non-unicast (that is, subnetwork-broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.

ifInDiscards Counter R The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.

ifInErrors Counter R The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.

ifInUnknownProtos Counter R The number of packets received via the interface which were discarded because of an unknown or unsupported protocol

ifOutOctets Counter R The total number of octets transmitted out of the interface, including framing characters

ifOutUcastPkts Counter R The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.



MIB-II Support A-11

A

A-12


ifOutNUcastPkts Counter R The total number of packets that higher-level protocols requested be transmitted to a non-unicast (that is, a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent.

ifOutDiscards Counter R The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.

ifOutErrors Counter R The number of outbound packets that could not be transmitted because of errors.

ifOutQLen Gauge R The length of the output packet queue (in packets).

ifSpecific OBJECT IDENTIFIER

R A reference to MIB definitions specific to the particular media being used to realize the interface. For example, if the interface is realized by an ethernet, then the value of this object refers to a document defining objects specific to ethernet. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any conforming implementation of ASN.1 and BER must be able to generate and recognize this value.





The Address Translation Group/Table

Implementation of the Address Translation group is mandatory for all systems. Note however that this group is deprecated by MIB-II. That is, it is being included solely for compatibility with MIB-I nodes, and will most likely be excluded from MIB-III nodes. From MIB-II and onwards, each network protocol group contains its own address translation tables.

The Address Translation group contains one table which is the union across all interfaces of the translation tables for converting a NetworkAddress (for example, an IP address) into a subnetwork-specific address. For lack of a better term, this document refers to such a subnetwork-specific address as a "physical" address. Examples of such translation tables are: for broadcast media where ARP is in use, the translation table is equivalent to the ARP cache; or, on an X.25 network where non-algorithmic translation to X.121 addresses is required, the translation table contains the NetworkAddress to X.121 address equivalences.

Table A-4 Address Translation Table


atIfIndex INTEGER R/W The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex

atPhysAddress PhysAddress R/W The media-dependent physical address. Setting this object to a null string (one of zero length) has the effect of invaliding the corresponding entry in the atTable object.that is, it effectively disassociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant atPhysAddress object.

atNetAddress NetworkAddress R/W The NetworkAddress (for example, the IP address) corresponding to the media-dependent physical address.

MIB-II Support A-13

A

A-14


The IP Group

Table A-5 IP Group Table


ipForwarding INTEGER R/W The indication of whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host). Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to change this object to an inappropriate value.

ipDefaultTTL INTEGER R/W The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.

ipInReceives Counter R The total number of input datagrams received from interfaces, including those received in error.

ipInHdrErrors Counter R The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.

ipInAddrErrors Counter R The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.

ipForwDatagrams Counter R The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful.

ipInUnknownProtos Counter R The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.

ipInDiscards Counter R The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (for example, for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.

ipInDelivers Counter R The total number of input datagrams successfully delivered to IP user-protocols (including ICMP)



ipOutRequests Counter R The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.

ipOutDiscards Counter R The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion

ipOutDiscards Counter R The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.

ipOutNoRoutes Counter R The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. Note that this includes any datagarms which a host cannot route because all of its default gateways are down.

ipReasmTimeout INTEGER R The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.

ipReasmReqds Counter R The number of IP fragments received which needed to be reassembled at this entity.

ipReasmOKs Counter R The number of IP datagrams successfully

ipReasmFails Counter R The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.

ipFragOKs Counter R The number of IP datagrams that have been successfully fragmented at this entity.

ipFragFails Counter R The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be; for example, because their Don't Fragment flag was set

ipFragCreates Counter R The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.

Table A-5 IP Group Table (continued)


MIB-II Support A-15

A

A-16


The IP Address Table The IP address table contains this entity's IP addressing information.

The IP Routing Table The IP routing table contains an entry for each route presently known to this entity.

Table A-6 IP Address Table


ipAdEntAddr IpAddress R The IP address to which this entry's addressing information pertains.

ipAdEntIfIndex INTEGER R The index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex

ipAdEntNetMask IpAddress R The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

ipAdEntBcastAddr INTEGER R The value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is used, the value will be 1. This value applies to both the subnet and network broadcasts addresses used by the entity on this (logical) interface

ipAdEntReasmMaxSize INTEGER (0..65535)

R The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface.

Table A-7 IP Routing Table


ipRouteDest IpAddress R/W The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. Multiple routes to a single destination can appear in the table, but access to such multiple entries is dependent on the table- access mechanisms defined by the network management protocol in use.

ipRouteIfIndex INTEGER R/W The index value which uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.

ipRouteMetric1 INTEGER R/W The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

ipRouteMetric2 INTEGER R/W An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.





ipRouteNextHop IpAddress R/W The IP address of the next hop of this route.(In the case of a route bound to an interface which is realized via a broadcast media, the value of this field is the agent's IP address on that interface.)

ipRouteType INTEGER R/W The type of route. Note that the values direct(3) and indirect(4) Refer to the notion of direct and indirect routing in the IP architecture. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipRouteTable object. That is, it effectively disassociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipRouteType object.Values:other(1), -- none of the followinginvalid(2), -- an invalidated routedirect(3), -- route to directly connected (sub-)networkindirect(4) -- route to a non-localhost/network/sub-network

ipRouteProto INTEGER R The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.other(1), -- none of the followinglocal(2), -- non-protocol information, e.g., manually configured entriesnetmgmt(3), -- set via a network management protocolicmp(4), -- e.g., obtained via ICMP,Redirect

(continued on next page)

Table A-7 IP Routing Table (continued)


MIB-II Support A-17

A

A-18


ipRouteProto (continued)

The remaining values are all gateway routing protocolsegp(5),ggp(6),hello(7),rip(8),is-is(9),es-is(10),ciscoIgrp(11),bbnSpfIgp(12),ospf(13),bgp(14)

ipRouteAge INTEGER R/W The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.

ipRouteMask IpAddress R/W Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network, and then using one of:

mask network255.0.0.0 class-A255.255.0.0 class-B255.255.255.0 class-C

If the value of the ipRouteDest is 0.0.0.0 (a default route), then the mask value is also 0.0.0.0. It should be noted that all IP routing subsystems implicitly use this mechanism.


ipRouteInfo OBJECT IDENTIFIER

R A reference to MIB definitions specific to the particular routing protocol responsible for this route, as determined by the value specified in the route's ipRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any conforming implementation of ASN.1 and BER must be able to generate and recognize this value.

Table A-7 IP Routing Table (continued)




The IP AddressTranslation Table

The IP address translation table contains the IpAddress to physical address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty; that is, it has zero entries.

Additional IP Objects

Table A-8 IP Address Translation Table


ipNetToMediaIfIndex INTEGER R/W The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.

ipNetToMediaPhysAddress PhysAddress R/W The media-dependent `physical' address.

ipNetToMediaNetAddress IpAddress R/W The IpAddress corresponding to the media-dependent `physical' address.

ipNetToMediaType INTEGER R/W The type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipNetToMediaTable. That is, it effectively disassociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToM MediaType object.Values:other(1) — None of the followinginvalid(2) — Invalidated mappingdynamic(3)static(4)

Table A-9 Additional IP Objects


ipRoutingDiscards Counter R The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries.

MIB-II Support A-19

A

A-20


The ICMP Group

Table A-10 ICMP Group Table


icmpInMsgs Counter R The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmp In Errors.

icmpInErrors Counter R The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).

icmpInDestUnreachs Counter R The number of ICMP Destination Unreachable messages received.

icmpInTimeExcds Counter R The number of ICMP Time Exceeded messages received.

icmpInParmProbs Counter R The number of ICMP Parameter Problem messages received.

icmpInSrcQuenchs Counter R The number of ICMP Source Quench messages received.

icmpInRedirects Counter R The number of ICMP Redirect messages received.

icmpInEchos Counter R The number of ICMP Echo (request) messages received.

icmpInEchoReps Counter R The number of ICMP Echo Reply messages received.

icmpInTimestamps Counter R The number of ICMP Timestamp (request) messages received.

icmpInTimestampReps Counter R The number of ICMP Timestamp Reply messages received.

icmpInAddrMasks Counter R The number of ICMP Address Mask Request messages received.

icmpInAddrMaskReps Counter R The number of ICMP Address Mask Reply messages received.

icmpOutMsgs Counter R The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.

icmpOutErrors Counter R The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value.

icmpOutDestUnreachs Counter R The number of ICMP Destination Unreachable messages sent.

icmpOutTimeExcds Counter R The number of ICMP Time Exceeded messages sent

icmpOutParmProbs Counter R The number of ICMP Parameter Problem messages sent.

icmpOutSrcQuenchs Counter R The number of ICMP Source Quench messages sent.



icmpOutRedirects Counter R The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.

icmpOutEchos Counter R The number of ICMP Echo (request) messages sent

icmpOutEchoReps Counter R The number of ICMP Echo Reply messages sent.

icmpOutTimestamps Counter R The number of ICMP Timestamp (request) messages sent.

icmpOutTimestampReps Counter R The number of ICMP Timestamp Reply messages sent.

icmpOutAddrMasks Counter R The number of ICMP Address Mask Request messages sent.

icmpOutAddrMaskReps Counter R The number of ICMP Address Mask Reply messages sent.

Table A-10 ICMP Group Table


MIB-II Support A-21

A

A-22


The TCP Group Note that instances of object types that represent information about a particular TCP connection are transient; they persist only as long as the connection in question.

Table A-11 TCP Group Table


tcpRtoAlgorithm INTEGER R The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.Values:other(1) — none of the followingconstant(2) — a constant rtorsre(3) — MIL-STD-1778, Appendix Bvanj(4) — Van Jacobson's algorithm [10]

tcpRtoMin INTEGER R The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.

tcpRtoMax INTEGER R The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.

tcpMaxConn INTEGER R The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.

tcpActiveOpens Counter R The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.

tcpPassiveOpens Counter R The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.

tcpAttemptFails Counter R The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.

tcpEstabResets Counter R The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.

tcpCurrEstab Gauge R The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.



tcpInSegs Counter R The total number of segments received, including those received in error. This count includes segments received on currently established connections.

tcpOutSegs Counter R The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.

tcpRetransSegs Counter R The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.

Table A-11 TCP Group Table (continued)


MIB-II Support A-23

A

A-24


The TCP ConnectionTable

The TCP connection table contains information about this entity's existing TCP connections.

Table A-12 TCP Connection Table


tcpConnState INTEGER R/W The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).Values:closed(1),listen(2),synSent(3),synReceived(4),established(5),finWait1(6),finWait2(7),closeWait(8),lastAck(9),closing(10),timeWait(11),deleteTCB(12)

tcpConnLocalAddress IpAddress R The local IP address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used.

tcpConnLocalPort INTEGER (0..65535

R The local port number for this TCP connection

tcpConnRemAddress IpAddress R The remote IP address for this TCP connection

tcpConnRemPort INTEGER (0..65535)

R The remote port number for this TCP connection



Additional TCP Objects

The UDP Group

The UDP Listener Table The UDP listener table contains information about this entity's UDP end points on which a local application is currently accepting datagrams.

Table A-13 Additional TCP Objects


tcpInErrs Counter R The total number of segments received in error (e.g., bad TCP checksums).

tcpOutRsts Counter R The number of TCP segments sent containing the RST flag.

Table A-14 UDP Group


udpInDatagrams Counter R The total number of UDP datagrams delivered to UDP users.

udpNoPorts Counter R The total number of received UDP datagrams for which there was no application at the destination port.

udpInErrors Counter R The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.

udpOutDatagrams Counter R The total number of UDP datagrams sent from this entity.

Table A-15 UDP Listener Table


udpLocalAddress IpAddress R The local IP address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used.

udpLocalPort INTEGER (0..65535) R The local port number for this UDP listener.

MIB-II Support A-25

A

A-26


The SNMP Group Some of the objects defined below will be zero-valued in those SNMP implementations that are optimized to support only those functions specific to either a management agent or a management station. In particular, it should be observed that the objects below Refer to an SNMP entity, and there may be several SNMP entities residing on a managed node (for example, if the node is hosting acting as a management station).

Table A-16 SNMP Group


snmpInPkts Counter R The total number of Messages delivered to the SNMP entity from the transport service.

snmpOutPkts Counter R The total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.

snmpInBadVersions Counter R The total number of SNMP Messages which were delivered to the SNMP protocol entity and were for an unsupported SNMP version.

snmpInBadCommunityNames Counter R The total number of SNMP Messages delivered to the SNMP protocol entity which used a SNMP community name not known to said entity.

snmpInBadCommunityUses Counter R The total number of SNMP Messages delivered to the SNMP protocol entity which represented an SNMP operation which was not allowed by the SNMP community named in the Message.

snmpInASNParseErrs Counter R The total number of ASN.1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP Messages.

snmpInTooBigs Counter R The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `tooBig'.

snmpInNoSuchNames Counter R The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `noSuchName'.

snmpInBadValues Counter R The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `badValue'.

snmpInReadOnlys Counter R The total number valid SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `readOnly'. It should be noted that it is a protocol error to generate an SNMP PDU which contains the value `readOnly' in the error-status field, as such this object is provided as a means of detecting incorrect implementations of the SNMP.



snmpInGenErrs Counter R The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `genErr'.

snmpInTotalReqVars Counter R The total number of MIB objects which have been retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs.

snmpInTotalSetVars Counter R The total number of MIB objects which have been altered successfully by the SNMP protocol entity as the result of receiving valid SNMP Set-Request PDUs.

snmpInGetRequests Counter R The total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity

snmpInGetNexts Counter R The total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity

snmpInSetRequests Counter R The total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity

snmpInGetResponses Counter R The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity

snmpInTraps Counter R The total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.

snmpOutTooBigs Counter R The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `tooBig

snmpOutNoSuchNames Counter R The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status is `noSuchName'.

snmpOutBadValues Counter R The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `badValue'.

snmpOutGenErrs Counter R The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `genErr'.

snmpOutGetRequests Counter R The total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity

snmpOutGetNexts Counter R The total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity

snmpOutSetRequests Counter R The total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.

Table A-16 SNMP Group (continued)


MIB-II Support A-27

A

A-28


snmpOutGetResponses Counter R The total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.

snmpOutTraps Counter R The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.

snmpEnableAuthenTraps INTEGER R/W Indicates whether the SNMP agent process is permitted to generate authentication-failure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authentication-failure traps may be disabled. Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant between re-initializations of the network management system.Values:enabled(1), disabled(2)

Table A-16 SNMP Group (continued)




Fabric Element MIB Support

Figure A-3 Fibre Channel Fabric Element MIB Supported

The Fibre Channel Fabric Element MIB enables users on network management stations to monitor, control, and configure the switch remotely using functions specifically for Connectrix switches and directors. Five groups of variables are defined and supported by the agent:

◆ Configuration (FcFeConfig)

◆ Operation (FcFeOp)

◆ Error (FcFeError)

◆ Accounting (FcFeAcct)

◆ Capability (FcFeCap)

The following sections define the Fibre Channel Fabric Element MIB variables and their output. All variables are in the Fibre Channel Fabric Element MIB, except for fcFxPortPhysAdminStatus which is defined under fcFxPortPhysTable in the fcFeOp group, are read-only.

fcFeError (3)fcFeOp (2) fcFeAcct (4) fcFeCap (5)fcConfig (1)

fcFe (1)

fcFabric (2)

fibre channel(42)

experimental(3)

Fabric Element MIB Support A-29

A

A-30


Predefined Types

Table A-17 Fabric Element Management MIB: Predefined Types

Type Syntax Description

DisplayString OCTET STRING

MilliSeconds INTEGER (0..2147383647)

2^31 – 1

MicroSeconds INTEGER (0..2147383647)

FcNameId OCTET STRING (SIZE(8))

Worldwide Name or Fibre Channel Name associated with an FC entity. It’s a Network_Destination_ID or Network_Source_ID composed of a value up to 60 bits wide, occupying the remaining 8 bytes while the first nibble identifies the format of the Name_Identifier with hex values: 0: ignored, 1: IEEE 48-bit address, 2: IEEE extended, 3: Locally assigned, 4: 32-bit IP address.

FabricName FcNameId The Name Identifier of a Fabric. Each Fabric shall provide a unique Fabric Name. Only the following formats are allowed: IEEE48, and Local.

FcPortName FcNameId The Name Identifier associated with a port. Only the following formats are allowed: IEEE48, IEEE extended, and Local.

FcAddressId OCTET STRING (SIZE (3))

Fibre Channel Address Identifier. A 24-bit value unique within the address space of a Fabric

FcRxDataFieldSize INTEGER (128..2112)

Receive Data_Field Size

FcBbCredit INTEGER (0..32767)

Buffer-to-buffer Credit

FcphVersion INTEGER (0..255)

FcStackedConnMode INTEGER The values are defined as follow: none(1), transparent(2), lockedDown(3).

FcCosCap INTEGER (0..127)

bit 0 – Class F, bit 1 – Class 1, bit 2 -- Class 2, bit 3 – Class 3, bit 4 – Class 4, bit 5 – Class 5, bit 6 – Class 6, bit 7 – reserved for future.

Fc0BaudRate INTEGER The values are defined as follow: other(1) – none of below, oneEighth(2) – 155 Mbaud (12.5MB/s), quarter(4) – 266 Mbaud (25.0MB/s), half(8) – 532 Mbaud (50.0MB/s), full(16) – 1 Gbaud (100MB/s), double(32) – 2 Gbaud (200MB/s), quadruple(64) -- 4 Gbaud (400MB/s).

Fc0BaudRateCap INTEGER (0..127)

bit 0 – other, bit 1 – oneEighth, bit 2 – quarter, bit 3 – half, bit 4 – full, bit 5 – double, bit 6 – quadruple, bit 7 – reserved for future.



Fc0MediaCap INTEGER (0..65535)

bit 0 – unknown, bit 1—single mode fibre (sm), bit 2 – multi-mode fibre 50 micron (m5), bit 3 -- multi-mode fibre 62.5 micron (m6), bit 4 – video cable (tv), bit 5 – miniature cable (mi), bit 6 -- shielded twisted pair (stp), bit 7 – twisted wire (tw), bit 8 – long video (lv), bits 9-15 -- reserved for future use.

Fc0Medium INTEGER The values are defined as follow: unknown(1), sm(2), m5(4), m6(8), tv(16), mi(32), stp(64), tw(128), lv(256).

Fc0TxType INTEGER The values are defined as follow: unknown(1), longWaveLaser(2) – (LL), shortWaveLaser(3)—(SL), longWaveLED(4) – (LE), electrical(5) – (EL), shortWaveLaser-noOFC(6) – (SN).

Fc0Distance INTEGER The values are defined as follow: unknown(1), long(2), intermediate(3), short(4).

FcFeModuleCapacity INTEGER (1..256)

FcFeFxPortCapacity INTEGER (1..256)

FcFeModuleIndex INTEGER (1..256)

FcFeFxPortIndex INTEGER (1..256)

FcFeNxPortIndex INTEGER (1..126)

FcFxPortMode INTEGER The values are defined as follow: unknown(1), fPort(2), flPort(3).

FcBbCreditModel INTEGER The values are defined as follow: regular(1), alternate(2).

Table A-17 Fabric Element Management MIB: Predefined Types (continued)



A

A-32


MIB Objects Defined in the Fabric Element MIB

Module Table A table that contains, one entry for each module in the Fabric Element, information of the modules.

Table A-18 Fabric Element MIB Objects

Fabric Element MIB Object Name Type

Provided By Access Description

fcFabricName FabricName PCP R The Name_Identifier of the Fabric to which this Fabric Element belongs.

FcElementName FcNameId PCP R The Name_Identifier of the Fabric Element.

FcFeModuleCapacity FcFeModuleCapacity SNMP R The maximum number of modules in the Fabric Element, regardless of their current state.

Table A-19 Fabric Element MIB Modules



fcFeModuleDescr DisplayString (SIZE(256))

McK DEV_TBL

R A textual description of the module. This value should include the full name and version identification of the module. It should contain printable ASCII characters.This string should be derived from VPD information stored in the FRU EEPROM.

FcFeModuleObjectID OBJECT IDENTIFIER

SNMP R The vendor’s authoritative identification of the module. This value may be allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of module is being managed. For example, this object could take the value 1.3.6.1.4.1.99649.3.9 if vendor ‘Neufe Inc.’ was assigned the subtree 1.3.6.1.4.1.99649, and had assigned the identifier 1.3.6.1.4.1.99649.3.9 to its ‘FeFiFo-16 PlugInCard.This is a fixed object identifier assigned from the McDATA enterprise subtree (1.3.6.1.4.1.289.2.1.1.2).



fcFeModuleOperStatus INTEGER SNMP R This object indicates the operational status of the module: online(1) – the module is functioning properly; offline(2) – the module is not available; testing(3) – the module is under testing; and faulty(4) – the module is defective in some way.The status is evaluated from fcFPortPhysOperStatus as following order. Testing(3): the module is under testing if all four ports on the current module are testing; faulty(4): the module is defective if any of the ports on the current module is faulty.Online(1): the module is functioning properly if any of the ports on the current module is online or testing;offline(2): the module is not available if any of the ports on the current module is offline.

FcFeModuleLastChange TIMETICKS SNMP R This object contains the value of sysUpTime when the module entered its current operational status. A value of zero indicates that the operational status of the module has not changed since the agent last restarted.This is SS_TIM_RD_TICKS(MILLISEC) * 10

fcFeModuleFxPortCapacity FcFeFxPortCapacity AS R The number of FxPort that can be contained within the module. Within each module, the ports are uniquely numbered in the range from 1 to fcFeModuleFxPortCapacity inclusive. However, the numbers are not required to be contiguous.This is AS_glob.prod_cnfg_ptr->ports_per_module

fcFeModuleName FcNameId PCP R The Name_Identifier of the module.This is the port module World Wide Name.

Table A-19 Fabric Element MIB Modules (continued)




A

A-34


FxPort Configuration Table

A table that contains, one entry for each FxPort in the Fabric Element, configuration and service parameters of the FxPorts.

Table A-20 FxPort Configuration Table



fcFxConfFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxPortName FcPortName PCP R The name identifier of this FxPort. Each FxPort has a unique port name within the address space of the Fabric.This is the WWN assigned to the port.

FcFxPortFcphVersionHigh FcphVersion FC2 R The highest or most recent version of FC-PH that the FxPort is configured to support. Since the switch is not capable of changing its support for FC-PH version, the version reported is the one currently in use for this port. If there is no device logged in, then the value is 0.If a device is logged in, the values reported are:6 = FC-PH 4.07 = FC-PH 4.18 = FC-PH 4.29 = FC-PH 4.30x10 = FC-PH2 0x20 = FC-PH3

FcFxPortFcphVersionLow FcphVersion FC2 R The lowest or earliest version of FC-PH that the FxPort is configured to support. Since the switch is not capable of changing its support for FC-PH version, the version reported is the one currently in use for this port. If there is no device logged in, then the value is 0. For values Refer to FcFxPortFcphVersionHigh.

FcFxPortBbCredit FcBbCredit PCP R The total number of receive buffers available for holding Class 1 connect-request, Class 2 or 3 frames from the attached NxPort. It is for buffer-to-buffer flow control in the direction from the attached NxPort (if applicable) to Fport.



FcFxPortRxBufSize FcRxDataFieldSize LOGIN SERVER

R The largest Data_Field Size (in octets) for an FT_1 frame that can be received by the FxPort.This is fixed at 2112.

FcFxPortRatov MilliSeconds PCP R The Resource_Allocation_Timeout Value configured for the FxPort. This is used as the timeout value for determining when to reuse an NxPort resource such as a Recovery_Qualifier. It represents E_D_TOV (Refer to next object) plus twice the maximum time that a frame may be delayed within the Fabric and still be delivered.

FcFxPortEdtov MilliSeconds PCP R The E_D_TOV value configured for the FxPort. The Error_Detect_Timeout Value is used as the timeout value for detecting an error condition.

FcFxPortCosSupported FcCosCap SNMP R A value indicating the set of Classes of Service supported by the FxPort.This is fixed at CLASS_2 | CLASS_3 (0x0C).

fcFxPortIntermixSupported INTEGER SNMP R A flag indicating whether or not the FxPort supports an Intermixed Dedicated Connection. The values are defined as follow: yes(1) and no(2).This is fixed at no(2).

FcFxPortStackedConnMode FcStackedConnMode SNMP R A value indicating the mode of Stacked Connect supported by the FxPort.This is fixed at none(1).

FcFxPortClass2SeqDeliv INTEGER SNMP R A flag indicating whether or not Class 2 Sequential Delivery is supported by the FxPort. The values are defined as follow: yes(1) and no(2).This is fixed at yes(1).

FcFxPortClass3SeqDeliv INTEGER SNMP R A flag indicating whether or not Class 3 Sequential Delivery is supported by the FxPort. The values are defined as follow: yes(1) and no(2).This is fixed at yes(1).

Table A-20 FxPort Configuration Table (continued)




A

A-36


FcFxPortHoldTime MicroSeconds PCP R The maximum time (in microseconds) that the FxPort shall hold a frame before discarding the frame if it is unable to deliver the frame. The value 0 means that the FxPort does not support this parameter.This is equal to quarter of E_D_TOV which is obtained from PCP.

FcFxPortBaudRate Fc0BaudRate FPM R The FC-0 baud rate of the FxPort.One of these values, or no value will be returned:0x10, 1 Gbaud (100 MB/s) 0x20, 2 Gbaud (200 MB/s) 0x40, 4 Gbaud (400 MB/s)

FcFxPortMedium Fc0Medium FPM R The FC-0 medium of the FxPort.The value is a bitwise OR of these values:0x02, Single-mode fibre 0x04, Multimode fibre 50 micron 0x08, Multimode fibre 62.5 micron Or it will be unknown (0x01) if no information is available.

FcFxPortTxType Fc0TxType FPM R The FC-0 transmitter type of the FxPort:1, unknown (long distance laser)2, Longwave Laser (LC version)3, Shortwave Laser6 Shortwave Laser-no OFC

FcFxPortDistance Fc0Distance FPM R The FC-0 distance range of the FxPort transmitter:1, Unknown2, Long3, Intermediate4, Short

Table A-20 FxPort Configuration Table (continued)





FxPort Operation Table

A table that contains, one entry for each FxPort in the Fabric Element, operational status and parameters of the FxPorts.

Table A-21 FxPort Operation Table



fcFxPortOperFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxPortID FcAddressId Login Server

R The address identifier by which this FxPort is identified within the Fabric. The FxPort may assign its address identifier to its attached NxPort(s) during Fabric Login.Return a port id if the port is login into the fabric, otherwise this address is 000000 in FCEOS.

fcFPortAttachedPortName FcPortName Login Server

R The port name of the attached N_Port, if applicable. If the value of this object is ‘0000000000000000’H, this F_Port has no NxPort attached to it. This variable has been deprecated and may be implemented for backward compatibility. Not supported for NL ports.

FcFPortConnectedPort FcAddressId SNMP R The address identifier of the destination FxPort with which this FxPort is currently engaged in a either a Class 1 or loop connection. If the value of this object is ‘000000’H, this FxPort is not engaged in a class 1 connection. This variable has been deprecated and may be implemented for backward compatibility.This address is fixed at 0x000000.

FcFxPortBbCreditAvailable Gauge PSCC R The number of buffers currently available for receiving frames from the attached port in the buffer-to-buffer flow control. The value should be less than or equal to fcFxPortBbCredit.

FcFxPortOperMode FcFxPortMode AS R The current operational mode of the FxPort.This value is fport(2) if the port_state_data is unavailable or the port is a fport, or unknown(1) for the other port state.

FcFxPortAdminMode FcFxPortMode AS R The desired operational mode of the FxPort.This value is fport(2) if the port_state_data is unavailable or the port is a fport, or unknown(1) for the other port state.


A

A-38


FxPort Physical Level Table

A table that contains one entry for each FxPort in the Fabric Element, physical level status and parameters of the FxPorts.

Table A-22 FxPort Physical Level Table



fcFxPortPhysFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxPortPhysAdminStatus INTEGER PCP, FPM

R/W The desired state of the FxPort. A management station may place the FxPort in a desired state by setting this object accordingly. The testing(3) state indicates that no operational frames can be passed. When a Fabric Element initializes, all FxPort start with fcFxPortPhysAdminStatus in the offline(2) state. As the result of either explicit management action or per configuration information accessible by the Fabric Element, fcFxPortPhysAdminStatus is then changed to either the online(1) or testing(3) states, or remains in the offline state. The values are defined as follow: online(1) – place port online, offline(2) – take port offline, testing (3).This MIB variable is maintained by both the portState, ps*, defined in FPM and the PORT_BLOCKED_STATE, pstate*, defined in PCP. The psNotInstalled shows that the port is not exist. The psIntDiags and psExtLoop indicate the testing(3) state. The pstateUNBLOCKD and pstateBLOCKD indicate the online(1) and offline(2) respectively.

If the port cannot be set to testing because it is inactive or in a failed state, the return value will be resource_unavailable(13).



FcFxPortPhysOperStatus INTEGER FPM, SNMP

R The current operational status of the FxPort. The testing(3) indicates that no operational frames can be passed. If fcFxPortPhysAdminStatus is offline(2) then fcFxPortPhysOperStatus should be offline(2). If fcFxPortPhysAdminStatus is changed to online(1) then fcFxPortPhysOperStatus should change to online(1) if the FxPort is ready to accept Fabric Login request from the attached NxPort; it should proceed and remain in the link-failure(4) state if and only if there is a fault that prevents it from going to the online(1) state. The values are defined as follow: online(1) – Login may proceed, offline(2) – Login cannot proceed, testing(3) – port is under test, link-failure(4) – failure after online/testing.Refer to Port State Descriptions on page A-100.

FcFxPortPhysLastChange TimeTicks SNMP R The value of sysUpTime at the time the FxPort entered its current operational status. A value of zero indicates that the FxPort’s operational status has not changed since the agent last restarted.This is SS_TIM_RD_TICKS(MILLISEC) * 10.

FcFxPortPhysRttov MilliSeconds SNMP R The Receiver_Transmitter_Timeout value of the FxPort. This is used by the receiver logic to detect Loss of Synchronization.This value is fixed at 100ms.

Table A-22 FxPort Physical Level Table (continued)




A

A-40


FxPort Fabric Login Table

An entry containing service parameters established from a successful fabric login.

Table A-23 FxPort Fabric Login Table

Fabric Element MIB Object Name TypeProvided By Access Description

fcFxlogiFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxlogiNxPortIndex FcFeNxPortIndex SNMP R The object identifies the associated NxPort in the attachment for which the entry contains information.

FcFxPortFcphVersionAgreed FcphVersion Login Server

R The version of FC-PH that the FxPort has agreed to support from the Fabric Login.

FcFxPortNxPortBbCredit FcBbCredit Login Server

R The total number of buffers available for holding Class 1 connect-request, Class 2 or Class 3 frames to be transmitted to the attached NxPort. It is for buffer- to-buffer flow control in the direction from FxPort to NxPort. The buffer-to-buffer flow control mechanism is indicated in the respective fcFxPortBbCreditModel.

FcFxPortNxPortRxDataFieldSize FcRxDataFieldSize Login Server

R The Receive Data Field Size of the attached NxPort. This is a binary value that specifies the largest Data Field Size for an FT_1 frame that can be received by the NxPort. The value is in number of bytes and ranges from 128 to 2112 inclusive.

FcFxPortCosSuppAgreed FcCosCap Login Server

R A variable indicating that the attached NxPort has requested the FxPort for the support of classes of services and the FxPort has granted the request.



FcFxPortIntermixSuppAgreed INTEGER SNMP R A variable indicating that the attached NxPort has requested the FxPort for the support of Intermix and the FxPort has granted the request. This flag is only valid if Class 1 service is supported. The values are defined as follow: yes(1) and no(2).This is always no(2).

FcFxPortStackedConnModeAgreed FcStackedConnMode SNMP R A variable indicating whether the FxPort has agreed to support stacked connect from the Fabric Login. This is only meaningful if Class 1 service has been agreed.This is always none(1).

FcFxPortClass2SeqDelivAgreed INTEGER Login Server

R A variable indicating whether the FxPort has agreed to support Class 2 sequential delivery from the Fabric Login. This is only meaningful if Class 2 service has been agreed. The values are defined as follow: yes(1) and no(2).

FcFxPortClass3SeqDelivAgreed INTEGER Login Server

R A flag indicating whether the FxPort has agreed to support Class 3 sequential delivery from the Fabric Login. This is only meaningful if Class 3 service has been agreed. The values are defined as follow: yes(1) and no(2).

FcFxPortNxPortName FcPortName Login Server

R The port name of the attached NxPort, if applicable. If the value of this object is ‘0000000000000000’H, this FxPort has no NxPort attached to it.This is the world wide Name of the attached to NxPort. It’s same as fcFPortAttachedPortName.

Table A-23 FxPort Fabric Login Table (continued)



A

A-42


FcFxPortConnectedNxPort FcAddressId SNMP R The address identifier of the destination FxPort with which this FxPort is currently engaged in a either a Class 1 or loop connection. If the value of this object is ‘000000’H, this FxPort is not engaged in a connection.This is fixed at ‘000000’H.

fcFxPortBbCreditModel FcBbCreditModel SNMP R This object identifies the BB_Credit model used by the FxPort. The regular model refers to the Buffer-to-Buffer flow control mechanism defined in FC-PH [1] is used between the F_Port and the N_Port. For FL_Ports, the Alternate Buffer-to-Buffer flow control mechanism as defined in FC-AL [4] is used between the FL_Port and any attached NL_Ports.This is fixed at regular(1).

Table A-23 FxPort Fabric Login Table (continued)




FxPort Error Table A table that contains one entry for each FxPort, counters that record the numbers of errors detected.

Table A-24 FxPort Error Table



fcFxPortErrorFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxPortLinkFailures Counter PSCC R The number of link failures detected by this FxPort.

FcFxPortSyncLosses Counter PSCC R The number of loss of synchronization detected by the FxPort.

FcFxPortSigLosses Counter PSCC R The number of loss of signal detected by the FxPort.

FcFxPortPrimSeqProtoErrors Counter PSCC R The number of primitive sequence protocol errors detected by the FxPort.

FcFxPortInvalidTxWords Counter PSCC R The number of invalid transmission word detected by the FxPort.

FcFxPortInvalidCrcs Counter PSCC R The number of invalid CRC detected by the FxPort.

FcFxPortDelimiterErrors Counter PSCC R The number of Delimiter Errors detected by this FxPort.

FcFxPortAddressIdErrors Counter PSCC R The number of address identifier errors detected by this FxPort.

FcFxPortLinkResetIns Counter PSCC R The number of Link Reset Protocol received by this FxPort from the attached NxPort.

FcFxPortLinkResetOuts Counter PSCC R The number of Link Reset Protocol issued by this FxPort to the attached NxPort.

FcFxPortOlsIns Counter PSCC R The number of Offline Sequence received by this FxPort.

FcFxPortOlsOuts Counter PSCC R The number of Offline Sequence issued by this FxPort.


A

A-44


Class 1 Accounting Table

A table that contains one entry for each FxPort in the Fabric Element, Class 1 accounting information. These entries are all zero, since Class 1 is not supported.


A table that contains one entry for each FxPort in the Fabric Element, Class 2 accounting information recorded since the management agent has re-initialized.

Table A-25 Class 2 Accounting Table



fcFxPortC2AcctFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxPortC2InFrames Counter PSCC R The number of Class 2 frames received by this FxPort from its attached NxPort.

FcFxPortC2OutFrames Counter PSCC R The number of Class 2 frames delivered through this FxPort to its attached NxPort.

FcFxPortC2InOctets Counter PSCC R The number of Class 2 frame octets, including the frame delimiters, received by this FxPort from its attached NxPort.

FcFxPortC2OutOctets Counter PSCC R The number of Class 2 frame octets, including the frame delimiters, delivered through this FxPort to its attached NxPort.

FcFxPortC2Discards Counter SNMP R The number of Class 2 frames discarded by this FxPort. This value is not supported; therefore it is always zero.

FcFxPortC2FbsyFrames Counter PSCC R The number of F_BSY frames generated by this FxPort against Class 2 frames.

FcFxPortC2FrjtFrames Counter PSCC R The number of F_RJT frames generated by this FxPort against Class 2 frames.




A table that contains one entry for each FxPort in the Fabric Element, Class 3 accounting information recorded since the management agent has re-initialized.

Table A-26 Class 3 Accounting Table



fcFxPortC3AcctFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxPortC3InFrames Counter PSCC R The number of Class 3 frames received by this FxPort from its attached NxPort.

FcFxPortC3OutFrames Counter PSCC R The number of Class 3 frames delivered through this FxPort to its attached NxPort.

FcFxPortC3InOctets Counter PSCC R The number of Class 3 frame octets, including the frame delimiters, received by this FxPort from its attached NxPort.

FcFxPortC3OutOctets Counter PSCC R The number of Class 3 frame octets, including the frame delimiters, delivered through this FxPort to its attached NxPort.

FcFxPortC3Discards Counter PSCC R The number of Class 3 frames discarded by this FxPort.


A

A-46


FxPort Capability Table

A table that contains one entry for each FxPort, the capabilities of the port within the Fabric Element.

All the counters are 32 bit counters.

Table A-27 FxPort Capacity Table


fcFxPortCapFxPortIndex FcFeFxPortIndex SNMP R This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.This number ranges from 1 to AS_glob.prod_cnfg_ptr->ports_per_module.

FcFxPortCapFcphVersionHigh FcphVersion FC2 R The highest or most recent version of FC-PH that the FxPort is capable of supporting. For values Refer to FcFxPortFcphVersionHigh.

FcFxPortCapFcphVersionLow FcphVersion FC2 R The lowest or earliest version of FC-PH that the FxPort is capable of supporting. For values Refer to FcFxPortFcphVersionHigh.

FcFxPortCapBbCreditMax FcBbCredit SNMP R The maximum number of receive buffers available for holding Class 1 connect-request, Class 2 or Class 3 frames from the attached NxPort.This value is fixed at 16.

FcFxPortCapBbCreditMin FcBbCredit SNMP R The minimum number of receive buffers available for holding Class 1 connect-request, Class 2 or Class 3 frames from the attached NxPort.This value is fixed at 1.

FcFxPortCapRxDataFieldSizeMax FcRxDataFieldSize SNMP R The maximum size in bytes of the Data Field in a frame that the FxPort is capable of receiving from its attached NxPort.This value is fixed at 2112.



FcFxPortCapRxDataFieldSizeMin FcRxDataFieldSize SNMP R The minimum size in bytes of the Data Field in a frame that the FxPort is capable of receiving from its attached NxPort.This value is fixed at 2112.

FcFxPortCapCos FcCosCap SNMP R A value indicating the set of Classes of Service that the FxPort is capable of supporting.This value is fixed at CLASS_2 | CLASS_3 (0x0C).

fcFxPortCapIntermix INTEGER SNMP R A flag indicating whether or not the FxPort is capable of supporting the intermixing of Class 2 and Class 3 frames during a Class 1 connection. This flag is only valid if the port is capable of supporting Class 1 service. The values are defined as follow: yes(1) and no(2).This value is fixed no(2).

FcFxPortCapStackedConnMode FcStackedConnMode SNMP R A value indicating the mode of Stacked Connect request that the FxPort is capable of supporting.This value is fixed at none(1).

FcFxPortCapClass2SeqDeliv INTEGER SNMP R A flag indicating whether or not the FxPort is capable of supporting Class 2 Sequential Delivery.This value is fixed at yes(1).

FcFxPortCapClass3SeqDeliv INTEGER SNMP R A flag indicating whether or not the FxPort is capable of supporting Class 3 Sequential Delivery.This value is fixed at yes(1).

FcFxPortCapHoldTimeMax MicroSeconds SNMP R The maximum holding time (in microseconds) that the FxPort is capable of supporting.This value is not supported; therefore it is always zero.

Table A-27 FxPort Capacity Table (continued)



A

A-48


FcFxPortCapHoldTimeMin MicroSeconds SNMP R The minimum holding time (in microseconds) that the FxPort is capable of supporting.This value is not supported; therefore it is always zero.

FcFxPortCapBaudRates Fc0BaudRateCap FPM R A value indicating the set of baud rates that the FxPort is capable of supporting. This variable has been deprecated and may be implemented for backward compatibility.

FcFxPortCapMedia Fc0MediaCap FPM R A value indicating the set of media that the FxPort is capable of supporting.

Table A-27 FxPort Capacity Table (continued)




Fibre Alliance MIB (fcmgmt.mib)

Type Definitions

Table A-28 FibreAlliance MIB Type Definitions


FcNameId OCTET STRING (SIZE(8)) Represents the Worldwide Name (WWN; IEEE 60-bitvariety; standard part of T11 definitions for fibre channel) associated with a Fibre Channel (FC) entity.

FcGlobalId OCTET STRING (SIZE(16)) Represents the Worldwide Name (WWN; IEEE 124-bit variety) associated with a Fibre Channel (FC) entity.

FcEventSeverity INTEGER The set of values which define the event severity that will be logged by this connectivity unit. Values unknown (1) through debug (9) are essentially self-explanatory; mark (10) means that all messages are logged. The values are defined as follow: unknown (1), emergency (2), alert (3), critical (4), error (5), warning (6), notify (7), info (8), debug (9), mark (10).

FcUnitType INTEGER The values are defined as follow: unknown (1) – cannot be determined, other (2) – none of the following, hub (3) – passive connectivity unit supporting loop protocol, switch (4) – active connectivity unit supporting multiple protocols, gateway (5) – unit that converts not only the interface but also the frame into another protocol. The assumption is that there is always two gateways connected together. For example, FC <-> ATM, converter (6) – unit that converts from one interface to another, For example, FC <-> SCSI, hba(7) – host bus adapter, proxyAgent (8) – software proxy-agent, storageDevice (9) – disk, cd, tape, etc, host (10) – host computer, storageSubsystem (11) – raid, library, etc, module (12) – subcomponent of a system, swDriver (13) – software driver, storageAccessDevice (14) – Provides storage management and access for heterogeneous hosts and heterogeneous devices.

FcPortFCClass BITS Represents the class(es) of service represented on a given port, in a given operational context. The values are defined as follow: unknown (0), classF (1), class1(2), class2 (3), class3 (4), class4 (5), class5 (6), class6 (7).

Fibre Alliance MIB (fcmgmt.mib) A-49

A

A-50


Connectivity Unit Group

Table A-29 Connectivity Unit Group

FA MIB Object Name Type Value Access Description

fcConnUnitNumber INTEGER 1 R The number of connectivity units present on this system. May be a count of the boards in a chassis or the number of full boxes in a rack.

FcConnURL DisplayString HTTP://<switch IP address>

R The top-level URL of the system. If it does not exist the value is an empty string. The URL format is implementation dependent and can have keywords embedded that are preceded by a percent sign (e.g.,%USER).

The following are the defined keywords that will be recognized and replaced with data during a launch:• USER — Replace with username• PASSWORD — Replace with password• GLOBALID — Replace with globalid• SERIALNO — Replace with serial numberA management application will read this object from the MIB, provide values for any of the keywords listed above that are present in the string, and then use the URL to invoke or launch the program referenced.

FcConnUnitSnsMaxRows Unsigned32 (Same as Gauge).

The number entries in the Name Server Table.

R The maximum number of rows in the fcConnUnitSnsTable table.



fcConnUnitTable Contains general information on the system’s units.

Table A-30 fcConnUnitTable

FA MIB Object Name Type Product Mapping Access Description

*fcConnUnitId OCTET STRING Switch WWN R The unique identification for this connectivity unit among those within this proxy domain. The value MUST be unique within the proxy domain because it is the index variable for fcConnUnitTable. The value assigned to a given connectivity unit SHOULD be persistent across agent and unit resets. It SHOULD be the same as fcConnUnitGlobalId if fcConnUnitGlobalId is known and stable.

FcConnUnitGlobalId FcGlobalId Switch WWN R An optional global-scope identifier for this connectivity unit. It MUST be a WWN for this connectivity unit or 16 octets of value zero. WWN formats requiring fewer than 16 octets MUST be extended to 16 octets with trailing zero octets. If a WWN is used for fcConnUnitId, the same WWN MUST be used for fcConnUnitGlobalId.

When a non-zero value is provided, it SHOULD be persistent across agent and unit resets. It SHOULD be globally unique. It SHOULD be one of these FC-PH/PH3 formats:IEEE (NAA=1)IEEE Extended (NAA=2)IEEE Registered (NAA=5).IEEE Registered extended (NAA=6).


A

A-52


FcConnUnitGlobalId (continued)

FcGlobalId Switch WWN R Use of the IEEE formats allows any IEEE-registered vendor to assure global uniqueness independently. The following are some references on IEEE WWN formats: http://standards.ieee.org/regauth/oui/tutorials/fibreformat.html http://standards.ieee.org/regauth/oui/tutorials/fibrecomp_id.htmlIf one or more WWNs are associated with the connectivity unit via other management methods, one of them SHOULD be used for fcConnUnitGlobalId. If there is not a WWN assigned specifically to the connectivity unit, there is some merit, though not a requirement, to using a WWN assigned to (one of) its permanently attached FC/LAN interface(s). This can not risk uniqueness, though. As a counterexample, if your agent runs in a host and the host has an HBA, it is quite possible that agent, host, and HBA will all be distinct connectivity units, so the host and agent can not use the WWN of the HBA. Another example: If your hub has a built-in Ethernet port, it might be reasonable for the hub to use its LAN address (prefixed with the appropriate NAA) as its fcConnUnitId. But if the Ethernet were a replaceable PCCard, the hub should have an independent ID.

FcConnUnitType FcUnitType switch(4) R The type of this connectivity unit.

FcConnUnitNumports Unsigned32 Number of ports from PROD_CNFG.

R Number of physical ports in the connectivity unit (internal/embedded, external).

Table A-30 fcConnUnitTable (continued)




FcConnUnitState INTEGER online and coming-online will indicate online state (2), and offline and going-offline will indicate offline state (3).

R This object reports the overall state of the connectivity unit. The meaning of all values is essentially self-explanatory. Any of these values may occur with any of the fcConnUnitStatus values.The values are defined as follows: unknown (1), online (2), offline (3).

FcConnUnitStatus INTEGER This value will be mapped from current status of switch in such a way that operational status indicates ok (3), degraded status indicates warning (4), failed status indicate failed (5).

R This object reports the overall status of the connectivity unit. The warning (4) value means that the connectivity unit needs attention; all other values are essentially self-explanatory. Any of these values may occur with any of the fcConnUnitState values.The values are defined as follows: unknown (1), unused (2), ok (3), warning(4), failed (5)

fcConnUnitProduct SnmpAdminString The oem product name. R The connectivity unit vendor’s product model name.

FcConnUnitSerialNo SnmpAdminString OEM serial number. R The serial number identification for this connectivity unit.

FcConnUnitUpTime TimeTicks R The number of centiseconds since the last unit initialization.

FcConnUnitUrl DisplayString Same as fcConnURL. R/W URL to launch a management application, if applicable. Otherwise empty string. In a standalone unit, this would be the same as the top level URL. This has the same definition as systemURL for keywords.

FcConnUnitDomainId OCTET STRING (SIZE (3))

FFCCXXwhere XX is the active domainId of the switch.

R 24 bit Fibre Channel address ID of this connectivity unit. Following the fibre channel standard, the right-most bit of the right-most octet is for the least significant bit of the address value; the left-most bit of the left-most octet, if needed, is for the most significant bit of the address value. If this value is not applicable, all bits set to 1.




A

A-54


FcConnUnitProxyMaster INTEGER yes(3) R A value of ‘yes’ means this is the proxy master unit for a set of managed units. For example, this could be the only unit with a management card in it for a set of units. A standalone unit should return ‘yes’ for this object. The values are defined as follow: unknown (1), no (2), yes (3).

FcConnUnitPrincipal INTEGER R Whether this connectivity unit is the principal unit within the group of fabric elements. If this value is not applicable, return unknown. The values are defined as follow: unknown (1), no (2), yes (3).

FcConnUnitNumSensors Unsigned32 The number of sensors. R Number of sensors in the fcConnUnitSensorTable.

FcConnUnitNumRevs Unsigned32 1 R The number of revisions in the fcConnUnitRevsTable.

FcConnUnitModuleId OCTET STRING(SIZE(16))

return 16 zeros.(currently not supported)

R This is a unique id, persistent between boots, that can be used to group a set of connectivity units together into a module. The intended use would be to create a connectivity unit with a fcConnUnitType of ‘module’ to represent a physical or logical group of connectivity units. Then the members of the group would set the value of fcConnUnitId for this ‘container’ connectivity unit. FcConnUnitModuleId should be zeros if this connectivity unit is not part of a module.

FcConnUnitName SnmpAdminString switch’s configured name. Writable and persistent across IPL.

R/W A name for this connectivity unit. This object value should be persistent between boots.

FcConnUnitInfo SnmpAdminString A textual description of the product. Writable and persistent across IPL.

R/W Information about this connectivity unit. This object value should be persistent between boots.





FcConnUnitControl INTEGER Always return unknown (1) on read operation. ResetConnUnitWarmStart (4), offlineConnUnit (5), and onlineConnUnit (6) will be supported by PCP. ResetConnUnitWarmStart (4) indicates IPL on the switch is performed. ResetConnUnitColdStart (3) is not supported.

R/W This object is used to control the addressed connectivity unit. NOTE: ‘ColdStart’ and ‘WarmStart’ are as defined in mib-2 and are not meant to be a factory reset.

ResetConnUnitColdStart: the addressed unit performs a ‘ColdStart’ reset.

ResetConnUnitWarmStart: the addressed unit performs a ‘WarmStart’ reset.

OfflineConnUnit: the addressed unit puts itself into an implementation dependant ‘offline’ state. In general, if a unit is in an offline state, it cannot be used to perform meaningful Fibre Channel work.

OnlineConnUnit: the addressed unit puts itself into an implementation dependant ‘online’ state. In general, if a unit is in an online state, it is capable of performing meaningful Fibre Channel work.

NOTE: Each implementation may chose not to support SNMP Set operations for any or all of these values. For Sets specifying varbinds for instances of this object and values not supported by a given implementation, the agent will return the SNMP WrongValue PDU error code.The values are defined as follow: unknown (1), invalid (2), resetConnUnitColdStart (3), resetConnUnitWarmStart (4), offlineConnUnit (5), onlineConnUnit (6).




A

A-56


FcConnUnitContact SnmpAdminString Contact information for this connectivity unit. Writable and persistent across IPL.

R/W Contact information for this connectivity unit. The contact information is intended to facilitate contacting someone in case of problems, questions, etc. (e.g., the help desk internal to a company).

FcConnUnitLocation SnmpAdminString The physical location of the switch.Writable and persistent across IPL.

R/W Location information for this connectivity unit.

FcConnUnitEventFilter FcEventSeverity Writable and it’s set to the Default value of info(8) after IPL.

R/W This value defines the event severity that will be logged by this connectivity unit. All events of severity less than or equal to fcConnUnitEventFilter are logged in the fcConnUnitEventTable.

FcConnUnitNumEvents Unsigned32 Number of events in the fcConnUnitEventTable (always 200 or fewer); the maximum size of the event table.

R Number of events currently in the fcConnUnitEventTable.

FcConnUnitMaxEvents Unsigned32 200. R Max number of events that can be recorded at any one time in the fcConnUnitEventTable.

FcConnUnitEventCurrID Unsigned32 The current event index is used as the last used event id.

R The last used event id (fcConnUnitEventIndex) recorded in the fcConnUnitEventTable. When no events are presently recorded in the fcConnUnitEventTable, the value of this object MUST be zero.





Firmware Table The revisions table lists the revisions supported by the associated connectivity units.

Table A-31 Firmware Table


*fcConnUnitRevsIndex Unsigned32 Not accessible R A unique value among all fcConnUnitRevsEntrys with the same value of fcConnUnitId, in the range between 1 and fcConnUnitNumRevs[fcConnUnitId].

FcConnUnitRevsRevision SnmpAdminString XX.XX.XX (The revision of the switch).

R A vendor-specific value identifying a revision of a component of the connectivity unit.

FcConnUnitRevsDescription SnmpAdminString “Switch Firmware Level”

R Description of a component in the fcConnUnit to which the revision corresponds.


A

A-58


Sensor Table The sensor table lists the sensors (for fan and power supplies) supported by each switch. For each switch, the table will contain a list of all fan and power supply FRU positions, regardless of whether they are installed or not. When a FRU is not installed, the UnitSensorStatus for that table entry will be unknown(1). When a power supply or fan FRU is installed or removed, a sensor trap will be sent (if enabled) which contains an index to the appropriate entry in this table, for the affected FRU. Note that the number of entries in the table does not change when a fan/power supply FRU is installed or removed.

Table A-32 Sensor Table


*fcConnUnitSensorIndex Unsigned32 Not assessable. R A unique value among all fcConnUnitSensorEntrys with the same value of fcConnUnitId, in the range between 1 and fcConnUnitNumSensors[fcConnUnitId].

FcConnUnitSensorName SnmpAdminString The module name of the FRU, such as FAN, PWR or THM

R A textual identification of the sensor intended primarily for operator use.

FcConnUnitSensorStatus INTEGER This value is evaluated from FRU status. The active, backup and update-busy states are mapped to ok(3). And the failed state is mapped to failed(5).

R The status indicated by the sensor. The values are defined as follow: unknown (1) – the unit cannot determine the status, other (2) -- the status does not fit any of the remaining values, ok (3) – indicates good status, warning (4) – indicates the unit needs attention, failed (5) B indicates the unit is non-functional.

FcConnUnitSensorInfo SnmpAdminString The serial number of the FRUs. It’s not supported if the module is failed.

R Miscellaneous static information about the sensor such as its serial number.



FcConnUnitSensorMessage SnmpAdminString The textual description of the FRU status, such as “active” or “failed”.

R This describes the status of the sensor as a message. It may also provide more resolution on the sensor indication, for example ‘Cover temperature 1503K, above nominal operating range’.

FcConnUnitSensorType INTEGER fan (4) or power-supply (5)

R The type of component being monitored by this sensor. The unknown (1) and other (2) values meanings analogous to those for the fcConnUnitSensorStatus object; all other values are essentially self-explanatory.The values are defined as follow: unknown (1), other (2), battery (3), fan (4), powerSupply (5), transmitter (6), enclosure (7), board (8), and receiver (9).

FcConnUnitSensorCharacteristic INTEGER Not supported. Always other (2).

R The characteristics being monitored by this sensor. The unknown (1) and other (2) values meanings analogous to those for the fcConnUnitSensorStatus object; emf (5) refers to electro-magnetic field; all other values are essentially self-explanatory. The values are defined as follow: unknown (1), other (2), temperature (3), pressure (4), emf (5), currentValue (6), airflow (7), frequency (8), and power (9).

Table A-32 Sensor Table (continued)



A

A-60


The Port Table Generic information on ports for a specific fcConnUnit.

Table A-33 Port Table


fcConnUnitPortIndex Unsigned32 The port index. R A unique value among all fcConnUnitPortEntrys on this connectivity unit, between 1 and fcConnUnitNumPorts.

FcConnUnitPortType INTEGER If the port is Not installednotPresent(3)else if the Port State is online use the operating Port Type:F_Port = fPort(8)FL_Port = flPort(7)E_Port = ePort(9)H_Port = hubPort(4)B_Port = ePort(9)else use the configured Port Type:Gx_Port = gPort(10)G_Port = gPort(10)Fx_Port = flPort(7)F_Port = fPort(8)E_Port = ePort(9)

R The port type refers to the protocol active on the port and can take one of the following values: unknown (1) – cannot be determined, other (2) – none of the following, notPresent (3) – no port, hubPort (4) – hub port, nPort (5) – end port for fabric, lPort (6) – end port for loop, flPort (7) – public loop, fPort (8) – fabric port, ePort (9) -- fabric expansion port, gPort (10) -- generic fabric port, domainController (1) – domain controller, hubController (12) – hub controller, scsi (13) – parallel SCSI port, escon (14) – escon port, lan (15) – LAN port, wan (16) – WAN port.



FcConnUnitPortFCClassCap FcPortFCClass If the port is not installed, fcConnUnitPortFCClassCap = 0 else it depends on the configured Port Type:Gx_Port 0x58 = classF(0x40) + class2(0x10) + class3(0x08)G_Port 0x58 = classF(0x40) + class2(0x10) + class3(0x08)Fx_Port 0x18 = class2(0x10) + class3(0x08)F_Port 0x18 = class2(0x10) + class3(0x08)E_Port 0x58 = classF(0x40) + class2(0x10) + class3(0x08)

R Bit mask that specifies the classes of service capability of this port. If this object is not applicable, the agent MUST return all bits set to zero.

Table A-33 Port Table (continued)



A

A-62


FcConnUnitPortFCClassOp FcPortFCClass If the port is Not installedfcConnUnitPortFCClassOp = 0else if the Port State is offlinefcConnUnitPortFCClassOp = 0else it depends on the operating Port Type:F_Port Use Class of Service specified in Fabric LoginFL_Port Use Class of Service specified in one or more Fabric Login's (OR'd together)E_Port 0x58 = classF(0x40) + class2(0x10) + class3(0x08)

R Bit mask that specifies the classes of service that are currently operational at this port. If this object is not applicable, the agent MUST return all bits set to zero.

FcConnUnitPortState INTEGER Refer to Port State Descriptions on page 2-110.

R The current state of the port hardware. The bypassed value (4) means that the port is online but is currently being isolated from the loop or fabric for some reason; the other values are essentially self-explanatory. Any value for this object may co-exist with any value for the fcConnUnitPortStatus object. The values are defined as follow: unknown (1), online (2), offline (3), bypassed (4).





FcConnUnitPortStatus INTEGER Refer to Port State Descriptions on page A-100.

R The current overall protocol status for the port. The warning value (4) means that the port needs attention; the notParticipating value (6) means that protocol is not being processed; the initializing value (7) means that the port is in the process of coming into service; the bypassed value (8) means that the port has been manually or automatically isolated from the loop or fabric; the other values are essentially self-explanatory. Any value for this object may co-exist with any value for the fcConnUnitPortState object. The values are defined as follow: unknown (1), unused (2), ok (3), warning (4), failure (5), notParticipating (6), initializing (7), bypassed (8).

FcConnUnitPortTransmitterType INTEGER This is mapped from the port technology as follow: not present and serial indicate unknown(1), optical sw1g and optical sw2g indicate shortwave(4). Optical lw1g and optical lw2g indicate longwave(5), copper db9 and copper amp indicate copper(6). (Get the value from port technology owned by FPM).

R The technology of the port transceiver. The values are defined as follow: unknown (1), other (2), unused (3), shortwave (4) longwave (5), copper (6), and scsi (7), longwaveNoOFC (8), shortwaveNoOFC (9), longwaveLED (10),




A

A-64


fcConnUnitPortModuleType INTEGER If the port is not installed, return gbicNotInstalled(8). Otherwise return smallFormFactor(9).

R The module type of the port connector. This object refers to the hardware implementation of the port. The embedded value (4) means ‘fixed’ (e.g., oneXnine).The values are defined as follows: unknown (1), other (2), gbic (3), embedded (4), glm(5), gbicSerialId (6), gbicNoSerialId (7), gbicNotInstalled (8), smallFormFactor (9).

FcConnUnitPortWwn FcNameId World Wide Name of the port.

R The World Wide Name of the port. If applicable,otherwise empty string.

FcConnUnitPortFCId OCTET STRING (SIZE(3))

If the port is an F_Port, return fabric address of the node in form of [domain, area, node]. (Supported by Login Server)If the port is an E_Port, return left-adjusted domain ID of the switch.

R This is the assigned Fibre Channel ID of this port. This value is expected to be a Big Endian value of 24 bits. If this is loop, then it is the ALPA that is connected. If this is an eport, then it will only contain the domain ID left justified, zero filled. If this port does not have a Fibre Channel address, return all bits set to 1.

FcConnUnitPortSerialNoSn SnmpAdminString Not applicable. R The serial number identification of the unit (e.g., for a GBIC). If this is not applicable, return a zero-length string.

FcConnUnitPortRevision SnmpAdminString Not applicable. R The port revision (e.g., for a GBIC).

FcConnUnitPortVendor SnmpAdminString Not applicable. R The port vendor (e.g., for a GBIC).

FcConnUnitPortSpeed Gauge32 Return 100000 kilobytes for 1 Gb/s switches and 200000 kilobytes for 2 Gb/s switches.

R The speed of the port in kilobytes per second.





FcConnUnitPortControl INTEGER ResetConnUnitPort(3), offlineConnUnitPort(6), onlineConnUnitPort(7), and portFailure(42501) are the only set-operations are supported. Always return unknown(1) on read.

R/W This object is used to control the addressed fcConnUnit’s port. Valid commands are: Unknown (1) and invalid (2) are only used as values that are read.ResetConnUnitPort (3): If the addressed connectivity unit allows this operation to be performed on this port, the addressed port performs a vendor-specific ‘reset’ operation. Examples of these operations are: the Link Reset protocol, the Loop Initialization protocol, or a resynchronization occurring between the transceiver in the addressed port to the transceiver that the port is connected to.BypassConnUnitPort (4): If the addressed connectivity unit allows this operation to be performed to this port, the addressed port performs a vendor-specific ‘bypass’ operation. Examples of these operations are: transitioning from online to offline, a request (NON-PARTICIPATING) command to the Loop Port state machine, or removal of the port from an arbitrated loop by a hub.UnbypassConnUnitPort (5): If the addressed connectivity unit allows this operation to be performed to this port, the addressed port performs a vendor-specific ‘unbypass’ operation. Examples of these operations are: the Link Failure protocol, a request (PARTICIPATING) command to the Loop Port state machine, or addition of the port to an arbitrated loop by a hub.




A

A-66


FcConnUnitPortControl (continued) OfflineConnUnitPort (6): If the addressed connectivity unit allows this operation to be performed to this port, the addressed port performs a vendor-specific ‘offline’ operation. Examples of these operations are: disabling a port’s transceiver, the Link Failure protocol, request (NON-PARTICIPATING) command to the Loop Port state machine, or removal of the port from an arbitrated loop by a hub.OnlineConnUnitPort (7): If the addressed connectivity unit allows this operation to be performed to this port, the addressed port performs a vendor-specific ‘online’ operation. Examples of these operations are: enabling a port’s transceiver, the Link Failure protocol, request (PARTICIPATING) command to the Loop Port state machine, or addition of the port from an arbitrated loop by a hub.Note: Each implementation may chose not to support SNMP Set operations for any or all of these values. For Sets specifying varbinds for instances of this object and values not supported by a given implementation, the agent will return the SNMP WrongValue PDU error code.

FcConnUnitPortName SnmpAdminString Port Name R/W A string describing the addressed port.





FcConnUnitPortPhysicalNumber Unsigned32 Physical port number from 0 to Maximum port number – 1.

R This is the internal port number this port is known by. In many implementations, this should be the same as fcConnUnitPortIndex. Some implementations may have an internal port representation not compatible with the rules for table indexes. In that case, provide the internal representation of this port in this object. This value may also be used in the fcConnUnitLinkPortNumberX or fcConnUnitLinkPortNumberY objects of the fcConnUnitLinkTable.

FcConnUnitPortProtocolCap (added from Mib3.0)

OCTET STRING (SIZE (2))

If the port is Not installed:fcConnUnitPortProtocolCap = 0else it depends on the configured Port Type:Gx_Port 3 = Loop(1) + Fabric(2)G_Port 2 = Fabric(2)Fx_Port 3 = Loop(1) + Fabric(2)F_Port 2 = Fabric(2)E_Port 2 = Fabric(2)

R Bit mask that specifies the driver level protocol capability of this port. If this is not applicable, return all bits set to zero.The bits have the following definition: unknown – 0, Loop – 1, Fabric – 2,SCSI – 4, TCP/IP - 8, VI – 16, FICON – 32.

FcConnUnitPortProtocolOp(added from Mib3.0)

OCTET STRING (SIZE (2))

If the port is Not installed:fcConnUnitPortProtocolOp = 0else if the Port State is offlinefcConnUnitPortProtocolOp = 0else it depends on the operating Port Type:F_Port 2 = Fabric(2)FL_Port 1 = Loop(1)E_Port 2 = Fabric(2)H_Port 1 = Loop(1)B_Port 2 = Fabric(2)

R Bit mask that specifies the driver level protocol(s) that are currently operational. If this is not applicable, return all bits set to zero. This object has the same definition as fcConnUnitPortProtocolCap.




A

A-68


FcConnUnitPortNodeWwn (added from Mib3.0)

FcNameId switch WWN R The Node World Wide Name of the port if applicable, otherwise all zeros. This should have the same value for a group of related ports. The container is defined as the largest physical entity. For example, all ports on HBAs on a host will have the same Node WWN. All ports on the same storage subsystem will have the same Node WWN.

FcConnUnitPortHWState (added from Mib3.0)

INTEGER Refer to Port State Descriptions on page A-100.

R The hardware detected state of the port. The values are defined as follow: unknown (1), failed (2) – port failed diagnostics, bypassed (3) – FCAL bypass, loop only, active (4) – connected to a device, loopback (5) – Port in ext loopback, txfault (6) – Transmitter fault, noMedia (7) – media not installed, linkDown (8) – waiting for activity (rx sync).





The Event Table The table of connectivity unit events. Errors, warnings, and information should be reported in this table.

Table A-34 Event Table


*fcConnUnitEventIndex Unsigned32 An event index. R Each connectivity unit has its own event buffer. As it wraps, it may write over previous events. This object is an index into the buffer. It is recommended that this table be read using ‘getNext’s to retrieve the initial table. The management application should read the event table at periodic intervals and then determine if any new entries were added by comparing the last known index value with the current highest index value. The management application should then update its copy of the event table. If the read interval is too long, it is possible that there may be events that may not be contained in the agent’s internal event buffer. For example, an agent may read events 50-75. At the next read interval, fcConnUnitEventCurrID is 189. If the management app tries to read event index 76, and the agent’s internal buffer is 100 entries max, event index 76 will no longer be available. The index value is an incrementing integer starting from one every time there is a table reset. On table reset, all contents are emptied and all indices are set to zero. When an event is added to the table, the event is assigned the next higher integer value than the last item entered into the table. If the index value reaches its maximum value, the next item entered will cause the index value to roll over and start at one again.

FcConnUnitREventTime DisplayString (SIZE (15))

The time when the event occurred.

R This is the real time when the event occurred. It has the following format:DDMMYYYY HHMMSS DD = day number, MM = month number, YYYY = year number, HH = hour number, MM= minute number, SS = seconds numberIf not applicable, return a NULL string.


A

A-70


FcConnUnitSEventTime TimeTicks Translated from fcConnUnitREventTime.

R This is the sysuptime timestamp when the event occurred.

FcConnUnitEventSeverity FcEventSeverity The mapping from switch event severity level to FcEventServerity:Switch:informationalminor major critical(4)severe emergency(2)

MIB:info(8)error(5)

R The event severity level:unknown (1)emergency (2)alert (3)critical (4)error (5)warning (6)notify (7)info (8)debug (9)mark (10)

FcConnUnitEventType INTEGER Always status(3). R The type of this event. The values are defined as follow: unknown (1), other (2), status (3), configuration (4), topology (5).

FcConnUnitEventObject OBJECT IDENTIFIER

Only the OID of the fcConnUnit is returned. Other information is not supported.

R This is used with the fcConnUnitEventType to identify which object the event refers to. It can be the OID of a connectivity unit or of another object like fcConnUnitPortStatus[...]

fcConnUnitEventDescr SnmpAdminString “Reason code XX”, XX is the event reason code.

R The description of the event.

Table A-34 Event Table (continued)




Link Table The link table is intended to organize and communicate any information the agent which would assist a management application to discover the Connectivity Units in the framework and the topology of their interconnect. That is, the goal is to assist the management application not only to list the elements of the framework, but to map them.

With this goal, the agent should include as much as it possesses about any links from its own connectivity units to others, including links among its own units.

An agent should include partial information about links if it is not able to fully define them. For an entry to be considered to be valid, both the X (local) and the Y (remote) need to have one valid value.

If the agent is able to discover links which do not directly attach to members of its agency and its discovery algorithm gives some assurance the links are recently valid, it may include these links.

Link information entered by administrative action may be included even if not validated directly if the link has at least one endpoint in this agency, but should not be included otherwise.

A connectivity unit can fill the table in as best it can. One of the methods to fill this in would be to use the RNID ELS (ANSI document 99-422v0). This allows one to query a port for the information needed for the link table.

This table is accessed either directly if the management software has an index value or via GetNexts. The value of the indexes are not required to be contiguous. Each entry created in this table will be assigned an index. This relationship is kept persistent until the entry is removed from the table or the system is reset. The total number of entries are defined by the size of the table.

Note for switch/director firmware: A reset or firmware load will cause this table to be regenerated from the persistent login database; table indices will most likely be associated with different entries after the reset.


A

A-72


Table A-35 Link Table


*fcConnUnitLinkIndex Unsigned32 A link index. R This value is used to create a unique value for each entry in the link table with the same fcConnUnitId. The value can only be reused if it is not currently in use and the value is the next candidate to be used. This value is allowed to wrap at the highest value represented by the number of bits. This value is reset to zero when the system is reset and the first value to be used is 1.

FcConnUnitLinkNodeIdX OCTET STRING (SIZE(16))

The WWN of the local fcConnUnit is returned. This information is available for both E and F ports

R The node WWN of the unit at one end of the link. If the node WWN is unknown and the node is a fcConnUnit in the responding agent then the value of this object MUST BE equal to its fcConnUnitId.

FcConnUnitLinkPortNumberX Integer32 The fcConnUnit’s local port number is returned. This information is available for both E and F ports.

R The port number on the unit specified by fcConnUnitLinkNodeIdX if known, otherwise –1. If the value is non-negative then it will be equal to fcConnUnitPortPhysicalNumber.

FcConnUnitLinkPortWwnX OCTET STRING The local side port WWN on the link. This information is available for both E and F ports.

R The port WWN of the unit specified by fcConnUnitLinkNodeIdX if known, otherwise 16 octets of binary 0.

FcConnUnitLinkNodeIdY OCTET STRING (SIZE(16))

The attached node WWN on the link. This information is available for E ports and F ports. E port nodeIdY can be retrieved from RNID, F port NodeIdY is supported by FLOGI.

R The node WWN of the unit at the other end of the link. If the node WWN is unknown and the node is a fcConnUnit in the responding SNMP agent then the value of this object must be equal to its fcConnUnitId.



FcConnUnitLinkPortNumberY Integer32 The attached port number on the link. This information is available only for E ports from ISR. For F port, -1 is returned.

R The port number on the unit specified by fcConnUnitLinkNodeIdY if known, otherwise –1. If the value is non-negative then it will be equal to fcConnUnitPortPhysicalNumber.

FcConnUnitLinkPortWwnY OCTET STRING The attached port WWN on the link. For E ports, returns the WWN of the connected switch.

R The port WWN on the unit specified by fcConnUnitLinkNodeIdY if known, otherwise 16 octets of binary 0.

FcConnUnitLinkAgentAddressY OCTET STRING (SIZE(16))

R The address of an FCMGMT MIB agent for the node identified by fcConnUnitLinkNodeIdY, if known; otherwise 16 octets of binary 0.

FcConnUnitLinkAgentAddressTypeY Unsigned32 R If fcConnUnitLinkAgentAddressY is non-zero, then it is a protocol address. FcConnUnitLinkAgentAddressTypeY is the ‘address family number’ assigned by IANA to identify the address format. (e.g., 1 is Ipv4, 2 is Ipv6).

FcConnUnitLinkAgentPortY Unsigned32 R The IP port number for the agent. This is provided in case the agent is at a non-standard SNMP port.

FcConnUnitLinkUnitTypeY FcUnitType If it’s E port, return switch (4). Otherwise return RNID type Y.

R Type of the FC connectivity unit as defined in fcConnUnitType.

FcConnUnitLinkConnIdY OCTET STRING (SIZE(3))

For F ports, return Fibre Channel Address. For E ports, return left adjusted domainId of the switch.

R This is the Fibre Channel ID of this port. If the connectivity unit is a switch, this is expected to be a 24-bit Big Endian value. If this is loop, then it is the ALPA that is connected. If this is an e-port, then it will only contain the domain ID. If not any of those, unknown or cascaded loop, return all bits set to 1.

Table A-35 Link Table (continued)



A

A-74


Port Statistics Table There is one statistics table for each individual port. For all objects in statistics table, if the object is not supported by the conn unit then the high order bit is set to 1 with all other bits set to zero. The high order bit is reserved to indicate if the object if supported or not. All objects start at a value of zero at hardware initialization and continue incrementing till end of 63 bits and then wrap to zero.

Table A-36 Port Statistics Table

FA MIB Object Name Type Access

Product Mapping Description

*fcConnUnitPortStatIndex Unsigned32 R

A port number, starting from 1 to maximum number of ports.

A unique value among all entries in this table, between 0 and fcConnUnitNumPort[fcConnUnitPortUnitId]

fcConnUnitPortStatCountError Counter64 R

This MIB object counts:• address ID errors• CRC errors, delimiter errors • frames too short• invalid transmission words• link failures• primitive sequence errors• signal losses• synchronization losses(Supports only low 32 bits of counter; high 32 bits are set to zero.)

A count of the errors that have occurred on this port.

FcConnUnitPortStatCountTxObjects Counter64 R

stTxFrames (64 bit counter) The number of frames/packets/Ios/etc that have been transmitted by this port. Note: A Fibre Channel frame starts with SOF and ends with EOF. FC loop devices should not count frames passed through. This value represents the sum total for all other Tx objects.

FcConnUnitPortStatCountRxObjects Counter64 R

stRxFrames (64 bit counter) The number of frames/packets/Ios/etc that have been received by this port. Note: A Fibre Channel frame starts with SOF and ends with EOF. FC loop devices should not count frames passed through. This value represents the sum total for all other Rx objects.



FcConnUnitPortStatCountTxElements Counter64 R

stTxOctets (64 bit counter) The number of octets or bytes that have been transmitted by this port. One second periodic polling of the port. This value is saved and compared with the next polled value to compute net throughput. Note, for Fibre Channel, ordered sets are not included in the count.

FcConnUnitPortStatCountRxElements Counter64 R

stRxOctets (64 bit counter) The number of octets or bytes that have been received by this port. One second periodic polling of the port. This value is saved and compared with the next polled value to compute net throughput. Note, for Fibre Channel, ordered sets are not included in the count.

FcConnUnitPortStatCountBBCreditZero Counter64 R

Not supported Count of transitions in/out of Bbcredit zero state. The other side is not providing any credit. Note, this is a Fibre Channel stat only.

FcConnUnitPortStatCountInputBuffersFull Counter64 R

Not supported Count of occurrences when all input buffers of a port were full and outbound buffer-to-buffer credit transitioned to zero. There is no credit to provide to other side. Note, this is a Fibre Channel stat only.

FcConnUnitPortStatCountFBSYFrames Counter64 R

Not supported Count of times that FBSY was returned to this port as a result of a frame that could not be delivered to the other end of the link. This occurs if either the Fabric or the destination port is temporarily busy. Port can only occur on SOFc1 frames (the frames that establish a connection). Note, this is a Fibre Channel only stat. This is the sum of all classes. If you cannot keep the by class counters, then keep the sum counters.

FcConnUnitPortStatCountPBSYFrames Counter64 R

Not supported Count of times that PBSY was returned to this port as a result of a frame that could not be delivered to the other end of the link. This occurs if the destination port is temporarily busy. PBSY can only occur on SOFc1 frames (the frames that establish a connection). Note, this is a Fibre Channel only stat. This is the sum of all classes. If you cannot keep the by class counters, then keep the sum counters.

Table A-36 Port Statistics Table (continued)




A

A-76


FcConnUnitPortStatCountFRJTFrames Counter64 R

Not supported Count of times that FRJT was returned to this port as a result of a Frame that was rejected by the fabric. Note, this is the total for all classes and is a Fibre Channel only stat.

FcConnUnitPortStatCountPRJTFrames Counter64 R

Not supported Coudnt of times that FRJT was returned to this port as a result of a Frame that was rejected at the destination N_Port. Note, This is the total for all classes and is a Fibre Channel only stat.

FcConnUnitPortStatCountClass1RxFrames Counter64 R

Not supported Count of Class 1 Frames received at this port. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass1TxFrames Counter64 R

Not supported Count of Class 1 Frames transmitted out this port. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass1FBSYFrames Counter64 R

Not supported Count of times that FBSY was returned to this port as a result of a Class 1 Frame that could not be delivered to the other end of the link. This occurs if either the Fabric or the destination port is temporarily busy. FBSY can only occur on SOFc1 frames (the frames that establish a connection). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass1PBSYFrames Counter64 R

Not supported Count of times that PBSY was returned to this port as a result of a Class 1 Frame that could not be delivered to the other end of the link. This occurs if the destination N_Port is temporarily busy. PBSY can only occur on SOFc1 frames (the frames that establish a connection). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass1FRJTFrames Counter64 R

Not supported Count of times that FRJT was returned to this port as a result of a Class 1 Frame that was rejected by the fabric. Note, this is a Fibre Channel only stat.






FcConnUnitPortStatCountClass1PRJTFrames Counter64 R

Not supported Count of times that FRJT was returned to this port as a result of a Class 1 Frame that was rejected at the destination N_Port. Note, this is a Fibre Channel only stat.


stC2FramesIn (64 bit counter) Count of Class 2 Frames received at this port. Note, this is a Fibre Channel only stat.


stC2FramesOut (64 bit counter) Count of Class 2 Frames transmitted out this port. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass2FBSYFrames Counter64 R

stC2FabricBusy (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of times that FBSY was returned to this port as a result of a Class 2 Frame that could not be delivered to the other end of the link. This occurs if either the Fabric or the destination port is temporarily busy. FBSY can only occur on SOFc1 frames (the frames that establish a connection). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass2PBSYFrames Counter64 R

Not supported Count of times that PBSY was returned to this port as a result of a Class 2 Frame that could not be delivered to the other end of the link. This occurs if the destination N_Port is temporarily busy. PBSY can only occur on SOFc1 frames (the frames that establish a connection). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass2FRJTFrames Counter64 R

stC2FabricReject (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of times that FRJT was returned to this port as a result of a Class 2 Frame that was rejected by the fabric. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass2PRJTFrames Counter64 R

Not supported Count of times that FRJT was returned to this port as a result of a Class 2 Frame that was rejected at the destination N_Port. Note, this is a Fibre Channel only stat.


stC3FramesIn (64 bit counter) Count of Class 3 Frames received at this port. Note, this is a Fibre Channel only stat.





A

A-78



stC3FramesOut (64 bit counter) Count of Class 3 Frames transmitted out this port. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountClass3Discards Counter64 R

stC3Discards (64 bit counter) Count of Class 3 Frames that were discarded upon reception at this port. There is no FBSY or FRJT generated for Class 3 Frames. They are simply discarded if they cannot be delivered. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountRxMulticastObjects Counter64 R

Not supported Count of Multicast Frames or Packets received at this port.

FcConnUnitPortStatCountTxMulticastObjects Counter64 R

Not supported Count of Multicast Frames or Packets transmitted out this port.

FcConnUnitPortStatCountRxBroadcastObjects Counter64 R

Not supported Count of Broadcast Frames or Packets received at this port.

FcConnUnitPortStatCountTxBroadcastObjects Counter64 R

Not supported Count of Broadcast Frames or Packets transmitted out this port. On a Fibre Channel loop, count only OPNr frames generated.

FcConnUnitPortStatCountRxLinkResets Counter64 R

stLinkResetsIn (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of Link resets. This is the number of LRs received. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountTxLinkResets Counter64 R

stLinkResetsOut ( Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of Link resets. This is the number LRs transmitted. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountNumberLinkResets Counter64 R

stLinkResetsIn + stLinkResetsOut (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of Link resets and LIPs detected at this port. The number times the reset link protocol is initiated. These are the count of the logical resets, a count of the number of primitives. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountRxOfflineSequences Counter64 R

stOlssIn (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of Offline Primitive OLS received at this port. Note, this is a Fibre Channel only stat.






FcConnUnitPortStatCountTxOfflineSequences Counter64 R

stOlssOut (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of Offline Primitive OLS transmitted by this port. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountNumberOfflineSequences Counter64 R

stOlssIn plus stOlssOut (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of Offline Primitive sequence received at this port. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountLinkFailures Counter64 R

stLinkFailures (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of link failures. This count is part of the Link Error Status Block (LESB). (FC-PH 29.8). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountInvalidCRC Counter64 R

stInvalidCrcs (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of frames received with invalid CRC. This count is part of the Link Error Status Block (LESB). (FC-PH 29.8). Loop ports should not count CRC errors passing through when monitoring. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountInvalidTxWords Counter64 R

stInvalidTxWords (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of invalid transmission words received at this port. This count is part of the Link Error Status Block (LESB). (FC-PH 29.8). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountPrimitiveSequenceProtocolErrors Counter64 R

stPrimSeqProtoErrors (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of primitive sequence protocol errors detected at this port. This count is part of the Link Error Status Block (LESB). (FC-PH 29.8). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountLossofSignal Counter64 R

stSigLosses (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of instances of signal loss detected at port. This count is part of the Link Error Status Block (LESB). (FC-PH 29.8). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountLossofSynchronization Counter64 R

stSyncLosses (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of instances of synchronization loss detected at port. This count is part of the Link Error Status Block (LESB). (FC-PH 29.8). Note, this is a Fibre Channel only stat.





A

A-80


FcConnUnitPortStatCountInvalidOrderedSets Counter64 R

Not supported. Count of invalid ordered sets received at port. This count is part of the Link Error Status Block (LESB). (FC-PH 29.8). Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountFramesTooLong Counter64 R

Not supported. Count of frames received at this port where the frame length was greater than what was agreed to in FLOGI/PLOGI. This could be caused by losing the end of frame delimiter. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountFramesTruncated Counter64 R

stFramesTooShort (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of frames received at this port where the frame length was less than the minimum indicated by the frame header – normally 24 bytes, but it could be more if the DFCTL field indicates an optional header should have been present. Note, this is a Fibre Channel only stat.

fcConnUnitPortStatCountAddressErrors Counter64 R

stAddrIDErrors (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of frames received with unknown addressing; for example, unknown SID or DID. The SID or DID is not known to the routing algorithm. Note. This is a Fibre Channel only stat.

FcConnUnitPortStatCountDelimiterErrors Counter64 R

stDelimiterErrors (Supports only low 32 bits of counter; high 32 bits are set to zero).

Count of invalid frame delimiters received at this port. An example is a frame with a class 2 start and a class 3 at the end. Note, this is a Fibre Channel only stat.

FcConnUnitPortStatCountEncodingDisparityErrors Counter64 R

Not supported. Count of disparity errors received at this port. Note, this is a Fibre Channel only stat.






Name Server Table This table is accessed either directly (if the management software has an index value) or via GetNexts. The value of the indexes need not be contiguous. Each entry created in this table will be assigned an index. This relationship is kept presistent until the entry is removed from the table or the system is reset. The total number of entries is defined by the size of the table.

Table A-37 Name Server Table


fcConnUnitSnsPortIndex Unsigned32 (Same as Gauge)

A port number, starting from 1 to maximum number of ports.

R The physical port number of this SNS table entry. Each physical port has an SNS table with 1-n entries indexed by fcConnUnitSnsPortIdentifier (port address).

fcConnUnitSnsPortIdentifier FcAddressId 3 bytes FcAddress in the least significant bytes.

R The Port Identifier for this entry in the SNS table.

fcConnUnitSnsPortName FcNaneId Port WWN Name R The Port WWN Name for this entry in the SNS table.

fcConnUnitSnsNodeName FcNameId Node Name R The Node Name for this entry in the SNS table.

fcConnUnitSnsClassOfSvc OCTET STRING (SIZE) (1))

Class of Service that matches the FC class service convention used in name server.

R The classes of service offered by this entry in the SNS table.

fcConnUnitSnsNodeIPAddress OCTET STRING (SIZE) (16))

Node IP address R The Ipv6 formatted address of the Node for this entry in the SNS table. In order for this data to be present, IP address must have been registered with the switch.

fcConnUnitSnsProcAssoc OCTET STRING (SIZE) (8))

Process Associator. R The Process Associator for this entry in the SNS table. Refer to FC-PH sec. 19.4.

fcConnUnitSnsFC4Typ OCTET STRING (SIZE) (32))

FC4 type R The FC-4 Types supported by this entry in the SNS table. Bitmap of FC-4 types supported. Refer to FC-GS2 table 27.


A

A-82


fcConnUnitSnsPortType OCTET STRING (SIZE) (1))

Port type R The Port Type of this entry in the SNS table.Refer to FC-GS2 table 5.

fcConnUnitSnsPortIPAddress OCTET STRING (SIZE) (16))

Port IP Address R The Ipv6 formatted address of this entry in the SNS table. In order for this data to be present, IP address must have been registered with the switch. Refer to FC-GS2 sec 12.4.5.

fcConnUnitSnsFabricPortName FcNameId Fabric Port Name R The Fabric Port name of this entry in the SNS table.

fcConnUnitSnsHardAddress FcGlobalId Bytes address from name server in the least significant bytes.

R The Hard AL_PA of this entry in the SNS table.This address is device selected, not dynamically assigned.

fcConnUnitSnsSymbolicPortName DisplayString (SIZE (0..79)

Symbolic port name R The Symbolic Port Name of this entry in the SNS table.

fcConnUnitSnsSymbolicNodeName DisplayString (SIZE (0..79))

Symbolic node name R The Symbolic Node Name of this entry in the SNS table.

Table A-37 Name Server Table (continued)




Trap Registration Group

The TrapRegTable A table containing a row for each IP address/port number to which traps will be sent.

Table A-38 Trap Registration Group


fcTrapMaxClients Unsigned32 The maximum number of SNMP trap recipients can be supported in the system.

R The maximum number of SNMP trap recipients supported by the connectivity unit.

FcTrapClientCount Unsigned32 The current number of trap recipients

R The current number of rows in the trap table.

Table A-39 Trap Registration Table


*fcTrapRegIpAddress IpAddress Trap recipient’s IP address. R/C The IP address of a client registered for traps.

*fcTrapRegPort Unsigned32 UDP port. R/C The UDP port to send traps to for this host. Normally this would be the standard trap port (UDP/162).


A

A-84


FcTrapRegFilter FcEventSeverity The severity filter. R/C This value defines the trap severity filter for this trap host. The fcConnUnit will send to the designated target entity traps that have a severity level less than or equal to this value.

FcTrapRegRowState RowStatus Row status R/C Specifies the operational status of the row.A RowStatus object may take any of six defined values:active (1): traps may be sent as specified in this row; a management application may change the value of any objects in the row when the status is active.notInService (2): traps will not be sent using this row.notReady (3): the conceptual row exists in the agent, but is missing information necessary to send traps (i.e., if any of the other objects in the row are not present or contain invalid values); this value may not be supplied by a management application.createAndGo (4): supplied by a management application wishing to create a new instance of a conceptual row, supplying valid values for the all the other objects in the row, and have its status automatically set to active, making it available for use in sending traps.createAndWait (5): supplied by a management application wishing to create a new instance of a conceptual row but not make it available for use in sending traps at that time;destroy (6): supplied by a management application wishing to delete an existing conceptual row.

Table A-39 Trap Registration Table (continued)




Trap Types

Table A-40 Trap Types

FA MIB Object NameProduct Mapping

Type Number

OID and Value Description

fcConnUnitStatusChange Generated when the switch’s online status or operational status changes.

1

“.1.3.6.1.2.1.8888.1.1.3.1.6” + unitId fcConnUnitStatus, “.1.3.6.1.2.1.8888.1.1.3.1.5” + unitId fcConnUnitState

The overall status of the connectivity unit has changed. Recommended severity level (for filtering): alert.

fcConnUnitDeletedTrap Not supported on the connUnit. 2

N/A An fcConnUnit has been deleted from this agent. Recommended severity level (for filtering): warning.

fcConnUnitEventTrap Generated when a new event is generated. 3

“.1.3.6.1.2.1.8888.1.1.7.1.1” + unitId fcConnUnitEventIndex, “.1.3.6.1.2.1.8888.1.1.7.1.5” + unitId fcConnUnitEventType,“.1.3.6.1.2.1.8888.1.1.7.1.6” + unitId fcConnUnitEventObject,“.1.3.6.1.2.1.8888.1.1.7.1.7” + unitId fcConnUnitEventDescr

An event has been generated by the connectivity unit.Recommended severity level (for filtering): info.

fcConnUnitSensorStatusChange Generated when one of fans/power supply status is changed.

4

“.1.3.6.1.2.1.8888.1.1.5.1.3” + unitId + sensor_nbr fcConnUnitSensorState

The overall status of the connectivity unit has changed.Recommended severity level (for filtering): alert.

fcConnUnitPortStatusChange Generated when a port state/status is changed. 5

“.1.3.6.1.2.1.8888.1.1.6.1.6” + unitId + port_nbr fcConnUnitPortStatus, “.1.3.6.1.2.1.8888.1.1.6.1.5” + unitId + port_nbr fcConnUnitPortState

The overall status of the connectivity unit has changed. Recommended severity level (for filtering): alert.


A

A-86


Connectrix Private Enterprise MIB (fceos.mib)

Figure A-4 Private Enterprise MIB Support

private (4)

enterprise (1)

McDATA (289)

commDev (2)

fibrechannel

(1)

fcSwitch (1)

fcEos (2)

fcEosFru (2) fcEosPort (3)fcEos

PortBinding (4)fcEosSys (1)

fcEosZoning

(5)fcEosTA (6)



The fcEos Private Enterprise MIB defines and supports six groups:

◆ System group (fcEosSys)

◆ Field replaceable unit (FRU) group (fcEosFru)

◆ Fibre Channel port group (fcEosPort)

◆ Port binding group (fcEosPortBinding)

◆ Zoning group (fcEosZoning)

◆ Threshold alert group (fcEosTA)

The tables that appear in the following sections define variables available in the private enterprise MIB. All variables are read-only unless noted otherwise.

Table A-41 Private Enterprise MIB Table


FcEosSysOperStatus INTEGER The values are defined as follow: operational(1), redundant-failure(2), minor-failure(3), major-failure(4), not-operational(5).

FcEosFruCode INTEGER The values are defined as follow: fru-bkplane(1) – Backplane, fru-ctp(2) – Control Processor card, fru-sbar(3) – Serial Crossbar, fru-fan2(4) – Center fan module, fru-fan(5) – Fan module, fru-power(6) – Power supply module, fru-reserved(7) – Reserved, not used, fru-glsl(8) – Longwave, Single-Mode, LC connector, 1 Gig, fru-gsml(9) – Shortwave, Multi-Mode, LC connector, 1 Gig, fru-gxxl(10) – Mixed, LC connector, 1 Gig, fru-gsf1(11) – SFO pluggable, 1 Gig, fru-gsf2(12) – SFO pluggable, 2 Gig, fru-glsr(13) – Longwave, Single-Mode, MT-RJ connector, 1 Gig, fru-gsmr(14) – Shortwave, Multi-Mode, MT-RJ connector, 1 Gig, fru-gxxr (15) -- Mixed, MT-RJ connector, 1 Gig, fru-fint1(16) – F-Port, internal, 1 Gig.

FcEosFruPosition INTEGER (1..255)

FcEosPortIndex INTEGER (1..2048)

FcEosPortPhyState INTEGER The values are defined as follow: psNotInstalled(1), psAvailable(2), psBlocked(3), psUnavailable(4), psLinkFailure(5), psLinkFailLOL(6), psIntDiags(7), psExtLoop(8), psPortFail(9), psSR(10), psLR(11), psInaccessible (12), psInactive(13).

Connectrix Private Enterprise MIB (fceos.mib) A-87

A

A-88


System Group

FcEosPortWWN OCTET STRING (SIZE(8))

FcEosPortList OCTET STRING (SIZE (32))

LoopPortALPA OCTET STRING (SIZE(16)) This is how the ALPAs are represented as a bitmap for products which support loop devices:bit 0 = FL_ALPA(00)bits 1-30 = ALPA 01-3Abits 31-62 = ALPA 3C-72bits 63-94 = ALPA 73-B2bits 95-126 = ALPA B3-EFFor products which do not support loop devices, the bitmap is all zeros.

Table A-41 Private Enterprise MIB Table (continued)


Table A-42 System Group Variables

FCEOS MIB Object Name Type Provided By Access Description

fcEosSysCurrentDate DisplayString (SIZE (1..64))

McK R The current date information.

fcEosSysBootDate DisplayString (SIZE (1..64))

McK R The date and time of the last IPL of the switch.

fcEosSysFirmwareVersion DisplayString(SIZE (1..24))

AS R The current version of the firmware.

fcEosSysTypeNum DisplayString(SIZE (1..64))

McK DEV-TBL R The ASCII type number of the switch.

fcEosSysModelNum DisplayString(SIZE (1..64))

McK DEV-TBL R The ASCII model number of the switch.

fcEosSysMfg DisplayString(SIZE (1..64))

McK DEV-TBL R The ASCII manufacturer of the switch.

fcEosSysPlantOfMfg DisplayString(SIZE (1..64))

McK DEV-TBL R The ASCII plant of manufacturer of the switch.

fcEosSysEcLevel DisplayString(SIZE (1..64))

McK DEV-TBL R The ASCII EC level ID of the switch.



fcEosSysSerialNum DisplayString(SIZE (1..64))

McK DEV-TBL R The ASCII system serial number of the switch. Returns the switch OEM serial number.

fcEosSysOperStatus FcEosSysOperStatus PCP R The current operational status of the switch.

fcEosSysState INTEGER PCP R If the operational status of the switch is operational, the switch will be in one of the four states: online(1), coming-online(2), offline(3), and going-offline(4).

fcEosSysAdmStatus INTEGER PCP R/W The desired administrative status of the switch. A management station may place the switch in a desired state by setting this object accordingly. The desired administrative status are online(1) and offline(2). The online means setting the switch to be accessible by an external Fibre Channel port, and offline means setting the switch to be inaccessible.

fcEosSysConfigSpeed INTEGER PCP R Switch speed capability. It’s a user-initiated option to adjust the system-wide port speed capability. The values are defined as follow: one-gig (1), two-gig (2).

Table A-42 System Group Variables (continued)



A

A-90


FRU Table (Module Group)

Table A-43 FRU Table

FCEOS MIB Object Name Type


fcEosFruCode fcEosFruCode SNMP R Field Replaceable Unit. A hardware component of the product that is replaceable as an entire unit. Each module defined in this MIB has a fixed FRU code.

fcEosFruPosition fcEosFruPosition SNMP R This object identifies the position of the module. The value starts from 1 to the maximum number of the cards that can be contained within this switch.

fcEosFruStatus INTEGER SNMP R This object identifies the operational status of the module. The unknown(0) state indicates that no information is available for the FRU, which may happen when no FRU is installed; The active(1) state indicates that the current module is active; The backup(2) state indicates that the back up module is used; The update-busy (3) state indicates that the module is in the updating process; The failed(4) state indicates that the current module is failed.

fcEosFruPartNumber DisplayString(SIZE (0..64))

McK DEV-TBL

R The part number of the module. For the fan FRU, the returned value is NULL.

fcEosFruSerialNumber DisplayString(SIZE (0..64))

McK DEV-TBL

R The serial number of the module. For the fan FRU, the returned value is NULL.

fcEosFruPowerOnHours Counter McK DEV-TBL

R The number of the hours that the FRU has been in operation. For the fan FRU, the returned value is NULL.

fcEosFruTestDate DisplayString(SIZE (0..64))

McK DEV-TBL

R The final test date of the module. For the fan FRU, the returned value is NULL.



Port Table (Port Group)

Table A-44 Port Table



fcEosPortIndex fcEosPortIndex SNMP R The fixed physical port number on the switch. It ranges from 1 to the number of physical ports that can be supported in the switch.

fcEosPortPhyState fcEosPortPhyState

FPM R The physical state of the port.

fcEosPortOpStatus INTEGER FPM, SNMP

R The operational status of the port. The values are defined as follow: online(1), offline(2), testing(3), and faulty(4). The online(1) state indicates that user frames can be passed. Refer to Port State Descriptions on page 2-121. If the port is not installed, returns offline(2).

fcEosPortAdmStatus INTEGER PCP, FPM

R/W The desired state of the port. A management station may place the port in a desired state by setting this object accordingly. The testing(3) state indicates that no user frames can be passed. As the result of either explicit management action or per configuration information accessible by the switch, fcEosPortAdmStatus is then changed to either the online(1) or testing(3) states, or remains in the offline(2) state. If the port is not installed, returns offline(2).

fcEosPortConnector INTEGER PSCC R Supported connector types of the port. The values are defined as follow: unknown(1), lc(2), mt-rj(3), mu(4), and internal-port(5).

fcEosPortDistance INTEGER (0..127)

PSCC R A bit map to represent distance types of the Port. Bit 0 unknown, bit 1-3 reserved, bit 4 long distance (l), bit 5 intermediate distance (i), bit 6 short distance (s), bit 7 very long distance.

fcEosPortXceiverType INTEGER PSCC R Supported transceiver types of the port. The values are defined as follow: unknown (1), longDistance(2) – (LL-V), longWaveLaser-LL(3) – (LL), shortWaveLaser-OFC(4) – (SL), shortWaveLaser-noOFC(5) – (SN), longWaveLaser-LC(6) – (LC).

fcEosPortMedia INTEGER (0..127)

PSCC R A bit map to represent transmission media of the port. Bit 0 single mode(sm), bit 1 reserved, bit 2 multi-mode 50m (m5), bit 3 multi-mode 62.5 (m6), bit 4-6 reserved, bit 7 copper.


A

A-92


fcEosPortSpeedCap INTEGER (0..127)

PSCC R A bit map to represent the speed of optical transceiver:Bit 0 — 100 MB/sBit 1 — reservedBit 2 — 200 MB/sBit 3 — reservedBit 4 — 400 MB/s Bits 5-7 — reserved

fcEosPortConfigSpeed INTEGER PCP R The configured port speed. The values are defined as follow: one-gig (1), two-gig (2), negotiate (3).

fcEosPortOpSpeed PCP R The current operating speed of the port. The values are defined as follow: unknown (1), one-gig (2), two-gig (3), negotiate (4).

fcEosPortConfigType INTEGER R/W The configured port type:gPort (1)fPort (2)ePort (3)flPort (4)fxPort (5)gxPort (6)

fcEosPortOpType INTEGER R The operating port type:unknown (1)ePort (2)fPort (3)flPort (4)

fcEosPortALPAIndex LoopPortALPA R The ALPA-Index bit map that identifies the list ofALPA's associated with the FL_port. Only applicable for flPorts.

fcEosPortFAN TruthValue R/W This object identifies/configures if the port supports Fabric Address Notification mode. Only applicable for flPorts.

fcEosPortTxWords32 Counter PSCC R A 32 bit counter for the number of words within frames that the port has transmitted. (Primitive signals and primitive sequence are not included.)

fcEosPortRxWords32 Counter PSCC R A 32 bit counter for the number of words within frames that the port has received. (Primitive signals and primitive sequence are not included.)






fcEosPortTxFrames32 Counter PSCC R A 32 bit counter for the number of (Fibre Channel) frames that the port has transmitted.

fcEosPortRxFrames32 Counter PSCC R A 32 bit counter for the number of (Fibre Channel) frames that the port has received.

fcEosPortTxThroughput Counter PSCC R The Bps (bytes per second) transmission rate of the port.

fcEosPortRxThroughput Counter PSCC R The Bps (bytes per second) reception rate of the port.

fcEosPortTxC2Words32 Counter PSCC R A 32 bit counter for the number of class 2 4-byte words that the port has transmitted. (Primitive signals and primitive sequence are not included.)

fcEosPortRxC2Words32 Counter PSCC R A 32 bit counter for the number of class 2 4-byte words that the port has received. (Primitive signals and primitive sequence are not included.)

fcEosPortTxC2Frames32 Counter PSCC R A 32 bit counter for the number of Class 2 frames that the port has transmitted.

fcEosPortRxC2Frames32 Counter PSCC R A 32 bit counter for the number of Class 2 frames that the port has received.

fcEosPortTxC2Octets32 Counter PSCC R A 32 bit counter for the number of Class 2 Octets that the port has transmitted.

fcEosPortRxC2Octets32 Counter PSCC R A 32 bit counter for the number of Class 2 Octets that the port has received.

fcEosPortTxC3Words32 Counter PSCC R A 32 bit counter for the number of class 3 4-byte words that the port has transmitted. (Primitive signals and primitive sequence are not included.)

fcEosPortRxC3Words32 Counter PSCC R A 32 bit counter for the number of class 3 4-byte words that the port has received. (Primitive signals and primitive sequence are not included.)

fcEosPortTxC3Frames32 Counter PSCC R A 32 bit counter for the number of Class 3 frames that the port has transmitted.

fcEosPortRxC3Frames32 Counter PSCC R A 32 bit counter for the number of Class 3 frames that the port has received.

fcEosPortTxC3Octets32 Counter PSCC R A 32 bit counter for the number of Class 3 Octets that the port has transmitted.





A

A-94


fcEosPortRxC3Octets32 Counter PSCC R A 32 bit counter for the number of Class 3 Octets that the port has received.

fcEosPortC3Discards32 Counter PSCC R A 32 bit counter for the number of Class 3 frames that the port has discarded

fcEosPortDiscardFrames Counter PSCC R The number of frames that the port has discarded.

fcEosPortTxLinkResets Counter PSCC R The number of link resets initiated by this switch port.

fcEosPortRxLinkResets Counter PSCC R The number of link resets initiated by the attached N_port.

fcEosPortTxOLSs Counter PSCC R The number of offline sequences initiated by this switch port.

fcEosPortRxOLSs Counter PSCC R The number of offline sequences initiated by the attached N_port.

fcEosPortSyncLosses Counter PSCC R The number of loss of synchronization timeout.

fcEosPortSigLosses Counter PSCC R The number of times that a Loss of Signal is detected.

fcEosPortProtocolErrors Counter PSCC R The number of protocol errors detected.

fcEosPortInvalidTxWords Counter PSCC R The number of Invalid Transmission words that the port has received.

fcEosPortLinkFailures Counter PSCC R The number of transitions to an LFx state.

fcEosPortCrcs Counter PSCC R The number of CRC errors detected from frames received.

fcEosPortTruncs Counter PSCC R The number of frames shorter than the Fibre Channel minimum.

fcEosPortTxWords64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of words within frames that the port has transmitted. (Primitive signals and primitive sequence are not included.)

fcEosPortRxWords64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of words within frames that the port has received. (Primitive signals and primitive sequence are not included.)

fcEosPortTxFrames64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of (Fibre Channel) frames that the port has transmitted.

fcEosPortRxFrames64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of (Fibre Channel) frames that the port has received.






fcEosPortTxC2Words64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of class 2 4-byte words that the port has transmitted. (Primitive signals and primitive sequence are not included.)

fcEosPortRxC2Words64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of class 2 4-byte words that the port has received. (Primitive signals and primitive sequence are not included.)

fcEosPortTxC2Frames64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 2 frames that the port has transmitted.

fcEosPortRxC2Frames64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 2 frames that the port has received.

fcEosPortTxC2Octets64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 2 Octets that the port has transmitted.

fcEosPortRxC2Octets64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 2 Octets that the port has received.

fcEosPortTxC3Words64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of class 3 4-byte words that the port has transmitted. (Primitive signals and primitive sequence are not included.)

fcEosPortRxC3Words64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of class 3 4-byte words that the port has received. (Primitive signals and primitive sequence are not included.)

fcEosPortTxC3Frames64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 3 frames that the port has transmitted.

fcEosPortRxC3Frames64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 3 frames that the port has received.

fcEosPortTxC3Octets64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 3 Octets that the port has transmitted.

fcEosPortRxC3Octets64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 3 Octets that the port has received.

fcEosPortC3Discards64 OCTET STRING (SIZE (8))

PSCC R A 64 bit counter for the number of Class 3 frames that the port has discarded

fcEosPortTxFlows Counter PSCC R A 32 bit counter for the number of flows rerouted from this port.

fcEosPortRxFlows Counter PSCC R A 32 bit counter for the number of flows rerouted to this port.





A

A-96


Port Binding Table

Zoning Variables

Table A-45 Port Binding Table

FCEOS MIB Object Name TypeProvided By Access Description

fcEosPortBindingIndex fcEosPortIndex SNMP R The fixed physical port number on the switch. It ranges from 1 to the number of physical ports that can be supported in the switch.

fcEosPortBindingFlag INTEGER PCP R/W The flag indicates whether or not Port Binding is in effect for an individual port. The values are defined as follow: yes (1), no (2).

fcEosPortConfiguredWWN fcEosPortWWN PCP R/W The authorized port WWN for attached servers and storage systems (F_Ports), or the authorized switch WWN for attached switches (E_Ports).

fcEosPortAttachedWWN fcEosPortWWN PCP R The WWN of the device currently attached to the port whether it has successfully connected or is currently being rejected due to a Port Binding violation.

Table A-46 Zoning Variables

FCEOS MIB Object Name TypeProvided By Access Description

fcEosActiveZoneSetNam DisplayString PCP R The active zone set name.

fcEosActiveZoneCount INTEGER PCP R The count of zones included in the active zone set.

fcEosDefaultZoneSetState ZoneSetState PCP R The state of the default zone set

fcEosActiveZoneSetState ZoneSetState PCP R The state of the active zone set

fcEosHardwareEnforcedZoning INTEGER PCP R Indicates if zoning is hardware enforced (1=Hardzoning, 0=Nameserver zoning only).



Active Zone Table

Active Member Table

Table A-47 Active Zone Table


fcEosZoneIndex INTEGER PCP R Zone index number. This number will range from 1 to the number of zones specified by the ActiveZoneCount.

fcEosZoneName DisplayString PCP R The zone name.

fcEosZoneMemberCount INTEGER PCP R The number of members included in the zone.

Table A-48 Active Zone Member Table


fcEosZoneIndex DisplayString PCP R The index of the zone that this member belongs to.

fcEosMemberIndex INTEGER PCP R Member index number. This number will range from 1 to the number of members specified by the corresponding ZoneMemberCount..

fcEosMemberType ZoneSetState PCP R Indicates the addressing method for this member (1=WWN, 2=Port number).

fcEosMemberWWN ZoneSetState PCP R The WWN name as an 8-character string. This value is only valid if the member type is 1, otherwise it will default to 0.

fcEosMemberDomainID INTEGER PCP R The domain ID. This value is only valid if the member type is 2, otherwise it will default to NULL.

fcEosMemberPortNumber INTEGER PCP R The port number. This value is only valid if the member type is 2, otherwise it will default to NULL.


A

A-98


Threshold Alert Table

Table A-49 Threshold Alert Table

FCEOS MIB Object Name Type Provided by Access Description

fcEosTAIndex INTEGER PCP R This object is used to identify which threshold has been triggered.

fcEosTAName DisplayString(SIZE (1..64))

PCP R The threshold alert name.

fcEosTAState INTEGER PCP R The current state of the threshold. (enabled = 1, disabled = 2)

fcEosTAType INTEGER PCP R The type of the threshold. (throughput = 1, counter = 2)

fcEosTAPortType INTEGER PCP R A threshold can be set on a list of physical port numbers or on all the ports of the specified type (ePorts, fPorts). (list = 1, ePorts = 2, fPorts = 3, flPorts = 4)

fcEosTAPortList fcEosPortList PCP R A bit map that identifies which ports this threshold alert applies to (only valid if the Threshold Alert Port Type = list). The left most bit represents the port 0.

fcEosTAInterval INTEGER PCP R The number of minutes in a threshold alert interval.

fcEosTATriggerValue INTEGER PCP R If the alert type is a Throughput Threshold Alert, then this is the percent utilization (1-100) required to trigger an alert. If the alert type is a Counter Threshold Alert, then this is the counter delta required to trigger an alert.

fcEosTTADirection INTEGER PCP R This only applies when the alert type is a Throughput Threshold Alert. It specifies the throughput direction of the threshold. (Transmit = 1, receive = 2, either = 3)

fcEosTTATriggerDuration INTEGER PCP R This only applies when the alert type is a Throughput Threshold Alert. It specifies the amount of time during a threshold alert interval that the trigger must be exceeded before an alert is generated.

fcEosCTACounter INTEGER PCP R This only applies when the alert type is a Counter Threshold Alert. It specifies statistical counter or counter set to be monitored. (This object is not supported in the current release.)



Enterprise Specific Traps

Table A-50 Enterprise-Specific Traps

FCEOS MIB Object NameType Number Product Mapping OID and Value Description

fcEosPortScn 1 Generated when Fibre Channel port operational state changes.

fcEosPortOpStatus An fcEosPortScn(1) is generated whenever a Fc_Port changes its operational state. For instance, the Fc_Port goes from on-line to offline.

fcEosFruScn 2 Generated when FRU operational state changes.

fcEosFruStatus An fcEosFruScn(2) is generated whenever a FRU status changes its operational state.

fcEosPortBindingViolation 3 Generated when Port binding violation occurs.

fcEosPortAttachedWWN An fcEosPortBindingViolation(3) is generated whenever the switch detects that a port binding violation occurs.

fcEosThresholdAlert 4 Generated when Threshold alert occurs.

fcEosPortIndex, fcEosTAIndex An fcEosThresholdAlert(4) is generated whenever a threshold alert occurs.


A

A-100


Port State Descriptions

FCEOS, Fibre Alliance M3.1.

Table A-51 Port State Descriptions

Port Status Used Internally by Connectrix Manager

Port State in Connectrix Manager

Connectrix Manager Alert Symbol a

Green Port LEDS

Amber Port LEDs

FibreAlliance MIB b: connUnitPortState

FibreAlliance MIB b: connUnitPortStatus

FibreAlliance MIB b: connUnitPortHWState

FE MIB c: fcFxPortPhysOperStatus Description

STAT_SERVICE_REQUIRED Not Installed

unknown(1) unknown(1) unknown(1)

No table entry Port card not installed.

STAT_LINK_FAIL_LOL No Light

offline(3) unused(2) noMedia(7)

offline(2) No signal (light) is being received on the Director port. This is a normal condition when there is no cable plugged into the port, or when the device attached to the other end of the cable is powered down.

STAT_AVAILABLE Online On

online(2) ok(3) active(4)

online(1) The attached device has successfully connected to the Director and is ready to communicate, or is in the process of communicating, with other attached devices. As long as the port remains in the online state, the green port LED remains illuminated or blinks when there is traffic.

STAT_BLOCKED Offline

offline(3) ok(3) active(4)

offline(2) The Director port has been configured as “Blocked” and is transmitting the Fibre Channel Offline Sequence (OLS) to the attached device.



STAT_UNAVAILABLE Offline Yellow Triangle

online(2) ok(3) active(4)

online(1) The Director port has been configured as “Unblocked” and is receiving the Fibre Channel Offline Sequence (OLS) indicating that the attached device is offline.

STAT_INTERNAL_DIAGSSTAT_EXTERNAL_LOOP

Testing Yellow Triangle Blinking

online(2) ok(3) loopback(5)

testing(3) The port is currently executing a diagnostic test. The amber port LED blinks once every two seconds for the duration of the test.

STAT_LINK_RESET Link Reset Yellow Triangle

online(2) initializing(7) active(4)

online(1) The switch and the attached device are performing a link reset operation to recover the link connection. Ordinarily, this is a transient state that should not persist.

STAT_LINK_FAILURE Not Operational Yellow Triangle

online(2) initializing(7) active(4)

online(1) The switch port is receiving the Fibre Channel Not Operational Sequence (NOS) indicating that the attached device is not operational.

PortStatus.isInvalidAttachment() Invalid Attachment Yellow Triangle On

online(2) warning(4) active(4)

online(1) The switch port is in an invalid attachment state due to an improper connection. A reason code will accompany this state.

Table A-51 Port State Descriptions (continued)




Green Port LEDS

Amber Port LEDs






A

A-102


a. The alert symbol is displayed on the corresponding port card in the Hardware View, and next to the specific port in the Port Card Detailed View, and in the Alert column of the Port List View. It indicates that a corrective action is required to return the port back to a normal operating state.

b. connUnitPortState(1)unknown, (2)online, (3)offline, (4)bypassedconnUnitPortStatus(1)unknown, (2)unused, (3)ok, (4)warning, (5)failure, (6)notparticipating, (7)initializing, (8)bypassedconnUnitPortHWState(1)unknown, (2)failed, (3)bypassed, (4)active, (5)loopback, (6)txfault, (7)noMedia, (8)linkDown

c. fcFxPortPhysOperStatus(1)online, (2)offline, (3)testing, (4)link-failure

STAT_SERVICE_REQUIREDSTAT_PORT_FAIL

Port Failure Red Diamond On

online(2) failure(5) failed(2)

link-failure(4) The switch port has failed and requires service. The amber LED for the port remains illuminated.

STAT_INACCESSIBLE N/A N/A

No table entry No table entry No table entry

No table entry An inaccessible port state pertains to ports that cannot be installed or removed as discrete entities, and do not indicate any port state other than inaccessible. An example of this is ports 128-131 on an ED-140M, which are reserved for the embedded ports for the primary and backup CTPs.

STAT_INACTIVE Inactive Yellow Triangle

offline(3) warning(4) active(4)

offline(2) The ‘Inactive Port State’ signifies a port is not able to come online due to a configuration conflict (either software or hardware) on the switch. The intention of the ‘Inactive’ port state is to provide user notification when a configuration conflict is preventing a port from coming on line. One of the reasons for this state is an unlicensed port.

Table A-51 Port State Descriptions (continued)




Green Port LEDS

Amber Port LEDs






BIvisible Body Tag

This appendix describes the procedure for configuring unique addresses for each switch.

• Configuring Network Addresses ................................................... B-2

Configuring NetworkAddresses

Configuring Network Addresses B-1

B

B-2

Configuring Network Addresses

Configuring Network AddressesThe DS-24M2 is delivered with the following default network addresses:

◆ MAC address — The media access control (MAC) address is programmed into flash memory on the control processor (CTP) at the time of manufacture. The MAC address is unique for each switch, and should not be changed.

◆ IP address — The IP address is 10.xxx.yyy.zzz, where:

• xxx is the machine address and programmed into flash memory on the CTP card at the time of manufacture.

• yyy is the 5th byte of the MAC address.

• zzz is the 6th byte of the MAC address.

If multiple switches are installed on the same LAN, each switch (and the Connectrix Service Processor) must have a unique IP address. One switch can use the default address, but the addresses of the remaining switches must be changed.

If multiple switches, other managed products, and the Connectrix Service Processor are delivered in an EMC EC1200 cabinet, all devices are configured with unique IP addresses that do not require change. The addresses require change only if multiple equipment cabinets are LAN-connected.

◆ Subnet mask — The default subnet mask is 255.0.0.0. If the switch is installed on a complex public LAN with one or more routers, the address may require change.

◆ Gateway address — The default gateway address is 0.0.0.0. If the switch is installed on a dedicated LAN with no connection through a router, the address does not require change. If the switch is installed on a public LAN (corporate intranet), the gateway address must be changed to the address of the corporate intranet’s local router.

Verify the type of LAN installation with the customer’s network administrator. If one switch (or one EC-1200 cabinet) is installed on a dedicated LAN, network addresses do not have to be changed.

If multiple switches (or multiple EC-1200s) are installed or a public LAN segment is used, network addresses must be changed to conform to the customer’s LAN addressing scheme.


BConfiguring Network Addresses

The following tools are required:

◆ A maintenance terminal (desktop or notebook PC) with:

• The Microsoft Windows 98, Windows 2000, or Windows Millennium Edition operating system installed.

• RS-232 serial communication software (such as ProComm Plus or HyperTerminal) installed. HyperTerminal is provided with Windows operating systems.

◆ An asynchronous RS-232 modem cable (provided by installation or service personnel).

Perform the following steps to change a switch’s IP address, subnet mask, or gateway address.

1. Connect one end of the RS-232 modem cable to the 9-pin maintenance port at the rear of the switch chassis.

2. Connect the other cable end to a 9-pin communication port (COM1 or COM2) at the rear of the maintenance terminal PC.

3. Power on the maintenance terminal. After the PC powers on, the Windows desktop displays. Refer to operating instructions shipped with the PC.

The following steps describe the procedure using HyperTerminal.

4. From the Windows taskbar, click Start, Programs, Accessories, Hyperterminal, Hyperterminal.

This displays the Connection Description dialog box (Figure B-1).

Figure B-1 Connection Description Dialog Box


B

B-4


5. Type DS-24M2 into the Name field and click OK. This displays the dialog box in Figure B-2.

Figure B-2 Connect To Dialog Box

6. Ensure that the Connect using field displays COM1 or COM2 (depending on the serial communication port connection to the switch), and click OK.

This displays the COM1 (or 2) Properties dialog box (Figure B-3).

Figure B-3 Com 1, 2 Properties Dialog Box



7. Configure the Port Settings parameters as follows:

• Bits per second — 115200

• Data bits — 8

• Parity — None

• Stop bits — 1

• Flow control — Hardware

When the parameters are set, click OK.

This displays the HyperTerminal window (Figure B-4).

Figure B-4 HyperTerminal Window

8. At the > prompt, type the user-level password (the default is level-2) and press ENTER. The password is case-sensitive. The HyperTerminal window appears with software and hardware version information for the switch, and a {U}> prompt at the bottom of the window.

>xxxxxxxSSP0>ipconfigMAC Address: 08 88 C0 00 F5IP Address: 10.1.8.6Subnet Mask: 255.0.0.0Gateway Address: 0.0.0.0

SSP0>


B

B-6


9. At the {U}> prompt, type ipconfig and press ENTER. The HyperTerminal window appears with configuration information listed as follows:

• MAC Address

• IP Address (default is 10.xxx.yyy.zzz)

• Subnet Mask (default is 255.0.0.0)

• Gateway Address (default is 0.0.0.0)

10. Change the IP address, subnet mask, and gateway address as directed by the customer’s network administrator. To change the switch network addresses, type the following at the {U}> prompt and press ENTER.

ipconfig xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz.zzz.zzz.zzz

The IP address is always xxx.xxx.xxx.xxx, the subnet mask is always yyy.yyy.yyy.yyy, and the gateway address is always zzz.zzz.zzz.zzz, where the octets xxx, yyy, and zzz are decimals, 0 through 255. If a network address is to remain unchanged, type the current address in the respective field.

When the new network addresses are configured at the switch, the message Request completed OK appears at the bottom of the HyperTerminal window.

11. Select the Exit option from the File pull-down menu to close the HyperTerminal application. The following message box appears:

12. Click Yes. The following message box appears:

13. Click No to exit and close the HyperTerminal application.



14. Power off the maintenance terminal:

a. From the Windows taskbar, click Start, Shut Down.

b. At the Windows NT Workstation menu, select the Shut Down option.

c. At the Shut Down Windows window, select Shut down the Computer and click Yes to power off the PC.

15. Disconnect the serial null modem cable from the switch and the maintenance terminal.


B

B-8



CIvisible Body Tag

This appendix describes the procedures for configuring the DS-24M2 from the Embedded Web Server if the switch does not have access to a Connectrix service processor.

• Introduction .......................................................................................C-2• Configuring Switch Ports.................................................................C-7• Configuring Switch Identification .................................................. C-9• Configuring the Date and Time .................................................... C-11• Configuring Switch Parameters.................................................... C-12• Configuring Fabric Parameters..................................................... C-14• Configuring Network Information............................................... C-17• Configuring SNMP Trap Message Recipients ............................ C-19• Configuring Zoning........................................................................ C-22• Configuring User Names and Passwords ................................... C-25• Configuring Port Binding .............................................................. C-26• Configuring Feature Keys.............................................................. C-28

Configuring the Switchfrom the Embedded

Web Server

Configuring the Switch from the Embedded Web Server C-1

C

C-2

Configuring the Switch from the Embedded Web Server

IntroductionIf the DS-24M2 was purchased for stand-alone installation, the Embedded Web Server (EWS) will be used to configure and manage the switch. Through the Web Server, you can perform most of the configuration and monitoring operations that you can perform through the Connectrix Manager.

Although the DS-24M2 provides the facility for management through the Embedded Web Server, EMC recommends using the Connectrix Manager instead. The Connectrix Manager provides these enterprise-level management features not available with the Embedded Web Server:

◆ Automatic system backup

◆ Fabric-level management

◆ Multiswitch management

◆ Multiswitch status monitoring, with automatic call-home notification.

The Embedded Web Server management interface is a one-to-one relationship only — you can manage/monitor only one director/switch at a time.

CAUTION!If you choose to configure the switch’s network IP address to be on a public network, this could allow someone to attempt to manage the switch via the EWS. Therefore, if you configure the switch with a public IP address, EMC recommends that the EWS be disabled, using Connectrix Manager. If you intend to use the EWS (even though EMC does recommend and/or support its use), verify that it is enabled in Connectrix Manager; however, be sure to change the default passwords of the EWS. (Refer to Configuring User Names and Passwords on page C-25 for information on changing the password.)

This same caution applies to the CLI (Telnet) interface. (Refer to Appendix D.)


CConfiguring the Switch from the Embedded Web Server

The Reset Configuration operation will not reset the password of the Embedded Web Server. (Refer to Resetting the Configuration on page 7-16 for information on resetting the configuration.)

By using the Connectrix Manager, you do not have do configure the DS-24M2 with a public IP. The Connectrix Manager utilizes a private network inside the Connectrix cabinet to connect to the DS-24M2.

Management Support — Connectrix Manager vs. Embedded Web ServerThis section lists Connectrix features and functions, and shows whether they are supported by Connectrix Manager and the Embedded Web Server.

Table C-1 demonstrates the considerable advantages of managing the Connectrix environment with Connectrix Manager. If Connectrix Manager is already used on site, or if it was purchased for management of ED-140Ms, ED-64Ms, and/or ED-1032s, EMC highly recommends that the DS-xxM switch(es) be purchased with a Product Manager license as well. If this license is purchased, when installing a DS-xxM outside of a Connectrix cabinet, consider cabling these switch product's Ethernet cable back to the Ethernet hub in a nearby EC-1x00 cabinet and installing the switches into Connectrix Manager. If this is not an option, consider cabling the new switches onto the same Ethernet as the Connectrix Manager's Clients. Connectrix Manager can support switches on its private and public Ethernets simultaneously.

Table C-1 Management Support Table

Category Feature/Function

Connectrix Manager 4.1/4.2/6.0/6.2/6.3

Embedded Web Server 1.2/1.4/2.0

Embedded Web Server 4.0/4.1

Zoning Configuration a Zoning Backup Y N N

Zoning Restore Y N N

Zoning Library Y N N

WWN Nicknames Y N N

WWN Display Drag and Drop Y N N

Introduction C-3

C

C-4


a. Connectrix Manager displays the WWNs of all connected N_Ports and allows the user to drag and drop the WWNs into the zones. Connectrix Manager allows the user to configure nicknames for the WWNs. The Embedded Web Server does not have nicknames or drag and drop zoning; however, it does have a pull-down box that allows you to select the WWN for any attached node.

If a DS-xxM is managed by a Connectrix service processor and zoning changes are made directly to the DS-xxM using the EWS, those changes will not be reflected in the Zoning Library on the Connectrix service processor.

b. Connectrix Manager has the capability to call home to the Support Center 24 hours a day, 7 days a week. The Embedded Web Server does not have this feature built in. Call-home support for standalone DS-xxM switches is done using the new MIB in microcode 1.2/1.4/2.0. EMC ControlCenter WebEdition 4.3 and OnAlert interface with this MIB to provide call-home support.

c. Connectrix Manager can back up all zoning, operating parameters, identification, nicknames, user rights, and logs. Connectrix Manager also has an utility that will perform automatic backups. The Embedded Web Server does not have backup capabilities; however it does have the ability to manually download switch configuration data via the File Transfer tab.

d. Connectrix Manager can view multiple switches/directors and multiple fabrics. The Embedded Web Server can view the switch on a one-to-one relationship only; thus, the user can manager/monitor only one switch at a time.

e. Both Connectrix Manager and the Embedded Web Server can perform firmware upgrades on line; however, only Connectrix Manager has a firmware library.

Remote Support b Call-home Y Y b Y

Dial-In Y Y b Y

Configuration c Backup Y N N

Automatic Backup Y N N

Multiswitch Management d Multi-Switch Management Y N Y

Fabric Management d Fabric Management Y N Y

Firmware upgrades e On-line Y Y Y

Library Y N N

Table C-1 Management Support Table (continued)

Category Feature/Function

Connectrix Manager 4.1/4.2/6.0/6.2/6.3

Embedded Web Server 1.2/1.4/2.0

Embedded Web Server 4.0/4.1



Required Browsers To use the Embedded Web Server, you need a PC platform with Internet access and either of these browsers:

◆ Netscape Navigator 4.6 or higher

◆ Microsoft Internet Explorer 4.0 or higher

Opening the Web Server Application

To open the Web Server application:

1. Ensure that the PC and the Ethernet LAN segment (with the switch attached) are connected through the Internet.

2. At the PC, launch the browser application.

3. At the browser, enter the IP address of the switch as the URL.

This displays the dialog box in Figure C-1:

Figure C-1 User Name and Password Dialog Box

4. Enter the default user name (Administrator) and password (password) (both are case-sensitive); then click OK.

The Embedded Web Server interface opens to a View window (Figure C-2) that shows hardware components of the switch.

Introduction C-5

C

C-6


Figure C-2 Embedded Web Server — View Window

The Name is taken from the switch configuration. Refer to Configuring Switch Identification on page C-9.

The menu at the left side of the provides access to most of the same configuration and monitoring operations that you can perform using tthe Connectrix Manager. Clicking Help provides comprehensive information on performing these operations.

AccessingConfiguration

Operations

To access configuration operations, click Configure on the left side of the window. This displays the window shown in Figure C-3 on page C-7.



Configuring Switch PortsPerform the procedure in this section to configure names and operating characteristics for the switch ports. Refer to Configuring Ports on page 5-17 for more information on some of the parameters.

Figure C-3 shows the Configure window, opened to the default page.

Figure C-3 Embedded Web Server— Configure Ports Window

Configuring Switch Ports C-7

C

C-8


Configure port parameters as follows; then click Activate to save the information:

• Name — Up to 24 alphanumeric characters. This name should identify the device to which the port is attached.

• Blocked — Block/unblock transmission from a port by clicking the checkbox to add/remove a checkmark.

• 10-100 km — Enable/disable extended distance buffering for a port by clicking the checkbox to add/remove a checkmark.

• Type — Select E_Port, F_Port, or G_Port.

• Speed — 1 Gb/sec, 2 Gb/sec, Negotiate.



Configuring Switch IdentificationThe Configure: Switch window allows you to configure the switch name, description, location, and contact person. The Name, Location, and Contact variables configured here correspond to the SNMP variables sysName, sysLocation, and sysContact. These variables are used by SNMP management workstations when obtaining data from managed switches.

Refer to Configuring Switch Identification on page 5-2 for information on performing this operation through the Connectrix Manager.

To configure switch identification:

1. On the Configure window (Figure C-3 on page C-7), click the Switch tab. This displays the window in Figure C-4.

Figure C-4 Embedded Web Server — Configure Switch Identification


• Name — Up to 24 alphanumeric characters. Each switch/director should be configured with a unique name. This is necessary for directors on a LAN with DNS entries, and it also will help in future identification and maintenance tasks.

If the switch is installed on a public LAN, the name should reflect the switch’s Ethernet network DNS host name. For example, if the DNS host name is DS-24M21.emc.com, enter DS-24M21 in this dialog box.

Configuring Switch Identification C-9

C

C-10


• Description — Up to 255 alphanumeric characters.

• Location — Up to 255 alphanumeric characters.

• Contact person — Up to 255 alphanumeric characters.

3. Click Activate to save the information.



Configuring the Date and TimeThe operation described here allows you to configure the effective date and time for the switch. Refer to Configuring the Date and Time on page 5-31 for information on performing this operation through the Connectrix Manager.

1. On the Configure: Switch window (Figure C-4 on page C-9), click Date/Time. This displays the window in Figure C-5.

Figure C-5 Embedded Web Server — Configure Switch Date/Time

2. Click the Date fields that require changing, and enter numbers in these ranges:

• Month (MM): 1 through 12

• Day (DD): 1 through 31

• Year (YYYY): greater than 1980

3. Click the Time fields that require changing, and enter numbers in these ranges:

• Hour (HH): 0 through 23

• Minute (MM): 0 through 59

• Second (SS): 0 through 59


Configuring the Date and Time C-11

C

C-12


Configuring Switch ParametersThe operation described here allows you to configure Fibre Channel operating parameters fo the switch. Refer to Configuring Operating Parameters on page 5-4 for descriptions of the parameters and information on performing this operation through the Connectrix Manager.

1. On the Configure:Switch window (Figure C-4 on page C-9), click Parameters.

This displays the window in Figure C-6.

Figure C-6 Embedded Web Server — Configure Switch Parameters


• Preferred Domain ID — 1 through 31. (The default is 1.)

If the switch is attached to another switch/director, both units must have unique Domain IDs. If the values are not unique, the port connection segments and the switch cannot communicate with the fabric.

• Insistent Domain ID — If this option is Enabled, the Preferred Domain ID will become the active domain identification when the fabric initializes. Refer to Insistent on page 5-6 for more information.



• Rerouting Delay — Ensures (if Enabled) that frames are delivered in order through the fabric to their destination. Refer to Rerouting Delay on page 5-7 for more information.

• Domain RSCNs — If this option is Enabled, Domain RSCNs (register for state change notifications ) are sent between end devices in a fabric to provide additional connection information to host bus adapters (HBAs) and storage devices. Refer to Domain RSCNs on page 5-7 for more information.

• Suppress RSCNs on Zone set activations — If this option is Enabled, fabric-format RSCNs (register for state change notifications ) are not sent to ports on the switch following any change to the fabric's active zone set.

Generally, you should set this parameter to Disabled. Refer to Suppress RSCNs on Zone Set Activations on page 5-7 for more information.


Configuring Switch Parameters C-13

C

C-14


Configuring Fabric ParametersThe operation described here allows you to configure Fibre Channel fabric parameters for the switch. Refer to Configuring Operating Parameters on page 5-4 for descriptions of the parameters and information on performing this operation through the Connectrix Manager.

1. Set the switch off line as follows:

a. Click Operations at the left side of the Web Server window.

b. On the Operations window, click the Online State tab. This displays the current state:

c. Click Set Offline.

This message appears:

Your operations changes have been successfully activated

2. On the Configure:Switch window (Figure C-4 on page C-9), click Fabric Parameters.

This displays the window in Figure C-7 on page C-15.



Figure C-7 Embedded Web Server — Configure Fabric Parameters


• BB_Credit — 1 through 16.

• R_A_TOV — 10 through 1200 (tenths of a second). (This translates to a range of 1 through 120 seconds.) The default is 100 tenths, or 10 seconds.

If the switch is attached to another switch/director, both units must be set to the same R_A_TOV. If the values are not identical, the port connection segments and the switch cannot communicate with the fabric. In addition, the R_A_TOV must be greater than the E_D_TOV.

• E_D_TOV — 2 through 600 (tenths of a second). (This translates to a range of 0.2 through 60 seconds.) The default is 20 tenths, or 2 seconds.

If the switch is attached to another switch/director, both units must be set to the same E_D_TOV. If the values are not identical, the port connection segments and the switch cannot communicate with the fabric. In addition, the E_D_TOV must be less than the R_A_TOV.

• Switch Priority — EMC recommends leaving the setting at Default. Refer to Switch Priority on page 5-9 for more information.

Configuring Fabric Parameters C-15

C

C-16


• Interop Mode:

– Select McDATA Fabric 1.0 if all switches in the fabric are in this list: ED-1032, ED-140M, ED-64M, DS-32M, DS-32M2, DS-24M2, DS-16M, DS-16M2

– Select Open Fabric 1.0 if one or more switches in the fabric are in this list: DS-16B, DS-8B


5. Set the switch on line:


b. On the Operations window, click the Online State tab.

c. Click Set Online.



Configuring Network InformationVerify the type of LAN installation with the customer’s network administrator:

◆ If one switch (or one EC-1200 cabinet) is installed on a dedicated LAN, network information (IP address, subnet mask, and gateway address) does not require changing.

◆ If multiple switches (or multiple EC-1200 cabinets) are installed, or a public LAN segment is used, network information must be changed to conform to the customer’s LAN addressing scheme.

If network addresses were changed (refer to Appendix B), this procedure is not required. If network information was not changed, perform the following steps to change a switch IP address, subnet mask, or gateway address:

1. On the Configure: Switch window (Figure C-4 on page C-9), click Network.


Figure C-8 Embedded Web Server — Configure Switch Network

Configuring Network Information C-17

C

C-18


2. Configure the parameters as specified by the customer’s network administrator. The parameters and their default settings are:

• IP Address — Default is 10.1.1.10

• Subnet Mask — Default is 255.0.0.0

• Gateway Address — Default is 0.0.0.0


A message displays the new address information. After a few moments, the browser automatically redirects the display to the new URL (the newly-entered IP address).



Configuring ManagementThe Management screens allow you to:

◆ Configure SNMP community names, write authorizations, and network addresses

◆ Enable or disable the command line interface

◆ Configure the Management Server (if installed)

Configuring SNMP Trap Message Recipients

The operation described here allows you to configure community names, write authorizations, and network addresses for up to 12 SNMP trap message recipients.

Refer to Configuring the SNMP Agent on page 5-24 for descriptions of the parameters and information on performing this operation through the Connectrix Manager.

To configure SNMP trap recipients:

1. If network information was configured at the browser, go to step 2. If network information was not configured, click the Management tab on the Configure window (Figure C-4 on page C-9).


Configuring Management C-19

C

C-20


Figure C-9 Embedded Web Server — Configure SNMP

2. For each trap recipient, configure the parameters as follows:

• Community Name — Up to 32 alphanumeric characters. The community name is incorporated into SNMP trap messages to ensure against unauthorized viewing or use.

• Write Authorization — Is enabled if the box is checked. (The default is disabled.) Click the checkbox to add or remove a checkmark

When write authorization is enabled, a management workstation user can change sysContact, sysName, and sysLocation SNMP variables.

• Trap Recipient — IP address or DNS host name of the SNMP management workstation, up to 64 alphanumeric characters. EMC recommends using the IP address.

• UDP Port Number — The default user datagram protocol (UDP) port number for trap recipients is 162. To override this port number, enter a decimal port number in the associated UDP Port Number field.




Enabling/Disabling the CLI

To enable of disable the command line interface:

1. On the Management window, click the CLI tab.

This displays a message similar to the following:

Figure C-10 CLI Enabled/Disabled Message

2. Click Enable/Disable (whichever appears).

Configuring the Open Systems Management Server

A feature key is necessary to enable the Open Systems Management Server (OSMS). This can be acquired only through an RPQ.

To configure the management server features:

1. On the Management window, click the OSMS tab.

2. Configure the screen.


Configuring Management C-21

C

C-22


Configuring ZoningZoning operations allow you to create, modify, and/or delete zones and zone sets. (Refer to the Connectrix Manager User Guide for more information on zoning.)

1. On the Configure window (Figure C-3 on page C-7), click the Zoning tab.


Figure C-11 Embedded Web Server — Configure Zone Set

The information and prompts displayed on the Zone Set and Zones windows are fairly self-explanatory.

2. On the Zone Set window you can add, delete (clear), or rename a zone set, or enable/disable the default zone.

3. To add, delete, or modify a zone, click Zones to display a Zones window (Figure C-12 on page C-23).



Figure C-12 Embeded Web Server — Configure Zone

4. Any zones in the zone set are listed in the lower part of the window. If the zone list extends past the bottom of the window, you can display more by clicking Display More Zones or by using the scroll bar at the right.

Clicking a zone’s Delete button allows you to delete the zone. Clicking the zone name displays a Modify Zone window (Figure C-13 on page C-24).

Configuring Zoning C-23

C

C-24


Figure C-13 Embedded Web Server — Modify Zone

5. If you want to add an attached node to the zone, select its Attached Node World Wide Name and click Add Member.

To add a node that is not attached, enter its WWN into the World Wide Name field and click Add Member.

6. To add additional zones, click Zones. Then enter a zone name and click Add New Zone.

Clicking the new zone name displays a Modify Zone window. Add new members to the zone.

7. To save the configuration, click Zone Set. Then click Save and Activate Zoning Configuration.

This also changes the zone set status from Unsaved to Saved.



Configuring User Names and PasswordsThe operation described here allows you to to configure the administrator-level and operator-level passwords (as specified by the customer’s network administrator) used to access the Embedded Web Server application.

1. On the Configure window (Figure C-3 on page C-7), click the Security tab.

This displays a dialog box for your user name and password (shown in Figure C-1 on page C-5).

2. Enter your user name and password; then click OK.


Figure C-14 Embedded Web Server — Configure Security

3. In the New User Name fields, enter Administrator and Operator names of up to 16 alphanumeric characters each.

4. In the New Password fields, enter passwords of up to 16 alphanumeric characters each.

5. Enter the same passwords in the Confirm New Password fields.


Configuring User Names and Passwords C-25

C

C-26


Configuring Port BindingThis operation allows you to specify a WWN or nickname that can then be bound to a port. Refer to Configuring Port Binding on page 5-22 for more information.

1. On the Configure window (Figure C-3 on page C-7), click the Security tab; then click the Port Binding tab on the Security window.


2. Configure tht parameters as described under Configuring Port Binding on page 5-22.




Figure C-15 Embedded Web Server — Configure Port Binding

Configuring Port Binding C-27

C

C-28


Configuring Feature KeysFeature keys are add-on options (such as FlexPorts) that are installed and enabled at the customer site, either at installation time or at a later date.

Once the optics are installed and you have obtained the appropriate FlexPort feature key from the EMC Powerlink website (http://powerlink.emc.com), follow these steps to configure the feature key using the Embedded Web Server:

Refer to Adding FlexPorts on page 5-22 for information on adding ports.

1. If you are installing the FlexPort feature key, install the optics in the appropriately numbered positions, and then proceed with step 2. (You do not have to set the switch off line to install the FlexPort feature key.)

If you are installing any other feature key, set the switch off line as follows:


b. On the Operations window, click the Online State tab. This displays the current state:

c. Click Set Offline.

This message appears:

Your operations changes have been successfully activated

2. From the Embedded Web Server Operations menu, click the Feature Installation tab.

This displays a window similar to Figure C-16 on page C-29.



Figure C-16 Embedded Web Server — Feature Installation

3. Type the feature key in the Feature Key field; then click Activate.

4. The interface displays a confirmation page with a warning, stating that this action overrides the current set of switch features.

Click Activate to activate the new feature key. All current features are replaced with new features.

5. If you set the switch off line to install one or more feature keys, set it back on line:


b. On the Operations window, click the Online State tab.

c. Click Set Online.

Enterprise Fabric Extensions, 16 FlexPorts, Open Trunking

Offline

Offline

Configuring Feature Keys C-29

C

C-30



DInvisible Body Tag

This appendix describes the commands that can be entered through the command line interface (CLI) for the DS-24M2. Access through a Telnet client is presumed.

◆ Telnet Sessions ...................................................................................D-2◆ CLI Overview ....................................................................................D-3◆ The config Branch ...........................................................................D-16◆ maint .................................................................................................D-59◆ perf ....................................................................................................D-63◆ show..................................................................................................D-78

Command LineInterface

Command Line Interface D-1

D

D-2

Command Line Interface

Telnet SessionsThe CLI can be used only through a Telnet Client session in an out-of-band management environment, using the Ethernet port in the switch. Although the primary use of the CLI is in host-based scripting environments, the CLI commands can also be entered directly at a command line. Any hardware platform that supports the Telnet Client software can be used.

By default, Telnet access is enabled. If access has been disabled, you can enable it through the Connectrix Manager, a Product Manager, or the Embedded Web Server. Refer to Enabling Telnet on page 5-44.

Ethernet Connection Loss

If the Ethernet cable is disconnected from the switch during a Telnet session, one of three scenarios is possible:

◆ Replace the Ethernet cable before the client connection times out, and the Telnet session will continue.

◆ Wait 15 minutes for the client connection times out; then replace the Ethernet cable and restart the connection.

◆ If the client connection has already timed out:

a. Replace the Ethernet cable.

b. Open an Embedded Web Server or Connectrix Manager Product Manager window.

c. Toggle the enabled state of the CLI, thereby clearing the client connection.

d. Restart the client connection.

Once the client connection is reestablished, verify your configuration’s completeness and accuracy.


DCommand Line Interface

CLI OverviewThe Command Line Interface (CLI) provides an alternative to the Connectrix Manager and Embedded Web Server (EWS) for DS-24M2 management capabilities.

The primary purpose of the CLI is for scripts written for use in a host-based scripting environment. Therefore, this appendix presumes that the user is familiar with:

• Establishing and using a Telnet session

• Using the command line of a terminal

• Writing scripts

• Networking, SAN, and zoning concepts

• Connectrix products in the user’s network

The CLI can be used only through a Telnet client session in an out-of-band management environment, using the Ethernet port in the switch. Although the primary use of the CLI is in host-based scripting environments, the CLI commands can also be entered directly at a command line. Any hardware platform that supports Telnet client software can be used.

The primary purpose of the CLI is to automate management of a large number of switches/directors with the use of scripts.

Because the CLI is not an interactive interface, no prompts are displayed to guide the user through a task. If an interactive interface is needed, use the Connectrix Manager or Embedded Web Server.

For day-to-day operations, EMC recommends using the Connectrix Manager, not the CLI, unless absolutely necessary.

CLI Overview D-3

D

D-4


CAUTION!If you choose to configure the switch’s network IP address to be on a public network, this could allow someone to attempt to manage the switch via the CLI. Therefore, if you configure the switch with a public IP address, EMC recommends that the CLI be disabled, using Connectrix Manager. If you intend to use the CLI (even though EMC does recommend and/or support its use), verify that it is enabled in Connectrix Manager; however, be sure to change the default passwords of the CLI. (Refer to login on page D-11.)

This same caution applies to the Embedded Web Server interface. (Refer to Appendix C.)

Entering CLI Commands

CLI commands can be entered directly at the command line of a terminal or coded in a script.

CLI commands are not case sensitive.

DocumentConventions

Throughout this appendix, periods are used to separate the components of a command name. However, the periods cannot be included when the command is actually entered at the terminal or coded in a script. (How to enter the commands is explained in Navigating the CLI Command Tree on page D-9.)

Even though the commands cannot be entered with the periods, the command line prompts do include the periods; for example:

Config.Port>



NavigationConventions

Basic command line navigation conventions are supported. Table D-1 includes the asynchronous commands that are recognized by the CLI.

Table D-1 CLI Command Tree Navigation Conventions

Character Sequence Common Name Action or Description

<CR> Carriage Return Pass a completed line to the parser.

<DEL> Delete Backspace one character and delete the character.

<NL> New Line Pass a completed line to the parser.

<SP> Space Used to separate keywords.

# Pound Sign Used to designate comments in a script.

? Question Mark Provide help information.

“ Quotation Mark Used to surround a single token.

Â Control-A Position the cursor to the start of the line.

^B Control-B Position the cursor left one character.

^D Control-D Delete the current character.

Ê Control-E Position the cursor to the end of the line.

^F Control-F Position the cursor right one character.

^H Control-H Backspace one character and delete the character.

Î Tab Complete the current keyword.

^K Control-K Delete to the end of the line.

^L Control-L Redraw the line.

^N Control-N Move down one line in the command history.

^P Control-P Move up one line in the command history.

^R Control-R Redraw the line.

Û Control-U Clear the input and reset the line buffer.

^X Control-X Clear the input and reset the line buffer.

<ESC>[A Up Arrow Move up one line in the command history.

CLI Overview D-5

D

D-6


Command Tree The command tree of the CLI begins from the Root. The commands in the four extended branches (config, maint, perf, and show) supported on the DS-24M2 are described later in this appendix.

There are three additional commands (login, logout, and commaDelim) that are not true branches. These commands are described later in this section.

Table D-2 shows the hierarchy under the Root (reading from left to right). The commands (with the exception of the zoning commands) are listed in alphabetical order to make them easier to locate.

Although the commands can be entered in any order (depending on the desired results), the order shown in Table D-2 for the zoning commands is a typical order in which the zoning commands are entered.

Note that the order in which commands are entered determines the order in which the show commands display the values.

<ESC>[B Down Arrow Move down one line in the command history.

<ESC>[C Right Arrow Position the cursor right one character.

<ESC>[D Left Arrow Position the cursor left one character.

Table D-1 CLI Command Tree Navigation Conventions (continued)

Character Sequence Common Name Action or Description

Table D-2 CLI Command Tree

config -------------------- enterpriseFabMode setState

features ----------------- installKey

enterpriseFabMode

openSysMS

ip -------------------------- ethernet

show

port ----------------------- blocked

extDist

name

speed

show

type

openSysMS ----------- setState



security ----------------- fabricBinding ----------- activatePending

addMember

clearMemList

deleteMember

replacePending

setState

showActive

showPending

portBinding ------------- bound

wwn

show

switchBinding ---------- addMember

deleteMember

setState

show

userRights -------------- administrator

operator

show

snmp --------------------- addCommunity

authTraps

deleteCommunity

show

switch -------------------- bbCredit

domainRSCN

edTOV

insistDomainId

interopMode

prefDomainId

priority

raTOV

rerouteDelay

show

zoningRSCN

system ------------------ contact

date

description

Table D-2 CLI Command Tree (continued)

CLI Overview D-7

D

D-8


location

name

show

zoning ------------------- setDefZoneState

activateZoneSet

deactivateZoneSet

replaceZoneSet

clearZoneSet

addZone

deleteZone

renameZoneSet

addWwnMem

addPortMem

clearZone

deleteWwnMem

deletePortMem

renameZone

showPending

showActive

maint --------------------- port ----------------------- beacon

reset

system ------------------ beacon

clearSysError

ipl

resetConfig

setOnlineState

perf ----------------------- class2

class3

clearStats

errors

link

traffic

thresholdAlerts -------- setState

deleteAlert

counter ------------------ addAlert

addPort




Navigating the CLI Command TreeOnce the administrator or operator logs in and sees the Root> prompt, the CLI commands are accessed by navigating up and down the CLI command tree. To move from the root through the any of the four extended branches, enter the name of the next branch as shown in Table D-2.

For example, to use the config.port.name command to configure the name for port 4 on the switch, you would enter a series of commands similar to the following:

Root> configConfig> portConfig.Port> name 4 "Sam’s Tape Drive"

To back up a level, enter two periods; for example:

removePort

setCounter

setParams

show

show --------------------- eventLog

features

frus

ip -------------------------- ethernet

loginServer

nameServer

nameServerExt

port ----------------------- config

info

status

technology

security ----------------- fabricBinding

portBinding

switchBinding

switch

system

zoning


CLI Overview D-9

D

D-10


Config.Port> ..Config>

One approach to making the navigation more concise is to jump directly to return to the root of the CLI command tree, to avoid navigating back up the branch:

Config.Port> rootRoot>

Another approach to making the navigation more concise is to use the complete command syntax from the Root> prompt each time. For example, to issue the config.port.name command and then the maint.port.beacon command, enter the commands similar to the following:

Root> config port name 4 "Sam’s Tape Drive"Root> maint port beacon 4 true

As shown in this example, use of the complete command syntax avoids navigating up and down the levels of the CLI command tree, and the prompt stays at the root level. The use of the complete command syntax is particularly useful when writing scripts.

When coding a script, remember to code the appropriate character sequences (described under Navigation Conventions on page D-5):

Root> config port name 4 "Sam’s Tape Drive"<CR>Root> maint port beacon 4 true<CR>

Limitation on MovementsAs commands are entered, they are recorded in a history log. Note these limitations on movement that result from use of the history log:

◆ If a command has more than 60 characters, the command runs, but the command is not recorded in the history log, and the position in the tree does not change, as shown in the following example. Because the command is not recorded in the history, a subsequent asynchronous command (navigation command) cannot depend on it.

Root> config zoning addWwnMem TheUltimateZone 10:00:00:00:C9:22:9B:64

Root>

◆ Whenever the position in the CLI command tree moves to a new branch (for example, config to maint, config to config.port, or config.port to config), the history log is cleared. In this case, any



asynchronous commands (for example, the up-arrow command <ESC>[A or the up-arrow keyboard symbol) cannot move the position back towards the root, as shown in this example:

Root> configRoot.Config> portRoot.Config.Port> <ESC>[ARoot.Config.Port>

◆ Whenever the position in the CLI command tree moves to a new branch (config, maint, perf, or show), the history log is cleared.

CommandParameters

Some command parameters accept character strings that include spaces. Quotation marks are required when a string includes spaces. For example:

Config.System> location Building_24_Room_16

Config.System> location "Building 24 Room 16"

For parameters that accept a string, if spaces are not included, the quotation marks are not required around that string.

To include quotation marks in a string, use the escape character (\) before the quotation marks.

Config.System> location "Building 24 \"Joe’s PlayLab\""

A null string can be created by using the quotation marks without any space between them. For example:

config.system> location ""

Command Output All output from the CLI commands is limited to the standard 80 columns supported by most Telnet interfaces. The output is flush-left.

login The Command Line Interface allows a single Telnet client to be connected to the switch. If a Telnet client logs out, or if after 15 minutes of inactivity the client’s access times out, another Telnet client may log in. Also note that the Telnet client (user) must log in any time the switch is restarted, because the current user’s access is lost. Examples of a restart include an IPL and any power-off situation.

Syntax login

Purpose This command allows a Telnet client to connect to the switch.

CLI Overview D-11

D

D-12


Description This command allows the user to log in with either Administrator or Operator access rights. The default password for each is password.

A user who logs in with Administrator access rights can use all of the commands described in this appendix. Operator access rights grant permission to use only the show branch of the DS-24M2 CLI command tree; for example, the show.system command.

The login command is called automatically by the CLI each time a new Telnet session is activated, as well as each time new administrator access rights are configured.

After the login command is issued, the Username: prompt automatically appears. After a valid user name is entered, the Password: prompt automatically appears. After the corresponding valid password is entered, the Root> prompt appears. At this prompt the user enters any of the commands included in Table D-2 on page D-6.

A user name and password can be set by the Administrator through the config.security.userRights.administrator command or through the config.security.userRights.operator command.

The CLI does not require that the user names and passwords set through the CLI commands match those set through the switch’s Embedded Web Server.

Parameters This command has no parameters.

Command Examples login Username: Administrator Password: password

login Username: Operator Password: password

logout

Syntax logout

Purpose This command allows a Telnet client to disconnect from the switch.



Description This command logs out the single Telnet client connected to the switch. This command can be entered at any point in the command tree.


Command Examples Root> logout

config> logout

config.port> logout

commaDelim The other output examples shown in this appendix presume that commaDelim is disabled.

Syntax commaDelim enable

Purpose This command enables the user to obtain displayed information in comma-delimited format. (Tabular format is the default.)

Description This command can be entered at any point in the command tree.

Parameters This command has one parameter

Command Examples Root> commaDelim true

config> commaDelim 1

config.port> commaDelim false

Output ExampleDate/Time,Code,Severity,FRU,Event Data,09/12/01 10:58A,375,Major,CTP-0,00010203 04050607 08090A0B 0C0D0E0F,09/12/01 10:58A,375,Major,CTP-0,00010203 04050607 08090A0B 0C0D0E0F,09/12/01 09:58A,385,Severe,CTP-0,00010203 04050607 08090A0B 0C0D0E0F,09/11/01 07:18P,395,Severe,CTP-0,00010203 04050607 08090A0B 0C0D0E0F,

enable Specifies the comma-delineated state for output. Valid values are true and false. Boolean 1 or 0 may be substituted as values.

CLI Overview D-13

D

D-14


Handling Command Line Interface Errors

The CLI detects two types of errors:

◆ An error associated with the interface; for example, a keyword is misspelled or does not exist:

Root> confgError 234: Invalid Command

◆ An error associated with fabric or switch issues; for example, a parameter error is detected by the switch, where port 24 is entered for a switch that supports only 16 ports:

Root> config port name 24 "Port 24"Error 248: Invalid Port Number

In either case, the command is ignored, and the CLI remains at the point it was before the command was entered.

Using CLI Help The question mark (?) can be used within a command to obtain certain information:

◆ If the question mark is used in place of a command keyword, all the keywords at that level of the CLI command tree appear.

◆ If the question mark is used at the end of a complete command, any parameters for that command appear.

◆ If the question mark is used after one or more characters of a keyword, any keywords at that level of the CLI command tree appear.

Root> config s?security snmp switch system

Root> config system ?

Command identified

contact - sets the system contact attribute

date - sets the system date and time

description - sets the system description string

location - sets the system location attribute

name - sets the system name attribute

show - displays the system configuration

Root> config security userRights operator ?

- username <username>

- password <password>



Commenting Scripts The pound sign (#) can be used to add comments in a script file. The pound sign must be the first character in the line; the CLI ignores everything after the pound sign in that line. The following lines are valid:

Root> #Change port 3 to an E_PortRoot> config portconfig.port> ##################config.port> ## Begin Script ##config.port> ##################

The pound sign cannot be used after any other characters (a command, for example) to start a comment. The following is an invalid script line:

Root> maint system beacon true # Turn on beaconing

To correct the previous script line, move the comment either before or after the line with the command. For example, the following examples are both valid:

Root> # Turn on beaconingRoot> maint system beacon true

Root> maint system beacon trueRoot> # Turn on beaconing

Comments of over 200 characters in length may cause unpredictable system behavior. Limit comments to 200 characters per line.

CLI Overview D-15

D

D-16


The config BranchThe config branch of the CLI command tree contains commands that set parameter values on the switch. These values are not temporary (session) values, but are retained across power cycles.

The commands in the config branch can by used only by a user with administrator-level user rights.

CLI config commands are activated on the switch immediately, except as noted.

In general, the config naming commands (except for the config.zoning commands) use the USASCII character set. All of the characters in this 128-character set (the first 7-bit subset of the ISO-8859-1 Latin-1 character set) are valid. Any exceptions are noted in the specific command descriptions.

config.enterpriseFabMode.setState

The functionality of this command is identical to config.features.installKey on page D-17.

Syntax setState enterpriseFabModeState

Purpose This command sets the Enterprise Fabric Mode state for the fabric. The EMC Enterprise Fabric Extensions feature key must be installed to activate the Enterprise Fabric Mode state.

Parameters This command has one parameter:

Command Example Root> config enterpriseFabMode setState 1

enterpriseFabModeState Specifies whether entrepriseFabMode is active. Valid values are activate and deactivate. Boolean 1 and 0 may be substituted as values.



config.features.installKey

Syntax installKey featureKey

Purpose This command allows the user to install a feature set that is enabled by the provided feature key.

If any currently installed feature is being removed by the new feature key, the switch must be off line when the command is issued.


Command Example Root> config features installKey AaBb-CCdD-eeFF-gH

config.features.enterpriseFabMode

The functionality of this command is identical to config.enterpriseFabMode.setState on page D-16.

Syntax enterpriseFabMode enterpriseFabModeState

Purpose This command sets the Enterprise Fabric Mode state for the fabric. The EMC Enterprise Fabric Extensions feature key must be installed to activate the Enterprise Fabric Mode state.


featureKey Specifies the key you have received to enable optional software feature on a specific product. A feature key is a string of case-sensitive, alphanumeric ASCII characters. The number of characters may vary in the format; however, the key must be entered exactly, including the hyphens. An example of a feature key format is XxXx-XXxX-xxXX-xX.

enterpriseFabModeState Specifies whether entrepriseFabMode is active. Valid values are activate and deactivate. Boolean 1 and 0 may be substituted as values.

The config Branch D-17

D

D-18


Command Example Root> config features enterpriseFabMode 1

config.features.openSysMS

The functionality of this command is identical to config.openSysMS.setState on page D-23.

Syntax openSysMS openSysMSState

Purpose This command sets the enabled state of the Open Systems Management Server. The Open Systems Management Server feature key must be installed in order to enable the openSysMS State.

Parameters This command has one parameter.

Command Example Root> config features openSysMS 1

config.features.show

Syntax show

Purpose This command shows the product feature information configured for this switch.


Command Example Root> config features show

osmsState Specifies whether the Open Systems Management Server is enabled. Valid values are enable and disable. Boolean 1 and 0 may be substituted as values.



Output The product feature data is displayed as a table that includes the following properties.

Output Example The output from the config.ip.show command appears as follows:

config.ip.ethernet

Syntax ethernet ipAddress gatewayAddress subnetMask

Purpose This command sets the Ethernet network settings.

Description The Telnet connection can be lost when these Ethernet network settings are changed.

If the IP address is reconfigured, your Telnet client must be reconnected to the new IP address. A new login will be requested.

Installed Feature Set The feature set installed using a feature key. Only installed keys are displayed.

Feature Individual features within each set. In many cases, there is only one feature within each feature set.

State The state of the individual feature. Fabric-wide features are displayed as Active/Inactive. Switch-centric features are displayed as Enabled/Disabled.

Installed Feature Set-----------------------------Open Systems ManagementServerEnterprise Fabric ExtensionsEnterprise Fabric ExtensionsEnterprise Fabric Extensions

Feature------------------OSMSFabric BindingSwitch BindingEnterprise Fabrics

State-----EnabledActiveEnabledActive


D

D-20


Parameters This command has three parameters:

Command Example Root> config ip ethernet 10.0.0.0 0.0.0.0 255.0.0.0

config.ip.show

Syntax show

Purpose This command shows the LAN configuration.


Command Example Root> config ip show

Output Example The output of config.ip.show appears as in this example:

config.port.blocked

Syntax blocked portNumber blockedState

Purpose This command sets the blocked state for a port.

ipAddress Specifies the new IP address for the switch. The address must be entered in dotted decimal format (for example, 10.0.0.0).

gatewayAddress Specifies the new gateway address for the Ethernet interface. The address must be entered in dotted decimal format (for example, 0.0.0.0).

subnetMask Specifies the new subnet mask for the Ethernet interface. The address must be entered in dotted decimal format (for example, 255.0.0.0).

IP Address:Gateway Address:Subnet Mask:

10.0.0.00.0.0.0255.0.0.0



Parameters This command has two required parameters:

Command Examples Root> config port blocked 4 false

Root> config port blocked 4 0

config.port.name

Syntax name portNumber “portName”

Purpose This command sets the name for a port.


Command Example Root> config port name 4 “Sam’s tape drive”

config.port.speed

Syntax speed portNumber portSpeed

Purpose This command sets the speed for a port.

Description A port can be configured to operate at 1 Gb/sec, 2 Gb/sec, or a negotiated speed.

The port speed can be set only to 1 Gb/sec, if the switch speed is 1 Gb/sec. An attempt to set the port speed to 2 Gb/sec or to negotiate in a switch with a 1 Gb/sec switch speed results in an error message.

portNumber Specifies the port number. Valid values for the DS-24M2 are 0 through 23.

blockedState Specifies the blocked state for the port. Valid values are true and false. Boolean 1 or 0 may be substituted as values.


portName Specifies the name for the port. The port name must not exceed 24 characters in length.


D

D-22


If the port speed is set to negotiate, the port and the device to which it is attached negotiate the data speed setting to either 1 Gb/sec or 2 Gb/sec.

Port speed changes temporarily disrupt port data transfers.

Parameters This command has two required parameters.

Command Examples Root> config port speed 4 2g

Root> config port speed 6 negotiate

config.port.type

Syntax name portNumber portType

Purpose This command sets the allowed type for a port.

Description A port can be configured as an E_Port, an F_Port, or a G_Port:

◆ E_Port — Only other switches/directors may attach to that port.

◆ F_Port — Cannot be used as an interswitch link, but may attach to a device with an N_Port.

◆ G_Port — Either a device or another switch/director may attach.


Command Example Root> config port type 4 fport


portSpeed Specifies the speed of the port. Valid values are 1g, 2g, and negotiate.


portType Specifies the type of the port. Valid values are eport, fport, and gport.



config.port.show

Syntax show portNumber

Purpose This command displays the port configuration for a single port.


Command Example Root> config port show 4

Output The port configuration is displayed as a table that includes the following properties:

◆ Port number◆ Port name◆ Blocked state — true or false◆ Extended distance — true or false◆ Type — F Port, E Port, or G Port◆ Speed — 1 Gb/sec, 2 Gb/sec, or Negotiate

Output Example The output of config.port.show appears as in this example:

config.openSysMS.setState

The functionality of this command is identical to config.features.openSysMS on page D-18.

Syntax setState osmsState

Purpose This command sets the enabled state of the Open Systems Management Server. The Open Systems Management Server feature key must be installed in order to enable the openSysMS State.


Port Number:Name:Blocked:Extended distance:Type:Speed:

4Sam’s tape drivefalsefalseF Port2 Gb/sec


D

D-24



Command Example Root> config openSysMS setState 1

config.security.FabricBinding

Note that the config.security.fabricBinding commands function in a different way from most CLI commands, which are single-action commands that take effect immediately. The first fabricBinding command entered invokes a work-area editor. The commands take effect on a temporary copy of a Fabric Member List in the work area until the temporary copy in the work area is activated to the fabric or is discarded.

Because not all the verification of the Fabric Member List can occur on the temporary copy in the work area, it is possible, however unlikely, that the copy of the list encounters no errors until the list is activated to the fabric.

config.security.fabricBinding.activatePending

Syntax activatePending

Purpose This command activates the fabric binding configuration contained in the pending work area to the fabric.

This command takes effect immediately. The CLI verifies the list before activating it to the fabric and adds the managed switch to the list if it is not already present.


Root> config security fabricBinding activatePending

osmsState Specifies whether the Open Systems Management Server is enabled. Valid values are enable and disable. Boolean 1 and 0 may be substituted as values.



config.security.fabricBinding.addMember

Syntax addMember wwn domainId

Purpose This command adds a new member to the Fabric Member List in the pending fabric binding work area. The number of entries is limited to the maximum available domain IDs for the fabric (31).

Changes from this command are not activated to the fabric until the activatePending command is issued.

Parameters This command has two parameters:

Root> config security fabricBinding addMember AA:99:23:23:08:14:88:C1 2

config.security.fabricBinding.clearMemList

Syntax clearMemList

Purpose This command clears the Fabric Membership List for the pending fabric binding working area.

This information is not saved to the fabric until the activatePending command is issued. When the list is cleared, the CLI automatically adds the managed switch to the fabric membership list.


wwn Specifies the world wide name (WWN) of the member to be added to the fabric membership list. The value of the WWN must be in colon-delimited hexadecimal notation (for example, AA:00:AA:00:AA:00:AA:00).

domainId The domain ID of the member to be added to the fabric membership list. Valid domain ID's range from 1 to 31.


D

D-26


config.security.fabricBinding.deleteMember

Syntax deleteMember wwn domainId

Purpose This command removes a member from the Fabric Membership List in the pending fabric binding work area.

Changes are not activated to the fabric until the activatePending command is issued.


Root> config security fabricBinding deleteMember AA:99:23:23:08:14:88:C1

Root> config security fabricBinding deleteMember 2

config.security.fabricBinding.replacePending

Syntax replacePending

Purpose This command replaces the pending working area with the fabric binding configuration that is currently loaded on the fabric.


Root> config security fabricBinding replacePending

wwn Specifies the WWN of the member to be removed from the fabric membership list. The value of the WWN must be in colon-delimited hexadecimal notation (for example, AA:00:AA:00:AA:00:AA:00).

domainId The domain ID of the member to be removed from the fabric membership list. Valid domain IDs range from 1 to 31.



config.security.fabricbinding.setState

Syntax setState fabricBindingState

Purpose This command sets the fabric binding state for the pending fabric binding configuration work area.

This state is not saved to the fabric until the activatePending command is issued.


Root> config security fabricBinding setstate restrict

fabricBindingState Specifies the fabric binding state for the pending fabric binding configuration work area. Valid values are:◆ inactive — Deactivate fabric binding.

Switches/directors are allowed to join the fabric without restriction. The fabric membership list is empty in this state and as such, the fabric membership list is cleared when this state is requested.

◆ restrict — Activate fabric binding and restrict connections. Only switches identified in the fabric membership list may join the fabric in this state. The fabric membership list is automatically populated with devices attached prior to activation, but all new members must be manually added before connecting. The switch must be on line to complete this request.


D

D-28


config.security.fabricBinding.showActive

Syntax showActive

Purpose This command displays the fabric binding configuration saved on the fabric. It performs the same function as show.security.fabricBinding.


Output This command displays the following fabric binding configuration data:

Output Example The output from the config.security.fabricBinding.showActive command displays as follows.

Fabric Binding State: Active RestrictingDomain 1 (00:11:22:33:44:55:66:77Domain 2 (88:99:AA:BB:CC:DD:EE:FF)Domain 14 (11:55:35:45:24:78:98:FA)

config.security.fabricBinding.showPending

Syntax showPending

Purpose This command displays the fabric binding configuration in the pending working area and has not yet been activated to the fabric. If no changes have been made to the pending environment, the CLI displays the active membership list.


Fabric Binding State

The active fabric binding state: Inactive or Active Restricting

fabric membership list

The active fabric membership list.



Output The fabric binding configuration data is displayed as a table that includes the following properties.

Output Example The output from the config.security.fabricBinding.showPending command displays as follows.

Fabric Binding State: Active RestrictingDomain 1 (00:11:22:33:44:55:66:77)Domain 2 (88:99:AA:BB:CC:DD:EE:FF)Domain 14 (11:55:35:45:24:78:98:FA)

config.security.portBinding.bound

Syntax bound portNumber portBindingState

Purpose This command sets the port binding state for a given port.



The pending fabric binding state: Inactive or Active Restricting

fabric membership list

The pending fabric membership list.


portBindingState Specifies the port binding state as active or inactive. Valid values are true and false. (Boolean 1 or 0 may be substituted as values.)◆ If true, the specified port will be bound to

the WWN configured with the config.security.portBinding.wwn command. If no WWN has been configured, no devices can log in to that port.

◆ If false, any device is free to connect to the specified port in this state, regardless of the WWN setting.


D

D-30


Command Examples Root> config security portBinding bound 4 true

Root> config security portBinding bound 4 1

config.security.portBinding.wwn

Syntax bound portNumber boundWwn

Purpose This command configures the single device WWN to which a port is bound.



boundWwn Specifies the WWN of the device that is being bound to the specified port. The value must be entered in colon-delimited hexidecimal notation (for example, 11:22:33:44:55:66:AA:BB).If the boundWwn is configured and the portBindState is:◆ Active — Only the device described by

boundWwn is able to connect to the specified port.

◆ Inactive — The WWN is retained, but any device can connect to the specified port.



Command Examples Root> config security portBinding wwn 4 AA:99:23:23:08:14 :88:C1

Root> config security portBinding wwn 4 attached

Root> config security portBinding wwn 4 remove

config.security.portBinding.show

Syntax show portNumber

Purpose This command displays the port binding configuration for a single port.


Command Example Root> config security portBinding show 4

boundWwn

(continued)Instead of the WWN, either of two values can be entered in this parameter:◆ attached — Automatically configures the

currently attached device WWN as the bound WWN.

◆ remove — Changes the WWN to the default value, 00:00:00:00:00:00:00:00. Even though this removes the WWN-port association, if the portBindingState value set with the config.security.portBinding.bound command is still true (port binding is active), other devices are prevented from logging in to this port. To allow other devices to log in to this port, use the config.security.portBinding.bound command to set the portBindingState parameter to false.



D

D-32


Output The port binding configuration is displayed as a table that includes the following properties:

◆ Port number.◆ port binding — Active or Inactive.◆ Bound WWN — The WWN of the device that is bound to the

specified port. If this field is blank, no device has been bound to the specified port.

Output Example The output of config.security.portBinding.show appears as in this example:

config.security.switchBinding.addMember

Syntax addMember wwn

Purpose This command adds a new member to the Switch Membership List. A maximum number of 256 members may be added to the list.


Root> config security switchBinding addMember AA:99:23:23:08:14:88:C1

config.security.switchBinding.deleteMember

Syntax deleteMember wwn

Purpose This command removes a member from the Switch Member List. The user cannot remove a member that is currently logged in to the switch.

Port Number:Port Binding:Bound WWN:

4ActiveAA:99:23:23:08:14:88:C1

wwn Specifies the switch or N_Port device WWN of the member to be added to the switch membership list. The value of the WWN must be in colon-delimited hexadecimal notation (for example, AA:00:AA:00:AA:00:AA:00).




Root> config security switchBinding deleteMember AA:99:23:23:08:14:88:C1

config.security.switchBinding.setState

Syntax setState switchBindingState

Purpose This command sets the switch binding state on the switch.

wwn Specifies the switch or N_Port device WWN of the member to be removed from the switch membership list. The value of the WWN must be in colon-delimited hexadecimal notation (for example, AA:00:AA:00:AA:00:AA:00). The user may also enter all for this argument to clear the switch membership list completely. Note that the user cannot clear a WWN that is currently logged in to the switch.


D

D-34



Root> config security switchBinding setState allRestrict

switchBindingState Sets the switch binding state for the switch. Valid values are: ◆ disable — Disable switch binding.

Devices (servers, storage, and other switches) are allowed to connect to the switch without restrictions.

◆ eRestrict — Enable switch binding and restrict E_Port connections. E_Ports are prevented from forming ISL connections unless explicitly identified in the switch membership list. F_Port connections are allowed without restriction.

◆ fRestrict — Enable switch binding and restrict F_Port connections. Server and (or) storage devices are prevented from forming F_Port connections with the switch unless explicitly identified in the switch membership list. E_Ports are allowed to form ISL connections without restriction.

◆ allRestrict — Enable switch binding and restrict E_Port and F_Port connections. Both E_Ports and F_Ports prohibit connections with all devices unless explicitly identified in the switch membership list.



config.security.switchBinding.show

Syntax show

Purpose This command displays the switch binding configuration.


Output This command displays the following switch binding configuration data:

Output Example The output from the config.security.portBinding.show command appears as follows.

Switch Binding State: Enabled and Restricting E Ports 00:11:22:33:44:55:66:7788:99:AA:BB:CC:DD:EE:FF11:55:35:45:24:78:98:FA

config.security.userRights.administrator

Syntax administrator “username” “password”

Purpose This command sets the name and password for administrator-level access.

Description Immediately after the name and password for the administrator is set, you are prompted to log in with the new access rights.

switchBindingState ◆ Disabled◆ Enabled and Restricting F_Ports◆ Enabled and Restricting E_Ports◆ Enabled and Restricting All Ports.

Switch Membership List

The Switch Membership List saved on the switch.


D

D-36


Parameters This command has two parameters.

Command Example Root> config security userRights administrator “Administrator” “newpassword”

config.security.userRights.operator

Syntax operator “username” “password”

Purpose This command sets the name and password for operator-level access.


Command Example Root> config security userRights operator “Operator” “newpassword”

username Specifies the new user name for administrator-level login. The default is set to Administrator. This parameter is 1 to 15 characters. Valid characters include all characters in the USASCII character set, excluding control characters and spaces. (Spaces are not valid even though quotation marks are used.)

password Specifies the password for administrator-level login. The default is set to password. This parameter is 1 to 15 characters. Valid characters include all characters in the USASCII character set, excluding control characters and spaces. (Spaces are not valid even though quotation marks are used.)

username Specifies the new user name for operator-level login. The default is set to Operator. This parameter is 1 to 15 characters. Valid characters include all characters in the USASCII character set, excluding control characters.

password Specifies the password for operator-level login. The default is set to password. This parameter is 1 to 15 characters. Valid characters include all characters in the USASCII character set, excluding control characters.



config.security.userRights.show

Syntax show

Purpose This command shows the user rights for the CLI access levels.


Command Example Root> config security userRights show

Output The user rights configuration data is displayed as a table, as shown in the following example.

Output Example

config.snmp.addCommunity

Syntax addCommunity commIndex "commName" writeAuthorization trapRecipient udpPortNum

Purpose This command adds an SNMP community to the SNMP configuration.

Operator Username: OperatorOperator Password: **************Administrator Username: AdministratorAdministrator Password: ***************


D

D-38


Parameters This command has five parameters. Up to six community names and trap recipients may be defined.

Command Example Root> config snmp addCommunity 1 "CommunityName1" enabled 123.123.123.123. 162

config.snmp.authTraps

Syntax authTraps enabledState

Purpose This command enables or disables the authorization traps to be sent to SNMP management stations when unauthorized stations try to access SNMP information from the switch.

commIndex Specifies the community to be created or edited. Valid values are integers 1 through 6.

commName Specifies the community name of the community specified by commIndex. The community name must not exceed 32 characters in length. Valid characters include all those in the ISO Latin-1 character set. Duplicate community names are allowed, but the corresponding writeAuthorization values must match.

writeAuthorization Specifies the write authorization state of the community. Valid values are enabled and disabled. Boolean 1 or 0 may be substituted as values.

trapRecipient Specifies the trap recipient. Values must be 4 bytes in dotted-decimal format.

udpPortNum Specifies the UDP port number to which the switch sends traps for each recipient. The values must be a decimal number; the default value is 162. Valid values include all legal UDP port numbers.




Command Examples Root> config snmp authTraps true

Root> config snmp authTraps 1

config.snmp.deleteCommunity

Syntax deleteCommunity commIndex

Purpose This command entirely deletes a community from the SNMP.


Command Example Root> config snmp deleteCommunity 5

config.snmp.show

Syntax show

Purpose This command shows the switch SNMP configuration.


Command Example Root> config snmp show

enabledState Specifies whether the authorization traps are enabled. Valid values are true and false. Boolean 1 or 0 may be substituted as values.

commIndex Specifies the community to be deleted. Valid values are integers 1 through 6. This value was set in the commIndex parameter of the config.snmp.addCommunity command.


D

D-40


Output The switch configuration data is displayed as a table that includes the following properties

◆ Authentication Traps — The state of the authentication traps (for example, enabled) that are sent to SNMP management stations when unauthorized stations attempt to access SNMP information from the switch.

◆ Index — The community index number.

◆ Community Name — The name of the community.

◆ WriteAuth — The write authorization state.

◆ Trap Recipient — The address of the trap recipient, in 4-byte dotted-decimal format.

◆ UDP Port — The user datagram protocol (UDP) port number to which the director will send traps for each recipient.

Output Example The output from config.snmp.show is similar to the following:

config.switch Some of the config.switch commands require that the switch be set off line. (Use maint.system.setOnlineState to set the switch off line.) If these commands are entered while the switch is on line, an error message results.

config.switch.domainRSCN

Syntax domainRSCN domainRSCNState

Purpose This command sets the domain RSCN state for the switch. The switch can be either off line or on line when this command is executed.

Authorization Traps: Enabled

Index-----123456

Community Name------------------CommunityName1CommunityName1CommunityName1public

WriteAuth------------EnabledEnabledDisabledEnabled

Trap Recipient----------------123.123.123.12310.25.25.10132.44.85.224

UDP Port---------162144162162




Command Example Root> config switch domainRSCN 1

config.switch.insistDomainId

Syntax insistDomainId insistentDomainIdState

Purpose This command sets the insistent domain ID state for the switch.


Command Example Root> config switch insistDomainId 1

config.switch.edTOV

Syntax edTOV timeoutValue

Purpose This command sets the E_D_TOV for the switch.

Description The switch must be off line before issuing this command. Use maint.system.setOnlineState to set the switch off line.

Special care should be used when scripting this command due to its relationship with R_A_TOV.

domainRSCNState Specifies whether the domain RSCN state is enabled. Valid values are enable and disable. Boolean 1 and 0 may be substituted as values.

insistentDomainIdState Specifies whether the insistent domain ID state is enabled. Valid values are enable and disable. Boolean 1 and 0 may be substituted as values.


D

D-42



Command Example Root> config switch edTOV 4

config.switch.interopMode

Syntax interopMode interopMode

Purpose This command sets the interoperability mode for the switch.



Command Example Root> config switch interopMode open

config.switch.prefDomainId

Syntax prefDomainId domainId

Purpose This command sets the preferred domain ID for the switch.



timeoutValue Specifies the new E_D_TOV value. The units for this value are tenths of a second. This parameter must be an integer in the range 2 through 600 (0.2 second to 60 seconds), and it must be smaller than the R_A_TOV.

interopMode Specifies the interoperability mode. Valid values are mcdata (McDATA Fabric 1.0) and open (Open Fabric 1.0)

domainId Specifies the new preferred domain ID value. This parameter must be an integer in the range 1 through 31.



Command Example Root> config switch prefDomainId 1

config.switch.priority

Syntax priority switchPriority

Purpose This command sets the switch priority.



Command Example Root> config switch priority principal

switchPriority Specifies the switch priority. Valid values are: principal, default, or neverprincipal:◆ principal sets the numerical switch priority

to 1. The switch with a priority of 1 becomes the principal switch; however, if two or more switches have a priority of 1, the switch with the lowest WWN becomes the principal switch.

◆ default sets the numerical switch priority to 254. If no switch is set to principal, the switch with a priority 254 becomes the principal switch; however, if two or more switches have a priority of 254, the switch with the lowest WWN becomes the principal switch

◆ neverprincipal sets the numerical switch priority to 255. This switch is not able to become the principal switch.

At least one switch in a multiswitch fabric must have a switch priority value of principal or default.


D

D-44


config.switch.raTOV

Syntax raTOV timeoutValue

Purpose This command sets the R_A_TOV for the switch.


Special care should be used when scripting this command due to its relationship with E_D_TOV.


Command Example Root> config switch raTOV 20

config.switch.rerouteDelay

Syntax rerouteDelay rerouteDelayState

Purpose This command enables or disables rerouting delay for the switch.

Description The switch can be either on line or off line before issuing this command. Use maint.system.setOnlineState to set the switch off line.

This command is applicable only if the configured switch is in a multiswitch fabric. Enabling the rerouting delay ensures that frames are delivered in order through the fabric to their destination.

If there is a change to the fabric topology that creates a new path (for example, a new switch is added to the fabric), frames may be routed over this new path if its hop count is less than a previous path with a minimum hop count. This may result in frames being delivered to a destination out of order because frames sent over the new, shorter path may arrive ahead of older frames still in route over the older path.

timeoutValue Specifies the new R_A_TOV value. The units for this value are tenths of a second. This parameter must be an integer in the range 10 through 1200 (1 second to 120 seconds), and it must be larger than the E_D_TOV.



If rerouting delay is enabled, traffic ceases in the fabric for the time specified in the config.switch.edTOV command. This delay allows frames sent on the old path to exit to their destination before new frames begin traversing the new path. Note that during this delay period, frames addressed to the destinations that are being rerouted are discarded if they are Class 3 frames and rejected if they are Class 2 or Class F frames.

Parameter This command has one parameter.

Command Examples Root> config switch rerouteDelay true

Root> config switch rerouteDelay 1

config.switch.show

Syntax show

Purpose This command shows the switch configuration.

Description The switch can be either on line or off line before issuing this command. Use maint.system.setOnlineState to set the switch off line.


Command Example Root> config switch show

Output The switch configuration data is displayed as a table that includes the following properties:

◆ BB Credit — The maximum number of outstanding frames that can be transmitted without causing a buffer overrun condition at the receiver.

◆ R_A_TOV — Resource Allocation Time Out Value (in tenths of a second).

◆ E_D_TOV — Error Detect Time Out Value (in tenths of a second).

◆ Preferred Domain Id — The preferred domain ID of the switch.

rerouteDelayState Specifies whether a rerouting delay is enabled. Valid values are true and false. Boolean 1 or 0 may be substituted as values.


D

D-46


◆ Switch Priority — Principal, Default, or Never Principal.

◆ Speed — Data rate set on the switch.

◆ Rerouting Delay — A delay that ensures that frames are delivered in order through the fabric to their destination. Values are Enabled or Disabled.

◆ Interop Mode — Interoperability mode for the switch.

◆ Insistent Domain ID — When enabled, ensures that the embedded firmware cannot change a switch's preferred domain ID.

◆ Domain RSCN — When enabled, allows domain RSCNs to be sent to registered members of the fabric.

◆ Zoning RSCN — When enabled, allows zoning RSCNs to be sent to registered members of the fabric.

Output Example The output from config.switch.show command appears as in the following example:

config.switch.zoningRSCN

Syntax zoningRSCN zoningRSCNState

Purpose This command determines whether fabric-format RSCNs will be sent to ports on the switch following changes to the fabric's active zone set. (These changes include activating and deactivating the zone set, or enabling and disabling the default zone.)

Refer to Suppress RSCNs on Zone Set Activations on page 5-7 for more information.

BB Credit:R_A_TOV: E_D_TOV:Preferred Domain Id:Switch Priority:Speed:Rerouting Delay:Interop Mode:Insistent Domain Id:Domain RSCN:Zoning RSCN:

22041Principal2 Gb/secEnabledOpen Fabric 1.0DisabledEnabledEnabled



This parameter is structured differently in different interfaces. To suppress fabric-format RSCNs from the Product Manager or Embedded Web Server, you enable the parameter Suppress RSCNs on Zone Set Activations. To accomplish the same result from the CLI, you set zoningRSCN to disable.


Command Example Root> config switch zoningRSCN 1

config.system.contact

Syntax contact “systemContact”

Purpose This command sets the system contact attribute.


Command Example Root> config system contact “Joe”

zoningRSCSNState Specifies whether the zoning RSCN state is enabled. Valid values are enable and disable (where enable allows fabric-format RSCNs to be sent). Boolean 1 and 0 may be substituted as values.

systemContact Specifies the new system contact string for the switch. The contact can contain up to 255 characters.


D

D-48


config.system.date

Syntax date sysDate sysTime

Purpose This command sets the system date and time.


Command Examples Root> config system date 04:16:2001 10:34:01

Root> config system date 10/09/2001 14:07:55

config.system.description

Syntax description “systemDescription”

Purpose This command sets the system description string.


Command Example Root> config system description “DS-24M2 Fibre Channel Switch”

sysDate Specifies the new system date. The format of the date parameter must be mm:dd:yyyy or mm/dd/yyyy. Valid date values include:mm: 1 through 12dd: 1 through 31yyyy: 1981 or later

sysTime Specifies the new system time. The format of the time parameter must be hh:mm:ss. Valid time values include:hh: 0 through 23mm: 0 through 59ss: 0 through 59

systemDescription Specifies the new system description string for the switch. The name can contain up to 255 characters.



config.system.location

Syntax location “systemLocation”

Purpose This command sets the system location attribute.


Command Example Root> config system location “Everywhere”

config.system.name

Syntax name “systemName”

Purpose This command sets the system name attribute.

Parameters This command has one required parameter.

Command Example Root> config system name “Joe’s Switch”

config.system.show

Syntax show

Purpose This command shows the system configuration.


Command Example Root> config system show

Output The system configuration is displayed as a table similar to that shown under Output Examples.

systemLocation Specifies the new system location for the switch. The location can contain up to 255 characters.

systemName Specifies the new system name for the switch. The name can contain up to 24 characters.


D

D-50


Output Examples The output from config.system.show appears as shown in the following example:

config.zoning Note that the config.zoning commands function in a different way from most other CLI commands, which are single action commands that take effect immediately. A zoning configuration is typically too complicated to be described by a single command, so the first zoning command entered invokes a work area editor. The commands take effect on a temporary copy of a zone set in the work area until the temporary copy in the work area is activated to the fabric or is discarded.

Because not all the verification of the zone set can occur on the temporary copy in the work area, it is possible (but unlikely) that the copy of the zone set encounters no errors until the zone set is activated to the fabric.

config.zoning.setDefZoneState

Syntax setDefZoneState defaultZoneState

Purpose This command enables or disables the default zone and takes effect immediately fabric wide.

Description This command takes effect immediately in the fabric.


Command Examples Root> config zoning setDefZoneState false

Root> config zoning setDefZoneState 0

Name:Description:Contact:Location:Date/Time:

Joe’s SwitchDS-24M2 Fibre Channel SwitchJoeEverywhere04/16/2001 10:34:01

defaultZoneState Specifies whether the default zone is enabled. Valid values are true and false. Boolean 1 or 0 may be substituted as values.



config.zoning.activateZoneSet

Syntax activateZoneSet

Purpose This command activates the zone set contained in the work area to the fabric and takes effect immediately.



Command Example Root> config zoning activateZoneSet

config.zoning.deactivateZoneSet

Syntax deactivateZoneSet

Purpose This command places all attached devices in the default zone and takes effect immediately fabric wide. This command clears both the active zone set and the working area.


The default zone must be activated independently of this command.


Command Example Root> config zoning deactiveZoneSet

config.zoning.replaceZoneSet

Syntax replaceZoneSet

Purpose This command replaces the work area with the active zone set that is currently loaded on the fabric.


Command Example Root> config zoning replaceZoneSet


D

D-52


config.zoning.clearZoneSet

Syntax clearZoneSet

Purpose This command clears the zone set contained in the work area, removing all zones, and takes effect immediately.

Description This command does not change the zone set name.


Command Example Root> config zoning clearZoneSet

config.zoning.addZone

Syntax addZone “zoneName”

Purpose This command adds a new (empty) zone to the zone set in the work area.

Description Changes are not activated on the switch until the config.zoning.activateZoneSet command is issued. The CLI supports the number of zones per zone set specified for a given product.


Command Example Root> config zoning addZone TheUltimateZone

zoneName Specifies the name of the new zone. The zoneName must contain 1 to 64 characters. Valid characters are:ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789$-^_Spaces are not permitted, and the first character must be alphabetical.



config.zoning.deleteZone

Syntax deleteZone “zoneName”

Purpose This command deletes a zone from the zone set in the work area.

Description Changes are not activated on the switch until the config.zoning.activeZoneSet command is issued.


Command Example Root> config zoning deleteZone TheLeastUltimateZone

config.zoning.renameZoneSet

Syntax renameZoneSet “zoneSetName”

Purpose This command changes the name of the zone set in the work area.

Description Changes are not activated on the switch until the config.zoning.activateZoneSet command is issued.


Command Example Root> config zoning renameZoneSet TheUltimateZoneSet

zoneName Specifies the name of the zone to be deleted.

zoneSetName Specifies the new name for the zone set. The zoneSetName must contain 1 to 64 characters. Valid characters are:ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789$-^_Spaces are not permitted, and the first character must be alphabetical.


D

D-54


config.zoning.addWwnMem

Syntax addWwnMem “zoneName” wwn

Purpose This command adds a World Wide Name zone member to the specified zone in the work area.

Description The CLI supports the number of zones members per zone specified for a given product.


Command Example Root> config zoning addWwnMem TheUltimateZone 10:00:00:00:C9:22:9B:64

config.zoning.addPortMem

Syntax addPortMem “zoneName” domainId portNumber

Purpose This command adds the domain ID and port number of a zone member to the specified zone in the work area.

Description The CLI supports the number of zones members per zone specified for a given product.


zoneName Specifies the name of the zone.

wwn The World Wide Name of the member to be added to the zone. The value of the WWN must be in colon-delimited hexidecimal notation (for example, AA:00:AA:00:AA:00:AA:00).

zoneName Specifies the name of the zone.

domainId Specifies the domain ID of the member to be added to the zone. Valid values are integers 1 through 15.

portNumber Specifies the port number of the member to be added to the zone. Valid port number values for the DS-24M2 are 0 through 23.



Command Example Root> config zoning addPortMem TheUltimateZone 10 6

config.zoning.clearZone

Syntax clearZone “zoneName”

Purpose This command clears all zone members for the specified zone in the work area.

Description This command does not change the zone name.


Command Example Root> config zoning clearZone TheNotUltimateAtAllZone

config.zoning.deleteWwnMem

Syntax deleteWwnMem “zoneName” wwn

Purpose This command removes a WWN member from a zone that is in the work area.


Command Example Root> config zoning deleteWwnMem TheNotSoUltimateZone 10:00:00:00:C9:22:9B:AB

zoneName Specifies the name of the zone to be cleared.

zoneName Specifies the name of the zone that contains the member to be deleted.

wwn Specifies the World Wide Name of the member to be deleted from the zone. The value of the WWN must be in colon-delimited hexidecimal notation (for example, AA:00:AA:00:AA:00:AA:00).


D

D-56


config.zoning.deletePortMem

Syntax deletePortMem “zoneName” domainId portNumber

Purpose This command deletes a domain ID and port number for a zone member in the specified zone in the work area.

Parameters This command has three parameters.

Command Example Root> config zoning deletePortMem TheUltimateZone 10 5

config.zoning.renameZone

Syntax renameZone “oldZoneName” “newZoneName”

Purpose This command renames a zone in the work area.


Command Example Root> config zoning renameZone TheOldUltimateZone TheUltimateZone

zoneName Specifies the name of the zone that contains the member to be deleted.

domainId Specifies the domain ID of the member that to be deleted from the zone. Valid domain IDs are integers 1 through 31.

portNumber Specifies the port number of the member to be deleted from the zone. Valid port number values for the DS-24M2 are 0 through 23

oldZoneName Specifies the current zone name of the zone to be renamed.

newZoneName Specifies the new zone name. The name must contain 1–64 characters. Valid characters are: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789$-^_Spaces are not permitted, and the first character must be alphabetical.



config.zoning.showPending

Syntax showPending

Purpose This command shows the zoning configuration in the work area of the zone set that has not yet been activated.


Command Example Root> config zoning showPending

Output The zoning configuration data is displayed as a table that includes the enabled/disabled status, name, and member zones of the zone set.

Output Example The output from config.zoning.showPending is similar to the following:

Pending Zone SetDefault Zone Enabled: FalseZoneSet: TheNewUltimateZoneSet Zone: TheNewUltimateZone ZoneMember: Domain 10, Port 6 ZoneMember: Domain 15, Port 2 Zone: TheNewNotSoUltimateZone ZoneMember: 10:00:00:00:C9:22:9B:AB ZoneMember: 10:00:00:00:C9:22:9B:C6 ZoneMember: 10:00:00:00:C9:22:9B:AB Zone: TheNewNotUltimateAtAllZone ZoneMember: Domain 2, Port 63

config.zoning.showActive

Syntax showActive

Purpose This command shows the zoning configuration saved on the fabric.


Command Example Root> config zoning showActive



D

D-58


Output Example The output from config.zoning.showActive is similar to the following:

Active Zone SetDefault Zone Enabled: FalseZoneSet: TheUltimateZoneSet Zone: TheUltimateZone ZoneMember: Domain 10, Port 6 ZoneMember: Domain 15, Port 2 ZoneMember: Domain 2, Port 63 ZoneMember: 10:00:00:00:C9:22:9B:64 ZoneMember: 10:00:00:00:C9:22:9B:BD Zone: TheNotSoUltimateZone ZoneMember: 10:00:00:00:C9:22:9B:AB ZoneMember: 10:00:00:00:C9:22:9B:C6 ZoneMember: 10:00:00:00:C9:22:9B:AB Zone: TheNotUltimateAtAllZone ZoneMember: Domain 2, Port 63



maintThe maint branch of the CLI command tree contains commands that relate to maintenance activities.

The commands in the maint branch can be used only by the Administrator.

Note that the maint.system.resetConfig command resets all configuration data and non-volatile settings, including network information, to their default values (factory settings). Management access may be lost until the network information is restored.

maint.port.beacon

Syntax beacon portNumber beaconState

Purpose This command enables or disables port beaconing for a particular port.


Command Examples Root> maint port beacon 4 false

Root> maint port beacon 4 0

maint.port.reset

Syntax reset portNumber

Purpose This command resets an individual port.

Description This command resets an individual port without affecting any other ports. However, if a device is attached to the port and the device is online, the reset causes a link reset to occur. If the port is in a failed


beaconState Specifies whether unit beaconing is enabled. Valid values are true and false. Boolean 1 or 0 may be substituted as values.

maint D-59

D

D-60


state (that is, after failing a loopback test), the reset restores the port to an operational state. The reset also clears all statistics counters and disables port beaconing for the specified port.


Command Example Root> maint port reset 4

maint.system.beacon

Syntax beacon beaconState

Purpose This command enables or disables unit beaconing.


Command Examples Root> maint system beacon false

Root> maint system beacon 0

maint.system.clearSysError

Syntax clearSysError

Purpose This command clears the system error light.


Command Example Root> maint system clearSysError

portNumber Specifies the port number to be reset. Valid values for the DS-24M2 are 0 through 23.

beaconState Specifies whether unit beaconing is enabled. Valid values are true and false. Boolean 1 or 0 may be substituted as values.



maint.system.ipl

Syntax ipl

Purpose This command IPLs the switch.

Description Connection to the CLI is lost when this command runs.


Command Example Root> maint system ipl

maint.system.resetConfig

Syntax resetConfig

Purpose This command resets all NV-RAM configuration parameters (including feature keys and IP addresses) to their default values.

Description This command IPLs the switch. Connection from the command line interface to the switch is lost when this command runs.

This command resets all configuration data and non-volatile settings, including network information, to their default values (factory settings). Management access may be lost until the network information is restored.

The default values are set in the firmware of the switch.


Command Example Root> maint system resetConfig

maint.system.setOnlineState

Syntax setOnlineState onlineState

Purpose This command sets the switch on line or off line.

maint D-61

D

D-62



Command Examples Root> maint system setOnlineState true

Root> maint system setOnlineState 1

onlineState Specifies whether the switch is on line. Valid values are true and false. Boolean 1 or 0 may be substituted as values.



perfThe perf branch of the CLI command tree contains commands that relate to performance services.

The commands in the perf branch can by used by either the administrator or the operator.

The counters in perf command output are 32-bit values that wrap at 4,294,967,296. To calculate the full value of a counter, multiply 4,294,967,296 by the value in the wrap field, and add the resulting product to the value in the count field. For example, if a TxFrames statistic has a count value of 1842953 and a wrap value of 12, the full value of the counter is:

(4,294,967,296 x 12) + 1842953 = 51,541,450,505.

perf.class2

Syntax class2 portNumber

Purpose This command displays port Class 2 counters for a single port.


Command Example Root> perf class2 2

Output The port Class 2 counter data is displayed as a table that includes the following properties.

◆ Port — The port number.

◆ Rx Frames — The number of Fibre Channel Class 2 frames the port has received.

◆ Tx Frames — The number of Fibre Channel Class 2 frames the port has transmitted.

◆ Rx Words — The number of Class 2 4-byte words within frames the port has received.

◆ TX Words — The number of Class 2 4-byte words within frames the port has transmitted.


perf D-63

D

D-64


◆ Busied Frms — The number of times that FBSY was returned to this port as a result of a Class 2 frame that could not be delivered to the other end of the link. This occurs if either the fabric or the destination port is temporarily busy.

◆ Rjct Frames — The number of times that FRJT was returned to this port as the result of a Class 2 frame that was rejected by the fabric.

Output Example The output from perf.class2 is similar to the following:

perf.class3

Syntax class3 portNumber

Purpose This command displays port Class 3 counters for a single port.


Command Example Root> perf class3 2

Output The port Class 3 counter data is displayed as a table that includes the following properties.


◆ Rx Frames — The number of Fibre Channel Class 3 frames the port has received.

◆ Tx Frames — The number of Fibre Channel Class 3 frames the port has transmitted.

◆ Rx Words — The number of Class 3 4-byte words within frames the port has received.

Port 2 Statistic-----------RxFramesTxFramesRxWordsTxWordsBusied FrmsRjct Frames

Wrap----------2312653200

Count----------295318418429532953184184295329531841842953




◆ TX Words — The number of Class 3 4-byte words within frames the port has transmitted.

◆ Disc Frames — The number of Class 3 frames that have been discarded upon receipt by this port. There are no FBSYs or FRJTs generated for Class 3 frames.

Output Example The output from perf.class3 is similar to the following:

perf.clearStats

Syntax clearStats portNumber

Purpose This command resets all port statistics for an individual port or for all ports.


Command Example Root> perf clearStats 4

Root> perf clearStats all

Port 2 Statistic-----------RxFramesTxFramesRxWordsTxWordsDisc Frms

Wrap----------32653226

Count----------29531841842953295318418429531842953


perf D-65

D

D-66


perf.errors

Syntax errors

Purpose This command displays port error counters for a single port.


Command Example Root> perf errors 2

Output The port error counter data is displayed as a table that includes the following properties.


◆ Prim Seq Err — The number of state machine protocol errors detected by the port hardware.

◆ Disc Frms — The number of received frames discarded due to a frame size of less than size words or to frames dropped because the BB credit was zero. This number is counted during the first round of frame verification and applies to both Class 2 and Class 3 traffic.

◆ Inv Tx Wrds — The number of 10-bit transmission words that the port is unable to map to 8-bit bytes because of disparity errors or misaligned K characters while in the OL2 or OL3 state.

◆ CRC Errs — The number of frame CRC errors detected by the port.

◆ Dlim Errs — The number of invalid frame delimiters (SOF or EOF) received by the port.

◆ Addr Id Errs — The number of frames received with unknown addressing.




Output Example The output from perf.errors is similar to the following:

Port 2 Statistic Count ----------- ---------- Prim Seq Err 753452 Disc Frms 351269 Inv Tx Wrds 2953184 CRC Errs 1842953 Delim Errs 2953184 Addr Id Errs 1842953

perf.link

Syntax link portNumber

Purpose This command displays port link counters for a single port.


Command Example Root> perf link 2

Output The port link counter data is displayed as a table that includes the following properties.


◆ OLS In — The number of offline sequences initiated by the attached N_Port.

◆ OLS Out — The number of offline sequences initiated by this switch port.

◆ Reset In — The number of link resets initiated by the attached N_Port.

◆ Reset Out — The number of link resets initiated by this switch.

◆ Link Flrs — The number of times the port has detected a link error resulting from an invalid link state transition or timeout.

◆ Sync Losses — The number of times the port has detected a loss of synchronization timeout while not in an offline or LF2 state.


perf D-67

D

D-68


◆ Sig Losses — The number of times the port has detected a loss of signal while not in an offline or LF2 state.

Output Example The output from perf.link is similar to the following:

perf.thresholdAlertsThe perf.thresholdAlerts commands are standard command line interface features; they do not require a feature key. You can configure up to 16 threshold alerts, including both counter threshold alerts and throughput threshold alerts. For a list of the available threshold alerts counters, refer to Table D-3.

In order to activate a threshold alert using the CLI, you must enter a certain commands in order. Enable a threshold alert using the following order:

1. Create a counter threshold alert using perf.thresholdAlerts.counter.addAlert. (Refer to perf.thresholdAlerts.counter.addAlert on page D-70.) Create a name for the threshold alert that you can use in subsequent commands. The threshold alert must then be configured using the other counter threshold alert commands.

2. Associate the threshold alert counter with the threshold alert name using perf.thresholdAlerts.counter.setCounter. (Refer to perf.thresholdAlerts.counter.setCounter on page D-73.)

3. Configure the threshold alert using other perf.threshold alert commands. For example, you should assign the threshold alert to a port using perf.thresholdAlerts.counter.addAlert. (Refer to perf.thresholdAlerts.counter.addPort on page D-71.)

Port 2 Statistic-----------OLS InOLS OutReset InReset OutLink FlrsSync LossesSig Losses

Count----------753452351269295318418429532953184184295335246



4. Once the alert is fully configured, it can be activated using perf.thresholdAlerts.setState. (Refer to perf.thresholdAlerts.setState on page D-76.) An alert cannot be modified unless it is in the disabled state.

Summed Sets Some of the threshold alerts consist of groups of related items called summed sets. When any items in the summed set is encountered, the

Table D-3 Threshold Alert Counters

Number Threshold Alert Counter or Counter Set

1 Link Resets Sent

2 Link Resets Received

3 OLS Sent

4 OLS Received

5 Link Failures

6 Sync Losses

7 Signal Losses

8 Protocol Errors

9 Invalid Tx Words

10 CRC Errors

11 Discarded Frames

12 Frames Too Short

13 Delimiter Errors

14 Address ID Errors

15 Class2BusiedFrames

16 Class2RejectedFrames

17 Class3DiscardedFrames

18 Physical Link Errors Set (refer to Summed Sets)

19 Link Sequence Counts Set (refer to Summed Sets)

20 Logical Link Errors Set (refer to Summed Sets)

perf D-69

D

D-70


total value of the summed set counter is incremented. The items that make up the summed sets are:

◆ Physical Link Errors Summed Set• Link Failures• Sync Losses• Signal Losses• Protocol Errors• Invalid Tx Words• CRC Errors• Frames Too Short• Delimiter Errors

◆ Link Sequence Counts Summed Set• Link Resets Received• Link Reset Sent• OLS Received• OLS Sent

◆ Logical Link Errors Summed Set• Discarded Frames• Address ID Errors• Class 2 Busied Frames• Class 2 Rejected Frames• Class 3 Discarded Frames

perf.thresholdAlerts.counter.addAlert

Syntax addAlert name

Purpose This command configures a new counter threshold alert and assigns it a name. The new alert is assigned default settings which can then be changed using the other counter threshold alert commands.

The default settings for a new counter threshold alert are:

◆ Ports: None◆ Counter: None◆ Increment: 100◆ Interval: 60 minutes◆ State: Disabled




Command Example Root> perf thresholdAlerts counter addAlert Checklinks

perf.thresholdAlerts.counter.addPort

Syntax addPort name portNumber

Purpose This command adds a port to the specified counter threshold alert.

Parameters This command has the following parameters.

Command Example Root> perf thresholdAlerts counter addPort linkresets 12

name Specifies the name of the new counter threshold alert. This name can consist of any ASCII characters up to a maximum length of 64 characters. To use spaces or special characters in this name, put quotation marks around the name. This parameter is case-sensitive.

name The name of a counter threshold alert as defined by the command perf.thresholdAlerts.counter.addAlert. (Refer to perf.thresholdAlerts.counter.addAlert on page D-70.)

portNumber Specifies the port number or port type. Valid values are either a single port number, all ports, or port type.

The following port numbers are valid:0 through 23, or all, which applies the counter threshold alert to every port on the product.

Specifying a port type removes all the ports from the alert and applies the alert to each port that is the specified type of port. Valid values for the DS-24M2 are eport and fport.

A counter threshold alert is not allowed to specify both port types and individual port numbers.

perf D-71

D

D-72


perf.thresholdAlerts.counter.deleteAlert

Syntax deleteAlert name

Purpose This command deletes a specified counter threshold alert.


Command Example Root> perf thresholdAlerts counter deleteAlert checklinks

perf.thresholdAlerts.counter.removePort

Syntax removePort name portNumber

Purpose This command removes a port from the specified counter threshold alert.

An alert cannot be modified unless it is in the disabled state.


Command Example Root> perf thresholdAlerts counter removePort checklinks 12



portNumber Specifies the port number. Valid values are 0 through 23, or all, which removes every port on the product from the counter threshold alert.



perf.thresholdAlerts.counter.setCounter

Syntax setCounter name counterNumber

Purpose This command sets the counter statistic that will be used to trigger the counter threshold alert. Use this command to associate a counter with the threshold alert name created using the perf.thresholdAlerts.setState command.


Command Example Root> perf thresholdAlerts counter setCounter checklinks 1

perf.thresholdAlerts.counter.setParams

Syntax setParams name increment interval

Purpose This command sets the increment and interval times for a specified counter threshold alert.

An alert cannot be modified unless it is in the disabled state.

name The name of a counter threshold alert as defined by the command perf.thresholdAlerts.counter.addAlert (Refer to perf.thresholdAlerts.counter.addAlert on page D-70.)

counterNumber Specifies the counter number. Valid values are shown in Table D-3 on page D-69.

perf D-73

D

D-74



Example The meaning for each of these inputs can best be described using the following example sentence:

If ports 0,1, or 2 CRC Error counter increments more then five times within a period of 30 minutes, send an alert. Where:

The increment value takes place in an interval that is a fixed length amount of time. This interval is not a rolling window interval.

Command Example Root> perf thresholdAlerts counter setParams checklinks 5 30


increment This sets the number of times a counter must increment during the interval period to trigger the alert. Acceptable values are in the range of 1 to 70,560.

interval This sets the interval time for the alert. Acceptable values are in the range of 5 to 70,560 (minutes).

Port listCTA CounterIncrement valueInterval Time

= 0, 1, 2= CRCErrors= 5 = 30 minutes



perf.thresholdAlerts.counter.show

Syntax show name

Purpose This command displays the settings for an individual counter threshold alert.


Command Example Root> perf thresholdAlerts counter show linkresets

Output Example The output from perf.thresholdAlerts.counter.show is similar to the following:

perf.ThreshAlerts.counter.showStatisticTable

Syntax showStatisticTable

Purpose This command displays the table of different statistic counters that can be added to a counter threshold alert. This table is used for reference only.

This command has no parameters.

Command Example Root> perf ThreshAlerts counter showStatisticTable

name The name of a threshold alert as defined by the command perf.thresholdAlerts.counter.addAlert. (Refer to perf.thresholdAlerts.counter.addAlert on page D-70.)

Index:Name:Ports:Counter Statistic:Increment:Interval:Alert State:

3Example_CRC_Error_Finder2,4-7,20-24CRC Errors530Disabled

perf D-75

D

D-76


Output Example The output from perf.traffic is similar to the following:

perf.thresholdAlerts.setState

Syntax setState name enabledState

Purpose This command sets the enabled state of the specified counter threshold alert.


Number------1234567891011121314151617181920

Counter or Counter Set----------------------Link Resets SentLink Resets ReceivedOLS SentOLS ReceivedLink FailuresSync LossesSignal LossesProtocol ErrorsInvalid Tx WordsCRC ErrorsDiscarded FramesFrames Too ShortDelimiter ErrorsAddress ID ErrorsCls2 BusiedFrmsCls2 RejectedFrmsCls3 DiscardFrmsPhys Lnk Err SetLnk Seq Cnt SetLogic Lnk Err Set

name The name of a threshold alert as defined by the command perf.thresholdAlerts.counter.addAlert. (Refer to perf.thresholdAlerts.counter.addAlert on page D-70.)

enabledState Sets the counter threshold alert enabled state. Valid values are enabled and disabled. Boolean 1 and 0 values may also be substituted.



Command Example Root> perf thresholdAlerts setState checklinks enabled

perf.traffic

Syntax traffic portNumber

Purpose This command displays port traffic counters for a single port.


Command Example Root> perf traffic 2

Output The port traffic counter data is displayed as a table that includes the following properties.


◆ Rx% — The received link utilization percentage.

◆ Tx% — The transmitted link utilization percentage.

◆ Rx Frames — The number of Fibre Channel Class 2 and Class 3 frames that the port has received.

◆ Tx Frames — The number of Fibre Channel Class 2 and Class 3 frames that the port has transmitted.

◆ Rx Words — The number of 4-byte words in Class 2 and Class 3 frames that the port has received.

◆ Tx Words — The number of 4-byte words in Class 2 and Class 3 frames that the port has transmitted.

Output Example The output from perf.traffic is similar to the following:


Port 2 Statistic-----------Rx%Tx%RxFramesTxFramesRxWordsTxWords

Wrap----------N/A N/A 23 12 65 32

Count----------75302953184184295329531841842953

perf D-77

D

D-78


showThe show branch of the CLI command tree contains commands that display, but do not change, stored data values.The displayed output that results from these commands might not be identical to the output from the show commands that are within the other CLI command tree branches; for example, config.port.show.

The commands in the show branch can by used by either the Administrator or the Operator.

show.eventLog

Syntax eventLog [clear]

Purpose This command shows the contents of the event log as maintained in NV-RAM on the switch.


Command Example Root> show eventLog

Output The event log data are displayed as a table that includes the following properties.

◆ Date/Time — The date and time when the event occurred.

◆ Code — The event reason code.

◆ Severity — The severity of the event. The values are:

• Major —Unit operational (major failure).

• Minor —Unit operational (minor failure).

• Severe —Unit not operational.

• Info—Unit operational (information only).

◆ FRU — The FRU and FRU position, where applicable.

◆ Event Data — The 32-byte hexidecimal description of the event in words.



Output Example The output from show.eventLog is similar to the following:

Date/Time Code Severity FRU Event Data ---------------- ---- -------- ----- ---------------------------------- 04/12/01 10:58A 375 Major CTP-0 00010203 04050607 08090A0B 0C0D0E0F 04/12/01 09:58A 385 Severe CTP-0 00010203 04050607 08090A0B 0C0D0E0F 04/11/01 07:18P 395 Severe CTP-0 00010203 04050607 08090A0B 0C0D0E0F

show.features

Syntax features

Purpose This command displays a table of all installed feature sets and their states. The output is exactly the same as the output to config.features.show.


Command Example Root> show features

Output The features data is displayed as a table that includes the following properties.

Output Example The output from the show.features command displays as follows.

Installed Feature Set

The feature set installed using a feature key. Only installed keys are displayed.

Feature Individual features within each set. In many cases, there is only one feature within each feature set.

State The state of the individual feature. Fabric-wide features are displayed as Active/Inactive. Switch-centric features are displayed as Enabled/Disabled.

Installed Feature Set----------------------------Open Systems Management ServerEnterprise Fabric ExtensionsEnterprise Fabric ExtensionsEnterprise Fabric Extensions

Feature---------------OSMSFabric BindingSwitch BindingEnterprise Fabrics

State----EnabledActiveEnabledActive

show D-79

D

D-80


show.frus

Syntax frus

Purpose This command displays information about all FRUs.


Command Example Root> show frus

Output The FRU information is displayed as a table that includes the following properties.

◆ FRU — The FRU name. Unknown or Not Installed means the FRU is not installed.

◆ Position — The relative position of the FRU, that is, its slot.

◆ State — The state of the FRU. Values are:

• Active —the current module is active.

• Backup —this module is not currently being used, but it is available for immediate failover.

• Failed —the current module is failed.

◆ Serial Num — The serial number of the FRU.

◆ Part Num — The part number of the FRU.

◆ Beaconing — The beaconing state of the FRU (on or off).

◆ Pwr On Hrs — The power-on hours value for the FRU.

Output Example The output from show.frus is similar to the following:

FRU--------CTPPowerPowerFanFanFanFanFanFan

Position--------001012345

State------ActiveActiveActiveActiveActiveActiveActiveActiveActive

Serial Num----------118031905N/AN/AN/AN/AN/AN/AN/AN/A

Part Num--------------S802578490N/AN/AN/AN/AN/AN/AN/AN/A

Beacon------offN/AN/AN/AN/AN/AN/AN/AN/A

Pwr On Hrs----------799799799799799799799799799



show.ip.ethernet

Syntax ethernet

Purpose This command displays Ethernet attributes.


Command Example Root> show ip ethernet

Output The ethernet attributes data is displayed as a table that includes the following properties.

◆ IP Address — The IP address for the Ethernet adapter as set in the config.lan.ipAddress command.

◆ Gateway Address — The gateway address for the Ethernet adapter as set in the config.lan.gatewayAddress command.

◆ Subnet Mask — The subnet mask for the Ethernet adapter as set in the config.lan.subnetMask command.

Output Example The output from show.ip.ethernet is similar to the following:

LAN InformationIP Address: 144.49.10.15Gateway Address: 144.49.10.1Subnet Mask: 255.255.255.0

show D-81

D

D-82


show.loginServer

Syntax loginServer

Purpose This command displays information from the login server database for devices attached to this switch.


Command Example Root> show loginServer

Output The device information is displayed as a table that includes the following properties:

◆ Port — The port number where the device is attached.

◆ BB Crdt — The maximum number of remaining frames that can be transmitted without causing a buffer overrun condition at the receiver.

◆ RxFldSz — The buffer-to-buffer receive data field size from the FLOGI received from the attached N_Port.

◆ COS — The class of service (for example, 1; 2; 4; 5; 6; F; 1,2; 2,3).

◆ Port Name — The Port World Wide Name of the attached device.

◆ Node Name — The Node World Wide Name of the attached device.

Output Example The output from show.loginServer is similar to the following:

Port BB Crdt RxFldSz COS Port Name Node Name ---- ------- ------- --- ----------------------- ----------------------- 0 10 2,3 00:11:22:33:44:55:00:77 20:11:22:33:44:55:66:77 1 10 2 00:11:22:33:44:55:00:78 20:11:22:33:44:55:66:78 4 10 2,3 00:11:22:33:44:55:00:79 20:11:22:33:44:55:66:79 7 10 2,3 00:11:22:33:44:55:00:80 20:11:22:33:44:55:66:80 8 10 2 00:11:22:33:44:55:00:81 20:11:22:33:44:55:66:81 10 10 2,3 00:11:22:33:44:55:00:82 20:11:22:33:44:55:66:82 11 10 2,3 00:11:22:33:44:55:00:83 20:11:22:33:44:55:66:83 12 10 3 00:11:22:33:44:55:00:84 20:11:22:33:44:55:66:84 13 10 2,3 00:11:22:33:44:55:00:85 20:11:22:33:44:55:66:85 15 10 2,3 00:11:22:33:44:55:00:86 20:11:22:33:44:55:66:86



show.nameServer

Syntax nameServer

Purpose This command displays information from the name server database for devices attached to this switch.


Command Example Root> show nameServer

Output The device information data is displayed as a table that includes the following properties:

◆ Type — N, NL, F/NL, F, FL, E, B.

◆ Port Id — The 24-bit Fibre Channel address.



◆ COS — The class of service (for example, 1; 2; 3; 4; 5; 6; F; 1,2; 2,3).

◆ FC4 Types — The FC4 types registered for this device. The numbers in this field correspond to the list at the bottom of the table.

show D-83

D

D-84


Output Example The output from show.nameServer is similar to the following:

Type Port Id Port Name Node Name COS FC4 Types ---- ------- ----------------------- ----------------------- --- --------- N 010400 00:11:22:33:44:55:66:77 20:11:22:33:44:55:66:77 2,3 2 N 010500 00:11:22:33:44:55:66:78 20:11:22:33:44:55:66:78 2,3 0 N 010600 00:11:22:33:44:55:66:79 20:11:22:33:44:55:66:79 2,3 2 N 010700 00:11:22:33:44:55:66:80 20:11:22:33:44:55:66:80 2 2 N 010800 00:11:22:33:44:55:66:81 20:11:22:33:44:55:66:81 3 2 N 010900 00:11:22:33:44:55:66:82 20:11:22:33:44:55:66:82 3 2 N 010C00 00:11:22:33:44:55:66:83 20:11:22:33:44:55:66:83 2,3 2 N 010D00 00:11:22:33:44:55:66:84 20:11:22:33:44:55:66:84 2,3 2 N 010E00 00:11:22:33:44:55:66:85 20:11:22:33:44:55:66:85 2 5 N 010F00 00:11:22:33:44:55:66:86 20:11:22:33:44:55:66:86 2 4 N 011200 00:11:22:33:44:55:66:87 20:11:22:33:44:55:66:87 2,3 2 N 011300 00:11:22:33:44:55:66:88 10:11:22:33:44:55:66:88 2,3 2

FC4 Types 0: ISO/IEC 8802-2 LLC 1: ISO/IEC 8802-2 LLC/SNAP 2: SCSI-FCP 3: SCSI-GPP 4: IPI-3 Master 5: IPI-3 Slave 6: IPI-3 Peer 7: CP IPI-3 Master 8: CP IPI-3 Slave 9: CP IPI-3 Peer 10: SBCCS-Channel 11: SBCCS-Control Unit 12: FC-SB-2 Channel to Control Unit 13: FC-SB-2 Control Unit to Channel 14: Fibre Channel Service 15: FC-FG 16: FC-SW 17: FC-AL 18: SNMP 19: HIPPI-FP 20: Vendor Unique



show.nameServerExt

Syntax nameServerExt

Purpose This command displays information from the name server database for devices attached to this director. It displays the exact same information as shown in the show.nameServer command, but also includes display of the Symbolic Nameserver information. Note that it is possible to have more than one device per port for any public loop devices attached to an FL_Port.

The symbolic nameserver information will force the CLI to wrap its display several times per node. For this reason, this command is supported only in comma-delimited mode. The user will receive an error message if this command is issued in tabular mode.


Command Example Root> show nameServerExt

Output The device information data is displayed as a table that includes the following properties.

◆ Type — N, NL, F/NL, F, FL, E, B.

◆ Port Id — The 24-bit Fibre Channel address.



◆ COS — The class of service (for example, 1; 2; 3; 4; 5; 6; F; 1,2; 2,3).

◆ FC4 Types — The FC4 types registered for this device. The numbers in this field correspond to the list at the bottom of the table.

◆ SymNodeName — 255-character representation of the Symbolic Node Name.

◆ SymPortName — 255-character representation of the Symbolic Port Name.

show D-85

D

D-86


Output Example The output from show.nameServerExt is similar to the following:

Type, Port Id, Port Name, Node Name, COS, FC4 Types, SymNodeName, SymPortName,

N, 010400, 00:11:22:33:44:55:00:77, 20:11:22:33:44:55:66:77, 2-3, 2, Node Name A, Port Name A,

N, 010500, 00:11:22:33:44:55:01:77, 20:11:22:33:44:55:66:77, 2-3, 0, This Is Symbolic Node Name B, Symbolic Port Name B Is Slightly Longer

N, 010600, 00:11:22:33:44:55:66:02, 20:11:22:33:44:55:66:77, 2-3, 2, , ,

FL, 000001, 00:11:22:33:44:55:66:03, 20:11:22:33:44:55:66:77, 2, 0, Loop Node 1, Loop Port 7,

FL, 000002, 00:11:22:33:44:55:66:04 20:11:22:33:44:55:66:77, 3, 2, Loop Node 2, Loop Port 7,

sshow.port.config

Syntax config

Purpose This command shows the port configuration for all ports.


Command Example Root> show port config

Output The port configuration attributes are displayed as a table that includes the following properties.


◆ Name — The name of the port as set in the config.port.name command.

◆ Blocked — The blocked state of the port as set in the config.port.blocked command.

◆ Ext Dist — The extended distance state as set in the config.port.extDist command.

◆ Type — The port type as set in the config.port.type command.

◆ Speed — The port speed as set in the config.port.speed command.

Output Example The output from show.system is similar to the following:



Port Name Blocked Ext Dist Type Speed---- ------------------------ ------- -------- ----- --------- 0 Port 1 false false fPort 1 Gb/sec1 Port 2 true true fPort 1 Gb/sec2 Port 3 false false gPort 1 Gb/sec3 Port 4 false false fPort 2 Gb/sec4 Port 5 true true fPort 2 Gb/sec5 Port 6 false false fPort 2 Gb/sec6 Port 7 true true fPort 1 Gb/sec7 Port 8 false false fPort Negotiate8 Port 9 false true fPort 1 Gb/sec 9 Port A false false fPort 1 Gb/sec 10 Port B false false fPort 2 Gb/sec 11 Port C false false fPort 2 Gb/sec 12 Port D false false fPort 1 Gb/sec 13 Port E false false fPort 1 Gb/sec 14 Port F false false fPort 1 Gb/sec 15 Port X false false fPort 1 Gb/sec

show.port.info

Syntax info

Purpose This command displays port information for all ports.


Command Example Root> show port info

Output The port information data is displayed as a table that includes the following properties.


◆ WWN — The World Wide Name of the port.

◆ OpSpeed — The current operating speed (1 Gb/sec, 2 Gb/sec, or Not Established).

◆ SpeedCap — The current transceiver capability speed (1 Gb/sec or 2 Gb/sec).

show D-87

D

D-88


Output Example The output from show.port.info is similar to the following:

Port WWN OpSpeed SpeedCap ---- ----------------------- -------- -------- 0 10:00:80:00:11:22:33:44 1 Gb/sec 2 Gb/sec 1 10:00:80:01:11:22:33:44 1 Gb/sec 2 Gb/sec 2 10:00:80:02:11:22:33:44 1 Gb/sec 2 Gb/sec 3 10:00:80:03:11:22:33:44 1 Gb/sec 2 Gb/sec 4 10:00:80:04:11:22:33:44 2 Gb/sec 2 Gb/sec 5 10:00:80:05:11:22:33:44 2 Gb/sec 2 Gb/sec 6 10:00:80:06:11:22:33:44 2 Gb/sec 2 Gb/sec 7 10:00:80:07:11:22:33:44 2 Gb/sec 2 Gb/sec 8 10:00:80:08:11:22:33:44 2 Gb/sec 2 Gb/sec 9 10:00:80:09:11:22:33:44 2 Gb/sec 2 Gb/sec 10 10:00:80:10:11:22:33:44 1 Gb/sec 2 Gb/sec 11 10:00:80:11:11:22:33:44 1 Gb/sec 2 Gb/sec 12 10:00:80:12:11:22:33:44 1 Gb/sec 2 Gb/sec 13 10:00:80:13:11:22:33:44 1 Gb/sec 2 Gb/sec 14 10:00:80:14:11:22:33:44 1 Gb/sec 2 Gb/sec 15 10:00:80:15:11:22:33:44 1 Gb/sec 2 Gb/sec

show.port.status

Syntax status

Purpose This command displays port status for all ports.


Command Example Root> show port status

Output The port status data is displayed as a table that includes the following properties.


◆ State — The port state; for example:

• Segmented E_Port

• Invalid Attachment

• Not Installed

• Online

• Offline

• Not Operational

• No Light



• Testing

• Port Failure

• Link Reset

◆ Type — The operational port type:

• If the configured port type is F_Port or E_Port, this value will match the configured type.

• If the configured type is G_Port, this value can be E_Port, F_Port, or G_Port, depending on what is connected to the port.

◆ Attached WWN — The World Wide Name of the device or switch attached to the port, if one is attached.

◆ Beaconing — The beaconing state for the port (true or false).

◆ Reason — An optional message number that indicates if the port has a segmented ISL, a port binding violation has occurred, or the port is inactive. The message description for this message number is provided at the bottom of the table:

• If the operational state is Segmented E_Port:01 = Segment not defined02 = Incompatible operating parameters03 = Duplicate Domain ID(s)04 = Incompatible zoning configurations05 = Build fabric protocol error06 = No principal switch07 = No response from attached switch08 = ELP retransmission failure timeout

• If the operational state is Invalid Attachment:09 = Unknown10 = ISL connection not allowed on this port11 = ELP rejected by the attached switch12= Incompatible switch at other end of the ISL13 = External loopback adapter connected to the port14 = N_Port connection not allowed on this port15 = Non-EMC switch at other end of the ISL16 = ISL connection not allowed on this port17 = ISL connection not allowed to external fabrics18 = Port binding violation—unauthorized WWN19 = Unresponsive node connected to port20 = Incompatible security attributes

show D-89

D

D-90


21 = Fabric Binding violation22 = Authorization failure23 = Switch Binding violation

• If the operational state is Inactive:24 = Inactive – RC 025 = No Serial Number26 = Feature Not Enabled

Output Example The output from show.port.status is similar to the following:

Port----0123456789101112131415

State----------------OnlineOnlineNo LightOfflineOnlinePort FailureLink ResetSegmented E_PortOnlineOfflineInactiveOnlineNo LightOnlineInvalid AttachmentOnline

Type-----fPortgPortfPortePortgPortfPortgPortePortePortfPortePortfPortfPortfPortfPortfPort

Attached WWN-----------------------10:00:80:00:11:22:33:4410:00:80:00:11:22:33:4510:00:80:00:11:22:33:5510:00:80:00:11:22:33:0010:00:80:00:11:22:33:5710:00:80:00:11:22:33:4610:00:80:00:11:22:33:6310:00:80:00:11:22:33:4710:00:80:00:11:22:33:8810:00:80:00:11:22:33:4910:00:80:00:11:22:33:5010:00:80:00:11:22:33:5310:00:80:00:11:22:33:5610:00:80:00:11:22:33:5910:00:80:00:11:22:33:6410:00:80:00:11:22:33:66

Beaconing---------falsetruetruefalsefalsefalsefalsefalsefalsefalsefalsefalsefalsefalsefalsefalse

Reason------

02

26

15

03: Duplicate Domain ID(s)04: Switch Speed Conflict10: ISL connection not allowed on this port



show.port.technology

Syntax technology

Purpose This command displays port technology information for all ports.


Command Example Root> show port technology

Output The port technology data is displayed as a table that includes the following properties.


◆ Connectr — The port connector type (LC, MT_RJ, MU, Internal).

◆ Transcvr — The transceiver type (Long LC, Short, Short OFC, Long LL, Long Dist).

◆ Distance — The distances supported (Short, Intermediate, Long, Very Long).

◆ Media — The media type (M-M 62.5um, M-M 50um, M-M 50,62.5um, S-M 9um, Copper).

Output Example The output from show.port.technology is similar to the following:.

Port----0123456789101112131415

Connectr--------LCLCLCMT_RJMT_RJMT_RJLCLCLCLCLCLCLCLCLCLC

Transcvr---------Long LCLong LCLong LCLong LCLong LCLong LCLong LCLong LCLong LCLng LCLong LCLong LCLong LCLong LCLong LCLong LC

Distance------------LongLongLongLongLongLongLongLongLongLongLongLongLongLongLongLong

Media-----------M-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50umM-M 50um

show D-91

D

D-92


show.security.fabricBinding

Syntax fabricBinding

Purpose This command displays the fabric binding configuration saved on the fabric. The command performs the same function as config.security.fabricBinding.showActive.


Command Example Root> show security fabricBinding

Output The fabric binding configuration data is displayed as a table that includes the following properties.

Output Example The output from the show.security.fabricBinding command displays as follows.

Fabric Binding State: Active RestrictingDomain 1 (00:11:22:33:44:55:66:77)Domain 2 (88:99:AA:BB:CC:DD:EE:FF)Domain 14 (11:55:35:45:24:78:98:FA)

show.security.portBinding

Syntax portBinding

Purpose This command shows the port binding configuration for all ports.


Command Example Root> show security portBinding


The active fabric binding state: Inactive or Active Restricting

Fabric Membership List

The active fabric membership list.



Output The port binding configuration data is displayed as a table that includes the following properties.


◆ Port Binding — The state of port binding for the specified port (Active or Inactive).

◆ Bound WWN — The WWN of the device that is bound to the specified port. If this field is blank, no device is bound to the specified port.

Output Example The output from show.ip.ethernet is similar to the following:

Port Port Binding Bound WWN ---- ----------- ----------------------- 0 Active AA:00:AA:00:AA:00:AA:00 1 Inactive 00:00:00:00:00:00:00:00 2 Inactive CC:33:44:55:CC:33:44:55 3 Active 00:00:00:00:00:00:00:00 4 Inactive 00:00:00:00:00:00:00:00 5 Inactive 00:00:00:00:00:00:00:00 6 Inactive 00:00:00:00:00:00:00:00 7 Inactive 00:00:00:00:00:00:00:00 8 Inactive 00:00:00:00:00:00:00:00 9 Inactive 00:00:00:00:00:00:00:00 10 Inactive 00:00:00:00:00:00:00:00 11 Inactive 00:00:00:00:00:00:00:00 12 Inactive 00:00:00:00:00:00:00:00 13 Inactive 00:00:00:00:00:00:00:00 14 Inactive 00:00:00:00:00:00:00:00 15 Inactive 00:00:00:00:00:00:00:00

show.security.switchBinding

Syntax switchBinding

Purpose This command displays the switch binding configuration.


Command Example Root> show security switchBinding

show D-93

D

D-94


Output The switch binding configuration data is displayed as a table that includes the following properties.

Output Example The output from the show.security.switchBinding command appears as follows:

Switch Binding State: Enabled and Restricting E Ports00:11:22:33:44:55:66:7788:99:AA:BB:CC:DD:EE:FF11:55:35:45:24:78:98:FA

show.switch

Syntax switch

Purpose This command displays switch attributes.


Command Example Root> show switch

Output The switch attributes data is displayed as a table that includes the following properties.

◆ State — The state of the switch (for example, on line or off line).

◆ BB Credit — The BB _Credit value.

◆ R_A_TOV — The R_A_TOV as set in the config.switch.raTov command.

◆ E_D_TOV — The E_D_TOV as set in the config.switch.edTov command.

◆ Preferred Domain Id — The domain ID as set in the config.switch.domainId command.

◆ Switch Priority — The switch priority as set in the config.switch.priority command.

Switch Binding State

◆ Disabled◆ Enabled and Restricting F_Ports◆ Enabled and Restricting E_Ports◆ Enabled and Restricting All Ports

Switch Membership List

The active switch membership list.



◆ Speed — The switch speed as set in the config.switch.speed command.

◆ Rerouting Delay — The rerouting delay as set in the config.switch.rerouteDelay command.

◆ Operating Mode — The operating mode (Open Systems).

◆ Interop Mode — The interoperability mode as set in the config.switch.interopMode command.

◆ Active Domain Id — The active domain ID of the switch. This ID may or may not be the same as the preferred domain ID.

◆ World Wide Name — The World Wide Name for the switch.

◆ Insistent Domain Id — The configured Insistent domain ID state as set in the config.switch.insistDomainId command.

◆ Domain RSCN — The configured Domain RSCN state as set in the config.switch.domainRSCN command.

◆ Zoning RSCN — The configured Zoning RSCN state as set in the config.switch.zoningRSCN command.

Output Example The output from show.switch is similar to the following:

Switch InformationState: OnlineBB Credit: 2R_A_TOV: 20E_D_TOV: 4Preferred Domain Id: 1Switch Priority: DefaultSpeed: 2 Gb/secRerouting Delay: EnabledOperating Mode: Open SystemsInterop Mode: Open Fabric 1.0Active Domain Id: 1World Wide Name: 10:00:08:00:88:00:21:07Insistent Domain Id: EnabledDomain RSCN: EnabledZoning RSCN: Enabled

show D-95

D

D-96


show.system

Syntax system

Purpose This command displays a set of system attributes.


Command Example Root> show system

Output The system attributes are displayed as a table that includes the following properties.

◆ Name — The system name as set in the config.system.name command.

◆ Description — The system description as set in the config.system.description command.

◆ Contact — The system contact as set in the config.system.contact command.

◆ Location — The system description as set in the config.system.description command.

◆ Date/Time — The system date and time as set in the config.system.date command.

◆ Serial Number — The serial number for the system.

◆ Type Number — The type number for the system.

◆ Model Name — The model name for the system (for example, DS-24M2).

◆ Model Number — The model number for the system. All products have the model number 001, except 1 Gb switch models, which are 002.

◆ EC Level — The engineering change level installed.

◆ Firmware Version — The current firmware version installed.

◆ Beaconing — The enabled state of unit beaconing (enabled or disabled).



Output Example The output from show.system is similar to the following:

show.thresholdAlerts.alert

Syntax alert

Purpose This command provides the name, type, and enabled state of each threshold alert. This command displays information about all threshold alerts, including both counter threshold alerts (CTAs) and throughput threshold alerts (TTAs).


Command Example Root> show thresholdAlerts alert

Output The threshold alert data appears as a table that includes the following properties.

◆ Date/Time — Date and time of the threshold alert

◆ Name — Name of the threshold alert, truncated (if necessary) to 45 characters

◆ Type — Trigger statistic or threshold type of the alert (abbreviated to 17 characters):

• Tx Util — (TTA) Transmit Utilization

• Rx Util — (TTA) Receive Utilization

• Tx/Rx Util — (TTA) Transmit or Receive Utilization

• Link Resets Sent — (CTA) Link Resets Sent

• Link Resets Received — (CTA) Link Resets Received

System InformationName: Joe’s SwitchDescription: Connectrix DS-24M2 SwitchContact: JoeLocation: EverywhereDate/Time: 10/16/2001 10:34:01AMSerial Number: 123456789Type Number: 1Model Name; DS-24M2Model Number; 001EC Level: 1Firmware Version: 01.03.00 Build 34Beaconing: Disabled

show D-97

D

D-98


• OLS Sent — (CTA) OLS Sent

• OLS Received — (CTA) OLS Received

• Link Failures — (CTA) Link Failures

• Sync Losses — (CTA) Sync Losses

• Signal Losses — (CTA) Signal Losses

• Protocol Errors — (CTA) Primitive Sequence Errors/Protocol Errors

• Invalid Tx Words — (CTA) Invalid Tx Words

• CRC Errors — (CTA) CRC Errors

• Discarded Frames — (CTA) Discarded Frames

• Frames Too Short — (CTA) Frames Too Short

• Delimiter Errors — (CTA) Delimiter Errors

• Address ID Errors — (CTA) Address ID Errors

• Cls2 BusiedFrms — (CTA) Class 2 Busied Frames

• Cls2 RejectedFrms — (CTA) Class 2 Rejected Frames

• Cls3 DiscardFrms — (CTA) Class 3 Discarded Frames

• Phys Lnk Err Set — (CTA) Physical Link Errors Summed Set

• Lnk Seq Cnt Set — (CTA) Link Sequence Counts Summed Set

• Logic Lnk Err Set — (CTA) Logical Link Errors Summed Set

◆ State — The enabled state of the CTA: enabled or disabled

Output Example The output from show.thresholdAlerts.alert is similar to the following:

Name Type State------------------------------------ ----------------- --------Throughput Threshold #1 Rx Util EnableThreshold for CRC CRC Errors DisabledSafety #2 Logic Lnk Err Set EnabledSafety #1 Cls2 BusiedFrms Disabled



show.thresholdAlerts.log

Syntax log [clear]

Purpose This command shows the contents of the threshold alert log. This log shows all the threshold alerts that have been triggered, including both counter threshold alerts (CTAs) and throughput threshold alerts (TTAs).


Command Example Root> show thresholdAlerts log

Output The threshold alert log data displays as a table that includes the following properties.

◆ Date/Time — Date and time of the threshold alert

◆ Name — Name of the threshold alert, truncated (if necessary) to 22 characters

◆ Port — (CTA only) Type of threshold alert

◆ Type — Trigger statistic or threshold type of the alert (abbreviated to 17 characters):

• Tx Util — (TTA) Transmit Utilization

• Rx Util — (TTA) Receive Utilization

• Tx/Rx Util — (TTA) Transmit or Receive Utilization

• Link Resets Sent — (CTA) Link Resets Sent

• Link Resets Received — (CTA) Link Resets Received

• OLS Sent — (CTA) OLS Sent

• OLS Received — (CTA) OLS Received

• Link Failures — (CTA) Link Failures

• Sync Losses — (CTA) Sync Losses

• Signal Losses — (CTA) Signal Losses

• Protocol Errors — (CTA) Primitive Sequence Errors/Protocol Errors

• Invalid Tx Words — (CTA) Invalid Tx Words

clear This optional parameter causes all reroute log entries to be cleared.

show D-99

D

D-100


• CRC Errors — (CTA) CRC Errors

• Discarded Frames — (CTA) Discarded Frames

• Frames Too Short — (CTA) Frames Too Short

• Delimiter Errors — (CTA) Delimiter Errors

• Address ID Errors — (CTA) Address ID Errors

• Cls2 BusiedFrms — (CTA) Class 2 Busied Frames

• Cls2 RejectedFrms — (CTA) Class 2 Rejected Frames

• Cls3 DiscardFrms — (CTA) Class 3 Discarded Frames

• Phys Lnk Err Set — (CTA) Physical Link Errors Summed Set

◆ Value — Increment or utilization value of the alert

◆ Interval — Time interval of the alert

Output Example The output from show.thresholdAlerts.log is similar to the following:

Date/Time Name Port Type Value Int---------------- ------------- ----- ----------------- ----- ---05/26/02 10:58A CTA Alert #4 2 Cls3 DiscardFrms 250 1005/24/02 12:01A CTA Alert #4 2 Cls3 DiscardFrms 250 1005/22/02 10:58A My test CTA 43 CRC Errors 35 3005/20/02 08:01P TTA Test #3 2 Tx Util 85 12003/01/02 02:58A CTA Alert #1 130 CRC Errors 100 60

show.zoning

Syntax zoning

Purpose This command shows the zoning configuration saved on the fabric.


Command Example Root> show zoning




Output Example The output from show.zoning is similar to the following:

Active ZoneSet-------------Default Zone Enabled: FalseZoneSet: TheUltimateZoneSet

Zone: TheUltimateZoneZoneMember: Domain 10, Port 6ZoneMember: Domain 15, Port 2ZoneMember: Domain 2, Port 63ZoneMember: 10:00:00:00:C9:22:9B:64ZoneMember: 10:00:00:00:C9:22:9B:BD

Zone: TheNotSoUltimateZoneZoneMember: 10:00:00:00:C9:22:9B:ABZoneMember: 10:00:00:00:C9:22:9B:C6ZoneMember: 10:00:00:00:C9:22:9B:AB

Zone: TheNotUltimateAtAllZoneZoneMember: Domain 2, Port 63

show D-101

D

D-102



EInvisible Body Tag

This appendix lists the physical characteristics and operating environment of the DS-24M2.

◆ Specifications ..................................................................................... E-2

Specifications

Specifications E-1

E

E-2

Specifications

Specifications

Table 0-1

PhysicalCharacteristics

Dimensions Height: 1.7 in (4.3 cm)

Width: 17.1 in (43.4 cm)

Depth: 19 in (48.3 cm)

Weight 17 lbs (7.7 kg)

Airflow Clearance in Rack

• Top and bottom: None required• Front and rear: 3.0 in. (7.6 cm)• Sides: 0.5 in. (1.3 cm)

Shock and Vibration Tolerance

60 Gs for 10 milliseconds without nonrecoverable errors

Acoustical Noise 70 dB “A” scale

Heat Dissipation 167 BTU/hr

Table 0-2

PowerRequirements

Input voltage 90 to 264 VAC, 47 to 63 Hz

Current Plan for single-phase or phase-to-phase connections and 5-amp dedicated service.

Average Power Consumption

• 120Vrms Irms = 1.61 A• 220Vrms Irms = 0.94 A


ESpecifications

Table 0-3

Storage andShipping

Environment

Protective packaging must be provided to protect the DS-16M under all shipping methods (domestic and international).

Shipping Temperature -40° F to 140° F (-40° C to 60° C)

Storage Temperature 34° F to 140° F (1° C to 60° C)

Shipping Relative Humidity

5% to 100%

Storage Relative Humidity

5% to 80%

Maximum Wet-Bulb Temperature

84° F (29° C)

Maximum Altitude 40,000 ft (12,192 m)

Table 0-4

OperatingEnvironment

Temperature 40° F to 104° F (4° C to 40° C)

Relative Humidity 8% to 80%


81° F (27° C)


Inclination 10° maximum

Specifications E-3

E

E-4

Specifications

Table 0-5

Storage andShipping

Environment

Protective packaging must be provided to protect the DS-16M under all shipping methods (domestic and international).

Shipping Temperature -40° F to 140° F (-40° C to 60° C)

Storage Temperature 34° F to 140° F (1° C to 60° C)

Shipping Relative Humidity

5% to 100%

Storage Relative Humidity

5% to 80%


84° F (29° C)


Table 0-6

OperatingEnvironment

Temperature 40° F to 104° F (4° C to 40° C)

Relative Humidity 8% to 80%


81° F (27° C)


Inclination 10° maximum


Fnvisible Body Tag

This appendix reviews the EMC process for detecting and resolving software problems, and provides essential questions that you should answer before contacting the EMC Customer Support Center.

◆ Overview of Detecting and Resolving Problems ..........................F-2◆ Troubleshooting the Problem ...........................................................F-3◆ Before Calling the Customer Support Center ................................F-4◆ Documenting the Problem................................................................F-5◆ Reporting a New Problem ................................................................F-6◆ Sending Problem Documentation....................................................F-7

Customer Support

Customer Support F-1

F

F-2

Customer Support

Overview of Detecting and Resolving ProblemsEMC software products are supported directly by the EMC Customer Support Center in the United States.

EMC uses the following process to resolve customer problems with its software products (Figure F-1).

Figure F-1 Problem Detection and Resolution Process

ProblemDetection

Refer to thisCustomer Support

Appendix for Instructions

Collect ProblemInformation as

Directed

Contact the EMC CustomerSupport Center:

U.S.:Canada:Worldwide:

(800) SVC-4EMC(800) 543-4SVC(508) 497-7901

Confirm that theProblem is Software

Related

Call will be Directedto an EMC SoftwareSupport Engineer

Problem isTracked andManaged toResolution


FCustomer Support

Troubleshooting the ProblemPlease perform the relevant diagnostic steps before you contact the EMC Customer Support Center:

1. Read the documentation carefully.

2. Reconstruct the events leading up to the problem and describe them in writing.

3. Run some test cases to reproduce the problem.

If you encounter a problem that requires technical programming or analysis, call the nearest EMC office or contact the EMC Customer Support Center at one of the following numbers:

United States: (800) 782-4362 (SVC-4EMC)

Canada: (800) 543-4782 (543-4SVC)

Worldwide: (508) 497-7901

Please do not request a specific support representative unless one has already been assigned to your particular system problem.

For additional information on EMC products and services available to customers and partners, refer to the EMC Powerlink website at:

http://powerlink.EMC.com

Troubleshooting the Problem F-3

F

F-4

Customer Support

Before Calling the Customer Support CenterHave the following information available before calling the Customer Support Center or your support representative (if one has been assigned to you):

❑ Your company name

❑ Your name

❑ Your phone number

❑ For an existing problem, the problem tracking system ID, if one was previously assigned to the problem by a support representative

❑ For an MVS problem, the JESLOG, SYSPRINT, all STDOUT DD members of the server job output and similar output for the client, and the relevant portion of the SYSLOG


FCustomer Support

Documenting the ProblemIf the EMC Customer Support Center requests information regarding the problem, please document it completely, making sure to include the following information:

❑ Your company name and address

❑ Your name

❑ Your telephone number

❑ The importance of the problem, so that it can be assigned a priority level

To expedite the processing of your support request, you can photocopy this list and include it with the package.

Documenting the Problem F-5

F

F-6

Customer Support

Reporting a New ProblemFor a new problem, please provide the following information:

❑ Release level of the software that you are running

❑ Software installation parameters

❑ Host type on which you are running

❑ Operating system you are running and its release number

❑ Functions of the software that you are running

❑ Whether you can reproduce the problem

❑ Previous occurrences of the problem

❑ Whether the software has ever worked correctly

❑ Time period that the software did work properly

❑ Conditions under which the software worked properly

❑ Changes to your system between the time the software worked properly and the problem began

❑ Exact sequence of events that led to the system error

❑ Message numbers and complete text of any messages that the system produced

❑ Log file dated near the time the error occurred

❑ Results from tests that you have run

❑ Other related system output

❑ Other information that may help solve the problem


FCustomer Support

Sending Problem DocumentationUse one of the following methods to send documentation of the problem to the EMC Customer Support Center:

◆ E-mail

◆ FTP

◆ U.S. mail to the following address:

EMC Customer Support Center45 South StreetHopkinton, MA 01748-9103

If the problem was assigned a number or a specific support representative, please include that information in the address as well.

Sending Problem Documentation F-7

F

F-8

Customer Support


Glossary

This glossary contains terms related to EMC Connectrix. Many of these terms are used in this manual. The glossary includes terms and definitions from:

• The Dictionary of Computing, ZC20-1699.

• The American National Standard Dictionary for Information Systems, ANSI X3.172-1990, copyright 1990, by the American National Standards lnstitute (ANSI). Copies can be purchased from the American National Standards Institute, 1430 Broadway, New York, New York 10018.

• The ANSI/EIA Standard - 440A: Fiber Optic Terminology, copyright 1989 by the Electronic Industries Association (EIA). Copies can be purchased from the Electronic lndustries Association, 2001 Pennsylvania Avenue N.W., Washington, D.C. 20006.

• The Information Technology Vocabulary, developed by Subcommittee 1, Joint Technical Committee 1, of the lnternational Organization for Standardization and the lnternational Electrotechnical Commission (ISO/IEC JTCI/SCI).

Connectrix DS-24M2 User Guide g-1

g-2

Glossary

AAccess Control List of all devices that can access other devices across the network

and the permissions associated with that access. See also persistent binding and zoning.

Active Domain ID The Domain ID actively being used by a switch. It is assigned to a switch by the principal switch.

Active Zone Set A Zone Set that is currently enabled. (Only one Zone Set at a time can be active.) Zoning across the fabric is determined by the characteristics of the active Zone Set.

Agent Software that processes queries on behalf of an application and returns replies.

Alarm An SNMP message notifying an operator of a network problem.

Any-to-Any PortConnectivity

For each source port, software configured hardware routing tables that define the destination ports with which the source port is allowed to communicate.

Application (1) The use to which an information processing system is put, for example, a payroll application, an airline reservation application, a network application. (2) A collection of software components used to perform specific types of work on a computer.

Arbitration The process of selecting one respondent from a collection of several candidates that request service concurrently.

ASIC Application-Specific Integrated Circuit, a circuit designed for a specific purpose, such as implementing lower-layer Fibre Channel protocols (FC-0). ASICs contrast with general-purpose devices such as memory chips or microprocessors, which can be used in many different applications.

ASCII American Standard Code for Information Interchange.

Audit Log A log containing summaries of actions taken by a Connectrix Management software user, recording an audit trail of changes. For example: adding, modifying, or deleting user or product administration records the operation, including the date and time, in the audit log.


Glossary

Authentication Verification of the identity of a process or person.

BBB_Credit See Buffer-to-Buffer Credit.

Beaconing Repeated transmission of a beacon light and message until the error is corrected or bypassed.

BER See Bit Error Rate.

Bidirectional In Fibre Channel, the capability to simultaneously communicate at maximum speeds (100 Mbps) in both directions over a link.

Bit Error Rate Ratio of received bits that contain errors to total of all bits transmitted.

Blocked Port Devices communicating with a blocked port are prevented from logging in to a Connectrix switch or communicating with other devices attached to the Connectrix switch. A blocked port continuously transmits the offline sequence (OLS).

Bridge A device that connects and passes packets between two network segments that use the same communications protocol.

Broadcast Send a transmission to all N_Ports on a fabric.

Broadcast Frames Data packet, also known as a broadcast packet, whose destination address specifies all computers on a network. See also multicast.

Buffer Storage area for data in transit. Buffers compensate for differences in processing speeds between devices.

Buffer-to-Buffer Credit The maximum number of frames a port can transmit without receiving a receive ready signal from the receiving device.

Build Fabric A fabric rebuilding process that retrieves information from all switches in the fabric and assigns the principal switch.

A Build Fabric follows any of these occurrences:

• Multiple switches are interconnected to form a fabric.

• A switch is removed from the fabric.


g-4

Glossary

• A switch with Operating Mode set to Open Systems and Interop Mode set to McDATA 1.0 is added to the fabric. (Refer to Configuring Operating Parameters on page 5-4.)

• An ISL is removed.

CCall Home A product feature that allows the Connectrix service processor to

automatically dial out to a support center and report system problems. The support center server accepts calls from the Connectrix service processor, logs reported events, and can notify one or more support center representatives. Telephone numbers and other information are configured through the Windows NT dial-up networking application. The Call Home function can be enabled and disabled through the Product Manager.

Channel Point-to-point link that transports data from one point to the other.

Class 2 Fibre ChannelService

In Class 2 service, the fabric and destination N_Ports provide connectionless service with notification of delivery or nondelivery between the two N_Ports.

Class 3 Fibre ChannelService

Class 3 service provides a connectionless service without notification of delivery between N_Ports. (This is also known as datagram service.) The transmission and routing of Class 3 frames is the same as for Class 2 frames.

CLI Command line interface.

Command LineInterface

A display line on the screen, onto which the user enters commands.

Community A relationship between an SNMP agent and a set of SNMP managers that defines authentication, access control, and proxy characteristics.

Community Name A name that represents an SNMP community that the agent software recognizes as a valid source for SNMP requests. An SNMP management program that sends an SNMP request to an agent program must identify the request with a community name that the agent recognizes or the agent discards the message as an authentication failure. The agent counts these failures and reports the count to the manager program upon request, or sends an authentication failure trap message to the manager program.


Glossary

Community Profile Information that specifies which management objects are available to what management domain or SNMP community name.

Connectionless Nondedicated link. Typically used to describe a link between nodes that allows the switch to forward Class 2 or Class 3 frames as resources (ports) allow. Contrast with the dedicated bandwidth that is required in a Class 1 Fibre Channel Service point-to-point link.

Connectivity Unit A hardware component that contains hardware (and possibly software) that provides Fibre Channel connectivity across a fabric. Connectrix switches are example of a Connectivity Unit.

ConnectrixManagement

Software

The software application that implements the management user interface for all managed products. The Connectrix Management software can run either locally on the Connectrix service processor or remotely on a user workstation.

Connectrix ServiceProcessor

A PC shipped with a product for the sole purpose of running the Connectrix Management software.

Credit A numeric value that determines the flow control value for a switch handling Class 2 traffic in a fabric.

CTP Control Processor, a circuit card or subsystem that contains the microprocessor director. The CTP also initializes hardware components of the system after power-on. A 10/100 Mbps RJ-45 twisted pair connector is located on the CTP to connect to the Ethernet LAN and communicate with the Connectrix service processor or SNMP management station.

DDASD Direct Access Storage Device.

Default Pertaining to an attribute, value, or option that is assumed when none is explicitly specified.

Default Zone Contains all attached devices that are not members of any active Zone.

Device (1) A piece of equipment, such as a server or storage device, that is attached to a Connectrix switch or a similar product. A device as defined here is not controlled by the Connectrix Product Manager and its operating parameters. (2) In EMC Symmetrix, a uniquely


g-6

Glossary

addressable physical or logical part of the Symmetrix subsystem, such as a disk. (This description is presented here only to clarify a term used in other EMC documents.)

Dialog Box A pop-up window containing informational messages or fields to be modified with desired options. This term is often used interchangeably with window.

DID Destination ID, the address identifier that indicates the targeted destination of the transmitted frame.

Director (1) An Enterprise-Class Fibre Channel switch. The Connectrix ED-64M Director is a fully redundant Fibre Channel switch, containing: dual power supplies, fan modules, CTP cards, SBARs, and multiple FPMs, all hot-swappable. (2) A board-level module in the Symmetrix that provides the interface between host channels (via an associated adapter module in the Symmetrix) and Symmetrix disk devices. (This description is presented here only to clarify a term used in other EMC documents.)

DNS See Domain Name Service Name.

Domain ID A number (1 to 31) that uniquely identifies a switch in a fabric. A distinct Domain ID is allocated to each switch in the fabric by the principal switch.

Domain NameService Name

Host or node name for a system that is translated to an IP address through a Name Server. All DNS names have a host name component and, if fully qualified, a domain component, such as host1.abcd.com. In this example, host1 is the host name.

DWDM Dense Wavelength Division Multiplexing, a process in which different channelsof data are carried at different wavelengths over one pair of fiber optic links. This is in contrast with a conventional fiber optic system in which only one channel is carried over a single wavelength traveling through a single fiber.

EE_D_TOV See Error Detect Time Out Value.

E_Port Expansion Port, a physical interface within the Fibre Channel switch that attaches to another E_Port on a Fibre Channel switch through an interswitch link.


Glossary

Embedded WebServer

A management interface embedded on the switch’s code that offers features similar to (but not as robust as) the Connectrix Manager and Product Manager.

Error Detect Time OutValue

Defines the time the switch waits for an expected response before declaring an error condition. The error detect time out value (E_D_TOV) can be set within a range of two-tenths of a second to one second using the Connectrix switch Product Manager.

Error Message An indication that an error has been detected. See also Information Message and Warning Message.

ESD Electrostatic discharge.

Ethernet A baseband LAN that allows multiple station access to the transmission medium at will without prior coordination and which avoids or resolves contention.

Event Log A record of significant events that have occurred on a Connectrix switch, such as FRU failures, degraded operation, and port problems.

EWS See Embedded Web Server.

Expansion Port A physical interface that attaches to another E_Port on a Fibre Channel switch through an interswitch link to form a multiswitch fabric.

Explicit Fabric Login F_Ports support a data field size that is agreed upon during fabric login.

FFA Fibre Adapter, another name for a Symmetrix Fibre Channel director.

Fabric One or more switching devices that interconnect Fibre Channel N_Ports, and route Fibre Channel frames based on destination IDs in the frame headers.

Fabric Element Any active switch or director in the fabric.

Fabric Login Process used by N_Ports to establish their operating parameters including the presence or absence of a fabric, paths to other N_Ports, and specific operating characteristics for each port.


g-8

Glossary

Fabric Manager Software application that is the system management framework and the user interface for managing EMC Fibre Channel connectivity products. The Connectrix Manager can run either locally on the Connectrix service processor or remotely on a user workstation.

Fabric Port Physical interface within the fabric, which attaches to an N_Port through a point-to-point full duplex link connection.

Failover The process of detecting a failure on an active Connectrix switch FRU and the automatic transition of functions to a backup FRU.

Fan-in/Fan-out Terms used to describe the server:storage ratio, where a graphic representation of a 1:n (fan-in) or n:1 (fan-out) logical topology looks like a hand-held fan, with the wide end toward n.

A fan-in or fan-out rate is often referred to as just the n part of the ratio; for example, a 1:6 fan-in is also called a fan-in rate of 6.

FCPFCPFCPFCP A standard Fibre Channel protocol used to run SCSI over Fibre Channel.

FC-SW The Fibre Channel Fabric standard.

Fibre A general term used to cover all physical media types supported by the Fibre Channel specification, such as optical fiber, twisted pair, and coaxial cable.

Fiber optics The branch of optical technology concerned with the transmission of radiant power through fibers made of transparent materials such as glass, fused silica, and plastic.

Either a single discrete fiber or a nonspatially aligned fiber bundle can be used for each information channel. Such fibers are often called optical fibers to differentiate them from fibers used in non-communication applications.

Storage

Storage SwitchSwitch Servers 1

2

n

Server

Fan-In Fan-Out

1

2

n


Glossary

Fibre Channel The general name of an integrated set of ANSI standards that define new protocols for flexible information transfer. Logically, Fibre Channel is a high-performance serial data channel.

Firmware The program code (embedded software) that resides and executes on a connectivity device, such as a Connectrix switch, a Symmetrix Fibre Channel director, or a host bus adapter (HBA).

Flash Memory A computer chip with a read-only memory that retains its data when the power is turned off, and that can be erased and reprogrammed without being removed from the circuit board.

F_Port Fabric Port, a physical interface within the fabric. An F_Port attaches to an N_Port through a point-to-point full-duplex link connection.

Frame The smallest indivisible packet of data that is sent on a link.

Frame Header Control information placed before data when encapsulating data for network transmission.

FRU Field-Replaceable Unit, a hardware component that can be replaced as an entire unit. The Connectrix switch Product Manager can display status for the FRUs installed in the unit.

GGateway Address In TCP/IP, a device that connects two systems that use the same or

different protocols.

G_Port A physical interface within the fabric capable of acting either as an F_Port or an E_Port (extension port) depending on the port type at the other end of the link.

GUI Graphical user interface.

HHardware Log A record of FRU insertions and removals in a Connectrix switch.

HBA See Host Bus Adapter.

Hexadecimal Pertaining to a numbering system with base of 16; valid numbers use the digits 0 through 9 and characters A through F (which represent the numbers 10 through 15).


g-10

Glossary

High Availability A performance feature characterized by hardware component redundancy and hot-swappability (enabling non-disruptive maintenance). High-availability systems maximize system uptime while providing superior reliability, availability, and serviceability.

Hop Data movement from one node to the next.

Host Bus Adapter A bus card in a host system that allows the host system to connect to a fabric.

II/O See Input/Output.

IML Initial Machine Load, initiated through the IML button on a Connectrix switch. An IML issues a hardware reset for all installed CTP subsystems on the switch, but does not affect other hardware.

In-Band Management Transmission of monitoring/control functions over the Fibre Channel interface.

Information Message A message telling a user that a function is performing normally or has completed normally. User acknowledgement might or might not be required, depending on the message. See also Error Message and Warning Message.

Input/Output (1) Pertaining to a device whose parts can perform an input process and an output process at the same time. (2) Pertaining to a functional unit or channel involved in an input process, output process, or both (concurrently or not), and to the data involved in such a process. (3) Pertaining to input, output, or both.

Interface (1) A shared boundary between two functional units, defined by functional characteristics, signal characteristics, or other characteristics as appropriate. The concept includes the specification of the connection of two devices having different functions. (2) Hardware, software, or both, that links systems, programs, or devices.

Internet Protocol See IP.


Glossary

Interoperability The ability to communicate, execute programs, or transfer data between various functional units over a network.

Interswitch Link See ISL.

IP Internet Protocol, the TCP/IP standard protocol that defines the datagram as the unit of information passed across an internet and provides the basis for connectionless, best-effort packet delivery service. IP includes the ICMP control and error message protocol as an integral part.

IP Address A unique string of numbers that identifies a device on a network. The address consists of four groups (quadrants) of numbers delimited by periods. (This is called dotted-decimal notation.) All resources on the network must have an IP address. A valid IP address is in the form nnn.nnn.nnn.nnn, where each nnn is a decimal in the range 0 to 255.

IPL Initial Program Load, initiated through a menu option in a Connectrix switch Product Manager. This performs the same function as an IML, but resets the active CTP only. It does not affect the backup CTP subsystem if it is installed.

ISL A physical E_Port connection between two switches in a fabric.

LLaser A device that produces optical radiation using a population inversion

to provide light amplification by stimulated emission of radiation and (generally) an optical resonant cavity to provide positive feedback. Laser radiation can be highly coherent temporally, spatially, or both.

LED Light-emitting diode.

Link The physical connection between two devices on a switched fabric.

Link Incident A problem detected on a fiber optic link; for example, loss of light, or invalid sequences.

Load Balancing The ability to distribute traffic over all network ports that are the same distance from the destination address by assigning different paths to different messages. Increases effective network bandwidth.


g-12

Glossary

Loopback Plug In a fiber optic environment, a type of duplex connector used to wrap the optical output signal of a device directly to the optical input.

Loopback Test Test that checks attachment or control unit circuitry, without checking the mechanism itself, by returning the output of the mechanism as input.

LUN Logical Unit Number; a number, assigned to a storage device, that (in combination with the storage device node port’s WWN) represents a unique identifier for a logical device on a storage area network.

MMAC Address Media Access Control address, the hardware address of a device

connected to a shared network.

Maintenance Port RS-232 connector on a Connectrix switch where a PC running an ASCII terminal emulator can be attached or dial-up connection made for specialized maintenance support.

Managed Product A hardware product that can be managed using the Connectrix Product Manager. For example, a Connectrix switch is a managed product.

Management Session Exists when a user logs on to the Connectrix Management software and successfully connects to the product server. The user must specify the network address of the product server at logon time.

Media Access Control See MAC Address.

Megabyte (MB) A unit of measure for storage size, loosely one million bytes. One megabyte actually equals 1,048,576 bytes.

MIB Management Information Base, a related set of objects (variables) containing information about a managed device and accessed via SNMP from a network management station.

Multicast Multicast is used when multiple copies of data are to be sent to designated, multiple, destinations.

Multiswitch Fabric Fibre Channel fabric created by linking more than one switch or director together to allow communication. See also ISL.


Glossary

Multiswitch Linking Port-to-port connections between two switches.

NName Server The program facility that allows the N_Ports to register and discover

Fibre Channel attributes.

Network Address A name or address that identifies a managed product, such as a Connectrix switch, or a Connectrix sevice processor on a TCP/IP network. The network address can be either an IP address in dotted decimal notation, or a Domain Name Service (DNS) name as administered on a customer network. All DNS names have a host name component and (if fully qualified) a domain component, such as host1.emc.com. In this example, host1 is the host name and EMC.com is the domain component.

Nickname A name representing one or more port numbers or World Wide Names.

Node The point at which one or more functional units connect to the network.

N_Port Node Port, a physical interface within an end device (node) which can attach to an F_Port or directly to another N_Port through a point-to-point link connection.

NVRAM Nonvolatile random access memory.

OOffline Sequence A sequence sent by the transmitting port to indicate that it has

detected a problem while attempting to initialize a link.

OLS See Offline Sequence.

Operating System Software that controls the execution of programs and that may provide such services as resource allocation, scheduling, input/output control, and data management. Although operating systems are predominantly software, partial hardware implementations are possible.


g-14

Glossary

Optical Cable A fiber, multiple fibers, or a fiber bundle in a structure built to meet optical, mechanical, and environmental specifications.

OS See Operating System.

Out-of-BandManagement

Transmission of monitoring/control functions outside of the Fibre Channel interface.

PPanel A subdivision of a window in a GUI used to group related

information within the window. Typically, a heading and/or frame marks the panel as an individual entity of the window. As with a window, data within the panel is usually confined to that panel. Size and shape of the panel and its data is dependent upon the purpose of the panel, and may or may not be modified by user changes to the window size and shape.

Parameter (1) A characteristic element whose value is a variable that is given a constant value for a specified application. (2) An item in a menu for which the user specifies a value or for which the system provides a value when the menu is interpreted. (3) Data passed between programs or procedures.

Password (1) A value used in authentication or a value used to establish membership in a group having specific privileges. (2) A unique string of characters known to the computer system and to a user who must specify it to gain full or limited access to a system and to the information stored within it.

Path In a network, any route between any two nodes.

Persistent Binding Server-level access control uses configuration information to bind a server device name to a specific Fibre Channel storage volume or logical unit number, through a specific HBA and storage port WWN.

Port (1) An access point for data entry or exit. (2) A receptacle on a device to which a cable for another device is attached.

Port Card Field replaceable hardware component that provides the connection for fiber cables and performs specific device-dependent logic functions.


Glossary

Port Name A symbolic name that the user defines for a particular port through the Product Manager.

POST Power-On Self Test, a series of self-tests executed each time the unit is booted or reset.

Preferred Domain ID Domain ID that a switch is assigned by the principal switch in a switched fabric. The preferred domain ID becomes the active domain ID except when configured otherwise by the user.

Principal Switch In a multiswitch fabric, the switch that allocates domain IDs to itself and to all other switches in the fabric. There is always one principal switch in a fabric. If a switch is not connected to any other switches, it acts as its own principal switch.

Product (1) Connectivity Product, a generic name for a switch, director, or any other Fibre Channel product. (2) Managed Product, a generic hardware product that can be managed by the Product Manager (a Connectrix switch is a managed product). Note distinction from the definition for Device.

Product Manager A software component of the Connectrix Management software, such as a Connectrix switch Product Manager, that implements the management user interface for a specific product. When a Product instance is opened from the Connectrix Management software Product View, the corresponding Product Manager is invoked.

Product Name A user configurable identifier assigned to a Managed Product. Typically, this name is stored on the product itself. For a Connectrix switch, the Product Name can also be accessed by an SNMP Manager as the System Name. The Product Name should align with the host name component of a Network Address.

Product View The top-level display in the Connectrix Management software user interface that displays icons of Managed Products.

Protocol (1) A set of semantic and syntactic rules that determines the behavior of functional units in achieving communication. (2) A specification for the format and relative timing of information exchanged between communicating parties.


g-16

Glossary

RR_A_TOV See Resource Allocation Time Out Value.

Resource AllocationTime Out Value

Is used to time out operations that depend on the maximum possible time that a frame could be delayed in a fabric and still be delivered. The resource allocation time out value of (R_A_TOV) can be set within a range of two-tenths of a second to 120 seconds using the Connectrix switch Product Manager.

Remote Access Link The ability to communicate with a data processing facility through a remote data link.

Remote Notification The system can be programmed to notify remote sites of certain classes of events.

Remote UserWorkstation

A workstation, such as a PC, using Connectrix Management software and Product Manager software that can access the Connectrix sevice processor over a LAN connection. A user at a remote workstation can perform all of the management and monitoring tasks available to a local user on the Connectrix sevice processor.

SSAN See Storage Area Network.

Segmented E_Port E_Port that has ceased to function as an E_Port within a multiswitch fabric due to an incompatibility between the fabrics that it joins.

SEL System error light.

Service Processor See Connectrix Service Processor.

Session See Management Session.

SFP Small form-factor pluggable, a type of shortwave or longwave optic transceiver.

SMTP Simple Mail Transfer Protocol, a TCP/IP protocol that allows users to create, send, and receive text messages. SMTP protocols specify how messages are passed across a link from one system to another. They do not specify how the mail application accepts, presents or stores the mail.


Glossary

SNMP Simple Network Management Protocol, a TCP/IP protocol that generally uses the User Datagram Protocol (UDP) to exchange messages between a management information base (MIB) and a management client residing on a network.

Storage Area Network A network linking servers or workstations to disk arrays, tape backup systems and other devices, typically over Fibre Channel.

Subnet Mask Used by a computer to determine whether another computer with which it needs to communicate is located on a local or remote network. The network mask depends upon the class of networks to which the computer is connecting. The mask indicates which digits to look at in a longer network address and allows the router to avoid handling the entire address. Subnet masking allows routers to move the packets more quickly. Typically, a subnet may represent all the machines at one geographic location, in one building, or on the same local area network.

Switch Priority Value configured into each switch in a fabric that determines its relative likelihood of becoming the fabric’s principal switch.

TTCP/IP Transmission Control Protocol/Internet Protocol.

Topology Logical and/or physical arrangement of stations on a network.

Trap An asynchronous (unsolicited) notification of an event originating on an SNMP-managed device and directed to a centralized SNMP Network Management Station.

Toggle To change the state of a feature/function that has only two states. For example, if a feature/function is enabled, toggling changes the state to disabled.

UULP Upper Layer Protocol, the protocol user of FC-4, including IPI, SCSI,

IP, and SBCCS.


g-18

Glossary

Unblocked Port Devices communicating with an unblocked port can log in to a Connectrix switch or a similar product and communicate with devices attached to any other unblocked port if the devices are in the same Zone.

Unicast Unicast routing provides one or more optimal path(s) between any of two switches that make up the fabric. (This is used to send a single copy of the data to designated destinations.)

URL Uniform Resource Locater, the addressing system used by the World Wide Web. It describes the location of a file or server anywhere on the Internet.

WWarning Message An indication that a possible error has been detected. See also Error

Message and Information Message.

World Wide Name A unique identifier, even on global networks. The WWN is a 64-bit number (XX:XX:XX:XX:XX:XX:XX:XX).

WWN See World Wide Name.

ZZone A set of devices that can access one another. All connected devices

may be configured into one or more Zones. Devices in the same Zone can “see” each other, while different Zones cannot.

Zoning Zoning allows an administrator to group several devices by function or by location. All devices connected to a connectivity product, such as a Connectrix switch, may be configured into one or more Zones.

Zone Set A set of Zones.


Index

AAC power. See power, ACaddress, gateway B-2address, IP B-2address, MAC B-2address, node 4-21addresses, network

configuringvia CLI D-19via Embedded Web Server C-17via PC B-2

default B-2displaying via CLI D-20

alert symbols 4-5alerts, link incident. See link incident alertsAudit Log 6-4

Bbackup 7-10BB_Credit 3-13beaconing, port, enabling/disabling

via CLI D-59via Product Manager 4-15

beaconing, unit, enabling/disablingvia CLI D-60via Product Manager 4-14

binding (pending), fabric, activating via CLI D-24binding configuration (pending), fabric, replacing

via CLI D-26binding state (pending), fabric, setting via CLI

D-27

binding, fabric, configuringvia CLI D-24via Connectrix Manager. See Connectrix

Manager User Guidebinding, port

configuringvia CLI D-29via Embedded Web Server C-26via Product Manager 5-17

described 5-22binding, switch

configuringvia CLI D-32via Product Manager 5-12

described 5-12bound WWN


described 5-21buffer-to-buffer credit 3-13

Ccall-home notification, enabling 7-9Clear System Error Light 4-14CLI

command parameters D-11command tree D-6enabling/disabling using Embedded Web

Server C-21errors, handling D-14help, using D-14navigation conventions D-5

Connectrix DS-24M2 User Guide i-1

i-2

Index

CLI (continued)output D-11overview D-3scripts, commenting D-15

command line interface. See CLIcommands, SNMP A-4comments xxvconfig command (CLI) D-16configuration data, default values 7-17configuration report, exporting 5-41configuration, backing up and restoring 7-10configuration, resetting


connectivity features 1-12connectors 2-6Connectrix Manager

compared to Embedded Web Server C-3logging in 3-6

Connectrix service processor 1-8control processor 1-6CTP 1-6customer support xxiv, F-3Customer Support Center F-7

Ddata, maintenance, collecting 7-3data, Product Manager

backing up 7-12restoring 7-13

date, configuringvia CLI D-48via Embedded Web Server C-11via Product Manager 5-31

diagnostics, port 7-2dialog boxes, using 3-5domain ID, insistent. See insistentdomain ID, preferred. See preferred domain IDdomain RSCNs

described 5-7enabling/disabling

via CLI D-40via Embedded Web Server C-12via Product Manager 5-4

EE_D_TOV


described 5-9e-mail notification, enabling 7-8Embedded Web Server

application, opening C-5browser requirements C-5compared to Connectrix Manager C-3enabling via Product Manager 5-43overview C-2password, default C-5user name, default C-5

Enterprise Fabric Mode, enablingvia CLI D-16, D-17via Connectrix Manager.

See Connectrix Manager User Guideerror counters, port D-66error light, clearing


Event Log 6-6EWS. See Embedded Web Server

FFA MIB. See FibreAlliance MIBfabric address notification 5-20fabric binding (pending), activating via CLI D-24fabric binding configuration (pending), replacing

via CLI D-26fabric binding state (pending), setting via CLI

D-27fabric binding, configuring

via CLI D-24via Connectrix Manager. See Connectrix

Manager User GuideFabric Element MIB

class 1 accounting table A-44class 2 accounting table A-44class 3 accounting table A-45described A-29FxPort capability table A-46FxPort configuration table A-34


Index

Fabric Element MIB (continued)FxPort error table A-43FxPort fabric login table A-40FxPort operation table A-37FxPort physical level table A-38modules A-32objects defined in A-32

Fabric Member List, pendingclearing via CLI D-25members, adding via CLI D-25members, removing via CLI D-26

fabric parametersconfiguring via CLI D-40configuring via Embedded Web Server C-14configuring via Product Manager 5-8

FAN (fabric address notification) 5-20FCEOS MIB

active member table A-97active zone table A-97described A-86enterprise specific traps A-99fru table (module group) A-90port binding table A-96port table (port group) A-91system group variables A-88threshold alert table A-98zoning variables A-96

fcmgmt.mib. See FibreAlliance MIBfeature keys, installing/configuring


FibreAlliance MIBconnectivity unit group A-50event table A-69fcConnUnitTable A-51firmware table A-57link table A-71name server table A-81port statistics A-74port table A-60sensor table A-58trap registration group A-83trap registration table A-83trap types A-85type definitions A-49

firmware, updating 1-15

FlexPorts, adding via Product Manager 5-22FRU List view 4-25FRU properties 4-9FRUs, identifying 4-2

Ggateway address B-2

Hhardware features 1-9Hardware Log 6-8hardware operation, monitoring 4-6Hardware view 4-2help xxivhigh-availability features 1-11

Iidentification, switch, configuring

via CLI D-47, D-48, D-49via Embedded Web Server C-9via Product Manager 5-2

IML 1-16Initial Machine Load See IMLInitial Program Load See IPLinsistent (domain ID)


described 5-6interop mode


described 5-11IP address B-2IPL functions 1-17IPL procedure


Kkeyboard navigation 3-6

i-3Connectrix DS-24M2 User Guide

i-4

Index

LLEDs 2-4LIN. See link incident alertslink incident alerts

clearing via Product Manager 4-16configuring via Product Manager 5-17described 4-37where displayed 5-19

Link Incident Log 6-9link resets 4-30logging in to Connectrix Manager 3-6logging in to switch

via CLI D-11via Embedded Web Server C-5

logging out of switch via CLI D-12logs

accessing 6-2audit 6-4event 6-6expanding columns 6-3hardware 6-8link incident 6-9sorting entries 6-3threshold alert 6-11using 6-2

MMAC address B-2maint command (CLI) D-59maintenance data, collecting 7-3maintenance port 1-7management overview 1-10Management Server, Open Systems, configuring

via CLI D-18, D-23via Embedded Web Server C-21via Product Manager 5-27

mask, subnet B-2menus, pop-up 4-14MIB

Fabric Element. See Fabric Element MIBFCEOS. See FCEOS MIBFibreAlliance. See FibreAlliance MIBprivate enterprise. See FCEOS MIB

MIB-IIadditional IP objects A-19additional TCP objects A-25

address translation group A-13ICMP group A-20interfaces group A-9IP address table A-16IP address translation table A-19IP group A-14IP routing table A-16SNMP group A-26system group A-8TCP connection table A-24TCP group A-22UDP group A-25UDP listener table A-25

MIBs, downloading A-3

Nname, port


deleting via Product Manager 5-19described 5-19

nickname, defining for Product Manager views 4-24

No Link status 4-3Node List view 4-21node properties 4-23node types 4-22

Oonline/offline state, setting


Open Systems Management Server, configuringvia CLI D-18, D-23via Embedded Web Server C-21via Product Manager 5-27

operating parameters, configuringvia CLI. See individual parameter entriesvia Embedded Web Server C-12via Product Manager 5-4

operation, monitoring 4-5operational states

ports 4-35switch 1-15


Index

Ppassword, CLI

configuring D-35, D-36default D-12

password, Connectrix Managerconfiguring. See Connectrix Manager User

Guidedefault 3-7

password, Embedded Web Serverconfiguring C-25default C-5

password, HyperTerminal B-5perf command D-63performance features 1-9performance services D-63Performance view 4-25periodic date/time synchronization 5-31port binding


described 5-22port diagnostics 7-2port error counters D-66Port List view 4-25port names


deleting via Product Manager 5-19described 5-19

port operational states 4-35port properties 4-9port speed, setting


port state descriptions in FCEOS MIB A-100port statistics

clearingvia CLI D-65via Product Manager 4-27

described 4-27displaying via Product Manager 4-27

port type, configuringvia CLI D-22via Embedded Web Server C-7via Product Manager 5-17

port types 1-5ports, blocking/unblocking

via CLI D-20via Embedded Web Server C-7via Product Manager (Configure Ports) 5-17via Product Manager (right-click menu) 4-15

ports, configuringvia CLI D-16via Embedded Web Server C-7via Product Manager 5-17

ports, resettingvia CLI D-59via Product Manager 4-16

POSTs 2-2power supplies 1-7power, AC

switching off 2-3switching on 2-2

power-on self tests 2-2preferred domain ID


described 5-5principal switch


described 5-9priority. See switch priorityprivate enterprise MIB A-86Product Manager

closing 3-11data, backing up 7-12data, restoring 7-13opening 3-10overview 3-2using 3-5


i-6

Index

propertiesFRU 4-9node 4-23port 4-9switch 4-13windows, displaying 4-9

QQuikSync 7-14

RR_A_TOV


described 5-8rerouting delay


described 5-7restoring configuration data 7-10RSCNs on zone set activations

described 5-7enabling/suppressing


Ssecurity features 1-12service xxivservice processor.

See Connectrix service processorserviceability features 1-13Set Online State 7-6SFP transceivers 1-3show command (CLI) D-78SNMP

access A-2commands A-4community, deleting via CLI D-39configuring


overview A-2requirements A-2traps A-4

SNMP commands A-4specifications E-2speed, port, setting


states, operationalport 4-35switch 1-15

statistics, portclearing


described 4-27subnet mask B-2switch binding


described 5-12online state functions 5-15zoning function 5-16

switch identification, configuringvia CLI D-47, D-48, D-49via Embedded Web Server C-9via Product Manager 5-2

switch management 1-10switch parameters, configuring

via CLI D-40, D-42via Embedded Web Server C-12via Product Manager 5-4

switch priorityconfiguring


described 5-9switch properties 4-13system error light, clearing



Index

Ttechnical support xxiv, F-3Telnet

enabling 5-44sessions D-2

Threshold Alert Log 6-11threshold alerts


described 4-38time, configuring


transceivers 1-3traps A-4

UUnit Type 4-22

user name, CLIconfiguring D-35, D-36default D-12

user name, Connectrix Managerconfiguring. See Connectrix Manager User

Guidedefault 3-7

user name, Embedded Web Serverconfiguring C-25default C-5

user rights, Connectrix Manager 3-21

WWeb Server. See Embedded Web Server

Zzoning RSCNs. See RSCNs on zone set activationszoning, configuring

via CLI D-50via Connectrix Manager. See Connectrix

Manager User Guidevia Embedded Web Server C-22


i-8

Index


Documents

Connectrix DS-24M2 Fibre Channel Switch User Guide · Connectrix DS-24M2 User Guide iii Laser Compliance Statement Laser transceivers used in the DS-24M2 are tested and certified