Server Login Via SP Console Not Possible on Netra X4270 Platform

Asset ID:	1-72-1932111.1
Update Date:	2018-03-23
Keywords:

Solution Type Problem Resolution Sure

Solution 1932111.1 : Server Login Via SP Console Not Possible on Netra X4270 Platform

Applies to:

Sun Netra X4270 Server - Version All Versions and later
SUSE \ UnitedLinux x86-64

Symptoms

This document is for "Nokia Siemens Networks", but customer does not want to have his Company name in the title, because this Doc in Public.

Issue description:
------------------------------------

1. Login in ILOM and issue the command '-> start /SP/console ' : starts successfully and gets login prompt.
2. Able to enter login name correctly
3. When password entered, unwanted characters displayed in password field, which should be blank, actually and password rejected.

Cause

Login mechanism is provided from the Linux OS

different configuration between working and non working server

Failing server menue.lst ( only console=ttyS0)

title SUSE Linux Enterprise Server 10 SP3
  root (hd0,1)
  kernel /vmlinuz-2.6.16.60-0.54.5-smp root=/dev/system/root console=ttyS0 resume=/dev/md0 splash=silent showopts
  initrd /initrd-2.6.16.60-0.54.5-smp

working server (console=ttyS0,19200 console=tty0):

title SUSE Linux Enterprise Server 10 SP3
root (hd0,1)
kernel /vmlinuz root=/dev/md1 acpi=on console=ttyS0,19200 console=tty0 splash=silent showopts numa=off noht
initrd /initrd

failing server /etc/inittab (entry SUFD::respawn ... missing)

sh:12345:powerfail:/sbin/shutdown -h now THE POWER IS FAILING
1:2345:respawn:/sbin/mingetty --noclear tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
S0:12345:respawn:/sbin/agetty -L 9600 ttyS0 vt100
cons:12345:respawn:/sbin/smart_agetty -L 42 console
pm:2345:respawn:/opt/SMAW/SMAWoamne/bin/pmGenAgtLinuxStart
fm:2345:respawn:/opt/SMAW/SMAWoamne/bin/fmAgtLinuxStart

(please node the modules "pm" and "fm" above are none standard and for this particular customer installation)

working server ( no "cons:" entry but in the failing server):

sh:12345:powerfail:/sbin/shutdown -h now THE POWER IS FAILING
1:2345:respawn:/sbin/mingetty --noclear tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
S0:12345:respawn:/sbin/agetty -L 9600 ttyS0 vt100
SUFD::respawn:/etc/init.d/sufd_rc_script spawn >/dev/console
pm:2345:respawn:/opt/SMAW/SMAWoamne/bin/pmGenAgtLinuxStart
fm:2345:respawn:/opt/SMAW/SMAWoamne/bin/fmAgtLinuxStart

(module SUFD is also customer specific)

failing server /etc/sudoers is missing

working server:

# /etc/sudoers
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/add_to_system_files.sh
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/act_inittab_wait_for_startup.sh
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/edit_inittab.sh
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/replace_hosts_file.sh
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/replace_hosts_equiv_file.sh
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/add_to_etc_services.sh
sdfrun ALL = NOPASSWD: /opt/sdf/sbin/ds_admin
sdfrun ALL = NOPASSWD: /sbin/init q
sdfrun ALL = NOPASSWD: /etc/init.d/secure_iptables reload
sdfrun ALL = NOPASSWD: /opt/cntdb/bin/cntdb_query_state *
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/emergency-fallback.sh
sdfrun ALL = NOPASSWD: /opt/cntdb/sbin/modify_sysctl_conf.sh
sdfrun ALL = NOPASSWD: /sbin/reboot
migration ALL = (sdfrun) NOPASSWD: /opt/sdf/bin/ss
migration ALL = NOPASSWD: /bin/mkdir /opt/sdf/backup/migration
migration ALL = NOPASSWD: /bin/chown migration /opt/sdf/backup/migration
migration ALL = NOPASSWD: /bin/rmdir /opt/sdf/backup/migration
sdfrun ALL = NOPASSWD: /etc/init.d/ldapproxy
sdfrun ALL = (ldapproxy) NOPASSWD: /opt/cntdb/dbm/bin/ldapproxy_configure.sh

(customer specific config in sudoers config as well)

Solution

The below procedure has been tested by customer team in the lab and we are able to simulate the scenario:

1. Login to server as AdminUser and switch to root user
# id

uid=0(root) gid=0(root) groups=0(root)

2. Verify the below files

# ls -ltr /etc/securetty

-rw-r--r-- 1 root root 223 Sep 5 23:13 /etc/securetty

# ls -ltr /etc/inittab

-rw-r--r-- 1 root root 3201 Sep 5 22:45 /etc/inittab

#
3. Create a backup file

# cp /etc/securetty /etc/securetty.orig

# ls -ltr /etc/securetty*

-rw-r--r-- 1 root root 223 Sep 5 23:13 /etc/securetty

-rw-r--r-- 1 root root 223 Sep 6 02:19 /etc/securetty.orig

# cp /etc/inittab /etc/inittab.orig

# ls -ltr /etc/inittab*

-rw-r--r-- 1 root root 3201 Sep 5 22:45 /etc/inittab

-rw-r--r-- 1 root root 3201 Sep 6 02:19 /etc/inittab.orig

#
4. Update the parameters in the files

# vi /etc/securetty

add # to console

like:

#console

Save and Exit

# vi /etc/inittab

add the # to

cons:12345:respawn:/sbin/smart_agetty -L 42 console

like:

#cons:12345:respawn:/sbin/smart_agetty -L 42 console

# Save and Exit

5. Perform the process control initialization with the below command

# init q

6. Login via /SP/console to the server

-> start /SP/console

Are you sure you want to start /SP/console (y/n)? y

Serial console started. To stop, type ESC (

localhost login: <user_name>

Password: XXXXX

Attachments

This solution has no attachment