Across dozens of municipal leaves, tenant routing-instance names and IDs drift (vrf-parks vs Parks_VRF vs tnt3). Why does consistent naming matter for multitenancy?
Select an answer to reveal the explanation.
Short Explanation
If Parks is vrf-parks on one leaf and tnt3 on another, humans will attach the wrong VLAN at 2 a.m. Consistent names are seat belts for multitenancy—boring, mandatory, and cheaper than an outage postmortem. Hyphens are fine; chaos is not.
Full Explanation
Operable multitenancy depends on consistent routing-instance naming and identifiers across the fabric so automation, documentation, and human change control attach interfaces and RTs to the correct tenant. Junos does not forbid hyphens, nor does EVPN require name-to-description character identity. Unique-per-leaf renaming increases mis-attachment risk rather than helping BGP.