> As there is quite a bit of voice traffic involved I asked if this was really
> per packet or if it was "per flow" as he had mentioned. I was told that
> even though the configuration uses the wording "per-packet" that it's really
> per flow occurring. It does appear to actually be some kind of
Yes, per-packet really means per-flow. The default is per-prefix. Have to use
mlpp to get per-packet.
Regards
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Paul Stewart
Sent: Thursday, May 20, 2010 5:52 PM
To
> M10i already has many peers that support *2 byte asn only* and is running
> without any issues, but *why it is not able to negotiate with Maipu to make
> the peer up without disabling the 4byte asn capability*.
>
> ASFAIK, 4 byte ASN or AS4_PATH is an optional transitive attribute unlike
> AS_P
Hi Chuck,
I applied the command (hidden/ undocumented) and it worked.
M10i already has many peers that support *2 byte asn only* and is running
without any issues, but *why it is not able to negotiate with Maipu to make
the peer up without disabling the 4byte asn capability*.
ASFAIK, 4 byte AS
Hi there
I opened a JTAC ticket this evening and looking for some opinion - after I
closed the case I'm not sure of what I was told...
The ticket was opened because leaving a EX4200 VC there are two GigE
connections going to a Cisco 6500 - so equal cost OSPF. According to the
routing t
set neighbor w.x.y.z disable-4byte-as
On Thu, May 20, 2010 at 09:03:55PM +0545, khagendra dhakal wrote:
> Dear all,
>
> Platform: M10i
> JUNOS: JUNOS 9.2R2.15
>
> Platform: Maipu 2800
> IOS: rp8-i-6.1.37(xnwt-11).bin), version 6.1.37
>
>
> PROBLEM: Has anyone had any bad experience on bgp peer
Dear all,
Platform: M10i
JUNOS: JUNOS 9.2R2.15
Platform: Maipu 2800
IOS: rp8-i-6.1.37(xnwt-11).bin), version 6.1.37
PROBLEM: Has anyone had any bad experience on bgp peering between the
above mentioned Devices with the following error: ?
Error:
BGP RECV xxx.xxx.xxx.xxx+3407 -> xxx.xxx.xxx.xxx
Hi everybody,
to complete this thread. JTAC just gave me a call because of my opened case
regarding this problem.
They confirmed that the problem is an issue in version 10.1r2.8. The workaround
is to reboot the srx after an upgrade with the no-validate command, to add the
wlan admin-authentica
Bill Blackford wrote:
Platform: EX3200-24T
JUNOS: 10.0S1.1
PROBLEM:
I have several EX series devices deployed and so far, and only one is
exhibiting the behavior of the routing-engine uptime being vastly different
from the actual system uptime.
When I issue:
show system uptime
I'm seeing th
9 matches
Mail list logo
