For HA pairs, administrative communication must be enabled on both nodes.
The serial port and dedicated iDRAC9 dedicated management port at the rear of the system are the only supported interfaces for console access. Do not connect to the USB and iDRAC direct micro-USB port on the front of the system.
Connect the DB-9 cable to the serial port on the back panel of the system (#2 in the figure above).
Launch a terminal emulation program from your computer and configure the following communication settings:
NOTE: Set the baud rate to 115200 for the system to work correctly; 9600 baud rate does not work.
Press
Enter to activate the console.
NOTE:
It can take up to 5 minutes for the system to display console messages.
The system can take up to 15 minutes to complete the boot process. If you do not see the prompt on your terminal to log in, complete Step 4.
Verify the front blue power LED is on. If it is not, make sure the power cables are fully seated at both ends, and all AC sources are on.
Establish an SOL connection
Connect the RJ-45 cable to the iDRAC management port on the back panel of the system (#1 in the figure above).
Run the
ssh
<iDRAC-IP-address> -l
<iDRAC-username> command to access iDRAC
Log in with the credentials for the iDRAC username.
Run the
console com2 command to initiate the SOL session.
NOTE:Press
Enter until the console loads.
Log in to the system console
Log in to the system console using the
sysadmin username.
localhost.localdomain login: sysadmin
Type the default password, which is the system serial number. The system serial number is a 14-character alphanumeric string starting with "APM." The sticker with the serial number on it is located on the front of the system.
Password: system_serial_number
NOTE:If you type an incorrect password four consecutive times, the system locks out the specified username for 120 seconds. The login count and lockout period are configurable and might be different on your system. See the
DDOS Administration Guide and the
DDOS Command Reference Guide for setting these values.
For Data Domain HA systems, SSH keys created on the active node take 30 seconds to one minute to propagate to the standby node.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\