A.05.80 HP Insight Remote Support Advanced Managed Systems Configuration Guide (June 2013)
Table Of Contents
- Managed Systems Configuration Guide
- Contents
- About This Document
- Insight Remote Support Advanced Managed Systems Overview
- ProLiant Windows Server Configuration
- ProLiant Linux Server Configuration
- ProLiant VMware ESX Server Configuration
- ProLiant VMware ESXi Server Configuration
- Proliant Citrix Server Configuration
- ProLiant c-Class BladeSystem Enclosure Configuration
- Integrity Windows 2003 Server Configuration
- Integrity Windows 2008 Server Configuration
- Integrity Linux Server Configuration
- Integrity Superdome 2 Server Configuration
- HP-UX Server Configuration
- Meeting HP-UX Operating System, Software, and Patch Requirements
- More About WBEM and SFM with Insight Remote Support
- Verifying System Fault Management is Operational
- Creating WBEM Users
- Configuring WEBES to Support WBEM Indications
- Firewall and Port Requirements for HP-UX Managed Systems
- Configuring HP-UX Managed Systems for Proactive Collection Services
- OpenVMS Server Configuration
- Tru64 UNIX Server Configuration
- NonStop Server Configuration
- Enterprise Virtual Array Configuration
- Understanding the Different Server Types and Software Applications
- Command View EVA 8.0.1 and Higher Hosted on the CMS
- Important Port Settings Information
- Important Information Regarding New HP SIM Installations
- Correcting an Existing HP SIM Installation
- Change the WMI Mapper Proxy port in the HP SIM User Interface on the CMS
- Restore Defaults to the wbemportlist.xml file
- Installing and Configuring Command View EVA After HP SIM
- Resetting the Port Numbers when Command View EVA was Installed before HP SIM
- Command View EVA Hosted on a Separate SMS
- Requirements and Documentation to Configure Command View EVA on the SMS
- Overview of Command View EVA 7.0.1 through 8.0.1 with SMI-S Requirements
- SMS System and Access Requirements
- WEBES – EVA Communication
- HP SIM – EVA Communication
- Software Required on the SMS
- Fulfilling ELMC Common Requirements for a Windows SMS
- Installing MC3 on the SMS
- Configuring EVA-Specific Information on the CMS
- Requirements to Support EVA4400 and P6000 with Command View EVA on the ABM
- Enabling User-Initiated Service Mode in Command View EVA 9.3
- Performing a Remote Service Test in Command View EVA 9.3
- Troubleshooting EVA Managed Systems
- P4000 Storage Systems Migration Procedure
- Network Storage System Configuration
- Modular Smart Array Configuration
- Tape Library Configuration
- System Requirements
- Managed Systems Configuration
- Nearline (Tape Library) Configuration
- Secure Key Manager Configuration
- StoreOnce D2D (Disk-to-Disk) Backup System Configuration
- Enterprise Systems Library G3 Configuration
- TapeAssure Service Configuration
- Prerequisites
- Command View for Tape Libraries and TapeAssure Service Installation
- Configure the Command View TL 2.8 CIMOM and TapeAssure Provider
- Configure the Command View TL 3.0 CIMOM and TapeAssure Provider
- HP SIM Device Discovery
- WEBES Configuration
- Create a New SMI-S Protocol in WEBES
- Subscribe to the Command View TL and TapeAssure CIMOM
- SAN Switch Configuration
- E-Series Switch Configuration
- A-Series Switch Configuration
- UPS Network Module Configuration
- Modular Cooling System Configuration
- Glossary
- Index
Managed Systems Configuration Guide
Chapter 21: SAN Switch Configuration
Community 3: public (rw) No trap recipient configured yet
Community 4: public (ro) No trap recipient configured yet
Community 5: common (ro) No trap recipient configured yet
Community 6: FibreChannel (ro) No trap recipient configured yet
3. Set SNMPV1 community string and Trap recipient:
> snmpconfig --set snmpv1
SNMP community and trap recipient configuration:
Community (rw): [public] gcc-public ! Create new community
Trap Recipient's IP address : [0.0.0.0] 1.2.3.4
Trap recipient Severity level : (0..5) [0] 2
Trap recipient Port : (0..65535) [162] Community (rw): [public]
Trap Recipient's IP address : [0.0.0.0] Community (rw): [public]
Trap Recipient's IP address : [0.0.0.0] Community (ro): [public]
Trap Recipient's IP address : [0.0.0.0] Community (ro): [common]
Trap Recipient's IP address : [0.0.0.0] Community (ro): [FibreChannel]
Trap Recipient's IP address : [0.0.0.0] Committing configuration...done.
Note: The trap severity level is associated with each trap recipient IP address. The event trap
level is in conjunction with the event's severity level. When an event occurs and if its severity
level is at or below the set value, the SNMP event traps (swEventTrap,
swFabricWatchTrap, and connUnitEventTrap) are sent to the trap recipients.
By default, this value is set to 0, implying that no such traps are sent. The possible values are the
following:
n 0 none
n 1 critical
n 2 error
n 3 warning
n 4 informational
n 5 debug
4. Display the new settings:
> snmpconfig --show snmpv1
SNMPv1 community and trap recipient configuration:
Community 1: gcc-public (rw) Trap recipient: 1.2.3.4 Trap port: 162 Trap
recipient Severity level: 2
Community 2: public (rw) No trap recipient configured yet
Community 3: public (rw) No trap recipient configured yet
Community 4: public (ro) No trap recipient configured yet
Community 5: common (ro) No trap recipient configured yet
Community 6: FibreChannel (ro) No trap recipient configured yet
5. Set SNMP access control:
> snmpconfig --set accesscontrol
HP Insight Remote Support Advanced (A.05.80)Page 180 of 204