In the sshd_config file, edit the entry for Port 22 to Port <Number>, where <Number> is the target port number. If you do not want to restart the appliance and make the changes effective, terminate the sshd process by using the kill command, and then restart the process.
When the appliance starts, the following message appears:
Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 10 seconds...” Hit space and you should see the following prompt:
Type '?' for a list of commands, 'help' for more detailed help.
After the appliance starts, the following message appears:
Enter full pathname of shell or RETURN for /bin/sh:
mount /dev/ad0s1a /flash
Run the mount command again to mount the flash directory.
# ssh-keygen -t rsa
# scp id_dsa.pub <user>@<remote_host>/.ssh/id_dsa.pub
# cat id_dsa.pub >> authorized_keys2
# chmod 640 authorized_keys2
# rm id_dsa.pub
Pressing Delete during the POST process displays the appliance’s BIOS settings.
The Load Optimal Settings message box appears.
|Advanced||SuperIO Configuration||Parallel Port Address||Disabled|
|Floppy Configuration||Floppy A||Disabled|
|Boot Settings Configuration||Quiet Boot||Disabled|
|PS/2 Mouse Support||Disabled|
|Remote Access Configuration||Remote Access||COM1|
|Serial Port Mode||9600 8'n'1|
|PCI PnP||Allocate IRQ to PCIVGA||NO|
|Legacy USB Support||Disabled|
|Power||ACPI Aware OS||NO|
You need to reset BIOS when the serial console does not respond. This usually happens after you upgrade the appliance and the serial console is disabled. However, you can still access the appliance by using the telnet or SSH utility.
If the appliance does not receive any packets, it reports a hang condition, because on a network it is very unlikely not to receive any packets. However, if the appliance is plugged into quite interface, you can ignore this error message.
(You can expect the entry for the kernel of the release/build that you just installed to be missing from the file.)
root@LBCOL03B# ./installns installns version (10.0-47.7) kernel (ns-10.0-47.7.gz) Note: Installation may pause for up to 3 minutes while data is written to the flash. Caution: Do not interrupt the installation process. Doing so may cause the system to become unusable. Installation will proceed in 5 seconds, CTRL-C to abort No Valid Netscaler Version Detected root@LBCOL03B#
Am I doing something incorrectly?
This issue could be the result of incorrect version information in the ns.conf file. To resolve this issue, open the ns.conf file in a text editor, such as the vi editor. Update the release-specific entry in the ns.conf file to #NS<Release_No> Build <Build_No>. Here, <Release_No> is the NetScaler release number to which you want to downgrade the software, and the <Build_No> is the build number of the software release to which you want to downgrade the software.
login: nsroot Password: connect: No such file or directory nsnet_connect: No such file or directory Login incorrect
I tried to resolve this issue by using the password recovery procedure, but I was not successful. Have I done something incorrectly?
You cannot resolve this issue by using the password recovery procedure. NetScaler releases 8.0 and later use the new licensing system, based on the Imgrd daemon, which runs during the startup procedure. For this daemon to work properly, the host name of NetScaler appliance, which is set in the /nsconfig/rc.conf file, must be resolved by a name server to the NetScaler IP address. Alternately, you can create a hosts file in the /nsconfig directory and add the 127.0.0.1 <Host_Name> entry in file.
Additionally, make sure that you have copied the license files to the /nsconfig/license/ directory.
What could be the reason?
Changing the netmask of the NetScaler IP might result in a short outage. Make sure that you change the netmask on the secondary appliance, and then break the high availability pairing. Check the functionality of the appliance. If everything works as expected, rebuild the high availability pairing.
To change the netmask on the appliance, run the configns command from the CLI prompt, and then choose the second option in the menu.
#cp /nsconfig/ns.conf /nsconfig/ns.conf.bkup
The ns.conf.bkup file is a backup for the running configuration.