Class ConsolidateBehindRouterRule

java.lang.Object
com.eqixiac.equinix.design.estate.rules.ConsolidateBehindRouterRule
All Implemented Interfaces:
EstateRule

public final class ConsolidateBehindRouterRule extends Object implements EstateRule
FindingCategory.CONSOLIDATE_BEHIND_ROUTER, both directions.
  • Consolidate: at least consolidateMinConnections live port-to-cloud (COLO to SP) connections whose A side is in one metro. A Fabric Cloud Router there would give them one routing domain (cloud-to-cloud traffic without hair-pinning through the customer's router). When the scope already has a live router in that metro the recommendation re-homes onto it; otherwise it prices a new STANDARD router. The financial impact compares today's connections with the router plus the same bandwidth as IP_VCs; it is often a cost, not a saving, and is reported as such.
  • Reverse: a live router with exactly one connection. It could be replaced by a direct connection; the saving is the router price (the connection is assumed to cost the same as an EVPL_VC of the same bandwidth). Routers with no connections are left to IdleResourceRule.
  • Field Details

    • NEW_ROUTER_PACKAGE

      public static final String NEW_ROUTER_PACKAGE
      The package priced for a new router (assumption: the smallest production package).
      See Also:
  • Constructor Details

    • ConsolidateBehindRouterRule

      public ConsolidateBehindRouterRule()
  • Method Details