ASAP 3.0 Server Transfer of Information

© 2005 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

ASAP 3.0 Server

Transfer of Information

April 2008 2TOI Template—

ASAP 3.0 Product Overview• Monitors Status and Performance of NSK Servers

– Hardware

– Operating system

– Software subsystems and applications

• Alerts When Something Isn’t Right– EMS event alerts

– ASAP Client or Website alerts

– Email, pager alerts

Applications Comm CPU Disk Expand ExpandIP

Files Nodes Process ProcessBusy RDF Spooler

Swap Tape TCP/IP TELSERV TMF

C-Series D-Series G-Series H-Series J-Series

TNSII TXP Himalaya RISC Integrity Blades


ASAP 3.0 Product Overview• Alerts Based on Your Criteria

– Goals can specified on 1,000s of attributes

– Reports the data AND what it means to you

• Optionally Takes Actions to Correct Conditions– Issuing operator commands

– Executing complex macros

• Stores History For Years if Needed– Automatically managed historical database

– Store details, aggregate summaries or both

• Provides Many Interfaces– Published APIs

– HP Operations


ASAP 3.0 Product Overview• And Does Many Other Things

– Consumes few resources

– Runs measure on demand

– Supports customer add-ons

– Co-exists with other products or runs standalone

– Supports a single node or many nodes

– Runs multiple copies without limit

– Runs in the background or as the primary operator interface

– Provides many levels of customization

– Accesses data via textual CI, graphic console or via interfaces to other products

– Continues to grow and be enhanced


ASAP 3.0 Product Overview• Target Market

– Existing ASAP customers (free upgrade)

– Existing customers running higher-priced 3 Party solutions

– Any new NSK customer

• Related Products– ASAP Extension 2.07 (T0403)

– ASAP Hybrid for NSK Server 1.00 (T0404)

– ASAP Hybrid for Linux 1.00 (T0405)

– ASAP TCP/IP Plug-in (T0406) will no longer be available, it has been rolled back into the main product (for free !)

• Version Information– ASAP 3.0 is the 10th new version of ASAP since its first

release in June of 1999


ASAP 3.0 Product Overview• Support Considerations

– GMCSC Level 1 and Level 2 support

– Development Level 3 support

– Use [email protected] to email development team

• Additional Sources of Information– www.NonStopASAP.com website

– ASAP Manuals (Client, Server, Messages)

– OMF Migration Guide Manual

– New ASAP QuickStart Guide available with ASAP 3.0

• Please see ASAP 2.0 TOI materials for architecture, data structures and flows, and other technical information about ASAP Server

mailto:[email protected]

http://www.nonstopasap.com/


ASAP 3.0 New Server Features• Historical Database Enhancements

– Relative files using alternate keys– Refresh on/off

• TCP/IP and TelServ Support– New ASAPTCP SGP – 19 new entities supported, 1,000+ new attributes

added• CPU Memory Support

– ASAPMON CPU SGP enhanced– 6 new memory attributes reported for CPUs

• Virtual Memory Support– New SWAP SGP– 17+ new attributes added

• Product is Now Licensed


Historical Database Enhancements• Originally Key-sequenced only

– Worked great for many year but load could be noticeable

– Supported partitioning to spread the load

– Excessive block-splits at high volume with large records remained a problem

• Can now define database files as Relative– Uses alternate key search path

– Much more efficient at high volume even with large records

– DBTCP (TCP/IP) defaults to Relative

– All other DB files remain Key-sequenced by default

SET PARTITION DEFAULT | <entity> TYPE R


Historical Database Enhancements• Originally only Refresh ON

– Causes file label to be re-written at each EOF change

– Probably not necessary for all environments

• Can now turn Refresh OFF– File label not re-written at EOF change

– Less disk I/O activity

– Refresh ON remains the default

SET PARTITION DEFAULT | <entity> REFRESH OFF


TCP/IP and TELSERV Support• Optional TCP/IP Plug-in Available with ASAP 2.8

– Supported TCP/IP v4 (conventional)

– Supported TCP/IP v6 in compatibility mode only and only via SAM processes

– Supported ICMP, IP, Process, QIO, RTE and UDP stats

– Supported Subnet, Route and Port stats

– Supported TelServ Process, Service and Window stats

– Was a chargeable extra plug-in

– Customers complained about having an extra plug-in to buy


TCP/IP and TELSERV Support• ASAP 3.0 Includes Enhanced TCP/IP Support

– Supports TCP/IP v4 (conventional)

– Supports TCP/IP v6 in all modes (does not use SAM)

– Supports ICMP, IP, Process, QIO, RTE and UDP stats

– Also supports ARP, IGMP, LOOP, MONGQ and SOCK stats

– Also supports ICMP6 and IP6 stats

– Supports Subnet, Route and Port stats

– Supports TelServ Process, Service and Window stats

– A total of 19 new TCP/IP and TelServ entities in ASAP 3.0

– More than 1,000 new attributes in EDL

– Is now a part of the base product, at no extra charge


TCP/IP and TELSERV Support• Use SET TCP ON to turn on TCP/IP and TelServ• PORT, SERVICE and WINDOW monitoring is OFF by

default– Use SET TCP PARAM “<name>” to enable– SET TCP PARAM “PORT, SERVICE, WINDOW” enables all

3• BE WARNED !

– TCP can produce a lot of historical data– Recommend a minimum rate of 5 minutes– Use SET TCP PARAM “RATE 5” if ASAP rate is less than 5

minutes– DBTCP defaults to largest possible size Format 1 file– Use SET PARTITION FORMAT2 ON to create as Format 2– Use SET PARTITION TCP ALL PRIEXT | SECEXT <x> to

increase file size


TCP/IP and TELSERV Support• ASAPTCP gets information about TCP/IP and TELSERV

using an SCP process

• You Must Specify an SCP Process for ASAPTCP to Use– SET TCP PARAM “SCPNAME <name>”

– Sometimes $ZNET can be used without problems

– Other times a separate SCP process should be started prior to starting ASAPTCP• SCP/NAME $ZNEA, NOWAIT, CPU 1/0; AUTOSTOP -1

• ASAPTCP uses the SPI protocol to communicate with its SCP process

• SCP process sends request to TCP/IP and TELSERV


TCP/IP and TELSERV Support• TCP Automatically Discovers and Monitors ALL Objects

– All TCPIP and TCP6MAN processes

– All TELSERV processes

– All stats for all monitored processes

– All Routes and Subnets

– All Ports, Services and Windows if enabled for monitoring

• Can use MONITOR command to only monitor specific processes, Ports, Routes, Subnets, Services or Windows

• If a process is monitored, then all stats (entities) subordinate to the process are produced

• If a process is not monitored (and others are) then Port, Route, Subnet, Service or Window stats for that process are also not monitored


TCP/IP and TELSERV Support• Monitor Route, Subnet, Service and Windows for

Processes that aren’t monitored by specifically monitoring them with MONITOR commands

• Monitoring Examples– Specify nothing, all things will be monitored

– MONITOR TCPPROCESS $ZPTM0• Only monitor this TCP/IP process

• Only Routes and Subnets subordinate to this process will be monitored

– MONITOR ROUTE $ZPTM1.RT1• Monitors this specific route regardless of whether or not

process $ZPTM1 is monitored

• Note this only monitors this ROUTE unless others are specified

– MONITOR PORT 23


TCP/IP and TELSERV Support• You Cannot Separately Monitor

– Individual TCP entities (except Process, Port, Subnet and Route). They are monitored when the Process is.

– Ports that belong to processes that are not monitored

• Automatically Monitored Objects Refresh Differently– Configured objects (TCP and TELSERV Processes, TCP

Subnets and TELSERV Services) only reconfigure once per hour• In other words once each hour ASAP checks to see if there

has been a change in configuration

– Dynamic objects (TCP Ports and Routes, TELSERV Windows) reconfigure at each interval

– Can always force a reconfiguration using the COMMIT command


TCP/IP and TELSERV Support• You Can Set Goals on Almost Anything

– Goals can be set on any TCP entity or sub-entity on almost any attribute

– Use the SHOW <entity> command to display the attributes within an entity

– Those with an asterisk can have goals set against them

• So Many Attributes, So Little Screen Real Estate– There are literally thousands of attributes reported for

TCP/IP and TELSERV.

– ASAP Client cannot possibly display all the attributes available at the same time

– We have defined an initial set of attributes to be displayed

– Use the Client Properties Sheet to customize your display


TCP/IP and TELSERV Support• You Can Use Abbreviations!

– TCPPROCESS can be abbreviated TCP– TELSERVPROCESS can be abbreviated TELSERV– All other TCP<name> can be abbreviated <name>– All other TELSERV<name> can be abbreviated

<name>– MONITOR TCP $ZPTM1– MONITOR ROUTE $ZPTM1.RT1– MONITOR TELSERV $ZTN01– MONITOR WINDOW $ZTN01.PTY03A

• You can specify “#” or not– MONITOR ROUTE $ZTCP1.#RT1 (or just RT1)

• You can specify “$ZZTCP.#” or not– MONITOR TCP $ZZTCP.#ZPTM0 (or just $ZPTM0)


TCP/IP and TELSERV Support• Use the TCP Command to Display TCP/TELSERV Data

– TCP (displays all TCP/TELSERV objects without details)

– TCP <entity-name> (displays a specific entity)

– Can use Entity Abbreviations

– TCP ARP, DETAIL (display detailed ARP data for all TCPs)

– TCP ARP $ZPTM1, DETAIL (display ARP data for $ZPTM1)

– TELSERV entities have additional abbreviations• TELSERVPROCESS TP

• TELSERVSERVICE TS

• TELSERVWINDOW TW

– TCP TW, DETAIL (display Window data for all Windows)

– SEE HELP TCP for more options


CPU Memory Support• New Memory Attributes added to CPU and System

Entities– PageSz Number of bytes per page.

– MemSize Total physical memory size

– MemSwap Number of swappable pages

– MemLock Virtual Memory locked pages

– MemFree Free memory pages available

– MemLockMax Max amount of Virtual pages

– MemLockHigh Highest amount of locked memory since CPU was loaded.


CPU Memory Support• Use the MEMORY or MB option with the CPU command

to display the enhanced Memory counters.– CPU, MEM will display Pagesize, MemSize, MemSwap,

MemLocked, MemFree and MemLockMax counters in pages.

– CPU, MB will display Pagesize, MemSize, MemSwap, MemLocked, MemFree and MemLockMax counters in Megabytes.

– CPU,RAW,TAB,STATE,MB is the command used by the client and will display all of the above counters plus the MemLockHigh counters in Megabytes.

– CPU,AVG,MEM will display the average Pagesize, MemSize, MemSwap, MemLocked, MemFree and MemLockMax counters in pages.

– CPU, AVG, MB will display the average Pagesize, MemSize, MemSwap, MemLocked, MemFree and MemLockMax counters in Megabytes.


CPU Memory Support• You Can Set Goals on the following attributes

– MemSize Value specified in MB

– MemSwap Value specified in MB

– MemLock Value specified in MB

– MemFree Value specified in MB

– MemLockMax Value specified in MB

– MemLockHigh Value specified in MB

Examples:

Goal CPU 2, MemFree > 3000, MemLock < 2000

Goal SYSTEM, MemFree > 1500, MemLock < 2800


Virtual Memory Support• ASAP 3.0 Includes KMSF Support. Named the SWAP

SGP.– Provides Total virtual Swap space allocated in all KMSF

files for every CPU.– Provides the total Reserved space for all the swap files

for each CPU.– Provides the total Available space for all swap files for

each CPU. – Provides the number of swap files for each CPU.– Provides the Sum of KMSF Reservations for all segments

for each CPU.– Provides the Full percentage for all swap files for each

CPU.– Provides the Available percentage for all swap files for

each CPU.– Provides the total Reservations made for process

creations for each CPU during each sample interval.


Virtual Memory Support • SWAP Features Continued.

– Provides the number of Failed reservations for process creates during each sample interval for each CPU

– Provides the total Reservations released during the sample interval for each CPU

– Provides the number of failed Reservations released during the sample interval for each CPU

– Provides the successful reservation resizes during the sample interval for each CPU

– Provides the number of failed reservation resizes during the sample interval for each CPU

– Provides the successful allocations made in all the swap files during the sample interval for each CPU

– Provides the number of failed allocations made in all the swap files during the sample interval for each CPU


Virtual Memory Support • SWAP Features Continued.

– Provides the Successful freed allocations during the sample interval for each CPU

– Provides the number of failed freed allocations during the sample interval for each CPU

– Provides individual swap file statistics.• Name of all the swap files for each CPU

• Percentage full of the each swap file

• The total space allocated on disk for each swap file.

• The total Reserved space for each swap file

• The total Available space for each swap file


Virtual Memory Support • SWAP SGP Configuration.

– SET SWAP ON. Enables Virtual memory monitoring.

– SET SWAP CPU <cpuno>. Starts the SWAP SGP process $ZOOA in the specified CPU.

– SET SWAP object $vol.subvol.filname. Uses the swap file object filename located on $vol.subvol.filename. Set SWAP OBJECT $SYSTEM.ZASAP.ASAPSWP

– SET SWAP PARAM “RATE <minutes>”. Instructs the Swap SGP to get virtual memory stats at the sample interval defined by minutes.

– SET SWAP PARAM “DEBUG”. Starts the Swap SGP in debug mode. This is an undocumented parameter that is only to be used by Support and Development staff members. Should never instruct a customer to use this parameter.


Virtual Memory Support • SWAP MONITORING and GOALS

– The Swap SGP discovers all of the Swap files configured in KMSF.

– User monitoring in this release is only by CPU and not by individual swap file.• MONITOR SWAP <cpuno>

– Goals can be set on the following Swap attributes:• Status• Files• TotalSwap in MB• Reserved in MB• Available in MB• Reservations • Creates OK/Failed• Release OK/Failed• Resize OK/Failed• Allocates OK/Failed• Frees OK/Failed

– Goal Swap 3, Files = 4, CreatesFailed < 5, TotalSwap > 4200


Virtual Memory Support • SWAP SGP display commands.

– SWAP. Displays by CPU status information.• UP/Down, No File, NoVol, No Buf.

• Number of Swap Files Configured.

• Total Swap space for all configured swap files in MB.

• Percent available swap space available

• Percent swap space used.

• Total Reserved space for all swap files in MB

• Total Available space for all swap files in MB

• Sum of KMSF reservations for all segments


Virtual Memory Support • SWAP SGP display commands continued.

– SWAP, DETAIL. Displays by CPU additional status information.• Creates OK. Number of successful Reservations made for

process creates during the Swap sample interval

• Creates FAILED. Total number of failed Reservations made for process creates during the Swap sample interval

• Releases OK. Number of successful Reservations Released during the Swap sample interval

• Releases FAILED. Number of failed Reservations Released during the Swap sample interval

• ReSizes OK. Number of successful Reservations Re-Sizes during the Swap sample interval

• ReSizes FAILED. Number of failed Reservations Re-Sizes during the Swap sample interval



– SWAP, DETAIL continued.• Allocates OK. Number of successful Allocations made in

the swap files during the Swap sample interval.

• Allocates FAILED. Number of failed Allocations in the swap files during the Swap sample interval.

• Frees OK. Number of successful Freed allocations during the Swap sample interval.

• Frees FAILED. Number of failed Freed allocations during the Swap sample interval.



– SWAP, FILE. Displays by CPU individual swap file status information.• All the configured Swap file names for each CPU

• Percentage full for each configured swap file

• The total disk space allocated for each swap file

• The total Reserved space for each swap file

• The total Available space for each swap file


Virtual Memory Support • SWAP SGP FYI’s

– The Swap SGP starts a process named $<ASAPID>B which is a SeeView Server Gateway process. Uses this process to communicate with NSKCOM.

– Swap SGP issues 2 NSKCOM commands at each sample interval. • Status Swapfile *,CPU <cpuno>• Status KMSF, CPU <cpuno>

– Parses the NSKCOM output by keywords and maintains the keywords and values in the Parsed^Values table.

– All percent values are calculated by the SWAP SGP.– Deltas values are calculated for the OK/Failed

attributes. – Swap stats are stored a page values and stored in the

ASAP database file DBSWP. Megabyte values are calculated by the ASAP CI.


Product is Now Licensed• A License Key is Required for Each Node

• Email [email protected] to Obtain License Keys– Supply SYSINFO output from each system

– Indicate whether ASAP Hybrid and ASAP Extension also execute on each of the systems

• License Keys Returned via Email– One file per system

• Install License Keys– FTP (ASCII) license file to NSK Server

– Rename as $SYSTEM.SYSTEM.ASAPLIC

– Then Start ASAP

mailto:[email protected]


References• Please see ASAP 2.0 TOI materials for architecture,

data structures and flows, and other technical information about ASAP Server

• Additional Sources of Information– www.NonStopASAP.com website

– ASAP Manuals (Client, Server, Messages)

– OMF Migration Guide Manual

– New ASAP QuickStart Guide available with ASAP 3.0

http://www.nonstopasap.com/

ASAP 3.0 Server Transfer of Information

Documents

Transcript of ASAP 3.0 Server Transfer of Information