Owners Manual

Dell Integrated Systems for Oracle Business Analytics (DISOBA) – Owner’s Guide 1.0
ports 0/4 and 0/5 on the S60 management switch is connected to the public network
adapters on the R320 management server. This is the route in to the management server
from the customer’s public environment that is isolated as VLAN 10 network traffic. Once
connected to the management server, any of the DISOBA hardware components that are
on the isolated private rack network VLAN 30 can be accessed for management or
monitoring.
Users can connect to the management server
 Using a browser on their client-machine to log in to the management server’s
iDRAC for graphical console, or
 Using a terminal on their client-machine to SSH in to the management server’s
public IP for faster command line access
NOTE: The IP address for the iDRAC7 or the bonded public adapters on the management
server need to be configured first at the customer’s site before any user can remotely
access them.
And, once remotely logged in to the management server (MS), the user can connect to
any of the DISOBA components with any of the options listed in Table 5.
DISOBA Component
Graphical (Use Browser on MS)
CLI (Use Terminal on MS)
OBIEE Server (R730)
iDRAC
SSH (private management IP)
Database Nodes* (R920s)
iDRAC
SSH (private management IP)
DAAD Storage Arrays
iDRAC
SSH (private management IP)
Brocade 6510 Switches
Management IP
SSH (management IP)
S6000 Switches
Management IP
Telnet (management IP)
S60 Switch
Management IP
Telnet (management IP)
Table 5 DISOBA Components Remote Management Connectivity Options
*IMPORTANT: Though the Database Nodes can be accessed directly via its Oracle public
network ports, it is strictly recommended not to connect to it for management or
monitoring purposes. Oracle public network should be strictly used for database traffic.
Refer to Table 4 for the pre-assigned private IP addresses for each of the DISOBA
hardware components on the private rack network.