Question

Mitel UC360 Phone

  • 2 August 2019
  • 2 replies
  • 68 views

Userlevel 1
My Mitel UC360 conference phones are coming up on the wrong VLAN. I have other Mitel handsets, like the 5320, that work just fine.

My switching is configured so that the computer VLAN is untagged and the voice VLAN is tagged. This works perfectly for all of my handsets, but not the conference phones.

My switches are configured to look for DSCP value of 46. According to the switch, the UC360 is reporting DSCP values of 46 and the VLAN ID is that of my voice VLAN. However, it gets an IP address on my computer network. I'm not sure how the phone's LLDP status shows the appropriate voice VLAN, but the computer VLAN takes the traffic.

My only workaround is to configure the port to untag my voice VLAN.

Side note- I run NAC as well, but even with that I'm unable to get the phones to associate with the tagged VLAN. It has to be the untagged VLAN.

My port configuration example:
code:
configure lldp port  advertise system-capabilities
configure lldp port advertise vendor-specific dot1 port-vlan-id
configure lldp port advertise vendor-specific med capabilities
configure lldp port advertise vendor-specific med power-via-mdi
configure lldp port advertise vendor-specific dot1 vlan-name vlan Mitel
configure lldp port advertise vendor-specific med policy application voice vlan Mitel dscp 46



LLDP status for my port:
code:
LLDP Port  detected 1 neighbor
Neighbor: (5.1)0.0.0.0/08:00:0F:, age 10 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 : 08:00:0F:
- Time To Live: 120 seconds
- Port Description: "LAN port"
- System Name: "UC360"
- System Description: "UC360,ver: 2.1.0.13,dsp: 3.1.0.14,02/08/2019 18:2\
4:37 +0000"
- System Capabilities : "Telephone"
Enabled Capabilities: "Telephone"
- Management Address Subtype: MAC (6)
Management Address : 08:00:0F:
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 : 1000BaseTFD (30)
- MED Capabilities: "MED Capabilities, Network Policy, Extended Power via MDI - PD"
MED Device Type : Endpoint Class III (3)
- MED Network Policy
Application Type : Voice (1)
Policy Flags : Known Policy, Tagged (0x1)
VLAN ID :
L2 Priority : 2
DSCP Value : 46
- MED Network Policy
Application Type : Voice Signaling (2)
Policy Flags : Known Policy, Tagged (0x1)
VLAN ID :
L2 Priority : 2
DSCP Value : 46
- MED Extended Power-via-MDI
Power Type : PD Device (1)
Power Source : Unknown (0)
Power Priority: High (2)
Power Value : 20.5 Watts
- MED Hardware Revision: "PCB Version: 1"
- MED Firmware Revision: "Version 2.1.0.13"
- MED Software Revision: "Main 2.1.0.13"
- MED Serial Number: ""
- MED Manufacturer Name: "Mitel Networks"
- MED Model Name: "UC360"
- MED Asset ID: ""

2 replies

Userlevel 1
Ours was doing this. It was either the DHCP didn't have correct tag info or the phone system. I want to say DHCP.
Userlevel 1
Ted,

I just deployed this particular Extreme switch- before it was Cisco. I was told it was working before the upgrade.

Currently I have the ports configured for our voice VLAN untagged and it works just fine.

I'll take a look at the DHCP config and see if something is missing.

Tommy

Reply