- About Vivit
- LUGs & SIGs
- Vivit Blogs
- News & Events
- Knowledge Base
|HPE Storage Solutions Forum - Polyserve Solutions|
What is that latest vxvm version and how to download latest vxvm SP and hotfix
Anyone have a good idea of how to migrate from a 2 node cluster PSFS to single NTFS node?
All help is appreciated. Need to get of this old CFS and 2003 server to 2008R2/2012R2.
I know polyserve is EOSL bt i recenlty ran into a problem before migration. I am unable to login.
When I launch the console, it asks for usename and password and it fails eveytime i give my login.
anybody's help would be a oasis in the desert :)
Effective after tomorrow - PolyServe support will end.
End-of-Support-Life (EOSL): February 28, 2014
We had an old Polyserve system on 2 Linux HP ProLiant nodes serving a filesystem to all the nodes in our cluster.
After a general shutdown and reboot, I observed a strange behavior: some nodes were able to NFS mount and work with the filesystem as usual, but some other mounted the filesystem but an 'ls' command lasted more than 2 minutes:
When I checked the situation with mxconsole, I saw no problem but the Export Group where a certificate error appears (attached capture). The log file (mx.0.log.0) is:
Sep 4, 2013 5:24:19 PM com.polyserve.cecomm.CECommManager postToCE SEVERE: IOException - sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed Sep 4, 2013 5:24:19 PM com.polyserve.nfs.ExportRecordsConfiguration loadExportRecordsFromCE SEVERE: Failed to communicate to CE javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed Sep 4, 2013 5:24:19 PM com.polyserve.nfs.ui.NFSClusterDeviceMonitorDialog loadError SEVERE: Failed to communicate to CE javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed
I read here about the problem with certificates ending in 2012 ¿can that be causing our problems? I've tried to check HP's FTP site to find new certificates or a solution to our problem but I haven't found any.
Can any one suggest me a possible solution? Our storage system has always been a black box for us (just shutdown and restart operations).
Thanks in advance.
We are encountering terrible slowness when attempting to copy file shares from our Polyserve file server cluster to any Microsoft server. Does anyone know if there should be inherent slowness involved in copying large amounts of data from Polyserve file shares and is their any tuning I should be doing or looking for before copying?
Where may i find fresh SSL certs for Polyserve (v3.6.2)?
The server.pem and cacert.pem have expired as of 21 September 2012, and hp.com is found lacking relevant information.
Working on work-arounds, but no joy at this hour.
Both certs issued by: PMXS Certificate Authority:
E = firstname.lastname@example.org
OU = Certificate Authority
We are running Polyserve File System for Windows on 4 servers, version 3.6.0.
The product number for this is T4416A
Does anyone know what the product number is for 4.1.0 ?
Reason being, we are looking to upgrade from 3.6.0 to 4.1.0
From where can I download PolyServe 4.1 for Windows 2008 64 bit
From the below link I can only download the documentation not the Installer
Thanks and Regards
Do you have Polyserve cluster software for Windows 2008 (32-bit ) standard edition?
I have a 8 node Poly cluster, base version 3.6.1 hotfix 3, db 3.6.2. I currently have 8 network interfaces amongst 4 physical NICs. 6 are teamed, etc across 2 of the NICs (10.77.44, 10.77.45, 10.77.46, 10.77.48.....), 1 NIC is for backup (10.77.47.x) and 1 NIC is currently for heartbeat (172.x). I need to get off the 172.x network and I need to figure out the best way with as minimal downtime as possible. Currently my backup 10.77.47 and heartbeat network 172.x have admin traffic enabled. My preliminary plan is:
Move the only two instances I had on the 10.77.48 interface off - DONE
Disable hosting and discourage Admin on 10.77.48. (want to use this as a alternative heartbeat network)
Disable the 172.x network interface (my backup network will be my admin network now)
Should I disable heartbeat in Matrix Server first - if it will let me? Disable the interface in network control panel? What do I need to know about stopping/starting Matrix Server?
I will have backup traffic on 10.77.47 during backup times. 10.77.48 will have nothing else running on it but does share traffic on the first 2 physical NICs I mentioned. The guide does say you can share traffic but it may effect performance. Any advice here?
After we get done, we may can come back and add the 4th NIC back in so I can have some better admin network help and redunancy.
Hi, Would like to check if SQL 2008R2 is supported in latest version of Polyserve?
Customer is checking is HP Polyserver Matrix Server 4.0 is certified with IPv6.
Can anyone confirm?
This is critically important to both our enterprise operations and disaster recovery planning, and we have to get a firm yes/no answer from HP and a target date so we can plan now for CY 2011 and 2012.
P.S. This thread has been moved from Network Attached Storage (NAS) (Small and Medium Business) to Polyserve Solutions. - Hp Forum Moderator
Within the last 2 weeks, load spikes on the Polyserve boxes, and it appears that the clients do not immediately get their data.
Anyone have an issue like that, or know of it?
So, are there any real issues with running a yast update? Polyserve update?
These are the first gen DL380 appliances.
Thanks for any input you can provide!
I would destroy some volume (psv6, psv7 )
I have unmounted in in GUI ( Filesystem )
In Linux they are unmounted but not in Polyserve:
[root@srnasln01 polyserve]# mx fs unmount psv6 ALL_SERVERS
10.247.10.6 umount failed: umount: /dev/psv/psv6: not mounted
10.247.10.22 umount failed: umount: /dev/psv/psv6: not mounted
[root@srnasln01 polyserve]# mx fs mount --path /PACS/vnasln1c/share1 psv6 ALL_SERVERS
10.247.10.6 mount failed: Volume already mounted
10.247.10.22 mount failed: Volume already mounted
[root@srnasln01 polyserve]# df |grep psv6
[root@srnasln01 polyserve]# mx fs status
FS psv6 (vnasln1c share1) MOUNTED(/PACS/vnasln1c/share1) rw,shared,data=ordered,async,createdir srnasln02.uhbs.ch
FS psv6 (vnasln1c share1) MOUNTED(/PACS/vnasln1c/share1) rw,shared,data=ordered,async,createdir srnasln01.uhbs.ch