IT Operations Management (ITOM)

How to monitor your SAN elements

How to monitor your SAN elements


Are you a data center administrator? Do you feel like you're spending more time every day on monitoring your SAN elements?

In a SAN data center environment, monitoring different SAN elements is a time consuming task for an Administrator. Monitoring each element through their management consoles, doing alert verifications in a big data center is a challenging task. But there is a solution for you.

Have you heard of HPE's Storage Operations Manager (SOM)?

With the help of SOM, SAN environments can be monitored through the incidents feature. SOM generates incidents based on the SNMP traps received from the SNMP clients. Incidents are notifications, alerts, or warnings that provide vital information about the device. Most SAN devices contain an SNMP agent that sends SNMP traps to SOM Server. To receive SNMP traps from the devices, register SOM as an SNMP manager.

SOM provides one centralized location, the Incidents folder in the Configuration workspace, where the management events and SNMP trap incident configurations are visible to you.

SOM supports two types of Events:
1. SNMP traps for different devices like 3PAR Storage System, Brocade and Cisco Switches.
2. Management Server Events

For example, if a Brocade SAN switch port goes offline then a Trap will be sent from the Brocade switch to the SOM Server and it will be shown in the SNMP Traps tab of the SOM, as shown in Figure 1. Please note that the Brocade switch needs to be discovered in the SOM server before receiving an alert from the Brocade switch.

Figure 1 SNMP Trap received from a Brocade Switch when port goes offline

Figure 1 SNMP Trap received from a Brocade Switch when port goes offline.png


Figure 2. SNMP Trap Received from a 3Par device when remote copy link failed

Figure 2. SNMP Trap Received from a 3Par device when remote copy link failed.jpg
You may want to avoid certain type of Traps from the device and may be interested in seeing some important alerts from the device. In SOM, you can configure to receive only certain type of SNMP traps from one device and can restrict few types of alerts from the same device.

For example, if you want to disable the CiscoZoneActivateNotifications from the Cisco SAN switches then you can disable that particular SNMP Trap on the SNMP Trap Configurations page as shown in Figure 3.

Figure 3. Restricting certain types of Alerts

Figure 3. Restricting certain types of Alerts.jpg

You can also see the management health events. When a SAN element is discovered and data collected you can see an alert stating the data collection is successful or failed.

For example, here the management Event received on Data collection successful for an Isilon Storage System.

Figure 4. Monitoring Element data collections

Figure 4. Monitoring Element data collections.jpg

SOM also provides alerts on the number of hosts discovered when running host inference rule. Host inference rule is basically a method of discovering the servers without even providing server credentials. Inference rules includes three different scopes (Zone, Zone Aliases, Host security group). You can see an alert with actual number of hosts discovered when each host inference rule runs. For example, when a rule on Host security group is executed, Hosts that are inferred from host security group as part of this rule will be shown in SOM All incidents page, as shown in Figure 5.

Figure 5. Monitoring Host Inference Rule executions

Figure 5. Monitoring Host Inference Rule executions.jpg


SOM uses Operations Bridge Reporter (OBR) as reporting solution. So, CSV Files will be exported from SOM to OBR for reporting purpose. You can monitor if a particular CSV Export is failed. Here is an example, an incident shows that the CSV generated for a specific SAN element at SOM side is not transferred to OBR Server.

Figure 6. Monitoring CSV Export Failures

Figure 6. Monitoring CSV Export Failures.jpg


You can monitor if any of your SAN elements are deleted from SOM Server. Here the screenshot depicts an event received on deleting a Storage System from the SOM Server.

Figure 7. Monitoring CSV Exports

Figure 7. Monitoring CSV Exports.jpg


Now that you have details on the events triggered by your environment, you can go ahead and take a necessary action.

On a concluding note, Incident Browsing workspace provided by SOM will ease out your life by showing all alerts from heterogeneous devices in your environment in a single view.

Thanks to Michael Procopio for his help in reviewing my post.

Storage Operations Manager (SOM) is a storage resource management solution that helps you reduce total costs of storage operations and increase productivity. Start your free trial today.

Tweet to us at @HPE_ITOps and let us know what you think! | Follow HPE Software on LinkedIn | Like us HPE Software on Facebook

  • infrastructure management
About the Author


Sr. Software Engineer with HPE Software, working in Storage Resource Management solution for 9 years.


It's avery good post but i think the title is more generic than the content especially the post is talking only about the storage so the tite should direct in what are inside