ADC no console after upgrading to 13.1-37.38 error getty: unknown gettytab entry '3wire'
book
Article ID: CTX477635
calendar_today
Updated On:
Description
Netscaler lost console access after HA pair was upgraded to 13.1 build 37.38 and received the following error on console:
Jan 10 21:39:49 ... getty[24784]: tcsetattr /dev/ttyu0: Operation not supported
Jan 10 21:39:49 ... getty[24785]: getty: unknown gettytab entry '3wire'
Jan 10 21:39:49 ... syslogd: last message repeated 1 times Jan 10
Environment
This software application is provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that: (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the software application be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the software application.
Resolution
Please log into the Netscaler via CLI
- Go to shell,
- Inside /ETC directory, delete the gettytab file (if present)
- Inside /NSCONFIG directory, delete the gettytab file (if present)
- Inside /NSCONFIG directory, edit file RC.NETSCALERand delete the following lines (if present)
- cp /nsconfig/gettytab /etc
- cp /nsconfig/gettytab /etc
- echo "default::cb:ce:ck:lc:fd#1000:im=\r\n`hostname` :sp#1200::if=/etc/issue:" >> /etc/gettytab
- Reboot Netscaler
- Previous steps didn't modify the current config, please save the correct configuration before rebooting.
Problem Cause
What triggers the issue
- Command that triggers this is set consoleloginprompt "TEXT"
- This command changed the prompt in the console, it was used for version 12.0 and previous ones.
> set consoleloginprompt "michael" Done>
- The command basically does 3 things:
- Copy gettytab file from /etc to /nsconfig folder
- Add a line “default::cb:ce:ck:lc:fd#1000:im=\r\michael :sp#1200::if=/etc/issue:” in the new /nsconfig/gettytab file
- Finally copy the line “cp /nsconfig/gettytab /etc” in rc.netscaler in order to keep the changes after a reboot.
Why modifying gettytab make an issue
- Gettytab file is for character interpretation. Each time we press a key it helps to display the correct character on the console. If it has any issue we wont be able to work propertly on the console and generate caracter errors.
Why issue showns on 13.1 and not 13.0, 12.0 and 10.0 When the command 'set consoleloginprompt' is executed we do modify the file /etc/gettytab to reflect the change in the prompt by replacing the default entry with a new one including the new prompt string , using the example above: root@sp_adc_13_0# grep ^default /nsconfig/gettytab “default::cb:ce:ck:lc:fd#1000:im=\r\michael :sp#1200::if=/etc/issue:” That works fine until 13.0 because we use FreeBSD 8 as the base until that release. Starting with 13.1 we migrated to FreeBSD 11. From the man page of FreeBSD 11: https://man.freebsd.org/cgi/man.cgi?query=gettytab&apropos=0&sektion=0&manpath=FreeBSD+11.2-RELEASE&arch=default&format=html
Issue/Introduction
Summary: to solve the problem, follow the steps below to delete customed scripts inside gettytab file.
Was this article helpful?
thumb_up
Yes
thumb_down
No