Preparation For Your Operations Console And System I Navigator Configuration - IBM i Series Handbook

Protection tips
When using an Operations Console local console on a network, it is suggested that you complete the
following tasks:
1. If you changed the value of Autocreate service tools device IDs on the system to 0, do the following:
Create an additional service tools device ID for each PC that will be used as a console with console
and control panel attributes.
For more information, see Operations Console simplification.
2. Add one or two additional backup device IDs for use in an emergency. This is not necessary if you
|
| use the option Autocreate service tools device IDs and its value is not zero.
3. Choose nontrivial access passwords. This is not necessary if you let the Operations Console manage
|
this password.
|
4. Protect the Operations Console PC in the same manner you would protect a twinaxial console or an
Operations Console with direct connectivity.
5. Change your password for the following DST user IDs: QSECOFR, 22222222, and QSRV.
| Note: Do not change the password for user 11111111. This is the only user that is included in the
system without an expired password. If you experience a problem with authentication using
|
another user ID, you can attempt to authenticate with 11111111/11111111.
|
6. Add backup service tools user IDs with enough authority to enable or disable user and service tools
device IDs.
Related concepts
"Operations Console simplification" on page 67
Operations Console can automatically create service tools device IDs, manage access passwords, and
discover systems.
Related reference
"Resynchronizing the PC and service tools device ID password" on page 70
By default, the system creates and maintains the service tools device ID and its password. You should
not have to manually resynchronize the password. However, if the system option Autocreate service
tools device IDs is set to 0, then you must manually manage the IDs and their passwords.
Related information
Service tools user IDs and passwords

Preparation for your Operations Console and System i Navigator configuration

Both System i Navigator and Operations Console can be run on a single PC. Depending on how you
connect Operations Console to your system, these network configuration options are available.
System i Navigator is the graphical interface for managing and administering your system from your
Windows desktop. System i Navigator makes operation and administration of systems easier and more
productive.
Operations Console lets you use a local or remote PC to access and control a System i console, a control
panel, or both. Operations Console enables connections or console activities across a local area network
(LAN), along with enabling directly cabled connections. A single PC can have multiple connections to
multiple systems and can be the console for multiple systems. An example is having a logically
partitioned system using the same PC as the console for all partitions. Because each partition is
considered a separate system, you need a separate connection to the partition for which you want to use
the console. Operations Console allows multiple connections to a single system, but only one PC can
have control of the system at a time. Based on the Operations Console connectivity, you can have one of
these methods of configuration:
18
System i: Connecting to System i Operations Console