10.5 The Customer Profile File
Automatic SEA notifications let you dispatch the appropriate corrective actions at your site. An important part of these notifications includes matching system information to the fault and failure messages from SEA. Your customer profile file is the key to this task.
- 10.5.1 How the Profile File Works
- 10.5.2 Number of Profile Files
- 10.5.3 Location of the Profile File
- 10.5.4 Calling the Profile File
- 10.5.5 Profile File Content
10.5.1 How the Profile File Works
When events are identified by automatic analysis, SEA assembles a problem report and attaches your profile text file to the report. The profile file helps the message accurately identify the following:
- The department, location, phone number, and contact person
- The system from which the message originated, including address, physical location, contact person for that system, and so on
In instances where the system includes attached Enterprise Array Controllers or SAN storage, the profile file becomes very important in indicating storage configuration, exact FRUs, and physical location of any failing component.
10.5.2 Number of Profile Files
A system must have access to at least one profile text file. One suggested setup is to have a profile file on each system. However, in a cluster environment it might be more efficient to create a single profile file and store it in a suitable directory on a common, shared disk that all nodes in the cluster have read access to.
Provided that you reference the correct file path (see Section 10.5.4 Calling the Profile File), there is no reason you cannot edit, update, and maintain a profile file in a different location than the suggested default.
10.5.3 Location of the Profile File
Even after installing WEBES, you can manually update the profile file using any text editor. The default name and location for the profile file is in the \config subdirectory under your WEBES (svctools) installation, as shown.
- Tru64 UNIX—/usr/opt/hp/svctools/specific/desta/config
- OpenVMS—SVCTOOLS_HOME:[SPECIFIC.DESTA.CONFIG]
- Windows—\hp\svctools\specific\desta\config
You can, however, locate and name the profile file as desired, provided that the system always has access to it.
10.5.4 Calling the Profile File
So that WEBES can detect the profile file, its path is specified in the following file:
- Tru64 UNIX—/usr/opt/hp/svctools/specific/desta/config/desta.reg
- OpenVMS—SVCTOOLS_HOME:[SPECIFIC.DESTA.CONFIG]DESTA.REG
- Windows—\hp\svctools\specific\desta\config\desta.reg
If you move the profile file from its default location, update the following line in the desta.reg file. You can edit desta.reg with any text editor.
CA.ACHSProfile=filenameFilename is the path and name of the profile file.
In Windows, backslash characters must be doubled for the path be interpreted correctly. For example:
CA.ACHSProfile=C:\\Program Files\\hp\\svctools\\specific\\desta\\config\\profile.txt10.5.5 Profile File Content
The installation process creates a basic profile file for you, based on your answers to the prompts during WEBES installation. The basic content includes contact, company, and system information that you supplied. However, it often is beneficial to add further detail to the file by editing it with a text editor after installation.
Adding storage configuration information to the profile file is very important. For example, when your storage is part of a storage area network (SAN), event detection occurs within the SAN itself, but the event information gets logged to all the hosts attached to the SAN environment. As such, multiple systems may in fact receive event information indicating the same potential failure because of the shared/redundant resource nature of the SAN.
Ultimately, this one event may be reported as multiple events. With accompanying configuration information, however, your administrator is able to build a true picture of where the fault is and more accurately direct resources to the physical location of the problem.
If your system is well bounded (i.e. all storage is direcly attached to SmartArray Controllers on the servers), simpler configuration information usually is enough.
10.5.5.1 Sample Profile 1—Simple
The following is a simple profile.txt depicting:
Customer: Acme Stonecutting, Inc.System Type: ProLiant Model 5500System S/N: V907-BY43-1972 System Name: ARGOSSSystem IP address: 123.4.567.89 Fixed(X) DHCP Served ( )Primary Contact: Fred FlintstoneSecondary Contact: Barney RubblePhone number: (xxx) 555-5555Special Instructions:Check with customer prior to dispatching services. Prior notification to security is necessary for service access to site.Remote call back to system permissible w/prior notification to customer so that account may be enabled.CONFIGURATION INFORMATION:Qty 2 - KZPAC array controllers on PCI bus #1 attached to qty 6 StorageWorks I shelves w/disks.10.5.5.2 Sample Profile 2—MSCS Cluster
The following shows configuration information from a profile.txt depicting:
- 2 ProLiant servers
- Attached to ESA12000/RA8000 Storage Array Subsystem
- The servers are in an MSCS configuration.
CONFIGURATION INFORMATION:MS Cluster SystemsSYSTEM: ProLiant Model: 5500System S/N: V907-BY43-1972 System Name: SNOBALSystem IP address: 192.7.100.99 Fixed(X) DHCP Served ( )SYSTEM: ProLiant Model: 5500System S/N: V903-BW43-1972 System Name: QUEBALSystem IP address: 192.7.100.98 Fixed(X) DHCP Served ( )Compaq FC Switch 16 Serial # 3G944001233TCPIP 192.7.100.100Compaq FCSwitch 16 Serial # 3G944001235TCPIP 192.7.100.101ESA12000 Array ControllerSubsystem Name: Joinerjoiner-Top >> HSG80 ZG91416110 Software S056P-0, Hardware E06joiner-Bottom>> HSG80 ZG83502157 Software S056P-0, Hardware E03ESA12000 Array ControllerSubsystem Name: Partnrpartnr-Top >> HSG80 ZG91516230 Software S056P-0, Hardware E06partnr-Bottom>> HSG80 ZG91516231 Software S056P-0, Hardware E0310.5.5.3 Sample Profile 3—MSCS Cluster with DRM
The following shows configuration information from a profile.txt depicting:
- Data Replicator Storage Solution
- Two (initiator and target) sites
- 2 ProLiant servers on each site
- ESA12000/RA8000 Storage Array Subsystems interconnected by FC Switches between the sites.
- FC SAN is linked between Initiator/Target sites by Compaq FC Gateway ATM interfaces and a leased ATM circuit.
- The servers are in an MSCS configuration.
CONFIGURATION INFORMATION:INITIATOR SITE: DENVERDenver, CO., US1244 E. McGuire Way, Floor 2, Room CR1MS Cluster SystemsSYSTEM: ProLiant Model: 8500System S/N: Q762-BHET-AE43-1305 System Name: FSTBALSystem IP address: 192.7.100.99 Fixed(X) DHCP Served ( )SYSTEM: ProLiant Model: 8500System S/N: Q761-BHET-AE44-0900 System Name: CRVBALSystem IP address: 192.7.100.98 Fixed(X) DHCP Served ( )ESA12000 Storage ARRAY CONTROLLERSubsystem Name: Denverdenver-Top >> HSG80 ZG91416110 Software S056P-0, Hardware E06denver-Bottom>> HSG80 ZG83502157 Software S056P-0, Hardware E03Compaq FC Switch 16 Serial # 3G944001233TCPIP 192.7.100.100 Fixed(X) DHCP Served ( )Compaq FCSwitch 16 Serial # 3G944001235TCPIP 192.7.100.101 Fixed(X) DHCP Served ( )FC GATEWAY Serial # 52623434TCPIP 192.7.100.102 Fixed(X) DHCP Served ( )Dial-in Phone Number to FC Gateway Asynchronous SwitchPh. 303-555-xxxx- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -TARGET SITE: CHICAGOChicago, Ill, CO., US1245 Times Blvd.Floor 7, CR200MS Cluster SystemsSYSTEM: ProLiant Model: 5500System S/N: xxxxxxxxxxxx System Name: SNKBALSystem IP address: 192.7.100.79 Fixed(X) DHCP Served ( )SYSTEM: ProLiant Model: 5500System S/N: xxxxxxxxxxxx System Name: SLDBALSystem IP address: 192.7.100.78 Fixed(X) DHCP Served ( )ESA12000 Array ControllerSubsystem Name: Chicagochicago-Top >> HSG80 ZG91416110 Software S056P-0, Hardware E06chicago-Bottom>> HSG80 ZG83502157 Software S056P-0, Hardware E03Compaq Switch 16 Serial # 3G012000435TCPIP 192.7.100.200 Fixed (X) ) DHCP Served ( )Compaq Switch 16 Serial # 3G9012000422TCPIP 192.7.100.201 Fixed (X) ) DHCP Served ( )FC GATEWAY Serial # 526538653TCPIP 192.7.100.202 FIXED ) DHCP Served ( )Dial-in Phone Number to FC Gateway Asynchronous SwitchPh. 312-222-xxxx