<
Switches
Strange ethertype 0x9900, 802.1q missed communication
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Strange ethertype 0x9900, 802.1q missed communication
Posts: 2
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-06-13
2016-06-18 19:30:27
Posts: 2
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-06-13
Strange ethertype 0x9900, 802.1q missed communication
2016-06-18 19:30:27
Tags:
Model :
Hardware Version :
Firmware Version :
ISP :
Hardware Version :
Firmware Version :
ISP :
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
2 Reply
Posts: 2
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-06-13
Strange ethertype 0x9900, 802.1q missed communication
2016-06-18 19:36:39
Model :
Hardware Version :
Firmware Version :
ISP :
Hello
I have some switches SG3216. I have some problems with them becouse they are all connected to one HP-1620-24g as a central switch in star topology. All uplinks are 802.1q tagged interfaces which carried some vlan tags. Sometime communication missed and i have no connection to this switch. After reboot everything is fine. I have active loop detectd, broadcast and multicast storm limited to 128k, dhcp-snooping and stp disabled on all network becouse i dont have redundant connections. All 802.1q sub-interfaces are terminated on Debian Linux machine when i have inter-vlan routing. When i run tcpdump i get something like this:
[CODE]
13:04:47.523104 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype Unknown (0x9900), length 60:
0x0000: 0000 60e3 27f2 eba4 0000 0001 52a7 284e ..`.'.......R.(N
0x0010: 39e4 efbf 6713 46e7 303f d29d 0000 0000 9...g.F.0?......
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:47.523439 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64:
0x0000: 0000 60e3 27f2 eba4 0000 0014 54dc ee06 ..`.'.......T...
0x0010: e1a3 14a4 bf36 8f53 9140 2112 0000 0000 .....6.S.@!.....
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:47.523740 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64:
0x0000: 0000 60e3 27f2 eba4 0000 0028 c4fe 5663 ..`.'......(..Vc
0x0010: b13c 616a 30b0 b7bc d8d3 82e6 0000 0000 . 0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:47.524028 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64:
0x0000: 0000 60e3 27f2 eba4 0000 0032 f3e4 7e57 ..`.'......2..~W
0x0010: 0845 cec7 5260 2316 62fc b8e7 0000 0000 .E..R`#.b.......
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:48.098097 ARP, Request who-has 192.168.50.200 tell 192.168.50.1, length 28
[/CODE]
The 60:e3:27:f2:eb:a4 is mac-address of SG3216. Looks like tp-link use unrecognized format of 802.1q ethertype? I haven't find 0x9900 on any ieee ethertypes list.
Hardware Version :
Firmware Version :
ISP :
Hello
I have some switches SG3216. I have some problems with them becouse they are all connected to one HP-1620-24g as a central switch in star topology. All uplinks are 802.1q tagged interfaces which carried some vlan tags. Sometime communication missed and i have no connection to this switch. After reboot everything is fine. I have active loop detectd, broadcast and multicast storm limited to 128k, dhcp-snooping and stp disabled on all network becouse i dont have redundant connections. All 802.1q sub-interfaces are terminated on Debian Linux machine when i have inter-vlan routing. When i run tcpdump i get something like this:
[CODE]
13:04:47.523104 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype Unknown (0x9900), length 60:
0x0000: 0000 60e3 27f2 eba4 0000 0001 52a7 284e ..`.'.......R.(N
0x0010: 39e4 efbf 6713 46e7 303f d29d 0000 0000 9...g.F.0?......
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:47.523439 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64:
0x0000: 0000 60e3 27f2 eba4 0000 0014 54dc ee06 ..`.'.......T...
0x0010: e1a3 14a4 bf36 8f53 9140 2112 0000 0000 .....6.S.@!.....
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:47.523740 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64:
0x0000: 0000 60e3 27f2 eba4 0000 0028 c4fe 5663 ..`.'......(..Vc
0x0010: b13c 616a 30b0 b7bc d8d3 82e6 0000 0000 . 0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:47.524028 60:e3:27:f2:eb:a4 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64:
0x0000: 0000 60e3 27f2 eba4 0000 0032 f3e4 7e57 ..`.'......2..~W
0x0010: 0845 cec7 5260 2316 62fc b8e7 0000 0000 .E..R`#.b.......
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
13:04:48.098097 ARP, Request who-has 192.168.50.200 tell 192.168.50.1, length 28
[/CODE]
The 60:e3:27:f2:eb:a4 is mac-address of SG3216. Looks like tp-link use unrecognized format of 802.1q ethertype? I haven't find 0x9900 on any ieee ethertypes list.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#2
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 39
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2015-11-09
Re:Strange ethertype 0x9900, 802.1q missed communication
2016-06-29 09:42:29
I am not very sure about your problem, but I am sure the TL-SG3216 supports 802.1q VLAN. You can contact their supporter directly for help.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#3
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 2
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-06-13
2016-06-18 19:30:27
Posts: 2
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-06-13
Information
Helpful: 0
Views: 2054
Replies: 2
Voters 0
No one has voted for it yet.
Tags
Related Articles
Heartbeat missed
3159
0
Eap heartbeat missed
3712
0
802.1q VLAN not working
517
0
802.1q tagging issues
374
1
Report Inappropriate Content
Transfer Module
New message