Difference between revisions of "ZenPack:Dell PowerEdge"

From Zenoss Wiki
Jump to: navigation, search
m (Remove beta note.)
Line 1: Line 1:
 
{{ZenPack
 
{{ZenPack
|Summary=Monitoring Dell PowerEdge 11G and 12G Servers, including blade servers with Dell M1000e chassis.
+
|Summary=The Dell PowerEdge ZenPack allows you to monitor Dell PowerEdge Servers, including blade servers with the Dell PowerEdge M1000e chassis.
 
|Organization=Zenoss, Inc.
 
|Organization=Zenoss, Inc.
 
|ZenPack name=ZenPacks.zenoss.Dell.PowerEdge
 
|ZenPack name=ZenPacks.zenoss.Dell.PowerEdge
|Documentation URL=http://www3.zenoss.com/l/3432/2013-10-08/358nrc
+
|Homepage=https://github.com/zenoss/ZenPacks.zenoss.Dell.PowerEdge
 
|Releases={{Release
 
|Releases={{Release
|Version=1.0.0
+
|Version=2.0.0
|Release date=2013/11/26
+
|Release date=2014/02/04
 
|Compatible with=Zenoss Resource Manager 4.2.x
 
|Compatible with=Zenoss Resource Manager 4.2.x
|Download URL=https://support.zenoss.com/ics/support/DLRedirect.asp?deptID=16059&fileID=57520
+
|Requires=WSMAN
 +
|Download URL=https://support.zenoss.com/ics/support/DLRedirect.asp?deptID=16059&fileID=63345
 
}}
 
}}
|Devices={{Device
+
{{note}} See Upgrade section if Upgrading from 1.0.0 to 2.0.0 [[#Upgrade| [Upgrade]]]
|Manufacturer=Dell
+
 
|Model=PowerEdge Servers (11g and 12g)
+
|Devices=
}}{{Device
+
|Applications={{Application
|Manufacturer=Dell
+
|Product Name=Dell PowerEdge
|Model=M1000e Blade Chassis
+
 
}}
 
}}
|Applications=
 
 
|Integrations=
 
|Integrations=
 
|DataAudits=
 
|DataAudits=
 
|Binaries=
 
|Binaries=
|Flavor=commercial
+
|Flavor=commercial}}
}}
+
This ZenPack provides support for monitoring Dell PowerEdge Servers (11G and 12G), including blade servers with the Dell PowerEdge M1000e chassis.  
This ZenPack provides support for monitoring Dell PowerEdge Servers (11G and 12G), including blade servers with the Dell PowerEdge M1000e chassis. Monitoring is performed via the OpenManage Server Agent (OMSA) using the SNMP API.  This ZenPack is currently supported on servers running either the Windows or Linux OS.
+
 
 +
Monitoring is performed via the OpenManage Server Agent (OMSA) using the SNMP API.   
 +
 
 +
This ZenPack is currently supported on servers running either the Windows or Linux OS. This ZenPack also provides support for monitoring Dell PowerEdge Servers (11G and 12G), via the Dell iDRAC using the WSMAN interface.  
  
Note: Future support is planned for Dell servers running VMware with the OMSA VIB, and for monitoring via the Dell iDRAC.  A release date for this support has not been determined at this time.
+
{{note}} Please restart zenoss after installing this ZenPack
  
 
== Gallery ==
 
== Gallery ==
Line 47: Line 49:
 
blade temperature sensors.png
 
blade temperature sensors.png
 
blade virtual Disks.png
 
blade virtual Disks.png
 +
 +
idrac_Blade.png
 +
idrac_PhysicalDisk.png
 +
idrac_VirtualDisk.png
 +
idrac_MemoryCard.png
 +
idrac_VideoController.png
 +
idrac_ChipSet.png
 +
idrac_EnclosureView.png
 +
idrac_Processor.png
 +
idrac_Software.png
  
 
</gallery>
 
</gallery>
Line 52: Line 64:
 
== Prerequisites ==
 
== Prerequisites ==
 
;Zenoss Version: >=4.2.3
 
;Zenoss Version: >=4.2.3
;External Dependencies: OpenManage Server Administrator Agent 7.2.0 (OMSA Agent) should be running on Linux/Windows devices.
+
;External Dependencies:  
:This should be verified using snmpwalk from your ZenOSS server: <pre>snmpwalk -v2c -c [community] [hostname]</pre>
+
* OpenManage Server Administrator Agent 7.2.0 (OMSA Agent) should be running on Linux/Windows devices.
 +
* This should be verified using snmpwalk from your zenoss server: <pre>snmpwalk -v2c -c [community] [hostname]</pre>
 +
 
 +
* WSMAN interface should be enabled and running on your zenoss server.
  
 
== Features ==
 
== Features ==
Line 63: Line 78:
 
* Event management.
 
* Event management.
 
* Service impact and root cause analysis. (Requires Zenoss Service Dynamics)
 
* Service impact and root cause analysis. (Requires Zenoss Service Dynamics)
 
  
 
== Discovery ==
 
== Discovery ==
 +
 
;Dell M1000e Blade Chassis
 
;Dell M1000e Blade Chassis
 +
 
* The following components will be automatically discovered through the Chassis Management Controller(CMC) IP address and the host name you provide. The properties and relationships will be continually maintained.
 
* The following components will be automatically discovered through the Chassis Management Controller(CMC) IP address and the host name you provide. The properties and relationships will be continually maintained.
  
Line 72: Line 88:
 
: Attributes:Chassis Name, Current Usage, Peak Usage, Min Usage, Max Power, Status
 
: Attributes:Chassis Name, Current Usage, Peak Usage, Min Usage, Max Power, Status
 
: Relationships:Chassis Management Controller
 
: Relationships:Chassis Management Controller
 +
  
 
;Chassis PowerSupply Units
 
;Chassis PowerSupply Units
: Attributes:Name, Chassis Name, Power in Amps, Power in Watts
+
: Attributes:Name, Chassis, Power in Amps, Power in Watts
 
: Relationships:Chassis Management Controller
 
: Relationships:Chassis Management Controller
  
 
;Chassis Management Controller
 
;Chassis Management Controller
: Attributes: System Slot, Chassis Name, Manufacturer, Service Tag, Model Name
+
: Attributes:Name, System Slot, Chassis Name, Manufacturer, Service Tag, Model Name
 
: Relationships:Chassis Power Consumption, Chassis Power Supply Units, Chassis Temperature Sensors, Chassis Slots
 
: Relationships:Chassis Power Consumption, Chassis Power Supply Units, Chassis Temperature Sensors, Chassis Slots
  
Line 86: Line 103:
  
 
;Chassis Slots
 
;Chassis Slots
: Attributes:Name, Slot Name, Server Index, Service Tag
+
: Attributes:Name, Slot Name, Server Index, Service Tag, Model
 
: Relationships:Chassis Management Controller
 
: Relationships:Chassis Management Controller
 
  
 
;Dell 11g and 12g servers
 
;Dell 11g and 12g servers
* The following components will be automatically discovered through the Server IP address and the host name you provide . The properties and relationships will be continually maintained.
+
* The following components will be automatically discovered through the Server IP address and the host name you provide. The properties and relationships will be continually maintained.
 +
 
  
 
;Main System Chassis
 
;Main System Chassis
:Attributes: Chassis Name, Manufacturer, Host Name, Service Code, Model, Service Tag, Lock Present, Chassis Type
+
: Attributes: Chassis Name, Manufacturer, Host Name, Service Code, Model, Service Tag, Lock Present, Chassis Type
:Relationships: Physical Disks, Temperature Sensors, Power Consumption, Virtual Disks, Processors, Processor Caches, Memory Cards, ChipSets, Ports, Cooling Fans
+
: Relationships: Physical Disks, Temperature Sensors, Power Consumption, Virtual Disks, Processors, Processor Caches, Memory Cards, ChipSets, Ports, Cooling Fans
 +
 
  
 
;Physical Disks
 
;Physical Disks
:Attributes: Name, Capacity, Used Space, Free Space, State
+
: Attributes: Name, Capacity, Used Space, Free Space, State
:Relationships: Main System Chassis
+
: Relationships: Main System Chassis
 +
 
  
 
;Temperature Sensors
 
;Temperature Sensors
:Attributes: Probe Name, Temperature, State
+
: Attributes: Probe Name, Temperature, State
:Relationships: Main System Chassis
+
: Relationships: Main System Chassis
  
;Power Consumption
 
:Attributes: Name, Power, Status
 
:Relationships: Main System Chassis
 
  
 +
;Power Consumption
 +
: Attributes: Name, Power, Status
 +
: Relationships: Main System Chassis
 +
 
;Virtual Disks
 
;Virtual Disks
:Attributes: Name, Device Name, Type, Disk Number, Read Policy, Write Policy, Cache Policy, Status, Layout
+
: Attributes: Name, Device Name, Type, Disk Number, Read Policy, Write Policy, Cache Policy, Status, Layout
:Relationships: Main System Chassis
+
: Relationships: Main System Chassis
 +
 
  
 
;Processors
 
;Processors
:Attributes: Name, Version, Manufacturer, Model, Speed, Core Count, Status
+
: Attributes: Name, Version, Manufacturer, Model, Speed, Core Count, Status
:Relationships: Main System Chassis
+
: Relationships: Main System Chassis
 +
 
  
 
;Processor Caches
 
;Processor Caches
:Attributes: Name, Processor Name, Associativity, Current Size, Maximum Size, Policy, Status
+
: Attributes: Name, Processor Name, Associativity, Current Size, Maximum Size, Policy, Status
:Relationships: Main System Chassis
+
: Relationships: Main System Chassis
 +
 
  
 
;Memory Cards
 
;Memory Cards
:Attributes:  Name, Manufacturer, Size, Type, Status
+
: Attributes:  Name, Manufacturer, Size, Type, Status
:Relationships: Main System Chassis
+
: Relationships: Main System Chassis
 +
 
  
 
;ChipSets
 
;ChipSets
 
:Attributes: Name, Manufacturer, Slot Index, Speed, Status
 
:Attributes: Name, Manufacturer, Slot Index, Speed, Status
 
:Relationships: Main System Chassis
 
:Relationships: Main System Chassis
 +
  
 
;Ports
 
;Ports
Line 135: Line 160:
  
 
* The following additional components apply only to Rack and Tower servers.
 
* The following additional components apply only to Rack and Tower servers.
 +
  
 
;Cooling Fans
 
;Cooling Fans
Line 141: Line 167:
  
  
=== Performance Monitoring ===
+
;Dell iDRAC (Dell Remote Access Controller)
The following metrics will be collected every 5 minutes by default. Any other Dell PowerEdge Server metrics can also be collected by adding them to the appropriate monitoring template.
+
* The following components will be automatically discovered through the iDRAC IP address and the host name you provide. The properties and relationships will be continually maintained.
  
  
 +
;Main System Chassis
 +
:Attributes: Chassis Name,  Host Name, Manufacturer, Model, Service Tag, BIOS Version, Life Cycle Controller Version, Power State
 +
:Relationships: Physical Disks, Virtual Disks, Processors, Memory Cards, ChipSets, Enclosure View, Software, Video Controller
  
  
 +
;Physical Disks
 +
:Attributes: Name, Slot Number, Security State, Bus Type, Media Type, Hot Spare, Capacity, Used Space, Free Space, State
 +
:Relationships: Main System Chassis
  
[[File:diskgraph.png|thumb|250px|DiskUtilization]]
 
;Physical Disk
 
:Disk Utilization: disk/usage in percentage (MAXIMUM)
 
  
 +
;Virtual Disks
 +
:Attributes: Name, Layout, Read Policy, Write Policy, Size, Stripe Size, Remaining Redundancy, State
 +
:Relationships: Main System Chassis
  
  
 +
;Processors
 +
:Attributes: Name, Model, Family, Manufacturer, Speed, Core Count, CPU Status, Status
 +
:Relationships: Main System Chassis
  
  
 +
;Memory Cards
 +
:Attributes:  Name, Manufacturer, Serial Number, Type, Size, Speed
 +
:Relationships: Main System Chassis
  
[[File:temperaturegraph.png|thumb|250px|Temperature]]
 
;Temperature Sensor
 
:Temperature: current temperature in Celsius(MAXIMUM)
 
  
 +
;ChipSets
 +
:Attributes: Name, Manufacturer, Device Index
 +
:Relationships: Main System Chassis
  
  
 +
;Enclosure View
 +
:Attributes: Name, FQDD, Version, Slot Count, Connector, Enclosure Position
 +
:Relationships: Main System Chassis
  
  
 +
;Software
 +
:Attributes: Name, Version, Vendor ID, Installation Date
 +
:Relationships: Main System Chassis
  
[[File:powerconsumptiongraph.png|thumb|250px|PowerConsumption]]
 
;Power Consumption
 
:Power Usage: current consumption in watts (MAXIMUM)
 
  
 +
* The following additional components apply only to iDRAC7 Controller.
  
  
 +
;Video Controller
 +
:Attributes:  Name, Description, Manufacturer, Bus Number, Data Bus Width, Slot Type, PCI Device ID, PCI Vendor ID
 +
:Relationships: Main System Chassis
  
  
 +
=== Performance Monitoring ===
 +
The following metrics will be collected every 5 minutes by default. Any other Dell PowerEdge Server metrics can also be collected by adding them to the appropriate monitoring template.
  
  
[[File:Processorgraph.png|thumb|250px|CacheUtilization]]
+
[[File:diskgraph.png|thumb|250px|DiskUtilization]]
;Processor Caches
+
;Physical Disk
:Cache Utilization: cache/ usage in percentage (MAXIMUM)
+
:Disk Utilization: disk/usage in percentage (MAXIMUM)
  
  
  
  
 +
[[File:temperaturegraph.png|thumb|250px|Temperature]]
 +
;Temperature Sensor
 +
:Temperature: current temperature in Celsius(MAXIMUM)
  
;Chassis Power Consumption
 
:Power Usage: current consumption in watts (MAXIMUM)
 
  
  
  
 +
[[File:powerconsumptiongraph.png|thumb|250px|PowerConsumption]]
 +
;Power Consumption 
 +
:Power Usage: current consumption in watts (MAXIMUM)
  
  
  
 +
 +
[[File:Processorgraph.png|thumb|250px|CacheUtilization]]
 +
;Processor Caches
 +
:Cache Utilization: cache/ usage in percentage (MAXIMUM)
 +
 +
 +
 +
 +
;Chassis Power Consumption
 +
:Power Usage: current consumption in watts (MAXIMUM) Dell Remote Access Controller(iDRAC) will also provide performance metrics data of the Dell PowerEdge Server. The following metrics will be collected every 5 minutes by default. Any other Dell PowerEdge Server metrics can also be collected by adding them to the appropriate monitoring template.
 +
 +
 +
[[File:iDRACPhysicalDiskUtilization.png|thumb|250px|IDRAC Physical Disk Utilization]]
 +
;Physical Disk:Disk Utilization
 +
: disk/usage and disk/free space in percentage (MAXIMUM)
 +
 +
 +
[[File:iDRACProcessorSpeed.png|thumb|250px|IDRAC Processor Speed]]
 +
;Processor
 +
:Processor Current Speed: processor/current speed space in MHz(MAXIMUM)
 +
<br clear=all>
  
 
=== Event Management ===
 
=== Event Management ===
 
The following event classes and their subclasses will be continually collected and passed into the Zenoss event management system.
 
The following event classes and their subclasses will be continually collected and passed into the Zenoss event management system.
 +
  
 
* Alarm
 
* Alarm
 
* Event
 
* Event
 +
  
 
Various information encoded in these event classes will be used to automatically determine as best as possible the following Zenoss event fields.
 
Various information encoded in these event classes will be used to automatically determine as best as possible the following Zenoss event fields.
 +
  
 
;Standard Zenoss Event Fields
 
;Standard Zenoss Event Fields
Line 207: Line 282:
 
* severity
 
* severity
 
* eventClassKey (for mapping specific event types)
 
* eventClassKey (for mapping specific event types)
 +
  
 
== Installed Items ==
 
== Installed Items ==
 
Installing this ZenPack will add the following items to your Zenoss system.
 
Installing this ZenPack will add the following items to your Zenoss system.
 
 
;Configuration Properties
 
;Configuration Properties
 
 
* zCollectorPlugins
 
* zCollectorPlugins
 
* zSnmpMonitorIgnore
 
* zSnmpMonitorIgnore
 +
* zWSMANPort
 +
* zWSMANUseSSL
 +
* zWSMANUsername
 +
* zWSMANPassword
  
  
 
;Device Classes
 
;Device Classes
 +
* /Devices/Server/Dell/ChassisController
 +
:Chassis Management Controller will be added in this device class using Chassis IP.
  
* /Device
 
  
;Modeler Plugins
+
* /Devices/Server/Linux/Dell
 +
:Linux Dell Blade server will be added in this device class using Blade device IP.
 +
 
 +
 
 +
* /Devices/Server/Windows/Dell
 +
:Windows Dell Blade server will be added in this device class using Blade device IP.
 +
 
 +
 
 +
* /Devices/Server/Dell/iDRAC6
 +
:iDRAC6 controller of Blade will be added in this device class using respective iDRAC6 IP.
 +
 
 +
 
 +
* /Devices/Server/Dell/iDRAC7
 +
:iDRAC7 controller of Blade will be added in this device class using respective iDRAC7 IP.
 +
;Modeler PluginsThe following plugins will be used for modeling Blade and Chassis Controller using the respective blade and Chassis Controller IP Addresses via SNMP interface.
 +
 
  
 
* ChassisControllerModeler
 
* ChassisControllerModeler
 +
:This plugin is for modeling Chassis Controller.
 +
 +
 
* PowerEdgeModeler
 
* PowerEdgeModeler
 +
:This plugin is for modeling Blade and Rack devices.
  
 +
 +
* zenoss.dell.snmp.DellDeviceModeler
 +
:This plugin is for retrieving the basic Dell hardware and os information. The following plugins will be used for modeling Blade and Chassis Controller details using the iDRAC controller via WSMAN interface.
 +
 +
 +
* iDRAC6Modeler
 +
:This plugin is for modeling Dell Remote Access Controller 6.
 +
 +
 +
* iDRAC7Modeler
 +
:This plugin is for modeling Dell Remote Access Controller 7.
 +
 +
 +
* DellIDRACModeler
 +
:This plugin is for retrieving the basic iDRAC manufacturer, firmware information.
 
;Datasource Types
 
;Datasource Types
 +
  
 
* SNMP
 
* SNMP
 +
* WSMAN
 +
  
 
;Monitoring Templates
 
;Monitoring Templates
 +
* PhysicalDisk (/Server/Linux/Dell, /Server/Windows/Dell , /Server/Dell/iDRAC6, /Server/Dell/iDRAC7)
 +
* Temperature (/Server/Linux/Dell, /Server/Windows/Dell)
 +
* PowerConsumption (/Server/Linux/Dell, /Server/Windows/Dell)
 +
* ChassisPowerConsumption (/Server/Dell/ChassisController)
 +
* ProcessorCache (/Server/Linux/Dell, /Server/Windows/Dell)
 +
* Processor (/Server/Dell/iDRAC6, /Server/Dell/iDRAC7)
 +
<br clear=all>
  
* physicalDisk (in /Server/Linux/Dell & /Server/Windows/Dell)
 
* Temperature (in /Server/Linux/Dell & /Server/Windows/Dell)
 
* PowerConsumption (/Server/Linux/Dell & /Server/Windows/Dell)
 
* ChassisPowerConsumption (in /Server/Dell/ChassisController)
 
* ProcessorCache (/Server/Linux/Dell & /Server/Windows/Dell)
 
  
<br clear=all>
 
 
== Service Impact and Root Cause Analysis ==
 
== Service Impact and Root Cause Analysis ==
 
 
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact and root cause analysis capabilities for services running on Dell PowerEdge. The service impact relationships shown in the diagram and described below are automatically added. These will be included in any services that contain one or more of the explicitly mentioned components.  
 
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact and root cause analysis capabilities for services running on Dell PowerEdge. The service impact relationships shown in the diagram and described below are automatically added. These will be included in any services that contain one or more of the explicitly mentioned components.  
  
[[File:chassis_blade_impact_yuml.png|thumb|320px|Chassis and Blade Impact Relationship Diagram]]
 
[[File:nonblade_impact_yuml.png|thumb|320px|NonBlade device Impact Relationship Diagram]]
 
  
;Internal Impact Relationships
+
[[File:chassis_blade_impact_yuml.png|thumb|320px|Chassis and Blade(modeled via SNMP) Impact Relationship Diagram]]
 +
[[File:nonblade_impact_yuml.png|thumb|320px|NonBlade device(modeled via SNMP) Impact Relationship Diagram]]
 +
[[File:iDRACBlade_impact_yuml.png|thumb|320px|Blade device(modeled via iDRAC) Impact Relationship Diagram]]
  
* Chassis Controller access failure impacts all the blade devices available in its slots.
 
  
 +
;Internal Impact Relationships
 +
* Chassis Controller access failure impacts all the blade devices available in its slots.
 
* Chassis Management Controller failure impacts all related hosts, chassis slots, temperature sensors, power consumption, power supply units.
 
* Chassis Management Controller failure impacts all related hosts, chassis slots, temperature sensors, power consumption, power supply units.
 
 
* Blade/NonBlade Host failure impacts the related physical disks, virtual disks, temperature sensors, memory cards, processors, processor caches, power consumption, chipsets, ports, cooling fans.
 
* Blade/NonBlade Host failure impacts the related physical disks, virtual disks, temperature sensors, memory cards, processors, processor caches, power consumption, chipsets, ports, cooling fans.
 +
* In iDRAC modeling, Blade Host failure impacts the related physical disks, virtual disks, memory cards, processors, chipsets, enclosureview, softwares, videocontrollers.
 +
  
 
<br clear=all>
 
<br clear=all>
 +
  
 
Most of the impacts described above follow the default policy of a node being in the worst state of the nodes that impact it. For example, a Chassis Management Controller failure will imply that all related hosts are also failed.
 
Most of the impacts described above follow the default policy of a node being in the worst state of the nodes that impact it. For example, a Chassis Management Controller failure will imply that all related hosts are also failed.
  
<br clear=all>
 
== Usage ==
 
  
=== Adding ChassisController ===
+
<br clear=all>
  
Use the following steps to start monitoring ChassisController using the Zenoss web interface.
+
 
# Navigate to the Infrastructure page. [[File:cmc_add_menu.png|thumb|320px|Add Device]]
+
== Usage ==
 +
====Adding ChassisController====
 +
Use the following steps to start monitoring ChassisController using the Zenoss web interface.  
 +
# Navigate to the Infrastructure page.  
 +
[[File:cmc_add_menu.png|thumb|320px|Add Device]]
 
# Navigate to organizer Devices/Server/Dell/ChassisController.
 
# Navigate to organizer Devices/Server/Dell/ChassisController.
# Choose Add a Single Device from the add button.<br clear=all>
+
# Choose Add a Single Device from the add button.
# Fill out the form. [[File:cmc_add_dialog.png|thumb|320px|Add Dialog]]
+
<br clear=all>
 +
 
 +
 
 +
# Fill out the form.  
 +
[[File:cmc_add_dialog.png|thumb|320px|Add Dialog]]
 
#* ''Name'' can be anything you want.
 
#* ''Name'' can be anything you want.
 
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 
# Click ''ADD''.
 
# Click ''ADD''.
 +
 +
 +
<br clear=all>
 +
 +
 +
----
 +
 +
 +
====Adding Linux SNMP Dell Blade/Rack device====
 +
Use the following steps to start monitoring Linux Dell PowerEdge device using the Zenoss web interface.
 +
 +
 +
# Navigate to the Infrastructure page. [[File:poweredge_linux_add_menu.png|thumb|320px|Add Device]]
 +
# Navigate to organizer Devices/Server/Linux/Dell.
 +
# Choose Add a Single Device from the add button.
 +
  
 
<br clear=all>
 
<br clear=all>
 +
# Fill out the form. [[File:blade_linux_add_dialog.png|thumb|320px|Add Dialog]]
 +
#* ''Name'' can be anything you want.
 +
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 +
# Click ''ADD''.
 +
# Dell Blade / Rack server that runs on Linux will be added in the /Devices/Server/Linux/Dell device class.<br clear=all>
 +
  
 
----
 
----
  
Alternatively you can use zenbatchload to add devices from the command line.To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets.
 
Multiple devices can be added under the same ''/Server/Dell/ChassisController'' section.
 
  
<syntaxhighlight lang="text">
+
====Adding Windows SNMP Dell Blade/Rack device====
/Server/Dell/ChassisController <hostname> setManageIp='<IP Address>'
+
Use the following steps to start monitoring Windows Dell PowerEdge device using the Zenoss web interface.
 +
# Navigate to the Infrastructure page. [[File:poweredge_windows_add_menu.png|thumb|320px|Add Device]]
 +
# Navigate to organizer Devices/Server/Windows/Dell.
 +
# Choose Add a Single Device from the add button.
  
</syntaxhighlight>
 
  
<syntaxhighlight lang="text">
+
<br clear=all>
  
Example : /Server/Dell/ChassisController CMC_1 setManageIp='10.100.40.190'
 
  
</syntaxhighlight>
+
# Fill out the form. [[File:blade_windows_add_dialog.png|thumb|320px|Add Dialog]]
 +
#* ''Name'' can be anything you want.
 +
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 +
# Click ''ADD''.
 +
# Dell Blade / Rack server that runs on Windows will be added in the /Devices/Server/Windows/Dell device class.
  
You can then load the chassis controller(s) with the following command.
 
  
<syntaxhighlight lang="bash">
+
<br clear=all>
  
zenbatchload <filename>
 
  
</syntaxhighlight>
+
----
  
 +
 +
====Adding Dell Blade/Rack information to the /Server/Microsoft/Windows Organizer====
 +
Use the following steps to monitor a Windows Device using the ZenPacks.zenoss.Microsoft.Windows zenpack.
 +
# Navigate to the Infrastructure page.
 +
# Navigate to organizer Devices/Server/Microsoft/Windows.
 +
# Select Details
 +
# Select Modeler Plugins
 +
# Add zenoss.dell.snmp.PowerEdgeModeler and zenoss.dell.snmp.DellDeviceModeler to the Selected list
 +
# Save
 +
 +
 +
====Adding iDRAC6 controller====
 +
Use the following steps to start monitoring iDRAC6 using the Zenoss web interface.
 +
# Navigate to the Infrastructure page. [[File:add_iDRAC6_menu.png|thumb|320px|Add Device]]
 +
# Navigate to organizer Devices/Server/Dell/iDRAC6.
 +
# Choose Add a Single Device from the add button.
 
<br clear=all>
 
<br clear=all>
=== Adding Linux Dell PowerEdge device ===
+
# Fill out the form. [[File:add_iDRAC6_DeviceDialog.png|thumb|320px|Add Dialog]]
Use the following steps to start monitoring Linux Dell PowerEdge device using the Zenoss web interface.
+
# Navigate to the Infrastructure page. [[File:poweredge_linux_add_menu.png|thumb|320px|Add Device]]
+
# Navigate to organizer Devices/Server/Linux/Dell.
+
# Choose Add a Single Device from the add button.<br clear=all>
+
# Fill out the form. [[File:blade_linux_add_dialog.png|thumb|320px|Add Dialog]]
+
 
#* ''Name'' can be anything you want.
 
#* ''Name'' can be anything you want.
 
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 
# Click ''ADD''.
 
# Click ''ADD''.
 +
# iDRAC6 controller of Dell Blade server will be added in the /Devices/Server/Dell/iDRAC6 device class. Use the following steps for successful modeling.
 +
# Select the device added.
 +
# Navigate to Configuration Properties. [[File:configuration_iDRAC6.png|thumb|320px|Add Dialog]]
 +
# Provide the values for zWSMANPassword, zWSMANPort, zWSMANUseSSL and zWSMANUserName.
 +
# Model the device.
 +
 +
 
<br clear=all>
 
<br clear=all>
 
----
 
----
Alternatively you can use zenbatchload to add devices from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple devices can be added under the same ''/Server/Linux/Dell'' section.
 
<syntaxhighlight lang="text">
 
/Server/Linux/Dell <hostname> setManageIp='<IP Address>'
 
</syntaxhighlight>
 
<syntaxhighlight lang="text">
 
Example : /Server/Linux/Dell Linux-Blade setManageIp='10.100.40.180'
 
</syntaxhighlight>
 
You can then load the PowerEdge device(s) with the following command.
 
<syntaxhighlight lang="bash">
 
zenbatchload <filename>
 
</syntaxhighlight>
 
  
 +
 +
====Adding iDRAC7 controller====
 +
Use the following steps to start monitoring iDRAC7 using the Zenoss web interface.
 +
# Navigate to the Infrastructure page. [[File:add_iDRAC7_menu.png|thumb|320px|Add Device]]
 +
# Navigate to organizer Devices/Server/Dell/iDRAC7.
 +
# Choose Add a Single Device from the add button.
 
<br clear=all>
 
<br clear=all>
=== Adding Windows Dell PowerEdge device ===
+
# Fill out the form. [[File:add_iDRAC7_DeviceDialog.png|thumb|320px|Add Dialog]]
Use the following steps to start monitoring Windows Dell PowerEdge device using the Zenoss web interface.
+
# Navigate to the Infrastructure page. [[File:poweredge_windows_add_menu.png|thumb|320px|Add Device]]
+
# Navigate to organizer Devices/Server/Windows/Dell.
+
# Choose Add a Single Device from the add button.<br clear=all>
+
# Fill out the form. [[File:blade_windows_add_dialog.png|thumb|320px|Add Dialog]]
+
 
#* ''Name'' can be anything you want.
 
#* ''Name'' can be anything you want.
 
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 
#* ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
 
# Click ''ADD''.
 
# Click ''ADD''.
 +
# iDRAC7 controller of Dell Blade server will be added in the /Devices/Server/Dell/iDRAC7 device class. Use the following steps for successful modeling.
 +
# Select the device added.
 +
# Navigate to Configuration Properties. [[File:configuration_iDRAC7.png|thumb|320px|Add Dialog]]
 +
# Provide the values for zWSMANPassword, zWSMANPort, zWSMANUseSSL and zWSMANUserName.
 +
# Model the device.
 +
 +
 
<br clear=all>
 
<br clear=all>
 +
 +
 
----
 
----
Alternatively you can use zenbatchload to add devices from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple devices can be added under the same ''/Server/Windows/Dell'' section.  
+
 
 +
 
 +
====zenbatchload====
 +
* Alternatively you can use zenbatchload to add devices from the command line.
 +
* To do this, you must create a file with contents similar to the following.
 +
* Replace all values in angle brackets with your values minus the brackets.  
 +
* Multiple devices can be added under the same sections.  
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
/Server/Windows/Dell <hostname> setManageIp='<IP Address>'
+
'/Devices/Server/Dell/ChassisController' <device name>  setManageIp="<IP Address>"
 +
'/Devices/Server/Dell/iDRAC7' <device name> setManageIp="<IP Address>", zWSMANUsername='<username>', zWSMANPassword='<password>', zWSMANPort=443, zWSMANUseSSL='true'
 +
'/Devices/Server/Dell/iDRAC6' <device name> setManageIp="<IP Address>", zWSMANUsername='<username>', zWSMANPassword='<password>', zWSMANPort=443, zWSMANUseSSL='true'
 +
'/Devices/Server/Windows/Dell' <device name> setManageIp="<IP Address>"
 +
'/Devices/Server/Linux/Dell' <device name> setManageIp="<IP Address>"
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
 +
 
<syntaxhighlight lang="text">
 
<syntaxhighlight lang="text">
Example : /Server/Windows/Dell Windows-Blade setManageIp='10.100.40.184'
+
Example : /Server/Dell/ChassisController CMC_1 setManageIp='10.100.10.30'
 +
Example : /Server/Dell/iDRAC6 iDRAC6_1 setManageIp='10.100.10.32', zWSMANUsername='root', zWSMANPassword='calvin'
 +
Example : /Server/Dell/iDRAC7 iDRAC7_1 setManageIp='10.100.10.31', zWSMANUsername='root', zWSMANPassword='calvin'
 +
Example : /Server/Windows/Dell Windows-Blade setManageIp='10.100.10.27'
 +
Example : /Server/Linux/Dell Linux-Blade setManageIp='10.100.10.29'
 +
 
 +
 
 
</syntaxhighlight>
 
</syntaxhighlight>
You can then load the PowerEdge device(s) with the following command.
+
 
 +
 
 +
You can then load the Devices using zenbatchload with the following command.
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
zenbatchload <filename>
 
zenbatchload <filename>
 
</syntaxhighlight>
 
</syntaxhighlight>
 
<br clear=all>
 
<br clear=all>
 +
----
 +
 +
 +
== Upgrade==
 +
 +
 +
Upgrading of Dell ZenPack from version of 1.0.0 to new version 2.0.0
 +
{{note}} Refer to Prerequisites section
 +
;Use the following steps to upgrade from Dell PowerEdge 1.0.0 to 2.0.0
 +
# On the Zenoss Master
 +
# Backup the original __init__.py file located in $ZENHOME/ZenPacks/ZenPacks.zenoss.Dell.PowerEdge-1.0.0-py2.7.egg/ZenPacks/zenoss/Dell/PowerEdge
 +
# Copy the 2.0.0 egg file onto the zenoss master filesystem
 +
# Extract the patched __init__.py with the following command
 +
#*<syntaxhighlight lang="bash">
 +
unzip *Dell.PowerEdge-2*.egg patches/__init__.py
 +
</syntaxhighlight>
 +
# copy the __init__.py to $ZENHOME/ZenPacks/ZenPacks.zenoss.Dell.PowerEdge-1.0.00-py2.7.egg/ZenPacks/zenoss/Dell/PowerEdge
 +
# Install the 2.0.0 version of the Dell PowerEdge zenpack through UI / CLI.
 +
# On all collectors, run the following command if you wish to keep all performance data.  This is due to a relationship change.
 +
#*<syntaxhighlight lang="bash">
 +
find $ZENHOME/perf/Devices -name Blade_Index* -exec sh -c 'mv "${0}" "${0/Blade_Index_/Main System Chassis}"' {} \;
 +
</syntaxhighlight>
 +
 +
# Re-start the zenoss instance on the master.
 +
# Push the updates to the remote hubs/collectors.
 +
#* Verify the Upgrading to Dell PowerEdge ZenPack 2.0.0 with the following command.
 +
#*<syntaxhighlight lang="bash">
 +
zenpack --list | grep -i PowerEdge
 +
</syntaxhighlight>
 +
<br clear=all>
 +
 +
 
== Limitation ==
 
== Limitation ==
Dell Servers running VMware are not monitored by this ZenPack.  
+
Dell Servers running VMware are not monitored by this ZenPack. Currently this ZenPack does not recognize / model  IO modules and Fans of Chassis.
Currently this ZenPack does not recognize / model  IO modules and Fans of Chassis.
+
 
{{ZenPackFooter}}
 
{{ZenPackFooter}}

Revision as of 18:12, 19 February 2014


Note: This ZenPack is available in commercial versions of Zenoss. Click here to request more information about this commercial ZenPack. Click here to see all commercial ZenPacks.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.Dell.PowerEdge
More Information
GitHub page/HomePage

Devices Monitored:



Dell PowerEdge ZenPack

The Dell PowerEdge ZenPack allows you to monitor Dell PowerEdge Servers, including blade servers with the Dell PowerEdge M1000e chassis.

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Releases

Version 2.0.0- Download
Released on 2014/02/04
Requires WSMAN ZenPack
Compatible with Zenoss Resource Manager 4.2.x

Bulbgraph.png Note: See Upgrade section if Upgrading from 1.0.0 to 2.0.0 [Upgrade]

Background

This ZenPack provides support for monitoring Dell PowerEdge Servers (11G and 12G), including blade servers with the Dell PowerEdge M1000e chassis. 

Monitoring is performed via the OpenManage Server Agent (OMSA) using the SNMP API.

This ZenPack is currently supported on servers running either the Windows or Linux OS. This ZenPack also provides support for monitoring Dell PowerEdge Servers (11G and 12G), via the Dell iDRAC using the WSMAN interface.

Bulbgraph.png Note: Please restart zenoss after installing this ZenPack

Gallery

Prerequisites

Zenoss Version
>=4.2.3
External Dependencies
  • OpenManage Server Administrator Agent 7.2.0 (OMSA Agent) should be running on Linux/Windows devices.
  • This should be verified using snmpwalk from your zenoss server:
    snmpwalk -v2c -c [community] [hostname]
  • WSMAN interface should be enabled and running on your zenoss server.

Features

The features added by this ZenPack be summarized as follows. They are each detailed further below.

  • Initial discovery and continual synchronization of relevant components.
  • Performance monitoring.
  • Event management.
  • Service impact and root cause analysis. (Requires Zenoss Service Dynamics)

Discovery

Dell M1000e Blade Chassis
  • The following components will be automatically discovered through the Chassis Management Controller(CMC) IP address and the host name you provide. The properties and relationships will be continually maintained.
Chassis Power Consumption
Attributes:Chassis Name, Current Usage, Peak Usage, Min Usage, Max Power, Status
Relationships:Chassis Management Controller


Chassis PowerSupply Units
Attributes:Name, Chassis, Power in Amps, Power in Watts
Relationships:Chassis Management Controller
Chassis Management Controller
Attributes:Name, System Slot, Chassis Name, Manufacturer, Service Tag, Model Name
Relationships:Chassis Power Consumption, Chassis Power Supply Units, Chassis Temperature Sensors, Chassis Slots
Chassis Temperature Sensors
Attributes:Chassis Name, Front Panel, CMC Board, CMC Processor, State
Relationships:Chassis Management Controller
Chassis Slots
Attributes:Name, Slot Name, Server Index, Service Tag, Model
Relationships:Chassis Management Controller
Dell 11g and 12g servers
  • The following components will be automatically discovered through the Server IP address and the host name you provide. The properties and relationships will be continually maintained.


Main System Chassis
Attributes: Chassis Name, Manufacturer, Host Name, Service Code, Model, Service Tag, Lock Present, Chassis Type
Relationships: Physical Disks, Temperature Sensors, Power Consumption, Virtual Disks, Processors, Processor Caches, Memory Cards, ChipSets, Ports, Cooling Fans


Physical Disks
Attributes: Name, Capacity, Used Space, Free Space, State
Relationships: Main System Chassis


Temperature Sensors
Attributes: Probe Name, Temperature, State
Relationships: Main System Chassis


Power Consumption
Attributes: Name, Power, Status
Relationships: Main System Chassis
Virtual Disks
Attributes: Name, Device Name, Type, Disk Number, Read Policy, Write Policy, Cache Policy, Status, Layout
Relationships: Main System Chassis


Processors
Attributes: Name, Version, Manufacturer, Model, Speed, Core Count, Status
Relationships: Main System Chassis


Processor Caches
Attributes: Name, Processor Name, Associativity, Current Size, Maximum Size, Policy, Status
Relationships: Main System Chassis


Memory Cards
Attributes: Name, Manufacturer, Size, Type, Status
Relationships: Main System Chassis


ChipSets
Attributes: Name, Manufacturer, Slot Index, Speed, Status
Relationships: Main System Chassis


Ports
Attributes: Name, Connector Type, Security State, Status
Relationships: Main System Chassis


  • The following additional components apply only to Rack and Tower servers.


Cooling Fans
Attributes: Name, Number, Current Speed, Location, Status
Relationships: Main System Chassis


Dell iDRAC (Dell Remote Access Controller)
  • The following components will be automatically discovered through the iDRAC IP address and the host name you provide. The properties and relationships will be continually maintained.


Main System Chassis
Attributes: Chassis Name, Host Name, Manufacturer, Model, Service Tag, BIOS Version, Life Cycle Controller Version, Power State
Relationships: Physical Disks, Virtual Disks, Processors, Memory Cards, ChipSets, Enclosure View, Software, Video Controller


Physical Disks
Attributes: Name, Slot Number, Security State, Bus Type, Media Type, Hot Spare, Capacity, Used Space, Free Space, State
Relationships: Main System Chassis


Virtual Disks
Attributes: Name, Layout, Read Policy, Write Policy, Size, Stripe Size, Remaining Redundancy, State
Relationships: Main System Chassis


Processors
Attributes: Name, Model, Family, Manufacturer, Speed, Core Count, CPU Status, Status
Relationships: Main System Chassis


Memory Cards
Attributes: Name, Manufacturer, Serial Number, Type, Size, Speed
Relationships: Main System Chassis


ChipSets
Attributes: Name, Manufacturer, Device Index
Relationships: Main System Chassis


Enclosure View
Attributes: Name, FQDD, Version, Slot Count, Connector, Enclosure Position
Relationships: Main System Chassis


Software
Attributes: Name, Version, Vendor ID, Installation Date
Relationships: Main System Chassis


  • The following additional components apply only to iDRAC7 Controller.


Video Controller
Attributes: Name, Description, Manufacturer, Bus Number, Data Bus Width, Slot Type, PCI Device ID, PCI Vendor ID
Relationships: Main System Chassis


Performance Monitoring

The following metrics will be collected every 5 minutes by default. Any other Dell PowerEdge Server metrics can also be collected by adding them to the appropriate monitoring template.


DiskUtilization
Physical Disk
Disk Utilization: disk/usage in percentage (MAXIMUM)



Temperature
Temperature Sensor
Temperature: current temperature in Celsius(MAXIMUM)



PowerConsumption
Power Consumption
Power Usage: current consumption in watts (MAXIMUM)



CacheUtilization
Processor Caches
Cache Utilization: cache/ usage in percentage (MAXIMUM)



Chassis Power Consumption
Power Usage: current consumption in watts (MAXIMUM) Dell Remote Access Controller(iDRAC) will also provide performance metrics data of the Dell PowerEdge Server. The following metrics will be collected every 5 minutes by default. Any other Dell PowerEdge Server metrics can also be collected by adding them to the appropriate monitoring template.


IDRAC Physical Disk Utilization
Physical Disk
Disk Utilization
disk/usage and disk/free space in percentage (MAXIMUM)


IDRAC Processor Speed
Processor
Processor Current Speed: processor/current speed space in MHz(MAXIMUM)


Event Management

The following event classes and their subclasses will be continually collected and passed into the Zenoss event management system.


  • Alarm
  • Event


Various information encoded in these event classes will be used to automatically determine as best as possible the following Zenoss event fields.


Standard Zenoss Event Fields
  • device (set to device class)
  • component
  • summary
  • severity
  • eventClassKey (for mapping specific event types)


Installed Items

Installing this ZenPack will add the following items to your Zenoss system.

Configuration Properties
  • zCollectorPlugins
  • zSnmpMonitorIgnore
  • zWSMANPort
  • zWSMANUseSSL
  • zWSMANUsername
  • zWSMANPassword


Device Classes
  • /Devices/Server/Dell/ChassisController
Chassis Management Controller will be added in this device class using Chassis IP.


  • /Devices/Server/Linux/Dell
Linux Dell Blade server will be added in this device class using Blade device IP.


  • /Devices/Server/Windows/Dell
Windows Dell Blade server will be added in this device class using Blade device IP.


  • /Devices/Server/Dell/iDRAC6
iDRAC6 controller of Blade will be added in this device class using respective iDRAC6 IP.


  • /Devices/Server/Dell/iDRAC7
iDRAC7 controller of Blade will be added in this device class using respective iDRAC7 IP.
Modeler PluginsThe following plugins will be used for modeling Blade and Chassis Controller using the respective blade and Chassis Controller IP Addresses via SNMP interface.


  • ChassisControllerModeler
This plugin is for modeling Chassis Controller.


  • PowerEdgeModeler
This plugin is for modeling Blade and Rack devices.


  • zenoss.dell.snmp.DellDeviceModeler
This plugin is for retrieving the basic Dell hardware and os information. The following plugins will be used for modeling Blade and Chassis Controller details using the iDRAC controller via WSMAN interface.


  • iDRAC6Modeler
This plugin is for modeling Dell Remote Access Controller 6.


  • iDRAC7Modeler
This plugin is for modeling Dell Remote Access Controller 7.


  • DellIDRACModeler
This plugin is for retrieving the basic iDRAC manufacturer, firmware information.
Datasource Types


  • SNMP
  • WSMAN


Monitoring Templates
  • PhysicalDisk (/Server/Linux/Dell, /Server/Windows/Dell , /Server/Dell/iDRAC6, /Server/Dell/iDRAC7)
  • Temperature (/Server/Linux/Dell, /Server/Windows/Dell)
  • PowerConsumption (/Server/Linux/Dell, /Server/Windows/Dell)
  • ChassisPowerConsumption (/Server/Dell/ChassisController)
  • ProcessorCache (/Server/Linux/Dell, /Server/Windows/Dell)
  • Processor (/Server/Dell/iDRAC6, /Server/Dell/iDRAC7)



Service Impact and Root Cause Analysis

When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact and root cause analysis capabilities for services running on Dell PowerEdge. The service impact relationships shown in the diagram and described below are automatically added. These will be included in any services that contain one or more of the explicitly mentioned components.


Chassis and Blade(modeled via SNMP) Impact Relationship Diagram
NonBlade device(modeled via SNMP) Impact Relationship Diagram
Blade device(modeled via iDRAC) Impact Relationship Diagram


Internal Impact Relationships
  • Chassis Controller access failure impacts all the blade devices available in its slots.
  • Chassis Management Controller failure impacts all related hosts, chassis slots, temperature sensors, power consumption, power supply units.
  • Blade/NonBlade Host failure impacts the related physical disks, virtual disks, temperature sensors, memory cards, processors, processor caches, power consumption, chipsets, ports, cooling fans.
  • In iDRAC modeling, Blade Host failure impacts the related physical disks, virtual disks, memory cards, processors, chipsets, enclosureview, softwares, videocontrollers.




Most of the impacts described above follow the default policy of a node being in the worst state of the nodes that impact it. For example, a Chassis Management Controller failure will imply that all related hosts are also failed.




Usage

Adding ChassisController

Use the following steps to start monitoring ChassisController using the Zenoss web interface.

  1. Navigate to the Infrastructure page.
Add Device
  1. Navigate to organizer Devices/Server/Dell/ChassisController.
  2. Choose Add a Single Device from the add button.



  1. Fill out the form.
Add Dialog
    • Name can be anything you want.
    • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
  1. Click ADD.






Adding Linux SNMP Dell Blade/Rack device

Use the following steps to start monitoring Linux Dell PowerEdge device using the Zenoss web interface.


  1. Navigate to the Infrastructure page.
    Add Device
  2. Navigate to organizer Devices/Server/Linux/Dell.
  3. Choose Add a Single Device from the add button.



  1. Fill out the form.
    Add Dialog
    • Name can be anything you want.
    • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
  2. Click ADD.
  3. Dell Blade / Rack server that runs on Linux will be added in the /Devices/Server/Linux/Dell device class.




Adding Windows SNMP Dell Blade/Rack device

Use the following steps to start monitoring Windows Dell PowerEdge device using the Zenoss web interface.

  1. Navigate to the Infrastructure page.
    Add Device
  2. Navigate to organizer Devices/Server/Windows/Dell.
  3. Choose Add a Single Device from the add button.




  1. Fill out the form.
    Add Dialog
    • Name can be anything you want.
    • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
  2. Click ADD.
  3. Dell Blade / Rack server that runs on Windows will be added in the /Devices/Server/Windows/Dell device class.






Adding Dell Blade/Rack information to the /Server/Microsoft/Windows Organizer

Use the following steps to monitor a Windows Device using the ZenPacks.zenoss.Microsoft.Windows zenpack.

  1. Navigate to the Infrastructure page.
  2. Navigate to organizer Devices/Server/Microsoft/Windows.
  3. Select Details
  4. Select Modeler Plugins
  5. Add zenoss.dell.snmp.PowerEdgeModeler and zenoss.dell.snmp.DellDeviceModeler to the Selected list
  6. Save


Adding iDRAC6 controller

Use the following steps to start monitoring iDRAC6 using the Zenoss web interface.

  1. Navigate to the Infrastructure page.
    Add Device
  2. Navigate to organizer Devices/Server/Dell/iDRAC6.
  3. Choose Add a Single Device from the add button.


  1. Fill out the form.
    Add Dialog
    • Name can be anything you want.
    • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
  2. Click ADD.
  3. iDRAC6 controller of Dell Blade server will be added in the /Devices/Server/Dell/iDRAC6 device class. Use the following steps for successful modeling.
  4. Select the device added.
  5. Navigate to Configuration Properties.
    Add Dialog
  6. Provide the values for zWSMANPassword, zWSMANPort, zWSMANUseSSL and zWSMANUserName.
  7. Model the device.





Adding iDRAC7 controller

Use the following steps to start monitoring iDRAC7 using the Zenoss web interface.

  1. Navigate to the Infrastructure page.
    Add Device
  2. Navigate to organizer Devices/Server/Dell/iDRAC7.
  3. Choose Add a Single Device from the add button.


  1. Fill out the form.
    Add Dialog
    • Name can be anything you want.
    • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
  2. Click ADD.
  3. iDRAC7 controller of Dell Blade server will be added in the /Devices/Server/Dell/iDRAC7 device class. Use the following steps for successful modeling.
  4. Select the device added.
  5. Navigate to Configuration Properties.
    Add Dialog
  6. Provide the values for zWSMANPassword, zWSMANPort, zWSMANUseSSL and zWSMANUserName.
  7. Model the device.






zenbatchload

  • Alternatively you can use zenbatchload to add devices from the command line.
  • To do this, you must create a file with contents similar to the following.
  • Replace all values in angle brackets with your values minus the brackets.
  • Multiple devices can be added under the same sections.
'/Devices/Server/Dell/ChassisController' <device name>  setManageIp="<IP Address>"
'/Devices/Server/Dell/iDRAC7' <device name>  setManageIp="<IP Address>", zWSMANUsername='<username>', zWSMANPassword='<password>', zWSMANPort=443, zWSMANUseSSL='true'
'/Devices/Server/Dell/iDRAC6' <device name> setManageIp="<IP Address>", zWSMANUsername='<username>', zWSMANPassword='<password>', zWSMANPort=443, zWSMANUseSSL='true'
'/Devices/Server/Windows/Dell' <device name> setManageIp="<IP Address>"
'/Devices/Server/Linux/Dell' <device name> setManageIp="<IP Address>"


Example : /Server/Dell/ChassisController CMC_1 setManageIp='10.100.10.30'
Example : /Server/Dell/iDRAC6 iDRAC6_1 setManageIp='10.100.10.32', zWSMANUsername='root', zWSMANPassword='calvin'
Example : /Server/Dell/iDRAC7 iDRAC7_1 setManageIp='10.100.10.31', zWSMANUsername='root', zWSMANPassword='calvin'
Example : /Server/Windows/Dell Windows-Blade setManageIp='10.100.10.27'
Example : /Server/Linux/Dell Linux-Blade setManageIp='10.100.10.29'


You can then load the Devices using zenbatchload with the following command.

zenbatchload <filename>




Upgrade

Upgrading of Dell ZenPack from version of 1.0.0 to new version 2.0.0 Bulbgraph.png Note: Refer to Prerequisites section

Use the following steps to upgrade from Dell PowerEdge 1.0.0 to 2.0.0
  1. On the Zenoss Master
  2. Backup the original __init__.py file located in $ZENHOME/ZenPacks/ZenPacks.zenoss.Dell.PowerEdge-1.0.0-py2.7.egg/ZenPacks/zenoss/Dell/PowerEdge
  3. Copy the 2.0.0 egg file onto the zenoss master filesystem
  4. Extract the patched __init__.py with the following command
    • unzip *Dell.PowerEdge-2*.egg patches/__init__.py
  5. copy the __init__.py to $ZENHOME/ZenPacks/ZenPacks.zenoss.Dell.PowerEdge-1.0.00-py2.7.egg/ZenPacks/zenoss/Dell/PowerEdge
  6. Install the 2.0.0 version of the Dell PowerEdge zenpack through UI / CLI.
  7. On all collectors, run the following command if you wish to keep all performance data. This is due to a relationship change.
    • find $ZENHOME/perf/Devices -name Blade_Index* -exec sh -c 'mv "${0}" "${0/Blade_Index_/Main System Chassis}"' {} \;
  1. Re-start the zenoss instance on the master.
  2. Push the updates to the remote hubs/collectors.
    • Verify the Upgrading to Dell PowerEdge ZenPack 2.0.0 with the following command.
    • zenpack --list | grep -i PowerEdge



Limitation

Dell Servers running VMware are not monitored by this ZenPack. Currently this ZenPack does not recognize / model IO modules and Fans of Chassis.

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.Dell.PowerEdge-*.egg
  4. Restart these services:
    $ zenoss restart


Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus