Instructions follow
NOTE: Your device names returned may be different than shown below. 
Please substitute your device names.


1) Log into your system over telnet, ssh, modem, or serial connection. Do not use the console.

2) Redirect console messages (from a telnet or other remote session)
# touch /tmp/console
# swcons /tmp/console

3) Disable getty temporarily.
If you dont do this, you might not be able to remove the vty or vsa device. 
# vi /etc/inittab

change:
cons:0123456789:respawn:/usr/sbin/getty /dev/console
to:
cons:0123456789:off:/usr/sbin/getty /dev/console


3.5) Reprocess the inittab file
# telinit q

4) Check your existing console entry, adapters and devices:
# lscons (used only to see current setting)
/dev/vty0

# lsdev -C | grep sa
vsa0 available
vsa1 defined
vsa2 defined

OR
sa0 available


# lsdev -Cc tty
vty0 available
vty1 defined
vty2 defined
tty0 available



5) Remove all the devices, adapters, and syscons entries from 
ODM.

# odmdelete -q name=vsa0 -o CuDv
0518-307 odmdelete: 1 objects deleted.

# odmdelete -q name=vsa1 -o CuDv
0518-307 odmdelete: 1 objects deleted.

# odmdelete -q name=vsa2 -o CuDv
0518-307 odmdelete: 1 objects deleted.

# odmdelete -q name=sa0 -o CuDv
0518-307 odmdelete: 1 objects deleted.



6) Remove all vty's or the tty for your console

# odmdelete -q name=vty0 -o CuDv
0518-307 odmdelete: 1 objects deleted.

# odmdelete -q name=vty1 -o CuDv
0518-307 odmdelete: 1 objects deleted.

# odmdelete -q name=vty2 -o CuDv
0518-307 odmdelete: 1 objects deleted.

# odmdelete -q name=tty0 -o CuDv
0518-307 odmdelete: 1 objects deleted.



7) Very important. Remove the syscons entry from ODM.

# odmdelete -q attribute=syscons -o CuAt
0518-307 odmdelete: 1 objects deleted.


8) Run the bosboot command and save ODM changes with
savebase.

# bosboot -ad /dev/ipldevice
# sync
# savebase


9) Reboot

At boot, the configuration manager (cfgmgr) will reconfigure vsa0 
and vty0 (or tty) and prompt you to assign the console - this, since 
"syscons" is no longer set.


TROUBLESHOOT

If you are unable to get a login prompt after the above steps
and you still have a login over network via telnet or ssh, do
the following:

1) On command line run
# kdb

At the (0)> prompt type in "f 1" and enter
On the second line of the output, it should have a number
something like [0006fB48] et_wait+#######

et_wait is normal operation for the console - nothing is
holding the port from being opened successfully. If it
is anything else, the system may be blocked from 
spawning a getty to your console due to a program
or application error in the /etc/inittab file.

These applications are often started in the "wait"
mode where the system will start them and wait
for them to return/complete before continuing (even
though the system boots OK).

2) If you still have problems with console, try adding
"clocal" to the stty attributes for runtime and attibutes
for login (it must be set in both).

you may have to follow the above procedure to
edit inittab and swcons so you can access/change
the device.