Force10 MXL - stack or do not stack

Similar Questions

• 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.

• 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.

• 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

• Then a Force10 MXL blade handle no FCoE traffic?

  Hello.  I inherit a M1000e with few blades of the Force10 MXL switch installed.  The chassis has no other 10GBASE-T switches.  Since I have no plans on using FCoE, a Force10 MXL can be used for standard Ethernet (non-FCoE) traffic?  Or do I have to buy another switch?

  Thank you.

  Absolutely, to see the second page of the data sheet. It contains additional information about the available modules, how internal traffic is manipulated and external.

  http://Dell.to/1Q5fUo9

  The manuals are a great place to start. There is that a starter guide to help set up initial, and then a CLI and user guide to help configure additional features.

  http://Dell.to/1IIq8r2

  Let us know if you have any other questions.

• 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 S25 - stacking. Is the required stacking module?

  I would like to know if the S25N can be stacked using the buit of SFP ports in the chassis, or acquired the required stacking module?

  So that to stack switches, stackable modules must be used. Here is a good guide on the process.

  http://www.force10networks.com/CSPortal20/TechTips/0057_HowDoIStackSSeriesUnitsTogether.aspx

• 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

• MXL 990 Microphone will not install on Vista 64

  I recently bought a MXL 990 USB, but Windows Vista 64 microphone it won't install. The microphone does not a driver and it does not work , because it installs instantly on my XP system. I have consulted the MXL TEC and searched the Web and all the pages of Microsoft for answers, but found nothing. I ran software Microsoft Fix It, but it found no problem. My system updates automatically, but I searched some other updates for audio drivers without success. Again,that what mike does not require a pilot , however, the system requires one tries to find an and cannot (because they do not exist and are not necessary with this mike). Setting procedure is not possible because the microphone is not recognized and does not present as an option. Help, please!

  Please try plugging a "known to work with Vista" USB Audio device.

  If it is recognized, without disconnecting, plug the MXL 990 and see

  If Windows will recognize and install properly as a microphone.  If so,.

  the first device can be disabled as a device audio, but not disconnected.

  She needs to stay connected while you use the MXL 990; Unplug the unit

  the other device will cause the mic to continue to appear as a good

  device, but it will stop working, and no audio program will see his

  presence.  If you return to this topic and see the fix, please report it

  back and tell me if it worked for you, because it's a workaround that

  solved my problem of Win 7 990.
  

• stacking vs vlt - S4810 and MXL 10/40

  Hello

  I looked through the battery vs vlt article http://hasanmansur.com/2012/10/15/force10-s4810-stacking-vs-vlt/ and curious to know what Dell recommends for MXL and S4810 going on these days. I guess that even if these are the different types of switches, configuration, restrictions and features etc are similar.

  It seems that the firmware update is the key of the differential between the stack and the vlt. So update fw would get all the fabric on the configuration of the battery, but what of SUVs? VLT works very well when the fw update while peers are actually on different version?

  Thank you

  as much as I saw it, the only drawback is updated firmware that should be all the fabric on the configuration of the battery down. On the other hand, how vlt works during the upgradeHowever of the firmware in the different version update

  Regarding the VLT upgrade process, I was wrong, you do the second job first, then the primary. Just be sure to check that OTF notes for all stages of development.

  With a battery, you apply the image to the master and then propagate the upgrade of the master to other switches. This is the entire stack must restart to activate the new image.

• Configure access ssh_key based switch MXL. Not "based on the host."

  I have read the documentation and cannot get to a cohesive whole procedure in order to get the simple key-based authentication to work.

  The docs separate this task in a wide variety of measures in order to activate authentication "host-based", but I don't want to.  I use two laptops and 2 different offices in various locations.  "Host-based" is not going to work for me.  I need an authentication of purely "function key".  You need an example of what involved specific steps and the order to execute them.  I find that this process is pretty simple on the HP based including the new Arubas switches.  But this MXL documentation is difficult to decipher.

  It seems as it is a one-at-a-time operation, but it is more advanced and allows you to better separate, and so I'm happy with it so far.

  1. create the user with administrator privileges
  SN - MXL (conf) "JUtilisateur" somepass privilège 15 password #username

  2 enable authentication rsa
  SN - MXL (conf) ssh rsa authentication #ip activate

  3. copy your public key in the MXL (pull)
  SN - MXL #copy scp: flash:
  Address or name of the host remote []: 172.16.11.10
  Port number of the server [22]:
  Source file name []:.ssh/juser_rsa.pub
  User name to host remote login: "JUtilisateur"
  Password to the remote to connect host:
  The destination [juser_rsa.pub] file name:
  !!
  403 bytes copied successfully

  4. now log in as user, and run:
  SN - MXL #ip ssh juser_rsa.pub my authorized key of rsa authentication
  RSA keys added to the list of authorized Keys user.
  Delete the juser_rsa.pub file: (yes/no)? Yes

  5. I had to create the file ~.ssh/config with the following statement:

  host mxl
  Host name 172.16.11.1
  The user juser
  IdentityFile ~/.ssh/juser_rsa

  This means that the PRIVATE key is referenced.  Note: Make sure that your config file is has 644 permissions.

  6 test

  $ ssh mxl

  The option of SupportAssist EULA acceptance has not been selected. SupportAssist
  can be activated once the EULA of SupportAssist has been accepted. Use of the:
  command "Activate support-assist" to accept the EULA and activate SupportAssist.

  MON-MXL #.

  And I am.  Either way, I want to get rid of that little nag, as this MXL stack is not in a country supported by DELL.  Anyone know how to remove the horse?

• LAG, VLANS and Trunking Force10

  I'm with vSphere and I a vSwitch with several groups of ports configured, including 2 assigned to VLAN ID and a network of management with no Vlan ID.  This vSwitch will use physical NIC grouped to route this traffic to a physical Dell Force10 MXL switch.  My understanding of the standard networking, a trunk port must be configured and VLAN must be added to this as labeled trunk port, while the traffic that has no Vlan ID is left unidentified and by default is the vlan by default (usually Vlan 1).  The attached picture is the topology I and I need to make this work, but do not have a lot of experience with Force10 switches and so far, it looks very different.  In addition, if it is relevant, the external switch in the diagram is actually 2 Force10 switches separated stacked, and there are two connections to the other switch (currently a 6224 not managed) between the firewall and F10s, which is a separate issue - those must be configured as an OFFSET on the F10s and the 6224? One or the other?  Or?  If anyone can help with the configuration for this topology?  Please help me out here.  Thank you!

  

  Currently, the best method to get assistance and recommendations with Force10 equipment, is through the Force10 support group. They will be more quickly and accurately help you with this inquiry.

  www.force10networks.com/.../ContactSupportGen.aspx

  Watching a white Force10 pages looks like a trunk can be configured with these commands.

  Configure VLANs tagged for an Interface of Port Trunk

  #configurer MXL2 MXL2 vlan (conf) #interface 11

  MXL2 (conf-if-vl-11) #tagged tengigabitethernet 0/1

  MXL2 (conf-if-vl-11) #no shutdown

  MXL2 (conf-if-vl-11) #exit

  MXL2 (conf) #interface vlan 12

  MXL2 (conf-if-vl-12) #tagged tengigabitethernet 0/1

  MXL2 (conf-if-vl-12) #no shutdown

  MXL2 (conf-if-vl-12) #exit

  MXL2 (conf) #exit MXL2 #.

  en.Community.Dell.com/.../download.aspx

  Thank you.

• 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

• 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.