Library Network Interfaces
The library has four external network interfaces located in the Base Module's card cage on the Library Controller and Root Switch Cards.
- Customer ports — Used to connect the library into the customer's network. Used for library management functions (configuration, code upgrades, monitoring, and so on). Used by applications that use the web services interface (SCI).
- Service port — May be used to connect to a "phone home server" (specifically Automated Service Requests (ASR) using SDP2). If connected to SDP2, the port will be connected continuously. Service engineers can also use this port while servicing the library.
- OKM port — Used to connect the library to an Oracle Key Management (OKM) cluster. However, you may connect to an OKM cluster using the Service or Customer interface.
- Inter-library ports — These ports are disabled and not used in a SL4000 library.
For a diagram of the physical locations of the ports, see "Base Module Card Cage" in the SL4000 Library Guide.
Default Port Numbers
By default, the library uses the port numbers listed in the table below. If using a firewall, configure it to allow traffic to use these ports.
Enable the ports listed below on each of the network interfaces that are in use (except the OKM ports — you only need to enable the OKM ports on the network interface used to connect to the OKM cluster).
| Port | IP | Protocol | Description | Direction |
|---|---|---|---|---|
|
22 |
TCP |
SSH |
SSH access to Linux running on library. Only enabled for 72 hours after an "Escalation" role service user is created. |
To library |
|
25 |
TCP |
SMTP |
Connection to external SMTP (Simple Mail Transfer Protocol) server. Required if you have configured any e-mail destinations. |
From library |
|
53 |
TCP & UDP |
DNS |
DNS (domain name server) lookup. |
From library |
|
80 |
TCP |
HTTP |
Default port for browser access. |
To library |
|
161 |
UDP |
SNMP |
Inbound GET requests through SNMP. |
To library |
|
162 |
UDP |
SNMP |
Outbound SNMP TRAPs. |
From library |
|
123 |
TCP |
NTP |
Connection from library to an external NTP server. |
From library |
|
443 |
TCP |
HTTPS |
Default port for browser and web services interfaces. |
To library |
|
7104 |
TCP |
HTTP |
Alternate port for browser access. |
To library |
|
7102 |
TCP |
HTTPS |
Alternate port for browser and web services interfaces. |
To library |
|
7104 |
TCP |
HTTP |
Browser GUI based access to WebLogic console running on the library. Only accessible by an "Escalation" user. |
To library |
|
7105 |
TCP |
HTTPS |
Browser GUI based access to WebLogic console running on the library. Only accessible by an "Escalation" user. |
To library |
|
Externally Defined |
TCP |
HTTP & HTTPS |
Servers that are configured to receive outbound SCI calls will listen for SCI calls on ports of their choice. Open these port number in any firewalls and provided the port numbers configuring the destination on the library. |
From library |
|
Externally Defined |
TCP |
OKM |
If the library is configured to retrieve tape drive encryption keys from a OKM cluster, open the ports used for OKM (see the OKM documentation). |
From library |
Browser and Web Services Interfaces
The GUI can use both HTTP and HTTPS. The SCI interface uses only HTTPS to secure for the credentials passed in each request. By default, these two protocols are on their standard port number of 80 for HTTP and 443 for HTTPS. You can modify these ports in the GUI (see "Configure the Library with the Configuration Wizard" in the SL4000 Library Guide).
Service Access
Under normal library operations only customer-created users may log in to the library However, the administrator can enable service access when necessary (see Creating Service Users). Creating a service user with an Escalation role enables access to the library that is not normally allowed. Specifically, an Escalation user can log in to Linux on the library using SSH on port 22 and can access the WebLogic console function using port 7104 for HTTP or 7105 for HTTPS. Service users expire 72 hours after creation. The library disables port 22 if there are no enabled service users. The library always enables ports 7104 and 7105, but unless an Escalation user exists, there are no valid users that can log in to the WebLogic console.
SNMP
The library supports SNMP v3 protocol. The library uses ports 161 (inbound) and 162 (outbound) for SNMP GET commands and SNMP traps respectively.
The library can send e-mail messages when certain events occur (see "Configuring Notifications" in the SL4000 Library Guide). If you configure e-mail destinations, you must also configure an SMTP server and open port 25.
DNS
DNS configuration is optional. You only need to configure DNS if destinations (SNMP, E-mail, Outbound SCI) use host names. You can add up to three DNS servers (see "Configure the Library with the Configuration Wizard" in the SL4000 Library Guide). DNS uses port 53.
NTP
The library can use an external NTP server to control the library clock. If using an external NTP server, you must open port 123.
Oracle Key Manager (OKM)
You can connect an OKM cluster to the library's customer port, service port, or OKM port. The location of the OKM appliance within your network determines which port you should use. You select the port during network configuration of the library (see "Configure the Library with the Configuration Wizard" in the SL4000 Library Guide). Unlike older tape libraries, the SL4000 only requires a single connection to OKM, rather than individual connections to each encrypted tape drive. You must open the ports used by OKM on the selected connection. See the OKM documentation for details on which port numbers to use.