Drillthrough using a cluster name
Hi
I'm looking to use a hyperlink to open a BO report containing detailed business data from a summary report which gives a total count of records for each type of business data.
This is from http://devlibrary.businessobjects.com
" href="http://<webserver>/businessobjects/enterprise115/<platformSpecific>?sDocName=<document name>&sType=<document type>&iDocID=<document id>&lsS<prompt message>='object SELECT'">'object SELECT'</a>' "
So far so good. This works if the web server name is given in <webserver>
However , we use a cluster of web servers and it is this cluster name ( @xxx ) I want to use rather than a specific one.
Does anyone know how to do this ?
Thanks
Ken
In case anyone else has this problem, I eventually called Adobe tech support. My issue has been identified as a bug in both TCS2 and TCS3. With any luck, they'll fix it in an update.
Glynnis
Similar Messages
-
Cluster Name Resolution and failover
We are running a cluster consisting of two managed servers and one
admin server on Solaris using WebLogic 6.1 SP3. The application is
composed of EJB's only. Each managed server has been assigned a DNS
name (host names weblogic-cluster-ma & weblogic-cluster-mb). A
cluster address (DNS name weblogic-cluster) has been setup to
round-robin amongst the two IP's assocaited with the managed server
that are participating in the server.
If I do a nslookup on the same cluster name successively, I get two
different IP addresses.
The behavior that I am observing is as follows:
1. When all instances participating in the cluster are running
everything is fine. The clients are able to connect to the machine
using the cluster name while doing the JNDI lookup.
2. When one of the servers participating in the cluster is down, and
the cluster name is used to access it (the round-robin DNS name),
depending on which machine is down, all calls either get through or
none of them get through.
I do not want to use the following cluster aware syntax to access the
cluster
t3://weblogic-cluster-ma,weblogic-cluster-mb:7001
Instead I would like to use the cluster name
t3://weblogic-cluster:7001 and have transparent failover.
It would appear to me that if I have DNS return me back all the IP's
associated with the cluster then my problem would be solved.
for example:
nslookup weblogic-cluster.
216.33.240.47, 216.33.240.12
Is this possible? How have others solved this problem.
Thanks for your reply!
Aaravali,
What you describe should work. However, could you clarify statement
#2, specifically, "all calls either get through or none of them get
through." Do you mean that the client either works or it simply fails?
Are you failing on creating the initial context?
Regards,
Simon
Developer Relations Engineer
BEA SupportAaravali Karavali wrote:
> We are running a cluster consisting of two managed servers and one
> admin server on Solaris using WebLogic 6.1 SP3. The application is
> composed of EJB's only. Each managed server has been assigned a DNS
> name (host names weblogic-cluster-ma & weblogic-cluster-mb). A
> cluster address (DNS name weblogic-cluster) has been setup to
> round-robin amongst the two IP's assocaited with the managed server
> that are participating in the server.
>
> If I do a nslookup on the same cluster name successively, I get two
> different IP addresses.
>
> The behavior that I am observing is as follows:
>
> 1. When all instances participating in the cluster are running
> everything is fine. The clients are able to connect to the machine
> using the cluster name while doing the JNDI lookup.
> 2. When one of the servers participating in the cluster is down, and
> the cluster name is used to access it (the round-robin DNS name),
> depending on which machine is down, all calls either get through or
> none of them get through.
>
> I do not want to use the following cluster aware syntax to access the
> cluster
>
> t3://weblogic-cluster-ma,weblogic-cluster-mb:7001
>
> Instead I would like to use the cluster name
> t3://weblogic-cluster:7001 and have transparent failover.
>
> It would appear to me that if I have DNS return me back all the IP's
> associated with the cluster then my problem would be solved.
>
> for example:
>
> nslookup weblogic-cluster.
>
> 216.33.240.47, 216.33.240.12
>
> Is this possible? How have others solved this problem.
>
> Thanks for your reply!
-
Meter / slider questions - cluster names, changing needle colour
OK, so a couple of questions about meters /sliders.
I have a meter indicator on a form, with two needles. (example attached)
I want to create the cluster for the input using "bundle by name", but the meter "cluster" does not appear to have any names. I want the elements of the cluster to be "Channel 1" and "Channel 2" - how do I do this?
Secondly, I want to be able to set the needles to transparent.
I can do this with a meter with only one needle, but for more than one, I think you need to set the Active slider ("Actslider") property.
It strikes me that the easiest way to do this is to use a loop, but how do I discover how many needles the meter has? Or could I use the cluster names to s
pecify which needle I want to change colour?
TIA
Joolz
[I'm going to add the word "color" here so that those of you across the pond will also be able to find this from the search engine ;-) ]
Attachments:
Slider_Cluster_Question_for_Labview_Forum.vi 14 KBThank you both for the responses, and apologies for the tardy reply - changing priorities, etc, etc, you know how it is...
I've attached a Vi to act as an example for anyone else who has either of these problems.
The main thing I found out is that although you can, as you say, use a constant to "declare" the cluster names for the gauge, these names are only "remembered" by the wire - if you create a local variable of the gauge, it will NOT remember the cluster names. That's what had me confused...
Cheers
Joolz
Attachments:
Transparent_needles_and_Cluster_Names_for_Gauges.vi 84 KB -
Use initialization file key names/values as cluster name/values
I am trying to assign my initialization key name and values to a clusters names/values repestively. For example, I read in the ini file key names (dir, user, year) and would like those to be the cluster labels and then read in the associated values and assign them to the cluster.
For example, if my ini file is:
[Sample]
dir=c:
user=jnoel
year=1971
I would like the cluster element names to be dir,user, and year with the values for each being c:, jnoel, and 1971 respectively. I tried using the property node for label:text but Labview states the labels are not allowed to be changed in runtime. I would think there would be some way to do this (and if not there should be!).
Any help would be greatly appreicated.MikeS81 wrote:
Ben wrote:
Hide the cluster names and show the captions.
Captions can be written at run time.
Ben
Sorry,
that´s what i´ve meant.
Mike
No it is me that should say "Sorry". Before my coffee had kicked in I had not realized that the description = caption.
I was sorta wondering why you hadn not suggested captions, "doh!"
Well between the two of us we got it right.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction -
How to determine the Cluster name ?
Grid version : 11.2.0.3 on Solaris 10
When we start installing Grid Infrastructure, we specify a Cluster Name.
Question1.
How can I determine the cluster name of a 11.2 RAC Cluster ? We maintain a DB inventory. For each cluster , we want to specify the Cluster name.Hence we require the cluster name .
Question2.
The cluster name is of no functional importance. Right ? I don't remember using Cluster Name in any commands (srvctl, crsctl,...)To determine the cluster name,[oracle@iron1 ~]$ olsnodes -c
ironcluster
[oracle@iron1 ~]$I wouldn't say it has much technical significance, though it is used as a default in a few other names.
John Watson
Oracle Certified Master DBA
http://skillbuilders.com -
How to get Cluster Name in SQL
Hi
I've created a cluster model and I have renamed some of the clusters under the compare tab using the ODM tool.
When I query the clusters of the model in SQL I only get the cluster numbers. How can I get the new name/label that I assigned using the ODM tool?
Thanks
BrendanHi
How did you query the clusters of the model in SQL?
For example, this query will return the cluster ids and cluster names:
SELECT a.ID, a.CLUSTER_ID
FROM TABLE(DBMS_DATA_MINING.GET_MODEL_DETAILS_OC('CLUS_OC_1_15',NULL,NULL,1,0,0)) a
Denny -
SQL CLUSTER NAME REMAIN IN A FAILED STATE
We have the following configuration in our enterprise;
- Two physical servers ( both running windows server 2008 R2)
- The physical servers have been clustered (CLUSTER1).
- Six Virtual Machines ( two for each tier of our SharePoint 2010 installation)
- Two web front ends, two application servers, two database servers.
- The two database servers (running windows server 2008 R2) have been clustered (SQLCLUSTER2) and point to a SAN.
After an unexpected power failure, the SQLCLUSTER2 has refused to come online. The IP Address comes "Online" when turned on manually. The disks also come online when turned on manually using "Bring this resource online". But once the
Cluster name is attempted to be brought online all other resources turn into "failed" state and the entire SharePoint portal becomes unavailable. See image below
Note: We have recently had a problem with one of our Domain Controller and had to be decommissioned one of the two(2) DC's. My investigation reveals that the decommissioned DC was used to create the Cluster Name Object (CNO) SQLCLUSTER2.
I have been battling to restore the cluster to normalcy for over a week now. But periodically (after some hours) all the resources turn to "failed" state and down goes our SharePoint portal.
Please any assistance anyone can offer to help resolve this issue would be highly welcomed.Hi Pedro Fuentes,
Please refer the following article to check whether your CNO permission is correct.
Error during installation of an SQL server Failover Cluster Instance
http://blogs.msdn.com/b/psssql/archive/2013/09/30/error-during-installation-of-an-sql-server-failover-cluster-instance.aspx
The similar thread:
Sql Server 2008 R2 Clustered Setup fails with The cluster resource 'SQL Server' could not be brought online
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/04ee7ddd-f94a-4410-9ce4-cf25178e09da/sql-server-2008-r2-clustered-setup-fails-with-the-cluster-resource-sql-server-could-not-be-brought?forum=sqlsetupandupgrade
SQL Server Instance is not coming online on windows 2008 R2 cluster
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c7a8ad00-53be-409e-ac54-0a709e62e7bb/sql-server-instance-is-not-coming-online-on-windows-2008-r2-cluster?forum=winserverClustering
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. -
SQL cluster name on a Windows Failover Cluster
Hello,
I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
Thanks for your help,
LucaIt should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
SQL Server Network Name —
Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
This will be the name used to identify your cluster on the network. This is the name that will be available on the
network for the clients to connect SQL instance.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/ -
2012R2 hyper-v failover cluster Cluster name object has no DNS record created
I’m trying to setup a 2-node ws2012R2 cluster using ws2008R2 AD(with DNS) but got an issue with DNS entry creation on AD. I also tried ws2012 AD but it's the same problem.
The individual node DNS entries were created on AD automatically upon joining AD but I can’t get AD to create DNS entry for my cluster name object automatically. AD will have cluster name computer
created but no record for cluster name in DNS entries
Got the following event ID 1196 error with the info below.
Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS server failure.Hi hjma29,
How about your issue now? I just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Regards.
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. -
We have a 2012 Hyper-V cluster that isn't online and we can't migrate VMs to the other Hyper-V host. We see event errors in the Failover Cluster Manager:
The description for Event ID 1069 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component
on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Cluster Name
Cluster Group
Network Name
The description for Event ID 1254 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component
on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Cluster Group
The description for Event ID 1155 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component
on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ACMAIL
3604536
Any help or info is appreciated.
Thank you!Here is the network validation. Any thoughts?
Failover Cluster Validation Report
Failover Cluster Validation Report
Node: ACHV01.AshtaChemicals.localValidated
Node: ACHV02.AshtaChemicals.localValidated
Started8/6/2014 5:04:47 PM
Completed8/6/2014 5:05:22 PM
The Validate a Configuration Wizard must be run after any change is made to the
configuration of the cluster or hardware. For more information, see
Results by Category
NameResult SummaryDescription
NetworkWarning
Network
NameResultDescription
List Network Binding OrderSuccess
Validate Cluster Network ConfigurationSuccess
Validate IP ConfigurationWarning
Validate Multiple Subnet PropertiesSuccess
Validate Network CommunicationSuccess
Validate Windows Firewall ConfigurationSuccess
Overall Result
Testing has completed for the tests you selected. You should review the
warnings in the Report. A cluster solution is supported by Microsoft only if
it passes all cluster validation tests.
List Network Binding Order
Description: List the order in which networks are bound to the adapters on
each node.
ACHV01.AshtaChemicals.local
Binding OrderAdapterSpeed
iSCSI3Intel(R) PRO/1000 PT Quad Port LP Server Adapter #31000 Mbit/s
Ethernet 3Intel(R) PRO/1000 PT Quad Port LP Server AdapterUnavailable
Mgt - HeartbeatMicrosoft Network Adapter Multiplexor Driver #42000
Mbit/s
Mgt - LiveMigrationMicrosoft Network Adapter Multiplexor Driver #32000
Mbit/s
MgtMicrosoft Network Adapter Multiplexor Driver2000 Mbit/s
iSCSI2Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #371000
Mbit/s
3Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)Unavailable
ACHV02.AshtaChemicals.local
Binding OrderAdapterSpeed
Mgt - HeartbeatMicrosoft Network Adapter Multiplexor Driver #42000
Mbit/s
Mgt - LiveMigrationMicrosoft Network Adapter Multiplexor Driver #32000
Mbit/s
MgtMicrosoft Network Adapter Multiplexor Driver #22000 Mbit/s
iSCSI1Broadcom NetXtreme Gigabit Ethernet #71000 Mbit/s
NIC2Broadcom NetXtreme Gigabit EthernetUnavailable
SLOT 5 2Broadcom NetXtreme Gigabit EthernetUnavailable
iSCSI2Broadcom NetXtreme Gigabit Ethernet1000 Mbit/s
Back to Summary
Back to Top
Validate Cluster Network Configuration
Description: Validate the cluster networks that would be created for these
servers.
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Disabled
One or more interfaces on this network are connected to an iSCSI Target. This
network will not be used for cluster communication.
PrefixPrefix Length
192.168.131.024
ItemValue
Network InterfaceACHV01.AshtaChemicals.local - iSCSI3
DHCP EnabledFalse
Connected to iSCSI targetTrue
IP Address192.168.131.113
Prefix Length24
ItemValue
Network InterfaceACHV02.AshtaChemicals.local - iSCSI2
DHCP EnabledFalse
Connected to iSCSI targetTrue
IP Address192.168.131.121
Prefix Length24
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal
PrefixPrefix Length
192.168.141.024
ItemValue
Network InterfaceACHV01.AshtaChemicals.local - Mgt - Heartbeat
DHCP EnabledFalse
Connected to iSCSI targetFalse
IP Address192.168.141.10
Prefix Length24
ItemValue
Network InterfaceACHV02.AshtaChemicals.local - Mgt - Heartbeat
DHCP EnabledFalse
Connected to iSCSI targetFalse
IP Address192.168.141.12
Prefix Length24
Network: Cluster Network 3
DHCP Enabled: False
Network Role: Internal
PrefixPrefix Length
192.168.140.024
ItemValue
Network InterfaceACHV01.AshtaChemicals.local - Mgt - LiveMigration
DHCP EnabledFalse
Connected to iSCSI targetFalse
IP Address192.168.140.10
Prefix Length24
ItemValue
Network InterfaceACHV02.AshtaChemicals.local - Mgt - LiveMigration
DHCP EnabledFalse
Connected to iSCSI targetFalse
IP Address192.168.140.12
Prefix Length24
Network: Cluster Network 4
DHCP Enabled: False
Network Role: Enabled
PrefixPrefix Length
10.1.1.024
ItemValue
Network InterfaceACHV01.AshtaChemicals.local - Mgt
DHCP EnabledFalse
Connected to iSCSI targetFalse
IP Address10.1.1.4
Prefix Length24
ItemValue
Network InterfaceACHV02.AshtaChemicals.local - Mgt
DHCP EnabledFalse
Connected to iSCSI targetFalse
IP Address10.1.1.5
Prefix Length24
Network: Cluster Network 5
DHCP Enabled: False
Network Role: Disabled
One or more interfaces on this network are connected to an iSCSI Target. This
network will not be used for cluster communication.
PrefixPrefix Length
192.168.130.024
ItemValue
Network InterfaceACHV01.AshtaChemicals.local - iSCSI2
DHCP EnabledFalse
Connected to iSCSI targetTrue
IP Address192.168.130.112
Prefix Length24
ItemValue
Network InterfaceACHV02.AshtaChemicals.local - iSCSI1
DHCP EnabledFalse
Connected to iSCSI targetTrue
IP Address192.168.130.121
Prefix Length24
Verifying that each cluster network interface within a cluster network is
configured with the same IP subnets.
Examining network Cluster Network 1.
Network interface ACHV01.AshtaChemicals.local - iSCSI3 has addresses on all
the subnet prefixes of network Cluster Network 1.
Network interface ACHV02.AshtaChemicals.local - iSCSI2 has addresses on all
the subnet prefixes of network Cluster Network 1.
Examining network Cluster Network 2.
Network interface ACHV01.AshtaChemicals.local - Mgt - Heartbeat has addresses
on all the subnet prefixes of network Cluster Network 2.
Network interface ACHV02.AshtaChemicals.local - Mgt - Heartbeat has addresses
on all the subnet prefixes of network Cluster Network 2.
Examining network Cluster Network 3.
Network interface ACHV01.AshtaChemicals.local - Mgt - LiveMigration has
addresses on all the subnet prefixes of network Cluster Network 3.
Network interface ACHV02.AshtaChemicals.local - Mgt - LiveMigration has
addresses on all the subnet prefixes of network Cluster Network 3.
Examining network Cluster Network 4.
Network interface ACHV01.AshtaChemicals.local - Mgt has addresses on all the
subnet prefixes of network Cluster Network 4.
Network interface ACHV02.AshtaChemicals.local - Mgt has addresses on all the
subnet prefixes of network Cluster Network 4.
Examining network Cluster Network 5.
Network interface ACHV01.AshtaChemicals.local - iSCSI2 has addresses on all
the subnet prefixes of network Cluster Network 5.
Network interface ACHV02.AshtaChemicals.local - iSCSI1 has addresses on all
the subnet prefixes of network Cluster Network 5.
Verifying that, for each cluster network, all adapters are consistently
configured with either DHCP or static IP addresses.
Checking DHCP consistency for network: Cluster Network 1. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local -
iSCSI3 matches network Cluster Network 1.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local -
iSCSI2 matches network Cluster Network 1.
Checking DHCP consistency for network: Cluster Network 2. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local - Mgt
- Heartbeat matches network Cluster Network 2.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local - Mgt
- Heartbeat matches network Cluster Network 2.
Checking DHCP consistency for network: Cluster Network 3. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local - Mgt
- LiveMigration matches network Cluster Network 3.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local - Mgt
- LiveMigration matches network Cluster Network 3.
Checking DHCP consistency for network: Cluster Network 4. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local - Mgt
matches network Cluster Network 4.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local - Mgt
matches network Cluster Network 4.
Checking DHCP consistency for network: Cluster Network 5. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local -
iSCSI2 matches network Cluster Network 5.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local -
iSCSI1 matches network Cluster Network 5.
Back to Summary
Back to Top
Validate IP Configuration
Description: Validate that IP addresses are unique and subnets configured
correctly.
ACHV01.AshtaChemicals.local
ItemName
Adapter NameiSCSI3
Adapter DescriptionIntel(R) PRO/1000 PT Quad Port LP Server Adapter #3
Physical Address00-26-55-DB-CF-73
StatusOperational
DNS Servers
IP Address192.168.131.113
Prefix Length24
ItemName
Adapter NameMgt - Heartbeat
Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #4
Physical Address78-2B-CB-3C-DC-F5
StatusOperational
DNS Servers10.1.1.2, 10.1.1.8
IP Address192.168.141.10
Prefix Length24
ItemName
Adapter NameMgt - LiveMigration
Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #3
Physical Address78-2B-CB-3C-DC-F5
StatusOperational
DNS Servers10.1.1.2, 10.1.1.8
IP Address192.168.140.10
Prefix Length24
ItemName
Adapter NameMgt
Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver
Physical Address78-2B-CB-3C-DC-F5
StatusOperational
DNS Servers10.1.1.2, 10.1.1.8
IP Address10.1.1.4
Prefix Length24
ItemName
Adapter NameiSCSI2
Adapter DescriptionBroadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)
#37
Physical Address78-2B-CB-3C-DC-F7
StatusOperational
DNS Servers
IP Address192.168.130.112
Prefix Length24
ItemName
Adapter NameLocal Area Connection* 12
Adapter DescriptionMicrosoft Failover Cluster Virtual Adapter
Physical Address02-61-1E-49-32-8F
StatusOperational
DNS Servers
IP Addressfe80::cc2f:d769:fe24:3d04%23
Prefix Length64
IP Address169.254.2.195
Prefix Length16
ItemName
Adapter NameLoopback Pseudo-Interface 1
Adapter DescriptionSoftware Loopback Interface 1
Physical Address
StatusOperational
DNS Servers
IP Address::1
Prefix Length128
IP Address127.0.0.1
Prefix Length8
ItemName
Adapter Nameisatap.{96B6424D-DB32-480F-8B46-056A11A0A6A8}
Adapter DescriptionMicrosoft ISATAP Adapter
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.131.113%16
Prefix Length128
ItemName
Adapter Nameisatap.{A0353AF4-CE7F-4811-B4FC-35273C2F2C6E}
Adapter DescriptionMicrosoft ISATAP Adapter #3
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.130.112%18
Prefix Length128
ItemName
Adapter Nameisatap.{FAAF4D6A-5A41-4725-9E83-689D8E6682EE}
Adapter DescriptionMicrosoft ISATAP Adapter #4
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.141.10%22
Prefix Length128
ItemName
Adapter Nameisatap.{C66443C2-DC5F-4C2A-A674-2191F76E33E1}
Adapter DescriptionMicrosoft ISATAP Adapter #5
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:10.1.1.4%27
Prefix Length128
ItemName
Adapter Nameisatap.{B3A95E1D-CB95-4111-89E5-276497D7EF42}
Adapter DescriptionMicrosoft ISATAP Adapter #6
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.140.10%29
Prefix Length128
ItemName
Adapter Nameisatap.{7705D42A-1988-463E-9DA3-98D8BD74337E}
Adapter DescriptionMicrosoft ISATAP Adapter #7
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:169.254.2.195%30
Prefix Length128
ACHV02.AshtaChemicals.local
ItemName
Adapter NameMgt - Heartbeat
Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #4
Physical Address74-86-7A-D4-C9-8B
StatusOperational
DNS Servers10.1.1.8, 10.1.1.2
IP Address192.168.141.12
Prefix Length24
ItemName
Adapter NameMgt - LiveMigration
Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #3
Physical Address74-86-7A-D4-C9-8B
StatusOperational
DNS Servers10.1.1.8, 10.1.1.2
IP Address192.168.140.12
Prefix Length24
ItemName
Adapter NameMgt
Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #2
Physical Address74-86-7A-D4-C9-8B
StatusOperational
DNS Servers10.1.1.8, 10.1.1.2
IP Address10.1.1.5
Prefix Length24
IP Address10.1.1.248
Prefix Length24
ItemName
Adapter NameiSCSI1
Adapter DescriptionBroadcom NetXtreme Gigabit Ethernet #7
Physical Address74-86-7A-D4-C9-8A
StatusOperational
DNS Servers
IP Address192.168.130.121
Prefix Length24
ItemName
Adapter NameiSCSI2
Adapter DescriptionBroadcom NetXtreme Gigabit Ethernet
Physical Address00-10-18-F5-08-9C
StatusOperational
DNS Servers
IP Address192.168.131.121
Prefix Length24
ItemName
Adapter NameLocal Area Connection* 11
Adapter DescriptionMicrosoft Failover Cluster Virtual Adapter
Physical Address02-8F-46-67-27-51
StatusOperational
DNS Servers
IP Addressfe80::3471:c9bf:29ad:99db%25
Prefix Length64
IP Address169.254.1.193
Prefix Length16
ItemName
Adapter NameLoopback Pseudo-Interface 1
Adapter DescriptionSoftware Loopback Interface 1
Physical Address
StatusOperational
DNS Servers
IP Address::1
Prefix Length128
IP Address127.0.0.1
Prefix Length8
ItemName
Adapter Nameisatap.{8D7DF16A-1D5F-43D9-B2D6-81143A7225D2}
Adapter DescriptionMicrosoft ISATAP Adapter #2
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.131.121%21
Prefix Length128
ItemName
Adapter Nameisatap.{82E35DBD-52BE-4BCF-BC74-E97BB10BF4B0}
Adapter DescriptionMicrosoft ISATAP Adapter #3
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.130.121%22
Prefix Length128
ItemName
Adapter Nameisatap.{5A315B7D-D94E-492B-8065-D760234BA42E}
Adapter DescriptionMicrosoft ISATAP Adapter #4
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.141.12%23
Prefix Length128
ItemName
Adapter Nameisatap.{2182B37C-B674-4E65-9F78-19D93E78FECB}
Adapter DescriptionMicrosoft ISATAP Adapter #5
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:192.168.140.12%24
Prefix Length128
ItemName
Adapter Nameisatap.{104DC629-D13A-4A36-8845-0726AC9AE25E}
Adapter DescriptionMicrosoft ISATAP Adapter #6
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:10.1.1.5%33
Prefix Length128
ItemName
Adapter Nameisatap.{483266DF-7620-4427-BE5D-3585C8D92A12}
Adapter DescriptionMicrosoft ISATAP Adapter #7
Physical Address00-00-00-00-00-00-00-E0
StatusNot Operational
DNS Servers
IP Addressfe80::5efe:169.254.1.193%34
Prefix Length128
Verifying that a node does not have multiple adapters connected to the same
subnet.
Verifying that each node has at least one adapter with a defined default
gateway.
Verifying that there are no node adapters with the same MAC physical address.
Found duplicate physical address 78-2B-CB-3C-DC-F5 on node
ACHV01.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV01.AshtaChemicals.local adapter Mgt - LiveMigration.
Found duplicate physical address 78-2B-CB-3C-DC-F5 on node
ACHV01.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV01.AshtaChemicals.local adapter Mgt.
Found duplicate physical address 78-2B-CB-3C-DC-F5 on node
ACHV01.AshtaChemicals.local adapter Mgt - LiveMigration and node
ACHV01.AshtaChemicals.local adapter Mgt.
Found duplicate physical address 74-86-7A-D4-C9-8B on node
ACHV02.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV02.AshtaChemicals.local adapter Mgt - LiveMigration.
Found duplicate physical address 74-86-7A-D4-C9-8B on node
ACHV02.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV02.AshtaChemicals.local adapter Mgt.
Found duplicate physical address 74-86-7A-D4-C9-8B on node
ACHV02.AshtaChemicals.local adapter Mgt - LiveMigration and node
ACHV02.AshtaChemicals.local adapter Mgt.
Verifying that there are no duplicate IP addresses between any pair of nodes.
Checking that nodes are consistently configured with IPv4 and/or IPv6
addresses.
Verifying that all nodes IPv4 networks are not configured using Automatic
Private IP Addresses (APIPA).
Back to Summary
Back to Top
Validate Multiple Subnet Properties
Description: For clusters using multiple subnets, validate the network
properties.
Testing that the HostRecordTTL property for network name Name: Cluster1 is set
to the optimal value for the current cluster configuration.
HostRecordTTL property for network name Name: Cluster1 has a value of 1200.
Testing that the RegisterAllProvidersIP property for network name Name:
Cluster1 is set to the optimal value for the current cluster configuration.
RegisterAllProvidersIP property for network name Name: Cluster1 has a value of
0.
Testing that the PublishPTRRecords property for network name Name: Cluster1 is
set to the optimal value for the current cluster configuration.
The PublishPTRRecords property forces the network name to register a PTR in
DNS reverse lookup record IP address to name mapping.
Back to Summary
Back to Top
Validate Network Communication
Description: Validate that servers can communicate, with acceptable latency,
on all networks.
Analyzing connectivity results ...
Multiple communication paths were detected between each pair of nodes.
Back to Summary
Back to Top
Validate Windows Firewall Configuration
Description: Validate that the Windows Firewall is properly configured to
allow failover cluster network communication.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - Mgt - LiveMigration'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - iSCSI3'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - Mgt - Heartbeat'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - Mgt'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - iSCSI2'.
The Windows Firewall on node ACHV01.AshtaChemicals.local is configured to
allow network communication between cluster nodes.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - Mgt'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - iSCSI2'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - Mgt - LiveMigration'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - Mgt - Heartbeat'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - iSCSI1'.
The Windows Firewall on node ACHV02.AshtaChemicals.local is configured to
allow network communication between cluster nodes.
Back to Summary
Back to Top -
How to get servername from a request but not the cluster name?
hi all,
how do i get server name from the request? This is the scenario, When ever a request is made, its handed to a cluster and then directed to one of the server in the cluster.
When i say request.getServerName();---- This is giving me the cluster name and not the server name.
any suggestions/idea ? Thanks alot in advance.
Edited by: new_member on Apr 18, 2008 9:11 PMADJavaUser wrote:
You could try this:
Create a batch or shell script that executes ifconfig or ipconfig and writes the IP address out to a file.
Place each shell script file at different locations on each server within the cluster.
Then within the code, try to execute each script from an external process (Runtime.exec). Since the files are at different locations within each server only the correct shell script for each server should execute and write the IP Address to a file. You'll have to detect which one ran. Then open the file that was written, possible parse it for the IP Address and use the code that I already provided.
This is a time consuming process that will slow your application. Additionally depending on how your cluster is set up it might not work and still return the cluster's IP address.I got the solution....java.net.InetAddress.getLocalHost().getHostName(); works fine...But thanks guyz for ur responses -
How to get cluster name with c++ API?
Hi everyone,
I want to get cluster name with c++ API, do you know how to do that?
Thanks very much!!!
Guangyin937347 wrote:
Hi Robert,
For Java, we can get the cluster name like this:
cache.getCacheService.getCluster().getClusterName(),
for c++, just as you said, do you mean that i can try to get cluster name like this:
Sting::View name = cache->getCacheService()->getInfo()->getServiceName();
InvocationService::handle invocation = cast<InvocationService::handle>(CacheFactory::getService(name));
String clusterName = invocation->getInfo()->getServiceName();
But i can not get the right result.
I know little about how to use InvocationService, could you give me example?
Thanks very much!!!
GuangyinHi Guangyin,
I do not know the C++ API, I never used it, but what you wrote definitely does not look right.
InvocationService is a way to send arbitrary Java logic (you need to write both the Java logic and a C++ counterpart class, the C++ class will serialize itself with POF and the Java class will deserialize the same data appropriately) as a command to the cluster via the TCP*Extend connection and the command would execute on the proxy node and thus it would have access to the cluster itself.
You probably should start with the documentation of the Coherence*Extend C++ API documentation for samples.
http://docs.oracle.com/cd/E24290_01/coh.371/e22839/toc.htm
http://docs.oracle.com/cd/E24290_01/coh.371/e22839/cpp_part.htm#CHDHCIEJ
Best regards,
Robert -
Duplicate cluster names in network
I'm setting up several Weblogic servers for Oracle Forms and Reports. The Portal Forms Reports Discoverer installation/configuration installs managed servers and clusters with default names, and doesn't explicitly configure a unicast channel for the clusters.
We will be working with several Weblogic installations in our network (a production cluster and at least 4 test clusters), which will be able to see each other on the network. The clusters will all have the same default cluster names, and will all use the default unicast channel. We will only use the Forms and Reports functionalities from these clusters, we won't configure any services like JMS or JDBC.
Should I worry about these clusters conflicting with each other, if I don't configure a separate unicast channel per cluster? Or is there no need to worry, because Forms and Reports don't really use the unicast channel anyway?
Besides the Forms and Reports clusters, we will also configure some separate clusters in which we will deploy J2EE applications, which will use JMS and JDBC. Just like the Forms clusters mentioned above, these will also be a production, and several test clusters, on the same network.
These clusters will be entirely configurable by us, but the applications will use non-configurable JMS and JDBC names, which might cause conflicting JNDI-names on the network.
Am I correct in assuming that we need to configure one of the following (or both) for these J2EE application clusters?:
- Create a uniquely named network channel for protocol cluster-broadcast, to use as a unicast channel.
- Create each cluster with a unique name, so the separate clusters on the network will 'know' which managed servers are its members, and which messages to ignore.
Regards,
Peter.You can refer below link
http://blogs.msdn.com/b/mariussutara/archive/2008/09/05/cluster-and-maintenance-mode.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali -
Set cluster name and IP address ONLINE
Hi
I had to shut down all cluster nodes. After turned on all cluster nodes I saw in Management cluster console:
Basic cluster resourses:
Name: CLuster1 State:Offline
Adress IP: xx.xx.xx.xx. State Offline
How to set these cluster resources (cluster name, ip adress) Online using Powershell?
Kind Regards TomaszHi Yukio Seki,
If you want to know how to bring cluster resource online please refer the following KB:
Microsoft.FailoverClusters.PowerShell
https://technet.microsoft.com/en-us/library/ee461009.aspx
Failover Clusters Cmdlets in Windows PowerShell
https://technet.microsoft.com/en-us/library/hh847239.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Shared Services - Cluster name specified is invalid
I'm trying to give a user access to run a calc script (11.1.2) -when I go into Shared Services to launch "assign access control" I get the message "Cluster name [Essbase: MyServer name:1] specified is invalid". How do I correct this? or am I going about this the wrong way?
Thanks,
PaulYou can use grant Maxl command.
grant execute 'Sample'.'Basic'.'nu' to user 'admin';
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_tech_ref/frameset.htm?maxl_grant.html
Is Essbase working fine? Which url are you using to launch Shared Services?
Regards
Celvin
http://www.orahyplabs.com
Maybe you are looking for
-
How can I organize my songs by Artist, both on my Ipod and in the Library? I have multiple songs showing all by the same Artist, but I can't find anyway I can put all the songs under the same Artist.
-
Lightroom has lost all my keywords!!!
Let me start by saying that Adobe has the most irritating customer support I have EVER dealt with... way to not have an email or phone number anywhere for your paying customers Adobe. and if there is a line/email way to hide it so effeciently it can
-
What do I do if I can't upload photos into my photobook? Every time that I try, the upload starts but then stops. Then the only options I have are to cancel or retry. Has anyone else had this problem and how have they solved it?
-
First steps in GUI development
Hi, i have some experience in Win32 development (SDK and MFC) and i have to write an application for Solaris/CDE/Motif. So what i need are manuals/tutorials for Motif programming, a kind of hello world with some buttons to click on etc. So far i have
-
De-Noise setting with custom RAW fine-tuning ?
If I look at the De-Noise setting when using the Apple default you will notice that it varies with the ISO of the image (Njikon D4). As the ISO increases so does the De-Noise setting. This is often a good thing. If I save my own RAW fine-tuning setti