Web and Unmanaged
cancel
Showing results for 
Search instead for 
Did you mean: 

Packets from 1810G management "CPU" not tagged

Leenmark
Occasional Visitor

Packets from 1810G management "CPU" not tagged

Configured "Management VLAN id"=10. No connectivity to switch via tagged port.

 

Packet capture on connected device shows packets sent to switch tagged, but response is not tagged.

 

Example ARP resolution (.240 and .241 are 1801G-24 resp 1810G-8);

 

 

21:08:38.190012 e6:07:34:d9:ce:79 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 10, p 0, ethertype ARP, Request who-has 192.168.10.240 tell 192.168.10.254, length 28
21:08:38.190179 e6:07:34:d9:ce:79 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 10, p 0, ethertype ARP, Request who-has 192.168.10.241 tell 192.168.10.254, length 28
21:08:38.193285 b4:39:d6:c6:c7:f0 > e6:07:34:d9:ce:79, ethertype ARP (0x0806), length 64: Reply 192.168.10.241 is-at b4:39:d6:c6:c7:f0, length 50
21:08:38.193548 b4:39:d6:ce:47:c0 > e6:07:34:d9:ce:79, ethertype ARP (0x0806), length 64: Reply 192.168.10.240 is-at b4:39:d6:ce:47:c0, length 50

 

 

Is additional configuration needed? Bug?

Switches are 1 week old and at Software version P.1.17.

 

Pls advise. TXS!

2 REPLIES
jefflj
Frequent Advisor

Re: Packets from 1810G management "CPU" not tagged

Are the ports that connect the 1810 to the network tagged members of vlan 10?  Looking through the web Interface you should see (assume your uplink is port 12):

 

1) On the "Home" => "Network Setup" page, in the Management Access area, the Management VLAN ID should be set to 10. 

2) On the "VLANs" => "VLAN Configuration" page you should see at least 2 vlans, vlan 1 and vlan 10.  if not, in the VLAN area, select "Create VLAN", set "Create VLAN ID" to 10, and click the "Apply" button.

3)On the "VLANs" => "Participation/Tagging" page, set the "VLAN" pulldown to 10, then, in the port display below, the letter under the number of the uplink port (port 12, in this example) should be a "T", if not, click the letter until it changes to a "T".  Add any other ports to VLAN 10 that you want to, either "U" for untagged members, or :"T" for tagged members, and click the "Apply" button.

Remember, your uplink port should be a member of all VLANs that you want to connect to other parts of your network, and only one port can be an untagged member  of any VLAN, attempting to add a second untagged port as a member of a VLAN will cause the first port to be excluded from that VLAN...

Best practice is to have an uplink port be a tagged member of all uplinked VLANs

NdK
Occasional Visitor

Re: Packets from 1810G management "CPU" not tagged

I just stumbled in the same error.

1810G-8, 2 VLANs (1=default, 2=management).

Port 1 is configured for vlan1=tagged, vlan2=untagged.

Ports 2-8 are configured "reversed" (1=untagged, 2=tagged).

Once I set VLAN2 as management VLAN, I can only access management if I connect to port 1, even if my card is correctly configured to send packets for management network to vlan 2.

 

To me it smells like a firmware bug :( And it would be the second I find on the 1810.