Softpanorama

May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Getting console via ssh in DRAC

News IPMI Recommended Links Updating the DRAC Firmware iDRAC7 goes unresponsive vFlash
RACADM Command Line Interface  Dell Lifecycle Controller iDRAC Service Module Dell PowerEdge M1000e Enclosure Dell Chassis Management Controll Getting console via ssh in DRAC
IPMI Configuring Platform Events iLO 3 -- HP engineering fiasco PERC controller Humor Etc

Even when you can't connect to the server it is safer to work with command like console via Teraterm then with GUI console. And both DRAC and ILO allow such a mode. In this case you can cut and paste commands from your records or from the Web minimizing possible errors. You can also log everything that you do via Teraterm log facility or some similar method. Don't be blindly chained to GUI console.

Dell default settings of both server BIOS and DRAC allow usage of serial console via ssh.

Here are several links

I have a dell R710 with the idrac express with versions 1.2 firmware. I can login to the idrac via the web interface. I configured the idrac express according to:

http://support.dell.com/support/edocs/software/smdrac3/idrac/idrac12mono/en/ug/pdf/ug.pdf

Page 86 "Configuring iDRAC6 for Viewing Serial Output Remotely Over SSH/Telnet"

I can ssh in to the idrac, I then execute the command according to the manual:

/admin1-> console com2

I get the message:

Connected to Serial Device 2. To end type: ^\

At this point my login is hung, no output and executing the "^\"  does nothing, I have to kill my ssh session.

This is a Red Hat 5.4 Linux machine. I do not care at this point about redirecting the console before boot up so I did not implement Page 90 "Configuring Linux for Serial Console Redirection During Boot"

Cannot find any explanation of the BIOS "redirection after boot enable/disable" setting mentioned on Page 86. I tried both enable and disable, no joy. Can not find good doc on overview and settings on console redirection for the various drac versions, that would be nice.

Any suggestions? Thanks.

===

After further investigation:

I did get console output if I rebooted the system, I could access the bios setup etc.

When the linux kernel is loaded you must perform the steps "Configuring Linux for Serial Console Redirection During Boot". I believe the "redirection after boot enable/disable" setting would be used to disable the use of the tty port so an external device could be connect to it. Would be nice to get a detailed explanation of all these settings. 


Top Visited
Switchboard
Latest
Past week
Past month

NEWS CONTENTS

Old News ;-)

idrac express ssh console com2 redirect

11 Nov 2009 | Dell Community

jwsunc

I have a dell R710 with the iDRAC express with versions 1.2 firmware. I can login to the iDRAC via the web interface. I configured the iDRAC express according to:

http://support.dell.com/support/edocs/software/smdrac3/idrac/idrac12mono/en/ug/pdf/ug.pdf

Page 86 "Configuring iDRAC6 for Viewing Serial Output Remotely Over SSH/Telnet"

I can ssh in to the idrac, I then execute the command according to the manual:

/admin1-> console com2

I get the message:

Connected to Serial Device 2. To end type: ^\

At this point my login is hung, no output and executing the "^\" does nothing, I have to kill my ssh session.

This is a Red Hat 5.4 Linux machine. I do not care at this point about redirecting the console before boot up so I did not implement Page 90 "Configuring Linux for Serial Console Redirection During Boot"

Cannot find any explanation of the BIOS "redirection after boot enable/disable" setting mentioned on Page 86. I tried both enable and disable, no joy. Can not find good doc on overview and settings on console redirection for the various drac versions, that would be nice.

Any suggestions? Thanks.

====

After further investigation:

I did get console output if I rebooted the system, I could acess the bios setup etc. When the linux kernel is loaded you must perform the steps "Configuring Linux for Serial Console Redirection During Boot". I believe the "redirection after boot enable/disable" setting would be used to disable the use of the tty port so an external device could be connect to it. Would be nice to get a detailed explanation of all these settings.

SSH using Dell's DRAC console

www.redhawk.org

The setup of the DELL DRAC for ssh console access.
This setup shows using DHCP for the DRAC ip address, but it can be hard set as well.

    * Enter setup F2
         1. Cursor down to Serial Communications.
         2. Set the other fields to the following.
                o Serial Communication : On with console Redirection via COM2
                o External Serial Connector : Remote Access Device
                o Failsafe Baud Rate : 57600
                o Remote Terminal Type : VT100/VT200
                o Redirection After Boot: Enabled 

         3. Save and exit.   

Now we should be able to ssh to the console.

 ssh vt-11-c -l root

 root@vt-11-c's password:
 Warning: No xauth data; using fake authentication data for X11 forwarding.

 Dell Remote Access Controller 5 (DRAC 5)
 Firmware Version 1.20 (Build 07.03.02)

 $   
To get to the console type:
 connect com2
This message flashes...
 Connected to com2. To end type: '^\'
Then you should have the console login.
 Red Hat Enterprise Linux WS release 4 (Nahant Update 5)
 Kernel 2.6.9-55.ELsmp on an x86_64

 vt-11 login:
To escape type 'CTRL' + '\'
 $ 
To change root password on a DRAC from ssh shell
 $ racadm config -g cfgUserAdmin -o cfgUserAdminPassword -i 2 NewPasswordHere
Now to do power tasks on the dell type smclp.
 $ smclp
 DRAC5 SM-CLP System Management Shell, version 1.0
 Copyright (c) 2004-2007 Dell, Inc.
 All Rights Reserved

cd system1

/system1

show

/system1:

  Targets:
    logs1

  Properties:
    CreationClassName       = CIM_ComputerSystem
    Name                    = 7B0CZC1
    NameFormat              = other
    Dedicated               = 0
    ResetCapability         = 4
    EnabledState            = 2
    RequestedState          = 12
    EnabledDefault          = 2
    HealthState             = 5
    OperationalStatus       = 2
    Description             = PowerEdge 2970

  Verbs:
    cd
    exit
    help
    reset
    show
    start
    stop
    version

    * To reboot the system type "reset"
    * To power off "stop"
    * To power on "start" 

How to enable serial port console redirection to the iDRAC6

Symantec Corp

It is possible to access the serial console of the Symantec Messaging Gateway, Symantec Traffic Shaper and the Symantec Web Gateway via iDRAC6 SSH interface. The Symantec appliance in question will need to have an iDRAC6 card installed. These steps may work on a previous version of the DRAC, all though, they have not been tested.

With a keyboard and monitor attached to the device reboot the device from the CLI interface. When the device is rebooting complete the steps below.

1. Press F2 during post to enter the BIOS setup.

2. Enter the "Serial Communication" configuration within the BIOS

3. Configure with the settings depicted in the attached screenshot.

4. Exit the BIOS and save the settings.

5. When prompted hit CTRL+R to enter the DRAC configuration during post.

6. Configure the DRAC so that it is accessible from your network and configure a password for the root user.

7. Exit the DRAC configuration and save the settings.

After the device has rebooted using an SSH client complete the steps below:

  1. SSH into the DRAC and login with the root user.
  2. Execute the commands below:
The DRAC should now be configured to access serial console. From the DRAC SSH interface run the command below to access the serial console:

console com2

To return to the DRAC interface and disconnect from the console the default escape sequence is ^\ (CTRL+\).

This will allow the same abilities as physically connecting a terminal emulator to the RS232 port of the device. Console redirection is also enabled from POST so the BIOS and associated controller interfaces available during POST can also be access via the serial console.

DRAC console redirection over a SSH tunnel MDLog-sysadmin

| Comments
The Dell Remote Access Controller or DRAC is an interface card by Dell which provides out-of-band management. The controller has its own processor, memory, battery, network connection, and access to the system bus. Key features include power management, virtual media access and remote console, all available through a supported web browser. This gives system administrators the ability to configure a machine as if they were sitting at the local console (terminal).

Since the DRAC card has its own IP separated from the one of the host server it is very common to assign for it a private IP; or even if it has a public IP it might be protected by a corporate firewall, making it very simple to connect from the corporate office, but not from outside. In such cases when you need to connect to the DRAC console from outside a solution is to tunnel over SSH your DRAC traffic.

In order for this to work you need to tunnel ports 443 (SSL) and and 5900,5901 (VNC). This can be achieved with openssh with a command like this:

1
ssh -L 443:dracip:443 -L 5900:dracip:5900 -L 5901:dracip:5901 -l user -N ssh_host

or similar from other ssh clients by mapping the respective ports.

If you would forward just 443, this will allow you to use the web interface of the DRAC card (and all its features, like power management, etc), but not the remote console redirection (5900,5901 are needed for the console to work).

After connecting the ssh tunnel you can just open in your local browser https://localhost/ and get the DRAC interface. The console redirection and it will work as expected.

Note: this solution has the limitation that it will work for only one DRAC console. You can tunnel over ssh multiple drac ips on port 443, like for ex: - localhost:443 -> dracip1:443 - localhost:444 -> dracip2:443, etc. but the remote console will require the ports 5900, 59001 and thus only one can work at the same time.

If you are running the DRAC console over a public IP, and you want to reach it from outside directly you will need to open in your firewall connections to the same ports TCP 443, 5900 and 5901.

Recommended Links

Google matched content

Softpanorama Recommended

Top articles

Sites

Top articles

Sites



Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D


Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: October, 01, 2019