Then a Force10 MXL blade handle no FCoE traffic?

Similar Questions

• Force10 MXL and blades - mapping of Interfaces

  Hello

  I know it's a recurring topic but I am facing a strange problem in the last M1000e chassis that I was sent.

  According to: mapping is very clear. For example, the first interface of the first plank must be connected via the Midplane to te0/1 (first in the IOM1 interface), but when I set up the battery of the A2 Force10 MXL (just a pile between A1 and A2) became the master so I changed the priorities to ensure that A1 is the master. Once this is done, I realized that the first interface of the first blade was linked to the Te1/1, the first IOM2 interface. Is it possible to change this? I have several chassis and I want to set all the same way...

  Thank you!

  What servers are used? Just to be clear, while MXL in A2 was the master, the LOM 1 port connected to 0/1 and the LOM 2 port connected to 1/1? Then when you changed a switch to A1, now port 1 shows that 1/1 LOM and LOM 2 port connected to 0/1?

  The ports are all physically defined by the M1000e chassis.
  Have you tried:
  -unstacking switches
  -Can ensure that ports appear correctly so that not stacked.
  -Set the priority and then put.
  -Check the enumeration.

• Force10 MXL config question

  My MXL blades have been set up by Dell Technology Services and work fine, but I would like to make a few changes now and not being Setup is not a network engineer, I have a problem with the docs I could find on the config of Force 10.  Specifically, I want to do 3 things:

  (1) change the SSH root password

  (2) remove a port to a LAG (port channel) group

  (3) add a new VLAN to some ports in the switch, including the one I just removed the lag, but abandon the SHIFT since the new VLAN

  Can someone point me to a doc that explains how to do this kind of things?

  Also, is it possible to access the console somehow by SSH in the CMC?  I swear I've seen Dell Tech Services people who do somehow, but I don't know how they did it.  Maybe I misunderstood what they were doing.  It would be nice to not have the addresses of IP config exposed and control access through the permissions of CMC.

  Thank you.

  Hi amunter,

  You can SSH to the CMC racadm commands and use to set it up. You just need to use PuTTY or other terminal program and go to the CMC host name or IP address.

  You should be able to change the password in this way

  (Force10) > activate

  (Force10) #config

  (Force10) (Config) #username admin passwd un_mot_de_passe

  _Config_07_29_2014.PDF https://www.force10networks.com/CSPortal20/Knowledgebase/documentation/CLIConfig/FTOS/MXL_9.5 (0.1)

  You can remove a port of a port channel in the channel of the port and using the command config no channel-member interface

  Page 395

  You can assign a VLAN to a port with the command interface vlan id - vlan

  Page 910

• Connect to Force10 MXL N4032 using cables QSFP + DA 40 G

  Hello

  I'm trying to connect a N4032 switch to a switch chassis Force10 MXL using QSFP + modules and a DA 40 G cable. Now, the problem I have is that when I plug the cable 40G QSFP DA I don't have a link, both switches show that the QSFP + optical has been inserted, and that the perspective is supported on two models of switches.

  The MXL is on the firmware 9.8.0.0 and the N4032 on 6.2.1.6.

  QSFP map show slot on the show N4032 command:

  Power admin card configured
  ID of the slot status State Pluggable model
  ----- ------ ------- ------- -------------------------------- ---------
  1/0 Enable full activate Dell N4032 number of networking
  1/1 full Activate activate card QSFP Dell Yes

  Optics QSFP + is connected to the port of1/1/1 on the N4032 and returns order status interface to see more:

  Physical admin link link LACP Flow physics
  INTF Type Mode Mode status trap Mode Mode
  --------- ------ ------- ---------- ---------- ------ ------- ------- -------
  TE1/0/1 Select Auto 10 G full turn off Active
  TE1/0/2 Select Auto 10 G full turn off Active
  TE1/0/3 select Auto 10 G full turn off Active
  TE1/0/4 turn down turn off idle
  TE1/0/5 turn down turn off idle
  TE1/0/6 turn down turn off idle
  TE1/0/7 activate Auto 10 G full activate deactivate Active
  TE1/0/8 enable Auto 10 G full activate deactivate Active
  TE1/0/9 turn down turn off idle
  TE1/0/10 turn down turn off idle
  TE1/0/11 select Auto 10 G full turn off Active
  TE1/0/12 enable Auto 10 G full activate deactivate Active
  TE1/0/13 turn down turn off idle
  TE1/0/14 turn down turn off idle
  TE1/0/15 turn on Auto 10 G full activate deactivate Active
  TE1/0/16 enable Auto 10 G full activate deactivate Active
  TE1/0/17 enable Auto 10 G full activate deactivate Active
  TE1/0/18 turn down turn off idle
  TE1/0/19 turn down turn off idle
  TE1/0/20 turn down turn off idle
  TE1/0/21 Enable Auto 1000 Full Up enable disable Active
  TE1/0/22 Enable Auto 1000 Full Up enable disable Active
  TE1/0/23 Enable Auto 1000 Full Up enable disable Active
  TE1/0/24 turn down turn off idle
  Of1/1/1 turn down turn off idle
  Of1/1/2 active 40 maximum G low turn off idle
  TE1/1/1 active 10G full detach turn off s/o
  TE1/1/2 Active 10 G full detach turn off s/o
  TE1/1/3 active 10G full detach turn off s/o

  As you can see that switch captures yet the speed of the optics. Now if I take the same cable and plug it between the 2 x N4032 switches - ports immediately show a link.

  Newspapers of the MXL show optics QSFP Fo0/33, it shows the status of the admin of the ports as upward, but the State of the interface is down. Now if I take the same cable of DA and plug it between the 2 MXL in the chassis, the interface state changes until almost immediately. The two MXL is configured in a VLT, but I tried to get the link to the top with the VLT and without the VLT, does anyway.

  This shows that cables of DA are fully functional, the ports I plug are functional - even when one end of the cable plugged into the N4032 and the other end in the MXL Force10, the link is not started.

  I have the show out of all 4 switches, if necessary technical support.

  Thank you

  Dave

  This problem has been resolved with the help of Technical Support.

  It was a mismatch of negotiation between switches.

  The fix has been add to the config of the port on the Force10 MXL:

  interface fortyGigE 0/33

  INTF-type cr4 autoneg

• DCB - Force10 MXL and Equallogic PS6210 - worth it or not?

  Hello all

  I have a new 3-blade M620 virtualization environment, 2 x MXL Force10 switches and 2 x Equallogic PS6210 - there is the possibility of using DCB - is it useful to configure DCB, will I get the gains and better stability, or for a small environment should I just use the configuration standard iscsi?

  Ideas or alternative options gratefully received.

  Thank you

  Hello

  If the switches are dedicated for iSCSI use, then there is no advantage to the use of DCB.  DCB in itself does not have iSCSI faster.  I just made sure non-iSCSI traffic doesn't interfere by providing iSCSI with a higher priority.  All other traffic is going in a "lossy" class of service.

  Also, you will need DCB converged network adapters to use BCD on the hosts.  Most of the iSCSI software adapters do not support DCB.

  Kind regards

• Force10 MXL - VLAN is not routing.

  I'm trying to set up a simple installation Layer 3 on stacked MXL Force10 switches.

  ManagementEthernet 0/0 90.21.0.175 YES manual upward, upward
  VLAN 33 10.1.33.1 YES manual upward, upward
  VLAN 101 10.1.32.1 YES manual upward, upward
  VLAN 103 192.168.103.1 YES manual upward, upward

  MXL-stack #sho vlan

  Q: U - no identified, the T - tag

  Ports Status Description Q NUM
  * 1 U active Te 0/3-6, 11-14, 17-23, 25-32
  U Te 1/3-6, 11-14, 16-23, 25-31

  EENET active 33 U Te 1/15<>
   
  101 production Dynamics network T Te 0/1-2, 7-8, 15-16, 24, 44<==10.1.33.x>
  T Te 1/8,24,32
                                          
  External network active 103 T Te 0/8,16,24<==192.168.103.x>
  T Te 1/1-2, 8, 24, 32
  U Te 1/7

  Route ip MXL-stack #sho

  Destination Gateway Dist/metric was last modified
  -----------                          -------                                ----------- -----------
  C Direct 10.1.32.0/24, Vl 101 0/0 3d2h
  C Direct 10.1.33.0/24, Vl 33 0/0 00:13:51
  C Direct 192.168.103.0/24, Vl 103 0/0 3d1h

  Battery Switch MXL
  Ping result message
  192.168.103.13 fail
  10.1.32.21 success
  10.1.33.10 success

  192.168.103.13 - default gateway is 192.168.103.1
  Ping result message
  192.168.103.1 success
  192.168.103.11 success
  10.1.32.1 success
  10.1.32.21 fail
  10.1.33.1 fail - 192.168.103.1 inaccessible Destination network

  10.1.32.21 - default gateway is 10.1.32.1
  Ping result message
  192.168.103.1 success
  192.168.103.13 fail
  10.1.33.1 success
  10.1.33.10 success

  10.1.33.10 - default gateway is 10.1.33.1
  Ping result message
  192.168.103.1 success
  192.168.103.13 fail
  10.1.32.1 success
  10.1.32.21 success

  I have my hosts on my different threads pointed to the stack for their default gateways, and I want my MXL battery to switch packets at layer 3 connectivity between subnets.  The part which I stem is why is my vlan 103 does not communicate?  I can't even he ping of the MXL battery that has the vlan on it.  This should be the easiest thing in the world, but it is a failure.  Someone has an idea?

  I am pleased to hear that the routing has started working. I agree, it seems strange that would not work one day and then work the next day. Were all devices removed or added to the network between the two days? Or any small changes to config?

  To remove a configuration you issue clear config

  http://www.force10networks.com/CSPortal20/TechTips/0080_HowDoISaveMyConfiguration.aspx

  The latest firmware is 9.3.0.0. Which provides overall improvements and would be calling and updated.

  iSupport portal (Web): http://www.force10networks.com/support/
  E-mail: [email protected]
  Phone (USA and Canada): 866-965-5800
  Phone (International): + 1-408-965-5800

  Can monitor to see if the problem back to the top again.

• Switch MXL blade 10/40GbE - what is the latest firmware, and where I can get it?

  Hi guys,.

  I logged into the site to support Force 10 today and found virtually useless.  Where can I get my support, documents and firmware for my MXL going on these days?

  The number is actually: 800-945-3355 for Force10.

  Apparently my sales guy forgot to add that switches M-Sereis to my Force10 load site profile.  It's a shame because it's been over a year since I bought the 2nd battery of them and he never even he added the first time.  If the support guys, that I just talked can not do the job, I'll have to track down this sales guy and her dog by doing this.

• Force10 MXL - stack or do not stack

  Hi guys,.

  If the availability is the most important thing, trunk or battery MXL rocking?

  I like simplified management, ability to balance the load on several links but I am concerned about uptime during the upgrade firmware (5-10 minutes?) and the possibility of a total interruption of the battery breaks.

  On the other hand Force10 perhaps more capable stacking that for example. 6224 switches, I had a lot of problems of overlap with.

  Forgive me if this is the wrong place to ask, but I couldn't find a Force10 forum? :-)

  Thank you

  Respect of
  Kristoffer

  The MXL switches support Virtual Link Trunking (VLT) later this year, which will solve this problem.

• Networking M1000e

  We ordered a M1000e chassis. We use Dell Force10 MXL blade switches (2) for networking. My question is that the switch MXL comes with 2 ports QSPF +. We also ordered (1) of these (Module 10GbE SFP +, 4 ports, Hot Swappable, 4 x SFP + ports (optical or direct attach cables needed) (331-8187)). WE have 1 but we want redundancy. My question is can I use a cable QSFP + who has a connection to 40 GB on the end of switch MXL and use 1 or 2 of the 10 GB SFP + cables on the other end in my Cisco switch? WE have not enough ports 10 Gbit/s at the moment to use all 4. I don't know if we need to use all 4 cables of 10 Gbps or can use 1 or 2 and develop in all 4? We think just go back the 331-8187 and using the drop cable.

  Using an extension cable for the connection of the switch will work fine. With cable bypass, you are not required to run all the lines on the same unit, or use them all at the same time. Each of the four 10 GB cables will act as a single port.

  Page 406 of the configuration guide details how to divide the QSFP port in ports SFP +.

  http://Dell.to/1IIq8r2

• VLANning questions about blades MXL

  Hello

  I have a new M100e with a SAN PS4110xs case, a few servers blade and two switches Force10 MXL (switches and SAN on fabric)

  I put it all in place and works fine, but using the default VLAN for all

  I want to connect the switches to a Juniper EX3300 via SFP ports + and send the subnet SAN out so that I can connect remotely to the IP address of the EqualLogic for VMM integration management

  However, every time I try to put SAN ports in a VLAN separate-, before even that I look into the chutes for the Juniper - I lose all connectivity on the San.

  I created a new VLAN (VLAN120), but as soon as I set the ports inside they cannot ping each other.

  int vlan120

  Tagged te0/1 (this is the port of SAN)

  Tagged te0/12 (it is a single server)

  Tagged te0/16 (that's the other server)

  as soon as I do that I lose all connectivity to the San and server cannot ping each other via the iSCSI network.

  I tried to use 'no label' instead of 'tag' with the same effect.

  The VLAN is active (non-stop)

  I am at a loss for what is the question.

  Any help gratefully received.

  Select this option.

  I understood the question - I got 2 trunk in the Juniper VLAN120 links - as soon as I disabled the second interface everything arises in life

  Now I need to try to find a way to implement a SHIFT between the two MXL in the stack and a Juniper ex3300 - I managed to get the connectivity that I need, but with only a single link - as it is a remote site I want redundancy :-)

• Force10 vlan exclusivity?

  I had a whale of a Saturday in my COLO today trying (and failing) to complete what would have been a very simple task.  I still don't understand why this happened, or how to solve this problem, but it's here.

  Installation of the equipment:

  Stacked Force10 MXL going on inside a M1000e chassis with cluster VMware ESXi 5.5 inside, supported by all storage Equallogis M4001x.

  3 servers blades inside all NPAR running to copy all links are marked.

  I've been running 4 VLAN for always: 1. internal networking for virtual hosts. 2 Vmotion ISCSI 3. 4. external connectivity with other hosts on outside LAN subnets.  It's good and dandy.  I need to set up connectivity to the Internet now and have added a 5th VLAN to my battery and label ports properly wear 'inner' connectivity to the virtual machine that needs the external connection.  Simple.  Now:

  VLAN 10. Is Vmotion

  VLAN 20 is iSCSI

  VLAN 100 is my internal LAN

  VLAN 200 is external LAN subnets

  VLAN 300 is the Internet,

  Here it comes... when I plug the cable (VLAN300) between my Internet switch MXL Internet... HOORAY!

  AND... (VLAN200) is inaccessible.  Now, I can SSH into my M1000e, but can't reach it from inside the organization.

  Until - I unplug the cable to the VLAN200 and then plug plug back then... VLAN200 becomes available, but VLAN300 is now inaccessible.

  I tested this 9 ways of Saturday night today, and this is what I learned.  I can't find any logging on MXL battery that will give me a clue as to why this is happening, nor can I explain myself.  I have antique HP switches that can handle this type of connectivity, but these interconnections of Force10 edge-impossible?  What gives?

  Is there a parameter of maxvlans on those things that just won't allow these two VLANs internal and external to exist together?

  Has anyone seen something like this?  I plan on calling DELL support on this first thing Monday if I can't get some help here.  Thanks for your comments that you leave me.

  I just sent an email, you can reply to the email with the switch configs.

  Thank you

• MXL PS-M4110 DCB questions

  Hi all

  The installation program:

  Configured the MXL according to Configuration guide for the switch blade Force10 MXL 10/40GbE. The MXL have the latest firmware. I configured VLAN DCB in the GUI.

  The question:

  The MXL shutters port console and this error:

  % DIFFSERV-4-DSM_PFC_NUM_NO_DROP_Q_EXCEEDS_LIMIT: configuration of the priorities of the CFP has failed on the interface Te 0/14 due to the limit is greater than Max allowed Lossless 2 system queues. Updated local Params with PFC Defaults(No priorities enabled for PFC) incase admin params failed to update or update with admin params for failure to update remote params, administrator must configure with the priorities of the PFC with loss less the queue limit.

  Clues please?

  The problem has been resolved be removed the PS-M4110, I guess that makes the port renegotiate DCB. Port beating the issue proved the eth1 interface. I forced the port on the switch to SPEED 1000 and it installs.

• Configuration of MXL port for PS-M4110 storage array

  Dear all,

  I have to configure my Force10 MXL GbE 10/40 for PS-M4110 storage array. I have two PS-M4110 connected to ports 0/13 and 0/15. I have configured the following way.

  FTOS (conf) # don't activate any dcb

  FTOS (conf) # enable iscsi

   

  Configuring the ports 0/13 and 0/15 (ditto)

  OTF (conf-if-you-0/15) con #sho
  !
  interface TenGigabitEthernet 0/13
  no ip address
  MTU 12000
  hybrid portmode
  switchport
  FlowControl rx tx off
  spanning tree bpmh edge-port
  spanning tree rstp edge port
  spanning tree portfast 0
  spanning tree pvst edge-port
  Profile-compellent iSCSI
  no downtime

  I just need to know if these settings are correct. And what I have to configure iscsi target (3 260 860) ip address of the port-(A.B.C.D) as well? If Yes, then what IP should be given here? Group-IPaddress?

  I used this guide as a reference.

  http://Dell.to/1uxp4LW

  And it seems that you have everything in place. The guide recommends not to use iscsi optimization for large san deployments. You can browse the guide too, just to double check.

• FCOE-basic questions

  My understanding is that the traffic from the blades in the chassis or a rack of series C contains FCOE and Ethernet frames.

  But what about the traffic of a UTA Netapp? Glancing at the NExus switch configuration, it seems that all the ports in use are Ethernet ports. then we configure the FCOE ports on the Ethernet ports for FCOE traffic top. Like this:

  interface vfc7
  link interface Ethernet1/7
  no downtime

  interface vfc8
  link interface Ethernet1/8
  no downtime

  But what about traffic from UTA? It does not contain both types, and then only a single protocol to disappear on the port? Or what is happening here? I think I know a UTA 2 ports map can contain 2-port of FCOE and IP, IE. 4 ports altogether.

  Someone has a document explaining the UTA and FCOE?

  UTA will use FC IP addresses and at the same time that each port.  It's a similar logic to the way the N5K works for the last 5 years.

  Yes, a Nexus 5 K port can understand two FCoE & Ethernet at the same time.  This is the basis for the Consolidation of IO with the nexus platform.  On the side of 5 K, all Ethernet traffic is received and changed accordingly.  For FCoE, packets are received, the package of FCoE is encapsulated off and pure CF payload within the FCoE package framework is then logically received on the VFC interface associated with the physical interface of N5K.  FC traffic is so forward as usual on the switch.

  Robert

• 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