VLAN config, Dell 6224, not passing tagged packets xg4
Working for a WISP, trying to configure a Dell PowerConnect 6224 to pass both tagged and untagged packets. Was running as only untagged and service runs correctly. Some new equipment we are using requires a management vlan along with a customer data vlan. I have configured port xg4 (fiber port) as general with both the default untagged (1) and also with vlan tag 20. I have done the same to the additional ports that are required for our services to work. Port g23 is a backup line ran to our Ceragon radio equipment. The test piece of equipment only requires the management vlan, and must request DHCP from the EMS server. This is why I have not configured the customer vlan yet. I would like to see the requests coming back all the way to the server before enabling, as this requires me to move all of the customers to the new DHCP system. 1 step at a time, right?
To monitor this, I am watching for DHCP requests coming from a SkyPilot radio out in the field that is my test equipment. I see the DHCP requests coming back to the headend at the Ceragon but can not see the same requests at the switch using port mirroring of xg4 to g13, or when I set g13 as general and tagged as part of the same 20 vlan.
Below is a piece of the config file.
Thanks!
interface ethernet 1/g13
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g14
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g17
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g18
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
interface ethernet 1/g23
storm-control broadcast
storm-control multicast
sflow 1 sampling 1024
sflow 1 polling 30
spanning-tree portfast
mtu 9216
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g24
sflow 1 sampling 1024
sflow 1 polling 30
gvrp enable
switchport mode general
exit
!
interface ethernet 1/xg4
spanning-tree disable
switchport mode general
switchport general allowed vlan add 20 tagged
exit
To monitor this, I am watching for DHCP requests coming from a SkyPilot radio out in the field that is my test equipment. I see the DHCP requests coming back to the headend at the Ceragon but can not see the same requests at the switch using port mirroring of xg4 to g13, or when I set g13 as general and tagged as part of the same 20 vlan.
Below is a piece of the config file.
Thanks!
interface ethernet 1/g13
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g14
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g17
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g18
sflow 1 sampling 1024
sflow 1 polling 30
switchport mode general
switchport general allowed vlan add 20 tagged
exit
interface ethernet 1/g23
storm-control broadcast
storm-control multicast
sflow 1 sampling 1024
sflow 1 polling 30
spanning-tree portfast
mtu 9216
switchport mode general
switchport general allowed vlan add 20 tagged
exit
!
interface ethernet 1/g24
sflow 1 sampling 1024
sflow 1 polling 30
gvrp enable
switchport mode general
exit
!
interface ethernet 1/xg4
spanning-tree disable
switchport mode general
switchport general allowed vlan add 20 tagged
exit
ArneLovius
if VLAN 20 is only tagged on ports, then your DHCP server will need to also have the VLAN20 as a tagged port on the NIC...
ASKER
Correct, I wasn't seeing the requests at all across the switch and that was my goal at the time of my posting. I found that xg4 and g24 on the Dell switch are tied together, and so I needed to make my vlan tagging on g24, not the xg4 port.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for k_hoffhines's comment #a38801470
for the following reason:
The one answer posted by someone else was relevant, but did not answer the question I had asked. I found the solution myself.
Accepted answer: 0 points for k_hoffhines's comment #a38801470
for the following reason:
The one answer posted by someone else was relevant, but did not answer the question I had asked. I found the solution myself.
The two ports are not "tied together".
As there is no complete answer, I would not choose 2)
The OP's problem has apparently been solved, but the answer provided is not enough for anyone else to follow so I would not choose 3)
Therefore 1) Deletion would be my choice
I note that the 2nd paragraph says "Further, if you recommend #3 or #4, ", but there are only three options...
The OP's problem has apparently been solved, but the answer provided is not enough for anyone else to follow so I would not choose 3)
Therefore 1) Deletion would be my choice
I note that the 2nd paragraph says "Further, if you recommend #3 or #4, ", but there are only three options...
ASKER
I can clarify my answer, but I do not know specifically without talking to Dell that this is absolutely correct.
The 2 devices connected together (Ceragon IP10 and Dell PowerConnect 6224) are both 1000Mb, not 10G. Since port xg4 is a 10G, I am assuming that port g24, which is gigabit, becomes a "proxy" for xg4. I had to make my vlan configuration changes on g24, not on xg4, to resolve the problem I was having. After configuring port g24 in general mode and allowing my vlan 20 tag, I then began seeing the requests from the SkyPilot radio at the switch, which was my original question. I did leave the vlan configuration on xg4 also, so this may be a case in which you have to configure both ports to make it work. Again, without speaking to Dell support, I am unable to answer that with specifics.
The question asked is here in this paragraph:
"To monitor this, I am watching for DHCP requests coming from a SkyPilot radio out in the field that is my test equipment. I see the DHCP requests coming back to the headend at the Ceragon but can not see the same requests at the switch using port mirroring of xg4 to g13, or when I set g13 as general and tagged as part of the same 20 vlan."
The suggestion of the server isn't relevant to what I was looking for at the switch, although I do realize that to get to the server I was going to need to have the server on the vlan. I did appreciate that comment but did not answer my question.
The other answer posted after I closed the question:
"by: ArneLoviusPosted on 2013-01-21 at 13:41:49ID: 38802329
The two ports are not "tied together"."
Does not provide any answer to the question asked, nor does it provide additional information to educate me further as to how the ports work together in this situation.
The 2 devices connected together (Ceragon IP10 and Dell PowerConnect 6224) are both 1000Mb, not 10G. Since port xg4 is a 10G, I am assuming that port g24, which is gigabit, becomes a "proxy" for xg4. I had to make my vlan configuration changes on g24, not on xg4, to resolve the problem I was having. After configuring port g24 in general mode and allowing my vlan 20 tag, I then began seeing the requests from the SkyPilot radio at the switch, which was my original question. I did leave the vlan configuration on xg4 also, so this may be a case in which you have to configure both ports to make it work. Again, without speaking to Dell support, I am unable to answer that with specifics.
The question asked is here in this paragraph:
"To monitor this, I am watching for DHCP requests coming from a SkyPilot radio out in the field that is my test equipment. I see the DHCP requests coming back to the headend at the Ceragon but can not see the same requests at the switch using port mirroring of xg4 to g13, or when I set g13 as general and tagged as part of the same 20 vlan."
The suggestion of the server isn't relevant to what I was looking for at the switch, although I do realize that to get to the server I was going to need to have the server on the vlan. I did appreciate that comment but did not answer my question.
The other answer posted after I closed the question:
"by: ArneLoviusPosted on 2013-01-21 at 13:41:49ID: 38802329
The two ports are not "tied together"."
Does not provide any answer to the question asked, nor does it provide additional information to educate me further as to how the ports work together in this situation.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you ArneLovius, that is actually a great answer to the situation that I posted, and an even better description than I had written.
No, you didn't not say anything about IP helper in the switch.
Yes, I was using wireshark with the filter bootp.option.typ == 53 . I can see the requests coming from the radio across the network and could see them at the switch on the Ceragon IP10. I could not see them at the 6224 until I configured vlan 20 on port g24.
Yes, we used 1G SFPs.
I will be in contact with Dell support to better understand why the changes were required on port g24 to make this work as it could be a larger issue.
Again, thanks for the great reply. I was frustrated by the first reply from you about the two ports.
ArneLovius, ID: 38808221, can have the points for providing a clear description and relevant information.
No, you didn't not say anything about IP helper in the switch.
Yes, I was using wireshark with the filter bootp.option.typ == 53 . I can see the requests coming from the radio across the network and could see them at the switch on the Ceragon IP10. I could not see them at the 6224 until I configured vlan 20 on port g24.
Yes, we used 1G SFPs.
I will be in contact with Dell support to better understand why the changes were required on port g24 to make this work as it could be a larger issue.
Again, thanks for the great reply. I was frustrated by the first reply from you about the two ports.
ArneLovius, ID: 38808221, can have the points for providing a clear description and relevant information.