Iscsi target on cluster node

Hi
I'm trying to install a cluster on a lab environment, i have to physical servers, and would like to use them as cluster nodes, on one of this nodes i would like to install iscsi target server to use for sharing disk to the cluster itself is this possible?
because i did all the configurations but after installing the cluster the iscsi target server doesn't work anymore.
thanks
Bad news: You cannot do it with a Microsoft built-in solutions because you do need indeed to have physical shared storage to make Microsoft iSCSI target clustered. Something like on Robert Smit blog here:
Clustering Microsoft iSCSI Target
https://robertsmit.wordpress.com/2012/06/26/clustering-iscsi-target-on-windows-2012-step-by-step/
...or here:
MSFT iSCSI Target in HA
https://technet.microsoft.com/en-us/library/gg232621(v=ws.10).aspx
...or very detailed walk thru here:
MSFT iSCSI Target in High Availability Mode
https://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
Good news: you can take a third-party solution from various companies (below) and create an HA iSCSI volumes on just a pair of nodes. See:
StarWind Virtual SAN
http://www.starwindsoftware.com/starwind-virtual-san-free
(this setup is FREE of charge, you just need to be an MCT, MVP or MCP to obtain your free 2-node key)
...to have a setup like this:
Also SteelEye has similar one here:
SteelEye #SANLess Clusters
http://us.sios.com/products/datakeeper-cluster/
DataCore SANsyxxxx
http://www.datacore.com/products/SANsymphony-V.aspx
You can also spawn a VMs running FreeBSD/HAST or Linux/DRBD to build a very similar setup yourself (Two-node setups should be Active-Passive to avoid brain split, Windows solutions from above all maintain own pacemaker and heartbeats to run Active-Active
on just a pair of nodes).
Good luck and happy clustering :)
StarWind Virtual SAN clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Similar Messages

SCVMM losing connection to cluster nodes

Hey guys'n girls, I hope this is the right forum for this question. I already opened a ticket at MS support as well because it's impacting our production environment indirectly, but even after a week there's been no contact. Losing faith in MS support there
The problem we're having is that scvmm is that a host enters the 'needs attention' state, with a winrm error 0x80338126. I guess it has something to do with the network or with Kerberos, and I've found some info on it, but I still haven't been able to solve
it. Do you guys have any ideas?
Problem summary:
We are seeing an issue on our new hyper-v platform. The platform should have been in production last week, but this issue is delaying our project as we can't seem to get it stable.
The problem we are experiencing is that SCVMM loses the connection to some of the Hyper-V nodes. Not one
specific node. Last week it happened to two nodes, and today it happened to another node. I see issues with WinRM, and I expect something to do with kerberos. See the bottom of this post for background details and software versions.
The host gets the status 'needs attention', and if you look at the status of the machine, WinRM gives an error. The error is:
Error (2916)
VMM is unable to complete the request. The connection to the agent cc1-hyp-10.domaincloud1.local was lost.
WinRM: URL: [http://cc1-hyp-10.domaincloud1.local:5985], Verb: [ENUMERATE], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_Service], Filter: [select * from Win32_Service where Name="WinRM"]
Unknown error (0x80338126)
Recommended Action
Ensure that the Windows Remote Management (WinRM) service and the VMM agent are installed and running and that a firewall is not blocking HTTP/HTTPS traffic. Ensure that VMM server is able to communicate with cc1-hyp-10.domaincloud1.local over WinRM by successfully
running the following command:
winrm id –r:cc1-hyp-10.domaincloud1.local
This
problem can also be caused by a Windows Management Instrumentation (WMI) service crash. If the server is running Windows Server 2008 R2, ensure that KB 982293 (http://support.microsoft.com/kb/982293)
is installed on it.
If the error persists, restart cc1-hyp-10.domaincloud1.local and then try the operation again. /nRefer to
http://support.microsoft.com/kb/2742275 for more details.
Doing a simple test from the VMM server to the problematic cluster node shows this error:
PS C:\> hostname
CC1-VMM-01
PS C:\> winrm id -r:cc1-hyp-10.domaincloud1.local
WSManFault
    Message = WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this
computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.
Error number: -2144108250 0x80338126
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM
firewall exception for public profiles limits access to remote computers within the same local subnet.
I CAN connect from other hosts to this problematic cluster node:
PS C:\> hostname
CC1-HYP-16
PS C:\> winrm id -r:cc1-hyp-10.domaincloud1.local
IdentifyResponse
    ProtocolVersion =
http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
    ProductVendor = Microsoft Corporation
    ProductVersion = OS: 6.3.9600 SP: 0.0 Stack: 3.0
    SecurityProfiles
        SecurityProfileName =
http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/spnego-kerberos
And I can connect from the vmm server to all other cluster nodes:
PS C:\> hostname
CC1-VMM-01
PS C:\> winrm id -r:cc1-hyp-11.domaincloud1.local
IdentifyResponse
    ProtocolVersion =
http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
    ProductVendor = Microsoft Corporation
    ProductVersion = OS: 6.3.9600 SP: 0.0 Stack: 3.0
    SecurityProfiles
        SecurityProfileName =
http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/spnego-kerberos
So at this point only the test from the cc1-vmm-01 to cc1-hyp-10 seems to be problematic.
I followed the steps in the page
https://support.microsoft.com/kb/2742275 (which is referred to above). I tried the VMMCA, but it can't really get it working the way I want, or it seems to give outdated recommendations.
I tried checking for duplicate SPN's by running setspn -x on affected machines. No results (although I do not understand
what an SPN is or how it works). I rebuilt the performance counters.
It tried setting 'sc config winrm type= own' as described in [http://blinditandnetworkadmin.blogspot.nl/2012/08/kb-how-to-troubleshoot-needs-attention.html].
If I reboot this cc1-hyp-10 machine, it will start working perfectly again. However, then I can't troubleshoot the issue, and it will happen again.
I want this problem to be solved, so vmm never loses connection to the hypervisors it's managing again!
Background information:
We've set up a platform with Hyper-V to run a VM workload. The platform consists of the following hardware:
2 Dell R620's with 32GB of RAM, running hyper-v to virtualize the cloud management layer (DC's, VMM, SQL). These machines are called cc1-hyp-01 and cc1-hyp-02. They run the management vm's like cc1-dc-01/02, cc1-sql-01, cc1-vmm-01, etc. The names are self-explanatory.
The VMM machine is NOT clustered.
8 Dell M620 blades with 320GB of RAM, running hyper-v to virtualize the customer workload. The machines are
called cc1-hyp-10 until cc1-hyp-17. They are in a cluster.
2 Equallogic units form a SAN (premium storage), and we have a Dell R515 running iscsi target (budget storage).
We have Dell Force10 switches and Cisco C3750X switches to connect everything together (mostly 10GB links).
All hosts run Windows Server 2012R2 Datacenter edition. The VMM server runs System Center Virtual Machine Manage 2012 R2.
All the latest Windows updates are installed on every host. There are no firewalls between any host (vmm and hypervisors) at this level. Windows firewalls are all disabled. No antivirus software is installed, no symantec software is installed.
The only non-standard software that is installed is the Dell Host Integration Tools 4.7.1, Dell Openmanage Server Administrator, and some small stuff like 7-zip, bginfo, net-snap, etc.
The SCVMM service is running under the domain account DOMAINCLOUD1\scvmm. This machine is in the local administrators group of each cluster node.
On top of this cloud layer we're running the tenant layer with a lot of vm's for a specific customer (although they are all off now).

I think I found the culprit, after an hour of analyzing wireshark dumps I found the vmm had jumbo frames enabled on the management interface to the hosts (and the underlying infrastructure does not).. Now my winrm commands started working again.

Server 2012 R2 iSCSI Target - Multiple targets per iSCSI Virtual Disk with CHAP

Scenario I am trying to achieve is this:
Windows Server 2012 R2 serves as iSCSI Target configured to have 1 iSCSI Virtual Disk
2 Hyper-V servers connecting to this target with iSCSI Inistator and have multiple targets for that iSCSI Virtual Disk using CHAP
**These 2 are nodes in fail over cluster, this iSCSI is added as a CSV.
Issue that I have, is that you can only have 1 target per iSCSI Virtual Disk
Both Hyper-V servers can connect to this LUN without issue when I add both initiator IDs to the target, but once I enable CHAP, you can only put one initiator ID in the "Name" field, so I can only connect from 1 Hyper-V server.
Do you know of a way around this?

From my understanding, "chaptest" is a single target, my goal was to make 2 targets to the same iSCSI virtual disk.
So if you were to right click the iSCSI virtual disk that "chaptest" is assigned to and click "Assign iSCSI Veritual Disk...", then select "New iSCSI Target, and proceed with the wizard it removes the "chaptest" target
and adds the new one just created.
My goal was to have 2 targets to 1 iSCSI VD, but seeing your screenshot, with 2 initiators connected, that goal doesn't seem needed anymore.
I was under the impression that the "User name" = the iscsi initiator IQN name, which had to be unique. That is why I thought I would need 2 targets.
Thanks

OVS servers restart when iSCSI target restarts

Long story short, I've been working on my new lab at home off and on. Tonight I was working on my lab to get to the point where I would have OVMM as a virtual machine as the dedicated host I have for temporary measures only has two gigs of ram vs the recommended 8 gigs of ram.
More to the point: I was working on the storage portion of my setup and I got my iSCSI target discovered (FreeNAS 9.3) and I was able to build my cluster of OVSs. I noticed earlier that my FreeNAS server had some pending updates and I figured it would be a good idea to perform these updates before I started using the iSCSI storage for active virtual machines. Naturally, when the updates are done on my FreeNAS server, it reboots.
What I don't understand is why both of my OVSs restarted at the same time after the FreeNAS server went down for a reboot. Was there a hidden gotcha? Did I overlook something in the documentation?
A side effect of the unexpected reboot is the fact that my OVS(2) did not come back online with OVMM and I could not ping my management interface for that OVS. I did several Google searches and tried some manual up/downs of the interfaces and tried one effort to manually configure bond0 to an IP address to try and get some sort of response. Needless to say, none of those were good ideas and didn't help. Therefore, I'm re-installing OVS on server 2 now.
If anyone has any ideas as to how I could have fixed OVS(2) I'm more than willing to take notes in case this happens again.
Thank you for any and all help,
Brendan
P.S. If this has any influence with my situation, I am running LACP bonds and all IP addresses are configured on the VLAN interfaces. I have not had any issues configuring my switch and with the exception of OVS(2) not wanting to reply after the unexpected restart I had everything working. An added gotcha is that the storage VLAN interface on OVS(2) continued to reply after the restart.

Hi Brendan,
the situation you encountered is expected for a single-headed iSCSI target. If you present OVM with a LUN - regardless if it's iSCSI or FC, OVM creates an OCFS2 volume on it, when you choose that LUN to be used as a storage repository. This is, since OCFS2 is a cluster-aware file system and thus is the only supported fs to use for a cluster setup. Now, although OVFS2 is really easy to setup - compared to other cluster file systems - it has some mechanics that will cause your nodes to fence (or reboot) in case the node looses "contact" with the OCFS2. Each node writes little keep-alive fragments onto the OCSF2 and if you reboot your iSCSI target, then this will cease and OCFS2 will fence itself, hoping for some minor glitch that may be gone after a reboot.
There are a couple of ways to achieve this with iSCSI, but their resp. setup is not easy, and the hoops to jump through are probably to many for a lab setup. E.g. I am running a two RAC nodes as iSCST targets, which in turn do have high-redundancy disk setup behind them, consiting of 3 seperate storage servers. So, in my setup I am able to survive:
- two storage node failures
- one RAC node failure (which provides the iSCSI target for my OVS)
Regarding your OVS2, as you have already re-installed OVS2, there will be now way, to tell, what went wrong with it, as you'd need access to the console to poke around a bit, while OVS2 is in that situation, where it doesn't respond to pings on it's management interface.
Cheers,
budy

How to sync the data between the two iSCSI target server

Hi experts:
I have double HP dl380g8 server, i plan to install the server 2012r2 iSCSI target as storage, i know the iSCSI storage can setup as high ability too, but after some research i doesn't find out how to sync the data between the two iSCSI target server, can
any body help me?
Thanks

Hi experts:
I have double HP dl380g8 server, i plan to install the server 2012r2 iSCSI target as storage, i know the iSCSI storage can setup as high ability too, but after some research i doesn't find out how to sync the data between the two iSCSI target server, can
any body help me?
Thanks
There are basically three ways to go:
1) Get compatible software. Microsoft iSCSI target cannot do what you want out-of-box but good news third-party software (there are even free versions with a set of limitations) can do what you want. See:
StarWind Virtual SAN [VSAN]
http://www.starwindsoftware.com/native-san-for-hyper-v-free-edition
DataCore SANxxx
http://datacore.com/products/SANsymphony-V.aspx
SteelEye DataKeeper
http://us.sios.com/what-we-do/windows/
All of them do basically the same: mirror set of LUs between Windows hosts to emulate a high performance and fault tolerant virtual SAN. All of them do this in active-active mode (all nodes handle I/O) and at least StarWind and DataCore have sophisticated
distributed cache implementations (RAM and flash).
2) Get incompatible software (MSFT iSCSI target) and run it in generic Windows cluster. That would require you to have CSV so physical shared storage (FC or SAS, iSCSI obviously has zero sense as you can feed THAT iSCSI target directly to your block storage
consumers). This is doable and is supported by MSFS but has numerous drawbacks. First of all it's SLOW as a) MSFT target does no caching and even does not use file system cache (at all, VHDX it uses as a containers are opened and I/O-ed in a "pass-thru" mode)
b) it's only active-passive (one node will handle I/O @ a time with other one just doing nothing in standby mode) and c) long I/O route (iSCSI initiator -> MSFT iSCSI target -> clustered block back end). For reference see:
Configuring iSCSI Storage for High Availability
http://technet.microsoft.com/en-us/library/gg232621(v=ws.10).aspx
MSFT iSCSI Target Cluster
http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
3) Re-think what you do. Except iSCSI target from MSFT you can use newer technologies like SoFS (obviously faster but requires a set of a dedicated servers) or just a shared VHDX if you have a fault tolerant SAS or FC back end and want to spawn a guest VM
cluster. See:
Scale-Out File Servers
http://technet.microsoft.com/en-us/library/hh831349.aspx
Deploy a Guest Cluster Using a Shared Virtual Hard Disk
http://technet.microsoft.com/en-us/library/dn265980.aspx
With Windows Server 2012 R2 release virtual FC and clustered MSFT target are both really deprecated features as shared VHDX is both faster and easier to setup and use if you have FC or SAS block back end and need to have guest VM cluster.
Hope this helped a bit :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Migrate iscsi Targets

Hello,
we have a 2 node sles10.3+oes2sp3 cluster.
both are iscsi-initiators against one target.
Now we need to migrate the data to another iscsi-target.
Is it possible to add the new target2 as a device to the existing pool, migrate the data from target1 to target2 and remove target1?
If yes what is the command for this?
thx,
hugo

In article <[email protected]>, Susehoush wrote:
> Now we need to migrate the data to another iscsi-target.
>
Will you be removing the first target? If so you will also need to
mirror the SBD before you go very far. I last did that step under
NetWare, but the process looks much the same now. Raw docs:
http://www.novell.com/documentation/...age=/documenta
tion//oes2/clus_admin_lx/data/bl9gj0q.html
then for the pools/volumes them selves, you can either do NSS drive
mirroring of them and/or use the Novell Migration Utility as
appropriate for your situation (i.e. are there pool/volume size changes
you need to do).
The new target will not be added as part of an existing pool, but as
its own for either step.
Andy Konecny
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

ISCSI target performance

Hello!
There're a lot of iSCSI targets with one or two 1Gbps nics on market today but I have serious doubts about their performance: 1Gbps(or 2Gbps) compared to 6 Gbps in raw SAS/SATA make me think their network speed will be the bottleneck in any setup (for example,
two node cluster with an iscsi target). Can anybody please tell me what performance issues may arise, for example, if I place a VM with SQL server on such target?
Thank you in advance,
Michael

"To have fault tolerance you have to have either dual hardware controllers (storage virtualization
creating LU from ultiple physical spindles) or use distributed software controllers (DRBD, HAST, Clustered Storage Spaces etc). " - I don't agree: fault tolerance can be provided by the single RAID 5 controller - of cause it's better to have two controllers
but it's just one more level of fault tolerance. Many (or even all of them) iSCSI targets have RAID controllers that allow them to be fault tolerant and I can't understand why this is not the case with DAS: "If RAID capable, HBAs must be in non-RAID
mode with all RAID functionality disabled".
To make a long story short I'd like to know why I can use RAID with iSCSI and can't with DAS/SAS.
Regards,
Michael
Because Clustered Storage Spaces don't handle LU reservations in software (unlike other Software Defined Storage solutions like VSAN for example) and rely on a hardware mechanism inside single dual pot SAS drive for that. So either you use dumb SAS controllers
providing raw access to SAS spindles or use Clustered RAID controller who handle distributed lock on it's own (LSI Syncro for example) and in this case you *CAN* RAID disks and them pass them to CSS.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

ISCSI target weirdness

Hello!
If I hadn't experienced the issue I'm going to talk about I would have hardly believed it may ever happen...
I'm starting setting up a test cluster (all hosts = WinServer 2012 R2): Host3 = iSCSI target, Host1 and Host2 - cluster nodes.
1) I create three iSCSI disks on Host3: Disk1-Q (5Gb),
FS (60 Gb), Mail (60 Gb). All of them are "part" of the single target.
2) ... then make an iSCSI connection to Host3 from Host1 and Host2.
3) On Host1 I open Disk Management and create three volumes: Disk1-Q (X),
FS (Y), Mail (Z).
4) I format disk X (Disk1-Q) and give it the name "QUORUM".
4) Now I must open Disk Management on Host2 and make these disks online....but having connected to Host2 I see that all three disks are already online and UNformatted.
Here goes my "funny" "tests:
5) On Host2 I format THE SAME disk X (Disk1-Q) and give it another name "QUORUM2" - the operation succeeds.
6) I create the folder "hhh" on disk X (Disk1-Q) when I connected to Host1 and create the folder "kkk" on
Disk1-Q when connected to Host2. Each node shows only its "own" folder on
Disk1-Q...
7!) a) On Host1: I copied one iso image (3,6 Gb) to disk X (Disk1-Q) and
b) On Host2: I copied other iso image (3.1 Gb) do disk
X (Disk1-Q).
The second copy operation succeeded too!!! Now my 5Gb disk X (iSCSI disk Disk1-Q) contains two iso images that total to 6.7Gb!
...I know that's impossible...is it magic?
...but looking at the pictures above what can you say?
Thank you in advance,
Michael

You cannot do what you're trying to do the way you do :) Making long story short: you connect single NTFS-formatted volume to more then one writer. They both update data and metadata w/o telling each other what they do. That results corrupted volume. You
absolutely need some separate arbiter to take care of ditributed locks. It can be CSV (set of filters on top of NTFS) or it can be some clustered file system (trust me you don't need this as it's expensive). Or layer SMB share on top of your block volume (iSCSI
or generic does not matter) and connect from multiple clients. For more details you can read the link below (ignore StarWind as issues are the same for any SAN). See:
SAN Vs. NAS
http://www.starwindsoftware.com/forums/starwind-f5/trying-clear-this-use-iscsi-instead-smb-t1392.html
Hope this helped a bit ;)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Unable to failover the services in active-active cluster node

Hi,
i am applying the sp2 patch for sql server 2008 r2 in active-active cluster, we have 3 services in the cluster , node 1 as 2 prefered owner and node 2 as 1 prefered owner, when i try to move the service from node 2 to node1 , i am getting the below errors
DCOM was unable to communicate with the computer XXXXXXXXX using any of the configured protocols.
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server XXXXXXXXX. The target name used was RPCSS/XXXXXX. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal
name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using
a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server
name is not fully qualified, and the target domain (XXXXXX) is different from the client domain (XXXXXXX), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
The Cluster service failed to bring clustered service or application 'CHCROCHC045' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Cluster resource 'SQL Server (CHCROCHC045)' in clustered service or application 'CHCROCHC045' failed.
any inputs appreciated to resolve this issue as i could not procedd with patching
BR
PGR

Hi PGR,
As the issue is more related to Windows Server, I would like to recommend you post the issue in the
Windows Server forums for better support.
In addition, below are some article about troubleshooting error ” DCOM was unable to communicate with the computer XXXXXXXXX using any of the configured protocols” for your reference.
Event ID 10009 — COM Remote Service Availability
How to troubleshoot DCOM 10009 error logged in system event?
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Error while getting cluster node subtree

Hi,
We are on SP15.
The console logs show the following error
log generation timestamp : 2006_01_17_at_17_14_05
java.rmi.RemoteException: Error while getting cluster node subtree of :name=ClusterNodeRepresentative,j2eeType=com.sap.engine.services.adminadapter.impl.ClusterNodeRepresentative,SAP_J2EEClusterNode=2053400,SAP_J2EECluster=""; nested exception is:
     com.sap.engine.services.jmx.exception.MBeanServerClusterException: Exception during invocation of remote MBeanServer method, target node: 2053400
     at com.sap.engine.services.adminadapter.impl.ConvenienceEngineAdministratorImpl.getClusterNodeSubTree(ConvenienceEngineAdministratorImpl.java:242)
     at com.sap.engine.services.adminadapter.impl.ConvenienceEngineAdministratorImplp4_Skel.dispatch(ConvenienceEngineAdministratorImplp4_Skel.java:99)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.jmx.exception.MBeanServerClusterException: Exception during invocation of remote MBeanServer method, target node: 2053400
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:816)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.adminadapter.impl.ConvenienceEngineAdministratorImpl.getClusterNodeSubTree(ConvenienceEngineAdministratorImpl.java:239)
     ... 10 more
Caused by: com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 345 | src: cluster target-node: 2053400 req: invoke params-number: 4 params-bytes: 0 | :name=ClusterNodeRepresentative,j2eeType=com.sap.engine.services.adminadapter.impl.ClusterNodeRepresentative,SAP_J2EEClusterNode=2053400,SAP_J2EECluster="" null null null ]
     at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:680)
     at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invoke(MBeanServerConnectionImpl.java:467)
     at com.sap.engine.services.jmx.MBeanServerConnectionSecurityWrapper.invoke(MBeanServerConnectionSecurityWrapper.java:221)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
     ... 12 more
Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=ClusterNodeRepresentative,j2eeType=com.sap.engine.services.adminadapter.impl.ClusterNodeRepresentative,SAP_J2EEClusterNode=2053400,SAP_J2EECluster=XD1 not found in repository
     at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)
     at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:567)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)
     at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)
     at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)
     at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:523)
     at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:578)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:106)
     at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:173)
     at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)
     at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
java.lang.NullPointerException
     at com.sap.engine.services.adminadapter.gui.ClusterView.addGlobalDispatcherServiceProperties(ClusterView.java:455)
     at com.sap.engine.services.adminadapter.gui.ClusterView.createGlobalTrees(ClusterView.java:508)
     at com.sap.engine.services.adminadapter.gui.ClusterView.access$1200(ClusterView.java:29)
     at com.sap.engine.services.adminadapter.gui.ClusterView$4.run(ClusterView.java:420)
java.rmi.RemoteException: Error while getting cluster node subtree of :name=ClusterNodeRepresentative,j2eeType=com.sap.engine.services.adminadapter.impl.ClusterNodeRepresentative,SAP_J2EEClusterNode=2053400,SAP_J2EECluster=""; nested exception is:
     com.sap.engine.services.jmx.exception.MBeanServerClusterException: Exception during invocation of remote MBeanServer method, target node: 2053400
     at com.sap.engine.services.adminadapter.impl.ConvenienceEngineAdministratorImpl.getClusterNodeSubTree(ConvenienceEngineAdministratorImpl.java:242)
     at com.sap.engine.services.adminadapter.impl.ConvenienceEngineAdministratorImplp4_Skel.dispatch(ConvenienceEngineAdministratorImplp4_Skel.java:99)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.jmx.exception.MBeanServerClusterException: Exception during invocation of remote MBeanServer method, target node: 2053400
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:816)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.adminadapter.impl.ConvenienceEngineAdministratorImpl.getClusterNodeSubTree(ConvenienceEngineAdministratorImpl.java:239)
     ... 10 more
Caused by: com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 345 | src: cluster target-node: 2053400 req: invoke params-number: 4 params-bytes: 0 | :name=ClusterNodeRepresentative,j2eeType=com.sap.engine.services.adminadapter.impl.ClusterNodeRepresentative,SAP_J2EEClusterNode=2053400,SAP_J2EECluster="" null null null ]
     at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:680)
     at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invoke(MBeanServerConnectionImpl.java:467)
     at com.sap.engine.services.jmx.MBeanServerConnectionSecurityWrapper.invoke(MBeanServerConnectionSecurityWrapper.java:221)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
     ... 12 more
Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=ClusterNodeRepresentative,j2eeType=com.sap.engine.services.adminadapter.impl.ClusterNodeRepresentative,SAP_J2EEClusterNode=2053400,SAP_J2EECluster=XD1 not found in repository
     at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)
     at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:567)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)
     at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)
     at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)
     at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:523)
     at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:578)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:106)
     at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:173)
     at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)
     at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
java.lang.NullPointerException
     at com.sap.engine.services.adminadapter.gui.ClusterView.addGlobalDispatcherServiceProperties(ClusterView.java:455)
     at com.sap.engine.services.adminadapter.gui.ClusterView.createGlobalTrees(ClusterView.java:508)
     at com.sap.engine.services.adminadapter.gui.ClusterView.access$1200(ClusterView.java:29)
     at com.sap.engine.services.adminadapter.gui.ClusterView$4.run(ClusterView.java:420)
Any clue whats it?
rgds

Go the same error
+ /usr/java14_64/bin/java -showversion -Duser.language=en -DP4ClassLoad=P4Connection -Dp4Cache=clean -jar go.jar
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142ifx-20061222 (ifix 113727: SR7 + 112603) (JIT enabled: jitc))
java.lang.NullPointerException
        at com.sap.engine.services.adminadapter.gui.ClusterView$4.run(ClusterView.java:405)
Need some help!
Bernard

Iscsi target rewriting sparse backing store

Hi all,
I have this particular problem when trying to use sparse file residing on zfs as backing store for iscsi target. For the sake of this post, lets say I have to use the sparse file instead of whole zfs filesystem as iscsi backing store.
However, as soon as the sparse file is used as iscsi target backing store, Solaris OS (iscsitgt process) decides to rewrite entire sparse file and make it non-sparse. Note this all happens without any iscsi initiator (client) accessed this iscsi target.
My question is why the sparse file is being rewritten at that time?
I can expect write at iscsi initiator connect time, but why at the iscsi target create time?
Here are the steps:
1. Create the sparse file, note the actual size,
# dd if=/dev/zero of=sparse_file.dat bs=1024k count=1 seek=4096
1+0 records in
1+0 records out
# du -sk .
2
# ll sparse_file.dat
-rw-r--r--   1 root     root     4296015872 Feb 7 10:12 sparse_file.dat
2. Create the iscsi target using that file as backing store:
# iscsitadm create target --backing-store=$PWD/sparse_file.dat sparse
3. Above command returns immediately, everything seems ok at this time
4. But after couple of seconds, disk activity increases, and zpool iostat shows
# zpool iostat 3
               capacity     operations    bandwidth
pool         used avail   read write   read write
mypool 5.04G   144G      0    298      0 35.5M
mypool 5.20G   144G      0    347      0 38.0M
and so on, until the write over previously sparse 4G is over:
5. Note the real size now:
# du -sk .
4193252 .Note all of the above was happening with no iscsi initiators connected to that node nor target. Solaris OS did it by itself, and I can see no reasons why.
I would like to have those files sparse, at least until I use them as iscsi targets, and I would prefer those files to grow as my initiators (clients) are filling them.
If anyone can share some thoughts on this, I'd appreciate it
Thanks,
Robert

Problem solved.
Solaris iscsi target daemon configuration file has to be updated with:
<thin-provisioning>true</thin-provisioning>
in order to iscsitgtd not to initialize the iscsi target backing store files. This is all valid only for iscsi targets having files as backing store.
After creating iscsi targets with file (sparse or not) as backing store, there is no i/o activity whatsoever, and thats' what I wanted.
FWIW, This is how the config file looks now.
# more /etc/iscsi/target_config.xml
<config version='1.0'>
<thin-provisioning>true</thin-provisioning>
</config>
#

Lustre 2.0 and iSCSI - Active Active Cluster

Hi All,
I am sitting with a project that has me lookig at all kinds of solutions.
Here is the Project Scope:
2 to 4 servers running Linux ( Still to be decided what Version of Linux )
the above said servers must see the same iSCSI Target and space.
iSCSI Device is a Hard Device with 18TB of SAS2 Drvies and 4 1GB Ports Trunked
The reason for this is that we want to run a Linux based Email system, however our load on email is to huge for just one server
Thus we want to load balance the requests to the 2 or 4 Linux servers and they need to see the same Email on the iSCSI device as a user migth retrieve email from server1 yet email could come in to the users maildir on server2.
Question Time:
Can Lustre 2.0 provide me a solution?.
If not
Can someone recommend a solution to me?.
Thanks To everyone on this forum for making it such a great wealth of Knowledge.

The reason for this is that we want to run a Linux based Email system, however our load on email is to huge for just one server
Can someone recommend a solution to me?.Enterprise solutions often include several email gateways to increase availability, security and workload by physically separating internal and external access and implementing different servers for sending and receiving smtp traffic. A Linux cluster for processing incoming and outgoing smtp email is not necessarily the best option to increase processing power and availability. For smtp servers with public or external access, spam and relay protection can be a challenging issue.
Edited by: Dude on Jan 12, 2011 6:46 PM

Can I use cluster node for metadata controller?

Just as the subject says - can I use a cluster node as a secondary metedata controller, or do I need to use an Xserve? We already have an Xserve we would use as the primary controller

I have done this and attached the node to my iBook by firewire and booted the node in target mode and set the ServerHD as the startup for my iBook. Upon restart my iBook was an OSX server

Setup of G5 Cluster Node as a Standalone Server....

I have tried to no avail to try and setup a G5 XServer cluster node as a new Mac OS X 10.6 server. Here is where I screwed up - I pulled the drive out not realizing that creating a new partition on my Mac Book Pro would not be compatible and toasted the partition or rather made it so it was intel based instead of Power PC based and further went about installing the OS via "target mode" and went all the way through and realized that the server would not recognize it. So tonight I went back created 2 new partitions on the drive made them Power PC based but the server still does not recognize the drives when I boot up using the Option key. I get 2 buttons (refresh and I'm guessing a next) but the refresh puts up a clock for about 10 - 15 seconds and comes back and the next does nothing visible.
Here is what I have tried so far:
1) Tried booting up with the different boot commands
a) #3 Start up from internal drive
b) #5 Setup in Target mode but I don't have a PowerPC Mac to install from
3) #6 Reset NVRam
2) Boot with the letter "c" but nothing happens other then getting to a window with a single folder that alternates between a question and the mac guy logo (sorry don't know the exact name)
3) Boot with a Fire Wire external BluRay DVD player but does not seem to recognize it at all (could be the BluRay I guess have not thought of that)
And I'm sure I have tried a few other things but currently at wits end. I have a video card (3rd one was the charm) so I have video but have no idea how to get my Mac OS X Server software installed on this machine....
Any help or suggest would be greatly appreciated - oh I'm sure by now you know I'm new to Macs - I was an old Apple ][e guy but have been on PCs since the late 80's and finally got back to Apple - love them.

I have tried to no avail to try and setup a G5 XServer cluster node as a new Mac OS X 10.6 server.
Stop right there.
10.6 is Intel-only. It won't boot a PowerPC-based server. It doesn't matter about the disk format, or anything else. 10.5.x is as far as you can go with this machine.

[SOLVED] iscsi target lio (targetcli_fb) problem

I configured the targetcli:(don't use authentication)
tpg1> set parameter AuthMethod=None
set attribute authentication=0
/etc/rc.d/target run well.
But when the initiator connects the target, target reports the error:
iSCSI Initiator Node: iqn.xxxx-xxxx-xxxx is not authorized to access iSCSI target portal group: 1
uname -a
Linux 3.2.13-1-ARCH
what else settings? Thanks.
This is the saveconfig.json
"fabric_modules": [],
"storage_objects": [
"attributes": {
"block_size": 512,
"emulate_dpo": 0,
"emulate_fua_read": 0,
"emulate_fua_write": 1,
"emulate_rest_reord": 0,
"emulate_tas": 1,
"emulate_tpu": 0,
"emulate_tpws": 0,
"emulate_ua_intlck_ctrl": 0,
"emulate_write_cache": 0,
"enforce_pr_isids": 1,
"is_nonrot": 0,
"max_sectors": 1024,
"max_unmap_block_desc_count": 0,
"max_unmap_lba_count": 0,
"optimal_sectors": 1024,
"queue_depth": 32,
"unmap_granularity": 0,
"unmap_granularity_alignment": 0
"buffered_mode": true,
"dev": "/home/faicker/test.img",
"name": "disk1",
"plugin": "fileio",
"size": 10737418240,
"wwn": "b83cf4a1-5e30-4df4-a5a2-ac7163d78a4d"
"targets": [
"fabric": "iscsi",
"tpgs": [
"attributes": {
"authentication": 0,
"cache_dynamic_acls": 0,
"default_cmdsn_depth": 16,
"demo_mode_write_protect": 1,
"generate_node_acls": 0,
"login_timeout": 15,
"netif_timeout": 2,
"prod_mode_write_protect": 0
"enable": 1,
"luns": [
"index": 0,
"storage_object": "/backstores/fileio/disk1"
"node_acls": [],
"parameters": {
"AuthMethod": "None",
"DataDigest": "CRC32C,None",
"DataPDUInOrder": "Yes",
"DataSequenceInOrder": "Yes",
"DefaultTime2Retain": "20",
"DefaultTime2Wait": "2",
"ErrorRecoveryLevel": "0",
"FirstBurstLength": "65536",
"HeaderDigest": "CRC32C,None",
"IFMarkInt": "2048~65535",
"IFMarker": "No",
"ImmediateData": "Yes",
"InitialR2T": "Yes",
"MaxBurstLength": "262144",
"MaxConnections": "1",
"MaxOutstandingR2T": "1",
"MaxRecvDataSegmentLength": "8192",
"OFMarkInt": "2048~65535",
"OFMarkInt": "2048~65535",
"OFMarker": "No",
"TargetAlias": "LIO Target"
"portals": [
"ip_address": "0.0.0.0",
"port": 3260
"tag": 1
"wwn": "iqn.2003-01.org.linux-iscsi.u205.x8664:sn.5f9e1e0139f2"
Last edited by faicker (2012-04-16 15:27:21)

/iscsi/iqn.20...1e0139f2/tpg1> ls /
o- / ..................................................................... [...]
o- backstores .......................................................... [...]
| o- block ................................................ [0 Storage Object]
| o- fileio ............................................... [1 Storage Object]
| | o- disk1 ........................ [/home/mocan/test.img (10.0G) activated]
| o- pscsi ................................................ [0 Storage Object]
| o- ramdisk .............................................. [0 Storage Object]
o- ib_srpt ....................................................... [Not found]
o- iscsi .......................................................... [1 Target]
| o- iqn.2003-01.org.linux-iscsi.u205.x8664:sn.5f9e1e0139f2 .......... [1 TPG]
| o- tpg1 ........................................................ [enabled]
| o- acls ........................................................ [1 ACL]
| | o- iqn.2003-01.org.linux-iscsi.u205.x8664:sn.5f9e1e0139f2 [1 Mapped LUN]
| | o- mapped_lun0 ............................ [lun0 fileio/disk1 (rw)]
| o- luns ........................................................ [1 LUN]
| | o- lun0 ........................ [fileio/disk1 (/home/mocan/test.img)]
| o- portals .................................................. [1 Portal]
| o- 0.0.0.0:3260 ................................................. [OK]
o- loopback ....................................................... [0 Target]
o- qla2xxx ....................................................... [Not found]
o- tcm_fc ........................................................ [Not found]
This is targetcli ls / result.
the open-iscsi initiator report error:
iscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure)
It still wasn't solved.
Last edited by faicker (2012-04-14 15:36:07)

Iscsi target on cluster node

Similar Messages

Maybe you are looking for