The Netscreen docs certainly leave a lot to be desired in this case...
The 'Early Frame' and 'Late Frame' counters are essentially buffer
management counters. If there was a wide discrepancy between the two
numbers there might be reasonable cause for alarm, but in your case the
numbers are almost
All,
I am having problems interpreting some results that I am getting when I run the
command - get counter statistics interface .
I am seeing an unusually high number of "Early Frame" and "Late Frame" packets
as well as "in overrun"
Can anyone give me a better description of how to interp
Should have mentioned earlier (in case it's relevant), the reason
for sham-link requirement is that there 'will' be a slow backup link
between the cisco and the m10, but it'll be direct, so the cisco and
m10 will think that's the better link (due to intra-area). So, was
hoping to use sham-link a
- Original Message -
From: Daniel Lete <[EMAIL PROTECTED]>
[...]
> In relation to your sham-link. You need a loopback IP
> within your VRF to act as source/destination of the sham
> link and these loopbacks are NOT to be announced to your
> CE.
I was going to make that point -- that i
On Wed, 2007-12-05 at 15:17 +0200, M.Mihailidis wrote:
> the thing im looking for is interim (something) to keep track of subscriber
> packets or bandwidth any one have any clue??
> - Original Message -
> From: M.Mihailidis
> To: Juniper-Nsp
> Sent: Wednesday, December 05, 2007
Hello David,
Irrelevant of the Sham Link configuration
a) LSA Type-5 in CE routers is maintained as LSA Type-5 when flooded across the
backbone. If in your CE routers you are using those, you will always see them
that way.
b) The extended community "Domain ID" appended in both PE routers needs t
the thing im looking for is interim (something) to keep track of subscriber
packets or bandwidth any one have any clue??
- Original Message -
From: M.Mihailidis
To: Juniper-Nsp
Sent: Wednesday, December 05, 2007 2:57 PM
Hello
i need help on monitoring packects on subscri
> After some more investigation following has been found:
>
> Mastership mismatch is not the cause of the JNPR sending MS
> bit on. It is
> done to signal the master to reset the state machine to
> ExStart. JNPR does
> this because state machine went to BadLSReq and restarted negotiation.
>
> D
Hello
i need help on monitoring packects on subscribers on an e320 can anyone
tell me how i can accomplish this?is it via aaa accounting? and which is the
commands to use?Every documention i found was not very helpful
Cheers
___
juniper-nsp mailin
Hello
i need help on monitoring packects on subscribers on an e320 can anyone
tell me how ican accomplish this?is it via aaa accounting? and which is the
commands to use?Every documention i found was not very helpful
Cheers
___
juniper-nsp mail
Hi Paul,
After some more investigation following has been found:
Mastership mismatch is not the cause of the JNPR sending MS bit on. It is
done to signal the master to reset the state machine to ExStart. JNPR does
this because state machine went to BadLSReq and restarted negotiation.
Dec 4 01:5
Hi,
Just a hint - can you use domain-id instead of sham-link? Take a look at
following links if you are concerned about what type of LSA you receive:
http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-vpns/id-10950345.html#id-10950345
http://www.juniper.net/techpubs/software/junos/j
Hi,
someone has a sample of a JunosScript that can intercept RTR traps and
act upon them.
Thanks,
Bit.
On Mon, 2007-12-03 at 23:49, Dale Ben wrote:
> Hi Eric,
>
> The JUNOS equivalent to SAA is called RPM or Real-time Performance
> Monitor [edit services rpm]. I don't think there is too mu
13 matches
Mail list logo
