Votes - , Average rating:
(
)
)
Manafacture: HP
File size: 130.67 kb
File name:
Language of manual:
The document is loading, please wait
 |
The document is loading, please wait
Other manuals for this model:
Desktops - HP Integrity NonStop H-Series (1.98 mb)
Desktops - HP Integrity NonStop H-Series (16.73 mb)
Desktops - HP Integrity NonStop H-Series (957.56 kb)
Desktops - HP Integrity NonStop H-Series (2.38 mb)
Desktops - HP Integrity NonStop H-Series (881.66 kb)
Desktops - HP Integrity NonStop H-Series (965.62 kb)
Desktops - HP Integrity NonStop H-Series (676.93 kb)
Desktops - HP Integrity NonStop H-Series (393.72 kb)
Desktops - HP Integrity NonStop H-Series (776.57 kb)
manual abstract
ASAP Installation and Configuration
ASAP ID and Suffixes
ASAP ID and Suffixes
To uniquely identify an ASAP environment, ASAP uses the concept of an ID. NSX also
used this concept. All processes running in the same ASAP environment have names
that begin with this ID followed by a unique suffix that identifies the component. The
default ID is $ZOO. You can change the ID with the ASAP SET ID command. Once the
ID is set, processes are automatically named at startup.
To check if your ASAP environment is running, use the ASAP STATUS command. The
output tells you which components are running.
This is a sample output of the STATUS command with all entities running:
+status
\ASAP Primry Backup Pri Access Reqs Lmsgs Created ReqTime SrvTime Et
--------- ------ ------ --- ------- ----- ----- -------- ------- ------- ---
$ZOOM V02 0,101 1,064 160 255,255 17876 15 5/11 19 1009:51 1009:51 0
$ZOO0 V02 0,102 160 255,255 16740 1 5/11 19 1009:51 1009:51 0
$ZOO1 V02 1,096 160 255,255 16740 1 5/11 19 1009:51 1009:51 0
$ZOON V02 0,103 RDF 160 255,255 17856 1 5/11 19 1009:51 1009:51 0
$ZOOG V02 0,105 NCP 160 255,255 17857 1 5/11 19 1009:51 1009:51 0
$ZOOH V02 0,106 APP 160 255,255 17777 45 5/11 19 1009:51 1009:51 0
$ZOOJ V02 0,107 DSK 160 255,255 17855 3 5/11 19 1009:51 1009:51 0
$ZOOK V02 0,108 EXP 160 255,255 17855 1 5/11 19 1009:51 1009:51 0
$ZOOL V02 0,109 FIL 160 255,255 17866 4 5/11 19 1009:51 1009:51 0
$ZOOO V02 0,110 SPL 160 255,255 17856 1 5/11 19 1009:51 1009:51 0
$ZOOQ V02 0,111 TAP 160 255,255 17856 1 5/11 19 1009:51 1009:51 0
$ZOOR V02 0,112 TMF 160 255,255 17856 1 5/11 19 1009:51 1009:51 0
$ZOOT V02 0,113 PRO 160 255,255 17856 1 5/11 19 1009:51 1009:51 0
(collect \ASAP.$ZOOS, rate 1, sync 60,1)
+
NCP is the Node entity. The statistics for the CPU, ProcessBusy, and System entities are
collected by an SGP in each CPU; the suffix is the CPU number in hexadecimal from 0
to F. In this example, there are only two CPUs, so only $ZOO0 and $ZOO1 appear. All
other entities have their own private SGP. Each entity has a unique suffix: the Disk
entity is always named idJ, the Tape entity is always named idQ; and so on. The
ASAP Monitor is always named idM; for example, $ZOOM.
Configuration
Adding or Deleting Entities
In OMF, you could add or delete an object type (entity), but this was only a logical
concept. For many OMF object types, deleting all objects of an object type resulted in
OMF stopping the monitoring of this object type. For example, if you deleted all disk
objects from the configuration, disk monitoring stopped.
In contrast, when you use ASAP, deleting all disk objects causes autodiscovery of all
disks. For other object types in OMF, you had to add or delete the entire object type
globally; for example, TMF Transactions. No matter which method was used, all object
types in OMF were dynamically added or deleted, because objects did not have separate
processes. With OMF, all object types were handled by one OMF monitor process.
ASAP Migration Guide for NSX and OMF Users — 520627-001
2 -2
...Other models in this manual:
Desktops - HP Integrity NonStop J-Series (130.67 kb)
Desktops - HP NonStop G-Series (130.67 kb)
Desktops - HP NonStop L-Series (130.67 kb)