I recommend 4 x 208V. The MX960 uses "power zones" in a 2+2
arrangement where half of the chassis is powered by 2 PEMs, and the
other half of the chassis is powered by the other 2 PEMs. Make sure
the 1st PEM for each zone is powered by the A feed, and the 2nd PEM
for each zone is powered by the
Hi Christian,
Exactly, ISSU aborts just after checking conformity of the configuration
with the targeted OS version. JTAC was unable to give us an rational
explanation about this.
Best regards.
2016-01-26 8:38 GMT+01:00 Christian Beyerlein <
christian.beyerlein+juniper-...@net-m.de>:
> Thx
❦ 25 janvier 2016 13:33 -0500, Chuck Anderson :
> There are two ways to do bridge-domains and vlan trunks on MX. The
> old way uses separate units for each VLAN. The new way uses a single
> unit 0 with all vlans in a family bridge. Try doing it the "old" way,
> pre-"family
❦ 25 janvier 2016 11:03 -0500, "Tim St. Pierre" :
> I'm pretty sure you have to add the interfaces to the bridge domains:
>
> vlan-200 {
> domain-type bridge;
> vlan-id 200;
> routing-interface irb.2;
> ++ interface xe-0/0/2.0;
> }
>
> We use a similar
Hi!
Does anyone already use 12.3X48 on datacenter SRX (SRX3600 HA)?
We are currently on 12.1X44 and would like to skip 12.1X46 and 12.1X47,
but 12.3X48 is not yet "JTAC recommended".
Any stability issues observed? Will ISSU work from 12.1X44?
We use only basic features, FW/NAT and ALG for
Hey!
Currently, I am using an IRB interface on a MX104:
For example, on xe-2/0/2, I have:
#v+
vlan-tagging;
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list [ 200 300 ];
}
}
#v-
I have this bridge domain:
#v+
vlan-200 {
domain-type bridge;
vlan-id
I'm pretty sure you have to add the interfaces to the bridge domains:
vlan-200 {
domain-type bridge;
vlan-id 200;
routing-interface irb.2;
++ interface xe-0/0/2.0;
}
We use a similar setup on MX, and it works well.
On 2016-01-25 10:34 AM, Vincent Bernat wrote:
Hey!
Currently,
Hi,
Just upgraded an SRX5600 HA cluster from 12.1X46-D20 to 12.3X48-20 without any
problem... so far (3 weeks ;-).
Only issue we encountered was with ISSU not accepting too much lt interfaces
between multiple L-SYSs, there is a listed PR in junos 12.3X48 release notes.
No matter what we tried
On Mon, Jan 25, 2016 at 05:45:25PM +0100, Vincent Bernat wrote:
> ❦ 25 janvier 2016 11:03 -0500, "Tim St. Pierre"
> :
>
> > I'm pretty sure you have to add the interfaces to the bridge domains:
> >
> > vlan-200 {
> > domain-type bridge;
> > vlan-id 200;
> >
Hello,
Please see below inline marked with [AA].
Thx
Alex
On 25/01/2016 07:08, Nathan Ward wrote:
Hi,
On 25/01/2016, at 19:48, Alexander Arseniev wrote:
On 24/01/2016 23:01, Nathan Ward wrote:
This sort of works, except there’s a strong chance that the attacker
Hello,
I am working on it. This may be my next patent :-)
Thx
Alex
On 25/01/2016 09:02, Nathan Ward wrote:
Hi,
It sounds like you’re quite positive that it works - perhaps you can
provide some examples of when it’s worked in practice?
--
Nathan Ward
I have two SRX3600 connected as A-P HA cluster, and there is a loopback
interface used for VPN termination and assigned to redundancy-group-1.Its
working in the primary firewall, but when I failover to the second firewall and
then failover again to the first firewall, the loopback interface
What are the options for powering a MX960 using AC power? The datacenter
provider is offering us power in the following options:
120V/20AMP A/B Power
120V/30AMP A/B Power
208V/30AMP A/B Power
We are leaning towards using a MX960 with 4 AC power supplies and limited
cards installed. More than
13 matches
Mail list logo