SRX

last person joined: 4 days ago 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
  • 1.  '${NODE}' is not defined

    Posted 02-01-2011 16:53

    I'm getting a pair of SRX240s set up in a chassis cluster. I've enabled clustering on what will be the primary node. I'm just getting started following KB15504 for the initial setup and hit a little snag,

     

     

    {primary:node0}[edit]
    root@covfw0# commit
    [edit]
      'apply-groups "${NODE}"'
        Configuration group '${NODE}' is not defined
    error: commit failed: (missing statements)

     For now, as a workaround, I can just set that to "node0," but am I missing something obvious here?

     



  • 2.  RE: '${NODE}' is not defined

    Posted 02-01-2011 17:08

    Can't tell from you what typed exactly what your config reads. Did you define your node0 and node1 data? The apply-groups node command acts on that.

     

    IE -

    groups {

                    node0 {

                           system {

                                  host-name xxxxxxxx

    .......................

    groups {

                    node1 {

                           system {

                                  host-name yyyyyyyyy

    ........................

     

    Can you post your config in more detail?



  • 3.  RE: '${NODE}' is not defined

    Posted 02-01-2011 20:20

    I don't think this has anything to do with the "group" commands, but this is what I have,

     

    groups {
        node0 {
            system {
                host-name covfw0;
            }
            interfaces {
                fxp0 {
                    unit 0 {
                        family inet {
                            address 172.18.4.250/24;
                        }
                    }
                }
            }
        }
        node1 {
            system {
                host-name covfw1;
            }
            interfaces {
                fxp0 {
                    unit 0 {
                        family inet {
                            address 172.18.4.251/24;
                        }
                    }
                }
            }
        }
    }

    Now what makes me think that those are OK is that when I put in,

     

    apply-groups node0

     Which is what I have as a workaround, it works fine.

     

    But if I change that to "${NODE}", which is what it will need to be to get node1 to work correctly, I get,

     

    {primary:node0}[edit]
    root@covfw0# delete apply-groups node0 
    
    {primary:node0}[edit]
    root@covfw0# set apply-groups "${NODE}" 
    
    {primary:node0}[edit]
    root@covfw0# show apply-groups 
    ## Last changed: 2011-02-02 11:57:23 UTC
    apply-groups "${NODE}"; ## '${NODE}' is not defined
    
    {primary:node0}[edit]
    root@covfw0# commit check 
    [edit]
      'apply-groups "${NODE}"'
        Configuration group '${NODE}' is not defined
    error: configuration check-out failed: (missing statements)
    
    {primary:node0}[edit]
    root@covfw0# 

     

     

     

     

     



  • 4.  RE: '${NODE}' is not defined
    Best Answer

    Posted 02-01-2011 21:41

    Grrrr... KB15504 says "${NODE}", but the correct syntax is "${node}".



  • 5.  RE: '${NODE}' is not defined

    Posted 04-17-2015 02:03

    Hello,

     

    can someone explain to me,  what the  group '${NODE} does??

     

    Thanks



  • 6.  RE: '${NODE}' is not defined

     
    Posted 05-18-2016 04:18

    The configuration you specified under group node0 will be active only on node0 and the one you specified under group node1 will be active only on node1.

     

    Basically you have different active config on node0 and node1.

     

    Simple example, this is used when you need seperate hostnames and management IPs for Node0 and Node1