The only issue I have come across is unsupported command/feature causing the config not load, and also preventing the startup of the management daemon. In the case I worked on it was the link-speed option tied to a RETH interface on a cluster. It doesn't appear to happen every time. I tried to reproduce on a SRX 210 cluster and I could get it to fail the same way.
If your SRXs come up and stay in a hold state and if the results of many operation commands result in "error: Could not connect to node0 : No route to host" type of error you are probably experiencing the issue. JTAC fixed the issue pretty quickly by starting a shell and running the following commands: % cd /var/run/db % mgd -i Which produced an error about link speed mismatch between the RETH and the GE interface. He then edited the configuration by deleting the option from the RETH interface and committed. After a reboot the SRX can back online and became a member of the cluster. Ralph -----Original Message----- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Daniel M Daloia Jr Sent: Thursday, July 28, 2011 9:57 AM To: juniper-nsp@puck.nether.net Subject: [j-nsp] JUNOS 10.4R4.5 on an SRX650 Hey Folks, Anyone using the current recommended release 10.4R4.5 on the SRX650 series? We have a pretty simple setup with clustering, IDP, BGP, OSPF. Just looking for any got-chas! Thanks! _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
