Le 30/05/2013 07:25, Farrukh Haroon a écrit :
Also if the link is passing through high-end Cisco switches you might have
to disable IP header checks, as mentioned in this KB article:
http://kb.juniper.net/InfoCenter/index?page=contentid=KB15141
I couldn't find anything related to ip header
Le 30/05/2013 07:28, Andrew Jones a écrit :
There is a hidden command you can use which is show chassis cluster
information detail which will give you a lot more information about how
the cluster is set up on each node and if there are any errors in regards
to the control link and fabric link.
Hi all,
I'm currently trying to setup a cluster of srx3400 using a pair of cisco
nexus to connect
control and data link for redundancy. Junos Version is 11.4r7.
Each SRX3400 uses one RE, one CRM, one SPC and one NPC.
The first node from the cluster is fine but the second node doesn't come
4090, however in later
versions of code that default behavior may have changed, and I think the VLAN
ID it uses is now configurable.
Thanks,
Will
On May 29, 2013, at 8:42 PM, juniper-nsp-requ...@puck.nether.net wrote:
Subject: [j-nsp] srx cluster - control and data link throuigh cisco
: [j-nsp] srx cluster - control and data link throuigh cisco
nexus switches
Message-ID: 51a64466.8070...@yahoo.fr
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi all,
I'm currently trying to setup a cluster of srx3400 using a pair of cisco
nexus to connect
control
Le 30/05/2013 02:53, Nicholas Oas a écrit :
Is igmp snoop disabled on the Ethernet ports which connect the data
and control links?
Yes it is. I forgot to mention that.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
Le 30/05/2013 05:56, Payam Chychi a écrit :
I 2nd this, check your mtu settings end to end, keep in mind the differences
between cisco and juniper when it comes to calculating lowest required mtu value
Mismatch mtu tends to have some very odd behaviour on protocols
MTU has been checked.
traffic is tagged
with VLAN 4090, however in later versions of code that default behavior may
have changed, and I think the VLAN ID it uses is now configurable.
Thanks,
Will
On May 29, 2013, at 8:42 PM, juniper-nsp-requ...@puck.nether.net wrote:
Subject: [j-nsp] srx cluster - control
Hi all,
some questions this morning :
- can I use the same vlan for both control links ? (em0 and em1 use the
same ip address).
- can I use the same vlan for control and data link ?
thanks
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
There is a hidden command you can use which is show chassis cluster
information detail which will give you a lot more information about how
the cluster is set up on each node and if there are any errors in regards
to the control link and fabric link. In particular check that the control
port
10 matches
Mail list logo
