SRX Services Gateway
SRX Services Gateway

manage devices in a cluster on interfaces other than fxp0

03.04.10   |  
‎03-04-2010 03:29 AM

Hello,

 

Is it possible to manage devices that are in a cluster without having to go through fxp0.

 

In screenos we could have a seperate management address.

 

I assume that we could do this by creating another interface that is not in a reth group but this would need to be on a seperate subnet.

 

Is it possible to have an address on the same subnet as a reth group for individual management of each device - like a management address?

3 REPLIES
SRX Services Gateway

Re: manage devices in a cluster on interfaces other than fxp0

03.08.10   |  
‎03-08-2010 04:51 PM

Unfortunately, at the moment there is no way to do this.  You should check with JTAC on this.

 

-Mike

SRX Services Gateway

Re: manage devices in a cluster on interfaces other than fxp0

03.10.10   |  
‎03-10-2010 05:39 PM

fxp0 is not firewalled thats why cant be in same subnet and same VRF.

 

thanks

raheel

Follow me on Twitter @anwar_raheel

--
If this post was helpful, please mark this post as an "Accepted Solution".
Kudos are always appreciated!
Highlighted
SRX Services Gateway

Re: manage devices in a cluster on interfaces other than fxp0

03.18.10   |  
‎03-18-2010 09:20 PM

JSRP has many differences compared with ScreenOS NSRP. In JSRP only one node has active RE which controls both nodes which acts as one logical box. With NSRP each node is always independently managed. Architecturally, ScreenOS does not have any sort of separation of control and data planes. Hence each node must act independently. JUNOS devices have a clear separation of control and data planes which offers many advantages. But there can only ever be one active RE. So when you manage the device from primary node you are actually managing both nodes.

 

However, if you DO ever need to hop over to secondary node, you can always log into primary node and then use below command to hop over to secondary node.

 

request routing-engine login node <node-#>

 

-Richard