Forgot to mention another important bits.

There is no filter on MX and the SRX is configured to allow all inbound 
services and protocols.

ihsan

On Jun 19, 2012, at 1:10 AM, Ihsan Junaidi Ibrahim wrote:

> Folks,
> 
> Here's my situation.
> 
> I have an MX5 configured to dual-homed to two sets of SRX240 in a cluster 
> with the intention of running OSPF + BGP between them.
> 
> The links are straight point to points with no switch in between.
> 
> OSPF between the two works alright, so does static. BGPv4 and BGPv6 (static 
> routing) works OK.
> 
> My problem is with OSPF3, no matter what I configured, the session just won't 
> come up.
> 
> Curiously, the link-locals are not seen on both sides.
> 
> ihsan@b1> show ipv6 neighbors 
> IPv6 Address                 Linklayer Address  State       Exp Rtr Secure 
> Interface
> 1111:1111:1::222             00:10:db:ff:10:03  reachable   5   yes no      
> ge-1/0/9.0 
> 
> ihsan@a1-node0> show ipv6 neighbors 
> IPv6 Address                 Linklayer Address  State       Exp Rtr Secure 
> Interface
> 1111:1111:1::223             a8:d0:e5:52:f8:28  reachable   31  yes no      
> reth3.0  
> 
> ihsan@a1-node0> show interfaces reth0 | match fe80 
>        Destination: fe80::/64, Local: fe80::210:dbff:feff:1000
> 
> ihsan@b1> show interfaces irb.0 | match fe80 
>        Destination: fe80::/64, Local: fe80::aad0:e5ff:fe52:f828
> 
> The OSPF3 hellos are sent out on both sides but only the MX is not receiving 
> hence the current state of OSPF3 Init on the SRX.
> 
> The config is just plain routing. No fancy MPLS, CoS stuff etc.
> 
> I have another MX5 and SRX240, plain routing with IPv6, without cluster and 
> IRBs. OSPFv3 works alright.
> 
> So I'm guessing it's either the cluster setup or the IRB or maybe combo of 
> both.
> 
> I'm on 11.4R3.7.
> 
> MX5
> ---
> ihsan@b1> show configuration interfaces irb 
> unit 0 {
>    description "L3 interface to ACS bridge domain";
>    family inet {
>        address 111.111.16.223/31;
>    }
>    family inet6 {
>        address 1111:1111:1::223/127;
>    }
> }
> 
> ihsan@b1> show configuration interfaces ge-1/0/9  
> description "To ge-1/0/0::a1-node0";
> mtu 9192;
> encapsulation ethernet-bridge;
> unit 0 {
>    family bridge;
> }
> 
> ihsan@b1> show configuration interfaces ge-1/1/9    
> description "To ge-1/0/0::a1-node1";
> mtu 9192;
> encapsulation ethernet-bridge;
> unit 0 {
>    family bridge;
> }
> 
> ihsan@b1> show configuration bridge-domains 
> acs-bridge {
>    domain-type bridge;
>    vlan-id none;
>    interface ge-1/0/9.0;
>    interface ge-1/1/9.0;
>    routing-interface irb.0;
> }
> 
> ihsan@b1> show configuration protocols ospf3      
> area 0.0.0.0 {
>    interface lo0.0 {
>        passive;
>    }
>    interface irb.0 {
>        interface-type p2p;
>    }
> }
> 
> SRX cluster
> ---
> {primary:node0}
> ihsan@a1-node0> show configuration interfaces reth3                   
> mtu 9192;
> redundant-ether-options {
>    redundancy-group 4;
> }
> unit 0 {
>    bandwidth 1g;
>    family inet {
>        address 111.111.16.222/31;
>    }
>    family inet6 {
>        address 1111:1111:1::222/127;
>    }
> }
> 
> {primary:node0}
> ihsan@a1-node0> show configuration protocols ospf3                  
> area 0.0.0.0 {
>    interface lo0.0 {
>        passive;
>    }
>    interface reth3.0 {
>        interface-type p2p;
>    }
> }
> 
> ihsan@a1-node0> show ospf3 neighbor 
> ID               Interface              State     Pri   Dead
> 111.111.16.159   reth3.0                Init      128     33
>  Neighbor-address fe80::aad0:e5ff:fe52:f828


_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to