My Blog

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.

Sometime ago installed my RedHat 5 with xen. Then I needed to create a virtual server running RedHat 4 in it, all needed to be 64 bit because Opsware required 64 bit RHEL AS4, so had to come up with an inexpensive solution. Got Intel Quad from Dell for $400 with 8gb ram, inexpensive desktop, installed RedHat 5 on it, then created xen virtual server in it running RedHat AS 4 for Opsware, of course opsware is not supported under XEN as a virtual server and it would not run under RedHat 5, so I had to hack it a bit to get it working, actually to get it installed is quite simple. Anyway so I had my RedHat AS4 vm running then I did notice that my desktop running all of that rebooted the other day, but my opsware virtual server did not start. With XEN I am not that familiar so I had issues starting it with command line, so I was ending up bringing xdisplay back to my pc remotely just to start it up. Well what it turned out that I don’t have to do this anymore. I was playing around with starting it up and why, I can do it automatically.

Anyway solution to start it up was very simple, on my RedHat 5 hyperviser I had to go to /etc/xen directory, there is directory called auto, and there is a config file for my virtual server called opsware (name of that virtual server) so to get it automatically started I needed to create a symbolic link inside that auto directory that pointed to that opsware config file.

Simple and easy, not when my desktop reboots my xen vm starts automatically.

Recently I needed to connect my browser to my opsware port 1004 but I got problems with certificate. This is where I needed to connect to: opsware:1004/ but I was getting nowhere as certificates were not installed for it. Solution is simple. I had to go to my opsware core server to the following directory:
/var/opt/opsware/crypto/spin/
there are two files that I needed:
browser.p12 and spin-developer.p12
please be very carefull as spin-developer is quite powerfull and you can do a lot of damages with it.

Anyway bring those two files to your desktop.
 open your internet explorer, select tools from the menu and chose internet options.

Read more…

Sometimes I need to dump session which did not work and send to support, here is quick how to do it. I am just putting this for myself for me to find it easily as I do it with this rest of my blog, so if you find this useful then its great if not then please dont worry about it.

opsware[root] PYTHONPATH=/opt/opsware/pylibs
opsware[root] export PYTHONPATH
opsware[root] /opt/opsware/bin/python dump_session.pyc 211550001
Grabbing Session 211550001…
Grabbing Session 211550001 info…
Grabbing Session 211550001 params/results…
Grabbing SessionCommands…
Grabbing SessionCommand 2351010001L (1/1) info…
Grabbing SessionCommand 2351010001L (1/1) params/results…
Found $session_id 211560001L
Grabbing Session 211560001L…
Grabbing Session 211560001L info…
Grabbing Session 211560001L params/results…
Grabbing SessionCommands…
Grabbing SessionCommand 2351020001L (1/1) info…
Grabbing SessionCommand 2351020001L (1/1) params/results…
Writing results…
opsware[root]

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.

Read more…