On MX, you can create access-ports connected to the hosts using
"interface-mode access" with a unique vlan id assigned to the port. This is
conceptually similar to "switchport mode access" on Cisco.
With either "interface-mode access" you do not need to explicitly assign the
logical unit to the br
On Tue, May 04, 2010 at 05:05:04PM -0400, Paul Stewart wrote:
>
> Can someone give me in "simple terms" what the differences are between
> "chassis network-services Ethernet" and "chassis network-services IP"?
When Juniper came out with the MX they had two large potential customer
bases with tw
I'll try to help... We also run MX and EX.
So, first off. MX and EX are not even remotely related in respect to
what they can and can not do. The MX is a L3 box with L2 capabilities,
the EX is a L2 box with L3 capabilities.
So, vlans in an MX are not global (at least not necessarily). This me
I don't have time to get all of it but very quickly the command you mentioned:
set chassis network-services ip;
refers to if you want this MX to be a L2 or L3 box. Changing this
requires a reset AFAIK. When in "network-services ethernet" mode you
can only use the DPC-X cards which are priced chea
Hi there..
I'm not sure if I'm asking this right . again, as I mentioned earlier - I'm
a Cisco guy jumping into the JunOS world so pardon me if I've missed this
somewhere in the docs. my translation between the two worlds is "slow but
steady"..
Working on an MX480 that has a pair of DPC car
Hi,
In this router, we have configured 2 logical router. In the 'physical'
we have only one provider (one full-routing) and in the logical one we
are connected to 2 providers (2 full-routing). Are these events for both
logical routers? They are differents providers, why should I configure
alw
Looks like there's a persistent oscillation in your routing topology. If you
see routes i.e. 195.240.208.0 that comes from different peer ASes, you might
want to configure always-compare-med in your bgp path-selection statement.
By default, it will only compare routes that come from the same peer A
Chris & David... thank you VERY much - this is exactly the info I needed
I can start working on configuration migrations now..;)
Appreciate it... cheers...
Paul
-Original Message-
From: David Ball [mailto:davidtb...@gmail.com]
Sent: Tuesday, May 04, 2010 10:59 AM
To: Paul Stewart
C
Hello,
I've just executed this comand on the shell and it appeared a lot of routes:
r...@eg01% rtsockmon -t rpd
sender flagtype op
[17:30:29] rpd Proute add inet6 2401:ee00:: tid=2
plen=32 type=user flags=0x10 nh=indr nhflags=0x4 nhidx=262144 filtidx=0
[17:
I tend to use groups (under [edit groups]) to create sections of
commonly-applied configurations. Very nice JUNOS feature. This might
be where you'd list elements that would apply to multiple BGP
neighbours (though groups can be used for ANY configuration elements
that you might want to reuse..
Ahh now that makes sense. Yes the other card is a DPC card.
In order to correct this, I'll have to migrate our connections the MPC
card. Do you know if a reload is required or can I just pull the DPCs
and online the MPC?
Thanks,
Michael
On Tue, May 4, 2010 at 2:46 AM, Richard A Steenbergen wro
On Tue, May 4, 2010 at 08:16, Paul Stewart wrote:
> Hi folks.
>
>
>
> I'm having a hard time getting a 'stock configuration' done on JunOS for
> eBGP peering.. Been reading Juniper docs and keep circling back with more
> questions than answers ;)
>
>
>
> Could someone get me pointed in the right d
Hi folks.
I'm having a hard time getting a 'stock configuration' done on JunOS for
eBGP peering.. Been reading Juniper docs and keep circling back with more
questions than answers ;)
Could someone get me pointed in the right direction? .
In Cisco, we do this:
neighbor xxx.32.235.3
Hello there,
This message has appeared in the log of our M20. It is not the first
time it occurs and we are quite worried. The average CPU consumption is
4% and just at the time the message appeared on the log, we found
increases up to 100% and an increase in temperature of 6 º in the
routing
So in my case, sanity checks mean the from action in term 3, if term 3 is
true then only jump to next policy and if not then continue to the next
term(term 4) and that will be reject, correct me if I am wrong.
On Tue, May 4, 2010 at 8:43 AM, wrote:
> Hi David,
>
> Here "next policy" means the de
Hi David,
Here "next policy" means the default BGP policy which by default accepts all
BGP routes that pass sanity checks.
Vladi
Sent from my BlackBerry® wireless device
-Original Message-
From: David water
Date: Tue, 4 May 2010 08:31:22
To:
Subject: [j-nsp] policy from JNCIP book
Hi,
I am trying to understand the policy in BGP, in JNCIP book we have following
policy with term 1 to 3. Term 1 and 2 is rejecting all unwanted routes and
term 3 is matching those are originating in C1 and reference to the next
policy. So here next policy will be next term (term4) if so then it w
Dear Nick,
You could check your IPSec logs to dig down the exact reason due to which
tunnel is dropping. It must be some parameter mismatch. Normally if your
establish tunnel between cisco devices and there is a parameter mismatch,
the tunnel wont establish. but incase of juniper the tunnel will e
18 matches
Mail list logo