Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
ACC Installation and Configuration Guide > Appendix C ACC Service Guard Configuration Notes

Overview

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

In the examples, there are two systems that each have one or more ACC cards, using the dual connect ACC distribution panel accessories. One system is a primary, and one is a secondary. The primary system has the ACC links in active use, and the secondary either does not start the ACC subsystem, or has each link (pmode) in the loopback mode.

There are 2 cases that need to be considered.

  • In the first case, the primary system has an unexpected, catastrophic failure or HP-UX panic.

  • In the second case, the primary system is shutdown (gracefully).

The SG cluster configuration is controlled by a script, run on each system when the system joins the cluster. The script is invoked with options that indicate which subsystems are to be made active, and which are to be inactive.

To control the behavior, in both cases you need to do the following:

  1. In the network configuration file, /opt/acc/cfg/loopback.answ (or the filename you choose), define the port mode for each link to be LBACK. You also need to define Term's for monitor (one for each ACC card).

  2. In the control file, /opt/acc/cfg/zmasterd_list, add statements to start watch and stop watch. The watch daemon is the heart beat generation for the ACC monitor protocol.

    When started, watch enables monitor, and then sends a heartbeat to monitor. Monitor will reset the ACC, if a heatbeat is missed. The ACC reset will put the ACC ports in LBACK (tri-state).

    This handles the case of an unexpected failure where the Service Guard cluster control script does not run with the stop option.

    You also need to make the file path for zmon correct (/opt/acc/cfg/loopback.tmem).

  3. In the start up, /etc/rc.config.d/acc file, make sure that the start flag is 0 (START_ZCOM=0). This allows the Service Guard script to control when to start/stop ACC, so that ACC will not restart automatically following a panic, or powerout event and interfere with the other system.

  4. Edit the Service Guard cluster control script to start and configure the ACC cards when the script is entered as start. An example of a start section is provided at the end of this list.

  5. Edit the Service Guard cluster control script to disable the ACC port and possibly shutdown ACC when the script is entered as stop. An example of a stop section is also provided.

Examples

Here are some examples of sections from a Service Guard cluster control script. In these examples, there is one ACC card and the ACC example file names. In addition, RS-232 / V.35 mode is assumed for active and inactive is LBACK (tri-state) mode. Note, these additions should be in the customer defined functions section of the Service Guard cluster control script.

# This function is a place holder for customer define functions.
# You should define all actions you want to happen here, before the service is
# started.
# ADD customer defined run commands.
#

# ACC subsystem
syslog_msg Starting ACC subsystem
/opt/acc/bin/zmasterd
# Add SNAPlus2 initialization commands here
syslog_msg Send init commands to SNAPlus2 ports

# a 5 sec sleep is recommended here (SR # 5000-716977)
sleep 5

# The zterm utility calls axin API to execute commands
# See example "setRS232.zterm" script below.
#
syslog_msg Resetting SNAPluss2 ports

/opt/acc/bin/zterm /opt/acc/cfg/setRS232.zterm

********************* control script "stop" section ************

# ACC subsystem
# disable the ports to "lback"

# See example "setLBACK.zterm" script below.

/opt/acc/bin/zterm /opt/acc/cfg/setLBACK.zterm

syslog_msg Stopping ACC subsystem
/opt/acc/bin/zmasterd stop

# this last entry is really only needed for patch install, or
# product removal
# a 5 sec sleep is recommended here (SR # 5000-716977)
sleep 5
/opt/acc/bin/zmasterd kill

******************* Example /opt/acc/cfg/zmasterd_list **************

# HP Z7250A- /opt/acc/cfg/zmaster_list file

# Start these daemons when zmasterd is started, and monitor them:
# Start zmlog with -nd option for no console logging.
start zmlog -nd
start zmon cold /opt/acc/cfg/sna_acc_sdlc.tmem
start znode

# Stop these daemons when zmasterd is run with the stop option.
stop zmon
stop znode

# Add other start and stop statements below:
#
# Replace this with SNAPlus2 initialization -- If required.
# sched zx25d_init
start watch
stop watch

******* example zterm command file "setRS232.zterm" *******
pt,0,0,2,3,0000H,0000H
pt,0,1,2,3,0000H,0000H
pt,0,2,2,3,0000H,0000H
pt,0,3,2,3,0000H,0000H
pt,0,4,2,3,0000H,0000H
pt,0,5,2,3,0000H,0000H
pt,0,6,2,3,0000H,0000H
pt,0,7,2,3,0000H,0000H
ex

******* example zterm command file "setLBACK.zterm" *******
pt,0,0,2,3,0000H,8000H
pt,0,1,2,3,0000H,8000H
pt,0,2,2,3,0000H,8000H
pt,0,3,2,3,0000H,8000H
pt,0,4,2,3,0000H,8000H
pt,0,5,2,3,0000H,8000H
pt,0,6,2,3,0000H,8000H
pt,0,7,2,3,0000H,8000H
ex

** example network configuration sna_acc_sdlc.answ (sna_acc_sdlc.tmem) **
*
* Network configuration (ttgen input) file sna_acc_sdlc.answ example for
* Service Guard
*
#include "/opt/acc/cfg/ttgendefine"

ttgen

Configuration
system-name "SNA/ACC Interface sample ttgen input file for SDLC"
program-zlu 100
terminal-zlu 1000
logical-term 800
physical-term 800
buffer-pool 3000000
logical-size 252
queue-Limit 200
transmit-limit 100
unack-limit 5000
port-limit 20000
node-entry 1

Interface-Definition
Z7200A 0 10:4:12 /opt/acc/mux/abs/loop_sna.zabs



Port-Definition
* Clock source is EXT for connection to a DSU that supplies clock
Port 0:0 LBACK 57600 Ext SDLC X1 NRZ
Port 0:1 LBACK 57600 Ext SDLC X1 NRZ
Port 0:2 LBACK 57600 Ext SDLC X1 NRZ
Port 0:3 LBACK 57600 Ext SDLC X1 NRZ
Port 0:4 LBACK 57600 Ext SDLC X1 NRZ
Port 0:5 LBACK 57600 Ext SDLC X1 NRZ
Port 0:6 LBACK 57600 Ext SDLC X1 NRZ
Port 0:7 LBACK 57600 Ext SDLC X1 NRZ

Terminal-Definition
Term 0001 0:0 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"
Term 0002 0:1 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"
Term 0003 0:2 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"
Term 0004 0:3 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"
Term 0005 0:4 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"
Term 0006 0:5 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"
Term 0007 0:6 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"
Term 0008 0:7 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"

Term 600 0:0 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 601 0:1 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 602 0:2 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 603 0:3 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 604 0:4 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 605 0:5 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 606 0:6 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 607 0:7 PORTTEST 0000h 0000h 99 0 0 0 0 "For Loopback Test"
Term 608 0:0 MONITOR 0000h 0000h 01 0 0 0 0 "Used for Watch Feature"

Node-Definition Local-Node 123
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2000 Hewlett-Packard Development Company, L.P.