just go to the command prompt of the server where the application server is
installed and then on that you can type NSH. If in your case only console
is available then its not possible.
I have only access to the BL Console and not the server. Is there a possibility that I can install NSH on my machine and then NSH to that App server using any command line to connect?
A flashing NSH as you desribed usually points to invalid session credentials. At the Console login prompt, you have an option to store session credentials. Did you select that option? If you did and you still have the same problem, then you would need to gather access to that box and to start NSH from the start menu and see if you can get the error message displayed.
If you want to install NSH on the same m/c . You can use NSH installer. You will find more information at https://docs.bmc.com/docs/display/public/bsa83/Installing+only+the+Network+Shell+%28Windows%29
Ok, In case, I am able to get in the Application server, how can I open the NSH with BLAdmin access? its using my Windows credentials currently..
Once you are able to access NSH (after installation of NSH as mentioned by Pankaj) , then you can create
an authentication profile using blcred commands using app server , config port and using authentication type, like below
blcred authprofile -add -profile <profile name> -host <App server hostname>:9840 -type srp
then you can aquire credentials like below using BLAdmin user and password
blcred cred -acquire -profile <profile name> -username BLAdmin -password <BLAdmin password>
1 of 1 people found this helpful
your appserver has NSH installed on it already so please don't try to run the installer again. there is no way to install the appserver w/o nsh. your GUI also has nsh on it, it's kind of core to the product.
if you are running 'nsh here' and have a window pop up then disappear you likely have a couple issues:
- your role:user cannot access the target system you ran 'nsh here' against
- port 4750 is not open to the target system from the system running the GUI/nsh (if you are not using the nsh proxy)
- you are using hte nsh proxy but you didn't check the 'cache crednetials for this session' box when you logged into the gui.
can you please check these ?