Yes I can understand, But i need to use the cluster and intend to add the secondary device again to the cluster. I hope it will set to the configured priorities after connecting both devices in the cluster as cold sync or flowd runs at the time of reboot to syc SPUs.
regards, Muhammad Fahad Khan JNCIP - M/T # 834 IT Specialist Global Technology Services, IBM [email protected] +92-301-8247638 Skype: fahad-ibm http://pk.linkedin.com/in/muhammadfahadkhan On Sat, Sep 18, 2010 at 5:14 AM, Harshit Kumar <[email protected]> wrote: > On a single node cluster, priority has no significance. You > can safely ignore this. You can move to stand-alone mode if > you don't plan to use the cluster. > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Fahad Khan > Sent: Friday, September 17, 2010 8:05 AM > To: [email protected] > Subject: [j-nsp] Chassis Cluster - Strange behavior > > Hi Folks, > > I have been running SRX3600 In chassis cluster. > > At the moment, I have disconnected control link and fabric link and > Secondary device is isolated from the network. But on primary device, the > cluster configs are still there. The network is working fine with primary > device but when i see chassis cluster status, i find this > > SRX3600-A> show chassis cluster status > Cluster ID: 1 > Node Priority Status Preempt Manual failover > > Redundancy group: 0 , Failover count: 1 > node0 254 primary no no > node1 0 lost n/a n/a > > Redundancy group: 1 , Failover count: 1 > node0 0 primary yes no > node1 0 lost n/a n/a > > why I am getting Node0 priority as 0 for red group 1, while i has been set > to 254??? > > have any body experienced????? > > thanks and regards, > > > Muhammad Fahad Khan > JNCIP - M/T # 834 > IT Specialist > Global Technology Services, IBM > [email protected] > +92-301-8247638 > Skype: fahad-ibm > http://pk.linkedin.com/in/muhammadfahadkhan > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
