Unsolved
This post is more than 5 years old
5 Posts
0
23939
January 9th, 2014 00:00
No network after enable teaming on PowerConnect 7048
Hello !
I try to enable a teaming connection between an Power Connect 7048 switch (stacked) to an Power Edge 720XD server. The server has an Intel Quad Port network card installed (Intel(R) Gigabit 4P I350-t-rNDC).
I do following settings on switch:
- define a LAG under ports/lag configuration
- activate the right ports under Link agragation/LAG Members (try out static and dynamic config)
- try out each LAG hashmode
- try out with and without spanning try settings
The follwing settings are set on the server:
- Installed the latest NIC driver and activate NIC teaming on netork port 2 and 3
- select IEEE 802.3ad Dynamic Link aggregation for dynamic mode
- try out static link aggragation with static mode
After configuration on dell switch i see that the current LAG status is UP. The check of the Intel card dos`nt shows any error or recomandation.
The network interfaces on the server showing Acitve in teaming configuration
And now the problem:
When i set the right IP Adress to the Team network interface i dont get any connection to the LAN. I ping to a componet and nothing happens.
What could i do?
BR
Patrick
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.2K Points
0
January 9th, 2014 07:00
Hi Patrick,
Do the NIC ports both work if they are not teamed? Does it show a status of up in dynamic mode? In static mode the assumption it makes is that is always up. Does the VLAN that it is connected to have an IP address assigned on the switch that you could try to ping? Have you tried using the adaptive load balancing feature on the team and not creating a LAG on the switch?
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.2K Points
0
January 9th, 2014 08:00
No there isn't anything different for configuring an IP when you are teamed. Do the individual nics still have IP addresses or were you clearing their IP configuration when the team is created? If the dynamic lag is showing up it is at least passing the LAG information between the switch and the NIC properly. If you use the show lacp command page 635 ftp://ftp.dell.com/Manuals/all-products/esuprt_ser_stor_net/esuprt_powerconnect/powerconnect-7048_Reference%20Guide_en-us.pdf It should confirm that the LAG is functional.
P_a_t_r_i_c_k
5 Posts
0
January 9th, 2014 08:00
Hi !
The NICs are working correct without teaming (Ping possible)
The status on switch shows up in dynamic or static configuartion.
is it neccessara to define an VLAN on the Intel Teaming Client. I tryed that out, but no succcess.
The Serer config is like that:
NiC 01 - Connection to LAN 10.145.25.0
NIC 02 - (phyical cabel to an separate switch 192.168.200.0) This NIC is teamed)
NIC 03 - (phyical cabel to an separate switch 192.168.200.0) This NIC is teamed)
Teamed NIC: IP 192.168.200.170 Subnet 255.255.255.0 no Gatway because its directly connected
NIC 04- not configured
Load Balance: i don´t try. I like to configure aggragation.
Is thee somting differnt in Ip condiguration when i config an teaming adapter?.
BR
Patrick
P_a_t_r_i_c_k
5 Posts
0
January 10th, 2014 02:00
Hi
Thanks for reply. I has checked that now and don´d find any issue.
Could this issue happen about the used switch firmware version?
I actually install RLB Mode now. This is working. Because it`s dosn´t needs any LACP configuration on switch.
Another question. Which teaming mode do you recomand to have the most throghput to the NIC. I like to use this to make backup and restores.
More important is the restore speed.
I have three 1 GB NIC available at the server.
BR
Patrick
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.2K Points
0
January 10th, 2014 07:00
What version is the firmware at? It probably wouldn't be a firmware issue but there might be security fixes that might still warrant a firmware update. If you can email me your running config I can make sure we are not missing something in the configuration. josha_craig@dell.com
RLB will be the fastest in your situation if you are doing multiple backups at the same time same as with the LAG hashing types Source MAC, VLAN, EtherType, and incoming port or Source IP and Source TCP/UDP port numbers. However if you are just getting one backup a time teaming or doing a LAG is not going to be a lot faster as it gives you more lanes for the data to travel down but if there is just one source of data it can only use one lane.