53-1002167-01 13 May 2011 Brocade Network Advisor SAN User Manual Supporting Network Advisor 11.1.
Copyright © 2010 - 2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Contents Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . xxxvii What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Management server and client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Logging into a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Launching a remote client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Clearing previous versions of the remote client . . . . . . . . . . . . 28 Launching the Configuration Wizard . . . . . . . . . . . . . . . . . . . . . 28 Changing the database user password . . . . . . . . . . . . . . . . . . .
Seed switch requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Seed switch failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Changing the seed switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Host discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Discovering Hosts by Network address or host name . . . . . . . 66 Importing Hosts from a CSV file . . . . . . . . . . . . . . . . . . . . .
Enabling SAN Ethernet loss events . . . . . . . . . . . . . . . . . . . . . . 94 Disabling SAN Ethernet loss events . . . . . . . . . . . . . . . . . . . . . . 94 Event storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Configuring event storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Storing historical events purged from repository. . . . . . . . . . . . 96 Flyovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling fabric tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 Accepting changes for a fabric . . . . . . . . . . . . . . . . . . . . . . . . .131 Accepting changes for all fabrics . . . . . . . . . . . . . . . . . . . . . . .132 Accepting changes for a switch, access gateway, or phantom domain 132 Chapter 5 User Account Management In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 Users overview . . . . . . . . . . . . . . . .
LDAP authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Loading an Active Directory group . . . . . . . . . . . . . . . . . . . . . .154 Assigning roles and AORs to an Active Directory group. . . . . .155 Removing roles and AORs from an Active Directory group . . .155 Deleting an Active Directory group . . . . . . . . . . . . . . . . . . . . . .156 Chapter 6 Call Home In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a customized view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 Copying a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 SAN topology layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 Customizing the layout of devices on the topology. . . . . . . . . . . . .181 Customizing the layout of connections on the topology . . . . . . . . .182 Changing a group background color . . . . . . . . . . . . . . . . .
Adding an option to the Tools menu . . . . . . . . . . . . . . . . . . . . . . . .204 Changing an option on the Tools menu . . . . . . . . . . . . . . . . . . . . . .206 Removing an option from the Tools menu. . . . . . . . . . . . . . . . . . . .206 Adding an option to a device’s shortcut menu . . . . . . . . . . . . . . . .207 Changing an option on a device’s shortcut menu . . . . . . . . . . . . .208 Removing an option from a device’s shortcut menu . . . . . . . . . . .
Launching the SMIA configuration tool on Unix . . . . . . . . . . .231 Launching a remote SMIA configuration tool. . . . . . . . . . . . . .232 Service Location Protocol (SLP) support . . . . . . . . . . . . . . . . .232 Home tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 CIMOM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273 Filtering port connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Viewing port details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275 Viewing ports and port properties . . . . . . . . . . . . . . . . . . . . . . 276 Port types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279 Showing connected ports . . . . . . . . . . . . . . . . .
Importing storage port mapping . . . . . . . . . . . . . . . . . . . . . . . . . . .304 Exporting storage port mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . .305 Chapter 13 Host management In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307 Host management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307 HCM software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 14 Fibre Channel over Ethernet In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333 FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333 DCB exchange protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334 Enhanced Ethernet features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334 Enhanced transmission selection. . . . . . . . . . . . . . . . . . . . . . .
LLDP-DCBX configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366 Configuring LLDP for FCoE . . . . . . . . . . . . . . . . . . . . . . . . . . . .366 Adding an LLDP profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367 Editing an LLDP profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368 Deleting an LLDP profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369 Assigning an LLDP profile to a port or ports in a LAG . . . . . . .
Configuring routing domain IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . .412 Chapter 17 Virtual Fabrics In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .413 Virtual Fabrics overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .413 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .414 Virtual Fabrics requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Steps for connecting to an LKM appliance . . . . . . . . . . . . . . . . . . .448 Launching the NetApp DataFort Management Console . . . . .448 Establishing the trusted link . . . . . . . . . . . . . . . . . . . . . . . . . . .448 Obtaining and importing the LKM certificate. . . . . . . . . . . . . .449 Exporting and registering the switch KAC certificates on LKM450 LKM key vault high availability deployment . . . . . . . . . . . . . . .
Replacing an encryption engine in an encryption group . . . . . . . .509 Creating high availability (HA) clusters . . . . . . . . . . . . . . . . . . . . . . 510 Removing engines from an HA cluster . . . . . . . . . . . . . . . . . . .511 Swapping engines in an HA cluster . . . . . . . . . . . . . . . . . . . . .512 Failback option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .512 Invoking failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing and editing switch encryption properties . . . . . . . . . . . . .561 Exporting the public key certificate signing request (CSR) from Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .563 Importing a signed public key certificate from Properties . . .564 Enabling and disabling the encryption engine state from Properties 564 Viewing and editing group properties . . . . . . . . . . . . . . . . . . . . . . .565 General tab. . . . . . . . . . . . . . . . . . .
Configuring zoning for the SAN . . . . . . . . . . . . . . . . . . . . . . . .583 Creating a new zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .584 Viewing zone properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585 Adding members to a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . .586 Creating a new member in a zone . . . . . . . . . . . . . . . . . . . . . .587 Customizing the zone member display. . . . . . . . . . . . . . . . . . .
Zoning administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .612 Comparing zone databases. . . . . . . . . . . . . . . . . . . . . . . . . . . .612 Managing zone configuration comparison alerts . . . . . . . . . .615 Setting change limits on zoning activation. . . . . . . . . . . . . . . .615 Deleting a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .616 Deleting a zone alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QOS, DSCP, and VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .642 DSCP quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .642 VLANs and layer two quality of service . . . . . . . . . . . . . . . . . . .642 When both DSCP and L2CoS are used. . . . . . . . . . . . . . . . . . .642 Open systems tape pipelining . . . . . . . . . . . . . . . . . . . . . . . . . . . . .643 FCIP Fastwrite and Tape Acceleration . . . . . . . . . . . . . . . . . . .
Troubleshooting FCIP Ethernet connections . . . . . . . . . . . . . . . . . .670 Chapter 21 Fabric Binding In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671 Fabric binding overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671 Enabling fabric binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .672 Disabling fabric binding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a C3 Discard Frames threshold . . . . . . . . . . . . . . . . .683 Adding an Invalid CRCs threshold. . . . . . . . . . . . . . . . . . . . . . .685 Adding an Invalid Words threshold . . . . . . . . . . . . . . . . . . . . . .686 Adding a Link threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .687 Adding a Link Reset threshold . . . . . . . . . . . . . . . . . . . . . . . . .688 Adding a Protocol Error threshold . . . . . . . . . . . . . . . . . . . . . . .
Creating a port group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .720 Viewing port groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .722 Editing a port group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .722 Deleting a port group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .723 Swapping blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .723 Chapter 24 VLAN Management In this chapter . . .
Tracing FC routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .750 Troubleshooting device connectivity. . . . . . . . . . . . . . . . . . . . .751 Confirming Fabric Device Sharing. . . . . . . . . . . . . . . . . . . . . . .753 Troubleshooting port diagnostics . . . . . . . . . . . . . . . . . . . . . . .753 FCIP troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .756 Configuring IP ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAN End-to-end monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .793 Configuring an end-to-end monitor pair . . . . . . . . . . . . . . . . . .793 Displaying end-to-end monitor pairs in a real-time graph . . . .795 Displaying end-to-end monitor pairs in a historical graph. . . .795 Refreshing end-to-end monitor pairs . . . . . . . . . . . . . . . . . . . .795 Deleting an end-to-end monitor pair. . . . . . . . . . . . . . . . . . . . .796 SAN Top Talker monitoring . . . . . . . . . . .
Chapter 29 Policy Monitor In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .823 Policy Monitor overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .823 Fabric policy monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .824 SAN Switch policy monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . .825 Host policy monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event action definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .867 Creating an event action definition. . . . . . . . . . . . . . . . . . . . . .867 Configuring varbind filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .869 Selecting source address products and ports . . . . . . . . . . . . .870 Configuring event action policies . . . . . . . . . . . . . . . . . . . . . . .872 Editing event actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-mailing selected event details from the Master Log . . . . . .905 Displaying event details from the Master Log . . . . . . . . . . . . .906 Copying part of the Master Log. . . . . . . . . . . . . . . . . . . . . . . . .907 Copying the entire Master Log . . . . . . . . . . . . . . . . . . . . . . . . .907 Exporting the Master Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . .907 Filtering events in the Master Log. . . . . . . . . . . . . . . . . . . . . . .
SAN shortcut menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .941 Appendix B Call Home Event Tables In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .957 Call Home Event Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .957 # CONSRV Events Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .959 # Thermal Event Reason Codes Table . . . . . . . . . . . . . . . . . . . . . . .
Database tables and fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .991 Advanced Call Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .991 Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .992 Client_view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .994 Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .997 Config . . . . . . . . . . . . . . . .
Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144 BOOT_IMAGE_FILE_DETAILS_INFO . . . . . . . . . . . . . . . . . . . . 1144 CEE_PORT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144 CNA_PORT_DETAILS_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . 1145 CNA_PORT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145 CORE_SWITCH_DETAILS_INFO . . . . . . . . . . . . . . . . . . . . . . .
SNMP_DATA_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235 SNMP_EXPR_DATA_INFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236 SNMP_DATA_VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xli • Additional information . . . . . . . . . . . .
• • • • Chapter 13, “Host management,” provides information on how to configure an HBA. Chapter 14, “Fibre Channel over Ethernet,”provides information on how to configure an FCoE. Chapter 15, “Security Management,” provides security configuration instructions. Chapter 16, “FC-FC Routing Service Management,” provides information on how to manage Fibre Channel Routing. • Chapter 17, “Virtual Fabrics,” provides information on configuring and managing logical switches.
Supported hardware and software In those instances in which procedures or parts of procedures documented here apply to some devices but not to others, this guide identifies exactly which devices are supported and which are not. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for Network Advisor 11.1.X, documenting all possible configurations and scenarios is beyond the scope of this document.
TABLE 1 Fabric OS Supported Hardware (Continued) Device Name Terminology used in documentation Firmware level required Brocade 5480 embedded switch Embedded 24-port, 8 Gbps Switch Fabric OS v6.1.0 or later Brocade 6510 48-port, 16 Gbpsswitch Fabric OS v7.0.0 or later Brocade 7500 Extension switch 4 Gbps Router, Extension Switch Fabric OS v5.1.0 or later Brocade 7500E Extension switch 4 Gbps Extension Switch Fabric OS v5.1.
TABLE 1 Fabric OS Supported Hardware (Continued) Device Name Terminology used in documentation Firmware level required Brocade DCX-4S 1 192-port Backbone Chassis Fabric OS v6.0.0 or later 192-port Backbone Chassis with 8 Gbps 16-FC port, 8 Gbps 32-FC port, and 8 Gbps 48-FC port blades Fabric OS v6.2.0 Brocade DCX-4S 1, 2 with FC8-64 Blades 192-port Backbone Chassis with 8 Gbps 64-FC port blades Fabric OS v6.4.
What’s new in this document The following changes have been made since this document was last released: • Information that was added: • Host adapter discovery • VM Manager discovery • Performance Data Aging tab to SMC • Port Auto Disable dialog box • Adapter port WWN virtualization • FCoE login management • Deployment Manager • Diagnostic Port Test • Collective Support Save (Server, Client, and devices) • Bottleneck detection • Frame Monitoring • Special Events Handling • Security Management • Policy Monit
Document conventions This section describes text formatting conventions and important notice formats used in this document.
Notice to the reader This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations. These references are made for informational purposes only. Corporation Referenced Trademarks and Products Linus Torvalds Linux Microsoft Corporation Windows, Windows NT, Internet Explorer Netscape Communications Corporation Netscape Red Hat, Inc.
Other industry resources For additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications: http://www.t11.org For information about the Fibre Channel industry, visit the Fibre Channel Industry Association website: http://www.fibrechannel.
• Brocade 7600—On the bottom of the chassis • Brocade 48000—Inside the chassis next to the power supply bays • Brocade DCX and DCX-4S—On the bottom right on the port side of the chassis 4. World Wide Name (WWN) Use the wwn command to display the switch WWN. If you cannot use the wwn command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX.
Chapter Getting Started 1 In this chapter • User interface components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Icon legend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 • Management server and client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 • Supported open source software products . . . . . . . . . . . . . . . . . . . . . . . . . .
1 User interface components FIGURE 1 Main window 1. Menu bar. Lists commands you can perform on the Management application. The available commands vary depending on which tab (SAN or Dashboard) you select. For a list of available commands, refer to Appendix A, “Application menus”. 2. Toolbar. Provides buttons that enable quick access to dialog boxes and functions. The available buttons vary depending on which tab (SAN or Dashboard) you select.
User interface components 1 Dashboard tab NOTE Only devices in your area of responsibility (AOR) display in the dashboard. The Dashboard tab provides a high-level overview of the network and the current states of managed devices. This allows you to easily check the status of the devices on the network. The dashboard also provides several features to help you quickly access reports, device configuration, and system logs.
1 User interface components 5. Widgets. Displays operational status, inventory status, event summary, and overall network/fabric status. 6. Status bar. Displays the connection, port, product, fabric, special event, call home, and backup status, as well as Server and User data. Menu bar The menu bar is located at the top of the main window. For a list of the many functions available on each menu, refer to “Dashboard main menus” on page 931.
User interface components 1 Widgets The Dashboard contains four widgets which can be shown or hidden, resized, collapsed or expanded, as well as maximized or minimized; however you cannot detach a widget. The status and inventory widget colors are defined in “Event type color codes” on page 6. FIGURE 4 Widgets The Dashboard includes the following widgets: 1. SAN Operational Status. Displays the device status as a pie chart. Displays the device status as a percentage of the total number of devices.
1 User interface components 2. SAN Inventory. Displays the SAN products inventory as stacked bar graphs. Displays each group as a separate bar on the graph. Displays the current state of all products discovered for a group in various colors on each bar. Displays the color legend below the y-axis. Displays tooltips on mouse-over to show the number of devices in that state. Inventory widget customization Group By list—Select to display product inventory for a specific grouping.
User interface components 1 Events widget customization • Range list—Select to display event information for a specific duration. To change the duration, select one of the following from the list. This Hour—Displays event information for the current hour beginning when the Dashboard is displayed. Last Hour—Displays event information for the previous hour to when the Dashboard is displayed. Yesterday—Displays event information for the previous day beginning at 12AM of the previous day.
1 User interface components • Export. To take a snapshot (.png) of the dashboard, complete the following steps. a. Click Export. b. Browse to the location where you want to save the snapshot. c. Enter a name for the snapshot in the File Name field. d. Click Save. • Print. To print the dashboard, complete the following steps. a. Click Print. b. Click OK. SAN tab The SAN tab (Figure 5) displays the Product List, Topology Map, Master Log, Utilization Legend, and Minimap.
User interface components 4 1 6 1 2 3 5 7 8 9 11 10 12 13 FIGURE 5 Main window - SAN tab 1. Menu bar. Lists commands you can perform on the SAN tab. For a list of SAN tab menu commands, refer to “SAN main menus” on page 932. 2. Main toolbar. Provides buttons that enable quick access to dialog boxes and functions. For a list of available commands, refer to “Main toolbar” on page 10. 3. Dashboard tab. Provides a high-level overview of the network managed by Management application server.
1 User interface components 11. Utilization Legend. (Trial and Licensed version only) Indicates the percentage ranges represented by the colored, dashed lines on the Connectivity Map. Only displays when you select Monitor > Performance > View Utilization or click the Utilization icon on the toolbar. 12. Minimap. Displays a “bird’s-eye” view of the entire topology. Does not display until you discover a fabric. 13. Status bar.
User interface components 1 View All list The View All list is located at the top left side of the window and enables you to create, copy, or edit a view, select to how to view the Product list (All Levels, Products and Ports, Products Only, or Ports Only) and to select which view you want to display in the main window. Does not display until you discover a fabric. To discover a fabric, refer to “Discovering fabrics” on page 49. 1 2 3 4 5 6 1. Create View. Select to create a new view. 2. Copy View.
1 User interface components Connectivity Map toolbar The Connectivity Map toolbar is located at the top right side of the View window and provides tools to export the topology, to zoom in and out of the Connectivity Map, collapse and expand groups, and fit the topology to the window. Not enabled until you discover a fabric. 1 2 FIGURE 8 3 4 5 6 The Connectivity Map toolbar 1. Export. Use to export the topology to a PNG file. 2. Zoom In. Use to zoom in on the Connectivity Map. 3. Zoom Out.
User interface components 1 • Domain ID. Displays the Domain ID for the product in the format xx(yy), where xx is the normalized value and yy is the actual value on the wire. • • • • • • • • • • • • • • • • • • • FC Address. Displays the Fibre Channel address of the port. Firmware. Displays the firmware version of the product. IP Address. Displays the IP address (IPv4 or IPv6 format) of the product. Location. Displays the physical location of the product. This field is editable at the fabric level.
1 User interface components FIGURE 9 Connectivity Map The Management application displays all discovered fabrics in the Connectivity Map by default. To display a discovered Host in the Connectivity Map, you must select the Host in the Product List. You can only view one Host and physical and logical connections at a time. Master Log The Master Log, which displays in the lower left area of the main window, lists the events and alerts that have occurred on the SAN.
User interface components 1 • Node WWN. The world wide name of the node on which the event occurred. • Fabric Name. The name of the fabric on which the event occurred. • Operational Status. The operational status (such as, unknown, healthy, marginal, or down) of the product on which the event occurred. • • • • • • First Event Product Time. The time and date the event first occurred on the product. Last Event Product Time. The time and date the event last occurred on the product. First Event Server Time.
1 User interface components Use the Minimap to view the entire SAN and to navigate more detailed map views. This feature is especially useful if you have a large SAN. Does not display until you discover a fabric. FIGURE 11 Minimap Anchoring or floating the Minimap You can anchor or float the Minimap to customize your main window. • To float the Minimap and view it in a separate window, click the Detach icon ( ) in the upper right corner of the Minimap.
Icon legend 1 3. Product Status. Displays the status of the most degraded device in the SAN. For example, if all devices are operational except one (which is degraded), the Product Status displays as degraded. Click this icon to open the Product Status Log. 4. Fabric Status. Displays the state of the fabric that is least operational, based on ISL status. The possible states are: operational, unknown, degraded or failed.
1 Icon legend Icon Description Icon Description Fabric Fabric OS Switch and Blade Switch Fabric OS Director Fabric OS CEE Switch Fabric OS Router Storage Fabric OS FC Switch in Access Gateway mode (single-fabric connected) Fabric OS FC Switch in Access Gateway mode (multiple-fabric connected) Fabric OS CEE Switch in Access Gateway mode (single-fabric connected) Fabric OS CEE Switch in Access Gateway mode (multiple-fabric connected) M-EOS Switch M-EOS Director iSCSI Target iSCSI Initiator
Icon legend 1 SAN group icons The following table lists the manageable SAN product group icons that display on the topology. Icon Description Icon Description Switch Group Host Group Storage Group Unknown Fabric Group Unmanaged Fabric Group Chassis Group Host group icons The following table lists the manageable Host product group icons that display on the topology.
1 Icon legend SAN product status icons The following table lists the product status icons that display on the topology.
Icon legend 1 Event icons The following table lists the event icons that display on the topology and Master Log. For more information about events, refer to “Fault Management” on page 843.
1 Management server and client Management server and client The Management application has two parts: the Server and the Client. The Server is installed on one machine and stores device-related information; it does not have a user interface. To view information through a user interface, you must log in to the Server through a Client. The Server and Clients may reside on the same machine, or on separate machines. If you are running Professional, the server and the client must be on the same machine.
Management server and client TABLE 4 1 Professional edition ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 24602 jboss.connector.bisocket.port - port 2 TCP Bisocket connector port Client–Server No 24603 jboss.connector.bisocket.secondary.port TCP - port 3 Bisocket connector secondary port Client–Server No 24604 jboss.naming.rmi.port - port 4 TCP RMI naming service port Client–Server No 24605 jboss.jrmp.invoker.
1 Management server and client TABLE 5 Trial and Licensed version ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 49 TACACS+ Authentication port TCP TACACS+ server port for authentication if TACACS+ is chosen as an external authentication Server–TACACS+ Server Yes 80 jboss.web.http.port TCP Non-SSL HTTP/1.
Management server and client TABLE 5 1 Trial and Licensed version ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 246045 jboss.connector.sslbisocket.port - port 4 TCP SSL Bisocket connector port Client–Server Yes 5 jboss.connector.sslbisocket.secondary.p ort - port 5 TCP SSL Bisocket connector secondary port Client–Server Yes 24606 smp.registry.port - port 6 TCP RMI registry port Client–Server Yes 24607 smp.server.export.
1 Management server and client TABLE 5 Trial and Licensed version ports (Continued) Port Number Ports Transport Description Communication Path Open in Firewall 55556 Launch in Context (LIC) client hand shaking port TCP Client port used to check if a Management application client opened using LIC is running on the same host Client No NOTE: If this port is in use, the application uses the next available port. 1 Port is not configurable (either in the switch or the Management server).
Management server and client 1 Logging into a server You must log into a server to monitor your network. NOTE You must have an established user account on the server to log in. To log into a server, complete the following steps. 1. Double-click the desktop icon or open the application from the Start menu. The Log In dialog box displays (Figure 13). FIGURE 13 Log In dialog box 2. Enter your user name and password. 3.
1 Management server and client 5. Click Login. 6. Click OK on the Login Banner dialog box. The Management application displays. Clearing previous versions of the remote client The remote client link in the Start menu does not automatically upgrade when you upgrade the Management application. You must clear the previous version from the Java cache. To clear the Java cache, complete the following steps. 1. Select Start > Settings > Control Panel > Java. The Java Control Panel dialog box displays. 2.
Management server and client 1 4. Select Internal FTP Server or External FTP Server on the FTP Server screen and click Next. If port 21 is busy, a message displays. Click OK to close the message and continue. Once the Management application is configured make sure port 21 is free and restart the Server to start the FTP service. NOTE If you use an FTP Server which is not configured on the same machine as the Management application, the Firmware Repository feature will not be available.
1 Management server and client b. Select an address from the Switch - Server IP Configuration Preferred Address list. If DNS is not configured for your network, do not select the ‘hostname’ option from either the Server IP Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the ‘hostname’ option prevents clients and devices from communicating with the Server.
Management server and client f. 1 Click Next. If you enter a syslog port number already in use, a message displays. Click No on the message to remain on the Server Configuration screen and edit the syslog port number (return to step 6a). Click Yes to close the message and continue with step 7. If you enter a port number already in use, a Warning displays next to the associated port number field. Edit that port number and click Next. 7. Complete the following steps on the SMI Agent Configuration screen.
1 Management server and client The defaults are Administrator and password, respectively. If you migrated from a previous release, your user name and password do not change. 12. Click Login. 13. Click OK on the Login Banner. Changing the database user password To change the read/write or read only database password, complete the following steps in the Install_Home/bin directory. 1. Open a command window. 2. Type dbpassword User_Name Password New_Password Confirm_Password and press Enter.
Management server and client 1 Viewing active sessions To view the Management application active sessions, complete the following steps. 1. Select Server > Active Sessions. The Active Sessions dialog box displays (Figure 19). FIGURE 18 Active Sessions dialog box 2. Review the active session information. The following information displays: • • • • • ID—Displays the name of the user (for example, Administrator). Description—Displays the description of the user (for example, Operator).
1 Management server and client Viewing server properties To view the Management application server properties, complete the following steps. 1. Select Server > Server Properties. The Server Properties dialog box displays. FIGURE 19 Server Properties dialog box 2. Click Close. Viewing port status You can view the port status for the following ports: FTP, SNMP, Syslog, and Web Server. To view the port status, complete the following steps. 1. Click the port status icon ( ).
Supported open source software products 1 Supported open source software products Table 6 lists the open source software third-party software products used in this release. TABLE 6 Supported Open Source Software Third-party Software Products Open Source Software License Type 7-ZipLZMASDK 4.65 public domain Abator 1.1 Apache License v2.0 ApacheAnt 1.7.1 Apache License v2.0 ApacheCommonsBeanUtils 1.8.1 Apache License v2.0 ApacheCommonsCodec 1.4 Apache License v2.0 ApacheCommonsCollections 3.
1 Supported open source software products TABLE 6 36 Supported Open Source Software Third-party Software Products (Continued) Open Source Software License Type dom4j 1.6.1 dom4j License EnterpriseDTFTP 1.5.6 LGPL GlazedLists 1.8.0 LGPL or MPL GoogleGuice 1.0 Apache HPInsightSoftwareVCEMWebClientSDK 6.2 HP SOFTWARE DEVELOPMENT KIT LICENSE AGREEMENT HornetQ 2.0.0 Apache License v2.0 iBATISDAOFramework 2.2.0 Apache iBatisforJava 2.3.4 Apache License v2.0 Infinispan 4.0.0 FINAL LGPL v2.
Supported open source software products TABLE 6 1 Supported Open Source Software Third-party Software Products (Continued) Open Source Software License Type OpenSAML 2.3.0 Apache License v2.0 OpenSSLforLinux 1.0.0a OpenSSL License PostgreSQL 8.4.3 PostgreSQL License QualityFirstLibrary 0.99.0 Mozilla License V1.1 and qflib License Quartz Enterprise Job Scheduler 1.66 Apache License v2.0 RockSawRawSocketLibrary 1.0.0 Apache License v2.0 SafeNet Sentinel Caffe 1.6.
1 SAN feature-to-firmware requirements SAN feature-to-firmware requirements Use the following table to determine whether the Management application SAN features are only available with a specific version of the Fabric OS firmware, M-EOS firmware, or both, as well as if there are specific licensing requirements. Feature Fabric OS M-EOS Access Gateway (AG) AG connected to Fabric OS devices requires firmware 5.2 or later. AG connected to M-EOS devices requires firmware 9.6 or later.
SAN feature-to-firmware requirements 1 Feature Fabric OS M-EOS Meta SAN Requires Fabric OS 5.2 or later for FC router and router domain ID configuration. Requires Fabric OS 6.0 or later in a mixed Fabric OS and M-EOS fabric. Requires Integrated Routing license. Not available. Performance Requires Fabric OS 5.0 or later for FC_ports, -end Requires M-EOS and M-EOSn 9.6.X or later for FC_ports and marching ants. monitors, and marching ants. Requires Fabric OS 5.
1 Accessibility features for the Management application Accessibility features for the Management application Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. The following list includes the major accessibility features in the Management application: • Keyboard shortcuts • Look and Feel Keyboard shortcuts You can use the keystrokes shown in the table below to perform common functions.
Accessibility features for the Management application 1 Look and Feel You can configure the Management application to mimic your system settings as well as define the size of the font. ‘Look’ refers to the appearance of graphical user interface widgets and ‘feel’ refers to the way the widgets behave. The Management application currently uses the ‘Management_Application Default Look and Feel’ for some of the components (for example, Layout, Minimap, and so on) and the “Java Metal Look and Feel” for others.
1 Accessibility features for the Management application Changing the font size The Options dialog box enables you to change the font size for all components including the Connectivity map of the Management application interface. Font size changes proportionately in relation to the system resolution. For example, if the system resolution is 1024 x 768, the default font size would be 8 and large font size would be 10. 1. Select Server > Options. The Options dialog box displays. 2.
Chapter 2 Licenses In this chapter • Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Managed count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Entering the license key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Upgrading the application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Managed count Managed count The Management application audits and verifies the managed count against the maximum limit for your license under the following conditions: • Every 3 hours from server start time. Note that you may be able to manage more products or ports than the maximum licensed limit briefly (maximum of three hours) between these periodic checks. • When a new client logs in to the server. • When you access the License dialog box (Help > License).
Upgrading the application 2 NOTE You are not required to enter a license key for SMI Agent only installation. If you choose to the SMI Agent only option, when you open the Management application client, a License dialog displays, where you must enter a license key. Before you enter the license key you must install the application. For step-by-step instructions, refer to “Installing the Application” in the Installation Guide. 1. Select Help > License. The License dialog box displays 2.
2 Upgrading the application TABLE 8 SAN + IP upgrade paths Current Software Release To Software Release SAN Professional Plus + IP Enterprise Licensed version SAN + IP Enterprise Licensed version Enterprise trial Enterprise Licensed version 1. Select Help > License. The License dialog box displays. 2. Enter the license key (on the Key Certificate) in the License Key field and click Update. 3. Click OK on the message. The Client closes after updating the license successfully.
Chapter 3 Discovery In this chapter • SAN discovery overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Viewing the fabric discovery state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting fabric discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN Fabric monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN Seed switch . . . . . . . . . . . . . . . .
3 SAN discovery overview NOTE Professional Plus edition can discover up to 4 fabrics. NOTE Professional Plus edition can discover, but not manage the Backbone chassis.Use the device’s Element Manager, which can be launched from the Connectivity Map, to manage the device. This device cannot be used as a Seed switch. NOTE Professional edition can discover, but not manage M-EOS devices or the Backbone chassis.
SAN discovery overview 3 Discovering fabrics NOTE Fabric OS devices must be running Fabric OS 5.0 or later. M-EOS devices must be running M-EOS 9.6 or later. NOTE Only one copy of the application should be used to monitor and manage the same devices in a subnet. To discover specific IP addresses or subnets, complete the following steps. 1. Select Discover > Fabrics. The Discover Fabrics dialog box displays. FIGURE 21 Discover Fabrics dialog box 2.
3 SAN discovery overview FIGURE 22 Add Fabric Discovery dialog box (IP Address tab) 3. Enter a name for the fabric in the Fabric Name field. 4. Enter an IP address for a device in the IP Address field. For seed switch requirements, refer to “Seed switch requirements” on page 63. NOTE The Backbone Chassis cannot be used as seed switch to discover and manage edge fabrics. You must discover a seed switch from each edge fabric to discover and manage the edge fabric.
SAN discovery overview 3 For Virtual Fabric discovery device requirements, refer to “Virtual Fabrics requirements” on page 415. To discover a Virtual Fabric device, you must have the following permissions: • Switch user account with Chassis Admin role permission on the physical chassis. • Switch and SNMPv3 user account with access rights to all logical switches (all Fabric IDs (1 - 128). For information about configuring permissions on a Fabric OS device, refer to the Fabric OS Administrator’s Guide.: 5.
3 SAN discovery overview d. Select the SNMP version from the SNMP Version list. • If you selected v1, continue with step e. • If you select v3, the SNMP tab displays the v3 required parameters. Go to step i. To discover a Fabric OS device (not virtual fabric-capable), you must provide the existing SNMPv3 username present in the switch. To discover a Virtual Fabric device, you must configure SNMPv3 and your SNMP v3 user account must be defined as a Fabric OS switch user.
SAN discovery overview 3 Editing the password for multiple devices You can only edit password for Fabric OS devices in the same fabric. To edit the password for multiple devices within the same fabric, complete the following steps. 1. Select Discover > Fabrics. The Discover Fabrics dialog box displays. 2. Select multiple devices within the same fabric from the Discovered Fabrics table. 3. Click Edit. The Fabric_Name Edit Switches dialog box displays. FIGURE 24 Edit Switches dialog box 4.
3 SAN discovery overview Configuring SNMP credentials 1. Select Discover > Fabrics. The Discover Fabrics dialog box displays. 2. Select an IP address from the Discovered Fabrics table. 3. Click Edit. The Add Fabric Discovery dialog box displays. 4. To revert to the default SNMPv3 settings, click the Automiatic option. Go to step 19. 5. To manually configure SNMP, select the Manual option. Go to step 6. 6. Click the SNMP tab. 7. Select the SNMP version from the SNMP Version list.
SAN discovery overview 3 19. Click OK on the Add Fabric Discovery dialog box. If the seed switch is not partitioned, continue with step 20. If the seed switch is partitioned, the Undiscovered Seed Switches dialog box displays. a. Select the Select check box for each undiscovered seed switch to discover their fabrics. b. Click OK on the Undiscovered Seed Switches dialog box. 20. Click Close on the Discover Fabrics dialog box.
3 Viewing the fabric discovery state Rediscovering a previously discovered fabric To return a fabric to active discovery, complete the following steps. 1. Select Discover > Fabrics. The Discover Fabrics dialog box displays. 2. Select the fabric you want to return to active discovery in the Previously Discovered Addresses table. 3. Click Discover. 4. Click OK on the confirmation message. The rediscovered fabric displays in the Discovered Fabrics table. 5. Click Close on the Discover Fabrics dialog box.
Troubleshooting fabric discovery TABLE 9 Icon 3 Discovery Status Icons Description Displays when the fabric or host is managed and the management status is okay. Displays when the switch is managed and the switch management status is not okay. Displays when the fabric or host is not managed. The Discovery Status field details the actual status message text, which varies depending on the situation.
3 Troubleshooting fabric discovery M-EOSn discovery troubleshooting The following section states a possible issue and the recommended solution for M-EOSn discovery errors. Problem Resolution M-EOS seed switch discovery is not supported using SNMPv3 on the following devices: • 32-Port, 2 Gbps Switch • 16-Port, 4 Gbps Fabric Switch • 24-Port Fabric Switch • 32-Port, 4 Gbps Switch • 140-Port Director Discover the device using SNMPv1. To configure SNMPv3 and manage the device, complete the following steps.
Troubleshooting fabric discovery 3 Virtual Fabric discovery troubleshooting The following section state possible issues and the recommended solutions for Virtual Fabric discovery errors. Problem Resolution At the time of discovery, the seed switch is Virtual Fabric-enabled; however, the user does not have Chassis Admin role for the seed switch. At the time of discovery, the user does not have the Chassis Admin role for all other switches in the fabric.
3 SAN Fabric monitoring SAN Fabric monitoring NOTE Monitoring is not supported on Hosts. The upper limit to the number of HBA and CNA ports that can be monitored at the same time is 32. The same upper limit applies if switch ports and HBA ports are combined. You can select switch ports and adapter ports from a maximum of ten devices. Fabric monitoring enables discovery of and data collection for the specified fabric and all associated devices.
SAN Fabric monitoring 3 Monitoring discovered fabrics NOTE Monitoring is not supported on Hosts. To monitor a fabric and all associated devices, complete the following steps. 1. Select Discovery > Fabrics. The Discover Fabrics dialog box displays. 2. Select the fabric you want to monitor from the Discovered Fabrics table. 3. Click Monitor. The monitor function fails if the fabric has user-defined Admin Domains created or if the fabric is merged with another fabric already in the monitored state. 4.
3 SAN Seed switch SAN Seed switch The seed switch must be running a supported Fabric OS or M-EOS version and must be HTTP-reachable. Sometimes, the seed switch is auto-selected, such as when a fabric segments or when two fabrics merge.
SAN Seed switch 3 Seed switch requirements Depending on your environment, you must meet the following hardware and firmware version requirements for seed switches. Fabric OS devices: • For Fabric OS only fabrics, the seed switch must be running Fabric OS 5.0 or later. • For mixed fabrics (Fabric OS and M-EOS), the seed switch must be running Fabric OS 6.0 or later. For a complete list of all supported Fabric OS hardware, refer to “Supported hardware and software” on page xxxvii l.
3 SAN Seed switch Seed switch failover The Management application collects fabric-wide data (such as, fabric membership, connectivity, name server information, zoning, and so on) using the seed switch. Therefore when a seed switch becomes unreachable or there is no valid seed switch, the fabric becomes unmanageable.
SAN Seed switch 3 Changing the seed switch When you change the seed switch for a fabric, the Management application performs the following checks in the order they are listed: • • • • Identifies all switches and removes those running unsupported firmware version. Identifies which of the remaining switches are running the latest firmware versions. Filters out those switches that are not reachable. Identifies which switches are Virtual Fabric-enabled switches (Fabric OS only).
3 Host discovery Host discovery The Management application enables you to discover individual hosts, import a group of Host from a comma separated values (CSV) file, or import all hosts from discovered fabrics or VM managers. NOTE Host discovery requires HCM Agent 2.0 or later. NOTE SMI and WMI discovery are not supported. Discovering Hosts by Network address or host name To discover a Host by Network address or host name, complete the following steps. 1. Select Discover > Host Adapters.
Host discovery FIGURE 26 3 Add Host Adapters dialog box 3. (Optional) Enter a discovery request name (such as, Manual 06/12/2009) in the Discovery Request Name field. 4. Select Network Address from the list. 5. Enter the IP address (IPv4 or IPv6 formats) or host name in the Network Address field. 6. Click Add. The IP address or host name of the Host displays in the Host List.
3 Host discovery 7. Configure Host credentials, if necessary. a. Enter the HCM Agent port number in the Port field. b. Enter your username in the User ID field. c. Enter your password Password field. 8. Repeat step 5 through step 7 for each Host you want to discover. 9. Click OK on the Add Host Adapters dialog box. If an error occurs, a message displays. Click OK to close the error message and fix the problem. A Host Group displays in Discovered Hosts table with pending status.
Host discovery 3 4. Browse to the CSV file location. The CSV file must meet the following requirements: • Comma separated IP address or host names • No commas within the values • No escaping supported For example, XX.XX.XXX.XXX, XX.XX.X.XXX, computername.company.com 5. Click Open. The CSV file is imported to the Add Host Adapters dialog box. During import, duplicate values are automatically dropped. When import is complete, the imported values display in the Host List.
3 Host discovery FIGURE 28 Add Host Adapters dialog box 3. Enter a discovery request name (such as, MyFabric) in the Discovery Request Name field. 4. Select Hosts in Fabrics from the list. 5. Select All fabrics or an individual fabric from the list. 6. Click Add. All hosts which are part of a managed fabric and have a registered host name display in the list. If no host with a registered host name exists, an error message displays. Click OK to close the error message. 7.
Host discovery 3 Importing Hosts from a VM manager To discover Hosts from a discovered VM manager, complete the following steps. 1. Select Discover > Host Adapters. The Discover Host Adapters dialog box displays. 2. Click Add. The Add Host Adapters dialog box displays. FIGURE 29 Add Host Adapters dialog box 3. Enter a discovery request name (such as, MyVMManager) in the Discovery Request Name field. 4. Select Hosts from VM Manager from the import by list. 5.
3 Host discovery 8. Click OK on the Add Host Adapters dialog box. If an error occurs, a message displays. Click OK to close the error message and fix the problem. A Host Group displays in Discovered Hosts table with pending status. To update the status from pending you must close and reopen the Discover Host Adapters dialog box. 9. Click Close on the Discover Host Adapters dialog box. Editing Host adapter credentials To edit Host credentials, complete the following steps. 1.
Host discovery 3 To delete a host from active discovery, complete the following steps. 1. Select Discover > Host Adapters. The Discover Host Adapters dialog box displays. 2. Select the host you want to delete from active discovery in the Discovered Hosts table. 3. Click Delete. 4. Click OK on the confirmation message. The deleted host displays in the Previously Discovered Addresses table. 5. Click Close on the Discover Host Adapters dialog box.
3 Host discovery Viewing the host discovery state The Management application enables you to view device discovery status through the Discover Host Adapters dialog box. To view the discovery status of a device, complete the following steps. 1. Select Discover > Host Adapters. The Discover Host Adapters dialog box displays. 2. Right-click the Hosts node select Expand All to show all devices. The Name field displays the discovery status icons in front of the device name.
VM Manager Discovery 3 VM Manager Discovery The Management application enables you to discover VM managers. NOTE VM Manager discovery requires vCenter Server 4.0 or later. NOTE You can discover up to 10 VM Managers. Discovering a VM manager To discover a VM manager, complete the following steps. 1. Select Discover > VM Managers. The Discover VM Managers dialog box displays.
3 VM Manager Discovery 2. Click Add. The Add VM Manager dialog box displays. FIGURE 32 Add VM Manager dialog box 3. Enter the IP address or host name in the Network Address field. 4. Enter the VM manager port number in the Port field. 5. Enter the VM manager username in the User ID field. 6. Enter the VM manager password Password field. 7. Select the Enable display of network information in vSphere client check box to enable vSphere client plug-in registration.
VM Manager Discovery 3 Editing a VM manager To edit VM manager discovery, complete the following steps. 1. Select Discover > VM Managers. The Discover VM Managers dialog box displays. 2. Select the Host in the Discovered VM Managers list and click Edit. The Edit VM Manager dialog box displays. FIGURE 33 Edit VM Manager dialog box 3. Change the VM manager port number in the Port field. 4. Enter the VM manager username in the User ID field. 5. Enter the VM manager user password Password field. 6.
3 VM Manager Discovery Including a host in VM manager discovery To include host in VM manager discovery complete the following steps. 1. Select Discover > VM Managers. The Discover VM Managers dialog box displays. 2. Select a Host you want to include in the Discovered VM Managers list and click Include.. 3. Click Close on the Discover VM Managers dialog box.
VM Manager Discovery 3 Deleting a VM manager from discovery To delete a host permanently from discovery, complete the following steps. 1. Select Discover > VM Managers. The Discover VM Managers dialog box displays. 2. Select the VM manager you want to delete permanently from discovery in the Previously Discovered Addresses table. 3. Click Delete. 4. Click OK on the confirmation message. 5. Click Close on the Discover VM Managers dialog box.
3 VM Manager Discovery Troubleshooting VM manager discovery If you encounter discovery problems, complete the following checklist to ensure that discovery was set up correctly. 1. Verify IP connectivity by issuing a ping command to the switch. a. Open the command prompt. b. From the Server, type ping Device_IP_Address. 2. Enter the IP address of the device in a browser to verify the SNMP settings. For example, http://10.1.1.11.
Chapter Application Configuration 4 In this chapter • Server Data backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 • Server Data restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 • SAN Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 • SAN End node display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Server Data backup Server Data backup The Management application helps you to protect your data by backing it up automatically. The data can then be restored, as necessary. NOTE Backing up data takes some time. It is possible that, in a disaster recovery situation, configuration changes made after the last backup interval will be missing from the backup.
Server Data backup 4 Back up directory structure overview The Management server backs up data to two alternate folders. For example, if the backup directory location is D:\Backup, the backup service alternates between two backup directories, D:\Backup\Backup and D:\Backup\BackupAlt. The current backup is always D:\Backup and contains a complete backup of the system. The older backup is always D:\BackupAlt. If a backup cycle fails, the cause is usually a full CD-RW.
4 Server Data backup 4. Choose one or more of the following options: • Select the Include Adapter Boot Image directory check box. • Select the Include FTP Root directory check box. If you select the FTP Root directory, the FTP Root sub-directories, Technical Support and Trace Dump, are selected automatically and you cannot clear the sub-directory selections. If you do not select the FTP Root directory, the sub-directories can be selected individually.
Server Data backup 4 4. Choose one or more of the following options: • Select the Include Adapter Boot Image directory check box. • Select the Include FTP Root directory check box. If you select the FTP Root directory, the FTP Root sub-directories, Technical Support and Trace Dump, are selected automatically and you cannot clear the sub-directory selections. If you do not select the FTP Root directory, the sub-directories can be selected individually.
4 Server Data backup 4. Choose one or more of the following options: • Select the Include Adapter Boot Image directory check box. • Select the Include FTP Root directory check box. If you select the FTP Root directory, the FTP Root sub-directories, Technical Support and Trace Dump, are selected automatically and you cannot clear the sub-directory selections. If you do not select the FTP Root directory, the sub-directories can be selected individually.
Server Data backup 4 Enabling backup Backup is enabled by default. However, if it has been disabled, complete the following steps to enable the function. 1. Select Server > Options. The Options dialog box displays. 2. Select Server Backup in the Category list. 3. Select the Enable Backup check box. 4. Click Apply or OK. Disabling backup Backup is enabled by default. If you want to stop the backup process, you need to disable backup. To disable the backup function, complete the following steps. 1.
4 Server Data backup Changing the backup interval When the backup feature is enabled, your SAN is protected by automatic backups. The backups occur every 24 hours by default. However, you can change the interval at which backup occurs. ATTENTION Do NOT modify the backup.properties file. To change the backup interval, complete the following steps. 1. Select Server > Options. The Options dialog box displays. 2. Select Server Backup in the Category list. 3.
Server Data restore 4 Reviewing backup events The Master Log, which displays in the lower left area of the main window, lists the events that occur on the Fabric. If you do not see the Master Log, select View > Show Panels > All Panels.
4 Server Data restore • Backup\conf – contains the Management application configuration files. • Backup\cimom – contains the SMIA configuration files. In a disaster recovery situation, it is possible that configuration changes made less than 45 minutes before Server loss (depending on the backup interval you set) could be missing from the backup. Restoring data 1. (Windows) Open the Server Management Console from the Start menu on the Management application server.
SAN Display 4 SAN Display You can configure the display for FICON and reset the display to the default settings. Setting your FICON display FICON display setup rearranges the columns of any table that contains end device descriptions to move the following eight columns to be the first columns: FC Address, Serial #, Tag, Device Type, Model, Vendor, Port Type, and WWN. To set the FICON display, complete the following steps. 1. Select Server > Options. The Options dialog box displays (Figure 35).
4 SAN Display Resetting your display You can reset your system to display the default display settings. Note that returning to current settings after a reset may require configuring each global fabric or group setting individually. The following table (Table 13) details the settings that change with reset and the associated default state. TABLE 13 Default Display Settings Settings Default State Show port Disabled. Show connected end device Set to Hide All. Map Layout Set to default for Groups.
SAN End node display 4 SAN End node display The connectivity map can be configured to display or not display end nodes. This option enables you to set the end node display for all newly discovered fabrics. Note that disabling end node display limits the connectivity map to emphasize switch members only. Displaying end nodes To display end nodes when discovering a new fabric, complete the following steps. 1. Select Server > Options. The Options dialog box displays (Figure 36).
4 SAN Ethernet loss events SAN Ethernet loss events An Ethernet event occurs when the Ethernet link between the Management Server and the managed SAN device is lost. You can configure the application to enable events when the Ethernet connection is lost. Enabling SAN Ethernet loss events The Options dialog box enables you to configure the Management application to generate an Ethernet event after a device is offline for a specific period of time.
Event storage 4 Event storage You can configure the number of historical events in the repository as well as how long the events will be retained. Configuring event storage To configure event storage, complete the following steps. 1. Select Server > Options. The Options dialog box displays (Figure 38). FIGURE 38 Options dialog box (Event Storage option) 2. Select Event Storage in the Category list. 3.
4 Flyovers Storing historical events purged from repository To store historical events purged from the repository, complete the following steps. 1. Select Server > Options. The Options dialog box displays. 2. Select Event Storage in the Category list. 3. Select the Yes option. 4. Click OK. Purged events from the master log table are stored in the Install_Home\data\archive\events directory using the format event_MMDDYYY.zip (for example, event_04052011.zip. These files are retained for a maximum of 7 days.
Flyovers FIGURE 39 a. 4 Options dialog box (Flyovers option, Product tab) Select each property you want to display in the product flyover from the Available Properties table.
4 Flyovers 7. Select the Connection tab (Figure 40) and complete the following steps to select the information you want to display on flyover. FIGURE 40 a. Options dialog box (Flyovers option, Connection tab) Select the protocol from the Protocol list. The default protocol is Fibre Channel. Depending on which protocol you select, some properties may not be available for all protocols. b. Select each property you want to display in the connection flyover from the Available Properties table.
SAN Names 4 FCoE • • • Name Node WWN MAC • • • Port# Port Type FCoE Index # IP • IP_Address:Port-IP_Address:Port c. Click the right arrow to move the selected properties to the Selected Properties table. d. Use the Move Up and Move Down buttons to reorder the properties in the Selected Properties table. The properties displayed in the Selected Properties table appear in the flyover display. 8. Click Apply or OK to save your work.
4 SAN Names Setting names to be unique You can edit duplicate names so that each device has a unique name. Note that the Duplicated Names dialog box only displays when you set names to be unique and there are duplicate names in the system. To edit duplicate names, complete the following steps. 1. Select Server > Options. The Options dialog box displays (Figure 41). FIGURE 41 Options dialog box (SAN Names option) 2. Select SAN Names in the Category list. 3.
SAN Names 4 Setting names to be non-unique You can choose to allow duplicate names in your fabric. To set names to be non-unique, complete the following steps. 1. Select Server > Options. The Options dialog box displays. 2. Select SAN Names in the Category list. 3. Select Set names to be non-unique to allow duplicate names on your system. 4. Click OK on the Options dialog box. Fixing duplicate names To fix duplicated names, complete the following steps. 1. Select Configure > Names.
4 SAN Names 2. Click Fix Duplicates. The Duplicated Names dialog box displays. 3. Select one of the following options. • If you select Append Incremental numbers for all repetitive names, the names are edited automatically using incremental numbering. • If you select I will fix them myself, edit the name in the Name field. 4. Click OK on the Duplicated Names dialog box. 5. Click OK to close the Configure Names dialog box. 6. Click OK on the confirmation message.
SAN Names 4 5. Click OK on the confirmation message. 6. Click OK to close the Configure Names dialog box. Adding a name to a new device To add a new device and name it, complete the following steps. 1. Select Configure > Names. The Configure Names dialog box displays. 2. Enter the WWN of the device in the Detached WWN field. 3. Enter a name for the device in the Name field. 4. Click Add. The new device displays in the table.
4 SAN Names Removing a name from a device 1. Select Configure > Names. The Configure Names dialog box displays. 2. In the Display table, select the name you want to remove. 3. Click Remove. An application message displays asking if you are sure you want clear the selected name. 4. Click Yes. 5. Click OK to close the Configure Names dialog box. 6. Click OK on the confirmation message. Editing names To edit the name associated with a device, complete the following steps. 1. Select Configure > Names.
SAN Names 4 Importing Names If the name length exceeds the limitations detailed in the following table, you must edit the name (in the CSV file) before import. Names that exceed these limits will not be imported. If you migrated from a previous version, the .properties file is located in the Install_Home\migration\data folder. Device Character limit Fabric OS switch 6.2 or later 30 (24 character limit when in FICON mode) Fabric OS switch 6.1.X or earlier 15 Fabric OS switch port 7.
4 SAN Names 4. Enter the name you want to search for in the Search field. You can search on partial names. NOTE To search for a device, the device must be discovered and display in the topology. 5. Click Search. All devices with the specified name (or partial name) are highlighted in the Display table. You may need to scroll to see all highlighted names. If the search finds no devices, a ‘no item found’ message displays. 6. Click OK to close the Configure Names dialog box.
Security 4 Security You can configure the Server Name, CHAP secret value, and login banner, and modify whether or not to allow clients to save passwords. When the login banner is enabled, each time a client connects to the server, the login banner displays with a legal notice provided by you. The client's users must acknowledge the login banner to proceed, otherwise they are logged out. Configuring the server name To set the CHAP secret, complete the following steps. 1. Select Server > Options.
4 Security 5. Re-enter the password in the Retype Secret field. If the secret does not meet the application requirements or the CHAP Secret and Retype Secret entries do not match, an error message displays. Click OK to re-enter the CHAP Secret and Retype Secret values. You are about to modify the ID/Secret of this server. Check all products that this server is managing and make sure the corresponding Software ID/Secret is updated appropriately.
Security 4 Configuring the login banner display To configure the login banner display, complete the following steps. 1. Select Server > Options. The Options dialog box displays. 2. Select Security Misc in the Category list. 3. Select the Display login banner upon client login check box. 4. Enter the message you want to display every time a user logs into this server in the Banner Message field. This field contains a maximum of 1024 characters. 5. Click Apply or OK to save your work.
4 Syslog Registration Syslog Registration You can automatically register the server as the syslog recipient on products. Registering a server as a Syslog recipient automatically 1. Select Server > Options. The Options dialog box displays. 2. Select Syslog Registration in the Category pane. FIGURE 44 Options dialog box (Trap Registration option) 3. Select the Auto register server as Syslog recipient check box, if necessary. This check box is selected by default. 4. Click Apply or OK to save your work.
SNMP Trap Registration 4 SNMP Trap Registration You can automatically register the server as the trap recipient on products. If SAN products have Informs enabled, the registration is for the Informs. Registering a server as a SNMP trap recipient automatically 1. Select Server > Options. The Options dialog box displays. 2. Select Trap Registration in the Category pane. FIGURE 45 Options dialog box (Trap Registration option) 3.
4 SNMP Trap Forwarding Credentials SNMP Trap Forwarding Credentials You can configure SNMP credentials for the traps forwarded by the server. Configuring SNMP v1 and v2c credentials To configure a SNMP v1 or v2c credentials, complete the following steps. 1. Select Server > Options. The Options dialog box displays. 2. Select Trap Forwarding Credentials in the Category pane. FIGURE 46 Options dialog box (Trap Forwarding Credentials option) 3.
Software Configuration 4 4. Select on of the following authentication types from the Authentication Type options. • HMAC_MD5 • HMAC_SHA 5. Enter the SNMP v3 user name (case sensitive, 1 to 16 characters) in the Auth Password and Confirm Password fields. Allows all printable ASCII characters. 6. Select one of the following privacy protocol types from the Privacy Protocol options. • CBC-DES • CFB_AES-128 7.
4 Software Configuration FIGURE 47 Options dialog box (Client Export Port option) 3. Enter the client export port number to set a fixed port number for the client in the Client Export Port field. 4. Click Apply or OK to save your work. NOTE Changes to this option take effect after a client restart. 5. Click OK on the “changes take effect after client restart” message.
Software Configuration 4 Client/Server IP You can configure connections between the client or switches and the Management application server. Configuring the server IP address NOTE The server binds using IPv6 address by default if your Operating System is IPv6-enabled (dual mode or IPv6 only). The server binds using IPv4 address by default if your Operating System is IPv4-enabled. Servers running in dual mode allow the client to communicate from both IPv6 and IPv4 addresses.
4 Software Configuration 3. Choose one of the following options in the Server IP Configuration list. • Select All. Go to step 4. • Select a specific IP address. Continue with step 5. • Select localhost. Continue with step 5. When Server IP Configuration is set to All, you can select any available IP address as the Return Address. If you select a specific IP address, the Return Address list shows the same IP address and you cannot change it. 4.
Software Configuration 4 5. Complete the following steps on the Server IP Configuration screen (Figure 49). FIGURE 49 Server IP Configuration screen a. Select an address from the Server IP Configuration list. b. Select an address from the Switch - Server IP Configuration Preferred Address list. If DNS is not configured for your network, do not select the “hostname” option from either the Server IP Configuration or Switch - Server IP Configuration Preferred Address list.
4 Software Configuration Configuring the application to use dual network cards Issues with Client-to-Server connectivity can be due to different reasons. Some examples are: • The computer running the Server has more than one network interface card (NIC) installed. • The computer running the Server is behind a firewall that performs network address translation.
Software Configuration FIGURE 50 4 Options dialog box (IP Preferences option) Memory allocation You can configure memory allocation for the client and server to improve performance. You can trigger switch polling when a state changes or you can poll at intervals when no state change occurs. NOTE SAN size is a consideration in selection of polling periods. Configuring memory allocation settings To configure memory allocation settings, complete the following steps. 1. Select Server > Options.
4 Software Configuration For a 32-bit Windows/Linux Server • Small : 768 MB • Medium : 1024 MB • Large : 1024 MB For a 64-bit Windows Server • Small : 20481024 MB • Medium : 1500 MB • Large : 10242048 MB Client Heap Size (for both 32 and 64-bit servers) • Small : 512 MB • Medium : 512 MB • Large : 768 MB b. Click OK on the confirmation message. 4. Enter the memory allocation (MB) for the client in the Client Memory Allocation field.
Software Configuration 4 • Enterprise Medium : 1500 MB • Enterprise Large : 2048 MB NOTE There is no restriction on the maximum value for Server Heap Size in a 64-Bit Server. The correct server heap size value must be given according to the RAM present in the server. 6. Click Apply or OK to save your work. NOTE Changes to this option take effect after an application restart. NOTE You can only restart the server using the Server Management Console (Start > Programs > Management_Application_Name 11.X.
4 Software Configuration 5. Click Apply or OK to save your work. NOTE Changes to this option take effect after an application restart. NOTE You can only restart the server using the Server Management Console (Start > Programs > Management_Application_Name 11.X.X > Server Management Console). 6. Click OK on the “changes take effect after application restart” message. Product communication You can configure connections between the switch and the Management application server.
Software Configuration 4 3. Choose one of the following options: • If you want to connect using HTTP, complete the following steps. a. Select the Connect using HTTP option. b. Enter the connection port number in the Port # field. Continue with step 4. • If you want to connect using HTTPS (HTTP over SSL), complete the following steps. a. Select the Connect using HTTPS (HTTP over SSL) only option. b. Enter the connection port number in the Port # field. Continue with step 4. 4.
4 Software Configuration Configuring an internal FTP server To configure the internal FTP server settings, complete the following steps. 1. Select Server > Options. The Options dialog box displays (Figure 52). 2. Select FTP/SCP in the Category list. FIGURE 52 Options dialog box (FTP/SCP option) 3. Select the Use built-in FTP Server option to use the default built-in FTP server. All active fields are mandatory. 4.
Software Configuration 4 Configuring an external FTP server To configure the external FTP server settings, complete the following steps. 1. Select Server > Options. The Options dialog box displays. 2. Select FTP/SCP in the Category list. 3. Select the Use External FTP Server and/or SCP Server option. 4. Select the External FTP Server check box to configure the external FTP server. All fields are mandatory. 5. Enter the IP address for the remote host in the Remote Host IP field. 6.
4 Software Configuration 9. Click Test to test the FTP server. A “Server running successfully” or an error message displays. If you receive an error message, make sure your credentials are correct, the server is running, the remote directory path exists, and you have the correct access permission; then try again. 10. Click OK on the message. 11. Click Apply or OK to save your work. Testing the FTP and SCP server To test the FTP and SCP server, complete the following steps. 1. Select Server > Options.
Software Configuration 4 Server port You can configure the server port settings so that you can assign a web server port number and set the server port to be SSL-enabled. Configuring the server port To configure server settings, complete the following steps. 1. Select Server > Options. The Options dialog box displays (Figure 53). 2. Select Server Port in the Category list. FIGURE 53 Options dialog box (Server Port option) 3. Select the Enable SSL check box to enable this function for the server port.
4 Software Configuration 6. Click Apply or OK to save your work. NOTE Changes to this option take effect after application restart. 7. Click OK on the “changes take effect after application restart” message. Support mode You can configure support settings to allow enhanced diagnostics. Configuring support mode settings To configure support mode settings, complete the following steps. 1. Select Server > Options. The Options dialog box displays (Figure 54). 2.
Software Configuration 4 3. Select the Log client support data - Log Level list, and select the type of log data you want to configure. Log level options include: All, Fatal, Error, Warn, Info, Debug, Trace, and Off. Default is Info. The log level options return to the default value (Info) when the client or server is restarted. 4. Select the Log server support data - Log Level list, and select the type of log data you want to configure.
4 Fabric tracking Fabric tracking When you discover a new fabric and initial discovery is complete, fabric tracking is automatically enabled. Subsequently, if a switch or end-device is added to or removed from the fabric, a plus (+) or minus (-) icon displays (see table below) next to the product icon. Connections are also tracked. A new connection displays a solid gray line with a added icon and missing connections display a yellow dashed line with a removed icon.
Fabric tracking 4 Disabling fabric tracking 1. Disable fabric tracking by choosing one of the following options: • Select the fabric on which you want to disable fabric tracking on the Product List or Connectivity Map and select Monitor > Track Fabric Changes. • Right-click the fabric on which you want to disable fabric tracking on the Product List or Connectivity Map and select Track Fabric Changes. The Accept Changes Summary dialog box displays.
4 Fabric tracking • Device Ports—This table shows a brief summary of the device ports including status (whether the device port will be added ( ) or removed ( ) from the fabric), device type, port, port WWN, node WWN, and attached port number.
Fabric tracking 4 • Device Ports—This table shows a brief summary of the device ports including status (whether the device port will be added ( ) or removed ( ) from the fabric), device type, port, port WWN, node WWN, and attached port number.
4 134 Fabric tracking Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 5 User Account Management In this chapter • Users overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • User accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Password policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • User profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Roles.
5 User accounts User accounts NOTE You must have User Management Read and Write privileges to add new accounts, set passwords for accounts, and apply roles to the accounts. For a list of privileges, refer to “User Privileges” on page 961. Management application user accounts contain the identification of the Management application user, as well as privileges, roles, and AORs assigned to the user. Privileges provide access to the features in Management application.
User accounts 5 12. Assign roles and AORs by selecting the role or AOR in the Available Roles / AOR table and click the right arrow button to move the role or AOR to the Selected Roles / AOR table. Select multiple roles or AORs by holding down the CTRL key and clicking more than one role or AOR. 13. Remove roles and AORs by selecting the role or AOR in the Selected Roles / AOR table and click the left arrow button to move the role or AOR to the Available Roles / AOR table.
5 User accounts 12. Assign roles and AORs by selecting the role or AOR in the Available Roles / AOR table and click the right arrow button to move the role or AOR to the Selected Roles / AOR table. Select multiple roles or AORs by holding down the CTRL key and clicking more than one role or AOR. 13. Remove roles and AORs by selecting the role or AOR in the Selected Roles / AOR table and click the left arrow button to move the role or AOR to the Available Roles / AOR table.
User accounts 5 12. Assign roles and AORs by selecting the role or AOR in the Available Roles / AOR table and click the right arrow button to move the role or AOR to the Selected Roles / AOR table. Select multiple roles or AORs by holding down the CTRL key and clicking more than one role or AOR. 13. Remove roles and AORs by selecting the role or AOR in the Selected Roles / AOR table and click the left arrow button to move the role or AOR to the Available Roles / AOR table.
5 User accounts 3. Remove roles and AORs by selecting the role or AOR in the Selected Roles / AOR table and click the left arrow button to move the role or AOR to the Available Roles / AOR table. Select multiple roles or AORs by holding down the CTRL key and clicking more than one role or AOR. 4. Click OK to save the user account and close the Edit User dialog box. If you make changes to the user’s role or AOR while the user is logged in, a confirmation message displays.
User accounts 5 Deleting a user account NOTE You cannot delete the default "Administrator" user account. To permanently delete a user account from the server, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Select the user you want to delete in the Users table and click Delete. 3. Click Yes on the confirmation message. If currently accessing the server, the user will be logged out once the user account is deleted. 4. Click Close to close the Users dialog box.
5 Password policies Password policies NOTE You must have User Management Read and Write privileges to configure password policy. Passwords are an important aspect of computer security. They are the front line of protection for user accounts. The purpose of the password policy is to establish a standard for the creation of strong passwords, the protection of those passwords, and the frequency of change.
Password policies d. 5 Enter the minimum number of lowercase characters required in the Lower Case Characters field. Only enabled when the Empty Password - Allow check box is clear. Valid values are 0 through 127. The default is 0. e. Enter the minimum number of digits required in the Number of Digits field. Only enabled when the Empty Password - Allow check box is clear. Valid values are 0 through 127. The default is 0. f.
5 User profiles 10. Click Yes on the confirmation message. 11. Click Close to close the Users dialog box. Viewing password policy violators To view password policy violators, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Click the Policy tab. 3. Click View Policy Violators. The View Policy Violators dialog box displays. 4. Review the password policy violator details.
User profiles 5 Viewing your user profile To view your user profile, complete the following steps. 1. Select Server > User Profile. The User Profile dialog box displays the following information: • User ID—Displays your user identifier. • Full Name—Displays the name if entered while adding a user; otherwise, this field is blank. • Password—Displays your password as dots (.). If the password policy is configured for an empty password, this field is blank.
5 User profiles 5. Change your phone number in the Phone Number field. 6. Select the E-mail Notification Enable check box to enable e-mail notification. Clear the E-mail Notification Enable check box to disable e-mail notification. 7. Click Filter to set up basic event filters. For step-by-step instructions about setting up basic event filters, refer to “Setting up basic event filtering” on page 845. 8. Change your e-mail address in the E-mail Address field.
User profiles 5 Resetting optional messages To reset all Management application optional messages to their default behaviors, complete the following steps. 1. Select Server > User Profile. The User Profile dialog box displays. 2. Click Optional Messages Reset. The Password Policy dialog box displays. 3. Click Yes on the confirmation message. A successful reset message displays. 4. Click OK on the User Profile dialog box.
5 Roles Roles NOTE You must have User Management Read and Write privileges to view, add, modify, or delete roles. A role is a group of Management application tasks or privileges that can be assigned to several users who have similar functions. When you create a role, it immediately becomes available in the Users dialog box. Creating a new role To create a new role, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Click Add under the Roles table.
Roles 5 3. Add read and write access by selecting the features to which you want to allow read and write access in the Available Privileges list and click the right arrow button to move the features to the Read & Write Privileges list. Select multiple features by holding down the CTRL key and clicking more than one privilege. The features are moved to the Read & Write Privileges list. 4.
5 Roles Copying a role You can create a new role by copying an existing one. When you copy a role, you copy the selected privileges in that role. To copy an existing role, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Select the role you want to copy in the Roles table and click Duplicate. The Duplicate Role dialog box displays. 3. Enter a name of the role in the Name field. 4. (Optional) Enter a short description for the role in the Description field. 5.
Areas of responsibility 5 Deleting a role To delete a role, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Select the role you want to delete in the Roles table and click Delete. 3. Click Yes on the confirmation message. 4. Click Close to close the Users dialog box. Areas of responsibility NOTE You must have User Management Read and Write privileges to view, add, modify, or delete operational areas of responsibility.
5 Areas of responsibility 6. Click OK to save the new AOR and close the Add AOR dialog box. The new AOR displays in the AOR list of the Users dialog box. 7. Click Close to close the Users dialog box. Assigning products to an AOR You can assign fabricsand hosts to an AOR from the Add, Edit, or Duplicate AOR dialog box. To assign fabricsand hosts to an AOR, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Click Add, Edit, or Duplicate under the AOR table.
Areas of responsibility 5 Copying an AOR To create a new AOR by copying an existing one, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Select the AOR you want to copy in the AOR table and click Duplicate. The Duplicate AOR dialog box displays. 3. Change the name of the AOR in the Name field. 4. (Optional) Change the short description for the AOR in the Description field. 5. Assign or remove products as needed.
5 LDAP authorization Deleting an AOR To delete an AOR, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Select the AOR you want to delete in the AOR table and click Delete. 3. Click Yes on the confirmation message. 4. Click Close to close the Users dialog box. LDAP authorization NOTE You must have User Management Read and Write privileges to map roles and AORs to Active Directory groups.
LDAP authorization 5 10. Click OK. The Active Directory Groups table displays with all first level Active Directory groups available in the specified LDAP server, as well as any Active Directory groups already mapped in the Management server (Local database). To assign or remove roles and AORs, refer to “Assigning roles and AORs to an Active Directory group” on page 155 or “Removing roles and AORs from an Active Directory group” on page 155. 11. Click Close to close the Users dialog box.
5 LDAP authorization Deleting an Active Directory group To delete an Active Directory group, complete the following steps. 1. Select one or more Active Directory groups that you want to delete from the Active Directory Groups table. 2. Click Delete. 3. Click Yes on the confirmation message. 4. Click OK on the deletion successful message. 5. Click OK to save your work.
Chapter 6 Call Home In this chapter • About call home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Showing a call home center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Hiding a call home center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Editing a call home center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Enabling a call home center . . . . . . . . .
6 About call home About call home NOTE Call Home is supported on Windows systems for all modem and E-mail call home centers and is supported on Unix for the E-mail call home centers. Call Home notification allows you to configure the Management application Server to automatically send an e-mail or dial-in to a support center to report system problems on specified devices (Fabric OSand M-EOS switches, routers, and directors).
About call home 6 • Adds an entry to the Master Log file and screen display. • Generates a XML report (only available with EMC call centers) with the product details which is sent with the E-mail. • Generates an HTML report for E-mail-based Call Home centers. For more information about Call Home events, refer to “Call Home Event Tables” on page 957. For more information about Event Management, refer to “Fault Management” on page 843.
6 Showing a call home center Showing a call home center To show a call home center, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays (Figure 55). FIGURE 55 Call Home dialog box 2. Click Show/Hide Centers (beneath the Call Home Centers table). The Centers dialog box displays with a predefined list of call home centers (Figure 56). FIGURE 56 Centers dialog box 3.
Hiding a call home center 6 Hiding a call home center NOTE Before you can hide a call home center, you must remove all assigned products. To hide a call home center, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays. 2. Click Show/Hide Centers (beneath the Call Home Centers table). The Centers dialog box displays with a predefined list of call home centers. 3. Clear the check boxes of the call home centers you want to hide and click OK.
6 Editing a call home center FIGURE 57 Configure Call Home Center dialog box (Brocade International or IBM option) 4. Make sure the call home center type you selected displays in the Call Home Centers list. 5. Select Enable to enable this call home center. 6. Set the time interval at which to check the call home center by selecting the Set the heartbeat interval at ___ days (1-28) check box and entering the interval in the field. 7.
Editing a call home center 6 Editing the Brocade North America call home center Modem call home centers are only available for Brocade. To edit this call home center, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays. 2. Select Brocade North America in the Call Home Centers table. 3. Click Edit Centers (beneath the Call Home Centers table). The Configure Call Home Center dialog box displays(Figure 58).
6 Editing a call home center Editing an E-mail call home center E-mail call home centers are available for Brocade, IBM, and Oracle. To edit one of these call home centers, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays. 2. Select the call home center you want to edit (Brocade E-mail, IBM E-mail, or Oracle E-mail) in the Call Home Centers table. 3. Click Edit Centers (beneath the Call Home Centers table).
Editing a call home center 6 14. Enter a password in the SMTP Server Settings - Password field. This is a required field when the SMTP server authentication is enabled. 15. Enter the e-mail address for replies in the E-mail Notification Settings - Reply Address field. 16. Enter the customer e-mail address in the E-mail Notification Settings - Send To Address field. 17. Click Send Test to test the mail server. The selected call home center must be enabled to test the mail server.
6 Editing a call home center 7. Enter the path to the ConnectEMC application in the ConnectEMC field or browse to the ConnectEMC application location. 8. Enter the phone number or extension of the local server in the Local Server - Modem # field. 9. Enter the identification number of the local server in the Local Server - Cabinet Serial # field. 10. Enter the site name for the local server in the Local Server - Site Name field. 11. Click Send Test to test the Connect EMC application.
Enabling a call home center 7. 6 Enter the port number (default is 2069) of the call home center in the Port field 8. Click Send Test to test the address. The selected call home center must be enabled to test the IP address. A faked event is generated and sent to the selected call home center. You must contact the call home center to verify that the event was received and in the correct format.
6 Testing the call home center connection Testing the call home center connection Once you add and enable a call home center, you should verify that call home is functional. To verify call home center functionality, complete the following steps. 1. Select Monitor > Event Notification > Call Home. 2. Click Edit Centers (beneath the Call Home Centers table). The Configure Call Home Center dialog box displays. 3. Select the center you want to check in the Call Home Centers list. 4.
Viewing Call Home status 6 Viewing Call Home status You can view call home status from the main Management application window or from the Call Home Notification dialog box. The Management application enables you to view the call home status at a glance by providing a call home status icon on the Status Bar. The following table illustrates and describes the icons that indicate the current status of the call home function.
6 Assigning a device to the call home center Assigning a device to the call home center Discovered devices (switches, routers, and directors) are not assigned to a corresponding call home center automatically. You must manually assign each device to a call home center before you use call home. To assign a device or multiple devices to a call home center, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays. 2.
Removing all devices and filters from a call home center 6 Removing all devices and filters from a call home center To remove all devices and filters from a call home center, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays. 2. Select the call home center from which you want to remove devices and filters in the Call Home Center table. 3. Click the left arrow button. A confirmation message displays. 4. Click OK.
6 Assigning an event filter to a call home center Assigning an event filter to a call home center Event filters allow call home center users to log in to a Management server and assign specific event filters to the devices. This limits the number of unnecessary or ‘acknowledge’ events and improves the performance and effectiveness of the call home center. You can only select one event filter at a time; however, you can assign the same event filter to multiple devices or call home centers.
Overwriting an assigned event filter 6 Overwriting an assigned event filter A device can only have one event filter at a time; therefore, when a new filter is applied to a device that already has a filter, you must confirm the new filter assignment. To overwrite an event filter, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays. 2. Select the event filter you want to apply in the Call Home Event Filters table.
6 Removing an event filter from a device Removing an event filter from a device To remove an event filter from a device, complete the following steps. 1. Select Monitor > Event Notification > Call Home. The Call Home dialog box displays. 2. Choose one of the following options in the Call Home Centers table: • Right-click an event filter assigned to a device and select Remove Filter. • Right-click a device to which the event filter is assigned and select Remove Filter.
Chapter 7 View Management In this chapter • View management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Creating a customized view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Editing a customized view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Deleting a customized view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Copying a view . . . . . . . . . . . . . . . . . . .
7 Creating a customized view Creating a customized view You may want to customize the Product List and Connectivity Map to simplify management of large SANs by limiting the topology size or Product List columns. For each customized view, you can specify the fabrics and hosts that display on the Connectivity Map, as well as the columns and device groupings that display on the Product List. Customized view settings reside on the server.
Editing a customized view 7 3. Click the Fabrics tab. 4. In the Available Fabrics table, select the fabrics you want to include in the view and click the right arrow button to move your selections to the Selected Fabrics and Hosts table. To select more than one row, press CTRL and click individual rows. To select muliple sequental rows, press SHIFT and click on a sequence of rows. 5. Click the Hosts tab. FIGURE 63 Create View dialog box - Hosts tab 6.
7 Editing a customized view FIGURE 64 Edit View dialog box - Fabrics tab 2. Click the Fabrics tab. 3. In the Available Fabrics table, select the fabrics you want to include in the view and use the right arrow button to move your selections to the Selected Fabrics and Hosts table. 4. Click the Hosts tab. FIGURE 65 Edit View dialog box - Hosts tab 5.
Deleting a customized view 7 Deleting a customized view To delete a customized view, use the following procedure. 1. Select View > Manage View > Delete View > View_Name. 2. Click Yes on the message. If you delete the current view, the view changes to the default view (View All). Copying a view To copy a customized view, use the following procedure. 1. Use one of the following methods to open the Copy View dialog box: • Select View > Manage View > Copy View > View_Name.
7 SAN topology layout SAN topology layout You can customize various parts of the topology, including the layout of devices and connections and groups’ background colors, to easily and quickly view and monitor devices in your SAN. The following menu options are available on the View menu. Use these options to customize the topology layout. • Map Display. Select to specify a new layout for the desktop icons, background color for groups, and line type for connections between icons. • Domain ID/Port #.
Customizing the layout of devices on the topology 7 Customizing the layout of devices on the topology You can customize the layout of devices by group type or for the entire Connectivity Map. Customizing the layout makes it easier to view the SAN and manage its devices. Group types include Fabric, Host, Storage, Router and Switch groups. 1. Right-click a group or the Connectivity Map and select Map Display. The Map Display Properties dialog box displays.
7 Customizing the layout of connections on the topology 3. Select the Set as Default Layout check box to set your selection as the default. 4. Click OK on the Map Display Properties dialog box. Customizing the layout of connections on the topology You can change the way inter-device connections display on the topology. 1. Right-click a group or the Connectivity Map and select Map Display. The Map Display Properties dialog box displays. 2.
Reverting to the default background color 7 3. Select or specify a color and preview it in the Preview pane. • To pick a color from a swatch, select the Swatches tab. Select a color from the display. • To specify a color based on hue, saturation, and brightness, click the HSB tab. Specify the hue (0 to 359 degrees), saturation (0 to 100%), and brightness (0 to 100%). • To specify a color based on values of red, green, and blue, click the RGB tab. Specify the values for red, green, and blue (0 to 255).
7 Changing the port label Changing the port label To change the port label, complete the following steps. 1. Select a port in the Connectivity Map or Product List. 2. Select View > Port Label, and select one of the following options: • • • • • • • Name. Displays the name as the port label. Port Number. Displays the port number as the port label. Port Address. Displays the port address as the port label. Port WWN. Displays the port world wide name as the port label. User Port #.
Grouping on the topology 7 Grouping on the topology To simplify management, devices display in groups. Groups are shown with background shading and are labeled appropriately. You can expand and collapse groups to easily view a large topology. Collapsing groups To collapse a single group on the topology, choose one of the following options: • Click the icon at the top right-hand corner of the group on the topology ( ). • Double-click in the group, but not on a device.
7 Grouping on the topology Configuring custom connections NOTE Active zones must be available on the fabric. To create a display of the connected end devices participating in a single zone or group of zones, complete the following steps. 1. Choose one of the following options: • Select a fabric on the topology and select View > Connected End Devices > Custom. • Right-click a fabric on the topology and select Connected End Devices > Custom from the shortcut menu.
Customizing the main window 7 Deleting a custom connection configuration NOTE Active zones must be available on the fabric. To delete a custom connection configuration, complete the following steps. 1. Choose one of the following options: • Select a fabric on the topology and select View > Connected End Devices > Custom. • Right-click a fabric on the topology and select Connected End Devices > Custom from the shortcut menu. The Connected End Devices - Custom display for Fabric dialog box displays. 2.
7 Customizing the main window b. Select a zoom percentage. c. Click OK to save your changes and close the Zoom dialog box. Zooming out To zoom out of the Connectivity Map, use one of the following methods: • Click the zoom-out icon ( ) on the Connectivity Map toolbar. • Press CTRL and the minus sign on the number pad on the keyboard. • Use the Zoom dialog box. a. Select View > Zoom. The Zoom dialog box displays. b. Select a zoom percentage. c.
Customizing the main window 7 4. Click Save. If the file name is a duplicate, a message displays. Click Yes to replace the image or click No to go back to the Export Topology To PNG File dialog box and change the file name. The File Download dialog box displays. 5. Click Open to view the image or click Cancel to close the dialog box.
7 Customizing the main window FIGURE 70 Customize Columns dialog box 2. Choose from the following options: • Select the check box to display a column. OR Select the column name and click Show. • Clear the check box to hide a column. OR Select the column name and click Hide. • Click Select All to select all check boxes. • Click Deselect All to clear all check boxes. • Click Restore Defaults to restore the table to the original settings. 3. Click OK.
Customizing the main window 7 Resizing the columns You can resize a single column or all columns in the table. To resize a single column, right-click the column header and select Size Column to Fit or Table > Size Column to Fit. To resize all columns in the table, right-click anywhere in the table and select Size All Columns to Fit or Table > Size All Columns to Fit. Sorting table information To sort the table by a single column, click the column header.
7 Search Searching for information in a table You can search for information in the table by any of the values found in the table. 1. Right-click anywhere in the table and select Table > Search. The focus moves to the Search field. FIGURE 71 Search field 2. Enter all or part of the search text in the Search field and press Enter. The first instance is highlighted in the table. 3. Press Enter to go to the next instance of the search text.
Search 7 Searching for a device You can search for a device by name, WWN, or device type. When searching in the Connectivity Map, make sure you search the right view (View > Manage View > Display View > View_Name) with the appropriate options of port display (View > Port Display > Display_Option) and connected end devices (View > Port Display > Show All) enabled. To search for a device, complete the following steps. 1. Enter your search criteria in the search field.
7 Search 3. Enter your search criteria in the search field. • Text—Enter a text string in the search text box. This search is case sensitive. For example, you can enter the first five characters in a device name. All products in the Product List that contain the search text display highlighted. • Regular Expression—Enter a Unicode regular expression in the search text box. (For hints, refer to “Regular Expressions” on page 983.
Chapter 8 Third-party tools In this chapter • About third-party tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Starting third-party tools from the application . . . . . . . . . . . . . . . . . . . . . . • Launching a Telnet session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Launching an Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Launching Web Tools. . . . . . . . . . . . . . . . . . . .
8 Starting third-party tools from the application Starting third-party tools from the application You can open third-party tools from the Tools menu or a device’s shortcut menu. Remember that you cannot open a tool that is not installed on your computer. You must install the tool on your computer and add the tool to the Tools menu or the device’s shortcut menu. NOTE Installing tools is only available with the Trial and Licensed version versions. To open an application, perform the following steps. 1.
Launching an Element Manager 8 Launching an Element Manager Element Managers are used to manage Fibre Channel switches and directors. You can open a device’s Element Manager directly from the application. To launch a device’s Element Manager, complete the following steps. On the Connectivity Map, double-click the device you want to manage. The Element Manager displays. OR On the Connectivity Map, right-click the device you want to manage and select Element Manager > Hardware. The Element Manager displays.
8 Launching Web Tools Launching Web Tools Use Web Tools to enable and manage Fabro OS access gateway, switches, and directors. You can open Web Tools directly from the application. For more information about Web Tools, refer to the Brocade Web Tools Administrator’s Guide. For more information about Fabro OS access gateway, switches, and directors, refer to the documentation for the specific device. To launch a device’s Element Manager, complete the following steps.
Launching FCR configuration 8 Launching FCR configuration Use FCR Configuration to launch the FC Routing module, which enables you to share devices between fabrics without merging the fabrics. You can open the FC Routing module directly from the Management application. For more information about FC Routing, refer to the Brocade Web Tools Administrator’s Guide. The FCR Configuration option is available only for the following devices with Fabric OS 5.
8 Launching Name Server Launching Name Server Use Name Server to view entries in the Simple Name Server database. You can open the Name Server module directly from the Management application. For more information about Name Server, refer to the Brocade Web Tools Administrator’s Guide. NOTE You must have Element Manager - Product Administration privileges for the selected device to launch Web Tools.
Launching HCM Agent 8 Launching HCM Agent Use Fabric OS HCM Agent to enable and manage Fabric OS HBAs. You can open HCM Agent directly from the application. For more information about HCM Agent, refer to the HCM Agent Administrator’s Guide. For more information about Fabric OS HBAs, refer to the documentation for the specific device. To launch a Fabric OS HBA’s Element Manager, complete the following steps.
8 Launching Fabric Watch Launching Fabric Watch Use Fabric Watch as an health monitor that allows you to enable each switch to constantly monitor its SAN fabric for potential faults and automatically alerts you to problems long before they become costly failures.. For more information about Fabric Watch, refer to the Fabric Watch Administrator’s Guide. For more information about Fabro OS access gateway, switches, and directors, refer to the documentation for the specific device.
Adding a tool 8 Adding a tool You can specify third-party tools so they appear on the Setup Tools dialog box. From there, you can add them to the Tools menu and then open the tools directly from the Management application. To add a tool, complete the following steps. 1. Select Tools > Setup. The Setup Tools dialog box displays. 2. Click the Tools Menu tab. 3. Click Define. The Define Tools dialog box displays (Figure 72). FIGURE 72 Define Tools dialog box 4.
8 Entering the server IP address of a tool Entering the server IP address of a tool If the third-party tool is a web-based application, you must enter the IP address of the applications server as a parameter to be able to open the application. To enter the server IP address, complete the following steps. 1. Select Tools > Setup. The Setup Tools dialog box displays. 2. Click the Tools Menu tab.
Adding an option to the Tools menu FIGURE 73 8 Setup Tools dialog box (Tools menu tab) 3. Type a label for the option as you want it to appear on the Tools menu in the Menu Text field. 4. Select the application from the Tool list, or click Define if you want to specify a new tool. To specify a new tool, refer to “Adding a tool” on page 203. 5. (Optional) Enter parameters, such as a URL, in the Parameters field. 6. (Optional) Select a keyboard shortcut in the Keystroke list.
8 Changing an option on the Tools menu Changing an option on the Tools menu You can edit parameters for third-party tools that display on the Tools menu. To edit a option to the tools menu, complete the following steps. 1. Select Tools > Setup. The Setup Tools dialog box displays. 2. Click the Tools Menu tab. The Tool Menu Items table displays all configured tools, including the tool name as it displays on the Tools menu, parameters, and keystroke shortcuts. 3.
Adding an option to a device’s shortcut menu 8 Adding an option to a device’s shortcut menu You can add an option to a device’s shortcut menu. To add an option to the device’s shortcut menu, complete the following steps. 1. Select Tools > Setup. The Setup Tools dialog box displays. 2. Click the Product Menu tab. The Product Popup Menu Items table displays all configured shortcut menu options. 3. Type or select the text in the Menu Text list as you want it to appear on the menu. 4.
8 Changing an option on a device’s shortcut menu Changing an option on a device’s shortcut menu You can change the parameters for a tool that displays on a device’s shortcut menu. To edit an option to the device’s shortcut menu, complete the following steps. 1. Select Tools > Setup. The Setup Tools dialog box displays. 2. Click the Product Menu tab. The Product Popup Menu Items table displays all configured shortcut menu options. 3.
Removing an option from a device’s shortcut menu 8 Removing an option from a device’s shortcut menu You can remove a tool that displays on a device’s shortcut menu. To remove an option to the device’s shortcut menu, complete the following steps. 1. Select Tools > Setup. The Setup Tools dialog box displays. 2. Click the Product Menu tab. The Product Popup Menu Items table displays all configured menu options. 3. Select the menu item you want to remove in the Product Popup Menu Items table. 4. Click Remove.
8 Microsoft System Center Operations Manager (SCOM) plug-in SCOM plug-in requirements • Make sure you import the Management application management pack (Management_Application_Name.FabricView.xml) to the SCOM Server prior to registering the SCOM Plug-in. The management pack is located in the following directory on the DVD scom/OEM_Name. • Make sure the Management application server host is managed by the SCOM Server in agent managed mode.
Microsoft System Center Operations Manager (SCOM) plug-in 8 Editing a SCOM server To edit the SCOM server, complete the following steps. 1. Select Tools > Plug-in for SCOM. The Plug-in for SCOM dialog box displays. 2. Select the server you want to edit and click Edit. The Edit SCOM Server dialog box displays. The Host field is not editable in the Edit SCOM Server dialog box. 3. Edit the domain name in the Domain field. 4. Enter your user ID and password. 5. Click OK. 6. Click Close.
8 212 Microsoft System Center Operations Manager (SCOM) plug-in Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 9 Server Management Console In this chapter • Server Management Console overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Changing server port numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • AAA Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Restoring the database. . . .
9 Services Launching the SMC on Linux Perform the following steps to launch the Server Management Console on Linux systems. 1. On the Management application server, go to the following directory: Install_Directory/bin 2. Type the following at the command line: ./smc OR sh smc Services You must be logged in at the administrator (Windows systems) or root (UNIX systems) level to stop, start, and restart the Management application services.
Services 9 3. Review the following information for each available service. • • • • Name—The name of the server; for example, FTP Server or Database Server. Process Name—The name of the process; for example, postgres.exe (Database Server). Status—The status of the service; for example, started or stopped. Start Time—The date and time the service started. The Start Time for Service Location Protocol displays as ‘Not Available’. 4. Click Close to close the Server Management Console.
9 Services Starting all services NOTE The Start button restarts running services in addition to starting stopped services which causes client-server disconnect. To start all services, complete the following steps. 1. Launch the Server Management Console. 2. Click the Services tab. 3. Click Start to start all services. NOTE If the server is configured to use an external FTP server, the Server Management Console does not attempt to start the built-in FTP service. 4.
Changing server port numbers 9 Changing server port numbers Use the Ports tab of the Server Management Console to change the Management application server and Web server port numbers. The default Web Server port number is 80. The Management application server default port number is 24600. To change the Management application server or web server port number, complete the following steps. 1. Click the Ports tab. 2. Type a new port number in the Management_Application_Name Server or Web Server port field.
9 AAA Settings • Know the TCP port you are using. For Radius servers, ports 1812 or 1645 (actually UDP ports) are commonly used. Check with the Radius server vendor if you are not sure which port to specify. • Know how long you want to wait between attempts to reach the server if it is busy. This is expressed as a timeout value (default is 3 seconds) in seconds. Values are between 1 and 15.
AAA Settings 9 6. Select the authentication policy (PAP or CHAP) from the Authentication Type field. Default is CHAP. 7. Enter the shared secret in the Shared Secret and Confirm Secret fields. 8. Enter the timeout timer value (in seconds) that specifies the amount of time to wait between retries when the server is busy in the Timeout (Sec) field. Default is 3 seconds. 9. Enter the number of attempts to be made to reach a server before assuming it is unreachable in the Attempts field.
9 AAA Settings Configuring an LDAP server If you are using an LDAP server for authentication, make the following preparations first: • Have the IP address of the server available. • Know the TCP port you are using. The LDAP server uses Transport Layer Security (TLS). LDAP over TLS generally uses port 389. Check with the LDAP server administrator if you are not sure which port to specify. • Know how long you want to wait between attempts (default is 3 seconds) to reach the server if it is busy.
AAA Settings 9 3. Click Add. The Add or Edit LDAP Server dialog box displays (Figure 78). FIGURE 78 Add or Edit LDAP server 4. Enter the LDAP server’s IP address in the IP Address field. 5. Enter the TCP port used by the LDAP server in the TCP Port field. Default is 389. 6. Enter the timeout timer value (in seconds) that specifies the amount of time to wait between retries when the server is busy in the Timeout (Sec) field. Default is 3 seconds. 7.
9 AAA Settings Configuring a TACACS+ server To configure TACACS+ server authentication, complete the following steps. 1. Select the AAA Settings tab. 2. For Primary Authentication, select TACACS+ Server. FIGURE 79 AAA Settings tab - TACACS+ server 3. Click Add. FIGURE 80 Add or Edit TACACS+ server 4. Enter the TACACS+ server’s IP address in the Network Address field. 5. Enter the TCP port used by the TACACS+ server in the TCP Port field. Default is 49. 6.
AAA Settings 9 9. Click OK to return to the AAA Settings tab. 10. Set secondary authentication by selecting one of the following options from the Secondary Authentication list: • Local Database • None 11. Set the fall back condition to secondary authentication by selecting one of the following options from the Fail Over Option list: • TACACS+ Server Not Reachable • TACACS+ Server Authentication Failed 12.
9 AAA Settings 7. Enter your user ID and password and click Test. Test verifies your user ID and password on the switch and verifies user privileges on the Management application server. 8. Click Apply to save the configuration. Configuring Windows authentication Windows authentication enables you to authenticate a user account against the Windows user accounts and the Management application server when running on Windows hosts.
Restoring the database 9 Displaying the client authentication audit trail All responses to authentication requests coming from clients are logged to an audit trail log file. This file is automatically backed up on the first day of every month. 1. Select the AAA Settings tab. 2. Click Display next to Authentication Audit Trail. The Login dialog box displays. 3. Enter your username and password in the appropriate fields and click OK. The defaults are Administrator and password, respectively.
9 Restoring the database FIGURE 81 Restore tab 4. Click Browse to select the path (defined in the Output Directory field on the Options dialog box - Backup pane) to the database backup location. 5. Click Restore. Upon completion, a message displays the status of the restore operation. Click OK to close the message and the Server Management Console. For the restored data to take effect, re-launch the Configuration Wizard using the instructions in “Launching the Configuration Wizard” on page 28.
Capturing technical support information 9 Capturing technical support information The Technical Support Information tab of the SMC allows you to capture technical support information for the Management application as well as the configuration files for all switches in discovered fabrics. This information is saved in a zip file in a location that you specify. To capture technical support information, complete the following steps. 1. Select the Technical Support Information tab.
9 Upgrading HCM on the Management server 3. Enter the path where you want to save the support data and a name for the support save file in the Output Path field. For example, Full_Path\Support_Save_File_Name.zip. You can also browse to the location you want to save the support data and append the file name to the path when you return to the Techncial Support Information tab. If you do not specify an output path, the Management application automatically saves the data to the Install_Home/support directory.
Defining the performance data aging interval 9 Defining the performance data aging interval The Performance Data Aging tab enables you to define the performance data collection interval. NOTE Changes to the performance data aging option requires a server restart. NOTE You can only restart the server using the Server Management Console (Start > Programs > Management_Application_Name 11.X.X > Server Management Console). To define the performance data collection interval, complete the following steps. 1.
9 SMI Agent configuration 5. Click Yes on the confirmation message. The server automatically restarts. 6. Click Close. SMI Agent configuration The SMIA Configuration Tool enables you to configure SMI Agent settings, such as security, CIMOM, and certificate management. This tool is automatically installed with the Management application as part of the Server Management Console.
SMI Agent configuration 9 3. Enter your username and password in the appropriate fields. The defaults are Administrator and password, respectively. If you migrated from a previous release, your username and password do not change. 4. Select or clear the Save password check box to choose whether you want the application to remember your password the next time you log in. 5. Click Login. The SMIA Configuration Tool dialog box displays.
9 SMI Agent configuration 4. Enter your username and password in the appropriate fields and click OK. The defaults are Administrator and password, respectively. If you migrated from a previous release, your username and password do not change. The SMIA Configuration Tool dialog box displays. Launching a remote SMIA configuration tool To launch a remote SMIA configuration tool, complete the following steps. 1.
SMI Agent configuration 9 SLP support includes the following components: • slpd script starts the slpd platform • slpd program acts as a Service Agent (SA). A different slpd binary executable file exists for UNIX and Windows systems. • slptool script starts the slptool platform-specific program • slptool program can be used to verify whether SLP is operating properly or not. A different slptool exists for UNIX and Windows.
9 SMI Agent configuration • slptool findattrs service:wbem:https://IP_Address:Port NOTE Where IP_Address:Port is the IP address and port number that display when you use the slptool findsrvs service:wbem command. Use this command to verify that Management application SMI Agent SLP service is properly advertising its WBEM SLP template over the HTTP protocol. Example output: Install_Home\cimom\bin>slptool findattrs service:wbem:http://10.24.35.61:5988 (template-type=wbem),(template-version=1.
SMI Agent configuration 9 SLP on UNIX systems This section describes how to verify the SLP daemon on UNIX systems. SLP file locations on UNIX systems • SLP log—Install_Home/cimom /cfg/slp.log • SLP daemon—Install_Home/cimom /cfg/slp.conf You can reconfigure the SLP daemon by modifying this file. • SLP register—Install_Home/cimom /cfg/slp.reg You can statically register an application that does not dynamically register with SLP using SLPAPIs by modifying this file.
9 SMI Agent configuration Verifying SLP service installation and operation on Windows systems 1. Launch the Server Management Console from the Start menu. 2. Click Start to start the SLP service. 3. Open a command window. 4. Type cd c:\Install_Home\cimom \bin and press Enter to change to the directory where slpd.bat is located. 5. Type > slptool findsrvs service:service-agent and press Enter to verify the SLP service is running as a Service Agent. 6.
SMI Agent configuration 9 Accessing Management application features To access Management application features such as, fabric and host discovery, role-based access control, application configuration and display options, server properties, as well as the application name, build, and copyright, complete the following steps. 1. Click the Home tab, if necessary. 2. Select from the following to access the feature or dialog box.
9 SMI Agent configuration 1. Click the Authentication tab. FIGURE 87 Authentication tab 2. Select the Enable Client Mutual Authentication check box, as needed. If the check box is checked, CIM client mutual authentication is enabled. If the check box is clear (default), client mutual authentication is disabled. 3. Select the Enable Indication Mutual Authentication check box, as needed. If the check box is checked, indication mutual authentication is enabled.
SMI Agent configuration 9 1. Click the Authentication tab. 2. Choose from one of the following options: • Select No Authentication to allow the CIM client to query the CIMOM server without providing credentials; however, note that the CIMOM server requires the Management application credentials to connect to the Management application server to retrieve the required data. To provide Management application credentials, complete the following steps. a.
9 SMI Agent configuration Configuring the SMI Agent port number To configure the SMI Agent port number, complete the following steps. 1. Click the CIMOM tab. FIGURE 88 CIMOM tab 2. Select or clear the Enable SSL check box, to enable or disable SSL for the SMI Agent. NOTE Disabling SSL will disable Indication and Client Mutual Authentication. If the check box is checked (default), SSL is enabled. If the check box is clear, SSL is disabled. 3.
SMI Agent configuration 9 4. Click Apply. NOTE Changes on this tab take effect after the next CIMOM server restart. NOTE You can only restart the server using the Server Management Console (Start > Programs > Management_Application_Name 11.X.X > Server Management Console). If you disabled SSL, a confirmation message displays. Click Yes to continue. 5. Click Close to close the SMIA Configuration Tool dialog box.
9 SMI Agent configuration Configuring the CIMOM log NOTE You must have SAN - SMI Operation Read and Write privileges to view or make changes on the CIMOM tab. To configure the CIMOM log, complete the following steps. 1. Click the CIMOM tab. 2. Select a log category from the Log Level list to start logging support data for the server. Options include the following: • Off—select to turn off logging support data.
SMI Agent configuration 9 Certificate management NOTE You must have SMI Operation Read and Write privileges to view or make changes on the Certificate Management tab. The Certificate Management tab enables you to manage your CIM client and Indication authentication certificates.
9 SMI Agent configuration 5. Click Import. The new certificate displays in the Certificates list and text box. If the certificate location is not valid, an error message displays. Click OK to close the message and reenter the full path to the certificate location. If you did not enter a certificate name, an error message displays. Click OK to close the message and enter a name for the certificate. If the certificate file is empty or corrupted, an error message displays. Click OK to close the message. 6.
SMI Agent configuration 9 Deleting a certificate NOTE You must have SMI Operation Read and Write privileges to view or make changes to the Certificate Management tab. To delete a certificate, complete the following steps. 1. Click the Certificate Management tab. 2. Select Client or Indication from the Authentication list. The appropriate certificates display in the Certificates list. 3. Select the certificate you want to delete in the Certificates list. 4. Click Delete. 5.
9 SMI Agent configuration 1. Click the Summary tab. FIGURE 90 Summary tab 2. Review the summary. NOTE When the CIMOM server is stopped, the server configuration information does not display on the Summary tab. The following information is included in the summary. 246 Field/Component Description Client Mutual Authentication Displays whether or not the client mutual authentication is enabled or disabled for the Server Configuration and the Current Configuration.
SMI Agent configuration 9 Field/Component Description Log Level Displays the log level for the Server Configuration and the Current Configuration. Options include the following: • 10000—Off • 1000—Severe • 900—Warning • 800—Info (default) • 700—Config • 500—Fine • 400—Finer • 300—Finest • 0—All Managed Ports Displays the number of managed ports. For more information about managed port count rules, refer to “Managed count” on page 44. Licensed Ports Displays the number of licensed ports. 3.
9 248 SMI Agent configuration Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 10 SAN Device Configuration In this chapter • Configuration repository management . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Viewing device properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Enhanced group management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Ports . . . . . . . . . . . . . . . . . . . . . . . .
10 Configuration repository management Saving switch configurations NOTE Save switch configuration is only supported on Fabric OS switches. NOTE To save switch configuration on more than one switch at a time, you must have the Enhanced Group Management license. Configuration files are uploaded from the selected switches and stored in individual files. Files are named with the convention cfg_fabricName_switchName_domainID. 1. Select Configure > Configuration > Save.
Configuration repository management 10 Restoring a switch configuration for a selected device The Restore Switch Configuration dialog box enables you to download a previously saved switch configuration to a selected device. To restore a switch configuration, complete the following steps. 1. Right-click a device in the Product List or the Connectivity Map, and select Configuration > Restore. The Restore Switch Configuration dialog box displays. FIGURE 92 Restore Switch Configuration dialog box 2.
10 Configuration repository management Backing up a switch configuration NOTE The Enhanced Group Management (EGM) license must be activated on a switch to perform this procedure and to use the supportSave module. If a periodic backup is scheduled at the SAN level, that backup will apply to all switches from all fabrics discovered. Any new fabrics being discovered are automatically added to the list of fabrics to be backed up.
Configuration repository management 10 3. Set the Schedule parameters. These include the following: - The desired Frequency for backup operations (daily, weekly, monthly). The Day you want back up to run. If Frequency is Daily, the Day list is grayed out. If Frequency is Weekly, choices are days of the week (Sunday through Saturday). If Frequency is Monthly, choices are days of the month (1 through 31). - The Time (hour, minute) you want back up to run.
10 Configuration repository management Restoring a configuration from the repository If you delete a fabric or switch from discovery, the configuration remains in the repository until you delete it manually. Stored configurations are linked to the switch WWN; therefore, if the IP address or switch name is changed and then rediscovered, the Switch Configuration Repository dialog box displays the new switch name and IP address for the old configuration.
Configuration repository management 10 Viewing configuration file content NOTE This feature requires a Trial or Licensed version. You can view switch configuration file content in a text file. 1. Right-click a device in the Product List or the Connectivity Map, and select Configuration > Configuration Repository. The Switch Configuration Repository dialog box displays. 2. Click View. The configuration details display.
10 Configuration repository management Searching the configuration file content NOTE This feature requires a Trial or Licensed version. To search the configuration file content, complete the following steps. 1. Right-click a device in the Product List or the Connectivity Map, and select Configuration > Configuration Repository. The Switch Configuration Repository dialog box displays. 2. Click View. The configuration details display. 3.
Configuration repository management 10 Deleting a configuration NOTE This feature requires a Trial or Licensed version. 1. Right-click a device in the Product List or the Connectivity Map, and select Configuration > Configuration Repository. The Switch Configuration Repository dialog box displays. 2. Select the configuration you want to delete, and click Delete. Exporting a configuration NOTE This feature requires a Trial or Licensed version. 1.
10 Configuration repository management Keeping a copy past the defined age limit NOTE This feature requires a Trial or Licensed version. 1. Right click a device in the Product List or the Connectivity Map, and select Configuration > Configuration Repository. The Switch Configuration Repository dialog box displays. 2. Select the check box under Keep for the configuration you want to preserve.
Enhanced group management 10 Enhanced group management Use Enhanced Group Management (EGM), a separate licensed feature, to control access to specific features on Fabric OS devices. The features affected include the following: • Firmware Download - enables you to perform group firmware download. For specific instructions for firmware download, refer to “Firmware management” on page 259. • Security - enables you to perform Group Security Policy Replication.
10 Firmware management Displaying the firmware repository The firmware repository is available on the Firmware Management dialog box. The Management application supports .zip and .gz compression file types for firmware files. 1. Select Configure > Firmware Management. The Firmware Management dialog box displays. 2. Select the Repository tab (Figure 97). Initially, the repository is empty. You must import firmware files into the repository.
Firmware management 10 Importing a firmware file and release notes Firmware files and release notes can be imported into the Firmware Repository. 1. Select Configure > Firmware Management. The Firmware Management dialog box displays. 2. Select the Repository tab (Figure 97). 3. Click Import. The Import Firmware from File dialog box displays (Figure 98). FIGURE 98 Import firmware 4. Type in the location of the firmware file and release notes, or use Browse to select the location.
10 Firmware management Download firmware NOTE Non-disruptive firmware download (HCL) is not supported when downgrading from Fabric OS version 6.2 to 6.1. You must remove all non-default logical switches and disable Virtual Fabrics before downgrading. NOTE You cannot use Fabric OS firmware download with command line options in the Management application. You can download firmware using the Firmware Management dialog box. 1. Select Configure > Firmware Management.
Firmware management 10 6. To download the firmware to the selected switches one at a time, select the Serial download check box. Use the Up and Down buttons to determine the order in which the firmware is downloaded to the switches. If firmware download fails on one switch, all other switches in the queue will be skipped. If the Serial download check box is cleared, the download occurs in parallel on the switches (up to 20 at a time). 7.
10 Properties Properties You can customize the device and fabric Properties dialog boxes to display only the data you need by adding, editing, and deleting property labels. You can also edit property fields to change information. Viewing Fabric properties To view the properties for a fabric, complete the following step. 1. Right-click any fabric and select Properties. The Fabric_Name Properties dialog box displays, with information related to the selected fabric.
Properties 10 Viewing device properties To view the properties for a device or, complete the following step. 1. Right-click any product icon and select Properties. The Properties dialog box displays, with information related to the selected device (such as, switches, directors, HBAs, trunks, tunnels, and nodes). Depending on the device type, some of the properties listed in the following table may not be available for all products.
10 Properties TABLE 17 Device properties (Continued) Field/Component Description IP Address The device’s IP address. IPSec Policy # 266 The IPSec policy number. Also includes the following information: Authentication Algorithm Encryption Algorithm SA Life • • • L2 Capable Whether the device is Layer 2 capable. L3 Capable Whether the device is Layer 3 capable. L2 Mode The Layer 2 mode. Options include Access, Converged, or Trunk. LAG ID The link aggregation group identifier.
Properties TABLE 17 10 Device properties (Continued) Field/Component Description State The device’s state, for example, online or offline. Status The operational status. Switch Name The switch name. Switch IP The switch IP address. Switch WWN The switch world wide name. Tape Pipelining Whether tape pipelining is On or Off for the FCIP tunnel. Tunnel ID The tunnel identifier. Type The device type. Unit Type The unit type of the node. Vendor The product vendor.
10 Properties Adding a property label You can add a new field to any of the tabs on the Properties dialog box. To add a new field, complete the following steps. 1. Right-click any product icon and select Properties. The Properties dialog box displays. 2. Select the tab to which you want to add a property. 3. Right-click on any label. The new property label displays above the one you select. 4. Select Add. The Add Property dialog box displays. 5. Type a label and description for the property. 6.
Properties 10 Deleting a property label You can delete any label that you created on any of the tabs from the Properties dialog box. To delete a label, complete the following steps. 1. Right-click any product icon and select Properties. The Properties dialog box displays. 2. Select the tab on which you want to delete a property. 3. Right-click the label for the property you want to delete. 4. Select Delete. 5. Click Yes on the confirmation message. The property you selected is deleted.
10 Ports Ports You can enable and disable ports, as well as view port details, properties, type, status, and connectivity. Viewing port connectivity The connected switch and switch port information displays for all ports. To view port connectivity, choose one of the following steps: • Right-click a product icon and select Port Connectivity. • Select a product icon and select Monitor > Port Connectivity. The Port Connectivity View dialog box displays (Figure 100).
Ports 10 The following table details the information located (in alphabetical order) on the Port Connectivity View dialog box. TABLE 18 Port connectivity properties Field Description Actual Distance The actual distance for -end port connectivity. Area ID /Port Index The area ID and the port index of the port. Blade Number The number of the blade. Blocked Whether the selected port is blocked. Buffer Limited Whether buffers are limited.
10 Ports TABLE 18 272 Port connectivity properties (Continued) Field Description Device Port/Switch Name The device port and switch name. Device Port/Switch State The device port and switch state. Device Port/Switch Manufacturer The device port and manufacturer of the switch. Device Port/Switch Manufacturing Plant The device port and switch manufacturing plant. Device Port / Switch Type Number The device port and switch type number.
Ports TABLE 18 10 Port connectivity properties (Continued) Field Description Switch IDID Whether the switch’s insistent domain ID (IDID) is enabled. If it is enabled, the IDID is the same ID that is requested during switch reboots, power cycles, CP failovers, firmware downloads, and fabric reconfiguration. Switch in Order Delivery Whether switch in-order delivery is enabled. Switch IP The switch’s IP address. Switch Port Count The number of ports on the switch.
10 Ports Filtering port connectivity To filter results from the port connectivity view, complete the following steps. 1. Click the Filter link from the Port Connectivity View dialog box The Filter dialog box displays (Figure 101). FIGURE 101 Filter dialog box 2. Click a blank cell in the Field column to select the property from which to filter the results. 3. Click a blank cell in the Relation column to select an action operation.
Ports 10 Resetting the filter Reset immediately clears all existing definitions. You cannot cancel the reset. To reset the Filter dialog box, complete the following steps. 1. Click the Filter link from the Port Connectivity View dialog box. The Filter dialog box displays. 2. Click Reset. All existing definitions are cleared automatically. You cannot cancel the reset. Enabling the filter To enable the filter, select the Filter check box.
10 Ports Viewing ports and port properties To view ports on the Connectivity Map, right-click a product icon and select Show Ports. NOTE Show Ports is not applicable when the map display layout is set to Free Form (default). NOTE This feature is only available for connected products. On bridges and CNT products, only utilized Fibre Channel ports display; IP ports do not display. To view a port’s properties, right-click on a port and select Properties, or double-click on the port.
Ports 10 Depending on the port type, some of the following properties (Table 19) may not be available for all products. TABLE 19 Port properties Field Description # Virtual Session Ports The number of virtual session ports associated with the GE port. Additional Port Info Additional error information relating to the selected port. Address The address of the port. Active FC4 Types The active FC4 types. Active Tunnels The number of active tunnels.
10 Ports TABLE 19 278 Port properties (Continued) Field Description MAC Address The Media Access Control address assigned to a network adapters or network interface cards (NICs). Manufacturer Plant The name of the manufacturer plant. Modify button Click to launch the Element Manager. Model The model number of the device. Name The name of the port (up to 128 characters). This field is editable.
Ports TABLE 19 10 Port properties (Continued) Field Description Vendor The product vendor. Virtual FCoE Port Count The number of FC ports on the device. Port types On the Connectivity Map, right-click a switch icon and select Show Ports. The port types display showing which ports are connected to which products. NOTE Show Ports is not applicable when the map display layout is set to Free Form (default). NOTE This feature is only available for connected products.
10 Ports Viewing port connection properties You can view the information about products and ports on both sides of the connection. 1. Right-click the connection between two end devices on the Connectivity Map and select Properties. OR Double-click the connection between two devices on the Connectivity Map. The Connection Properties dialog box displays.
Ports TABLE 21 10 Port connection properties (Continued) Field Description 2-WWPN The world wide port number of the second switch. 2-MAC Address The MAC address of the second switch. 2-IP Address The IP address of the second switch. 2-Trunk Whether there is a trunk on the second switch. 2-Speed (Gbps) The speed of the second switch. 2-Tunnel ID The tunnel ID of the second switch. 2-Circuit ID The circuit ID of the second switch.
10 Ports TABLE 21 Port connection properties (Continued) Field Description Name The name of the switch. NPIV Enabled Whether the NPIV port is enabled. Parameter The parameter of the switch. Physical/Logical Whether the port is a physical port or a logical port. PID Format The port ID format of the switch. Port # The port number. Port Address The address of the port. Port Module The port’s module. Port NPIV The number of NPIV ports. Port Type The type of port.
Ports 10 Determining inactive iSCSI devices For router-discovered iSCSI devices, you can view all of the inactive iSCSI devices in one list. To do this, use the Ports Only view and then sort the devices by FC Address. The devices that have an FC address of all zeros are inactive. 1. Select View All, Levels, and then Ports Only from the main window. 2. Use the scroll bar to view the columns to the right and locate the FC Address column in the Ports Only list. 3.
10 Ports Viewing port optics NOTE QSFP ports do not display in the Port Optics dialog box. To view port optics, complete the following steps. 1. Right-click the switch for which you want to view port optic information on the Connectivity Map and select Port Optics (SFP). The Port Optics (SFP) dialog box displays(Figure 104). FIGURE 104 Port Optics dialog box 2. Review the port optics information. • Combined Status—Displays the current status of the port.
Ports 10 Status icons: Warning icon—One of the five parameters exceeds the threshold of that parameter. The corresponding parameter field displays with a yellow background. No icon—No parameters exceed the threshold of that parameter. Unknown icon—The port is not a 16 Gbps capable port or the device is running Fabric OS 6.4.X or earlier. Error icon—Unable to retrieve status of the supported port. Slot/Port #—The slot and port number of the selected fabric.
10 Port Auto Disable 3. Sort the results by clicking on the column header. 4. Rearrange the columns by dragging and dropping the column header. 5. Click Close to close the Port Optics (SFP) dialog box. Refreshing port optics To refresh port optics, click Refresh. The Management application retrieves updated port optic information.
Port Auto Disable 10 Viewing the port auto disable status NOTE The device must be running Fabric OS 6.3 or later. To view the port auto disable status, complete the following steps. 1. Select Configure > Port Auto Disable. The Port Auto Disable dialog box displays. FIGURE 105 Port Auto Disable dialog box 2. Select one of the followingfrom the Show list to determine what ports to display: • • • • All Ports (default) Disabled PAD Ports Enabled PAD Ports Blocked Ports 3.
10 Port Auto Disable • Loss of Sync—Whether the Loss of Sync event is enabled or disabled in port auto disable. • Loss of Signal—Whether the Loss of Signal event is enabled or disabled in port auto disable. • OLS—Whether the Offline Primitive Sequence event is enabled or disabled in port auto disable. • NOS—Whether the Not Operational Primitive Sequence event is enabled or disabled in port auto disable.
Port Auto Disable 10 6. Select one or more of the following event types: • • • • • Port Auto Disable Loss Of Sync—Requires devices running Fabric OS 7.0 or later. Loss Of Signal—Requires devices running Fabric OS 7.0 or later. OLS (Offline Primitive Sequence)—Requires devices running Fabric OS 7.0 or later. NOS (Not Operational Primitive Sequence)—Requires devices running Fabric OS 7.0 or later. • LIP (Loop Initialization Primitive Sequence)—Requires devices running Fabric OS 7.0 or later. 7.
10 Port Auto Disable Enabling port auto disable on all ports on a device NOTE The device must be running Fabric OS 6.3 or later. To enable port auto disable on all ports on a device, complete the following steps. 1. Select Configure > Port Auto Disable. The Port Auto Disable dialog box displays. 2. Select the fabric on which you want to enable port auto disable (PAD) from the Fabric list. 3. Select All Ports from the Show list. 4. Select the device on which you want to enable PAD on all ports. 5.
Port Auto Disable 10 6. Clear any of the following selected event types. • • • • • Port Auto Disable Loss Of Sync—Requires devices running Fabric OS 7.0 or later. Loss Of Signal—Requires devices running Fabric OS 7.0 or later. OLS (Offline Primitive Sequence)—Requires devices running Fabric OS 7.0 or later. NOS (Not Operational Primitive Sequence)—Requires devices running Fabric OS 7.0 or later. • LIP (Loop Initialization Primitive Sequence)—Requires devices running Fabric OS 7.0 or later. 7.
10 Port Auto Disable Unblocking ports NOTE The device must be running Fabric OS 6.3 or later. To unblock ports, complete the following steps. 1. Select Configure > Port Auto Disable. The Port Auto Disable dialog box displays. 2. Select the fabric on which you want to enable port auto disable (PAD) from the Fabric list. 3. Select Blocked Ports from the Show list. 4. Click Unblock. 5. Click OK on the Port Auto Disable dialog box.
Chapter 11 Host Port Mapping In this chapter • Host port mapping overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Creating a new Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Renaming an HBA Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Deleting an HBA Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Viewing Host properties . . . . . . . .
11 Creating a new Host Creating a new Host To create a new Host, complete the following steps. 1. Right-click an HBA icon and select Host Port Mapping. The Host Port Mapping dialog box displays. FIGURE 106 Host Port Mapping dialog box 2. Click New Host. A new Host displays in the Hosts table in edit mode. 3. Double-click the new Host name to make it editable, type a name for the new Host, and press Enter. The name of the new Host appears in the Hosts table in alphabetical order.
Deleting an HBA Host 11 Deleting an HBA Host To delete a Host, complete the following steps. 1. Right-click an HBA icon and select Host Port Mapping. The Host Port Mapping dialog box displays. 2. Select the Host you want to delete in the Hosts table. 3. Click Delete. The selected Host is deleted. Any HBAs associated with the Host are automatically moved from the Host table to the HBAs table. 4. Click OK to save your changes and close the Host Port Mapping dialog box.
11 Importing HBA-to-Host mapping Importing HBA-to-Host mapping The Host Port Mapping dialog box enables you to import externally created HBA ports-to-Host mapping information into the application. The imported file must be in CSV format. The first row must contain the headers (wwn, name) for the file. Example wwn,name 20:00:00:00:C9:69:D5:27, s1 20:00:00:05:1E:0A:35:0E, s2 When the import is complete a result summary displays with the information listed in Table 22.
Removing an HBA from a Host 11 • Checks for existing mappings in the current map. If a mapping already exists, a message displays with the current mapping information. Click Yes to overwrite the current mapping. Click Yes to All to overwrite all mapping conflicts. Click No to leave the current mapping. Click No to All to leave all current mappings when conflict occurs. Click Cancel to cancel the import. 5. Click OK to close the Import Results dialog box. 6.
11 Exporting Host port mapping 4. Browse to the location where you want to save the export file. Depending on your operating system, the default export location are as follows: • Desktop\My documents (Windows) • \root (Linux) 5. Enter a name for the files and click Save. 6. Click OK to close the Host Port Mapping dialog box.
Chapter 12 Storage Port Mapping In this chapter • Storage port mapping overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Creating a storage array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Adding storage ports to a storage array. . . . . . . . . . . . . . . . . . . . . . . . . . . . • Unassigning a storage port from a storage array . . . . . . . . . . . . . . . . . . . . • Reassigning mapped storage ports . . . . . . . . . . . . . . . .
12 Creating a storage array Creating a storage array To create a storage array, complete the following steps. 1. Open the Storage Port Mapping dialog box by performing one of the following actions: - Select a storage port icon in the topology view, then select Discover > Storage Port Mapping. - Right-click any storage port icon in the topology view and select Storage Port Mapping. Right-click any storage port in the Device Tree and select Storage Port Mapping.
Unassigning a storage port from a storage array 12 Unassigning a storage port from a storage array To unassign a storage port from a storage array, complete the following steps. 1. Open the Storage Port Mapping dialog box by performing one of the following actions: - Select a storage port icon in the topology view, then select Discover > Storage Port Mapping. - Right-click any storage port icon in the topology view and select Storage Port Mapping.
12 Editing storage array properties Editing storage array properties To edit storage array properties, complete the following steps. 1. Open the Storage Port Mapping dialog box by performing one of the following actions: - Select a storage port icon in the topology view, then select Discover > Storage Port Mapping. - Right-click any storage port icon in the topology view and select Storage Port Mapping. Right-click any storage port in the Device Tree and select Storage Port Mapping.
Viewing storage port properties 12 Viewing storage port properties 1. Open the Storage Port Mapping dialog box by performing one of the following actions: - Select a storage port icon in the topology view, then select Discover > Storage Port Mapping. - Right-click any storage port icon in the topology view and select Storage Port Mapping. Right-click any storage port in the Device Tree and select Storage Port Mapping. The Storage Port Mapping dialog box displays. 2.
12 Importing storage port mapping Importing storage port mapping The Storage Port Mapping dialog box enables you to import externally created storage port mapping information into the application. The imported file must be in CSV format. The first row must contain the headers (wwn, name) for the file, which is ignored during the import.
Exporting storage port mapping 12 When import is complete a result summary displays with the following information (“Import Results” on page 305). TABLE 23 Import Results Value Definition Total Valid Input Records Number of lines identified in the CSV file without any errors (excluding the Header). Unique storage port WWN’s Recognized Number of unique storage ports identified in the CSV file.
12 Exporting storage port mapping 3. Click Export. The Export dialog box displays. 4. Browse to the location where you want to save the export file. Depending on your operating system, the default export location are as follows: • Desktop\My documents (Windows) • \root (Linux) 5. Enter a name for the files and click Save. 6. Click OK to close the Storage Port Mapping dialog box.
Chapter 13 Host management In this chapter • Host management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • HCM software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Host bus adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Converged network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Host adapter discovery . . . . . .
13 HCM software • HCM supports management for individual adapters (1/4/8 Gbps HBAs), 10 Gbps CNAs, 16 Gbps FC adapters, and other devices, such as the host, DCB ports, FCoE ports, and Ethernet ports. The Management application, in conjunction with HCM, provides end-to-end management capability. For information about configuring, monitoring, and managing individual adapters using the HCM GUI or the Brocade Command Utility (BCU), refer to the Adapters Administrator’s Guide.
Host bus adapters 13 • Diagnostics, which enables you to test the adapters and the devices to which they are connected: - Link status of each adapter and its attached devices - Read/write buffer test, which tests the link between the adapter and its devices Loopback test, which is external to the adapter, to evaluate the ports (transmit and receive transceivers) and the error rate on the adapter FC protocol tests, including echo, ping, and traceroute Ethernet loopback test (CNA only) • Monitoring, w
13 Converged network adapters Converged network adapters Table 25 describes available Brocade Converged Network Adapters (CNAs) for PCIe x 8 host bus interfaces, hereafter referred to as Brocade CNAs. These adapters provide reliable, high-performance host connectivity for mission-critical SAN environments.
Fabric adapters 13 Fabric adapters Table 26 describes available Brocade 1860 Fabric Adapter models. The BR-1860 provides dual mode support for the port.
13 Connectivity map Connectivity map The Connectivity Map, which displays in the upper right area of the main widow, is a grouped map that shows physical and logical connectivity of Fabric OS components, including discovered and monitored devices and connections. These components display as icons in the Connectivity Map.
Host port mapping 13 If you create a new Host and associate HBAs to it, and then you try to discover a host with the same HBAs using Host discovery, the HBA’s discovered using host discovery must match the HBAs associated to the Host exactly; otherwise, Host discovery will fail.
13 Adapter software Adapter software The Adapter Software dialog box allows you to perform the following tasks: • Select and import a driver file or delete existing drivers from the driver repository • Update the driver to the hosts. This feature is available for hosts that are disovered through the Host Connectivity Manager (HCM) agent with driver version 2.3.0.0 and higher. To update the drivers to selected hosts, complete the following steps: 1. Select Host > Adapter Software from the Configure menu.
Adapter software 13 Driver repository You can access the Driver Repository dialog box from the Adapter Software dialog box. Initially, the repository is empty. You must import files into the repository. Imported driver files are then displayed in the Available Driver Files list in the Driver Repository dialog box. Importing a driver into the repository To import drivers into the Management application, perform the following tasks. 1. From the Adapter Software dialog box, click the Repository button.
13 Adapter software Deleting a boot image from the repository 1. Select one or more driver files from the Available Driver Files list on the Driver Repository dialog box. 2. Click Delete. The driver file is removed from the Driver Repository dialog box. NOTE Windows drivers (.exe files) cannot be imported into the server repository when the Management application server is running on Linux or Solaris platforms.
Adapter software 13 Importing a boot image into the repository To import boot images into the Management application, perform the following tasks. 1. From the Boot Image Management dialog box, click the Repository button. The Boot Image Repository dialog box, shown in Figure 110, displays. FIGURE 110 Boot Image Repository dialog box 2. Click Import on the Boot Image Repository dialog box. 3. The Import Boot Image dialog box displays. 4.
13 Adapter software Downloading a boot image to a selected host To download boot images to a selected host, perform the following tasks. 1. Select one or more hosts from the Available Hosts list on the Boot Image Management dialog box, and click the right arrow button to move the selected hosts to the Selected Hosts list. You can select up to 50 hosts. The first 20 hosts execute the download concurrently.
Role-based access control 13 Role-based access control The Management application enables you to create resource groups and assign users to the selected role within that group. This enables you to assign users to a role within the resource group. The Management application provides one pre-configured resource group (All Fabrics). When you create a resource group, all available roles are automatically assigned to the resource group.
13 Host performance management Host performance management Real-time performance enables you to collect data from managed HBA and CNA ports. You can use real-time performance to configure the following options: • Select the polling rate from 20 seconds up to 1 minute. • Select up to 32 ports total from a maximum of 10 devices for graphing performance. • Choose to display the same Y-axis range for both the Tx MB/Sec and Rx MB/Sec measure types for easier comparison of graphs.
Host security authentication TABLE 27 13 Counters (Continued) FC port measures HBA port measures CNA port measures Received length error frames Received code error frames Instructions for generating real-time performance data are detailed in “Generating a real-time performance graph” on page 783. Host security authentication Fibre Channel Security Protocol (FC-SP) is a mechanism used to secure communication between two switches or between a switch and a device such as an HBA port.
13 supportSave on adapters a. Select the Enable Authentication check box to enable or disable the authentication policy. If authentication is enabled, the port attempts to negotiate with the switch. If the switch does not participate in the authentication process, the port skips the authentication process. The Hash type list shows the following options, but only one option, DHNULL, is supported. • MD5 - A hashing algorithm that verifies a message’s integrity using Message Digest version 5.
Host fault management 13 Host fault management Fault management enables you to monitor your SAN using the following methods: • Monitor logs for specified conditions and notify you or run a script when the specified condition is met. • Create event-based policies, which contain an event trigger and action. • Configure E-mail event notification. • Receive and forward Syslog messages from Brocade switches and Brocade HBAs, managed using the Host Connectivity Manager (HCM).
13 Backup support Syslog forwarding NOTE Syslog messages are only available on Brocade devices and HBAs (managed using the HCM Agent). Syslog forwarding is the process by which you can configure the Management application to send Syslog messages to other computers. Switches only send the Syslog information through port 514; therefore, if port 514 is being used by another application, you must configure the Management application to listen on a different port.
Backup support 13 6. Enter the time (using a 24-hour clock) you want the backup process to begin in the Next Backup Start Time Hours and Minutes fields. 7. Select an interval from the Backup Interval drop-down list to set how often backup occurs. 8. Browse to the hard drive and directory to which you want to back up your data. 9. Click Apply or OK. The application verifies that the backup device exists and that the server can write to it.
13 Adapter port WWN virtualization Adapter port WWN virtualization Adapter port world wide name (WWN) virtualization enables the adapter port to use a switch-assigned WWN rather than the physical port WWN for communication, allowing you to pre-provision the server with the following configuration tasks: • Create the zones with the Fabric Assigned WWN before the servers and devices are connected to the switches, before they are exposed to the SAN network.
Adapter port WWN virtualization 13 Enabling the FAWWN feature on a switch or AG ports 1. Select Configure > Fabric Assigned WWN. or Right-click the switch and select Fabric Assigned WWN. The Configure Fabric Assigned WWNs dialog box displays. 2. Select a switch port from the Fabric Assigned WWN - Configuration list. 3. Click the Enable button. The selected switch’s Port status is enabled. 4. Click OK. The Fabric Assigned WWN Confirmation and Status dialog box displays. 5.
13 Adapter port WWN virtualization Manually assigning a FAWWN to a switch or AG port 1. Select Configure > Fabric Assigned WWN. or Right-click the switch and select Fabric Assigned WWN. The Configure Fabric Assigned WWNs dialog box displays. 2. Select a switch port or AG port from the Fabric Assigned WWN - Configuration list. 3. Click the Auto button. If the switch port does not have an Auto FAWWN map type and the FAWWN feature is not yet enabled on the port, a message displays. 4.
Adapter port WWN virtualization 13 Configuring Fabric Assigned WWNs on attached AG ports The Add AG Fabric Assigned WWN Configuration dialog box, shown in Figure 113, enables you to configure the Fabric Assigned WWN feature on a selected attached Access Gateway (AG) port. 1. Select Configure > Fabric Assigned WWN. or Right-click the switch and select Fabric Assigned WWN. The Configure Fabric Assigned WWNs dialog box displays. 2. Click the Attached AG Ports tab.
13 Adapter port WWN virtualization FIGURE 114 Add AG Fabric Assigned WWN Configuration dialog box 5. Enter a valid world wide name (WWN), with or without colons, for the Access Gateway node. Optionally, you can select an existing AG Node WWN from the list. The AG Node WWN combo box includes all discovered AG Node WWNs that are connected to the selected switch. 6. Enter a port or a port range using numbers or a hyphen (-).
VM Manager 13 3. Select the WWN row you want to move by right-clicking it, select the Copy Row option, and paste the contents into a text editor. 4. Select an online AG FAWWN row and click the Delete button. 5. Select a switch from the Switch list and click Add to launch the Add AG Fabric Assigned WWN Configuration dialog box. 6. Using the information you copied to the text editor, configure the AG port WWN information to be moved to the selected switch. 7. Click OK.
13 VM Manager 6. Enable or disable the vSphere client plug-in registration. If you enable this plug-in, events are forwarded from the Management application to the vCenter server. 7. Click OK. The VMM discovery process begins. When complete, the vCenter server and all ESX hosts managed by that vCenter display in the Host product tree.
Chapter 14 Fibre Channel over Ethernet In this chapter • FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Enhanced Ethernet features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCoE protocols supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCoE Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 Enhanced Ethernet features DCB exchange protocol DCB Exchange (DCBX) protocol allows enhanced Ethernet devices to convey and configure their DCB capabilities and ensures a consistent configuration across the network. DCBX protocol is used between data center bridging (DCB) devices, such as a converged network adapter (CNA) and a FCoE switch, to exchange configuration with directly-connected peers. NOTE When DCBX protocol is used, any other LLDP implementation must be disabled on the host systems.
FCoE protocols supported 14 Ethernet jumbo frames The basic assumption underlying FCoE is that TCP/IP is not required in a local data center network and the necessary functions can be provided with Enhanced Ethernet. The purpose of an “enhanced” Ethernet is to provide reliable, lossless transport for the encapsulated Fibre Channel traffic. Enhanced Ethernet provides support for jumbo Ethernet frames and in-order frame delivery.
14 FCoE Licensing FCoE Licensing The FCoE license enables Fibre Channel over Ethernet (FCoE) functionality on the 8 Gbps 8-FC port, 10 GbE 24-DCB port Switch. Without the FCoE license, the 8 Gbps 8-FC port, 10 GbE 24-DCB port Switch is a pure L2 Ethernet switch and will not allow FCoE bridging capabilities. With the FCoE license, the FCoE Configuration dialog displays virtual FCoE port information and enables you to manage the virtual port information.
DCB configuration 14 2. Highlight a discovered DCB switch from the Available Switches table, and click the right arrow button to move the switch to the Selected Switches Table. 3. Highlight the selected switch and click OK to start the configuration. The running configuration is saved to the selected switch, effective on the next system startup.
14 Switch policies Switch policies You can configure and enable a number of DCB policies on a switch, port, or link aggregation group (LAG). The following switch policy configurations apply to all ports in a LAG: • DCB map and Traffic Class map • Link Layer Discovery Protocol (LLDP) The switch policies are described in the following sections.
Switch policies 14 Opening the DCB Configuration dialog box Launch the DCB Configuration dialog box using one of the following methods: • Select Configure > DCB from the menu bar. • Right-click the DCB switch from the device tree, and select Configure > DCB. • Right-click the DCB switch from the topology map and select Configure > DCB. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions.
14 Switch policies Creating a DCB map to carry the LAN and SAN traffic To create a DCB map to carry the LAN and SAN traffic, complete the following steps. This procedure is applicable for FOS versions lower than FOS 7.0. For FOS versions 7.0 and higher, you can only edit the the default DCB map. 1. Select Configure > DCB. The DCB Configuration dialog box displays. 2. Select the switch to edit in the DCB Ports and LAGs table and click Edit. The Edit Switch dialog box displays. 3. Click the QOS tab.
Switch policies 14 Configuring LLDP for FCoE To configure LLDP for FCoE, complete the following steps. 1. Select Configure > DCB. The DCB Configuration dialog box displays. 2. Select the switch to edit in the DCB Ports and LAGs table and click Edit. The Edit Switch dialog box displays. 3. Click the LLDP-DCBX tab. 4. The Edit Switch - LLDP-DCBX tab dialog box displays. FIGURE 119 DCB Edit Switch dialog box - LLDP-DCBX tab 5. Select the LLDP profile in the LLDP Profiles table. 6.
14 Switch policies Configuring the DCB interface with the DCB Map and Global LLDP profile To configure the DCB interface, complete the following steps. 1. Select Configure > DCB. The DCB Configuration dialog box displays. 2. Select the Te port connected to the CNA in the DCB Ports and LAGs table and click Edit. 3. Select the Port tab, if necessary, and select the Enable check box. 4. Select L2 from the Interface Mode list. 5.
Switch policies 7. 14 Click OK on the VLAN Configuration dialog box. The VLAN Configuration dialog box displays. 8. Select the VLAN you created and click Edit to convert the VLAN to FCoE VLAN. 9. Select the FCoE check box. 10. Select the DCB interface to carry the FCoE traffic from the Selection List and click Add to add it to the Selected List. 11. Click OK on the VLAN Configuration dialog box to save your changes. 12. Close Web Tools.
14 Switch policies Adding a LAG Link aggregation is a mechanism to bundle several physical ports together to form a single logical channel or trunk. The collection of ports is called a link aggregation group (LAG). NOTE An internal port cannot be part of a LAG. You can create LAGs with external ports only. The Add LAG button is enabled when a single DCB switch or ports of a single DCB switch are selected.
Switch policies 14 4. Configure the following LAG parameters: NOTE Ports with 802.1x authentication or ports that are L2 or L3 mode-enabled are not supported in a LAG. • Status - Enabled or Disabled. You must enable the LAG to use the DCB functionality. • LAG ID - Enter the LAG identifier, using a value between 1-63. Duplicate LAG IDs are not allowed. • Interface mode - none or L2. The L3 interface mode option is displayed in the Edit LAG dialog box only.
14 Switch policies 9. Click Start on the Deployment Status dialog box to save the changes to the selected LAG or LAGs. 10. Click Close to close the Deployment Status dialog box. Editing a DCB switch 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select the DCB switch from the Products/Ports table. 3. Click Edit. The Edit Switch dialog box displays (Figure 121). FIGURE 121 Edit Switch dialog box 4.
Switch policies 14 6. Click OK. The Deploy to Products dialog box displays. 7. Click OK after changing the attributes of the current deployment. The Deployment Status dialog box launches. 8. Click Start on the Deployment Status dialog box to save the changes to the selected devices. 9. Click Close to close the Deployment Status dialog box. Editing a DCB port 1. Select Configure > DCB from the menu bar.
14 Switch policies 4. Modify the following DCB Port parameters as required: • Status - Enable or Disable. You must enable the LAG to use the DCB functionality. • Interface Mode - None or L2. For external ports, the L3 interface mode displays, in addition to None or L2. If you select L3 as the interface mode, the IP/Netmask field is enabled and you can then assign the primary and secondary IP addresses. L2 Mode - This is enabled if you select L2 as the Interface Mode.
Switch policies 14 Editing a LAG Use the following procedure to change members and policies in a link aggregation group (LAG). 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select the link aggregation group (LAG) from the Products/Ports table. 3. Click Edit. The Edit LAG dialog box displays. FIGURE 123 Edit LAG dialog box 4. Configure the following LAG parameters, as required: NOTE Ports with 802.
14 Switch policies • L2 Mode - Select the L2 mode (Access or Trunk). Access mode allows only one VLAN and allows only untagged frames. Trunk mode allows more than one VLAN association and allows tagged frames. Primary - Enter the primary IP address assigned to an L3 port. • NOTE Primary and secondary IP fields are applicable only to the external ports and the interface mode must be L3 to enable these fields. • Secondary - Enter the secondary IP address (optional).
Switch policies 14 Enabling a DCB port or LAG If you select multiple switches or multiple ports and LAGs from two or more switches, both the Enable button and the Disable button are disabled. 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select one or more DCB ports or LAGs (which can span multiple switches) that you want to enable.
14 QoS configuration QoS configuration QoS configuration involves configuring packet classification, mapping the priority and traffic class, controlling congestion, and scheduling. The configuration of these QoS entities consist of DCB Map and Traffic Class Map configuration. In a Data Center Bridging (DCB) configuration, Enhanced Transmission Selection (ETS) and Priority-based flow control (PFC) are configured by utilizing a priority table, a priority group table, and a priority traffic table.
QoS configuration 14 Creating a DCB map This procedure is applicable only for FOS versions lower than FOS 7.0. When you create a DCB map, each of the Class of Service (CoS) options (0-7) must be mapped to at least one of the Priority Group IDs (0-7) and the total bandwidth must equal 100. All QoS, DCB map, and Traffic map configurations apply to all ports in a LAG. There can be, at the most, 16 entries in the Priority Group table.
14 QoS configuration 4. Select DCB from the Map Type list. 5. Configure the following DCB Map parameters in the DCB Map table: • Name - Enter a name to identify the DCB map. If the switch is a 10 Gbps DCB/FC switch module, you cannot change the name. • Precedence - Enter a value between 1 - 100. This number determines the map’s priority. • Priority Flow Control check box - Check to enable priority flow control on individual priority groups.
QoS configuration 14 5. Keep the same DCB Map name and modify the following values, as required. See Table 28 for an example of priority group configuration. • Name - Enter a name to identify the DCB map. If the switch is a 10 Gbps DCB/FC switch module, you cannot change the name. • Precedence - Enter a value between 1 - 100. This number determines the map’s priority. • % Bandwidth - Enter a bandwidth value for priority group IDs 0-7. The total of all priority groups must equal 100%.
14 QoS configuration Assigning a DCB map to a port or link aggregation group A port can have either a DCB map or a Traffic Class map assigned to it, but it cannot have both. 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a port or LAG, and click Edit. 3. Click the QoS tab on the Edit Port dialog box. The QoS dialog box displays. FIGURE 125 QoS, Assign a DCB Map to a port dialog box 4.
QoS configuration 14 Creating a traffic class map 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a switch, and click Edit. 3. Click the QoS tab on the Edit Switch dialog box. The QoS dialog box displays. 4. Select Traffic Class from the Map Type list. 5. Name the Traffic Class map. 6. Click the Traffic Class cell in a CoS row and directly enter a value from 0-7.
14 QoS configuration Deleting a traffic class map 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a switch, and click Edit. 3. Click the QoS tab on the Edit Switch dialog box. The QoS dialog box displays. 4. Select a Traffic Class Map that you want to delete from the Traffic Class Maps table. 5. Click the left arrow button. The selected DCB Map row is removed from the table. 6.
FCoE provisioning 14 FIGURE 126 QoS, assign a traffic class map to a port dialog box 4. Click the Assign a map check box. 5. Select Traffic Class in the Map Type list. 6. Select a Traffic Class Map in the Traffic Class Map list. 7. When you have finished the configuration, click OK to launch the Deploy to Ports/LAGs dialog box. Refer to “Product, Port, and LAG Deployment” on page 373 for more information.
14 FCoE provisioning Changing the VLAN ID on the default FCoE map You can change the VLAN ID on the default FCoE map only when no ports or LAGs are participating as members of the switch. You must first manually remove the FCoE Map option for each of the port members before you change the VLAN ID on the switch. 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a switch and click Edit. 3.
FCoE provisioning 14 Enabling or disabling the FCoE map on the port You must first manually disable an FCoE map-enabled port if you want to edit the VLAN ID of the FCoE map. See “Changing the VLAN ID on the default FCoE map” on page 360 for information on editing the VLAN ID using the Edit Switch dialog box, FCoE tab. 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a port and click Edit. 3.
14 VLAN classifier configuration VLAN classifier configuration The Management application supports VLAN classifier management only on Fabric OS (FOS) version 6.3.1_dcb and FOS 7.0.0. VLAN classifier rules are used to define specific rules for classifying untagged packets to selected VLANs based on protocol and MAC addresses. The classified frames are then tagged with a VLAN ID. VLAN classifier rules can be categorized into the following areas: • 802.
VLAN classifier configuration 14 FIGURE 129 Edit Switch dialog box, VLAN Classifiers tab 4. Click the Add button under the Available Rule list. The Add Rules dialog box displays, as shown in Figure 130. FIGURE 130 Add Rules dialog box The Rule ID field is pre-populated with the next available Rule ID number. 5. Keep the Rule ID number as it is, or change the number using a value between 1 through 256. 6. Select a rule type. Valid rule types are MAC (MAC address-based rule) and Proto (802.
14 VLAN classifier configuration 9. Click OK to add the rule to the Available Rules list on the VLAN Classifiers dialog box and close the Add Rules dialog box. NOTE Clicking Apply also adds the rule to the Available Rules list on the VLAN Classifiers dialog box, and in addition, the Add Rules dialog box remains open and clears all entries for you to define the next rule. 10. When you have finished the configuration, click OK to launch the Deploy to Products dialog box, shown in Figure 134.
VLAN classifier configuration 14 Creating a VLAN classifier group You can assign existing rules to a selected VLAN classifier and form a VLAN classifier group. If no rules are available, you can add rules to a selected switch using the Add Rules dialog box. 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a switch and click Edit. 3. Click the VLAN Classifiers tab on the Edit Switch dialog box.
14 LLDP-DCBX configuration LLDP-DCBX configuration Link Layer Discovery Protocol (LLDP) provides a solution for the configuration issues caused by increasing numbers and types of network devices in a LAN environment, because, with LLDP, you can statically monitor and configure each device on a network.
LLDP-DCBX configuration 14 FIGURE 131 Edit Switch dialog box - LLDP-DCBX tab 5. Select the Global Configuration LLDP profile in the LLDP Profiles table. 6. Click the left arrow button to edit. 7. Select the FCoE Application and FCoE Logical Link check boxes in the Advertise table to advertise them on the network. 8. When you have finished the configuration, click OK to launch the Deploy to Products dialog box, shown in Figure 134.
14 LLDP-DCBX configuration 5. Configure the LLDP Profile parameters: • Name - Type a name for the LLDP profile. If the name of the LLDP profile already exists on the switch, an overwrite warning displays. • Description - Type a meaningful description of the LLDP profile. • Mode - Select a mode from the list: Tx (transmitted) or Rx (received). • Hello - Enter a hello interval time for the bridge. The value range is 4-180 and the default value is 30. • Multiplier - Enter a multiplier.
LLDP-DCBX configuration 7. 14 Click the right arrow to update the LLDP Profile parameters. 8. When you have finished the configuration, click OK to launch the Deploy to Products dialog box, shown in Figure 134. Deleting an LLDP profile 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a switch, and click Edit. 3. Click the LLDP-DCBX tab on the Edit Switch dialog box. 4.
14 LLDP-DCBX configuration FIGURE 132 Assign an LLDP profile dialog box 4. Click Assign an LLDP profile to button to enable the feature. NOTE Assign the Global Configuration is the default. The Available Profiles list is disabled if global configuration is selected. In addition, the Assign an LLDP profile button is disabled if no LLDP profiles exist on the switch. 5. Select an LLDP profile from the Available Profiles list. 6.
802.1x authentication 14 802.1x authentication 802.1x is a standard authentication protocol that defines a client-server-based access control and authentication protocol. 802.1x restricts unknown or unauthorized clients from connecting to a LAN through publicly accessible ports. NOTE 802.1x is not supported for internal ports. A switch must be enabled for 802.1x authentication before you configure its parameters. See “Setting 802.1x parameters for a port” for more information. Enabling 802.
14 802.1x authentication Setting 802.1x parameters for a port The 802.1x parameters can be configured whether the feature is enabled on the switch. The default parameters are initially populated when 802.1x is enabled, but you can change the default values as required. 1. Select Configure > DCB from the menu bar. The DCB Configuration dialog box displays, showing the status of all DCB-related hardware and functions. 2. Select a port and click Edit. 3. Click the 802.1x tab on the Edit Port dialog box.
Product, Port, and LAG Deployment 14 • Re-authentication Interval - The number of seconds between re-authentication attempts. The value range is 1 to 4294967295. The default value is 3600 seconds. This feature is not dependent on the re-authentication state being enabled. • Port Control - Select an authorization mode from the list to configure the ports for authorization. Options include auto, force-authorized, or force-unauthorized and the default value is auto. 6.
14 Product, Port, and LAG Deployment FIGURE 134 Deploy to Products dialog box FIGURE 135 Deploy to Ports dialog box 374 Brocade Network Advisor SAN User Manual 53-1002167-01
Product, Port, and LAG Deployment 14 FIGURE 136 Deploy to LAGs dialog box 4. Click one of the following deployment options: • • • • Deploy now Save and deploy now Save deployment only Schedule 5. Click one of the following save configuration options: • Save to running • Save to running and startup • Save to running and startup then reboot The name for the scheduled product deployment is pre-populated with a “DCB-MM-DD-YYYY-HR-MIN-SS” prefix. This is an editable field. 6.
14 Product, Port, and LAG Deployment 8. Select one or more of the following configurations, to be deployed on the selected targets: For switches: • • • • • • QoS, DCB Map QoS, Traffic Class Map FCoE Map VLAN Classifiers and Rules LLDP Profiles 802.1x Configuration NOTE See “Source to target switch FOS version compatibility for deployment” for restrictions. For ports: • • • • • Port attributes (interface mode, etc.) QoS, DCB Map / Traffic Class Map FCoE Map LLDP Profiles 802.
Product, Port, and LAG Deployment 14 Source to target switch FOS version compatibility for deployment Table 29 lists the restrictions that exist when deploying source switches to target switches. TABLE 29 Source to target switch FOS version compatibility Source FOS version and device Target FOS version supported Comments Brocade 8000 DCB switch and FCOE10-24 DCB blade with FOS version 6.4.2 or earlier. Allows Brocade 8000 DCB switch and FCOE10-24 DCB blade with FOS version 6.4.2 or earlier.
14 DCB Performance DCB Performance Performance monitoring provides details about the quantity of traffic and errors a specific port or device generates on the fabric over a specific time frame. You can also use Performance features to indicate the devices that create the most traffic and to identify the ports that are most congested. The Performance menu items launch either SAN or IP performance dialog boxes based on which tab you select.
DCB Performance 14 Historical Performance Graph The Historical Performance Graph dialog box enables you to customize how you want the historical performance information to display. Generating a historical performance graph 1. Select a DCB port from the DCB Configuration dialog box, and select Historical Graph from the Performance list. A message displays, prompting you to close the DCB Configuration dialog. 2. Click OK to close the DCB Configuration dialog and open the Performance dialog box.
14 FCoE login groups FCoE login groups The FCoE Configuration dialog box allows you to manage the FCoE login configuration parameters on the DCB switches in all discovered fabrics. FCoE login configuration is created and maintained as a fabric-wide configuration. 1. Select Configure > FCoE from the menu bar. or Right-click the DCB device and select FCoE. The FCoE Configuration dialog box displays, shown in Figure 139. FIGURE 139 FCoE Configuration dialog box 2.
FCoE login groups 14 Adding an FCoE login group Complete the following steps to add switches to a login group. You can manually add ports by entering the world wide name (WWN) or select available managed CNAs from all discovered hosts. Only directly-connected devices are supported. 1. Select Configure > FCoE from the menu bar. or Right-click the DCB device and select FCoE. 2. Click Add. The Add Login Group dialog box, shown in Figure 140, displays. FIGURE 140 Add Login Group dialog box 3.
14 FCoE login groups 7. Click OK. The FCoE Login Group Confirmation and Status dialog displays. 8. Review the changes carefully before you accept them. 9. Click Start to apply the changes, or click Close to abort the operation. On closing the FCoE Login Group Confirmation and Status dialog box, the FCoE Configuration Dialog refreshes the data and the latest information is displayed. • “FCoE login groups” Editing an FCoE login group Complete the following steps to edit the name of a login group.
FCoE login groups 14 3. Change the name of the login group. NOTE The Fabric field and the Switch field are read-only fields. 4. Perform one of the following editing tasks: • Rename the login group by entering the new name into the Name field. The Allow All option must be selected to rename the login group. • Select one of the following options to add or remove login members into the Available Members list. The Allow Specific option must be selected to add or remove login members.
14 FCoE login groups Disabling the FCoE login management feature on a switch 1. Select Configure > FCoE from the menu bar. or Right-click the DCB device and select FCoE. The FCoE Configuration dialog box displays. 2. Select an FCoE-enabled switch from the Login Groups list and click Disable. The FCoE Login Group Confirmation and Status dialog displays. 3. Review the changes carefully before you accept them. 4. Click Start to apply the changes, or click Close to abort the operation.
Virtual FCoE port configuration 14 Virtual FCoE port configuration The virtual FCoE port has the following configuration features: • Displays the virtual FCoE ports on each of the DCB devices, which provides the Ethernet with bridging capability. • One-to-one mapping of FCoE ports with 10 Gbps Ethernet ports. • Option to enable or disable the virtual FCoE ports. • Option to view the end devices connected to a virtual FCoE port.
14 Virtual FCoE port configuration 4. Perform one of the following tasks: • Click Enable to enable a selected virtual FCoE port for DCB configuration. • Click Disable to disable a selected virtual FCoE port from DCB configuration. • Click Connected Devices to view a list of FCoE virtual ports and to what they are directly connected. 5. Click Close to close the dialog box.
Chapter Security Management 15 In this chapter • Layer 2 access control list management . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 • Security configuration deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Layer 2 access control list management A Layer 2 access control list (L2 ACL) enables you to filter traffic based on the information in the IP packet header using the MAC address and Ethernet type.
15 Layer 2 access control list management Fabric OS L2 ACL configuration This section provides procedures for configuring a standard for extended L2 ACL on a device, assigning the L2 ACL to an interface, as well as clearing L2 ACL assignments from a device. Creating a standard L2 ACL configuration To create a standard L2 ACL configuration, complete the following steps. 1. Select the device and select Configure > Security > L2 ACL > Product. The Device_Name - L2 ACL Configuration dialog box displays. 2.
Layer 2 access control list management 15 The new ACL configuration displays in the ACLs table. To create additional ACLs, repeat step 2 through step 10. 11. Click OK on the Device_Name - L2 ACL Configuration dialog box. The Deploy to Products - L2 ACL dialog box displays. To save the configuration, refer to “Saving a security configuration deployment” on page 402 Editing a standard L2 ACL configuration To create a standard L2 ACL configuration on a Fabric OS device, complete the following steps. 1.
15 Layer 2 access control list management d. Select the Count check box to enable counting. Count specifies the number of packets filtered (allowed or denied) for the ACL rule. e. Click the right arrow button. The new ACL entry displays in the ACL Entries table. To add additional ACL entries, repeat step 5. 6. Click OK on the Add - L2 ACL Configuration dialog box. The updated ACL configuration displays in the ACLs table. To edit additional ACLs, repeat step 2 through step 5. 7.
Layer 2 access control list management a. Enter the sequence number for the ACL in the Sequence field. b. Select Permit or Deny from the Action list. c. In the Source list, select one of the following options: 15 • Any • MAC Selecting MAC enables the Source field. Enter the source MAC address on which the configuration filters traffic in the Source field. d. Select the Count check box to enable counting. Count specifies the number of packets filtered (allowed or denied) for the ACL rule. e.
15 Layer 2 access control list management 4. Enter a name for the ACL in the Name field. 5. Enter a sequence number for the ACL in the Sequence field. 6. Select Permit or Deny from the Action list. 7. In the Source list, select one of the following options: • Any • Host • MAC Selecting MAC or Host enables the Source field. Enter the source address on which the configuration filters traffic in the Source field. 8.
Layer 2 access control list management 15 Editing an extended L2 ACL configuration To edit an extended L2 ACL configuration on a Fabric OS device, complete the following steps. 1. Select the device and select Configure > Security > L2 ACL > Product. The Device_Name - L2 ACL Configuration dialog box displays. 2. Select the ACL you want to edit in the ACLs table and click Edit. The Configuration_Name Edit Extended L2 ACL Configuration dialog box displays. 3.
15 Layer 2 access control list management a. Enter sequence number for the ACL in the Sequence field. b. Select Permit or Deny from the Action list. c. In the Source list, select one of the following options: • Any • Host • MAC Selecting MAC or Host enables the Source field. Enter the source address on which the configuration filters traffic in the Source field. d.
Layer 2 access control list management 15 Copying an extended L2 ACL configuration To copy an extended L2 ACL configuration, complete the following steps. 1. Select the device and select Configure > Security > L2 ACL > Product. The Device_Name - L2 ACL Configuration dialog box displays. 2. Select the ACL you want to copy in the ACLs table and click Duplicate. The Duplicate - L2 ACL Configuration dialog box displays with the default name ‘Copy of Original_Name’. 3.
15 Layer 2 access control list management 6. To add a rule, complete the following steps. a. Enter sequence number for the ACL in the Sequence field. b. Select Permit or Deny from the Action list. c. In the Source list, select one of the following options: • Any • Host • MAC Selecting MAC or Host enables the Source field. Enter the source address on which the configuration filters traffic in the Source field. d.
Layer 2 access control list management 7. 15 Click OK on the Duplicate - L2 ACL Configuration dialog box. The new ACL displays in the ACL Entries table. To copy additional ACLs, repeat step 2 through step 7. 8. Click OK on the Device_Name - L2 ACL Configuration dialog box. The Deploy to Products - L2 ACL dialog box displays.
15 Layer 2 access control list management Clearing L2 ACL assignments To clear L2 ACL configuration from interfaces, complete the following steps. 1. Select Configure > Security > L2 ACL > Port. The Port Selection - L2 ACL dialog box displays. 2. Select a port or LAG in the Available Ports table and click the right arrow button. LAGs display in the Available Ports table using the following convention: Po LAG_Number. 3. Click OK.
Layer 2 access control list management 15 3. Click Yes on the confirmation message. 4. Click OK on the Device_Name - L2 ACL Configuration dialog box. NOTE The L2 ACL configuration is not deleted from the switch until you deploy the configuration to the switch. The Deploy to Products - L2 ACL dialog box displays.
15 Security configuration deployment Security configuration deployment Figure 146 shows the standard interface used to deploy security configurations. FIGURE 146 Deploy to Product/Ports dialog box Before you can deploy a security configuration, you must create the security configuration.
Security configuration deployment 15 Deploying a security configuration on demand To deploy a security configuration immediately, complete the following steps. FIGURE 147 Deploy to Product/Ports dialog box 1. Choose one of the following options: • Deploy now—Select to deploy the configuration immediately on the product or port without saving the deployment definition.
15 Security configuration deployment Saving a security configuration deployment To save a security configuration deployment, complete the following steps. FIGURE 148 Deploy to Product/Ports dialog box 1. Select the Save deployment only option to save the deployment definition for future deployment. 2. Select one of the following save configuration options: • Save to running—Select to update the running configuration; however, the deployment is not saved to the product’s flash memory.
Security configuration deployment 15 Scheduling a security configuration deployment To schedule a security configuration deployment, complete the following steps. FIGURE 149 Deploy to Product/Ports dialog box 1. Select Configure > Security > L2 ACL > Product. The Device_Name - L2 ACL Configuration dialog box displays. 2. Choose one of the following options: • Select New from the Add list. The Add - L2 ACL Configuration dialog box displays. • Select an ACL in the list and click Edit.
15 Security configuration deployment 10. Choose one of the following options to configure the frequency at which deployment runs for the schedule: • To configure deployment to run only once, refer to “Configuring a one-time deployment schedule” on page 404. • To configure hourly deployment, refer to “Configuring an hourly deployment schedule” on page 405. • To configure daily deployment, refer to “Configuring a daily deployment schedule” on page 405.
Security configuration deployment 15 Configuring an hourly deployment schedule To configure an hourly schedule, complete the following steps. 1. Select Hourly from the Frequency list. 2. Select the minute past the hour you want deployment to run from the Minutes past the hour list. Where the minute value is from 00 through 59.
15 Security configuration deployment Configuring a monthly deployment schedule To configure a monthly schedule, complete the following steps. 1. Select Monthly from the Frequency list. 2. Select the time of day you want deployment to run from the Time (hh:mm) lists. Where the hour value is from 0 through 12, the minute value is from 00 through 59, and the day or night value is AM or PM. 3. Select the day you want deployment to run from the Day of the Month list (1 through 31).
Chapter 16 FC-FC Routing Service Management In this chapter • Devices that support Fibre Channel routing . . . . . . . . . . . . . . . . . . . . . . . . • Fibre Channel routing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Guidelines for setting up Fibre Channel routing . . . . . . . . . . . . . . . . . . . . . • Connecting edge fabrics to a backbone fabric . . . . . . . . . . . . . . . . . . . . . . • Configuring routing domain IDs . . . . . . . . . . . . . . . . . . . .
16 Fibre Channel routing overview Fibre Channel routing overview Fibre Channel (FC) routing provides connectivity to devices in different fabrics without merging the fabrics. Using Fibre Channel routing, you can share tape drives across multiple fabrics without the administrative overhead, such as change management and network management, and scalability issues that might result from merging the fabrics.
Guidelines for setting up Fibre Channel routing 16 VE_Port Edge fabric 2 IP cloud Edge fabric 1 Edge fabric 3 E_Port E_Port IFL IFL IFL VEX_Port FC router EX_Port (2) = LSAN Backbone fabric FIGURE 150 A metaSAN with edge-to-edge and backbone fabrics Guidelines for setting up Fibre Channel routing The following are some general guidelines for setting up Fibre Channel routing: • Ensure that the backbone fabric ID of the FC router is the same as that of other FC routers in the backbone fabric.
16 Connecting edge fabrics to a backbone fabric Connecting edge fabrics to a backbone fabric The following procedure explains how to set up FC-FC routing on two edge fabrics connected through an FC router using E_Ports and EX_Ports. For Enterprise Edition only: If you are connecting Fibre Channel SANs through an IP-based network, see “Configuring an FCIP tunnel” on page 646 for instructions on setting up an FCIP tunnel between a VE_Port and a VEX_Port.
Connecting edge fabrics to a backbone fabric 16 4. Click the right arrow button to move the FC router you selected to the Selected Router list. 5. Select a valid fabric ID (1 through 128) from the Fabric ID list. You can choose any unique fabric ID as long as it is consistent for all EX_Ports that connect to the same edge fabric. If the edge fabric is already configured with the backbone fabric, the Fabric ID list is disabled and populated with the pre-selected value. 6.
16 Configuring routing domain IDs Configuring routing domain IDs Logical (phantom) domains are created to enable routed fabrics. Two types of logical domains are created: • A front domain is created in edge fabrics for every interfabric link (IFL). • A translate (Xlate) domain is created in routed fabrics that share devices. Use the following procedure to change the domain IDs of these logical domains. 1.
Chapter 17 Virtual Fabrics In this chapter • Virtual Fabrics overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 • Virtual Fabrics requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 • Configuring Virtual Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17 Virtual Fabrics overview Terminology Table 30 lists definitions of Virtual Fabrics terms. TABLE 30 414 Virtual Fabrics terms Term Definition Physical chassis The physical switch or chassis from which you create logical switches and fabrics. Logical switch A collection of zero or more ports that act as a single Fibre Channel (FC) switch. When Virtual Fabrics is enabled on the chassis, there is always at least one logical switch: the default logical switch.
Virtual Fabrics requirements 17 Virtual Fabrics requirements To configure Virtual Fabrics, you must have at least one Virtual Fabrics-enabled physical chassis running Fabric OS 6.2.0 or later in your SAN. Use one of the following options to discover a Virtual Fabrics-enabled physical chassis on the Management application topology: • Discover a Virtual Fabrics-capable seed physical chassis running Fabric OS 6.2.0 or later. Virtual Fabrics is disabled by default.
17 Configuring Virtual Fabrics TABLE 32 Blade and port types supported on logical switches for backbone chassis (Continued) Logical switch Base switch • • • • • • • • • • Extension Blade—GE_ and VE_Ports FC 8 GB Port Blade—E_ and F_Ports FC 16 GB Port Blade—E_ and F_Ports 8 Gbps Extension Blade • FC ports: E_, F_, and VE_Ports • GE ports: VE_Ports 384-port and 192-port Backbone Chassis— ICL ports Extension Blade—GE_ and VEX_Ports FC 8 GB Port Blade—E_ and EX_Ports FC 16 GB Port Blade—E_ and EX_Ports
Configuring Virtual Fabrics 17 3. Set up logical switches in each physical chassis: a. Create logical switches in each physical chassis and assign ports to them. Make sure the logical switches are configured to allow XISL use. See “Creating a logical switch or base switch” on page 418 for instructions. b. Disable all of the logical switches in each physical chassis. Right-click each logical switch in the Connectivity Map or Product List and select Enable/Disable > Disable. c.
17 Configuring Virtual Fabrics Creating a logical switch or base switch NOTE Virtual Fabrics must be enabled on at least one physical chassis in your fabric. Optionally, you can define the logical switch to be a base switch. Each chassis can have only one base switch. 1. Select a switch with Virtual Fabrics enabled on the Product List or Connectivity Map and select Configure > Virtual Fabric > Logical Switches. The Logical Switches dialog box displays. 2.
Configuring Virtual Fabrics 17 8. (Optional) Perform the following steps to make the logical switch a base switch: a. Clear the Base Fabric for Transport check box. This check box is not relevant for base switches because all base switches can use XISLs. b. Select the Base Switch check box. 9. (Optional) For Backbone Chassis only, select an option in the 256 Area Limit list to use 256-area addressing mode (zero-based or port-based) or to disable this mode (default).
17 Configuring Virtual Fabrics 20. Click Start to send these changes to the affected chassis. NOTE Most changes to logical switches will disrupt data traffic in the fabric. The status of each change is displayed in the Status column and Status area in the dialog box. 21. When the changes are complete, click Close. 22. If the newly created switch is not part of a discovered fabric, then you must discover the switch. a. Undiscover the physical chassis. See “Deleting a fabric” on page 56 for instructions.
Configuring Virtual Fabrics 17 6. Click the right arrow button. The ports display in the selected logical switch node in the Existing Logical Switches table. 7. Click OK on the Logical Switches dialog box. The Logical Switch Change Confirmation and Status dialog box displays with a list of all changes you made in the Logical Switches dialog box. The Re-Enable ports after moving them and QoS disable the ports while moving them check boxes are selected by default.
17 Configuring Virtual Fabrics 8. Click OK on the Logical Switches dialog box. The Logical Switch Change Confirmation and Status dialog box displays with a list of all changes you made in the Logical Switches dialog box. The Re-Enable ports after moving them and QoS disable the ports while moving them check boxes are selected by default. NOTE Ports are disabled before moving from one logical switch to another. 9. (Optional) Select the Unbind Port Addresses while moving them check box. 10.
Configuring Virtual Fabrics 17 Configuring fabric-wide parameters for a logical fabric When you create a logical switch, you must assign it to a fabric and configure fabric-wide parameters. All the switches in a fabric must have the same fabric-wide settings. Instead of configuring these settings separately on each logical switch, you can create a logical fabric template, which defines the fabric-wide settings for a logical fabric.
17 Configuring Virtual Fabrics 8. Click OK on the New Logical Fabric Template dialog box. The new logical fabric template displays under the Discovered Logical Switches node in the Existing Logical Switches table (already highlighted). All of the logical fabric templates have the same name, “NewFabric”. You can differentiate among the templates by the FID number. You can now create logical switches using the fabric-wide settings in the logical fabric template.
Configuring Virtual Fabrics 17 Moving a logical switch to a different fabric You can move a logical switch from one fabric to another by assigning a different fabric ID. 1. Select a switch on the Product List or Connectivity Map and select Configure > Virtual Fabric > Logical Switches. The Logical Switches dialog box displays. 2. Right-click anywhere in the Existing Logical Switches table and select Table > Expand All. 3. Select the logical switch you want to move to another logical fabric. 4. Click Edit.
17 Configuring Virtual Fabrics Changing a logical switch to a base switch The Base Switch column in the Existing Logical Switches table indicates whether a logical switch is a base switch. 1. Select a switch on the Product List or Connectivity Map and select Configure > Virtual Fabric > Logical Switches. The Logical Switches dialog box displays. 2. Right-click anywhere in the Existing Logical Switches table and select Table > Expand All. 3. Select the logical switch you want to change to a base switch. 4.
Chapter 18 SAN Encryption configuration In this chapter • Encryption Center features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Encryption user privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Smart card usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Network connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18 Encryption Center features Encryption Center features The Encryption Center dialog box is the single launching point for all encryption-related configuration in the Management application (Figure 153). It also provides a table that shows the general status of all encryption-related hardware and functions at a glance. FIGURE 153 Encryption Center dialog box Beginning with Fabric OS 6.
Encryption user privileges 18 Encryption user privileges In the Management application, resource groups are assigned privileges, roles, and fabrics. Privileges are not directly assigned to users; users get privileges because they belong to a role in a resource group. A user can only belong to one resource group at a time. The Management application provides three pre-configured roles: • Storage encryption configuration. • Storage encryption key operations. • Storage encryption security.
18 Encryption user privileges TABLE 33 Privilege Storage Encryption Configuration Storage Encryption Key Operations Storage Encryption Security Read/Write • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 430 Launch the Encryption center dialog box. View switch, group, or engine properties. View the Encryption Group Properties Security tab. View encryption targets, hosts, and LUNs.
Smart card usage 18 Smart card usage Smart Cards are credit card-sized cards that contain a CPU and persistent memory. Smart cards can be used as security devices. You must have Storage Encryption Security user privileges to activate, register, and configure smart cards. Smart cards can be used to do the following: • Control user access to the Management application security administrator roles. • Control activation of encryption engines. • Securely store backup copies of master keys.
18 Smart card usage 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). 2. Select an encryption group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click an encryption group and select Security. The Encryption Group Properties dialog box displays with the Security tab selected (Figure 154). FIGURE 154 Encryption Group Properties dialog box - registering authentication cards 3.
Smart card usage 18 FIGURE 155 Add Authentication Card dialog box 5. Insert a smart card into the card reader. Wait for the card serial number to appear, then enter card assignment information as directed. 6. Click OK. 7. Wait for the confirmation dialog box indicating initialization is done, then click OK. The card is added to the Registered Authentication Cards table in the Encryption Group Properties dialog box. 8. Repeat step 5 through step 7 until you have successfully registered all cards.
18 Smart card usage FIGURE 156 Encryption Group Properties dialog box - Security tab 3. Click Register from Archive. The Authentication Cards dialog box displays (Figure 157). The dialog box lists the smart cards that are in the database. FIGURE 157 Authentication Cards dialog box - registering smart cards from archive 4. Select a card from the table, then click OK. 5. Wait for the confirmation dialog box indicating initialization is done, then click OK.
Smart card usage 18 3. Select the authentication card in the Registered Authentication Cards table. 4. Click Deregister. 5. A confirmation dialog box displays. Click Yes to confirm deregistration. The registered authentication card is removed from the table. 6. Click OK. The card is deregistered from the group.
18 Smart card usage 1. Select an encryption group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click a group and select Security. The Encryption Group Properties dialog box displays, with the Security tab selected (Figure 156). 2. Do one of the following: • Set System Cards to Required to require the use of a system card for controlling activation of the encryption engine. Click OK after reading the message in the encryption message dialog box.
Smart card usage 18 6. Store the card in a secure location, not in proximity to the switch or blade. Deregistering a system card System cards can be removed from the database by deregistering them. Use the following procedure to deregister a system card: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). 2.
18 Smart card usage 2. Select a smart card from the table, then do one of the following: • Click Delete to remove the smart card from the Management application database. Deleting smart cards from the Management application database keeps the Smart Cards table at a manageable size, but does not invalidate the smart card. The smart card can still be used. You must deregister a smart card to invalidate its use. The Delete operation applies only to recovery cards.
Network connections 18 Network connections Before you use the encryption setup wizard for the first time, you must have the following required network connections: • The management ports on all encryption switches and 384-port Backbone Chassis CPs that have encryption blades installed must have a LAN connection to the SAN management program, and must be available for discovery.
18 Configuring blade processor links Configuring blade processor links Each encryption switch or blade has two GbE ports labeled Ge0 and Ge1. The Ge0 and Ge1 ports are Ethernet ports that connect encryption switches and blades to other encryption switches and blades. Both ports of each encryption switch or blade must be connected to the same IP network and the same subnet. Static IP addresses should be assigned. Neither VLANs nor DHCP should be used.
Encryption node initialization and certificate generation 18 Encryption node initialization and certificate generation When an encryption node is initialized, the following security parameters and certificates are generated: • • • • • FIPS crypto officer FIPS user Node CP certificate A signed Key Authentication Center (KAC) certificate A KAC Certificate Signing Request (CSR) From the standpoint of external SAN management application operations, the FIPS crypto officer, FIPS user, and node CP certificat
18 Supported encryption key manager appliances Supported encryption key manager appliances As stated under “Network connections”, a supported key management appliance must be connected on the same LAN as the management port of the encryption switches, or of the Backbone Chassis Control Processors (CPs) in the case of the encryption blade.
Steps for connecting to an RKM appliance 18 Steps for connecting to an RKM appliance All switches you plan to include in an encryption group must have a secure connection to the RSA Key Manager (RKM). The following is a suggested order of steps needed to create a secure connection to RKM: 1. Export the KAC CSR to a location accessible to a CA for signing. 2. Submit the KAC CSR for signing by a CA. 3. Import the signed certificate into the Fabric OS encryption node. 4.
18 Steps for connecting to an RKM appliance Submitting the CSR to a certificate authority The CSR must be submitted to a CA to be signed. The certificate authority is a trusted third-party entity that signs the CSR. There are several CAs available and procedures vary, but the general steps are as follows: 1. Open an SSL connection to an X.509 server. 2. Submit the CSR for signing. 3. Request the signed certificate.
Steps for connecting to an RKM appliance 18 5. Select Upload, Configure SSL, and Restart Webserver. 6. After the web server restarts, enter the root password. 7. Open another web browser window, and start the RSA management user interface. You will need the URL, and have the proper authority level, user name, and password. NOTE The Identity Group name used in the next step might not exist in a freshly installed RKM. To establish an Identity Group name, click the Identity Group tab, and create a name.
18 Steps for connecting to an RKM appliance The CA certificate file referenced in the SSLCAcertificateFile field (see step 4) must be imported and registered on the switch designated as an encryption group leader. You may want to note this location before proceeding to “Loading the CA certificate onto the encryption group leader” on page 446.
Steps for connecting to an RKM appliance 18 . FIGURE 164 Encryption Group Properties with Key Vault Certificate 2. Select Load from File. A dialog box opens that allows you to browse to a location on your client PC that contains the downloaded CA certificate in .pem format.
18 Steps for connecting to an LKM appliance Steps for connecting to an LKM appliance The NetApp Lifetime Key Manager (LKM) resides on an FIPS 140-2 Level 3-compliant network appliance. The encryption engine and LKM appliance communicate over a trusted link. A trusted link is a secure connection established between the Encryption switch or blade and the NetApp LKM appliance, using a shared secret called a link key.
Steps for connecting to an LKM appliance 18 1. Select an LKM group from the Encryption Center Devices table, then select Group > Link Keys from the menu task bar, or right-click an LKM group and select Link Keys. The switch name displays in the link status table under Switch, with a Link Key Status of Link Key requested, pending LKM approval. 2. Select the switch, then click Establish.
18 Steps for connecting to an LKM appliance 2. Add the group leader to the LKM key sharing group. Enter lkmserver add --type third-party --key-sharing-group "/" followed by the group leader IP address. lkm-1>lkmserver add --type third-party --key-sharing-group \ "/" 10.32.244.71 NOTICE: LKM Server third-party 10.32.244.71 added. Cleartext connections not allowed. 3. On the NetApp LKM appliance terminal, enter sys cert getcert-v2 to display the LKM certificate content.
Steps for connecting to an LKM appliance 18 LKM key vault high availability deployment LKM appliances can be clustered to provide high availability capabilities. You can deploy and register one LKM with an encryption switch or blade and later deploy and register another LKM at any time if LKMs are clustered or linked together. Please refer to LKM documentation to link or cluster the LKMs.
18 Steps for connecting to an LKM appliance Tape LUN and DF -compatible tape pool support • DEK creation - The DEK is created and archived to the primary LKM only. Upon successful archival of the DEK to the primary LKM, the DEK can be used for encryption of a Tape LUN or DF-Compatible tape pool. The DEK is synchronized to a secondary LKM through LKM clustering. If DEK archival to the primary LKM fails, DEK archival is retried to the clustered secondary LKM.
Steps for connecting to an SKM appliance 18 Steps for connecting to an SKM appliance The SKM management web console can be accessed from any web browser with Internet access to the SKM appliance. The URL for the appliance is as follows: https://: Where: - is the hostname or IP address when installing the SKM appliance. is 9443 by default.
18 Steps for connecting to an SKM appliance 3. Select Local Users & Groups under Users and Groups. The User & Group Configuration page displays. 4. Select Add under Local Users. 5. Create a Brocade user name and password. 6. Select the User Administration Permission and Change Password Permission check boxes. 7. Select Save to save this user data. 8. Select Add under Local Groups. 9. Add a Brocade group under Group. 10. Select Save. 11. Select the new Brocade group name, then select Properties.
Steps for connecting to an SKM appliance 18 FIGURE 166 Key Vault Credentials dialog box 3. Enter the Brocade group user name and password. Keep the following rules in mind when registering the Brocade user name and password: - The user name and password must match the user name and password specified for the Brocade group. - The same user name and password must be configured on all nodes in an encryption group.
18 Steps for connecting to an SKM appliance 4. Enter information required by the Create Local Certificate Authority section of the window to create your local CA. - Enter a Certificate Authority Name and Common Name. These may be the same value. Enter your organizational information. Enter the Email Address to receive messages for the Security Officer. Enter the Key Size. HP recommends using 2048 for maximum security. Select Self-signed Root CA.
Steps for connecting to an SKM appliance 18 8. From the list of Available CAs in the right panel, select the CA you just created. Repeat these steps any time another local CA is needed. Downloading the local CA certificate from SKM The local CA certificate you created using the procedure for “Setting up the local Certificate Authority (CA) on SKM” on page 455 must be saved to your local system. Later, this certificate must be imported onto the Brocade encryption group leader nodes. 1.
18 Steps for connecting to an SKM appliance 11. Enter the required data in the Sign Certificate Request section of the window. - Select the CA name from the Sign with Certificate Authority drop-down list. Select Server as the Certificate Purpose. Enter the number of days before the certificate must be renewed based on your site's security policies. The default value is 3649 or 10 years. 12. Paste the copied certificate request data into the Certificate Request box. 13. Click Sign Request.
Steps for connecting to an SKM appliance 18 Creating an SKM High Availability cluster The HP SKM key vault supports clustering of HP SKM appliances for high availability. If two SKM key vaults are configured, they must be clustered. If only a single SKM appliance is configured, it may be clustered for backup purposes, but the backup appliance will not be directly used by the switch.
18 Steps for connecting to an SKM appliance Adding SKM appliances to the cluster If you are adding an appliance to an existing cluster, select the Cluster Settings section of the window, click Download Cluster Key, then save the key to a convenient location, such as your computer's desktop.
Steps for connecting to an SKM appliance 18 Signing the Brocade encryption node KAC certificates 1. The KAC certificate signing request generated when the encryption node is initialized must be exported for each encryption node and signed by the Brocade local CA on SKM. The signed certificate must then be imported back into the encryption node. 2. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 3.
18 Steps for connecting to an SKM appliance 1. Select a switch from the Encryption Center Devices table, then select Switch > Import Certificate from the menu task bar, or right-click a switch and select Import Certificate. The Import Signed Certificate dialog box displays (Figure 168). FIGURE 168 Import Signed Certificate dialog box 2. Browse to the location where the signed certificate is stored. 3. Click OK. The signed certificate is stored on the switch.
Steps for connecting to an SKM appliance 18 Tape LUN support • DEK Creation - The DEK is created and archived to the SKM cluster using the cluster’s virtual IP address. The DEK is synchronized with other SKMs in the cluster. Upon successful archival of the DEK to the SKM cluster, the DEK can be used for encryption of the tape LUN. If archival of the DEK to the SKM cluster fails, an error is logged and the operation is retried.
18 Steps for connecting to a TEMS appliance Steps for connecting to a TEMS appliance TEMS provides a web user interface for management of clients, keys, admins, and configuration parameters. A Thales officer creates domains, groups, and managers (a type of administrator), assigns groups to domains, and assigns managers to manage groups. Managers are responsible for creating clients and passwords for the groups they manage.
Steps for connecting to a TEMS appliance 18 1. Log in to the Thales management program as admin and select the Network tab (Figure 169). FIGURE 169 TEMS Network Settings 2. Enter the management IP address information under Management Interface. 3. Enter the client IP address information under KM Server Interface. 4. Enter a host name for the appliance, Internet or intranet domain, and, if used, the primary and secondary DNS IP address under Common Settings. 5. Set Service Settings.
18 Steps for connecting to a TEMS appliance Creating a client on TEMS This step assumes the group brocade has been created by an administrator. If the group brocade does not exist, you must log in to TEMS as officer, create the group, and assign the group to a manager. 1. From the Encryption Center Devices table, select a switch that needs to have a TEMS Client. 2. Select Properties. 3. Click Key Vault User Name. The Key Vault User Information dialog box displays (Figure 170).
Steps for connecting to a TEMS appliance 18 9. Enter a password in the Password and Verify Password fields. 10. Select the group brocade from the group pull-down menu. 11. Click Add Client. A TEMS client user is created and is listed in the table. Establishing TEMS key vault credentials on the switch The credentials established for the TEMS client must be presented to TEMS by the switch. 1.
18 Steps for connecting to a TEMS appliance 4. In the user table under the Certificate column, click the pen icon for the newly created user. The Sign Certificate Request page displays. 5. Enter the CSR file name exported from the switch in the From File box, or if you copied the CSR from Switch > Properties, paste the CSR file contents to the From Text box. 6. Click Sign. 7. Under the Certificate column, click the export icon (globe with an arrow). A file save dialog displays. 8.
Steps for connecting to a TKLM appliance 18 Steps for connecting to a TKLM appliance All switches you plan to include in an encryption group must have a secure connection to the Tivoli Key Lifecycle Manager (TKLM). A local LINUX host must be available to transfer certificates. NOTE Ensure that the time zone and clock time setting on the TKLM server and Brocade encryption nodes are the same. A difference of only a few minutes can cause the TLS connectivity to fail.
18 Steps for connecting to a TKLM appliance 1. Select a switch from the Encryption Center Devices table, then select Switch > Export Certificate from the menu task bar, or right-click the switch and select Export Certificate. The Export Signed Certificate dialog box displays. 2. Select Signed switch certificate, then click OK. A dialog box displays allowing you to save the signed certificate in .pem format in My Documents on your work station. 3. Make a note of this location.
Steps for connecting to a TKLM appliance 18 Creating a self-signed certificate for TKLM You must create a self-signed certificate for TKLM that can be downloaded to the Fabric OS encryption engines to verify the authenticity of TKLM. 1. Select Tivoli Key Lifecycle Manager > Configuration. The Configuration page displays. 2. Select Create self-signed certificate. 3. Under Certificate label in key store, enter a certificate label. 4. Under Certificate description (common name), enter a descriptive name. 5.
18 Steps for connecting to a TKLM appliance For Windows: \ibm\tivoli\tiptklmV2\bin\wsadmin.bat -username TKLMAdmin -password -lang jython 2. Check the certificate list using the following command: print AdminTask.tklmCertList('[]') The listing will contain the uuid for all certificates. Use the uuid of the server certificate to export the server certificate from the database to the file system. print AdminTask.
Encryption preparation 18 Encryption preparation Before you use the encryption setup wizard for the first time, you should have a detailed configuration plan in place and available for reference. The encryption setup wizard assumes the following: • You have a plan in place to organize encryption devices into encryption groups.
18 Creating a new encryption group Creating a new encryption group The following steps describe how to start and run the encryption setup wizard and create a new encryption group. NOTE When a new encryption group is created, any existing tape pools in the switch are removed. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 175). FIGURE 175 Encryption Center dialog box - No group defined 2.
Creating a new encryption group 18 FIGURE 176 Configure Switch Encryption wizard - welcome dialog box 4. Click Next. The Designate Switch Membership dialog box displays (Figure 177). FIGURE 177 Designate Switch Membership dialog box 5. Verify that Create a new encryption group containing just this switch is selected. 6. Click Next. The Create a New Encryption Group dialog box displays (Figure 178).
18 Creating a new encryption group FIGURE 178 Create a New Encryption Group dialog box 7. Enter an Encryption Group Name for the encryption group and select Automatic failback mode. Encryption group names can have up to 15 characters. Letters, digits, and underscores are allowed. If the name for the encryption group already exists, a pop-up warning message displays. Although unique group names avoid confusion while managing multiple groups, you are not prevented from using duplicate group names.
Creating a new encryption group 18 9. Select the Key Vault Type. Configuration options vary based on the key vault type you choose. To complete the wizard steps, proceed to the section that describes your particular key vault type. Key vault types are: - RSA Key Manager (RKM). For RKM key vault setting instructions, see “Configuring key vault settings for RSA Key Manager (RKM)” on page 477. - NetApp Link Key Manager (LKM).
18 Creating a new encryption group 3. If you are implementing encryption on data replication LUNs used by the EMC Symmetrix Remote Data Facility (SRDF), you must select Enabled for REPL Support. 4. Click Next. The Specify Certificate Signing Request File Name dialog box displays (Figure 181). FIGURE 181 Specify Certificate Signing Request File Name dialog box 5. Enter the location of the file where you want to store the certificate information, or browse to the desired location.
Creating a new encryption group 18 FIGURE 182 Specify Master Key File Name dialog box 7. Enter the location of the file where you want to store back up master key information, or browse to the desired location. 8. Enter the passphrase, which is required for restoring the master key. The passphrase can be between eight and 40 characters, and any character is allowed. 9. Re-enter the passphrase for verification. 10. Click Next. The Select Security Settings dialog box displays (Figure 183).
18 Creating a new encryption group FIGURE 183 Select Security Settings dialog box 11. Set quorum size and system card requirements. The quorum size is the minimum number of cards necessary to enable the card holders to perform the security sensitive operations listed above. The maximum quorum size is five cards.
Creating a new encryption group 18 FIGURE 184 Confirm Configuration dialog box 13. Verify the information, then click Next. 14. The Configuration Status dialog box displays (Figure 185). FIGURE 185 Configuration Status dialog box 15. Review the post-configuration instructions, which you can copy to a clipboard or print for later. 16. Click Next. The Next Steps dialog box displays (Figure 186). Instructions for installing public key certificates for the encryption switch are displayed.
18 Creating a new encryption group FIGURE 186 Next Steps dialog box 17. Review the post-configuration instructions, which you can copy to a clipboard or print for later. 18. Click Finish to exit the Configure Switch Encryption wizard. 19. Review “Understanding configuration status results” on page 503. Configuring key vault settings for NetApp Link Key Manager (LKM) The following procedure assumes you have already configured the initial steps in the Configure Switch Encryption wizard.
Creating a new encryption group 18 FIGURE 187 Select Key Vault dialog box for LKM 1. Enter the IP address or host name for the primary key vault. 2. Enter the name of the file that holds the primary key vault’s public key certificate or browse to the desired location. 3. If you are using a backup key vault, enter the IP address or host name, and the name of the file holding the backup key vault’s public key certificate in the fields provided. 4. Click Next.
18 Creating a new encryption group FIGURE 188 Specify Public Key Certificate (KAC) File Name dialog box 5. Specify the location of the file where you want to store the public key certificate that is used to authenticate connections to the key vault. The certificate stored in this file is the switch’s public key certificate. You will need to know this path and file name to install the switch’s public key certificate on the key management appliance. 6. Click Next.
Creating a new encryption group 18 FIGURE 189 Select Security Settings dialog box 7. Set quorum size and system card requirements. The quorum size is the minimum number of cards necessary to enable the card holders to perform the security sensitive operations listed above. The maximum quorum size is five cards.
18 Creating a new encryption group FIGURE 190 Confirm Configuration dialog box 9. Click Next. The Configuration Status dialog box displays (Figure 191).
Creating a new encryption group 18 All configuration items have green check marks if the configuration is successful. A red stop sign indicates a failed step. A message displays below the table, indicating the encryption switch was added to the group you named, and the public key certificate is stored in the location you specified. After configuration of the encryption group is completed, the Management application sends API commands to verify the switch configuration.
18 Creating a new encryption group FIGURE 193 Select Key Vault dialog box for SKM 1. Enter the IP address or host name for the primary key vault. 2. Enter the name of the file that holds the primary key vault’s CA key certificate or browse to the desired location. 3. Enter the password you established for the Brocade user group. 4. If you are using a backup key vault, enter the IP address or host name, and the name of the file holding the backup key vault’s public key certificate in the fields provided.
Creating a new encryption group 18 FIGURE 194 Specify Certificate Signing Request File Name dialog box 6. Enter the location of the file where you want to store the certificate information, or browse to the desired location. 7. Click Next. The Specify Master Key File Name dialog box displays (Figure 195).
18 Creating a new encryption group 8. Enter the passphrase, which is required for restoring the master key. The passphrase can be between eight and 40 characters, and any character is allowed. 9. Re-enter the passphrase for verification. 10. Click Next. 11. The Select Security Settings dialog box displays (Figure 196). FIGURE 196 Select Security Settings dialog box 12. Set quorum size and system card requirements.
Creating a new encryption group 18 FIGURE 197 Confirm Configuration dialog box 14. Verify the information, then click Next. The Configuration Status dialog box displays (Figure 198).
18 Creating a new encryption group All configuration items have green check marks if the configuration is successful. A red stop sign indicates a failed step. A message displays below the table, indicating the encryption switch was added to the group you named, and the public key certificate is stored in the location you specified. After configuration of the encryption group is completed, the Management application sends API commands to verify the switch configuration.
Creating a new encryption group 18 FIGURE 200 Select Key Vault dialog box for TEMS 1. Enter the IP address or host name for the primary key vault. 2. Enter the name of the file that holds the primary key vault’s public key certificate, or browse to the desired location. 3. Enter the password you created for the Brocade group TEMS client. 4.
18 Creating a new encryption group FIGURE 201 Specify Master Key File Name dialog box 6. Enter the name of the file used for backing up the master key or browse to the desired location. 7. Enter the passphrase, which is required for restoring the master key. The passphrase can be between eight and 40 characters, and any character is allowed. 8. Re-enter the passphrase for verification. 9. Click Next. The Select Security Settings dialog box displays (Figure 202).
Creating a new encryption group 18 FIGURE 202 Select Security Settings dialog box 10. Set quorum size and system card requirements. The quorum size is the minimum number of cards necessary to enable the card holders to perform the security sensitive operations listed above. The maximum quorum size is five cards.
18 Creating a new encryption group FIGURE 203 Confirm Configuration dialog box 12. Verify the contents, then click Next. 13. The Configuration Status dialog box displays (Figure 204).
Creating a new encryption group 18 All configuration items have green check marks if the configuration is successful. A red stop sign indicates a failed step. A message displays below the table, indicating the encryption switch was added to the group you named, and the public key certificate is stored in the location you specified. After configuration of the encryption group is completed, the Management application sends API commands to verify the switch configuration.
18 Creating a new encryption group FIGURE 206 Select Key Vault dialog box for TKLM 1. Enter the IP address or host name for the primary key vault. 2. Enter the name of the file that holds the primary key vault’s public key certificate or browse to the desired location. 3. If you are using a backup key vault, enter the IP address or host name, and the name of the file holding the backup key vault’s public key certificate in the fields provided. 4. Click Next.
Creating a new encryption group 18 FIGURE 207 Specify Public Key Certificate (KAC) File Name dialog box 5. Enter the name of the file where the switch’s public key certificate is stored, or browse to the desired location. 6. Click Next. The Specify Master Key File Name dialog box displays (Figure 208).
18 Creating a new encryption group 7. Enter the name of the file used for backing up the master key, or browse to the desired location. 8. Enter the passphrase, which is required for restoring the master key. The passphrase can be between eight and 40 characters, and any character is allowed. 9. Re-enter the passphrase for verification. 10. Click Next. The Select Security Settings dialog box displays (Figure 209). FIGURE 209 Select Security Settings dialog box 11.
Creating a new encryption group 18 FIGURE 210 Confirm Configuration dialog box 13. Verify the information, then click Next. The Configuration Status dialog box displays (Figure 211).
18 Creating a new encryption group All configuration items have green check marks if the configuration is successful. A red stop sign indicates a failed step. A message displays below the table, indicating the encryption switch was added to the group you named, and the public key certificate is stored in the location you specified. After configuration of the encryption group is completed, the Management application sends API commands to verify the switch configuration.
Creating a new encryption group 18 Understanding configuration status results After configuration of the encryption group is completed, the Management application sends API commands to verify the switch configuration. The CLI commands are detailed in encryption administrator’s guide for your key vault management system. • Initialize the switch. If the switch is not already in the initiated state, the Management application performs the cryptocfg --initnode command.
18 Adding a switch to an encryption group Adding a switch to an encryption group The setup wizard allows you to either create a new encryption group, or add an encryption switch to an existing encryption group. Use the following procedure to add a switch to an encryption group: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). 2.
Adding a switch to an encryption group 18 FIGURE 214 Designate Switch Membership dialog box 4. Select Add this switch to an existing encryption group. 5. Click Next. The Add Switch to Existing Encryption Group dialog box displays (Figure 215).
18 Adding a switch to an encryption group 6. Select the group in which to add the switch, then click Next. The Specify Public Key Certificate (KAC) File Name dialog box displays (Figure 216). FIGURE 216 Specify Public Key Certificate (KAC) File Name dialog box 7. Enter the location where you want to store the public key certificate that is used to authenticate connections to the key vault, or browse to the desired location, then click Next. The Confirm Configuration dialog box displays (Figure 217).
Adding a switch to an encryption group 18 FIGURE 217 Confirm Configuration dialog box 8. Click Next. The Configuration Status dialog box displays (Figure 218).
18 Adding a switch to an encryption group All configuration items have green check marks if the configuration is successful. A red stop sign indicates a failed step. A message displays below the table, indicating the encryption switch was added to the group you named, and the public key certificate is stored in the location you specified. 9. Review important messages, then click Next. The Error Instructions dialog box displays (Figure 219).
Replacing an encryption engine in an encryption group 18 Replacing an encryption engine in an encryption group To replace an encryption engine in an encryption group with another encryption engine within the same DEK Cluster, complete the following steps: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 2.
18 Creating high availability (HA) clusters Creating high availability (HA) clusters A high availability (HA) cluster is a group of exactly two encryption engines. One encryption engine can take over encryption and decryption tasks for the other encryption engine, if that member fails or becomes unreachable. When creating a new HA Cluster, add one engine to create the cluster, then add the second engine.
Creating high availability (HA) clusters 18 FIGURE 221 Encryption Group Properties dialog box - HA Clusters tab NOTE If you are creating a new HA cluster, a dialog box displays requesting a name for the new HA cluster. HA Cluster names can have up to 31 characters. Letters, digits, and underscores are allowed. Removing engines from an HA cluster Removing the last engine from an HA cluster also removes the HA cluster.
18 Creating high availability (HA) clusters Swapping engines in an HA cluster Swapping engines is useful when replacing hardware. Swapping engines is different from removing an engine and adding another because when you swap engines, the configured targets on the former HA cluster member are moved to the new HA cluster member. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). 2.
Adding encryption targets 18 Adding encryption targets Adding an encryption target maps storage devices and hosts to virtual targets and virtual initiators within the encryption switch. NOTE It is recommended that you configure the host and target in the same zone before configuring them for encryption. If the host and target are not already in the same zone, you can still configure them for encryption, but you will need to configure them in the same zone before you can commit the changes.
18 Adding encryption targets FIGURE 223 Configure Storage Encryption dialog box 4. Click Next. The Select Encryption Engine dialog box displays (Figure 224).
Adding encryption targets 18 The list of engines depends on the scope being viewed. • If the Targets dialog box is showing all targets in an encryption group, the list includes all engines in the group. • If the Targets dialog box is showing all targets for a switch, the list includes all encryption engines for the switch. • If the Targets dialog box is showing targets for a single encryption engine, the list contains only that engine. 5.
18 Adding encryption targets FIGURE 226 Select Hosts dialog box 7. Select hosts using either of the following methods: a. Select a maximum of 1024 hosts from the Hosts in Fabric table, then click the right arrow to move the hosts to the Selected Hosts table. (The Port WWN column contains all target information that displays when using the nsshow command.) b. Manually enter world wide names in the Port WWN and Node WWN text boxes if the hosts are not included in the table.
Adding encryption targets 18 FIGURE 227 Name Container dialog box 9. Click Next. The Confirmation dialog box displays (Figure 228). FIGURE 228 Confirmation dialog box 10. Click Next after you have verified the contents. Clicking Next creates the configuration. The Configuration Status dialog box displays (Figure 229). The dialog box lists the target and host that are configured in the target container, as well as the virtual targets (VT) and virtual initiators (VI).
18 Adding encryption targets NOTE If you can view the VI/VT Port WWNs and VI/VT Node WWNs, the container has been successfully added to the switch. FIGURE 229 Configuration Status dialog box 11. Review any post-configuration instructions or messages, which you can copy to a clipboard or print for later. 12. Click Next. The Next Steps dialog box displays (Figure 230). Instructions for installing public key certificates for the encryption switch are displayed.
Adding encryption targets 18 FIGURE 230 Next Steps dialog box 13. Review the post-configuration instructions, which you can copy to a clipboard or print for later. 14. Click Finish to exit the Configure Switch Encryption wizard. 15. Review “Understanding configuration status results” on page 503.
18 Configuring hosts for encryption targets Configuring hosts for encryption targets Use the Encryption Target Hosts dialog box to edit (add or remove) hosts for an encrypted target. NOTE Hosts are normally selected as part of the Configure Switch Encryption wizard, but you can also edit hosts later using the Encryption Target Hosts dialog box. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). 2.
Configuring hosts for encryption targets 18 FIGURE 232 Encryption Target Hosts dialog box 4. Select one or more hosts in a fabric, then move them to the Selected Hosts table using the right arrow, or manually enter world wide names in the Port WWN and Node WWN text boxes if the hosts are not included in the list. You must fill in both the Port WWN and the Node WWN. Click Add to move the host to the Selected Hosts list. 5. Click OK or Apply to apply your changes.
18 Adding target disk LUNs for encryption Adding target disk LUNs for encryption You can add a new path to an existing disk LUN or add a new LUN and path by launching the Add New Path wizard. To launch the wizard, complete the following steps: Before You Begin Before you can add a target disk LUN for encryption, you must first configure the Storage Arrays. For more information, see “Configuring Storage Arrays” on page 525. 1. Select Configure > Encryption from the menu task bar.
Adding target disk LUNs for encryption 18 4. Select the target port from the Target Port table. 5. Click Next. The Select Initiator Port dialog box displays (Figure 235). FIGURE 235 Select Initiator Port dialog box 6. Select the initiator port from the Initiator Port table. 7. Click Next. LUN discovery is launched and a progress bar displays. There are four possible outcomes: - A message displays indicating no LUNs were discovered. Click OK to dismiss the message and exit the wizard.
18 Adding target disk LUNs for encryption FIGURE 236 Select LUN dialog box 8. Set the Current LUN State as required. If the LUN already has an existing key ID, the Current LUN State field is automatically set to Encrypted. You can accept the automatically assigned state or change this value if desired. 9. If REPL Support was enabled by the Configure Switch Encryption wizard, a New LUN check box is presented and enabled by default.
Adding target disk LUNs for encryption 18 FIGURE 237 Correcting an Encryption Mode Mismatch When you correct a policy on a LUN, it is automatically selected for all paths to the selected LUN. When you modify LUN policies, a Modify icon displays to identify the modified LUN entry. 12. Click OK or Apply to apply the changes, or click OK to commit the transaction. Configuring Storage Arrays The Storage Array contains a list of storage ports that will be used later in the LUN centric view.
18 Adding target disk LUNs for encryption SRDF supports the following methods of data replication: • Synchronous Replication provides real-time mirroring of data between the source Symmetrix and the target Symmetrix systems. Data is written simultaneously to the cache of both systems in real time before the application I/O is completed, thus ensuring the highest possible data availability.
Adding target disk LUNs for encryption 18 FIGURE 238 Basic SRDF configuration with Brocade encryption switches Metadata requirements and remote replication When the metadata and key ID are written, the primary metadata on blocks 1–16 is compressed and encrypted. However, there are scenarios whereby these blocks cannot be compressed, and the metadata is not written to the media.
18 Adding target disk LUNs for encryption • The New LUN option is used only if an RKM key vault is configured for the encryption group. • The New LUN option can be used only if replication is enabled for the encryption group. • If the local LUN contains host data, configuring it with the New LUN option will cause the data on the last three blocks of the LUN to be lost. Before using the New LUN option, you must migrate the contents of the LUN to another LUN that is larger by at least three blocks.
Adding target tape LUNs for encryption 18 Adding target tape LUNs for encryption You configure a Crypto LUN by adding the LUN to the CryptoTarget container and enabling the encryption property on the Crypto LUN. You must add LUNs manually. After you add the LUNs, you must specify the encryption settings. When configuring a LUN with multiple paths, the same LUN policies must be configured on all paths to the LUN.
18 Adding target tape LUNs for encryption FIGURE 240 Encryption Target Tape LUNs dialog box 4. Click Add. The Add Encryption Target Tape LUNs dialog box displays (Figure 241). The dialog box includes a table of all LUNs in the storage device that are visible to hosts. LUNs are identified by the Host world wide name, LUN number, Volume Label Prefix number, and Enable Write Early ACK and Enable Read Ahead status. FIGURE 241 Add Encryption Target Tape LUNs dialog box 5. Select a host from the Host list.
Adding target tape LUNs for encryption 18 6. Choose a LUN to be added to an encryption target container using one of the two following methods: • Discover. Click to identify the exposed logical unit number for a specified initiator. If you already know the exposed LUNs for the various initiators accessing the LUN, you can enter the range of LUNs using the alternative method. • Enter a LUN number range. Click Show LUNs to add a range of LUNs to be configured for the selected host.
18 Configuring encrypted tape storage in a multi-path environment Configuring encrypted tape storage in a multi-path environment This example assumes one host is accessing one storage device using two paths: • The first path is from Host Port A to Target Port A, using Encryption Engine A for encryption. • The second path is from Host Port B to Target Port B, using Encryption Engine B for encryption. Encryption Engines A and B are in switches that are already part of Encryption Group X.
Tape LUN write early and read ahead 18 Tape LUN write early and read ahead The tape LUN write early and read ahead feature uses tape pipelining and prefetch to speed serial access to tape storage. These features are particularly useful when performing backup and restore operations, especially over long distances. You can enable tape LUN write early and read ahead while adding the tape LUN for encryption, or you can enable or disable these features after the tape LUN has been added for encryption.
18 Tape LUN write early and read ahead FIGURE 243 Encryption Target Tape LUNs dialog box - Setting tape LUN read ahead and write early 4. In the Enable Write EarlyAck and Enable Read Ahead columns, when the table is populated, you can set these features as desired for each LUN: • • • • To enable write early for a specific tape LUN, select Enable Write Early Ack for that LUN. To enable read ahead for a specific LUN, select Enable Read Ahead for that LUN.
Tape LUN statistics 18 Tape LUN statistics This feature enables you to view and clear statistics for tape LUNs. These statistics include the number of compressed blocks, uncompressed blocks, compressed bytes and uncompressed bytes written to a tape LUN. The tape LUN statistics are cumulative and change as the host writes more data on tape. You can clear the statistics to monitor compression ratio of ongoing host I/Os.
18 Tape LUN statistics FIGURE 245 Tape LUN Statistics dialog box 5. To clear the tape LUN statistics for all member LUNs for the container, click Clear. 6. When prompted with a confirmation dialog box, click Yes. 7. To update the tape LUN statistics, click Refresh. Viewing and clearing tape LUN statistics for specific tape LUNs To view or clear statistics for tape LUNs in a container, complete these steps: 1. Select Configure > Encryption from the menu task bar.
Tape LUN statistics 18 FIGURE 246 Target Tape LUNs dialog box 4. Select the LUN or LUNs for which to display or clear statistics. 5. Click Statistics. The Tape LUN Statistics dialog box displays (Figure 247). The dialog box displays the statistic results based on the LUN or LUNs you selected. FIGURE 247 Tape LUN Statistics dialog box 6. To clear the tape LUN statistics, click Clear. 7. When prompted with a confirmation dialog box, click Yes. 8. To update the tape LUN statistics, click Refresh.
18 Tape LUN statistics 2. Select a group, switch, or engine from the Encryption Center Devices table that contains the storage device to be configured, then select Group/Switch/Engine > Targets from the menu task bar, or right-click a group, switch, or engine and select Targets. NOTE You can also select a group, switch, or engine from the Encryption Center Devices table, then click the Targets icon. The Encryption Targets dialog box displays (Figure 248).
Re-balancing the encryption engine 18 Re-balancing the encryption engine If you are currently using encryption and running Fabric OS 6.3.x or earlier, you are hosting tape and disk target containers on different encryption switches or blades. Beginning with Fabric OS 6.4, disk and tape target containers can be hosted on the same switch or blade.
18 Master keys Master keys When an opaque key vault is used, a master key is used to encrypt the data encryption keys. The master key status indicates whether a master key is used and whether it has been backed up. Encryption is not allowed until the master key has been backed up. Only the active master key can be backed up, and multiple backups are recommended. You can back up or restore the master key to the key vault, to a file, or to a recovery card set. A recovery card set is set of smart cards.
Master keys 18 Master key actions NOTE Master keys belong to the group and are managed from Group Properties. Master key actions are as follows: • Backup master key, which is enabled any time a master key exists. You can back up the master key to a file, to a key vault, or to a smart card. You can back up the master key multiple times to any of these media in case you forget the passphrase you originally used to back up the master key, or if multiple administrators each needs a passphrase for recovery.
18 Master keys FIGURE 250 Backup Destination (to file) dialog box 4. Select File as the Backup Destination. 5. Enter a file name, or browse to the desired location. 6. Enter the passphrase, which is required for restoring the master key. The passphrase can be between eight and 40 characters, and any character is allowed. 7. Re-enter the passphrase for verification. 8. Click OK. Save the passphrase. This passphrase is required if you ever need to restore the master key from the file.
Master keys 18 FIGURE 251 Backup Destination (to key vault) dialog box 4. Select Key Vault as the Backup Destination. 5. Enter the passphrase, which is required for restoring the master key. The passphrase can be between eight and 40 characters, and any character is allowed. 6. Re-enter the passphrase for verification. 7. Click OK. A dialog box displays that shows the Key ID. The Key ID identifies the storage location in the key vault. 8. Store both the Key ID and the passphrase in a secure place.
18 Master keys The key is divided among the cards in the card set, up to 10. The quorum of cards required to restore the master key must be less than the total number of cards in the set, and no greater than five. For example, when the master key is backed up to a set of three cards, a quorum of any two cards can be used together to restore the master key. When the master key is backed up to a set of 10 cards, a quorum size of up to 5 cards can be configured for restoring the master key..
Master keys 7. 18 Run the additional cards through the reader that are needed for the set. As you read each card, the card ID displays in the Card Serial# field. Be sure to wait for the ID to appear. 8. Enter the mandatory last name and first name of the person to whom the card is assigned. 9. Enter a Card Password. 10. Re-enter the password for verification. 11. Record and store the password in a secure location. 12. Click Write Card.
18 Master keys 4. Choose the active or alternate master key for restoration, as appropriate. Refer to “Active master key” on page 540 and “Alternate master key” on page 540 if you need more information on active and alternate master keys. 5. Select File as the Restore From location. 6. Enter a file name, or browse to the desired location. 7. Enter the passphrase. The passphrase that was used to back up the master key must be used to restore the master key. 8. Click OK.
Master keys 18 6. Enter the key ID of the master key that was backed up to the key vault. 7. Enter the passphrase. The passphrase that was used to back up the master key must be used to restore the master key. 8. Click OK. Restoring a master key from a smart card set A card reader must be attached to the SAN Management application PC to complete this procedure. Use the following procedure to restore the master key from a set of smart cards. 1. Select Configure > Encryption from the menu task bar.
18 Master keys 6. Insert the recovery card containing a share of the master key that was backed up earlier, and wait for the card serial number to appear. 7. Enter the password that was used to create the card. After five unsuccessful attempts to enter the correct password, the card becomes locked and unusable. 8. Click Restore. The dialog box prompts you to insert the next card, if needed. 9. Repeat step 6 through step 8 until all cards in the set have been read. 10. Click OK.
Master keys 18 Viewing Master Key IDs When the master key has been backed up multiple times, you can use this feature to view the associated key IDs. To view master key IDs, follow these steps: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). 2. Select a group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click a group and select Security.
18 Zeroizing an encryption engine Zeroizing an encryption engine Zeroizing is the process of erasing all data encryption keys and other sensitive encryption information in an encryption engine. You can zeroize an encryption engine manually to protect encryption keys. No data is lost because the data encryption keys for the encryption targets are stored in the key vault. Zeroizing has the following effects: • All copies of data encryption keys kept in the encryption switch or blade are erased.
Zeroizing an encryption engine 18 A confirmation dialog box describes consequences and actions required to recover. FIGURE 258 Warning message - zeroizing an engine 3. Click Yes to zeroize the encryption engine. • For an encryption blade, after the zeroize operation is successful, a message displays noting that the encryption blade will be powered off and powered on to make it operational again. Click OK to close the message.
18 Using the Encryption Targets dialog box Using the Encryption Targets dialog box The Encryption Targets dialog box enables you to send outbound data that you want to store as ciphertext to an encryption device. The encryption target acts as a virtual target when receiving data from a host, and as a virtual initiator when writing the encrypted data to storage. To access the Encryption Targets dialog box, complete the following steps. 1. Select Configure > Encryption from the menu task bar.
Using the Encryption Targets dialog box 18 NOTE If the encryption group is busy when you click Commit, you are given the option to either force the commit, or abort the changes. Click Commit to re-create the redirection zone.
18 Disk device decommissioning Disk device decommissioning A disk device needs to be decommissioned when any of the following occurs: • The storage lease expires for an array, and devices must be returned or exchanged. • Storage is reprovisioned for movement between departments. • An array or device is removed from service. In all cases, all data on the disk media must be rendered inaccessible. Device decommissioning deletes all information that could be used to recover the data.
Disk device decommissioning 18 5. Click Yes to proceed with decommissioning. If a re-key operation is currently in progress on a selected LUN, a message is displayed that gives you a choice of doing a Forced Decommission, or to Cancel and try later after the re-key operation is complete. 6. To check on the progress of the decommissioning operation, click Refresh. When decommissioning is complete, the LUNs are removed from the Encryption Target LUNs table.
18 Disk device decommissioning FIGURE 261 Universal IDs dialog box 556 Brocade Network Advisor SAN User Manual 53-1002167-01
Re-keying all disk LUNs manually 18 Re-keying all disk LUNs manually The encryption management application allows you to perform a manual re-key operation on all encrypted primary disk LUNs and all non-replicated disk LUNs hosted on the encryption node that are in the read-write state. Manual re-keying of all LUNs might take an extended period of time. The management application allows manual re-key of no more than 10 LUNs concurrently.
18 Re-keying all disk LUNs manually FIGURE 263 Warning message - Re-key all 4. Click Yes. Re-keying operations begin on up to 10 LUNs. If more than 10 LUNs are configured on the switch, the remaining re-key operations are held in the pending state. 5. Open the Encryption Target Disk LUNs dialog box to see LUNs being re-keyed and LUNs pending. a. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). b.
Re-keying all disk LUNs manually 18 Viewing the progress of manual re-key operations To monitor the progress of manual re-key operations, complete these steps: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 1. Select an encryption group from the Encryption Center Devices table, then select Group > Re-Key Sessions from the menu task bar, or right-click an encryption group and select Re-Key Sessions. The Re-Key Sessions Status dialog box displays.
18 Viewing time left for auto re-key Viewing time left for auto re-key You can view the time remaining until auto re-key is no longer active for a disk LUN. The information is expressed as the difference between the next re-key date and the current date and time, and is measured in days, hours, and minutes. Although you cannot make changes directly to the table, you can modify the time left using CLI. For more information, see the administrator’s guide supporting your key vault management system.
Viewing and editing switch encryption properties 18 Viewing and editing switch encryption properties To view switch encryption properties, complete the following steps: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). The dialog box shows the status of all encryption-related hardware and functions at a glance. It is the single launching point for all encryption-related configuration. 2.
18 Viewing and editing switch encryption properties • Switch Status - the health status of the switch. Possible values are Healthy, Marginal, Down, Unknown, Unmonitored, and Unreachable. • Switch Membership Status - the alert or informational message description which details the health status of the switch. Possible values are Group Member, Leader-Member Comm, Error, Discovering, and Not a member. • Encryption Group - the name of the encryption group to which the switch belongs.
Viewing and editing switch encryption properties 18 • Backup Key Vault Connection Status - whether the backup key vault link is connected. Possible values are Unknown, Key Vault Not Configured, No Response, Failed authentication, and Connected. • Key Vault User Name – (TEMS only) launches dialog box to identify key vault user information. • Public Key Certificate Request text box - the switch’s KAC certificate, which must be installed on the primary and backup key vaults.
18 Viewing and editing switch encryption properties Importing a signed public key certificate from Properties To import a signed public key certificate, complete the following steps. 1. Click Import. The Import Signed Certificate dialog box displays (Figure 267). FIGURE 267 Import Signed Certificate dialog box 2. Enter or browse to the file containing the signed certificate. 3. Click OK. The file is imported onto the switch.
Viewing and editing group properties 18 Viewing and editing group properties To view encryption group properties, complete the following steps. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays (Figure 153). 2. Select a group from the Encryption Center Devices table, then select Group > Properties from the menu task bar, or right-click a group and select Properties.
18 Viewing and editing group properties General tab The General tab (Figure 269) is viewed from the Encryption Group Properties dialog box. To access the General tab, select a group from the Encryption Center Devices table, then select Group > Properties from the menu task bar, or right-click a group and select Properties. NOTE You can also select a group from the Encryption Center Devices table, then click the Properties icon.
Viewing and editing group properties 18 • Backup Key Vault Connection Status - the status of the connection to the backup key vault, if a backup is configured. • Primary key vault certificate - the details of the primary vault certificate; for example, version and signature information. • Backup key vault certificate - the details of the backup vault certificate; for example, version and signature information.
18 Viewing and editing group properties • OK - the member switch is responding to the group leader switch. • Not Available - the group leader is not a managed switch, so connection statuses are not being collected from the group leader. Members tab Remove button You can click the Remove button to remove a selected switch or group from the encryption group table. • You cannot remove the group leader unless it is the only switch in the group.
Viewing and editing group properties 18 FIGURE 271 Removal of switch warning A warning message displays when you attempt to remove an encryption group (Figure 272). Click Yes to proceed. FIGURE 272 Removal of an encryption group warning Security tab The Security tab displays the status of the master key for the encryption group and whether smart cards are required. From here, you register smart cards for use.
18 Viewing and editing group properties The Security tab (Figure 273) is viewed from the Encryption Group Properties dialog box. To access the Security tab, select a group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click a group and select Security. The Properties dialog box displays with the Security tab selected. NOTE You can also select a group from the Encryption Center Devices table, then click the Properties icon.
Viewing and editing group properties 18 HA Clusters tab The HA Clusters tab allows you to create and delete HA clusters, add encryption engines to and remove encryption engines from HA clusters, and failback an engine. The HA Clusters tab (Figure 274) is viewed from the Encryption Group Properties dialog box. To access the HA Clusters tab, select a group from the Encryption Center Devices table, then select Group > HA Clusters from the menu task bar, or right-click a group and select HA Clusters.
18 Viewing and editing group properties NOTE The Link Keys tab appears only if the key vault type is NetApp LKM. The Link Keys tab (Figure 275) is viewed from the Encryption Group Properties dialog box. To access the Link Keys tab, select an LKM group from the Encryption Center Devices table, then select Group > Link Keys from the menu task bar, or right-click an LKM group and select Link Keys. The Properties dialog box displays with the Link Keys tab selected.
Viewing and editing group properties 18 • To add a tape pool, click Add, then complete the Add Tape Pool dialog box. • To remove a tape pool, simply select one or more tape pools listed in the table, then click Remove. • To modify a tape pool, you must remove the entry, then add a new tape pool. The Tape Pools tab (Figure 276) is viewed from the Encryption Group Properties dialog box.
18 Viewing and editing group properties All encryption engines in the encryption group share the tape pool definitions. Tapes can be encrypted by an encryption engine where the container for the tape target LUN is hosted. The tape media is mounted on the tape target LUN. Tape pool definitions are not needed to read a tape. Tape pool definitions are only used when writing to tape. Adding tape pools A tape pool can be identified by either a name or a number, but not both.
Viewing and editing group properties 18 4. Select the Encryption Mode. Options include Clear Text, DF-Compatible Encryption, and Native Encryption. • DF-Compatible Encryption is valid only when LKM is the key vault. • The Key Lifespan (days) field is editable only if the tape pool is encrypted. • If Clear Text is selected as the encryption mode, the key lifespan is disabled. NOTE You cannot change the encryption mode after the tape pool I/O begins.
18 Viewing and editing group properties FIGURE 279 Encryption Group Properties Dialog Box - Engine Operations Tab NOTE You cannot replace an encryption engine if it is part of an HA Cluster. For information about HA Clusters, refer to “HA Clusters tab” on page 571.
Encryption-related acronyms in log messages 18 Encryption-related acronyms in log messages Fabric OS log messages related to encryption components and features may have acronyms embedded that require interpretation. Table 35 lists some of those acronyms.
18 578 Encryption-related acronyms in log messages Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 19 Zoning In this chapter • Zoning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Zone database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Zoning configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • LSAN zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Traffic isolation zoning . .
19 Zoning overview • QoS zones Assign high or low priority to designated traffic flows. Quality of Service (QoS) zones are normal zones with additional QoS attributes that you select when you create the zone. • Traffic Isolation zones (TI zones) Isolate inter-switch traffic to a specific, dedicated path through the fabric. See “Traffic isolation zoning” on page 606 for more information.
Zoning overview 19 • You want to analyze the impact of changes to storage access before applying the changes. For example, if you deploy a new server and want to ensure that the zoning changes result in only the new server gaining access to specific storage devices and nothing else. See “Comparing zone databases” on page 612. Accessing zoning Most of the zoning tasks are performed from the Zoning dialog box.
19 Zoning overview Administrator zoning privileges NOTE This section applies to the Enterprise and Professional Plus editions only. You can set read-only or read/write access for the following zoning components: • • • • • LSAN Zoning Zoning Activation (and deactivation) Zoning Offline Zoning Online Zoning Set Edit Limits When read/write privileges are defined for all components, an administrator can perform all zoning-related operations provided by dialog boxes and shortcut menus.
Zone database size 19 Note the following items about setting zoning privileges: • If no privilege level is set for any of the components, zoning is disabled at the Management application main menu and the Zoning dialog box cannot be opened. • If a privilege level is set for Activation without levels being set for the Offline, Online, or LSAN Zoning, the Zoning dialog box cannot be opened.
19 Zoning configuration 5. Create the zones. For specific instructions, refer to “Creating a new zone” on page 584. 6. Add members to each zone. For specific instructions, refer to “Adding members to a zone” on page 586 and “Creating a new member in an LSAN zone” on page 605. 7. Create a zone configuration. For specific instructions, refer to “Creating a zone configuration” on page 592. 8. Activate the zone configuration. For specific instructions, refer to “Activating a zone configuration” on page 594.
Zoning configuration 7. 19 For offline zone databases only, complete the following steps to save the zone configuration into the switch from the offline zone database: a. Select Save to Switch from the Zone DB Operation list. b. Click Yes on the confirmation message. The selected zone database is saved to the fabric without enabling a specific zone configuration. 8. Click OK or Apply to save your changes.
19 Zoning configuration Adding members to a zone Use this procedure to add a member to a zone when the member is listed in the Potential Members list of the Zone DB tab. Enterprise and Professional Plus versions: For instructions to add a member to a zone when the member is not listed in the Potential Members list, refer to the procedure “Creating a new member in a zone” on page 587. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2.
Zoning configuration 19 9. Click OK or Apply to save your changes. A message displays informing you that any zones or zone configurations you have changed will be saved in the zone database, and warning you to make sure no other user is making changes to the same areas. Creating a new member in a zone Use this procedure to add a member to a zone when the member is not listed in the Potential Members list of the Zone DB tab.
19 Zoning configuration Customizing the zone member display The following procedure applies to the zone display in the standard Zoning dialog box and also to the LSAN Zoning dialog box. 1. Select Configure > Zoning > Fabric. For LSAN zoning, select Configure > Zoning > LSAN Zoning (Device sharing). The Zoning or LSAN Zoning dialog box displays, based on the Configure > Zoning menu selection. 2. Click the Zone DB tab if that tab is not automatically displayed. 3.
Zoning configuration 19 6. Make sure the appropriate fabric is named on the Zoning Policies dialog box. 7. Perform one of the following actions based on the task you want to complete: • To enable the default zone, click Enable, and then click OK. • To disable the default zone, click Disable, and then click OK. The Zoning Policies dialog box closes and the Zone DB tab displays. 8. Click OK or Apply to save your changes.
19 Zoning configuration Creating a zone alias An alias is a logical group of port index numbers and WWNs. Specifying groups of ports or devices as an alias makes zone configuration easier, by enabling you to configure zones using an alias rather than inputting a long string of individual members. You can specify members of an alias using the following methods: • Identifying members by switch domain and port index number pair (for example, 2, 20). • Identifying members by device node and device port WWNs.
Zoning configuration 19 6. Add members to the alias by completing the following steps. a. Select an option from the Type list to choose how to display the objects in the Potential Members list. b. Show all discovered fabrics in the Potential Members list by right-clicking in the Potential Members list and selecting Expand All. This right-click option is not available if you selected WWN-Fabric Assignedin the Type list. 7. c.
19 Zoning configuration 4. Click Export. The Export Alias dialog box displays. 5. Browse to the location to which you want to export the zone alias data. 6. Enter a name for the export file in the File Name field. 7. Click Export Alias. 8. Click OK or Apply on the Zoning dialog box to save your changes. Renaming a zone alias 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Click the Zone DB tab if that tab is not automatically displayed. 3. Select Alias from the Type list. 4.
Zoning configuration 7. 19 Add zones to the zone configuration. For step-by-step instructions, refer to “Adding zones to a zone configuration” on page 593. 8. Click OK or Apply to save your changes. A message displays informing you that any zones or zone configurations you have changed will be saved in the zone database, and warning you to make sure no other user is making changes to the same areas. Viewing zone configuration properties 1. Select Configure > Zoning > Fabric.
19 Zoning configuration 5. Select one or more zones to add to the zone configurations in the Zones list. (Press SHIFT or CTRL and click each zone name to select more than one zone.) 6. Click the right arrow between the Zones list and Zone Configurations list to add the zones to the zone configurations. 7. Click OK or Apply to save your changes.
Zoning configuration 19 • The selected fabric is no longer discovered. • In McDATA Open Mode (InteropMode 3), the seed switch is a Fabric OS switch and either no EOS switch is in the fabric or none of the EOS switches are manageable. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Click the Zone DB tab if that tab is not automatically displayed. 3. Select an FC fabric from the Zoning Scope list.
19 Zoning configuration 7. Click OK to activate the zone configuration. If you are activating a zone configuration from the offline zone database, a message might display informing you of name conflicts between items in the offline zone database and the existing online zone database. Click Yes to overwrite the items in the online zone database, or No to cancel the activation.
Zoning configuration 19 6. Click OK or Apply to save your changes. A message displays informing you that any zones or zone configurations you have changed will be saved in the zone database, and warning you to make sure no other user is making changes to the same areas. Creating an offline zone database Offline zone databases are supported only in Enterprise and Professional Plus versions. Use this procedure to create a zone database and save it offline. 1. Select Configure > Zoning > Fabric.
19 Zoning configuration Refreshing a zone database 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Click the Zone DB tab if that tab is not automatically displayed. 3. Select a zone database from the Zone DB list. 4. Select Refresh from the Zone DB Operation list. A message displays informing you that refresh will overwrite the selected database. Click Yes to continue. 5. Click OK.
Zoning configuration 19 FIGURE 280 Compare/Merge Zone DBs dialog box 3. Select a database from the Reference Zone DB field. 4. Select a database from the Editable Zone DB field. The Reference Zone DB and Editable Zone DB areas display all available element types (zone configurations, zones, and aliases) for the two selected zone databases. In the Editable zone DB area, each element type and element display with an icon indicator (Table 37) to show the differences between the two databases. 5.
19 Zoning configuration 7. Select the Differences check box to display only the differences between the selected databases. 8. Select the Sync Scroll Enable check box to synchronize scrolling between the selected databases. 9. Merge zone configurations by completing the followings steps. a. Select one or more zone configuration nodes from the Reference Zone DB area. b. Select an element in the Editable Zone DB area. c. Click Merge. 10. Merge zones by completing the followings steps. a.
Zoning configuration 19 5. Click OK to save your work and close the Zoning dialog box. Exporting an offline zone database NOTE You cannot export an online zone database. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Select an offline zone database from the Zone DB list. 3. Select Export from the Zone DB Operation list. The Export Zone DB dialog box displays. 4. Browse to the location where you want to export the zone database file (.xml format). 5. Click Export Zone DB. 6.
19 LSAN zoning 4. Click OK to save your work and close the Zoning dialog box. LSAN zoning LSAN zoning is available only for backbone fabrics and any directly connected edge fabrics. A backbone fabric is a fabric that contains an FC router. All discovered backbone fabrics have the prefix LSAN_ in their fabric name, which is listed in the Zoning Scope list. NOTE LSAN zoning is supported only in Enterprise and Professional Plus editions.
LSAN zoning 19 10. Click OK to continue. All LSAN zones are activated on the selected fabrics and saved to the Zone DB. 11. Click OK to close the dialog box. Creating a new LSAN zone 1. Select a backbone fabric from the Connectivity Map or Product List. 2. Select Configure > Zoning > LSAN Zoning (Device Sharing). The Zoning dialog box displays. 3. Click the Zone DB tab if that tab is not automatically displayed. 4. Click New Zone. The prefix LSAN_ is automatically added in the text field. 5.
19 LSAN zoning Adding members to the LSAN zone Use this procedure to add a member to an LSAN zone when the member is listed in the Potential Members list of the Zone DB tab. 1. Select a backbone fabric from the Connectivity Map or Product List. 2. Select Configure > Zoning > LSAN Zoning (Device Sharing). The Zone DB tab of the Zoning dialog box displays. 3. If you want to show all discovered fabrics in the Potential Members list, right-click anywhere in the table and select Display All. 4.
LSAN zoning 19 Creating a new member in an LSAN zone Use this procedure to add a member to an LSAN zone when the member is not listed in the Potential Members list of the Zone DB tab. For instructions to add a member to a zone when the member is listed in the Potential Members list, refer to the procedure “Adding members to the LSAN zone” on page 604. 1. Select a backbone fabric from the Connectivity Map or Product List. 2. Select Configure > Zoning > LSAN Zoning (Device Sharing).
19 Traffic isolation zoning 11. Click OK to close the dialog box. Activating LSAN zones 1. Select a backbone fabric from the Connectivity Map or Product List. 2. Select Configure > Zoning > LSAN Zoning (Device Sharing). The Zone DB tab of the Zoning dialog box displays. 3. Click Activate. The Activate LSAN Zones dialog box displays. 4. Review the information in this dialog box. 5. Click OK to commit the LSAN zones and activate them in the selected fabrics.
Traffic isolation zoning 19 Enhanced TI zones In Fabric OS 6.4.0 or higher, ports can be in multiple TI zones. Zones with overlapping port members are called enhanced TI zones (ETIZ).
19 Traffic isolation zoning Configuring traffic isolation zoning The following procedure provides an overview of the steps you must perform to configure traffic isolation zoning. Note that for any zoning-related procedure, changes to a zone database are not saved until you click OK or Apply on the Zoning dialog box. If you click Cancel or the close button (X), no changes are saved. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2.
Traffic isolation zoning 19 6. Enter a name for the zone. For zone name requirements and limitations, refer to “Zoning naming conventions” on page 581. 7. Press Enter. Depending on the characters included in the name you enter, a message may display informing you the name contains characters that are not accepted by some switch vendors, and asking whether you want to proceed. Click Yes to continue, or No to cancel the zone creation. 8. Click OK or Apply to save your changes.
19 Traffic isolation zoning 8. Click the right arrow between the Potential Members list and Zones list to add the selected ports to the zone. A message may display informing you that one or some of the selected potential members cannot be zoned. Click OK to close the message box. Reconsider your selections and make corrections as appropriate. 9. Click OK or Apply to save your changes.
Traffic isolation zoning 19 3. Select an FC fabric from the Zoning Scope list. This identifies the target entity for all subsequent zoning actions and displays the zoning database for the selected entity. 4. Right-click the traffic isolation zone you want to disable in the Zones list and clear the Configured Enabled check box. 5. Click OK or Apply to save your changes.
19 Zoning administration • Ensure that there are multiple paths between switches. Disabling failover locks the specified route so that only TI zone traffic can use it. ATTENTION If failover is disabled, use care when planning your TI zones so that non-TI zone devices are not isolated. If disabled failover is not used correctly, it can cause major fabric disruptions that are difficult to resolve.
Zoning administration 19 To compare two zone databases, complete the following steps. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Select Compare from the Zone DB Operation list. The Compare/Merge Zone DBs dialog box displays, as shown in Figure 281.
19 Zoning administration FIGURE 281 Compare/Merge Zone DBs dialog box 3. Select a database from the Reference Zone DB field. 4. Select a database from the Editable Zone DB field. The Reference Zone DB and Editable Zone DB areas display all available element types (zone configurations, zones, and aliases) for the two selected zone databases. In the Editable zone DB area, each element type and element display with an icon indicator (Table 37) to show the differences between the two databases. 5.
Zoning administration 7. 19 Select the Differences check box to display only the differences between the selected databases. 8. Select the Sync Scroll Enable check box to synchronize scrolling between the selected databases. 9. Click Previous or Next to navigate line-by-line in the Editable Zone DB area. 10. Click Close. To merge two zone databases, refer to “Merging two zone databases” on page 598.
19 Zoning administration 3. Enter the maximum number of zone database changes that can be made for that fabric before a zone configuration is activated. To set a limit, enter a positive integer. To allow unlimited changes, enter 0. 4. Repeat step 2 and step 3 for each fabric on which you want to set limits. 5. To set a limit for new, undiscovered fabrics, enter a value in the Default Change Count for New Fabrics field. The default value is 0 (Unlimited). 6.
Zoning administration 19 Deleting a zone alias 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Click the Zone DB tab if that tab is not automatically displayed. 3. Select Alias from the Type list. 4. Right-click the zone alias you want to delete and select Delete. 5. Click Yes on the confirmation message. To selected zone alias is deleted from the Alias list. 6. Click OK or Apply on the Zoning dialog box to save your changes. Deleting a zone configuration 1.
19 Zoning administration Deleting an offline zone database For pure EOS fabrics in McDATA Fabric Mode (InteropMode 2) or McDATA Open Mode (InteropMode 3) and for mixed Fabric OS and M-EOS fabrics in McDATA Open Mode, you cannot delete the last available offline zone database, because only offline zoning is supported for these fabrics. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Select an FC fabric from the Zoning Scope list.
Zoning administration 19 Removing all user names from a zone database Use this procedure to remove all user names from the selected offline zone database. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Select an FC fabric from the Zoning Scope list. This identifies the target entity for all subsequent zoning actions and displays the zoning databases for the selected entity. 3.
19 Zoning administration 6. Click OK or Apply to save your changes. A message displays informing you that any zones or zone configurations you have changed will be saved in the zone database, and warning you to make sure no other user is making changes to the same areas. Duplicating a zone alias 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Click the Zone DB tab if that tab is not automatically displayed. 3. Select Alias from the Type list. 4.
Zoning administration 19 5. (Optional) Type a new name for the zone configuration. If you key in a new name, press Enter to save the name. Depending on the characters included in the name you enter, a message may display informing you the name contains characters that are not accepted by some switch vendors, and asking whether you want to proceed. Click Yes to continue, or No to cancel the renaming.
19 Zoning administration 4. Select the zone member in the Zones list that you want to find in the Potential Members list. Press SHIFT or CTRL and click each zone to select more than one zone. 5. Click Find < between the Potential Members list and the Zones list. • If the member is found, it is highlighted in the Potential Members list. • If the member is not found, a message displays informing you of this. Click OK to close the message box.
Zoning administration 19 5. Click Find < between the Zones list and the Zone Configurations list. • If the zone is found, it is highlighted in the Zones list. • If the zone is not found, a message displays informing you of this. Click OK to close the message box. Listing zone members Use this procedure to identify the zone in the active zone configuration of the fabric to which an individual port belongs and the members of that zone. If the seed switch is running Fabric OS 6.3.
19 Zoning administration Removing a member from a zone Use the following procedure to remove one or more members from a zone or zones. Note that the member is not deleted; it is only removed from the zone. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Click the Zone DB tab if that tab is not automatically displayed. 3. Select an FC fabric from the Zoning Scope list.
Zoning administration 19 5. Perform one of the following actions: • Right-click the name of the zone you want to remove in the Zone Configurations list and select Remove. • To remove multiple zones, select the zones to be removed from the zone configuration, and click the left arrow between the Zones list and the Zone Configurations list. When successful, the zone is removed from the Zone Configurations list. 6. Click OK or Apply to save your changes.
19 Zoning administration Renaming a zone 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Click the Zone DB tab if that tab is not automatically displayed. 3. Select an FC fabric from the Zoning Scope list. This identifies the target entity for all subsequent zoning actions and displays the zoning database for the selected entity. 4. Right-click the name of the zone you want to change in the Zones list and select Rename. 5. Type the new name for the zone.
Zoning administration 7. 19 Click OK or Apply to save your changes. A message displays informing you that any zones or zone configurations you have changed will be saved in the zone database, and warning you to make sure no other user is making changes to the same areas. Replacing zone members A zone member can be replaced in a specific, selected zone, or, if it is the member of more than one zone, it can be replaced in all the zones to which it belongs. 1. Select Configure > Zoning > Fabric.
19 Zoning administration Replacing an offline device by WWN The Management application enables you to replace an offline device by WWN from all zones and zone aliases in the selected zone DB. 1. Select Configure > Zoning > Fabric. The Zoning dialog box displays. 2. Select an FC fabric from the Zoning Scope list. This identifies the target entity for all subsequent zoning actions and displays the zoning database for the selected entity. 3. Select Offline Utility from the Zone DB Operation list.
Zoning administration 19 5. Select Name (default is WWN) in the corresponding Replace Using list. 6. Select the name of the offline device in the corresponding Replace Using list. If the selected name has multiple device or device port WWNs assigned (names are set to non-unique in Management application), the Device or Device Port WWN of Non-unique Name dialog box displays. The WWN list includes all device and device port WWNs assigned to the selected name. 7.
19 630 Zoning administration Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 20 Fibre Channel over IP In this chapter • FCIP services licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • IP network considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP platforms and supported features. . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP trunking . . . . . . . . . . . .
20 FCIP services licensing FCIP services licensing Most of the FCIP extension services described in this chapter require the High Performance Extension over FCIP/FC license. FICON emulation features require additional licenses. The following features and licensing apply to the 8 Gbps Extension platforms. • FCIP Adaptive Rate Limiting requires the FTR_AE (Advanced Extension) license. • FCIP trunking requires FTR_AE license.
FCIP platforms and supported features 20 FCIP platforms and supported features The following Fabric OS platforms that support FCIP: • The 8 Gbps extension switch. • The 8 Gbps Extension blade (384-port Backbone Chassis, 192-port Backbone Chassis). • The 4 Gbps Extension blade (384-port Backbone Chassis, 192-port Backbone Chassis, Director Chassis). There are differences in platform capabilities. For example, the 4 Gbps Extension Blade cannot support FCIP trunking or Adaptive Rate Limiting.
20 FCIP trunking The way FCIP tunnels and virtual ports map to the physical GbE ports depends on the switch or blade model. The 8 Gbps Extension Switch and 8 Gbps Extension Blade tunnels are not tied to a specific GbE port, and may be assigned to any virtual port within the allowed range. The 4 Gbps Extension Blade requires tunnels to be mapped to specific GbE ports and specific virtual ports. The mapping of GbE ports to tunnels and virtual port numbers is summarized in Table 39.
FCIP trunking 20 WAN IP Router 10.0.1.1 IP Router 10.0.0.1 FCIP Circuits 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.5 FCIP Circuits FCIP Tunnel 10.0.1.2 10.0.1.3 10.0.1.4 10.0.1.5 FIGURE 282 FCIP tunnel and FCIP circuits Design for redundancy and fault tolerance Multiple FCIP tunnels can be defined between pairs of 8 Gbps extension switches and 8 Gbps extension Blades, but doing so defeats the concept of a multiple circuit FCIP tunnel.
20 FCIP trunking • In a scenario where a FCIP tunnel has multiple circuits of different metrics the data will flow over the lower metric circuits unless a failover condition occurs, as described in “FCIP circuit failover capabilities”. • The maximum bandwidth for a single circuit is 1 Gbps. However, a maximum of 10 Gbps per circuit is allowed between 10 GbE ports on 8 Gbps Extension Blades when both blades are running Fabric OS 7.0 or greater.
Adaptive Rate Limiting 20 • Circuits 0 and 1 are created with a metric of 0. Circuit 0 is created with a maximum transmission rate of 1 Gbps, and Circuit 1 is created with a maximum transmission rate of 500 Mbps. Together, Circuits 0 and 1 provide an available bandwidth of 1.5 Gbps. • Circuits 2 and 3 are created with a metric of 1. Both are created with a maximum transmission rate of 1 Gbps, for a total of 2 Gbps. This bandwidth is held in reserve.
20 QoS SID/DID priorities over an FCIP trunk • F class - F class is the highest priority, and is assigned bandwidth as needed at the expense of lower priorities, if necessary. • QoS high - The QoS high priority gets at least 50% of the available bandwidth. • QoS medium - The QoS medium priority gets at least 30% of the available bandwidth. • QoS low - The QoS low priority gets at least 20% of the available bandwidth.
QoS SID/DID priorities over an FCIP trunk 20 Configuring QoS Priorities For 8 Gbps platforms only, you can change QoS priorities from the default settings using the following steps: 1. Select Configure > FCIP Tunnels. The FCIP Tunnels dialog box is displayed. All discovered fabrics with extension switches are listed under devices, and all existing FCIP tunnels are displayed. 2. Select the switch you want to configure under Products. 3.
20 IPsec and IKE implementation over FCIP IPsec and IKE implementation over FCIP Internet Protocol security (IPsec) uses cryptographic security to ensure private, secure communications over Internet Protocol networks. IPsec supports network-level data integrity, data confidentiality, data origin authentication, and replay protection.
IPsec and IKE implementation over FCIP 20 The following limitations apply to using IPsec: • • • • • • IPsec-specific statistics are not supported. To change the configuration of a secure tunnel, you must delete the tunnel and recreate it. There is no RAS message support for IPsec. IPsec can only be configured on IPv4 based tunnels. Secure Tunnels cannot be defined with VLAN Tagged connections. For the 4 Gbps Extension switch and Blade: - IPv6, NAT, and AH are not supported when IPsec is implemented.
20 QOS, DSCP, and VLANs QOS, DSCP, and VLANs Quality of Service (QoS) refers to policies for handling differences in data traffic. These policies are based on data characteristics and delivery requirements. For example, ordinary data traffic is tolerant of delays and dropped packets, but voice and video data are not. QoS policies provide a framework for accommodating these differences in data as it passes through a network. QoS for Fibre Channel traffic is provided through internal QoS priorities.
Open systems tape pipelining TABLE 40 20 Default Mapping of DSCP priorities to L2Cos Priorities (Continued) DSCP priority/bits L2CoS priority/bits Assigned to: 11 / 001011 3 / 011 Medium QoS 15 / 001111 3 / 011 Medium QoS 19 / 010011 3 / 011 Medium QoS 23 / 010111 3 / 011 Medium QoS 27 / 011011 0 / 000 Class 3 Multicast 31 / 011111 0 / 000 Broadcast/Multicast 35 / 100011 0 / 000 Low Qos 39 / 100111 0 / 000 Low Qos 43 / 101011 4 / 100 High QoS 47 / 101111 4 / 100 High QoS
20 FICON emulation features Consider the constraints described in Table 41 when configuring tunnels to use OSTP. TABLE 41 OSTP constraints FCIP Fastwrite Tape Acceleration Each GbE port supports up to 2048 simultaneous accelerated exchanges, which means a total of 2048 simultaneous exchanges combined for Fastwrite and Tape Acceleration.
FICON emulation features 20 FICON pacing mechanism may interpret delays as an indication of a large data transfer that could monopolize a shared resource, and react by throttling the I/O. IBM z/OS Global Mirror (z Gm) emulation provides local responses to remote hosts, eliminating distance related delays. A FICON XRC Emulation License is required to enable IBM z/OS Global Mirror (z Gm) Emulation.
20 FCIP configuration guidelines FCIP configuration guidelines FCIP configuration always involves two or more extension switches. The following should take place first before you configure a working FCIP connection from the Management application: • • • • • The WAN link should be provisioned and tested for integrity. Cabling within the data center should be completed. Equipment should be physically installed and powered on.
Configuring an FCIP tunnel 20 1. Select Configure > FCIP Tunnels. The FCIP Tunnels dialog box is displayed (Figure 287). All discovered fabrics with extension switches are listed under devices. FIGURE 287 FCIP Tunnels dialog box (fabric selected from Product tree) 2. Select the switch you want to configure under the Products tree. 3. Click the Add button, or right-click on the switch and select Add Tunnel. The Add FCIP Tunnel dialog is displayed (Figure 288).
20 Configuring an FCIP tunnel FIGURE 288 Add FCIP Tunnel dialog box 4. Click Select Switch Two under Switch Two Settings to display discovered extension switches, and select the switch that you want to connect to switch one. The switch name and fabric are displayed in the Switch and Fabric fields. 5. Enter a description of the tunnel in the Description field. NOTE You cannot assign a Tunnel ID until after at least one circuit is configured.
Adding an FCIP circuit 20 Adding an FCIP circuit When adding a new FCIP tunnel, you can add an FCIP circuit by selecting the Add button to the right of the Circuits properties table on the Add FCIP Tunnel dialog box (Figure 288 on page 648). For 8 Gbps platforms, you can add multiple FCIP circuits to the tunnel with this button. Add circuits to existing FCIP tunnels through the Edit FCIP Tunnel dialog box.
20 Adding an FCIP circuit 4. Select the IP Address for each port. This implementation of IPv6 uses unicast addresses for the interfaces with FCIP circuits. The unicast address must follow the RFC 4291 IPv6 standard and use the IANA assigned IPv6 Global Unicast address space (2000::/3). 5. For IPv4 addresses, specify the Subnet Mask. For IPv6 addresses, specify the prefix length. The default is created from the IP address and Subnet Mask.
Adding an FCIP circuit 20 10. If the physical connection exists, click Verify IP Connectivity to test the connection between switch one and switch two. The IP connectivity of the connection is tested with the ping utility. 11. Select Advanced Settings and continue if you want to do any of the following: • • • • Set the keep alive timeout to a value other than the default of 10 seconds. Set the minimum retransmission time to a value other than the default of 100 ms.
20 Configuring FCIP tunnel advanced settings Circuit configuration failure When a tunnel cannot be created because the process for adding a new circuit configuration fails, a FCIP Tunnel/Circuit Configurations dialog box displays. Using this dialog box, you can perform the following tasks: • • • • Roll back the current changes to the circuit configuration. Elect to not roll back current circuit configuration changes. Continue configuring additional circuits at this point.
Configuring FCIP tunnel advanced settings 20 FIGURE 291 Selecting a compression mode 3. Select the desired compression mode. A Standard option provides hardware compression and is available on all platforms. The 8 Gbps Extension Switch and the 8 Gbps Extension Blade provide three additional options for compression. The Moderate option enables a combination of hardware and software compression that provides more compression that hardware compression alone. This option supports up to 8 Gbps of FC traffic.
20 Configuring FCIP tunnel advanced settings 4. Click OK. Enabling Tperf test mode To enable Tperf test mode, do the following: 1. Select Advanced Settings on the Add FCIP Tunnel dialog box to display the Advanced Settings dialog box. 2. From the Transmission tab, select the TPerf Test Mode check box. 3. Select the Tape Acceleration check box. 4. Click OK. Tperf test mode should not be enabled during normal operations. It is only used for testing and troubleshooting tunnels.
Configuring FCIP tunnel advanced settings 20 FIGURE 292 Advanced Settings Security Tab for the 8 Gbps extension Switch and Blade 3. As an option, click Ensure connecting peer switches have known WWNs. This provides an added measure of security. 4. Enter the WWN for the remote switch. 5. Assign IKE and IPsec policies. For the 4 Gbps Extension Switch and Blade, you must choose from a drop-down list of policies. The 8 Gbps Extension Switch and Blade have predefined IKE and IPsec policies.
20 Configuring FCIP tunnel advanced settings 7. You can activate the Enable backward compatibility feature on 8 Gbps platforms if IPSec is enabled. This allows multiple 1 Gbps circuits to be created using 10 Gbps ports even if the switch at one end of the tunnel is using Fabric OS 7.0 and the switch at the other end is using Fabric OS earlier than v7.0.
Viewing FCIP connection properties 20 4. Select Populate Default Values at the top of the dialog box to set all operational parameters for FICON emulation to default values. This option is not be enabled if existing values are configured for the tunnel. 5. Select individual operational parameters for FICON emulation. - FICON Tape Write Max Pipe defines a maximum number of channel commands that may be outstanding at a given time during write pipelining.
20 Viewing General FCIP properties FIGURE 294 FCIP connection properties Viewing General FCIP properties Use the following steps to view general FCIP properties for a switch or blade. 1. Right click an extension blade or switch from the Fabric Tree structure or on the Connectivity Map, and select Properties. 2. Select the Properties tab.
Viewing General FCIP properties 20 FIGURE 295 General FCIP properties tab (Extension switch or blade) Use the following steps to view the properties of a chassis where an extension blade is installed. 1. Right click the chassis in the Switch group in Fabric Tree structure or on the Connectivity Map where the extension blade is installed, and select Properties. 2. Select the Properties tab.
20 Viewing FCIP FC port properties FIGURE 296 General FCIP properties tab (blade chassis) Viewing FCIP FC port properties Take the following steps to view FCIP FC port properties. 1. Right click an extension blade or switch from the Fabric Tree structure or on the Connectivity Map, and select Properties. 2. Select the Port tab. 3. Select the FC from the Type drop-down list (Figure 298).
Viewing FCIP Ethernet port properties 20 FIGURE 297 FC ports properties Viewing FCIP Ethernet port properties Take the following steps to view Ethernet port properties. 1. Right click an extension blade or switch from the Fabric Tree structure or on the Connectivity Map, and select Properties. 2. Select the Port tab. 3. Select the GigE from the Type drop-down list (Figure 298).
20 Editing FCIP tunnels FIGURE 298 GigE ports properties Editing FCIP tunnels NOTE You cannot edit an active tunnel; disable the tunnel before making changes. 1. From the FCIP Tunnels dialog box, select the tunnel you want to edit. 2. Select Edit. The Edit FCIP Tunnel dialog box displays (Figure 299).
Editing FCIP circuits 20 FIGURE 299 Edit FCIP Tunnel dialog box 3. Fields and parameters are as described in “Configuring an FCIP tunnel”. You can edit all editable fields and parameters. Editing FCIP circuits FCIP circuit settings may be edited from the Edit FCIP Circuit dialog box. The procedure for launching this dialog box for the 4 Gbps Extension Switch and Blade is different than the procedure for the 8 Gbps Extension Switch and the 8 Gbps Extension Blade.
20 Disabling FCIP tunnels The Edit FCIP Circuit dialog box displays. For the 8 Gbps Extension Switch and the 8 Gbps Extension Blade: 1. Select Edit. The Edit FCIP Tunnel dialog box displays. 2. Select a circuit that you want to edit from the Circuits properties table at the bottom of the dialog box and select Edit. The Edit FCIP Circuit dialog box displays (Figure 300). FIGURE 300 Edit FCIP Circuit dialog box 3. Fields and parameters are as described in “Adding an FCIP circuit”.
Enabling FCIP tunnels 20 Enabling FCIP tunnels 1. From the FCIP Tunnels dialog box, select the tunnel you want to enable. 2. Select Enable. 3. Click OK to enable the tunnel. Deleting FCIP tunnels 1. From the FCIP Tunnels dialog box, select the tunnel you want to delete. 2. Select the Delete. A confirmation dialog box displays, warning you of the consequences of deleting a tunnel. 3. Click OK to delete the tunnel. Disabling FCIP circuits 1.
20 Deleting FCIP Circuits 6. Click OK to enable the circuit(s). Deleting FCIP Circuits 1. From the FCIP Tunnels dialog box, select the tunnel that contains the circuit. 2. Select Edit. The Edit FCIP Tunnel dialog box displays. 3. Select the circuit that you want to delete from the Circuit properties table at the bottom of the dialog box. 4. Select Delete. 5. For tunnels with multiple circuits, select additional circuits from the table to delete and select Delete after each selection. 6.
Displaying tunnel properties from the FCIP tunnels dialog box 20 Displaying tunnel properties from the FCIP tunnels dialog box Tunnel properties can be displayed from the FCIP Tunnels dialog box. 1. Select a tunnel from the FCIP tunnels dialog box. 2. Select the Tunnel tab. Tunnel properties are displayed.
20 Displaying FCIP circuit properties from the FCIP tunnels dialog box Displaying FCIP circuit properties from the FCIP tunnels dialog box Tunnel properties can be displayed from the FCIP Tunnels dialog box using the following procedure. 1. Select a tunnel from the FCIP tunnels dialog box. 2. Select the Circuit tab. Circuit properties are displayed (Figure 302).
Displaying switch properties from the FCIP Tunnels dialog box 20 Displaying switch properties from the FCIP Tunnels dialog box Switch properties are displayed on the FCIP Tunnels dialog box when you select a switch (Figure 303).
20 Displaying fabric properties from the FCIP Tunnels dialog box Displaying fabric properties from the FCIP Tunnels dialog box Fabric properties are displayed on the FCIP Tunnels dialog box when you select a fabric. (Figure 304). FIGURE 304 Fabric properties on the FCIP Tunnels dialog box Troubleshooting FCIP Ethernet connections 1. Right-click a blade an extension blade or switch from the Fabric Tree structure or Connectivity Map, and select Properties. 2. Select the Port tab. 3.
Chapter 21 Fabric Binding In this chapter • Fabric binding overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Enabling fabric binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Disabling fabric binding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Adding switches to the fabric binding membership list . . . . . . . . . . . . . . .
21 Fabric binding overview Enabling fabric binding Fabric Binding is enabled through the Fabric Binding dialog box. After you have enabled Fabric Binding, use the Fabric Membership List/Add Detached Switch to add switches that you want to allow into the fabric. NOTE In a pure Fabric OS environment, Fabric Binding is only supported on Fabric OS 5.2 or later. In a mixed Fabric OS and M-EOS environment, Fabric Binding is only supported on Fabric OS 6.0 or later and M-EOS manageable switches and fabrics. 1.
Fabric binding overview 21 Disabling fabric binding Fabric Binding cannot be disabled while High Integrity Fabric is active if the switch is offline. This disables fabric binding and High Integrity Fabric on the switch, but not the rest of the fabric. Disabled switches segment from the fabric. Fabric Binding is disabled through the Fabric Binding dialog box. NOTE In a pure Fabric OS environment, Fabric Binding is only supported on Fabric OS 5.2 or later.
21 Fabric binding overview Adding detached devices to the fabric binding membership list To add a switch that does not have a physical connection and is not discovered to the fabric, complete the following steps. 1. Select Configure > Fabric Binding. The Fabric Binding dialog box displays. 2. Click Add Detached Switch. The Add Detached Switch dialog box displays. 3. Enter the domain ID of the switch in the Domain ID field. 4. Enter the nodeworld wide name (WWN) of the switch in the Node WWN field.
High integrity fabrics 21 High integrity fabrics The High Integrity Fabric (HIF) mode option automatically enables features and operating parameters that are necessary in multiswitch Enterprise Fabric environments. When HIF is enabled, each switch in the fabric automatically enforces a number of security-related features including Fabric Binding, Switch Binding, Insistent Domain IDs, and Domain Register for State Change Notifications (RSCNs).
21 High integrity fabrics High integrity fabric requirements The term high integrity fabric (HIF) refers to a set of strict, consistent, fabric-wide policies. There are several specific configuration requirements for high integrity fabrics: • Insistent domain ID (IDID) must be enabled in the participating switches. • Port-based routing must be used on the participating switches. • A policy must be set that limits connectivity to only the switches within the same fabric.
High integrity fabrics 21 2. Select the fabric on which you want to activate HIF from the Fabric Name list. The HIF status displays in the High Integrity Fabric field. 3. Click Activate. For Pure Fabric OS fabrics, HIF activates the Switch Connection Control (SCC) policy, sets Insistent Domain ID, and sets the Fabric Wide Consistency Policy (FWCP) for SCC in strict mode.
21 678 High integrity fabrics Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 22 Port Fencing In this chapter • About port fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Adding thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Removing thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22 Thresholds Thresholds You can create thresholds, which you can then assign to available objects in the tree. Port Fencing threshold types include the following: • • • • • • • • C3 Discard Frames (Fabric OS only) Invalid CRCs (Fabric OS only) Invalid Words (Fabric OS only) Link (M-EOS only) Link Reset (Fabric OS only) Protocol Errors (M-EOS and Fabric OS) Security (M-EOS) State Change (Fabric OS only) NOTE You can create up to 16 thresholds for M-EOS devices.
Thresholds • • • • • • • • • • 22 8 Gbps 16-port Embedded Switch 8 Gbps 24-port Embedded Switch 8 Gbps 8-FC port, 10 GbE 24-CEE port Switch 384-port Backbone Chassis 192-port Backbone Chassis 8 Gbps Encryption Switch Encryption Blade FC 8 GB 16-port Blade FC 8 GB 32-port Blade FC 8 GB 48-port Blade Invalid CRCs threshold NOTE This threshold is only available for Fabric OS devices. Use this type of threshold to block a port when an Invalid CRCs violation meets the Fabric OS switch threshold.
22 Thresholds Protocol error threshold Use Protocol Error thresholds to block a port when one of the following protocol errors meet the threshold: • ISL Bouncing–ISL has repeatedly become unavailable due to link down events. • ISL Segmentation (M-EOS only)–ISL has repeatedly become segmented. • ISL Protocol Mismatch–ISL has been repeatedly put into the Invalid Attachment state due to a protocol error. State Change threshold NOTE This threshold is only available for Fabric OS devices running 6.
Adding thresholds 22 Adding thresholds The Management application allows you to create Invalid CRCs, Invalid words, Link, Link Reset, Protocol Error, Security, and Sync Loss thresholds. Adding a C3 Discard Frames threshold NOTE This threshold is only available for Fabric OS devices running 6.3 or later. To add an C3 Discard Frames threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays (Figure 307).
22 Adding thresholds 4. Enter a name for the threshold in the Name field. 5. Select one of the following options: • Default—Uses device defaults. Go to step 8. • Custom—Uses your selections. Continue with step 6. 6. Enter the number of C3 discarded frames allowed for the threshold in the Threshold errors field. 7. Select the time period for the threshold from the errors per list.
Adding thresholds 22 Adding an Invalid CRCs threshold NOTE This threshold is only available for Fabric OS devices. To add an Invalid CRCs threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Select Invalid CRCs (Fabric OS only) from the Violation Type list. 3. Click Add. The Add Invalid CRCs Threshold dialog box displays. FIGURE 309 Add Invalid CRCs Threshold dialog box 4. Enter a name for the threshold in the Name field. 5.
22 Adding thresholds Adding an Invalid Words threshold NOTE This threshold is only available for Fabric OS devices. To add an Invalid Words threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Select Invalid Words (Fabric OS only) from the Violation Type list. 3. Click Add. The Add Invalid Words Threshold dialog box displays. FIGURE 310 Add Invalid Words Threshold dialog box 4. Enter a name for the threshold in the Name field.
Adding thresholds 22 Adding a Link threshold NOTE This threshold is only available for M-EOS devices. To add Link thresholds, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Select Link from the Violation Type list. 3. Click Add. The Add Link Threshold dialog box displays (Figure 311). FIGURE 311 Add Link Threshold dialog box 4. Enter a name for the threshold in the Name field. 5.
22 Adding thresholds Adding a Link Reset threshold NOTE This threshold is only available for Fabric OS devices. Use this threshold to block a port when a Link Reset violation meets the Fabric OS switch threshold. To add a Link Reset threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Select Link Reset (Fabric OS only) from the Violation Type list. 3. Click Add. The Add Link Reset Threshold dialog box displays.
Adding thresholds 22 8. Click OK to add the Link Resets threshold to the table and close the Add Link Reset Threshold dialog box. To assign this threshold to fabrics, switches, or switch ports, refer to “Assigning thresholds” on page 693. 9. Click OK on the Port Fencing dialog box. Adding a Protocol Error threshold To add a Protocol Error threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2.
22 Adding thresholds c. Select the time period for the threshold from the errors per list. The following choices are available: • None—the port is blocked as soon as the specified number of protocol errors allowed is met. • Second—the port is blocked as soon as the specified number of protocol errors allowed is reached within a second. • Minute—the port is blocked as soon as the specified number of protocol errors allowed is reached within a minute.
Adding thresholds 22 2. Select State Change (Fabric OS only) from the Violation Type list. 3. Click Add. The Add State Change Threshold dialog box displays. 4. Enter a name for the threshold in the Name field. 5. Select one of the following options: • Default—Uses device defaults. Go to step 8. • Custom—Uses your selections. Continue with step 6. 6. Enter the number of state changes allowed for the threshold in the Threshold errors field. 7.
22 Adding thresholds Adding a Security threshold NOTE This threshold is only available for M-EOS devices. To add a Security threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Select Security from the Violation Type list. 3. Click Add. The Add Security Threshold dialog box displays (Figure 309). FIGURE 315 Add Security Threshold dialog box 4. Enter a name for the threshold in the Name field. 5.
Adding thresholds 22 Assigning thresholds You can assign thresholds to any active object in the Ports table. You can only assign one threshold to an object at a time. If you assign a threshold to a switch, director, or fabric object, or to the All Fabrics object, the threshold is assigned to all subordinate objects (which do not have a directly assigned threshold) in the tree.
22 Adding thresholds Avoiding port fencing inheritance When you directly assign a threshold to an object, the threshold is inherited by all subordinate objects in the tree (unless they already have directly assigned thresholds). You cannot remove an inherited threshold from a subordinate object. However, the Management application allows you to effectively avoid inheritance for individual subordinate objects while maintaining inheritance for other subordinate objects.
Adding thresholds 22 FIGURE 316 Edit C3 Discard Frames Threshold dialog box 4. Change the name for the threshold in the Name field, if necessary. 5. Select one of the following options: • Default—Uses device defaults. Go to step 8. • Custom—Uses your selections. Continue with step 6. 6. Change the number of discarded frames allowed for the threshold in the Threshold field, if necessary. 7. Change the time period for the threshold from the errors per list, if necessary. 8.
22 Adding thresholds 4. Change the name for the threshold in the Name field, if necessary. 5. Select one of the following options: • Default—Uses device defaults. Go to step 8. • Custom—Uses your selections. Continue with step 6. 6. Change the number of port events allowed for the threshold in the Threshold field, if necessary. 7. Change the time period for the threshold from the errors per list, if necessary. 8. Click OK on the Edit Invalid CRCs Threshold dialog box.
Adding thresholds 22 8. Click OK on the Edit Invalid Words Threshold dialog box. If the threshold has already been assigned to ports, an “Are you sure you want to make the requested changes to this threshold on “X” ports?” message displays. Click OK to close. To assign this threshold to fabrics, switches, or switch ports, refer to “Assigning thresholds” on page 693. 9. Click OK on the Port Fencing dialog box. Editing a Link threshold NOTE This threshold is only available for M-EOS devices.
22 Adding thresholds Editing a Link Reset threshold NOTE This threshold is only available for Fabric OS devices. To edit a Link Reset threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Select Link Reset (Fabric OS only) from the Violation Type list. 3. Select the threshold you want to change and click Edit. The Edit Link Reset Threshold dialog box displays. FIGURE 320 Edit Link Reset Threshold dialog box 4.
Adding thresholds 22 Editing a Protocol Error threshold To edit a Protocol Error threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Select Protocol Error from the Violation Type list. 3. Select the threshold you want to change and click Edit. The Edit Protocol Error Threshold dialog box displays. FIGURE 321 Edit Protocol Error Threshold dialog box 4. Change the name for the threshold in the Name field, if necessary. 5.
22 Adding thresholds Editing a State Change threshold NOTE This threshold is only available for Fabric OS devices running 6.3 or later. To edit an State Change threshold, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays (Figure 307). FIGURE 322 Port Fencing dialog box 2. Select State Change (Fabric OS only) from the Violation Type list. 3. Select the threshold you want to change and click Edit.
Adding thresholds 22 6. Edit the number of state changes allowed for the threshold in the Threshold errors field, if necessary. 7. Change the time period for the threshold from the errors per list, if necessary. The following choices are available: • None—the port is blocked as soon as the specified number of invalid CRCs allowed is met. • Second—the port is blocked as soon as the specified number of invalid CRCs allowed is reached within a second.
22 Adding thresholds 5. Change the number of port events allowed for the threshold from the Threshold errors list, if necessary. 6. Change the time period for the threshold from the violations per list, if necessary. 7. Click OK on the Edit Security Threshold dialog box. If the threshold has already been assigned to ports, an “Are you sure you want to make the requested changes to this threshold on “X” ports?” message displays. Click OK to close.
Removing thresholds 22 Viewing all thresholds on a specific device To view all thresholds assigned to a specific switch, complete the following steps. 1. Select Monitor > Fabric Watch > Port Fencing. The Port Fencing dialog box displays. 2. Right-click anywhere in the Ports table and select Expand. 3. Right-click the device for which you want to view threshold information and select Switch Thresholds. The Switch Thresholds dialog box displays with a list of all thresholds assigned to the selected switch.
22 Removing thresholds A directly assigned icon ( ) displays next to each object with an assigned threshold which does not inherit a threshold from higher in the tree. NOTE If you remove a threshold from All Fabrics, it removes the threshold from individual Fabrics, switches, and switch ports in all Fabrics except for a Chassis group. You must remove repeat the procedure for the Chassis group. 5. Click OK on the Port Fencing dialog box.
Chapter 23 FICON Environments In this chapter • FICON Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring an Allow/Prohibit Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring an Allow/Prohibit Matrix manually . . . . . . . . . . . . . . . . . . . . . . • Saving or Copying Allow/Prohibit Matrix configurations to another device • Activating an Allow/Prohibit Matrix configuration . . . . . . . . . . . . . . . . . . .
23 Configuring an Allow/Prohibit Matrix FIGURE 326 Cascaded configuration, three domains, but only two in a path Configuring an Allow/Prohibit Matrix The Allow/Prohibit Matrix is a FICON port attribute that can be used to prohibit communication between specific ports. Prohibits are not recommended on E_Ports (inter switch links).
Configuring an Allow/Prohibit Matrix manually 23 FIGURE 327 Active Configuration 4. Prohibit a connection between two ports by clicking the intersection point between the ports. A prohibit icon ( ) displays at the intersection point. If you know the port addresses of the ports for which you want to prohibit or allow communication and do not want to search the matrix for the exact port intersection point, use the procedure “Configuring an Allow/Prohibit Matrix manually” on page 707. 5.
23 Configuring an Allow/Prohibit Matrix manually 3. Choose one of the following options: • Double-click a configuration file. • Select a configuration file and click the right arrow. A matrix displays. The switch ports are displayed on both the vertical axis and horizontal axis. A green circle icon ( ) indicates communication is allowed between the ports. 4. Click Manual Allow/Prohibit. The Manual Allow/Prohibit dialog box displays. FIGURE 328 Manual Allow/Prohibit dialog box 5.
Saving or Copying Allow/Prohibit Matrix configurations to another device 23 Saving or Copying Allow/Prohibit Matrix configurations to another device When copying or saving a configuration from a small switch (source switch with fewer ports; for example, 64 ports) to a larger switch (destination switch with a larger number of ports; for example, 256 ports) only the port address range of the smaller switch will be affected on the larger switch.
23 Saving or Copying Allow/Prohibit Matrix configurations to another device FIGURE 329 Save As/Duplicate dialog box 4. Enter a name for the configuration. 5. Enter a description for the configuration. 6. Select the check box for the switch to which you want to save the configuration in the Select Switch table. 7. Click OK.
Activating an Allow/Prohibit Matrix configuration 23 FIGURE 330 Save As/Duplicate dialog box 4. Enter a name for the configuration. 5. Enter a description for the configuration. 6. Select the check box for the device to which you want to save the configuration in the Select Switch table. 7. Click OK. A message displays stating that the outstanding port configuration is discarded when copying a configuration from the switch with more ports to a switch with fewer ports and vice versa.
23 Deleting an Allow/Prohibit Matrix configuration FIGURE 331 Activate Matrix Confirmation message 4. Select the Active=Saved check box to save the active configuration as the startup configuration (IPL). 5. Click OK to confirm. If you select the Active=Saved check box, the text [=Active] is appended to the IPL file in the Configure Allow/Prohibit Matrix dialog box. The Active=Saved check box and IPL filename represent the current state of the Active=Saved Mode (ASM) bit on the switch.
Changing the Allow/Prohibit Matrix display 23 Changing the Allow/Prohibit Matrix display You can modify the display using the Window Arrangement list above the matrix display or the Clear all port names option below the display. NOTE If you receive a 'FICON not supported on switch' error, refer to FICON troubleshooting for a list of possible causes.
23 Cascaded FICON fabric Cascaded FICON fabric NOTE You must have FICON Management privileges to configure a fabric for cascaded FICON. The Management application enables you to easily configure a fabric for cascaded FICON. Note that configuring a fabric for cascaded FICON may be disruptive to current I/O operations in the fabric, as it needs to disable and enable the switches in the fabric.
Cascaded FICON fabric 23 3. Select the FMS Mode check box to manage the fabric by a host-based management program using FICON CUP protocol. If you select FMS Mode, each switch is checked for a CUP license. Any switches that do not have a CUP license are listed, with a reminder that a CUP license is necessary to communicate with the fabric management server. 4. Select the DLS check box to enable dynamic load sharing (DLS) or Lossless DLS on all switches in the fabric.
23 Cascaded FICON fabric merge Cascaded FICON fabric merge The Management application provides a wizard to help you merge two fabrics for cascaded FICON. Note that merging two cascaded FICON fabrics may be disruptive to current I/O operations in both fabrics, as it needs to disable and enable the switches in both fabrics. The merge process will not make any configuration changes on the primary (production) fabric that are disruptive.
Cascaded FICON fabric merge 23 • (Optional) Configures long distance settings on selected ports of primary and secondary fabrics (requires Extended Fabric license). NOTE If the distance between the merged fabrics is 10 km or greater, you must configure the connection as a long distance connection.
23 Cascaded FICON fabric merge 4. Click Next. The Set up merge options screen displays. 5. Select FMS Mode to manage the fabric by a host-based management program using FICON CUP protocol. Note that you cannot enable FMS Mode on switches running Fabric OS 7.0 or later unless they have an active CUP license. 6. Select a secondary fabric where AD, ACL, and zone databases, if defined, will be cleared. 7.
Cascaded FICON fabric merge 23 11. Read and review the information on the Configure merge screen. If you understand and agree, click Next to confirm the information. A Summary screen displays. 12. Read the information, and click Finish to dismiss the wizard.
23 Port Groups a. Select the device you want to resolve the domain ID for in the Available Switches table and click the right arrow button. b. Select a new domain ID for the device from the Domain ID list. c. Repeat steps a and b for each device in the Available Switches table. d. Click OK on the Configure Domain IDs dialog box. 4. Repeat step 1 through step 3 until all resolvable tests pass. 5.
Port Groups 23 FIGURE 332 Port Groups dialog box 2. Click New. 3. Enter a name for the port group in the Name field. 4. Enter a description for the port group in the Description field. 5. Select one or more ports to add to the group in the Group Type - FC Ports table. A port group must have at least one port in the Membership List. All ports must be from switches in the same fabric. 6. Click the right arrow button. The selected ports display in the Membership List. 7. Click Update.
23 Port Groups Viewing port groups Port groups are user-specific, you can only view and manage port groups that you create. To view port groups, complete the following steps. 1. Select Configure > Port Groups. The Port Groups dialog box only displays port groups defined by you. If a fabric becomes un-monitored, any port groups associated with that fabric do not display in the Port Groups table. Once the fabric becomes monitored again, the associated port groups display in the Port Groups table.
Swapping blades 23 8. Click the left arrow button. The selected ports are removed from the Membership List. 9. Click Update. 10. Click OK. Deleting a port group To delete a port group, complete the following steps. 1. Select Configure > Port Groups. The Port Groups dialog box displays. 2. Select the port group you want to delete in the Port Groups table. 3. Click Remove. The selected ports are removed from the Port Groups table. 4. Click OK.
23 Swapping blades To swap blades, complete the following steps. 1. Select a chassis that contains at least two of the same type of blades. 2. Select Configure > Switch > Swap Blades. The Swap Blades dialog box displays. 3. Select the blade you want to replace from the first Swap Blades list. Once you select a blade, the second list automatically filters out the selected blade and any blade types that do not match the selected blade. 4.
Chapter VLAN Management 24 In this chapter • VLAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725 • Port VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 • STP or RSTP configuration on a port VLAN . . . . . . . . . . . . . . . . . . . . . . . . . 736 VLAN Manager VLAN Manager allows you to manage Virtual Local Area Networks (VLANs) on Brocade products.
24 VLAN Manager Configuration requirements for VLAN Manager Before you can manage VLANs with VLAN Manager, you must complete the following tasks: • Make sure that the discovery process has been run. Discovery captures configuration information from Brocade products and places that information in the Management application database. Refer to Chapter 3, “Discovery” for details on running discovery.
VLAN Manager 24 Displaying VLANs in the VLAN View The VLAN View tab displays all the VLANs discovered on the network and lists them by VLAN IDs. To view the VLANs in the VLAN View tab, complete the following steps. 1. Click the VLAN View tab in the VLAN Manager dialog box to display all the port VLANs. 2. Expand the folder under the VLAN View tab, then double-click a super-aggregated VLAN to display its port VLANs. VLANs are listed by their topologically distinct broadcast domains.
24 VLAN Manager Displaying VLANs by products The Product View tab of the VLAN Manager dialog box presents the products that have been discovered on the network and the VLANs that have been assigned to them. NOTE Only products assigned to Management application areas of responsibility (AORs) are listed under the VLANs in the Product View tab. To view VLANs, complete the following steps. 1. Click the Product View tab in the VLAN Manager dialog box. The VLAN Manager - Product View dialog box displays.
Port VLANs 24 Port VLANs VLAN Manager facilitates the creation, modification, and deletion of port VLANs on products that are known to the Management application. It also aids in the bulk deployment of these VLANs. For example, VLAN 3 may be configured on four products. If the VLAN definition for VLAN 3 is modified, the new definition can be deployed to all four products at one time.
24 Port VLANs 3. Enter a VLAN ID in the Configure VLANs field. You can enter more than one ID, separating individual IDs with a comma (for example, 10, 45, 79, 30). You can also enter ranges of VLAN IDs (for example, 41-51). 4. Click the Load Products button. Products that already have the entered VLAN IDs configured on them are automatically moved to the Selected Products panel. The Load Products button is disabled by default. 5.
Port VLANs 24 FIGURE 335 Select Classifier Groups dialog box Adding or modifying dual-mode ports You can configure an interface in a VLAN as a dual-mode port by assigning it as a tagged port to one VLAN and as an untagged port to another VLAN. You can add a dual-mode port to any VLAN except the default VLAN, VLAN 1. To add a dual-mode port to a VLAN, perform the following steps. 1.
24 Port VLANs Adding VLAN Properties The Add VLAN dialog box has two tabs: VLAN View and Product View. The VLAN properties vary for IOS and DCB products. When an IOS VLAN is selected, the Name, QoS, and Router Interface fields display. When a DCB VLAN or product is selected and moved to the Products/VLAN list, the Name and Admin Status fields and the FCoE check box display. All the fields displayed for DCB products are read-only. 1. On the Add VLAN dialog box, click the Properties tab.
Port VLANs 24 If you want to add a virtual routing interface to the VLAN, enter the virtual routing interface number in this parameter. You can add an IP address to the virtual routing interface once the VLAN is deployed. From the Product View tab, you can configure one virtual routing interface per VLAN, for each product. From the VLAN View tab, you can edit virtual routing interfaces on multiple products for a specific VLAN.
24 Port VLANs Deleting port VLANs from products Deleting a port VLAN removes all the interfaces on a product from that VLAN. A port VLAN can be deleted in both the VLAN and Product views. Deleting a port VLAN in the VLAN view 1. On the VLAN Manager dialog box, select the VLAN view. 2. Select the VLAN to be deleted. You can select multiple VLANs by holding down the Ctrl key and clicking the VLAN nodes. 3. Click Delete to launch the Deploy VLANs dialog box. 4.
Port VLANs 24 Deploying VLAN configurations The Deploy VLANs dialog box allows you to deploy a VLAN configuration to target products. FIGURE 337 STP/RSTP Configuration dialog box - Deployment Properties pane 1. Select a deployment option: • Click the Deploy now option if you want to deploy the VLAN definition. • Click the Save deployment only option if you want to save the VLAN definition without scheduling its deployment.
24 Spanning Tree Protocol Configuration 9. Click Start on the Deployment Status dialog box to save the changes to the selected products. 10. Click Close to close the Deployment Status dialog box. Spanning Tree Protocol Configuration Spanning Tree Protocol (STP) is a Layer 2 protocol that ensures a loop-free topology for any bridged local area network (LAN). STP allows a network design to include spare (redundant) links to provide automatic backup paths if an active link fails.
Spanning Tree Protocol Configuration 24 FIGURE 338 STP/RSTP Configuration dialog box 3. Select the target switch, VLAN, or port from the Target Context list. 4. Specify the following information: • Select STP or RSTP from the Spanning Tree list. • Select the Enable check box if you want to enable the protocol you selected. • Enter a value in the Priority field to identify the root bridge in a spanning tree (instance of STP). The bridge with the lowest value has the highest priority and is the root.
24 Spanning Tree Protocol Configuration Deploying STP configuration on a port VLAN The Deploy VLAN dialog box allows you to deploy an STP configuration to target products. The Selected Targets Summary list FIGURE 339 STP/RSTP Configuration dialog box - Deployment Properties pane 6. Select a deployment option: • Click the Deploy now option if you want to deploy the VLAN definition. • Click the Save only option if you want to save the VLAN definition without scheduling its deployment.
Spanning Tree Protocol Configuration 24 Configuring MSTP on a port VLAN You can configure MSTP attributes from the VLAN View tab or the Product View tab. 1. Perform one of the following tasks to select the VLAN on which MSTP will be configured: • On the VLAN View tab, expand the list of VLANs and select one or multiple VLANs on which MSTP will be configured.
24 Spanning Tree Protocol Configuration • Enter the interval after which the port will be enabled in the Re-enable Port Interval text box. The value range is 10 through 1000000 and the default is 300. • Click the Re-enable Port State check box to enable the time out mechanism for the port. • Select the Path Cost behavior option (Standard or Custom). • Select the transmit hold count for the bridge from the Tx Hold Count list. The value range is 1 through 10.
VLAN Routing 24 Deleting an MSTP instance 1. Select MSTP from the Spanning Tree list. The VLAN - STP Configuration dialog box displays the Available MSTP Instances list. 2. Select an MSTP instance from the Available MSTP Instances list, or enter the MSTP instance number. 3. Click the Delete button. 4. Click the right arrow button to move the MSTP instance to the Selected VLAN list. 5. Click OK. VLAN Routing VLAN restricts the broadcast domain to only its interface members.
24 VLAN Routing The Virtual Port - IP Configuration dialog box displays, as shown in Figure 341. If IP addresses have been configured for the switch virtual interface, they are listed in the Selected IP Addresses list in the dialog box. FIGURE 341 Virtual Port - IP Configuration dialog box 3.
VLAN Routing 24 4. Enter the following information: • Primary or Secondary options (DCB products only)—Indicates whether the IP address is the primary or secondary IP address of the VLAN. • Type—Select the type of IP address you want to assign to the VLAN. Choose CIDR or IP/Subnet. • Enter the IP address in the fields provided: If you chose the CIDR Subnet format, enter a subnet address in the subnet_address/subnet_mask_bits format (for example, 192.168.2.10/24).
24 744 VLAN Routing Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 25 Deployment Manager In this chapter • Introduction to the Deployment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . • Editing a deployment configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Duplicating a deployment configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . • Deleting a deployment configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Deploying a configuration . . . . . . . . . . . . . . . . . . . . . . . . .
25 Editing a deployment configuration Editing a deployment configuration 1. Select Configure > Deployment. The Deployment dialog box displays, as shown in Figure 343. FIGURE 343 Deployment dialog box 2. Select a deployment configuration in the Saved or Scheduled tab. 3. Click Edit. A dialog box specific to the type of deployment displays. This is the same dialog box that was used when the deployment was created. 4. Update the dialog box with the information you want to change.
Duplicating a deployment configuration 25 Duplicating a deployment configuration 1. Select Configure > Deployment. The Deployment dialog box displays. 2. Select a deployment configuration in the Saved or Scheduled tab. NOTE VLAN configurations cannot be duplicated. 3. Click Duplicate. A dialog box specific to the type of deployment displays. This is the same dialog box that was used when the original deployment was created. 4. Update the dialog box with any information you want to change.
25 Viewing deployment logs Viewing deployment logs 1. Select Configure > Deployment. The Deployment dialog box displays. 2. Click the Log tab. A list of deployment configurations that are executed and the status of each displays. Generating a deployment report 1. Select Configure > Deployment. The Deployment dialog box displays. 2. Select a deployment in the Saved, Scheduled, or Log tab. 3. Click Report. An HTML report displays.
Chapter 26 Troubleshooting In this chapter • FC troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Browser troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Client browser troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric tracking troubleshooting . . .
26 FC troubleshooting Tracing FC routes The Management application enables you to select a source port and a destination port and displays the detailed routing information from the source port or area on the local switch to the destination port or area on another switch. NOTE Trace route cannot be performed on offline devices. NOTE Trace route cannot be performed in a mixed (Fabric OS and M-EOS) fabric.
FC troubleshooting 26 4. Click the right arrow button. 5. Click OK. The Trace Route Summary dialog box displays. This dialog box includes the following information: • Trace Route Summary. This table shows a brief summary of the trace including the following: Port WWN Port name FC address Switch name (Fabric OS only) Whether ping was successful (Fabric OS only) (Fabric OS only) Round trip time (minimum, maximum, and average) (Fabric OS only) Whether the device ports are in active zones.
26 FC troubleshooting • Select the source and destination ports from a list by selecting the Select two device ports option and completing the following steps. a. Right-click a fabric in the Available Device Ports table and select Expand All. b. Select the ports (source and destination) for which you want to confirm device sharing from the Available Device Ports table. To add a detached device to troubleshoot device connectivity, refer to “Adding a detached device” on page 752. c.
FC troubleshooting 26 Confirming Fabric Device Sharing NOTE Fabric device sharing is only available with Trial or Licensed version. NOTE Fabric device sharing is only available on pure Fabric OS fabrics. To confirm that two or more fabrics have been configured to share devices, complete the following steps. 1. Select Configure > FC Troubleshooting > Fabric Device Sharing. The Fabric Device Sharing Diagnosis dialog box displays. 2.
26 FC troubleshooting 3. Click the right arrow button. 4. Click Start. The Management application performs the following operations to enable diagnostic mode on the selected ports: 1. Disable the source port. 2. Disable the destination port. 3. Enable the diagnostic mode on source E port. 4. Enable the diagnostic mode on destination E port. 5. Enable the source port. 6. Enable the destination port.
FC troubleshooting TABLE 43 26 Status Detail messages Operation/Test Possible message Disable the source or destination port Disabled the port slot_number/port_number of the switch switch_IP_address. Failed to disable the port slot_number/port_number of the switch switch_IP_address. Reason: CAL_error_message Enable the diagnostic mode on source or destination E ports Enabled diagnostic mode on port slot_number/port_number of the switch switch_IP_address.
26 FCIP troubleshooting FCIP troubleshooting NOTE FCIP troubleshooting is only available for Fabric OS devices. You can perform the following operations using FCIP troubleshooting: • Ping. Use to confirm that the configured FCIP tunnels are working correctly. • Trace Route. Use to view the route information from a source port on the local device to a destination port on another device and determine where connectivity is broken. • Performance. Select to view FCIP tunnel performance between two devices.
FCIP troubleshooting TABLE 44 26 FCIP IP Ping Response Details Field or Component Description Packet Lost percentage The number of packets lost expressed as a percentage of the packets sent. This will be 0%, 25%, 50%, 75% or 100% for 0, 1, 2, 3, or all 4 packets lost. Minimum Round Trip Time The shortest time, in milliseconds, of any response. If no response, the round trip times is 0. Maximum Round Trip Time The longest time, in milliseconds, of any response.
26 FCIP troubleshooting Tracing IP routes The Management application enables you to select an source and a target and displays the detailed routing information from the source port or area on the local switch to the destination port or area on another switch. Trace route cannot be performed on the offline devices or virtual devices. NOTE Trace route is only supported on Fabric OS devices running Fabric OS 5.2 or later. To trace routes, complete the following steps. 1.
FCIP troubleshooting 7. 26 Click Close on the IP Traceroute Result dialog box. 8. Click Cancel on the IP Traceroute dialog box. Viewing FCIP tunnel performance NOTE IP Performance is only supported on the 4 Gbps Router, Extension Switch and Encryption Blade running Fabric OS 5.2 or later. NOTE If you run IP Performance over a link also being used for production traffic, it will impact the production traffic performance. To view FCIP tunnel performance, complete the following steps. 1.
26 Application Configuration Wizard troubleshooting 7. Field/Component Description DELAY The average round trip time to send a packet of data and receive the acknowledgement. PMTU (Path Maximum Transmission Unit) The largest packet size that can be transmitted over the end-to- end path without fragmentation. This value is measured in bytes and includes the IP header and payload. IP Performance tries the configured Fabric OS Jumbo MTU value (anything over 15000, then 1500, then 1260.
Browser troubleshooting 26 Browser troubleshooting The following section states a possible issue and the recommended solution for browser errors. Problem Resolution The Cancel button does not work on the Report via E-mail dialog box when you use the Mozilla Firefox browser. Mozilla Firefox Browser does not support window close script. Click the browser Close button to cancel. NOTE: The Cancel button still displays on all Report via E-mail dialog boxes.
26 FICON troubleshooting FICON troubleshooting The following section states a possible issue and the possible cause for FICON errors. Problem Causes FICON not supported on switch error. FICON Unsupported Configurations: FICON is not supported on base switches. FICON is not supported on a logical switch which has an XISL configured. FICON is not supported if the PID format is 2. FICON is not supported if 10 bit address is enabled on 384-port Backbone Chassis for non-default switch.
Launch Client troubleshooting 26 Launch Client troubleshooting The following section states a possible issue and the recommended solution if you are unable to launch the remote client. Problem Resolution Remote client does not upgrade from versions prior to 11.0. The remote client does not automatically upgrade when you select the remote client shortcut of client versions earlier than 11.0. To clear the old client and launch the new remote client version, complete the following steps.
26 Launch Client troubleshooting Problem Resolution Unable to log into the Client (the application does not launch when you use a valid user name and password and exceptions are thrown in the client side). Use one the following procedures to configure the IP address in the host file. Windows operating systems 1 Log in using the 'Administrator' privilege. 2 Select Start > Run. 3 Type drivers in the Open field and press Enter. 4 Go to the ‘etc’ folder and open the ‘hosts’ file using a text editor.
Names troubleshooting 26 Names troubleshooting The following section states a possible issue and the recommended solution for names errors. Problem Resolution Duplicate name error. If you configured the Management application to only allow unique names and you try to use a name that already exists in the fabric.
26 Performance troubleshooting Performance troubleshooting The following section states a possible issue and the recommended solution for Performance errors. Problem Resolution An error message with the following text displays: Real Time statistics collection has failed. Please see master log for details. Make sure that the following prerequisites for Performance Monitoring Data collection are met.
Performance troubleshooting Problem Resolution An error message with the following text displays: Real Time statistics collection has failed. Please see master log for details. 2 Brocade Network Advisor SAN User Manual 53-1002167-01 26 To collect data, the SNMP credentials in the Management application and switch must match. SNMP v1 or v3: The community strings entered in the Address Properties dialog box SNMP tab must match the one entered in the switch.
26 Performance troubleshooting Problem Resolution An error message with the following text displays: Real Time statistics collection has failed. Please see master log for details. 3 To collect GigE port and FCIP statistics, you must enable the FCIP-MIB capability.
Performance troubleshooting 26 Problem Resolution An error message with the following text displays: Real Time statistics collection has failed. Please see master log for details. 5 To collect data on Virtual Fabric-enabled switches, the Fabric OS user must have access to all Virtual Fabrics. The SNMPv3 user name must be the same as the Fabric OS user name. If the SNMPv3 and Fabric OS user names do not match, data is not collected for the virtual switches with the non-default VF ID.
26 Port Fencing troubleshooting Port Fencing troubleshooting The following section states a possible issue and the recommended solution for Port Fencing errors. Problem Resolution In a pure M-EOS fabric, fabric level policy information (for example, Port Fencing Link threshold) is stored in database based on the principle switch WWN.
Server Management Console troubleshooting 26 Server Management Console troubleshooting The following section states a possible issue and the recommended solution for server management console errors. Problem Resolution Unable to launch the SMC on a Windows Vista,Windows 7 , or Windows 2008 R2 system The Windows Vista,Windows 7,or Windows 2008 R2 system enables the User Access Control (UAC) option by default. When the UAC option is enabled, the SMC cannot launch.
26 Supportsave troubleshooting Problem Resolution Unable to launch the SMC on a Windows Vista or Windows 7 system continued Disable using the Group Policy by completing the following steps. You can perform this procedure on you local machine using Local Group Policy editor or for many computers at the same time using the Active Directory-based Group Policy Object (GPO) editor. To disable using the Local Group Policy editor, complete the following steps.
View All list troubleshooting 26 View All list troubleshooting The following section states a possible issue and the recommended solution for View All list errors. Problem Resolution View All list does not display. The View All list does not display until you discover a fabric. To discover a fabric, refer to “Discovering fabrics” on page 49. View All list does not display and there are discovered fabrics.
26 774 Zoning troubleshooting Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 27 Performance Data In this chapter • SAN performance overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN real-time performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN Historical performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN End-to-end monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN Top Talker monitoring . . . . . . . . . . . . . . . . .
27 SAN performance overview • Provide aging scheme. The granularity varies depending on the configuration on the Server Management Console, Performance Data Aging tab.
SAN performance overview • • • • • • • • • • • • • • • • • • • • • Compression Ratio — available for FCIP tunnels only. • • • • Dropped Frames — available for Managed HBA ports and Managed CNA ports. 27 Latency — available for FCIP tunnels only. Link Retransmits — available for FCIP tunnels only. Timeout Retransmits — available for FCIP tunnels only. Fast Retransmits — available for FCIP tunnels only. Duplicate Ack Received — available for FCIP tunnels only.
27 SAN performance overview SAN Performance management requirements To collect performance data, make sure the following requirements have been met: • Make sure the snmp access control list for the device is empty or the Management application server IP is in the access control list.
SAN performance overview 27 Trap port: 162 Trap recipient Severity level: 4 Community 6: FibreChannel (ro) Trap recipient: 1001:0:0:0:0:0:0:172 Trap port: 162 Trap recipient Severity level: 4 - To set the SNMP v1 credentials on the device, use the snmpconfig --set snmpv1 command. Example of setting SNMP v1 HCLSwitch:admin> snmpconfig --set snmpv1 SNMP community and trap recipient configuration: Community (rw): [test] Trap Recipient's IP address : [172.26.1.183] Trap recipient Severity level : (0..
27 SAN performance overview Priv Protocol: noPriv - To set the SNMP v3 credentials on the device, use the snmpconfig --set snmpv3 command. FM_4100_21:admin> snmpconfig --set snmpv3 SNMPv3 user configuration(SNMP users not configured in Fabric OS user database will have physical AD and admin role as the default): User (rw): [snmpadmin1] admin Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..
SAN performance overview 27 4. Click the Manual option to view SNMP credentials. 5. Click the SNMP tab. 6. Select the v1 or v3 from the SNMP Version list. 7. Make sure SNMP credentials match those on the device. 8. Click OK on the AddFabric Discovery dialog box. 9. Click Close on the Discover Fabrics dialog box. - To set SNMP credentials in the Management application, refer to “Discovery” on page 47. • Make sure that the SNMP security level is set to the appropriate level for the switch.
27 SAN real-time performance data • To collect performance on a Virtual Fabric enabled device, use the userconfig --show command to make sure the Fabric OS user has access to all the Virtual Fabrics. Make sure that the SNMPv3 user name is same as the Fabric OS user name. Otherwise, the data is not collected for virtual switches with a non-default VF ID. By default the admin user has access to all Virtual Fabrics.
SAN real-time performance data 27 Generating a real-time performance graph You can monitor a device’s performance through a performance graph that displays transmit and receive data. The graphs can be sorted by the column headers. You can create multiple real-time performance graph instances. NOTE To make sure that statistic collection for a switch does not fail, you must configure SNMP credentials for the switch. For step-by-step instructions, refer to “Discovery” on page 47.
27 SAN real-time performance data 6. Click the right arrow to move the selected ports to the Selected table. 7. Click OK. The Real Time Performance Graphs dialog box displays. Filtering real-time performance data To filter real-time performance data from the Real Time Performance Graphs dialog box, complete the following steps. 1. Open the Real Time Performance Graphs dialog box. For step-by-step instructions, refer to “Generating a real-time performance graph” on page 783.
SAN real-time performance data 27 14. Select the Display tabular data only check box to only show text with no graphs or icons. The Source and Destination icons and the Graph column do not display 15. Click Apply. The selected graph automatically displays in the Real Time Performance Graphs dialog box. 16. Click the close button (X) to close the Real Time Performance Graphs dialog box. Exporting real-time performance data To export real-time performance data, complete the following steps. 1.
27 SAN Historical performance data SAN Historical performance data Performance should be enabled constantly to receive the necessary historical data required for a meaningful report. The following options and features are available for obtaining historical performance data: • Collect historical performance data from the entire SAN or from a selected . NOTE Virtual Fabric logical ISL ports are not included in performance collection. • Persist data on every polling cycle (5 minutes).
SAN Historical performance data 27 Enabling historical performance collection for selected fabrics To enable historical performance collection for selected fabrics, complete the following steps. 1. Select Monitor > Performance > Historical Data Collection > Enable Selected. The Historical Data Collection dialog box displays. FIGURE 345 Historical Data Collection dialog box 2. Select the fabrics for which you want to collect historical performance data in the Available table.
27 SAN Historical performance data Generating a historical performance graph To generate a historical performance graph for a device, complete the following steps. 1. Select the device for which you want to generate a performance graph. 2. Choose one of the following options: • Select Monitor > Performance > Historical Graph. OR • Right-click the device or fabric and select Performance > Historical Graph. The Historical Performance Graph dialog box displays.
SAN Historical performance data d. 27 Select the granularity at which you want to gather performance data from the Granularity list. The granularity varies depending on the configuration on the Server Management Console, Performance Data Aging tab.
27 SAN Historical performance data Filtering data by ports To filter data for a historical performance graph by ports, complete the following steps. 1. Select the type of ports from the Show list. FIGURE 347 Custom Port Selector dialog box 2. Right-click a device in the Available table and select Expand All. 3. Select the ports (press Ctrl or Shift and then click to select multiple ports) from which you want to gather performance data from the Available table and click the right arrow button.
SAN Historical performance data 27 Saving a historical performance graph configuration To save a historical performance graph configuration, complete the following steps. 1. Select the device for which you want to generate a performance graph. 2. Choose one of the following options: • Select Monitor > Performance > Historical Graph. OR • Right-click the device or fabric and select Performance > Historical Graph. The Historical Performance Graph dialog box displays. 3.
27 SAN Historical performance data Exporting historical performance data To export historical performance data, complete the following steps. 1. Generate a performance graph. To generate a performance graph, refer to “Generating a historical performance graph” on page 788. 2. Right-click anywhere in the graph table and select Export Table. The Save table to a tab delimited file dialog box displays. 3. Browse to the file location where you want to save the performance data. 4.
SAN End-to-end monitoring 27 SAN End-to-end monitoring NOTE End-to-end monitoring requires a Fabric OS device. NOTE End-to-end monitoring on an Access Gateway device requires Fabric OS 7.0 or later with an Advanced Performance Monitor license. Performance enables you to provision end-to-end monitors of selected target and initiator pairs. These monitors are persisted in the database and are enabled on one of the F_ports on the connected device (the Management application server determines the port).
27 SAN End-to-end monitoring FIGURE 349 Set End-to-End Monitors dialog box 2. Select the fabric for which you want to configure end-to-end monitoring from the Fabric list. 3. Select an initiator port from the Select an initiator port table. 4. Select a target port from the Select a target port table. 5. Click the right arrow to move the selected initiator and target ports to the Monitored Pairs table.
SAN End-to-end monitoring 27 Displaying end-to-end monitor pairs in a real-time graph To display an end-to-end monitor pair in a graph, complete the following steps. 1. Select Monitor > Performance > End-to-End Monitors. The Set End-to-End Monitor dialog box displays. 2. Select one or more end-to-end monitor pairs you want to view from the Monitored Pairs table. You can select up to 32 monitored pairs. 3. Click Real-Time Graph. The Real Time Performance Graphs dialog box displays.
27 SAN Top Talker monitoring Deleting an end-to-end monitor pair To delete an end-to-end monitor pair, complete the following steps. 1. Select Monitor > Performance > End-to-End Monitors. The Set End-to-End Monitor dialog box displays. 2. Select the end-to-end monitor pair you want to delete from the Monitored Pairs table. 3. Click Delete Monitor. 4. Click OK. SAN Top Talker monitoring NOTE Top Talkers requires the Advance Performance Monitoring (APM) license on the device.
SAN Top Talker monitoring 27 To configure a fabric mode Top Talker monitor, complete the following steps. 1. Select the device or fabric on which you want to monitor Top Talker data. NOTE On the 8 Gbps 8-FC port, 10 GbE 24-CEE port Switch, Top Talkers is only supported on the 8 Gbps FC Ports. 2. Select Monitor > Performance > Top Talkers. The Top talker Selector dialog box displays. FIGURE 350 Top talker Selector dialog box 3. Select Fabric to select a switch to monitor in the Top Talker Mode list.
27 SAN Top Talker monitoring • • • Source Switch/Port Destination • • DID Destination Port Destination Switch/Port 8. Click Destination to launch the Port Properties dialog box for the Destination port. 9. Click Source to to launch the Port Properties dialog box for the Source port. 10. Click the minimize button to hide this dialog box when it is not needed. Configuring an F_port mode Top Talker monitor NOTE An F_port mode Top Talker and an end-to-end monitor cannot be configured on the same F_port.
SAN Top Talker monitoring 27 9. Click Apply. The top 20 conversations display in the Current Top Talkers table. The Top Talkers Summary table displays all Top Talkers that occurred since the Top Talkers dialog box was opened (displays a maximum of 360). When the maximum is reached, the oldest Top Talker drops as a new one occurs.
27 Bottleneck detection Bottleneck detection A bottleneck is a port in the fabric where frames cannot get through as fast as they should. In other words, a bottleneck is a port where the offered load is greater than the achieved egress throughput. Bottlenecks can cause undesirable degradation in throughput on various links. When a bottleneck occurs at one place, other points in the fabric can experience bottlenecks as the traffic backs up.
Bottleneck detection 27 • Bottleneck detection is supported on 4 Gbps, 8 Gbps, and 16 Gbps platforms. • Bottleneck detection is supported in Access Gateway mode. • Bottleneck detection is supported whether Virtual Fabrics is enabled or disabled. In VF mode, bottleneck detection is supported on all fabrics, including the base fabric. How bottlenecks are reported Bottlenecks are reported through alerts in the Master Log. A bottleneck cleared alert is sent when the bottleneck is cleared.
27 Bottleneck detection If you add additional switches, including logical switches, to the fabric, bottleneck detection is not automatically applied, so be sure to enable bottleneck detection on those switches as well. NOTE It is recommended that you enable bottleneck detection on every switch in the fabric. Enabling bottleneck detection enables both latency and congestion detection.
Bottleneck detection 27 Configuring bottleneck alert parameters After you enable bottleneck detection, you can change the alert parameters on all eligible ports, switches, and fabrics. The alert parameters include whether alerts are sent and the threshold, time, and quiet time options.
27 Bottleneck detection Inheriting alert parameters from a switch When you enable bottleneck detection on a switch, all eligible ports on that switch inherit the same bottleneck parameters as the switch. You can then change the parameters for specific ports or exclude specific ports from bottleneck detection. Use the following procedure if you want to restore the switch bottleneck parameters to a port that has direct assigned settings. 1. Select Monitor > Performance > Bottlenecks.
Bottleneck detection 27 Displaying bottleneck statistics You can display a graph of bottleneck statistics for up to 32 ports at one time. You can display a graph showing the history of bottleneck conditions, for up to the last 150 minutes. 1. Select Monitor > Performance > Bottleneck Graph. The Bottleneck Graph Port Selector dialog box displays with bottlenecked ports shown in the Available list. 2. (Optional) Select All Ports from the Show list to display all ports in the Available list. 3.
27 Thresholds and event notification Disabling bottleneck detection Use this procedure to exclude specific ports from bottleneck detection or to disable bottleneck detection on entire switches or fabrics. It is not recommended to disable bottleneck detection on a port except under special circumstances. For example, if a long-distance port is known to be a bottleneck because of credit insufficiency, you could disable bottleneck detection on that port. 1. Select Monitor > Performance > Bottlenecks.
Thresholds and event notification 27 FIGURE 352 Threshold example To create a threshold policy, complete the following steps. 1. Select Monitor > Performance > Configure Thresholds. The Set Threshold Policies dialog box displays. FIGURE 353 Set Threshold Policies dialog box 2. Click Add. The New Threshold Policy dialog box displays.
27 Thresholds and event notification FIGURE 354 New Threshold Policy dialog box 3. Enter a name for the policy (100 characters maximum) in the Name field. 4. Select a policy type from the Policy Type list. You can only define policies for E and F/FL ports. 5. Select a measure from the Measure list. You can only define policies for the Tx and Rx % Utilization measures. You cannot add the same measure more than once.
Thresholds and event notification 27 13. Make the threshold changes by selecting one of the following options: • To only add new thresholds, select the Keep currently set thresholds and only add new thresholds check box. • To overwrite all existing thresholds on all fabrics and devices, select the Overwrite all thresholds currently set on all switches check box. 14. Click OK on the Confirm Threshold Changes dialog box. Editing a threshold policy To edit a threshold policy, complete the following steps.
27 Thresholds and event notification The threshold policy displays in the Available Threshold Policies table with a modified icon ( ). To assign a threshold policy to a fabric or device, refer to “Assigning a threshold policy” on page 811. 12. Click OK on the Set Threshold Policies dialog box. The Confirm Threshold Changes dialog box displays. FIGURE 356 Confirm Threshold Changes dialog box 13.
Thresholds and event notification 27 Assigning a threshold policy To assign a threshold policy to a fabric or device, complete the following steps. 1. Select Monitor > Performance > Configure Thresholds. The Set Threshold Policies dialog box displays. 2. Select one or more threshold policies you want to assign to a fabric or device in the Available Threshold Policies table. Press Ctrl or Shift and then click to select multiple policies. 3.
27 SAN Connection utilization 4. Click Yes on the confirmation message. 5. Click OK on the Set Threshold Policies dialog box. The Confirm Threshold Changes dialog box displays. 6. Make the threshold changes by selecting one of the following options: • To only add new thresholds, select the Keep currently set thresholds and only add new thresholds check box. • To overwrite all existing thresholds on all fabrics and devices, select the Overwrite all thresholds currently set on all switches check box. 7.
SAN Connection utilization 27 The colors and their meanings are outlined in the following table. Line Color Utilization Defaults Red line 80% to 100% utilization Yellow line 40% to 80% utilization Blue line 1% to 40% utilization Gray line 0% to 1% utilization Black line Utilization disabled Enabling connection utilization NOTE Fabrics where performance data collection is not enabled display connections as thin black lines. To display the connection utilization, complete the following steps.
27 SAN Connection utilization Disabling connection utilization NOTE Fabrics where performance data collection is not enabled display connections as thin black lines. To turn off the connection utilization, choose one of the following options: • Select Monitor > Performance > View Utilization (or CTRL + U). • Press CTRL + U. • Click the Utilization icon ( ). The Utilization Legend is removed from the main interface window. Changing connection utilization You can change the utilization percentages.
Chapter 28 Frame Monitor In this chapter • Frame Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Creating a custom frame monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Editing a frame monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Assigning a frame monitor to a port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Finding frame monitor assignments . . . . . . . . .
28 Frame Monitor Frame types The frame type can be a standard type (for example, a SCSI read command filter that counts the number of SCSI read commands that have been transmitted by the port) or a user-defined frame type customized for your particular use.
Creating a custom frame monitor 28 Frame Monitoring requirements To configure Frame Monitoring, the following requirements must be met: • The switch must be running Fabric OS 7.0.0 or later. • Frame Monitoring requires the Advanced Performance Monitoring license and the Fabric Watch license. NOTE The Advanced Performance Monitoring license is required to configure frame monitors. The monitoring functionality requires the Fabric Watch license.
28 Creating a custom frame monitor 2. Select the Switch option. The Products / Monitors list displays the switches that support Frame Monitoring. 3. Enter the monitor data in the Configure Monitor area. 4. Select one or more switches in the Products / Monitors list, and click the right arrow button to assign the frame monitor to those switches. 5. Select the Port option. 6. Expand the switch in the Products / Ports list. The Monitors list displays all of the frame monitors defined for that switch. 7.
Editing a frame monitor 28 11. Click Start. The frame monitor configuration is applied to the switches. 12. Click Close after configuration is complete (indicated by “Completed” in the Progress column). Editing a frame monitor 1. Select Monitor > Fabric Watch > Frame Monitor. The Frame Monitor dialog box displays. 2. Select the Switch option. 3. Expand the Products / Monitors list to display the frame monitors for each switch. 4. Select a frame monitor and click the left arrow button.
28 Finding frame monitor assignments 6. Click the right arrow button to move the frame monitor to the selected ports. The Monitor Details list displays the monitors that are assigned to a selected port. If no monitors are assigned, or if more than one port is selected, the Monitor Details list does not display. 7. Click OK. The Frame Monitor Configuration Status dialog box displays. 8. Click Start. The frame monitor configuration is applied to the ports. 9.
Removing a frame monitor from a switch 28 8. Click Start. The frame monitor configuration is applied to the ports. 9. Click Close after configuration is complete (indicated by “Completed” in the Progress column). Removing a frame monitor from a switch When you remove a frame monitor from a switch, the frame monitor is automatically removed from all assigned ports in the switch. You can remove only custom frame types; you cannot remove the pre-defined frame types. 1.
28 822 Removing a frame monitor from a switch Brocade Network Advisor IP User Manual 53-1002168-01
Chapter 29 Policy Monitor In this chapter • Policy Monitor overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Viewing existing policy monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Adding a policy monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Editing a policy monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Deleting a policy monitor . . . . . . .
29 Policy Monitor overview Fabric policy monitors Enables you to set the following policy monitors on fabrics. • Check zoning status—Enables you to determine if zoning is enabled or disabled on the fabric. Zoning plays a key role in the management of device communication. When you enforce zoning, devices not in the same zone cannot communicate. Zoning provides protection from disruption in the fabric (putting bounds on the scope of RSCNs). The best practice is always enabling zoning.
Policy Monitor overview 29 SAN Switch policy monitors Enables you to set the following policy monitors on SAN switches. • Check if the product is configured to send events to this server—Enables you to determine if the Management application server is registered as an SNMP recipient and Syslog recipient. If the Management application server fails to register as a listener for SNMP, Syslog, and other events, the Management application server cannot notify you of changes to the fabric or device.
29 Policy Monitor overview • Check if the product is configured to send Upload Failure Data Capture to an FTP server— Enables you to determine if Upload Failure Data Capture is enabled on the selected switches, that the configured FTP Server is accessible, and that you have write permission to the directory. Upload Failure Data Capture enables you to collect switch data periodically. This assists you to troubleshoot switch failure.
Viewing existing policy monitors 29 Management policy monitor Enables you to set a policy monitor on the Management application. Check to see if the server backup is enabled and working—Enables you to determine if back up is enabled for the Management application server and if the backup output directory is accessible and writable. Server backup automatically backs up the Management application database on a user-defined schedule.
29 Adding a policy monitor • Next Run—The time the policy will run again. • Last Run—The time the policy ran last. • Result—The result of last Policy Monitor run. There are three possible results: Success, Partially Failed, Failed, and Not Applicable. 3. Click Close on the Policy Monitor dialog box. Adding a policy monitor To view existing policy monitors, complete the following steps. 1. Select Monitor > Policy Monitor. The Policy Monitor dialog box displays. 2. Click Add .
Adding a policy monitor 29 6. Choose one of the following options: • To use the default frequency (one time, runs at current system time plus fifteen minutes), go to step 7. • To configure the frequency, click the ellipsis button and choose one of the following options to configure the frequency at which deployment runs for the policy monitor: 7. To configure deployment to run only once, refer to “Configuring a one-time policy monitor schedule” on page 839.
29 Adding a policy monitor 8. To set policy monitors for switches, select the SAN Switch Checks tab and complete the following steps. FIGURE 363 Add Policy Monitor dialog box, SAN Switch Checks tab a. Select the Check if the product is configured to send events to this server check box to determine if the Management application server is registered as an SNMP recipient and Syslog recipient. b.
Adding a policy monitor 29 9. To set policy monitors for hosts, select the Host Checks tab and complete the following steps. FIGURE 364 Add Policy Monitor dialog box, Hosts Checks tab a. Select the Check for redundant connections to attached fabrics check box to determine if there are at least the minimum number of configured physical connections between the host and the attached fabric. The default is 2. b.
29 Adding a policy monitor 10. To set policy monitors for the Management application, complete the following steps. FIGURE 365 Add Policy Monitor dialog box, Management Checks tab a. Select the Management Checks tab. b. Select the Check to see if the server backup is enabled and working check box to determine the following configurations: • Back up enabled for the Management application server. • Backup output directory is accessible and writable.
Editing a policy monitor 29 Editing a policy monitor To edit an existing policy monitor, complete the following steps. 1. Select Monitor > Policy Monitor. The Policy Monitor dialog box displays. 2. Select the policy you want to edit in the Monitors table and click Edit. The Edit Policy Monitor dialog box displays. FIGURE 366 Add Policy Monitor dialog box, Management Checks tab 3. Change the user-defined name for the policy in the Name field. The name does not have to be unique.
29 Editing a policy monitor 6. Choose one of the following options: • To use the default frequency (one time, runs at current system time plus fifteen minutes), go to step 7. • To configure the frequency, click the ellipsis button and choose one of the following options to configure the frequency at which deployment runs for the policy monitor: 7. To configure deployment to run only once, refer to “Configuring a one-time policy monitor schedule” on page 839.
Editing a policy monitor c. 29 Enter the minimum number of connections allowed between a switch pair in the Minimum Connections field. The default recommended is 2. d. Select the Check if the product is configured to send Upload Failure Data Capture to an FTP server check box to determine the following configurations: • Upload Failure Data Capture is enabled on the selected switches • Configured FTP Server is accessible • You have write permission to the directory. e.
29 Deleting a policy monitor Deleting a policy monitor To delete an existing policy monitor, complete the following steps. 1. Select Monitor > Policy Monitor. The Policy Monitor dialog box displays. 2. Select the policy you want to delete in the Monitors table. 3. Click Delete. 4. Click Yes on the confirmation message. 5. Click Close on the Policy Monitor dialog box. Running a policy monitor Before you run a policy monitor, make sure your policy monitors are valid.
Running a policy monitor 29 4. Review the report details.
29 Viewing a policy monitor report Viewing a policy monitor report To view an existing (must have been run at least once) policy monitor report, complete the following steps. 1. Select Monitor > Policy Monitor. The Policy Monitor dialog box displays. 2. Select the policy for which you want to view a report in the Monitors table. 3. Click Report. The Policy_Name - Policy Monitor Report displays in a web browser. FIGURE 368 Policy_Name - Policy Monitor Report 4. Review the report details.
Policy monitor scheduling 29 • SAN Switch Checks—Displays the switch name and switch IP address and Status of the policy check for the following options: SAN Switch - Check if the product is configured to send events to this server SAN Switch - Check if the product is configured to send Upload Failure Data Capture to an FTP server SAN Switch - Check for at least Configured_Minimum_Value connections to neighboring switches Host Check—Displays the Host name and Status of the policy check for the followi
29 Policy monitor scheduling Configuring an hourly policy monitor schedule To configure an hourly schedule, complete the following steps. 1. Select Hourly from the Frequency list. 2. Select the minute past the hour you want deployment to run from the Minutes past the hour list. Where the minute value is from 00 through 59. 3. Click OK on the Schedule Properties dialog box.
Policy monitor scheduling 29 Configuring a monthly policy monitor schedule To configure a monthly schedule, complete the following steps. 1. Select Monthly from the Frequency list. 2. Select the time of day you want deployment to run from the Time (hh:mm) lists. Where the hour value is from 0 through 12, the minute value is from 00 through 59, and the day or night value is AM or PM. 3. Select the day you want deployment to run from the Day of the Month list (1 through 31). 4.
29 842 Policy monitor scheduling Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 30 Fault Management In this chapter • Event notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Syslogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Event action definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30 Event notification Event notification The Management application records the SAN and IP events in the Master Log. You can configure the application to send event notifications to e-mail addresses at certain time intervals. This is a convenient way to keep track of events that occur on the SAN and IP networks. You can also configure products to “call home” for certain events, notifying the service center of product problems.
Defining filters 30 8. Enter the length of time the application should wait between notifications in the Summary Interval field and list. Notifications are combined into a single e-mail and sent at each interval setting. An interval setting of zero causes notifications to be sent immediately. ATTENTION Setting too short an interval can cause the recipient’s e-mail inbox to fill very quickly. 9.
30 Defining filters FIGURE 370 Define Filter - Basic tab dialog box 4. Select which product type you are defining (SAN, IP, or Host) and click the appropriate tab. 5. Click the Event Description check box and enter a description of the event in the field. 6. Click the Allow all products check box to control whether or not all products are always displayed. • When selected (the default), all products, even newly-added products, are added to the Selected Products to be displayed list.
Defining filters 30 Setting up advanced event filtering To set up advanced event filtering on the selected events for a user, complete the following steps. 1. Select Server > Users. The Users dialog box displays. 2. Select a user in the Users table and click Edit. The Edit User dialog box displays. 3. Select the E-mail Notification Enable check box and click the Filter link. The Define Filter dialog box displays. 4. Click Advanced Filtering. The Define Filter—Advanced Event Filtering dialog box displays.
30 Defining filters d. Click the right arrow button to move the event type to the Additional Filters - Include these Events list. e. To add additional filters, repeat step a through step d. 8. To exclude events from the event filter, complete the following steps. NOTE You can configure a maximum of ten filters to be included. a. Select the event type you want to remove from the Event Category list. All event types are listed in alphabetical order. b.
SNMP traps 30 SNMP traps Simple network management protocol (SNMP) provides a means to monitor and control network products and to manage configurations, statistics, performance, and security through authentication and privacy protocols. The Management application allows you to configure SNMP traps. The SNMP configuration tasks are described in the following sections.
30 SNMP traps FIGURE 372 SNMP Trap Recipients dialog box 2. Click Add from the Action list. 3. Enter the IP address of the SNMP trap receiver (the recipient server) in the Recipient IP Address field. This is a mandatory field. IPv4 addresses are accepted, but a Domain Name System (DNS) name is not accepted. 4. Enter the SNMP trap port of the recipient in the Recipient Port field. This is a mandatory field. Valid numeric values range from 1 through 65535 and 162 is the default. 5.
SNMP traps 30 Removing a trap recipient from one or more switches 1. Select Monitor > SNMP Setup > Product Trap Recipients. The SNMP Trap Recipients dialog box, shown in Figure 372, displays. 2. Click Remove from the Action list. 3. Enter the IP address of the SNMP trap port (the recipient server) in the Recipient IP Address field. 4. Select the fabric or switches from the Available list. NOTE For IP products, only switches are available to select. 5. Click OK.
30 SNMP traps FIGURE 373 SNMP Trap Forwarding dialog box The SNMP Trap Forwarding dialog box allows you to perform the following tasks: • • • • Add a trap destination. Edit a selected trap destination. Duplicate a selected trap destination. Delete a selected trap destination. Adding a trap destination The Add Trap Destination dialog box allows you to configure destinations for forwarding SNMP traps. 1. Select Monitor > SNMP Setup > Trap Forwarding.
SNMP traps 30 FIGURE 374 Add Trap Destination dialog box 4. Enter a general description of the trap destination in the Description field. 5. Enter the IP address of the trap destination in the IP Address field. This is a mandatory field. IPv4 and IPv6 addresses are accepted but a DNS name is not accepted. 6. Enter the SNMP trap listening port of the recipient in the Port # field. This is a mandatory field. Valid numeric values range from 1 through 65535. 7.
30 SNMP traps Adding a new trap filter The Add Trap Filter dialog box allows you to configure trap filters for forwarding SNMP traps. You can add trap filters on SAN products, IP products, or Hosts. 1. Select Monitor > SNMP Setup > Trap Forwarding. The SNMP Trap Forwarding dialog box displays. 2. Click Add in the Trap Filters area of the SNMP Trap Forwarding dialog box. The Add Trap Filter dialog box, shown in Figure 375, displays. FIGURE 375 Add Trap Filter dialog box 3. Select the SAN, IP, or Host tab.
SNMP traps • • • • 30 Warning Notice Info Debug Traps with the selected severity and those with higher severity levels are forwarded. For example, by default, Critical severity is selected. Therefore, traps with Critical, Alert, and Emergency severity levels are forwarded. To have all traps forwarded, select Debug, the lowest severity level. 9. By default, all traps are listed in the Available Traps list, under the folders for the MIB to which they belong.
30 SNMP traps FIGURE 376 Event Reception dialog box - Trap Credentials dialog box The Management application can receive SNMP v1 traps from Brocade SAN switches and directors that have any SNMP community strings. It can receive SNMP v3 traps and informs from these SAN products. The Table 49 explains the combinations of security and authentication, which will help you when you make your SNMP credentials configuration decisions.
SNMP traps TABLE 49 30 SNMP security and authentication (Continued) SNMP credential type Privacy protocol Authentication Result v3 Authentication Privacy protocol MD5 or SHA Provides authentication based on the HMAC-MD or HMAC-SHA algorithms. Provides privacy based on CBC_DES4 or CFB_AES_1285.
30 SNMP traps FIGURE 377 SNMP v3 Credentials dialog box 4. Type the user name in the User Name field. For configurations that do not have authentication or privacy, the Management application uses the user name to match for authentication. 5. Select an authentication protocol from the Auth Protocol list. You can select -None-, HMAC-MD5, or HMAC_SHA. HMAC_MD5 is the default. If you select no authentication, the Management application uses the user name to match for authentication. 6.
SNMP traps 30 FIGURE 378 SNMP v1/v2 Community String dialog box 4. Enter a unique community string in the Community String field, which will be used to match for authentication in SNMP v1 and v2c configurations. This field is case-sensitive. 5. Re-enter the string in the Confirm Community String field. 6. Click OK.
30 SNMP traps 4. Save the file. The Management application recompiles all the MIB files. If compilation is successful, the traps can now be registered in the Event Reception dialog box. NOTE If there are compilation errors, you can view the errors in the server log \logs\server\server.log (Windows) or /logs/server/server.log (UNIX). 5. If you make changes to the MIB file, open the mibs_to_compile.txt file and save the file.
SNMP traps 30 FIGURE 379 Trap Configuration tab of the Event Reception dialog box 3. Expand a folder for a MIB to display the traps in the MIB. If the list is too long, use the Search tool to find a MIB or trap. 4. Select the trap you want to register. The SNMP name and Object Identification (OID) of the trap appear at the top line of the configuration pane. Also, the status of the trap shows Not Registered, which is the default definition of the trap.
30 SNMP traps 6. When you have finished, click OK to accept your entries. The status of the trap changes to Registered - Customized and the trap appears in the Event Log. Unregistering a registered trap You can unregister only the traps that you have registered. You cannot unregister traps that come with the Management application by default. Perform the following steps if you want to unregister a trap that you registered. 1. Select Monitor > SNMP Setup > Event Reception. 2.
Syslogs 30 5. If the trap has been customized, a button labeled Default is availab.e. Click Default to revert the previous changes to its default. Syslogs Use the Options dialog box to automatically register the Management application server as the syslog recipient on all managed SAN and IP products. The syslog listening port number is 514 by default. If you change the port number from 514, auto-registration is disabled. Adding a syslog recipient 1.
30 Syslogs Removing a syslog recipient 1. Select Monitor > Syslog Configuration > Product Trap Recipients. The Syslog Recipients dialog box displays. 2. Select Remove from the Action list. 3. Enter the IP address of the syslog port (the recipient server) in the Recipient IP Address field. 4. Select the fabric or switches from the Available list. 5. Click OK. The Management application removes the recipient from the managed switches.
Syslogs 30 Adding a syslog destination The Add Syslog Destination dialog box allows you to configure destinations for forwarding syslog events. 1. Select Monitor > Syslog Configuration > Syslog Forwarding. The Syslog Forwarding dialog box displays. 2. Click the Enable syslog forwarding check box. 3. Click Add. The Add Syslog Destination dialog box, shown in Figure 382, displays. Enable and Syslog Repeater are enabled by default. FIGURE 382 Add Syslog Destination dialog box 4.
30 Syslogs Adding a syslog filter You can add a syslog filter on SAN products, IP products, or Hosts. 1. Select Monitor > Syslog Configuration > Syslog Forwarding. The Syslog Forwarding dialog box displays. 2. Click the Enable syslog forwarding check box. 3. Click Add in the Filters list. The Add Syslog Filter dialog box, shown in Figure 383, displays. FIGURE 383 Add Syslog Filter dialog box 4. Select the SAN, IP, or Host tab.
Event action definitions 30 Event action definitions To reduce the amount of events being logged in the Management application database, the Event Actions dialog box allows you to control what events the Management application monitors, on which products they are to be monitored, how often they are to be monitored, and what to do when the monitored events are generated. This information can be defined by creating an event action definition.
30 Event action definitions FIGURE 385 Add Events dialog box - Events pane 5. Select one of the following event types from the Show list: • • • • Traps (default) Application Events Pseudo Events Custom Events Depending on what event type you select, a box listing the available events or pseudo events displays. 6. By default, all traps are listed in the Available Traps list, under the folders for the MIB to which they belong.
Event action definitions 30 11. Select Configure varbind filters to configure filters on varbind values (see “Configuring varbind filters” on page 869 for more information). If you do not want to configure varbind filters, click Next. The Sources pane of the Add Event Action dialog box is displayed. You can use the search tool to search for sources.
30 Event action definitions • in – Matches collection • not_in – Does not match collection • ~ – Arbitrary Unicode regular expression 5. Enter the value of the varbind. The value you enter must conform to the data type required by the varbind. For example, if the varbind expects an integer and you enter a text string, your entry will be rejected. Alternatively, you can select values from dropdown choices, as shown in Figure 386. 6. Click Next.
Event action definitions 30 5. Select the event senders you want from the Available Sources list, then click the right arrow button to move them in the Selected Sources box. NOTE The selected source count cannot exceed 100. 6. If you selected a product group or port group as event senders, select one of the following group members: NOTE The Selected Product/Port Group members treated as parameter is not available if you selected Use Ifindex in source matching (step ).
30 Event action definitions Configuring event action policies The Policy pane of the Add Event Action dialog box, shown in Figure 388, allows you to define the frequency of the event, enter a message for an event that will be displayed in the event log, and specify the event severity. FIGURE 388 Policy pane of the Event Action dialog box 1. Click Act on all occurrences (default) if you want the action to be triggered each time the selected events occur. 2.
Event action definitions - 30 Click Time bound (act at the end of the duration specified) if you want the Management application to perform the specified action once the specified number of occurrences has occurred and the specified duration has elapsed. For example, if you want the action to be applied when 10 link down traps occur during a one-minute duration, the Management application waits until 10 link down traps occur and one minute has elapsed before the defined action is applied.
30 Event action definitions Editing event actions The Edit Event Action Group - Actions dialog box, shown in Figure 389, defines what action the Management application takes when the criteria are met. FIGURE 389 Action Group - Actions pane of the Edit Event Action dialog box 1.
Event action definitions 30 The Broadcast Message dialog box displays. a. Select a severity level from the list. b. Type a message in the Message Content field. c. Click OK. 5. The Special Events Handling check box is enabled by default. Leave it enabled if you want the event action to be added to the Special Event Handling event action category. Refer to “Special events handling” for more complete information. 6.
30 Event action definitions 9. From the Target list, select the product (the target source) to which the payload will be deployed: • Event Sender: Deploy the payload to the product that sent the event. If the event was sent by a non-Brocade product, the event action will not be deployed to that product. • Derived from: Deploy the payload to the product that matches the IP address as specified in the attribute of the selected source.
Event action definitions 30 Acknowledging special events When the Management application receives and processes events selected as special events, the following status bar icon displays. 1. Click the special events icon to launch the Special Events dialog box, shown in Figure 390. The dialog lists the most recent 1000 events that have been identified as special events. FIGURE 390 Special Events dialog box 2. Click the Acknowledged check box that corresponds to the special event you want to acknowledge.
30 Event action definitions Configuring event action e-mail settings The Action Group - E-mail Settings pane of the Add Event Action dialog box, shown in Figure 391, allows you to select e-mail recipients from a list, add new e-mail recipients, and compose e-mail messages. FIGURE 391 Action Group - E-mail Settings pane of the Add Event Action dialog box 1.
Event action definitions 30 6. Click Finish. The Summary pane of the Edit Event Action dialog box displays an overview of the e-mail configuration you are creating. 7. Review your entries and take one of the following actions: • • • • Click Finish to approve the configuration. Click Previous to return to the Action Group - E-mail Settings pane of the dialog box. Click Cancel to cancel the operation.
30 Event action definitions Deleting an event action definition Perform the following steps to delete an event action definition. 1. Select Monitor > Event Processing > Event Actions. The Event Actions dialog box displays. 2. Select the definition that you want to delete from the Event Actions list. 3. Click Delete. A message displays asking you to confirm the deletion request. 4. Click Yes to delete the definition, or No to cancel the request.
Event action definitions 30 3. Click the Import Snort® Rule button. The Import Snort® Rule File dialog box displays, as shown in Figure 393. FIGURE 393 Import Snort® Rule File dialog box 4. Enter the complete path of the Snort rule file located on the Syslog server. 5. Click OK to import the Snort rules. 6. While still in the Add Event Action dialog box, continue to click Next until you advance to the Action Group - Actions pane. 7.
30 Pseudo events Pseudo events A pseudo event is a combination of different SNMP traps that you decide would constitute a single event. For example, there are two separate SNMP traps for link up and link down occurrences. You might decide that these two occurrences should be just one event. Displaying pseudo event definitions Perform the following steps to display the properties of a pseudo event. 1. Select Monitor > Event Processing > Pseudo Events.
Pseudo events 30 Setting pseudo event policies The Policy pane of the Add Pseudo Event dialog box is displayed in Figure 395. FIGURE 395 Policy pane of the Add Pseudo Event dialog box 1. Click the Escalation button to create an escalation policy, and then enter the duration of time that the Management application waits before performing the specified action. Specify the escalation time in minutes or hours.
30 Pseudo events Refer to “Creating an event action with a pseudo event on the flapping policy” on page 890 for complete instructions. 4. Enter a description in the Message field. This description is displayed in the event log for this pseudo event.The event log displays the exact text you enter in this field; therefore, this message should describe the events in the event action policy. 5. Select a severity from Severity list. You must assign a severity to the pseudo event. 6. Click Next.
Pseudo events 30 1. From the Available Traps list, select the trap for the down state of a product or interface. 2. You can change the text associated with the selected trap by doing any of the following: • Click one of the following buttons: MIB Information, if you want the default SNMP name for the traps to be displayed. MIB Alias, if you want the aliases for the traps to be displayed. Use the Trap Filter tool to limit the trap severity.
30 Pseudo events Editing a pseudo event definition Use caution when you modify pseudo events. Saving changes to a pseudo event definition resets the run-time information for that pseudo event. 1. Select Monitor > Event Processing > Pseudo Events. The Pseudo Events dialog box, shown in Figure 394, displays. 2. Select the pseudo event definition that you want to edit from the Pseudo Events list. 3. Click the Edit button to display the Edit Pseudo Event dialog box. 4.
Pseudo events 30 6. Click Next. The Events pane of the Add Pseudo Event dialog box displays. 7. Select a critical event, such as LinkDown, and click the right arrow button to move it to the Selected Down Trap list. 8. Select a remediation event, such as LinkUp, and click the right arrow button to move it to the Selected Up Trap list. 9. Click Next to advance to the Summary pane. 10. Click Finish to complete the pseudo event configuration.
30 Pseudo events 13. Select the Management application user to whom the e-mail message will be sent from the Available Recipients list, and click the right arrow button to move the recipient to the Selected Recipients list. NOTE Make sure the user you select has an e-mail address defined in a user account. 14. Add additional e-mail recipient addresses in the Other Recipients field. Separate multiple e-mail addresses with a semicolon. 15.
Pseudo events 30 6. Click Next. The Events pane of the Add Pseudo Event Events dialog box displays. 7. Select a critical event, such as LinkDown, and click the right arrow button to move it to the Selected Down Trap list. 8. Select a remediation event, such as LinkUp, and click the right arrow button to move it to the Selected Up Trap list. 9. Click Finish to complete the pseudo event configuration. Now, you must create a new event action definition using the Add Event Actions dialog box.
30 Pseudo events 12. Click Next to advance to the Summary pane. 13. Click Finish. For more information about adding an event action, refer to “Event action definitions” on page 867. Adding a pseudo event on the flapping policy The flapping policy checks to see if the event consistently transitions between two opposite states during a specified length of time. If it does, then the specified action in the definition is performed.
Pseudo events 30 5. Select the Pseudo Events event type from the Show list. The available pseudo events display. 6. Select the pseudo event you created in step 1 through step 10, and click Next. The Sources pane of the Add Event Action dialog box displays. 7. Select the source that you will use to monitor this event from the Selected Sources list. 8. Click Next to advance to the Policy pane of the Add Event Action dialog box. The Policy pane of the Add Event Action dialog box displays. 9.
30 Event custom reports 14. Select the Apply as a Logging Policy check box to indicate whether or not you want the event occurrence to be logged in the Management application database: • Select Log to log the occurrence in the Management application database. • Select Drop to not log the occurrence in the Management application database. 15. Click Next to advance to the Summary pane. 16. Click Finish. For more information about adding an event action, refer to “Event action definitions” on page 867.
Event custom reports 30 Defining report settings Complete the following steps to define report settings. You must first enter a name and title on the Identification tab before you can run the result settings. 1. Select Reports > Event Custom Reports. The Event Custom Reports dialog box displays. 2. Click the Add button. 3. The Add/Edit Report Definition dialog box - Product tab displays. 4. Click the Result Settings tab. The Add/Edit Report Definition dialog box - Result Settings tab displays.
30 Event custom reports 6. Data for all attributes is sorted in ascending order and is sorted in the sequence that the attributes appear in the Sort By Columns list. In the Selected Columns list, select which attribute will be used to sort the generated report. Then click the right arrow button to move your selection to the Sort by Columns list. To remove an entry from the Sort by Columns list, select the entry, then click the left arrow button. 7.
Event custom reports 7. 30 Click the Do not share this definition button if you do not want to share this definition with other Management application users. If you select this button, no Management application users will see this definition on the Report Definitions tab of the Event Custom Reports dialog box when they log in. 8. Click the Share this definition (Read only) button if you want other Management application users to have Read Only permission for this definition.
30 Event custom reports FIGURE 400 Add/Edit Report Definition dialog box - Product Tab 4. Click the Filter tab. The Add/Edit Report Definition dialog box - Filter tab, shown in Figure 401, displays. FIGURE 401 Add/Edit Report Definition dialog box - Filter tab 5. To limit the search results to traps, syslog, and pseudo event messages with a specific text string, enter the text string in the Description field. 6.
Event custom reports 7. 30 Select the Acknowledge check box if you want messages that have been acknowledged to be included in the report. 8. Select the severity from the Available Severity list, and click the right arrow button to move your selection to the Selected Severity list. Events with the selected severity are included in the report. 9. Select the event type you want to include in the report from the Available Event Category list.
30 Event custom reports 5. Choose between relative time (the default) and absolute time. • Click Relative Time if you want to filter traffic based on when the report is generated, and then select a relative time from the Range list. Relative time is calculated based on the date and time the report is generated. • Click Absolute Time if you want to filter traffic sent at a specific date and time. a. Select the specific start date from the Start Date list. b.
Event custom reports 30 Editing a report definition For your definitions, you can modify the definition and save the changes you have made. For a shared definition from another user, you can modify the definition, then run that definition to obtain the desired report; however, you will not be able to save your changes. Complete the following steps to edit a definition. 1. Click the Report Definitions tab and select the definition you want to modify. 2. Click Edit. 3.
30 Event custom report schedules Event custom report schedules Click the Schedules tab, shown in Figure 403, to display its contents. The Schedules list shows the definitions that have been scheduled to automatically run at a specified date and time. FIGURE 403 Schedules tab of the Event Custom Report dialog box From the Schedules tab of the Event Custom Reports dialog box, you can perform the following tasks: • View—Displays the report data of the scheduled report definition.
Event custom report schedules 30 Adding an event report schedule The Add Schedule dialog box, shown in Figure 404, allows you to select an existing report definition and configure the parameters for when the report is run and to whom the report is sent. 1. Select Reports > Event Custom Reports. The Event Custom Reports dialog box displays. 2. Click the Schedules tab. 3. Click the Add button. The Add Schedule dialog box displays. FIGURE 404 Add Schedule dialog box 4.
30 Event custom report schedules • Weekly—If you selected Weekly as the schedule type, Day of the week appears. Select the day of the week when the report will be generated. • Monthly—If you selected Monthly as the schedule type, Day of the month appears. Select the day of the month when the report will be generated. • Yearly 8. Select a report format from the Format list: HTML or CSV. 9. Select the time when the report will be generated. Indicate the hour, minute, and whether it is AM or PM.
Event logs 30 Event logs You can view all events that take place through the Master Log at the bottom of the main window. You can also view a specific log by selecting an option from the Monitor menu’s Logs submenu. The logs are described in the following list: • Audit Log. Displays all ‘Application Events’ raised by the application modules and all Audit Syslog messages from the switches and Brocade HBAs. • Product Event Log.
30 Event logs Copying part of a log entry You can copy data from logs to other applications. Use this to analyze or store the data using another tool. To copy part of a log, complete the following steps. 1. Select Monitor > Logs > . The Logs dialog box displays the kind of log you selected. 2. Select the rows you want to copy. • To select contiguous rows, select the first row you want to copy, press Shift, and click the contiguous row or rows you want to copy.
Event logs 30 Exporting the entire log You can export the log data to a tab delimited text file. To export a log, complete the following steps. 1. Select Monitor > Logs > . The Log dialog box displays the kind of log you selected. 2. Right-click a row and select Export Table. The Save table to a tab delimited file dialog box displays. 3. Browse to the location where you want to export the data. 4. Enter a name for the file in the File Name field. 5. Click Save.
30 Event logs 5. Enter your e-mail address in the From field. 6. Click OK. Displaying event details from the Master Log You can view detailed information for an event. To display event details from the Master Log, complete the following steps. 1. Right-click an entry in the Master Log. 2. Select Properties. The Event Details dialog box displays. 3. Review the information. TABLE 50 Event details Event Field Description Count Number of times this event occurred on the host.
Event logs 30 Copying part of the Master Log You can copy data from logs to other applications. Use this to analyze or store the data using another tool. To copy part of the Master Log, complete the following steps. 1. Select the rows you want to copy in the Master Log. • To select contiguous rows, select the first row you want to copy, press Shift, and click the contiguous row or rows you want to copy.
30 Event logs 5. Click Save. All data and column headings are exported to the text file. 6. Click Close to close the dialog box. Filtering events in the Master Log You can filter the events that display in the Master Log on the main window. By default, all event types display in the Selected Events table. For more information about the Master Log, refer to “Master Log” on page 14. NOTE The e-mail filter in the Management application is overridden by the firmware e-mail filter.
Event logs Brocade Network Advisor SAN User Manual 53-1002167-01 30 909
30 910 Event logs Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter Technical Support 31 In this chapter • Server and client support save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911 • Device technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914 • Upload failure data capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919 Server and client support save You can use Technical Support to collect supportSave data for the Management server and clients.
31 Server and client support save 4. Select the Include Database check box to include the database in the support save and choose one of the following options. • Select the Partial (Excludes historical performance data and events) option to exclude historical performance data and events from the database capture. • Select the Full option to capture the entire database. Clear the Include Database check box to exclude the database in the support save. 5.
Server and client support save 31 6. Click OK on the SupportSave dialog box. 7. Click OK on the message. The application generates separate master logs to show the status of the Server Support save collection. Capturing Client support save data To capture client support save files, complete the following steps. 1. Select Monitor > Technical Support > SupportSave. The SupportSave dialog box displays. 2. Select the Client SupportSave check box to run supportsave on the client. 3.
31 Device technical support 3. Define a capture location by typing sh clientsupportsave in the CLI. If the path has spaces, enclose it in double quotes. By default, the capture location is /root /Management_Application_Name_Folder/Server IP/support. 4. Use an archive tool to create a ZIP file of the support save. Device technical support You can use Technical Support to collect supportSave data (such as, RASLOG, TRACE and so on) and switch events from Fabric OS devices.
Device technical support 31 11. Click OK on the confirmation message. Technical supportSave dats for SAN devices is saved to the following directory: Install_Home\data\ftproot\technicalsupport\ Technical supportSave uses the following naming convention for the SAN device support save files: Supportinfo-Day-mm-dd-yyyy-hh-mm-ss\Switch_Type-Switch_IP_AddressSwitch_WWN. Data collection may take 20-30 minutes for each selected switch. This estimate my increase depending on the number of switches selected.
31 Device technical support 5. Click OK on the Technical SupportSave dialog box. Data collection may take 20-30 minutes for each selected switch. This estimate my increase depending on the number of switches selected. The Technical SupportSave Status dialog box displays with the following details. Field Description Product Name The name of the product. IP Address The product’s IP address. Product Type The type of product. Progress The status of the supportsave. On products running Fabric OS 7.
Device technical support 31 To view the technical support repository, complete the following steps. 1. Select Monitor > Technical Support > View Repository. The Technical Support Repository dialog box displays. 2. Review the techncial support repository details: Field/Component Description Available SupportSave and Upload Failure Data Capture Files table Select the support data file you want to view. Displays the following information: File Name—The name of the supportSave file.
31 Device technical support E-mailing technical support information To e-mail technical support information, complete the following steps. 1. Select Monitor > Technical Support > View Repository. The Technical Support Repository dialog box displays. 2. Select the file you want to e-mail in the table. 3. Click E-mail to e-mail the event and supportsave files (zip). You must configure the Management application e-mail server before you can define the e-mail action.
Upload failure data capture 31 3. Click Delete. 4. Click OK on the Technical Support Repository dialog box. Upload failure data capture You can use upload failure data capture to enable, disable, and purge failure data capture files as well as configure the FTP Host for the switch. NOTE Upload failure data capture is only supported on Fabric OS devices. Enabling upload failure data capture 1. Select Monitor > Technical Support > Upload Failure Data Capture.
31 Upload failure data capture Disabling upload failure data capture NOTE Upload Failure Data Capture is only supported on Fabric OS devices. 1. Select Monitor > Technical Support > Upload Failure Data Capture. The Upload Failure Data Capture dialog box displays. 2. Select one or more devices on which you want to disable automatic trace dump from the Available Switches with Upload Failure Data Capture Enabled table. 3. Click the left arrow button.
Upload failure data capture 31 4. Choose one of the following options: • Select the Use Management_Application option to use the Management application FTP server. • Select the Custom option and complete the following steps to configure a FTP server for the selected device. a. Enter the server’s IP address in the Host IP field. b. Enter a user name for the server in the User Name field. c. Enter a password for the server in the Password field. d.
31 922 Upload failure data capture Brocade Network Advisor SAN User Manual 53-1002167-01
Chapter 32 Reports In this chapter • SAN report types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Generating SAN reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Viewing SAN reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Exporting SAN reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Printing SAN reports . . . . . . . . . .
32 Generating SAN reports Generating SAN reports To generate reports, complete the following steps. 1. Select Reports > Generate. The Generate Reports dialog box displays. 2. Select the types of reports you want to generate. • Fabric Ports • Fabric Summary 3. Select the fabrics for which you want to generate reports. 4. Click OK. The generated reports display in the View Reports dialog box. NOTE Hyperlinks in reports are active only as long as the source data is available. 5.
Exporting SAN reports Icon 32 Description Actual Size—Click to display the report at its actual size. Fit to Page—Click to resize the report to display entirely in the view. Fit to Width—Click to resize the report to fit in the view by width. Zoom In—Click to zoom in on the report. Zoom Out—Click to zoom out on the report. 4. Click Show in Browser to view the selected report in your default browser window. 5. Click Close to close the View Reports dialog box. 6.
32 Printing SAN reports Printing SAN reports You can print reports through an internet browser. 1. Select Reports > View. The View Reports dialog box displays. 2. Select the report you want to print in the left pane of the dialog box. If you do not see the report you want to view, generate it first by following the instructions in “Generating SAN reports” on page 924. NOTE Hyperlinks in reports are active only as long as the source data is available. 3. Click Show in Browser.
Generating SAN performance reports 32 Generating SAN performance reports NOTE Performance reports require a SAN Trial or Licensed version. To generate a historical performance report for a device, complete the following steps. 1. Select the device for which you want to generate a performance report. 2. Choose one of the following options: • Select Monitor > Performance > Historical Report. OR • Right-click the device and select Performance > Historical Report.
32 Generating SAN zoning reports g. Click Apply. The selected report automatically displays in the View Reports dialog box. NOTE Hyperlinks in reports are active only as long as the source data is available. To print the selected report, refer to “Printing SAN reports” on page 926. To export the selected report, refer to “Exporting SAN reports” on page 925. To delete the selected report, refer to “Deleting SAN reports” on page 926. 4. Click the close button (X) to close the View Reports dialog box. 5.
Generating SAN zoning reports 32 For more information about zoning, refer to “Zoning” on page 579.
32 930 Generating SAN zoning reports Brocade Network Advisor SAN User Manual 53-1002167-01
Appendix A Application menus In this appendix • Dashboard main menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931 • SAN main menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932 • SAN shortcut menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941 Dashboard main menus The menu bar is located at the top of the main window.
A SAN main menus Menu Command Command Options License. Select to view or change your License information. About Management_Application_Name. Select to view the application information, such as the company information and release number. SAN main menus The menu bar is located at the top of the main window. The following table outlines the many functions available on each menu. Menu Command Command Options Server Menu Users. (Trial and Licensed version Only) Select to configure users and user groups.
SAN main menus Menu Command A Command Options View Menu Show Main Tab. Select to choose which tab to display. Dashboard. Select to show the dashboard. SAN. Select to show the SAN tab. IP. Select to show the IP tab. Show Panels. Select to select which panels to display. All Panels. Select to show all panels. Topology Map. Select to only show the topology map. Product List. Select to only show the Product List. Master Log. Select to only show the Master Log. Manage View.
A Menu SAN main menus Command Command Options Map Display. Select to customize a group's layout to make it easier to view the SAN and manage its devices. Domain ID/Port #. Select to set the display domain IDs and port numbers in decimal or hex format. Decimal. Select to display all domain IDs and port numbers in decimal format. Hex. Select to display all domain IDs in hex format. Product Label. Select to configure which product labels display. Name.
SAN main menus Menu Command A Command Options Discover Menu Fabrics. Select to discover fabrics. Host Adapters . Select to discover hosts. VM Manager. Select to discover VM managers. Host Port Mapping. (Trial and Licensed version Only) Select to manually map HBA ports to a host. Storage Port Mapping. (Trial and Licensed version Only) Select to manually map Storage Ports to a Storage Device or other Storage Ports. Configure Menu Element Manager. Select to configure the selected device. Hardware.
A Menu SAN main menus Command Command Options Deployment. Select to manage deployment. Encryption. Select to configure encryption for your SAN. Fabric Binding. (Trial and Licensed version Only) Select to configure whether switches can merge with a selected fabric, which provides security from accidental fabric merges and potential fabric disruption when fabrics become segmented because they cannot merge. FCIP Tunnels. Select to configure tunnels and circuits on FCIP-capable devices.
SAN main menus Menu Command A Command Options Port Auto Disable. Select to configure port auto disable flag on individual FC_ports or all ports on a selected device, as well as unblock currently blocked ports. Security. Select to manage security. L2 ACL. Select to configure Layer 2 Access Control Lists on products and ports. Fabric Assigned WWN. Select to configure fabric assigned world wide names to a switch port or AG port. VLANs. Select to launch the VLAN Manager. Allow/Prohibit Matrix.
A SAN main menus Menu Command Command Options Monitor Menu. Performance. Select to monitor SAN devices. View Utilization. (Trial and Licensed version Only) Select to display connection utilization. View Bottlenecks. (Trial and Licensed version Only) Select to display bottlenecks. HIstorical Data Collection. (Trial and Licensed version Only) Select how to monitor historical data by choosing one of the following options: • Enable SAN Wide • Enable Selected • Disable All -End Monitors.
SAN main menus Menu Command A Command Options Fabric Watch. Select to manage fabric watch. Configure. Select to launch Fabric Watch. Port Fencing. (Trial and Licensed version Only) Select to configure port fencing to protect your SAN from repeated operational or security problems experienced by ports. Frame Monitor. Select to configure frame monitors. Performance Thresholds. (Trial and Licensed version Only) Select to monitor thresholds. Technical Support. Select to configure technical support data.
A SAN main menus Menu Command Command Options Events. Select to display all events triggered on the selected device. Logs. Select to display logs. Audit. Select to display a history of user actions performed through the application (except login/logout). Fabric. Select to display the events related to the selected fabric. FICON. Select to display the FICON events related to the selected device or fabric. Product Event. Select to display errors related to SNMP traps and Client-Server communications.
SAN shortcut menus Menu Command A Command Options Help Menu Contents. Select to open the Online Help. Find. Select to search the Online Help. License. Select to view or change your License information. About Management_Application_Name. Select to view the application information, such as the company information and release number. SAN shortcut menus You can use the Management application interface main menu to configure, monitor, and troubleshoot your SAN components.
A SAN shortcut menus Component Menu/Submenu Commands Comments View > Port List Node List Track Fabric Changes check box Trial and Licensed version Only Accept Changes Trial and Licensed version Only Trace Route Connected End Devices > Include Virtual Devices check box Hide All Show All Custom MyCustomList Create Meta SAN View Only available for Backbone fabrics. Create View Automatically Automatically creates a view with the selected fabric. View name is same as the current label.
SAN shortcut menus Component Menu/Submenu Commands Comments Port Display > Occupied Product Ports UnOccupied Product Ports Attached Ports Switch to Switch Connections Only available from Product List. Table > Copy 'Device_Name Group' Copy Row Copy Table Export Row Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Only available from Product List.
A SAN shortcut menus Component Menu/Submenu Commands Comments FCoE (DCB-capable switch) Allow / Prohibit Matrix Enterprise Edition Only Only available for Fabric OS devices. Only enabled when the Fabric OS device is FICON-capable and has the Enhanced Group Management license.
SAN shortcut menus Component Menu/Submenu Commands Comments Accept Change Trial and Licensed version Only Only enabled in tracked FC Fabrics. Only enabled when a plus or minus icon is present. A Show Ports check box Show Connections Port Display > Occupied Product Ports UnOccupied Product Ports Attached Ports Switch to Switch Connections Only available from Product List.
A SAN shortcut menus Component Menu/Submenu Commands Comments Accept Change Show Ports Show Connections Port Display > Occupied Product Ports UnOccupied Product Ports Attached Ports Switch to Switch Connections Only available from Product List. Table > Copy 'Device_Name Group' Copy Row Copy Table Export Row Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Only available from Product List.
SAN shortcut menus Component Menu/Submenu Commands Comments Port Display > Occupied Product Ports UnOccupied Product Ports Attached Ports Switch to Switch Connections Only available from Product List. Table > Copy 'Device_Name Group' Copy Row Copy Table Export Row Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Only available from Product List. A Properties DCB Element Manager > Hardware Ports Admin Router Admin Name Server Launches Web Tools.
A SAN shortcut menus Component Menu/Submenu Commands Comments Performance > Clear Counters Top Talkers Real-Time Graph Historical Graph Historical Report Bottleneck Graph Fabric Watch > Configure Port Fencing Frame Monitor Performance Thresholds Technical Support > Product / Host SupportSave Upload Failure Data Capture** View Repository Events Port Connectivity Port Optics (SFP) Telnet Telnet through Server Setup Tools Product Only enabled when the fabric is tracked, and the p
SAN shortcut menus Component Menu/Submenu Commands Comments Table > Copy 'Device_Name Group' Copy Row Copy Table Export Row Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Only available from Product List. A Properties HBA, iSCSI Host, and HBA Enclosure Element Manager Launches Element Manager for Fabric OS HBAs discovered using JSON agent. Launches blank window for unmanaged Fabric OS HBAs.
A SAN shortcut menus Component Menu/Submenu Commands Comments Port Display > Occupied Product Ports UnOccupied Product Ports Attached Ports Switch to Switch Connections Only available from Product List. Expand All Only available from Product List. Collapse All Only available from Product List. Properties Storage, iSCSI Storage, and Storage Enclosure Storage Port Mapping Trial and Licensed version Only Disabled for routed device.
SAN shortcut menus Component Menu/Submenu Commands A Comments Origin Port Display > Occupied Product Ports UnOccupied Product Ports Attached Ports Switch to Switch Connections Only available from Product List. Table > Copy 'Device_Name Group' Copy Row Copy Table Export Row Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Only available from Product List.
A SAN shortcut menus Component Menu/Submenu Commands Comments Table > Copy 'Device_Name Group' Copy Row Copy Table Export Row Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Only available from Product List. Collapse All Only available from Product List. Properties HBA and iSCSI Initiator Host Port Mapping Only available for Brocade, Emulex, and Qlogic HBAs and HBA enclosures. Performance > Real Time Graphs Disabled when all ports are offline.
SAN shortcut menus Component A Menu/Submenu Commands Comments Performance > Real Time Graphs Only available for occupied, managed ports. Disabled when all ports are offline. FC Security Protocol Only available for Managed JSON HBA Ports. Only available when you have the Security Privilege.
A SAN shortcut menus Component Menu/Submenu Commands Comments Giga-Bit Ethernet Port Performance > Real-Time Graph Modify Launches Element Manager. IP Troubleshooting > Ping Trace Route Performance (Trial and Licensed version Only) Port Display > Occupied Product Ports UnOccupied Product Ports Attached Ports Switch to Switch Connections Only available from Product List.
SAN shortcut menus Component Menu/Submenu Commands Comments Table > Copy 'Device_Name Group' Copy Row Copy Table Export Row Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Only available from Product List.
A SAN shortcut menus Component Menu/Submenu Commands Comments Table > Copy 'Component' Copy Table Export Table Search Select All Size All Columns To Fit Expand All Collapse All Customize Some form of this shortcut menu is available for all tables in the Management interface.
Appendix B Call Home Event Tables In this appendix This section provides information about the specific events that display when using Call Home. This information is shown in the following Event Tables. • Call Home Event Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • # CONSRV Events Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • # Thermal Event Reason Codes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B Call Home Event Table Event Reason Code FRU Code / Event Type Description Severity 202 PWR/HW Power supply thermal failure. 3 208 PWR/HW Power supply false shutdown. 3 210 PWR/HW Power supply i2c bus failure. 3 300 FAN/HW A cooling fan propeller has failed. 3 301 FAN/HW A cooling fan propeller has failed (two failed propellers). 3 302 FAN/HW A cooling fan propeller has failed. 3 303 FAN/HW A cooling fan propeller has failed.
B # CONSRV Events Table # CONSRV Events Table Event Reason Code FRU Code/Event Type Description Severity 504 DVP/LIM/HW M-EOS: Port module failure. 3 506 DVP/PORT Fibre Channel port failure 3 509 DVP/PORT Fibre Channel path failure. 0 511 LIM/DVP LIM SPP failure. 3 514 DVP/ LIM/PORT SFP/XFP optics failure. 3 517 LIM LIM SPP Offline. 3 530 LIM/DVP LIM Power-up diagnostic failure. 3 536 LIM/DVP Internal Frame Error port anomaly - threshold exceeded.
B Brocade Events Table Brocade Events Table Event Reason Code FRU Code/Event Type Description Severity 1009 MS-1009 Error in registered link incident record (RLIR) 4 1402 FW-1402 Flash usage is out of range (Fabric OS version 6.
Appendix User Privileges C In this appendix • About user privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961 • About Roles and Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979 About user privileges The Management application provides the User Administrator with a high level of control over what functions individual users can see and use.
C About user privileges TABLE 52 Application privileges and behavior Privilege Description No Privilege Read-Only Read/Write Active Session Management Allows you view active client sessions and disconnect an unwanted user. Disables the Active Sessions command from the Server menu. Enables the Active Sessions command from the Server menu. Disables all commands and functions on the dialog box except the Close and Help. Enables the Active Sessions command from the Server menu.
About user privileges TABLE 52 C Application privileges and behavior (Continued) Privilege Description No Privilege Read-Only Read/Write E-mail Event Notification Setup Allows you to define the e-mail server used to send e-mail. Disables Event Notification E-mail command on the Monitor menu and the E-mail Event Notification Setup button in the Users dialog box. Disables the E-mail option in the Master Log shortcut menu.
C About user privileges TABLE 52 Application privileges and behavior (Continued) Privilege Description No Privilege Read-Only Read/Write Fault Management Allows you to control access to the SNMP Trap Registration and Forwarding dialog box, the Event Storage option of the Options dialog box, the Syslog Registration and Forwarding dialog box, as well as the Export and Clear functions in the Event Log dialog box and the Show and Hide functions in the Customize Columns dialog box.
About user privileges TABLE 52 C Application privileges and behavior (Continued) Privilege Description No Privilege Read-Only Read/Write Firmware Management Allows you to download firmware to selected switches and manage the firmware repository. Disables the Firmware Management command from the Configure menu and right-click menu. Enables the Firmware Management command from the Configure menu and right-click menu. Disables all commands and functions on the dialog box except the Close and Help.
C About user privileges TABLE 52 Application privileges and behavior (Continued) Privilege Description No Privilege Read-Only Read/Write Properties Edit Allows you to edit many director and switch properties. Enables the Properties command on Edit menu and right-click menus. Disables edit function (removes green triangles) from editable property fields. Disables the Names command on the Configure menu. Enables the Properties command on Edit menu and right-click menus.
About user privileges TABLE 52 C Application privileges and behavior (Continued) Privilege Description No Privilege Read-Only Read/Write Server Software Configuration Allows you to configure some of the properties of the client and server of the management application. Disables the Software Configuration Parameters folder and subpages in the Options dialog box. The configuration cannot be viewed.
C About user privileges TABLE 52 Application privileges and behavior (Continued) Privilege Description No Privilege Read-Only Read/Write User Management Allows you to create and define users and groups, as well as assign privileges and views to groups. Disables the Users command on the main Server menu and the Users button on the main tool bar.
About user privileges TABLE 53 C SAN privileges and application behavior Privilege Description No Privilege Read-Only Read/Write SAN - Discovery Setup Allows you to configure discovery setup. Disables Setup on the Discover menu and toolbar. Enables Setup on the Discover menu and toolbar. Allows you to open the Discover Setup dialog box; however, disables all functions. Enables Setup on the Discover menu and toolbar. Enables all functions in the Discover Setup dialog box.
C About user privileges TABLE 53 SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - FICON Management Allows you to configure Cascade FICON Fabric and Cascade FICON Fabric Merge. Also allows you to configure block ports and allow/prohibit matrix on active configuration or any offline configurations. Disables the Configure Fabric, Merge Fabrics commands on the Configure > FICON menu.
About user privileges TABLE 53 C SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - Port Mapping Storage Allows you to construct multi-port storage systems out of individual storage ports. Disables the Storage Port Mapping command from Discover menu and right-click menus for Storage products and ports in the tree and map.
C About user privileges TABLE 53 SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - Storage Encryption Configuration Allows you to configure storage encryption configuration, including selecting storage devices and LUNs, viewing and editing switch, group, or engine properties, viewing and editing storage device encryption properties, and initiating manual LUN re-keying. Disables the Encryption command from the Configure menu.
About user privileges TABLE 53 C SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - Storage Encryption Security Allows you to configure storage encryption security, including creating a new encryption group, adding a switch to an existing group, zeroizing an encryption engine, backing up or restoring a master key, and enabling encryption functions after a power cycle. Disables all functions from the dialog box except view.
C About user privileges TABLE 53 SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - View Management Allows you to create, edit, and delete views. Selecting from views should always be allowed unless restricted by the assignment of Views in the Group definition in the Users dialog box.
About user privileges TABLE 53 C SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - Zoning - Set Edit Limits Allows you to set the number of zoning edit operations that can be performed on a fabric zone database before activating a zone configuration. Disables the Zoning > Set Edit Limits command from the Configure menu. Enables the Zoning > Set Edit Limits command from the Configure menu.
C About user privileges TABLE 53 SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - Zoning Activation (Fabric and offline zone database) Allows you to activate a zone configuration selected in the Zoning dialog box. Disables the Activate, Deactivate, and Zoning Policies buttons in the Zoning dialog box. Enables the Zoning Policies button; however, you cannot perform any operations within the Zoning dialog box.
About user privileges TABLE 53 C SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - Zoning Offline Allows you to edit the zone database in offline mode and save the zone database to the repository or to the switch. In Zoning dialog box, the Zone DB list includes offline zones; however, if an offline zone is selected, the contents are not loaded into the Zoning dialog box.
C About user privileges TABLE 53 SAN privileges and application behavior (Continued) Privilege Description No Privilege Read-Only Read/Write SAN - Zoning Online Allows you to edit any of the fabric zone databases in the available fabrics within the Zoning dialog box from the client side and then save to the switch. In Zoning dialog box, the Zone DB list includes online and offline zones; however, if an online zone is selected, the contents are not loaded into the Zoning dialog box.
About Roles and Access Levels C About Roles and Access Levels The Management application provides pre-configured roles (SAN System Administrator, IP System Administrator, Security Administrator, Zone Administrator, Security Officer, Operator, and Network Administrator); however, the SAN System Administrator can also create roles manually (refer to “Creating a new role” on page 148 for instructions.) • Application Features and Role Access Levels . . . . . . . . . . . . . . . . . . . . . . .
C About Roles and Access Levels TABLE 54 Application Features and Role Access Levels (Continued) Feature Roles with Read/Write Access Roles with Read-Only Access Server Software Configuration SAN System Administrator Operator Setup Tools SAN System Administrator Operator Technical Support Data Collection SAN System Administrator Operator User Management SAN System Administrator, Security Officer Operator Virtual Network Management SAN System Administrator Operator VLAN Manager SAN Sys
About Roles and Access Levels TABLE 55 C SAN Features and Role Access Levels (Continued) Feature Roles with Read/Write Access Roles with Read-Only Access SAN- Storage Encryption Configuration SAN System Administrator,, Security Operator SAN- Storage Encryption Key Operations SAN System Administrator, Security Administrator, Security Officer SAN- Storage Encryption Security SAN System Administrator, Security Administrator Operator SAN- Troubleshooting SAN System Administrator SAN- View Manage
C 982 About Roles and Access Levels Brocade Network Advisor SAN User Manual 53-1002167-01
Appendix D Regular Expressions This appendix presents a summary of Unicode regular expression constructs that you can use in the Management application. • Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Character classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Pre-defined character classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D Regular Expressions TABLE 57 Construct Matches [abc] a, b, or c (simple class) [^abc] Any character except a, b, or c (negation) [a-zA-Z] a through z or A through Z, inclusive (range) [a-d[m-p]] a through d, or m through p: [a-dm-p] (union) [a-z&&[def]] d, e, or f (intersection) [a-z&&[^bc]] a through z, except for b and c: [ad-z] (subtraction) [a-z&&[^m-p]] a through z, and not m through p: [a-lq-z](subtraction) TABLE 58 Pre-defined character classes Construct Matches .
Regular Expressions TABLE 60 java.lang.Character classes (simple java character type) Construct Matches \p{javaLowerCase} Equivalent to java.lang.Character.isLowerCase() \p{javaUpperCase} Equivalent to java.lang.Character.isUpperCase() \p{javaWhitespace} Equivalent to java.lang.Character.isWhitespace() \p{javaMirrored} Equivalent to java.lang.Character.
D Regular Expressions TABLE 64 Reluctant quantifiers Construct Matches X?? X, once or not at all X*? X, zero or more times X+? X, one or more times X{n}? X, exactly n times X{n,}? X, at least n times X{n,m}? X, at least n but not more than m times TABLE 65 Possessive quantifiers Construct Matches X?+ X, once or not at all X*+ X, zero or more times X++ X, one or more times X{n}+ X, exactly n times X{n,}+ X, at least n times X{n,m}+ X, at least n but not more than m times TAB
Regular Expressions TABLE 68 Special constructs (non-capturing) Construct Matches (?:X) X, as a non-capturing group (?idmsux-idmsux) Nothing, but turns match flags on–off (?idmsux-idmsux:X) X, as a non-capturing group with the given flags on–off (?=X) X, through zero-width positive lookahead (?!X) X, through zero-width negative lookahead (?<=X) X, through zero-width positive lookbehind (?X) X, as an independent, non-capturing group Broca
D 988 Regular Expressions Brocade Network Advisor SAN User Manual 53-1002167-01
Appendix Database Fields E In this appendix Tables • Advanced Call Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991 • Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992 • Client_view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994 • Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E In this appendix • Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074 • User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077 • Zoning 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080 Views • BOOT_IMAGE_FILE_DETAILS_INFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • CEE_PORT_INFO . . . . . . . . . . . . .
E Database tables and fields • ROLE_PRIVILEGE_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SCOM_EE_MONITOR_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SENSOR_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SMART_CARD_USAGE_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SWITCH_DETAILS_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E Database tables and fields TABLE 71 ACH_EVENT_FILTER_MAP Field Definition Format FILTER_ID * ID of the event filter. int EVENT_ID * Event ID which needs to be associated with the filter. int Definition Format TABLE 72 Size ACH_EVENT Field ID * Size int REASON_CODE Reason code of the event. varchar 256 FRU_CODE FRU code of the event. varchar 256 DESCRIPTION Description of the event. varchar 256 SEVERITY Severity of the event. int TYPE Type of the event.
E Database tables and fields TABLE 76 CARD_CAPABILITY Field Definition Format CARD_ID * DB ID of the card. int CAPABILITY_ * Name of the capability detected on the card. varchar ENABLED 1 = the capability is enabled on the card. Default value is 0. int TABLE 77 256 VIRTUAL_SWITCH_CAPABILITY Field Definition Format VIRTUAL-SWITCH_ID * DB ID of virtual switch. int CAPABILITY_ * Name of capability detected on virtual switch.
E Database tables and fields TABLE 78 CARD (Continued) Field Definition Format FCIP_CIRCUIT_CAPABLE The blade is capable of creating FCIP Circuits. 1 = true. 0 = false. Default value is 0. smallint FCIP_LICENSED FCIP Advanced Extension Licensing is available. 1 = available. 0 = not licensed. -1 = not supported. Default value is -1. smallint MAX_FCIP_TUNNELS The maximum number of tunnels that can be created in this slot. -1 = not supported. Default value is -1.
E Database tables and fields TABLE 80 USER_ (Continued) Field Definition Format NOTIFICATION_ENABLED Flag for e-mail notification. Default value is 0. smallint FULL_NAME User''s Full Name. varchar 512 PHONE_NUMBER User''s Phone number. varchar 32 INVALID_LOGIN_COUNT This is a counter filed to identify the number of invalid smallint login attempts. Note: After successful login this filed will be set to NULL. Default value is 0.
E Database tables and fields TABLE 83 CLIENT_VIEW_COLUMN (Continued) Field Definition Format Size ENTITY_CATEGORY Either "fabric" or "product (switch or device)" or "port"; or combination of these 3 basic categories. Default value is 0. varchar 128 COLUMN_INDEX 0 = Predefined column. 1 = First user-defined column. 2 = Second user-defined column. 3 = Third user-defined column. Default value is 0. small int DESCRIPTION Column description, typically populated for user-defined columns.
E Database tables and fields TABLE 85 FABRIC (Continued) Field Definition Format MANAGEMENT_STATE Bit map to indicate various management indications for the fabric. smallint TRACK_CHANGES 1 = changes (member switches, ISL and devices) in the fabric are tracked. smallint STATS_COLLECTION 1 = statistics collection is enabled on the fabric. smallint CREATION_TIME When the fabric record is inserted, i.e., created. timestamp LAST_FABRIC_CHANGED Time when fabric last changed.
E Database tables and fields TABLE 88 COLLECTOR Field Definition Format Size NAME * Name of the collector registered with the collection framework. varchar 256 CLASS_NAME Java class name which serves as the collector. varchar 256 DESCRIPTION Collector description, usually not used. varchar 512 TABLE 89 FABRIC Field Definition Format ID * int SAN_ID Foreign key to SAN table; usually 1 since there is only one SAN.
E Database tables and fields TABLE 90 COLLECTOR_END_TIMESTAMP Field Definition Format Size COLLECTOR_SOURCE * Internal key for switches and fabrics for which collection is undertaken. varchar 256 COLLECTOR_NAME * Collection name, Java class used to collect specific fabric or switch information. varchar 256 TIMESTAMP_ When the last successful collection is done. timestamp LAST_COLLECTED_STATUS Status of the last collection, successful or not. 200 is for successful.
E Database tables and fields TABLE 95 SECURITY_POLICY (Continued) Field Definition Format Size POLICY_TYPE* Type of the Policy. The possible values are IKE or IPSec smallint ENCRYPTION_ALGORITHM Encryption Algorithm for the policy.The following are the possible Encryption: NONE,DES,3DES,AES-128,AES-256,AES-CM-128 or AES-CM-256.
E Database tables and fields TABLE 97 FIRMWARE_FILE_DETAIL (Continued) Field Definition Format Size FIRMWARE_LOCATION Firmware file location in the Management applciation repository. varchar 1024 RELEASE_NOTES_ LOCATION Release notes file location in theManagement applciation repository. varchar 1024 FIRMWARE_REPOSITORY_ TYPE Repository type to identify the FTP server: 0 = internal FTP. 1 = external FTP.
E Database tables and fields TABLE 101 SWITCH_CONFIG (Continued) Field Definition Format Size BACKUP_DATE_TIME The date/time stamp at which the configuration has been uploaded. timestamp CONFIG_DATA The actual switch configuration data. text CEE_CONFIG_DATA Switch configuration data for CEE text KEEP_COPY The column value (1) helps to preserve the configuration even after the expiration of its age.
E Database tables and fields Device TABLE 105 DEVICE_PORT Field Definition ID* Format Size int NODE_ID DB ID of the device node to which this port belongs. int DOMAIN_ID Domain ID of the switch to which this device port is attached. int WWN Device port WWN. char 23 SWITCH_PORT_WWN WWN of the switch port to which this device port is attached. char 23 NUMBER Switch port number to which this device is attached. smallint PORT_ID Device port ID.
E Database tables and fields TABLE 106 FICON_DEVICE_PORT Field Definition Format DEVICE_PORT_ID* Value for the device port to which these FICON properties are applied. int TYPE_NUMBER varchar 16 MODEL_NUMBER Ficon device model number, such as S18. varchar 64 MANUFACTURER Manufacturer of the device, typically IBM. varchar 64 MANUFACTURER_PLANT Plant number where the device is manufactured. varchar 64 SEQUENCE_NUMBER Device sequence number.
E Database tables and fields TABLE 107 DEVICE_NODE (Continued) Field Definition Format AG 1 = the device node is actually an AG connected to a switch in the fabric. Default value is 0. smallint PREVIOUS_MISSING_STAT E Default value is 0. smallint TABLE 108 DEVICE_ENCLOSURE_MEMBER Field Definition Format ENCLOSURE_ID* DEVICE_ENCLOSURE table ID. int DEVICE_PORT_WWN* WWN Of Device Port. char DEVICE_PORT_ID Device_Port table ID.
E Database tables and fields TABLE 109 DEVICE_ENCLOSURE (Continued) (Continued) Field Definition Format TRACK_CHANGES Flag to enable/disable tracking. Default value is 0. smallint LAST_UPDATE_TIME Last time at which the host information was updated. timestamp LAST_UPDATE_MODULE Module which updated the host information. smallint TRUSTED Flag to mark the enclosure trusted. Default value is 0. smallint CREATION_TIME Time when enclosure was created. Default is ’now()’.
E Database tables and fields TABLE 110 FABRIC (Continued) Field Definition Format AD_ENVIRONMENT 1 = there are user-defined ADs in this fabric. smallint MANAGED 1 = it is an actively "monitored" fabric; otherwise, it is an "unmonitored" fabric. smallint MANAGEMENT_STATE Bit map to indicate various management indications for the fabric. smallint TRACK_CHANGES 1 = changes (member switches, ISL and devices) in the fabric are tracked.
E Database tables and fields TABLE 115 EE_MONITOR_STATS (Continued) Field Definition Format CREATION_TIME The polling time. timestamp ACTIVE_STATE State of collection 0 = failed 1 = success smallint TX Transmit (TX) value in bytes. double precision RX Receive (RX) value in bytes. double precision CRCERRORS Number of CRC errors.
E Database tables and fields TABLE 118 EE_MONITOR (Continued) Field Definition Format DEST_PORT_ID References the ID in DEVICE_PORT table and this is a target for EE monitor. int NAME Name of the End_End Monitor. varchar ERROR CODE Error code returned from the switch, when enabling End-End monitor is attempted on the switch. int STATUS Status of creating the End-End monitor on the switch. It can be either failed or succeeded.
E Database tables and fields TABLE 123 MESSAGE_RECIPIENT Field Definition Format ID* int DESCRIPTION Description about recipient. varchar 256 IP_ADDRESS IP Address of the recipient. varchar 128 PORT Port number of the recipient. int RECIPIENT_TYPE_ID Recipient Type (Syslog or SNMP). int ENABLED If forwarding to destination is enabled. smallint SOURCE_ADDRESS_ADD ED If source address is added as another varbind in trap. -1 for Syslog i.e RECIPIENT_TYPE_ID: 2. Default value is -1.
E Database tables and fields TABLE 125 SNMP_CREDENTIALS (Continued) Field Definition Format Size WRITE_COMMUNITY_ STRING The SNMP Write-Only Community String is like a password. It is sent along with each SNMP Set-Request and allows (or denies) access to device. The default value is "private". This is applicable if the agent is configured to operate in SNMPv1. varchar 64 USER_NAME A human-readable string representing the name of the user.
E Database tables and fields TABLE 126 SYSLOG_EVENT (Continued) Field Definition Format EVENT_NUMBER Sequence number of the event. int EVENT_COUNT Number of occurrences of the event. int AUDIT Audit file of the syslog message. varchar FIRST_OCCURENCE_ SWITCH_TIME First occurrence switch time. timestamp LAST_OCCURENCE_ SWITCH_TIME Last occurrence switch time. timestamp FIRST_OCCURENCE_ HOST_TIME Last occurrence switch time.
E Database tables and fields TABLE 127 EVENT (Continued) Field Definition Format EVENT_COUNT Number of occurrences of the event.. Default value is 1. int RESOLVED Resolution status of the event. Default value is 0. smallint ACKED_TIME Time at which the event is acknowledged. Timestamp Size FIRST_OCCURRENCE_HOST First occurrence host time; this is set to GMT time. _TIME timestamp 10 EVENT_AUDIT Flag to indicate if the event is audited.
E Database tables and fields TABLE 129 EVENT_NOTIFICATION (Continued) Field Definition Format Size USER_NAME User name for authentication. varchar 256 PASSWORD Password for authentication. varchar 256 NOTIFICATION_INTERVAL Time interval between successive event notifications. int NOTIFICATION_UNIT Time interval Unit: 0 = Seconds 1 = Minutes 2 = Hours Default value is 0. smallint TEST_OPTION Time interval Unit: 0 = Send test to configured e-mail address.
E Database tables and fields TABLE 130 EVENT_RULE (Continued) Field Definition Format SEVERITY_LEVEL Event severity level. Default value is 4. int SOURCE_NAME Name of the source. varchar 1024 DESCRIPTION_CONTAINS Description pattern about the rule. varchar 255 LAST_MODIFIED_TIME Rules last edited time. timestamp SELECTED_TIME_UNIT Timestamp unit of the selected rule: 0 = second 1 = Minutes 2 = Hours Default value is 1.
E Database tables and fields TABLE 132 SAN (Continued) Field Definition Format STATS_COLLECTION 1 = statistics collection is enabled; otherwise, 0. Default value is 0. smallint CREATION_TIME time at which this record was created. Default value is ’now()’. timestamp LAST_UPDATE_TIME time when this was last updated. Default value is ’now()’. timestamp TABLE 133 FABRIC Field Definition Format ID* Size int SAN_ID Foreign key to SAN table; usually 1 since there is only one SAN.
E Database tables and fields TABLE 133 FABRIC (Continued) Field Definition Format LAST_UPDATE_TIME Time when fabric was last updated. Default value is ’now()’. timestamp ACTIVE_ZONESET_NAME Name of the zone configuration which is effective / active in that fabric. varchar 256 USER_DEFINED_VALUE_1 User-defined custom value. varchar 256 USER_DEFINED_VALUE_2 User-defined custom value. varchar 256 USER_DEFINED_VALUE_3 User-defined custom value.
E Database tables and fields FC Port Stats TABLE 136 FC_PORT_STATS Field Definition ID* References the ID in CORE_SWITCH table. int PORT_ID References the ID in SWITCH_PORT table. int TX Transmission (TX) value in bytes. double precision. RX Receive (RX) value in bytes. double precision. TX_UTILIZATION Transmit utilization value in percentage. double precision. RX_UTILIZATION Receive utilization value in percentage. double‘ precision. CREATION_TIME The polling time.
E Database tables and fields TABLE 137 FC_PORT_STATS_30MIN (Continued) Field Definition Format RX double precision. TX_UTILIZATION double precision. RX_UTILIZATION double precision. CREATION_TIME timestamp ACTIVE_STATE smallint LINKFAILURES double precision. TXLINKRESETS double precision. RXLINKRESETS double precision. SYNCLOSSES double precision. SIGNALLOSSES double precision. SEQUENCEERRORS double precision. INVALIDTRANSMISSIONS double precision. CRCERRORS double precision.
E Database tables and fields TABLE 138 FC_PORT_STATS_2HOUR (Continued) Field Definition LINKFAILURES double precision. TXLINKRESETS double precision. RXLINKRESETS double precision. SYNCLOSSES double precision. SIGNALLOSSES double precision. SEQUENCEERRORS double precision. INVALIDTRANSMISSIONS double precision. CRCERRORS double precision.
E Database tables and fields TABLE 139 FC_PORT_STATS_1DAY (Continued) Field Definition Format SIGNALLOSSES double precision. SEQUENCEERRORS double precision. INVALIDTRANSMISSIONS double precision. CRCERRORS double precision.
E Database tables and fields FCIP TABLE 140 FCIP_TUNNEL Field Definition Format ID* int ETHERNET_PORT_ID GigE Port ID on which the tunnel is created. int TUNNEL_ID Tunnel ID for that GigE Port. smallint VLAN_TAG VLAN Tag on the tunnel (if present). int SOURCE_IP Source IP on which the tunnel is created. char 64 DEST_IP Destination IP on the other end of tunnel. char 64 LOCAL_WWN Local port WWN for the tunnel. char 23 REMOTE_WWN_RESTRICT Remote Port WWN for the tunnel.
E Database tables and fields TABLE 143 FCIP_TUNNEL_DETAILS (Continued) Field Definition Format FICON_TIN_TIR_ EMULATION_ENABLED Whether Ficon_Tin_Tir_Emulation is enabled on that tunnel. smallint FICON_DEVICE_LEVEL_ ACK_EMULATION_ENABLED Whether Device_Level_Ack_Emulation is enabled on that tunnel. smallint FICON_TAPE_WRITE_MAX_ PIPE The value for this on the tunnel. int FICON_TAPE_READ_MAX_ PIPE The value for this on the tunnel.
E Database tables and fields TABLE 144 FCIP_TUNNEL_STATS (Continued) Field Definition Format ACTIVE_STATE State of collection: 0 = failed 1 = success smallint RTT_BY_TO Counter of retransmit packet by timeout. double precision RTT_BY_DUP_ACK Counter of retransmit packet by duplicate Ack.
E Database tables and fields TABLE 146 FCIP_TUNNEL_STATS_2HOUR (Continued) Field Definition Format CREATION_TIME timestamp TX double precision RX double precision TX_UTILIZATION double precision RX_UTILIZATION double precision DROPPED_PACKETS double precision COMPRESSION double precision LATENCY double precision LINK_RETRANSMITS double precision ACTIVE_STATE smallint RTT_BY_TO Counter of retransmit packet by timeout.
E Database tables and fields TABLE 147 1026 FCIP_TUNNEL_STATS_1DAY (Continued) Field Definition Format TCP_OOO Counter of TCP out of order double precision SLOW_START SlowStart status from stage 1 to 8 double precision Size Brocade Network Advisor SAN User Manual 53-1002167-01
E Database tables and fields GigE Port Stats TABLE 148 FCIP_TUNNEL Field Definition ID* Format Size int TUNNEL_ID Tunnel ID for that GigE Port. smallint VLAN_TAG VLAN Tag on the tunnel (if present). Default value is -1. int SOURCE_IP Source IP on which the tunnel is created. char 64 DEST_IP Destination IP on the other end of tunnel. char 64 LOCAL_WWN Local port WWN for the tunnel. char 23 REMOTE_WWN_RESTRICT Remote Port WWN for the tunnel.
E Database tables and fields TABLE 148 1028 FCIP_TUNNEL (Continued) Field Definition Format FICON_TAPE_WRITE_TIMER The Value for FICON_TAPE_WRITE_TIMER on the tunnel. Default value is -1. int FICON_TAPE_MAX_WRITE_ CHAIN The Value for FICON_TAPE_MAX_WRITE_CHAIN on the tunnel. Default value is -1. int FICON_OXID_BASE The Value for FICON_OXID_BASE on the tunnel. Default value is -1. int FICON_XRC_EMULATION_E NABLED Whether Xrc_Emulation is enabled on that tunnel. Default value is 0.
E Database tables and fields TABLE 148 FCIP_TUNNEL (Continued) Field Definition Format TPERF_ENABLED Is Tperf enabled. Default: 0, Values: 0|1. Default value is 0. smallint AUTH_KEY This is the preshared-key to be used during IKE authentication. varchar CONNECTED_COUNT Active connections count. Default value is 1. smallint TUNNEL_STATUS_STRING Tunnel Status string value from switch for the tunnel. varchar COMPRESSION_MODE Compression mode value (0,1,2,3). Default value is 0.
E Database tables and fields TABLE 150 GIGE_PORT_STATS_30MIN (Continued) Field Definition TX double precision RX double precision TX_UTILIZATION double precision RX_UTILIZATION double precision DROPPED_PACKETS double precision COMPRESSION double precision LATENCY double precision BANDWIDTH double precision TABLE 151 Definition Format ID* int SWITCH_ID int PORT_ID int CREATION_TIME timestamp TX double precision RX double precision TX_UTILIZATION double precision RX_UTIL
E Database tables and fields TABLE 152 GIGE_PORT_STATS_1DAY (Continued) Field Definition Format LATENCY double precision BANDWIDTH double precision TABLE 155 ISL Field Definition ID* Format Size int FABRIC_ID Fabric DB ID. int SOURCE_DOMAIN_ID Source domain ID. int SOURCE_PORT_NUMBER Source port number. smallint DEST_DOMAIN_ID Destination domain ID. int DEST_PORT_NUMBER Destination port number. smallint COST The cost of the link. int TYPE The type of link.
E Database tables and fields TABLE 156 FABRIC (Continued) Field Definition Format MANAGED 1 = it is an actively "monitored" fabric; otherwise, it is an "unmonitored" fabric. smallint MANAGEMENT_STATE Bit map to indicate various management indications for the fabric. smallint TRACK_CHANGES 1 = changes (member switches, ISL and devices) in the fabric are tracked. smallint STATS_COLLECTION 1 = statistics collection is enabled on the fabric.
E Database tables and fields TABLE 160 LICENSED_FEATURE Field Definition ID* Format Size int NAME License feature name, a short text description. varchar 64 DESCRIPTION Optional detailed description about the license feature. varchar 256 Format Size TABLE 161 SWITCH_LICENSE Field Definition ID* int CORE_SWITCH_ID Refers to the entry in the CORE_SWITCH table. int LICENSE_KEY Stores the license key obtained from the switch.
E Database tables and fields TABLE 162 1034 CORE_SWITCH (Continued) Field Definition Format Size LAST_UPDATE_TIME 1 = the Management application server is registered with the switch to receive Syslog. Default is ’now()’. timestamp SYSLOG_REGISTERED 1 = Syslog is enabled for this switch. Default value is 0. smallint CALL_HOME_ENABLED 1 = call home is enabled for this switch. Default value is 1.
E Database tables and fields Encryption Device TABLE 163 KEY VAULT Field Definition ID* Format Size int IP_ADDRESS The IP Address (IPv4, IPv6, or hostname) of the key vault. varchar PORT_NUMBER The TCP port number for the key vault. int PUBLIC_CERTIFICATE The key vault’s public key certificate. Switches use varchar this to establish a secure connection to the key vault. 4096 CRETIFICATE_LABEL A text name to identify the certificate.
E Database tables and fields TABLE 164 CRYPTO_SWITCH (Continued) Field Definition Format Size CP_CERTIFICATE The public key certificate, in PEM format, of the switch’s Control Processor module. This certificate is exchanged with other switches to establish secure communication between switches in an Encryption Group. varchar 4096 KAC_CERTIFICATE The public key certificate, in PEM format, of the switch’s Key Archive Client module.
E Database tables and fields TABLE 165 ENCRYPTION GROUP (Continued) Field Definition Format SYSTEM_CARD_REQUIRED Boolean value that indicates whether a System Card (smart card) must be inserted in the Encryption Engine to enable the engine after power-up. This feature is not yet supported. smallint ACTIVE_MASTER_KEY_STAT US The operational status of the "master key" or "Key Encryption Key (KEK)" used to encrypt Data Encryption Keys in a key vault. Not used for NetApp LKM key vaults.
E Database tables and fields TABLE 166 ENCRYPTION_TAPE_POOL (Continued) Field Definition Format ENCRYPTION_GROUP_ID Foreign key reference to the ENCRYPTION_GROUP record that describes which Encryption Group this tape pool belongs to. int TAPE_POOL_NAME User-supplied name or number for the tape pool. This is the same name or number specified in the tape backup application. Numbers are stored in hex.
E Database tables and fields TABLE 168 ENCRYPTION_GROUP_MEMBER (Continued) Field Definition Format Size MEMBER_WWN The Node WWN of the member switch. char 23 MEMBER_STATUS The reachability status of the member switch as seen by the group leader switch. For possible values see the enum definition in the DTO class. Default value is 0.
E Database tables and fields TABLE 171 SMART CARD Field Definition Format Size GROUP_NAME The name of the Encryption Group used to initialize the card. For recovery set cards, this identifies which group’s master key is backed up on the card. varchar 64 CREATION_TIME The date and time that the card was initialized. For recovery set cards, this is the date and time the master key was written to the card.
E Database tables and fields Encryption Container TABLE 173 CRYPTO HOST Field Definition ID* Format Size int CRYPTO_TARGET_CONTAIN ER_ID Foreign key reference to the int CRYPTO_TARGET_CONTAINER that contains this host. VI_NODE_WWN Node WWN of Virtual Initiator that represents this host. char 23 VI_PORT_WWN Port WWN of Virtual Initiator that represents this host.
E Database tables and fields TABLE 175 1042 CRYPTO LUN (Continued) Field Definition Format Size SERIAL_NUMBER The LUN serial number, used to identify the physical LUN. varchar 64 ENCRYPTION_STATE Boolean. True (1) if LUN is being encrypted. False (0) if cleartext. smallint STATUS Not currently used but left in for possible future use. Replaced by LUN_STATE. smallint REKEY_INTERVAL The number of days that data encryption keys should be used before automatically generating a new key.
E Database tables and fields TABLE 175 CRYPTO LUN (Continued) Field Definition Format CRYPTO_HOST_ID Foreign key reference to the CRYPTO_HOST that uses this LUN. int LUN_NUMBER The Logical Unit Number of the LUN, as seen by the LUNs host. This may be an integer (0 - 65565) or a WWN-format 8-byte hex number. varchar BLOCK_SIZE 'The LUN's Logical Block Size, in bytes. Only valid for disk LUNs. int TOTAL_BLOCKS The total number of logical blocks in the LUN.
E Database tables and fields TABLE 176 1044 ENCRYPTION ENGINE (Continued) Field Definition Format Size SP_CERTIFICATE The public key certificate, in PEM format, for the Security Processor within the Encryption Engine. Used to create link keys for NetApp LKM key vaults. varchar 4096 EE_STATE The operational status of this Encryption Engine. For possible values, see the enum definition in the DTO class.
E Database tables and fields Meta SAN TABLE 179 LSAN_DEVICE Field Definition ID* Format Size int BB_FABRIC_ID Backbone fabric DB ID. int FCR_FABRIC_ID FID assigned to edge fabric. int DEVICE_PORT_WWN Device port WWN of physical device. char 23 PHYSICAL_PID PID of physical device.
E Database tables and fields TABLE 182 FABRIC (Continued) Field Definition Format TYPE Type of fabric: 0 = legacy fabric 1 = base fabric 2 = logical fabric smallint SECURE 1 = it is a secured fabric. smallint AD_ENVIRONMENT 1 = there are user-defined ADs in this fabric. smallint MANAGED 1 = it is an actively "monitored" fabric; otherwise, it is an "unmonitored" fabric. smallint MANAGEMENT_STATE Bit map to indicate various management indications for the fabric.
E Database tables and fields Network TABLE 185 IP_INTERFACE Field Definition ID* Format Size int ETHERNET_PORT_ID GigE Port ID. int IP_ADDRESS IP address on the Ip_interface. varchar 64 NET_MASK Subnet mask for the interface. varchar 64 MTU_SIZE MTU Size for that interface. int CHECKSUM Check Sum. varchar 64 Definition Format Size TABLE 186 IP_ROUTE Field ID* int ETHERNET_PORT_ID GigE Port ID. int PORT_NUMBER Port Number related to the GigE Port.
E Database tables and fields TABLE 189 OUI_GUESSED_DEVICE_MAP Field Definition Format Size OUI* Vendor OUI. char 6 TYPE Guessed device type for this vendor. varchar 32 Field Definition Format Size FEATURE_ID* ID used to uniquely identify the feature. int 6 NAME Name of the feature. varchar 256 DESCRIPTION Description for the feature.
E Database tables and fields TABLE 193 PORT_FENCING_POLICY_MAP Field Definition ID* Format Size int POLICY_ID Foreign key to ID column of PORT_FENCING_POLICY table. int LEVEL 0 = All Fabric 1 = Fabric 2 = Core Switch Group 3 = Switch 4 = Port Type 5 = Port List smallint SUB_LEVEL 1 = E_Port 2 = F_Port 3 = FL_Port, Fabric WWN, Switch WWN char 23 NODE WWN of Node which policy assigned. char 23 INHERITANCE Directly assigned or inherited from root level.
E Database tables and fields TABLE 195 QRTZ_TRIGGERS (Continued) Field Definition Format Size JOB_GROUP Name of the job group. varchar 80 IS_VOLATILE Whether the trigger should be persisted in the JobStore for re-use after program restarts. boolean DESCRIPTION A description for the trigger instance - may be useful for remembering/displaying the purpose of the trigger, though the description has no meaning to Quartz. varchar 120 NEXT_FIRE_TIME The next fire time in milliseconds.
E Database tables and fields TABLE 197 QRTZ_FIRED_TRIGGERS (Continued) Field Definition Format IS_STATEFUL Whether the job implements the interface StatefulJob. boolean REQUESTS_RECOVERY True or false. boolean TABLE 198 size QRTZ_JOB_LISTENERS Field Definition Format Size JOB_NAME* Name of the job. varchar 80 JOB_GROUP* Name of the job group. varchar 80 JOB_LISTENER* Job listener action class instance.
E Database tables and fields TABLE 203 QRTZ_LOCKS Field Definition Format Size LOCK_NAME* Resource identification name assigned by user. varchar 40 TABLE 204 QRTZ_CALENDARS Field Definition Format Size CALENDAR_NAME* Name of the Calendar. varchar 80 CALENDAR Calendar object. bytea TABLE 205 QRTZ_PAUSED_TRIGGER_GRPS Field Definition Format Size TRIGGER_GROUP* Name of the trigger group. varchar 80 Field Definition Format Size ID* Meta Data for available reports.
E Database tables and fields TABLE 209 ROLE Field Definition ID* Format Size int NAME Role name. varchar 128 DESCRIPTION Role description. varchar 512 HIDDEN Field to identify whether the role is Hidden from users or not. Values: 0= Not Hidden 1= Hidden Currently, only ''All Users'' Role is hidden and other roles are visible to user. Default value is 0. smallint TABLE 210 ROLE_PRIVILEGE_MAP Field Definition Format ROLE_ID* User role ID. int PRIVILEGE_ID* Privilege ID.
E Database tables and fields TABLE 215 USER_ Field Definition Format ID * int NAME User name. varchar 128 DESCRIPTION User description. varchar 512 PASSWORD User password. varchar 512 EMAIL User e-mail ID. varchar 1024 NOTIFICATION_ENABLED Flag for e-mail notification. Default value is 0. smallint FULL_NAME User''s Full Name. varchar 512 PHONE_NUMBER User''s Phone number.
E Database tables and fields TABLE 218 RESOURCE_FABRIC_MAP Field Definition Format RESOURCE_GROUP_ID* Resource group ID. int FABRIC_ID* Fabric ID, which is in the resource group.
E Database tables and fields SNMP TABLE 220 SNMP_CREDENTIALS Field Definition Format ID* 1056 Size int VIRTUAL SWITCH_ID Virtual switch ID for which this instance of the SNMP credentials apply. int RECIPIENT_ID Recipient in the MESSAGE_RECIPIENT table. int POR)_NUMBER Port number of the SNMP agent on the switch for get and set requests. smallint RETRY_COUNT Number of times to retry if get/set request to the SNMP agent times out. Default value is 3.
E Database tables and fields TABLE 220 SNMP_CREDENTIALS (Continued) Field Definition Format Size PRIV_PROTOCOL An indication of whether messages sent or received on behalf of this user can be encrypted and if so, which privacy protocol to use. The current values for this field are: usmNoPrivProtocol and usmDESPrivProtocol. This is applicable if the agent is configured to operate in SNMPv3.
E Database tables and fields TABLE 221 SNMP_PROFILE (Continued) Field Definition Format Size AUTH_PROTOCOL An indication of whether or not messages sent or received on behalf of this user can be authenticated and if so, which authentication protocol to use. The supported values for this field are: usmNoAuthProtocol, usmHMACMD5AuthProtocol, and usmHMACSHAAuthProtocol. This is applicable if the agent is configured to operate in SNMPv3.
E Database tables and fields Stats TABLE 223 FAVORITES Field Definition ID* Format Size int NAME Name of the favorite. varchar 64 USER_ The application user credentials. varchar 128 TOP_N The top number of ports(5,10,15,20). varchar 40 SELECTION_FILTER Types of ports (FC/FCIP/GE) and -End Monitors. varchar 40 FROM_TIME The time interval in which the graph is shown. Time interval can be predefined or custom.
E Database tables and fields TABLE 224 USER_ (Continued) Field Definition Format LOCKED_OUT_DATETIME The date time stamp when a user got locked out because of exceeding max number of invalid login attempts. timestamp STATUS User''s account status: 0=Disabled 1=Enabled Default value is 1. smallint SOURCE_OF_CREATION To identify the source for creating the user account. 0= User created through Management applciation Client 1= User created when authenticated through external server.
E Database tables and fields TABLE 227 DEFAULT_FAVORITES (Continued) Field Definition Format Size TOP_N Types of ports (FC/FCIP/GE) and -End Monitors. varchar 40 SELECTION_FILTER The time interval in which the graph is shown. varchar 40 FROM_TIME Always null. The default favorite is not customized. varchar 40 CUSTOM_LAST_VALUE Always null. The default favorite is not customized. int CUSTOM_TIME_UNIT Always null. The default favorite is not customized.
E Database tables and fields Switch TABLE 228 VIRTUAL-SWITCH Field Definition Format ID* 1062 Size int LOGICAL_ID Logical ID of the switch. smallint NAME Switch name. varchar 64 WWN WWN of the switch. char 23 VIRTUAL_FABRIC_ID Virtual fabric ID. If VF enabled then will have the VFID; otherwise it will be -1. smallint DOMAIN_ID Domain ID of the switch. smallint BASE_SWITCH 1 = this is a base switch; otherwise, 0. smallint SWITCH_MODE 2 = switch is in AG mode; otherwise, 0.
E Database tables and fields TABLE 229 CORE_SWITCH Field Definition ID* Format Size int IP_ADDRESS IP address of the switch. varchar 128 WWN Chassis WWN. char 23 NAME Switch name. varchar 64 TYPE SWBD type number as given by Fabric OS. Default value is 0. smallint MODEL Model type of the switch: 0 = Unknown 1 = Not applicable 2 = Fabric OS switch 3 = M-EOS switch smallint FIRMWARE_VERSION Embedded (Fabric OS or M-EOS) software version. varchar 128 VENDOR Switch vendor.
E Database tables and fields TABLE 229 CORE_SWITCH (Continued) Field Definition Format NIC_PROFILE_ID NIC profile of the Management application server host used by this switch to communicate in interactive configuration and other operations. It determines which Management application host IP used by this switch. int MANAGING_SERVER_IP_ ADDRESS IP address(v4/v6) of the Management applciation server which is currently managing the M-model switch. Used for M-EOS switch only.
E Database tables and fields TABLE 232 SWITCH_MODEL (Continued) Field Definition Format Size DESCRIPTION Model description, such as FC link speed, port count and whether multi-card (director) class switch or other type of switch. Default is ‘Not Available’. varchar 256 MODEL Switch model string. varchar 32 REMARK Remarks, such as an internal project name. varchar 64 TABLE 233 PURGED_SWITCH Field Definition Format Size WWN* WWN of the switch. char 23 NAME Name of the switch.
E Database tables and fields TABLE 234 1066 CORE_SWITCH_DETAILS (Continued) Field Definition Format Size FC_MASK Subnet mask for FC IP. char 64 FC_IP Fibre Channel IP address. char 64 FC_CERTIFICATE smallint SW_LICENSE_ID char 23 SUPPLIER_SERIAL_ NUMBER Serial number of the chassis. varchar 32 PART_NUMBER The part number assigned by the organization responsible for producing or manufacturing the PhysicalElement. varchar 32 CHECK_BEACON 1 = beacon is turned on; otherwise, 0.
E Database tables and fields TABLE 234 CORE_SWITCH_DETAILS (Continued) Field Definition Format Size MAX_NUM_OF_BLADES Required by SMIA to populate Brocade_Chassis.MaxNumOfBlades property. It indicates the max no of blades that can be present in a chassis. smallint VENDOR_VERSION Required by integrated SMI agent to populate Brocade_Product.Version property. varchar 32 VENDOR_PART_NUMBER Required by integrated SMI agent to populate Brocade_Product.SKUNumber property.
E Database tables and fields TABLE 235 1068 CORE_SWITCH (Continued) Field Definition Format Size CREATION_TIME Time when this record was created by the Management application. Default is ’now()’. timestamp LAST_SCAN_TIME Time when this record was last updated. timestamp LAST_UPDATE_TIME 1 = the Management application server is registered with the switch to receive Syslog. Default is ’now()’. timestamp SYSLOG_REGISTERED 1 = Syslog is enabled for this switch. Default value is 0.
E Database tables and fields Switch port TABLE 237 GIGE_PORT Field Definition ID* Format Size int SWITCH_PORT_ID ID for the GigE Port in SWITCH_PORT. int PORT_NUMBER GigE Port Number(0 for ge0 and 1 for ge1). int SLOT_NUMBER Slot number on which the GigE Port is present. int ENABLED Enabled or disabled. Default value is 0. smallint SPEED Port speed details. Default value is 0. bigint MAX_SPEED Port maximum speed supported. bigint MAC_ADDRESS MAC Address of that port.
E Database tables and fields TABLE 238 SWITCH_PORT (Continued) Field Definition Format PORT_NUMBER The logical port number of the user port. There is no assumption of any relation to the physical location of a port within a chassis. smallint USER_PORT_NUMBER User port number. Unique port number in a chassis. smallint PORT_ID Port ID of this port. varchar PORT_INDEX Number used for identifying port in zoning. smallint AREA_ID Area number the port is assigned to.
E Database tables and fields TABLE 238 SWITCH_PORT (Continued) Field Definition Format PERSISTENT_DISABLE 1 = port is persistently disabled. smallint FICON_SUPPORTED 1 = FICON is supported; otherwise, 0. smallint BLOCKED 1 = port is blocked; otherwise, 0. smallint PROHIBIT_PORT_NUMBERS varchar PROHIBIT_PORT_COUNT smallint NPIV Whether NPIV mode is enabled.
E Database tables and fields TABLE 238 SWITCH_PORT (Continued) Field Definition Format LOGICAL_PORT_NUMBER F-Port trunk logical port number. Default value is -1. smallint DEFAULT_AREA_ID Default Area id of F-Port trunk port. Default value is -1. smallint LOGICAL_PORT_WWN Logical port WWN of F-Port trunk group. char 23 PREVIOUS_TYPE This fields copies the old state of the port type. The field could be used to track the state change information for the switch port type.
E Database tables and fields TABLE 242 FPORT_TRUNK_GROUP (Continued) Field Definition Format MASTER_USER_PORT User port number for the master port of this trunk. smallint WWN WWN of the trunk group. char TRUNK_AREA User-assigned area number used to group together F_ports of the trunk. smallint TABLE 243 Size 23 FPORT_TRUNK_MEMBER Field Definition Format GROUP_ID* Foreign key to the PORT_TRUNK_GROUP table. int PORT_NUMBER* Member user port number. smallint WWN Member port WWN.
E Database tables and fields TABLE 244 VIRTUAL_SWITCH (Continued) Field Definition Format Size USER_DEFINED_VALUE_2 varchar 256 USER_DEFINED_VALUE_3 varchar 256 CORE_SWITCH_ID Core switch DB ID. int INTEROP_MODE Mode in which this switch is operating.
E Database tables and fields TABLE 249 VIRTUAL_SWITCH Field Definition Format Size ID* int LOGICAL_ID smallint NAME varchar 64 WWN char 23 VIRTUAL_FABRIC_ID Default value is 0. DOMAIN_ID smallint smallint BASE_SWITCH Default value is 0. smallint SWITCH_MODE Default value is 0. smallint ROLE varchar 32 FCS_ROLE varchar 16 AD_CAPABLE Default value is 0. smallint FABRIC_IDID_MODE smallint OPERATIONAL_STATUS varchar MAX_ZONE_CONFIG_SIZE Defaultis 0.
E Database tables and fields TABLE 249 VIRTUAL_SWITCH (Continued) Field Definition Format DEFAULT_LOGICAL_SWITCH Check to see whether virtual switch is a default logical switch or not. 1 is true and 0 is false. Default value is 0. smallint FEATURES_SUPPORTED Contains the features supported as a bit mask. Default value is 0. int FMS_MODE Default value is 0. smallint DYNAMIC_LOAD_SHARING Default value is 0. smallint PORT_BASED_ROUTING Default value is 0.
E Database tables and fields TABLE 249 VIRTUAL_SWITCH (Continued) Field Definition Format Size PREVIOUS_STATE This fields copies the old state of the switch . The field could be used to track the state change information for the switch.These values to be populated by FCS during Fabric Refresh task.SMIA requested this information but could be used by any module which needs to track the state change varchar 32 MANAGED_ELEMENT_ID A unique managed element ID for this virtual switch.
E Database tables and fields TABLE 252 AVAILABLE_FLYOVER_PROPERTY (Continued) Field Definition Format TYPE The flyover property type: 0 = Product property 1 = Connection property smallint DEFAULT_SELECTION AVAILABLE_FLYOVER_PROPERTY DEFAULT_SELECTION 1 = default selected product/connection property 0 = not included in the default list. smallint TABLE 253 SELECTED_FLYOVER_PROPERTY Field Definition Format PROPERTY_ID* Refers to Flyover_Property ID from AVAILABLE_FLYOVER_PROPERTY table.
E Database tables and fields TABLE 256 PRODUCT_APP (Continued) Field Definition Format Size PROP2_KEY Second condition name to be satisfied by a selected product to launch a particular tool. varchar 256 PROP2_VALUE Second condition value to be satisfied by a selected product to launch a particular tool. varchar 256 TOOL_ID The tool to be used for launching the application. int PARAMETERS Link to that application. varchar IP_SELECTED Selected IP Address option.
E Database tables and fields TABLE 259 LSAN_ZONE (Continued) Field Definition Format EDGE_FABRIC_ID FID assigned to edge fabric. int NAME LSAN zone name. varchar BACKBONE 0= is not a backbone lsan zone, 1= is a backbone lsan zone. Default value is 0. smallint TABLE 260 Size 128 LSAN_ZONE_MEMBER Field Definition Format LSAN_ZONE_ID* LSAN_ZONE record reference. int MEMBER_PORT_WWN* Zone member WWN.
E Database tables and fields TABLE 264 ZONE_ALIAS_MEMBER Field Definition ID* Format int TYPE Zone alias member type: 2 = WWN 4 = D,P smallint VALUE Member value (D,P or WWN). varchar ZONE_ALIAS_ID PK of the owning zone alias. int TABLE 265 Definition Format ZONE_SET_ID* PK of the owning zone set. INT ZONE_ID* PK of the owning zone. INT Definition Format Size ZONE Field ID* Size int ZONE_DB_ID PK the owning ZONE_DB. int NAME The zone name. varchar TYPE The zone type.
E Database tables and fields TABLE 267 ZONE_DB (Continued) Field Definition Format DEFAULT_ZONE_STATUS All access or no access when no active zone configuration. smallint ZONE_TXN_SUPPORTED Zoning commands support transaction. smallint MCDATA_DEFAULT_ZONE McData switch default zoning mode. smallint MCDATA_SAFE_ZONE McData switch safe zoning mode. smallint ZONE_CONFIG_SIZE Zone configuration string length. int ZONE_AVAILABLE_SIZE Available zone DB size in the switch.
E Database tables and fields TABLE 272 AD_GROUP_ROLE_MAP Field Definition Format AD_GROUP_ID Active directory group ID int ROLE_ID TABLE 273 Size int AOR Field Definition Format Size ID* int NAME varchar 128 DESCRIPTION varchar 512 TABLE 274 AOR_DEVICE_GROUP_MAP Field Definition Format AOR_ID ID of the AOR. int DEVICE_GROUP_ID The Product Group which is in the AOR.
E Database tables and fields TABLE 279 AUTO_TRACE_DUMP Field Definition Format CORE_SWITCH_ID int ENABLED The enabled/disabled state of automatic trace dump transfer on the switch smallint PROTOCOL The protocol Unknown(0)/FTP(1)/SCP(2) to be used for transfer smallint IP_ADDRESS The Host IP Address varchar 64 USER_NAM The user name varchar 64 LOCATION Directory location where trace dump files are to be saved varchar 1024 PASSWORD The user password varchar 64 Format Size TABL
E Database tables and fields TABLE 282 BOOT_LUN_SEQUENCE Field Definition ID Format int NAME Name of the Boot LUN Sequence varchar FABRIC_ID PK of the owning fabric INT TABLE 283 64 BOOT_LUN_SEQUENCE_DETAIL Field Definition ID * Format Size int BOOT_LUN_SEQ_ID PK of the owning Boot LUN Sequence char PORT_WWN WWN of the port in the Boot LUN Sequenc int LUN_NUM LUN number of the port in the Boot LUN Sequence int SEQUENCE_NUM Sequence number of the port in the Boot LUN Sequence
E Database tables and fields TABLE 284 CEE_PORT (Continued) Field Definition Format Size QOS_NAME Name of the QoS Map set on the port varchar 64 DOT1X_ENABLED Indicate if 802.1x authentication is enabled on this port. The default value is 0. smallint TABLE 285 CLIENT_VIEW_MEMBER_HOST Field Definition Format CLIENT_VIEW_ID Primary key of CLIENT_VIEW table int HOST_ID Primary key of DEVICE_ENCLOSURE table int Field Definition Format ID * Arbitrary integer to identify the cluster.
E Database tables and fields TABLE 289 CNA_PORT Field Definition Format ID Primary key autogenerated ID int PORT_NUMBER Port number of the CNA port int PORT_WWN Port WWN of the port char 23 NODE_WWN Node WWN of the port char 23 PHYSICAL_PORT_TYPE Port type CNA/FC varchar 32 NAME Name of the port varchar 256 MAC_ADDRESS MAC address of the port. varchar 64 MEDIA Media of the port varchar 64 CEE_STATE State of the port. varchar 64 HBA_ID ID of the port.
E Database tables and fields TABLE 291 COLLECTOR_END_TIMESTAMP (Continued) Field Definition Format TIMESTAMP_ When the last successful collection is done. timestamp LAST_COLLECTED_STATUS Status of the last collection, successful or not. 200 is for successful. Values are standard HTTP protocol values. smallint TABLE 292 CRYPTO_HOST Field Definition Format ID Size int CRYPTO_TARGET_CONTAINE R_ID Foreign key reference to the CRYPTO_TARGET_CONTAINER that contains this host.
E Database tables and fields TABLE 293 CRYPTO_LUN (Continued) Field Definition Format LAST_REKEY_PROGRESS Indicates whether a re-key operation is in progress. 0 = no re-keying in progress. > 0 = percentage done of re-keying operation in progress. Only valid for disk LUNs. The default value is 0. smallint If a tape session is in progress, this is the volume label for the currently mounted tape. Only valid for tape LUNs. varchar PRIOR_ENCRYPTION_STAT E Not used.
E Database tables and fields TABLE 293 CRYPTO_LUN (Continued) Field Definition Format LUN_FLAGS Bitmap of LUN options. The only option currently used is bit 0 (least significant) which indicates that the LUN must be manually enabled because it has been disabled due to inconsistent metadata detected. The default value is 0. bigint ENCRYPTION_ALGORITHM Stores the Encryption Algorithm used to encrypt/decrypt data on the LUN varchar KEY_ID_STATE State of the Key ID retrieval from Key Vault.
E Database tables and fields TABLE 294 CRYPTO_TARGET_CONTAINER (Continued) Field Definition Format FAILOVER_STATUS Indicates whether this container''s target is being encrypted by the encryption engine on which the container is configured (value 0) or by another encryption engine in the HA Cluster (value 1). Default value is 0.. smallint FAILOVER_STATUS_2 Failover status from the HA Cluster peer.
E Database tables and fields TABLE 297 ENCRYPTION_ENGINE Field Definition Format ID 1092 Size int SWITCH_ID Foreign key reference to both the VIRTUAL_SWITCH table and the CRYPTO_SWITCH table (both switch tables use the same primary key values). Identifies the switch that contains this encryption engine. int SLOT_NUMBER For chassis switches, the slot or blade that contains the encryption engine. Always 0 for pizza-box switches with a single embedded encryption engine.
E Database tables and fields TABLE 297 ENCRYPTION_ENGINE (Continued) Field Definition Format LINK_MTU Local EE Link MTU. The default value is -1. int LINK_STATE Local EE State says whether link is down or up varchar REBALANCE_REQUIRED This field indicates whether a rebalance operation is required on the Encryption Engine. It can take two values, One(1) indicating that rebalance is required on the Encryption Engine and zero(0) indicating that no rebalance is required on the Encryption Engine.
E Database tables and fields TABLE 298 ENCRYPTION_GROUP (Continued) Field Definition Format Boolean value that indicates whether a System Card (smart card) must be inserted in the Encryption Engine to enable the engine after power-up. This feature is not yet supported. The default value is 0. smallint ACTIVE_MASTER_KEY_ STATUS The operational status of the "master key" or "Key Encryption Key (KEK)" used to encrypt Data Encryption Keys in a key vault. Not used for Decru LKM key vaults.
E Database tables and fields TABLE 299 ETHERNET_CLOUD Field Definition ID The unique id of the switch this cloud is associated to. int ETHERNET_ISL Field Definition ID Format Size int SOURCE_PORT_ID The unique id of the source port. int DEST_PORT_ID The unique id of the destination port.
E Database tables and fields TABLE 302 EVENT_CATEGORY Field Definition Format ID 0 - Unknown 1 - Product Event 2 - Link Incident Event 3 - Product Audit Event 4 - Product Status Event 5 - Security Event 6 - User Action Event 7 - Management Server Event int DESCRIPTION TABLE 303 varchar 50 Format Size EVENT_DESCRIPTION Field Definition ID int DESCRIPTION varchar 1024 Format Size TABLE 304 EVENT_DETAILS Field Definition ID int EVENT_ID int FIRST_OCCURRENCE_SWI TCH_TIME times
E Database tables and fields TABLE 305 EVENT_FWD_FILTER Field Definition ID Format int NAME Filter Name DESCRIPTION varchar 32 varchar 256 TYPE Filter Type (SNMP/ SYSLOG) smallint APPLICATION_ENABLED If Application Events enabled smallint SNORT_ENABLED If Snort Messages enabled smallint PSUDO_ENABLED If Pseudo Events enabled smallint REGULAR_EXP Common filtering message for Syslog Forwarding varchar SEVERITY Emergency(0), Alert(1), Critical(2), Error(3), Warning(4), Notice(5),
E Database tables and fields TABLE 310 EVENT_INSTANCE Field Definition Format ID int EVENT_POLICY_ID Foreign Key to Event_Policy Table int EVENT_KEY A String Key string which identifies a specific instance of an Event. varchar 64 STRING_PATTERN A Regular expression pattern string which can be used to match an Event instance. varchar 1024 CATEGORY A small integer which identifies the Category of an Event instance.
E Database tables and fields TABLE 313 EVENT_POLICY Field Definition ID Format Size int TYPE Even Policy Type 0 - Pseudo Event 1 - Event Action smallint NAME The Name of the Event Policy varchar 256 DESCRIPTION The Description of the Event Policy varchar 1024 STATUS Administrative status of the Event Policy 0 - disabled 1- enabled smallint LAST_MODIFIED_TIME The Severity of the Event that is logged per Event Policy 0- Unknown 1- Emergency 2- Alert 3- Critical 4- Error 5- Warning 6-
E Database tables and fields TABLE 314 EVENT_POLICY_SOURCE_ENTRY (Continued) Field Definition Format SOURCE_SELECTION_TYPE Option selected to give Source Information 0- IPAddress/Node wwn/Name provided 1- Source selected from available list of sources. The default value is 0.
Database tables and fields TABLE 318 E FCIP_TUNNEL_CIRCUIT (Continued) Field Definition Format TAPE_ACCELERATION_ENABLED Whether TapeAccelaration is enabled on that circuit smallint IKE_POLICY_NUM The IKE Policy on the int circuit.The default value is -1. IPSEC_POLICY_NUM The IPSEC Policy on the circuit'.
E Database tables and fields TABLE 318 1102 FCIP_TUNNEL_CIRCUIT (Continued) Field Definition Format Size MAX_RETRANSMISSIONS Max number of Retransmission attempts on the circuit. The default value is 0. int SLOT_NUMBER Slot number of the circuit. The default value is 0. smallint VE_PORT_NUMBER VE port number of the tunnel to which the circuit belongs. int SECURITY_FLAG Security Flag associated with the circuit. The default value is 0.
Database tables and fields TABLE 319 E FCIP_TUNNEL_PERFORMANCE Field Definition Format TUNNEL_ID Primary key of the Switch Port int SWITCH_ID 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 int TX 'The number of octets or bytes that have been transmitted by this port.
E Database tables and fields TABLE 319 FCIP_TUNNEL_PERFORMANCE (Continued) Field Definition Format RTT_BY_TIME_OUT Counter of retransmit packets due to timeout double precision RTT_BY_DUP_ACK Counter of retransmit packets due to duplicate acknowledgement' double precision DUPLICATE_ACK Counter of duplicate acknowledgement packets double precision ROUND_TRIP_TIME Round trip time in milliseconds double precision TCP_OUT_OF_ORDER Counter of TCP out-of-order.
E Database tables and fields TABLE 321 FRU (Continued) Field Definition Format Size VENDOR_PART_ NUMBER provides the Vendor-assigned part number of this package, requested by SMIA and values filled in by Switch Asset Collector varchar 64 VENDOR_SERIAL_ NUMBER provides the Vendor-assigned serial number of this package, requested by SMIA and values filled in by Switch Asset Collector' varchar 64 CAN_BE_FRUED provides whether this element can be removed from the switch, requested by SMIA and v
E Database tables and fields TABLE 321 FRU (Continued) Field Definition Format PREVIOUS_OP_STATUS provides the previous operational status of FRU element, requested by SMIA and values filled in by Switch Asset Collector. Helps identify the operational status transitions. The default value is -1.
Database tables and fields TABLE 323 E HBA (Continued) Field Definition Format MANAGEMENT_INTERFACE Management interface bit mask, JSON/WMI/SMI etc . The default value is -1.
E Database tables and fields TABLE 323 HBA (Continued) Field Definition Format Size VPD_PW PW details of the device varchar 32 VPD_EDC EDC details of the device varchar 32 VPD_MDC MDC details of the device varchar 32 VPD_FABRIC_GEOGRAPHY FABRIC_GEOGRAPHY of the device varchar 256 VPD_LOCATION LOCATION of the device varchar 256 VPD_MANUFACTURER_ID MANUFACTURER_ID of the device varchar 256 VPD_PCI_GEOGRAPHY PCI_GEOGRAPHY of the device varchar 256 VPD_VENDOR_DATA VENDOR_DAT
E Database tables and fields TABLE 325 HOST_DISCOVERY_REQUEST (Continued) Field Definition Format The status of HBA Discovery using CIM, indicating success or failure. The default value is 0. int CIM_MANAGEMENT_STA TE Reflects the status of the request E.g. 0-> Completed, 1->Add Pending 2->Delete Pending 3->Edit Pending 4->Delete Failed. The default value is 1.
E Database tables and fields TABLE 328 LAG (Continued) Field Definition Format LAG_MODE Static or dynamic (1=dynamic, 2=static) smallint ACTIVE LACP active or passive (1=active, 2=passive) valid if mode=dynamic smallint TYPE Trunking type (1=standard, 2=brocade, 3=hybrid) smallint IF_MODE L2 or L3 mode varchar 8 L2_MODE Type of L2 mode (default=access varchar 32 MAC_ACL_POLICY stores the MAC ACL policy information of the LAG varchar 64 VLAN_LIST Comma separated vlan id list.
E Database tables and fields TABLE 331 LICENSE_RULE (Continued) Field Definition Format DESCRIPTION Description of the rule varchar SCOPE Scope of the rule - is it applicable to Fabric, switch or ports varchar CATEGORY Category of the rule - is it used by unknown - 0, asset collection - 1, or 2 - the license manager service smallint ENABLE Whether the rule needs to be considered or not. 1 consider, 0 - do not consider for calculation. The default value is 1.
E Database tables and fields TABLE 335 PASSWORD_HISTORY Field Definition USER_NAME Size varchar 128 PASSWORD_UPDATED_ DATETIME The date and time the user updated password recently. timestamp PREVIOUS_PASSWORD User''s Previous password varchar 512 Format Size TABLE 336 PHANTOM_PORT Field Definition ID int WWN The Wwn of the phantom port. char VIRTUAL_SWITCH_ID The id of the phantom switch. int PORT_NUMBER The port number of the phantom port. The default value is -1.
E Database tables and fields TABLE 337 PORT_BOTTLENECK_CONFIG (Continued) Field Definition Format WINDOW_ Value of bottleneck detection latency window in millisecond. The default value is 0. int QUIET_TIME Value of bottleneck detection quiet time in millisecond. The default value is 0. int CREATION_TIME Creation time of the record. timestamp LAST_UPDATE_TIME Last update time of the record.
E Database tables and fields TABLE 342 RESOURCE_HOST_MAP Field Definition Format RESOURCE_GROUP_ID Resource Group ID int HOST_ID HOST_ID,which is in the resource group int TABLE 343 SSL_KEY_PASSWORD Field Definition Format ID Size int KEY_PASSWORD_ALIAS Key Password Alias is the alias name used for the encrypted key password. This alias name is used to identify the password in client UI.
E Database tables and fields TABLE 345 IP_DEVICE_LICENSE (Continued) Field Definition Format PRECEDENCE Defines the priority of a particular trial license among those having the same package and License ID. This is primarily used for determining which license to use, when there are many trial and normal licenses with same package name and LID. The value range is (0..65535) int LICENSE_STATE This indicates the state of the license.
E Database tables and fields TABLE 348 ZONE_TRANSACTION Field Definition Format FABRIC_ID The id of the fabric on which the zoning transaction is open. This is the primary key for this table and is a foreign key from the FABRIC table where ZONE_TR.FABRIC_ID == FABRIC.ID int USER_NAME The Management applciation username of the cimclient who has opened the zoning transaction on the fabric.
E Database tables and fields TABLE 353 V_CENTER_HOST Field Definition ID Format Size int HOST The FQDN or the ip address of the host varchar PORT The port of the VCENTER server on the host. The default value is 443 . int USER_NAME The username to login into the VCENTER varchar 64 PASSWORD The password to login into the VCENTER varchar 64 VERSION The version of VCENTER. The default value is 4.0 .
E Database tables and fields TABLE 356 VIRTUAL_FCOE_PORT_STAT Field Definition ID int SWITCH_ID int PORT_ID int TX The number of valid frames sent from the port double precision RX The number of valid frames received at this port double precision TX_UTILIZATION The computed value of TX based on speed of port (for MarchingAnts) double precision RX_UTILIZATION The computed value of RX based on speed of port (for MarchingAnts) double precision CREATION_TIME The time this stats record w
E Database tables and fields TABLE 357 VIRTUAL_FCOE_PORT_STAT_1DAY (Continued) Field Definition Format RX_UTILIZATION double precision CREATION_TIME timestamp ACTIVE_STATE smallint LINK_FAILURES double precision TX_LINK_RESETS double precision RX_LINK_RESETS double precision SYNC_LOSSES double precision SIGNAL_LOSSES double precision SEQUENCE_ERRORS double precision INVALID_TX double precision CRC_ERRORS double precision DATA_GAPS_5MIN smallint DATA_GAPS_30MIN Data gap in 2 h
E Database tables and fields TABLE 358 VIRTUAL_FCOE_PORT_STAT_2HR (Continued) Field Definition CREATION_TIME double precision ACTIVE_STATE timestamp LINK_FAILURES double precision TX_LINK_RESETS double precision RX_LINK_RESETS double precision SYNC_LOSSES double precision SIGNAL_LOSSES double precision SEQUENCE_ERRORS double precision INVALID_TX double precision CRC_ERRORS double precision DATA_GAPS_5MIN smallint DATA_GAPS_30MIN TABLE 359 Data gap in 30 minutes table Size sma
E Database tables and fields TABLE 359 VIRTUAL_FCOE_PORT_STAT_30M (Continued) Field Definition Format TX_LINK_RESETS double precision RX_LINK_RESETS double precision SYNC_LOSSES double precision SIGNAL_LOSSES double precision SEQUENCE_ERRORS double precision INVALID_TX double precision CRC_ERRORS double precision DATA_GAPS_5MIN TABLE 360 Data gap in 5 minutes table Size smallint VIRTUAL_MACHINE Field Definition Format ID Uniquely identifies the virtual machine.
E Database tables and fields TABLE 360 VIRTUAL_MACHINE (Continued) Field Definition Format DATASTORE_NAME The user-assigned name for the VMs datastore. The datastore holds the VMs virtual disks, swap file, and configuration data varchar DATASTORE_LOCATION The location of the VMs datastore May be a SAN target disk or a locally-attached host disk folder. For VMware, this is a target LUN name. varchar NODE_WWN The Node WWN for this VM.
E Database tables and fields TABLE 363 USER_DEFINED_DEVICE_DETAIL (Continued) Field Format Size USER_DEFINED_VALUE1 varchar 256 USER_DEFINED_VALUE2 varchar 256 USER_DEFINED_VALUE3 varchar 256 Size TABLE 364 Definition SWITCH_BOTTLENECK_CONFIG Field Definition Format VIRTUAL_SWITCH_ID The database ID of the switch that the configuration belongs to int 'Flag indicates if bottleneck detection is enabled or not. The default value is 0.
E Database tables and fields TABLE 365 Definition Format RX_UTILIZATION 'The computed value of RX based on speed of port double precision LINK_FAILURE 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 double precision TX_LINK_RESETS Count of Link resets. This is the number of LRs received. Note, this is a Fibre Channel only stat double precision RX_LINK_RESETS Count of Link resets.
E Database tables and fields TABLE 366 SWITCH_TE_PORT_PERFORMANCE (Continued) Field Definition Format RX 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.
E Database tables and fields TABLE 367 SWITCH_TE_PORT_STATS Field Definition Format ID 1126 int SWITCH_ID The primary key of the switch int PORT_ID The primary key of the port int TRANSMIT_OK 'The number of valid frames sent from the port double precision RECEIVE_OK The number of valid frames received at this port.
E Database tables and fields TABLE 368 SWITCH_TE_PORT_STATS_1DAY Field Definition Format ID int SWITCH_ID int PORT_ID int TRANSMIT_OK double precision RECEIVE_OK double precision TRANSMIT_OK_PERCENT_U TIL RECEIVE_OK_PERCENT_UTI L double precision double precision CREATION_TIME timestamp ACTIVE_STATE smallint RECEIVE_EOF double precision UNDERFLOW_ERRORS double precision OVERFLOW_ERRORS double precision CRC_ERRORS double precision ALIGNMENT_ERRORS double precision RUNT_ERRORS
E Database tables and fields TABLE 369 SWITCH_TE_PORT_STATS_2HR Field Definition ID int SWITCH_ID int PORT_ID int TRANSMIT_OK double precision RECEIVE_OK double precision double precision RECEIVE_OK_PERCENT_UTI L CREATION_TIME timestamp ACTIVE_STATE smallint RECEIVE_EOF double precision UNDERFLOW_ERRORS double precision OVERFLOW_ERRORS double precision CRC_ERRORS double precision ALIGNMENT_ERRORS double precision RUNT_ERRORS double precision EXCESS_COLL_ERRORS double precis
E Database tables and fields TABLE 370 SWITCH_TE_PORT_STATS_30MIN (Continued) Field Definition Format PORT_ID int TRANSMIT_OK double precision RECEIVE_OK double precision TRANSMIT_OK_PERCENT_ UTIL double precision RECEIVE_OK_PERCENT_ UTIL double precision CREATION_TIME timestamp ACTIVE_STATE smallint RECEIVE_EOF double precision UNDERFLOW_ERRORS double precision OVERFLOW_ERRORS double precision CRC_ERRORS double precision ALIGNMENT_ERRORS double precision RUNT_ERRORS double p
E Database tables and fields TABLE 372 TOPO_MAP_IMAGE Field Definition Format ID int NAME Image name in the foo.png format varchar IMAGE_OBJECT 'Image Object BLOB bytea Definition Format TABLE 373 256 SMART_CARD Field ID Size int CARD_TYPE Indicates how this smart card is configured: 0 = authorization card. The default value is 0. smallint CARD_INFO Additional smart card details.
E Database tables and fields TABLE 374 SNMP_DATA_1DAY (Continued) Field Definition Format Size VALUE double precision TIME_IN_SECONDS int COLLECTOR_ID int MIB_INDEX char 256 Format Size TABLE 375 SNMP_DATA_2HOUR Field Definition ID int MIB_OBJECT_ID int TARGET_TYPE numeric TARGET_ID int VALUE double precision TIME_IN_SECONDS int COLLECTOR_ID int MIB_INDEX char 256 Size TABLE 376 (2,0) SNMP_DATA_30MIN Field Definition Format ID Primary key autogenerated ID int
E Database tables and fields TABLE 377 SNMP_EXPR_DATA_1DAY (Continued) Field Definition Format TIME_IN_SECONDS int COLLECTOR_ID int TABLE 378 SNMP_EXPR_DATA_2HOUR Field Definition Format ID int EXPRESSION_ID int TARGET_TYPE smallint TARGET_ID int VALUE double precision TIME_IN_SECONDS int COLLECTOR_ID int TABLE 379 Definition Format ID Primary key autogenerated ID int EXPRESSION_ID DB ID of the expression object used for collection int TARGET_TYPE Target/Source type c
E Database tables and fields TABLE 381 SENSOR Field Definition Format ID int CORE_SWITCH_ID int Size SENSOR_ID Identifies the sensor device , requested by SMIA and values filled in by Switch Asset Collector. Maps to Device Id in the html page. The default value is -1. int CURRENT_READING Identifies the current temperature reading sensor, requested by SMIA and values filled in by Switch Asset Collector, Maps to value field in the html page. The default value is -1.
E Database tables and fields TABLE 381 SENSOR (Continued) Field Definition Format UNIT_NUMBER provides the unit number of the sensor, requested by SMIA and values filled in by Switch Asset Collector will be available only from FOS 6.4 switches and above . This the gives the index of the unit. For SLOT FRU, this will be slot number. For FAN fru, this will be fan number. The default value is -1.
E Database tables and fields TABLE 383 HOST_DISCOVERY_OPTION (Continued) Field Definition Format Size CIM_NAMESPACE CIM Namespace. The default value is 'root/brocade varchar 128 CIM_PORT Port number used for the CIM agent. The default value is 5988. int DISCOVER_VM Flag to indicate VM discovery for a host. On/Off'. The default value is 0.
E Database tables and fields TABLE 385 HBA_REMOTE_PORT_LUN (Continued) Field Definition Format BLOCK_SIZE The block size of the logical unit, in bytes (for example, 512 Bytes). The default value is 0. int VENDOR The vendor of the device to which the logical unit is assigned varchar 256 PRODUCT_ID The product identifier of the device to which the logical unit is assigned varchar 256 PRODUCT_VERSION The revision level of the device to which the logical unit is assigned.
E Database tables and fields TABLE 386 HBA_REMOTE_PORT (Continued) Field Definition Format Size QOS_PRIORITY QOS Priority on the target. The default value is 'Unknown'. varchar 64 QOS_FLOW_ID QOS Flow ID on the target. The default value is 0. varchar 64 CURRENT_SPEED Current speed of the remote port, as enforced by TRL. The default value is 0. varchar 64 TRL_ENFORCED The default value is 0. varchar 16 BUS_NO Channel number in the PCI Bus. The default value is 0.
E Database tables and fields TABLE 387 HBA_PORT (Continued) Field Definition Format CONFIGURED_TOPOLOGY The topology setting. The default value is 1. int MAX_SPEED_SUPPORTED The maximum port speed that is supported on the port, in Gb/s. The default value is 0. int OPERATING_STATE Indicates whether the link is online or offline. The default value is 0. smallint OPERATING_TOPOLOGY The topology setting at which the port is operating. The default value is 1.
E Database tables and fields TABLE 388 HBA_PORT_DETAIL (Continued) Field Definition Format BOOT_SPEED The default value is 0. int BOOT_TOPOLOGY The default value is 1. int BB_CREDIT The maximum number of receive buffer. The default value is 8. int FRAME_DATA_FIELD_SIZE The default value is 512. int HARDWARE_PATH Indicates whether MPIO is enabled or disabled V_PORT_COUNT Number of logical ports. The default value is 0.
E Database tables and fields TABLE 388 HBA_PORT_DETAIL (Continued) Field Definition Format FCSP_AUTH_STATE Indicates whether FC-SP authentication is on or off. The default value is 0. smallint FCSP_STATUS The status of FC-SP authentication. The default value is 'Disabled'. varchar 32 FCSP_ALGORITHM The configured authentication algorithm. The default value is 'MD5'. varchar 64 FCSP_GROUP The DH Group (DH Null, group 0 is the only option). The default value is 0.
E Database tables and fields TABLE 389 HBA_PORT_FCOE_DETAILS (Continued) Field Definition Format PORT_LOG_ENABLED The default value is 0. smallint MAX_FRAME_SIZE The default value is 512. int MTU The default value is 0. int PATH_TOV The default value is 0. int SCSI_QUEUE_DEPTH The default value is 0. int Size STATE varchar 64 SUPPORTED_CLASS varchar 256 TRL_SPEED The default value is 0. int TRL_STATE The default value is 0.
E Database tables and fields TABLE 391 Definition Format ID Identifies a server running a supported hypervisor. The ID value is the same as the ID of the corresponding DEVICE_ENCLOSURE record. int NODE_WWN The Node WWN for this host. char 23 HYPERVISOR_NAME Hypervisor name and version, such as VMware ESX Server v3.5.0 varchar 64 HYPERVISOR_TYPE Numeric hypervisor type ID. 1 = VMware, 2 = Hyper-V. The default value is 0. smallint CPU_COUNT Number of CPUs in the server.
E Database tables and fields TABLE 392 VM_LUN (Continued) Field Definition Format PATH_POLICY Determines how multiple paths to this LUN are used. 0 = fixed, 1 = Most Recently Used, 2 = Round Robin. The default value is 0. smallint UUID Universal unique ID varchar 64 Definition Format Size TABLE 393 Size VM_PATH Field ID int HOST_ID Identifies the host containing this path. This is a foreign key reference to VM_HOST.ID int VM_ID Identifies the VM using this path to a LUN.
E Views TABLE 393 VM_PATH (Continued) Field Definition Format Size VM_NODE_WWN The initiator node WWN used by the VM. If NPIV is used, this is a virtual node WWN assigned to the VM. If NPIV is not used, this WWN is the same as the node WWN of one of the HBAs in the host.
Views E CEE_PORT.OCCUPIED, CEE_PORT.LAST_UPDATE, CEE_PORT.NET_MASK, CEE_PORT.PROTOCOL_DOWN_REASON, CEE_PORT.MAC_ACL_POLICY, CEE_PORT.QOS_TYPE, CEE_PORT.QOS_NAME, CEE_PORT.DOT1X_ENABLED, CORE_SWITCH.IP_ADDRESS as PHYSICAL_SWITCH_IP, CORE_SWITCH.WWN as PHYSICAL_SWITCH_WWN, GIGE_PORT.OPERATIONAL_STATUS, GIGE_PORT.MAX_SPEED, GIGE_PORT.PORT_TYPE, GIGE_PORT.REMOTE_MAC_ADDRESS, GIGE_PORT.SLOT_NUMBER, VIRTUAL_SWITCH.WWN, SWITCH_PORT.USER_PORT_NUMBER, SWITCH_PORT.
E Views select CNA_PORT.ID, CNA_PORT.PORT_NUMBER, CNA_PORT.PORT_WWN, CNA_PORT.NODE_WWN, CNA_PORT.PHYSICAL_PORT_TYPE, CNA_PORT.NAME, CNA_PORT.MAC_ADDRESS, CNA_PORT.MEDIA, CNA_PORT.CEE_STATE, CNA_PORT.HBA_ID, CNA_PORT.CREATION_TIME as CNA_PORT_CREATION_TIME, CNA_ETH_PORT.ID as ETH_PORT_ID, CNA_ETH_PORT.ETH_DEV, CNA_ETH_PORT.ETH_LOG_LEVEL, CNA_ETH_PORT.NAME as ETH_PORT_NAME, CNA_ETH_PORT.MAC_ADDRESS as ETH_MAC_ADDRESS, CNA_ETH_PORT.IOC_ID, CNA_ETH_PORT.HARDWARE_PATH, CNA_ETH_PORT.STATUS, CNA_ETH_PORT.
Views E CORE_SWITCH_DETAILS.FC_CERTIFICATE, CORE_SWITCH_DETAILS.SW_LICENSE_ID, CORE_SWITCH_DETAILS.SUPPLIER_SERIAL_NUMBER, CORE_SWITCH_DETAILS.PART_NUMBER, CORE_SWITCH_DETAILS.CHECK_BEACON, CORE_SWITCH_DETAILS.TIMEZONE, CORE_SWITCH_DETAILS.MAX_PORT, CORE_SWITCH_DETAILS.CHASSIS_SERVICE_TAG, CORE_SWITCH_DETAILS.BAY_ID, CORE_SWITCH_DETAILS.TYPE_NUMBER, CORE_SWITCH_DETAILS.MODEL_NUMBER, CORE_SWITCH_DETAILS.MANUFACTURER, CORE_SWITCH_DETAILS.PLANT_OF_MANUFACTURER, CORE_SWITCH_DETAILS.
E Views LUN.ENCRYPTION_ALGORITHM, LUN.KEY_ID_STATE, LUN.REKEY_SESSION_NUMBER, LUN.PERCENTAGE_COMPLETE, LUN.REKEY_ROLE, LUN.CURRENT_LBA, LUN.LUN_STATE_STRING, LUN.NEW_LUN, LUN.NEW_LUN_TYPE, CRYPTO_HOST.HOST_PORT_WWN, CRYPTO_HOST.HOST_NODE_WWN from CRYPTO_LUN LUN, CRYPTO_HOST where LUN.CRYPTO_HOST_ID = CRYPTO_HOST.ID; CRYPTO_TARGET_ENGINE_INFO create or replace view CRYPTO_TARGET_ENGINE_INFO as select CRYPTO_TARGET_CONTAINER.ID TARGET_CONTAINER_ID, CRYPTO_TARGET_CONTAINER.NAME, CRYPTO_TARGET_CONTAINER.
Views E CORE_SWITCH.OPERATIONAL_STATUS as PHYSICAL_OPERATIONAL_STATUS, CORE_SWITCH.TYPE, CORE_SWITCH.MAX_VIRTUAL_SWITCHES, CORE_SWITCH.NUM_VIRTUAL_SWITCHES, CORE_SWITCH.FIRMWARE_VERSION, CORE_SWITCH.VENDOR, CORE_SWITCH.REACHABLE, CORE_SWITCH.UNREACHABLE_TIME, CORE_SWITCH.MODEL, CORE_SWITCH.SYSLOG_REGISTERED, CORE_SWITCH.SNMP_REGISTERED, CORE_SWITCH.CALL_HOME_ENABLED, CORE_SWITCH.USER_IP_ADDRESS, CORE_SWITCH.NIC_PROFILE_ID, CORE_SWITCH.MANAGING_SERVER_IP_ADDRESS, CORE_SWITCH.VF_ENABLED, CORE_SWITCH.
E Views VIRTUAL_SWITCH.PREVIOUS_OPERATIONAL_STATUS, VIRTUAL_SWITCH.LAST_SCAN_TIME, VIRTUAL_SWITCH.DOMAIN_MODE_239, VIRTUAL_SWITCH.DOMAIN_ID_OFFSET, VIRTUAL_SWITCH.DISCOVERED_PORT_COUNT, VIRTUAL_SWITCH.FCOE_LOGIN_ENABLED, VIRTUAL_SWITCH.LAST_PORT_MEMBERSHIP_CHANGE, VIRTUAL_SWITCH.FCIP_CIRCUIT_CAPABLE, VIRTUAL_SWITCH.MAX_FCIP_TUNNELS, VIRTUAL_SWITCH.MAX_FCIP_CIRCUITS, VIRTUAL_SWITCH.FCIP_LICENSED, VIRTUAL_SWITCH.ADDRESSING_MODE, VIRTUAL_SWITCH.PREVIOUS_STATE, VIRTUAL_SWITCH.
Views E SWITCH_PORT.ID as SWITCH_PORT_ID, SWITCH_PORT.WWN as SWITCH_PORT_WWN, SWITCH_PORT.NAME as SWITCH_PORT_NAME, SWITCH_PORT.SLOT_NUMBER, SWITCH_PORT.PORT_NUMBER, SWITCH_PORT.PORT_INDEX, SWITCH_PORT.TYPE as SWITCH_PORT_TYPE, SWITCH_PORT.FULL_TYPE as SWITCH_PORT_FULL_TYPE, SWITCH_PORT.STATUS as SWITCH_PORT_STATUS, SWITCH_PORT.HEALTH as SWITCH_PORT_HEALTH, SWITCH_PORT.SPEED, SWITCH_PORT.MAX_PORT_SPEED, SWITCH_PORT.NPIV, SWITCH_PORT.NPIV_CAPABLE, SWITCH_PORT.CALCULATED_STATUS, SWITCH_PORT.
E Views N2F_PORT_MAP, SWITCH_PORT AG_N_PORT, SWITCH_PORT AG_F_PORT where N2F_PORT_MAP.VIRTUAL_SWITCH_ID = AG_N_PORT.VIRTUAL_SWITCH_ID and N2F_PORT_MAP.N_PORT = AG_N_PORT.USER_PORT_NUMBER and N2F_PORT_MAP.VIRTUAL_SWITCH_ID = AG_F_PORT.VIRTUAL_SWITCH_ID and N2F_PORT_MAP.F_PORT = AG_F_PORT.USER_PORT_NUMBER; DEVICE_NODE_INFO create or replace view DEVICE_NODE_INFO as select DEVICE_NODE.ID, DEVICE_NODE.FABRIC_ID, DEVICE_NODE.WWN, DEVICE_NODE.TYPE, DEVICE_NODE.DEVICE_TYPE, DEVICE_NODE.
Views E DEVICE_PORT.SYMBOLIC_NAME, DEVICE_PORT.FC4_TYPE, DEVICE_PORT.COS, DEVICE_PORT.IP_PORT, DEVICE_PORT.HARDWARE_ADDRESS, DEVICE_PORT.TRUSTED, DEVICE_PORT.CREATION_TIME, DEVICE_PORT.MISSING, DEVICE_PORT.MISSING_TIME, DEVICE_PORT.NPV_PHYSICAL, DEVICE_PORT.EDGE_SWITCH_PORT_WWN, FICON_DEVICE_PORT.TYPE_NUMBER, FICON_DEVICE_PORT.MODEL_NUMBER, FICON_DEVICE_PORT.MANUFACTURER, FICON_DEVICE_PORT.MANUFACTURER_PLANT, FICON_DEVICE_PORT.SEQUENCE_NUMBER, FICON_DEVICE_PORT.TAG, FICON_DEVICE_PORT.
E Views DEV_PORT_GIGE_PORT_LINK_INFO create or replace view DEV_PORT_GIGE_PORT_LINK_INFO as select DEVICE_PORT_GIGE_PORT_LINK.DEVICE_PORT_ID, DEVICE_PORT_GIGE_PORT_LINK.GIGE_PORT_ID, DEVICE_PORT_GIGE_PORT_LINK.DIRECT_ATTACH, DEVICE_PORT.TRUSTED, DEVICE_PORT.CREATION_TIME, DEVICE_PORT.MISSING, DEVICE_PORT.MISSING_TIME from DEVICE_PORT_GIGE_PORT_LINK, DEVICE_PORT where DEVICE_PORT_GIGE_PORT_LINK.DEVICE_PORT_ID = DEVICE_PORT.
Views E ETHERNET_ISL, GIGE_PORT SOURCE_GIGE_PORT, VIRTUAL_SWITCH SOURCE_VIRTUAL_SWITCH, SWITCH_PORT SOURCE_SWITCH_PORT, GIGE_PORT DEST_GIGE_PORT, VIRTUAL_SWITCH DEST_VIRTUAL_SWITCH, SWITCH_PORT DEST_SWITCH_PORT where SOURCE_GIGE_PORT.ID = ETHERNET_ISL.SOURCE_PORT_ID and SOURCE_GIGE_PORT.SWITCH_PORT_ID = SOURCE_SWITCH_PORT.ID and SOURCE_SWITCH_PORT.VIRTUAL_SWITCH_ID = SOURCE_VIRTUAL_SWITCH.ID and DEST_GIGE_PORT.ID = ETHERNET_ISL.DEST_PORT_ID and DEST_GIGE_PORT.SWITCH_PORT_ID = DEST_SWITCH_PORT.
E Views left outer join left outer join EVENT_CATEGORY.ID left outer join left outer join EVENT_DESCRIPTION.ID left outer join left outer join EVENT_ORIGIN on EVENT.EVENT_ORIGIN_ID = EVENT_ORIGIN.ID EVENT_CATEGORY on EVENT.EVENT_CATEGORY_ID = EVENT_MODULE on EVENT.EVENT_MODULE_ID = EVENT_MODULE.ID EVENT_DESCRIPTION on EVENT.EVENT_DESCRIPTION_ID = EVENT_DETAILS on EVENT.ID = EVENT_DETAILS.EVENT_ID EVENT_CALL_HOME on EVENT.ID = EVENT_CALL_HOME.
Views E FABRIC.CONTACT, FABRIC.LOCATION, FABRIC.DESCRIPTION, FABRIC.CREATION_TIME, FABRIC.LAST_SCAN_TIME, FABRIC.LAST_UPDATE_TIME, FABRIC.TRACK_CHANGES, FABRIC.TYPE, FABRIC.USER_DEFINED_VALUE_1, FABRIC.USER_DEFINED_VALUE_2, FABRIC.USER_DEFINED_VALUE_3, FABRIC.PRINCIPAL_SWITCH_WWN, FABRIC.ZONE_TRANSACTION_TIMEOUT, FABRIC.FABRIC_MODEL, FABRIC.ENHANCED_TI_ZONE_SUPPORT, VIRTUAL_SWITCH.ID as SEED_SWITCH_ID, VIRTUAL_SWITCH.VIRTUAL_FABRIC_ID, VIRTUAL_SWITCH.INTEROP_MODE, CORE_SWITCH.
E Views FCIP_TUNNEL_CIRCUIT.SECURITY_FLAG, FCIP_TUNNEL_CIRCUIT.DSCP_CONTROL, FCIP_TUNNEL_CIRCUIT.CIRCUIT_STATUS, FCIP_TUNNEL_CIRCUIT.ENABLED, FCIP_TUNNEL_CIRCUIT.MISMATCHED_CONFIGURATIONS, FCIP_TUNNEL_CIRCUIT.CIRCUIT_STATUS_STRING, FCIP_TUNNEL_CIRCUIT.L2COS_F_CLASS, FCIP_TUNNEL_CIRCUIT.L2_COS_HIGH, FCIP_TUNNEL_CIRCUIT.L2_COS_MEDIUM, FCIP_TUNNEL_CIRCUIT.L2_COS_LOW, FCIP_TUNNEL_CIRCUIT.DSCP_F_CLASS, FCIP_TUNNEL_CIRCUIT.DSCP_HIGH, FCIP_TUNNEL_CIRCUIT.DSCP_MEDIUM, FCIP_TUNNEL_CIRCUIT.DSCP_LOW, GIGE_PORT.
Views E FCIP_TUNNEL.FICON_TR_EMUL_ENABLED, FCIP_TUNNEL.FICON_DEBUG_FLAGS, FCIP_TUNNEL.REMOTE_WWN, FCIP_TUNNEL.CDC, FCIP_TUNNEL.ADMIN_STATUS, FCIP_TUNNEL.CONTROL_L2_COS, FCIP_TUNNEL.DSCP_CONTROL, FCIP_TUNNEL.TRUNKING_ALGORITHM, FCIP_TUNNEL.EXTENDED_TUNNEL, FCIP_TUNNEL.VIRTUAL_SWITCH_ID, FCIP_TUNNEL.CIRCUIT_COUNT, FCIP_TUNNEL.MISMATCHED_CONFIG_DETAILS, FCIP_TUNNEL.SLOT_NUMBER, FCIP_TUNNEL.FICON_ENABLED, FCIP_TUNNEL.TPERF_ENABLED, FCIP_TUNNEL.AUTH_KEY, FCIP_TUNNEL.CONNECTED_COUNT, FCIP_TUNNEL.
E Views FRU_INFO create or replace view FRU_INFO as select FRU.ID, FRU.CORE_SWITCH_ID, FRU.TAG, FRU.PART_NUMBER, FRU.SERIAL_NUMBER, FRU.VENDOR_PART_NUMBER, FRU.VENDOR_SERIAL_NUMBER, FRU.CAN_BE_FRUED, FRU.SLOT_NUMBER, FRU.MANUFACTURER_DATE, FRU.UPDATE_DATE, FRU.VERSION, FRU.MANUFACTURER, FRU.VENDOR_EQUIPMENT_TYPE, FRU.OPERATIONAL_STATUS, FRU.TOTAL_OUTPUT_POWER, FRU.SPEED, FRU.CREATION_TIME, FRU.LAST_UPDATE_TIME, FRU.PREVIOUS_OP_STATUS, FRU.VENDOR, CORE_SWITCH.WWN as PHYSICAL_SWITCH_WWN, VIRTUAL_SWITCH.
Views E GIGE_PORT.SWITCH_PORT_ID = SWITCH_PORT.ID and SWITCH_PORT.VIRTUAL_SWITCH_ID = VIRTUAL_SWITCH.ID; GIGE_PORT_INFO create or replace view GIGE_PORT_INFO as select GIGE_PORT.ID, GIGE_PORT.SWITCH_PORT_ID, GIGE_PORT.PORT_NUMBER, GIGE_PORT.SLOT_NUMBER, GIGE_PORT.ENABLED, GIGE_PORT.SPEED, GIGE_PORT.MAX_SPEED, GIGE_PORT.MAC_ADDRESS, GIGE_PORT.PORT_NAME, GIGE_PORT.OPERATIONAL_STATUS, GIGE_PORT.LED_STATE, GIGE_PORT.SPEED_LED_STATE, GIGE_PORT.PORT_TYPE, GIGE_PORT.PERSISTENTLY_DISABLED, GIGE_PORT.
E Views HBA_PORT.CNA_PORT_ID, HBA_PORT.PORT_NWWN, HBA_PORT.PHYSICAL_PORT_WWN, HBA_PORT.SWITCH_IP, HBA_PORT.PRINCIPAL_SWITCH_WWN, HBA_PORT.HBA_ID, HBA_PORT.PORT_NUMBER, HBA_PORT.NAME, HBA_PORT.FACTORY_PORT_WWN, HBA_PORT.FACTORY_NODE_WWN, HBA_PORT.PREBOOT_CREATED, HBA_PORT_DETAIL.PERSISTENT_BINDING, HBA_PORT_DETAIL.FABRIC_NAME, HBA_PORT_DETAIL.BOOT_OVER_SAN, HBA_PORT_DETAIL.BOOT_OPTION, HBA_PORT_DETAIL.BOOT_SPEED, HBA_PORT_DETAIL.BOOT_TOPOLOGY, HBA_PORT_DETAIL.BB_CREDIT, HBA_PORT_DETAIL.
Views E HBA_PORT_FCOE_DETAILS.MAX_FRAME_SIZE as FCOE_MAX_FRAME_SIZE, HBA_PORT_FCOE_DETAILS.MTU as FCOE_MTU, HBA_PORT_FCOE_DETAILS.PATH_TOV as FCOE_PATH_TOV, HBA_PORT_FCOE_DETAILS.SCSI_QUEUE_DEPTH as FCOE_SCSI_QUEUE_DEPTH, HBA_PORT_FCOE_DETAILS.STATE as FCOE_STATE, HBA_PORT_FCOE_DETAILS.SUPPORTED_CLASS as FCOE_SUPPORTED_CLASS, HBA_PORT_FCOE_DETAILS.TRL_SPEED as FCOE_TRL_SPEED, HBA_PORT_FCOE_DETAILS.TRL_STATE as FCOE_TRL_STATE, HBA_PORT_FCOE_DETAILS.PG_ID as FCOE_PG_ID, HBA_PORT_FCOE_DETAILS.
E Views HBA_REMOTE_PORT_LUN.TARGET_WWN, HBA_REMOTE_PORT_LUN.PHYSICAL_LUN, HBA_REMOTE_PORT_LUN.LUN_ID, HBA_REMOTE_PORT.FCP_IM_STATE, HBA_REMOTE_PORT.IO_LATENCY_MIN, HBA_REMOTE_PORT.IO_LATENCY_MAX, HBA_REMOTE_PORT.IO_LATENCY_AVERAGE, HBA_REMOTE_PORT.DATA_RETRANSMISSION_SUPPORT, HBA_REMOTE_PORT.REC_SUPPORT, HBA_REMOTE_PORT.TASK_RENTRY_IDENT_SUPPORT, HBA_REMOTE_PORT.CONFIRMED_COMPLETIONS_SUPPORT from HBA_TARGET, HBA_REMOTE_PORT, HBA_REMOTE_PORT_LUN where HBA_TARGET.
Views E DEVICE_ENCLOSURE.SERIAL_NUMBER, DEVICE_ENCLOSURE.FIRMWARE, DEVICE_ENCLOSURE.USER_DEFINED_VALUE1, DEVICE_ENCLOSURE.USER_DEFINED_VALUE2, DEVICE_ENCLOSURE.USER_DEFINED_VALUE3, DEVICE_ENCLOSURE.HCM_AGENT_VERSION, DEVICE_ENCLOSURE.OS_VERSION, DEVICE_ENCLOSURE.CREATED_BY, DEVICE_ENCLOSURE.TRACK_CHANGES, DEVICE_ENCLOSURE.LAST_UPDATE_TIME, DEVICE_ENCLOSURE.LAST_UPDATE_MODULE, DEVICE_ENCLOSURE.TRUSTED, DEVICE_ENCLOSURE.CREATION_TIME, DEVICE_ENCLOSURE.MISSING, DEVICE_ENCLOSURE.
E Views ISL.SOURCE_DOMAIN_ID, ISL.SOURCE_PORT_NUMBER, ISL.MISSING, SOURCE_VIRTUAL_SWITCH.ID as SOURCE_SWITCH_ID, SOURCE_VIRTUAL_SWITCH.NAME as SOURCE_SWITCH_NAME, SOURCE_VIRTUAL_SWITCH.WWN as SOURCE_SWITCH_WWN, SOURCE_VIRTUAL_SWITCH.CORE_SWITCH_ID as SOURCE_CORE_SWITCH_ID, SOURCE_VIRTUAL_SWITCH.BASE_SWITCH as SOURCE_BASE_SWITCH, SOURCE_SWITCH_PORT.ID as SOURCE_SWITCH_PORT_ID, SOURCE_SWITCH_PORT.WWN as SOURCE_SWITCH_PORT_WWN, SOURCE_SWITCH_PORT.NAME as SOURCE_SWITCH_PORT_NAME, SOURCE_SWITCH_PORT.
Views E ISL_INFO.TYPE, ISL_INFO.SOURCE_PORT_NUMBER, ISL_INFO.SOURCE_SWITCH_ID, SOURCE_CORE_SWITCH.IP_ADDRESS as SOURCE_SWITCH_IP_ADDRESS, SOURCE_VIRTUAL_SWITCH.WWN as SOURCE_SWITCH_WWN, ISL_INFO.SOURCE_DOMAIN_ID as MASTER_PORT, ISL_INFO.SOURCE_SWITCH_NAME, ISL_INFO.SOURCE_SWITCH_PORT_ID, ISL_INFO.DEST_PORT_NUMBER, ISL_INFO.DEST_SWITCH_ID, DEST_CORE_SWITCH.IP_ADDRESS as DEST_SWITCH_IP_ADDRESS, DEST_VIRTUAL_SWITCH.WWN as DEST_SWITCH_WWN, ISL_INFO.SOURCE_SWITCH_PORT_WWN, ISL_INFO.
E Views PHANTOM_PORT_INFO create or replace view PHANTOM_PORT_INFO as select PHANTOM_PORT.ID, PHANTOM_PORT.WWN, PHANTOM_PORT.VIRTUAL_SWITCH_ID, PHANTOM_PORT.PORT_NUMBER, PHANTOM_PORT.PORT_ID, PHANTOM_PORT.SPEED, PHANTOM_PORT.MAX_SPEED, PHANTOM_PORT.TYPE, PHANTOM_PORT.REMOTE_NODE_WWN, PHANTOM_PORT.REMOTE_PORT_WWN, PHANTOM_PORT.PHANTOM_TYPE, PHANTOM_PORT.BB_FABRIC_ID, VIRTUAL_SWITCH.WWN as VIRTUAL_SWITCH_WWN from PHANTOM_PORT, VIRTUAL_SWITCH where PHANTOM_PORT.VIRTUAL_SWITCH_ID = VIRTUAL_SWITCH.
Views E SWITCH_PORT.VIRTUAL_SWITCH_ID, SWITCH_PORT.USER_PORT_NUMBER, SWITCH_PORT.TYPE from PORT_BOTTLENECK_STATUS left outer join SWITCH_PORT on PORT_BOTTLENECK_STATUS.SWITCH_PORT_ID = SWITCH_PORT.ID; PORT_GROUP_INFO create or replace view PORT_GROUP_INFO as select SWITCH_PORT.ID as PORT_ID, SWITCH_PORT.NAME as SWITCH_PORT_NAME, SWITCH_PORT.WWN, SWITCH_PORT.HEALTH, SWITCH_PORT.STATUS, SWITCH_PORT.PORT_NUMBER, SWITCH_PORT.SLOT_NUMBER, SWITCH_PORT.FICON_SUPPORTED, SWITCH_PORT.STATE, SWITCH_PORT.
E Views SCOM_EE_MONITOR_INFO This view provides combined ee_monitor, ee_monitor_stats, device_port and device_node tables to get the EE Monitor information for SCOM plug-in. create or replace view SCOM_EE_MONITOR_INFO as select distinct EE_MONITOR.NAME, EE_MONITOR.SWITCH_PORT_ID, EE_MONITOR.SOURCE_PORT_ID, EE_MONITOR.DEST_PORT_ID, EE_MONITOR_STATS.TX, EE_MONITOR_STATS.RX, EE_MONITOR_STATS.CRCERRORS, EE_MONITOR_STATS.CREATION_TIME, SOURCE_PORT.PORT_ID as SID, DEST_PORT.PORT_ID as DID, SOURCE_NODE.
Views E SENSOR.VERSION, SENSOR.CREATION_TIME, SENSOR.LAST_UPDATE_TIME, SENSOR.FRU_TYPE, SENSOR.UNIT_NUMBER, SENSOR.STATE, CORE_SWITCH.WWN as PHYSICAL_SWITCH_WWN, VIRTUAL_SWITCH.SWITCH_MODE as VIRTUAL_SWITCH_MODE from SENSOR, CORE_SWITCH, VIRTUAL_SWITCH where SENSOR.CORE_SWITCH_ID = CORE_SWITCH.ID and SENSOR.CORE_SWITCH_ID = VIRTUAL_SWITCH.CORE_SWITCH_ID; SMART_CARD_USAGE_INFO create or replace view SMART_CARD_USAGE_INFO as select SC.ID SMART_CARD_ID, SC.CARD_TYPE, SC.CARD_INFO, SC.CARDCN_ID, SC.
E Views SMART_CARD SC, ENCRYPTION_GROUP EG, RECOVERY_CARD_GROUP_MAPPING RCGM where SC.ID = RCGM.SMART_CARD_ID and EG.ID = RCGM.ENCRYPTION_GROUP_ID and SC.CARD_TYPE = 1 union select SC.ID SMART_CARD_ID, SC.CARD_TYPE, SC.CARD_INFO, SC.CARDCN_ID, SC.FIRST_NAME, SC.LAST_NAME, SC.NOTES, SC.CREATION_TIME, EE.ID ENGINE_ID, -1 ENCRYPTION_GROUP_ID, '' GROUP_NAME, -1 CARD_POSITION, EE.SWITCH_ID CRYPTO_SWITCH_ID, EE.
Views E CORE_SWITCH.NAT_PRIVATE_IP_ADDRESS, CORE_SWITCH.ALTERNATE_IP_ADDRESS, VIRTUAL_SWITCH.ID, VIRTUAL_SWITCH.NAME, VIRTUAL_SWITCH.OPERATIONAL_STATUS, VIRTUAL_SWITCH.SWITCH_MODE, VIRTUAL_SWITCH.AD_CAPABLE, VIRTUAL_SWITCH.WWN, VIRTUAL_SWITCH.ROLE, VIRTUAL_SWITCH.FCS_ROLE, VIRTUAL_SWITCH.DOMAIN_ID, VIRTUAL_SWITCH.VIRTUAL_FABRIC_ID, VIRTUAL_SWITCH.BASE_SWITCH, VIRTUAL_SWITCH.MAX_ZONE_CONFIG_SIZE, VIRTUAL_SWITCH.CREATION_TIME, VIRTUAL_SWITCH.LAST_UPDATE_TIME, VIRTUAL_SWITCH.USER_NAME, VIRTUAL_SWITCH.
E Views CORE_SWITCH_DETAILS.TAG, CORE_SWITCH_DETAILS.ACT_CP_PRI_FW_VERSION, CORE_SWITCH_DETAILS.ACT_CP_SEC_FW_VERSION, CORE_SWITCH_DETAILS.STBY_CP_PRI_FW_VERSION, CORE_SWITCH_DETAILS.STBY_CP_SEC_FW_VERSION, CORE_SWITCH_DETAILS.TYPE as DETAILS_TYPE, CORE_SWITCH_DETAILS.EGM_CAPABLE, CORE_SWITCH_DETAILS.SUB_TYPE, CORE_SWITCH_DETAILS.PARTITION, CORE_SWITCH_DETAILS.MAX_NUM_OF_BLADES, CORE_SWITCH_DETAILS.SNMP_INFORMS_ENABLED, CORE_SWITCH_DETAILS.VENDOR_VERSION, CORE_SWITCH_DETAILS.
Views E SWITCH_PORT.ACTUAL_DISTANCE, SWITCH_PORT.LONG_DISTANCE_SETTING, SWITCH_PORT.DEGRADED_PORT, SWITCH_PORT.REMOTE_NODE_WWN, SWITCH_PORT.REMOTE_PORT_WWN, SWITCH_PORT.LICENSED, SWITCH_PORT.SWAPPED, SWITCH_PORT.TRUNKED, SWITCH_PORT.TRUNK_MASTER, SWITCH_PORT.PERSISTENT_DISABLE, SWITCH_PORT.FICON_SUPPORTED, SWITCH_PORT.BLOCKED, SWITCH_PORT.PROHIBIT_PORT_NUMBERS, SWITCH_PORT.PROHIBIT_PORT_COUNT, SWITCH_PORT.NPIV, SWITCH_PORT.NPIV_CAPABLE, SWITCH_PORT.NPIV_ENABLED, SWITCH_PORT.
E Views SWITCH_SNMP_INFO create or replace view SWITCH_SNMP_INFO as select CORE_SWITCH.ID as PHYSICAL_SWITCH_ID, CORE_SWITCH.NAME as PHYSICAL_SWITCH_NAME, CORE_SWITCH.IP_ADDRESS, CORE_SWITCH.WWN as PHYSICAL_SWITCH_WWN, CORE_SWITCH.OPERATIONAL_STATUS as PHYSICAL_OPERATIONAL_STATUS, CORE_SWITCH.TYPE, CORE_SWITCH.MAX_VIRTUAL_SWITCHES, CORE_SWITCH.FIRMWARE_VERSION, CORE_SWITCH.VENDOR, CORE_SWITCH.REACHABLE, CORE_SWITCH.UNREACHABLE_TIME, CORE_SWITCH.MODEL, CORE_SWITCH_DETAILS.CONTACT, CORE_SWITCH_DETAILS.
Views E coalesce(SNMP_CREDENTIALS.WRITE_COMMUNITY_STRING, (select SNMP_PROFILE.WRITE_COMMUNITY_STRING from SNMP_PROFILE where SNMP_PROFILE.NAME='default')) as SNMP_WRITE_COMMUNITY_STRING, coalesce(SNMP_CREDENTIALS.USER_NAME, (select SNMP_PROFILE.USER_NAME from SNMP_PROFILE where SNMP_PROFILE.NAME='default')) as SNMP_USER_NAME, coalesce(SNMP_CREDENTIALS.CONTEXT_NAME, (select SNMP_PROFILE.CONTEXT_NAME from SNMP_PROFILE where SNMP_PROFILE.NAME='default')) as SNMP_CONTEXT_NAME, coalesce(SNMP_CREDENTIALS.
E Views VIRTUAL_FCOE_PORT.PORT_TYPE, VIRTUAL_FCOE_PORT.ENABLED, VIRTUAL_FCOE_PORT.STATUS, VIRTUAL_FCOE_PORT.TRUNK_INDEX, VIRTUAL_FCOE_PORT.PORT_NUMBER, VIRTUAL_FCOE_PORT.NAME, VIRTUAL_FCOE_PORT.SLOT_NUMBER, VIRTUAL_FCOE_PORT.VLAN_ID, VIRTUAL_FCOE_PORT.DEVICE_COUNT, VIRTUAL_FCOE_PORT.PEER_MAC, VIRTUAL_SWITCH.WWN as VIRTUAL_SWITCH_WWN, VIRTUAL_SWITCH.ROLE as SWITCH_ROLE, VIRTUAL_SWITCH.VIRTUAL_FABRIC_ID as VIRTUAL_FABRIC_ID, VIRTUAL_SWITCH.DOMAIN_ID as DOMAIN_ID, VIRTUAL_SWITCH.
Views E from DEVICE_PORT left outer join USER_DEFINED_DEVICE_DETAIL on DEVICE_PORT.WWN = USER_DEFINED_DEVICE_DETAIL.WWN, CORE_SWITCH, SWITCH_PORT, VIRTUAL_SWITCH, VM_CONNECTIVITY, DEVICE_NODE, FABRIC where VM_CONNECTIVITY.ADAPTER_PORT_WWN = DEVICE_PORT.WWN and DEVICE_PORT.SWITCH_PORT_WWN = SWITCH_PORT.WWN and SWITCH_PORT.VIRTUAL_SWITCH_ID = VIRTUAL_SWITCH.ID and VIRTUAL_SWITCH.CORE_SWITCH_ID = CORE_SWITCH.ID and DEVICE_PORT.NODE_ID = DEVICE_NODE.ID and DEVICE_NODE.FABRIC_ID = FABRIC.
E Views and and and and SWITCH_PORT.VIRTUAL_SWITCH_ID = VIRTUAL_SWITCH.ID VIRTUAL_SWITCH.CORE_SWITCH_ID = CORE_SWITCH.ID DEVICE_PORT.NODE_ID = DEVICE_NODE.ID DEVICE_NODE.FABRIC_ID = FABRIC.ID; VM_EE_MONITOR_INFO This view provides combined ee_monitor, ee_monitor_stats, device_port and device_node tables to get the EE Monitor information for vmplug-in. create or replace view VM_EE_MONITOR_INFO as select distinct EE_MONITOR.NAME, EE_MONITOR.SWITCH_PORT_ID, EE_MONITOR.SOURCE_PORT_ID, EE_MONITOR.
Views E VM_HOST.CPU_COUNT, VM_HOST.CPU_TYPE, VM_HOST.CPU_RESOURCES as HOST_CPU_RESOURCES, VM_HOST.MEM_RESOURCES as HOST_MEM_RESOURCES, VM_HOST.LICENSE_SERVER, VM_HOST.BOOT_TIME as HOST_BOOT_TIME, CLUSTER.NAME as CLUSTER_NAME, CLUSTER.IP_ADDRESS as CLUSTER_ADDRESS, VIRTUAL_MACHINE.ID as VM_ID, VIRTUAL_MACHINE.HYPERVISOR_VM_ID, VIRTUAL_MACHINE.NAME as VM_NAME, VIRTUAL_MACHINE.DESCRIPTION as VM_DESCRIPTION, VIRTUAL_MACHINE.OS as VM_OS, VIRTUAL_MACHINE.STATUS as VM_STATUS, VIRTUAL_MACHINE.
E Views VM_PATH.ACTIVE as PATH_ACTIVE, VM_PATH.PREFERRED as PATH_PREFERRED from VM_LUN join VM_PATH on VM_LUN.ID = VM_PATH.LUN_ID; VM_STATISTICS_INFO This view gets the FC port statistics for the VM Connectivity data. create or replace view VM_STATISTICS_INFO as select distinct DEVICE_PORT.SWITCH_PORT_WWN, DEVICE_PORT.DOMAIN_ID, VM_CONNECTIVITY.HYPERVISOR_HOST, VM_CONNECTIVITY.ADAPTER_PORT_WWN, VM_CONNECTIVITY.ADAPTER_PORT_STATUS, VM_CONNECTIVITY.HYPERVISOR_VM_ID, VM_CONNECTIVITY.VM_NAME, CORE_SWITCH.
Views E CORE_SWITCH.NAME as CORE_NAME, SWITCH_TE_PORT_STATS.TRANSMIT_OK, SWITCH_TE_PORT_STATS.RECEIVE_OK, SWITCH_TE_PORT_STATS.TRANSMIT_OK_PERCENT_UTIL, SWITCH_TE_PORT_STATS.RECEIVE_OK_PERCENT_UTIL, -1,-1,-1,-1,-1, SWITCH_TE_PORT_STATS.CREATION_TIME, VIRTUAL_SWITCH.NAME as VIRTUAL_NAME, SWITCH_PORT.STATUS as SWITCH_PORT_STATUS, SWITCH_PORT.PORT_ID, SWITCH_PORT.
E Views ZONE_DB.ID = ZONE_DB_CONFIG.
Views E ); -- Name: accessible_port_group; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE accessible_port_group ( accessible_entity_id integer NOT NULL, port_group_id integer ); -- Name: accessible_vip_server; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE accessible_vip_server ( accessible_entity_id integer NOT NULL, server_ip character varying(39) NOT NULL, server_mode character varying(39) NOT NULL, server_iron_ip character varying(39) ); -- Name: acl_spec; Typ
E Views -- Name: address_spec; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE address_spec ( address_spec_id integer NOT NULL, table_subtype character varying(32) NOT NULL ); -- Name: alert; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE alert ( alert_id integer NOT NULL, name character varying(32) NOT NULL, user_id integer NOT NULL, description character varying(255), status character(1), props_str character varying(2048), last_updated bigint, severity smallint,
Views E macaddr character varying(17), authenticated smallint, associated smallint, forwarding smallint, lastkeytype smallint, manualblock smallint, dynamicblock smallint, attemptsconsumed integer, attemptsremained integer, remainedcycletime integer, remainedblocktime integer ); -- Name: ap_ids_last_saved; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE ap_ids_last_saved ( device_id integer NOT NULL, time_stamp bigint NOT NULL ); -- Name: ap_ids_sqnum_seq; Type: SEQUENCE; Schema: dcm;
E Views authenticated smallint, associated smallint, isforwarding smallint, keytype smallint, lastauthenticatedtime bigint, associatedtime bigint, lastassociatedtime bigint, lastdisassociatedtime bigint, txpacketcount bigint, rxpacketcount bigint, txbytecount bigint, rxbytecount bigint, time_interval bigint, radio smallint, channel smallint ); -- Name: ap_station_last_saved; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE ap_station_last_saved ( device_id integer NOT NULL, time_stamp b
Views E ); -- Name: block_mac_list; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE block_mac_list ( block_mac_list_id integer NOT NULL, mac character varying(32) NOT NULL, radio_vap numeric(2,0), lockout_time character varying(64), last_seen_ap_id integer, last_time_seen character varying(64), device_group_id integer, is_full_device_group numeric(1,0), deployment_setting_id integer ); -- Name: cfg_backup_archive; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE cfg_
E Views -- Name: cfg_restore_backup_detail; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE cfg_restore_backup_detail ( cfg_backup_detail_id integer NOT NULL, user_id integer, cfg_file_revision_id integer ); -- Name: chassis_component; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE chassis_component ( chassis_component_id integer NOT NULL, device_id integer NOT NULL, name character varying(128), description character varying(128), class character varying(32), hw_re
Views E exec_option numeric(2,0), is_public numeric(1,0), content character varying, report_file_name character varying(256), template_report_type numeric(2,0) ); -- Name: cli_template_report_execution; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE cli_template_report_execution ( cli_template_report_execution_id integer NOT NULL, device_deployment_job_id integer, cli_template_id integer, content character varying, compare_status numeric(2,0) ); -- Name: cli_template_target_device; Ty
E Views -- Name: collector_target_entry; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE collector_target_entry ( collector_target_entry_id integer NOT NULL, collector_id integer, target_id integer NOT NULL, prop_str character varying(8192), collector_target_entry_type integer ); -- Name: collector_threshold_rearm_trigger; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE collector_threshold_rearm_trigger ( collector_threshold_rearm_trigger_id integer NOT NULL, collec
Views E device_deployment_job_id integer NOT NULL, interface_id integer NOT NULL ); -- Name: deployment_setting; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE deployment_setting ( deployment_setting_id integer NOT NULL, scenario_id integer NOT NULL, user_id integer NOT NULL, is_write_to_ram numeric(1,0), is_reload numeric(1,0), deployment_mode character(1), do_pre_post_snapshot numeric(2,0) NOT NULL, cli_template_id integer NOT NULL, pre_post_deploy_setting_id integer NOT NULL, post_
E Views local_username_port_cfg character varying(512), local_password_port_cfg character varying(512), local_username_read_only character varying(512), local_password_read_only character varying(512), radius_username_port_cfg character varying(512), radius_password_port_cfg character varying(512), radius_username_read_only character varying(512), radius_password_read_only character varying(512), tac_username_port_cfg character varying(512), tac_password_port_cfg character varying(512), tac_username_read_
Views E name_key character varying(64) NOT NULL, device_config_id integer NOT NULL, value_str bytea NOT NULL, line_num smallint NOT NULL, key1 smallint, key2 smallint, ref_table_name character varying(64), table_id integer, table_subtype character varying(32) NOT NULL, type_key character varying(32) ); -- Name: device_deployment_job; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE device_deployment_job ( device_config_id integer NOT NULL, device_deployment_job_id integer NOT NULL, depl
E Views start_time numeric(20,0) NOT NULL, duration integer ); -- Name: discovery_log; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE discovery_log ( discovery_log_id integer NOT NULL, discovery_cycle_id integer NOT NULL, "timestamp" numeric(20,0), category smallint, device_ip character varying(40), messages character varying(4096) ); -- Name: discovery_profile; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE discovery_profile ( discovery_profile_id integer NOT NUL
Views E -- Name: events; Type: VIEW; Schema: dcm; Owner: dcmadmin CREATE VIEW events AS SELECT emain.trap_log_id, emain.trap_sender, emain."timestamp", emain.severity, emsgs.messages, emain.is_ack, emain.log_type, emain.slot, emain.port, emain.device_id, emain.event_action_id, emain.device_group_id, emain.port_group_id, emain.trap_device_ip, emain.log_sub_type, emain.unit FROM (events_main emain LEFT JOIN events_messages emsgs ON ((emain.messages_id = emsgs.
E Views is_port_vlan_enabled numeric(1,0), architecture_type numeric(2,0), build_label character varying(64), ssl_slot numeric(4,0) ); -- Name: foundry_module; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE foundry_module ( module_id integer NOT NULL, serial_num character varying(32), dram_size numeric(4,0), boot_flash_size numeric(4,0), module_type numeric(4,0), code_flash_size numeric(4,0), expansion_module_type numeric(4,0), expansion_module_description character varying(128) ); --
Views E -- Name: image_archive; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE image_archive ( image_archive_id integer NOT NULL, product_type character varying(32) NOT NULL, feature_mask character varying(32), supported_type character varying(32) NOT NULL, flash_size integer, location character varying(255) NOT NULL, file_name character varying(64) NOT NULL, version_label character varying(32) NOT NULL, release_datetime character varying(64), special_key character varying(32), image_
E Views CREATE TABLE ip_address_spec ( address_spec_id integer NOT NULL, ip_address character varying(40) NOT NULL, wildcard_mask character varying(40) ); -- Name: inm_ip_interface; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE inm_ip_interface ( ip_interface_id integer NOT NULL, ip_routing_service_id integer, interface_id integer, device_id integer NOT NULL, ip_subnet_id integer NOT NULL, ip_address character varying(40) NOT NULL, subnet_mask character varying(40) ); -- Name: ip_rou
Views E network_number character varying(32) NOT NULL, frame_type numeric(4,0) NOT NULL ); -- Name: ironclad_adaptive_entry; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE ironclad_adaptive_entry ( policy_entry_id integer NOT NULL, normal_burst numeric(20,3), normal_burst_type character(1), max_burst numeric(20,3), max_burst_type character(1), conform_action numeric(2,0), exceed_action numeric(2,0), vlan_id numeric(4,0) ); -- Name: jetcore_adaptive_entry; Type: TABLE; Schema: dcm; Own
E Views config_state character varying(1), time_stamp character varying(64) ); -- Name: license_files; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE license_files ( license_file_id integer NOT NULL, identifier character varying(255) NOT NULL, license_details character varying(255) NOT NULL, is_eval numeric(1,0) NOT NULL ); -- Name: license_parameters; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE license_parameters ( license_param_id integer NOT NULL, identifier
Views E type numeric(2,0) ); -- Name: loopback_interface; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE loopback_interface ( interface_id integer NOT NULL ); -- Name: mac_filter_entry; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mac_filter_entry ( mac_filter_entry_id integer NOT NULL, mac_filter_group_id integer, mac_filter_num numeric(8,0) NOT NULL, is_permit numeric(1,0), src_mac_address character varying(24) NOT NULL, src_address_mask character varying(24),
E Views is_independent numeric(1,0) NOT NULL, xml_instance bytea NOT NULL, key1 character varying(128), key2 character varying(128), last_updated_time numeric(20,0), is_internal numeric(1,0) ); -- Name: mib_object; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mib_object ( mib_object_id integer NOT NULL, oid character varying(128) NOT NULL, name character varying(64), value_type numeric(2,0), target_type numeric(2,0) ); -- Name: module; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tabl
Views E mpls_admin_group_db_id integer NOT NULL, interface_id integer NOT NULL ); -- Name: mpls_lsp; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mpls_lsp ( mpls_lsp_db_id integer NOT NULL, table_subtype character varying(32) NOT NULL, name character varying(255) NOT NULL, destination_ip_address character varying(255) NOT NULL, oper_status smallint NOT NULL, device_id integer NOT NULL ); -- Name: mpls_path; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mpls_pat
E Views ); -- Name: mpls_rsvp_lsp_admin_group_container; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mpls_rsvp_lsp_admin_group_container ( mpls_rsvp_lsp_admin_group_container_db_id integer NOT NULL, mpls_rsvp_lsp_parameters_db_id integer, mpls_rsvp_lsp_frr_parameters_db_id integer ); -- Name: mpls_rsvp_lsp_frr_parameters; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mpls_rsvp_lsp_frr_parameters ( mpls_rsvp_lsp_frr_parameters_db_id integer NOT NULL, bandwidth
Views E ); -- Name: mpls_service; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mpls_service ( mpls_service_db_id integer NOT NULL, name character varying(255) NOT NULL, vcid bigint NOT NULL, mpls_service_type smallint NOT NULL, vll_mode smallint, status smallint NOT NULL, conflicts integer NOT NULL, last_updated_time numeric(20,0) ); -- Name: mpls_service_device_relation; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE mpls_service_device_relation ( mpls_service_
E Views mrp_ring_device_db_id integer NOT NULL, mrp_ring_id integer NOT NULL, device_id integer NOT NULL, port_vlan_db_id integer DEFAULT 0 NOT NULL, mrp_ring_name character varying(255), topo_grp_id integer DEFAULT 0 NOT NULL, state smallint NOT NULL, role smallint NOT NULL, hello_time integer NOT NULL, pre_fwd_time integer NOT NULL, pri_port_interface_id integer DEFAULT 0 NOT NULL, pri_port_state smallint NOT NULL, pri_port_type smallint NOT NULL, pri_port_active_interface_id integer DEFAULT 0 NOT NULL,
Views E port_num smallint NOT NULL, module_id integer NOT NULL, is_port_present smallint, table_subtype character varying(32) NOT NULL ); -- Name: policy; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE policy ( policy_id integer NOT NULL, name character varying(64) NOT NULL, user_id integer, is_public numeric(1,0), description character varying(256) ); -- Name: policy_entry; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE policy_entry ( policy_entry_id integer NOT
E Views -- Name: port_vlan; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE port_vlan ( vlan_db_id integer NOT NULL, stp numeric(1,0), vlan_id smallint NOT NULL, qos smallint, global_vlan_db_id integer, stp_instance_id integer ); -- Name: pos_interface; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE pos_interface ( interface_id integer NOT NULL ); -- Name: inm_privilege; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE inm_privilege ( privilege_i
Views E last_updated bigint, name character varying(64) NOT NULL, messages character varying(255), policy_desc character varying(255) ); -- Name: query_based_device_group; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE query_based_device_group ( device_group_id integer NOT NULL, query_text character varying(512) ); -- Name: radio_interface; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE radio_interface ( interface_id integer NOT NULL, radio_type numeric(2,0) NOT N
E Views ); -- Name: report_definition; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE report_definition ( report_definition_id integer NOT NULL, name character varying(64) NOT NULL, category character varying(20) NOT NULL, user_id integer NOT NULL, type numeric(2,0) NOT NULL, last_modified character varying(64) NOT NULL, description character varying(128), definition character varying NOT NULL, is_with_data_source numeric(1,0), prompt numeric(1,0) DEFAULT 0, is_prompt_fields_filled nu
Views E sensor_total integer, sensor_up integer, sensor_down integer, sensor_relief integer, last_viewed_timestamp bigint NOT NULL ); -- Name: rf_overview_logs; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE rf_overview_logs ( log_timestamp bigint NOT NULL, log_message character varying(512) NOT NULL ); -- Name: rfmon_ap; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE rfmon_ap ( sqnum integer NOT NULL, time_stamp bigint, device_id integer NOT NULL, sys_up_time int
E Views totalcrcerrframes integer, totalfragerrframes integer, totalretryframes integer, totalassocreq integer, totalassocresp integer, totalreassocreq integer, totalreassocresp integer, totalprobereq integer, totalproberesp integer, totalbeacon integer, totaldisassoc integer, totalauth integer, totaldeauth integer, totalcriticalalerts integer, totalmoderatealerts integer, totalminor integer ); -- Name: rfmon_ap_last_saved; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE rfmon_ap_last_
Views E authtype smallint, networkmode smallint, wepenabled smallint, cfpollable smallint, shortpreamblemode smallint, rsnsupported smallint, onexenabled smallint, shortslottime integer, failedreassocattempts integer, failedassocattempts integer, associateid integer, rssi integer, listeninterval integer, ssidlen smallint, ssid character varying(256), ipaddress character varying(40), deauthreasoncode integer, deassocreasoncode integer, ratesupported character varying(256), extratesupported character varyin
E Views -- Name: rl_access_control_group; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE rl_access_control_group ( rl_access_control_group_id integer NOT NULL, name character varying(64) NOT NULL, user_id integer, is_public numeric(1,0), description character varying(256) ); -- Name: rl_access_control_list; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE rl_access_control_list ( rl_access_control_list_id integer NOT NULL, rl_acl_num numeric(8,0) NOT NULL, is_standa
Views E privilege_id integer NOT NULL, role_id integer NOT NULL ); -- Name: routing_service; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE routing_service ( service_id integer NOT NULL ); -- Name: scenario; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE scenario ( scenario_id integer NOT NULL, name character varying(256) NOT NULL, user_id integer NOT NULL, description character varying(1024), is_internal numeric(1,0) NOT NULL, creation_time character varying(16)
E Views -- Name: scenario_port_binding; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE scenario_port_binding ( scenario_binding_id integer NOT NULL, interface_id integer NOT NULL ); -- Name: scenario_port_group_binding; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE scenario_port_group_binding ( port_group_id integer NOT NULL, scenario_binding_id integer NOT NULL ); -- Name: schedule_email_user; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE s
Views E ); -- Name: service_group_spec; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE service_group_spec ( port_spec_id integer NOT NULL, service_group_id integer ); -- Name: service_name_entry; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE service_name_entry ( service_name_entry_id integer NOT NULL, service_group_id integer NOT NULL, service_port_definition_id integer NOT NULL, name character varying(32) ); -- Name: service_port_definition; Type: TABLE; Schema:
E Views L4_DEST_PORT integer, SRC_SUBNET_BITS smallint, DEST_SUBNET_BITS smallint, LOCAL_AS bigint, SRC_AS bigint, SRC_PEER_AS bigint, SFLOW_IP_ROUTE_INFO_ID integer, IP_FLOW_LABEL integer, SRC_USER integer, DEST_USER integer, FRAMES bigint not null, BYTES bigint not null, TCP_FLAGS smallint ); create table SFLOW_STAGING_SLNUM ( MIN_SLNUM bigint ) with (autovacuum_vacuum_threshold=4); -- Name: sflow_hour_summary; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: create table SFLOW_HOUR_SUMMARY ( SLNU
Views E create table SFLOW_HOUR_SUMMARY_SLNUM ( MAX_SLNUM bigint ) with (autovacuum_vacuum_threshold=4); -- Name: sflow; Type: VIEW; Schema: dcm; Owner: dcmadmin create or replace view SFLOW as select DEVICE_ID, IN_SLOT, IN_PORT, OUT_SLOT, OUT_PORT, L4_PROTOCOL, IP_TOS, SRC_SUBNET_BITS, DEST_SUBNET_BITS, IN_PRIORITY, OUT_PRIORITY, IN_VLAN, OUT_VLAN, L3_PROTOCOL, L4_SRC_PORT, L4_DEST_PORT, TIME_IN_SECONDS, SRC_MAC, DEST_MAC, L3_SRC_ADDR, L3_DEST_ADDR, TCP_FLAGS, LOCAL_AS, SRC_AS, SRC_PEER_AS, SFLOW_IP_ROUT
E Views -- Name: sflow_minute_bgp_view; Type: VIEW; Schema: dcm; Owner: dcmadmin create or replace view SFLOW_MINUTE_BGP_VIEW as select DEVICE_ID, TIME_IN_SECONDS, SRC_AS, SFLOW_IP_ROUTE_INFO_ID, IN_VLAN, OUT_VLAN, FRAMES, BYTES from SFLOW_MINUTE_BGP where SLNUM <= (select MAX_SLNUM from SFLOW_MINUTE_BGP_SLNUM fetch first 1 rows only) union all select DEVICE_ID, TIME_IN_SECONDS, SRC_AS, SFLOW_IP_ROUTE_INFO_ID, IN_VLAN, OUT_VLAN, FRAMES, BYTES from SFLOW_STAGING where SLNUM >= (select MIN_SLNUM from SFLOW_
Views E IN_VLAN smallint, OUT_VLAN smallint, SRC_MAC bytea, DEST_MAC bytea ); create table SFLOW_MINUTE_MAC_SLNUM ( MAX_SLNUM bigint ) with (autovacuum_vacuum_threshold=4); -- Name: sflow_minute_mac_view; Type: VIEW; Schema: dcm; Owner: dcmadmin create or replace view SFLOW_MINUTE_MAC_VIEW as select DEVICE_ID, TIME_IN_SECONDS, SRC_MAC, DEST_MAC, IN_VLAN, OUT_VLAN, FRAMES, BYTES from SFLOW_MINUTE_MAC where SLNUM <= (select MAX_SLNUM from SFLOW_MINUTE_MAC_SLNUM fetch first 1 rows only) union all select DEVI
E Views where SLNUM >= (select MIN_SLNUM from SFLOW_STAGING_SLNUM fetch first 1 rows only); -- Name: sflow_report_l3_source; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE sflow_report_l3_source ( sflow_report_l3_source_id integer NOT NULL, report_definition_id integer NOT NULL, address_group_id integer, ip_subnet_definition_id integer ); -- Name: sflow_report_l4_source; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE sflow_report_l4_source ( sflow_report_l4_source
Views E constraint PK_SNMP_EXPR_DATA primary key (ID) ); -- Name: snmp_expression; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: create table SNMP_EXPRESSION ( EXPRESSION_ID serial not null, NAME character varying(64) not null, DESCRIPTION character varying(512), EQUATION character varying(1024) ); -- Name: snmp_fwd_aa; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE snmp_fwd_aa ( snmp_fwd_aa_id integer NOT NULL, trap_community character varying(64), trap_user character varyin
E Views CREATE TABLE snmp_fwd_targets ( snmp_fwd_targets_id integer NOT NULL, is_enable character varying(8) DEFAULT 'Yes'::character varying NOT NULL, ip_address character varying(40) NOT NULL, snmp_trap_port integer DEFAULT 162 NOT NULL, snmp_version character varying(8) DEFAULT 'v2/v3'::character varying NOT NULL, snmp_notify_type character varying(1) DEFAULT '1'::character varying NOT NULL, snmp_to_nnm character varying(8) DEFAULT 'No'::character varying NOT NULL ); -- Name: snmp_fwd_trap_oid; Type: T
Views E -- Name: ssl_certificate; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE ssl_certificate ( ssl_certificate_id integer NOT NULL, name character varying(255), location character varying(255), file_name character varying(255), key_id integer NOT NULL, cert_type numeric(2,0) NOT NULL, start_time numeric(20,0), expiration_time numeric(20,0), format numeric(2,0) NOT NULL, description character varying(1024), notification_time numeric(20,0) NOT NULL DEFAULT 0, notification_sent numer
E Views CREATE TABLE stp_entry ( stp_entry_id integer NOT NULL, device_id integer NOT NULL, vlan_id integer NOT NULL, port_id character varying(32) NOT NULL, port_priority smallint NOT NULL, path_cost integer NOT NULL, port_state smallint NOT NULL, designated_cost integer NOT NULL, designated_root character varying(32) NOT NULL, designated_bridge character varying(32) NOT NULL, edge_port smallint NOT NULL, p2p smallint NOT NULL, oper_path_cost integer NOT NULL, port_role smallint NOT NULL, bpdu_tx integer
Views E row_id integer NOT NULL, file_pointer bigint NOT NULL, file_name character varying(512) ); -- Name: system_profile; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE system_profile ( system_profile_id integer NOT NULL, new_installation_update_status character varying(64) NOT NULL, db_schema_string character varying(20), is_demo_version numeric(1,0), demo_expiration_datetime character varying(32), is_full_install numeric(1,0) DEFAULT 0, serial_number character varying(64), system_
E Views -- Name: trap_backup_detail; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE trap_backup_detail ( cfg_backup_detail_id integer NOT NULL, cfg_change_user_name character varying(64), trap_log_id integer ); -- Name: trunk_group_interface; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE trunk_group_interface ( interface_id integer NOT NULL ); -- Name: trunk_group_member; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE trunk_group_member ( tru
Views E phone_number character varying(32), status character(1) NOT NULL, user_type numeric(2,0) DEFAULT 0 NOT NULL, email_address1 character varying(255), email_address2 character varying(255), email_address3 character varying(255), email_address4 character varying(255), email_alertflag1 character(1), email_alertflag2 character(1), email_alertflag3 character(1), email_alertflag4 character(1), last_updated character varying(32), previous_passwords_used character varying(2500), nbi_identity_key character v
E Views ); -- Name: vlan_dynamic_interface_member; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE vlan_dynamic_interface_member ( vlan_interface_relation_id integer NOT NULL ); -- Name: vlan_excluded_interface; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE vlan_excluded_interface ( vlan_interface_relation_id integer NOT NULL ); -- Name: vlan_interface_member; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE vlan_interface_member ( vlan_interfac
Views E -- Name: vpls_endpoint_relation; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE vpls_endpoint_relation ( mpls_service_endpoint_relation_db_id integer NOT NULL ); -- Name: vpnpt_authentication; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE vpnpt_authentication ( vpnpt_authentication_id integer NOT NULL, vpnpt_policy_id integer, realm_policy_id integer ); -- Name: vpnpt_policy; Type: TABLE; Schema: dcm; Owner: dcmadmin; Tablespace: CREATE TABLE vpnpt_policy
E Views xinfo character varying(64) ); -- Name: wired_interface; Type: VIEW; Schema: dcm; Owner: dcmadmin CREATE VIEW wired_interface AS SELECT l2.device_id, l2.device_ip_address, l2.physical_device_id, l2.unit_number, l2.slot_id, l2.slot_num, l2.module_id, l2.physical_port_id, l2.port_num, l2.interface_id, l2.name, l2.if_name, l2.identifier, l2.table_subtype, l2.tag_mode, l2.speed_in_mb, l2.physical_address, l2.duplex_mode, l3.ip_id, l3.ip_interface_id, l3.ip_address, l3.
Views E radio_interface.beacon_rate, radio_interface.dtim, radio_interface.rts_threshold, radio_interface.is_turbo_mode, radio_interface.radio_g_mode, radio_interface.max_associated_clients FROM radio_interface) wireless ON ((l2.interface_id = wireless.
E Views select * from SNMP_DATA_2HOUR union all select * from SNMP_DATA_1DAY; SNMP_EXPR_DATA_INFO create or replace view SNMP_EXPR_DATA_INFO as select * from SNMP_EXPR_DATA union all select * from SNMP_EXPR_DATA_30MIN union all select * from SNMP_EXPR_DATA_2HOUR union all select * from SNMP_EXPR_DATA_1DAY; SNMP_DATA_VIEW create view SNMP_DATA_VIEW AS ( ( SELECT de.device_id, de.ip_address AS device_ip, se.target_type, de.device_id AS target_id, de.sys_name AS target_name, 1 AS collectible_type, se.
Views E SELECT de.device_id, de.ip_address AS device_ip, sd.target_type, ifs.interface_id AS target_id, ifs.if_name AS target_name, 0 AS collectible_type, sd.mib_object_id AS collectible_id, sd.collector_id, ( SELECT perf_collector.name AS collector_name FROM perf_collector WHERE perf_collector.collector_id = sd.collector_id) AS collector_name, ( SELECT (mib_object.name::text || '.'::text) || sd.mib_index::text AS collectible_name FROM mib_object WHERE mib_object.mib_object_id = sd.
E 1238 Views Brocade Network Advisor SAN User Manual 53-1002167-01
Index A access levels defined, 979 features, 979–??, 980–981 roles, 979 accessing FTP server folder, 123 ACK emulation, device level, 656 activating Allow/Prohibit Matrix configuration, 711 LSAN zones, 606 zone configuration, 594 active session management, roles and access levels, 979 active sessions, viewing, 33 Adaptive Rate Limiting (ARL), 637 add/delete properties, roles and access levels, 980 Adding C3 discard frames threshold, 683 state change threshold, 690, 700 adding detached devices to fabric bin
C C3 Discard Frames threshold, 680 call home, 158 centers assigning a device, 170 assigning event filters, 172 disabling, 168 editing, 161 Brocade International, 161 e-mail, 164 EMC, 165 HP LAN, 166 IBM, 161 modem, 163 enabling, 167 enabling support save, 167 hiding, 161 removing a device, 170 removing all devices and filters, 171 removing event filters, 173 test connection, 168 viewing, 160 configuring, 158 roles and access levels, 979 status, determining, 17 system requirements, 159 viewing status, 169 ca
configuring allow/prohibit matrix, 706 asset polling, 121 bottleneck alert parameters, 803 call home, 158 cascaded FICON fabric, 714 client export port, 113 discovery, 49 e-mail notification, 844 encrypted storage in a multi-path environment, 517 explicit server IP address, 116 external FTP server, 125 FCIP advanced settings, 652 FCIP tunnels, 646 FICON emulation, 656 FTP server, 123 internal FTP server, 124 IP interfaces, 646 IP routes, 646 IPSec and IKE policies, 654 LDAP server, 220 login banner, 109 log
default zone (fabrics) disabling, 588 enabling, 588 defining, event filter, 171 delete switch configuration, 257 deleting Allow/Prohibit Matrix configuration, 712 end-to-end monitoring pairs, 796 fabrics, 55, 56, 72 FCIP tunnels, 665, 666 historical performance graph, 792 hosts, 73, 79 offline zone database, 618 property labels, 269 reports, 926 storage arrays, 302 technical support information, 918 threshold policies, 811 VM managers, 78 zone alias, 617 zone configuration, 617 zones, 616 deleting firmware
E edge fabrics about, 408 Edit menu, 932 editing property fields, 269 property labels, 268 storage array properties, 302 threshold policies, 809 thresholds, 694 views, 177 zone alias, 590 Element Manager, launching launching Element Manager, 197 e-mail event notification setup roles and access levels, 979 e-mail filter override, 323 e-mail notification configuring, 844 emailing technical support information, 918 enable SSL, 127 enabling bottleneck detection, 801 call home centers, 167 default zone for fabri
event action definitions configuring e-mail settings, 878 configuring varbind filters, 869 creating a new definition, 879 modifying an existing definition, 879 event actions, handling special events, 876 event custom reports adding a report schedule, 901 copying an existing definition, 898 defining report settings, 893 defining the report identity, 894 deleting a report definition, 899 editing a report definition, 899 filtering a report definition, 895 filtering events by date and time, 897 event details di
FC-FC routing about, 408 setting up, 409 supported switches, 407 FCIP advanced settings configuring, 652 connection properties viewing, 657 DSCP, 642 Ethernet connection troubleshooting, 670 Ethernet port properties viewing, 661 Fastwrite, 643 FC port properties viewing, 660 IPsec implementation, 640 L2CoS, 642 management roles and access levels, 980 performance graphs, Ethernet ports displaying, 666 performance graphs, FC ports displaying, 666 properties viewing, 658 QoS implementation, 642 services licens
FICON management roles and access levels, 980 filtering events for users, 323 master log events, 908 port connectivity view results, 274 real time performance data, 784 finding assigned thresholds, 702 firmware deleting files from repository, 261 downloading, 262 management, overview, 259 overwriting, 263 firmware management roles and access levels, 979 firmware repository deleting firmware files, 261 displaying, 260 importing into, 261 flyovers configuring, 96 turning on and off, 99 viewing, 99 FSPF link c
I IBM z/OS Global Mirror (z Gm), 644 icons device, 17, 18 products, 17, 18 IFL.
logging in remote client, 27 remote SMIA configuration tool, 232 server, 27 Logical Switch Configuration roles and access levels, 980 login banner configuring, 109 disabling, 109 login security configuring, 108 logon conflicts, 594 logs event, 903 LSAN zone creating, 603 LSAN zones activating, 606 LSAN zoning configuring, 602 overview, 602 roles and access levels, 981 LUN choosing to be added to an encryption target container, 531 M Main window master log, 14 menu bar, 10 minimap, 15 main window SAN tab, 8
monitoring connection utilization, 812 end-to-end, 793 end-to-end, configuring, 793 end-to-end, displaying, 795 monitoring fabrics, 60 monitoring pairs deleting, 796 refreshing, 795 monitoring statistics, 309 multi-path configuration for encrypted storage using the Management application, 517 N Name Server, launching, 200 names adding to existing device, 102 adding to new device, 103 editing, 104 exporting, 104 fixing duplicates, 101 importing, 105 removing from device, 104 searching by, 105 setting as non
port optics refreshing, 286 viewing, 284 port properties, 276 port status, determining, 283 port status, viewing, 34 port types, viewing, 279 port-based routing, 676 ports, 270 determining status, 283 disabling, 273 enabling, 273 showing connected, 279 view connectivity, 270 viewing, 276 viewing connection properties, 280 viewing types, 279 primary FCS, 47 printing reports, 926 priorities, threshold, 680 privileges user, 961 privileges, administrator, 582 privileges, user, 429 product label, changing, 183 P
removing members from zone, 624 objects from zone alias, 591 servers, 295 switches from fabric binding, 674 thresholds, 703 thresholds from individual objects, 703 thresholds from table, 704 zone from zone configuration, 624 zones from zone configuration, 624 removing event filters call home centers, 173 call home event filters table, 174 devices, 174 renaming zone alias, 592 zone configuration, 626 zones, 626 renaming servers, 294 replacing zone members, 627 replicate switch configuration, 258 report roles
server name configuring, 107 server name, determining, 17 server port configuring, 127 enable SSL, 127 server port numbers, changing, 217 server properties, viewing, 34 servers associating to HBAs, 295 determining name, 17 logging in, 27 removing, 295 renaming, 294 setting CHAP secret, 108 setting up advanced filtering, 847 discovery, 49 setup tools, 195 adding menu options, 204 adding to device shortcut menu, 207 changing menu options, 206 changing option on device shortcut menu, 208 changing server addres
storage ports adding to storage array, 300 reassigning to storage array, 301 unassigning from storage array, 301 support mode configuring, 128 Switch authentication configuring, 223 switch binding, FICON, 676 switch configuration backup, 252 deleting, 257 exporting, 257 file, search content, 256 file, view content, 255 importing, 257 keeping past age limit, 258 replicating, 258 restore, 254 switch connection control (SCC) policy, 676 switch encryption configuration confirm configuration using the management
tape pools adding, 574 description of, 573 identifying using a name or a number, 574 modifying, 573 removing, 573 tape read and write acceleration, 643 tape write acceleration, 644 technical support data collection roles and access levels, 980 technical support information copying to an external FTP server, 918 deleting, 918 emailing, 918 immediate, 915 technical support information collection scheduling, 914 technical support information, capturing, 227 technical support information, viewing, 917 Telnet la
traffic isolation zoning, 606 configuring, 608 troubleshooting discovery, 57, 74, 80 FCIP Ethernet connections, 670 tunnels, configuring, 646 U unassigning storage ports from storage array, 301 unassociating, HBA to server, 297 UNIX authentication configuring, 224 unregistering an SNMP trap, 862 un-zoned members listing, 623 user privileges, 961 User Administrator, 961 user ID, determining, 17 user interface, description, 1 user management roles and access levels, 980 user privileges defined, 429, 961 RBAC
W Web Tools, launching, 198 Windows authentication configuring, 224 WWN searching by, 106 Z zeroizing effects of using on encryption engine, 550 zone adding to comnfiguration, 593 alias, 590 creating, 584 creating LSAN, 603 database size, 583 merging, 583 removing, 624 traffic isolation, adding members, 609 traffic isolation, creating, 608 traffic isolation, disabling, 610 traffic isolation, disabling failover, 611 traffic isolation, enabling, 610 traffic isolation, enabling failover, 611 zone alias creati
zoning reports generating, 928 zoning set edit limits, roles and access levels, 981 zooming in, 187 zooming out, 188 Brocade Network Advisor SAN User Manual 53-1002167-01 1257
