NonStop Software Essentials Installation and Quick Start Guide

5 Configuring and Starting NonStop Software Essentials
This section covers the conditional configuration steps (required under certain circumstances) and
the steps required to start the NonStop Software Essentials process and access the NonStop Software
Essentials interface, including:
• “Configuring TCP/IP Stacks Outside of the Dedicated Maintenance LAN (Conditional)”
(page 17)
• “Using a Different Protocol File than $SYSTEM.ZTCPIP.PROTOCOL” (page 17)
• “Registering for WBEM Alerts and Lifecycle Events” (page 18)
• “Starting the NonStop Software Essentials Process” (page 18)
• “Configuring OSM (Conditional)” (page 19)
• “Discovering the NonStop System in HP SIM” (page 19)
• “Launching NonStop Software Essentials” (page 19)
Configuring TCP/IP Stacks Outside of the Dedicated Maintenance LAN
(Conditional)
The NonStop Software Essentials server component is shipped out of the box so that it can be used
with the NonStop Software Essentials client component running on the NonStop System Console
(NSC). The NonStop Software Essentials server component listens on the default maintenance LAN
TCP/IP stacks ($ZTCP0 and $ZTCP1). If you want to use a CMS to run the NonStop Software
Essentials client component, you must create and edit an NSECONF file to have the NonStop
Software Essentials server component listen on a different TCP/IP stack.
To create and edit an NSECONF file to change the default stack, follow these steps:
1. Copy the $SYSTEM.ZNSE.NSEEXMPL file in the NSECONF file.
2. Edit the $SYSTEM.ZNSE.NSECONF file and add the Stack=<Stack> entry. The Stack
parameter should point to the TCP/IP process name associated with the IP address used for
discovery in HP SIM; for example:
Stack=$ZTC0
Multiple stacks can be registered by specifying multiple entries for Stack, as follows:
Stack=$ZTC0
Stack=$ZTC1
3. Add the following in the $SYSTEM.ZNSE.NSECONF file if you do not want the NonStop
Software Essentials client running on NSC to communicate with the NonStop Software Essentials
server component:
Ignore_Default_Stacks=On
When needed, the NSECONF file should be created and/or edited before starting the NonStop
Software Essentials process (NSE-HTTP). If the process is already running, it must be stopped and
restarted for the changes specified in the NSECONF file to take effect (see “Starting the NonStop
Software Essentials Process” (page 18)).
NOTE: When configuring an additional TCP/IP stack, you will also need to add that stack to the
OSMCONF file for the NonStop system, as described in “Configuring OSM (Conditional)” (page 19).
Using a Different Protocol File than $SYSTEM.ZTCPIP.PROTOCOL
NonStop Software Essentials uses the $SYSTEM.ZTCPIP.PROCOTOL file internally. If you are
using a different protocol file, or if the protocol file is in a different location, follow these steps to
ensure that NonStop Software Essentials uses your specific protocol file:
Configuring TCP/IP Stacks Outside of the Dedicated Maintenance LAN (Conditional) 17