SRX1500 Cluster - Possible bug with reth interfaces

Hi,

This is a pretty new product and I'm configuring a Chassis Cluster of it.

I'm running the current recommended version 15.1X49-D40 and I found a problem that if it is a bug it is very bad because it is a very basic stuff that works on the other SRX clusters I have configured during my life.

For example, I have a reth interface running LACP and composed of interfaces ge-0/0/0-1 and ge-7/0/0-1 configured like this:

show configuration interfaces reth0
vlan-tagging;
redundant-ether-options {
redundancy-group 1;
minimum-links 1;
lacp {
active;
}
}
unit 40 {
vlan-id 40;
family inet {
address 1.1.1.1/24;
}
}
unit 100 {
vlan-id 100;
family inet {
address 192.168.21.1/24;
}
}

where I have just created vlan 40. The other interfaces were already there and working.

I commited the configuration and noticed that the interface was not working.

I used the command show interfaces terse, and this is what I get:

Interface Admin Link Proto Local Remote
ge-0/0/0 up up
ge-0/0/0.100 up up aenet --> reth0.100
...
ge-0/0/1 up up
ge-0/0/1.100 up up aenet --> reth0.100

...

ge-7/0/0 up up

ge-7/0/0.100 up up aenet --> reth0.100
...
ge-7/0/1 up up
ge-7/0/1.100 up up aenet --> reth0.100
...
reth0.40 up down inet 1.1.1.1/24
reth0.100 up up inet 192.168.21.1/24
...

As you can see the reth0.40 was created but the interfaces that are part of the reth0 do not have the logical interface .40

I tried commiting again, rollbakc, everything but no results.

When I failover RG0 to the other node, I issue a show interfaces terse and there they are:

Interface Admin Link Proto Local Remote
ge-0/0/0 up up
ge-0/0/0.40 up up aenet --> reth0.40
ge-0/0/0.100 up up aenet --> reth0.100
...

ge-0/0/1 up up
ge-0/0/1.40 up up aenet --> reth0.40
ge-0/0/1.100 up up aenet --> reth0.100
...

ge-7/0/0 up up
ge-7/0/0.40 up up aenet --> reth0.40
ge-7/0/0.100 up up aenet --> reth0.100
...

ge-7/0/1 up up
ge-7/0/1.40 up up aenet --> reth0.40
ge-7/0/1.100 up up aenet --> reth0.100

As you might imagine, it is not very nice having to failover RG0, with all the consequences that it brings, to add a new logical interface to the firewall.

This happens also when I delete an interface.

Looks like some failure of talking between CP and DP.

Does anyone have experience with this?

I'm tempted to make a regression to the previous version but since it is a v1, not very fond of the idea.

I'll open a case but the serial numbers are not yet loaded in the support so I'm asking here if anyone might have some idea.

Thanks

Paulo