voice vlan #339
Comments
|
You can use |
Thank you for your reply！ 1.Start the lldpd root@rk3188:/ # lldpd -v root@rk3188:/ # lldpd -ddddd -M 3 2019-08-09T21:12:20 [ DBG/main] lldpd 1.0.4-9-g9b68a67-dirty starting... 2.Then follow your orders, execution command returns immediately without any information being output. 1|root@rk3188:/ # lldpctl -d -f keyvalue show neighbors details | grep policy but lldpd output the following information 2019-08-09T21:32:11 [ DBG/control] accept a new connection In addition, the lldpd configuration information is as follows root@rk3188:/ # lldpcli show configuration Global configuration: Please give me more detailed instructions, Thanks a lot! |
|
Did you use |
yes, I have tried this command before |
|
Actually, I don't understand a lot about the implementation of voice vlan. Can you introduce the process? Above, hope to get your help, thank you very much! |
|
LLDP is just providing a piece of information. You can advertise the VLAN number to a neighbor with the |
|
show neigh details is as above, but there is no voice vlan information.
Thank you for your help all the time！ |
|
What you are highlighting is a regular VLAN (a TLV sent as part of 802.1AB, Dot1). It seems your remote equipment is not sending the LLDP-MED policy you are expecting. Is it configured to? |
|
Hello, Vincent I have some new discoveries, by comparing network packet capture data with SNOM devices (SNOM is a device that can send voice data through voice VLAN), we found that there is no media part in the data received by our rk3188 devices. The capture file has been uploaded, I don't know what causes the lack of information. please take a look at it. Thank you. RK3188 capture info: SNOM capture info: |
|
Did you try with different values for |
|
According to commands help doc: -M class Enable emission of LLDP-MED frame. 'class' should be one of: I've tried the following commands, received TLVs from the other side remains unchanged. lldpd -ddddd -M 2 [lldpcli] # configure med policy application voice Do I understand your meaning correctly? Is it used in this way? thanks a lot! |
|
If you can get a capture of what the SNOM device is sending to get back the LLDP-MED TLV, we could compare with what lldpd is sending. |
|
OK, that's a good idea.
|
|
And if lldpd is not running, do you receive the appropriate TLV? You may have to link down/link up to let the other side knows there is a new device. |
|
（1）If lldpd isn't started, the device doesn't receive lldp data sent by the switch. |
|
If there is no specific configuration for the port where the SNOM device is, I don't have a clue on why it would get a LLDP frame with LLDP-MED TLVs. |
|
Hello, Vincent I have captured all the data packets between the SNOM device and the switch, please help me to look at some of the existing problems. First, the TAG ID we need to get from the switch is 1085, and the IP address of voice VLAN is 172.20.85.10.
(1) The first lldp packet （No.547） comes from the switch, and there is no LLDP-MED TLVs information in it. (3) Snom's second lldp broadcast packet also carries the IP address (172.20.85.10.) of vlan. I don't know how to get this IP address. |
|
From your capture, I don't see anything related to LLDP-MED from the H3C switch. To be honest, I don't even know who should send the network policy TLV. From your capture, it seems it's the phone that should send it. I don't know either where the 1085 VLAN comes from. Maybe it's a configuration parameter from the phone? Or maybe it did remember the value from a previous boot? As for the IP address, the device gets it from a DHCP request on VLAN 1085 (frame 1302). |
|
Hello, Vincent For the time being, we don't consider how 1085 was acquired. Would you please help us to see how to carry lldp-med information like snom's Frame No.316? https://wiki.wireshark.org/LinkLayerDiscoveryProtocol Thanks a lot! |
|
Please ignore the above. I have known how to insert lldp-med TVLs information. lldpcli configure ports eth0 med policy application voice vlan 1085 priority voice dscp 46 The following information is carried by the RK3188 packet： In addition, compare the snom packet and how to configure some other missing information, such as: Extended Power-via-MDI, Hardware Revision, Firmware Revision, Serial Number, Manufacturer Name, Model Name, Asset ID. |
|
To set tagged to yes, you have to add |
|
Hello, Vincent: Please help me, how to configuration to disable MDI-PSE. Thanks very much! change the values capable to not capable. |
|
It's currently not possible. You can patch the source. Search for |
|
|
You get it with |
great！Could you please tell me the exact source location of the corresponding code executed by the above command? thanks a lot! |
Hello, Vincent
I hope to simplify VoIP deployment by supporting Voice VLAN, our voice device is based on android 4.4, LLDP has been compiled successfully and is running well.
root@rk3188:/ # lldpcli -help
Usage: lldpcli [OPTIONS ...] [COMMAND ...]
Version: lldpd 1.0.4-9-g9b68a67-dirty
-d Enable more debugging information.
-u socket Specify the Unix-domain socket used for communication with lldpd(8).
-f format Choose output format (plain, keyvalue, json, json0).
-c conf Read the provided configuration file.
see manual page lldpcli(8) for more information
But I don't know what to do next, How to get tag ID of voice VLAN ?
Here's what I learned about other similar problems：
lldp-med #145
The result of my attempt:
130|root@rk3188:/ # lldpcli -d
[lldpcli] # conf med policy application voice vlan 4088 priority voice
2019-08-08T21:42:40 [INFO/lldpctl] LLDP-MED policy has been set for port eth0
After receiving the lldp packet with vlan, vlan will be automatically stripped? #319
I was wondering if I would need to change the implementation code ？
I look forward to your answer, thank you very much!
The text was updated successfully, but these errors were encountered: