HP OneView for Microsoft System Center Instruction Manuals and User Guides
We have 21 Instruction Manuals and User Guides for OneView for Microsoft System Center HP
Manuals
| Recognized languages: | English |
|---|---|
| Pages: | 16 |
| Size: | 218 KB |
Show table of contents
Read manual
Document Outline
- HP ProLiant Updates Catalog (v 2013.02.0) User Guide
- Contents
- 1 Introduction
- 2 Support matrix
- 3 Installing the HP ProLiant Updates Catalog
- 4 Using the HP ProLiant Updates Catalog
- 5 Reference
- 6 Troubleshooting
- 7 Deploying firmware and software updates manually
- 8 Support and other resources
- 9 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 27 |
| Size: | 504 KB |
Show table of contents
Read manual
Document Outline
- HP SCOM Management Packs User Guide
- Contents
- 1 Overview
- 2 User Guides for HP features for SCOM
- 3 Support Matrix
- HP BladeSystem Management Pack (v 2.1) for System Center
- HP ProLiant Agentless Management Pack (v 3.1) for System Center
- HP ProLiant Linux Management Pack (v 3.1) for System Center
- HP ProLiant PRO Management Pack (v 2.1) for System Center
- HP ProLiant Server Management Pack (v 2.2) for System Center
- HP ProLiant VMware Management Pack (v 3.1) for System Center
- HP Device Monitor Console (v 1.2)
- HP Device Monitor Service (v 1.2)
- HP Custom Data Manager (v 1.0)
- HP Virtual Connect Management Pack (v 3.1) for System Center
- 4 Installing and managing the HP SCOM Management Packs
- 5 Troubleshooting
- Monitoring view displays multiple HP Linux Servers folders and duplicate alerts might be reported
- Monitoring view displays multiple HP VMware Servers folders and duplicate alerts might be reported
- Retry option in Windows 7 or in Windows Server 2008 R2 Installer does not work
- Required services failed to start after an upgrade or fresh install of the DMS
- 6 Support and other resources
- 7 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 32 |
| Size: | 1007 KB |
Show table of contents
Read manual
Document Outline
- HP ProLiant Linux Management Pack (v 3.1) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using this management pack
- Using the Monitoring view
- Viewing all HP ProLiant servers that run supported versions of Linux operating system software
- Identifying a failed subsystem
- Viewing and analyzing alerts
- Launching the HP Device Monitor Console
- Adding a server
- Updating a managed server
- Removing a managed server
- Launching HP Integrated Lights-Out for a failed subsystem
- Launching the HP System Management Homepage task
- Using Run As profiles
- 3 More about this management pack
- 4 Events
- 5 Troubleshooting
- Introduction
- Discovery issues
- Authoring issues
- Operational and usage issues
- Alert notifications repeat the value displayed in Path, and the Path and Source values appear to be swapped
- Monitoring view displays multiple HP Linux Servers folders
- Researching state monitoring
- Expected associated classes are not displaying in the Server State view or the Health Collection view
- Event view and Performance view are empty
- Tasks cannot be launched from the Health Explorer properties page or the Product Knowledge page
- Diagram view displays initials of folder names
- Active Alerts view displays only one alert when there are multiple device state changes
- A previously monitored HP Linux server disappears from the Operations console with no related alerts
- HP Agentless servers that use AMS are discovered and listed in HP Linux Servers or HP VMware Servers views
- HP Systems view displays the same server multiple times
- Health Explorer does not display Knowledge information for computers and certain Windows components
- HP Custom Data Manager cannot be used with this management pack
- Device Monitor (DMC and DMS) operational and usage issues
- 6 Support and other resources
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 23 |
| Size: | 574 KB |
Show table of contents
Read manual
Document Outline
- HP ProLiant SCCM 2012 Integration Kit (v 2013.02.0) User Guide
- Contents
- 1 Introduction
- 2 Support matrix
- 3 Installing and configuring the HP ProLiant SCCM 2012 Integration Kit
- 4 Deploying Windows Server to ProLiant servers
- 5 Collecting extended inventory data
- 6 Reference
- 7 Troubleshooting
- Install fails immediately after a reboot
- The Create HP ProLiant Deployment Task Sequence wizard listboxes are empty
- The target server boots to WinPE but the task sequence doesn’t start
- Updated or new hardware configuration input files were not used
- After rebooting during the task sequence, the target server reports Invalid system disk or BOOTMGR is missing
- The target server fails to join the domain
- The inventory tool is installed but does not run
- The inventory tool runs but data is not collected
- 8 Support and other resources
- 9 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 35 |
| Size: | 3.93 MB |
Show table of contents
Read manual
Document Outline
- HP SCVMM 2012 Console Integration Kit (v 1.x) User Guide
- Contents
- 1 Overview
- 2 Support matrix
- 3 Installing and configuring the HP SCVMM 2012 Console Integration Kit
- 4 Using the HP SCVMM 2012 Console Integration Kit
- 5 HP Fabric Management NT events
- 6 Reference
- 7 Troubleshooting
- Import of Console Add-in throws error in Italian/French OS
- Unable to add VC Domain through the cmdlets
- Launch iLO tasks are disabled
- Launch iLO task not supported if iLO is in a different network than VMM management/console
- Reinstall is not supported
- Alerts not generated for Refresh All Data if HPCS cannot communicate with VCM
- Managed Hyper-V host reported as not managed
- Details missing when SCVMM console launched by user other than domain administrator
- Get-VirtualConnect and Set-VirtualConnect cmdlets do not update new VC management IP address if IP is changed
- VC FlexNICs connected to empty VC I/O bays are not reported
- Changing default browser setting
- ‘Refresh All’ appears to hang
- VCM password is changed inside the VCM console
- Delete a profile and reassign a new profile while using VC assigned logical UUID
- New system added to a domain shows an error when the Add-in is launched
- Configuration changes made to a domain do not show up in the ‘Configured VC Domains’ view
- Domain added using Add-in’s PowerShell cmdlet (Add-VirtualConnect) does not show up in the ‘Configured VC Domains’ view
- 8 Support and other resources
- 9 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 29 |
| Size: | 782 KB |
Show table of contents
Read manual
Document Outline
- HP SCVMM 2012 Console Integration Kit (v 2.0) User Guide
- Contents
- 1 Overview
- 2 Support matrix
- 3 Installing and configuring the HP SCVMM 2012 Console Integration Kit
- 4 Using the HP Fabric Management add-in
- 5 Using the HP Add Capacity Wizard
- 6 Reference
- 7 Troubleshooting
- Reinstall or upgrade fails
- Import Console Add-in wizard fails on Italian/French OS
- If the add-in has been removed and re-imported, then the add-in will not work
- HP OneView appliance or VCM added using the cmdlet does not show up in the Configured Fabric Managers view
- VCM configuration changes do not show up in the Configured Fabric Managers view
- If a VCM domain has been recreated, then the add-in may display an error
- If the HP OneView appliance IP address has changed, then the add-in will display an error and the Get-HPOneView and Set-HPOneView cmdlets will fail
- If the VCM IP address has changed, then the Get-VirtualConnect cmdlet will not show updated information and the Set-VirtualConnect cmdlet will fail
- If the HP OneView appliance or VCM password has changed, then add-in will display an error
- If a new host is added to an existing VCM, then the add-in will display an error
- VCM managed host reported as not managed
- If an HP OneView or VCM assigned profile using logical UUID is deleted and a new profile is assigned to a host, then the add-in will display an error
- Launch Remote Console and Launch iLO Web actions are disabled for VCM managed hosts
- Launch action fails
- Refresh All Data appears to hang
- Deploy server(s) link is disabled
- Alerts not generated for Refresh All Data action if HPCS cannot communicate with VCM
- To change the Launch action default browser
- 8 Support and other resources
- 9 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 95 |
| Size: | 3.66 MB |
Show table of contents
Read manual
Document Outline
- HP ProLiant Server Management Pack (v 1.x & 2.3) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using the HP ProLiant Server Management Pack
- Overriding the HP ProLiant Server Management setting for the SNMP and WMI management protocol preferences
- Monitoring HP ProLiant servers
- Using HP ProLiant servers predefined tasks
- Launching the HP System Management Homepage task
- Launching the HP Systems Insight Manager task
- Creating a custom HP Systems Insight Manager task
- Launching the Remote Desktop and Computer Management tasks
- Launching the HP ProLiant Integrated Management Log tasks
- Launching the HP Integrated Lights-Out task
- Starting failed services using HP ProLiant Management Tasks
- Analyzing HP alerts
- Using diagnostic scripts
- Discovering servers and clients
- Adding customized information
- Configuring a Run As profile
- 3 More about the HP ProLiant Server Management Pack
- HP ProLiant Server Management Pack elements
- WMI management and planning
- Views
- Tasks for HP ProLiant servers
- Classes
- Discovery rules
- Event processing rules
- Monitors
- State monitors
- 4 HP ProLiant servers NT events (SNMP)
- 5 HP ProLiant servers NT events (WMI)
- ProLiant memory events
- ProLiant processor events
- ProLiant remote management processor event
- ProLiant sensor events
- ProLiant system events
- ProLiant Ethernet events
- ProLiant Smart Array events
- ProLiant SAS events
- ProLiant SCSI events
- ProLiant Fibre Channel events
- ProLiant SATA events
- ProLiant Advanced Server Settings events
- 6 Troubleshooting
- Introduction
- Administrative issues
- Authoring issues
- Operational and usage issues
- Management pack and HP tools are not functioning on a managed node where Health Service is installed
- Using Microsoft Excel to update custom data with Custom Data Manager
- Displaying HP events as alerts on the SCOM console
- Researching state monitoring
- HP Health Collection state monitoring and failed component information
- Health Explorer shows a healthy status for disabled software services
- No HP ProLiant server appears in any DL, BL, or ML group
- System is discovered as an HP ProLiant server but is not monitored
- Expected associated classes do not appear in the Server State view or the Group State view
- Event view and Performance view are empty
- The Server State view shows a server that is no longer monitored, but the Group Diagram view still shows that the server is monitored
- Alert Descriptions in the Alert Properties view are truncated
- Alert notifications repeat value displayed in Path, and Path and Source values appear to be swapped
- Not all component statuses are updated instantly after a previously monitored device comes back online
- Limitations on using the Operations Manager Gateway Server
- The Group Diagram view shows folders named by initials
- Server icon or alert state of a managed server appears gray
- The HP System Management Homepage task shortcut is not accessible
- Web Console is a read-only view and is not supported in this release of the HP ProLiant Server Management Pack for System Center
- Server not monitored with HP Insight Management WBEM Providers
- Server not monitored with HP Insight Management Agents
- Diagnostic script results not updated when HP ProLiant server WMI Cooling Collection monitor changes state
- Incorrect HP Insight Management Agents version appears in the SCOM console
- HP ProLiant Server WMI Health Collections are not discovered in the SCOM console
- The server state is warning or critical, but System Management Homepage does not show any state errors
- HP ProLiant Management Tasks do not start failed HP Insight Management Agent services
- HP ProLiant Management Tasks can report an unexpected exit code
- HP ProLiant virtual nodes are not visible in the SCOM console
- Virtual Machine Computer objects display in Windows Computers view
- Client systems running on non-server Windows (for example, ProLiant Workstation Blades) do not appear in the SCOM console
- Workstation client nodes are discovered even when the parameter Enabled in the Client Discovery Rule is overridden to False
- Workstation client nodes are discovered even when the Client Discovery Rule is disabled after upgrade to HP ProLiant Server Management Pack version 1.30 or higher
- Active Alert view displays only one alert when there are multiple device state changes
- 7 Support and other resources
- 8 Documentation feedback
- A Installing the HP ProLiant Server Management Pack for System Center 1.x
- B HP ProLiant Server Management Pack (v 1.x) for Microsoft System Center Support Information
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 60 |
| Size: | 3.52 MB |
Show table of contents
Read manual
Document Outline
- HP BladeSystem Management Pack (v 1.x) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Installing HP BladeSystem Management Pack 1.x
- Installation overview
- Installing the HP BladeSystem Management Pack 1.x
- Installation results
- Uninstalling the HP BladeSystem Management Pack for Operations Manager
- Repairing the installation of the HP BladeSystem Management Pack for Operations Manager
- Modifying the HP BladeSystem Management Pack for Operations Manager installation
- 3 Using the Enclosure Monitor Manager
- Launching the Enclosure Monitor Manager
- Connecting to the Enclosure Monitor Service
- Refreshing monitor data
- Adding enclosures
- Removing managed enclosures
- Modifying enclosure configuration
- Modifying enclosure login
- Launching the HP Onboard Administrator website
- Launching the HP BladeSystem Management Pack help
- 4 Using the HP BladeSystem Management Pack with Operations Manager
- 5 More about the HP BladeSystem Management Pack
- 6 Enclosure monitor performance and scalability guidelines
- 7 BladeSystem NT events
- 8 Troubleshooting
- Introduction
- Enclosure monitor management issues
- Authoring issues
- Operational and usage issues
- Researching state monitoring
- An HP p-Class Server Blade does not appear in the HP BladeSystem Enclosure Group
- Expected associated classes are not displaying in the Enclosure State view or the Health Collection view
- Event view and Performance view are empty
- Alert notifications value is repeated in Path; Path and Source values appear to be swapped
- Tasks cannot be launched from the Health Explorer properties page or the Product Knowledge page
- The Group Diagram view displays initials of folder names
- State icon or alert state appears gray
- A fan or power supply icon appears when no fan or power supply is installed in the bay slot
- Active Alert view displays only one alert when there are multiple device state changes
- Management console displays the same enclosure multiple times
- Management console does not display alerts in the Active Alert view window when opened from the Enclosure State view
- Health Explorer does not display Knowledge information for computers and certain Windows components
- HP Custom Data Manager cannot be used in the HP BladeSystem Management Pack
- Enclosure Monitor Manager operational and usage issues
- The monitor manager is unable to connect to the monitor service because of a connection issue
- The monitor manager is unable to connect to the monitor service because of an incompatible version
- The monitor manager is unable to connect to the monitor service because of user credentials
- The monitor manager status line displays failure status
- The monitor manager fails to validate an enclosure registration
- The Details pane in the monitor manager is not updated automatically
- A critical state displays in the monitor manager for the monitor service
- A critical state displays in the monitor manager for a managed enclosure
- The default Internet browser is not used when opening the Onboard Administrator web page
- Unable to launch a wizard in the monitor manager due to a lost connection
- Unable to launch a wizard in the monitor manager due to multiple user connections
- Add Enclosure wizard does not add an unverified enclosure
- Modify Enclosure Login wizard or Modify Enclosure Configuration wizard does not update an unverified enclosure
- Changes made in Modify Enclosure Login wizard or Modify Enclosure Configuration wizard are not immediately reflected in the monitor service
- A newly added enclosure appears in the Tree pane, but no information is available in the Details pane
- Downgrade of Onboard Administrator firmware is not supported
- Updating the Onboard Administrator password
- 9 Support and other resources
- 10 Documentation feedback
- A HP BladeSystem Management Pack (v 1.x) for Microsoft System Center Support Information
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 13 |
| Size: | 190 KB |
Show table of contents
Read manual
| Recognized languages: | English |
|---|---|
| Pages: | 37 |
| Size: | 1.19 MB |
Show table of contents
Read manual
Document Outline
- HP ProLiant Agentless Management Pack (v 3.1) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using this management pack
- Using the Monitoring view
- Viewing all HP ProLiant Agentless servers
- Identifying a failed subsystem
- Viewing and analyzing alerts
- Launching the HP Device Monitor Console
- Adding a server
- Updating a managed server
- Removing a managed server
- Launching HP Integrated Lights-Out for a failed subsystem
- Using Run As profiles
- 3 More about this management pack
- 4 Events
- 5 Troubleshooting
- Introduction
- Discovery issues
- Authoring issues
- Operational and usage issues
- Alert notifications repeat the value displayed in Path, and the Path and Source values appear to be swapped
- Researching state monitoring
- Expected associated classes are not displaying in the Server State view or the Health Collection view
- Event view and Performance view are empty
- Tasks cannot be launched from the Health Explorer properties page or the Product Knowledge page
- Diagram view displays initials of folder names
- Active Alerts view displays only one alert when there are multiple device state changes
- Active Alerts view displays an additional BladeSystem OA test alert when an iLO Management Engine test alert occurs
- HP Agentless server uses AMS, but Network Monitors and Realtime Monitors are not displayed in the Operations console
- HP Agentless servers that use AMS are discovered and listed in HP Linux Servers or HP VMware Servers views
- HP Systems view displays the same server multiple times
- Health Explorer does not display Knowledge information for computers and certain Windows components
- HP Custom Data Manager cannot be used with this management pack
- Device Monitor (DMC and DMS) operational and usage issues
- 6 Support and other resources
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 22 |
| Size: | 319 KB |
Show table of contents
Read manual
Document Outline
- HP ProLiant SCCM 2012 Integration Kit (v 2014.02.0) User Guide
- Contents
- 1 Introduction
- 2 Support matrix
- 3 Installing and configuring
- 4 Deploying Windows Server to ProLiant servers
- 5 Deploying ProLiant firmware and software updates
- 6 Collecting extended inventory data
- 7 Troubleshooting
- 8 Support and other resources
- 9 Documentation feedback
- A Hardware Configuration
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 33 |
| Size: | 2.76 MB |
Show table of contents
Read manual
Document Outline
- HP BladeSystem Management Pack (v 2.x) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using the HP BladeSystem Management Pack with Operations Manager
- 3 More about the HP BladeSystem Management Pack
- 4 BladeSystem NT events
- 5 Troubleshooting
- Introduction
- Authoring issues
- Operational and usage issues
- Researching state monitoring
- An HP p-Class Server Blade does not appear in the HP BladeSystem Enclosure Group
- No column to display HP enclosure overall state in Monitor Service State view and HP Management Servers view
- Expected associated classes are not displaying in the Enclosure State view or the Health Collection view
- Event view and Performance view are empty
- Alert notifications value is repeated in Path; Path and Source values appear to be swapped
- Tasks cannot be launched from the Health Explorer properties page or the Product Knowledge page
- The Group Diagram view displays initials of folder names
- A fan or power supply icon appears when no fan or power supply is installed in the bay slot
- Active Alert view displays only one alert when there are multiple device state changes
- Management console displays the same enclosure multiple times
- Management console does not display alerts in the Active Alert view window when opened from the Enclosure State view
- Health Explorer does not display Knowledge information for computers and certain Windows components
- HP Custom Data Manager cannot be used in the HP BladeSystem Management Pack
- Device Monitor (DMC and DMS) operational and usage issues
- 6 Support and other resources
- 7 Documentation feedback
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 15 |
| Size: | 236 KB |
Show table of contents
Read manual
Document Outline
- HP ProLiant SCVMM 2012 Integration Kit (v 2014.02.0) User Guide
- Contents
- 1 Introduction
- 2 Support matrix
- 3 Installing and configuring
- 4 Deploying Hyper-V to ProLiant servers
- 5 Deploying ProLiant firmware and software updates
- 6 Troubleshooting
- 7 Support and other resources
- 8 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 17 |
| Size: | 241 KB |
Show table of contents
Read manual
Document Outline
- HP ProLiant Updates Catalog (v 2014.04.0) User Guide
- Contents
- 1 Introduction
- 2 Support matrix
- 3 Installing the HP ProLiant Updates Catalog
- 4 Using the HP ProLiant Updates Catalog
- 5 Reference
- 6 Troubleshooting
- The compliance percentage is 0%
- Initial install status is failed
- Software bundle fails to install
- Firmware bundle fails to install
- With version 2013.09.0, the Windows Server 2008 software bundles do not install the latest HP Insight Management WBEM Providers
- With versions 2014.02.0 and 2014.04.0, the Windows Server software bundles do not install the latest HP Insight Management Agents
- 7 Support and other resources
- 8 Documentation feedback
- A Deploying firmware and software updates manually
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 28 |
| Size: | 466 KB |
Show table of contents
Read manual
Document Outline
- HP SCOM Management Packs User Guide
- Contents
- 1 Overview
- 2 User Guides for HP features for SCOM
- 3 Support Matrix
- HP BladeSystem Management Pack (v 2.1) for System Center
- HP ProLiant Agentless Management Pack (v 3.3) for System Center
- HP ProLiant Linux Management Pack (v 3.2) for System Center
- HP ProLiant PRO Management Pack (v 2.1) for System Center
- HP ProLiant Server Management Pack (v 2.2) for System Center
- HP ProLiant VMware Management Pack (v 3.1) for System Center
- HP Device Monitor Console (v 1.2)
- HP Device Monitor Service (v 1.2)
- HP Custom Data Manager (v 1.0)
- HP Virtual Connect Management Pack (v 3.1) for System Center
- 4 Installing and managing the HP SCOM Management Packs
- 5 Troubleshooting
- Monitoring view displays multiple HP Linux Servers folders and duplicate alerts might be reported
- Monitoring view displays multiple HP VMware Servers folders and duplicate alerts might be reported
- Retry option in Windows 7 or in Windows Server 2008 R2 Installer does not work
- Required services failed to start after an upgrade or fresh install of the DMS
- 6 Support and other resources
- 7 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 66 |
| Size: | 3.30 MB |
Show table of contents
Read manual
Document Outline
- HP OneView Management Pack (v 2.x) User Guide
- Contents
- 1 Overview
- 2 Support matrix
- 3 Installing the HP OneView Management Pack
- 4 Using HP OneView Management Pack
- 5 Using HP OneView Enclosure Management Pack
- 6 Using HP OneView Virtual Connect Management Pack
- 7 HP OneView Event Manager Service
- 8 Troubleshooting
- Administrative issues
- Operational and usage issues
- Active Alert view displays only one alert when there are multiple device state changes
- HP OneView appliance discovery will fail via HP OneView Configuration Dashboard using the appliance hostname on Windows Server 2008 R2
- All discovered managed devices and their subcomponents may disappear during a discovery cycle
- Uninstall may retain files and folders when the HP OneView Management Pack is installed in a custom path
- Scalability guidelines for the HP OneView Management Pack
- 9 Support and other resources
- 10 Documentation feedback
- A Migrating from HP Insight Control Management Packs to HP OneView Management Pack
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 41 |
| Size: | 6.87 MB |
Show table of contents
Read manual
Document Outline
- HP Virtual Connect Management Pack (v 3.0) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using the Virtual Connect Management Pack with Operations Manager
- 3 More about the Virtual Connect Management Pack
- 4 Virtual Connect NT events
- 5 Troubleshooting
- Introduction
- Authoring issues
- Operational and usage issues
- Researching state monitoring
- Expected associated classes are not displaying in the Domain State or Health Collection views
- Event view and Performance view are empty
- Tasks not launching from the Health Explorer Properties or Product Knowledge pages
- The Group Diagram view displays initials of folder names
- Active Alert view displays one alert although multiple device state changes occurred
- Management console displays the same domain multiple times
- Management console does not display alerts in the Active Alert view when opened from the Domain State view
- Health Explorer does not display Knowledge Information for computers and certain Windows components
- HP Custom Data Manager cannot be used in the HP Virtual Connect Management Pack
- Health rollup to VC Domain does not bring the worst case health status from underlying health components
- If a VC FC Uplink becomes unpopulated its health status is set to “Warning” instead of “Healthy”, irrespective of Flex-Fabric and Ethernet uplinks
- If an FC cable is removed from a VC FC module, the alert from the port does not display in the VC Active Alerts view
- When an uplink status restores from Error to Normal, Event ID 7500 is raised in VC Active Alerts view
- Alerts show the IP of the module rather than the overall Primary IP, or statically configured domain IP
- When a static domain IP is configured, any alert raised from a Primary VC module will have the source IP of the domain IP instead of the Primary module IP
- When an Ethernet/Flex Fabric/FC module's power is switched off its Uplink status shows “Healthy”, but the Port status property shows “Not Linked” in the Ethernet/Flex Fabric/FC Uplink Ports State view
- Managing a VC domain via any VCEM web console
- Device Monitor (DMC and DMS) operational and usage issues
- 6 Support and other resources
- 7 Documentation feedback
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 96 |
| Size: | 3.75 MB |
Show table of contents
Read manual
Document Outline
- HP ProLiant Server Management Pack (v 1.x & 2.2) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using the HP ProLiant Server Management Pack
- Overriding the HP ProLiant Server Management setting for the SNMP and WMI management protocol preferences
- Monitoring HP ProLiant servers
- Using HP ProLiant servers predefined tasks
- Launching the HP System Management Homepage task
- Launching the HP Systems Insight Manager task
- Creating a custom HP Systems Insight Manager task
- Launching the Remote Desktop and Computer Management tasks
- Launching the HP ProLiant Integrated Management Log tasks
- Launching the HP Integrated Lights-Out task
- Starting failed services using HP ProLiant Management Tasks
- Analyzing HP alerts
- Using diagnostic scripts
- Discovering servers and clients
- Adding customized information
- Configuring a Run As profile
- 3 More about the HP ProLiant Server Management Pack
- HP ProLiant Server Management Pack elements
- WMI management and planning
- Views
- Tasks for HP ProLiant servers
- Classes
- Discovery rules
- Event processing rules
- Monitors
- State monitors
- 4 HP ProLiant servers NT events (SNMP)
- 5 HP ProLiant servers NT events (WMI)
- ProLiant memory events
- ProLiant processor events
- ProLiant remote management processor event
- ProLiant sensor events
- ProLiant system events
- ProLiant Ethernet events
- ProLiant Smart Array events
- ProLiant SAS events
- ProLiant SCSI events
- ProLiant Fibre Channel events
- ProLiant SATA events
- ProLiant Advanced Server Settings events
- 6 Troubleshooting
- Introduction
- Administrative issues
- Authoring issues
- Operational and usage issues
- Management pack and HP tools are not functioning on a managed node where Health Service is installed
- Using Microsoft Excel to update custom data with Custom Data Manager
- Displaying HP events as alerts on the SCOM console
- Researching state monitoring
- HP Health Collection state monitoring and failed component information
- Health Explorer shows a healthy status for disabled software services
- No HP ProLiant server appears in any DL, BL, or ML group
- System is discovered as an HP ProLiant server but is not monitored
- Expected associated classes do not appear in the Server State view or the Group State view
- Event view and Performance view are empty
- The Server State view shows a server that is no longer monitored, but the Group Diagram view still shows that the server is monitored
- Alert Descriptions in the Alert Properties view are truncated
- Alert notifications repeat value displayed in Path, and Path and Source values appear to be swapped
- Not all component statuses are updated instantly after a previously monitored device comes back online
- Limitations on using the Operations Manager Gateway Server
- The Group Diagram view shows folders named by initials
- Server icon or alert state of a managed server appears gray
- The HP System Management Homepage task shortcut is not accessible
- Web Console is a read-only view and is not supported in this release of the HP ProLiant Server Management Pack for System Center
- Server not monitored with HP Insight Management WBEM Providers
- Server not monitored with HP Insight Management Agents
- Diagnostic script results not updated when HP ProLiant server WMI Cooling Collection monitor changes state
- Incorrect HP Insight Management Agents version appears in the SCOM console
- HP ProLiant Server WMI Health Collections are not discovered in the SCOM console
- The server state is warning or critical, but System Management Homepage does not show any state errors
- HP ProLiant Management Tasks do not start failed HP Insight Management Agent services
- HP ProLiant Management Tasks can report an unexpected exit code
- HP ProLiant virtual nodes are not visible in the SCOM console
- Virtual Machine Computer objects display in Windows Computers view
- Client systems running on non-server Windows (for example, ProLiant Workstation Blades) do not appear in the SCOM console
- Workstation client nodes are discovered even when the parameter Enabled in the Client Discovery Rule is overridden to False
- Workstation client nodes are discovered even when the Client Discovery Rule is disabled after upgrade to HP ProLiant Server Management Pack version 1.30 or higher
- Active Alert view displays only one alert when there are multiple device state changes
- 7 Support and other resources
- 8 Documentation feedback
- A Installing the HP ProLiant Server Management Pack for System Center 1.x
- B HP ProLiant Server Management Pack (v 1.x) for Microsoft System Center Support Information
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 48 |
| Size: | 8.48 MB |
Show table of contents
Read manual
Document Outline
- HP Virtual Connect Management Pack (v 3.1) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using the Virtual Connect Management Pack with Operations Manager
- 3 More about the Virtual Connect Management Pack
- 4 Virtual Connect NT events
- 5 Troubleshooting
- Introduction
- Authoring issues
- Operational and usage issues
- Researching state monitoring
- Expected associated classes are not displaying in the Domain State or Health Collection views
- Event view and Performance view are empty
- Tasks not launching from the Health Explorer Properties or Product Knowledge pages
- The Group Diagram view displays initials of folder names
- Active Alert view displays one alert although multiple device state changes occurred
- Management console displays the same domain multiple times
- Management console does not display alerts in the Active Alert view when opened from the Domain State view
- Health Explorer does not display Knowledge Information for computers and certain Windows components
- HP Custom Data Manager cannot be used in the HP Virtual Connect Management Pack
- Health rollup to VC Domain does not bring the worst case health status from underlying health components
- If a VC FC Uplink becomes unpopulated its health status is set to “Warning” instead of “Healthy”, irrespective of Flex-Fabric and Ethernet uplinks
- When an uplink status restores from Error to Normal, Event ID 7500 or 7800 is raised in VC Active Alerts view
- Alerts show the IP of the module rather than the overall Primary IP, or statically configured domain IP
- When a static domain IP is configured, any alert raised from a Primary VC module will have the source IP of the domain IP instead of the Primary module IP
- When an Ethernet/Flex Fabric/FC module's power is switched off its Uplink status shows “Healthy”, but the Port status property shows “Not Linked” in the Ethernet/Flex Fabric/FC Uplink Ports State view
- When link status is ‘Unpopulated,’ port health status is shown as ‘Warning’ for Ethernet & FlexFabric Uplink Ports
- Managing a VC domain via any VCEM web console
- VC event IDs 7500, 7800 doesn’t show VC uplink port as per VCM
- Event ID 7800 critical alert is not generated
- Both event IDs 7500 and 7800 are raised when an Ethernet or FC uplink is disconnected from VC Flex Fabric Module
- Device Monitor (DMC and DMS) operational and usage issues
- 6 Support and other resources
- 7 Documentation feedback
- Index
| Recognized languages: | English |
|---|---|
| Pages: | 26 |
| Size: | 485 KB |
Show table of contents
Read manual
Document Outline
- HP SCOM Management Packs User Guide
- Contents
- 1 Overview
- 2 User Guides for HP features for SCOM
- 3 Support Matrix
- HP BladeSystem Management Pack (v 2.1) for System Center
- HP ProLiant Agentless Management Pack (v 3.1) for System Center
- HP ProLiant Linux Management Pack (v 3.1) for System Center
- HP ProLiant PRO Management Pack (v 2.1) for System Center
- HP ProLiant Server Management Pack (v 2.2) for System Center
- HP ProLiant VMware Management Pack (v 3.1) for System Center
- HP Device Monitor Console (v 1.1.3)
- HP Device Monitor Service (v 1.1.2)
- HP Custom Data Manager (v 1.0)
- 4 Installing and managing the HP SCOM Management Packs
- 5 Troubleshooting
- 6 Support and other resources
- 7 Documentation feedback
- Glossary
| Recognized languages: | English |
|---|---|
| Pages: | 34 |
| Size: | 1011 KB |
Show table of contents
Read manual
Document Outline
- HP Device Monitor (v 1.2) for Microsoft System Center User Guide
- Contents
- 1 Overview
- 2 Using the HP Device Monitor Console
- Opening the Device Monitor Console
- Adding a DMS connection
- Removing a DMS connection
- Disconnecting from the DMS
- Refreshing monitor data
- Adding devices to the DMS
- Deleting devices from the DMS
- Updating device configuration
- Setting up a non-administrator account to use the DMC
- Accessing HP Device Monitor help
- 3 Using Windows PowerShell with HP Device Monitor
- 4 More about the HP Device Monitor
- 5 Device monitor performance and scalability guidelines
- 6 HP Device Monitor Service NT events
- 7 Troubleshooting the HP Device Monitor
- Introduction
- Device monitor management issues
- DMC operational and usage issues
- DMC connection to DMS service hangs after server power outage
- Unable to add OA through DMC
- Checking DMS operation
- Windows SNMP Trap Service is required for DMS but is disabled on servers using SCOM 2012 for network monitoring
- SCOM does not discover devices
- SCOM does not alert managed devices
- The DMC is unable to connect to the DMS
- The DMC is unable to connect to the DMS because of user credentials
- The DMC status line displays failure status
- A Linux or VMware ESX server is not displayed in the SCOM console after adding a device with the same host name
- A Linux or VMware ESX server is not displayed in the SCOM console after the device is updated
- Events are not being logged in the HP Device Monitor Event log when a non-administrator account is used
- Add Onboard Administrator does not add an unverified enclosure
- Downgrade of Onboard Administrator firmware is not supported
- Updating the password or community string
- Add Agentless Server option not displayed in the DMC
- Cannot launch the DMC from the SCOM console
- Operating System field in the DMC indicates “unknown”
- After changing the hostname of a device, the device is no longer displayed in the SCOM console.
- Active Alert view displays only one alert when there are multiple device state changes
- Add Virtual Connect Domain option not displayed in the DMC
- Active\Primary VC Module IP displayed in DMC instead of Domain IP when VC Domain IP changes.
- Re-creating already discovered VC Domain
- DMC cannot connect to DMS in different domain
- Postgres service fails to start after OS reboot
- 8 Support and other resources
- Index