ORBEM
Important |
In StarOS release 21.2 and higher, ORBEM is not supported. |
The system can be managed by a Common Object Broker Request Architecture (CORBA)-based, Element Management System (EMS).
Important |
Commands used in the configuration samples in this section provide base functionality. The most common commands and keyword options are presented. In many cases, other optional commands and keyword options are available. Refer to the Command Line Interface Reference for detailed information about all commands. |
To configure the system to communicate with an EMS:
Procedure
Step 1 |
Set client ID parameters and configure the STOP/TCP port settings by applying the example configuration in Configuring ORBEM Client and Port Parameters |
Step 2 |
Configure Internet Inter-ORB Protocol (IIOP) transport parameters by applying the example configuration in Configuring IIOP Transport Parameters |
Step 3 |
View your new ORBEM configuration by following the steps in Verifying ORBEM Parameters |
Step 4 |
Save the configuration as described in Verifying and Saving Your Configuration. |
Configuring ORBEM Client and Port Parameters
Use the following example to set client ID parameters and configure the SIOP/TCP port settings:
configure
orbem
client id encrypted password password
max-attempt number
session-timeout time
siop-port port_number
event-notif-siop-port siop_notif_port
event-notif-service
end
-
You can issue the client id command multiple times to configure multiple clients.
-
If a client ID is de-activated due to reaching the configured maximum number of attempts, use the activate client id command to reactivate it.
-
If a firewall exists between the system and the EMS, open the SIOP port number and the TCP port number 15011.
-
If the ORB Notification Service is enabled via the event-notif-service command, you can set filters to determine which events are to be sent. By default, the Service sends all error and higher level events, "info" level events for the ORBS facility, CLI command logs, and license change logs. Optionally, configure a filter by including the event-notif-service filter command. Enter this command for each filter you need to configure.
Configuring IIOP Transport Parameters
Use the following example to configure Internet Inter-ORB Protocol (IIOP) transport parameters that enable ORB-based management to be performed over the network:
configure
orbem
iiop-transport
iiop-port iiop_port_number
event-notif-iiop-port iiop_notif_port
end
-
If you are using the Secure Sockets Layer (SSL) option, do not enable the IIOP transport parameter.
-
You configure the ORBEM interface to use SSL by specifying a certificate and private key.
Verifying ORBEM Parameters
Procedure
Step 1 |
Run the show orbem client table command to verify that the client was configured properly. This command lists the configured ORBEM clients and displays their state and privileges. |
Step 2 |
Run the show orbem status command to verify the ORBEM parameter configuration. The following displays a sample of this command's output.
|