Touche. We do plan to upgrade these boxes to 5.x. I was merely hoping to
get this working "for now". I was also tempted to drop out of CLI and just
try "ifconfig fxp0 up" but they are production boxes, so...
Thanks,
Kevin
[There is text before PGP section.]
>
-- Start of PGP signed section.
> Hmm, curious. Is there a specific reason why you've chosen to use
> 4.x when this is no longer a formally supported version (formal
> support is maintained for the current version plus the two previous
> versions, i.e. 5.2, 5.1 and 5.0)? Unfortunately, this means that all
> the release notes for 4.x versions are no longer accessible on the
> website so it's not possible to check if there were any known bugs of
> this nature.
>
> The only other things you might try rely on the boxes not being in
> production.
>
> 1) try rebooting the box and see if it comes up with the interface
> enabled (assuming that the file /config/juniper.conf doesn't have the
> interface disabled).
> 2) try copying /config/juniper.conf to /var/tmp/juniper.conf, then
> delete the entire running config (and commit), then do a load
> override /var/tmp/juniper.conf (and commit). This should load the
> config entirely fresh.
>
> If either (or both) of these work, it probably indicates a bug which,
> I'm afraid, you have no chance of getting fixed in a 4.x version of
> code. The only solution would be to either upgrade to 5.x or not
> disable fxp0 ;-)
>
> Regards,
>
> Guy
>
> > -----Original Message-----
> > From: sigma@smx.pair.com [mailto:sigma@smx.pair.com]
> > Sent: Wednesday, May 01, 2002 9:28 PM
> > To: Guy.Davies@telindus.co.uk
> > Cc: juniper-nsp@puck.nether.net
> > Subject: Re: [j-nsp] fxp0 administratively disabled
> >
> >
> >
> > I should have mentioned that prior to this, the fxp0 interface
> > *was* specifically disabled.
> >
> > I have previously tried both deleting the disable statement
> > and adding the
> > enable statement. Neither has any effect after a commit. I
> > even put an
> > enable in the family inet section.
> >
> > Kevin
> >
> > [There is text before PGP section.]
> > >
> > -- Start of PGP signed section.
> > > By default, all interfaces are administratively enabled in all
> > > versions of JUNOS (so long as they're supported in that
> > version). If
> > > an interface is disabled, then it has to be in the config
> > > somewhere (either directly under that interface or in a group
> > > which matches fxp0). If it isn't enabled, you can use the
> > > command "set interfaces fxp0 enable". If it is explicitly
> > > disabled, you can use the command "delete interfaces fxp0
> > > disable".
> > >
> > > Regards,
> > >
> > > Guy
> > >
> > > > -----Original Message-----
> > > > From: sigma@smx.pair.com [mailto:sigma@smx.pair.com]
> > > > Sent: Wednesday, May 01, 2002 9:12 PM
> > > > To: juniper-nsp@puck.nether.net
> > > > Subject: [j-nsp] fxp0 administratively disabled
> > > >
> > > >
> > > >
> > > > Is there some special incantation required to allow the fxp0
> > > > management
> > > > interface to work under JunOS 4.x? On a JunOS 5.2R1.4
> > > > system, it comes up
> > > > and works fine, but no matter what I try on several 4.x
> > > > systems, the port
> > > > is "up" but steadfastly remains "administratively disabled".
> > > >
> > > > Kevin
> > > >
> > -- End of PGP signed section, PGP failed!
> >
-- End of PGP signed section, PGP failed!
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:35 EDT