HP Serviceguard Toolkit for Integrity Virtual Servers manual Hostlogfile full, Loglevellevel

Page 29

--[probe_count <probe count>]

--[polling_interval <Number of seconds between every poll>

where:

lan: It is the LAN that needs to be monitored

ip: It is the target IP address of any target, such as the gateway which is common to all package nodes.

guest_logfile: It is the complete path of the user specified guest log file.

host_logfile: It is the complete path of the user specified host log file.

log_level: It is the extent of logging on both guest and host. The default value is 0. The following table contains the associated log messages with each log level:

Log Level

Associated Log Messages

log_level 0

It is the default log message. It includes messages that

 

cause the script to exit, such as interface is down and

 

pings failed.

log_level 1

It includes messages, such as missed pings. This is useful

 

for situations, wherein, intermittently few pings might be

 

missed, but subsequently pings might start passing. In

 

such a case, a script does not exit with error but the

 

missed pings are logged. It helps in tracking the network

 

stability and reachability.

log_level 2

It is the highest configurable log level. It includes

 

messages for each ping that is executed. It is helpful for

 

diagnostic purposes.

probe_count: It is the number of pings checked to declare an interface down. The default value is 4

polling_interval: It is the number of seconds between every poll. The default value is 2 seconds. The default logging for fatal messages is done in syslog.log on host and guest.

To monitor a single DIO LAN create a service for the specified LAN in the VM or vPar guest configuration file.

To monitor the DIO LAN in the guest, manually edit the package configuration file as described in the following table:

Attribute Name

Value

service_name

<service_name>

service_cmd

/usr/sbin/cmappmgr

 

-node<guest_name>

 

-cmappserver_timeout

 

<time_out_value> -service /

 

opt/hp/cmappserver/

 

cmapp_net_mon.pl

 

--lan<lan_id>

 

--ip<ip_address>

 

[--guest_logfile

 

<full_path_of file_on_guest>

 

--host_logfile <full_

 

path_of file_on_host>

 

--log_level<level>

 

--probe_count<count>

 

--polling_interval

 

<num_of_seconds>]

Example

lan_mon

/usr/sbin/cmappmgr -node remo1 -cmappserver_timeout

240-service /opt/hp/cmappserver/cmapp_net_mon.pl --lan lan0 --ip 192.168.1.154 --guest_logfile /var/adm/vm1_lan0.log --host_logfile /var var/adm/vm1_lan0.log --log_level 1-probe_count 5 --polling_interval 3

Configuring DIO LAN and NPIV disks monitoring using cmappmgr/cmappserver 29

Image 29
Contents Abstract Page Contents Overview HP Serviceguard Toolkit for Integrity Virtual ServersAdvantages DependenciesHP Integrity VM Serviceguard toolkit HP Serviceguard Toolkit for Integrity Virtual Servers VM/vPar as Serviceguard packages Supported configurationFor example, # cmdeployvpkg -m 1 -P vm1 Network componentsStorage considerations Storage considerations #swremove SG-IVS-Toolkit # swinstall -s depot path# swlist -l product SG-IVS-Toolkit Vswitchmgr Vparreset IvshpvmutilsK004vswitchmgr S802vswitchmgrCreating packages Using SG IVS toolkitPreconfiguration Change the vgnamecmd to vgchange -a s Check the configuration of the package Hpvmvolumegroup /dev/vgsharedACmmakepkg -m tkit/vtn/vpar -n vparname pkg.conf Using Serviceguard commandsCd /etc/cmcluster/vm/vParname Cmdeployvpkg command Using SG IVS Toolkit commandsServicename Cmapplyconf -P pkg.confRunning packages Managing packagesMaintaining packages #cmdeployvpkg -m 1 -P vm or vpar nameConverting packages Halting packagesDeleting packages Run cmdeployvpkg -C -P vmname Configuring guest application monitoring service Failure of a monitored VM or vPar guest application Configuring guest application monitoring service Key generation on the VM or vPar guest HP-UX /opt/hp/cmappserverRpm -i cmappserverslesia64.rpm for Sles CmappserverAdd /opt/hp/cmappserver to the path #cmdeployvpkg -P vm1 -x merge -x appmon Cmappservertimeoutcmappserver connection timeout secondsHpux # cmdeployvpkg -P slvm1 -x merge -x appmonConfiguring guest application monitoring service Loglevel Lanmon Usr/sbin/cmappmgr -node remo1 -cmappservertimeoutHostlogfile full Pathof fileonhostAdm/vm1npivdiskmon.log Help VersionUpgrading cmappmgr/cmappserver combination Configuring guest application monitoring service For example # cmmovevpkg -v -P slvm1 -h xyzo2 Online VM guest package migrationOnline VM guest package migration Service monitor detected a failure in guest vmname TroubleshootingRun cmdeployvpkg command with -m 0 option Etc/cmcluster/scripts Mscripts Mastercontrolscript.shCmcluster/scripts/tkit/vtn/ tkitmodule.sh Limitations Information to collect before contacting HP How to contact HPSupport and other resources Related information Typographic conventions HP authorized resellersDocumentation feedback TIP Page Page DMP GlossaryIndex