thank you much for the doc but fundamentally there is still one question that needs an answer first. On the 6248, are the four SFP+ ports in the front of switch supposed to be used for 10GB? Versus you add on a module like this
on the back of the 6248 and make your 10GB SFP connection in the back, not the front. That is one thing that the doc you provide is not clear as to where on the switch are the physical connection actually occur at
OK, I got the proper 10G module install on the back of the 6248. Now I got good connectivity between the dell powerconnect 6248 and my 10G link on the NAS server. However, I am running into a routing problem and need some advise as to why it is not routing
I have a SonicWall TZ-400 (192.168.10.2) connect to port 1 on the 6248 (it is set to vlan10 - vlan interface of 192.168.10.1). The default route on the switch is set to 0.0.0.0 out to 192.168.10.2. I have my PC/laptop connected to port 10 and it is also set to vlan10
I added vlan 200 with vlan interface set to 192.168.200.1 It is set on port xg3
PC6248#show run !Current Configuration: !System Description "PowerConnect 6248, 3.3.10.3, VxWorks 6.5" !System Software Version 3.3.10.3 !Cut-through mode is configured as disabled ! configure vlan database vlan 10,200 vlan routing 10 1 vlan routing 200 2 vlan association subnet 192.168.10.0 255.255.255.0 10 vlan association subnet 192.168.200.0 255.255.255.0 200 exit snmp-server location "HQ" snmp-server contact "Dominic Chan"
hostname "PC6248" sntp broadcast client enable sntp client poll timer 128 sntp server 0.us.pool.ntp.org sntp server 1.us.pool.ntp.org clock timezone -5 minutes 0 zone "est" stack member 1 2 member 2 2 exit switch 1 priority 12 switch 2 priority 11 ip address none ip domain-name tataoui.com ip name-server 8.8.8.8 ip name-server 209.18.47.61 ip routing ip route 0.0.0.0 0.0.0.0 192.168.10.2 ip helper-address 192.168.10.2 dhcp interface vlan 10 name "PC-Mobile clients" routing ip address 192.168.10.1 255.255.255.0 ip rip ip irdp exit interface vlan 200 name "iSCSI Storage" routing ip address 192.168.200.1 255.255.255.0 ip rip ip irdp exit interface ethernet 1/g1 description "WAN (SonicWall) Uplink" switchport access vlan 10 exit interface ethernet 1/xg3 spanning-tree portfast switchport access vlan 200 exit
On the PowerConnect 6248, I can ping to all the IP
However, on either the SonicWall or the PC, all traffic stop at 192.168.200.1, and can't reach or ping to 192.168.200.10. I opened up a case with SonicWall and did a packet trace, and it show the traffic stop at 192.168.200.1 So what parameter / syntax am I missing on the 6248 to reach the last mile?
This is the current routing table on the switch
Network Address Subnet Mask Protocol Next Hop Interface Next Hop IP Address
Are you implying that I trunk the link between the SonicWall and 6248? Currently, there is no VLAN tagging setup on the SonicWall, nor do I need to based on feedback from SonicWall. Also, I did another test where I enable VLAN 200 on port 42 (standard ethernet port). I connect a laptop with IP set to 192.168.200.11, and it was able to ping without any issue. So now I am wondering why it works with port 42 1/g42 but not the 10G (xg3). Is there additional configuration or limitation one must set for 10G module ports?
Yes I can. I think the problem is that the endpoint is dual home. so it depend on which segment I started the ping, it expect the gateway to be from that vlan interface.
DELL-Marco B
Moderator
•
4K Posts
0
January 18th, 2021 07:00
Hello,
I suggest you to keep an eye on this documentation:
https://dell.to/2CefM5f
How leds are on the ports?
We cannot guarantee that the SFP+ cable is compatible with the server.
Can you check also with firmware is installed on the switch?
Thanks
Marco
dwchan69
21 Posts
0
January 18th, 2021 11:00
thank you much for the doc but fundamentally there is still one question that needs an answer first. On the 6248, are the four SFP+ ports in the front of switch supposed to be used for 10GB? Versus you add on a module like this
https://www.ebay.com/itm/Dell-U691D-2-Port-10GB-SFP-Module-for-PowerConnect-6248/284152221888?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m2763.l2649
on the back of the 6248 and make your 10GB SFP connection in the back, not the front. That is one thing that the doc you provide is not clear as to where on the switch are the physical connection actually occur at
DELL-Sam L
Moderator
•
7.8K Posts
0
January 18th, 2021 12:00
Hello dwchan69,
Here is the link to the users guide for your powerconnect 6248 that will explain more about the ports. https://dell.to/39DRdxC
dwchan69
21 Posts
0
February 1st, 2021 10:00
OK, I got the proper 10G module install on the back of the 6248. Now I got good connectivity between the dell powerconnect 6248 and my 10G link on the NAS server. However, I am running into a routing problem and need some advise as to why it is not routing
I have a SonicWall TZ-400 (192.168.10.2) connect to port 1 on the 6248 (it is set to vlan10 - vlan interface of 192.168.10.1). The default route on the switch is set to 0.0.0.0 out to 192.168.10.2. I have my PC/laptop connected to port 10 and it is also set to vlan10
I added vlan 200 with vlan interface set to 192.168.200.1 It is set on port xg3
PC6248#show run
!Current Configuration:
!System Description "PowerConnect 6248, 3.3.10.3, VxWorks 6.5"
!System Software Version 3.3.10.3
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 10,200
vlan routing 10 1
vlan routing 200 2
vlan association subnet 192.168.10.0 255.255.255.0 10
vlan association subnet 192.168.200.0 255.255.255.0 200
exit
snmp-server location "HQ"
snmp-server contact "Dominic Chan"
hostname "PC6248"
sntp broadcast client enable
sntp client poll timer 128
sntp server 0.us.pool.ntp.org
sntp server 1.us.pool.ntp.org
clock timezone -5 minutes 0 zone "est"
stack
member 1 2
member 2 2
exit
switch 1 priority 12
switch 2 priority 11
ip address none
ip domain-name tataoui.com
ip name-server 8.8.8.8
ip name-server 209.18.47.61
ip routing
ip route 0.0.0.0 0.0.0.0 192.168.10.2
ip helper-address 192.168.10.2 dhcp
interface vlan 10
name "PC-Mobile clients"
routing
ip address 192.168.10.1 255.255.255.0
ip rip
ip irdp
exit
interface vlan 200
name "iSCSI Storage"
routing
ip address 192.168.200.1 255.255.255.0
ip rip
ip irdp
exit
interface ethernet 1/g1
description "WAN (SonicWall) Uplink"
switchport access vlan 10
exit
interface ethernet 1/xg3
spanning-tree portfast
switchport access vlan 200
exit
On the PowerConnect 6248, I can ping to all the IP
192.168.10.2 (SonicWall Router)
192.168.10.1 (VLAN 10 Interface)
192.168.10.126 (PC Client)
192.168.200.1 (VLAN 200 Interface)
192.168.200.10 (VLAN 200 endpoints - server)
However, on either the SonicWall or the PC, all traffic stop at 192.168.200.1, and can't reach or ping to 192.168.200.10. I opened up a case with SonicWall and did a packet trace, and it show the traffic stop at 192.168.200.1 So what parameter / syntax am I missing on the 6248 to reach the last mile?
This is the current routing table on the switch
Network Address Subnet Mask Protocol Next Hop Interface Next Hop IP Address
DELL-Josh Cr
Moderator
•
9.5K Posts
0
February 1st, 2021 11:00
Hi,
Try changing the port from the switch to the sonicwall from access to trunk so it can carry both VLANs.
dwchan69
21 Posts
0
February 1st, 2021 12:00
Are you implying that I trunk the link between the SonicWall and 6248? Currently, there is no VLAN tagging setup on the SonicWall, nor do I need to based on feedback from SonicWall. Also, I did another test where I enable VLAN 200 on port 42 (standard ethernet port). I connect a laptop with IP set to 192.168.200.11, and it was able to ping without any issue. So now I am wondering why it works with port 42 1/g42 but not the 10G (xg3). Is there additional configuration or limitation one must set for 10G module ports?
DELL-Josh Cr
Moderator
•
9.5K Posts
0
February 1st, 2021 13:00
Can you ping from the 192.168.200.11 address to the 192.168.200.10 address?
dwchan69
21 Posts
0
February 5th, 2021 11:00
Yes I can. I think the problem is that the endpoint is dual home. so it depend on which segment I started the ping, it expect the gateway to be from that vlan interface.
Olipoppin
1 Message
0
July 31st, 2022 13:00
All the links in these forums are useless -_-