[j-nsp] 802.3ad trouble

[Josef Buchsteiner]

from what I can see you are already install a next-hop id of 17.000
meaning you have already 17.000 next-hop allocated in the system.
I would be curios how your system is setup and why you have that much
on next-hops. I will contact you unicast

Josef

Friday, August 13, 2004, 8:41:28 AM, you wrote:

JE> Hi,

JE> We've recently created a 802.3ad trunk between our Nortel Passport
JE> 8100-series switch and our M40.
JE> The ae0-interface on the M40 has about 160 prefixes in the inet-family.  The
JE> trunk consists of 3 FE-links.
JE> All seems to be working fine at first, but after a few minutes, all hell
JE> breaks loose, and random nexthops will
JE> be missing in the PFE.

JE> Our logs will be flooded with stuff like this:
JE> Aug 11 16:38:57  dtc-core-02 scb NH: Non-existant NH (17058:Unicast, 2) in
JE> generic change path
JE> Aug 11 16:38:57  dtc-core-02 scb NH(nh_ucast_add): Fails to install L2
JE> descriptor
JE> Aug 11 16:38:57  dtc-core-02 scb last message repeated 3 times
JE> Aug 11 16:38:57  dtc-core-02 scb NH: Aggregate nh (16953) with unknown nh in
JE> list (17025)
JE> Aug 11 16:38:57  dtc-core-02 scb NH: Non-existant NH (17025:Unicast, 2) in
JE> generic change path
JE> Aug 11 16:38:58  dtc-core-02 scb NH(nh_ucast_add): Fails to install L2
JE> descriptor
JE> Aug 11 16:38:58  dtc-core-02 /kernel: RT_PFE: NH IPC op 1 (ADD NEXTHOP)
JE> failed, err 1 (Unknown)
JE> Aug 11 16:38:58  dtc-core-02 /kernel: RT_PFE: NH details: idx 17174 type 2
JE> ifl 135
JE> Aug 11 16:38:58  dtc-core-02 /kernel: RT_PFE: NH IPC op 1 (ADD NEXTHOP)
JE> failed, err 1 (Unknown)
JE> Aug 11 16:38:58  dtc-core-02 /kernel: RT_PFE: NH details: idx 17179 type 2
JE> ifl 175

JE> When I disable the trunk & rename the ae0 interface to fe-0/0/0, everything
JE> is fine, so I expected this to be a problem
JE> with the aggregated ethernet code in de JunOS version we were running at the
JE> time. (6.2R1.5)

JE> In the release notes of 6.3R1.4 I found the following:
JE> "On aggregated Ethernet or aggregated SONET interfaces, if a logical
JE> interface has hundreds of next hops, the installation of these routes into
JE> the Packet Forwarding Engine might take several minutes and cause scheduler
JE> slips in the routing protocol process (rpd). [PR/48856]"

JE> So I decided to upgrade the M40, hoping this would be a fix to our
JE> problem.... but it wasn't.

JE> If anybody has a clue what's going wrong here, I'd really like to know :-)

JE> Thanks,

JE> -- Jorn

JE> _______________________________________________
JE> juniper-nsp mailing list juniper-nsp at puck.nether.net
JE> http://puck.nether.net/mailman/listinfo/juniper-nsp