You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if stitcher could detect an invalid excludehop.
Specifically: urn:publicid:IDN+authority+interface+interfacename is valid, as is urn:publicid:IDN+authority+interface+interfacename=vlannumber. Such as urn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernet or urn:publicid:IDN+exogeni.net:pscNet+interface+pscNet:Domain:vlan:18cb52fd-b2e6-43b3-9f06-ef82d954a393:vlan
or urn:publicid:IDN+exogeni.net:pscNet+interface+pscNet:Domain:vlan:18cb52fd-b2e6-43b3-9f06-ef82d954a393:vlan=1234
However, these are malformed: urn:publicid:IDN+exogeni.net:pscNet+interface+pscNet:Domain:vlan:18cb52fd-b2e6-43b3-9f06-ef82d954a393:vlan:vlannumber urn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernet:1234
That is, the vlan numbers to exclude are separated by an equals sign - anything else is wrong. The problem is that the difference is subtle. The rules on naming hops are rather loose. Nothing precludes ending an interface name with a number. So this is legal: urn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernet:3
or urn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernet:3-5
The text was updated successfully, but these errors were encountered:
It would be nice if stitcher could detect an invalid excludehop.
Specifically:
urn:publicid:IDN+authority+interface+interfacenameis valid, as isurn:publicid:IDN+authority+interface+interfacename=vlannumber. Such asurn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernetorurn:publicid:IDN+exogeni.net:pscNet+interface+pscNet:Domain:vlan:18cb52fd-b2e6-43b3-9f06-ef82d954a393:vlanor
urn:publicid:IDN+exogeni.net:pscNet+interface+pscNet:Domain:vlan:18cb52fd-b2e6-43b3-9f06-ef82d954a393:vlan=1234However, these are malformed:
urn:publicid:IDN+exogeni.net:pscNet+interface+pscNet:Domain:vlan:18cb52fd-b2e6-43b3-9f06-ef82d954a393:vlan:vlannumberurn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernet:1234That is, the vlan numbers to exclude are separated by an equals sign - anything else is wrong. The problem is that the difference is subtle. The rules on naming hops are rather loose. Nothing precludes ending an interface name with a number. So this is legal:
urn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernet:3or
urn:publicid:IDN+exogeni.net:pscvmsite+interface+PSC:ExoGeni:TenGigabitEthernet:1:ethernet:3-5The text was updated successfully, but these errors were encountered: