Archive
Opsware Core unable to communicate to agent running on Symantec PureDisk SuSE server.
Having issue to talk back to Symantec PureDisk SuSE server, port 1002 is closed on PD firewall (iptables). To add this as an exception do the following
1)login to PD server
2) cp -p /etc/puredisk/custom_iptables_rules /etc/puredisk/custom_iptables_rules.orig
3) vi /etc/puredisk/custom_iptables_rules
4) add the following entry
# protocol (tcp,udp,tcmp,all) source[/mask] port
tcp 10.10.10.1 1002
# where 10.10.10.1 is your Opsware CORE IP
5) make the permament change based on the edits and restart firewall
sh /opt/pdconfigure/scripts/installers/ChangeIPTables.sh
6) confirm changes by running iptables -L and make sure that port 1002 for TCP from your core server is there.
7) then go to opsware web gui and run communication test to reestablish your connection back.
Thats it.
If you do like this or any other documents please support my efforts by clicking on any of the AD links.
How do I keep my Red Hat Linux servers up to date with HP Server Automation
Server Automation: Gateway name resolution error – gateway.proxyError
Problem
|
|
|
Minimum permissions required to change “Server Use” or “Deployment Stage”
|
Server Automation / opsware Inventory Model
If you would like to connect to the API documentation that describes the SA Plataform API, you should do the following:
1. You must copy to your local system the certificate (p12 file) available in your SA Core under /var/opt/opsware/crypto/spin/ directory.
2. When importing the certificate, it requires the password provided in the response file used during the installation. The password is included in the %decrypt_passwd parameter.
3. After importing the certificate, access the API documentation. Specify the following URL in your browser:
opsware:1032/twister/docs/index.html Or: opsware:443/twister/docs/index.html
The host is the IP address or host name of the core server running the SA Web Client component.
How to check current aaa permissions on opsware sas
Login to your ogfs (opsware global file system), best by either opening up java gui and then launch global shell or ssh to port 2222.
cd to /opsw/Permissions/UserGroups/
in that directory you will see all bunch of groups defined in your opsware, if you get to any of them, just for example lets go to:
Opsware System Administrators
How to properly uninstall opsware sas agent from solaris client server that has bunch of local zones.
Practically you have to uninstall opsware agent in both Global and all Local zones on your Solaris client box. Steps to completely uninstall your opsware sas agent are as follow, best way to uninstall everything correctly is to run the following:
/opt/opsware/agent/bin/agent_uninstall.sh –delete_opsw_rpm
After that you can rm -rf all of the following directories if you want to make certain that everything is gone:
/opt/opsware
/var/opt/opsware
/etc/opt/opsware
/var/log/opsware
How to open xterm via global shell in opsware on remote system as root
Best way to accomplish task of opening getting root xterm displayed back on remote system via opsware is to do the following:
ssh -l your_user_ID -p 2222 opsware_ip
make sure you have exceed or xmanager or other X server running on your PC or linux
then write script like the following:
#!/bin/ksh
export DISPLAY=your_desktop_IP:0.0
/usr/openwin/bin/xterm -bg black -fg green -title `hostname` -sb -sl 32000 &
then execute it:
rosh -l root -n destination_server -s ./xterm
this will push xterm script to destination_server and it will execute it, you should see xterm popping up on your screen any time now.
Powered by Yahoo! Answers