Do you just want to know duration?
Single supervisor or multiple?
On Fri, Mar 15, 2019, 13:21 Scott Voll wrote:
> What does a Non-disruptive Nexus 77xx upgrade look like to a single homed
> device, attached to it?
>
> TIA
>
> Scott
> ___
> cisco-nsp
What does a Non-disruptive Nexus 77xx upgrade look like to a single homed
device, attached to it?
TIA
Scott
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at
Newer versions of NXOS for these platforms support "internet peering mode"
Up to 1,000,000 routes.
Is anyone using this hardware / routing template and taking in the full table?
Table 3. LPM Routing Modes for Cisco Nexus 9300-EX Series Switches LPM Routing
Mode
CLI Command:
system routing
Newer versions of NXOS for these platforms support "internet peering mode"
Up to 1,000,000 routes.
Is anyone using this hardware / routing template and taking in the full table?
Table 3. LPM Routing Modes for Cisco Nexus 9300-EX Series Switches
LPM Routing Mode
CLI Command:
system routing
Hi James
On Wed, Mar 13, 2019 at 09:29:13AM +, James Bensley wrote:
> The ingress PE probably only has the same source and destination MACs
> to hash on to generate the FAT label. This means that in the scenario
> that your customer is using MPLS the required level of entropy isn't
>
On Tue, 12 Feb 2019 at 18:19, James Jun wrote:
>
> Hey all,
>
> I have a PW scenario that looks like this:
>
> Customer --- PE1 P [4x10GE LAG] PE2 -- Customer
>
> PE1, P and PE2 routers are all ASR9K.
>
> EoMPLS PW is delivered to customer; both PE1 and PE2 configure FAT-PW as
>
