SRX

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



Expand all | Collapse all

Configure/commit issue

Jump to Best Answer
  • 1.  Configure/commit issue

    Posted 09-30-2015 08:10

    Hi all,

    When i applied a new configuration on my existing srx240, the commit button don't validate the new configuration, without any error message.

    And when i pass to CLI mode, and type "configure" i have the message below:


    root@--> configure
    warning: Clustering enabled; using private edit
    error: shared configuration database modified

    Please temporarily use 'configure shared' to commit
    outstanding changes in the shared database, exit,
    and return to configuration mode using 'configure'

    {primary:node0}

    Could you help to resolve and troubleshoot this issue, without losting the existing configuration, and also with zero time downtime?

    Many thanks for your help

    Regards,


    #Commit
    #issue
    #configure
    #SRX240


  • 2.  RE: Configure/commit issue
    Best Answer

    Posted 10-02-2015 08:46

    Hi,

    Delete the configured management and control interface on the device and their related configuration and commit the changes. This will help to resolve the issue.

    {hold:node0}
    root> edit
    warning: Clustering enabled; using private edit
    error: shared configuration database modified
    Please temporarily use 'configure shared' to commit
    outstanding changes in the shared database, exit,
    and return to configuration mode using 'configure'
    {hold:node0}
    root> configure shared
    Entering configuration mode
    The configuration has been changed but not committed
    {hold:node0}[edit]
    root# show interfaces | display set
    set interfaces fe-0/0/1 fastether-options redundant-parent reth0
    set interfaces fe-0/0/2 fastether-options redundant-parent reth1
    set interfaces fe-0/0/7 unit 0 family inet address 192.168.0.1/24 < (Control interface on SRX100)
    set interfaces fe-1/0/1 fastether-options redundant-parent reth0
    set interfaces fe-1/0/2 fastether-options redundant-parent reth1
    set interfaces fab0 fabric-options member-interfaces fe-0/0/5
    set interfaces fab1 fabric-options member-interfaces fe-1/0/5
    set interfaces reth0 redundant-ether-options redundancy-group 1
    set interfaces reth0 unit 0 family inet address 192.168.100.1/24
    set interfaces reth1 redundant-ether-options redundancy-group 1
    set interfaces reth1 unit 0 family inet address 172.16.1.1/24

    {hold:node0}[edit]
    root# delete interfaces fe-0/0/7
    {hold:node0}[edit]
    root# delete security zones security-zone trust interfaces fe-0/0/7.0
    {hold:node0}[edit]
    root# commit
    node0:
    commit complete
    {primary:node0}[edit]
    root@Node_0# run show interfaces terse
    Interface Admin Link Proto Local Remote
    fe-0/0/0 up down
    fe-0/0/1 up down
    fe-0/0/1.0 up down aenet --> reth0.0
    fe-0/0/2 up down
    fe-0/0/2.0 up down aenet --> reth1.0
    fe-0/0/3 up down
    fe-0/0/4 up down
    fe-0/0/5 up down
    fe-0/0/5.0 up down aenet --> fab0.0
    fe-0/0/6 up down
    fe-0/0/7 up up
    fab0 up down
    fab0.0 up down inet 30.17.0.200/24
    fxp0 up up
    fxp0.0 up up inet 10.20.30.1/24
    fxp1 up up
    fxp1.0 up up inet 129.16.0.1/2
    tnp 0x1100001
    gre up up
    ipip up up
    irb up up
    lo0 up up
    lo0.16384 up up inet 127.0.0.1 --> 0/0
    lo0.16385 up up inet 10.0.0.1 --> 0/0
    10.0.0.16 --> 0/0
    128.0.0.1 --> 0/0
    128.0.1.16 --> 0/0
    lo0.32768 up up
    lsi up up
    mtun up up
    pimd up up
    pime up up
    pp0 up up
    ppd0 up up
    ppe0 up up
    reth0 up down
    reth0.0 up down inet 192.168.100.1/24
    reth1 up down
    reth1.0 up down inet 172.16.1.1/24
    st0 up up
    tap up up
    {primary:node0}[edit]
    root@Node_0# run show chassis cluster status
    Cluster ID: 1
    Node Priority Status Preempt Manual failover
    Redundancy group: 0 , Failover count: 0
    node0 200 primary no no
    node1 1 secondary no no
    Redundancy group: 1 , Failover count: 0
    node0 200 primary no no
    node1 1 secondary no no


    refer to this link : https://voe0205.wordpress.com/

     

    [Please Mark My Solution Accepted if it Helped, Kudos are Appreciated Too]