Solved

Configure 7048 two switches with teaming

Posted on 2014-12-13
3
187 Views
Last Modified: 2016-11-23
We have two Dell PowerConnect 7048 switches.  We have 6 dell r710s with multiple NICs and we would like to configure these switches for redundancy on my public network.  My private network, for my SAN traffic is fine and is configured appropriately.
We put both switches in place and teamed the Nics on the servers.  Everything in the default vlan works, but no traffic between vlans will communicate.  We have several VLANs created in the firewall and our virtual machines are members of certain vlans.  The hyper visors are all part of our default vlan, vlan10.

can anyone tell me how to configure these switches to work?  I have the following questions:
1. do we have to enable tagging at the firewall level vlan?  when I did enable tagging it made no difference.
2. do we have to create each vlan on the switch?
3. if so we will have to use tagging as the devices on the specific vlans are not physical and therefore are not connecting to physical port.
4. We will need communication between the vlans.

Currenlty we have an unmanaged switch in place, just a cheap netgear switch and everything works fine.  Once we IP the switch and plug into it, only the default vlan communicates.

5. the switches are currently connected but we are not using a LAG.  should we connect the two switches?

the idea is to team the nics for the public traffic so if we hve a switch failure, we are OK. One network interface from server 1 in switch 1 and the second interface in switch 2.

The reason we had the switches connected is because some of the devices do not have multiple nics.

any help would be greatly appreciated
thanks
0
Comment
Question by:jfeucht
  • 2
3 Comments
 
LVL 42

Expert Comment

by:kevinhsieh
ID: 40498796
I am not familiar with the Dell switches specifically as all my switches are Cisco. That said, a couple points should help you.

I assume your hypervisor is Hyper-V. Hopefully you are running 2012 or 2012 R2. If that is the case, use the native NIC teaming feature and configure them as switch independent. This doesn't require LAG and allows for failover should a NIC, cable, or switch fail, and it allows for aggregate bandwidth to be greater than what a single NIC can provide.

Each switch needs to be configured for every VLAN.

The ports that you connect your servers to need to be configured as trunk ports so they can accept tagged traffic for the appropriate VLAN from either the hypervisor or the VM. The network configuration of each VM allows you to specify the VLAN tag that gets applied.

Which device is routing between VLANs? If it is your firewall then you need to connect it as a trunk to your switches. If the switches are doing the routing and only a single vlan connects the switches to the firewall I would not tag the traffic from the firewall and just set the correct vlan access on the switch.

I would LAG the two switches together over trunk ports so that there is greater bandwidth between the switches and greater availability should a port or cable fail.
0
 

Author Comment

by:jfeucht
ID: 40507745
Thanks for the input.  Im still not sure how to configure them... we did create trunk ports but did not create the vlans.  Im assuming that we have to apply ports to the vlans.  can we add multiple vlans to each port?  I would need each port to be aware of every vlan.  Also, you mention that we need to set the VM to be aware of its vlan, so im assuming there is an option to setup tagging at the VM level.  There is an option to set the vlan in the firewall to enable tagging as well.
thanks
0
 
LVL 42

Accepted Solution

by:
kevinhsieh earned 500 total points
ID: 40508430
You need to create VLANs, that should be a separate step.

Configuring a trunk port tells the switch that multiple VLANs are acceptable on that port. It can either accept traffic tagged for every VLAN, or you might be able to limit to specific permitted VLANs (for example, say your DMZ was on a VLAN, you wouldn't necessarily want any your host or VMs to be able to communicate on the DMZ through a trunk port. I would suggest dedicated NIC and port on the switch for DMZ).

If you add every VLAN to a port, it needs to be a trunk port.

The VLAN tagging is a per VM vNIC option.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now