To troubleshoot this kind of condition, you need to understand 1) the
complete structure of the headers (is there any tunneling, MPLS,
pseudowires etc) 2) what kind of forwarding decision your MX performs for
those packets: IP LPM only, Ethernet switching, IP + Ethernet (irb-based
L3), MPLS, MPLS+I
ok update.
We restarted the MPC4E on our 960 and voila, all 4 links being used- LOL
!!! The MPC4E that we restarted also had another AE bundle exhibiting the
same issue across other ports. Anyways, working now, cant even begin to
explain what the problem might have been.
Many thanks
JfD
On 10 A
Guys thanks for all the replies, when I took an sflow sample, I oculd see
at least 100+ flows with varying src/dst tuple and flow sizes, so cant
understand why flows are stuck on one link. I can understand if tuples were
hashing to one link, but these are varies sources/destinations... makes no
sen
My first look at spring/sr.
I have 5 nodes with node sids and able to do l3vpn over spring-enabled-ospf
node sid's like this. (forgive the 1,2,5 out of sequence usage...long
story)
101--1--2--5--102
pe1--p--p--p--pe
Does anyone know the
4 matches
Mail list logo