This post is more than 5 years old
131 Posts
0
63136
Force10 MXL - VLAN is not routing.
I am trying to configure a simple layer3 setup on stacked Force10 MXL switches.
ManagementEthernet 0/0 90.21.0.175 YES Manual up up
Vlan 33 10.1.33.1 YES Manual up up
Vlan 101 10.1.32.1 YES Manual up up
Vlan 103 192.168.103.1 YES Manual up up
MXL-Stack#sho vlan
Q: U - Untagged, T - Tagged
NUM Status Description Q Ports
* 1 Active U Te 0/3-6,11-14,17-23,25-32
U Te 1/3-6,11-14,16-23,25-31
33 Active eenet U Te 1/15 <==10.1.33.10
101 Active Production Network T Te 0/1-2,7-8,15-16,24,44 <==10.1.33.x hosts
T Te 1/8,24,32
103 Active External Network T Te 0/8,16,24 <==192.168.103.x hosts
T Te 1/1-2,8,24,32
U Te 1/7
MXL-Stack#sho ip route
Destination Gateway Dist/Metric Last Change
----------- ------- ----------- -----------
C 10.1.32.0/24 Direct, Vl 101 0/0 3d2h
C 10.1.33.0/24 Direct, Vl 33 0/0 00:13:51
C 192.168.103.0/24 Direct, Vl 103 0/0 3d1h
From the MXL Switch Stack
Ping Result Message
192.168.103.13 Fail
10.1.32.21 Success
10.1.33.10 Success
From 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 - From 192.168.103.1 Destination Net Unreachable
From 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
From 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 nets pointed to the stack for their default gateways, and I want my MXL stack to switch the packets at Layer 3 for connectivity among the subnets. The part that stumps me is why is my vlan 103 not communicating at all? I cannot even ping it from the MXL stack that has the vlan on it. This ought to be the simplest thing in the world, but it is failing. Anyone have an idea?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 27th, 2013 10:00
I am glad to hear the routing has started to work. I agree, it does seem peculiar that would not be working one day and then working the next. Were any devices removed or added to the network between the two days? Or any small changes to config?
To delete a current config you issue clear config
http://www.force10networks.com/CSPortal20/TechTips/0080_HowDoISaveMyConfiguration.aspx
The latest firmware is 9.3.0.0. Which provides some overall improvements and would be worth calling in and getting updated.
iSupport Portal (Web): http://www.force10networks.com/support/
E-mail: Dell-Force10_Technical_Support@Dell.com
Telephone (US and Canada): 866-965-5800
Telephone (International): +1-408-965-5800
Then monitor to see if the issue comes back up again.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 27th, 2013 06:00
What ports are 192.168.103.13, 10.1.32.21, 10.1.33.10 plugged into? And what devices do these IP addresses belong to?
Can you show us the output of #show version
Looking at the config it looks like you already took these steps, but it wont hurt to look through this quick video and make sure all these steps were taken.
http://www.dell.com/learn/us/en/19/videos~en/documents~esupport-mxl-vlan-routing-en-v1.aspx
Thanks
Jack_the_coiner
131 Posts
0
December 27th, 2013 09:00
Hi Daniel,
I will answer your questions, but I want to post one update first. I just arrived and got logged into my switch stack. First thing I wanted to check to see if the situation was the same. It is not. My pings from the MXL stack are now now reaching the 192.168.103.x vlan, and I am receiving replies. Nothing changed overnight, but now the most vexing issue has magically vanished. This is FLAKY now. Why were my pings failing last night, but today they are succeeding? This is seriously frustrating. In my opinion flakiness is the worst possible situation. It should be either UP or DOWN, but never in between.
This morning I have:
From the MXL Switch Stack
Ping Result
192.168.103.13 Success
10.1.32.21 Success
10.1.33.10 Success
From 192.168.103.13 - default gateway is 192.168.103.1
Ping Result
192.168.103.1 Success
192.168.103.11 Success
10.1.32.1 Success
10.1.32.21 Success
10.1.33.1 Success
From 10.1.32.21 - default gateway is 10.1.32.1
Ping Result Message
192.168.103.1 Success
192.168.103.13 Success
10.1.33.1 Success
10.1.33.10 Success
From 10.1.33.10 - default gateway is 10.1.33.1
Ping Result
192.168.103.1 Success
192.168.103.13 Success
10.1.32.1 Success
10.1.32.21 Success
See that? FULL CONNECTIVITY. I wish I knew why.
I think my next step will be to strip this down and begin fresh. I want to erase the config, but leave the management IP information and the stacking. Is there a quick way to do this? I wonder. Keep an eye on this thread for more details about what I am up to with this stack, and my results.
Jack_the_coiner
131 Posts
0
December 27th, 2013 10:00
Here is my setup:
M1000e chassis with: 8 blades. The blades are a mixture of M610, M620, and M420 servers. I intend to configure the stack to route between VLANS, and the servers will be running ESXi 5.5, with or without NPAR enabled. This requires an exercize in VLAN tagging which can be extremely confusing. I will start the fun soon. As of this moment some of the ESXi licenses have timed out, and I will reinstall to reset the clocks. I will also wipe my switch configs to the minimum and build fresh. The picture below does not show the MXL switches, but that is what those are in slots A1 and A2.
Jack_the_coiner
131 Posts
0
December 27th, 2013 10:00
MXL-Stack#show version
Dell Force10 Real Time Operating System Software
Dell Force10 Operating System Version: 2.0
Dell Force10 Application Software Version: 9.2(0.0)
Copyright (c) 1999-2013 by Dell Inc. All Rights Reserved.
Build Time: Mon Jul 29 13:49:38 PDT 2013
Build Path: /sites/sjc/work/build/buildSpaces/build19/E9-2-0/SW/SRC
MXL-Stack uptime is 2 week(s), 4 day(s), 20 hour(s), 35 minute(s)
System image file is "system://A"
System Type: MXL-10/40GbE
Control Processor: MIPS RMI XLP with 2147483648 bytes of memory.
256M bytes of boot flash memory.
2 34-port GE/TE/FG (XL)
96 Ten GigabitEthernet/IEEE 802.3 interface(s)
4 Forty GigabitEthernet/IEEE 802.3 interface(s)
MXL-Stack#
Jack_the_coiner
131 Posts
0
January 2nd, 2014 09:00
Thank you Daniel. I was able to rebuild much of the environment, and get the routing working reliably. Next I need to master the ACL.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
January 2nd, 2014 11:00
ACLs can be widely different from business to business, based on needs. The user guide has some great information you can use to plan and implement your ACL.
Page 71
ftp://ftp.dell.com/Manuals/all-products/esuprt_ser_stor_net/esuprt_force10/force10-mxl-blade_Reference%20Guide_en-us.pdf
This writeup is for an S50, but may be helpful for the MXL.
http://www.force10networks.com/CSPortal20/TechTips/0068_HowDoILimitManagementAccess.aspx
Hope this helps some