2 SAN FABRIC 20Km

Hi Experts
I want to connect two san fabric switch away from each other 20KM using a dedicated fiber in order to replicate san traffic , question is what transceiver on san fabric should i use to terminate the fiber cable coming from the MUX ,is SM or MM or must be an FC Transceiver?
thanks
Ibrahim

If you are being provided the fiber channel link via a MUX owned by a third-party service provider, then you need to ask them what transceiver type (short reach or long reach) and the fiber type necessary to connect to their equipment. I would hope it would be a short reach, multimode transceiver for low cost. But, it will depend upon the MUX.
The following Cisco document outlines the available optical transceivers and the MDS equipment it is compatible with.
http://www.cisco.com/en/US/prod/collateral/ps4159/ps6409/ps4358/product_data_sheet09186a00801bc698.html

Similar Messages

How to remove SAN switches from Cisco Fabric

I have 2 SAN Fabrics, each with 2x MDS9513 and a few Cisco Blade Center Switches, DS-IBM-FC-K9. I need to decommission some of the blade switches. I need a procedure how to do it step by step. When do I disconnect the ISL's, when do I delete the VSAN's from the blade switches etc. Do not want to delete the VSAN on all switches.

Once the hosts ( blades ) are no longer being used in the Blade Centers, shut the ports in the ISLs on the 9513 switches. Removing a switch from the fabric does not delete VSANs. If you have zones or VSANs that are no longer used, then you might want to clean those up afterward.

DCNM-SAN: No fabrics found

Hi,
I have the following problem concerning DCNM-SAN.
I recently upgraded to DCNM 5.2.2c.
We came from a lower DCNM version, where Fabric Manager was not already included in the DCNM package.
I've uninstalled Fabric Manager as it was recommended by an upgrade manual from Cisco.
After some time, it was possible to install DCNM 5.2.2c.
The DCNM-LAN is working, but the DCNM-SAN isn't.
Unfortunately, I'm unable to access our SAN fabrics.
Our environment exists of Cisco MDS switches and a one server where DCNM-LAN and DCNM-SAN are installed.
When we open the DCNM-SAN client and try to login, I can login but I get an "There are no fabrics available for <username>@Radius" error.
With some investigation, I found out that we needed to have the "network-admin" role in ACS 4.2.
We have already had that role configured, so that couldn't be the case.
I also checked if the DCNM-SAN service was running, and it is.
Can somebody please help me out as we are not able to access the fabrics.
With kind regards,
Bart Mars

http://www.cisco.com/en/US/customer/docs/switches/datacenter/sw/5_x/dcnm/release/notes/dcnm_5_2_relnotes.html#wp61633
Supported as of 5.2 per the release notes above. And both can coexist in the same VM.
This is the validation from the release note:
The Cisco DCNM server can run within a virtual machine, and requires one of the supported Windows or Linux operating systems listed in this section.
Specifics for the host OS can be found in the release notes.
Hope that helps,
Cary Cube'
CSE, CISCO

Fabric Manager - do I need to install server component?

Hi,
I would like to know if I need to install the server component of Fabric Manager, or if I can just use the client component to manage the switches directly.
I have 2 MDS 9120 switches which will be run as 2 separate fabrics. They will be used in a non-production environment and I will need to configure VSAN and zoning using pWWN. If I do need to install the server part, what is the benefit of using the licenced version over the unlicenced?
Thanks, Darren.

Darren,
The choice to install and licence the server component would be to manage your entire SAN fabric as a holistic centralized topology versus using the client which pretty much only allows you to view the fabrics individually within Fabric Manager.
For a small non-production environment like yours you will be fine, but if you find yourself in a situation where your fabric is becoming a larger Production enironment then I would recommend moving to the licenced server version.
regards
Alan

Latest round of patches on fabric booted system causes Solaris 10 to hang

I have a fairly stock install of Solaris 10 6/06 on a T2000 which uses a Emulex HBA to boot from Xiotech SAN attached disks.
I installed the following patches:
118712 14 < 16 R-- 24 SunOS 5.10: Sun XVR-100 Graphics Accelerator Patch
120050 05 < 06 RS- 28 SunOS 5.10: usermod patch
120222 16 < 17 R-- 19 SunOS 5.10: Emulex-Sun LightPulse Fibre Channel Adapter driver
120629 02 < 08 R-- 24 SunOS 5.10: libpool patch
120824 08 < 09 R-- 39 SunOS 5.10: SunBlade T6300 & Sun Fire (T1000, T2000) platform patc
121118 11 < 12 R-- 21 SunOS 5.10: Sun Update Connection System Client 1.0.9
122660 08 < 09 R-- 17 SunOS 5.10: zones patch
124258 03 < 05 RS- 19 SunOS 5.10: ufs and nfs driver patch
124327 -- < 04 R-- 34 SunOS 5.10: libpcp patch
120222 16 < 17 R-- 19 SunOS 5.10: Emulex-Sun LightPulse Fibre Channel Adapter driver
When I rebooted the system it will no longer boot up.
If I do a {ok} boot -m milestone=none and attempt to start all the services by hand, I see:
svc:/platform/sun4u/mpxio-upgrade:default (Multipath upgrade)
State: offline since June 4, 2007 4:05:58 PM CDT
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: man -M /usr/share/man -s 1M stmsboot
See: /etc/svc/volatile/platform-sun4u-mpxio-upgrade:default.log
It appears the mpxio-upgrade script is failing to start.
If I run /lib/svc/method/mpxio-upgrade by hand the script hangs and can not be killed. Since I am on console the only want to recover is to send-brk and reboot. I truss'ed it and the last device it was trying to read is:
82: open("/devices/pseudo/devinfo@0:devinfo", O_RDONLY) = 5
82: ioctl(5, 0xDF82, 0x00000000) = 57311
This is the second time this has happened in the last 2 months. The first time the problem was resolved with a new kernel patch. However Sun could not tell me what the exact problem was.
Has anyone else run into SAN/Fabric booted servers failing to boot after various patches?

We have discovered the problem. It has nothing to do with SAN booting at all. It has to do with having a device plugged into the serial port. I was using this system to act as serial console for another device in the same rack. When the Sun kernel engineering asked me to unplug the serial cable and reboot I was skeptical, but it worked.
Sun has filed this as a bug. The only work around right now is to make sure you have nothing plugged into the serial port.

Ask the Expert: Cisco UCS Troubleshooting Boot from SAN with FC and iSCSI

Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco UCS Troubleshooting Boot from SAN with FC and iSCSI with Vishal Mehta and Manuel Velasco.
The current industry trend is to use SAN (FC/FCoE/iSCSI) for booting operating systems instead of using local storage.
Boot from SAN offers many benefits, including:
Server without local storage can run cooler and use the extra space for other components.
Redeployment of servers caused by hardware failures becomes easier with boot from SAN servers.
SAN storage allows the administrator to use storage more efficiently.
Boot from SAN offers reliability because the user can access the boot disk through multiple paths, which protects the disk from being a single point of failure.
Cisco UCS takes away much of the complexity with its service profiles and associated boot policies to make boot from SAN deployment an easy task.
Vishal Mehta is a customer support engineer for Cisco’s Data Center Server Virtualization TAC team based in San Jose, California. He has been working in the TAC for the past three years with a primary focus on data center technologies such as Cisco Nexus 5000, Cisco UCS, Cisco Nexus 1000v, and virtualization. He has presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE certification (number 37139) in routing and switching and service provider.
Manuel Velasco is a customer support engineer for Cisco’s Data Center Server Virtualization TAC team based in San Jose, California. He has been working in the TAC for the past three years with a primary focus on data center technologies such as Cisco UCS, Cisco Nexus 1000v, and virtualization. Manuel holds a master’s degree in electrical engineering from California Polytechnic State University (Cal Poly) and VMware VCP and CCNA certifications.
Remember to use the rating system to let Vishal and Manuel know if you have received an adequate response.
Because of the volume expected during this event, our experts might not be able to answer every question. Remember that you can continue the conversation in the Data Center community, under subcommunity Unified Computing, shortly after the event. This event lasts through April 25, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Evan
Thank you for asking this question. Most common TAC cases that we have seen on Boot-from-SAN failures are due to misconfiguration.
So our methodology is to verify configuration and troubleshoot from server to storage switches to storage array.
Before diving into troubleshooting, make sure there is clear understanding of this topology. This is very vital with any troubleshooting scenario. Know what devices you have and how they are connected, how many paths are connected, Switch/NPV mode and so on.
Always try to troubleshoot one path at a time and verify that the setup is in complaint with the SW/HW interop matrix tested by Cisco.
Step 1: Check at server
a. make sure to have uniform firmware version across all components of UCS
b. Verify if VSAN is created and FC uplinks are configured correctly. VSANs/FCoE-vlan should be unique per fabric
c. Verify at service profile level for configuration of vHBAs - vHBA per Fabric should have unique VSAN number
Note down the WWPN of your vhba. This will be needed in step 2 for zoning on the SAN switch and step 3 for LUN masking on the storage array.
d. verify if Boot Policy of the service profile is configured to Boot From SAN - the Boot Order and its parameters such as Lun ID and WWN are extremely important
e. finally at UCS CLI - verify the flogi of vHBAs (for NPV mode, command is (from nxos) – show npv flogi-table)
Step 2: Check at Storage Switch
a. Verify the mode (by default UCS is in FC end-host mode, so storage switch has to be in NPIV mode; unless UCS is in FC Switch mode)
b. Verify the switch port connecting to UCS is UP as an F-Port and is configured for correct VSAN
c. Check if both the initiator (Server) and the target (Storage) are logged into the fabric switch (command for MDS/N5k - show flogi database vsan X)
d. Once confirmed that initiator and target devices are logged into the fabric, query the name server to see if they have registered themselves correctly. (command - show fcns database vsan X)
e. Most important configuration to check on Storage Switch is the zoning
Zoning is basically access control for our initiator to targets. Most common design is to configure one zone per initiator and target.
Zoning will require you to configure a zone, put that zone into your current zonset, then ACTIVATE it. (command - show zoneset active vsan X)
Step 3: Check at Storage Array
When the Storage array logs into the SAN fabric, it queries the name server to see which devices it can communicate.
LUN masking is crucial step on Storage Array which gives particular host (server) access to specific LUN
Assuming that both the storage and initiator have FLOGI’d into the fabric and the zoning is correct (as per Step 1 & 2)
Following needs to be verified at Storage Array level
a. Are the wwpn of the initiators (vhba of the hosts) visible on the storage array?
b. If above is yes then Is LUN Masking applied?
c. What LUN number is presented to the host - this is the number that we see in Lun ID on the 'Boot Order' of Step 1
Below document has details and troubleshooting outputs:
http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-b-series-blade-servers/115764-ucs-san-tshoot-00.html
Hope this answers your question.
Thanks,
Vishal

NetApp and Hitachi SAN

I have a Solaris 9 server attached to a SAN fabric using two Silkworms 3850 with two emulex LP9002L-F2 cards. Presently there is a Hitachi 9500V storage presenting LUNs to the Sol9 server without any problems. We aquired two Netapp Filers 3820c that are attached to the SAN fabric. The server uses Veritas FS 4.1 and vxdmp for failover.
My question is:
Do I need separate HBA cards for each storage? one set for hitachi and one set for NetApp ? Or just the existing HBAs will do as long as the NetApp presents luns to it ?The NetApp techie says you can not access more than one storage at a time. Is either All hitachi or all SAN.
Please shed some light!.
Thanks in advanced.

There is what works.
There is what is supported.
It probably works to present the NetApp LUNs to the same HBAs that are accessing the SAN. However, if NetApp says it isn't supported .... then you need to ask them why.

Do we need to create two zones for Two HBA for a host connected with SAN ?

Hi,While creating Zone , Do we need to create two zones for Two HBA for a host connected with SAN ? Or a zone is enough for
a host which having Two HBAs...We have two 9124s for our SAN fabric...
As I found like one zone below, I little bit confused that , if a host having two HBA connected with SAN, should I expect two zones for every Host?
from the zone set, I gave the command show zoneset
zone name SQLSVR-X-NNN_CX4 vsan 1
    pwwn 50:06:NN:NN:NN:NN:NN:NN
    pwwn 50:06:NN:NN:NN:NN:NN:NN
          pwwn 10:00:NN:NN:NN:NN:NN:NN
But I found only one zone for the server's HBA2:by the same time in the fabric I found switches A & B showing the WWNs of those HBAs on its
connected N port...Its not only for this server alone, but for all hosts..Can you help me to clarify on this please..that should we need to create one zone for
one HBA?

if u have two independent fabrics between hosts and storage, i think the below confs are recommended.
Scenario 1: 2 HBAs single port each ( redundancy across HBA / Storage port )
HBA1 - port 0 ---------> Fabric A ----------> Storage port ( FAx/CLx )
HBA2 - port 0 ---------> Fabirc B ----------> Storage port ( FAy/CLy )
Scenario 2: 2 HBAs of dual port each
HBA1 - port 0 -------> Fabric A ---------> Storage port ( FAx/CLx )
HBA2 - port0 ---------> Fabric A ---------> Storage port ( FAs/CLs )
HBA1 - port 1 --------> Fabric A --------> Storage port ( FAy/CLy )
HBA2 - port 1 ---------> Fabric B --------> Storage port ( FAt/CLt )
the zone which is in your output is VSAN 1. if its a production VSAN, Cisco doesn't recomends to use VSAN 1 ( default vsan ) for production.

SAN redundant paths

Hello,
When reading ESXi Boot from SAN instructions for UCS, I came across the following sentence:
"Configure a LUN or RAID volume on your SAN, then connect to the SAN and verify that one (and only one) path exists from the SAN HBA to the LUN".
I don't understand this sentence, as the design best practices in SAN, correct me if I'm wrong, make each path from HBA to LUN split in 2 (one for each Storage Processor).
What am I missing here?
Thanks a lot,

An easy way is to disable the fc path to a vHBA path by going into the Service Profile, vHBA config and setting its VSAN to another VSAN that it is not zoned in. By default VSAN 1 is always available. But, if VSAN 1 is in use, create a new VSAN, say VSAN 42 (pick something that doesn't exist anywhere in your SAN fabric) and assign the vHBA to VSAN 42 during the installation. After the installation is complete and you are ready to configure MP, put the vHBA back into it's correctly configured VSAN.
Or, If you have access to the SAN configuration, you can remove the vHBA/StorageTarget configuration during the install. After installation, put the configuration back in place and activate it.
The single path install is a requirement of Windows Server 2003 and 2008, not UCS.
http://download.microsoft.com/download/f/9/7/f9775acc-baa6-45cc-9dec-b82983705620/Boot%20from%20SAN%20in%20Windows.doc
"Allow a single path to storage when installing the operating system (OS). For multiple HBA port configurations, only one HBA port should be connected to the SAN during installation. The same restriction applies to the storage controller ports"
For ESX and RHEL, both paths can be enabled during install. For RHEL, if you don't have both paths enabled during install, it's extra work to bring the second path in after installation.

Physical Connectivity from Fabric Interconnect to MDS and Failover please suggest

Dear Team
We have 2 FI and 2 MDS 1 SAN
Currenlty the connectivity is
2 direct physical connections from FI-A to MDS1
2 direct physical Connections from FI-B to MDS2
From MDS 1 connection to SAN Primary controller
From MDS 1 connection to SAN Secondary controller
From MDS 2 connection to SAN primary controller
From MDS 2 connection to SAN Secondary controller
Hope the above connectivty is fine?
we had looked at
http://www.cisco.com/en/US/prod/collateral/ps4159/ps6409/ps5990/white_paper_c11_586100.html (as team always preferred to go via cisco standards)
In FI we have to cluster the FI and Primary and Subordinate,likewise here for MDS to we need to? or will it be done via FIs ?
If not these 2 MDs they work independent but sharing the configs that happens among them?
Now what ever changes (Zone Creation)we make on MDS1 hope that will get relpicated to MDS2 via FIs?
If MDS1 Fails will all the configuration be available on MDS2 and still the infra will be smooth running ? and vice versa?
Any additional steps to be done to achieve it?
Which is the best way to achieve it please suggest
Thanks and Regards
Jose

Hi Jose.
Physically your connectivity is good.
On the UCS side, the 'Primary' and 'Subordinate' role refer only to the Management of the system and which device is actually running UCS Manager.
Each MDS device will have separate configuration (zoning). It's different between the 2 devices.
The blade itself will have a connection out each side, or 'SAN Fabric'.
e.g.
           +----+
       +---+    +-----+
       |   |    |     |
       |   |    |     |
       |   |SAN |     |
       | +->----<--+ |
       | |         | |
       | |         | |
   +---+-+-+    +--+--+--+
   |       |    |        |
   |MDS-A |    |MDS-B   |
   +--^-^--+    +---^-^--+
      | |           | |
   +--+-+--+    +---+-+--+
   |       |    |        |
   |UCS-A |    | UCS-B |
   +--+----+    +-----+--+
      |               |
      |               |
VSAN100    +-----+    | VSAN200
      |    |     |    |
      +---->     <----+
           |Blade|
           +-----+
The blade will have a HBA on FabricA (VSAN100) and FabricB (VSAN200)
Each HBA will have a different WWPN, and on the SAN array, each controller will have a WWPN
So on MDS-A, the zoning will be:
Blade WWPN A
Storage WWPN Primary A
Storage WWPN Secondary A
MDS-B, the zoning will be:
Blade WWPN B
Storage WWPN Primary B
Storage WWPN Secondary B
So the configuration is *not* synced between the two MDS devices, but they each have visibility to the blades vHBA device. At the blade level, the Multipathing software on the Operating System will handle any failover.
On the UCS, we would generally use a Port Channel up to the MDS.

Solaris support booting from san ?

Does anyone know if Solaris 10 supports booting from a san fabric lun ? In particular, an IBM DS4800.
The installer doesn't see the luns when it comes time to choose a disk to install on, only the internal disks.
The server is a IBM LS20 blade. I've managed to install Sol. 10 on the internal drives and can see the luns on the DS4800.
I'm using Solaris 10 Express 10/05 x86/64.
Brian.

Do you see the luns after boot? I'm wondering if there isn't a driver for your controller in the default installation environment. I would assume one could be added (that being one of the big benefits of newboot). Especially if you could create a jumpstart server. (It's easer to add a driver to it than to burn a new CD/DVD).
Darren

DCNM v7.1 fabric already exist error message

Hi my friends:
Do you konw where storage san device in dcnm because when i try to add another this show me that the same device exist,but i can found in screen,
I attached the error message.
Thank,
Best regard.
Marco

Hi Marco,
DCNM will discover the entire SAN fabric from a single discovery job. By entering the IP address of an initial seed switch, DCNM finds and adds adjacent switches. It is likely that the .34 switch was found by one of the 2 previous discovery jobs. There are two places in DCNM to determine if the switch has already been discovered.
You can find a list of all devices managed by DCNM, including SAN devices, in the Web GUI under [Inventory > Switches]. Additionally, you can launch the DCNM-SAN java client to view the fabric as well as configure the devices. To launch the SAN client, open the DCNM Web GUI and find the 'DCNM-SAN' button in the upper right corner of the screen. The SAN client accepts the same user credentials as the Web GUI. Once logged into the SAN client, select the discovered fabric and 'open' it to view all of its devices.
-Eric

SAN Boot Policy Clarification

I would like some clarification regarding the SAN Boot policy. I was always under the impression you were suppose to use the WWPN of the storage port. But what if you have many storage ports coming from the array (16 for example), this would not be possible.
Is the purpose of this policy to simply force the HBA to login into the SAN fabric?
If so, I can use one from my actual array or just make one up, correct?
Since all the zoning is being done by the SAN switch (Brocade/MDS/Nexus) and LUN masking at the array level, I would think putting the actual WWPN of a storage port is not necessary.
Thanks for any clarification.

My thought was you could just throw a valid wwpn in (any valid wwpn, doesn't have to be the array) again just to log in to the fabric. The it would scan the bus and off you go.
When I tried that with our try and buy setup and a NetApp array, doing windows 2008 r2 san boot, I could never get the luns to show up. We put in the arrays 4 wwpns and that got it to show up.
im not sure why it matters, and I think we had something else wrong. if you look at blogs online almost all of them show to just throw a wwpn in there to start flogi and that's it.
If you have 16 wwpns that could be an issue. As you probably know the boot policy only lets you put a primary and secondary for each HBA. I would try placing a random wwpn in and see if it works.

Rebooting FI causes errors on SAN

I have 2 fabrics consisting of a 6120XP in FC switching mode connected to a MDS 9124 with a 4 port port channel. There are also HP Proliant servers connected directly to the each fabric on the 9124s. Storage is a EMC Clariion NS480. All servers are running ESX 4.1u1. I want to share luns between the HP servers and the UCS blade servers in order to vmotion VMs over to the UCS servers.
When I upgraded the firmware on one of the 6120s and rebooted, the HP ESX servers temporarily lost access to the shared luns. This also happened when I added the LUNS to the storage group for one of the UCS ESX servers.
Is there a configuration issue that can cause this or am I wrong to expect that I can share LUNS between the HP and UCS servers

Have you checked the MDS logs?
Assuming your zoning is setup correctly and each host is segemented from others, the rebooting of any host or NPV device should not affect anything else in your SAN fabric.
Q. How are you zoning your UCS and non-UCS initiators? (wwpn, port etc)
Run a show tech on your MDS(s) and check the logs around the time of the interuption/upgrade and see if there are any clues.
Regards,
Robert

Fc port 47 on fabric interconnect A oper state: failed, reason: Link failure: OLS received

Hi,
this UCS is connected to a qlogics SAN Fabric. We can see the LUN in ESX 5, but can't write. If we want write something to the LUN, we get the error above. We know that the qlogic Fabric is not supported by UCS, but its NPIV and i have a similar Installation which is doing fine.
Any Ideas?
Thanks, Marco

Hello,
NOS refers to "No operatioal sequence". Fibre channel has primitive seqences which are used to establish and maintain a link among the devices.
During the initial login phase,
1.Fiber channel switch sends a NOS signal
2.HBA connected to it sends an "OLS (offline sequence) signal.
3.Switch would send a "Link reset"(LR)
4.HBA responds with a "LRR (link reset response)"
When a NOS received condition is met,
•A signal loss or sync loss condition is detected.
•The port is administratively shut down.
•The port is operationally down.
When the port status is in "link failure or not-connected" state, it means that the physical path is not completely active or no active signals has been sent. Check the cables/SFP's if pluged in properly and check the configuration (port type, speed and vsan settings) for further troubleshooting.

2 SAN FABRIC 20Km

Similar Messages

Maybe you are looking for