Masking vs. zoning for UCS and NetApp storage LUNS

I know it's more a matter of Cisco MDS/storage, but nobody knows masking the LUNS and zoning, which one would be the most preferred method? I have two switches Cisco fabric 9148, two controllers SAN Netapp FAS3210 1 UCS chassis with 4 blades B200 M2. I said that I should not connect the Cisco UCS fabric interconnect directly at the back of the NetApp SAN and configure with LUN masking, but I rather configure a fabric zoning on switches Cisco 9148 MDS. Normally, this wouldn't be a problem but we have an offsite location where we have not all DMS switches to, and I would like to connect them directly to the San.

I was told that this could lead to corruption if misconfigured dsik and point of view of Cisco is to use a zoning by some type of switch Cisco Fabric. Of course, I have of course this Cisco advises anyone to manage this type of configuration through their facilities instead of on the SAN. Does anyone have an opinion on the matter?

Zoning and masking are two completely different characteristics.

Zoning occurs on your storage switches and is the equivalent of an ACL (Access Control List).  It limits who may be considering other targets and/or initiators.  (Who I see?)

Occurs on your storage array and masking limits what initiator LUN has access to.  (What do I see?)

* UCS is not supported to directly connect a storage array in the interconnection of fabric, at least to have a storage upstream switch (MDS or equivalent) to push the zoning.  The use of zoning prevents a faulty initiator potentially impacting on the operation of the others by limiting what they can see in the fabric.

If you happen to have a Nexus 5 K by chance, they can also work as your storage switch.  The N5K is able to perform almost all of the same services as MDS fabric and is fully supported.

Kind regards

Robert

Tags: Cisco DataCenter

Similar Questions

  • Configuration of Nexus 5 k for SAN switching between UCS 6100 s and NetApp storage

    We strive to get our configuration of the UCS environment make start SAN LUN on our NetApp storage. We have a pair of Nexus 5Ks with the company / SAN license on them and the 6-port FC module. What to do to configure Nexus 5000 to operate as the SAN switch between the target storage and environment of the UCS?

    You see the 6120 WWPN on the N5Ks? What is the result of 'show flogi database' and 'show int br '.

    You have mapped the FC ports on the 6120 for the proper VSAN?

    NPIV is enabled?

  • PSP for ESXi using NetApp storage

    I use ESXi 4.1.  Storage is CF of NetApp.  I enabled ALUA on groups of the initiator.  The Type of storage array is VMW_SATP_ALUA.  The selection of the path is by default, the most recently used.  What is the cmd to ESXi4.1 define the selection of the default path for the Round Robin.  Thank you

    That means that the policy in your case has been changed to MRU, but not RR, then maybe you can run the command again once, he appeared properly tuned.

    esxcli - server - root nmp ATAS setdefaultpsp psp - VMW_PSP_RR - ATAS VMW_SATP_DEFAULT_AA username

  • UCS FI and iSCSI storage

    We are poised to implement a UCS B Series. I have a question for FI 6248UP. I have read and used the emulator for UCS Manager and noticed that you can configure ports FI as ways for storage material. Is it limited to a certain protocol storage or the seller? We use Dell EQ and plan to be there to connect the EQ 6510 X. I was wondering if that is supported and if iSCSI upstream traffic would be able to access the storage?

    The 6248UPs will be passed to a pair of Catalyst 4506-E race vs. We have an IBM chassis and servers should be able to access the EQ6510X too. I guess I just need master iSCSI VLANS for the 6248UP and the servers would have access?

    Thank you!

    Hi Cowetac,

    Yes, not all storage arrays are supported by UCS, but your DELL Equalogic is supported. If you have any questions about the other compatibility of storage arrays, you can take a look at the UCS (see link below) storage interoperability matrix.

    UCS storage interoperability Matrix (matrix of the storage of UCS - B of table 10-2)

    http://www.Cisco.com/en/us/docs/switches/Datacenter/MDS9000/interoperability/matrix/Matrix8.html

    I guess I just need master iSCSI VLANS for the 6248UP and the servers would have access?

    Depends, if you use one port of the device the UCS for you connect directly to storage, you can use a single vlan.

    If you are connected via the Ethernet uplinks via a switch, you need to set your switches as a trunk port.

  • SRM for vSphere 4.0 and NetApp

    Someone there SRM implemented in a NetApp environment ESX 4.0?

    If so, how it works?

    Here are some documents that might be useful for installing vSphere 4 and SRM with NetApp:

    NetApp vSphere SRM recommended

    http://www.NetApp.com/us/communities/tech-onTap/SRM-0708.html

    http://blog.scottlowe.org/2008/12/11/3183-VMware-SRM-on-NetApp-storage/

    =========================================================================

    William Lam

    VMware vExpert 2009

    Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

    repository scripts vGhetto

    VMware Code Central - Scripts/code samples for developers and administrators

    150 VMware developer

    Introduction to the vMA (tips/tricks)

    Getting started with vSphere SDK for Perl

    Twitter: @lamw

    If you find this information useful, please give points to "correct" or "useful".

  • Permanent and continuous storage for family photos large and video solution

    I have been using external hard drives to save years of athletics competitions for my children, for posterity and my team amateur video (iMovie project) at the end of the season.  However, I need a failsafe, courses and the permanent storage for my thousands of photos and 300 GB of digital video clips (and more).  If I continue to use external drives, I still have readers risk bad over time.  What are my options, please?

    Keep several copies on separate drives offsite. There is no solution "fail safe." You can mitigate or reduce the impact knowing that drives die, buildings burn, data gets corrupted/stolen or lost. Knowing that on the records of time bad go migrate your data to new disks on a rotation schedule.

  • UCS and storage network

    I am using iSCSI with the software iSCSI adapter in ESXi as well as of the UCS and use binding to ports to bind each vmkernel iSCSI port to a specific vmnic and I use 2 vmnic.  Must I also within the UCS links each vmnic so that vmnic1 traffic to cross a 1 interconnection fabric and the movement of vmnic2 fabric crossbar Interconnect 2?

    Must I also within the UCS links each vmnic so that vmnic1 traffic to cross a 1 interconnection fabric and the movement of vmnic2 fabric crossbar Interconnect 2?

    A vEth can only come out in a unique fabric of interconnection - it's decided when you take the fabric (A or B) for the vNIC. There is no additional connection to perform.

  • VM ESXi and Cisco's UCS and EMC without a question of a novice

    I'm confused about the places where to install ESXi 5.0. This is on a windows Server or UCS blades if you have blades of the UCS and EMC San

    I know that we must install vcenter, a first round upward on the Cisco UCS blades. Do I connect EMC San?

    How to set these at all? I need a tutorial step by step for these 3 types of equipment to set up.

    Thank you!

    You can install any OS on blades, it's simple as console for all blades connected with the network and storage, it requires knowledge networking and storage configuration Cisco blades. Each blade has a remote as ILO or DRAC console, you can mount ISO image and start to install the OS, according to the needs we can configure boot from the local disk or boot from SAN, engineer of the UCS who has enough knowledge will create profiles of service for a whole different requirement for Windows Server and Citrix Xen server or ESXi servers , each requirement will be have the profile, just add blades and card service profile to access the console Blade Server, please download UCS virtual device and confiure and start learning.

  • The NetApp storage HP data migration

    I have LUNS presented to ESX clusters of HP storage.  We recently bought of NetApp storage and want to migrate data from the HP storage with NetApp storage.

    Is it possible to present two different storage vendors on the same ESX Server LUNS?  You can use storage vmotion to migrate virtual machines to a data on HP store to another store of data on the NetApp

    Yes you can present of LUN two fdifferent manufacturers and then use storage vmotion to move VMs data - it was one of the main reasons for svMotion was created.

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • Another issue for people using Netapp with VMWare via NFS

    Could you please attach to this message your logfile vmkernel since the last 2 weeks? Just remove all the names server for him.

    I need to compare with my journal if it is somehow 'common' to VMware and netapp

    That's what I see in my logs:

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.338 cpu4:1028) NFSLock: 516: stop to access the 0xc21db80 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.338 cpu4:1028) NFSLock: 516: stop to access the 0xc21a310 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.338 cpu4:1028) NFSLock: 516: stop to access the 0xc21e798 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.338 cpu4:1028) NFSLock: 516: stop to access the 0xc219448 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.338 cpu4:1028) NFSLock: 516: stop to access the 0xc219f08 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21d4c8 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21bdf0 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21d0c0 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21c4a8 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21ecf8 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21df88 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21dcd8 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21f3b0 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21d370 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc219040 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc219db0 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc218d90 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc218ee8 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21bb40 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21a468 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc2196f8 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc219b00 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21d778 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21e0e0 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21e390 fd 4

    August 25 at 04:03:42 dv29-011 vmkernel: 33:13:05:52.339 cpu4:1028) NFSLock: 516: stop to access the 0xc21e4e8 fd 4

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.004 cpu2:1026) NFSLock: 478: start Access again to fd 0xc219040

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.004 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21e390

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.004 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21e4e8

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.008 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21bb40

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.008 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21d370

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.009 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21e0e0

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.009 cpu2:1026) NFSLock: 478: start Access again to fd 0xc219b00

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.011 cpu2:1026) NFSLock: 478: start Access again to fd 0xc218ee8

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.015 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21f3b0

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.015 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21d778

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.015 cpu2:1026) NFSLock: 478: start Access again to fd 0xc2196f8

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.017 cpu2:1026) NFSLock: 478: start Access again to fd 0xc218d90

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.017 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21dcd8

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.017 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21a468

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.021 cpu2:1026) NFSLock: 478: start Access again to fd 0xc219db0

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.022 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21df88

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.024 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21bdf0

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.024 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21ecf8

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.025 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21d4c8

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.026 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21c4a8

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.027 cpu2:1026) NFSLock: 478: start Access again to fd 0xc219f08

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.028 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21d0c0

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.029 cpu2:1026) NFSLock: 478: start Access again to fd 0xc219448

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.030 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21e798

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.034 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21a310

    August 25 at 04:03:58 dv29-011 vmkernel: 33:13:06:09.036 cpu2:1026) NFSLock: 478: start Access again to fd 0xc21db80

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc219040 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc219db0 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc218d90 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc218ee8 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21bb40 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21a468 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc2196f8 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc219b00 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21d778 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21e0e0 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21e390 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21e4e8 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21db80 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21a310 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21e798 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc219448 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc219f08 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.052 cpu1:1025) NFSLock: 516: stop to access the 0xc21d4c8 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21bdf0 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21d0c0 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21c4a8 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21ecf8 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21df88 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21dcd8 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21f3b0 fd 4

    August 26 at 04:04:07 dv29-011 vmkernel: 34:13:06:15.053 cpu1:1025) NFSLock: 516: stop to access the 0xc21d370 fd 4

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.641 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21e390

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.642 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21e4e8

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.667 cpu2:1080) NFSLock: 478: start Access again to fd 0xc219b00

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.668 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21e0e0

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.670 cpu2:1080) NFSLock: 478: start Access again to fd 0xc2196f8

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.672 cpu2:1182) NFSLock: 478: start Access again to fd 0xc21d778

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.672 cpu2:1182) NFSLock: 478: start Access again to fd 0xc21a468

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.705 cpu2:1182) NFSLock: 478: start Access again to fd 0xc21bb40

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.706 cpu2:1182) NFSLock: 478: start Access again to fd 0xc218ee8

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.706 cpu2:1182) NFSLock: 478: start Access again to fd 0xc218d90

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.712 cpu2:1080) NFSLock: 478: start Access again to fd 0xc219db0

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.713 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21bdf0

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.713 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21d4c8

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.714 cpu2:1182) NFSLock: 478: start Access again to fd 0xc219f08

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.714 cpu2:1182) NFSLock: 478: start Access again to fd 0xc219448

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.718 cpu2:1080) NFSLock: 478: start Access again to fd 0xc219040

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.718 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21d370

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.718 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21f3b0

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.719 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21dcd8

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.719 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21df88

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.720 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21ecf8

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.720 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21c4a8

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.720 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21d0c0

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.721 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21e798

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.721 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21a310

    August 26 04:05:52 dv29-011 vmkernel: 34:13:07:59.721 cpu2:1080) NFSLock: 478: start Access again to fd 0xc21db80

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21a468 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc2196f8 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc219b00 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21d778 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21e0e0 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21e390 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21e4e8 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21db80 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21a310 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21e798 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc219448 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc219f08 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21d4c8 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21bdf0 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21d0c0 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21c4a8 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21ecf8 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21df88 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21dcd8 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21f3b0 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21d370 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc219040 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc219db0 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc218d90 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc218ee8 fd 4

    August 27 at 04:03:51 011 dv29 vmkernel: 35:13:05:56.744 cpu5:1029) NFSLock: 516: stop to access the 0xc21bb40 fd 4

    August 27 at 04:04:26 dv29-011 vmkernel: 35:13:06:31.629 cpu3:1027) NFSLock: 478: start Access again to fd 0xc21bb40

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc218ee8

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc218d90

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc219db0

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc219040

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21d370

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21f3b0

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21dcd8

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21df88

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21ecf8

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21c4a8

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21d0c0

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21bdf0

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.157 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21d4c8

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc219f08

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc219448

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21e798

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21a310

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21db80

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21e4e8

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21e390

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21e0e0

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21d778

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc219b00

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc2196f8

    August 27 at 04:04:27 dv29-011 vmkernel: 35:13:06:32.158 cpu3:1156) NFSLock: 478: start Access again to fd 0xc21a468

    Until last week we saw an error IOCStatus on a linux host. It wasn't the typical time. This is compared to 10-15 (out of 60) hosts linux every Sunday morning and a few variables at other times of load during the week. However, nothing broke down. We went 2 Sundays now since the upgrade of the code and have only seen 1 error w/o accidents. I'm happy with that for now. I'd really like to know what the cause of this well is first. Our storage Administrator said that he has nothing of nfs in the upgrade of the code. Class DOTF, that I went noted a change in the process of kahuna of 7.3 who had to help load. Not sure if it is or not.

  • Exchange 2007 and NetApp FC

    Here's the skinny:

    1200 + users. approx. 600 GB data messaging; 1 CASE/HTX server & 1 Server MBX under EXC 2007 Enterprise 64-bit, server 08.  We have a lot of equipment and storage for the design.  I have questions on is the configfor of the vm to the server of the mailbox.  I had intended to give the vm vHDD 2.  1 vmfs containing BONES and such and the 2nd vHDD would be a RDM to FC SAN volume.

    All thoughts, recommendations would be greatly appreciated.

    I would create readers separate newspapers and mailboxes, databases between 500 GB and more boxes to the letters and 100 GB for logs and each environment varies so plan accordingly.  Did you check NetApp & Exchange 2007 on VMware best practices for different scenarios and designs.  Here's a quick look at http://www-download.netapp.com/edm/TT/docs/NetApp_VMware_Exchange_TR.pdf I'm assuming you use CCR so plan carefully for optimal performance and layoffs.

    If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

    Kind regards

    Stefan Nguyen

    VMware vExpert 2009

    iGeek Systems Inc.

    VMware, Citrix, Microsoft Consultant

  • Can I have more than one player iCloud folder in my finder? One account for work and one for personal use.

    I want to synchronize my work to my home mac mac but don't want my work and personal files of mixture in the same iCloud drive. I want to be able to simply select the folder in the finder and access my files to work with my staff connected to iCloud services. I have 2 sets of devices. A working iPhone and a personal iPhone. My work requires that I have strictly for work purposes only to get rid of my phone personal is not an option. Is there a way to have the disc records hard icloud of two different accounts on the same mac under the same profile?

    ICloud there than one disc for each Apple ID. You can, however, create more than an Apple ID, but that creates other issues as demanding that you trade ins iCloud to access the content of the newspaper reader.

    You can create subfolders in your drive to iCloud for work and personal use. You can also purchase a subscription to more storage if you need.

    No solution to this question. Each has its compromise.

    Could you use, say, iCloud for your personal files, but use Dropbox for those work-related?

  • should I get the 32 gig and increase storage icloud or get the 128 gig?

    Should I get the 32 gig and increase storage icloud or get the 128 gig?

    iCloud can't complete really the iPads of storage on board. You can't have apps to run from iCloud, you can't the films played to iCloud, etc...

    If you plan to use more than the 32GBs go for bigger sizes.

  • Configuration of the BIOS XW8600 for SSD and HDD

    Until recently, my xw8600 has been configured with the emulation of SATA under storage on the separate IDE controller Options.  250 GB hard drives connected to the SATA 1 and SATA ports 0 and readers of DVD RW Drive connected to 2 SATA and SATA 3 ports.

    I wanted to install a GTX240 Neutron Corsair SSD, but discovered when I changed the SATA RAID + DCIS emulation (to activate all 5 ports of SATA controller and optimize the performance of the SSD), the system could not find the boot drive.  I checked the startup command settings and found the slot drive HARD listed title module of memory into the attached USB printer HP Officejet 7500 a first and could not be changed.

    I decided to go back to SATA IDE emulation separate, remove the optical drive on SATA 2 port and attach the SSD it.  This facility is expected to start successfully; but after installing windows 7 x 64 on the SSD (Windows XP, x 64, still on the HARD drive), I found Windows 7 has been very very slow.

    Can anyone offer any suggestions or comments on how I can improve this situation?

    Thanks for any help, you can suggest.

    What is an installation of Windows 7 Pro 64 - bit of a retail installation DVD purchase, or something HP?  If I remember well Vista 64 was the latest HP OS with sold.  In this case you won't have to deal with a set of HP restore disks.  I would never do an "upgrade" of a prior installation of OS in W7.  I only do not clean install W7 on a freshly long-type reformatted hard drive or an SSD.  I buy my "system builder" OEM license W7Pro 64 - bit DVD/COA from newegg.com (you can find that many sources and approximately 140.00 each).

    Plan to do a clean install on this SSD from scratch and when you format before that settle does long formatting version, while it is booted from the W7 DVD.  That will take some time.  Or, if you have a functioning before the OS install on a hard drive, you can restore the xw8600 you can connect the SSD in the second or third SATA port and reformat (long version) management of records like this.

    The boot drive or SSD, Spinner, must always be connected to the primary SATA port, which in these workstations, is usually blue plastic, while the rest are a dark black.

    Make sure that your BIOS is later... There was a version for this and the xw6600 with a few months ago.  It is an important.

    Put the SSD in your favorite mount, hang it in the main SATA port, prepare the W7 DVD in the DVD drive (which should be attached to the second port SATA or IDE cable if it's a DVD ATA drive). Throwing xw8600, go straight into the BIOS and go to which you can change the SATA emulation.  Change that on "RAID + AHCI.  Save on the way out of the BIOS, and the workstation will now reboot usually requiring formal approval of the change F1.

    Demarrer start on the DVD, select clean install and things will be fine.  I usually set my boot order to start hard drive/SSD first and second optical drive.  Then, when I load an OS I just use the F9 key during the early start to switch to the DVD player for this single event.

    It's the key information: If you have correctly set to "RAID + AHCI" SATA emulation for the W7 installation process, then the appropriate drivers will not be loaded from the DVD on the startup disk, and you won't receive anywhere near your expected speed.  I helped a friend who had done exactly what you did, and when we corrected things literally double SSD performance scores.  I recommend that the reformatting/clean reinstall from zero here, because you want to really perfect the basics and the way he was treated initially can leave you with a few important questions.

    After you have things working with the SSD and the DVD player you can add in your other material sequentially.  I would like to make a reboot between each addition, just be very careful.  Some old HP DVD drives have a problem with W764 loading during the emulation of the SATA BIOS is set correctly and there is a solution for this, but you don't want from now this info.

    All the advice I have written in this forum about the xw6400 installs apply to the xw6600 and xw8600, including information on the upgrades of the processor.

    Let us know how things are, so that others can enjoy...

  • Satellite P200-1DY: need XP drivers - LAN, SM bus and mass storage controller

    I have a Satellite P200-1DY running XP - SP2. Where can I find the drivers for Ethernet, storage of buses and the mass of SM controller controller?

    Are they 'hidden' in one of the drivers in one of the driver for XP Toshiba site list?

    How can I identify what version of laptop I have: PSPB0, B3, B6, etc. ?

    Oh. I have already answered in the other thread you posted here in the forum;
    http://forums.computers.Toshiba-Europe.com/forums/message.jspa?MessageID=117816#117816

    Seems you've discovered what series it is ;)

    PS: the SM bus and mass storage controller are communities which are only compatible Vista and so drivers don't exist for the XP operating system

Maybe you are looking for