Veritas NetBackup. Release 3.1. Document Revision 1

Transcription

1 Veritas NetBackup Appliance iscsi Guide Release 3.1 Document Revision 1

2 Veritas NetBackup Appliance iscsi Guide Release Document Revision 1 Legal Notice Copyright 2017 Veritas Technologies LLC. All rights reserved. Veritas, the Veritas Logo, and NetBackup are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third party software for which Veritas 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 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 Veritas Technologies LLC 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. VERITAS TECHNOLOGIES LLC 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 , et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on premises or hosted services. 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 Veritas Technologies LLC 500 E Middlefield Road Mountain View, CA Technical Support Technical Support maintains support centers globally. All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policies. For information about our support offerings and how to contact Technical Support, visit our website: You can manage your Veritas account information at the following URL: If you have questions regarding an existing support agreement, please the support agreement administration team for your region as follows: Worldwide (except Japan) Japan CustomerCare@veritas.com CustomerCare_Japan@veritas.com Documentation The latest documentation is available on the Veritas website: Documentation feedback Your feedback is important to us. Suggest improvements or report errors or omissions to the documentation. Include the document title, document version, chapter title, and section title of the text on which you are reporting. Send feedback to: APPL.docs@veritas.com You can also see documentation information or ask a question on the Veritas community site: Veritas Services and Operations Readiness Tools (SORT) Veritas Services and Operations Readiness Tools (SORT) is a website that provides information and tools to automate and simplify certain time-consuming administrative tasks. Depending on the product, SORT helps you prepare for installations and upgrades, identify risks in your datacenters, and improve operational efficiency. To see what services and tools SORT provides for your product, see the data sheet:

4 Contents Chapter 1 Overview... 6 About iscsi... 6 About iscsi initiator and targets... 7 Supported iscsi features... 7 Overview of the iscsi topology... 8 About the iscsi Qualified Name (IQN)... 9 Chapter 2 Understanding the appliance configurations NetBackup 5240 appliance I/O configuration H NetBackup 5340 compute node I/O configurations QLE8442 dual-port 10Gb Ethernet/iSCSI capable card with SFP+ modules Chapter 3 Understanding NetBackup for VMware About NetBackup for VMware Overview of the VMware backup process Transport modes options (VMware) Chapter 4 Configuring iscsi Configuring the appliance for iscsi Setting the IQN for the initiator Viewing the interface properties Configuring the interface properties Removing and resetting the interface properties About CHAP authentication Discovering targets by using the portal address About isns Discovering targets by using isns Connecting to a target Disconnecting the sessions with a target Viewing the targets... 31

5 Contents 5 Chapter 5 Troubleshooting iscsi issues and some best practices Gathering device logs with the DataCollect command About syslogd messages About iscsi alerts Best Practices... 36

6 Chapter 1 Overview This chapter includes the following topics: About iscsi About iscsi initiator and targets Supported iscsi features Overview of the iscsi topology About the iscsi Qualified Name (IQN) About iscsi iscsi is a way of connecting storage devices over a network by using TCP/IP. iscsi was developed to enable transmission of SCSI commands over the existing Internet Protocol (IP) network by using the TCP/IP protocol. iscsi offers the possibility of delivering both messaging traffic and block-based storage over IP networks without installing a separate Fibre Channel network. The protocol allows clients (called initiators) to send SCSI commands to SCSI storage devices (targets) on remote servers. A target is a storage resource located on an iscsi server (generally, one of possibly many instances of iscsi storage nodes running on that server). To communicate with each other, iscsi initiators and targets establish iscsi sessions. The following NetBackup Appliances and configurations support iscsi. NetBackup 5240 configuration H NetBackup 5340 configurations A, B, C, D, and E

7 Overview About iscsi initiator and targets 7 About iscsi initiator and targets iscsi is a way to share storage over a network and works at the block device level. For iscsi communication, the following components talk with each other: Initiator Target The clients which access the iscsi storage are called initiators. This iscsi Initiator can connect to a server (the iscsi target). In doing so, the iscsi Initiator sends SCSI commands to the iscsi target. These SCSI commands are packaged in IP packets for this purpose. An iscsi target device receives iscsi commands and shares the storage. The storage can be a physical disk, or an area representing multiple disks or a portion of a physical disk. A storage array is a typical iscsi target. Supported iscsi features See the following pointers to understand how iscsi is supported with NetBackup appliances: iscsi is supported on configuration H of the 5240 appliance and in all configurations of the 5340 compute node. Configuration H of the NetBackup 5240 appliance always functions as an initiator. See NetBackup 5240 appliance I/O configuration H on page 10. The NetBackup 5340 configurations function as initiators. See NetBackup 5340 compute node I/O configurations on page 11. iscsi supports VMware backups only. It supports the NetBackup for VMware feature. See About NetBackup for VMware on page 15. For this release, the iscsi functionality commands are available on the NetBackup Appliance Shell Menu only. iscsi supports IPv4 addresses only. iscsi connections over IPv6 are not supported. In addition, the initiator and the target must be on the same Layer 2 network (L2). iscsi supports Dynamic Multipathing (DMP). You can connect by multiple paths to the same target. The backups or restores over iscsi can continue as long as one path is available.

8 Overview Overview of the iscsi topology 8 Using an isns server (Internet Storage Name Service) for discovering targets is supported. See About isns on page 26. A VLAN can be configured on either the network interface or the iscsi interface. If VLAN is configured on both the network and iscsi interface, the VLAN for the network interface is effective on both the interfaces. Note that when VLAN is configured on both the network and iscsi interface on different subnets, the configuration is not supported. Network interface iscsi interface Description IP VLAN IP VLAN Subnet X None Subnet X None Supported Subnet X None Subnet Y VLAN A Supported Subnet X VLAN B Subnet X VLAN B Supported Subnet X VLAN B Subnet Y VLAN B Not Supported Only a Small Form-Factor Pluggable (SFP+) module is supported in the 10Gb Ethernet/iSCSI card. You receive an alert if an unsupported SFP module is detected in the 10Gb Ethernet/iSCSI card (if alerts are configured). For the latest NetBackup Appliance compatibility information, refer to the Hardware Compatibility List on the following website: Overview of the iscsi topology The appliance can operate as the VMware backup host and take VMware backups by using iscsi. In this topology, the appliance functions as an initiator and is connected to a storage array (target) on a TCP/IP network. The storage array can be connected to an ESX host over FC/LAN etc. The following illustration shows a NetBackup 5240 topology as an example. The topology for NetBackup 5340 is the same.

9 Overview About the iscsi Qualified Name (IQN) 9 Figure 1-1 iscsi topology SCSI commands Initiator (Configuration H of the NetBackup 5240 appliance) Appliance as the backup host uses NetBackup client software to back up virtual machines Data Transfer over TCP/IP Target (iscsi supporte storage array) ESX servers Virtual machines VM VM VM VM VM VM The virtual machines are backed up on the appliance over iscsi. About the iscsi Qualified Name (IQN) In an iscsi network, each iscsi element that uses the network has a unique iscsi name and is assigned an address for access. Each iscsi element, whether an initiator or target, is identified by a unique iscsi Qualified Name (IQN). The IQN is a logical name that is not linked to an IP address. The IQN has the following properties: It is unique. No two initiators or targets can have the same name. It can be up to 255 characters long. It can only contain numbers (0-9), letters (A-Z and a-z), colons (:), hyphens (-), and periods (.). A sample IQN format is iqn.yyyy-mm.naming-authority:unique name where: yyyy-mm is the year and month when the naming authority was established. naming-authority is usually reverse syntax of the Internet domain name of the naming authority. Unique name is any name you want to use, for example, the name of your host. The naming authority must make sure that any names assigned following the colon are unique. Example: iqn com.veritas:abc

10 Chapter 2 Understanding the appliance configurations This chapter includes the following topics: NetBackup 5240 appliance I/O configuration H NetBackup 5340 compute node I/O configurations QLE8442 dual-port 10Gb Ethernet/iSCSI capable card with SFP+ modules NetBackup 5240 appliance I/O configuration H The rear panel of the NetBackup 5240 appliance contains three PCIe riser card assemblies. PCIe riser card assemblies 1 and 2 each support three standard PCIe cards, while PCIe riser card assembly 3 supports two low profile PCIe cards. The slots are labeled 1 to 8. The following graphic shows the riser assemblies and the slot numbers. Figure 2-1 Rear panel riser assembly locations and PCIe slot assignments Riser Assembly 3 Riser Assembly 2 Riser Assembly

11 Understanding the appliance configurations NetBackup 5340 compute node I/O configurations 11 The NetBackup 5240 appliance supports multiple PCIe-based I/O configuration options. The following table shows the configuration H option that has the iscsi card in slot 2. Table 2-1 NetBackup 5240 appliance configuration H I/O configuration option 1 * ** 8 H - 10 GbE NIC 1, 2 10 GbE NIC 1, 2-8 Gb FC HBA 2 8 Gb FC HBA (iscsi) * 1 contains a factory installed PCIe RAID 6 controller when at least one NetBackup 5240 Storage Shelf is purchased with the NetBackup 5240 appliance. Otherwise, slot 1 is not populated. ** 7 contains the NetBackup 5240 Appliance's internal PCIe raid controller. This RAID controller is used to create the RAID 1 Array for the disk drives on which the appliance operating system is installed. The operating system drives are located in slots 0 and 1 of the front panel. PCIe card cable connection types: 1 Direct-Attach copper cable (also called a Twinaxial cable or Twinax) 2 Fiber optic cable See the NetBackup Appliance Product Description Guide for more details. NetBackup 5340 compute node I/O configurations The rear panel of the NetBackup 5340 compute node contains three PCIe riser card assemblies. PCIe riser card assemblies 1 and 2 each support three standard PCIe cards. PCIe riser card assembly 3 supports two low profile PCIe cards. The slots are labeled 1 to 8. In the following illustration the riser assemblies are outlined in red. The PCIe slots are identified. Figure 2-2 Rear panel riser assembly locations and PCIe slot assignments

12 Understanding the appliance configurations NetBackup 5340 compute node I/O configurations 12 The NetBackup 5340 compute node supports multiple PCIe-based I/O configuration options. The following table shows configurations A, B, C, D, and E. Each configuration supports iscsi. Table 2-2 Standard available PCIe-based I/O configurations for the NetBackup 5340 compute node I/O configuration option 1 * * A QLE2692 QLE8442 QLE8442 QLE2692 QLE8442 QLE8442 Reserved QLE Gb FC 10GbE NIC 1, 3 10GbE NIC 1, 3 16Gb FC 10GbE NIC 1, 3 10GbE NIC 1, 3 10GbE NIC 1, 3 (iscsi capable) (iscsi capable) (iscsi capable) (iscsi capable) (iscsi capable) B QLE2692 QLE8442 QLE8442 QLE2692 QLE8442 QLE2562 Reserved QLE Gb FC 10GbE NIC 1, 3 10GbE NIC 1, 3 16Gb FC 10GbE NIC 1, 3 8Gb FC 10GbE NIC 1, 3 (iscsi capable) (iscsi capable) (iscsi capable) (iscsi capable) C QLE2692 QLE8442 QLE8442 QLE2692 QLE2562 QLE2562 Reserved QLE Gb FC 10GbE NIC 1, 3 10GbE NIC 1, 3 16Gb FC 8Gb FC 8Gb FC 10GbE NIC 1, 3 (iscsi capable) (iscsi capable) (iscsi capable) D QLE2692 QLE2562 QLE8442 QLE2692 QLE2562 QLE2562 Reserved QLE Gb FC 8Gb FC 10GbE NIC 1, 3 16Gb FC 8Gb FC 8Gb FC 10GbE NIC 1, 3 (iscsi capable) (iscsi capable)

13 Understanding the appliance configurations QLE8442 dual-port 10Gb Ethernet/iSCSI capable card with SFP+ modules 13 Table 2-2 Standard available PCIe-based I/O configurations for the NetBackup 5340 compute node (continued) I/O configuration option 1 * * E QLE2692 QLE2562 QLE2562 QLE2692 QLE2562 QLE2562 Reserved QLE Gb FC 8Gb FC 8Gb FC 16Gb FC 8Gb FC 8Gb FC 10GbE NIC 1, 3 (iscsi capable) * The 16Gb Fibre Channel HBA ports in slots 1 and 4 are used to connect the NetBackup 5340 compute node to the Veritas 5U84 Primary Storage Shelf. As a result, slots 1 and 4 do not support standard network I/O operations. PCIe card cable connection types: 1 Direct-Attach copper cable (also called a Twinaxial cable or Twinax) 2 Standard copper 3 Fiber optic cable QLE8442 dual-port 10Gb Ethernet/iSCSI capable card with SFP+ modules The QLE8442 is a dual-port 10GbE network interface card. It supports simultaneous LAN (TCP/IP) and SAN (Fibre Channel over Ethernet [FCoE] and iscsi) traffic at 10Gbps Ethernet (GbE) line rate speeds. The QLE8442 also provides very low host CPU usage by enabling full hardware offloads. Table 2-3 Item Bracket height QLE8442 dual-port 10Gb Ethernet card specifications Specification Full height Power consumption System interface type Speed and slot width 9.65 watts (nominal) PCIe v GT/s, 8-lane

14 Understanding the appliance configurations QLE8442 dual-port 10Gb Ethernet/iSCSI capable card with SFP+ modules 14 Table 2-3 Item Storage over Ethernet LED indicators QLE8442 dual-port 10Gb Ethernet card specifications (continued) Specification iscsi LINK/ACTIVITY Off = No link (cable disconnected) Continuously illuminated = Line on Blinking = Network activity Certifications Operating temperature Storage temperature Operational humidity Storage humidity Air flow FCC A, ICES A, UL, CE, VCCI, CISPR, KCC 0 to 55 C (32 TO 131 f) -40 to 65 C (-40 to 149 F) 7% to 55 C 93% maximum at 65 C C To purchase a QLE8442 dual-port 10Gb Ethernet card with SFP+ modules for your appliance, contact your Veritas sales representative, or your Veritas Partner representative. QLE8442 dual-port 10Gb Ethernet card with SFP+ modules SKU Number Description NETBACKUP APPLIANCE XX40 QLOGIC QLE GBPS DUAL PORT ETHERNET/ISCSI CRU with SFP modules included

15 Chapter 3 Understanding NetBackup for VMware This chapter includes the following topics: About NetBackup for VMware Overview of the VMware backup process Transport modes options (VMware) About NetBackup for VMware NetBackup for VMware provides backup and restore of the VMware virtual machines that run on VMware ESX servers. NetBackup for VMware takes advantage of VMware vstorage APIs for data protection. The backup process is off-loaded from the ESX server to a VMware backup host. NetBackup for VMware does the following: Performs off-host backup of virtual machines (NetBackup client software is not required on the virtual machine). Off-host backup reduces the backup processing load on the VMware host. Increases the backup speed as compared to standard file-order backup methods, if the virtual machine is heavily populated with small files. Automatically creates quiesced snapshots using VSS (Windows only). Creates quiesced snapshots on Linux if snapshot quiesce is enabled in the Linux guest OS. Uses snapshot technology to keep virtual machines 100% available to users. Supports VMware vsphere and vcloud Director.

16 Understanding NetBackup for VMware Overview of the VMware backup process 16 Performs full backups and incremental backups, including block-level incrementals. Backs up the full virtual machine. Backs up the virtual machines even when they are turned off. Can restore selected files from the backup. Overview of the VMware backup process The following table describes the phases in the NetBackup backup process. Table 3-1 Phase Phase 1 Phase 2 Phase 3 NetBackup backup process Description The NetBackup master server initiates the backup. The NetBackup client on the VMware backup host initiates a VMware snapshot on the virtual machine. Windows: VSS synchronizes the file system on the virtual machine. Linux: If snapshot quiesce is enabled in the Linux guest OS, the file system is synchronized on the virtual machine. (Contact your operating system vendor and VMware for additional information on how to enable snapshot quiesce.) Phase 4 Phase 5 The VMware server creates a snapshot on the virtual disk datastore. The NetBackup client reads the snapshot from the datastores and writes the data to the NetBackup storage unit. Transport modes options (VMware) The transport modes determine how the snapshot data travels from the VMware datastore to the VMware backup host. The appropriate mode depends in part on the type of network that connects the VMware datastore to the VMware backup host. By default, all modes are selected. NetBackup tries each transport mode in order, from top to bottom. It uses the first mode that succeeds for all disks in the virtual machine.

17 Understanding NetBackup for VMware Transport modes options (VMware) 17 Table 3-2 Transport Modes Mode san Description For unencrypted transfer over Fibre Channel (SAN) or iscsi. Note: On NetBackup appliances, the VMware backups happening over iscsi use the san transport mode. Note: This mode is not supported for the virtual machines that use VMware Virtual Volumes (VVols). hotadd Lets you run the VMware backup host in a virtual machine. Note: For the virtual machines that use VVols, the virtual machine and the backup host (hotadd) virtual machine must reside on same VVol datastore. For instructions on this transport mode and on installing the backup host in a VMware virtual machine, refer to your VMware documentation. nbd nbdssl For unencrypted transfer over a local network that uses the Network Block Device (NBD) driver protocol. This mode of transfer is usually slower than Fibre Channel. For encrypted transfer (SSL) over a local network that uses the Network Block Device (NBD) driver protocol. This mode of transfer is usually slower than Fibre Channel.

18 Chapter 4 Configuring iscsi This chapter includes the following topics: Configuring the appliance for iscsi Setting the IQN for the initiator Viewing the interface properties Configuring the interface properties Removing and resetting the interface properties About CHAP authentication Discovering targets by using the portal address About isns Discovering targets by using isns Connecting to a target Disconnecting the sessions with a target Viewing the targets Configuring the appliance for iscsi Before configuring your appliance for iscsi, ensure that the iscsi targets are configured in your environment. Check the documentation provided by the target vendor for more reference. Table 4-1 provides instructions to configure and set up iscsi on the appliance.

19 Configuring iscsi Setting the IQN for the initiator 19 Table 4-1 Configuring iscsi on the appliance Step No. 1. Description Configure IQN for the initiator Reference See Setting the IQN for the initiator on page Configure the iscsi interface. The IP address must be configured. You may optionally configure other interface properties like Netmask, gateway etc. See Configuring the interface properties on page Discover the targets by using the portal address or the isns server. Connect to the target See Discovering targets by using the portal address on page 25. See Discovering targets by using isns on page 27. See Connecting to a target on page 29. Setting the IQN for the initiator This section explains how you can set the IQN for the NetBackup Appliance (initiator). To set the IQN 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Initiator Set IQN and enter the IQN as a parameter. Note the following about IQN: The IQN must be up to 255 characters long. The IQN can only contain numbers (0-9), letters (A-Z and a-z), colons (:), hyphens (-), and periods (.). Example: iqn com.veritas:abc 4 The following message is displayed: iscsi> Initiator Set IQN iqn.veritas.abc - [Info] The IQN has been updated to iqn.veritas.abc.

20 Configuring iscsi Viewing the interface properties 20 Viewing the interface properties appliance.iscsi > Interface Show This section lists the procedures for viewing the iscsi interface properties. To view the interface properties Showing the available interfaces... 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Interface Show and press Enter to view the iscsi interfaces. The following properties are displayed: Interface Name Network MAC Address IP Address Netmask Gateway MTU VLAN Interface Tag iscsi1 eth6 00:0e:1e:53:55: iscsi2 eth7 00:0e:1e:53:55: Configuring the interface properties This section lists the procedures for configuring interface properties like gateway, IPv4 address, Netmask, Maximum Transmission Unit (MTU), and the VLAN Tag for an ISCSI interface. The MTU controls the maximum transmission unit size for an Ethernet frame. It must be a number from 68 to Note that when you configure the MTU for an iscsi interface, the new MTU value is configured for both the iscsi interface and the network interface to which it is mapped. VLAN Tagging is the practice of inserting a VLAN ID into a packet header in order to identify which VLAN (Virtual Local Area Network) the packet belongs to. More specifically, switches use the VLAN ID to determine which ports, or interfaces, to send a broadcast packet to. A VLAN can be configured on either the network interface or the iscsi interface. If VLAN is configured on both the network and iscsi interface, the VLAN for the network interface is effective on both the interfaces.

21 Configuring iscsi Configuring the interface properties 21 To configure the IP address 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Interface IPAddress Set. 4 Enter the IP address and the iscsi interface name as parameters. Press Enter. Example: iscsi> Interface IPAddress Set iscsi1 [Info] The IP address has been configured for iscsi1. Note: The values used in the examples are sample placeholder values. To configure the Netmask 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Interface Netmask Set. 4 Enter the Netmask value and the iscsi interface name as parameters. Press Enter. Example: iscsi> Interface Netmask Set iscsi10 [Info] The Netmask has been configured for iscsi10. To configure the gateway 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu.

22 Configuring iscsi Configuring the interface properties 22 3 Type the command Interface Gateway Set. 4 Enter the gateway value and the iscsi interface name as parameters. Press Enter. Example: iscsi> Interface Gateway Set iscsi10 [Info] The gateway has been configured for iscsi10. To configure the Maximum Transmission Unit (MTU) 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Interface MTU Set. 4 Enter the MTU value and the iscsi interface name. The MTU must be a number from 68 to The new MTU value applies to the iscsi interface and also the network interface that it maps to. Example: iscsi> Interface MTU Set 3000 iscsi10 The new MTU value applies to both iscsi1 and also network interface eth6. Do you want to continue?(yes/no)[no]:yes [Info] The MTU has been configured for iscsi10. To configure the VLAN tag 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu.

23 Configuring iscsi Removing and resetting the interface properties 23 3 Type the command Interface VLAN Set. 4 Enter the VLAN ID and the iscsi interface name as parameters. Press Enter. The VLAN ID must be a number from 1 to Example: iscsi> Interface VLAN Set 75 iscsi10 [Info] The VLAN tag has been configured for iscsi10. Removing and resetting the interface properties This section lists the procedures for removing all the interface properties except MTU. It also contains the procedure to reset MTU to the default value (1500). The MTU cannot be removed and can only be reset to its default value. To remove the interface properties 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Use the following commands to remove the specific properties: Type the command Interface Gateway Remove and enter an iscsi interface name. This command removes the gateway from the specified interface. Example: iscsi> Interface Gateway Remove iscsi1 [Info] The Gateway has been removed from iscsi1. Type the command Interface IPAddress Remove and enter an iscsi interface name. The command removes the IP address from the specified interface. Example: iscsi> Interface IPAddress Remove iscsi1 [Info] The IP address has been removed from iscsi1. Type the command Interface Netmask Remove and enter an iscsi interface name.

24 Configuring iscsi About CHAP authentication 24 The command removes the Netmask from the specified interface. Example: iscsi> Interface Netmask Remove iscsi1 [Info] The Netmask has been removed from iscsi1. Type the command Interface VLAN Remove and enter an iscsi interface name. The command removes the VLAN tag from the specified interface. Example: iscsi> Interface VLAN Remove iscsi1 [Info] The VLAN tag has been removed from iscsi1. To reset the MTU 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Interface MTU Reset and enter an iscsi interface name. Note that the command resets MTU to the default value (1500) on both the iscsi interface and the network interface to which it maps. Example: iscsi > Interface MTU Reset iscsi1 The MTU will be reset to 1500 for both iscsi1 and also the network interface eth6. Do you want to continue?(yes/no)[no] :yes [Info] The MTU has been reset to About CHAP authentication The authentication method that is used for appliances is called Challenge Handshake Authentication Protocol (or CHAP). The CHAP authentication can be applied to the following commands or actions: Discovering a target Connecting to the target

25 Configuring iscsi Discovering targets by using the portal address 25 During the initial stage of an iscsi session, the appliance (initiator) sends a login request to the storage system to begin an iscsi session. The storage system will then either permit or deny the login request, or determine that a login is not required. If authentication is enabled on the target, the credentials must be authenticated and the session established before the server can access the storage resources. The server compares the value from the client and, if the information matches, grants the session. If the response fails, the session is denied, and the request phase starts over. The initiator logs in using a CHAP user name and password. You can specify a CHAP password or generate a random password. To set up and configure CHAP authentication, see the target vendor documentation. Discovering targets by using the portal address This section provides instructions for discovering iscsi targets by using the target portal address. The target portal address is the hostname or IPv4 address that is associated with the target. The format of the target portal address is <IPv4 Address/hostname>:[<port>]. Example: or abc:3260 where 3260 is the default port. You must first discover a target in order to connect to it. To discover a target by using the target portal address 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Target Discover Portal 4 Enter the target portal address and the iscsi interface name that you have configured as parameters. Note the following considerations: The target portal address must be of the following format: <IPv4 address/hostname>[:port]. The host name can be a short name or a fully qualified domain name. Example: or abc:3260

26 Configuring iscsi About isns 26 The iscsi interface name can only contain numbers (0-9), letters (A-Z and a-z), colons (:), hyphens (-), under scrores (_) and periods (.) It must begin with numbers (0-9), letters (A-Z and a-z) and underscores (_) only. 5 Run the Target Discover Portal <Portal Address> <Interface Name> command. You are asked to provide a username and password. Type yes if your target requires authentication. The targets that are available on the specified portal address and interface are discovered and displayed in the following manner: Does your target require a username and password? (yes,no)[no]:no Showing the discovered targets No. Target IQN Target Portal Address Interfaces iqn veritas:abc :3260 iscsi1, iscsi iqn veritas:xyz :3260 iscsi1, iscsi iqn veritas:host :3260 iscsi1, iscsi Note: If you run the iscsi > Target Discover Portal or iscsi > Target Discover isns command again after the targets are connected, it overrides the existing connection settings like target credentials. If the target requires authentication, you will need to enter the target credentials again when the existing sessions are reconnected. The existing sessions need to be reconnected if the appliance restarts or when you change the IQN for the appliance or when the iscsi processes are restarted etc. About isns An isns server uses the Internet Storage Name Service protocol to maintain information about active iscsi devices on the network, including their IP addresses, iscsi node names, and portal groups. The isns protocol enables automated discovery and management of iscsi devices on an IP storage network. An iscsi initiator like the NetBackup appliance can query the isns server to discover iscsi target devices.

27 Configuring iscsi Discovering targets by using isns 27 You can use an isns (Internet Storage Name Service) server to discover targets. Configuring the isns server eliminates the need for configuring every initiator for every target. When numerous hosts exist on a network, configuring an isns server saves time. An isns server provides a central management point for the group by dynamically maintaining up-to-date information about the iscsi target names for group volumes. If you are using an isns server, there is no need to discover targets by using the specific target names in the command. The following diagram explains the interaction between the appliance and the isns server. Find list of targets or credentials from the isns server isns server Connect to target NetBackup appliance (Initiator) iscsi target array Discovering targets by using isns This section provides instructions for discovering iscsi targets by using the Internet storage name service (isns) method. Use this method if you have at least one isns server on your network. This method enables the iscsi initiator to discover targets that are registered to the isns server. For this method, you must supply the isns server address and/or port. The iscsi initiator can then query the specified isns server to discover targets. The default port for an isns server is You can connect to a target only after discovering it. Review the following considerations: If you run the iscsi > Target Discover Portal or iscsi > Target Discover isns command again after the targets are connected, it overrides the existing connection settings like target credentials. If the target requires authentication, you will need to enter the target credentials again when the existing sessions are reconnected. The existing sessions need to be reconnected if the appliance

28 Configuring iscsi Discovering targets by using isns 28 restarts or when you change the IQN for the appliance or when the iscsi processes ae restarted etc. When targets are discovered by using isns on two iscsi interfaces like first run the Target Discover isns command for iscsi1 and then iscsi2, only the recent record is displayed by the Target Show All command. For example the Interfaces column in the Target Show All command may not show both the interfaces (iscsi1, iscsi2) for some targets. It actually shows the interface from the most recent command (iscsi2 in this case) for some targets. To discover iscsi targets by using an isns server Note: An isns server must already be set up and available on the network before running the following procedure. 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Target Discover isns. 4 Enter the address of the isns server and the iscsi Interface name that you have configured as parameters. The isns address must be of the following format <IPv4 address/hosname>[:port]. The host name can be a short name or a fully qualified domain name. The default port is Example: or abc:3205

29 Configuring iscsi Connecting to a target 29 The iscsi interface name can only contain numbers (0-9), letters (A-Z and a-z), colons (:), hyphens (-), under scrores (_) and periods (.) It must begin with numbers (0-9), letters (A-Z and a-z) and underscores (_) only. 5 Run the Target Discover isns <isns address> <Interface name> command to discover all the iscsi targets that are registered with the isns server on the specific interface. You are asked to provide a username and password. Type yes if your target requires authentication. Note: When CHAP authentication is enabled on a target device and targets are discovered by using isns, the iscsi > Target Discover command may not prompt for target credentials. Does your target require a username and password? (yes,no)[no]:no Showing the discovered targets No. Target IQN Target Portal Address Interfaces iqn veritas:abc :3260 iscsi1, iscsi iqn veritas:xyz :3260 iscsi1, iscsi iqn veritas:host :3260 iscsi1, iscsi Connecting to a target After initiator and target connections are discovered, iscsi initiators must be logged on to targets to establish connections and transfer data over iscsi. Logons are persistent and connections are automatically restored if servers restart (unless the user logs off from the target). To connect an initiator to a single target, specify the IP address of the portal and the target IQN.

30 Configuring iscsi Disconnecting the sessions with a target 30 To connect to a target 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Target Connect. 4 Enter the IQN and portal address of the discovered target. A user name is required if authentication is enabled on the target. Note the following about IQN, portal address, and user name: The IQN can only contain numbers (0-9), letters (A-Z and a-z), colons (:), hyphens (-), and periods (.) Example: iqn com.veritas:storage.lun1 The target portal address must be of the following format: <IP address/hostname>[:port]. Only IPv4 addresses are supported. The host name can be a short name or a fully qualified domain name. Example: or abc:3260 The user name can only contain numbers (0-9), letters (A-Z and a-z), hyphens (-), underscrores (_), and periods (.). It must begin with numbers (0-9), letters (A-Z and a-z), and underscores (_) only. Example: john.smith 5 Run the command to connect to the target. You can connect to one discovered target at a time. Disconnecting the sessions with a target You can use the iscsi > Target Disconnect command to disconnect sessions with the target that has the specific IQN and portal address. Once you run this command, all the sessions that are connected to this target will get disconnected. You can disconnect sessions with one target at a time. Note: This command takes more time to complete if workloads are running on the iscsi interface. To disconnect the sessions with a target 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu.

31 Configuring iscsi Viewing the targets 31 3 Type the command Target Disconnect. 4 Enter the IQN and portal address of the target that you want to disconnect. Note the following about IQN and portal address: The IQN can only contain numbers (0-9), letters (A-Z and a-z), colons (:), hyphens (-), and periods (.) Example: iqn com.veritas:storage.lun1 The target portal address must be of the following format: <IPv4 address/hostname>[:port]. The host name can be a short name or a fully qualified domain name. Example: or abc: Run the command to disconnect sessions with the specific target. Type yes when the following prompt appears: Do you want to disconnect the target session?[yes, no](no):yes [Info] The target session has been disconnected. Viewing the targets Showing the connected targets... This section provides instructions on how you can view the targets. You can use the iscsi > Target Show command to view all the discovered targets or the connected targets. To view the connected targets 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Target Show Connected and press Enter. 4 The list of connected targets is displayed in the following manner: No. Session ID Target IQN Target Portal Address Status iqn veritas:abc :3260 Online The Status of the session can be either Online or Offline. The Status can be Offline if a cable is pulled or if there are network connectivity issues.

32 Configuring iscsi Viewing the targets 32 Showing all the targets... To view all the available targets 1 Open a Secure Shell (SSH) session to log on to the appliance as an administrator. 2 Navigate to the Main_Menu > Settings > iscsi menu. 3 Type the command Target Show All and press Enter. 4 A list of all the discovered targets is displayed in the following manner: No. Target IQN Target Portal Address Interfaces iqn veritas:abc :3260 iscsi iqn veritas:xyz :3260 iscsi iqn veritas:host :3260 iscsi Note: When targets are discovered by using isns on two iscsi interfaces, only the recent record is displayed by the Target Show All command. For example, if you run the Target Discover isns command for iscsi1 and then iscsi2, the Interfaces column in the Target Show All command may not show both the interfaces (iscsi1, iscsi2) for some targets. It actually shows the interface from the most recent command (iscsi2 in this case) for some targets.

33 Chapter 5 Troubleshooting iscsi issues and some best practices This chapter includes the following topics: Gathering device logs with the DataCollect command About syslogd messages About iscsi alerts Best Practices Gathering device logs with the DataCollect command You can use the DataCollect command from the Main > Support shell menu to gather device logs. You can share these device logs with the Veritas Support team to resolve device-related issues. The DataCollect command collects the following logs: Release information Disk performance logs Command output logs iscsi logs

34 Troubleshooting iscsi issues and some best practices About syslogd messages 34 Note: The iscsi logs can be found in /var/log/messages and /var/log/iscsiuio.log. CPU information Memory information Operating system logs Patch logs Storage logs File system logs Test hardware logs AutoSupport logs Hardware information Sysinfo logs To gather device logs with the DataCollect command 1 Log on to the NetBackup Appliance Shell Menu. 2 From the Main > Support view, type the following command to gather device logs. DataCollect The appliance generates the device log in the /tmp/datacollect.zip file. 3 Copy the DataCollect.zip to your local folders using the Main > Support > Logs > Share Open command. 4 You can send the DataCollect.zip file to the Veritas Support team to resolve your issues. About syslogd messages You may see the following messages appear on the NetBackup Appliance Shell Menu: Message from syslogd@host at Sep 12 10:09:14... iscsid: Message from syslogd@host at Sep 12 10:13:27... iscsid:

35 Troubleshooting iscsi issues and some best practices About iscsi alerts 35 Message from at Sep 12 10:17:53... iscsid: These messages may appear at different times on the NetBackup Appliance Shell Menu. They may appear when you are running an iscsi command, in the middle of a command output, or even when the console is idle. These messages are harmless and should be ignored. About iscsi alerts If you have configured alerts for a specific appliance, you can also receive iscsi alerts (as applicable). An iscsi alert is generated in the following situations: An iscsi session with the target gets disconnected (V ) An iscsi session with the target storage server is offline (V ) An unsupported Small Form-Factor Pluggable (SFP+) module is detected in a 10 Gb Ethernet/iSCSI card (V ) The following are sample iscsi alerts: An iscsi session with the target has been disconnected. Time of event: :34:13 (-07:00) UMI Event code: V Component Type: Connections Component: <Target IQN> <Portal address> <Interface name> Status: Disconnected State: ERROR Additional information about this error is available at following link: V An iscsi session with the target storage server is offline. Time of event: :34:13 (-07:00) UMI Event code: V Component Type: Connections Component: <Target IQN> <Portal address> <Interface name> Status: Offline State: ERROR Additional information about this error is available at following link: V The SFP+ module that is currently installed in the 10Gb Ethernet/iSCSI card is not supported. Time of event: :31:42 (-07:00) UMI Event code: V

36 Troubleshooting iscsi issues and some best practices Best Practices 36 Component Type: Ethernet Component: PCIe slot 6, port 1 SFP Status: Unsupported State: ERROR Additional information about this error is available at following link: V Best Practices The following are some recommendations and best practices for iscsi: Configure an IQN that is different from the default value. See Setting the IQN for the initiator on page 19. Configure alerts so that you can receive iscsi-related alerts. See the NetBackup Appliance Administrator's Guide for information about configuring alerts.