If certain problems occur, you might want to restore the Operations Center configuration
to the preconfigured state where the Tivoli® Storage
Manager servers
are not defined as hub or spoke servers.
Procedure
To restore the configuration, complete the following
steps:
- Stop the Operations Center web
server.
- Unconfigure the hub server by completing the following
steps:
- Issue the following commands on the hub server, where IBM-OC-hub_server_name is
the name of the administrator ID that was created automatically when
you initially configured the hub server:
SET MONITORINGADMIN ""
SET MONITOREDSERVERGROUP ""
SET STATUSMONITOR OFF
SET ALERTMONITOR OFF
REMOVE ADMIN IBM-OC-hub_server_name
- Reset the password for the hub server by issuing the
following command on the hub server:
SET SERVERPASSWORD ""
Attention: Do not complete this step if the hub server is configured
with other servers for other purposes, such as library sharing, exporting
and importing of data, or node replication.
- Unconfigure spoke servers by completing the following steps:
- On the hub server, issue the following command for each
spoke server, where IBM-OC-hub_server_name is
the name of the server group that was created automatically when you
configured the first spoke server, and spoke_server_name is
the server name that is set for the spoke server:
DELETE GRPMEMBER IBM-OC-hub_server_name spoke_server_name
- Check whether any spoke servers remain as members of
the server group by issuing the following command:
QUERY SERVERGROUP IBM-OC-hub_server_name
- After all spoke servers are deleted from the server
group, issue the following commands on the hub server:
DELETE SERVERGROUP IBM-OC-hub_server_name
SET MONITOREDSERVERGROUP ""
- On each spoke server, issue the following commands:
REMOVE ADMIN IBM-OC-hub_server_name
SETOPT PUSHSTATUS NO
SET ALERTMONITOR OFF
SET STATUSMONITOR OFF
- Delete the definition of the hub server by issuing the
following command on each spoke server:
DELETE SERVER hub_server_name
Attention: Do not complete this step if the definition is used
for other purposes, such as library sharing, exporting and importing
of data, or node replication.
- Delete the definition of each spoke server by issuing
the following command on the hub server:
DELETE SERVER spoke_server_name
Attention: Do not complete this step if the definition is used
for other purposes, such as library sharing, exporting and importing
of data, or node replication.
- Restore the default settings on each server by issuing
the following commands:
SET STATUSREFRESHINTERVAL 5
SET STATUSRETENTION 48
SET ALERTUPDATEINTERVAL 10
SET ALERTACTIVEDURATION 480
SET ALERTINACTIVEDURATION 480
SET ALERTCLOSEDDURATION 60
SET STATUSATRISKINTERVAL TYPE=AP INTERVAL=24
SET STATUSATRISKINTERVAL TYPE=VM INTERVAL=24
SET STATUSATRISKINTERVAL TYPE=SY INTERVAL=24
SET STATUSSKIPASFAILURE YES TYPE=ALL
- Restart the initial configuration wizard of the Operations Center.