Document 6506408

Transcription

Document 6506408

NetApp E-Series
NetApp
E-Series SNMP trap usage
- not final version - (2013/10/24)
Welcome to SNMP training
by Wolfgang Ratschmeier (ST-VS/ETP4) 3rd level team Nürnberg
Manage DSA E-Series iSCSI storage array
E-Series
Security Systems
1
Internal | Wolfgang Ratschmeier (STDN/ASA) | October 2013 | not final | © Robert Bosch GmbH 2012. All rights reserved, also regarding
any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.
NetApp E-Series SNMP trap usage
Chapter I How to install Santricity Manager ES Storage Manager
1.
Select the installation file you need for your Server system
where you want to run the Service of the “Santricity Manager
ES Sotrage Manager” in order to monitor various iSCSI DSA
E-Series (64- Bit OS or 32-Bit OS):
http://144.76.6.227/downloads/support-cctv/DSA_E-Series_NetApp/64-Bit_SMIA-WinX64-10.84.x0.36_password_protected.zip
http://144.76.6.227/downloads/support-cctv/DSA_E-Series_NetApp/32-Bit_SMIA-WS32-10.84.x0.32_password-protected.zip
The password to unzip those packages is “NetApp4Bosch”
Security Systems
2
How to install Santricity Manager ES Storage Manager
2.
Select “Custom”!!
Security Systems
3
3.
Unselect “MPIO” as no fiber channel HBA is to be used in the
server where the
SANtricity software is
installed
Java Access Bridge
option also must
remain unchecked
Security Systems
4
4.
Select “Automatically Start Monitor” in order to get a
service for SNMP
messaging and
system monitoring
started even
the SANtricity ES
Storage Manager
software is not started
(GUI window not open)
Security Systems
5
5.
Click on “Done” to restart your monitoring system
Make sure you then add all relevant iSCSI E-Series
systems to the management software
Security Systems
6
6.
Start SANtricity and use “Automatic Discovery…” to scan your
network for E-Series iSCSI targets
Security Systems
7
Configure SANtricity Manager software
7. At “Enterprise Management window” click on “Setup” tab and
click on “Configure Alerts”
8.
Select “An individual storage
array” to just configure alerts
for a specific iSCSI system, or
“All storage arrays”
Security Systems
8
Select Storage Array (DSA E-Series units)
9.
Select your DSA E-Series iSCSI system and click on “OK”
10. At “Filtering” enable the
options you whish
to get messages for:
Security Systems
9
Define Hosts for SNMP traps
11. Add host IP e.g. for a
BVMS system to send
the SNMP traps to:
Type in the destination IP
Use “public” as Community
name and click on “Add”
At the next dialog box click
on “Yes” as no mail service
will be
used
Security Systems
10
Chapter II
How to implement SNMP monitoring of
E-Series iSCSI storage arrays into BVMS 4.5
E-Series
Security Systems
11
Preparations for SNMP trap transmission
During BMVS Install, make sure
the “Installl SNMP feature support”
option has been checked
to be installed
During BVMS Central Server
is running
… open the WindowsTask Manager
… and start the “Resource Monitor”
Security Systems
12
At Recource Monitor select the tab “Network” and expand the
“Listening Ports” section to search for all Listening
UDP ports 162
Make sure that no other software beside the windows
“snmptrap.exe” is using this port.
Security Systems
13
In order to prepare the Bosch VMS Central Server to act as
an SNMP receiver the following steps are recommended:
In the “Device Tree” of Bosch VMS Configuration Client
go to tree node “Other Devices” and add a new SNMP device
The name of the “SNMP device” can indicate the function
e.g. “E-Series Base, Power-fan canister 1 or 2 failure” for the
two power supplies at the 12-bay Base E-Series unit
Security Systems
14
In the upper section of the SNMP device add first the IP of
your iSCSI target you want to
receive traps from
(example “160.10.100.250)
Security Systems
15
When selecting this SNMP instance, the
“Show Trap Logger Tool”
becomes available
at the right window
section
Click on “Show Tarp Logger Tool”
to open the dialog to see all
incoming traps (see next slides)
Security Systems
16
Perform test and click on “Start”
Here one example of some
received traps
The OID to scan for E-Series messages is:
1.3.6.1.4.1.789.1123.1.500.1.1.5
the trap with this OID provide as value specific
NetApp MEL Event codes which can be used to
filter out e.g. critical events
Example:
280b is the value for a Power supply issue
The OID which shows clear text information e.g.
for SNMP software like Monitor ONE is ending with .9
1.3.6.1.4.1.789.1123.1.500.1.1.9
A list of MEL Event codes is
listed at the end of this set of training slides
Security Systems
17
In order to test SNMP trap transmission from
e.g. DSA-N2E6X3-12AT run the SANtricity
software as described in the previous slides
Go to “Configure Alerts” dialog
and click the “Test” button
Security Systems
18
When clicking on “Test” in SANtricity GUI, the following
confirmation dialog is seen:
Security Systems
19
E-Series OID source for event codes is always
1.3.6.1.4.1.789.1123.1.500.1.1.5
object name
OID
Comments
storageManager
SANtricity management software product.
The trap MIB definition of the SANtricity management software uses
.1.3.6.1.4.1.789.1123.1.500.
this OID. The storageManager OID in object name format is:
iso.org.dod.internet.private.enterprises.netapp.eSeriesStorageSystem.
There is one „object ID“ with one sub-tree/leaf with different event codes
.500 = uses the SM10R3 MIB file,
.1 = trapBase
When ever an OID value with „ 1.3.6.1.4.1.789.1123.1.500.0.2“ is received,
this is indicating that a critical event will follow
Security Systems
20
You then see the incoming “Alert Test”
Using the SNMP Trap Logger
of BVMS it would be possible to
“trace/collect” errors and alarms;
Of course pro-active it is recommended
to minimum add the following
NetApp MEL Event codes as alarm trigger
226C = Drive Failure; 226D = Drive removed
283B = Power Supply Failure; 283C = Power Supply Warning
7307 = Battery Near Expiration (RMA exchange should be planned)
210C or 7305 = Battery Failure
More examples later
Security Systems
21
Adding SNMP Trap Filter Rules
Based on the known
OID for E-Series events
and the possible value
of the “alarming OID”,
add the OID and value like shown here
Create multiple SNMP devices; Each with its event code as
filtered Value
Security Systems
22
Common event codes used with E-Series
list #
Event code
short description
BOSCH recmmendations
1
2
180A
1904
iSCSI Failed Host Card
Failed Host Card
contact RMA help desk and exchange complete controller (not only HIC)
contact RMA help desk and exchange complete controller (not only HIC)
3
7500
Backup Device Failed
contact Support and provide support bundle by using SANtricity 10.84 or later
4
2110
Cache Mamory Diagnostics Failure
5
210E
Cache Data Loss
6
7306
Battery Missing
Battery is not detected or missing. Check controller;
unscrew and pull battery module; Put it back in and check in the running system if the
battery is detected again. If not - contact support and send support bundle by using
SANtricity software v.10.84 or later
7
7305
Battery Failure
download support bundle by using SANtricity software v.10.84 or later and contact RMA
help desk. Request a new Battery and provide the support bundle files.
8
7308
Battery Expired
Donwload the support bundle by using Santricity software v.10.84 or later and request
pro-actively a new Battery for the E-Series controller. The replacement can be done
9
7307
Battery Near Expiration
Donwload the support bundle by using Santricity software v.10.84 or later and request
pro-actively a new Battery for the E-Series controller. The replacement does not need to
be done before 7308 is not received
10
2271
Drive Unsupported Capacity
This message should not appear as BOSCH only provides NetApp HDDs which are
tested and supported in the E-Series Firmware which BOSCH delivers from stock
Security Systems
23
Common event codes used with E-Series
list #
11
12
13
Event code
2262
2267
2260
short description
BOSCH recmmendations
Wrong Drive Type
Collect Support Bundle file by using SANtricity v.10.84 or later and provide this to your local support
team. Make sure that a certified and BOSCH delivered HDD is inserted to the E-Series iSCSI Disk
Array
Incompatible Drive
Array
Uncertified Drive
Array
14
226C
Drive Failure
Arrange the necessary steps to exchange the HDD using SANtricity as soon the new HDD was
received via RMA. Depending on system hot spare availability the procedures are slightly different.
Contact your support specialist for NetApp E-Series
15
226D
Drive in VolumeGroup or HS Removed
Check if a HDD which is actively used for Data recording is manually removed or not mount
properly. Consult SANtricity GUI for trouble shooting and gather Support Bundle information
16
283C
Power Supply Warning
Collect Support Bundle using SANtricity and provide the results to the RMA help desk; Replace
Power / Fan Canister if error is not gone away, contact the support
17
18
19
283B
2302
283A
Power Supply Failure
Power Supply Validation Fail
Power Supply Missing
Collect Support Bundle using SANtricity and provide the results to the RMA help desk; Replace
Power / Fan Canister if error is not gone away, contact the support
Pull and Reseat Power Fan Canister
Pull and Reseat Power Fan Canister
20
280D
Enclosure Fail
Replace controller/ESM and check Support Bundle file upfront with the Support specialists at
BOSCH
21
2807
Enclosure Fail
Replace controller/ESM and check Support Bundle file upfront with the Support specialists at
BOSCH
22
2831
uncertified ESM
Security Systems
24
Chapter III
Configure Alarm Messaging in BVMS
E-Series
Security Systems
25
This section will be provided in the
next version of this slide set
Security Systems
26
Chapter IV
Decision trees for NetApp E-Series
E-Series
Security Systems
27
decision trees
and error codes
Security Systems
28
decision trees
and error codes
Security Systems
29
decision trees
and error codes
Security Systems
30
decision trees
and error codes
Security Systems
31
decision trees
and error codes
Security Systems
32
decision trees
and error codes
Security Systems
33
decision trees
and error codes
Security Systems
34
Chapter V
VRM SNMP traps
Security Systems
35
Receive SNMP traps at BVMS
Since VRM 2.22 version the VRM MIB was enhanced
Video Loss is signaled via SNMP trap for VSG and Encoders
-- 1.3.6.1.4.1.3967.3.4
-- 1.3.6.1.4.1.3967.3.4.4
-- 1.3.6.1.4.1.3967.3.4.5
camera
video_alarm_on
video_alarm_off
SYNTAX OCTET STRING
More examples will follow here:
-
Security Systems
36

Document 6506408

Transcription

Similar documents

MRC BASSARA E

BE35 Bonanza Guide

HOW TO INSTALL THE SP12 TURBO UPGRADE KIT

Picturing family matters

AsahiGuard E-SERIES Product Information

Antenne Bayern Chooses 2wcom

Flyer - Indu-Sol

Nonwood Declaration - Amptown Cases GmbH

PREDATOR TRAPS