> James Bensley > Sent: Friday, April 5, 2019 8:53 AM > > Opt 2. Find a way to introduce more entropy between you and your > customer directly. Can they do something crazy like setup a bunch of /31s > between their PEs using sub-interfaces and ECMP across them, assuming > they have better visibility into their customers traffic. > This doesn't solve the issue that they might just have one source and > destination thought, so not guaranteed to work (just shifting the problem > domain). > Actually if the feature to allow ASR9k to perform MPLS parsing on interfaces acting as PW access circuits then if customer is asked to enable entropy-labels of FAT labels the ASR should then be able to use the entropy label information a) load-share among it's core-facing links, b) derive its own entropy labels if the feature is enabled.
adam _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
