Cluster Validation / UDP 3443

Hello,
I'm running into a problem running Cluster Validation (2012 R2)
I'm getting a network communications error stating that each node is unable to contact the other over UDP3343.
The only advice I've found online instructs me to open UDP3343 on the firewall. (or disable it all together)
All firewalls are disabled, all other IP communications are fine.
a Netstat shows that UDP3343 is not listening and a NMAP shows the port is not open.
Why would UDP3343 not be listening?
Thank you!
-Ryan
-Ryan Biddle-

Hi rbiddle,
The 3343 problem typically caused by the firewall or AV soft block the cluster communication, please try to disable your firewall and AV soft then install the Recommended
hotfixes and updates for Windows Server 2012 R2-based failover clusters updates.
The related KB:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151/en-us
Please check the following link for more information:
You are unable to join a node into a Cluster if UDP port 3343 is blocked
http://support.microsoft.com/kb/2455128
Windows Server 2008 R2: Networking in Failover Clusters
http://technet.microsoft.com/en-us/magazine/hh535729.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Failover Cluster Validation Report with warnings

Hi,
I have 2 Node cluster on windows 2008 R2.I have run cluster validation report and found following warnings pls suggest and guide me health of cluster and how to fix and remove these warnigns. thx.
Validate All Drivers Signed
Validate that tested servers contain only signed drivers.
Validating that the servers contain only signed drivers...
The node 'cluster1.domain.com'has unsigned drivers.
Device Name Device Class Driver Version Driver Date Manufacturer Inf Name Driver Name Device ID Description Status Start Mode
Virtual CloneDrive SCSIADAPTER 5.4.4.3 1/15/2011 12:00:00 AM Elaborate Bytes AG oem1.inf Value Not Found ROOT\SCSIADAPTER\0000 Virtual CloneDrive Value Not Found Unknown
Unsigned drivers were found on one or more of the servers.

Hi,
you need to run iso files at your cluster nodes often?
Well i think you need to provide iso files to your VMs. This is possible without "Virtual CloneDrive"!
I have seen many errors with this kind of software up to bluescreens.
But ok if you really need this software just ignore the warning from cluster validation report.
The cluster will work correctly if this are the only warnings from cluster validation report.
Regards
Sebastian

Failover Cluster Validation Report Error with IBM USB Remote NDIS Network device

We are setting up Microsoft Windows Server 2008 R2 Failover Cluster on IBM X3850 X5 and get errors in the Failover cluster Validation Report due to the IBM USB Remote NDIS Network Device is using APIPA adresses and both servers are using same APIPA-adresse.
How should I configure the Server and OS for the Failover cluster to be MS approved?
IBM don't recommend that i disable the Network device, but it is a possible solution!?!

What I did was use ipconfig /all to see the settings it is using and then when and set the ip setting on the NDIS driver to be that except I increment the last value by 1 for each node so that they do not have the same IP address. I ran the
cluster validation again and it came up clean and I have not experienced any issues yet. It does give warnings about it being an Automatic Private IP Address and should not be used, which is ok because we are not going to use it anyways.
Rich Baumet

Cluster Validation Fails on List iSCSI Host Bus Adapters

I have an 8 Node SQL Failover Cluster.
This cluster has been in service for quite some time now, suddenly the Cluster Validation is failing...
When it gets to the "List iSCSI Host Bus Adapters" (which we do no use on any of these nodes) it fails with the error:
"An error occurred while executing the test. There was an error getting information about the iSCSI controllers installed on the nodes. There was an error retrieving information about the iSCSI host bus adapters from node 'node1'. Invalid class "
The test is not performed on any of the other nodes, it just fails.
This is causing a problem when trying to extend SQL to some of the newer nodes that have been added.
I have tried evicting and readding nodes, I've tried uninstalling/reinstalling failover clustering, among other things.
I did notice that on node7, if I attempt validation, and ONLY mention node7, the test will complete on that box only.
Again, we do not even use iSCSI, this is a Fibre Channel cluster. It's just the attempt by the validation wizard to list the iSCSI Host Bus Adapters that do not exist, that is failing....
Any thoughts? I did see a similar post which mentioned having a problem listing Fibre Channel adapters that sounded like the exact same error, but there was no resolution there either...

Hi,
For SQL Server Cluster issues, I suggest discussing them in our SQL Server Disaster Recovery and Availability forum. They are the best resource to troubleshoot SQL Server Cluster issues.
http://social.msdn.microsoft.com/Forums/en/sqldisasterrecovery/threads
Tim Quan - MSFT

Failed Cluster Validation Wizard - Active Directory

Hi All,
I have a problem creating a cluster that has just got me stumped.
I've created two other clusters at two other sites with exact same hardware and configuration. All worked fine at those location.
For this third location, the cluster build is not going so well.
I have 2 x Dell server for a 2 node cluster, and a Dell SAN. There are iSCSI HBAs and switches for iSCSI and a flat network for the LAN and Management on another switch. The heartbeat is connected via a directly connected cable.
The nodes are running 2012 R2 Core, with latest patches (April 2015).
Firewall is disabled by Group Policy, both on servers and Domain Controller.
The Domain Controller at this site is on the local LAN.
On each future cluster node, the LAN cards can ping the Domain Controller by name and address (using -S to verify the source address). On the DC it can also ping each LAN interface, again both by name and IP. Heartbeat NICs can similarly ping each other.
Using a Management Server on a remote subnet (Domain Account, local admin of all concerned servers, except the DC, and having read/write on the target OU), the Cluster Validation Wizard fails, on one node only.
I'm getting an error message on "System Configuration\Validate Active Directory Configuration" of:
Connectivity to a writable domain controller from node DEN1NTHV02.mycorp.net could not be determined because of this error: Could not get domain controller name from machine DEN1NTHV02.
Node(s) DEN1NTHV01.mycorp.net can reach a writable domain controller.
Node(s) DEN1NTHV02.mycorp.net cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers.
The computer accounts are in the same OU, and both are enabled and have no (seeming) other problems.
So, (1) does anyone have any idea, or (2) where can I find the verbose output text of the failed test?

Re-check your IP configuration. Ensure the only NICs with a gateway defined is the primary NIC that will be used for client access.
"a flat network for the LAN and Management on another switch. The heartbeat is connected via a directly connected cable."
Just FYI. Though a cross-over cable between the two nodes works for a two-node cluster, it is not recommended if there is even a chance of the cluster going beyond two nodes.
Secondly, from your above statement, it sounds like you have the other, non-iSCSI networks plugged into a single switch. That becomes a single point of failure.
. : | : . : | : . tim

Failing "List Services Information" Cluster validation test

Hi
I'm building a 2 node Windows 2008 SP2 Cluster. I've setup the SAN Disks, NIcs etc and am running the cluster validation tests. However this always fails on the "List Services Information" Test with the following error statement:
"An error occurred while executing the test. There was an error getting information about the running services on the nodes. There was an error retrieving information about the Services from node '<Server FQDN>'. Object reference not set to an
instance of an object.
Note: I replaced the actual server fqdn with <Server FQDN>
Any help is appreciated.
Thanks

Hi,
I know it is not a SQL cluster but you could still have a try with steps below as a workaround. See:
http://support.microsoft.com/kb/953748/en-us
•For an integrated failover Add-Note setup, run the following command on each node that is being added:
Setup /SkipRules=Cluster_VerifyForErrors /Action=InstallFailoverCluster
•For an advanced or enterprise installation, run the following command:
Setup /SkipRules=Cluster_VerifyForErrors /Action=CompleteFailoverCluster
•If you receive this validation failure when you add a node to an existing failover installation, run the following command on each node that is being added:
Setup /SkipRules=Cluster_VerifyForErrors /Action=AddNode
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Hyper-V cluster validation report "Found duplicate physical address" on nic team interfaces.

I recently built a Windows 2012 Hyper-V cluster with 5 nodes. The validation report shows “duplicate physical address” error (error text pasted below).
The hardware: HP BladeSystem – servers are BL460c blades, in a c7000 enclosure, connected to HP Virtual Connect switches.
Each server has 2 physcal nics, teamed in Windows. In the NIC Teaming console, I created the following Team Interfaces and assigned each a VLAN ID:
“Team1” (the default team)
“Team1 - VLAN 204 – Management”
“Team1 - VLAN 212 - 2012HB”
“Team1 - VLAN 211 -Exchange DAG Replication”
I also created 2 HV Virtual Switches. Neither one allows management interface to share. They are assigned to “Team1” and “Team1 - VLAN 211 -Exchange DAG Replication” respectively.
Therefore, in Network Connection, I see the 2 physical Ethernet nics, and 4 “virtual” nics. Only 2 of them have IP addresses assigned: Management and HB. These are the two that the validation wizard complains
about.
The MAC address is not configurable in the NIC Teaming console, so I don’t see a way to resolve this error, except to use separate physical nics. I don’t want to do that because a) I would lose the benefits of
the bandwidth aggregation that Virtual Connect provides, and b) When creating an Interface on a Team in Windows, it looks like it ALWAYS gives it the same MAC address, so that should be a supported configuration.
Everything works just fine, and there are no other errors or IP conflicts or anything else. But I really want to fix it because I don’t know what unknown problems this may be causing.
From the Cluster Validation report:
Found duplicate physical address 10-60-4B-A9-4A-30 on node Cluster201.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster201.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address F0-92-1C-13-3C-2C on node Cluster202.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster202.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C1-7E-9C on node Cluster210.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster210.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 3C-4A-92-DE-1E-74 on node Cluster211.OurDomain.local adapter VC-Team - VLAN 212 - 2012HB and node Cluster211.OurDomain.local adapter
VC-Team - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C0-3D-50 on node Cluster212.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster212.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Thanks!
Dan

Hi Dan,
"It turns out that both hosts had the same default MAC address ranges for their virtual switches. Since the host vNICs were attached to the virtual switch on each host they received the first couple of MAC addresses from the switches.
For details please refer to following link:
http://www.jefflafr.com/blog/4/19/2013/conflicting-mac-addresses-when-building-a-hyper-v-cluster-with-converged-networking
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cluster validation

I have a 3 node hyper-v 2008 R2 fully patched cluster. I'm using a CSV via ISCSI to NetApp storage. When I validate my cluster I get this warning for all the storage tests.
"No disks were found on which to perform cluster validation tests."
I also see this explanation.
* The disks are already clustered and currently Online in the cluster. When testing a working cluster, ensure that the disks that you want to test are Offline in the cluster.
Where/how do I offline these disks? What are the ramifications and what will go down if they are off-lined?
Thanks
E

I have a 3 node hyper-v 2008 R2 fully patched cluster. I'm using a CSV via ISCSI to NetApp storage. When I validate my cluster I get this warning for all the storage tests.
"No disks were found on which to perform cluster validation tests."
I also see this explanation.
* The disks are already clustered and currently Online in the cluster. When testing a working cluster, ensure that the disks that you want to test are Offline in the cluster.
Where/how do I offline these disks? What are the ramifications and what will go down if they are off-lined?
Thanks
E

Access is denied messages in Win2012 R2 Failover Cluster validation report and CSV entering a paused state

Been having some issues with nodes basically dropping out of clusters config.
Error showing was
"Cluster Shared Volume 'Volume1' ('Data') has entered a paused state because of '(c000020c)'. All I/O will temporarily be queued until a path to the volume is reestablished."
All nodes (Poweredge 420) connected a Dell MD3200 shared SAS storage.
Nodes point to Virtual 2012 R2 DC's
Upon running validation with just two nodes, get the same errors over and over again.
Bemused!
List Software Updates
Description: List software updates that have been applied on each node.
An error occurred while executing the test.
An error occurred while getting information about the software updates installed on the nodes.
One or more errors occurred.
Creating an instance of the COM component with CLSID {4142DD5D-3472-4370-8641-DE7856431FB0} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
and
List Disks
Description: List all disks visible to one or more nodes. If a subset of disks is specified for validation, list only disks in the subset.
An error occurred while executing the test.
Storage cannot be validated at this time. Node 'zhyperv2.KISLNET.LOCAL' could not be initialized for validation testing. Possible causes for this are that another validation test is being run from another management client, or a previous validation test was
unexpectedly terminated. If a previous validation test was unexpectedly terminated, the best corrective action is to restart the node and try again.
Access is denied
The event viewer on one of the hosts shows
Cluster node 'zhyperv2' lost communication with cluster node 'zhyperv1'. Network communication was reestablished. This could be due to communication temporarily being blocked by a firewall or connection security policy update. If the problem persists
and network communication are not reestablished, the cluster service on one or more nodes will stop. If that happens, run the Validate a Configuration wizard to check your network configuration. Additionally, check for hardware or software errors related
to the network adapters on this node, and check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected
such as hubs, switches, or bridges.
Only other warning is because the 4 nic ports in each node server are teamed on one ip address split over two switches - I am not concernd about this and could if required split then pairs, I think this is a red herring????

Hi,
Such events happen because of the following reason:
1- Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks not enabled on all network interfaces. Check this KB article: http://support.microsoft.com/kb/2008795
. Please make sure these two protocols are enabled on all cluster networks
2- Network connectivity issue can cause this event as well. Please make sure the network cabling/Cards/Switches are correctly configured and working as expected
3- Connectivity issue with the storage can also cause this event. Please make sure all the nodes are connected to storage. Check HBA/Cabling connectivity to SAN. Make sure
that the SAN drivers are up-to-date.
4- Antivirus may interrupt network communication and cause this failure. Please exclude CSV volumes from being scanned by AV: http://social.technet.microsoft.com/wiki/contents/articles/953.microsoft-anti-virus-exclusion-list.aspx
5- Disable TCP Chimney related settings on all cluster nodes. http://support.microsoft.com/kb/951037
6- Please check the Network Binding Order (http://social.technet.microsoft.com/Forums/windowsserver/en-US/2535c73a-a347-4152-be7a-ea7b24159520/hyperv-r2-csv-cluster-recommended-binding-order?forum=windowsserver2008r2highavailability)
7- Firewall Rules For All Inbound and Outbound For Cluster and Hyper-V for all the Profiles
8- Update NIC Driver/Firmware.
9- Check Compatibility of the NIC with Windows Server 2012R2
10- Set-NetAdapterRss - Resources and Tools for IT Professionals | TechNet : http://technet.microsoft.com/en-us/library/jj130863.aspx
11- Check the Following Article http://social.technet.microsoft.com/Forums/windowsserver/en-US/e06fede9-931c-4dee-8379-4fd985e20f0a/hypervvmswitch-eventid-106
12- General Updates to be applied on the nodes :
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: November 2013 : http://support.microsoft.com/kb/2887595
Windows 8.1 and Windows Server 2012 R2 General Availability Update Rollup :
http://support.microsoft.com/kb/2883200
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Failover cluster Validation

Hi
If i have production servers working on hyper v failover cluster and i want for some reason to run the validaion on the failover cluster
what is the consideration before i ran the validation ?
shall i shutdown all vms?
Thanka
MCP MCSA MCSE MCT MCTS CCNA

Hi Yasser,
Here are a few articles that might help. I've pointed out a few of the key comments here, and it appears that storage validation is the only category that will cause downtime. So if you want to validate storage, then yes, you'll need to shut them down.
http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx (Server 2008/2008R2)
"By default, the wizard warns you if storage tests have been selected but will not be run on storage that is online, that is, storage used by clustered services or applications. In this situation, you can run validation tests (including
storage tests) by creating or choosing a new logical unit number (LUN) from the same shared storage device and presenting it to all nodes. By testing this LUN, you can avoid disruption to clustered services and applications already online within the cluster
and still test the underlying storage subsystem."
http://blogs.msdn.com/b/clustering/archive/2011/06/28/10180803.aspx (Server 2008R2)
"Across these dozens of tests, only a few of them will impact running cluster workloads and these are all within the storage category, so skipping this entire category is an easy way to avoid disruptive tests."
http://technet.microsoft.com/library/jj134244#BKMK_RUN_TESTS (Server 2012/2012R2)
"If a clustered role is using a disk when you start the wizard, the wizard will prompt you about whether to take that clustered role offline for the purposes of testing. If you choose to take a clustered role offline, it will remain offline
until the tests finish."
Thanks,
Jared

Windows Server 2012 Cluster Validation Failing On List All Potential Cluster Disks

I'm in the process of setting up a new cluster using Windows Server 2012 with a view to migrate from our existing 2008 R2 cluster. I am having problems validating the storage and the wizard keeps failing on the List All Potential Cluster Disks
test (which causes all the other storage tests to be cancelled).
I'm getting the following error:
Failed while verifying removal of any Persistent Reservation on physical disk 19ba99a4 at node RC-HYPERV-3.riddlesdown.local.
When I look in validation report, disk 19ba99a4 is the management LUN (Access LUN 31 as termed by the storage software).
Looking on my 2008 R2 cluster this doesn't appear in Disk Management.
Any ideas how I can get rid of it or the error that it is causing?

Hi,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Aiden
TechNet Subscriber Support
If you are
TechNet Subscription
user and have any feedback on our support quality, please send your feedback
here.
Aiden Cao
TechNet Community Support

Cluster Validation error.

I have 2012 R2 Failover cluster with two nodes.
When I try to add third node and run Validation test, I've got error in Validation Report:
"Two disks have been found on node Hyperv01.local.com with duplicate disk signatures or disk GUIDs. The disks involved are physical disk 2 and physical disk 12. There may be a Multipath I/O (MPIO) problem such as the software is not installed or is not
working properly. If MPIO is not involved, or MPIO has been verified as working, you must either mask one of these disks off at this node, or run validation and specify a disk list that includes only one of these disks, for example by using the Test-Cluster
cmdlet in Windows PowerShell."
But disk signature and disk GUIDs are different.
All disks connected via ISCSI.
Can anyone please help?
Thank you.

Hi oxyGEN_ua,
Please confirm your storage compatible with server 2012r2 and your do not use the disk which marked as active and please confirm all your node have the same update and hotfix,
please install the following update.
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
https://support.microsoft.com/kb/2920151/en-us?wa=wsignin1.0
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cluster validation stating an update needs to be installed, but when checked, it's installed...Answers???

I'm setting up a simple, two node, cluster in Server 2012R2. When doing the Validation test it states that the updates on one of my nodes is not up to date. However, upon further investigation, I've found that most, if not all, updates the
test is telling me needs to be installed are installed. I have two other clusters that are set up the same way, the validation test came up good across the board and they have linked up nicely, but this one will not perform correctly. The only
difference between the three is the updates showing out of sync on the one cluster. Any help would be greatly appreciated.

Hi,
So the Clusters are fully patched and also running UR1 and did a reboot ?
and the updates are installed as shown in the update manger list.
what you could do is stop the Update service and delete the C:\Windows\SoftwareDistribution folder.
When starting the services it will recreate the folder ;-) then reboot the cluster and start validation.
Greetings, Robert Smit Follow me @clustermvp http://robertsmit.wordpress.com/ “Please click "Vote As Helpful" if it is helpful for you and Proposed As Answer” Please remember to click “Mark as Answer” on the post that helps you

Messaging + cluster + Validation of resource failed

Hello,
I have messaging server 7 configured on 2 servers and there is one server for cluster. so 2 + 1 cluster here.
After manual scwitch to be3 from be1, service is running fine.
However in next step of configuration with cluster it is failing.
I have installed HA agent 7 which comes with comm suite 6 x86,Solaris 10
#scstat -g
-- Resource Groups and Resources --
            Group Name     Resources
Resources: mail1-msg-res mail1-lh-res mail1-hastp-res
Resources: mail2-msg-res mail2-lh-res mail2-hastp-res
-- Resource Groups --
            Group Name     Node Name                State          Suspended
     Group: mail1-msg-res be1                Online         No
     Group: mail1-msg-res be3                Offline        No
     Group: mail2-msg-res be2                Online         No
     Group: mail2-msg-res be3                Offline        No
-- Resources --
            Resource Name Node Name                State          Status Message
Resource: mail1-lh-res   be1                Online         Online - LogicalHostname online.
Resource: mail1-lh-res   be3                Offline        Offline - LogicalHostname offline.
Resource: mail1-hastp-res be1                Online         Online
Resource: mail1-hastp-res be3                Offline        Offline
Resource: mail2-lh-res   be2                Online         Online - LogicalHostname online.
Resource: mail2-lh-res   be3                Offline        Offline - LogicalHostname offline.
Resource: mail2-hastp-res be2                Online         Online
Resource: mail2-hastp-res be3                Offline        Offline
#scrgadm -a -t SUNW.ims
root@e-eihqbe1 # scrgadm -a -j mail1-msg-res -t SUNW.ims -g mail1-msg-res -x IMS_serverroot=/messaging/mail1/bin/ -y Resource_dependencies=mail1-hastp-res,mail1-lh-res
(C189917) VALIDATE on resource mail1-msg-res, resource group mail1-msg-res, exited with non-zero exit status.
(C720144) Validation of resource mail1-msg-res in resource group mail1-msg-res on node be3 failed.What am I missing?
regards,
sumant.

Basically the problem causing the resource creation for the COMMS service to fail (ie, placing the messaging server under cluster control) is that in order to validate the service you have to be able to access the binaries on both system at the same time, like APACHE. So it's either, install binaries locally for both systems or use a global file system. It's not stated, but if you look in the HA configuration in Chapter 3 in Sun Java System Messaging Server 6.3 Administration Guide, the "Two node Symmetric Messaging Server -- Example" has an vfstab listed with the global options set. And if you look at the ZFS example in the 7.0 documentation, they install the binaries on the local file systems.
It appears the rule of thumb is:
Binaries=local or global
Config = failover fs
So what they guy did above-- or from what I can make sense of-- was to make the file system available to both hosts, at the same time. Since I was mucking with ZFS, I just copied everything over to the other host (scp), faked the mount point so the FS was available on both nodes, and then ran the create script. Once I was done, I deleted the copy and switched the resource at will.
Correct me if I'm wrong (chemo brain, and it's been a while) but I think the validate scripts are only used when creating the resource. You don't even need them when you create your own basic GDS service. If I was to create my own Agent, I'd just make sure the validation portion was under the start/stop script. I just might do that...

Cluster Validation Requirement (for contract support)

Can anyone give definitive information on how a newly built cluster may be validated ? We have a support contract in place but I have not found detailed information on how to meet this requirement and how it relates to support during a production-down issue.
Thanks,
Jim

Thanks Tim. My rep is investigating right now.
I was hoping there might be some detailed information on the validation service on the Oracle/Sun sites. Obviously we'd like to avoid an iterative process by knowing up front what is involved before asking for the service.
Jim

Cluster Validation / UDP 3443

Similar Messages

Maybe you are looking for