Many thanks for the reply.
You will have to excuse my ignorance, but how will enabling MST solve this issue?
I am assuming by having the ability to map multiple VLANs to one spanning tree instance, the VLANs created after my initial spanning tree instances ran out, will activate once mapped under MST...
as fas as I remember, that is the default behavior for any Vlan interface, regardless of the number or STP instances. You need at least one port assigned to the Vlan in order for the Valn interface to become active.
Is that what you are asking ?
Yes that is how I expect it to behave, and that was the case upto around 145 VLANs. Now that is not the case and I have no idea why.
I assign the access port on my edge switch as untagged, the VLAN is allowed on the trunk as tagged. I plug my laptop into the port in the correct IP range and I cannont ping the VLAN gateway.
If I add the same VLAN to a port on the Core L3 Switch, in this case the 2960, the vlan activates and I can now ping the gateway.
If I go back to the edge switch, plug my laptop into the previously configured port it works.
I am very bemused.
Disable ip routing on the edge switch give it a default-gateway
Make sure the vlan you are using is propagated to the edge switch
Note: Any vlans allowed to traverse an active trunk will active the L3 vlans without requiring a access port to be assigned to the vlan