Server L3 Vlans

[Erlend Røsok]

Hello, we are testing out openclos and are so far very happy about it. There is one thing we cannot seem to do though. We would like the option to provision more than one server vlan, and choose the vlan-id for those vlans.

Do you think this can be implemented in the future?

Best Regards
Erlend Røsok

[Moloy c]

Hi Erlend,

Glad to know that you guys find OpenClos useful. 

Any specific reason you guys want more than one vlans. The purpose of Layer-3 Fabric is to not care about the VLANs and servers talk over L3, not worry about broadcast domain. Btw OpenClos creates vlan with id = 1 for each leaf switch, but servers across leaf switches don't talk to each other over L2. You can change the VLAN id on the file - jnpr/openclos/conf/junosTemplates/vlans.txt. But currently no plan to create multiple VLANs per leaf switch. 

Thanks,

Moloy

[Erlend Røsok]

Hey Moloy.

The vlan-id is not such a concern, and would be a "nice to have" feature. But we do want to provision more than one server vlan. In our situation we need a compute vlan, storage vlan and a ceph frontend vlan on all our leafs. They can be vlan 1-3 of course, but setting the vlan-id you want to use seems like a small thing to implement.

Best Regards

Erlend Røsok

[Moloy c]

Hi Erlend,

It is not difficult to add multiple VLANs ...

1. Add additional VLANs like STORAGE/CEPH in vlans.txt

2. Add corresponding vlan id as unit on irb in rvi_stanza.txt

3. Modify accessInterface.txt, make vlan name as jinja variable.

4. Modify _createAccessPortInterfaces() in l3Clos.py. For desired set of interfaces pass different vlan name.

Please let me know if you need additional help.

Regards,

Moloy

[Erlend Røsok]

Thanks for the suggestion. I will look into it. There seems to something missing to these steps. How will these vlans connect to the vlanPrefix i am making in closTemplate.yaml? I will need to have three prefixes there, and they must correlate to the correct vlans. I am not a programmer, so i was hoping you would be able to implement this at some point. That being said, we will most likely manually add these vlans to the fabric before we can get this feature, but others might have the same needs.

Anyway, great product. Thanks for your help!

Best Regards

Erlend Røsok

[Moloy c]

That's correct! If you want to make if generic the parameters should be configurable from closTemplate.yaml. At that point you need two things, vlan name/id and access interface range for each vlan. We will look in to the feasibility of adding this as a feature, but till then you can hack it with the steps provided.

Please keep sending feedback.

Regards,

Moloy