[j-nsp] COS went configured, made the SRX3600 interface down
Fahad Khan
fahad.khan at gmail.com
Fri Sep 24 00:48:33 EDT 2010
David,
People like "dale" can understand and have idea to give the better answer of
my question :). You dont have to go to the lower level every time.
regards,
Muhammad Fahad Khan
JNCIP - M/T # 834
IT Specialist
Global Technology Services, IBM
fahad at pk.ibm.com
+92-301-8247638
Skype: fahad-ibm
http://pk.linkedin.com/in/muhammadfahadkhan
On Fri, Sep 24, 2010 at 1:58 AM, Dale Shaw <dale.shaw at gmail.com> wrote:
> Hi,
>
> In my experience, enabling or disabling per-unit-scheduler flaps the
> interface, yes.
>
> Definitely with 10.0R3, maybe with R2. I've seen it on J and SRX.
>
> Lucky you did it inside a maintenance window! ;-)
>
> Cheers
> Dale
>
> On Friday, September 24, 2010, Fahad Khan <fahad.khan at gmail.com> wrote:
> > Hi,
> >
> > I simply implemented per-unit-scheduler on reth0.x(egress interface),
> > committed the config, It made the whole network down. Using Junos
> 10.0R3.10
> > in cluster
> >
> > has any body implemented COS on SRX3600 and saw this behaviour???
> >
> > regards
> > Muhammad Fahad Khan
> > JNCIP - M/T # 834
> > IT Specialist
> > Global Technology Services, IBM
> > fahad at pk.ibm.com
> > +92-301-8247638
> > Skype: fahad-ibm
> > http://pk.linkedin.com/in/muhammadfahadkhan
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
More information about the juniper-nsp
mailing list