You mean the agent information is visible to only few users using a console and it works for some?
Yes it is visible to few users using a console with few servers , not for all hosts. Like i can see some of them with my id but other users with the same permission do not see the Agent inforamtion form their console.
can the client running the agent info connect directly to each target on port 4750 ?
is the client configured to use the nsh proxy?
you may want to setup the nsh proxy and configure the client to use that. i'm assuming you can live browse the native objects, like 'filesystem', on these hosts ok ?
can the client running the agent info connect directly to each target on port 4750 ? Question Not clear to me?
is the client configured to use the nsh proxy? No
i'm assuming you can live browse the native objects, like 'filesystem', on these hosts ok ? Yes
On some hosts i am getting Agent Info ,but if i checked randomly i do see agent info on some of them. What is the use of setting up NSH Proxy , i did not configure / use this till now in my environment.
If the client cannot connect to port 4750 on each target system directly, then the ‘agentinfo’ will not work. if that is the case then you should setup the nsh proxy and configure your clients to use it, this will send all nsh traffic from the client through the appserver to the target, so that the client does not need a direct connection to the agent.
yes i can connect to port 4750 via my desktop to all target servers in question, but it is strange that i can see 'agentinfo' via console with domain id , but some of my colleague do not with same BLAdmin right?
What is the error that other colleagues get while doing the agentinfo? What is in the exports file?
Look in the rscd.log on the target servers and see why they are denied. Is there a mapping entry in the rsc files for the people getting denied? Their username in the ‘NSH only’ of the users file.
I do not see any error in the rscd.log file , when one of my colleague try to access any custome command like agentinfo, memory, cpu info etc. it shows him to blank output, but i click and see it comes for me. below is the ACLs settings in my env.
# BLAdmins ACLs
# NSH-only ACLs
are they logged in as their user name or BLAdmin ? if they are logged in w/ their own username, then they are not allowed access because there is no mapping in the users file for them, so you should try pushng acls so that a mapping entry for them shows up in this file.
There are no entries for users other than you for the NSH-only ACL's
That can be one of the reason for such a failure
If they open an NSH shell on their same box,client, and run agentinfo against the same agent, you will get an error of not authorized, test this.
Thanks for the all replies, but that is not the case you suggested, but it looks like other problem i tested some custome commnds with few users. and we have two options:
1. User connects through Local RCP client -> They can access everything and see 'agentinfo,disk, memory' etc.
2. User connects through Citrix client -> They face issue to access these custome command info on some of the the host but not all.
So i am come to conculsion that users connect via Ctrix having issue. Could you please let me know what have to do it at citrix end so that users should see / get all the custome commands info.
What is in the exports file on the target?
Also, do this. open up the gui from citrix. Tail one of the target server’s rscd.log. try and access the target from the citrix client w/ nsh. Look in the rscd log for entries. post those entries.
I did the same which you suggest , i can run nsh command via citrix client , but unable to see any 'agentinfo' , cp, memory info etc. Please find the screen dump and logs as well.
01/24/12 08:43:12.635 INFO rscd - test 3158 -1/-1 (???): ???: FIPS already enabled
01/24/12 08:43:12.665 INFO rscd - 10.18.162.77 3158 0/0 (BLAdmins:raj@PROD.DOMAIN.COM): nsh: nsh -D //test
01/24/12 08:43:34.007 INFO rscd - test 3183 -1/-1 (???): ???: FIPS already enabled
01/24/12 08:43:34.029 INFO rscd - 10.18.162.77 3183 0/0 (BLAdmins:raj@PROD.DOMAIN.COM): agentinfo: agentinfo -D //test test