This week we’ve been rolling out more Mitel VOIP handsets and had to make sure we had the Voice VLAN pushed out to all the switches and check the tagging on the uplinks to make sure the handsets would all connect properly.
After an hour of chasing VLAN tagging via the CLI I thought I’d better see if there was a smarter way to check the switches and fired up ProCurve Manager Plus. Under Default Management Group –> Network Map –> VLANS you can select the VLAN number that you want to check and PCM will show a network map with the switches that have that VLAN tagged and show you how those switches are connected to each other. Or more importantly, not connected.
The screen capture above shows our VOIP VLAN and that I tagged all the right ports to connect the PE switch, but missed the VOIP tagging between the Queens Wing switch and the core. Easy to spot in PCM and just as easy to fix, and one less problem to fix once the handsets are rolled out
When I paid Adam (@DJADSA) a visit last week I noticed that he’d labelled important interfaces on his switches. When I was wondering which ports from the 5400 to tag for the edge switches, it occurred to me that we could be more organised with our switches and do something similar. Having that sort of documentation on the network ports/trunks/uplinks would save time when quickly adding new VLANs etc and would save time troubleshooting other network issues
from the CLI
name "10Gb Uplink from Core"