FCoE uplink is down on vsan

Similar Questions

• Will be older, slower, diskless / nodes consumption slow down a VSAN system?

  Hello

  We have a 6 identical VSAN contributing storage of cluster nodes.
  We have also two old machines (think generation Proliant G7), which are simply 'broad' and we thought to use these two to host performance reduced, not part of the virtual computer, which we have many offshore.

  Question: these two boxes older, which are much slower than today's material, will drag down the performance of the entire solution VSAN. 6 nodes, contributors 'feel' the presence of these aging and all devices slow down?

  There are best practices do not use a cluster asymmetric but does that refer to contribute nodes only?  I understand that the nodes 'consumers only', basically just "sitting there" but when will be the part of the Cluster vSAN, they have a negative impact? If so, why?

  The network connections will be 10 gig and identical to the 6 contributing nodes. It's just the performance of the processor that are slower.

  We will use the affinity / no affinity rules to keep those "low performance" VM on these older machines.

  Kind regards

  Steven

  Hello, this is my understanding of your configuration.  6 new nodes in a cluster of vSAN contributing storage.  2 old nodes in a cluster of vSAN contribute not storage.  I would not expect the old 2 knots to affect performance.  Just my opinion, no way for me to provide proof.  Thank you, Zach.

• Please tell me how to connect with FCoE mini-UCS and Nexus N5k (N5K-C5548UP-B-S32)

  I have UCS 5108 chassis of Server Blade (with two blades B200 M3 inside and two FI 6324) connected to the switch of Nexus N5k 4x10GE links.

  I want to set both aggregated channels FCoE (vFC) of chassi to pass.

  All the instructions I've seen mention that UCS-mini needs to be mode end-host FC, but version 3.0 UCSM does not support this mode, what should you do?

  I put in place following the www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116248-configure-fcoe-00.html instructions

  But after the installation, I get an error on the fabric: FCoE or FC uplink is down on Vsan 500;

  And the Nexus program: Vsan 500 is declining (pending flogi)

  When I ' display interface vfc 1 ' CLI nexus I don't see "Trunk VSAN (high)", but

  "VSANS trunk (boot) (500).

  Unfortunately, I can't find the technical notes for mini UCS (with UCSM v. 3.0), so maybe you can promt guides or suggestion for this?

  Thank you in advance!

  Same question here.

  TIA

• VSAN membership down on the CF mapped uplink port

  Hello

  Since I upgrade Cisco UCS Manager, all frame and fabric of interconnections of version 2.2 (1), I have a few minor flaws.

  I configure ports 31 and 32 as FC uplink ports and mapped each port to a vsan:

  Port 31 = VSAN 'blue '.

  32 port = "red" VSAN

  (I know, it is not common to map two different VSAN to the same fabric, but I have to)

  Since the update, I get minor flaws:

  31--> FCoE or FC uplink port is broken on 'red' VSAN / membership-down

  32--> FCoE or FC uplink port is broken on 'blue' VSAN / membership-down

  I have no channels of port FC or FC enabled link mode. Interconnection of fabric is EHM.

  Even in other tissues.

  Can anyone help me or is it the same cosmetic problem as stated in the quote?

  FCoE Uplink vsan membership fault for any vsan not configured upstream Symptom:
  
  Fabric Vsan Membership Down fault message on FCoE uplink ports
  Severity: Major
  Code: F1083
  Name: Fabric Vsan Membership Down
  Conditions:
  Observed with UCSM 2.1 and when FCoE uplink port is configured on the Fabric Interconnect
  Workaround:
  None.Error message is cosmetic.
  

  Thanks in advance

  / Danny

  Hello Danny,

  Yes, it is a cosmetic issue in UCSM 2.2.1

  the question is followed by

  https://Tools.Cisco.com/bugsearch/bug/ CSCum89468

  The one that you cited ( CSCud81857 ) is specific to the rising FI FCoE in version 2.1 of UCSM.

  HTH

  Padma

• Performance issue with multiple jumps of FCoE

  At at - it implemented FCoE multihop on the new firmware 2.1? I moved my UCS lab he and storage performance stagnated. Here's what I have in my lab.

  2 nexus 5500 s - used for LAN and FC switch

  EMC CX4-120 - connected to the 5500 s Nexus 2

  UCS 6120/FEX 2104 - Pre-FCoE to installation has been a port-channel 2 SAN ports in every tissue of the Nexus 5ks.

  6 servers B200 M1

  ESXi 5

  I wired to the top a twinax addition on a fabric of interconnection to 5548 Nexus in FC fabric

  I wired to the top a twinax addition on interconnection fabric Nexus 5548 FC fabric b B

  Configured interfaces such as FCoE uplink in UCS

  Placed the FCoE interfaces in the proper VSAN

  A tissue at the same time, I have disabled port-channel SAN FC to force the vHBAs to connect to the uplink of FCoE. Didn't have any problems with this and vHBAs appeared in the table flogi to the couple of 5ks on the interface correct vfc.

  Reloaded my ESXi (SAN boot) hosts and guests restarted very well using uplink of FCoE to Nexus 5ks.

  When I turned on a virtual machine, it took more than 20 minutes for it to start and he was to the point where it was usable.

  No drops or errors on the FCoE interfaces or the fabric of interconnections vfc and Nexus 5ks.

  As soon as I have reactivated the CF port-channel SAN using 4 GB SFP modules and disable the performance of uplink FCoE was fine again.

  I hope that it is something to do with the older hardware of the generation 1 6100 s and the IOM s 2100 and not a bug.

  I have 2 other servers HP rack mount with CNAs Qlogic FCoE on the VMFS LUNS even without any problem.

  Case ID: 624922297

  The Nexus switches as well as technical support UCSM are attached.

• FCoE Multihop

  Hi all

  I am fairly new to the world of storage and now I'm working on the FCoE multihop test laboratory. I have a few questions that need to be clarified and some examples of caonfiguration that need to be corrected. I've also attached the logical topology for my lab. Here is the information on my topology:

  • Blue = line ethernet
  • Red line = CF
  • Green = line FCoE
  • 2xN5K with NXOS v5.xx
  • 1xFI 6120 with UCSM v2.1
  • NetApp FAS2200
  • I activated fcoe and npiv pn my 2xN5K function

  What I want to do done VSAN (VSAN 360 and 361 VSAN) NetApp 2 and connect it to CF link to my 2xN5K as FC and then continue downstream, it my FI and UCS blade via link FCoE. Here are some questions I want to ask questions on:

  1. From what I read, we must separate FCoE traffic ethernet traffic in this scenario, that's why I use 2 FCoE links separated beside 2 ethernet (on vPC configuration) link, from 2N5K to FI. Is this true?
  2. To activate the FCoE, we map the VLAN-VSAN, and from what I've read, there are separate VLANS for this VLAN mapping VSAN that carries the normal ethernet traffic. Is this true?
     NB: I have 2 VLAN on blade UCS (260 and 261) and for this FCoE connectivity, I create 2 VLAN more (360 and 361) map to VSAN 360 and 361.
  3. This question have a link with #2--> from what I've read, the traffic of VLAN than carry FCoE traffic can not pass vPC link Peer, that's why I created different VLAN so that on vPC Peer link I can filter FCoE VLAN (VLAN 360 and 361). Is this true?
  4. By N5K links that are connected to the FI must be configured in F mode, what links that connect directly to NetApp (Interface type = CF)? On which mode is it?

  I think that's all for now, I hope that you guys can guide me in this world of storage. I await your response. Thanks in advance.

  Best regards

  IJE

  IJE Hello,

  (1) Yes, you must use the uplink dedicated for FCoE when you use vPC between FI and N5K. If you do use VPC (IE FI has <---->N5K-== directly via the mode), you can use rising unified (FCoE + LAN) on the same physical links.

  (2) Yes. You will use same ID VLAN-VSAN on FI and N5K to be part of the same fabric.

  (3) Yes, don't allow VLAN FCoE links counterparts vPC.

  (4) type port N5K connection FI and Netapp would be F

  Please refer to the following doc

  FCoE 5000 Nexus with attached FCoE UCS (Multi-Hop FCoE) Configuration example

  http://www.Cisco.com/en/us/products/ps9670/products_configuration_example09186a0080c13e92.shtml

  HTH

  Padma

• 6200 FCoE in the direction of the North

  I have a quick question that I have not been able to get a definitive right answer to (in literature)-regarding the new 6200 FI and FCoE in the direction of the North...

  Anyway, my question: with the function UP on the 6200 (with UCS 2.0) - can we now do FCoE in the north direction (in this case a nexus 5548UP)? Or do we still need out in separate eth and FC rising?

  I see of the configuration Guide, we can configure ports such as FCoE ports - and options for eth uplinks and CF uplinks are still there too. I was not able to determine if the FCoE port type can be used for uplink.

  Thanks in advance!

  Hi Daniel,.

  * You can always northbound FCoE connectivity of the UCS YEW which in your case, you can not uplink between 62xx FCoE and the 5548UP.

  * You must always have seprate FC rising and uplinks Eth.

  * The feature to have FCoE uplink will be available in a future release (on request at the end of the year).

  * the FCoE ports that you see are to use when you want to direct fix storage of FCoE for FI (limited support model).

  I hope this helps!

  . / Afonso

• VSAN guests can access the FC SAN storage at the same time?

  Soon we will invest in new ESXi hosts and we want to design them for the ability to VSAN. But since VSAN is a fairly new technology, we also want the same hosts to act as our old guests and have warehouses of data in our SAN (FC SAN attached storage) environment.

  Host VSANS have access to VSAN and FC SAN storage at the same time?

  What advantages and disadvantages do you see with this design?

  Yes, there is nothing to stop an ESXi participating both host a cluster VSAN, and also had access other storage taken in charge of protocols such as NFS, FC, FCoE or iSCSI.

  However, you will not be able to use the LUNS or Volumes presented on NFS, FC, FCoE or iSCSI for storage VSAN.

  VSAN requires local disks to build the VSAN data store.

  I guess the only concern would be the additional management that comes with having many types of different storage, but this is true even if VSAN wasn't in the picture.

• Balancing of VMware with Nexus 1000v

  With the vmware puts vDS or vSS, I see many designs use the asset-liability approach for binding rising consolidation of NETWORK cards, IE a vmnic is active will fabric and a vmnic is passive will fabric B. This setting is configured in vSphere.

  Se this article: http://bradhedlund.com/2010/09/15/vmware-10ge-qos-designs-cisco-ucs-nexus/

  Is this correct, that we can put in place a regime with the 1000V? All the network is on the 1000V config, and as far as I know, we can only configure the uplink in these 3 modes:

  1. LACP 2. vPC-Host Mode 3. vPC-Host Mode Mac pinning

  and they are all 'active' based.

  Post edited by: Atle Dale

  Yes.  All uplinks are used.  Each VM virtual interface is pinned to one of of the uplinks.  If one uplink goes down, all interfaces pinned gets dynamically likes to remaining uplinks.  A mac address will only see on a single interface at a time.  This is how MAC pinning prevents STP loops.

  Robert

• Is a UPC (Unified Port Controller) of the FI 6200 supports multi protocol port simultaneously?

  Hello a good person.

  Is a UPC (Unified Port Controller) of the FI 6200 supports multi protocol ports simultaneously?

  For example, the second UPC has 1/9-16. Configure the ports like these? 1/9-10 for the server ports, 1/11-12 for the uplink ports, 1/13-14 for FCoE Uplink ports, 1/15 and 16 for the Uplink FC ports and so on. I know that Cisco Documents describe a port can be configured as server port, FC, FCoE... I "don't not interesting in these gross comments."

  Thanks in advance.

  Paul

  In UCS unified configuration of ports is controlled by a scroll bar, as shown here.

  

  There is a fixed configuration for FI ports, then another to the expansion Module. FCoE and Ethernet ports are both type Ethernet from a unified point of view port, CF requires that you select the ports you want to be FC ports.

  All ports to the left of the slider bar will be Ethernet, which can also be configured for FCoE, and everything to the right will be CF.  So to answer your specific scenario above Yes. BUT with a caveat.

  If you have moved the cursor between port 14 and 15 then left would be Ethernet can be configured as a Server Port, Port Uplink or FCoE port and ports 15 and 16 could be configured as FC ports.  BUT the downside would be that ports 17-32 would also be FC ports and you couldn't get to the Ethernet ports later.  If the port configuration is adjacent to ports on fixed ports, as well as on the extension module.

  Best practice is to determine how many FC ports you need and configure each component accordingly.

  Here are some details on the guidelines for the unified configuration of Ports.

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/GUI/config/Guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html#concept_0249934662D1439AA5E926A503AC8B4B

  Hope this helps,

  Steve McQuerry

  UCS - Technical Marketing

• Question on networks

  So I got place in the role of Manager of the UCS with only knowledge of interview (currently in training).  I noticed some things that I'm curious about but do not know where I should look for more information.

  For one.  We were orinigally using the port channels to do when we have a connection of 1 g at the base of the FI in networking, now that we are 10g my network team told me that we do port channel and what I've got now the installer is 3 network connections scored and 1 connection marked unified 2 FI B network uplink and 1 Unified Uplink and 1 network FI.

  This looks very bad for me, but I also can't seem to set the port to uplink unified to a network port (I don't see that as a choice of configuration).

  If anyone has some good info on what I really need to be looking at who's going to be great, but if you encounter a problem similar would be great.

  Thank you

  Sean,

  Do a more thorough search in our database I found that this has no problem and in fact says that it works like for FCoE and Ethernet uplink port at the same time and it should appear on the tab LAN and SAN as uplink ports.

  We define the role of the port on the 'Network', 'FCoEUplink' or 'UnifiedUplink', based on whehter, that port is used as ethernet uplink, fcoe uplink or both.

  If you go to the LAN/SAN tab and check the interface you should be able to see the interface, as for the two because they are unified uplink Ports which can be ports CF or Eth.

  Can you try to cancel the configuration of the port from the tab "hardware"? LAN/SAN tabs you will only remove/disable the interface and then just configure it as uplink LAN or SAN?

  Let me know what happens.

  Note THE answers useful.

  -Kenny

• UCS Boot from SAN

  Hello

  I hope boot us from SAN, is UCS capable of automatically failing on OS start path, fabric case of failure? If the answer is NO, is there not a serious problem of booting from SAN?

  Thank you very much

  Multipathing is applied at startup and data lun and is independent of the policy of the boot

  I'm sorry that I do not understand where I misused the term automatic.

  The policy of the boot is a static, very simple construction: first use the first path to start; it it fails, try the other?

  CF Multipathing, regarding once the server is up and running: before the failure of tissue, you have 2 paths, after only one path to the LUNs (data and start-up).

  If all uplinks to the North switch failure, or a whole tissue, UCSM report link to all NICs for/vhba of this fabric. (default setting for network control strategy-> Action on the failure of the uplink-> link down)

• Port of uplink on PowerConnect 8024F went to the D State down

  Hi all

  We had a strange behavior on one of our switches PowerConnect 8024F. The uplink port of the device (connected to a port on a Cisco Catalyst 6513 10Gig) came down. The output of 'show interfaces status' looked like this:

  Port speed Duplex Neg frothing link Description
  Status of the State
  ---------  -------------------------  ------  -------  ----  ------ ------------
  TE1/0/1 cat6500-rz-1 (te11/2) 10000 Full Off D-low idle
  TE1/0/2 pc8024-ub-1 (te1, 0, 1) complete 10000 Off place Active
  TE1/0/3 pc8024-uv-1 (te1, 0, 1) complete 10000 Off place Active
  TE1/0/4 pc5500-naf02n-1 (te1, 0, 1) complete 10000 Off place Active
  TE1/0/5 pc5500-naf04n-1 (te1, 0, 1) complete 10000 Off place Active
  TE1/0/6 pc5500-naf03-1 (te1, 0, 2) 10000 Full Active Off
  TE1/0/7 pc8024-mensa-1 (te1, 0, 1) complete 10000 Off place Active
  Defekt TE1/0/8 n/a unknown inactive low Auto
  TE1/0/9 pc5500-naf03-2 (te1, 0, 1) complete 10000 Off place Active
  TE1/0/10 pc5500-naf03-3 (te1, 0, 1) complete 10000 Off place Active
  ...

  .. and so on. Firmware is 5.1.2.3. We rebooted the device and he returned to normal behavior.

  Now, can someone explain to me what the "D-Down" State means? I have not found anything in the documentation and using google not any success.

  The configuration of the port looks like the following:

  Description ' cat6500-rz-1 (te11/2).
  MTU 9216
  switchport mode general
  switchport general allowed vlan add 4-5, 14, 22-2729-33, 36, 39-41, 43 tag
  switchport general allowed vlan add 47,51-52,54-56,58-60,63-64,66,75,78-79 tag
  switchport general allowed vlan add 81, 86-90, 93-99, 107, 120, 122 tag
  switchport general allowed vlan add 124 132 - 135, 137, 140, 142-143 147-152 154 tag
  switchport general allowed vlan add 156-157, 160, 165-166, 171, 173-175 the tag
  switchport general allowed vlan add 177-178 180-181, 183, 189, 192, 195-196 the tag
  switchport general allowed vlan add 199,201,203-205 207-208 210-212 the tag
  switchport general allowed vlan add 219-222 224-225 227-233 235-244 246 tag
  switchport general allowed vlan add 248-249, 253, 256, 258-260 262-267 tag
  switchport general allowed vlan add 269-272 274-276 278-279, 282, 284, 286-288 the tag
  switchport general allowed vlan add 292 295 - 298, 323, 344, 347, 349 tag
  switchport general allowed vlan add 354,362,366,370,372,378-380 382-383 385-386 tag
  switchport general allowed vlan add 391,399,405,431,443,447 tag
  switchport general allowed vlan add 475-476, 485, 488, 511, 522, 584, 700-703 710-714 tag
  switchport general allowed vlan add 725,734,838,854-855 909 tag
  switchport general allowed vlan add 950 961 - 962, 981, 999, 1234, 1236, 2205, 2218-2220 tag
  switchport general allowed vlan add 2222,2233,2414,2417 tag
  switchport general allowed vlan add 2506-2507, 2519, 2521, 2621, 2699 tag
  Access-group PVST Mac - filter 1
  LLDP transmit tlv sys - name sys - cap
  LLDP transmit-mgmt

  The used mac filter access PVST-group is:

  Mac-extended access list filter-PVST
  refuse any 0100.0CCC. RCC 0000.0000.0000
  allow a full
  output

  Thanks for reading and suggestions!

  Robin

  It's all associated spanning-tree protocols. D to the bottom is synonymous with diagnostic downwards, which occurs if more than 15 BPDU per second is received during 3 seconds. The switch closes the port. USL worker task is bound traffic so a big change covering tree cause it's really high.

• Scenario VSAN with 3 hosts - hosts, 2/3 down

  Hello community,

  I have a question about the following scenario. Take a look at my enclosed PDF also.

  -VSAN with a total of 3 guests (A, B, C)

  -VM 1 is running on host a.

  What happens when the host B and C goes down?

  The VM on the host of way continues running or down also?

  Thanks for that.

  Migo

  lmigo wrote:

  What I need, is that the virtual machine host A continues to operate even if the hosts B and C go away.

  As the VMS on host A is running and there is no problem, I want to make it work so that problems with & B and C are resolved.

  Is this possible in a VSAN environment?

  "There is no problem" depends on how you look at it. From a point of view VSAN you just lost quorum as more then 50% of the components must be available. There are a lot of questions in this scenario as I see it. What you are looking for is not possible with VSAN.

• stop the ethernet uplink port will cause the port of the unit down

  Dear all,

  I want to make sure that this kind of network traffic will communicate internal fi.

  I've disabled the uplink port and found the path of material has also declined.

  Port of the device must road toward uplink port and then back to UCS server?

  Thank you for the clarification.

  Best regards

  Dennis Dai

  Expected behavior.  By default, if there is no uplinks online & fwd, then all links South (Server binds and the ports of the device) will be used also to the bottom.

  See the explanation of Abi here for more information how to change this behavior.

  https://supportforums.Cisco.com/thread/2187144?TSTART=0

  In short, we must change policy control of the network of the way of the material in the Hardware tab.

  Kind regards

  Robert