Issues with LLDP-MED between 5320's and Juniper switch

[unclerico]

After almost two years away from Mitel gear I am back!! My new company is installing 3300's replacing a few aging PBX's at about 30 locations so this is fun. Anyways, we are installing a 3300 and about 15 5320 IP sets and we are running into issues with LLDP-MED values being sent by the 5320's to our Juniper switches. Juniper validates all LLDP frames so if one of the mandatory TLV's is not compliant or missing it will log an error and discard; in this case it is the Type 1 TLV (Chassis ID). When I fire up a new 5320 fresh out of the box there are no LLDP issues; the phone gets its proper voice VLAN assigned as well as DSCP/.1p values and from there is proceeds to update the firmware. The problem arises after the phone reboots from the firmware update. Once it reboots I see VLAN None Priority None and then it proceeds to grab an IP address from the data VLAN via DHCP (3300 is the DHCP server for the phones, while Windows manages DHCP for everything else). About three minutes later all of the sudden the Chassis ID TLV that is sent via LLDP from the phone is populated correctly and then the phone registers properly. Take a look at some pcap output from a monitor session one of the Juniper switches:

First one is from a phone fresh out of the box:

15:40:40.966241 In LLDP, length 315
Chassis ID TLV (1), length 6
Subtype Network address (5): AFI IPv4 (1): 0.0.0.0
Port ID TLV (2), length 7
Subtype MAC address (3): 08:00:0f:6c:e5:62
Time to Live TLV (3), length 2: TTL 10s
Port Description TLV (4), length 8: LAN port
System Name TLV (5), length 13: MITEL 5320 DM
System Description TLV (6), length 76
MITEL 5320 DM,h/w rev 0,ASIC rev 1,f/w Boot 04.00.01.09,f/w Main 04.00.01.09
System Capabilities TLV (7), length 4
System Capabilities [Bridge, Telephone] (0x0024)
Enabled Capabilities [Bridge, Telephone] (0x0024)
Management Address TLV (8), length 14
Management Address length 7, AFI 802 (6): 08:00:0f:6c:e5:62
Unknown Interface Numbering (1): 0

Here's what it looks like once it grabs an IP:

15:41:29.964216 In LLDP, length 313
Chassis ID TLV (1), length 6
Subtype Network address (5): AFI IPv4 (1): 172.16.42.73
Port ID TLV (2), length 7
Subtype MAC address (3): 08:00:0f:6c:e5:62
Time to Live TLV (3), length 2: TTL 10s
Port Description TLV (4), length 8: LAN port
System Name TLV (5), length 13: MITEL 5320 DM
System Description TLV (6), length 76
MITEL 5320 DM,h/w rev 0,ASIC rev 1,f/w Boot 04.00.01.09,f/w Main 04.00.01.09
System Capabilities TLV (7), length 4
System Capabilities [Bridge, Telephone] (0x0024)
Enabled Capabilities [Bridge, Telephone] (0x0024)
Management Address TLV (8), length 12
Management Address length 5, AFI IPv4 (1): 172.16.42.73
Unknown Interface Numbering (1): 0

Now, here's what it looks like once the firmware has been updated:

15:43:14.521911 In LLDP, length 315
Chassis ID TLV (1), length 6
Subtype Network address (5): AFI Reserved (0), no AF printer !
Port ID TLV (2), length 7
Subtype MAC address (3): 08:00:0f:6c:e5:62
Time to Live TLV (3), length 2: TTL 10s
Port Description TLV (4), length 8: LAN port
System Name TLV (5), length 13: MITEL 5320 IP
System Description TLV (6), length 76
MITEL 5320 IP,h/w rev 0,ASIC rev 1,f/w Boot 05.01.00.13,f/w Main 05.01.00.16
System Capabilities TLV (7), length 4
System Capabilities [Bridge, Telephone] (0x0024)
Enabled Capabilities [Bridge, Telephone] (0x0024)
Management Address TLV (8), length 14
Management Address length 7, AFI 802 (6): 08:00:0f:6c:e5:62
Unknown Interface Numbering (1): 0

Let me know if you have any ideas. Thanks ahead of time.

 

[skibby1981]

The only thing I can think of is to go into the 3300 DHCP options and verify the proper vlan info for the phones is entered into option 125. In the latest firmware, Mitel changed how vlans are handled to conform with industry standards. If you're using switches with vlanning and option 125 doesn't have the correct info filled out, you get those long timeouts.