Brocade SAN switch training

Anyone else facing issues with Adobe?We have about 25 users that work on graphics in our company, they use:
- Illustrator
- Photoshop
- InDesign, etc...Since Adobe (auto)-updated their software from 2014 to 2015 edition, all of our users are complaining about stability issues, software crashes, very very slow programs...I've called Adobe support numerous times in the past couple of days and they keep blaming everything except for their own software.First call: "It's the hardware sir!"
Sure...: i7-4770, 16GB DDR3, 256GB SSD, NVidia Quadro 1GB, built this year, specifically for our editors.2nd call: It's the drivers sir...
Checked, everything is up to date3rd call: It's the user accounts... they're all corrupt...Yesterday: User reports there's a Illustrator update... let's try that...
Check the whats new section: "Stability fixes, performance...

Storage Replica versus Robocopy: Fight!I've used Robocopy for so many years, that this blog post really caught my eye. Surely, Robocopy could not be beaten doing file copies? oh dear, it looks as though we have a new Sherriff in town.This copy tests both systemsunder various workloads:[originally postedby Ned Pyle]Hi folks, Ned here again. While we designed Storage Replica in Windows Server 2016 for synchronous, zero data-loss protection, it also offers a tantalizing option: extreme data mover. Today I compare Storage Replica’s performance with Robocopy and demonstrate using SR for more than just disaster planning peace of mind.Oh, and you may accidentally learn about Perfmon data collector sets.In this cornerRobocopy has been around for decades and is certainly the most advanced file copy utility shipped in Windows. Unlike the...

Similar Messages

Windows 2012 Hyper-V Virtual SAN Switch Best Practice

I have a four node cluster running W2012 Datacenter edition on each. All systems have Emulex HBA compatible with Hyper-V and Virtual SAN technology. The hosts are connected to a Brocade SAN Switch with NPIV Enabled. I've
created a Virtual SAN on each host. The vSAN is connected to 2 physical HBA. Each HBA is connected to a different physical SAN Switch.
I have some questions about the best practice of the whole system.
1. Do I have to create a vSAN per physical HBA ? Or create one vSAN that include 2 HBA ?
2. Add 2 virtual HBA per VM to have fault tolerance ? Or one virtual HBA that is connected to a vSAN with 2 HBAs ?
3. Do I have to create a virtual port for each VM on the HBA Gui (OCManager) ?
Any best pratice or advice ?
Thanks

Hi,
first you will do almost the same as you do on a physical SAN, normally you build 2 Fabrics right ?
In Case you have that in place you will configure also 2 vSANs to build up your 2 seperate ways/pathes.
Here my top links for that Topic
Hyper-V Virtual Fibre Channel Design Guide
http://blogs.technet.com/b/privatecloud/archive/2013/07/23/hyper-v-virtual-fibre-channel-design-guide.aspx
Very Good Blog with all the Scenarios you can have, sinlge Fabric to Multi ......
Here the TechNet Info around "Hyper-V Virtual Fibre Channel Overview"
http://technet.microsoft.com/en-us/library/hh831413.aspx
and the "Implement Hyper-V Virtual Fibre Channel"
http://technet.microsoft.com/en-us/library/dn551169.aspx
A good Advice is also to install this Hotfix -
http://support.microsoft.com/kb/2894032/en-us
It is a sexy feature but if one point in the chain is doing wrong things with your NPIV Packets you are lost, so in my personal view you miss the for me most inportant point why i do Hyper-V, the Separation of HW and Software :-)
One Problem i had once was after live Migration of a VM with configured vFC the Destination Host lost there FC Connection, but only if the Host have been one SAN Hop away from the HP Storage , was a HP Driver Problem, used the original Qlogic Driver and
everything was fine, so same as with some HP Networking Driver for Broadcom, do not trust every update, test it before puting it in production.
Hope that helps ?
Udo

FCIP (Brocade SAN-18R router) firewall issues

Hi all, I have a customer with a production and a disaster recovery site, they've recently added the SAN router (Brocade device) for the replication traffics, 2 SAN routers at production and 2 SAN routers at DR, well, they claimed that while they tested back-to-back it is successful, but if traverse through the MetroEthernet link, the SAN routers at both sites is not talking to each others...here's the connection looks like:
i. SAN Production -> Cisco 6509 -> FWSM -> Metro-Ethernet -> Cisco 6509 -> Checkpoint FW -> SW -> SAN DR
I've make sure that the FWSM and Checkpoint FW does not affect the traffic by permitting any-any traffic in both SAN routers, I've done some sniffing and found out they used a few ports including IPComp protocol...but both sites are just not communicating...
any specific area I missed out in order to make the SAN routers works properly? In the FWSM ASDM I do see that traffics is passing all right...attached here is the traffics reached to the FWSM in DR, please shade some lights in order for me to solve the issue...
Thanks

Does you brocade have Ethernet interfaces for FCIP tunnels? If not, then you can't connect Fibre Channel port on Brocade to Ethernet port on 2960g.
If it does, you can connect its ethernet port to the 2960g at the DR site, but you then still need another brocade san switch that has both fibre channel ports and ethernet ports. The FCIP tunnel will be from the brocade to the brocade switch, the 2960g is just transport of ethernet/IP packets.

Cisco Nexus 5548UP to Brocade SAN Connectivity

Hi,
I have a Server-SAN-Storage setup as shown in the attachment/below. There are new Cisco UCS rack mount servers with VIC 1225 and Virtual servers on VMware Esxi hypevisor connected to a new Cisco Nexus 5548UP switch in IP+FCoE mode. The new 5548 switch then connects to an existing production SAN of Brocade 48000 Director SAN switch which connects to storage in production environment.
I need to know the best way to connect the 5548 switch to the Brocade SAN switch without disrupting the existing Production SAN environment i.e. Brocade SAN switch configurations & setup e.g. Fabric Principal switch. priority etc.
Would configuring the 5548 switch in NPV mode be best practice?

See Figure 6-2 Converged Multi-hop FCoE Network Design Using FCoE NPV
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/fcoe/513_n1_1/ops_fcoe/ops_fcoe_npv.html
You have to use NPV on N5k, there is no FC interop support on N5k, to connect to Brocade.

No SAN Switch Logins

I have the typical setup:
2 x 6248 Interconnects
2 x Brocade SAN Switches
EMC Storage
All cross connected for redundancy. However, I am not seeing any logins to the second SAN switch when I boot a blade. I looked at all the vSAN config's etc., and it looks good and was wondering if anoyne had any other ideas?
Thanks

When you are talking SAN and say "Cross Connected" for redundancy it kind of freaks me out.
Topology should be
FIA => BrocadeA
FIB => BrocadeB
BrocadeA and BrocadeB should Never cross paths.
You would have two vHBA's per Service Profile.
Would look like this:
vHBA_A => FIA => BrocadeA
vHBA_B => FIB => BrocadeB
The nameservers on each Brocade should only see the WWPN's for the vHBA's on their fabric.
BUT to maybe answer the question you actually asked, the vHBA template will assign either fabric A or B. That is why you need two vHBA's for a dual fabric. If you want to see logins on both switches make sure you create a vHBA_A and vHBA_B set to corresponding Fabric/FI.
See Below for example.
Craig

11g plugin for Brocade VA-40FC SAN switch?

Hello,
Is anyone aware of a 11g plugin for Brocade Fibre Channel SAN switches, particularly the VA-40FC? Google only leads me to a plugin for the Brocade ServerIron appliance.
Many thanks,
R.

Cisco UCS an McData SAN Switch

Hallo zusammen,
wir versuchen eine Verbindung zwischen ESX auf einem UCS und einem NetApp Metrocluster herzustellen. SAN Infrastruktur basiert auf McData SAN Switchen.
In der Vergangenheit habe ich die komplette Infratruktur mit HP/Brocade SAN Switchen administriert ohne Probleme. Hier waren keine speziellen Einstellungen notwendig. WWN Pools und vHBA und die Verbindung stand.
Der SAN Admin meinte NPV sei auf dem Port aktiviert und NPIV wird unterstützt. Er sieht auch meine WWPNs und hat das Zoning am SAN konfiguriert. Leider sehen unsere ESX Server keine präsentierte LUN.
Für Tipps und Infos zur notwendigen Konfiguration wäre ich sehr dankbar. vSphere Umgebung läuft auf 5.5, UCS auf 2.1. Ich habe bereits alle Einstellungen unter UCS getestet. Ich habe auch ein bisschen mit den VSANs gespielt, was aber in der Vergangenheit nie notwendig war. FIs laufen im End Host Mode. ESX Rescan zeigt keine Pfade oder Target, LIP hat auch keinerlei Änderungen gebracht.
Da ich auf die SAN Konfiguration keinen Zugriff habe möchte ich zunächst sicher gehen, dass ich am UCS nichts vergessen habe. Switching Mode sollte kein Thema sein.
Viele Grüße
Bastian

From your putty Logs, I don't see any issues...
e1/17 and e1/21 are both up. I also don't see any blocked VLANs. Where's this "ENM Loop" you speak of?
Ethernet1/21 is up
Hardware: 1000/10000 Ethernet, address: 547f.eeda.6f9c (bia 547f.eeda.6f9c)
Description: U: Uplink
RE-SLCFI1-A(nxos)# sh int trunk
Port          Native Status        Port
              Vlan                  Channel
Eth1/17       500     trunking      --
Eth1/21       501     trunking      --
Port          Vlans Allowed on Trunk
Eth1/17       1,5,500,999
Eth1/21       1,501,999
Port          Vlans Err-disabled on Trunk
Eth1/17       none
Eth1/21       none
Port          STP Forwarding
Eth1/17       1,5,500,999
Eth1/21       1,501,999

Problems witch channels to the FICON SAN switches

We have some problems witch channels to the FICON SAN switches: channel 56 on Mainframe1 to switch 5B5 (FDBELF5C1_VSAN500_DISK) and channel 28 (on Mainframe1) to switch 5B7 (FDBELF5C1_VSAN510_TAPE). Forr Mainframe2 the channels are 35 to 5B5 and 37 to 5B7.
Hereby an example for switch 5B5 and channels 56 (BAD) and 43 (GOOD):
---> command: D M=DEV(5B5)
IEE174I 10.21.40 DISPLAY M 494
DEVICE 05B5 STATUS=ONLINE
CHP 56 43
ENTRY LINK ADDRESS 6543 655B
DEST LINK ADDRESS 75FE 75FE
PATH ONLINE
N YCHP PHYSICALLY ONLINE Y Y
PATH OPERATIONAL Y Y
MANAGED N N
CU NUMBER 05B5 05B5
MAXIMUM MANAGED CHPID(S) ALLOWED: 0
DESTINATION CU LOGICAL ADDRESS = 00
SCP CU ND = 0MDS9K.513.CSC.1F.00059B7ACEC4.00E0
SCP TOKEN NED = 0MDS9K.513.CSC.1F.00059B7ACEC4.0000
SCP DEVICE NED = 0MDS9K.513.CSC.1F.00059B7ACEC4.0000
When one tries to put the path online then the following error messages are seen:
---> command: VARY PATH(5B5,56),ONLINE
IEE386I PATH(05B5,56) NOT BROUGHT ONLINE
IEE763I NAME= IOSCCMSG CODE= 0000000800000032
IOS291I CONFIGURATION DATA COULD NOT BE READ ON PATH(05B5,56) RC=32
DEVICE SUPPORT CODE DETECTED INCORRECT CDR DATA
IEE763I NAME= IECVIOPM CODE= 0000000400000000
IOS554I CONFIGURATION DATA PROCESSING FAILED
IEE764I END OF IEE386I RELATED MESSAGES µ
We don't think that the problem is port related but switch related!
For the moment problems are present on only one of our 4 mainframe SAN directors. Firmware level of the directors was changed 3 weeks ago to NX-OS 4.2(7b).

Problem solved after IODF weekend.
Channels were toggled.
Rgds,
Ivy

Query: Best practice SAN switch (network) access control rules?

Dear SAN experts,
Are there generic SAN (MDS) switch access control rules that should always be applied within the SAN environment?
I have a specific interest in network-based access control rules/CLI-commands with respect to traffic flowing through the switch rather than switch management traffic (controls for traffic flowing to the switch).
Presumably one would want to provide SAN switch demarcation between initiators and targets using VSAN, Zoning (and LUN Zoning for fine grained access control and defense in depth with storage device LUN masking), IP ACL, Read-Only Zone (or LUN).
In a LAN environment controlled by a (gateway) firewall, there are (best practice) generic firewall access control rules that should be instantiated regardless of enterprise network IP range, TCP services, topology etc.
For example, the blocking of malformed TCP flags or the blocking of inbound and outbound IP ranges outlined in RFC 3330 (and RFC 1918).
These firewall access control rules can be deployed regardless of the IP range or TCP service traffic used within the enterprise. Of course there are firewall access control rules that should also be implemented as best practice that require specific IP addresses and ports that suit the network in which they are deployed. For example, rate limiting as a DoS preventative, may require knowledge of server IP and port number of the hosted service that is being DoS protected.
So my question is, are there generic best practice SAN switch (network) access control rules that should also be instantiated?
regards,
Will.

Hi William,
That's a pretty wide net you're casting there, but i'll do my best to give you some insight in the matter.
Speaking pure fibre channel, your only real way of controlling which nodes can access which other nodes is Zones.
for zones there are a few best practices:
* Default Zone: Don't use it. unless you're running Ficon.
* Single Initiator zones: One host, many storage targets. Don't put 2 initiators in one zone or they'll try logging into each other which at best will give you a performance hit, at worst will bring down your systems.
* Don't mix zoning types: You can zone on wwn, on port, and Cisco NX-OS will give you a plethora of other options, like on device alias or LUN Zoning. Don't use different types of these in one zone.
* Device alias zoning is definately recommended with Enhanced Zoning and Enhanced DA enabled, since it will make replacing hba's a heck of a lot less painful in your fabric.
* LUN zoning is being deprecated, so avoid. You can achieve the same effect on any modern array by doing lun masking.
* Read-Only exists, but again any modern array should be able to make a lun read-only.
* QoS on Zoning: Isn't really an ACL method, more of a congestion control.
VSANs are a way to separate your physical fabric into several logical fabrics. There's one huge distinction here with VLANs, that is that as a rule of thumb, you should put things that you want to talk to each other in the same VSANs. There's no such concept as a broadcast domain the way it exists in Ethernet in FC, so VSANs don't serve as isolation for that. Routing on Fibre Channel (IVR or Inter-VSAN Routing) is possible, but quickly becomes a pain if you use it a lot/structurally. Keep IVR for exceptions, use VSANs for logical units of hosts and storage that belong to each other. A good example would be to put each of 2 remote datacenters in their own VSAN, create a third VSAN for the ports on the array that provide replication between DC and use IVR to make management hosts have inband access to all arrays.
When using IVR, maintain a manual and minimal topology. IVR tends to become very complex very fast and auto topology isn't helping this.
Traditional IP acls (permit this proto to that dest on such a port and deny other combinations) are very rare on management interfaces, since they're usually connected to already separated segments. Same goes for Fibre Channel over IP links (that connect to ethernet interfaces in your storage switch).
They are quite logical to use and work just the same on an MDS as on a traditional Ethernetswitch when you want to use IP over FC (not to be confused with FC over IP). But then you'll logically use your switch as an L2/L3 device.
I'm personally not an IP guy, but here's a quite good guide to setting up IP services in a FC fabric:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/mds9000/sw/4_1/configuration/guides/cli_4_1/ipsvc.html
To protect your san from devices that are 'slow-draining' and can cause congestion, I highly recommend enabling slow-drain policy monitors, as described in this document:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/mds9000/sw/5_0/configuration/guides/int/nxos/intf.html#wp1743661
That's a very brief summary of the most important access-control-related Best Practices that come to mind. If any of this isn't clear to you or you require more detail, let me know. HTH!

Why a SAN switch can see vHBA WWPNs but not WWNN?

I have setup UCSM but the SAN switches (EMC) could only see all the WWPN on each server's vHBA, not the WWNN. They are all UCS B200M2 model. I saw the WWNNs are already assign to all service profile as shown in the storage tab.
Has anyone encountered this before? I am digging my head for more than 2 hours but no clue.
Rebooted the blades, disassociate/reassociate blades, re-ack blades, unbind/rebind vHBA templates on the server's vHBA had been done but no luck
Appreciate for any help here.
kind regards,

Simon is correct. In UCSM is where you would only see the WWNN under the storage tab. You are only zoning the WWPN. If I may ask, what reason would you need to see the WWNN if the paths to the HBA is being seen?
Just curious?
Sent from Cisco Technical Support iPhone App

Configuring Nexus 5k for SAN switching between UCS 6100s and NetApp storage

We are trying to get our UCS environment setup to do SAN boot to LUNs on our NetApp storage. We have a pair of Nexus 5Ks with the Enterprise / SAN license on them and the 6-port FC module installed. What needs to be done to configure the Nexus 5000 to operate as the SAN switch between the storage target and the UCS environment?

I'm still not seeing the LUN on the NetApp device from my service profile. Here are the outputs from the two
commands you referenced here along with a few other commands if they help at all.
Port fc2/1 is the conneciton to the UCS 6100 with FCID 0x640004 being the vHBA in my Server profile.
Port fc2/5 is the NetApp target. I have the LUN masked to the vHBA port name 20:00:00:25:b5:01:00:ff
I have just the wwpn from the vHBA in my server profile and the wwpn of the NetApp target port zoned together. I'm not seeing any FC traffic at the NetApp though from looking at the statistics. Do I need to include something else in my zoning?
Again, any assistance would be appreciated. This is obviously our first venture into FC...

UCS servers with IBM's TotalStorage SAN16B-2 SAN Switch

Hi Experts,
We have IBM TotalStorage SAN16B-2 SAN Switch, & cisco UCS 6120 Fabric Interconnect, dint find any document for compatibilty between this.
This is a SAN switch with each port capable of delivering a throughput of up to 4 gbps.
Can we use this SAN switch to connect ucs Fabric interconnect????
Thanks,
Mazhar

As long as the switch supports NPIV it should be fine.
Regards,
Robert

SAN Switch Cisco -16Port

Hi,
Any suggestions for SAN Switch 16 Port ( All Active) from MDS series.
Thanks in advance!!

DCNM-SAN-M91-K9 - very nice to have if you want to track switch utilization, manage multiple fabrics at the same time. Not a must have ..but a nice to have.
M9148PL8-8G-SFP - i believe you must purchase this to activate an extra 8 ports to give you a total of 16 ports.
M9100ENT1K9 - if you have requirements for advances features like IVR then you would need this. If you just need to create zones, VSANs ..you don't need that license.
@dynamoxxx

Nexus 5548UP for SAN Switch

We have purchased a Nexus 5548UP switch for our SAN environment. I've only configured it for jumbo frames and currently doing testing on the performance, as some say use jumbo frames while others say do not. My question is, and I know this is a loaded question but how do you guys go about configuring your SAN switches? What exactly are you configuring on it? Such as for performance tuning or the like. The reason I ask, is we have the switch and it's pretty much working, but I'd like to learn more about it and how to tune it and fully take advantage of the switch.

That is correct, between two Dell Optiplex workstations. We also tested between the server that will go into prod and an Optiplex, but once again the Optiplex could be the limiting factor. You think that could be it? Here's my config, so you know how it's setup right now.
version 5.2(1)N1(7)
hostname N5K
feature telnet
feature lldp
feature vtp
username admin password 5 $1$oZ1234567898765432123456/ role network-admin
banner motd #Nexus 5000 Switch
ip domain-lookup
policy-map type network-qos jumbo
class type network-qos class-default
mtu 9216
multicast-optimize
system qos
service-policy type network-qos jumbo
snmp-server user admin network-admin auth md5 0x422842c9d320064123456789fc703d20
priv d3264f23456789000c703d20 localizedkey
vrf context management
port-profile default max-ports 512
interface Ethernet1/1
flowcontrol receive on
flowcontrol send on
interface Ethernet1/2
interface Ethernet1/3
interface Ethernet1/4
interface Ethernet1/5
flowcontrol receive on
flowcontrol send on
interface Ethernet1/6
interface Ethernet1/7
interface Ethernet1/8
interface Ethernet1/9
flowcontrol receive on
flowcontrol send on
interface Ethernet1/10
interface Ethernet1/11
interface Ethernet1/12
interface Ethernet1/13
flowcontrol receive on
flowcontrol send on
interface Ethernet1/14
interface Ethernet1/15
interface Ethernet1/16
interface Ethernet1/17
interface Ethernet1/18
interface Ethernet1/19
interface Ethernet1/20
interface Ethernet1/21
interface Ethernet1/22
interface Ethernet1/23
interface Ethernet1/24
interface Ethernet1/25
interface Ethernet1/26
interface Ethernet1/27
interface Ethernet1/28
interface Ethernet1/29
interface Ethernet1/30
interface Ethernet1/31
interface Ethernet1/32
interface mgmt0
ip address 11.11.11.11/24
line console
exec-timeout 720
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.2.1.N1.7.bin
boot system bootflash:/n5000-uk9.5.2.1.N1.7.bin

JBOD 9-pin connector to SAN switch

I'm a newbie to SAN.
There are JBODs with 9-pin D-type connector. my SAN switch has fibre SFP connector. Is there a cable to connect them?

Yes. There is something called a MIA, Media Interface adapter, and it will convert copper to Fibre. Usually you plug the MIA into the back on the JBOD and attach the fibre to the MIA and the switch. Often times MIA require SC type fibre connections where as the MDS used LC type connects, just make sure you get a fibre cable that is SC on one end and LC on the other. These cables are common since most patch panels use the SC interface.

Brocade SAN switch training

Similar Messages

Maybe you are looking for