Custom Query (1408 matches)
Results (34 - 36 of 1408)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1351 | fixed | SCS: 2 hop path has no dependencies | ||
| Description |
A circuit from Utah DDC to PG Utah shows no dependencies between the hops at the SCS. One of those should depend on the other, though it doesn't matter which. |
|||
| #1352 | fixed | SCS thinks link type vlan is not stitching | ||
| Description |
Xi says the SCS thinks a " This is not correct. Link type of 'vlan' should mean stitching. Link type of 'lan' generally means local to one AM. Leaving out the link type means the default / do something reasonable - assume type 'lan' if there is only 1 AM, and assume type 'vlan' for stitching if there are >1 AMs. The shared VLAN is something different. Such a link has a child element with local name "link_shared_vlan". This is in a separate namespace, the shared vlan extension: |
|||
| #1353 | fixed | Unknown path reported for complex 9 site topology | ||
| Description |
A 9 node topology that uses both AL2S and ION sites reports "Cannot find the set of paths" error even though all sites are known. A diagram is attached for the topology along with the RSpec used. According to Xi, the link between Illinois and Chicago (ill-chic-4) caused the failure, and the problem is a known issue which is fixed in 2.0 branch which is running in production and development SCS. After switching to an SCS with the fix, there is still a problem with the link between Chicago and Rutgers (chic-rut-7). Xi is investigating this problem. |
|||
