> We try to avoid the terms "ifd" and "ifl" completely in our docs,
> but these internal terms have slipped out in a few places. The
> relationship is fairly simple: "ifd" is the physical interface
> device, where "ifl" is the logical interface (aka unit). Logical
> interfaces are arranged as children of a physical interface.
They also frequently show up in error logs, e.g.
Jun 9 18:25:07 ar2.od cosd[1262]: COSD_GENCFG_WRITE_FAILED: GENCFG write
failed for Classifier to IFL 698. Reason: File exists
Jun 9 20:03:43 cr1.td rpd[1039]: KRT ADD for 195.1.122.235/32 => { ifl 497
addr #0 0.19.5b.b9.d.c } failed, error "EINVAL -- Bad parameter in request".
I would much prefer if there was a *documented* command to translate
these references to interface/unit. Yes, I know it can be done by
accessing the PFE - but that's not an interface normal users are
encouraged to use.
Steinar Haug, Nethelp consulting, [email protected]
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
