[j-nsp] ifl and ifd list

Richard A Steenbergen ras at e-gerbil.net
Wed Jun 9 16:26:07 EDT 2010


On Wed, Jun 09, 2010 at 08:57:20PM +0200, sthaug at nethelp.no wrote:
> > 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.

Yeah we run into this all the time (daily, at the rate the bugs are
piling up around here :P). Fortunately the internal indexes are exposed
under "show interface detail", so you could easily whip up an op script
to display them in whatever format you'd like. For example:

Physical interface: xe-0/0/0, Enabled, Physical link is Up
  Interface index: 138, SNMP ifIndex: 135, Generation: 141

Or the | display xml view:

    <interface-information xmlns="http://xml.juniper.net/junos/9.5R3/junos-interface" junos:style="normal">
        <physical-interface>
            <name>xe-0/0/0</name>
            <admin-status junos:format="Enabled">up</admin-status>
            <oper-status>up</oper-status>
            <local-index>138</local-index>

The IFD above is 138.

There are also the following hidden commands for looking up the 
interfaces by index directly:

show interfaces ifd-index
show interfaces ifl-index

But speaking of feature requests related to viewing stuff in the pfe, 
I'd love to get something to run a single command on a remote shell and 
then exit (i.e. invoke cprod -c rather than vty). Similar to how Cisco 
gives you "remote login" (i.e. start shell pfe) and "remote command". 

-- 
Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)


More information about the juniper-nsp mailing list