[j-nsp] CoS on Junos5.3

[Josef Buchsteiner]

At 10:24 AM 11/28/2002, Josef Buchsteiner wrote:
>At 05:29 PM 11/27/2002, Sonny I Franslay wrote:
>>Hi Josef,
>>
>>Would the symptom comes back if we cold reboot the router?
>
>it should not

Sonny,
         want to add to my statement that it 'may work' after
a cold reboot. If the logical interface number changes after
a reboot we still fail to rewrite ieee. PR26012 has been
fixed but is not available on any released version yet. For
the time being the only workaround is to deactivate/activate
the class-of-service stanza.

hope this helps
Josef


>Josef
>
>
>>thanks,
>>sonny
>>----- Original Message -----
>>From: "Josef Buchsteiner" <josefb@juniper.net>
>>To: "Sonny I Franslay" <sonnyfranslay@pacific.net.sg>
>>Sent: Tuesday, November 26, 2002 4:09 PM
>>Subject: Re: [j-nsp] CoS on Junos5.3
>>
>>
>> > At 12:50 AM 11/26/2002, Sonny I Franslay wrote:
>> > >Hi Josef,
>> > >
>> > >I 've never attempted the cos on any other interface but FE and GigE. I'm
>> > >afraid I may not have a conclusive answer to your question, but we only
>>see
>> > >this symtom when applying the CoS on these two interfaces so far.
>> > >
>> > >How would it make any difference whether it is a broadcast interface or
>>not?
>> >
>> >
>> > Sonny,
>> >          I strongly believe you were running into a known problem report
>> > PR26012.
>> > This happen after software upgrade and/or initial CoS Configuration and
>>related
>> > to Ethernet Interfaces. We had to enable to cache the re-write for all
>> > interfaces
>> > which we had not done before. The same symptom will happen with ieee
>>rewrite.
>> > It is also related to the default exp rewrite we do all the time.
>> > Once it is working you should not see nay troubles anymore.
>> >
>> >          Once you deactivate/activate the interface or the
>>class-of-service
>> > stanza
>> > cosd ( the daemon on the RE) will download all class-of-service related
>> > configuration setting to the i/o Asic on the FEB or FPC which is the
>>reason
>> > why it worked after you have done this since you just reprogrammed the
>> > Asic.
>> >
>> >
>> > hope this helps
>> > Josef
>> >
>> >
>> >
>> > >thanks & regards,
>> > >Sonny
>> > >
>> > >----- Original Message -----
>> > >From: "Josef Buchsteiner" <josefb@juniper.net>
>> > >To: "Sonny Franslay" <sonnyfranslay@pacific.net.sg>
>> > >Sent: Tuesday, November 26, 2002 3:22 AM
>> > >Subject: Re: [j-nsp] CoS on Junos5.3
>> > >
>> > >
>> > > > Sonny,
>> > > >          one last question and then I can think ca confirm
>> > > > and have all the puzzles together. Have you ever seen this
>> > > > symptom on non-broadcast interfaces ?
>> > > >
>> > > > thanks
>> > > > Josef
>> > > >
>> > > >
>> > > > At 03:44 PM 11/25/2002, Sonny Franslay wrote:
>> > > > >Hi Josef,
>> > > > >
>> > > > > >
>> > > > > > is interface fe-0/2/0 also configured with vland-id's ?
>> > > > > > did you had also configured in the very begin classifiers
>> > > > > > as well or only the re-write rule as mentioned in the note ?
>> > > > > >
>> > > > >
>> > > > >Nope, it is not configured wtih vlan-id. Below is the interface
>>config:
>> > > > >
>> > > > >fe-0/2/0 {
>> > > > >     description "VLAN1 10.10.90.0/24";
>> > > > >     unit 0 {
>> > > > >         family inet {
>> > > > >             address 10.10.90.4/24;
>> > > > >         }
>> > > > >     }
>> > > > >}
>> > > > >
>> > > > >I did not use any classifier. I used the loss-priority bit to
>> > > > >differentiate the packets coming in via the WAN interface from the
>> > >others.
>> > > > >I connfigured the rewrite rule at the same time as I configured the
>> > > > >interface (to apply the rewrite rule policy to the interface).
>> > > > >
>> > > > >Do I need to define the rewrite rules seperately from applying it on
>>the
>> > > > >interface? Meaning I have to do 2 separate "commits"?
>> > > > >This is what I want to find out actually.
>> > > > >
>> > > > >thanks & regards,
>> > > > >sonny
>> > > >
>> >
>>
>>
>>_______________________________________________
>>juniper-nsp mailing list juniper-nsp@puck.nether.net
>>http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>_______________________________________________
>juniper-nsp mailing list juniper-nsp@puck.nether.net
>http://puck.nether.net/mailman/listinfo/juniper-nsp