Feature Request: Limit Autorouting Search to MPLS Core Sections
Besvarat
When using the "Auto Routing Logical Paths" tool to find routes for LSP Paths, the search results include transport containers that are not core sections of our MPLS network. It would be very helpful to have the ability to constrain the search to using only core sections of a selected MPLS network. This could be a dropdown selection along with the other constraints, and ideally it would auto-populate the MPLS network name that the parent Label Switch Path TC is associated with. The user could select a "None" option in the dropdown that would disable this constraint if desired.
-
Under consideration
0 -
UPVOTE
- For those users attempting to detail-document MPLS-TP and MPLS-TE infrastructure/circuits and the underlying legacy TDM/SONET/STM traffic via Pseudowire carrier systems
- This type of extremely deterministic and latency-sensitive packet traffic requires much more statically-controlled/designed transport container routes/paths (LSP Tunneling), as well as the ability to ascertain Impact Analysis quickly of planned/unplanned Fiber Breaks, Microwave Fading/Interference, etc… ALL of which physically transport/carry these Core Trunks on a multitude of complex other carrier systems (DWDM, Leased Ethernet Provider, etc).
- This is EXTREMELY common for Utility Companies (Power/Gas/Water/etc) in USA for the foreseeable 10-15 years unfortunately. DETAIL EXPLANATION FOLLOWS (If care):
- This is because those utility companies (beginning in 2015 with FCC Copper End-of-life regulatory ruling) were forced to simply migrate existing TDM/SONET/STM carrier traffic off existing leased communication company carriers, and onto their own utility private networks (as existing TDM/SONET/STM carrier circuits to avoid paying to upgrade the endpoint multiplexers). Manufacturers have begun to end-of-life support TDM/SONET/STM carrier equipment and technology in favor of Ethernet/IP Packet, but the sheer volume of existing infrastructure, Network Security vulnerabilities/restrictions, and US regulatory requirements on these Utility companies, they cannot presently support the replacement speed at which the technology is changing.
- Therefore, it will be much, much longer before the ability for Utilities to purely go packet-based technology and must support documentation for both Ethernet/IP-Packet as well as Legacy TDM/SONET/STM carrier systems.
- And for many Electrical companies, Ethernet/IP-Packet technology that supports high-speed/low-latency Tele-point-to-point Protection Relay Carrier communication circuits will not be possible ANY time soon. Which means either Electrical Relay-to-Relay communications circuits are only possible with Direct Fiber connectivity (which is difficult for fiber strand count capacity/availability)… or through Multiplexed IEEE C37.94-compliant standard circuits. This sometimes means that only TDM/SONET/STM-based architecture/platforms will support the deterministic carrier requirements of bandwidth/latency. MPLS Pseudowire carrier circuits adhering to encapsulated C37.94 standards will work… but NOT dynamic-routed ones… MUST be measurable and deterministic.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
2 kommentarer