LLDP not working for polycom, but working for Cisco phones on x460-G2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-21-2015 03:31 PM
We have two phones, one Polycom VVW310 and a Cisco 7911 plugged into sequential ports on our stack. They are configured with the same LLDP configuration and the Cisco joins the proper voip network while the polycom does not. In the neighbor details, the only difference seems to be in the policy section. The polycom shows "unknown policy" and the cisco shows "known policy". Any ideas?
-----------------------------------------------------------------------------
LLDP Port 1:15 detected 1 neighbor
Neighbor: (5.1)0.0.0.0/00:04:F2:8C:4F:5D, age 59 seconds
- Chassis ID type: Network address (5); Address type: IPv4 (1)
Chassis ID : 0.0.0.0
- Port ID type: MAC address (3)
Port ID : 00:04:F2:8C:4F:5D
- Time To Live: 120 seconds
- Port Description: "1"
- System Name: "Polycom VVX 310"
- System Description: "Polycom;VVX-VVX_310;3111-46161-001,2;SIP/4.1.8.06\
28/30-Sep-14 00:40;UP/5.1.8.0598/30-Sep-14 01:08;"
- System Capabilities : "Bridge, Telephone"
Enabled Capabilities: "Telephone"
- IEEE802.3 MAC/PHY Configuration/Status
Auto-negotiation : Supported, Enabled (0x03)
Operational MAU Type : 1000BaseTFD (30)
- MED Capabilities: "MED Capabilities, Network Policy, Extended Power via MDI - PD, Inventory"
MED Device Type : Endpoint Class III (3)
- MED Network Policy
Application Type : Voice (1)
Policy Flags : Unknown Policy, Untagged (0x0)
VLAN ID : 0
L2 Priority : 5
DSCP Value : 46
- MED Network Policy
Application Type : Voice Signaling (2)
Policy Flags : Unknown Policy, Untagged (0x0)
VLAN ID : 0
L2 Priority : 5
DSCP Value : 44
- MED Extended Power-via-MDI
Power Type : PD Device (1)
Power Source : PSE and Local (3)
Power Priority: Unknown (0)
Power Value : 5.0 Watts
- MED Hardware Revision: "3111-46161-001,2"
- MED Firmware Revision: "UP/5.1.8.0598/30-Sep-14 01:08"
- MED Software Revision: "SIP/4.1.8.0628/30-Sep-14 00:40"
- MED Serial Number: "0004f28c4f5d"
- MED Manufacturer Name: "Polycom"
- MED Model Name: "VVX-VVX_310"
- MED Asset ID: ""
LLDP Port 1:16 detected 1 neighbor
Neighbor: (5.1)10.91.0.30/002584178E5F:P1, age 24 seconds
- Chassis ID type: Network address (5); Address type: IPv4 (1)
Chassis ID : 10.91.0.30
- Port ID type: Locally assigned (7)
Port ID : "002584178E5F:P1"
- Time To Live: 180 seconds
- Port Description: "SW PORT"
- System Name: "SEP002584178E5F"
- System Description: "Cisco IP Phone CP-7911G,V8, SCCP11.8-4-4S"
- System Capabilities : "Bridge, Telephone"
Enabled Capabilities: "Bridge, Telephone"
- Management Address Subtype: IPv4 (1)
Management Address : 10.91.0.30
Interface Number Subtype : Unknown (1)
Interface Number : 0
Object ID String : "null"
- IEEE802.3 MAC/PHY Configuration/Status
Auto-negotiation : Supported, Enabled (0x03)
Operational MAU Type : 100BaseTXFD (16)
- MED Capabilities: "MED Capabilities, Network Policy, Extended Power via MDI - PD, Inventory"
MED Device Type : Endpoint Class III (3)
- MED Network Policy
Application Type : Voice (1)
Policy Flags : Known Policy, Tagged (0x1)
VLAN ID : 900
L2 Priority : 5
DSCP Value : 46
- MED Network Policy
Application Type : Voice Signaling (2)
Policy Flags : Known Policy, Tagged (0x1)
VLAN ID : 900
L2 Priority : 4
DSCP Value : 32
- MED Extended Power-via-MDI
Power Type : PD Device (1)
Power Source : Unknown (0)
Power Priority: Unknown (0)
Power Value : 5.0 Watts
- MED Hardware Revision: "8"
- MED Firmware Revision: "tnp11.3-0-1-32.bin"
- MED Software Revision: "SCCP11.8-4-4S"
- MED Serial Number: "FCH132097PD"
- MED Manufacturer Name: "Cisco Systems, Inc."
- MED Model Name: "CP-7911G"
- MED Asset ID: ""
-----------------------------------------------------------------------------
LLDP Port 1:15 detected 1 neighbor
Neighbor: (5.1)0.0.0.0/00:04:F2:8C:4F:5D, age 59 seconds
- Chassis ID type: Network address (5); Address type: IPv4 (1)
Chassis ID : 0.0.0.0
- Port ID type: MAC address (3)
Port ID : 00:04:F2:8C:4F:5D
- Time To Live: 120 seconds
- Port Description: "1"
- System Name: "Polycom VVX 310"
- System Description: "Polycom;VVX-VVX_310;3111-46161-001,2;SIP/4.1.8.06\
28/30-Sep-14 00:40;UP/5.1.8.0598/30-Sep-14 01:08;"
- System Capabilities : "Bridge, Telephone"
Enabled Capabilities: "Telephone"
- IEEE802.3 MAC/PHY Configuration/Status
Auto-negotiation : Supported, Enabled (0x03)
Operational MAU Type : 1000BaseTFD (30)
- MED Capabilities: "MED Capabilities, Network Policy, Extended Power via MDI - PD, Inventory"
MED Device Type : Endpoint Class III (3)
- MED Network Policy
Application Type : Voice (1)
Policy Flags : Unknown Policy, Untagged (0x0)
VLAN ID : 0
L2 Priority : 5
DSCP Value : 46
- MED Network Policy
Application Type : Voice Signaling (2)
Policy Flags : Unknown Policy, Untagged (0x0)
VLAN ID : 0
L2 Priority : 5
DSCP Value : 44
- MED Extended Power-via-MDI
Power Type : PD Device (1)
Power Source : PSE and Local (3)
Power Priority: Unknown (0)
Power Value : 5.0 Watts
- MED Hardware Revision: "3111-46161-001,2"
- MED Firmware Revision: "UP/5.1.8.0598/30-Sep-14 01:08"
- MED Software Revision: "SIP/4.1.8.0628/30-Sep-14 00:40"
- MED Serial Number: "0004f28c4f5d"
- MED Manufacturer Name: "Polycom"
- MED Model Name: "VVX-VVX_310"
- MED Asset ID: ""
LLDP Port 1:16 detected 1 neighbor
Neighbor: (5.1)10.91.0.30/002584178E5F:P1, age 24 seconds
- Chassis ID type: Network address (5); Address type: IPv4 (1)
Chassis ID : 10.91.0.30
- Port ID type: Locally assigned (7)
Port ID : "002584178E5F:P1"
- Time To Live: 180 seconds
- Port Description: "SW PORT"
- System Name: "SEP002584178E5F"
- System Description: "Cisco IP Phone CP-7911G,V8, SCCP11.8-4-4S"
- System Capabilities : "Bridge, Telephone"
Enabled Capabilities: "Bridge, Telephone"
- Management Address Subtype: IPv4 (1)
Management Address : 10.91.0.30
Interface Number Subtype : Unknown (1)
Interface Number : 0
Object ID String : "null"
- IEEE802.3 MAC/PHY Configuration/Status
Auto-negotiation : Supported, Enabled (0x03)
Operational MAU Type : 100BaseTXFD (16)
- MED Capabilities: "MED Capabilities, Network Policy, Extended Power via MDI - PD, Inventory"
MED Device Type : Endpoint Class III (3)
- MED Network Policy
Application Type : Voice (1)
Policy Flags : Known Policy, Tagged (0x1)
VLAN ID : 900
L2 Priority : 5
DSCP Value : 46
- MED Network Policy
Application Type : Voice Signaling (2)
Policy Flags : Known Policy, Tagged (0x1)
VLAN ID : 900
L2 Priority : 4
DSCP Value : 32
- MED Extended Power-via-MDI
Power Type : PD Device (1)
Power Source : Unknown (0)
Power Priority: Unknown (0)
Power Value : 5.0 Watts
- MED Hardware Revision: "8"
- MED Firmware Revision: "tnp11.3-0-1-32.bin"
- MED Software Revision: "SCCP11.8-4-4S"
- MED Serial Number: "FCH132097PD"
- MED Manufacturer Name: "Cisco Systems, Inc."
- MED Model Name: "CP-7911G"
- MED Asset ID: ""
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-27-2015 04:02 PM
I will take a look after the holiday when the client returns. The configuration is the "standard" suggested by Extreme in several posts here on the hub and in technotes. Nothing fancy... Polycom just seems to stay on the default VLAN no matter what. I'll grab the trace and upload after the new year. Thanks for the offer of assistance. I too am not an LLDP expert and not sure where else to look...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-27-2015 04:02 PM
http://support.polycom.com/content/dam/polycom-support/products/Voice/business_media_phones/user/en/...
This is covered under the "Configuring LLDP Fast Start Count" section in the above document link from Polycom
This is covered under the "Configuring LLDP Fast Start Count" section in the above document link from Polycom
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-27-2015 04:02 PM
There was a similar issue on the Polycom VVX 410 VoIP phone, see the following article:-
https://gtacknowledge.extremenetworks.com/articles/Solution/Polycom-VoIP-Phone-not-obtaining-DHCP-IP...
https://gtacknowledge.extremenetworks.com/articles/Solution/Polycom-VoIP-Phone-not-obtaining-DHCP-IP...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-27-2015 04:02 PM
Do you have new information about that? I have the same issue.
