Running a CRS317-1G-16S+ just doing simple L2 VLAN trunking.
Having issues with adding VLANs to interfaces (only trunks). I cannot add new VLANs to interfaces. The only way I managed to get the first lot (101-504) working was to cut/paste the config in the “stable” version, then change to the RC. The configs seem to stick.
However, I cannot add any new VLANs to interfaces whilst booted into the ROS RC.
[admin@dx02-sw01] /interface ethernet switch vlan> add ports=sfp-sfpplus1,sfp-sfpplus16 switch=switch1 vlan-id=778 disabled=no failure: not supported for this switch
This is quite a worry that it will not accept the same config syntax/command - this is going to be going into a production environment - slowly losing faith in anything L2 on these devices!!
Thanks for the reply. I have read those particular documents several times which has helped me get this far with L2 on the CRS317. However, there is nothing that jumps out at me that says that I would not be able to add a new VLAN to specific ports on the RC.
Is there something in particular you can see that I am missing? The command is (or should be) a fairly simple one to add a new vlan and add them to interfaces for trunking…
Sorry for being so brief. Just did this recently and still had the tabs open in the browser. Indeed the new vlan config seems to be missing or hiding well Maybe I found this by trial and error.
However, the vlans need to be configured on the bridge since the rc version.
I have this in my lab setup and it works (just the relevant parts of it):
Aha. Thanks very much. I shall give this a go after backing everything up and reverting to ROS. ROS seems very powerful for L3, but complex (too complex for simple tasks) for L2. Saying that, I am only comparing to many years of Cisco where the configuration takes care of a lot under the hood!
Aha. Thanks very much. I shall give this a go after backing everything up and reverting to ROS. ROS seems very powerful for L3, but complex (too complex for simple tasks) for L2. Saying that, I am only comparing to many years of Cisco where the configuration takes care of a lot under the hood!