iSeries Manager communicates with the Nexsan iSeries via the Nexsan iSeries management port IP address. The Nexsan iSeries communicates with hosts via iSCSI portals which are configured via iSeries Manager. iSeries Manager automatically discovers all disks and LUNs connected to the Nexsan iSeries storage ports. iSeries Manager enables multi-cluster management.
Initial Nexsan iSeries Configuration
The Nexsan iSeries has a default IP Address of 10.11.12.123. This allows you to set initial startup parameters via a telnet session.
Assigning a Management IP Address
The management IP address can be set via:
To initialize the Nexsan iSeries via telnet/SSH session
1. |
Change your computer’s IP Address to anything on the same subnet 10.11.12.* |
2. |
Connect to the management port on the Nexsan iSeries. |
4. |
Enter Username and Password: admin. |
You will be asked to accept or change the default values for:
3. |
Nexsan iSeries name. This name will appear in the iSeries Manager Navigation Pane. If you don’t enter a name, iSeries Manager will use the last section of its IP address. This name can be changed later via the Nexsan iSeries Properties tab if there is only one Nexsan iSeries present. |
4. |
Management port (Mgnt or ETH1). |
To initialize the Nexsan iSeries via an RS-232 serial connection
1. |
Connect the cable to the appropriate port on the management server, and open a Terminal session. Set the following parameters in the terminal: Bits per second = 115200, Flow Control = None, Emulation = Autodetect. |
Figure 3-1. Terminal Properties
2. |
Enter Username and Password: admin. |
3. |
Set the default IP Address. |
5. |
Set the default Nexsan iSeries name. This name will appear in the iSeries Manager Navigation Pane. If you don’t enter a name, iSeries Manager will use the last section of its IP address. This name can be changed later via the Nexsan iSeries Properties tab if there is only one Nexsan iSeries present. |
6. |
Set the default management port (Mgnt or ETH1). |
iSeries Manager User Login Profiles
Once you add a user profile, the default username and password is erased. |
|
|
The default user name for iSeries Manager is admin.User names can be any string up to 79 characters long. |
|
|
The default password for iSeries Manager is admin.Passwords must be at least 6 and not more than 12 characters long. |
To configure a user profile:
1. |
From the iSeries Manager menu bar, select Secure > iSeries Manager Users… |
The
Add User dialog box opens.
3. |
Enter the user name and password in the appropriate fields. |
The Add User dialog box closes. The new user name now appears in the Users window. You can sort the user names by clicking the sort arrow.
Figure 3-3. Users Window
Changing the User Password
To change the current user password:
1. |
From the iSeries Manager menu bar, select Secure > iSeries Manager Passwords… |
The Change Password window opens.
Figure 3-5. Change Password
2. |
Enter the old and new password and click OK. |
Nexsan iSeries & Cluster Configuration
A
cluster is a group of FC storage units and switches that function as one unit for virtualization. Clusters provide high availability in the event of Nexsan iSeries failover.
iSeries Manager enables you to make a cluster from two Nexsan iSeries and configure both at the same time. Additionally, a cluster can be made by adding a new Nexsan iSeries to an already configured stand-alone Nexsan iSeries and then synchronizing the cluster.
This section details the steps necessary for configuring a single, stand alone Nexsan iSeries. When additional steps must be taken for cluster configuration, they are noted . |
Adding a New Nexsan iSeries
All stand alone Nexsan iSeries must be added to iSeries Manager.
To add a new Nexsan iSeries:
1. |
From the Quick Launch:
Configure > Create System Entity > Storage Resource Group [Single Switch]… |
Figure 3-6. New Storage Resource Group (Single Switch)
The New Nexsan iSeries dialog box opens.
2. |
Enter the Nexsan iSeries configuration parameters in the dialog box. |
The IP address is mandatory. The remaining fields contain default values. |
Figure 3-7. New Nexsan iSeries
Table 3-1. Nexsan iSeries Management Parameters
|
|
|
|
|
Location in the navigation tree |
|
|
|
|
|
IP address of the management interface configured on Nexsan iSeries during initial setup. |
|
|
IP mask for the management interface |
|
|
UDP port on which SNMP manager-agent communications run |
|
|
UDP port on which the SNMP agent will issue traps |
|
|
Defined group granted read access to data |
|
|
Defined group granted write access to data |
|
|
Time in milliseconds before an SNMP session is considered closed. |
|
|
Number of times to try to re-establish an active SNMP session |
|
|
SNMP protocol version being used to establish iSeries Manager communications with the specified Nexsan iSeries |
|
|
|
|
|
IP address of first storage |
|
|
IP address of second storage |
3. |
The new Nexsan iSeries appears in the Navigation pane and is represented by two entities: a “ virtual entity” and a “ physical entity”. The menu options differ for the two different types of entities. The virtual entity is referred to as “cluster level”. |
Figure 3-8. Nexsan iSeries Entity (Cluster Level)
Figure 3-9. Nexsan iSeries Physical Entity
Setting Nexsan iSeries Properties
You can change Nexsan iSeries properties via the different tabs in the Properties Window (
Figure 3-12).
To display Nexsan iSeries properties:
1. |
From the Quick Launch:
select Configure > Configure Network. |
Figure 3-10. Properties (Nexsan iSeries Menu)
The Nexsan iSeries Properties dialog box opens.
2. |
Select the Nexsan iSeries from the drop down list box at the top. |
Figure 3-11. Select (Nexsan iSeries Menu)
The Nexsan iSeries Properties dialog box opens displaying different tabs.
3. |
Toggle between these tabs to configure the different Nexsan iSeries properties. |
Figure 3-12. Nexsan iSeries Properties
|
|
|
|
|
Name of the Nexsan iSeries |
|
|
Contact person for technical support |
|
|
Location of the contact person |
|
|
IP address of the Nexsan iSeries management interface |
|
|
IP mask for the management interface |
|
|
Date and time since the last Nexsan iSeries reset |
|
|
|
|
|
|
|
|
Nexsan iSeries connection status |
|
|
Description of Nexsan iSeries hardware and software |
You can set the local date and time on a Nexsan iSeries.
Alarms are time-stamped according to the computer clock that is running the iSeries Manager server. |
To set Nexsan iSeries date and time:
1. |
From the Nexsan iSeries Properties Window ( Figure 3-12), select the Properties tab. |
The Nexsan iSeries
Properties dialog box opens.
2. |
Select the year, month and day for the Nexsan iSeries ( Figure 3-13). |
3. |
Select the hour, minutes and seconds. |
4. |
Select AM or PM. Select AM for morning, PM for evening (12:00 AM=midnight, 12:00 PM=noon). |
Figure 3-13. Setting the Nexsan iSeries Date
To enable a host to communicate with the Nexsan iSeries, an IP address must be assigned to the port. After adding an IP address, configure an iSCSI portal on the IP address (see
Portals).
|
Each network port can have multiple IP addresses assigned to it. |
|
Nexsan iSeries 2000 has two 1Gb Ethernet network ports. All other Nexsan iSeries have three 1 Gb Ethernet network ports. |
If you are adding a network port IP address in a cluster, assign the IP address as active on one Nexsan iSeries and inactive on the second Nexsan iSeries. In the event of a Nexsan iSeries failover, the second Nexsan iSeries will activate its inactive IP addresses and begin exposing the IP address' target LUNs. |
To add network IP addresses:
1. |
From the Nexsan iSeries Properties Window ( Figure 3-12), select the IP tab. |
Figure 3-14. Add Network Port IP Parameters
3. |
Configure the Activity as active or inactive. |
5. |
Add this IP to the neighbor in the cluster by checking the checkbox. |
The new network port IP address is listed in the IP
tab.
Figure 3-15. Add Network Port IP Parameters
Table 3-3. Network Port Parameters
|
IP addresses configured as active on the first Nexsan iSeries will be configured as inactive on the second. |
|
In the event of failover, the inactivate IP addresses are activated on the functioning Nexsan iSeries to take over target LUN exposure. The IP address’s activity will be shown as switched. |
|
A portal is the combination of an interface IP address and a TCP port. You must assign iSCSI portals to enable communications between an iSCSI initiator and iSCSI target.
1. |
From the Nexsan iSeries Properties Window ( Figure 3-12), select the Portals tab. |
The Add Portal dialog box opens.
3. |
Select the IP address from the drop-down menu of existing IP address and enter the port number. Click OK. |
When you add an iSCSI portal to a Nexsan iSeries in a cluster, you need to add the portal to the second Nexsan iSeries as well. In the event of a Nexsan iSeries failover, this allows the second Nexsan iSeries to begin exposing the failed Nexsan iSeries target LUNs through the portal. |
4. |
When working in a cluster, click the Add portal to neighbor in cluster checkbox. |
The iSCSI portal is added to the Nexsan iSeries Properties tab.
Figure 3-16. Portal Values
Table 3-4. Portal Parameters
|
|
|
|
|
User-assigned IP address of an interface |
|
|
TCP port through which the iSCSI protocol passes (usually 3260) |
To delete an iSCSI portal:
1. |
In the Navigation pane, right click on the Nexsan iSeries and select Properties. |
The Nexsan iSeries
Properties dialog box opens (
Figure 3-12).
2. |
Toggle to the Portals tab. |
3. |
Select desired portal and click Delete. |
A dialog box appears asking if you want to delete selected portals. Click
Yes to confirm delete.
To enable communications between the Nexsan iSeries and IP networks located outside the Nexsan iSeries LAN, you must configure IP routing paths for each external network port.
|
Each Nexsan iSeries can have only one IP route designated to a specific external network, even if there is more than one possible physical path to that network. |
In a cluster, an IP route must be added to both Nexsan iSeries. In the event of a Nexsan iSeries failover, the second Nexsan iSeries will be able to establish communications through the route and expose the failed Nexsan iSeries target LUNs. |
1. |
From the Nexsan iSeries Properties Window ( Figure 3-12), select the IP Route tab. |
The Add IP Route dialog box opens.
Figure 3-17. Add IP Route Dialog Box
4. |
You can configure a default gateway for each port, including the management port, for routing all traffic not otherwise specified in the Nexsan iSeries routing table by using 0.0.0.0 for both the IP address and IP Mask. |
|
If you are working in a cluster, select ‘Add route to neighbor in cluster’ to add the route to the second Nexsan iSeries. |
|
Don’t select the checkbox if you want to exclude the route from the second Nexsan iSeries in the cluster. |
|
5. |
Click OK. The Add IP Route dialog box closes. The new IP route is listed in the IP Route tab ( Figure 3-18). |
Table 3-5. IP Routing Parameters
|
|
|
|
|
IP address of destination network Use IP address 0.0.0.0 to create a default gateway |
|
|
IP mask of destination network Use IP mask 0.0.0.0 to create a default gateway |
|
|
IP address of gateway router |
|
|
Network interface to open route through |
Figure 3-18. New IP Route Dialog Box
Creating a New Storage Resource Group (Cluster)
iSeries Manager enables you to easily configure network port IP addresses, iSCSI portals and IP routes simultaneously on both Nexsan iSeries in the cluster.
To add a new cluster from two new Nexsan iSeries:
1. |
From the Quick Launch:
Configure > Create System Entity > Storage Resource Group [Cluster]… |
Figure 3-19. New Storage Resource Group (Cluster)
The New Cluster dialog box opens.
Figure 3-20. New Cluster Dialog Box
2. |
Select location to create the cluster from the drop down list box. |
Creating a Cluster by Adding New Nexsan iSeries to Stand-Alone Nexsan iSeries
To make a cluster by adding a new Nexsan iSeries to a stand alone Nexsan iSeries:
1. |
In the Navigation pane, right click on the stand alone Nexsan iSeries (at cluster level), and select New > Nexsan iSeries … |
Both Nexsan iSeries in a cluster must have different aliases. If you add a second Nexsan iSeries with the same alias as the first Nexsan iSeries, no cluster will be created and no failover will be possible. The Nexsan iSeries will be listed in the iSeries Manager navigation pane with an orange exclamation mark (major alarm) and the Alarms window will display the alarm Nexsan iSeries are not neighbors. For iSeries Manager to create a cluster, you need to rename the second Nexsan iSeries via the Nexsan iSeries Properties. |
3. |
Define the Nexsan iSeries parameters for the second Nexsan iSeries (V2) as follows: |
If volumes or targets are created on one Nexsan iSeries operating alone, when another Nexsan iSeries is added, its database must be synchronized to the first Nexsan iSeries database. This can happen in three situations:
1. |
A new Nexsan iSeries is added to a configured and functioning Nexsan iSeries to form a cluster. |
2. |
An offline Nexsan iSeries in a cluster comes back online. |
3. |
CLI is used to make an isolated configuration change in one Nexsan iSeries. |
When an element is not synchronized, a yellow exclamation mark
may appear to the left of it (instead of a green check mark
) meaning that the alarm
Object not redundant is opened (see
Viewing Alarm Properties in Chapter 6).
To synchronize a cluster:
1. |
Select the cluster to synchronize. |
2. |
Right click and select Cluster Sync from the open menu ( Figure 3-21). |
Synchronization is instantaneous. During synchronization, a yellow exclamation mark
at the selected element's level (and below) are converted to green check marks
. The green check marks indicate that synchronization has completed.
Figure 3-21. Synchronize Selected
Setting Cluster Properties
The Cluster Properties dialog box (
Figure 3-23) allows you to configure general cluster parameters as well as view the Nexsan iSeries neighbor details.
Keep Alive, Suspicious and Faulty Intervals
The Nexsan iSeries sends out
keep alive signals to the other Nexsan iSeries (its neighbor) in a cluster. Suspicious and Faulty Intervals define the time interval for the Nexsan iSeries to not get Keep-alive signals from its neighbor and subsequently change its neighbors’ state to suspicious and faulty. The faulty state triggers a takeover procedure.
To configure keep alive, suspicious and faulty intervals:
1. |
In the Navigation pane, right click the cluster and select Properties... |
Figure 3-22. Properties Selected
2. |
Enter the desired intervals for Keep-alive Intervals, Suspicious Intervals, and Faulty Intervals. |
Figure 3-23. Cluster Properties Dialog Box
To view neighbor properties for a cluster:
1. |
In the Navigation pane, right click and select Properties… |
The
Cluster Properties dialog box opens.
Figure 3-24. Cluster Properties Dialog Box – Neighbors Tab
You can break a cluster by removing one of its neighbors (Nexsan iSeries). A Nexsan iSeries can be deleted from a cluster only after it is offline and iSeries Manager recognizes it as disconnected.
|
If you remove a Nexsan iSeries from a cluster, all of its configurations will be automatically transferred to its neighbor. However, the activity of the IP addresses will be active and not switched. |
|
If the removed Nexsan iSeries is re-connected, the IP addresses will not failback to the re-connected Nexsan iSeries. The IP addresses and their exposed targets will be exposed on both Nexsan iSeries. |
|
If the removed Nexsan iSeries is re-connected, then duplicate IP addresses will exist. |
|
1. |
Disconnect (turn off) the Nexsan iSeries from the system. |
The offline Nexsan iSeries is marked with a red exclamation mark
.
2. |
The remaining Nexsan iSeries is marked with a blue exclamation mark  to show that it has taken over exposing the offline Nexsan iSeries targets. |
3. |
Right click on the offline Nexsan iSeries and select Delete. |
Figure 3-25. Delete Offline Nexsan iSeries
4. |
A Dialog box opens asking if you want to delete the offline Nexsan iSeries. Click Yes. |
iSeries Manager begins removing the offline Nexsan iSeries from the iSeries Manager database.
5. |
The Navigation pane displays the remaining Nexsan iSeries in the cluster. |
Figure 3-26. Navigation Pane with Remaining Nexsan iSeries
Additional Nexsan iSeries Functionality
This section describes routine and optional Nexsan iSeries configuration operations.
FC Storage Port Configuration
The Nexsan iSeries default configuration for FC connections is Auto NL_Port in a public loop. Each storage port connected to an FC device can be reconfigured to change the connection speed, port type and connection mode.
To change FC/SCSI storage port parameters:
1. |
In the Navigation pane, select the Nexsan iSeries, right click and select Fibre Channel... |
Figure 3-27. Nexsan iSeries Fibre Channel Option
The Fibre Channel Parameters dialog box opens.
2. |
Toggle to the Interfaces tab. |
3. |
Configure parameters for Speed and Topology by selecting them from the drop down menus. |
Figure 3-28. Setting FC Port Speed
Certain Nexsan iSeries versions have advanced shutdown and wake up functionality. You can shutdown and wake up the Nexsan iSeries directly from iSeries Manager.
In order to use this feature, the management port must be set to Mgnt and not Eth1. |
To shutdown the Nexsan iSeries:
|
In the Navigation pane, right click on the Nexsan iSeries and select Shutdown. |
To wake up the Nexsan iSeries:
|
In the Navigation pane, right click on the Nexsan iSeries and select Wake on LAN. |
Figure 3-30. Wake on LAN
|
|
SFP parameters are available for the Nexsan iSeries 400i. |
You can view SFP parameters for FC Interfaces.
1. |
In the Navigation pane, right click on the Nexsan iSeries and select Properties… |
The Nexsan iSeries
Properties dialog box opens (
Figure 3-12).
2. |
Toggle to the Interfaces Tab. |
3. |
Select the desired interface, right click and select SFP ( Figure 3-31). |
The SFP Properties dialog box appears.
Figure 3-31. SFP Properties
Nexsan support for Ethernet Jumbo frames enables sending and receiving Ethernet frames with more than 1,500 bytes of payload (
MTU - Maximum Transmission Unit). Jumbo frames can carry up to 16,128 bytes of payload. Many, but not all, Gigabit Ethernet switches and Gigabit Ethernet network interface cards support jumbo frames, therefore when using jumbo frames make sure they are supported on all other elements in the iSCSI SAN.
To select MTU size for support of Jumbo Frames:
1. |
From the Interfaces tab, select and Ethernet interface, click in the MTU column and select the desired size. |
Figure 3-32. Jumbo Frames
Discovery of iSCSI Storage Devices
An iSCSI device can have many portals. Each portal can have remote targets associated with it. In order for the Nexsan iSeries to recognize a portal’s remote targets, you must define the IP Address of the iSCSI portal. Once defined, the Nexsan iSeries will automatically receive the list of remote targets attached to the portal.
There are two ways to discover remote iSCSI targets:
1. |
Discover all remote targets attached to an iSCSI device. |
2. |
Discover a specific remote target. |
To discover remote targets attached to an iSCSI device:
1. |
In the Navigation pane, right click on the Cluster and select iSCSI > Remote Portals. |
Figure 3-33. Remote Portals
The iSCSI Remote Portals window appears.
3. |
Enter IP Address and click OK. |
The Portals are added to the iSCSI Remote Portals window.
Figure 3-34. iSCSI Remote Portals
To discover a specific remote iSCSI target:
1. |
Select the Nexsan iSeries, right click and select New > iSCSI Remote Target… |
Figure 3-35. New Remote Target
The New iSCSI Remote target window appears.
Figure 3-36. iSCSI Remote Target
2. |
Configure Target alias and Target name for existing remote target. |
4. |
Select the Nexsan iSeries, right click and select iSCSI > Remote Target… |
Figure 3-37. Discover Remote Target
The iSCSI Remote Targets window appears.
5. |
Select the remote target, right click and select Add Portal. |
The Add Portal window appears.
6. |
Configure the IP Address, TCP Port and Group Portal Tag for the Portal. |
The Portal is added and remote target is now connected.
Figure 3-38. Configure Remote Target Portal
The Nexsan iSeries supports Internet Storage Name Service (iSNS) protocol for advertising its targets and portals on the iSNS server. This enables iSCSI initiators in the IP-SAN to locate the Nexsan iSeries targets automatically. Targets defined by the Nexsan iSeries Access Control List (ACL) as having controlled access are accessible only to those servers defined as having access to the target.
1. |
In the Navigation pane, right click on desired cluster and select iSNS… |
The
iSNS Servers dialog box opens.
Figure 3-39. Nexsan iSeries Selected
2. |
Click Add to open the New iSNS Server dialog box ( Figure 3-40). |
3. |
Enter the iSNS server IP address and click OK. |
The IP address is added to the iSNS Server dialog box.
Figure 3-40. New iSNS Server Dialog Box
RADIUS Server Configuration
A RADIUS server can be configured on the Nexsan iSeries to direct a CHAP challenge to the RADIUS server and eliminate the need to configure all user name + password pairs on the Nexsan iSeries. This decreases configuration time and increase overall network security.
To configure a Radius server:
1. |
From the Navigation pane, select the cluster or stand-alone Nexsan iSeries. Right click and select RADIUS from the open menu. |
Figure 3-41. Nexsan iSeries Selected
The RADIUS Servers dialog box opens.
The Add RADIUS Server dialog box opens.
3. |
Enter the new RADIUS server parameters. |
Figure 3-42. RADIUS Server Configuration
SNMP and trap port configurations are editable from this tab.
Table 3-6. SNMP Tab Parameters
|
|
|
|
|
UDP port on which SNMP manager-agent communications run |
|
|
UDP port on which the SNMP agent will issue traps |
|
|
defined group granted read access to data |
|
|
defined group granted write access to data |
|
|
time in milliseconds before an SNMP session is considered closed |
|
|
number of times to re-establish an active SNMP session |
|
|
SNMP protocol version being used to establish iSeries Manager communications with the specified Nexsan iSeries |
If your network topology includes a management station communicating with the Nexsan iSeries via CLI, you can enable Telnet communications to be transported through a port other than the standard Telnet port 23. If your Telnet communications connection to the Nexsan iSeries traverses a firewall, the standard Telnet port 23 may be blocked by the firewall as a security measure. The designated port can be opened in the firewall for dedicated Nexsan iSeries - management terminal communications.
To designate a telnet port:
1. |
In the Navigation pane, select the Nexsan iSeries. |
2. |
Right click on the Nexsan iSeries and select Properties. The Nexsan iSeries Properties dialog box opens ( Figure 3-12). |
4. |
Enter the new Telnet port and click OK. |
Figure 3-44. Setting Telnet Port
5. |
A message box opens stating that you must reset the Nexsan iSeries for the new Telnet port properties to take effect. Click OK. |
6. |
Reset the Nexsan iSeries (see Reset ). |
7. |
Check that the new Telnet port was applied by checking the Advanced tab in the Nexsan iSeries Properties dialog box ( Figure 3-44). |
Report LUNs Command (Discovering Storage Devices)
The Nexsan iSeries default algorithm for storage devices discovery uses the SCSI command
REPORT LUNS. Certain storage devices either do not support this command or do not respond according to the SCSI standard.
When working with devices that do not support the SCSI command REPORT LUNS, To discover these devices, the REPORT LUNs command must be disabled. If certain devices in the SAN are not being discovered by the Nexsan iSeries, disable or re-enable device discovery using REPORT LUNs. |
To disable/enable report LUNs command:
1. |
In the Navigation pane, right click on the Nexsan iSeries and select Properties. |
The Nexsan iSeries
Properties dialog box opens (
Figure 3-12).
3. |
Disable (uncheck) or re-enable (check) Report LUNs Discovery. |
Figure 3-45. Report LUNs Discovery Box
Rediscover Nexsan iSeries or Cluster Database
Rediscover causes iSeries Manager to refresh the information and update its database.
|
The command Rediscover rediscovers the database for the Nexsan iSeries or cluster. |
|
The command Storage Discovery rediscovers the physical disks attached to the Nexsan iSeries. |
|
To rediscover the database for the Nexsan iSeries or cluster:
1. |
Right click on cluster and select Rediscover ( Figure 3-46). |
2. |
A confirmation window appears asking if you want to rediscover the Nexsan iSeries. Click Yes. |
3. |
A status window appears at the bottom of the screen indicating that Discovery has started. |
Figure 3-47. Discovery Started
4. |
When all attached storage devices, system configurations and virtual volumes have been discovered, the status window indicates that the operation has completed. |
Figure 3-48. Discovery Completed
Storage Discovery rediscovers the physical disks attached to the Nexsan iSeries.
To rediscover the physical disks attached to the Nexsan iSeries:
1. |
Right click on cluster and select Storage Discovery ( Figure 3-49). |
Figure 3-49. Storage Discovery
2. |
A confirmation window appears asking if you want to initiate the storage discovery. Click Yes. |
You can reset the Nexsan iSeries from iSeries Manager. All configuration databases will be maintained on the Nexsan iSeries, including network port aliases and all configured volumes and targets.
In the case of a cluster, Reset will cause the second Nexsan iSeries to takeover. |
To reset a Nexsan iSeries:
1. |
In the Navigation pane, select the Nexsan iSeries. |
2. |
Right click on the Nexsan iSeries and select Reset. |
Figure 3-50. Reset Selected From Nexsan iSeries Menu
3. |
A confirmation window appears asking if you want to Reset the Nexsan iSeries. Click Yes. |
The status bar displays Resetting Nexsan iSeries
while the Nexsan iSeries
is being reset.
4. |
As part of the reset process, iSeries Manager rediscovers the Nexsan iSeries. After the discovery process has completed, you can resume work. The status bar will display Ready. |
Figure 3-51. Ready Status
If the reset Nexsan iSeries is part of a cluster, you may have to synchronize the cluster. See Synchronizing a Cluster. |
Removing Nexsan iSeries from a Cluster
Removing the Nexsan iSeries will remove all management configurations for the Nexsan iSeries from iSeries Manager (see
Breaking a Cluster).
Nexsan iSeriesStorage Service Level Assurance (SLA)
Storage Service Level Assurance (SLA) controls storage traffic by categorizing all iSCSI targets that are exposed on a Nexsan iSeries as belonging to either one of two QoS groups: The High Priority Group or The Low Priority Group. When enabled, the SLA mechanism enforces a limit on the throughput generated by the lower priority group. Any bandwidth throughput beyond the limit is reserved for the usage of the High Priority group. Thus by limiting the traffic of the Low priority group the mechanism assures this group will not overuse the system's bandwidth resources and thereby interfere with the bandwidth requirements of the High Priority Group.
Group does not require the reserved bandwidth and therefore this bandwidth is unused. In such cases the bandwidth allocated to the lower priority group is An exception to the bandwidth limit rule occurs only during times when the High Priority automatically dynamically expanded to make use of the available traffic-free bandwidth. Once the bandwidth needs of the High Priority Group rise again, the limit on the lower priority group is again dynamically retracted back to the predefined limit. This mechanism ensures that the lower priority targets have access to as much bandwidth as they need, as long as they do not interfere with the traffic from higher priority targets.
To enable the Nexsan iSeries SLA and set the bandwidth limit:
By default the Nexsan iSeries SLA mechanism is disabled. When SLA is disabled the system stores and remembers any Priority Group allocation of targets, but does not enforce any throughput limitation on the lower priority group |
1. |
In the Navigation pane, select the Nexsan iSeries, right click and select Properties. |
Figure 3-52. Device Properties
The Nexsan iSeries Properties dialog box opens.
By default the Nexsan iSeries SLA mechanism is disabled. SLA settings are enabled per Nexsan iSeries.To enable SLA on multiple Nexsan iSeries you must enable SLA for each participating Nexsan iSeries. When SLA is disabled the system stores and remembers any Priority Group allocation of targets, but does not enforce any throughput limitation on the lower priority group |
3. |
To enable QoS, check Enable. |
4. |
Set the throughput limit for the lower priority targets group by specifying the QoS Limit. This QoS limit is a limit for the combined traffic for all targets in the Low Priority Group. |
To set and view target priority levels:
1. |
Selecting a target from the Navigation Pane. |
The target QoS pane appears in the bottom right of the iSeries Manager window.
2. |
Click the radio button corresponding to the chosen priority. |
Alternatively, you can set the QoS priority as follows:
1. |
Right click on a target in the Navigation Pane. |
2. |
Select QoS and the desired priority level. |
Figure 3-55. QoS Priority
