We are an ISP who provide connectivity for a wide array of clients, including HMO/Multiple dwelling apartments.
When we deploy switches, their config is always the same.
When we used ruckus we had no issue with setting up a golden config and pointing the switch to that config for it to mirror across every switch.
I was recently caught out when I realized that VLAN Config is not actually applied to the ports unless you manually specify it for each switch.
Can someone tell me what I am missing here? I thought the whole idea of ZT was that you send a switch out and it grabs the config and just works? I don’t want to touch anything! I want to be able to send our team out with kit and it gets plugged in and up and running, like I was told it would be!
Hi Jacob, using cnMaestro you can pre-configure the switch in a switch group during the onboarding. Currently switch port must be configured for each new switch when assigning the switch to the switch group. We are working on improving the port configuration in the upcoming cnMaestro release. Port templates can be set up for each switch type after that the new switch can inherit the port configuration from one of the pre-configured port templates. Please raise and post your support ticket and I will get in touch to walk you through the onboarding/configuration process and explain the upcoming switch port configuration improvement. Thanks.
Thanks, feel free to close this for now - Until further updates are released, the conversation is going to be limited.
I will note the date and will follow up in due course if further advances have not yielded meaningful results. I would have expected templating at the port level to be something of an easy win at this time, however, this appears not to be the case.