Symantec NetBackup Deduplication Appliance Software Administrator's Guide

Transcription

1 Symantec NetBackup Deduplication Appliance Software Administrator's Guide Software release Revision 1 NetBackup 5020 NetBackup 5000

2 The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: , revision 1 Legal Notice Copyright 2012 Symantec Corporation. All rights reserved. NetBackup, PureDisk, Symantec, and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

3 Symantec Corporation 350 Ellis Street Mountain View, CA

4 Technical Support Contacting Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s support offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about Symantec s support offerings, you can visit our Web site at the following URL: All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Customers with a current support agreement may access Technical Support information at the following URL: Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: Product release level

5 Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Licensing and registration Customer service Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: Customer service information is available at the following URL: Customer Service is available to assist with non-technical questions, such as the following types of issues: Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs, DVDs, or manuals

6 Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America

7 Contents Technical Support... 4 Chapter 1 Storage pool management procedures for deduplication appliances About the storage pool management procedures you can perform on a deduplication appliance Accessing the administrative Web UI's Hardware Monitoring tab Using the call home feature Enabling the call home feature from the appliance shell menu Enabling the call home feature from the administrative Web UI About Symantec Critical System Protection Bonding the network interfaces Configuring a secondary network for storage pool administration Changing an appliance node's IP address Examining an appliance node to determine whether it was defined in terms of an FQDN or in terms of an IP address Changing an appliance node's IP address About Fibre Channel communication Example - two all-in-one, single-node deduplication appliance storage pools Example - two multinode deduplication appliance storage pools Verifying, enabling, or disabling Fibre Channel communication Enabling (or disabling) Fibre Channel communication from the shell menu Enabling (or disabling) Fibre Channel communication from the administrative Web UI About non-event-based SNMP traps Enabling non-event-based SNMP traps for hardware monitoring... 47

8 8 Contents Using the command-line shell to enable non-event-based SNMP traps Using the command-line shell to disable non-event-based SNMP traps About passwords on the deduplication appliance sysadmin account's password Operating system root user's password Configuration Wizard's password Storage pool administrative Web UI's root account password Root account's password on a remote storage pool Removing a node from a storage pool Chapter 2 Hardware monitoring and alerts About hardware monitoring and alerts Retrieving hardware monitoring information About notification from the deduplication appliance Configuring notifications from the appliance shell menu Configuring notifications from the administrative Web UI Chapter 3 Software monitoring and alerts About software monitoring and alerts Retrieving software monitoring information Configuring software monitoring alerts Chapter 4 Resetting and reimaging a deduplication appliance storage pool About resetting and reimaging a deduplication appliance node or storage pool Performing a network reset on an unconfigured appliance Resetting or reimaging a configured deduplication appliance (Conditional) Preparing NetBackup for a deduplication appliance reset or reimage (Conditional) Preparing other storage pools for a deduplication appliance reset or reimage (Conditional) Preparing to reset a storage pool or reimage a node Performing a storage pool reset Performing a soft reset... 86

9 Contents 9 Performing an image reset Performing a USB reimage Chapter 5 Disaster recovery About deduplication appliance disaster recovery About deduplication appliance disaster recovery methods Disaster recovery without a disaster recovery backup Disaster recovery with a disaster recovery backup Chapter 6 Configuring virtual local area networks (VLANs) About VLANs VLAN example Configuring VLANs and storage zones Verifying VLAN prerequisites Moving a storage pool to a VLAN-compatible trunk port Moving a deduplication appliance storage pool to a trunk port Moving a PureDisk ROE storage pool to a trunk port Configuring the node interfaces Configuring the node interfaces on a deduplication appliance storage pool Configuring the node interfaces on a PureDisk ROE storage pool Creating mapping tables Creating mapping tables on a deduplication appliance storage pool (appliance shell menu method) Creating mapping tables on a PureDisk ROE storage pool (command method) Creating mapping tables (Configuration Wizard method) Completing the VLAN configuration About the VLAN configuration pages in the Storage Pool Configuration Wizard VLAN Configuration - Message from webpage page VLAN Configuration - Discover configuration page VLAN Configuration - Node List page VLAN Configuration - VLAN network settings and VLAN mapping edit page Summary - VLAN Topology Summary page Adding clients to the VLANs About configuring VLANs with bonded network interfaces (deduplication appliances only)

10 10 Contents About PureDisk operations within VLANs Chapter 7 Enabling the intelligent platform management interface (IPMI) About the intelligent platform management interface (IPMI) Configuring the IPMI Verifying configuration prerequisites Logging on to the Configuration Wizard and accessing the IPMI configuration pages Specifying the IPMI administrator password from the Configuration Wizard (Optional) Adding IPMI users and setting IPMI user passwords from the Configuration Wizard Specifying appliance node IPMI network information from the Configuration Wizard (Conditional) Changing a user password from the Configuration Wizard Determining appliance firmware version Guidelines for IPMI passwords and user names Completing the IPMI configuration pages in the Configuration Wizard Completing the User management tab Completing the Network configuration tab Examining log information Completing the Change IPMI password page IPMI maintenance procedures Synchronizing web console access after adding nodes to the storage pool Changing a user password from the appliance shell menu Using the appliance shell menu to configure the IPMI Logging on to the appliance shell menu and accessing the IPMI commands Specifying the IPMI administrator password from the appliance shell menu (Optional) Adding IPMI users and setting IPMI user passwords from the appliance shell menu Specifying appliance node IPMI network information from the appliance shell menu Using the web console Starting the web console from inside the Configuration Wizard

11 Contents 11 Starting the web console from outside of Configuration Wizard Starting a deduplication appliance from the web console Stopping a deduplication appliance from the web console Downloading an ISO image and installing the ISO image on the appliance Chapter 8 Using Symantec Critical System Protection About Symantec Critical System Protection Configuring Symantec Critical System Protection Appendix A About PureDisk About PureDisk in the Deduplication Appliance Software releases About platform-specific PureDisk storage pool behavior Authentication brokers High availability Storage pool reconfiguration Upgrades and rollbacks Disaster recovery backups and restores About PureDisk documentation Appendix B About Call Home upload information About the appliance hardware information that is uploaded About the NetBackup 5020 communications connections Appendix C Troubleshooting the deduplication appliance About troubleshooting deduplication appliance resets About logging for optimized deduplication Enabling optimized deduplication logging Enabling the spoold log Log file locations About removing a computer from a hosts file Appendix D Appliance shell menu command reference About the appliance shell menu Logging into the shell menu Shell menu usage NetBackup deduplication appliance administrative shell menu root > admin

12 12 Contents root > FC root > IPMI root > network root > PDCLI root > PureDisk root > SCSP root > storage root > support root > vzone common > exit common > history common > logout common > nodeinfo admin > password admin > su FC > disable-ft FC > enable-ft FC > listpath FC > reset FC > scan FC > show FC > stat FC > verify-conf IPMI > network IPMI > user network > bonding network > config network > DNS network > hostname network > hosts network > networkstatus network > nsswitch network > ping network > property network > route network > setnodeip network > summary network > unconfig network > vlan PureDisk > dsstat PureDisk > healthcheck PureDisk > patch PureDisk > removenode

13 Contents 13 PureDisk > restart PureDisk > seedutil PureDisk > show PureDisk > start PureDisk > status PureDisk > stop scsp > audit scsp > serverinfo storage > df storage > raid storage > volume storage > vxprint support > applianceversion support > callhome support > clock support > support > hwmon support > InstallerUI support > iostat support > licenseinfo PureDisk > log support > megacli support > meminfo support > ntp support > poweroff support > ps support > reboot support > reset support > serialno support > snmp support > top support > uptime support > version support > vmstat vzone > collect vzone > config vzone > link vzone > zone Index

14 14 Contents

15 Chapter 1 Storage pool management procedures for deduplication appliances This chapter includes the following topics: About the storage pool management procedures you can perform on a deduplication appliance Accessing the administrative Web UI's Hardware Monitoring tab Using the call home feature About Symantec Critical System Protection Bonding the network interfaces Configuring a secondary network for storage pool administration Changing an appliance node's IP address About Fibre Channel communication Verifying, enabling, or disabling Fibre Channel communication About non-event-based SNMP traps About passwords on the deduplication appliance Removing a node from a storage pool

16 16 Storage pool management procedures for deduplication appliances About the storage pool management procedures you can perform on a deduplication appliance About the storage pool management procedures you can perform on a deduplication appliance The Storage Pool Configuration Wizard welcome page contains links to the following: About, which lists NetBackup Deduplication Appliance Software release information. Installationhelp, which displays information from the Deduplication Appliance Software Getting Started Guide. Symantec updates the deduplication appliance and the PureDisk documentation from time to time. The following website contains links to all the deduplication appliance documentation in PDF format: The following website contains links to the PureDisk documentation: Logout, which stops the installer and lets you exit. Reset storage pool, which lets you remove configuration information. Configure VLAN topology, which lets you create and edit information for storage pool virtual local area networks (VLANs). Change configuration wizard password, which displays a pop-up window that guides you through the process of changing the password for the Storage Pool Configuration Wizard. Configure IPMI, which lets you configure a lights-out intelligent platform management interface (IPMI) to monitor and manage the storage pool from a remote location. Specify backup, restore, or replication networks, which lets you update networking to make use of multiple network interface cards. Contact technical support, which launches a new browser window with links to Symantec Technical Support information. The deduplication appliance shell menu lets you change passwords, obtain network information, and perform various other maintenance tasks. For information about the deduplication appliance shell menu, see the following: See About the appliance shell menu on page 202. In addition to the preceding administrative tasks, you can also perform maintenance on your appliance. The following are the maintenance procedures:

17 Storage pool management procedures for deduplication appliances Accessing the administrative Web UI's Hardware Monitoring tab 17 Examining the Hardware Monitoring tab in the administrative Web UI See Accessing the administrative Web UI's Hardware Monitoring tab on page 17. Enabling or disabling the call home feature See Using the call home feature on page 18. Bonding the network interface cards See Bonding the network interfaces on page 26. Configuring a secondary administrative network See Configuring a secondary network for storage pool administration on page 29. Changing a node's IP address See Changing an appliance node's IP address on page 31. Using Fibre Channel communication. See About Fibre Channel communication on page 40. Verifying, enabling, and disabling Fibre Channel communication. See Verifying, enabling, or disabling Fibre Channel communication on page 43. Enabling non-event-based SNMP traps. See About non-event-based SNMP traps on page 45. Managing passwords See About passwords on the deduplication appliance on page 51. Removing an appliance node from a storage pool See Removing a node from a storage pool on page 54. Accessing the administrative Web UI's Hardware Monitoring tab In the administrative Web UI, click Monitor > System to display the Hardware Monitoring tab. The deduplication appliance detects hardware alerts and displays them in the administrative Web UI's Hardware Monitoring tab. From this tab, you can click Clear All Hardware Alerts to clear the alerts. No other actions can be performed from this tab.

18 18 Storage pool management procedures for deduplication appliances Using the call home feature Using the call home feature A deduplication appliance can connect to the Symantec Call Home Server for the purpose of uploading hardware and software status information. This capability is referred to as call home and is enabled by default. The call home capability requires port 443 to be open. Port 443 is open by default. As an option, the call home feature lets you specify a proxy server. The proxy server you use must be able to accept https connections from the Symantec Call Home Server. In addition, the proxy server also must be able to forward https connection requests to the Symantec Call Home Server. Symantec supports the following proxy servers: Apache Software Foundation Microsoft Forefront Threat Management Gateway (TMG) Squid Proxy Server from squid-cache.org Symantec supports secure sockets layer (SSL) tunneling in some proxy servers, as follows: On the Apache proxy server. You can use the appliance shell menu to disable tunneling if the Apache proxy server is not working with tunneling enabled. If you use Microsoft Forefront TMG, Symantec requires that tunneling be enabled. By default, the call home feature is enabled and tunneling is also enabled. Squid. SSL tunneling can be either enabled or disabled if you use a Squid proxy server. If you encounter a hardware problem, contact Symantec Technical Support. The Technical Support Engineer uses the serial number of your appliance to assess hardware status trends. When the Call Home feature is enabled and the deduplication appliance encounters a component failure, the deduplication appliance sends hardware log files to the Symantec Operations Readiness Tools (SORT) automatically. For more information about SORT, see the following website: When a hardware failure occurs, the deduplication appliance generates a local alert and sends an notification to you regarding the hardware failure. If the call home feature is enabled, the deduplication appliance also uploads the hardware failure information to a Symantec server. For information about hardware alerts and a complete list of the hardware components that the appliance monitors, see the following: See About hardware monitoring and alerts on page 57.

19 Storage pool management procedures for deduplication appliances Using the call home feature 19 The following topics explain how to use the appliance shell menu to enable the call home feature: See Enabling the call home feature from the appliance shell menu on page 19. See Enabling the call home feature from the administrative Web UI on page 23. Enabling the call home feature from the appliance shell menu The following procedure explains how to enable the call home feature from the appliance shell menu. More information about the commands in the procedure is available. See About the appliance shell menu on page 202. To enable the call home feature (appliance shell menu method) 1 Make sure that the deduplication appliance is configured and known to work. 2 Log into the deduplication appliance shell menu. Complete the following steps: Use a Secure Shell connection to connect to the appliance. Type the user name and password for the appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is a zero (0) character. After the welcome information appears, type q to display the root menu. 3 (Optional) Enable the appliances in the storage pool to communicate to the Symantec Call Home Server through a proxy server. If you want to enable a proxy server, go to the support view and type the following command: > callhome proxy add address port [ username ] [ password ] [ nodeip ] This command accepts the following arguments: Argument address Meaning The FQDN or the IP address of the proxy server. For example, myproxy.123.com or port The port on the proxy server that the appliance can use.

20 20 Storage pool management procedures for deduplication appliances Using the call home feature Argument username Meaning (Conditional) Type the user name that the proxy server requires or type placeholder characters. Some proxy servers require a user name and a password. Type placeholder characters in the username field if the following are both true: The proxy server does not require a user name and password. You want to specify a nodeip. For placeholder characters, type one of the following: Empty quotation mark characters, as follows: "" The word null. password (Conditional) Type the proxy server password or type placeholder characters. If the proxy server requires a user name and a password, type the proxy server password. Type placeholder characters in the password field if the following are both true: The proxy server does not require a user name and password. You want to specify a nodeip. For placeholder characters, type one of the following: Empty quotation mark characters, as follows: "" The word null. nodeip (Optional) Specify the IP address of the node for which you want to configure the call home capability. By default, the command uses the IP address of the node you used when you logged into the appliance shell menu. If you do not specify the nodeip parameter and there are multiple nodes in your storage pool, the command takes effect on all nodes in the storage pool. For example, assume that you have two appliances configured into one storage pool. You logged into the appliance shell menu on the storage pool authority node. You configured the call home feature for the storage pool authority node first. Now, you want to configure the call home feature for the other node. At this time, type the callhome proxy add command and specify the IP address of the other node in the nodeip field. Tip: The support > nodeinfo command returns the node IP addresses of all the appliances in the storage pool. The following examples show how to use the callhome proxy add command: Assume that your storage pool consists of one appliance, and your proxy server does not require a user name or a password. The following example command specifies a proxy server named pool.proxy.com and a port of 237 for this appliance: callhome proxy add pool.proxy.com 237

21 Storage pool management procedures for deduplication appliances Using the call home feature 21 Assume that your storage pool consists of two nodes. You logged into the appliance shell menu on the storage pool authority to configure the call home capability. Your proxy server does not require a user name or password. The following example command specifies the proxy server for all appliance nodes in this storage pool: callhome proxy add pool.proxy.com 237 If you do not specify the nodeip parameter, the command takes effect on all nodes in the storage pool. Assume that your storage pool consists of two nodes. You logged into the appliance shell menu on the storage pool authority to configure the call home capability. Your proxy server does not require a user name or password. The following example commands specify the proxy server for just the content router in this storage pool: callhome proxy add pool.proxy.com 237 "" "" Alternatively, you can type the second line in this example as follows: callhome proxy add pool.proxy.com 237 null null Assume that your storage pool authority consists of one appliance, and your proxy server requires a user name and a password. The following example command adds the proxy server for this appliance: callhome proxy add pool.proxy.com 237 pixie dixie

22 22 Storage pool management procedures for deduplication appliances Using the call home feature 4 (Conditional) Disable tunneling as needed for the appliances that are connected to Apache Software Foundation proxy servers. Perform this step only if the deduplication appliance is connected to an Apache proxy server and the proxy server is not working with tunneling enabled. If the deduplication appliance is connected to a Microsoft Forefront TMG or a Squid proxy server, you are not required to perform this step. Type the following command: callhome proxy tunnel 0 [ nodeip ] For nodeip, specify the IP address of the deduplication appliance that you want to connect to the proxy server. If you do not specify the nodeip parameter and there are multiple nodes in your storage pool, the command takes effect on all nodes in the storage pool. For example, specify the IP address of a content router if you type this command from the storage pool authority and you want to configure the proxy server for one of the content routers. 5 (Optional) Specify the hardware notification level. Type the following command if you want to set the amount of time that needs to elapse between alert messages: support> hardware notification_interval modify time [nodeip] Argument time nodeip Meaning Specify the number of minutes that need to elapse between the alert mails that are sent to the administrator. Type a number that is a multiple of 15. Specify the IP address of the deduplication appliance for which you want to configure the alert interval. For example, specify the IP address of a content router if you type this command from the storage pool authority and you want to configure the alert interval for one of the content routers The alert notification interval does not have to be the same for all nodes in the storage pool. For example, you can specify a different notification interval for each node in the storage pool. 6 Log out of the deduplication appliance shell menu.

23 Storage pool management procedures for deduplication appliances Using the call home feature 23 Enabling the call home feature from the administrative Web UI The following procedure explains how to enable the call home feature from the administrative Web UI. To enable the call home feature (administrative Web UI method) 1 Open a browser, and type the following URL to access the storage pool authority's opening panel: For URL, type the URL for the storage pool authority node. 2 Log in as root. 3 Click Settings > Configuration.

24 24 Storage pool management procedures for deduplication appliances Using the call home feature 4 In the left pane, under Configuration, click Call Home.

25 Storage pool management procedures for deduplication appliances Using the call home feature 25 5 In the right pane, under the Call Home heading, use the information in the following table to complete the fields on this page. Note: If the call home feature is enabled, and you want to disable it, clear the box to the right of Enable Call Home. Field Proxy Settings Appliance specification Check this box to enable a proxy server. Clear this box to disable a proxy server or to suspend use of a proxy server. Proxy Server The FQDN or the IP address of the proxy server. For example, myproxy.123.com or Proxy Port User name The port on the proxy server that the appliance can use. (Conditional) Type the user name that the proxy server requires or type placeholder characters. Some proxy servers require a user name and a password. Leave this field empty if a user name is not required. Password (Conditional) Type the proxy server password or type placeholder characters. If the proxy server requires a user name and a password, type the proxy server password. Leave this field empty if a password is not required. Enable Location Settings Check this box to enable the location settings, which specify the physical location and contact information for the appliance. Symantec can provide better support when you enable location settings. Clear this box if you want to disable or suspend location settings. Contact Address Phone Type the name of the contact person for the appliance. Symantec contacts this person if the appliance needs service. Type the address of the building in which the appliance resides. Type the telephone number of the appliance's contact person. Type the address of the appliance's contact person. If you need to specify more than one address, use semicolons (;) to separate the addresses.

26 26 Storage pool management procedures for deduplication appliances About Symantec Critical System Protection Field Contract Number Appliance specification Type the Symantec support contract number. Enclose this number in quotation mark (" ") characters. If you do not know the contract number, type the keyword UNKNOWN. Do not enclose UNKNOWN in quotation mark characters. You can update this information with a contract number at a later date. Node IP to push Call Home settings (Conditional) Type the FQDNs or IP addresses of other nodes in the storage pool for which you want to enable the call home feature. If you need to specify more than one address, use semicolons (;) to separate the addresses. About Symantec Critical System Protection Symantec Critical System Protection (SCSP) secures physical and virtual servers using flexible, policy-based monitoring, and protection. It addresses compliance requirements across heterogeneous environments. Using non-signature based Host Intrusion Prevention, it proactively protects against zero-day attacks and malicious insider threats. It also ensures Host Integrity and compliance using host intrusion detection based system monitoring, notification, and auditing. More information about SCSP is available. See About the appliance shell menu on page 202. Bonding the network interfaces The deduplication appliance lets you configure the network interfaces to increase network bandwidth and to provide redundancy. The deduplication appliance includes two 10-GB ports that you can bond together in one IP address. Caution: Do not bond either of the two 10-GB ports with the 1-GB port. This action can affect performance adversely. The deduplication appliance supports the following bonding modes: active-backup, which routes all network traffic through a single interface. If this interface fails, the deduplication appliance switches the traffic to another available interface. This mode does not require you to reconfigure network switches.

27 Storage pool management procedures for deduplication appliances Bonding the network interfaces ad (also known as LACP mode), which supports the IEEE 802.3ad communication standard. This mode is also known as dynamic link aggregation mode. This mode presents all the interfaces with a single physical address. If you enable this mode, connect the bonded ports to a network switch that supports IEEE 802.3ad dynamic link aggregation. balance-alb, which distributes both the incoming and the outgoing network traffic among all interfaces. This mode does not require you to reconfigure network switches. Some bond modes require additional configuration on the switch or the router. The ports that connect to the deduplication appliance should be trunked as shown in the following table: Table 1-1 Mode Active-backup ad or LACP Balance-alb Port bonding configuration Switch ports configuration None required ad aggregation None required Different vendors use different terminologies, EtherChannel (Cisco switches), port trunking, and so on. Please consult the network administrator about the switch port configuration before you enable bonding. The default balance-alb mode does not require any special switch configuration. More information about bond modes is available: The following procedure explains how to bond the interfaces. To bond the interfaces in the deduplication appliance 1 Connect to the deduplication appliance for which you want to enable a bond by using a Secure Shell (SSH) agent. For example, you can use the PuTTY, which is available as a free download. 2 Log into the deduplication appliance. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0).

28 28 Storage pool management procedures for deduplication appliances Bonding the network interfaces 3 Type network at the system prompt and press Enter. For example: > network 4 Type bonding show to display the bonding that is currently in effect. 5 (Conditional) Type bonding disable to disable the bonding that is in effect currently. Perform this step if the bonding show command indicates that bonding is enabled currently. 6 Type the following bonding enable command to configure bonding: > bonding enable nodeip bondname mode bond_ip bond_netmask eth# eth# [eth#] [eth#] The required parameters are as follows: For nodeip, specify the IP address of the node you want to contact. For mode, specify active-backup, 802.3ad, or balance-alb. For bond_ip, specify the IP address you want to use to identify the new bond. For bond_netmask, specify the netmask that you want to use to identify the new bond. For eth#, specify the interfaces that you want to bond. Specify the interfaces as ethnumber. You must specify at least two interfaces. Bonding command example: bonding enable bond0 balance-alb eth2 eth3 The preceding command creates a new virtual interface on the computer that is called bond0 with an IP address of The bond is composed of interfaces eth2 and eth3. You can also specify that the node IP address and the bond IP address be the same. In that case, the primary interface becomes part of the bond.

29 Storage pool management procedures for deduplication appliances Configuring a secondary network for storage pool administration 29 Figure 1-1 Bonding example Server_ Server_02 eth1 eth Command issued from Server_01 bonding enable bond0 balance-alb eth1 eth2 Configuring a secondary network for storage pool administration If you have a NetBackup 5020 appliance, and you configured it to use a 10-GB network during the configuration process, you can configure an administrative network on the 1-GB interface. After you configure the administrative network, the 10-GB network becomes dedicated to backups, restores, and other work. The following procedure explains how to configure a 1-GB administrative network for an appliance.

30 30 Storage pool management procedures for deduplication appliances Configuring a secondary network for storage pool administration To configure an additional network for administrative purposes 1 Obtain the configuration information for the new network from your network administrator. Obtain the following information: Information to obtain IP address Default gateway Netmask Network information for this interface 2 Use an Ethernet cord to connect the deduplication appliance's 1-GB interface to your corporate network. Plug one end of the cord into the port that is labeled NIC 2. This port is a 1-GB port. 3 Open a Web browser and type the following URL: For address, specify the storage pool authority node's IP address or fully qualified domain name (FQDN). 4 (Conditional) Affirm the security exception for the installer. Depending on your site's security policies, you might see a browser security certificate affirmation page when you start the installer. 5 On the logon page, in the User Name field, type root. 6 In the Password field, type the password. By default, the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). 7 Click Log on. 8 On the welcome page, click Start the network configuration wizard.

31 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address 31 9 On the Network Configuration page, complete the following fields: Field Name Network Interface IP Address Default Gateway Content Use the pull-down menu to select interface eth1. Type the IP address that you want to assign to interface eth1. Type the default gateway for this interface. This value is the gateway that you obtained from your network administrator. 10 Click Next. 11 Observe the network configuration progress on the Progress page. 12 When the network configuration is complete, click Finish. Changing an appliance node's IP address Symantec requires that you configure appliances with fully qualified domain names (FQDNs) for the following reasons: The features of the Deduplication Appliance Software interoperate with NetBackup software when the deduplication appliance is configured in terms of FQDNs. If you ever need to change an appliance's IP address, the deduplication appliance must have been configured with an FQDN in the Storage Pool Configuration Wizard when the storage pool was configured originally. Previous releases of the Deduplication Appliance Software permitted you to define an appliance in terms of IP addresses. However, you cannot change an appliance's IP address if you configured the deduplication appliance with only an IP address when you performed the initial configuration. If you want to change an appliance's FQDN to a different FQDN, or if you want to change an appliance's IP address to an FQDN, use the procedure called Changing node IP addresses to FQDNs or changing node FQDNs to new FQDNs (unclustered storage pools) in the PureDisk Administrator's Guide. The following procedures explain how to examine an appliance's initial configuration definitions and how to change an appliance node's IP address: See Examining an appliance node to determine whether it was defined in terms of an FQDN or in terms of an IP address on page 32.

32 32 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address See Changing an appliance node's IP address on page 33. Examining an appliance node to determine whether it was defined in terms of an FQDN or in terms of an IP address The following procedure lets you determine whether an appliance node was configured with an FQDN or with an IP address when the appliance was configured. To verify FQDN use or IP address use on an appliance node 1 Use an SSH connection to connect to the storage pool authority node. 2 Type the user name and password for the deduplication appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). 3 After the welcome information appears, press q to display the root mode menu. 4 Type the following command at the shell menu prompt: > nodeinfo

33 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address 33 5 Analyze the output. If the node was configured with an FQDN, the output is similar to the following: [node_1] enabled: true ip: acme.beep.com netmask: interface: eth1 status: active services: spa,nbu,mbs,mbe,cr If, however, the node was configured with an IP address, the output is similar to the following: [node_1] enabled: true ip: netmask: interface: eth1 status: active services: spa,nbu,mbs,mbe,cr 6 Type the following command at the shell menu prompt to return to the main shell menu: > exit If you want to change the deduplication appliance node's IP address, stay in the shell menu. Do not exit the shell menu. See Changing an appliance node's IP address on page 33. Changing an appliance node's IP address The following procedure explains how to change an appliance node's IP address.

34 34 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address To change an appliance node's IP address 1 (Conditional) Verify whether the node was configured with an IP address or with an FQDN. Perform this step if you are not sure about how the node was configured. See Examining an appliance node to determine whether it was defined in terms of an FQDN or in terms of an IP address on page Log into the administrative Web UI, click Monitor > Jobs, and stop all the jobs that are running on the storage pool. 3 Perform the following steps to start the shell menu: Use an SSH connection to connect to the storage pool authority node. You can use IP address , which is eth0, to connect to the storage pool authority node's eth0 (NIC1) port. Type the user name and password for the deduplication appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). After the welcome information appears, press q to display the root mode menu. 4 Type the following command to enter PureDisk mode: > PureDisk 5 Type the following command to stop all services on all nodes: > stop all 6 Type the following command to return to the main shell menu: > exit 7 (Conditional) If a bond was previously created, disable the bond. Type the following command to enter network mode: > network Type the following command to display the current bonding status: > bonding show

35 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address 35 > config show If the output from the bonding show command indicates that bonding is enabled, use the instructions in the next bulleted item to disable the bonding. If the output from the bonding show command indicates that bonding is disabled, proceed to the following step: Step 10 Type the following command to disable all existing interface bonds for the interface you want to change: > bonding disable nodeip bondname The output from the bonding show command includes the information you need to specify the nodeip and the bondname arguments to the bondingdisable command. Additional information about these arguments is as follows: For nodeip, type the IP address you want to change. For bondname, type the name of the bonding interface. Type y in response to the question regarding the possible loss of your network connection. 8 Type the config show command to display the current configuration, and examine the output. For example, the following command shows that eth2 and eth3 are not configured: Node IP Address Interface IP Address Netmask HW Address MTU * eth :0C:29:83:3A:D * eth * :0C:29:83:3A:DD * eth2 N/A N/A 00:0C:29:83:3A:E * eth3 N/A N/A 00:0C:29:83:3A:F Type the following command to add an IP address to an unconfigured interface of the node: > config addr node_ip ethnum new_ip netmask These arguments are as follows: For node_ip, type the IP address of the node you want to change. For ethnum, type name of an idle interface. Choose an interface that is not configured at this time.

36 36 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address The example in step 8shows that eth2 and eth3 are unconfigured interfaces. For new_ip, type the new IP address that you want to assign to the node. For netmask, type the netmask for this interface. For example, assume that you want to change a node's IP address from to IP address currently resides on eth1. You can type the following shell menu command: > config addr eth Keep the shell menu open. You need to use it again in subsequent steps. 10 Change the IP address in the Domain Name Server (DNS) or in the hosts file(s). Your goal is to change how the deduplication appliance node names are resolved to reflect the new IP address. If your site uses a DNS, update the DNS to reflect the new naming. For example, change the IP address from acme.beep.com/ to acme.beep.com/ If your site does not use a DNS, update the hosts files on each computer that interoperates with the deduplication appliance node. Perform these updates as follows: For appliance nodes within this storage pool, update the hosts file information from the storage pool authority node's shell menu. The following list explains, in general terms, the deduplication appliance shell menu commands to use when you update the hosts file on an appliance node: To add the new IP address to all the nodes in the storage pool, type network, and then type the hosts add. To remove the old IP address from all the nodes in the storage pool, type network, and then type the hosts del command. For other storage pools that communicate with the changed storage pool, update the hosts files on all nodes. Log into the other storage pool's storage pool authority node. Then use the shell menu to update the hosts information for all the other appliance nodes in that storage pool. For example, update other storage pools if replication between storage pools is enabled.

37 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address 37 For other computers at your site that need to connect to the changed storage pool, log into each computer, and update the hosts file manually. For example, update clients. Note that the fully qualified domain name (FQDN) of the node does not change during this procedure. If you use both a DNS and a hosts file, make sure that the changes you make do not conflict. For more information about the hosts file, see the Deduplication Appliance Software Getting Started Guide. For more information about the deduplication appliance shell menu and the parameters for the shell menu commands, see the following: See Logging into the shell menu on page Type the following command to assign the new IP address to the node: > config addr node_ip ethnum new_ip netmask The parameters are as follows: For node_ip, type the new IP address that you want to assign to the node. For ethnum, type the ethnum number of the interface. For new_ip, type the new IP address that you want to assign to the node. This instance is the second time that you type the new IP address on this command line. For netmask, type the netmask for this interface. For example, assume that you want to change a node's IP address from to IP address currently resides on eth1. You can type the following shell menu command: config addr eth Type the following shell menu command to return to the root menu: > exit

38 38 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address 13 Type the following shell menu command. Then examine its output to confirm that all the IP addresses have been updated to the new IP addresses: > nodeinfo For example, assume that you have a two-node storage pool with IP addresses and You can type the following commands to display the FQDNs and IP addresses to verify their correctness: spa> nodeinfo [node_1] enabled: true ip: spa.myco.net netmask: interface: eth1 status: services: active spa,nbu,mbs,mbe,cr [node_2] enabled: true ip: additional_node.myco.net netmask: interface: eth1 status: active services: nbu,mbe,cr 14 Type the following shell menu command to access the network commands: > network

39 Storage pool management procedures for deduplication appliances Changing an appliance node's IP address Use the ping command to test the connectivity between the nodes in the storage pool, as follows: > ping host nodeip > ping For host, type the IP address or the host name of the destination computer to receive the ping. For nodeip, type the IP address of the source computer from which you want to send the ping. For example, assume that you need to verify connectivity to and from the nodes in your storage pool. You can type the following commands to verify that the nodes can connect to computers outside the storage pool: PING a568.d.akamai.net ( ) 56(84) bytes of data. 64 bytes from a deploy.a.com ( ): icmp_seq=1 ttl=46 time=345 ms > ping PING a568.d.akamai.net ( ) 56(84) bytes of data. 64 bytes from a deploy.a.com ( ): icmp_seq=1 ttl=46 time=344 ms Type the following commands to ensure that the nodes can connect to each other: > ping PING ( ) 56(84) bytes of data. 64 bytes from : icmp_seq=1 ttl=64 time=0.342 ms > ping PING ( ) 56(84) bytes of data. 64 bytes from : icmp_seq=1 ttl=64 time=0.167 ms 16 At the menu prompt, type the following command to access the PureDisk shell menu commands: > PureDisk 17 Type the following command to start PureDisk services: > start all

40 40 Storage pool management procedures for deduplication appliances About Fibre Channel communication 18 Type the following command to return to the root menu: > exit 19 Log into the deduplication appliance's Storage Pool Configuration Wizard or administrative Web UI and resume administrative operations. About Fibre Channel communication You can configure your hardware appliance with an optional Fibre Channel card. The deduplication appliance can use the Fibre Channel connection to transmit data from the storage pool to other storage pools. The deduplication appliance can also use Fibre Channel to transmit data to other computers on the network. For information about how to verify, enable, or disable Fibre Channel communication, see the following: See Verifying, enabling, or disabling Fibre Channel communication on page 43. The addition of Fibre Channel cards enables optimized duplication of the following: Data transmissions between a NetBackup 7.5 (or later) environment and a deduplication appliance storage pool. For information about how to enable or disable Fibre Channel transmissions from NetBackup, see the Symantec NetBackup Deduplication Guide. Data transmissions from a NetBackup media server appliance to a deduplication appliance storage pool. Data transmissions between two storage pools that consist entirely of deduplication appliances. The NetBackup product family can deduplicate client data and store the data in small, unique segments. In an optimized duplication, NetBackup copies the unique, deduplicated data segments from one host to another. For optimized duplication to be successful, all deduplication appliances need to be equipped with the optional Fibre Channel cards. If optimized duplication over the Fibre Channel connection fails, the system uses TCP/IP communication. To receive the full benefit of the faster communication speeds associated with Fibre Channel, make sure that all optimized deduplication communication is over Fibre Channel. Any conversions from Fibre Channel to TCP/IP and then back to Fibre Channel slows down communication speed. If the environment requires a conversion from Fibre Channel to TCP/IP and back to Fibre Channel, consider using strictly TCP/IP. After the storage pool is configured, use your switch's software interface to configure Fibre Channel zones. If you have multiple storage pools, and you want

41 Storage pool management procedures for deduplication appliances About Fibre Channel communication 41 the storage pools to communicate with each other, configure each appliance in each storage pool to communicate with each appliance in the other storage pools. Include only one initiator and one target in one zone. Do not put HBA ports from the same computer into the same zone. The deduplication appliance issues an error message if you attempt to enable Fibre Channel communication on an appliance that is not equipped with a Fibre Channel card The following topics show zoning examples: See Example - two all-in-one, single-node deduplication appliance storage pools on page 41. See Example - two multinode deduplication appliance storage pools on page 42. Example - two all-in-one, single-node deduplication appliance storage pools The following figure shows the Fibre Channel connections between two small storage pools: Figure 1-2 Two-node Fibre Channel zoning example Storage Pool A Storage Pool B Appliance 1 Appliance 2 Initiator Initiator Target Target In the preceding figure, each storage pool is an all-in-one, single-node deduplication appliance storage pool. Correct zoning consists of two separate zones, one for each initiator/target pair, as follows: Zone 1 includes the initiator for appliance 1 and the target for appliance 2. Zone 2 includes the initiator for appliance 2 and the target for appliance 1.

42 42 Storage pool management procedures for deduplication appliances About Fibre Channel communication After you configure the Fibre Channel zones, the deduplication appliance sends data over the Fibre Channel network whenever possible. If your site's Fibre Channel network is unavailable, the deduplication appliance uses the TCP/IP network. Example - two multinode deduplication appliance storage pools The following figure shows the Fibre Channel connections between two multinode storage pools: Figure 1-3 Multinode Fibre Channel zoning example Storage Pool A Appliance 1 Initiator Target Storage Pool B Appliance 4 Initiator Appliance 2 Target Initiator Target Appliance 5 Initiator Appliance 3 Target Initiator Target In the preceding figure, storage pool A is a three-node deduplication appliance storage pool, and storage pool B is a two-node deduplication appliance storage pool. Correct zoning consists of 12 separate zones, one for each initiator/target pair, as follows: Zone 1 includes the initiator for appliance 1 and the target for appliance 4. Zone 2 includes the initiator for appliance 1 and the target for appliance 5.

43 Storage pool management procedures for deduplication appliances Verifying, enabling, or disabling Fibre Channel communication 43 Zone 3 includes the initiator for appliance 2 and the target for appliance 4. Zone 4 includes the initiator for appliance 2 and the target for appliance 5. Zone 5 includes the initiator for appliance 3 and the target for appliance 4. Zone 6 includes the initiator for appliance 3 and the target for appliance 5. Zone 7 includes the initiator for appliance 4 and the target for appliance 1. Zone 8 includes the initiator for appliance 4 and the target for appliance 2. Zone 9 includes the initiator for appliance 4 and the target for appliance 3. Zone 10 includes the initiator for appliance 5 and the target for appliance 1. Zone 11 includes the initiator for appliance 5 and the target for appliance 2. Zone 12 includes the initiator for appliance 5 and the target for appliance 3. Verifying, enabling, or disabling Fibre Channel communication By default, Fibre Channel communication is disabled. You can use the following procedures to enable or disable Fibre Channel communication: See Enabling (or disabling) Fibre Channel communication from the shell menu on page 43. See Enabling (or disabling) Fibre Channel communication from the administrative Web UI on page 44. Enabling (or disabling) Fibre Channel communication from the shell menu You can use the following procedure to enable or disable Fibre Channel transmissions from the shell menu. To enable (or disable) Fibre Channel communication from the shell menu 1 Use a Secure Shell (SSH) agent to connect to the deduplication appliance for which you want to enable or disable Fibre Channel communication. For example, you can use PuTTY, which is available as a free download. 2 Log into the deduplication appliance. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0).

44 44 Storage pool management procedures for deduplication appliances Verifying, enabling, or disabling Fibre Channel communication 3 Type FC at the system prompt and press Enter. For example: > FC 4 Type show nodeip to display the Fibre Channel connections that are currently in effect. For nodeip, type the IP address of the deduplication appliance for which you want to enable Fibre Channel communication. 5 Type enable-ft to enable Fibre Channel communication for this appliance. Perform this step if the show command indicates that Fibre Channel communication is disabled and you want to enable it. Note: If Fibre Channel communication is enabled, and you want to disable it, type disable-ft. Enabling (or disabling) Fibre Channel communication from the administrative Web UI You can use the following procedure to enable or disable Fibre Channel transmissions from the administrative Web UI. To enable (or disable) Fibre Channel transmission from the administrative Web UI 1 Open a browser, and type the following URL to access the storage pool authority's opening panel: For URL, type the URL for the storage pool authority node. 2 Log in as root. 3 Click Settings > Configuration.

45 Storage pool management procedures for deduplication appliances About non-event-based SNMP traps 45 4 In the left pane, under Configuration, click Fibre Channel. 5 In the right pane, under the Fibre Channel heading, click in the box and click Save. Note: If Fibre Channel communication is enabled, and you want to disable it, clear the box. Click the Fibre Channel box on the source storage pool only. You do not need to enable this capability on the receiving storage pool. About non-event-based SNMP traps The NetBackup deduplication appliance enables you to send non-event-based SNMP traps. The deduplication appliance can send an SNMP trap to notify you of the following types of non-event-based system activity: Disks reaching their hard limit or their soft limit Job failures Stopped services Hardware monitoring In addition to sending an SNMP trap, the deduplication appliance logs all traps in the following files: /Storage/log/NonEventBasedSNMP.log /Storage/log/pdhwmon.log The deduplication appliance sends traps of the following format: Storagepool: storagepoolid (storagepoolname,spa:spahostname) Agent: agentid ([alias, ][hostname, ]ipaddress[, PDserver]) [Dataselection: dsid (dataselectionname)] [Job: jobid (workflowname)] [Jobstep: jobstepid (workflowstepname)] ErrID: errorid Descr: errordescription The following notes apply to the SNMP trap format: The deduplication appliance omits alias if it is empty or equal to hostname. The deduplication appliance omits hostname if it is empty or equal to ipaddress.

46 46 Storage pool management procedures for deduplication appliances About non-event-based SNMP traps The deduplication appliance includes PDserver only if the agent is a PureDisk server. The deduplication appliance omits PDserver if the error message applies to a client agent. If a field does not pertain to a specific trap, the deduplication appliance omits the field. This situation can occur, for example, with the Dataselection, Job, or Jobstep fields. You can use the Web UI to change the following values: The alias and hostname values for an agent. To change these values for client agents, complete the following steps: Select Manage > Agents. Select a client agent in the left pane. Edit the information in the right pane. Click Save. To change these values for server agents, complete the following steps: Select Settings > Topology. Select a server agent in the left pane. Edit the information in the right pane. Click Save. The storagepoolname. To change this value for a storage pool, complete the following steps: Select Settings > Topology. Select a storage pool in the left pane. Edit the information in the right pane. Click Save. The following is an SNMP trap example for software traps: SNMPv2-MIB::sysUpTime.0 = Timeticks: ( ) 15:34:03.65 SNMPv2-MIB::snmpTrapOID.0 = OID: VERITAS-COMMAND-CENTRAL-MIB::ccCritical VERITAS-COMMAND-CENTRAL-MIB::alertDescription = STRING: Storagepool: 771 (birdie,spa:acme.com)agent: (acme.com, PDserver)ErrID: 1001Descr: Service 'Controller' (pdctrl) is currently not running The following is an SNMP trap example for deduplication appliance hardware traps:

47 Storage pool management procedures for deduplication appliances About non-event-based SNMP traps 47.iso.org.dod.internet.mgmt.mib-2.system.sysUpTime.0: TimeTicks: 150 days, 0 hours, 26 minutes, 6 seconds.:.iso.org.dod.internet.snmpv2.snmpmodules.snmpmib.snmpmibobjects.snmptrap.snmptrapoid.0: Object ID: :.iso.org.dod.internet.private.enterprises.symantecsoftware.products.applianceMonitoringMib. systems.systemname: test_system_name:.iso.org.dod.internet.private.enterprises.symantecsoftware.products.appliancemonitoringmib. systems.powertrap: POWER 1 status : Failure detected: POWER 1 wattage : 0 Watts: POWER 1 lowwatermark : 0: POWER 1 highwatermark : 700 Watts:.iso.org.dod.internet.private.enterprises.symantecsoftware.products.applianceMonitoringMib. systems.cputrap: CPU 2 status : Disabled: CPU 2 voltage : -: CPU 2 lowwatermark : -: CPU 2 highwatermark : -: Note: Some lines in the preceding example were wrapped and indented for inclusion in this topic. The following topics contain information about SNMP traps on the deduplication appliance: See Enabling non-event-based SNMP traps for hardware monitoring on page 47. See Using the command-line shell to enable non-event-based SNMP traps on page 48. See Using the command-line shell to disable non-event-based SNMP traps on page 50. The information in this guide that describes SNMP traps supplements the information about how to enable the SNMP traps that is included in the following manual: PureDisk Backup Operator's Guide Enabling non-event-based SNMP traps for hardware monitoring The following procedure describes how to enable the SNMP software.

48 48 Storage pool management procedures for deduplication appliances About non-event-based SNMP traps To configure the SNMP software 1 Obtain the following files from the storage pool authority node and install them on your site's SNMP manager server: /opt/pdinstall/snmp/veritas-reg.mib /opt/pdinstall/snmp/veritas-tc.mib /opt/pdinstall/snmp/vrts-cc.mib /opt/pdinstall/snmp/symantec-appliance-monitoring.mib In the preceding list, the first three files constitute the NetBackup MIB and are used for monitoring software events. The last file is used for monitoring hardware events. 2 Perform one of the following procedures: The procedure called "Enabling the non-event-based SNMP trap feature" in the online Help or in the following manual: PureDisk Backup Operator's Guide The following procedure: See Using the command-line shell to enable non-event-based SNMP traps on page 48. See About non-event-based SNMP traps on page 45. Using the command-line shell to enable non-event-based SNMP traps The following procedure explains how to use the deduplication appliance's command-line shell to enable non-event-based SNMP traps. This procedure has the same effect as the SNMP enablement procedure in the following manual: PureDisk Backup Operator's Guide To enable non-event-based SNMP traps 1 Start a command-line shell session on the storage pool authority node. Perform the following steps: Connect to the storage pool authority node through an SSH connection. Type the user name and password for the deduplication appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). After the welcome information appears, press q to display the root mode menu. Type support at the shell menu prompt and press Enter.

49 Storage pool management procedures for deduplication appliances About non-event-based SNMP traps 49 For example: > support 2 Type the following snmp add command to specify one or two SNMP server names and (optionally) your SNMP community: > snmp add server1 [community] For server, specify the IP address, host name, or FQDN of your site's primary SNMP server. The deduplication appliance must be able to contact this server. For community, specify the community name. This argument is optional. Default is public. The following example specifies the primary SNMP server: > snmp add Successfully updated SNMP SERVER to If you want to add a secondary SNMP server, type the following snmp add command: > snmp add server1 [community] server2 > snmp add public (Optional) Type the following command to verify the SNMP server: > snmp show The following output shows one SNMP server: > snmp show SNMP PORT : 162 SNMP SERVER : SNMP ENABLE : 0 SNMP COMMUNITY : public The following output shows two SNMP servers: > snmp show SNMP PORT : 162 SNMP SERVER2 : SNMP SERVER : SNMP ENABLE : 0 SNMP COMMUNITY : public

50 50 Storage pool management procedures for deduplication appliances About non-event-based SNMP traps 4 Type the following command to enable SNMP: > snmp enable hardware 5 (Optional) Type the following command to verify that SNMP is enabled: > snmp show The following example shows the output from the snmp show command after you enable SNMP. Note the line that reads SNMP ENABLE : 1, which indicates that SNMP is enabled. > snmp show SNMP PORT : 162 SNMP SERVER2 : SNMP SERVER : SNMP COMMUNITY SNMP ENABLE SOFTWARE : 0 SNMP ENABLE HARDWARE : 1 : public 6 Type the following command to return to the main shell menu: > exit 7 Type the following command to exit the shell menu: > logout See About non-event-based SNMP traps on page 45. Using the command-line shell to disable non-event-based SNMP traps The following procedure explains how to disable non-event-based SNMP traps. To disable non-event-based SNMP traps 1 Start a command-line shell session on the storage pool authority node. Perform the following steps: Connect to the storage pool authority node through an SSH connection. Type the user name and password for the deduplication appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0).

51 Storage pool management procedures for deduplication appliances About passwords on the deduplication appliance 51 After the welcome information appears, press q to display the root mode menu. Type support at the shell menu prompt and press Enter. For example: > support 2 Type the following command to disable SNMP: > snmp disable hardware 3 (Optional) Type the following command to verify that SNMP is disabled: > snmp show SNMP PORT : 162 SNMP SERVER2 : SNMP SERVER : SNMP COMMUNITY : public SNMP ENABLE SOFTWARE : 0 SNMP ENABLE HARDWARE : 0 4 Type the following command to return to the main shell menu: > exit 5 Type the following command to exit the shell menu: > logout See About non-event-based SNMP traps on page 45. About passwords on the deduplication appliance The deduplication appliance has several user accounts. During the initial configuration, Symantec recommends that you change the password for the administrative root user from the default of P@ssw0rd to a strong password of your own. The sixth character is the numeral zero (0). For information about creating passwords, see the Deduplication Appliance Software Getting Started Guide. The following topics explain how to change the passwords in use on the deduplication appliance: See sysadmin account's password on page 52. See Operating system root user's password on page 52.

52 52 Storage pool management procedures for deduplication appliances About passwords on the deduplication appliance See Configuration Wizard's password on page 52. See Storage pool administrative Web UI's root account password on page 53. See Root account's password on a remote storage pool on page 53. sysadmin account's password The sysadmin account is the operating system account through which you can access the deduplication appliance command-line interface. For more information about how to use the command-line shell to change the sysadmin account's password, see the following: See About the appliance shell menu on page 202. The following procedure explains how to change the sysadmin account's password: To change the sysadmin account's password 1 Use a Secure Shell (SSH) connection to log into the storage pool authority node as sysadmin. 2 Type the existing password when prompted. 3 Press any key to display the help and the root mode menu. 4 Select admin on the root menu. 5 Select password. 6 Follow the prompts to change the password. The default is P@ssw0rd. Operating system root user's password This password is the individual appliance's operating system's root user account. The following procedure explains how to change this password. To change the operating system root user's password 1 Log into an appliance as root. 2 Use the passwd(1) command to change the root password. The default is P@ssw0rd. Configuration Wizard's password This password is used only when you start the installer to access the Web-based Network Configuration Wizard or Storage Pool Configuration Wizard. The following procedure explains how to change this password:

53 Storage pool management procedures for deduplication appliances About passwords on the deduplication appliance 53 To change the Configuration Wizard's password 1 Type the following URL into a browser: For spa_fqdn, specify the fully qualified domain name of the storage pool authority node. 2 On the welcome page, click Change configuration wizard password, which appears as a link at the right. 3 To change the password, follow the prompts on the window that appears. The default is P@ssw0rd. Storage pool administrative Web UI's root account password The storage pool authority's administrative Web UI has a root user account. The root user can access the storage pool authority services and can also configure the storage pool on the NetBackup master server. The following procedure explains how to change this password: To change the storage pool administrative Web UI's root account password 1 Type the following URL into a browser: For spa_fqdn, specify the fully qualified domain name of the storage pool authority node. 2 Click Settings > Configuration > User Management > Users > root. 3 In the right pane, click Change Password. 4 (Conditional) Change the operating system root user account password in your NetBackup environment. Perform this step if interoperation with NetBackup is enabled. If you change the operating system root user's password on the storage pool authority appliance node after operations with NetBackup have been defined, make sure to update the storage pool authority node's root user password in NetBackup. For information about how to change this password, see the PureDisk Deduplication Option Guide. Root account's password on a remote storage pool You can create a central storage pool that collects report information from other, remote storage pools. If you change the root password on one of the remote

54 54 Storage pool management procedures for deduplication appliances Removing a node from a storage pool (managed) storage pools, also change the password of the remote storage pool on the central storage pool's Settings page. The following procedure explains how to change this password: To change the root account's password on a remote storage pool 1 Type the following URL into a browser: For central_spa_fqdn, specify the fully qualified domain name of the central storage pool authority node. 2 Click Settings > Central SPA > World > Storage Pool Management > Deduplication Appliance. 3 In the right pane, update the Password field. Removing a node from a storage pool If your storage pool consists of multiple nodes, you can remove any node that is not the storage pool authority node. You cannot remove the storage pool authority node. The following procedure describes how to prepare an appliance node for removal and how to remove the node. It is very important to ensure that the node is unused and is no longer active before you perform the actual removal. The following procedure refers to the Storage Pool Management chapter of the PureDisk Administrator's Guide for information about how to prepare a node for removal. To remove a non-storage pool authority node from a storage pool 1 (Conditional) Reroute the content router on the deduplication appliance node that you want to remove. Perform this step if the node that you want to remove currently hosts an active content router. When you installed the node, the content router service was preinstalled on the node. At that time, you had the option to activate the content router. The content router service contains the backup data that you need to preserve. The way to preserve this data is through rerouting, which moves the backup data into content routers on other nodes. Depending on how much back data resides on the node that you want to remove, rerouting can take several hours or several days to complete. See the following:

55 Storage pool management procedures for deduplication appliances Removing a node from a storage pool 55 See the topic called "Rerouting a content router and managing content routers" in the "Storage Pool Management" chapter of the PureDisk Administrator's Guide. 2 (Conditional) Reroute the metabase engine on the deduplication appliance node that you want to remove. Perform this step if the node that you want to remove currently hosts an active metabase engine. When you installed the node, the metabase engine service was preinstalled and activated on the node. An active metabase engine service contains metadata that you need to preserve. The way to preserve this data is through rerouting, which moves the metadata from this node and into the metabase database on other nodes. When you reroute a metabase engine, you also move the clients that are attached to the controller on this node to controllers on other nodes. The procedure you need to follow to reroute a metabase engine requires root access to the node. You can use the deduplication appliance shell menu admin > su command to gain root access. See the following topic for more information: See the topic called "Rerouting a metabase engine" in the "Storage Pool Management" chapter of the PureDisk Administrator's Guide 3 (Conditional) Deactive the content router and the NetBackup export engine on the deduplication appliance node that you want to remove. Perform this step if the content router and the NetBackup export engine on the appliance node that you want to remove are active at this time. See the following: See the topic called "Deactivating a content router or a NetBackup export engine" in the "Storage Pool Management" chapter of the PureDisk Administrator's Guide: 4 Use an SSH connection to connect to the storage pool authority node. 5 Type the user name and password for the deduplication appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). 6 After the welcome information appears, press q to display the root mode menu. 7 Type the following command at the shell menu prompt: > PureDisk

56 56 Storage pool management procedures for deduplication appliances Removing a node from a storage pool 8 Type the following command at the shell menu prompt: > removenode hostname For hostname, type the host name of the node that you want to remove. 9 Type the following command at the shell menu prompt to return to the main shell menu: > exit 10 Dispense with the deactivated appliance node. For example, if you want to use the node in a different storage pool, make sure to reimage the node. For information about how to reimage an appliance see the following: See About resetting and reimaging a deduplication appliance node or storage pool on page 76.

57 Chapter 2 Hardware monitoring and alerts This chapter includes the following topics: About hardware monitoring and alerts Retrieving hardware monitoring information About notification from the deduplication appliance About hardware monitoring and alerts The deduplication appliance monitors itself for hardware problems. The hardware monitoring information includes the appliance serial number, the appliance model number, and information about the components that is listed in Table 2-1. You have two ways to configure hardware alerts. First, you can configure alerts by . Second, you can configure alerts through non-event-based SNMP. More information about these topics is available. See About notification from the deduplication appliance on page 63. See About non-event-based SNMP traps on page 45.

58 58 Hardware monitoring and alerts About hardware monitoring and alerts Table 2-1 Monitored hardware components in a NetBackup deduplication appliance Monitored hardware CPU Sample of collected data Displays the following information about the CPU: Status. Can be either Presence detected or Disabled. Voltage. Monitors the voltage to the appliance CPU chip and reports a CPU failure if any of the following conditions occur: No voltage The voltage is less than the low watermark. The low watermark is read from the system. The voltage is more than the high watermark. The high watermark is read from the system. State. Any state other than OK indicates a missing CPU or that the voltage for the CPUs is not within the normal range. Disk Monitors the boot drive and the storage drives. Reports a disk failure if an internal erroneous state occurs. Displays the following information: Slot Number. Slot in the robot that contains the volume. Status. Current status of the media. For example, Online, Spun Up, Unconfigured (bad). Foreign state. Indicates if the disk is foreign. For example, None or Foreign. Capacity. Current capacity of the disk. Type. The disk type. For example, SAS, SATA. Serial Number. The disk's serial number. Enclosure ID. Identification number of the enclosure in which the disk resides. State. If the State is not OK that means: The status is either Failure, Unconfigured (bad), Missing, or Offline. The status of the hot spare disk is not Hotspare. There is no disk in the slot.

59 Hardware monitoring and alerts About hardware monitoring and alerts 59 Table 2-1 Monitored hardware components in a NetBackup deduplication appliance (continued) Monitored hardware RAID Sample of collected data Monitors the RAID status and reports an error if the status changes from optimal. Displays the following information: Name. The name of the RAID device. Status. Shows the current status of the device, such as Optimal. Capacity. The capacity of each device. Type. The type of RAID device, such as RAID-1 or RAID-6. Disks. The disks being used. Write Policy. Current write policy of each virtual disk. Enclosure ID. The enclosure ID for the RAID array. Hotspare Available. Indicates the availability of global hot spare disks for the given virtual disk. State. If the State is not OK that means: The status is not Optimal. The Write Policy is Write through. The appliance does not contain any hot spare disks if the disk type is RAID-6. Fan Monitors the fan units and reports errors. Displays the following information: Status. Reports the presence or absence of a fan unit, as follows: Device Present or Device Absent. Speed. Monitors the fan speed and reports a fan failure when the following conditions occur: The fan speed drops below the low watermark. The low watermark is read from the system. The fan speed exceeds the high watermark. The high watermark is read from the system. State. If the State is not OK, that indicates a missing fan or that the speed is not within the normal range. Power Supply Monitors the power supply wattage. Displays the following information: Status. Detects the wattage levels and determines whether the readings are within the limits of the low watermark and the high watermark. The following are the types of status messages displayed: Presence detected. Displayed when the power is working as expected. Failure detected. Displayed when the power module is not installed or when the power supply is installed but not connected to the power outlet. Wattage. Monitors the wattage and reports a failure when the following conditions occur: The wattage drops below the low watermark. The wattage exceeds the high watermark. State. If the State is not OK, that indicates that the power supply is absent or that the wattage is not within the normal range.

60 60 Hardware monitoring and alerts About hardware monitoring and alerts Table 2-1 Monitored hardware components in a NetBackup deduplication appliance (continued) Monitored hardware Temperature Sample of collected data Monitors the temperature of the appliance at different points. Displays the following information: Type. Location within the appliance at which the temperature was read. This location can be one of the following: Intake Vent Temp Outtake Vent Temp Backplane Temp Temperature. Reports the actual temperature reading and reports a problem when the following conditions occur: The temperature drops below the low watermark. The low watermark is read from the system. The temperature exceeds the high watermark. The high watermark is read from the system. State. If the State is not OK, that indicates that the temperature reading at that location is not within the normal range. Fibre Channel HBA Hardware Alerts PCI Monitors the fibre card status. Displays the following information: Status. Can be either Online, which means that the port is connected to a cable, or LinkDown. Mode. The port's working mode, either Target or Initiator. Port WWN. The unique world-wide name (WWN) for the port. Slot. The physical slot where the fibre card is inserted. You can see the slot number on the rear panel. Speed. The port speed, for example, 2G, 4G, 8G. Remote Ports. Shows the WWNs of the other ports that this port can scan. Displays the WWN of each port that this port can scan remotely. State. If the State is not OK that means the port is not online, linkdown or diagnostics. Displays the hardware alerts. Monitors the peripheral component interconnect (PCI) expansion slots. Displays the following information: Slot. Slot. The physical slot where the PCI is inserted. You can see the slot number on the rear panel. Details. Information about the PCI card in the slot or the keyword EMPTY. If a card resides in the slot, the information includes the card type and the manufacturer.

61 Hardware monitoring and alerts About hardware monitoring and alerts 61 Table 2-1 Monitored hardware components in a NetBackup deduplication appliance (continued) Monitored hardware Adapter Sample of collected data Monitors the RAID adapter. Displays the following information: Adapter model. Includes the type and manufacturer. Adapter Status, which identifies the adapter s working status. BBU Status, which identifies the BBU s status. BBU Charging Status, which identifies if the BBU is charging, discharging, or none of them. BBU Learn Cycle Active. If the BBU is present and is in Learn Cycle Active state, the RAID s Write Policy is changed to Write Back automatically. This change results in poor write performance. BBU charge. The percentage of charge in the battery. If the appliance uses a supercap instead of a BBU, no value is shown here. State. If the State is not OK that means the BBU is missing, BBU is in Learning Cycle Active state, or BBU Charging is less than 60%. Network Monitors the network cards. Displays the following information: Port name. The card's ethx identifier. Card model. The card manufacturer. If Symantec does not support the card, displays the phrase Unsupported Network Card. Serial number. The card serial number. Port speed. MAC address. Link state. Displays Up or Down. Firmware Monitors the firmware, including network card firmware and RAID controller firmware. Displays the following information: Name. Displays the name of each piece of firmware. Version. Displays the version number of the firmware. Enclosure Note: This command is implemented for a future hardware platform. It is not supported on the current hardware. After the appliance logs a problem that needs attention, you can retrieve the notice in one of the following ways: Through the administrative Web UI in the hardware monitoring and alerts panels. See Retrieving hardware monitoring information on page 62. In an that is sent from the appliance to the local administrator.

62 62 Hardware monitoring and alerts Retrieving hardware monitoring information See About notification from the deduplication appliance on page 63. In a notification that is sent from the appliance to Symantec by the call home feature. See Using the call home feature on page 18. Symantec recommends that you check for hardware alert messages on a daily basis. Retrieving hardware monitoring information The following procedures explain how to retrieve hardware monitoring information from the administrative Web UI and from the appliance shell menu. To retrieve hardware monitoring information from the administrative Web UI 1 Log into the administrative Web UI. 2 Click Monitor > System. 3 In the left pane, click the plus sign (+) next to the name of the storage pool you want to monitor. The system displays the categories of information that are available to be monitored. 4 Click the hardware category for which you want the system to display information. To retrieve hardware monitoring information from the appliance shell menu 1 Connect to the storage pool authority node through a Secure Shell. 2 Type the logon name and password for the appliance. By default, the logon name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is the numeral zero (0). 3 Press any key to advance from the Welcome screen. 4 Press q to exit the help information. 5 Type the support > hwmon show hw_sensor command to monitor a specific piece of hardware or all of the components. For hw_sensor, type the name of the hardware you want to monitor. For more information about hardware monitoring, see one of the following: See About hardware monitoring and alerts on page 57. See About notification from the deduplication appliance on page 63. See Using the call home feature on page 18.

63 Hardware monitoring and alerts About notification from the deduplication appliance 63 About notification from the deduplication appliance The deduplication appliance has the ability to send an to a local administrator when a hardware failure is detected. The following table lists the hardware failures that prompt an notification. It also contains an example of the contents that would appear in the for each failure. Monitored Hardware Adapter Example of the contents ADAPTER 1 Adapter model : Intel (R) RAID Controller RS25SB008 ADAPTER 1 BBU Status : Not OK ADAPTER 1 ErrorStatus : 2 ADAPTER 1 Adapter Status : OK ADAPTER 1 BBU Learn Cycle Active : - ADAPTER 1 BBU charge : - ADAPTER 1 BBU Charging Status : - ADAPTER 1 State : Critical Warning CPU CPU 2 ErrorStatus : 1 CPU 2 Status : Disabled CPU 2 LowWaterMark : Volts CPU 2 Voltage : - CPU 2 State : Failure CPU 2 HighWaterMark : Volts

64 64 Hardware monitoring and alerts About notification from the deduplication appliance Monitored Hardware Disk Example of the contents DISK 10 Slot Number : 9 DISK 10 Enclosure ID : - DISK 10 Status : Not found DISK 10 Serial Number : - DISK 10 Capacity : - DISK 10 State : Failure DISK 10 Type : - DISK 10 Foreign state : - DISK 10 ErrorStatus : 1 DISK 23 Slot Number : 22 DISK 23 Enclosure ID : 8 DISK 23 Status : Unconfigured(good), Spun Up DISK 23 Serial Number : 9WM1N1EZST NS SN12 DISK 23 Capacity : TB [0xe8e088b0 Sectors] DISK 23 State : Warning DISK 23 Type : SATA DISK 23 Foreign state : Foreign DISK 23 ErrorStatus : 3 DISK 24 Slot Number : 23 DISK 24 Enclosure ID : 8 DISK 24 Status : Unconfigured(good), Spun Up DISK 24 Serial Number : 9WM1N1H5ST NS SN12 DISK 24 Capacity : TB [0xe8e088b0 Sectors] DISK 24 State : Warning DISK 24 Type : SATA DISK 24 Foreign state : Foreign DISK 24 ErrorStatus : 3 Fan FAN 1 ErrorStatus : 1 FAN 1 Speed : - FAN 1 Status : Device Absent FAN 1 LowWaterMark : RPM FAN 1 State : Failure FAN 1 HighWaterMark : RPM FAN 2 ErrorStatus : 1 FAN 2 Speed : - FAN 2 Status : Device Absent FAN 2 LowWaterMark : RPM FAN 2 State : Failure FAN 2 HighWaterMark : RPM

65 Hardware monitoring and alerts About notification from the deduplication appliance 65 Monitored Hardware Power Supply Example of the contents POWER 2 Wattage : - POWER 2 ErrorStatus : 1 POWER 2 Status : Failure detected POWER 2 LowWaterMark : 1 Watts POWER 2 State : Failure POWER 2 HighWaterMark : 700 Watts RAID Group RAIDGROUP 2 Enclosure ID : 8 RAIDGROUP 2 Status : Optimal RAIDGROUP 2 Disks : 4,5,6,7,8,10,11,12,13,14,15,16,17,18,19,2 RAIDGROUP 2 Capacity : TB RAIDGROUP 2 State : Warning RAIDGROUP 2 Type : Primary-6, Secondary-0, RAID Level Qualifi RAIDGROUP 2 ErrorStatus : 3 RAIDGROUP 2 All HotSpares Available : yes RAIDGROUP 2 Write Policy : WriteThrough, ReadAheadNone, Direc RAIDGROUP 2 Name : VD-2 For information about how to configure notifications, see the following: See Configuring notifications from the appliance shell menu on page 65. See Configuring notifications from the administrative Web UI on page 66. For general information about hardware notifications, see the following: See About hardware monitoring and alerts on page 57. See Retrieving hardware monitoring information on page 62. See Using the call home feature on page 18. Configuring notifications from the appliance shell menu You can use the support > hardware command from the appliance shell menu interface to configure the address that you want to use to receive the hardware failure notification. The contents of the identifies the type of hardware failure that occurred and a status of the failure. For more information about how to configure notifications from the appliance shell menu, see the following topic: See About the appliance shell menu on page 202.

66 66 Hardware monitoring and alerts About notification from the deduplication appliance For more information about notifications, see the following: See About notification from the deduplication appliance on page 63. Configuring notifications from the administrative Web UI You can use the appliance's administrative Web UI to specify notifications. The following procedure explains how to configure this feature by using the administrative Web UI. To configure notifications from the administrative Web UI 1 Log into the storage pool's administrative Web UI. 2 Click Settings > Configuration. 3 In the left pane, click Hardware. 4 In the right pane, complete the fields as follows: Field addresses SMTP server Notification interval Content Specify the addresses to which you want to send the hardware notifications. To specify more than one address, use a semicolon character (;) as the separator. Specify the fully qualified domain name of the site SMTP server. Specify the notification interval. The minimum interval is 15 minutes, and the interval must be in 15-minute increments. For example, you can specify 15, 30, 45, 60, and so on as the notification interval. Node IPs to set notification interval Specify the IP address of one or more storage pool nodes. To specify more than one node address, use a semicolon character (;) as the separator. 5 Click Save. After you click Save, the system stores the information you specified. You can specify different address or different notification intervals for specific nodes. Example: Assume that you want to send about the storage pool authority node every 15 minutes. Also assume that you want to send about the content router nodes every 30 minutes. To do this task, specify the storage pool authority

67 Hardware monitoring and alerts About notification from the deduplication appliance 67 node's information and click Save. After the Save completes, specify the 30-minute intervals for the content routers. For more information about notifications, see the following: See About notification from the deduplication appliance on page 63.

68 68 Hardware monitoring and alerts About notification from the deduplication appliance

69 Chapter 3 Software monitoring and alerts This chapter includes the following topics: About software monitoring and alerts Retrieving software monitoring information Configuring software monitoring alerts About software monitoring and alerts You can configure the deduplication appliance to monitors itself for software problems. The software situations you can monitor for alerts includes disk volume, transaction log age, and PureDisk services status. Information about the alert levels is listed in Table 3-1. Table 3-1 Software alert levels Alert level Value Debug Info Authorization Warning Error Critical Bug

70 70 Software monitoring and alerts Retrieving software monitoring information Retrieving software monitoring information The following procedures explain how to retrieve software monitoring information from the administrative Web UI. To retrieve software monitoring information from the administrative Web UI 1 Log into the administrative Web UI. 2 Click Monitor > Alerts & Notifications. 3 In the left pane, click the Alerts folder to see all alerts for all agents. Select the individual agents under Alerts to view the alerts for a specific agent. For more information about monitoring, see one of the following: See About hardware monitoring and alerts on page 57. See About notification from the deduplication appliance on page 63. Configuring software monitoring alerts You can configure software alerts by several different methods. The methods are: Use SMTP in the appliance shell menu. More information about this topic is available. See To configure software alerts through SMTP in the appliance shell menu on page 71. Use SMTP in the administrative Web UI. More information about this topic is available. See To configure software alerts through SMTP in the administrative Web UI on page 71. Use event-based SNMP in the administrative Web UI. More information about this topic is available. See To configure software alerts through event-based SNMP in the administrative Web UI on page 72. Use event-based SNMP in the appliance shell menu. More information about this topic is available. See To configure software alerts through event-based SNMP in the appliance shell menu on page 73. Use non-event-based SNMP in the administrative Web UI. More information about this topic is available. See To configure software alerts through non-event-based SNMP in the administrative Web UI on page 74.

71 Software monitoring and alerts Configuring software monitoring alerts 71 To configure software alerts through SMTP in the appliance shell menu 1 Connect to the storage pool authority node through a Secure Shell. 2 Type the logon name and password for the appliance. By default, the logon name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is the numeral zero (0). 3 Press any key to advance from the Welcome screen. 4 Press q to exit the help information. 5 Enter support to change to the support view. 6 Use the show parameter to review the current SMTP server settings. Use the set parameter to change the SMTP server if necessary. smtp show - Shows the current SMTP server setting. smtp set server_name - Defines the SMTP server. More information about these commands is available. See About the appliance shell menu on page Use the add command to add an address to receive the alerts. software add address More information about these commands is available. See About the appliance shell menu on page Use the show parameter to the SMTP alert settings. Use the set parameter to change the settings if necessary. software alert show - Shows the current alert settings. software alert set min max [agentid] - Change the alert settings. If agentid is omitted, the alert applies to the storage pool. More information about these commands is available. See About the appliance shell menu on page 202. To configure software alerts through SMTP in the administrative Web UI Note: More information about how to configure event escalation actions is available. Symantec NetBackup PureDisk Backup Operator Guide

72 72 Software monitoring and alerts Configuring software monitoring alerts 1 Open a browser, and type the following URL to access the storage pool authority's opening panel: For URL, type the URL for the storage pool authority node. 2 Log in as root with the correct password. By default, the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). 3 Click Settings > Configurations 4 In the left pane, click the plus sign next to Escalation Actions to expand Escalation Actions. 5 In the left pane, click Event Escalation Actions. In the right pane, click Add Event Escalation Action to add a new event escalation action. Enter a description in the Description field. Select SMTP from the Escalation Type drop-down. Enter the correct address in the address to use for escalation field. Optionally, enter a subject and an escalation message in the Subject and the Escalation message fields. 6 In the left pane, select Configuration File Templates > PureDisk Server Agent > Default ValueSet for PureDisk Server Agent > mail > smtpserver. 7 In the left pane, click All OS ip_address. In the right pane, for Value, enter the correct TCP/IP address for the SMTP server. 8 You must now add either and AgentEventEscalation or a StoragePoolEvent Escalation. More information about this is available. Symantec NetBackup PureDisk Backup Operator Guide SMTP Software Alerts is automatically enabled after SMTP server and address is configured By default alerts with levels from Error(5) to Bug(7) will be sent To configure software alerts through event-based SNMP in the administrative Web UI Note: More information about how to configure alerts through event-based SNMP is available. Symantec NetBackup PureDisk Backup Operator Guide

73 Software monitoring and alerts Configuring software monitoring alerts 73 1 Open a browser, and type the following URL to access the storage pool authority's opening panel: For URL, type the URL for the storage pool authority node. 2 Log in as root with the correct password. By default, the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). 3 Click Settings > Configurations > Escalation Actions > Event Escalation Actions. 4 In the left pane, click Event Escalation Actions. In the right pane, click Add Event Escalation Action to add a new event escalation action. Enter the correct SNMP server hostname or TCP/IP in the SNMP manager address field. Enter the correct SNMP community in the SNMP community field. 5 You must now add either and AgentEventEscalation or a StoragePoolEvent Escalation. More information about this is available. Symantec NetBackup PureDisk Backup Operator Guide To configure software alerts through event-based SNMP in the appliance shell menu 1 Connect to the storage pool authority node through a Secure Shell. 2 Type the logon name and password for the appliance. By default, the logon name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is the numeral zero (0). 3 Press any key to advance from the Welcome screen. 4 Press q to exit the help information. 5 Enter support to change to the support view. 6 The snmp and the snmp add commands provide access to modify the alerts. The snmp software alert set and show commands are used to set and show the alert levels. More information about these commands is available. See About the appliance shell menu on page 202. Note: SNMP software alerts are disabled by default. Use the support > snmp enable disable software command to enable alerts or disable alerts.

74 74 Software monitoring and alerts Configuring software monitoring alerts To configure software alerts through non-event-based SNMP in the administrative Web UI 1 Open a browser, and type the following URL to access the storage pool authority's opening panel: For URL, type the URL for the storage pool authority node. 2 Log in as root with the correct password. By default, the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). Refer to the Enabling the non-event-based SNMP trap feature section in PureDisk Backup Operator s Guide.

75 Chapter 4 Resetting and reimaging a deduplication appliance storage pool This chapter includes the following topics: About resetting and reimaging a deduplication appliance node or storage pool Performing a network reset on an unconfigured appliance Resetting or reimaging a configured deduplication appliance (Conditional) Preparing NetBackup for a deduplication appliance reset or reimage (Conditional) Preparing other storage pools for a deduplication appliance reset or reimage (Conditional) Preparing to reset a storage pool or reimage a node Performing a storage pool reset Performing a soft reset Performing an image reset Performing a USB reimage

76 76 Resetting and reimaging a deduplication appliance storage pool About resetting and reimaging a deduplication appliance node or storage pool About resetting and reimaging a deduplication appliance node or storage pool You can perform a software reset on an appliance node or on an entire storage pool. You can use the USB stick to reimage one or more appliances in your storage pool. Symantec supports different levels of reset and reimage procedures. You might want to reset or reimage your appliance to remove backup data, configuration data, software upgrades, or the operating system itself. The effects of a reset and a reimage are as follows: The software resets can remove networking data, user data, user specifications, and other information. You can perform different levels of resets. The various resets are progressively more invasive. A storagepool normal reset is the lightest reset. An image reset is the most comprehensive. When you perform an image reset, the result is that the factory-shipped operating system level now resides on the appliance. For most software resets, you need to perform the reset from the storage pool authority node. The storage pool authority waits for all other nodes to reset simultaneously before it resets itself. If there are reset problems with any nodes, the storage pool authority node displays the error for that node in the administrative shell output. The exception to this rule is the network reset, which needs to be performed on an individual appliance before the appliance is configured as a storage pool node A USB reimage removes all information from a specific appliance and installs the PDLinux operating system from the USB device onto the appliance. If you have an older operating system on an appliance, you can use a USB device from a newer release to upgrade that appliance to the newer release Table 4-1 explains the different software resets.

77 Resetting and reimaging a deduplication appliance storage pool About resetting and reimaging a deduplication appliance node or storage pool 77 Table 4-1 Action Network reset Software reset types Details A network reset is different from the other software resets because you can perform a network reset only if the storage pool is not configured. You perform a network reset on an individual, unconfigured appliance. A network reset removes all networking specifications. For example, assume that you specified an appliance's network information when you clicked Start the network configuration wizard on the Configuration Wizard 's landing page. If you decide that you want to change the networking information before you specify the storage pool configuration information, you can perform a network reset. You could also perform a network reset if you had configured the network through the appliance shell menu. Storage pool reset A storage pool reset is the lightest of the resets. The keyword for this type of reset isstoragepool. When you perform a storage pool reset, you can choose either a normal storage pool reset or a full storage pool reset. These are the least destructive resets. Please be aware, however, that a storage pool reset still destroys all backup data and a lot of configuration data. Perform a normal or full storage pool reset if you want to remove all user data, permissions, and so on and start backing up clients again with a new, empty storage pool. For example, if you made mistakes when you configured your storage pool, or if your storage pool is full of backup data you do not want to retain, you can perform a storage pool reset Soft reset A soft reset performs all the actions of a storage pool full reset, but a soft reset is more destructive. A soft reset deletes networking information, including VLAN, TCP/IP, and NIC bonding information. Perform a soft reset if you suspect that the PureDisk software on the storage pool is corrupted. The soft reset removes all backup data, network configuration, topology configuration, and so on. This reset removes and reinstalls the PureDisk software and (optionally) upgrades and patches. Image reset An image reset is the most comprehensive reset. After an image reset, the appliance is set to the way it was when the appliance first shipped from the factory. All data, network, VLAN, and configuration information is removed. Symantec supports the image reset only on the appliances that were shipped from the factory with the Deduplication Appliance Software 1.4 release or later installed upon them

78 78 Resetting and reimaging a deduplication appliance storage pool About resetting and reimaging a deduplication appliance node or storage pool If you have a multinode storage pool, make sure that all nodes are at the same Deduplication Appliance Software release level before you perform a software reset of the storage pool. If you perform a soft or an image reset on a storage pool with some nodes that were upgraded and other nodes that were shipped from the factory with a specific software level, the result (after the reset) might be that you have a storage pool with nodes at different Deduplication Appliance Software release levels. This mix of release levels occurs for the following reasons: The image resets recreates the appliance as it was in its factory-shipped state. For example, consider the following events: The appliance that was shipped from the factory with the Deduplication Appliance Software 1.4 release installed upon it. You upgraded the appliance to Deduplication Appliance Software You performed an image reset on the appliance. After the reset, Deduplication Appliance Software 1.4 again resides on that appliance. The reset recreates the factor-shipped appliance, not the upgraded appliance. You requested an image reset, but the system had to fail back to a soft reset for a particular node. Caution: A software reset deletes many storage pool objects, including backup data. Make sure that is your intent before you perform any type of reset. For more information, see one of the following topics: See Performing a network reset on an unconfigured appliance on page 79. See Resetting or reimaging a configured deduplication appliance on page 80. See (Conditional) Preparing NetBackup for a deduplication appliance reset or reimage on page 81. See (Conditional) Preparing other storage pools for a deduplication appliance reset or reimage on page 82. See (Conditional) Preparing to reset a storage pool or reimage a node on page 83. See Performing a storage pool reset on page 84. See Performing a soft reset on page 86. See Performing an image reset on page 88. See Performing a USB reimage on page 90.

79 Resetting and reimaging a deduplication appliance storage pool Performing a network reset on an unconfigured appliance 79 Performing a network reset on an unconfigured appliance You can perform a network reset on an unconfigured appliance. For example, if you used the Configuration Wizard or the appliance shell menu to configure the network, you can perform a network reset to remove that information from the node. As long as you have not configured that individual appliance as a storage pool node, you can perform a network reset to remove the network information A network reset removes the following from a deduplication appliance: VLAN interfaces. Bonding interfaces. TCP/IP information. A network reset changes eth0 to / FQDN and host name information. DNS configuration. /etc/hosts file. /etc/nsswitch.conf file. Node IP information. A network reset changes the node IP address to The following procedure explains how to perform a network reset. To perform a network reset on an unconfigured appliance 1 Connect to the appliance. Use one of the following methods to connect to the appliance: Use an Ethernet cord to attach a Windows laptop computer to the appliance node. Attach the appliance to an existing KVM switch. 2 Log into the appliance shell menu. Complete the following steps: Use a Secure Shell connection to connect to the appliance. Type the user name and password for the appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is a zero (0) character. After the welcome information appears, type q to display the root menu.

80 80 Resetting and reimaging a deduplication appliance storage pool Resetting or reimaging a configured deduplication appliance 3 At the shell prompt, type support to enter the support view. 4 At the support prompt, type reset network. For example, the following sequence shows how to specify a network reset:...> support...support> reset network image network soft storagepool If the network reset fails, examine file /Storage/log/network_reset.log. See Resetting or reimaging a configured deduplication appliance on page 80. Resetting or reimaging a configured deduplication appliance The procedure in this topic explains how to perform a software reset or a USB device reimage. The procedure applies to the configured appliance nodes that are included in a storage pool. If you have only a network configuration stored on an appliance and you want to remove all network specifications, use the following procedure: See Performing a network reset on an unconfigured appliance on page 79. To perform a software reset or a USB device reimage 1 (Conditional) Prepare your backup environment. Perform one or both of the following procedures if the storage pool interoperates with NetBackup or with another PureDisk storage pool: See (Conditional) Preparing NetBackup for a deduplication appliance reset or reimage on page 81. See (Conditional) Preparing other storage pools for a deduplication appliance reset or reimage on page (Conditional) Back up any data you want to preserve. Perform the following procedure if you want to preserve any storage pool metadata or any backup data: See (Conditional) Preparing to reset a storage pool or reimage a node on page Perform the software reset or USB device reimage. Use one of the following procedures:

81 Resetting and reimaging a deduplication appliance storage pool (Conditional) Preparing NetBackup for a deduplication appliance reset or reimage 81 See Performing a storage pool reset on page 84. See Performing a soft reset on page 86. See Performing an image reset on page 88. See Performing a USB reimage on page 90. See About resetting and reimaging a deduplication appliance node or storage pool on page 76. (Conditional) Preparing NetBackup for a deduplication appliance reset or reimage Perform the following procedure if your deduplication appliance interoperates with a NetBackup appliance or with a NetBackup backup environment. When you complete the following procedure, you ensure that the larger backup environment is not negatively affected when you reset or reimage the deduplication appliance storage pool To prepare NetBackup for a deduplication appliance reset or reimage 1 Disable all policies that send data to the deduplication appliance. 2 Expire all the images that are associated with the storage server. 3 Delete all the storage units that are associated with the storage server. 4 Delete all the disk pools that are associated with the storage server. 5 Delete any auto image replication targets that are configured on the storage server. 6 Delete the storage server. 7 Look for and remove any storage_server_name.cfg files from the ost-plugins directory that are related to the storage pool being reset. For Windows, the directory is install_path\veritas\bin\ost-plugins. For UNIX or Linux, the directory is /usr/openv/netbackup/lib/ost-plugins/. For more information about the preceding steps, see the NetBackup documentation. 8 Proceed to one of the following: See (Conditional) Preparing other storage pools for a deduplication appliance reset or reimage on page 82. See (Conditional) Preparing to reset a storage pool or reimage a node on page 83.

82 82 Resetting and reimaging a deduplication appliance storage pool (Conditional) Preparing other storage pools for a deduplication appliance reset or reimage See Performing a storage pool reset on page 84. See Performing a soft reset on page 86. See Performing an image reset on page 88. See Performing a USB reimage on page 90. Note: If you reset a deduplication appliance, the data that was transferred to NetBackup during an export to NetBackup remains in the NetBackup environment. See Resetting or reimaging a configured deduplication appliance on page 80. (Conditional) Preparing other storage pools for a deduplication appliance reset or reimage Perform the procedure in this topic if the deduplication appliance that you want to reset or reimage receives replicated data from another deduplication appliance storage pool or from a PureDisk Remote Office Edition (ROE) storage pool. When you complete this procedure, you ensure that the larger backup environment is not negatively affected when you reset or reimage the deduplication appliance storage pool To prepare PureDisk for a deduplication appliance reset or reimage 1 If PureDisk ROE or another deduplication appliance replicates to the appliance being reset or reimaged, disable or remove the replication policies that point to the appliance being reset. If this step is not done, the replication jobs fail. After the reset or the reimage finishes and the appliance is reconfigured, you can create new replication policies to point to the appliance. 2 Proceed to one of the following: See (Conditional) Preparing to reset a storage pool or reimage a node on page 83. See Performing a storage pool reset on page 84. See Performing a soft reset on page 86. See Performing an image reset on page 88. See Performing a USB reimage on page 90.

83 Resetting and reimaging a deduplication appliance storage pool (Conditional) Preparing to reset a storage pool or reimage a node 83 Note: The reset or reimage of a deduplication appliance does not remove the data that was transferred to another storage pool. The replicated data still exists on the destination storage pool after the reset or reimage. See Resetting or reimaging a configured deduplication appliance on page 80. (Conditional) Preparing to reset a storage pool or reimage a node Perform the procedure in this topic if you want to retain any of the information that resides on the storage pool that you want to reset or reimage. You need to decide whether you want to back up and reuse the data. If the storage pool or any of the nodes are damaged or otherwise unusable, it might not be possible to preserve or reuse the data. The following procedure explains how to back up or preserve data on a storage pool or on a node. To prepare to reset or reimage a storage pool or a node 1 Preserve the information you want to keep. If you want to keep any of the backup data or metadata that this storage pool retains, complete the procedures for those actions before you begin the reset or reimage. The PureDisk Administrator's Guide contains the procedures that explain how to preserve storage pool data. The following are some examples of how to preserve data: Content router rerouting and metabase engine rerouting. In a multinode storage pool, if you want to reset or reimage a node that hosts a content router or a metabase engine, make sure to reroute the storage pool so that the node's backup data and metadata is distributed to the other nodes. If all the nodes are near their capacity, you might need to add an additional node and route data to that new node before you reset or reimage the old node. Storage pool authority replication (SPAR). If you have an all-in-one, single-node storage pool and you want to preserve the policies, user data, data selections, and other metadata in the storage pool, you can perform a SPAR backup to another storage pool. Symantec does not support SPAR backups for multinode storage pools. Replication. You can replicate backup data from one storage pool to another storage pool.

84 84 Resetting and reimaging a deduplication appliance storage pool Performing a storage pool reset Export to NetBackup. You can send backup data from a storage pool to a NetBackup appliance or from a storage pool to a NetBackup environment. 2 Proceed to one of the following: See Performing a storage pool reset on page 84. See Performing a soft reset on page 86. See Performing an image reset on page 88. See Performing a USB reimage on page 90. See Resetting or reimaging a configured deduplication appliance on page 80. Performing a storage pool reset A storage pool reset removes backup files and/or most of your configuration. This reset function might be useful to you if you want to experiment with a configuration before you put it into production. The two reset modes are Normal and Full. A Full reset deletes all data objects that a Normal reset deletes, plus additional data objects. Table 4-2 explains what the storage pool reset option deletes: Table 4-2 Objects deleted in a storage pool reset (normal or full) Normal reset deletes: Job statistics. Job steps. Jobs. Policy runs. Events. Backup data on the content routers. Metabase engine records. Report data. Audit trail records. Full reset deletes: Job statistics. Job steps. Jobs. Policy runs. Events. Backup data on the content routers. Metabase engine records. Report data. Audit trail records. Data selections. Agents. Policies. Users. Individual user permissions. Permissions for user groups remain. Agent escalations, storage pool escalations, and policy escalations.

85 Resetting and reimaging a deduplication appliance storage pool Performing a storage pool reset 85 The normal and full reset options do not affect the following objects: Data selection templates Locations Departments User groups Escalation actions License keys LDAP configuration Configuration file templates Network configuration details and storage pool authority topology details You can use either of the following procedures to reset a storage pool. Method 1 - To reset a storage pool from the Configuration Wizard 1 Make sure that you prepared this storage pool and/or the NetBackup environment that is connected to this storage pool for the reset. The reset completes more smoothly, and with a minimum of system disruption, if you prepare the system. For information about how to prepare the system, see the following process topic: See Resetting or reimaging a configured deduplication appliance on page Open a Web browser and type the following URL to start the Configuration Wizard : For address, type the IP address or FQDN of the storage pool authority node. 3 Log into the Storage Pool Configuration Wizard. 4 Click Reset Storage Pool. 5 On the Reset Options page, select either Normal or Full. 6 Select Click here to proceed. 7 Click Next. 8 On the Reset Progress page, click Finish. Method 2 - To reset a storage pool from the command-line shell 1 Make sure that you prepared this storage pool and/or the NetBackup environment that is connected to this storage pool for the reset.

86 86 Resetting and reimaging a deduplication appliance storage pool Performing a soft reset The reset completes more smoothly, and with a minimum of system disruption, if you prepare the system. For information about how to prepare the system, see the following process topic: See Resetting or reimaging a configured deduplication appliance on page Log into the appliance shell menu. Complete the following steps: Use a Secure Shell connection to connect to the storage pool authority node. Type the user name and password for the appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is a zero (0) character. After the welcome information appears, type q to display the root menu. 3 At the shell prompt, type support to enter support mode. 4 At the support prompt, type reset. 5 At the support prompt, type reset storagepool. 6 At the support prompt, type reset storagepool full or reset storagepool normal. For example, the following sequence shows how to specify a full storage pool reset:...> support...support> reset image network soft storagepool...support> reset storagepool full normal...support> reset storagepool full See Resetting or reimaging a configured deduplication appliance on page 80. Performing a soft reset A soft reset performs all the reset actions that a storagepool reset performs. In addition, a soft reset removes the following objects: All existing Deduplication Appliance Software and all PureDisk software. The reset reinstalls the application software and (optionally) reinstalls all patches.

87 Resetting and reimaging a deduplication appliance storage pool Performing a soft reset 87 The appliance shell menu dialog asks if you want to reinstall the software patches. All backup data and metadata. The existing network configuration, which includes all VLAN information, all TCP/IP information, and all NIC bonding information. All host name, call home, and topology information. When you perform a soft reset, the Deduplication Appliance Software resets all the nodes in the storage pool. You cannot reset a single node in a storage pool. As a part of the soft reset process, you have the option to reset the admin or root password for the IPMI account. If you reset the password, the password returns to the default Passw0rd. The sixth character is a zero (0). If the soft reset fails, examine the log files in the following location: /root/reset/log Sometimes the reset process fails because the system was unable to install the software patches. If you performed a soft reset, requested that the reset reinstall patches, and the reset failed, try the reset again. When you specify the reset for the second time, do not request that the reset reinstall the software patches. The following procedure explains how to perform a soft reset. To perform a soft reset 1 Make sure that you prepared this storage pool and/or the NetBackup environment that is connected to this storage pool for the reset. The reset completes more smoothly, and with a minimum of system disruption, if you prepare the system. For information about how to prepare the system, see the following process topic: See Resetting or reimaging a configured deduplication appliance on page Connect to the storage pool authority node. Use one of the following methods to connect to the storage pool's storage pool authority node: Use an Ethernet cord to attach a Windows laptop computer to the storage pool authority node. Attach the appliance to an existing KVM switch. 3 Log into the appliance shell menu. Complete the following steps:

88 88 Resetting and reimaging a deduplication appliance storage pool Performing an image reset Use a Secure Shell connection to connect to the storage pool authority node. Type the user name and password for the appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is a zero (0) character. After the welcome information appears, type q to display the root menu. 4 At the shell prompt, type support to enter the support view. 5 At the support prompt, type reset. 6 At the support prompt, type reset soft. The reset restarts the appliances. Network connectivity is unavailable during the restart. For example, the following sequence shows how to specify a soft reset:...> support...support> reset image network soft storagepool...support> reset soft See Resetting or reimaging a configured deduplication appliance on page 80. Performing an image reset An image reset is the most comprehensive reset. The image reset reverts the appliance back to the way the appliance was when it was shipped from the factory. You can perform an image reset if a soft reset does not resolve a suspected corruption in the storage pool configuration. An image reset is more drastic than a soft reset in that it removes and reinstalls the PDLinux operating system information. An image reset performs all the reset actions that a soft reset performs, but it also removes the following objects: Operating system upgrades and patches. An image reset removes all software upgrades and patches from all nodes. The image reset restores the original PDLinux operating system that was originally installed on the nodes when the appliance was shipped from the factory. Deduplication Appliance Software upgrades and patches.

89 Resetting and reimaging a deduplication appliance storage pool Performing an image reset 89 PureDisk upgrades and patches. The existing root login password, storage pool authority password, command-line shell password, and the Configuration Wizard (installer) password. The reset sets these passwords back to their defaults. All topology information. In a multinode storage pool, only the storage pool authority node appears in the topology after the reset finishes. When you perform an image reset, the Deduplication Appliance Software resets all the nodes in the storage pool. You cannot reset a single node in a storage pool. In a multinode storage pool, the reset process starts on one of the nodes that is not enabled as the storage pool authority. The reset performs the reset actions on the storage pool authority node last. As a part of the image reset process, you have the option to reset the admin or root password for the IPMI account. If you reset the password, the password returns to the default Passw0rd. The sixth character is a zero (0). If the image reset fails, then the system performs a soft reset and writes a message to the reset log file in the following location: /root/reset/image_date/log The following factors can cause the system to perform a soft reset instead of an image reset: The system cannot validate the recovery images that its needs to perform the image reset. You upgraded the node from a release level that is earlier than Deduplication Appliance Software 1.4. Symantec supports the image reset only on the appliances that had the Deduplication Appliance Software 1.4 release, or later, installed on the appliance at the factory. The factory reset recreates the factory-shipped software version on that appliance. For example, if an appliance shipped from the factory with Deduplication Appliance Software 1.4.1, when you perform an image reset, the system recreates the Deduplication Appliance Software release on that appliance node. The following procedure explains how to perform an image reset. To perform an image reset 1 Make sure that you prepared this storage pool and/or the NetBackup environment that is connected to this storage pool for the reset. The reset completes more smoothly, and with a minimum of system disruption, if you prepare the system. For information about how to prepare the system, see the following process topic:

90 90 Resetting and reimaging a deduplication appliance storage pool Performing a USB reimage See Resetting or reimaging a configured deduplication appliance on page Connect to the storage pool authority node. Use one of the following methods to connect to the storage pool's storage pool authority node: Use an Ethernet cord to attach a Windows laptop computer to the storage pool authority node. Attach the appliance to an existing KVM switch. 3 Log into the appliance shell menu. Complete the following steps: Use a Secure Shell connection to connect to the storage pool authority node. Type the user name and password for the appliance shell menu. By default, the user name is sysadmin, and the password is P@ssw0rd. The sixth character in the password is a zero (0) character. After the welcome information appears, type q to display the root menu. 4 At the shell prompt, type support to enter the support view. 5 At the support prompt, type reset. 6 At the support prompt, type reset image. The reset restarts the appliances more than once. Network connectivity is unavailable during the restart. For example, the following sequence shows how to specify an image reset:...> support...support> reset image network soft storagepool...support> reset image See Resetting or reimaging a configured deduplication appliance on page 80. Performing a USB reimage When you reimage an appliance with a USB device, the reimage procedure copies the Deduplication Appliance Software that is on the USB device to the

91 Resetting and reimaging a deduplication appliance storage pool Performing a USB reimage 91 deduplication appliance. The reimage procedure removes all information that was configured or stored on the appliance. You received a USB device from Symantec when you received your appliance. The software on the USB device is the original factory configuration. You can use a USB device from one appliance to reimage a different appliance. If the Deduplication Appliance Software release level that is on the USB device is greater than the Deduplication Appliance Software release level that was on the appliance originally, the reimage procedure upgrades the appliance Caution: A USB device reimage deletes all backup data and all metadata on an appliance. Make sure that is your intent before you perform a USB device reimage. A USB reimage differs from the software resets in the following ways: A USB reimage (re)installs the appliance operating system and software packages. This process brings the appliance up to the factory installed software level that is on the USB stick. You can reimage only one appliance at a time. In a multinode storage pool, a reimage is a node-by-node, manual procedure. When you insert the USB device into a single node, the USB device reimages only that node. If you have a multinode storage pool and you want to reimage all the storage pool nodes, the order in which you reimage the nodes does not matter. After you reimage one or more of the appliances, you need to configure the reimaged appliances as storage pool nodes. The following procedure explains how to use a USB device to reimage an appliance. To perform a USB reimage 1 Make sure that you prepared this storage pool and/or the NetBackup environment that is connected to this storage pool for the reset. The reset completes more smoothly, and with a minimum of system disruption, if you prepare the system. For information about how to prepare the system, see the following process topic: See Resetting or reimaging a configured deduplication appliance on page Log off from the appliance and turn off the appliance.

92 92 Resetting and reimaging a deduplication appliance storage pool Performing a USB reimage 3 Log into the appliance through a console. The console can be an IPMI or a direct-attached keyboard, monitor, and mouse. Symantec supports KVM access through the IPMI on NetBackup 5020 deduplication appliances only. Symantec does not support KVM access through the IPMI on NetBackup 5000 deduplication appliances. 4 Insert the USB flash drive into one of the USB ports on the back of the appliance. 5 Turn on the appliance, and monitor the boot process. 6 When the splash screen appears, use the arrow keys to select Install NetBackup Deduplication Appliance Software 1.4.x and press Enter. If the USB splash screen does not appear, then you need to reset the appliance's boot order to ensure that the USB device boots first. The following technical article explains how to reset the boot order: After you change the boot order, begin this procedure again. 7 Monitor the boot process. 8 Remove the USB device after the following message appears: ************************************************************** Unable to continue. A bootable USB device is plugged in. The USB device can interfere with the imaging process. NOTE: The imaging process will not continue until the USB device is removed!!! Please remove the USB device and press any key to continue. ************************************************************** 9 Monitor the messages and make sure that the USB reimage process completes. 10 Reconfigure the appliance. For information about how to reconfigure an appliance, see the Deduplication Appliance Getting Started Guide. See Resetting or reimaging a configured deduplication appliance on page 80.

93 Chapter 5 Disaster recovery This chapter includes the following topics: About deduplication appliance disaster recovery About deduplication appliance disaster recovery methods Disaster recovery without a disaster recovery backup Disaster recovery with a disaster recovery backup About deduplication appliance disaster recovery Disaster recovery backups create a copy of your backup data and store the information in a safe place. In the event of a disaster, you can restore the data from the backup. More information about disaster recovery backups is available. Symantec NetBackup PureDisk Administrator s Guide, Disaster recovery backup procedures About deduplication appliance disaster recovery methods The kind of disaster recovery that is required depends on the state of the information on the /Storage partition. If the /Storage data is not lost, perform a recovery without a disaster recovery backup. If the entire node including the /Storage information is lost, perform a recovery from a disaster recovery backup. Within each of these general categories, different kinds of data can be lost so different recoveries are performed.

94 94 Disaster recovery Disaster recovery without a disaster recovery backup Table 5-1 Recovering from different kinds of disasters Description of the disaster Actions The node is completely broken and needs to be replaced. The /Storage information is located in a different place and is unaffected by the disaster. You need to rebuild the node with a new appliance. More information is available. See Rebuilding a node with a new appliance on page 94. The operating system on the node is broken. The appliance is still functional and the /Storage information is located in a different place and is unaffected by the disaster. The entire node, including the /Storage information is lost. You need to rebuild the node with a new appliance. More information is available. See Rebuilding the operating system on an existing node on page 96. You need to rebuild the entire system and attempt to recover the lost data. More information is available. See Disaster recovery with a disaster recovery backup on page 102. More information about disaster recovery is available. Symantec NetBackup PureDisk Administrator s Guide Disaster recovery without a disaster recovery backup A disaster recovery without a disaster recovery backup assumes the /Storage partition is not lost. In this case, either the physical appliance has failed and must be replaced, or the operating system on the appliance has failed and must be rebuilt. Rebuilding a node with a new appliance 1 Install a new appliance. More information on this topic is available. Symantec NetBackup Deduplication Appliance Software Getting Started Guide, Connecting the deduplication appliance to your network 2 Configure the new appliance with previous network configuration. More information on this topic is available. Symantec NetBackup Deduplication Appliance Software Getting Started Guide, Configuring the storage pool on a deduplication appliance 3 Stop the PureDisk service on the appliance using the following command: /etc/init.d/puredisk stop

95 Disaster recovery Disaster recovery without a disaster recovery backup 95 4 Delete the contents of the /Storage directory using the following command: rm -rf /Storage/* 5 Copy the previous /Storage data from its original location to the new /Storage directory. Alternatively, you can also remount the /Storage data. 6 Restart the appliance. 7 (Conditional) If you are rebuilding a storage pool authority node: Delete the VXAT RPMs from the appliance with the following commands: rpm -e VRTSatServer rpm -e VRTSatClient rm -rf /Storage/var/VRTSat rm -rf /var/vrtsat Reinstall the VXAT RPMs with the following commands: export SPAIP='hostname -f' export INSTALL_PATH=/opt Reinstall VXAT using the following commands: cd /opt/pdconfigure/scripts/installers./install.vrtsat.sh (Conditional) Open a case with Symantec Technical Support if there are indications of corruption in the installation. The RecoverCR tool may be able to assist in resolving corruption. 8 (Conditional) If you are rebuilding a content router node: Connect to the storage pool authority appliance using Secure Shell (ssh). Run the push-ssh-pubkey.exp script on the storage pool authority. This script is located in the /opt/pdappliance/scripts directory. Run the command as shown:./push-ssh-pubkey.exp root@content_router_ip_address password Connect to the content router using Secure Shell (ssh). Run the push-ssh-pubkey.exp script to change the key. Run the command as shown:./push-ssh-pubkey.exp root@spa_ip_address password

96 96 Disaster recovery Disaster recovery without a disaster recovery backup If the operating system on your appliance fails, becomes corrupt, or needs to be rebuilt for some other reason, use this procedure. The listed procedure explains how to create a new virtual disk using the RAID utility. The operating system is then installed on the virtual disk. Please be aware the appliance requires two virtual disks during installation. Rebuilding the operating system on an existing node 1 Confirm the appliance is turned off. 2 Unplug the old data disks that contained the /Storage partition and install and connect two or more new disks. These new disks are used as temporary storage disks. 3 Restart the appliance and configure the new disks using the RAID utility. It is necessary to interrupt the boot process to configure the RAID. Press Ctrl + H when prompted to interrupt the boot process. Use the mouse to enter the RAID utility. Clear the original configuration from RAID utility. The RAID controller detects the old disks and indicates the configuration is broken. Configure two virtual disks. One for the operating system and the other for temporary storage pool. The first virtual disk must be configured for RAID1. 4 Install the operating system using the DVD or the USB. The factory installation places the operating system on the first virtual drive and places /Storage on the second virtual drive. 5 Log into the appliance after the installation is finished and top all services that refer to the /Storage partition. Use the lsof -n grep Storage command to find the processes that reference /Storage. 6 Unmount the /Storage partition. Use the following command: umount /Storage 7 Export the PDDG disk group from the old data disks to import later in the procedure. vxdg deport PDDG

97 Disaster recovery Disaster recovery without a disaster recovery backup 97 8 Use the MegaCli command to list all virtual disks. linux-vj0c:~ # cd /opt/megaraid/megacli #./MegaCli64 -LDInfo -Lall -a0 v214:/opt/megaraid/megacli #./MegaCli64 -LDInfo -Lall -a0 Adapter 0 -- Virtual Drive Information: Virtual Disk: 0 (Target Id: 0) Name: RAID Level: Primary-1, Secondary-0, RAID Level Qualifier-0 Size: GB State: Optimal Stripe Size: 64 KB Number Of Drives:2 Span Depth:1 Default Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU Access Policy: Read/Write Disk Cache Policy: Disabled Encryption Type: None Virtual Disk: 1 (Target Id: 1) Name: RAID Level: Primary-1, Secondary-0, RAID Level Qualifier-0 Size:1.817 TB State: Optimal Stripe Size: 64 KB Number Of Drives:2 Span Depth:1 Default Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU Access Policy: Read/Write Disk Cache Policy: Disabled Encryption Type: None Exit Code: 0x00 9 Delete the second virtual disk and unplug the disks in this virtual disk. /opt/megaraid/megacli #./MegaCli64 -CfgLdDel -L1 -a0

98 98 Disaster recovery Disaster recovery without a disaster recovery backup 10 Unplug all temporary disks and plug in the old data disks (/Storage) in the appliance. 11 Run the following command to scan the configuration: /MegaCli64 -CfgForeign -Scan -a0 Example: v214:/opt/megaraid/megacli #./MegaCli64 -CfgForeign -Scan -a0 There are 1 foreign configuration(s) on controller 0 Exit Code: 0x00 12 Run the command that is shown to import any foreign configurations that are found by the MegaCli64 command. v214:/opt/megaraid/megacli #./MegaCli64 -CfgForeign -Import -a0

99 Disaster recovery Disaster recovery without a disaster recovery backup Verify the disk group and RAID configuration. v214:/opt/megaraid/megacli #./MegaCli64 -ldinfo -Lall -a0 Adapter 0 -- Virtual Drive Information: Virtual Disk: 0 (Target Id: 0) Name: RAID Level: Primary-1, Secondary-0, RAID Level Qualifier-0 Size: GB State: Optimal Stripe Size: 64 KB Number Of Drives:2 Span Depth:1 Default Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU Access Policy: Read/Write Disk Cache Policy: Disabled Encryption Type: None Virtual Disk: 1 (Target Id: 1) Name: RAID Level: Primary-6, Secondary-0, RAID Level Qualifier-3 Size:9.084 TB State: Optimal Stripe Size: 64 KB Number Of Drives:12 Span Depth:1 Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU Access Policy: Read/Write Disk Cache Policy: Disabled Ongoing Progresses: Background Initialization: Completed 0%, Taken 0 min. Encryption Type: None Exit Code: 0x00 14 Import the VX disk group. List all disks with the vxdisk list command.

100 100 Disaster recovery Disaster recovery without a disaster recovery backup v214:~ # vxdisk list DEVICE TYPE DISK GROUP STATUS sda auto:none - - online invalid sdb auto - - error Device sdb is the device that was removed earlier in this procedure. The new virtual disk is not found. Force vx to rescan the disks. Vx should now find sdc in list. v214:~ # vxdctl enable If this command stops responding, press Ctrl + C to terminate the command. Then run the following commands: chkconfig --del pd_fibre_channel chkconfig --del pd_auto_detect chkconfig --del puredisk reboot List all disks with the vxdisk list command v214:~ # vxdisk list DEVICE TYPE DISK GROUP STATUS sda auto:none - - online invalid sdc auto:sliced - - online Import the disk group with the commands shown. v214:~ # vxdisk clearimport sdc v214:~ # vxdg import PDDG v214:~ # echo $? 0 A value of zero (0) returned by the echo $? command indicates success. Check the device node of this virtual disk. v214:~ # ls /dev/vx/dsk/pddg/ Storage Mount the /Storage directory. mount -a /Storage

101 Disaster recovery Disaster recovery without a disaster recovery backup Configure the appliance with the TCP/IP address of the old appliance. Be sure to configure any VLAN and bonding information. 16 Issue the touch command to create the appliance.reconfigured file. touch /etc/appliance.reconfigured 17 Restart the appliance. 18 Confirm the PureDisk service is running correctly with the following command. # /etc/init.d/puredisk status 19 If there are any problems with any services, please correct the problems. 20 (Conditional) If you are rebuilding a storage pool authority: Remove the VXAT RPMs from the system. rpm -e VRTSatServer rpm -e VRTSatClient rm -rf /Storage/var/VRTSat rm -rf /var/vrtsat Reinstall the VXAT RPMs. export SPAIP='hostname -f' export INSTALL_PATH=/opt cd /opt/pdconfigure/scripts/installers Reinstall VXAT../Install.VRTSat.sh 21 (Conditional) If you are rebuilding a content router: Log into the storage pool authority appliance using ssh. Run the push-ssh-pubkey.exp script. The script is on the storage pool authority in the /opt/pdappliance/scripts directory. Issue the command as follows:./push-ssh-pubkey.exp root@cr_ip password For the command, replace password with the password for root and replace CR_IP with the TCP/IP address of the content router.

102 102 Disaster recovery Disaster recovery with a disaster recovery backup Disaster recovery with a disaster recovery backup Disaster recovery with a disaster recovery backup is composed of two processes. The first process is the disaster recovery backup. The second is the disaster recovery restore. The disaster recovery backup is categorized as either a full disaster recovery backup or a metadata only disaster recovery backup. More information about the disaster recovery backup is available. Symantec NetBackup PureDisk Administrator s Guide The type of disaster recovery restore required depends on which part of the environment failed. The individual restore cases are outlined in Table 5-2. Table 5-2 Disaster recovery restore options Part or parts of the environment that failed The storage pool authority in a single node environment fails. All nodes in a multi-node system fail. Required restore type Full restore. This restore uses a full disaster recovery backup. Full restore. This restore uses a full disaster recovery backup. Only the storage pool authority node fails. One or more content routers are still active. Only some of the content router nodes fail. The storage pool authority node is still active and one or more content routers may be active. Metadata only restore. This restore uses a metadata only disaster recovery backup. Metadata only restore. This restore uses a metadata only disaster recovery backup. The storage pool authority node and some of the content router nodes fail. There are, however, still some active content router nodes. Metadata only restore. This restore uses a metadata only disaster recovery backup. To recover an appliance using a disaster recovery backup 1 (Conditional) Reinstall the failed node or failed nodes if you are performing a full disaster recovery. 2 Use either appliance shell menu or administrative Web UI to reconfigure the appliance with the same networking information that was used in the original appliance (TCP/IP, FQDN, DNS, etc.).

103 Disaster recovery Disaster recovery with a disaster recovery backup (Conditional) If you have a multi-node environment, run /opt/pdappliance/scripts/push-ssh-pubkey.exp on storage pool authority node to push the ssh key to all non-storage pool authority nodes. 4 (Conditional) For full disaster recovery restores, run the disaster recovery prepare script (/opt/pdappliance/scripts/prepare_dr_restore_all.sh) on the failed nodes. If there are multiple failed nodes run the prepare_dr_restore_all.sh script on the storage pool authority first. Then run the prepare_dr_restore_all.sh script on all other failed nodes. 5 (Conditional) For metadata only disaster recovery, remount the original /Storage volume. 6 If the /Storage/databases was lost: Confirm the database service is not active. Use the pgrep command to check database service. pgrep postmaster (Conditional) Use the kill command to stop the database service if it is running. # pgrep postmaster # kill Use the /opt/pdappliance/scripts/rebuild_db.sh script to rebuild the LDAP and the PDDB databases on all rebuilt nodes. 7 Perform disaster recovery restore as directed in the PureDisk Remote Office Edition documentation, as per respective environment. (Conditional) Run the DR_Restore_all.sh script if you are doing a full disaster recovery. /opt/pdinstall/dr_restore_all.sh -no-install (Conditional) Run the ChangeIPTables.sh script if you are doing a full disaster recovery. /opt/pdconfigure/scripts/installers/changeiptables.sh (Conditional) Run the DR_Restore-all.sh script with the metadataonly option if you are only performing a metadata disaster recovery.

104 104 Disaster recovery Disaster recovery with a disaster recovery backup /opt/pdinstall/dr_restore-all.sh -no-install -metadataonly 8 (Conditional) For a metadata only restore, run the recovercr utility with the -fix parameter on the storage pool authority node to make the metadata in the database consist. The utility is located in /opt/pdinstall/var/packages/recovercr.tgz. Before using this utility, read the README_FIRST file in the tar ball. tar -C / -xf /opt/pdinstall/var/packages/recovercr.tgz recovercr/readme_first

105 Chapter 6 Configuring virtual local area networks (VLANs) This chapter includes the following topics: About VLANs VLAN example Configuring VLANs and storage zones Verifying VLAN prerequisites Moving a storage pool to a VLAN-compatible trunk port Configuring the node interfaces Creating mapping tables Completing the VLAN configuration About the VLAN configuration pages in the Storage Pool Configuration Wizard Adding clients to the VLANs About configuring VLANs with bonded network interfaces (deduplication appliances only) About PureDisk operations within VLANs About VLANs Symantec enables you to configure multiple virtual local area networks (VLANs) for a storage pool. You can attach clients to the VLANs in a way that segregates the data for each client (or group of clients). The VLAN ensures data separation

106 106 Configuring virtual local area networks (VLANs) VLAN example and security. When you configure VLANs, you assign a set of VLAN FQDNs and VLAN IP addresses to the storage pool authority node. When you attach clients to the storage pool, you can group clients together and assign clients to the appropriate VLAN FQDNs or VLAN IP addresses. Note: This chapter is included in both the Deduplication Appliance Software Administrator's Guide and in the PureDisk Remote Office Edition Administrator's Guide. This chapter includes information for both PureDisk platforms. The following topics contain more information about VLANs: See VLAN example on page 106. See Configuring VLANs and storage zones on page 108. See Verifying VLAN prerequisites on page 109. See Moving a storage pool to a VLAN-compatible trunk port on page 111. See Creating mapping tables on page 128. See Completing the VLAN configuration on page 137. See Adding clients to the VLANs on page 143. See About configuring VLANs with bonded network interfaces (deduplication appliances only) on page 145. See About PureDisk operations within VLANs on page 147. VLAN example The VLAN documentation uses the example in this topic to explain VLAN configuration procedures. Assume that your company has three departments, and you want to create a storage pool with three VLANs. You can attach each client to its own departmental VLAN. That is, you can attach the accounting department clients to the first VLAN. You can attach marketing department clients to the second VLAN. You can attach art department clients to the third VLAN. In Figure 6-1, the solid line indicates VLAN 19. The dashed line indicates VLAN 20. The dashed and dotted line indicates VLAN 21. Each storage pool node has a VLAN connection to the switch for each VLAN. Each client is attached to the switch through its own unique VLAN.

107 Configuring virtual local area networks (VLANs) VLAN example 107 Figure 6-1 VLANs for example storage pool spa.acme.com SPA Node CR1 CR2 VLAN20 VLAN19 VLAN21 Client Client Client Table 6-1 shows the IP addresses and FQDNs that are used for the VLANs in example storage pool spa.acme.com.

108 108 Configuring virtual local area networks (VLANs) Configuring VLANs and storage zones Table 6-1 IP addresses and FQDNs for storage pool acme.com VLANs Storage pool authority node Public IP = Public FQDN = spa.acme.com For VLAN 19: IP = FQDN = spavl19.acme.com Netmask = For VLAN 20: IP = FQDN = spavl20.acme.com Netmask = For VLAN 21: IP = FQDN = spavl21.acme.com Netmask = Content router 1 Public IP = Public FQDN = cr1.acme.com For VLAN19: IP = FQDN = cr1vl19.acme.com Netmask = For VLAN20: IP = FQDN = cr1vl20.acme.com Netmask = For VLAN21: IP = FQDN = cr1vl21.acme.com Netmask = Content router 2 Public IP = Public FQDN = cr2.acme.com For VLAN19: IP = FQDN = cr2vl19.acme.com Netmask = For VLAN20: IP = FQDN = cr2vl20.acme.com Netmask = For VLAN21: IP = FQDN = cr2vl21.acme.com Netmask = The example storage pool does not include any bonded interfaces. If your storage pool contains bonded interfaces, refer to the bonds rather than to the physical interfaces when you configure the storage pool's VLANs. For more information about configuring VLANs with bonded interfaces, see the following topic: See About configuring VLANs with bonded network interfaces (deduplication appliances only) on page 145. Configuring VLANs and storage zones The following procedure explains how to configure VLANs and storage zones. To configure VLANs and storage zones 1 Verify VLAN prerequisites. See Verifying VLAN prerequisites on page Move the storage pool to a trunk port that is compatible with VLANs. See Moving a storage pool to a VLAN-compatible trunk port on page 111.

109 Configuring virtual local area networks (VLANs) Verifying VLAN prerequisites Configure the node interfaces. On a deduplication appliance, use the appliance shell menu. On a PureDisk ROE storage pool, use PDLinux commands. See Configuring the node interfaces on page Create mapping tables. Each storage pool node requires a mapping table that explains the VLAN interfaces. In this step, you use either the appliance shell menu, PDLinux commands, or the Configuration Wizard to create a mapping table for each node. See Creating mapping tables on page Complete the VLAN configuration. See Completing the VLAN configuration on page Attach clients to the VLANs. See Adding clients to the VLANs on page 143. Verifying VLAN prerequisites The following procedure explains how to verify your environment before you begin the VLAN configuration process. To verify VLAN prerequisites 1 Obtain IP addresses, netmasks, fully qualified domain names (FQDNs), and VLAN identifiers from your network administrator. Obtain an IP address, a netmask, and an FQDN for each physical interface and each virtual interface in each node of the storage pool. Make sure to obtain this information for each physical interface and for each virtual interface. For example, the following topic explains the IP addresses and FQDNs that are used for the VLANs in example storage pool spa.acme.com: See VLAN example on page 106. Obtain a VLAN identifier for each VLAN. The ID number must be an integer in the range 1 ID_number For example, the following are acceptable VLAN IDs: 1, 26, 100. In example storage pool spa.acme.com, the VLAN identifiers and names are as follows: VLAN 19 is spavl19.acme.com

110 110 Configuring virtual local area networks (VLANs) Verifying VLAN prerequisites VLAN 20 is spavl20.acme.com VLAN 21 is spavl21.acme.com 2 Verify that the storage pool is configured correctly on your switch. The storage pool nodes must be attached to a port on the switch that is configured with trunk mode. If the storage pool is based on deduplication appliances, the switch must use trunking protocol IEEE 802.1q. If you have a production storage pool that is not on a trunk port, make plans to move the nodes to a trunk port. The VLAN configuration instructions explain how to prepare a storage pool for this move, but consult your switch documentation for switch-specific information. Make sure that all the VLAN IDs, physical interfaces, and bonded interfaces that you want to use are configured in the switch. The physical interface names are typically eth0, eth1, and so on. The bonded interfaces names are typically bond0, bond1, and so on. If you use bonded interfaces, make sure that all bonded interfaces are connected to the same switch through trunk port. Also make sure that the switch and the VLAN use the bond name (for example, bond0) instead of the physical interface name. 3 (Recommended) Verify that all storage pool nodes and all storage pool clients are attached to a DNS. Symantec recommends that you use a DNS if you implement the VLAN feature. The alternative is to edit the /etc/hosts file on all computers to include the correct addressing information. The Symantec documentation assumes that the environment includes a DNS. On a deduplication appliance, if you decide to use an /etc/hosts file rather than a DNS, you might have to update the /etc/hosts file several times during the configuration process. If you build a mapping file after you update the /etc/hosts file, make sure to run the following additional appliance shell menu system command from the vzone menu: config resolve fix. 4 Verify that the storage pool is configured correctly. The storage pool needs to be functioning correctly before you configure the VLANs. If the storage pool is new, run a few test backups and a few test restores to make sure that the storage pool is operating as expected. 5 Obtain the network mask for each IP address and FQDN from your network administrator.

111 Configuring virtual local area networks (VLANs) Moving a storage pool to a VLAN-compatible trunk port Configure the VLAN IP addresses and FQDNs in your DNS. If you do not have a DNS, configure the address information in the /etc/hosts file on each node in the storage pool. Later, when you attach clients to the storage pool, make sure to update the /etc/hosts file on the storage pool nodes and on the clients. If this storage pool is configured as a PureDisk deduplication option (PDDO) storage pool, make sure that the /etc/hosts files on the NetBackup media servers in your environment are configured with the VLAN addresses. 7 Proceed to the following: See Moving a storage pool to a VLAN-compatible trunk port on page 111. Moving a storage pool to a VLAN-compatible trunk port The following procedures explain how to move a storage pool to a VLAN-compatible trunk port: See Moving a deduplication appliance storage pool to a trunk port on page 111. See Moving a PureDisk ROE storage pool to a trunk port on page 114. Moving a deduplication appliance storage pool to a trunk port The following procedure explains how to move a deduplication appliance storage pool to a trunk port. To move a deduplication appliance storage pool to a trunk port 1 (Conditional) Change the state of the disk pool to DOWN. Perform this step if the storage pool is connected to a NetBackup media server as part of a PureDisk deduplication option (PDDO) deployment. You do not need to perform this step if the storage pool is not connected to a media server. Complete the following steps: Log into the NetBackup media server. Use the nbdevconfig command to remove the media server from the disk pool. On Linux and UNIX systems, type the following command: /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp disk_pool_name -state DOWN

112 112 Configuring virtual local area networks (VLANs) Moving a storage pool to a VLAN-compatible trunk port On Windows systems, type the following command: install_path\netbackup\bin\admincmd\nbdevconfig -changestate -stype PureDisk -dp disk_pool_name -state DOWN For disk_pool_name, specify the name of the disk pool. 2 Log in to the PureDisk administrative Web UI and make sure that no PureDisk jobs are currently running or are scheduled to be run. Perform the following steps: Select Monitor > Jobs. In the right pane, select the jobs you want to terminate. Select Stop job gracefully or Stop job immediately. You might lose data if you select Stop job immediately. Confirm the termination in the pop-up window that appears. For more information about how to stop jobs, see "Terminating a job that is running" in the PureDisk Backup Operator Guide, or see the online help. 3 Log out from the PureDisk administrative Web UI. 4 Start an appliance shell menu session on the storage pool authority node. Perform the following steps: Connect to the storage pool authority node through a Secure Shell (SSH) connection. For example, you can use PuTTY, which is available as a free download. Type the user name and password for the appliance shell menu. By default the user name is sysadmin and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). After the welcome information appears, press q to display the root mode menu. 5 Type PureDisk at the appliance shell menu prompt and press Enter. 6 Type stop all and press Enter. This command stops all services. 7 Turn off all the appliance nodes. 8 Configure the switch's ports for trunk mode. Use your switch's documentation to complete this step.

113 Configuring virtual local area networks (VLANs) Moving a storage pool to a VLAN-compatible trunk port Connect all the interfaces in all the nodes to the trunk port. Use your switch's documentation to complete this step. 10 Power-on all nodes. 11 Start an appliance shell menu session on the storage pool authority node. See Step 4 for information. 12 Type network at the appliance shell menu prompt and press Enter. 13 Type a series of ping commands to test the connectivity between the addresses in the storage pool. The ping command has the following format: ping host nodeip For host, type the IP address or FQDN of the target. This address is the address you want to reach. This address is the address that receives the ping. For nodeip, type the IP address or FQDN of the source. This address is the address that sends the ping. This step requires that you issue a ping command from each address to itself and from each address to each other address. For example storage pool spa.acme.com, SSH into as sysadmin and issue ping commands as follows: ping cr1.acme.com ping cr1vl19.acme.com ping cr1vl20.acme.com ping cr1vl21.acme.com ping cr2.acme.com ping cr2vl19.acme.com ping cr2vl20.acme.com ping cr2vl21.acme.com Type the following commands to log out of the appliance shell menu: exit

114 114 Configuring virtual local area networks (VLANs) Moving a storage pool to a VLAN-compatible trunk port logout 15 Proceed to the following: See Configuring the node interfaces on page 116. Moving a PureDisk ROE storage pool to a trunk port The following procedure explains how to move a PureDisk ROE storage pool to a trunk port. To move a PureDisk ROE storage pool to a trunk port 1 (Conditional) Change the state of the disk pool to DOWN. Perform this step if the storage pool is connected to a NetBackup media server as part of a PureDisk deduplication option (PDDO) deployment. You do not need to perform this step if the storage pool is not connected to a media server. Complete the following steps: Log into the NetBackup media server. Use the nbdevconfig command to remove the media server from the disk pool. On Linux and UNIX systems, type the following command: /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp disk_pool_name -state DOWN On Windows systems, type the following command: install_path\netbackup\bin\admincmd\nbdevconfig -changestate -stype PureDisk -dp disk_pool_name -state DOWN For disk_pool_name, specify the name of the disk pool. 2 Log in to the PureDisk administrative Web UI and make sure that no PureDisk jobs are currently running or are scheduled to be run. Perform the following steps: Select Monitor > Jobs. In the right pane, select the jobs you want to terminate. Select Stop job gracefully or Stop job immediately. You might lose data if you select Stop job immediately. Confirm the termination in the pop-up window that appears.

115 Configuring virtual local area networks (VLANs) Moving a storage pool to a VLAN-compatible trunk port 115 For more information about how to stop jobs, see "Terminating a job that is running" in the PureDisk Backup Operator Guide, or see the online Help. 3 Log out from the PureDisk administrative Web UI. 4 Use a Secure Shell (SSH) agent to connect to the storage pool authority node. For example, you can use the PuTTY, which is available as a free download. 5 Log into the storage pool authority node as root. 6 Type the following command to stop all PureDisk services: # /etc/init.d/puredisk stop 7 Power-off each node. Complete the following steps: Log into each node as root. Type the following command to power-off the node: # shutdown -h now Note: Make sure to log into each node and type the shutdown -h now command on each node. 8 Configure the switch's ports for trunk mode. Use your switch's documentation to complete this step. 9 Connect all the interfaces in all the nodes to the trunk port. Use your switch's documentation to complete this step. 10 Power-on all nodes. 11 Type a series of ping commands to test the connectivity between the addresses you defined in the storage pool. This step requires that you log in as root to each node in the storage pool and issue a ping command from each address to itself. Also issue a ping command from each address to each other address. Use the ping command in the following format: # ping -c1 host

116 116 Configuring virtual local area networks (VLANs) Configuring the node interfaces For host, type the target IP address or the target FQDN to receive the ping. This address is the address you want to reach. This address is the address that receives the ping. For example storage pool spa.acme.com, you can start by logging into as root and issuing ping commands as follows: ping -c1 cr1.acme.com ping -c1 cr1vl19.acme.com ping -c1 cr1vl20.acme.com ping -c1 cr1vl21.acme.com ping -c1 cr2.acme.com ping -c1 cr2vl19.acme.com ping -c1 cr2vl20.acme.com ping -c1 cr2vl21.acme.com 12 Proceed to the following: See Configuring the node interfaces on page 116. Configuring the node interfaces The following procedures explain how to configure the node interfaces: See Configuring the node interfaces on a deduplication appliance storage pool on page 116. See Configuring the node interfaces on a PureDisk ROE storage pool on page 119. Configuring the node interfaces on a deduplication appliance storage pool The following procedure explains how to configure the node interfaces on a deduplication appliance storage pool. To configure the node interfaces 1 Start an appliance shell menu session on the storage pool authority node. Perform the following steps: Connect to the storage pool authority node through a Secure Shell (SSH) connection.

117 Configuring virtual local area networks (VLANs) Configuring the node interfaces 117 For example, you can use PuTTY, which is available as a free download. Type the user name and password for the appliance shell menu. By default the user name is sysadmin and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). After the welcome information appears, press q to display the root mode menu. 2 Type network at the appliance shell menu prompt and press Enter. 3 Type vlan add commands to define the VLANs for this storage pool. The format for the vlan add command is as follows: network> vlan add nodeip vlan_id ethnum For nodeip, specify the public IP address of a node that you want to include in a VLAN. For vlan_id, specify the VLAN identification number that is specified on the switch. For num, specify the interface number of the interface that you want to use for this VLAN. You can use the same network interface for all the VLANs. For example, plan to specify eth1 for all the VLANs in all the nodes. The vlan add command specifies the NIC interface within a node that you want to use for a VLAN. Type one vlan add command for each VLAN and for each node. The number of vlan add commands you need to type is (the number of VLANs) X (the number of nodes in the storage pool). In the example storage pool in the following topic, there are three nodes, and you want to configure three VLANs: See VLAN example on page 106. The following are the nine commands that define the VLANs and NICs for the example storage pool: Define VLANs and NICs on the storage pool authority node: network> vlan add eth1 network> vlan add eth1 network> vlan add eth1 Define VLANs and NICs on content router 1: network> vlan add eth1 network> vlan add eth1

118 118 Configuring virtual local area networks (VLANs) Configuring the node interfaces network> vlan add eth1 Define VLANs and NICs on content router 2: network> vlan add eth1 network> vlan add eth1 network> vlan add eth1 Alternatively, if you want to configure the VLANs on bonded interfaces, type the vlan add command in the following format: network> vlan add public_ip vlan_id bondnum For num, specify the bond number. 4 (Optional) Type the vlan show command to check your work. The vlan show command displays the following information: Node IP VLAN NIC NIC IP Address Netmask vlan19 eth1 N/A N/A vlan20 eth1 N/A N/A vlan21 eth1 N/A N/A vlan19 eth1 N/A N/A vlan20 eth1 N/A N/A vlan21 eth1 N/A N/A vlan19 eth1 N/A N/A vlan20 eth1 N/A N/A vlan21 eth1 N/A N/A 5 Type config addr commands to specify IP addresses for the VLAN NICs. The format for the config addr command is as follows: network> config addr nodeip vlanvlan_id vlan_ip netmask For nodeip, specify the public IP address of a node in this storage pool that you want to include in a VLAN. For vlan_id, specify the identification number for this VLAN that is configured on the switch. For vlan_ip, specify the IP address that you want to assign to the VLAN NIC on the node. For netmask, specify the network mask for the vlan_ip. For example, the following commands define the IP addresses and netmasks for the NICs in the example storage pool:

119 Configuring virtual local area networks (VLANs) Configuring the node interfaces 119 Define IP addresses and netmasks for the NICs on the storage pool authority node: network> config addr vlan network> config addr vlan network> config addr vlan Define IP addresses and netmasks for the NICs on the content router 1: network> config addr vlan network> config addr vlan network> config addr vlan Define IP addresses and netmasks for the NICs on the content router 2: network> config addr vlan network> config addr vlan network> config addr vlan Type exit to leave network mode. 7 Type logout to leave the appliance shell menu. 8 Ensure that the interfaces boot. The boot process can take up to one minute to complete. 9 Proceed to the following: See Creating mapping tables on page 128. Configuring the node interfaces on a PureDisk ROE storage pool The following procedure explains how to configure the node interfaces on a PureDisk ROE storage pool. To configure the node interfaces on a PureDisk ROE storage pool 1 Connect to the storage pool authority appliance node through a secure shell (SSH) connection. 2 Log into the storage pool authority node as root. 3 Type the following command to change to the network commands directory. # cd /etc/sysconfig/network 4 Identify the interface upon which you want to configure the VLAN. You can use the same network interface for all of the VLANs. For example, you can specify eth1 for all the VLANs on all the nodes.

120 120 Configuring virtual local area networks (VLANs) Configuring the node interfaces 5 Create VLAN interface files for each VLAN that you want to configure. For example, to create VLAN19, VLAN20, and VLAN21, type the following commands: # touch ifcfg-vlan19 # touch ifcfg-vlan20 # touch ifcfg-vlan21 If you have a bonded interface, create a file that is named in the following style: # touch ifcfg-bond0 # ls -l -rw-r--r-- 1 root root -rw-r--r-- 1 root root -rw-r--r-- 1 root root 6 Determine the name of each interface's configuration file. This step shows how to use network commands to determine the physical interfaces in this node and to determine where the configuration files for these interfaces reside. To determine the interface configuration file names, use the network commands as follows: Type ls -l to list the network interfaces and the names of the configuration files for each interface. For example: :47 ifcfg-eth-id-00:50:56:98:00:24 # Line A :47 ifcfg-eth-id-00:50:56:98:00:25 # Line B :31 ifcfg-lo -rw-r--r-- 1 root root :31 ifcfg.template -rw-r--r-- 1 root root :42 ifcfg-bond0 # Line C -rw-r--r-- 1 root root :02 ifcfg-vlan19 # Line D -rw-r--r-- 1 root root :02 ifcfg-vlan20 # Line E -rw-r--r-- 1 root root :02 ifcfg-vlan21 # Line F The preceding output shows the configuration file names for each physical interface in the node. The following are notes regarding this output: Line A and Line B describe the configuration files for two different physical interfaces. Files ifcfg-eth-id-00:50:56:98:00:24 and ifcfg-eth-id-00:50:56:98:00:25 are the configuration files for two physical interfaces in this node. Line C describes the configuration file for the bonded interfaces

121 Configuring virtual local area networks (VLANs) Configuring the node interfaces 121 # ifconfig -a Lines D, E, and F describe the configuration files for the VLANs Type ifconfig -a to list the interfaces and the system data for each interface. For example: eth0 Link encap:ethernet HWaddr 00:50:56:98:00:24 inet addr: Bcast: Mask: inet6 addr: fe80::250:56ff:fe98:24/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets:52622 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes: (435.8 Mb) TX bytes: (2.4 Mb) eth1 Link encap:ethernet HWaddr 00:50:56:98:00:25 inet addr: Bcast: Mask: inet6 addr: fe80::250:56ff:fe98:25/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets:93910 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes: (439.7 Mb) TX bytes: (21.7 Mb) eth2 Link encap:ethernet HWaddr 00:50:56:98:00:26 inet6 addr: fe80::250:56ff:fe98:26/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes: (75.9 Mb) TX bytes: (262.6 Mb) eth3 Link encap:ethernet HWaddr 00:50:56:98:00:27 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:local Loopback inet addr: Mask: inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0

122 122 Configuring virtual local area networks (VLANs) Configuring the node interfaces TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: ( Mb) TX bytes: ( Mb) sit0 Link encap:ipv6-in-ipv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) bond0 Link encap:ethernet HWaddr 00:50:56:98:00:26 inet addr: Bcast: Mask: inet6 addr: fe80::250:56ff:fe98:26/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (66.3 Mb) TX bytes: (244.3 Mb) vlan19 Link encap:ethernet HWaddr 00:50:56:98:00:26 inet addr: Bcast: Mask: inet6 addr: fe80::250:56ff:fe98:26/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10529 errors:0 dropped:0 overruns:0 frame:0 TX packets:64731 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (745.0 Kb) TX bytes: (4.4 Mb) vlan20 Link encap:ethernet HWaddr 00:50:56:98:00:26 inet addr: Bcast: Mask: inet6 addr: fe80::250:56ff:fe98:26/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10529 errors:0 dropped:0 overruns:0 frame:0 TX packets:64731 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (745.0 Kb) TX bytes: (4.4 Mb) vlan21 Link encap:ethernet HWaddr 00:50:56:98:00:26 inet addr: Bcast: Mask: inet6 addr: fe80::250:56ff:fe98:26/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10529 errors:0 dropped:0 overruns:0 frame:0

123 Configuring virtual local area networks (VLANs) Configuring the node interfaces 123 TX packets:64923 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (745.0 Kb) TX bytes: (4.5 Mb) The ifconfig -a output lists system information for each interface. The left column lists the interface names. The right column lists the system information. For each interface name, the first line of information in the right column includes a string that starts with HWaddr. Notice that eth0 has HWaddr 00:50:56:98:00:24, and eth1 has HWaddr 00:50:56:98:00:25. Match these HWaddr identifiers to the output from the ls -l command to determine the configuration file names for eth0 and eth1. The files are as follows: The configuration file for eth0 is ifcfg-eth-id-00:50:56:98:00:24 The configuration file for eth1 is ifcfg-eth-id-00:50:56:98:00:25

124 124 Configuring virtual local area networks (VLANs) Configuring the node interfaces 7 Edit each interface configuration file to include the new IP address after the IPADDR= keyword. For example, before the edit, the content of ifcfg-eth-id-00:50:56:98:00:24 is as follows: BOOTPROTO='static' DEVICE='eth0' ETHTOOL_OPTIONS='' IPADDR=' ' MTU='' NETMASK=' ' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' You need to replace with After the edit, the content of ifcfg-eth-id-00:50:56:98:00:24 is as follows: BOOTPROTO='static' DEVICE='eth0' ETHTOOL_OPTIONS='' IPADDR=' ' MTU='' NETMASK=' ' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' 8 Use vi(1) or another editor to add the following lines to each VLAN interface file: STARTMODE='auto' ETHERDEVICE='if_typenum IPADDR='ip_addr' NETMASK='netmask' For if_type, specify either eth or bond. For num, specify the eth number or the bond number. Specify the same ETHERDEVICE line in each VLAN interface file. If the interfaces are bonded,

125 Configuring virtual local area networks (VLANs) Configuring the node interfaces 125 type ETHERDEVICE="bond0". If the interfaces are not bonded, type "ETHERDEVICE=eth2". For ip_addr, specify the virtual IP address of the Example 1. Assume that the network uses only physical interfaces, not bonded interfaces. Edit the VLAN interface files and add the following lines to each file: Edit ifcfg-vlan19 to contain the following lines: STARTMODE='auto' ETHERDEVICE='eth1' IPADDR=' NETMASK=' ' Edit ifcfg-vlan20 to contain the following lines: STARTMODE='auto' ETHERDEVICE='eth1' IPADDR=' NETMASK=' ' Edit ifcfg-vlan21 to contains the following lines: STARTMODE='auto' ETHERDEVICE='eth1' IPADDR=' NETMASK=' ' Example 2. If you had bonded interfaces in the storage pool nodes, the editing is as follows: Edit ifcfg-vlan19 to contain the following lines: STARTMODE='auto' ETHERDEVICE='bond0' IPADDR=' NETMASK=' ' Edit ifcfg-vlan20 to contain the following lines: STARTMODE='auto' ETHERDEVICE='bond0' IPADDR=' NETMASK=' '

126 126 Configuring virtual local area networks (VLANs) Configuring the node interfaces Edit ifcfg-vlan21 to contain the following lines: STARTMODE='auto' ETHERDEVICE='bond0' IPADDR=' NETMASK=' ' 9 (Conditional) Use a text editor to create the bond configuration file for the bonded interfaces. Perform this step if any of the interfaces are bonded. The bond configuration file specifies the physical interfaces that you bonded together. Example 1. The following is an example bond configuration file. In this file, bond0 contains two physical interfaces: eth2 and eth3. # vi ifcfg-bond0 BONDING_MASTER='yes' BONDING_MODULE_OPTS='mode=balance-alb miimon=100' BONDING_SLAVE_0='eth2' BONDING_SLAVE_1='eth3' BOOTPROTO='static' DEVICE='bond0' ETHTOOL_OPTIONS='' MTU='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' The following notes pertain to bond configuration files: If interfaces are bonded, most storage pools need only one bond configuration file. The maximum number of bond interfaces cannot exceed the number of physical interfaces. Include only one DEVICE= line per bond configuration file. This line needs to specify one of the bonded interfaces listed in the ifconfig command. Example 2. The following are additional bond configuration files. spa:/etc/sysconfig/network # cat ifcfg-bond0 STARTMODE='onboot' BOOTPROTO='static' IPADDR=' ' NETMASK=' ' BONDING_MASTER='yes'

127 Configuring virtual local area networks (VLANs) Configuring the node interfaces 127 BONDING_MODULE_OPTS='mode=6 miimon=100 use_carrier=0' BONDING_SLAVE_0='eth3' BONDING_SLAVE_1='eth4' spa:/etc/sysconfig/network # cat ifcfg-bond1 STARTMODE='onboot' BOOTPROTO='static' IPADDR=' ' NETMASK=' ' BONDING_MASTER='yes' BONDING_MODULE_OPTS='mode=6 miimon=100 use_carrier=0' BONDING_SLAVE_0='eth5' BONDING_SLAVE_1='eth6' 10 Type the following command to restart the network: # /etc/init.d/network restart Wait while the system registers the new configuration on the switch. 11 For each VLAN you configured, type the following command to ensure that the new VLAN interface is registered on the switch: # ifconfig vlannum For num, specify the VLAN number. For example, type the following commands to verify the VLAN examples in this procedure: # ifconfig vlan19 # ifconfig vlan20 # ifconfig vlan21

128 128 Configuring virtual local area networks (VLANs) Creating mapping tables 12 Log in as root to each node within the VLAN and type ping(8) commands to verify that each node in VLAN you configured is reachable from all the other nodes in the VLAN. For example, from the storage pool authority node, type the following commands: # ping # ping # ping Proceed to the following: See Creating mapping tables on page 128. Creating mapping tables The following procedures explain how to create the internal mapping tables that the VLANs require. Each node needs a mapping table to facilitate VLAN functioning. Perform one of the following procedures to configure VLANs on a deduplication appliance: See Creating mapping tables on a deduplication appliance storage pool (appliance shell menu method) on page 128. See Creating mapping tables (Configuration Wizard method) on page 135. Perform one of the following procedures to configure VLANs on a PureDisk ROE storage pool: See Creating mapping tables on a PureDisk ROE storage pool (command method) on page 132. See Creating mapping tables (Configuration Wizard method) on page 135. Creating mapping tables on a deduplication appliance storage pool (appliance shell menu method) The following procedure explains how to use the appliance shell menu to configure the node interfaces on a deduplication appliance storage pool.

129 Configuring virtual local area networks (VLANs) Creating mapping tables 129 To create mapping tables 1 Start an appliance shell menu session on the storage pool authority node. For information about how to start an appliance shell menu session, see the following topic: See Moving a deduplication appliance storage pool to a trunk port on page Type vzone to enter vzone mode. 3 Type the collect command to create a VLAN mapping table. For example: spa.vzone> collect [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: linux-9872.site, Zone: VLAN_ [WARNING] Node: spa.acme.com, IP: , is assigned by DHCP server. The mapping table does not support dynamic IP addresses [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: spavl19.acme.com, Zone: VLAN_ [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: spavl20.acme.com, Zone: VLAN_ [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: spavl21.acme.com, Zone: VLAN_ [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: spa.acme.com, Zone: VLAN_ [INFO] Node: cr1.acme.com, clear automatic mapping records for recollect [WARNING] Node: cr1.acme.com, IP: , already exists in mapping table [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN: cr1vl19.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN: cr1vl20.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN: cr1vl21.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN: cr1.acme.net, Zone: VLAN_

130 130 Configuring virtual local area networks (VLANs) Creating mapping tables [INFO] Node: cr2.acme.com, clear automatic mapping records for recollect [WARNING] Node: cr2.acme.com, IP: , already exists in mapping table [INFO] Added mapping, Node: cr2.acme.com, IP address: , FQDN: cr2vl19.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr2.acme.com, IP address: , FQDN: cr2vl20.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr2.acme.com, IP address: , FQDN: cr2vl21.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr2.acme.com, IP address: , FQDN: cr2.acme.net, Zone: VLAN_ Note that the preceding output has been wrapped for inclusion in this documentation. If the collect output is not as expected, wait a few minutes and type the command again. Network speeds and other factors can affect the time required to configure the IP addresses and netmasks. The messages in this output are as follows: INFO messages do not require any user response. WARNING messages indicate an error that does not affect functionality but should be examined. The system issues a warning message for the following types of errors: An interface is assigned with a DHCP server. PureDisk cannot use addresses that a DHCP server issues. PureDisk requires static IP addresses. An address is detected on more than one node. When the same IP address appears more than one time in a configuration, the collect command issues a warning message. If you type the collect command repeatedly, the system issues additional WARNING messages. You can ignore the additional WARNING messages.

131 Configuring virtual local area networks (VLANs) Creating mapping tables (Conditional) Make sure that all FQDNs can be queried to IPs and that all IPs can be reverse queried to FQDNs from the DNS server. Perform this step if your DNS server is not configured for reverse DNS resolution. Use the config edit command to add the lookup information. For each address that cannot be reverse queried, type one config edit command. The config edit command has the following format: config edit address_type public_node_fqdn vlan_topology_name fqdn For address_type, specify ip or fqdn. Specify ip if you need to update an IP address. Specify fqdn if you need to specify an FQDN. For node, specify the public IP address or FQDN of the node. For vlan_topology_name, specify the VLAN topology to which this node belongs. A node can be included in more than one VLAN. If necessary, type a config show command to display the VLAN topology name. For new_address, specify the new FQDN or the new IP address. This address is the address that you want to fix. Specify this command only for addresses that cannot be reverse queried. For example, type the following commands for the example storage pool: spa.vzone> config edit fqdn spa.acme.com VLAN_ spavl19.acme.com spa.vzone> config edit fqdn cr1.acme.com VLAN_ cr1vl19.acme.com spa.vzone> config edit fqdn cr2.acme.com VLAN_ cr2vl19.acme.com

132 132 Configuring virtual local area networks (VLANs) Creating mapping tables spa.vzone> link check 5 (Optional) Type the following command to verify the VLAN interface connections between the nodes in the storage pool. Note the OK in the right-most field of the following example output: Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr2.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr2.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr2.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr2.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] 6 Proceed to the following: See Completing the VLAN configuration on page 137. Creating mapping tables on a PureDisk ROE storage pool (command method) The following procedure explains how to use commands to create mapping tables for the storage pool. You can use this method on a PureDisk ROE storage pool. To create mapping tables 1 Log into the storage pool authority node as root. 2 Type the following command to change to the script directory: # cd /opt/pdconfigure/scripts/support/vlan

133 Configuring virtual local area networks (VLANs) Creating mapping tables Type the following command to build the mapping tables: #./vzone_collect.pl --update The output of this command is as follows for the example storage pool: [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: linux-9872.site, Zone: VLAN_ [WARNING] Node: spa.acme.com, IP: , is assigned by DHCP server. The mapping table does not support dynamic IP addresses [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: spavl19.acme.com, Zone: VLAN_ [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: spavl20.acme.com, Zone: VLAN_ [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN: spavl21.acme.com, Zone: VLAN_ [INFO] Added virtual zone: VLAN_ [INFO] Added mapping, Node: spa.acme.com, IP address: , FQDN:, Zone: VLAN_ [INFO] Node: cr1.acme.com, clear automatic mapping records for recollect [WARNING] Node: cr1.acme.com, IP: , already exists in mapping table [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN: cr1vl19.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN: cr1vl20.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN: cr1vl21.acme.com, Zone: VLAN_ [INFO] Added mapping, Node: cr1.acme.com, IP address: , FQDN:, Zone: VLAN_ The preceding output has been wrapped for inclusion in this documentation.

134 134 Configuring virtual local area networks (VLANs) Creating mapping tables 4 Type the following command to check the FQDNs: #./vzone_check.pl --fqdn-check The output of this command is as follows for the example storage pool: Zone: VLAN_ , Node: spa.acme.com, IP: , FQDN: linux-9872.site [OK] Zone: VLAN_ , Node: spa.acme.com, IP: , FQDN: spavl19.acme.com [OK] Zone: VLAN_ , Node: spa.acme.com, IP: , FQDN: spavl20.acme.com [OK] Zone: VLAN_ , Node: spa.acme.com, IP: , FQDN: spavl21.acme.com [OK] Zone: VLAN_ , Node: spa.acme.com, IP: , FQDN: [Failed. FQDN not configured] Zone: VLAN_ , Node: cr1.acme.com, IP: , FQDN: cr1vl19.acme.com [OK] Zone: VLAN_ , Node: cr1.acme.com, IP: , FQDN: cr1vl20.acme.com [OK] Zone: VLAN_ , Node: cr1.acme.com, IP: , FQDN: cr1vl21.acme.com [OK] Zone: VLAN_ , Node: cr1.acme.com, IP: , FQDN: [Failed. FQDN not configured] The preceding output has been wrapped for inclusion in this documentation. 5 (Conditional) Fix FQDNs that cannot be reverse queried from the DNS server. Perform this step if the output from the FQDN check command (in step 4) contained failure messages. To enable reverse queries in the example storage pool, type the following commands: #./vzone_mapping_conf.pl --update --node spa.acme.com --zone VLAN_ fqdn spa.acme.com #./vzone_mapping_conf.pl --update --node cr1.acme.com --zone VLAN_ fqdn cr1.acme.com The preceding commands have been wrapped for inclusion in this documentation.

135 Configuring virtual local area networks (VLANs) Creating mapping tables Type the following command to check the connectivity between the nodes in the storage pool:./vzone_check.pl --link-check The following output is for the example storage pool, and it shows that reverse queries are now enabled: Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: spa.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] Zone: VLAN_ , Node: cr1.acme.com, IP: [checking. OK] 7 Proceed to the following: See Completing the VLAN configuration on page 137. Creating mapping tables (Configuration Wizard method) The following procedure explains how to use the Configuration Wizard to create mapping tables for the storage pool. You can use this method on a deduplication appliance storage pool or on a PureDisk ROE storage pool. To create mapping tables 1 Type the following command into a browser to start the Configuration Wizard : For address, specify the public FQDN of the storage pool authority node. For example, specify 2 (Conditional) Affirm the security exception for the installer. Depending on your site's security practices, you might see a browser security certificate affirmation page when you start the installer. 3 On the log on page, in the User name field, type root. 4 In the Password field, type the password. By default, the password is P@ssw0rd. In the default password, the sixth character is the numeral zero (0).

136 136 Configuring virtual local area networks (VLANs) Creating mapping tables 5 Click Log on. 6 In the right pane, click Configure VLAN Topology. 7 On the VLAN Configuration - Message from webpage page, click OK or Cancel on the Message from webpage popup that appears. These selections are as follows: Click OK to create a mapping table. The system creates a VLAN mapping table for each node. The display changes to the VLAN Configuration - Discover configuration progress page. When the configuration progress is complete, click OK to advance to the VLAN Configuration - Node List page. Click Cancel to advance to the VLAN Configuration - Node List page. For example, you can click Cancel if the mapping tables for each node exist in the system and you want to edit VLAN information. 8 On the VLAN Configuration - Node List page, verify the node statuses. If all the status messages in the Subnet Mapping Status column display Configured for all the nodes that you want to include in the VLANs at this time, click Next. If any nodes have an Inactive or Unconfigured status, and you want to include these nodes in a VLAN, you need to activate or configure the node before you can include it in a VLAN. Click the pencil icon in the right column if you want to advance to the editing page. For information about how to edit the mapping table for a node, see the following: See VLAN Configuration - VLAN network settings and VLAN mapping edit page on page On the Summary-VLANTopologySummary page, click LinkCheck to verify the VLAN interface connections between the nodes in the storage pool. If all VLAN links are correct, the status of the VLAN is a green checkmark in the right-most column. Click Finish, which closes the wizard. If any VLAN links are incorrect, the status appears as a red X. Correct this problem as follows: If the addresses are incorrect, navigate back to the VLAN Configuration - VLAN network settings page and use the VLAN mapping edit table to correct the VLAN information. If one of the nodes is not configured completely, use the procedures in the following topic to complete the configuration: See Configuring the node interfaces on page 116.

137 Configuring virtual local area networks (VLANs) Completing the VLAN configuration 137 Click Back, and navigate to the VLANConfiguration- VLANnetworksettings page to correct the links. On a deduplication appliance, IP address is reserved for the installer. VLANs that include this IP address always appear with a red X. You can safely ignore rows in the VLAN Topology Summary table that include this IP address. 10 Proceed to the following: See Completing the VLAN configuration on page 137. Completing the VLAN configuration The following procedure explains how to complete the VLAN configuration and restart your backups. To complete the VLAN configuration 1 Type the following command to start all PureDisk services: # /etc/init.d/puredisk start 2 (Conditional) Change the state of the NetBackup disk pool to UP. Perform this step if the storage pool is connected to a NetBackup media server as part of a PureDisk deduplication option (PDDO) deployment. You do not need to perform this step if the storage pool is not connected to a media server. Complete the following steps: Log into the NetBackup media server. Use the nbdevconfig command to add the media server back to the disk pool. On Linux and UNIX systems, type the following command: /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp disk_pool_name -state UP On Windows systems, type the following command: install_path\netbackup\bin\admincmd\nbdevconfig -changestate -stype PureDisk -dp disk_pool_name -state UP

138 138 Configuring virtual local area networks (VLANs) About the VLAN configuration pages in the Storage Pool Configuration Wizard For disk_pool_name, specify the name of the disk pool. 3 Record the VLAN information you configured. This information is needed in case you need to perform a disaster recovery. Record your information in a table such as Table 6-2. Table 6-2 VLAN configuration record Zone name Storage pool authority addresses Node 1 addresses Node 2 addresses Node 3 addresses vlan spavl19.acme.com cr1vl19.acme.com cr2vl19.acme.com..... About the VLAN configuration pages in the Storage Pool Configuration Wizard The following topics explain the VLAN configuration pages in the Storage Pool Configuration Wizard: See VLAN Configuration - Message from webpage page on page 138. See VLAN Configuration - Discover configuration page on page 139. See VLAN Configuration - Node List page on page 139. See VLAN Configuration - VLAN network settings and VLAN mapping edit page on page 140. See Summary - VLAN Topology Summary page on page 142. VLAN Configuration - Message from webpage page Table 6-3 explains how to complete the VLAN Configuration - Message from webpage page.

139 Configuring virtual local area networks (VLANs) About the VLAN configuration pages in the Storage Pool Configuration Wizard 139 Table 6-3 Option OK VLAN Configuration - Message from webpage page Description Click OK to build the mapping tables for each node in the storage pool. If you configured VLANs in your storage pool but have not built the mapping tables, click OK. If mapping tables already exist, you can safely click OK to rebuild the mapping tables, but it is not necessary. Cancel Click Cancel to advance to the VLAN Configuration - Node List page. You can click Cancel if the node mapping tables already exists. VLAN Configuration - Discover configuration page Click OK after the Discover configuration process finishes. VLAN Configuration - Node List page The VLAN Configuration - Node List page shows the network information for each node. The Subnet Mapping Status column shows the node status. The node status can include one or two of the following keywords: Activated, which means that the node is active in the storage pool. Inactivated, which means that the node is included in the storage pool but is not activated. For example, if you added the node recently, the status is Inactivated. Configured, which means that the node has a VLAN mapping table. Unconfigured, which means that the node does not have a VLAN mapping table. Table 6-4 explains how to complete the VLAN Configuration - Node List page.

140 140 Configuring virtual local area networks (VLANs) About the VLAN configuration pages in the Storage Pool Configuration Wizard Table 6-4 Option VLAN Configuration - Node List page Description Click the pencil icon in the Action column Click the pencil icon if you want to add, update, or delete mapping table information. This action advances you to the VLAN Configuration - VLAN network settings and VLAN mapping edit page. For example, if the status is Unconfigured for any node, you can click the pencil icon to move to the VLAN Configuration - VLAN network settings and VLAN mapping edit page, which lets you add mapping table information. Click Next. Click Next to advance to the VLAN Topology Summary page. VLAN Configuration - VLAN network settings and VLAN mapping edit page The VLANConfiguration- VLANnetworksettingsandVLANmappingedit page includes two tables: the VLAN network settings table and the VLAN mapping edit table. Examine the Status column of the VLAN network settings table, and complete next steps according to Table 6-5. Table 6-5 Completing the VLAN Configuration - VLAN network settings and VLAN mapping edit page Status icon Meaning The FQDN and the IP address can be resolved to each other successfully. Your next step Click Next.

141 Configuring virtual local area networks (VLANs) About the VLAN configuration pages in the Storage Pool Configuration Wizard 141 Table 6-5 Completing the VLAN Configuration - VLAN network settings and VLAN mapping edit page (continued) Status icon Meaning The FQDN can be resolved to the IP address. The IP can be reverse resolved to the FQDN, but the FQDN cannot be resolved to the IP address. Your next step Complete the following steps: Click the row in which this icon appears. This action populates the VLAN mapping edit table at the bottom of this page. In the VLANmappingedittable, respecify the IP address so that it resolves to the FQDN. Click Validate Host to make sure that the new address information is correct. Click Add/Update to update the VLAN mapping table. Click Save. Complete the following steps: Reconfigure the FQDN in your DNS. Click Validate hosts. The query timed out or the query could not complete because of problems with the DNS server. Either the FQDN and the IP address cannot be resolved or there is a conflict between the existing FQDN and the queried FQDN. Check the link connection and check the DNS server. Use the ping command to see if the DNS server is reachable. Also use nslookup or dig commands to perform a resolve test. Check the DNS server. Use nslookup or dig commands to perform a resolve test. For a particular row of information, the table displays a dark blue shaded background in a table cell if the system detects an incorrect address. The current address, which the system queried, appears in the Conflict column. Make sure that all VLAN specifications are correct and that the addresses in DNS server are configured correctly. The VLAN mapping edit table enables you to correct the configuration. To populate the fields in this table, click on one of the rows in the VLAN network settings table that appears above the VLAN mapping edit table in the display. Table 6-6 explains how to correct the configuration.

142 142 Configuring virtual local area networks (VLANs) About the VLAN configuration pages in the Storage Pool Configuration Wizard Table 6-6 Option Using the VLAN mapping edit table to correct a configuration Description VLAN field in the VLAN mapping edit table NIC field in the VLAN mapping edit table IP Address field in the VLAN mapping edit table FQDN field in the VLAN mapping edit table Validate hosts Add/Update Use the drop-down to select the VLAN topology name that you want to correct. Use the drop-down to select the interface that you want to correct. Use the drop-down to select the IP address that you want to correct. Specify a new FQDN for the interface. Validates FQDNs in the mapping table list. This button causes the system to verify FQDNs and fix conflicts. Click OK on the popup message that appears. Changes the information for a selected VLAN. Typically, you click a row in the VLANnetworksettings table, use the VLAN mapping edit table to update information, and then click Add/Update to update the information for that VLAN in the VLAN network settings table. Delete Save Back Deletes the information for the selected row. Saves the configuration changes you made to the VLAN mapping edit table. Returns you to the VLAN Configuration - Node List page. Summary - VLAN Topology Summary page The VLAN Configuration - VLAN Topology Summary page lets you check the links in the mapping table. See Table 6-7 on page 143. explains how to complete the VLAN Configuration - VLAN Topology Summary page.

143 Configuring virtual local area networks (VLANs) Adding clients to the VLANs 143 Table 6-7 Option Link Check Back Summary - VLAN Topology Summary page Description Click Link Check if you want the system to verify that all the nodes can contact each other. Click Back to return to the configuration pages and correct the incorrect links. When you click Back, the VLAN Configuration - Message from webpage page displays. Click OK on the VLAN Configuration - Message from webpage page to regenerate the mapping tables and correct the interface specifications. Finish Click Finish if the Status column displays a green checkmark for the VLANs that you want to enable. The Status column displays a green checkmark if all nodes are within the same subnet and no links are broken. Adding clients to the VLANs When you configure VLANs, you assign multiple FQDNs and multiple IP addresses to a storage pool authority. The clients you attach to the storage pool need to attach to the storage pool by using a VLAN FQDN or a VLAN IP address. These VLAN FQDNs and VLAN IP addresses are the addresses you use when a particular storage pool operation requires you to log into the storage pool authority. For example, assume that you want to install PureDisk client agents on a host machine within VLAN19 in the example storage pool shown in the following topic: See VLAN example on page 106. For VLAN19, type the following address into a browser: Follow the instructions in the PureDisk Client Installation Guide to download and install the client agent software. For example, if you wanted to install a Linux client, the prompts are as follows: linux-oidb:~ # sh pdagent-linux_2.6_x run

144 144 Configuring virtual local area networks (VLANs) Adding clients to the VLANs => Please wait while extracting installer package... Symantec Installation Script Copyright Symantec Corporation, All Rights Reserved. This script will enable you to install and configure either the PureDisk deduplication option (PDDO plug-in) for NetBackup or a PureDisk agent. => Where do you want to install PureDisk agent? (/opt): => Are you sure you want to install it in /opt? [y,n] y => Starting PureDisk agent installation => Checking for available space in /opt: => done. => Extracting package: => done. => Please enter the IP address or hostname of your SPA server: spavl19.acme.com => Please enter your SPA username: root => Please enter your SPA password: => Please re-enter your SPA password: => Error: values do not match. Try again. => Please enter your SPA password: => Please re-enter your SPA password: => Testing connection with the SPA (spavl19.acme.com): => done. => Checking the SPA version: => done. => Please enter your department (press ENTER for default 'Unknown department'): => Please enter your location (press ENTER for default 'Unknown location'): => Please enter your data lock password (press ENTER to leave password blank): => Please re-enter your data lock password: => Registering agent on Storagepool Authority with the following settings: => + agent name: linux-oidb => Registering: => done. => Creating directory /opt/pdag/var: => done. => Creating directory /opt/pdag/tmp: => done. => Creating directory /opt/pdag/var/srd: => done. => Creating directory /opt/pdag/var/rt: => done. => Creating directory /opt/pdag/var/run: => done. => Creating directory /opt/pdag/var/progress: => done. => Creating directory /opt/pdag/var/keys: => done. => Retrieving routing tables: => done. => Generating SSL keys: => done => Do you want to allow file system browsing? (y) [y,n] y => File system browsing will be allowed. => Updating configuration file: => done.

145 Configuring virtual local area networks (VLANs) About configuring VLANs with bonded network interfaces (deduplication appliances only) 145 => Installing agent system startup files: => done. => Starting the agent: => done. => PureDisk agent installation completed successfully. => File /opt/pdag/log/installation/ _03h47_ _pda_install.log => contains a trace of this installation. About configuring VLANs with bonded network interfaces (deduplication appliances only) The deduplication appliance shell menu system contains commands that enable you to configure bonded network interfaces. The following procedure contains information about how to configure VLANs with bonded network interfaces. Perform this procedure from the appliance shell menu on a deduplication appliance.

146 146 Configuring virtual local area networks (VLANs) About configuring VLANs with bonded network interfaces (deduplication appliances only) To configure VLANs with bonded network interfaces 1 Specify either a dummy IP address or a physical IP address on the bonding enable command. If you decide to specify a dummy IP address, Symantec recommends that you specify the IP address for the netmask, which results in a subnet that contains only this dummy IP address. This reduces the possibility that you inadvertently specify IPs in the same subnet for the VLAN interfaces later. For example: linux-acmc.network> bonding enable bond0 balance-alb eth2 eth3 **** This may lose network connection, please do it at console, continue(y/n)?y **** IP is different from node ip , this may lose network connection, continue(y/n)?y 2 Use the vlan add command to configure the VLAN interfaces on the bonding interface. For example, type the following command to configure vlan1, vlan2 on bond0: linux-acmc.network> vlan add bond0 linux-acmc.network> vlan add bond0 linux-acmc.network> vlan show Node IP VLAN NIC NIC IP Address Netmask vlan1 bond0 N/A N/A vlan2 bond0 N/A N/A

147 Configuring virtual local area networks (VLANs) About PureDisk operations within VLANs Use the config addr command to configure IP addresses. For these IP addresses, make sure to specify a subnet that different from the subnet that you specified in step 1. For example: linux-acmc.network> config addr vlan linux-acmc.network> config addr vlan linux-acmc.network> config show Node IP Address NIC IP Address Netmask HW Address MTU * bond :0C:29:E5:7B: * eth * :0C:29:E5:7B: * eth :0C:29:E5:7B:7C * eth2 N/A N/A 00:0C:29:E5:7B: * eth3 N/A N/A 00:0C:29:E5:7B: * vlan :0C:29:E5:7B: * vlan :0C:29:E5:7B: Use the route show command to check the network routing and make sure that no entries conflict. That is, no entries can have the same destination. For example: linux-acmc.network> route show : Destination Gateway Genmask Flags Metric Ref Use Iface U vlan U vlan U eth U eth U eth U lo UG eth1 About PureDisk operations within VLANs The following operational notes pertain to using PureDisk software that is configured with VLANs: If you move a client from one VLAN to another VLAN, make sure to re-register the client on the new storage pool authority with the existing agent ID number.

148 148 Configuring virtual local area networks (VLANs) About PureDisk operations within VLANs To obtain the agent ID number, log into the administrative Web UI, select the client, and clickedit agent in the left pane. The dialog box that appears shows the ID number of the client s agent. Use this option if you reinstall the agent software on a client. This option ensures that any jobs that are associated with this client remain associated with the client after you install the new agent software. When PureDisk uses this parameter to reconnect this client to a storage pool, it uses the ID number from the last connection it made. For more information about registering or reregistering a client, see the PureDisk Client Installation Guide. PureDisk grants permissions at the storage pool level. The permissions you grant to a user on one VLAN also apply to that user when the user logs into a different VLAN. After the VLAN configuration is complete, the way you contact the storage pool depends on whether you want to contact the storage pool from outside the VLAN or from inside the VLAN, as follows: From outside the VLAN, you can address the storage pool by its public, non-vlan, storage pool authority node FQDN. For example, if you need to start the configuration wizard on the example storage pool, you type the following address into a browser window: From a host within one of the VLANs, use the storage pool's VLAN name to access the storage pool. For example, if you want to restore a file on one of the clients inside VLAN19, launch the administrative Web UI by typing the following address into a browser:

149 Chapter 7 Enabling the intelligent platform management interface (IPMI) This chapter includes the following topics: About the intelligent platform management interface (IPMI) Configuring the IPMI Guidelines for IPMI passwords and user names Completing the IPMI configuration pages in the Configuration Wizard IPMI maintenance procedures Using the appliance shell menu to configure the IPMI Using the web console About the intelligent platform management interface (IPMI) An IPMI lets you monitor and manage the deduplication appliance from a remote location by using the web console. From the remote location, you can use a laptop or you can use a keyboard, monitor, and mouse (KVM). The remote monitoring is enabled even when the deduplication appliance's operating system is not working. The web console is available by remote access even when the appliance is turned off, but the appliance must be connected to a power source in order for remote access to be possible

150 150 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI Symantec supports the IPMI on NetBackup 5020 deduplication appliances only. Symantec does not support the IPMI on NetBackup 5000 deduplication appliances. From the storage pool authority, Symantec supports the configuration of the IPMI of any node in the storage pool. From a content router, Symantec supports the configuration of the IPMI on that content router only. You can configure IPMI from the web UI or from the appliance shell menu. See Configuring the IPMI on page 150. See Using the appliance shell menu to configure the IPMI on page 167. When you receive a new appliance, the admin user account is present, but no other user accounts exist. The password for the admin IPMI user account is set to the factory default. The default password is Passw0rd. In the preceding password, the sixth character is a zero (0). You can configure the IPMI from either the Configuration Wizard or from the appliance shell menu. For more information about the IPMI and the web console, see the following topics: See Configuring the IPMI on page 150. See Guidelines for IPMI passwords and user names on page 159. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. See IPMI maintenance procedures on page 164. See Using the appliance shell menu to configure the IPMI on page 167. See Using the web console on page 172. Configuring the IPMI Table 7-1 explains how to configure the IPMI. For most configuration steps, you can use either the graphical user interface in the Configuration Wizard or you can use the command line interface in the appliance shell menu Table 7-1 Configuring the IPMI for a Deduplication Appliance node Step 1 Task Verify configuration prerequisites Where to find information See Verifying configuration prerequisites on page 152.

151 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI 151 Table 7-1 Configuring the IPMI for a Deduplication Appliance node (continued) Step Task Log in and begin the configuration Specify the administrator password (Optional) Create additional user accounts Specify appliance node IPMI network information (Conditional) Change user account passwords Where to find information See Logging on to the Configuration Wizard and accessing the IPMI configuration pages on page 153. OR See Logging on to the appliance shell menu and accessing the IPMI commands on page 168. See Specifying the IPMI administrator password from the Configuration Wizard on page 153. OR See Specifying the IPMI administrator password from the appliance shell menu on page 168. See (Optional) Adding IPMI users and setting IPMI user passwords from the Configuration Wizard on page 155. OR See (Optional) Adding IPMI users and setting IPMI user passwords from the appliance shell menu on page 170. See Specifying appliance node IPMI network information from the Configuration Wizard on page 156. OR See Specifying appliance node IPMI network information from the appliance shell menu on page 171. See (Conditional) Changing a user password from the Configuration Wizard on page 157. See About the intelligent platform management interface (IPMI) on page 149. See Guidelines for IPMI passwords and user names on page 159. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. See IPMI maintenance procedures on page 164. See Using the appliance shell menu to configure the IPMI on page 167. See Using the web console on page 172.

152 152 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI Verifying configuration prerequisites The following procedure lists the information that you need to gather before you start to configure the IPMI. To verify IPMI prerequisites 1 Verify that the storage pool is configured and works as expected. 2 For each appliance node in the storage pool for which you want to configure the IPMI, obtain the following information from your network administrator: An IPMI IP address A netmask The gateway IP address 3 (Conditional) Open the required ports in your firewall. If a firewall exists between the storage pool and the remote devices you use to manage the appliance (a laptop computer or a separate keyboard, video, and mouse), open the following ports based on the version of the appliance firmware: For 5000 and 5020 appliances with firmware versions 2.13 and earlier: #80 #5900 For 5000 and 5020 appliances with firmware versions later than 2.13: #443 #5900 More information about determining the firmware version is available. See Determining appliance firmware version on page 159. If you have a private internal network, remember to configure the settings accordingly in your network address translation (NAT). 4 Decide whether you want to configure the IPMI from the Configuration Wizard or from the appliance shell menu, and proceed as follows: If you want to configure the IPMI from the Configuration Wizard, proceed to the following: See Logging on to the Configuration Wizard and accessing the IPMI configuration pages on page 153. If you want to configure the IPMI from the appliance shell menu, proceed to the following:

153 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI 153 See Using the appliance shell menu to configure the IPMI on page 167. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. Logging on to the Configuration Wizard and accessing the IPMI configuration pages The following procedure explains how to log on to the Configuration Wizard and start the IPMI configuration. To log on to the Configuration Wizard and start the IPMI configuration 1 Type the following command into a browser to start the Configuration Wizard: For address, specify the public FQDN of the storage pool authority node. 2 (Conditional) Affirm the security exception for the installer. Depending on your site's security practices, you might see a browser security certificate affirmation page when you start the installer. 3 On the logon page, in the User name field, type root. 4 In the Password field, type the password. By default, the password is P@ssw0rd. In the default password, the sixth character is the numeral zero (0). 5 Click Log on. 6 In the right pane, click Configure IPMI. 7 Proceed to the following: See Specifying the IPMI administrator password from the Configuration Wizard on page 153. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. Specifying the IPMI administrator password from the Configuration Wizard The following procedure explains how to create an administrator password.

154 154 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI To specify an administrator password 1 (Conditional) Log on to the Configuration Wizard and access the IPMI configuration page. Perform this step if you are not already logged on. For information about how to perform this step, see the following: See Logging on to the Configuration Wizard and accessing the IPMI configuration pages on page Click the User management tab. 3 (Conditional) Specify which node contains the admin user with the Select node drop-down. Alternatively, you can specify to change the admin user on all nodes by selecting the Change on all nodes checkbox. 4 In the Users pane, make sure that admin is selected. Alternatively, click the row that contains the admin user. This action selects the admin user. 5 In the Adduser/ Changepassword pane, type the new admin user's password into both the Password field and into the Confirm password field. For information about valid passwords, see the following: See Guidelines for IPMI passwords and user names on page Click Apply. 7 Click Close. 8 Proceed to one of the following: If you want to configure other, non-administrator user accounts, proceed to the following: See (Optional) Adding IPMI users and setting IPMI user passwords from the Configuration Wizard on page 155. If you want the admin user to be the only user who can log into the web console, proceed to the following: See Specifying appliance node IPMI network information from the Configuration Wizard on page 156. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150.

155 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI 155 (Optional) Adding IPMI users and setting IPMI user passwords from the Configuration Wizard The appliance administrator can add accounts for additional users. These additional users can log into the IPMI console and administer the appliance nodes. Before the users you add can log into the IPMI console, the users need to change the password that the administrator assigns to them in this procedure The following procedure explains how to add additional users. To add IPMI users and set IPMI user passwords 1 (Conditional) Log on to the Configuration Wizard and access the IPMI configuration page. Perform this step if you are not already logged on. For information about how to perform this step, see the following: See Logging on to the Configuration Wizard and accessing the IPMI configuration pages on page Click the User management tab. 3 Specify which node contains the admin user with the Select node drop-down. Select the Change on all nodes checkbox to make the changes on all nodes in the storage pool. Do not select this checkbox if you only want to make the changes on a single node. 4 In the Add user / Change password pane, type the name of the new user into the User name field. 5 Type the password for the new user into the Password field and into the Confirm password password field. 6 Click Apply. The following message appears above the Users pane: Operation complete. The user needs to change the password before the user can log into the web console. Proceed to the following step. 7 Click Close.

156 156 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI 8 Notify IPMI console users of their account creation and direct them to change their user passwords. For each user account that you created, notify the user of this action and encourage them to change their passwords as soon as possible. The additional users need to change their passwords before they can administer any nodes through the IPMI console. For information about how users can change their passwords, see the following: See (Conditional) Changing a user password from the Configuration Wizard on page Proceed to the following: See Specifying appliance node IPMI network information from the Configuration Wizard on page 156. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. Specifying appliance node IPMI network information from the Configuration Wizard Typically, if you configure the IPMI for one appliance, you configure it for all nodes in the storage pool. The following procedure explains how to specify or edit IPMI network information for an appliance node. To specify network information during an initial IPMI configuration 1 (Conditional) Log on to the Configuration Wizard and access the IPMI configuration page. Perform this step if you are not already logged on. For information about how to perform this step, see the following: See Logging on to the Configuration Wizard and accessing the IPMI configuration pages on page Click the Network configuration tab. 3 In the (upper) Node list pane, select one of the appliance nodes. To select a node, click the row for the node or click the circle in the left-most column of the row for a particular appliance node. 4 In the (lower) Edit network pane, specify the following information:

157 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI 157 The IPMI IP address (required). The IPMI netmask (required). The IPMI gateway (optional). For each of the preceding items, specify the network information that you obtained from your network administrator. These are the specifications for the IPMI network. 5 Click Apply. 6 Repeat the following steps for each appliance node in the storage pool: Step 3 Step 4 Step 5 7 Make sure to record the IPMI IP of each node in the storage pool. Keep this information in a safe place outside of the storage pool. For example, you can write down the IPMI IP addresses, or you can take a screen capture of the Network configuration tab. If you need to access a node directly, and the storage pool authority node is not operational, you need the IPMI IP addresses to start the web console 8 Click Close. 9 (Conditional) Proceed to the following: If you configured any non-administrator user accounts, ask those users to complete the following procedure: See (Conditional) Changing a user password from the Configuration Wizard on page 157. If you did not configure any non-administrator user accounts, your IPMI configuration is complete. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. (Conditional) Changing a user password from the Configuration Wizard Perform this procedure if the administrator assigned a password to you. You can change an IPMI password in one of the following ways: If you are logged into the appliance as the root user, you can use the procedure in this topic, or you can use the procedure in the following topic:

158 158 Enabling the intelligent platform management interface (IPMI) Configuring the IPMI See Specifying the IPMI administrator password from the Configuration Wizard on page 153. If you are a non-administrator user, use the procedure in this topic. When the admin user creates your account, the admin user creates a password for you. You cannot log into the web console with that password, so use the procedure in this topic to change your password. The Change IPMI password link on the Configuration Wizard log on page opens the Change IPMI user password page. The following procedure explains how to change a password. To change a user account or administrator account password 1 Type the following command into a browser to start the Configuration Wizard: For address, specify the public FQDN of the storage pool authority node. 2 (Conditional) Affirm the security exception for the installer. Depending on your site's security practices, you might see a browser security certificate affirmation page when you start the installer. 3 In the right pane, click Change IPMI password. 4 On the Change IPMI password page, complete the following fields: User name. Type your user name. Password. Type your existing password. For example, if the administrator recently defined an account for you, type that password. New password. Type a new password. Confirm password. Type the new password again. Select node. Specify the node that has the user name and password you want changed. Change on all nodes. Select this option to change the password for the specified user on all nodes in the environment. For information about valid passwords, see the following: See Guidelines for IPMI passwords and user names on page Click Apply. 6 Click Close. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150.

159 Enabling the intelligent platform management interface (IPMI) Guidelines for IPMI passwords and user names 159 Determining appliance firmware version The ports that need to be open on your firewall and the connectivity to the web console depend on the firmware version of the appliance. Use the procedure that is shown to determine the firmware version on your appliance. To determine the firmware version on the appliance 1 Log onto the web console. More information is available about this topic: See Starting the web console from inside the Configuration Wizard on page 173. See Starting the web console from outside of Configuration Wizard on page In the left pane, under Upgrade Management, select Upgrade Firmware. 3 In the right pane, find BMC under Firmware Name, and review the Firmware Version listed. This is the firmware version on the appliance. Guidelines for IPMI passwords and user names You cannot change the password for a user's account from the web console itself. Use the Configuration Wizard to change the admin password and any user passwords. For information about how to change passwords, see one of the following: See Specifying the IPMI administrator password from the Configuration Wizard on page 153. See (Optional) Adding IPMI users and setting IPMI user passwords from the Configuration Wizard on page 155. User names must have at least four characters and are limited to 15 characters. Passwords must have at least eight characters and are limited to 19 characters. The default password for the admin account is Passw0rd. In the preceding password, the sixth character is a zero (0). You can use any of the following characters in user names and passwords: Uppercase letters Lowercase letters Numbers Hyphens (-). User names and passwords cannot start with a hyphen. Underscore characters (_)

160 160 Enabling the intelligent platform management interface (IPMI) Completing the IPMI configuration pages in the Configuration Wizard See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. See IPMI maintenance procedures on page 164. See Using the appliance shell menu to configure the IPMI on page 167. See Using the web console on page 172. Completing the IPMI configuration pages in the Configuration Wizard The following topics contain information about how to complete the fields on the IPMI configuration pages: See Completing the User management tab on page 160. See Completing the Network configuration tab on page 162. See Examining log information on page 163. See Completing the Change IPMI password page on page 163. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. See Guidelines for IPMI passwords and user names on page 159. See IPMI maintenance procedures on page 164. See Using the appliance shell menu to configure the IPMI on page 167. See Using the web console on page 172. Completing the User management tab Table 7-2 explains how to complete the fields in the User management tab.

161 Enabling the intelligent platform management interface (IPMI) Completing the IPMI configuration pages in the Configuration Wizard 161 Table 7-2 Field or button User name IPMI configuration - User management tab Content or action To create a new user account, type the new user name into this field. If no user by this name currently exists, the wizard creates a new user with the specified password. To change the password of an existing user account, type the name of an existing user into this field. Select node Change on all nodes Password Use this drop down to specify the node where you want to add or to modify the user account. Use this check box to modify the specified user account on all nodes in the environment. If you want to create a new user account, type the new user account password into this field. If you want to change the password of an existing user account, type the new password into this field. For information about valid passwords, see the following: See Guidelines for IPMI passwords and user names on page 159. Confirm password Type the password into this field. Type the same password you typed into the Password field. For information about valid passwords, see the following: See Guidelines for IPMI passwords and user names on page 159. Remove To remove a user, click the button to the left of the user you want to remove. Click Remove. You cannot remove the admin user. Apply Clear Click Apply to apply your changes. Click Clear to clear the fields on this tab. The following topics pertain to User management tab: See Specifying the IPMI administrator password from the Configuration Wizard on page 153. See (Optional) Adding IPMI users and setting IPMI user passwords from the Configuration Wizard on page 155. See Guidelines for IPMI passwords and user names on page 159. See About the intelligent platform management interface (IPMI) on page 149.

162 162 Enabling the intelligent platform management interface (IPMI) Completing the IPMI configuration pages in the Configuration Wizard See Configuring the IPMI on page 150. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. Completing the Network configuration tab Table 7-3 explains how to complete the Network configuration tab. Table 7-3 Field or button Node FQDN IPMI IP IPMI configuration - Network configuration tab Content or action This field is populated when you select the node you want to modify from the Node list pane. Type the new IP address into the IPMI IP field. You can obtain the network information from your network administrator. Note: Make sure to record the IPMI IP of each node in the storage pool. Keep this information in a safe place outside of the storage pool. For example, you can write down the IPMI IP addresses, or you can take a screen capture of the Network configuration tab. If you need to access a node directly, and the storage pool authority node is not operational, you need the IPMI IP addresses that you configured to start the web console IPMI netmask IPMI gateway Launch web console Apply Type the new network mask into the IPMI netmask field. Type the new gateway into the IPMI gateway field. Opens a window to the web console. Use your existing user name and password to log into the console. Select a node before you click this button. Note: This button was labeled Launch ISM in previous versions of the software. Click Apply to apply your changes. The following topics explain some tasks you can perform from the Network configuration tab: Specifying appliance node IPMI network information from the Configuration Wizard Starting the web console from inside the Configuration Wizard

163 Enabling the intelligent platform management interface (IPMI) Completing the IPMI configuration pages in the Configuration Wizard 163 Examining log information See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. The Log information tab shows task completion progress for all actions in the IPMI configuration session. Click Clear to clear the information. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. Completing the Change IPMI password page The Change IPMI password page lets you change your IPMI password and lets you sync an account. Users need to access this page and change their password after the admin user creates an account for them. Table 7-4 explains how to complete the Change IPMI password page. Table 7-4 IPMI configuration - Change IPMI password page Field, checkbox, or button User name Select node Change on all nodes Password New password Confirm password Apply Clear Content or action Type an existing user name. Specify the node where the account you want to change exists. Select the node name from the drop-down list. Check this box to change the specified account on all nodes in the environment. Type the existing password for the account. Type the new password for the account. Type the new password for the account. Click Apply to apply your changes. Click Clear to clear the fields on this tab.

164 164 Enabling the intelligent platform management interface (IPMI) IPMI maintenance procedures See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. IPMI maintenance procedures The following procedures describe maintenance procedures you need to perform when the IPMI is configured: See Synchronizing web console access after adding nodes to the storage pool on page 164. See Changing a user password from the appliance shell menu on page 166. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. See Guidelines for IPMI passwords and user names on page 159. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. See Using the appliance shell menu to configure the IPMI on page 167. See Using the web console on page 172. Synchronizing web console access after adding nodes to the storage pool Perform the following procedure if you add additional appliance nodes to a storage pool and you want to synchronize passwords. The procedure grants a user the permission to access the new nodes remotely. The admin user and all additional users need to perform this procedure. Note: This procedure assumes that the account exists on the newly added node. By default, the admin user is on all new nodes. More information about how to add new IPMI users is available. See (Optional) Adding IPMI users and setting IPMI user passwords from the Configuration Wizard on page 155.

165 Enabling the intelligent platform management interface (IPMI) IPMI maintenance procedures 165 To synchronize IPMI account passwords for the admin user on additional nodes 1 Type the following command into a browser to start the Configuration Wizard: For address, specify the public FQDN of the storage pool authority node. 2 (Conditional) Affirm the security exception for the installer. Depending on your site's security practices, you might see a browser security certificate affirmation page when you start the installer. 3 Log into the installer using the root user ID and password. 4 In the right pane of the logon page, click Configure IPMI. 5 From the Select node drop-down, select the newly added node. Make sure to deselect the Change on all nodes option. 6 Select the user name for the user you want to change the password. 7 Enter the new password and confirm the new password. Be sure to enter the same password that is used on the existing node or nodes. 8 Click Apply and then click Close. 9 Once the password on the new node matches the password for the original node or nodes, use the Change on all nodes option to reset the password on all nodes. To synchronize IPMI account passwords for normal users on additional nodes 1 Type the following command into a browser to start the Configuration Wizard: For address, specify the public FQDN of the storage pool authority node. Depending on your site's security practices, you might see a browser security certificate affirmation page when you start the installer. 2 (Conditional) Affirm the security exception for the installer. 3 Click Change IPMI password in the right pane. 4 From the Select node drop-down, select the newly added node. Make sure to deselect the Change on all nodes option.

166 166 Enabling the intelligent platform management interface (IPMI) IPMI maintenance procedures 5 Complete the Change IPMI password page. For information about how to complete this page, see the following: See Completing the Change IPMI password page on page Once the password on the new node matches the password for the original node or nodes, use the Change on all nodes option to reset the password on all nodes. See About the intelligent platform management interface (IPMI) on page 149. See IPMI maintenance procedures on page 164. Changing a user password from the appliance shell menu If you are the administrator of a deduplication appliance and you want to change the root password, you can change your own password or an IPMI user password from within the appliance shell menu. If you are not the administrator, you can change your user password only from the logon page of the Configuration Wizard. For more information, see the following: See (Conditional) Changing a user password from the Configuration Wizard on page 157. The following procedure explains how to change an IPMI user password from the appliance shell menu. To change an IPMI user account password or the IPMI admin account password from the appliance shell menu 1 (Conditional) Connect to the appliance and log onto the appliance shell menu. Perform this step if you are not already logged on to the appliance shell menu. For information about how to perform this step, see the following: See Logging on to the appliance shell menu and accessing the IPMI commands on page Type the user passwd username command. For username, specify the name of the user who wants to change his or her password. 3 At the New Password prompt, type the new password for the user.

167 Enabling the intelligent platform management interface (IPMI) Using the appliance shell menu to configure the IPMI At the Confirm Password prompt, type the new password for the user a second time. For example: IPMI> user passwd user_01 New Password : Confirm Password : User password has been changed IPMI> The appliance shell menu does not echo the passwords you type. 5 Type exit to return to the root view. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. Using the appliance shell menu to configure the IPMI You can use either the appliance shell menu or the Configuration Wizard to configure IPMI access. Before you start the appliance shell menu, make sure to verify the configuration prerequisites that are described in the following procedure: See Verifying configuration prerequisites on page 152. The following topics describe how to configure the IPMI from the appliance shell menu: See Logging on to the appliance shell menu and accessing the IPMI commands on page 168. See Specifying the IPMI administrator password from the appliance shell menu on page 168. See (Optional) Adding IPMI users and setting IPMI user passwords from the appliance shell menu on page 170. See Specifying appliance node IPMI network information from the appliance shell menu on page 171. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. See Guidelines for IPMI passwords and user names on page 159. See Completing the IPMI configuration pages in the Configuration Wizard on page 160.

168 168 Enabling the intelligent platform management interface (IPMI) Using the appliance shell menu to configure the IPMI See IPMI maintenance procedures on page 164. See Using the web console on page 172. Logging on to the appliance shell menu and accessing the IPMI commands The following procedure explains how to log on to the appliance shell menu and access the IPMI commands. To configure the IPMI from the appliance shell menu 1 Connect to the appliance for which you want to configure the IPMI. For example, you can use PuTTY, which is available as a free download. Symantec supports the IPMI on NetBackup 5020 appliances only. For information about using the IPMI in a storage pool with both NetBackup 5020 appliances and NetBackup 5000 appliances, see the following: See About the intelligent platform management interface (IPMI) on page Log into the appliance. By default, the user name is sysadmin, and the password is P@ssw0rd. In the preceding password, the sixth character is the numeral zero (0). 3 Type IPMI, and press Enter. For example: > IPMI 4 Proceed to the following: See Specifying the IPMI administrator password from the appliance shell menu on page 168. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. Specifying the IPMI administrator password from the appliance shell menu The following procedure explains how to specify the IPMI administrator password from the appliance shell menu.

169 Enabling the intelligent platform management interface (IPMI) Using the appliance shell menu to configure the IPMI 169 To specify the IPMI administrator password from the appliance shell menu 1 (Conditional) Connect to the appliance and log onto the appliance shell menu. Perform this step if you are not already logged on to the appliance shell menu. For information about how to perform this step, see the following: See Logging on to the appliance shell menu and accessing the IPMI commands on page Type user passwd admin nodeip. For information about valid passwords, see the following: See Guidelines for IPMI passwords and user names on page At the New Password prompt, type the new password for the admin user. 4 At the Confirm Password prompt, type the new password for the admin user a second time. For example: IPMI> user passwd admin nodeip New Password : Confirm Password : User password has been changed IPMI> The appliance shell menu does not echo the passwords you type. 5 Type exit to return to the root view. 6 Proceed to one of the following: If you want to configure other, non-administrator user accounts, proceed to the following: See (Optional) Adding IPMI users and setting IPMI user passwords from the appliance shell menu on page 170. If you want the admin user to be the only user who can log into the web console, proceed to the following: See Specifying appliance node IPMI network information from the appliance shell menu on page 171. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150.

170 170 Enabling the intelligent platform management interface (IPMI) Using the appliance shell menu to configure the IPMI (Optional) Adding IPMI users and setting IPMI user passwords from the appliance shell menu The appliance administrator can add accounts for additional users. These additional users can log into the web console and administer the appliance nodes. Before the users you add can log into the web console, the users need to change the password that the administrator assigns to them in this procedure The following procedure explains how to add IPMI users and set IPMI user passwords from the appliance shell menu. To add IPMI users and set IPMI user passwords from the appliance shell menu 1 (Conditional) Connect to the appliance and log onto the appliance shell menu. Perform this step if you are not already logged on to the appliance shell menu. For information about how to perform this step, see the following: See Logging on to the appliance shell menu and accessing the IPMI commands on page Type user add username. For username, type the name of a user that you want to add. 3 At the Input Password prompt, type a password for this user. 4 At the Confirm Password prompt, type the password a second time. For example: IPMI> user add user_01 Input Password : Confirm Password : User user_01 is added. user can actually login. Password must be changed before this 5 Notify web console users of their account creation and direct them to change their user passwords. For each user account that you created, notify the user of this action and encourage them to change their passwords as soon as possible. The additional users need to change their passwords before they can administer any nodes through the web console. For information about how a user can change his or her password, see the following: See (Conditional) Changing a user password from the Configuration Wizard on page 157.

171 Enabling the intelligent platform management interface (IPMI) Using the appliance shell menu to configure the IPMI Type exit to return to the root view. 7 Proceed to the following: See Specifying appliance node IPMI network information from the appliance shell menu on page 171. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. Specifying appliance node IPMI network information from the appliance shell menu The following procedure explains how to specify or edit IPMI network information for an appliance node from the appliance shell menu. To edit IPMI network information for an appliance node from the appliance shell menu 1 (Conditional) Connect to the appliance and log onto the appliance shell menu. Perform this step if you are not already logged on to the appliance shell menu. For information about how to perform this step, see the following: See Logging on to the appliance shell menu and accessing the IPMI commands on page Type network show to display the network information for all the appliance nodes in the storage pool. Make sure that all the nodes for which you want to configure the IPMI appear in the command output. 3 Type the following command: network config nodeip ipaddr IPMI_ipaddr IPMI_netmask [ IPMI_default_gateway ] The preceding command's arguments consist of the network information that you obtained from your network administrator. These are the specifications for the IPMI network. The arguments to this command are as follows: For nodeip, specify the IP address where you want to make the changes. For ipaddr, specify the public IP address of a node. For IPMI_ipaddr, specify the IP address that you want to assign to this node as the node's IPMI network address. For IPMI_netmask, specify the IPMI network mask.

172 172 Enabling the intelligent platform management interface (IPMI) Using the web console (Optional) For IPMI_default_gateway, specify the IPMI default gateway. 4 Repeat the following step for each appliance node: Step 3. 5 Type exit to return to the root view. 6 (Conditional) Proceed to the following: If you configured any non-administrator user accounts, ask those users to complete the following procedure: See (Conditional) Changing a user password from the Configuration Wizard on page 157. If you did not configure any non-administrator user accounts, your IPMI configuration is complete. See About the intelligent platform management interface (IPMI) on page 149. See Configuring the IPMI on page 150. Using the web console Symantec Corporation supports your ability to use the web console to perform the following tasks: Start and stop appliance operations. Load an ISO image from the Symantec's File Connect website. The web console enables you to perform many other tasks, but Symantec supports your ability to perform only the tasks in the preceding list. If additional operations are required, contact Symantec Technical Support. For information about the tasks you can perform from web console, see the following: See Starting the web console from inside the Configuration Wizard on page 173. See Starting the web console from outside of Configuration Wizard on page 173. See Starting a deduplication appliance from the web console on page 174. See Stopping a deduplication appliance from the web console on page 175. See Downloading an ISO image and installing the ISO image on the appliance on page 175. See About the intelligent platform management interface (IPMI) on page 149.

173 Enabling the intelligent platform management interface (IPMI) Using the web console 173 See Configuring the IPMI on page 150. See Guidelines for IPMI passwords and user names on page 159. See Completing the IPMI configuration pages in the Configuration Wizard on page 160. See IPMI maintenance procedures on page 164. See Using the appliance shell menu to configure the IPMI on page 167. Starting the web console from inside the Configuration Wizard The following procedure explains how to start the web console from within the Configuration Wizard. To start the web console from inside the Configuration Wizard 1 Log on to the Configuration Wizard and access the IPMI configuration page. For information about how to perform this step, see the following: See Logging on to the Configuration Wizard and accessing the IPMI configuration pages on page Click the Network configuration tab. 3 In the (upper) Node list pane, select a node. 4 Click Launch web console. This button was labeled Launch ISM in previous versions of the software. If a node's IPMI is not configured or if the appliance does not support IPMI, this button is disabled. See About the intelligent platform management interface (IPMI) on page 149. See Using the web console on page 172. Starting the web console from outside of Configuration Wizard When you configure the IPMI, you can start the web console to perform maintenance procedures on an appliance. If the storage pool authority node is unavailable, you can use this procedure to access the node directly. The following procedure explains how to start the web console from outside the Configuration Wizard.

174 174 Enabling the intelligent platform management interface (IPMI) Using the web console To start the web console from outside of Configuration Wizard From a Web browser, type the following IP address for 5020 appliances with firmware versions 2.13 and earlier: Type the following IP address for 5020 appliances with firmware versions later than 2.13: For IPMI_node_IP, specify the IPMI IP address you specified for this appliance node in the following procedure: See Specifying appliance node IPMI network information from the Configuration Wizard on page 156. More information about determining the firmware version is available. See Determining appliance firmware version on page 159. See About the intelligent platform management interface (IPMI) on page 149. See Using the web console on page 172. Starting a deduplication appliance from the web console The following procedure explains how to boot a deduplication appliance from the web console. To start (boot) a deduplication appliance from the web console 1 Start the web console. For information about how to log into the web console, see the following: See Starting the web console from inside the Configuration Wizard on page 173. See Starting the web console from outside of Configuration Wizard on page In the left panel, in the Device Configuration section, click Boot OS. 3 In the right panel, select Boot. 4 Click OK. See About the intelligent platform management interface (IPMI) on page 149. See Using the web console on page 172.

175 Enabling the intelligent platform management interface (IPMI) Using the web console 175 Stopping a deduplication appliance from the web console The following procedure explains how to shut down a deduplication appliance from the web console. To stop (shut down) a deduplication appliance from the web console 1 Start the web console. For information about how to log into the web console, see the following: See Starting the web console from inside the Configuration Wizard on page 173. See Starting the web console from outside of Configuration Wizard on page In the left panel, in the Device Configuration section, click Boot OS. 3 In the right panel, select Shut down. 4 Click OK. See About the intelligent platform management interface (IPMI) on page 149. See Using the web console on page 172. Downloading an ISO image and installing the ISO image on the appliance The following procedure explains how to download an ISO image from Symantec's FileConnect website to a local computer (such as a Windows personal computer), move the ISO image to an appliance, and reimage that appliance with the downloaded ISO.

176 176 Enabling the intelligent platform management interface (IPMI) Using the web console To download an ISO image and reimage an appliance 1 From a local personal computer, use a browser to access the following website: This URL points to Symantec's FileConnect website. 2 On the Enter Serial Number page, type the appliance's serial number into the empty box and click Enter. Continue to follow the FileConnect prompts until you have downloaded the new Deduplication Appliance Software ISO image. If you need help with the FileConnect website, click the FAQ link on the extreme right-hand side of the Enter Serial Number page. This FAQ includes a user guide and frequently asked questions. The final step in the download process asks you to specify a destination directory on the local PC for the software download. 3 From the local PC, start the web console. For information about how to log into the web console, see the following: See Starting the web console from inside the Configuration Wizard on page 173. See Starting the web console from outside of Configuration Wizard on page In the left panel, in the Device Configuration section, click Start KVM. 5 In the pop-up that appears, click OK to open the file. Make sure that the pop-up blocker in your browser is not enabled. If a security pop-up message appears for the Java ikvm Viewer, click Run. 6 At the top of the Java ikvm Viewer terminal window that appears, click Virtual Device > Virtual Media from the menu. The Virtual Media pop-up that appears is your virtual DVD drive. 7 In the Virtual Media pop-up, click Open Image. 8 Use the pull-down menu to the right of Look In to navigate to the ISO image that you downloaded. For example, click Images, then select the folder that contains the ISO image that you downloaded. When you locate the ISO image file that you need, click the image file itself and then click Open. 9 On the Virtual Media window, make sure that the ISO image you selected appears in the Image file name and full path field.

177 Enabling the intelligent platform management interface (IPMI) Using the web console Click Plug In. 11 Click OK. 12 Shut down and then restart the appliance: Perform the following steps to shut down the appliance: In the web Console, in the left panel, under Device Configuration, click Boot OS. In the right panel, select Shutdown and click OK. On the cautionary pop-up windows that appears, click OK. On the confirmation pop-up window that appears, click OK. Perform the following steps to boot the appliance: Under Device Configuration, click Boot OS. In the right panel, select Boot and click OK. On the confirmation pop-up window that appears, click OK. 13 Monitor the installation process in the Java ikvm Viewer window. The installation process can take 40 minutes or more. 14 After the welcome message appears, log into the appliance shell menu as sysadmin. Type the password at the Password: prompt. By default, the password is After you type the password, the system responds with the shell menu. 15 Type logout and press Enter to log out of the shell menu. 16 Use one of the following procedures to configure the Deduplication Appliance Software release that you installed: If this installation is a new installation, use the Deduplication Appliance Software Getting Started Guide to configure the software. If this installation is an upgrade, use the release notes for this software version to upgrade the appliance. See About the intelligent platform management interface (IPMI) on page 149. See Using the web console on page 172.

178 178 Enabling the intelligent platform management interface (IPMI) Using the web console

179 Chapter 8 Using Symantec Critical System Protection This chapter includes the following topics: About Symantec Critical System Protection Configuring Symantec Critical System Protection About Symantec Critical System Protection Symantec Critical System Protection (SCSP) secures physical and virtual servers using flexible, policy-based monitoring, and protection. SCSP also addresses compliance requirements across heterogeneous environments. SCSP uses non-signature based Host Intrusion Prevention to proactively protect against zero-day attacks and malicious insider threats. It also ensures Host Integrity and compliance using host intrusion detection based system monitoring, notification, and auditing. See Configuring Symantec Critical System Protection on page 179. Configuring Symantec Critical System Protection Under the Monitor tab, the SCSPAuditLogs option displays the SCSP information. The Audit Trail Report shows the last 12 hours of the SCSP log file by default.

180 180 Using Symantec Critical System Protection Configuring Symantec Critical System Protection Table 8-1 Column title Event ID Date Time Severity Event Type Message Audit trail report Description The event ID number that is associated with the specific event. Use the value with the scsp view command to view specific event IDs. The date and the time when the specific event occurred. The event s severity level. Use the severity level with the scsp view command to see all events with the specified severity level. The event type value for the specified event. Use the event type with the scsp view command to see all events with the specified event type. The message that is associated with the event. Click Filter Audit Logs to change what is displayed. The Enter values to filter audit logs dialog lets you refine the report. Click Apply or Cancel after you make your selections. Table 8-2 Option String Events Severity From To Filter Audit logs options Description Enter the text you want displayed. Be aware the text string you enter is case-sensitive. To search for a phrase, place the text inside quotation marks. Select the event type you want displayed from the drop-down. Select the alert severity level you want displayed. Indicate the start date and start time for events. Be aware the time is specified in 24 hour format. Indicate the end date and end time for events. Be aware the time is specified in 24 hour format. Click Set Log Retention to change the retention period for the SCSP audit log files. When you have made your changes, click OK or Cancel. This option is disabled when the appliance is connected to an SCSP server.

181 Using Symantec Critical System Protection Configuring Symantec Critical System Protection 181 Table 8-3 Log retention options Basis for retention Period Number of log files Values Specify the retention based on the number of days. Specify an integer greater than zero. Specify the total number of log files you want used. Use Connect to specify the location of an existing SCSP certificate or to download one from a different site. Table 8-4 Option Host name or IP Description Specify the fully qualified domain name or the TCP/IP address for the SCSP server to which the appliance should connect. To disconnect completely from an SCSP server, specify the TCP/IP address (the loop back IP address). This option resets the SCSP settings on appliance and brings the appliance back to an unmanaged state. Port Download authentication certificate from the site Provide the location to an existing certificate Specify the port number to use for the connection to the remote SCSP host. The default port number is 443. When you select this option, the appliance initiates the connection process for downloading a new SCSP certificate. By default the downloaded certificate is placed in the /storage/tmp/ directory. When you select this option, you must specify the location on the local appliance where the SCSP certificate exists. Click SCSP Documentation to connect to the Symantec website where additional documentation on SCSP is available. See About Symantec Critical System Protection on page 179.

182 182 Using Symantec Critical System Protection Configuring Symantec Critical System Protection

183 Appendix A About PureDisk This appendix includes the following topics: About PureDisk in the Deduplication Appliance Software releases About platform-specific PureDisk storage pool behavior About PureDisk documentation About PureDisk in the Deduplication Appliance Software releases The Deduplication Appliance Software contains Symantec NetBackup PureDisk. For information about PureDisk features and fixes, links to PureDisk documentation, and other information, see the PureDisk release notes at the following website: The following topics contains information about PureDisk on a deduplication appliance: See About platform-specific PureDisk storage pool behavior on page 183. See About PureDisk documentation on page 186. About platform-specific PureDisk storage pool behavior In addition to the appliance platform, Symantec supports PureDisk Remote Office Edition (ROE) software on customer-purchased hardware. For more general information about PureDisk platforms, see the following:

184 184 About PureDisk About platform-specific PureDisk storage pool behavior See the PureDisk Getting Started Guide. PureDisk operates in a nearly identical way on all platforms. Some features are supported on specific platforms only. The following describe specific areas in which storage pool operations on a deduplication appliance differ from storage pool operations on a PureDisk ROE storage pool: See Authentication brokers on page 184. See High availability on page 184. See Storage pool reconfiguration on page 184. See Upgrades and rollbacks on page 185. See Disaster recovery backups and restores on page 185. Authentication brokers High availability The deduplication appliance is preconfigured with a local root broker. For more information about brokers, see the following: See the PureDisk Getting Started Guide. Storage pool reconfiguration On a deduplication appliance, PureDisk does not support high availability. Information in the PureDisk documentation that refers to clustering or to high availability does not apply to the storage pools that are configured from one or more deduplication appliances The information in the "Storage Pool Management" chapter of the PureDisk Administrator's Guide describes several procedures that you can use to manage or reconfigure a storage pool. The management procedures in the PureDisk Administrator's Guide require you to use either the PureDisk ROE Storage Pool Configuration Wizard, the administrative Web UI, or the command line. Be aware that the Storage Pool Configuration Wizard on the deduplication appliance differs from the Storage Pool Configuration Wizard that is used by the deduplication appliance. The deduplication appliance does not support the PureDisk management procedures in the PureDisk Administrator's Guide that require you to start the PureDisk ROE Storage Pool Configuration Wizard. On the deduplication appliance, you can perform the management procedures that are described in the PureDisk Administrator's Guide that require you to use

185 About PureDisk About platform-specific PureDisk storage pool behavior 185 Upgrades and rollbacks the administrative Web UI or the command line. In addition, you can perform all the management procedures that are described in the following: See About the storage pool management procedures you can perform on a deduplication appliance on page 16. The release notes document for each deduplication appliance software upgrade explains how to apply software updates. Use the command-line installation method in the release notes to install the upgrade. Symantec includes the Manage Patches link on the Welcome page of the Storage Pool Configuration Wizard for PureDisk ROE. Symantec does not include the Manage Patches link on the Welcome page of the Storage Pool Configuration Wizard for the deduplication appliance. On appliance platforms, the software automatically creates a checkpoint when you apply a patch or update. On PureDisk ROE platforms, a user can specify that a checkpoint be created, but checkpoints are not created automatically. Disaster recovery backups and restores If you use the deduplication appliance as part of a NetBackup environment, make sure to back up the files that are stored on the appliance to your NetBackup environment. For example, you can use storage lifecycle policies to copy the data to NetBackup other storage devices. If you back up PureDisk clients directly to the deduplication appliance, make sure to back up the deduplication appliance itself. For example, if you have two appliances, you can create a replication policy to back up the data from one appliance to the other appliance. Alternatively, you can perform a disaster recovery backup as described in the PureDisk Administrator s Guide. More information about disaster recovery backup and disaster recovery restore is available. For conceptual overview and specific procedural information, refer to the Disaster recovery backup procedures chapter in the PureDisk Administrator s Guide. Similar information for recovery exists in the Disaster recovery restore procedures chapter in the PureDisk Administrator s Guide. Specific examples of different disaster recovery options are available. Please refer to the PureDisk storage pool disaster recovery strategy examples section in the PureDisk Administrator s Guide. For help using NetBackup in your disaster recovery planning, refer to the About using NetBackup to back up your PureDisk environment section in the PureDisk Administrator s Guide.

186 186 About PureDisk About PureDisk documentation About PureDisk documentation The PureDisk documentation set includes the manuals that apply to all PureDisk software implementations. This documentation set also includes the manuals that apply only to PureDisk when it is running on specific platforms. The following list describes the PureDisk manuals and contains notes regarding platform-specific information: Symantec NetBackup PureDisk Getting Started Guide. This manual introduces the PureDisk product and describes general PureDisk requirements that apply to all platforms. Information in this manual regarding hardware requirements does not apply to the PureDisk storage pools that are configured on deduplication appliances. Symantec NetBackup PureDisk Client Installation Guide. Applies to PureDisk on all platforms. Symantec NetBackup PureDisk Backup Operator's Guide. Applies to PureDisk on all platforms. Symantec NetBackup PureDisk Administrator's Guide. The following information in this manual does not apply to the PureDisk storage pools that are configured on deduplication appliances: Information regarding how to apply patches, manage patches, perform upgrades, and so on. The Deduplication Appliance Software release notes describe how to apply and manage software upgrades. Reconfiguration tasks that you perform with the Storage Pool Configuration Wizard. All information regarding high availability. All information regarding storage pool authority replication (SPAR). All information regarding disaster recovery. Symantec NetBackup PureDisk Best Practices Guide. Applies to PureDisk on all platforms. Symantec NetBackup PureDisk Command Line Interface Guide. Applies to PureDisk on all platforms. Symantec NetBackup PureDisk Deduplication Option Guide. Applies to PureDisk on all platforms. PureDisk Storage Pool Installation Guide. This manual pertains to PureDisk remote office storage pools only. It does not contain any information that pertains to PureDisk on a deduplication appliance.

187 About PureDisk About PureDisk documentation 187 The Deduplication Appliance Software online Help contains information from the preceding PureDisk manual set. The appliance exceptions that are noted in the preceding list also pertain to the online Help. The PureDisk documentation website is as follows: You can obtain all PureDisk documentation in PDF format from the following website: NetBackup Product Family Third-party Legal Notices also appears on the preceding website. This document lists the third-party software that is included in the Deduplication Appliance Software and contains attributions for the third-party software.

188 188 About PureDisk About PureDisk documentation

189 Appendix B About Call Home upload information This appendix includes the following topics: About the appliance hardware information that is uploaded About the NetBackup 5020 communications connections About the appliance hardware information that is uploaded Hardware monitor information manufacturer serial modelno Symantec SYMC The Call Home feature is designed to upload hardware and software information to a Symantec Call Home server. The hardware information that is gathered covers the appliance and any enclosures that are configured. The following is an example of the appliance hardware information that is bundled together into a report and uploaded to the Call Home server. Firmware Information ID Name Version State Intel Embedded Server RAID SCU I OK

190 190 About Call Home upload information About the appliance hardware information that is uploaded Technology II Intel (R) RAID Controller OK RS25SB Intel_X520 0x OK Intel_I OK QLogic (90d5) OK QLogic (90d5) OK BIOS SE5C600.86B OK Power Supply Information ID Status Wattage LowWaterMark HighWaterMark State Failure detected 0 Watts 1 Watts Watts Failure Presence detected Watts 1 Watts Watts OK CPU Information ID Status Voltage LowWaterMark HighWaterMark State Presence detected Volts Volts Volts OK Presence detected Volts Volts Volts OK Fan Information Disk Information ID Slot Status Foreign Capacity Type Serial Number Enclosure State Number state ID Failed None 0 KB [0x0 Unknown N/A Failure Sectors] Online, TB SEAGATE 2 1 Spun Up None [0xe8e088b0 SAS ST2000NM0001 N/A OK Sectors] 0002Z1P13SFL

191 About Call Home upload information About the appliance hardware information that is uploaded No disk OK No disk OK No disk OK No disk OK No disk OK No disk OK No disk OK No disk OK No disk OK No disk OK FibreChannel HBA Information ID Status Mode Port WWN Slot Speed Remote Ports State Linkdown Target 21:00:00:24:FF:39:FD:64 2 unknown - OK Linkdown Initiator 21:00:00:24:FF:39:FD:65 2 unknown - OK Linkdown Target 21:00:00:24:FF:39:FD:7A 5 unknown - OK Linkdown Initiator 21:00:00:24:FF:39:FD:7B 5 unknown - OK Temperature Information ID Type Temperature LowWaterMark HighWaterMark State Intake Vent 27 degrees 0 degrees C 55 degrees C OK Temperature C Outtake Vent 28 degrees 0 degrees C 85 degrees C OK Temperature C

192 192 About Call Home upload information About the appliance hardware information that is uploaded 3 Power Supply 1-0 degrees C 70 degrees C Critical Temperature Warning Power Supply 2 26 degrees 0 degrees C 70 degrees C OK Temperature C Adapter Information BBU Learn BBU ID Adapter model Status Voltage Temperature Cycle charge State Active Intel (R) RAID BBU Failure Controller RS25SB008 Absent Intel Embedded BBU 2 Server RAID Absent Failure Technology II Network Card Information ID Port Card Model Serial Number Port MAC Address Link State Name Speed State eth0 Intel_I c-38-ff-ff-67-1e Mb/ 00:1E:67:38:9C:16 Down OK s eth1 Intel_I c-38-ff-ff-67-1e Mb/ 00:1E:67:38:9C:17 Down OK s eth2 Intel_I c-38-ff-ff-67-1e Mb/s 00:1E:67:38:9C:18 Up OK eth3 Intel_I c-38-ff-ff-67-1e Mb/ 00:1E:67:38:9C:19 Down OK s eth4 Intel_X e9-38-ff-ff-67-1e Mb 00:1E:67:38:E9:50 Down OK /s eth5 Intel_X e9-38-ff-ff-67-1e Mb 00:1E:67:38:E9:51 Down OK /s PCI Information

193 About Call Home upload information About the appliance hardware information that is uploaded ID Slot Details State EMPTY OK Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to OK PCI Express HBA (rev 02) EMPTY OK RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS TB OK (rev 03) Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to OK PCI Express HBA (rev 02) EMPTY OK Alert Information ID Time Type Source Description T04:32:24 Drive Slot HDD 0 Drive Fault Asserted Status T04:32:18 Drive Slot HDD 0 Drive Fault Deasserted Status T04:50:05 Drive Slot HDD 0 Drive Fault Asserted Status T12:26:48 Drive Slot HDD 1 Drive Present Asserted Status T12:26:48 Drive Slot HDD 0 Drive Present Asserted Status

194 194 About Call Home upload information About the NetBackup 5020 communications connections About the NetBackup 5020 communications connections The appliance includes several ports that can be useful if you want to expand its capabilities. The following figure and table describe how you can use each port: Table B-1 Port or jack 1. USB 2.0 ports (2) Appliance communications connections Description Use to connect a mouse, keyboard, and other USB2 devices to the appliance. 2. System serial port 3.VGA port 4. 1GB/s Ethernet port (NIC2) 5. 1GB Ethernet port (NIC1) 6. IPMI port 7. Ethernet dual-port NIC Use to expand the functions of the operating system (OS) and third-party software. Should only be used at the direction of Symantec Technical Support. Use to connect a monitor or display to the appliance. Service network port that is used to connect the appliance to the application server (AS). Data in the AS is backed up and recovered to the appliance through this port. Use to connect a laptop to the appliance. Management network port that is used to manage and maintain the appliance through the network. On NetBackup 5020 appliances, this port is a 10 GB/s service network port. Use it to connect the appliance to the application server (AS). Data in the AS is backed up and recovered to the appliance through this port. On NetBackup 5000 appliances, this port is a 1 GB/s port.