6 

Troubleshooting

Nexsan iSeries Manager identifies error conditions and generates alarms accordingly.

The alarms are viewable and can be sorted. The last ten unacknowledged alarms generated are displayed in the bottom pane of the Nexsan iSeries Manager GUI.

Alarm Operations

Nexsan iSeries Manager supports alarm messages for real-time tracking and monitoring of both Nexsan iSeries Manager and Nexsan iSeries configurations and activity. Alarms are time-stamped according to the Nexsan iSeries Manager server date and time.

Configuring Email Alarm Notification

You can send an email when an alarm is opened for off-site alarm monitoring. The administrator should configure the alarms which will trigger the Email notification using Nexsan iSeries Manager Alarms Notification Configuration list.

A user profile must be configured on the SMTP server for sending Email notifications received from Nexsan iSeries Manager. The profile must include a user name and password for authentication. The SMTP server parameters are:

	Mail Server: Name or IP address of SMTP server

	From Address: Address that Email appears to be sent from

	User Name: User authentication name

	Password: User authentication password

To configure the alarm notification list:

1.	From the Nexsan iSeries Manager menu bar, select Alarm Notifications > Email Setup…

Figure ‎6-1. Alarms Menu

The Alarms Notification Configuration window opens.

2.	Select each alarm for which you want to receive email notification.

3.

Click OK.

Figure ‎6-2. Selected Alarms for Email Notification

To configure the email address for alarm notification:

1.	From the Nexsan iSeries Manager menu bar, select Alarms Notifications > E-mail Addresses…

Figure ‎6-3. Configure Menu

The Email Configuration dialog box opens.

2.	Enter the name or IP address of the SMTP server.

3.	Enter the email address for the outgoing email notification.

4.	Enter the User Name and Password for user authentication.

Figure ‎6-4. SMTP Server Configuration

5.	Toggle to the Destination tab and click Add…

The Add Address dialog box opens.

6.	Enter the Email address to send alarm notifications to and click OK.

Figure ‎6-5. Email to Send Alarm Notification to

The Email notification format is shown in Figure ‎6-6.

Figure ‎6-6. Alarm Email

Note: Email is sent only at the time when an alarm is generated. If an alarm entry already exists during the Email notification configuration, an Email notification will not be sent.

Viewing Specific Alarms

Every alarm can be associated with a specific Nexsan iSeries Manager element, e.g. cluster, Nexsan iSeries, disk, volume or target.

To view specific alarms:

Select the element.

	Right click and select Alarms > Specific.

Figure ‎6-7. Specific Alarms Selected

The Specific Alarms window opens.

Figure ‎6-8. Specific Alarms Window

From the Specific Alarms window, you can select an alarm and view its source and properties. You can also close an alarm. This will remove the closed alarm from the Current Alarms list and move it to the Closed Alarms list.

Viewing Propagated Alarms

A propagated alarm is generated by a source which is a logical member of a selected element.

The Propagated Alarms window lists all the specific alarms of a selected element as well as all the selected element derived alarms.

There are two propagation hierarchies:

	Cluster > Target > LU > Volume > Subdisk > Disk

	Cluster > Nexsan iSeries > Management Parameters and Configurations

To view propagated alarms:

	Select the element whose propagated alarms you want to view. Right click and select Alarms > Propagated.

Figure ‎6-9. Propagated Alarms Selected

The Propagated Alarms window opens with all propagated alarms for the element.

Figure ‎6-10. Propagated Alarms Window

From the Propagated Alarms window, you can select an alarm in order to view its source and properties. You can also close an alarm. This deletes it from the Current Alarms list and moves it to the Closed Alarms list.

Viewing Alarms History

You can view the list of all acknowledged (previous) alarms.

To view previous alarms:

	From the standard Nexsan iSeries Manager toolbar, click Alarms > History or click the History button .

Figure ‎6-11. Alarms Menu

The Alarms History window opens.

Figure ‎6-12. Alarms History Window

Viewing Current Alarms

You can view all current open alarms for all the Nexsan iSeries Manager elements.

To view current alarms:

1.	From the Quick Launch: Monitor > Current Alarms

The Current Alarms window opens.

Figure ‎6-13. Current Alarms Window

Viewing Current RAID Events

You can view all current RAID events for all connected storage devices.

To view RAID events:

2.	From the Quick Launch: Monitor > Current RAID Events

The RAID Events window opens.

Figure ‎6-14. RAID Events Window

Acknowledging an Alarm

An acknowledged alarm still exists but its severity will not propagate to higher levels. However, the alarm will still be listed in the Current Alarms window, along with the name of the user who acknowledged the alarm.

Note: If an alarm is listed in the Last 10 Alarms pane, after being acknowledged it is removed from the pane.

 

To acknowledge an alarm:

Select the alarm to acknowledge.

Do one of the following:

	Right click and select Acknowledge

OR

	Check the Ack checkbox from any alarm pane.

If the alarm was in the Last 10 Alarms pane, it is removed.

Figure ‎6-15. Acknowledge Alarm

Figure ‎6-16. Ack Checkbox

Closing an Alarm

Once an alarm occurs, it remains in the current alarm list till the situation that caused it ceases. However, it can be closed manually.

If the event that generated the alarms occurs again, another alarm will be generated and added to the current alarm list.

To close an alarm:

1.	Select the alarm to close. Right click and select Close.

Figure ‎6-17. Close Alarm

The Close Alarm dialog box opens.

2.	Click Yes to reconfirm the alarm closure.

Figure ‎6-18. Close Alarm Confirmation Dialog Box

The alarm will be closed and removed from the pane. You can view the closed alarm in the Alarms History window (Figure ‎6-12).

Viewing Alarm Properties

You can view the properties of an alarm, including:

	Alarm Severity

	Alarm Name

	Source Name

	Source Type

	Date Opened



Category

	Probable Cause

	Alarm Text

	Troubleshooting

Use the alarm properties to help solve the alarm issue.

To display alarm properties:

From any of the alarm windows, select the alarm whose properties you want to view.

	Right click and select Properties.

Figure ‎6-19. Properties

The Properties window opens.

Figure ‎6-20. Alarm Properties Window

Alarm Severity

Nexsan iSeries Manager supports four types of alarm severity:

	Warning alarms: may be temporary but the administrator should be notified of. Warning alarms are marked with a blue exclamation mark .

	Minor alarms: may cause service interruption or have an administrative reason. Minor alarms are marked with a yellow exclamation mark .

	Major alarms: may cause service interruption and clearly indicated problems in the system operation. Major alarms are marked with an orange exclamation mark .

	Critical alarms: represent service interruption. Critical alarms are marked with a red exclamation mark .

Table ‎6-1: Nexsan iSeries Manager Alarms

	Name	ID	Troubleshooting	Action
	Mirror sync	--	Mirror is synchronizing.
	Theoretical target	--	Target will only be operational with LUN 0.
	Storage is missing	0101	Storage has been disconnected. The administrator can reconnect the storage or replace it by a new one and then replace volume and delete the faulty storage	Reconnect or Delete.
	Storage Invalid	0102	A storage known by the system is configured differently. The administrator can delete the storage.	Delete.
	Storage Unknown	0103	V Switch doesn't know the state of the storage. Select cluster and then the option Storage Discovery.	Storage Discovery.
	Storage Provisioned	0104	A storage has been configured by the user but never has been discovered by the V Switch. Select cluster and then the option Storage Discovery.	Storage Discovery.
	Subdisk Mismatch	0105	A subdisk has been provisioned by the user but after having been connected, its characteristics are different from those configured.	Delete.
	Volume non-functional	0201	A volume is non-functional if it is relying on a storage that is missing or invalid. The administrator can reconnect the storage if missing or replace the volume and delete the non-functional one.	Replace and Delete.
	Volume internal	0202	Volume is not exposed.
	Volume needs sync	0203	Volume needs to be synchronized.	Synchronize.
	Vol Need Sync	0203	A volume needs synchronization when it is not synchronized with the other children of a mirror. Activating mirror synchronize will close the alarm when synchronization is finished.	Mirror Synchronize.
	Mirror not Mirror	0208	A mirror volume is not mirroring because the other leg(s) of the mirror are non-functional.	Replace defective volume.
	Expandable	0212	The administrator has resized a volume hasn’t yet expanded them. After expanding the volume, it will be the whole potential size attributed to it.	Expand.
	Over Used Snapshot	0213	A snapshot is approaching to the limit of its full capacity.	Resize.
	Snapshot Out of Sync	0214	A snapshot is no longer synchronized with its source.	Delete Snapshot.
	Snapshot Full	0215	A snapshot is full and no more synchronized with its source. Nothing can be done. Only delete the snapshot volume.	Delete Snapshot.
	Snapshot Modified	0216	A snapshot has been exposed with read-write access and was modified.	Delete Snapshot.
	Snapshot Expose Inconsistency	0217	A snapshot is exposed on a target exposed on a switch different from the one exposing the source.	Configuration.
	Volume Mismatch	0220	A volume has been provisioned by the user but after having been connected, its characteristics are different from those configured.	Delete.
	Not Validated	0221	A Volume has been configured and its size and block size haven't been validated.	Connect Storage.
	Theoretical Target	0301	A target has no LUN exposed on it.	Expose LU.
	Incomplete Definition	0302	There is no portal defined for it remote target.	Add Portal.
	Target not Connected	0303	The initiator of the V switch couldn't connect to the remote target.	Check IP and ACL.
	Fans faulty	0401	One FAN (and only one) doesn't work. Call support to replace the FAN.	Nexsan iSeries X. Only two fans are working.
	Fans critical	0402	Both FANs don't work. Call support to replace the FANs.	Call Tech Support.
	Power supplies faulty	0403	One of the power supplies doesn't work. Call support to replace the power supply.	Call Tech Support.
	CPU temperature warning	0404	The temperature of the CPU is above the tolerable threshold. Turn off the switch and call support.	Turn off Nexsan iSeries.
	On-board temperature warning	0405	The on-board temperature is above the tolerable threshold. Turn off the switch and call support.	Turn off Nexsan iSeries.
	No fans	0406	No FANs are working. Turn off the Nexsan iSeries and call support.	Turn off Nexsan iSeries.
	CPU temperature critical	0407	The temperature of the CPU is above the critical threshold. Turn off the switch and call support.	Turn off Nexsan iSeries.
	On-board temperature critical	0408	The on-board temperature is above the critical threshold. Turn off the switch and call support.	Turn off Nexsan iSeries.
	Inconsistent Database	0409	The Nexsan iSeries database is corrupted. Call technical support	Call technical support.
	Low Memory	0410	The device is under heavy load. Redistribute your resources.	Restart the Nexsan iSeries.
	Cluster Inc	0501	At least one V Switch missing from the cluster in order to provide full redundancy.	Add V Switch.
	Neighbor dead	0502	Nexsan iSeries lost connection with one of its neighbors. Check the network. Reconnecting the Nexsan iSeries will close the alarm	Reconnect.
	Neighbor unknown	0504	Nexsan iSeries doesn't know the state of one of its neighbors. After few seconds this alarm will be closed.	Wait.
	Object not redundant	0505	An object doesn't exist in the database of one of the Nexsan iSeries of the cluster. Synchronizing the object will solve the problem.	Synchronize the cluster.
	Alias inconsistency	0506	Inconsistent Alias. By giving a new alias to the object, the administrator will remove the alarm condition	Configure.
	LU number inconsistency	0507	A volume is exposed on a different LUN on the same target on two Nexsan iSeries of the cluster. Delete one of the LU and synchronize the other one.	Delete and synchronize.
	Data Attributes inconsistency	0508	Some parameters of an object are different according the Nexsan iSeries; if the parameters are writable, re-writing them should solve the problem.	Configure.
	Illegal Subdisk	0510	There is a subdisk on one V Switch while there is a volume on the whole disk on another V Switch.	Delete subdisk.
	Illegal Volume	0511	The volume is inconsistent in the cluster: its structure is different on each V Switch.	Delete Volume.
	LU volume inconsistency	0512	A specific LUN is pointing to two different volumes within the cluster. Deleting the virtual LU will solve the problem.	Delete.
	Target volume inconsistency	0513	A volume is exposed on a different target on two Nexsan iSeries of the cluster. Delete one of the LU and synchronize the other one.	Delete.
	Nexsan iSeries takeover	0514	Nexsan iSeries has taken over its neighbor. Reconnecting the second Nexsan iSeries will solve this alarm condition.	Wait.
	Inconsistent ACL	0515	The ACL configuration is different within the cluster.	Reconfigure ACL.
	Inconsistent Volume	0516	The volume does not have the same number of children in the cluster	Synchronize volumes.
	Inconsistent Size	0517	The volume does not have the same actual size in all the V Switches in the cluster.	Expand.
	Nexsan iSerieses are not neighbors	0518	The switches are not configured as being neighbors. Try to rediscover your cluster. Select cluster, right click and select Rediscover.	Configure.
	Target exposed inconsistency	0519	A target is inconsistently exposed among the cluster. The administrator should change the exposure of the target.	Configuration.
	Illegal LUN serial number	0523	The serial number of a specific logical unit is different within the Nexsan iSeries of the cluster. The administrator should delete one of the LU and then activate cluster synchronization.	Configuration.
	Portal Inconsistency	0524	A remote portal for a remote target is not defined in all the switches of the cluster.	Configure.
	ACL Entry not Redundant	0525	An ACL entry is not defined at the same target in all the switches of the cluster.	Configure.
	Incompatible License	0526	The devices in the cluster have incompatible licenses.	Configure. Ask your supplier to provide you with an upgraded license.
	Synchronizing	0527	One of the switches is synchronizing its states with that of its neighbor.	Wait.
	Standing	0528	Some incompatibility was found.	Check the configuration and correct it.
	Neighbor Removed	0531	The Nexsan iSeries were inconsistently configured from the cluster’s point of view, therefore the Nexsan iSeries was removed.	Add the neighbor Nexsan iSeries in the New Nexsan iSeries dialog box.
	Nexsan iSeries disconnected	0901	Nexsan iSeries Manager lost connection with a Nexsan iSeries. Check the network. Reconnecting the Nexsan iSeries will close the alarm. You can check also that the server's IP address is defined in the switch as manager by using the CLI command: snmp manager show. If it is not, please add it by using the CLI command: snmp manager add -ip <IP address>	Reconnect.
	Trap port in use	0902	Nexsan iSeries trap port is already in use. Change the trap port via Nexsan iSeries ->Properties ->SNMP to receive traps from this Nexsan iSeries. This trap port is where Nexsan iSeries Manager listens from. The trap port must also be changed in the CLI. This trap port is where the Nexsan iSeries sends from.	Configuration.
	Nexsan iSeries Manager inconsistent with the Nexsan iSeries	0903	There is total incompatibility between Nexsan iSeries Manager and the Nexsan iSeries. The administrator should exit Nexsan iSeries Manager and then run it again.	Reset Nexsan iSeries Manager.
	LinkDown	1001	An interface stopped functioning.	Reconnect.

 

Table ‎6-2: Disaster Recovery Alarms

	Name	ID	Troubleshooting	Action
	Journal Internal	0218	The journal is not used.	Connect a pair.
	Overused Journal	0219	A journal is approaching to the limit of its full capacity.	Resize journal.
	Illegal Volume Pair	0521	The primary or the secondary volume of a pair in a switch is part of another pair in another switch of the cluster.	Select one of the pair as the "good" one and delete the other one. Activate Cluster Sync to synchronize the cluster (or the pair only).
	Illegal Pair Consistency Group	0522	The pair of a CG in a switch is part of another CG in another switch of the cluster.	Set the problematic pair to appropriate consistency group.
	Journal out of sync	1201	A journal is no longer synchronized with one of the replicating production volumes. User should abort replication, and restart it including initial synchronization.	Restart DR Process.
	Journal Full	1202	A journal is no longer synchronized with one of the replicating production volumes because it was full. User should abort replication, and restart it including initial synchronization.	Restart DR Process.
	Pair Error	1203	One of the volumes essential to the replication is not functioning including a journal volume.	Check that all the volumes: primary, secondary and Journal are well configured and well connected to the switch.
	Need Synchronization	1204	A pair or a group can be in this state if the remote volume was disconnected. Reconnect and reinitialize the initial synchronization.	Activate Replicate.
	Initial Sync in Progress	1205	The pair or the group is actually synchronizing its data.	Wait patiently.
	Switched	1206	Either a disaster occurred or the administrator initiated a planned failover. After fallback, the mode of those objects will switch back to normal.	Fallback.
	Consistency Group DR Unknown	1207	This group has simultaneously, at least one pair in normal mode and at least one pair in switched mode. The only way to correct the problem is to restart everything from the beginning. The administrator should activate the option "Abort Replication" from the pull down menu and then restart initial synchronization.	Restart DR Process.
	Replication Inactive	1208	The group/pair is well configured but wasn't activated yet. The administrator should activate the option "Start Initial Synchronization or Start Replication" from the pull down menu.	Start DR Process.
	Replicate Merge	1209	The group/pair is actually merging.	Wait.
	Replicate Transfer	1210	The group/pair is actually transferring	Wait.
	CG Empty	1211	The group is empty. Configure a pair to it.	Complete configuration.
	PFailover	1212	The group/pair started a process of planned failover which has not yet completed.	After waiting a while, you can try: 1. Rediscover 2. Reset switch
	Fallback	1213	The group/pair started a process of Fallback which has not yet completed.	After waiting a while, you can try: 1. Rediscover 2. Reset switch
	CFWaiting	1214	The group/pair is waiting for the agreement of the other side in order to perform an action.	Wait a while and reset switch.
	CFError	1215	The group/pair couldn't get the agreement of the other side in order to perform an action. Reset the switches.	Reset.
	Not Symmetric DR	1301	The pair is not configured in both sites.	Use wizard in order to complete pair configuration.
	Unequivalent Pair	1302	A pair is defined on Primary1, Secondary1 in one site and Primary1, Secondary2 in another site.	Delete misconfigured pair and use wizard.
	Inverted Pair	1303	Pair is defined on Primary1, Secondary1 in one site and Secondary1, Primary1 in another site. Delete one pair and then use wizard in order to complete pair configuration..	Delete misconfigured pair.
	Asymmetric Attribute	1304	One pair has a different value between the sites.	Open the pair properties and reconfigure the initial sync type.
	Inverted Role	1305	The consistency group is declared local or remote in the both sites.	Use wizard.
	Inconsistent Replication	1306	The replication attributes are different within the sites.	Use wizard.
	Control Function Failure	1307	An action couldn't be performed. The most common reason for this alarm is that the network between a local site and a remote site is unavailable	Configuration.
	DiffSize	1308	The primary volume is different in size from the secondary one.	Delete and recreate the pair.
	Disaster	1309	The pair/group is in disaster mode.	Fallback.