03-03-2010 05:34 PM
We just created a j-series cluster and as expected were greated with this warning when entering configuration mode:
warning: Clustering enabled; using private edit
warning: uncommitted changes will be discarded on exit
Entering configuration mode
The problem is when we build a configuration and try to use a "commit confirmed x" we get this error:
error: commit confirmed not supported for private configuration
I have done some major research on using the private configuration and understand you cannot use the "commit confirmed" command in private configuration mode so my questions are:
1. How do we get out of private configuration mode
2. Can we get out of private configuration mode in the current config we have built
3. Can you only use private edit in a cluster and if so how can you ever use commit confirmed?
Also when I issue the configure dynamic command I don't see an option to use commit confirmed either.
Is there anything else I need to know?
03-03-2010 07:19 PM
I'm no Junos expert, but I believe this will apply:
(found by searching http://kb.juniper.net for "configure private")
03-04-2010 02:05 AM
Thanks for the quick reply but if I issue the rollback command I lose all of the changes I just made correct? I was trying to avoid that.
03-04-2010 04:49 AM
Had the same problem December last year and got the following answer from support:
"You can no longer use commit confirmed when using a cluster because you are configuring private candidate configurations. I'm not sure why you can't continue using commit confirmed; I just know that the ability to use the command goes away with chassis clustering. So, you'll just want to make sure you're aware of the changes that you're making to the cluster before committing those changes from the primary node."
This is why we stopped selling j-series and srx-clusters (along with the inability to update the cluster without service interuption).
03-20-2010 09:26 AM
It appears that even though 'conf ?' only shows dynamic and private as valid completions, you can still use 'conf exclusive' which *will* allow you to commit confirmed. Just tested on an SRX650 cluster running 10.0r2.10.
If anyone can think of any problems exclusive mode might cause on a cluster, or any reason Juniper intentionally left it out of the valid completions but left it as a valid command, I'd love to hear it.... Otherwise I think I'll be using exclusive mode from now on....
10-04-2010 03:34 PM
I *did* find a problem caused by "configure exclusive", on an SRX240 cluster, 10.0r3.10.
While testing this out, I performed a minor change under "configure exclusive", then did a "commit confirmed 3" and let it time out. After the timeout the result was:
Commit was not confirmed; automatic rollback failed.
This left the cluster configuration inconsistent, preventing commits of *any* further changes with the error
error: remote lock-configuration failed on node1
I had to manually commit the proposed change on node1 to fix this situation, and JTAC verified that the "confirmed" mechanism will not work out for the cluster.
03-30-2011 08:35 AM
It would be great if they would fix this.
Commit confirmed is a great feature when working with a first line "less proficient" team to handle grunt work.
07-13-2011 01:20 AM
Still same problem with commit confirmed. It is very important feature especially I am working remotely and afraid to lose connectivity so each time have to visit the site to make change. Do we have any news or still same issue?