Cisco SPA2102-AU Provisioning Guide - Page 37

Assignment Expressions, Operator, Alternate, Syntax, Description, Applicable to Integer - upgrade rule

Get Cisco SPA2102-AU PDF manuals and user guides View all Cisco SPA2102-AU manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

Chapter 2 Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2.0.6 Quoted strings can be compared for equality or inequality. Integers and version numbers can also be compared arithmetically. The comparison operators can be expressed as symbols or as acronyms, as indicated in the table below. Acronyms are particularly convenient when expressing the condition in an XML-style profile. Table 2-2 Comparison Operators for Conditional Expressions Operator = != < >= Alternate Syntax eq ne lt le gt ge Description Applicable to Integer and Version Operands equal to Yes not equal to Yes less than Yes less than or Yes equal to greater than Yes greater than or Yes equal to Applicable to Quoted String Operands Yes Yes No No No No For legacy support to firmware versions prior to 2.0.6, the not-equal-to operator can also be expressed as a single ! character (in place of the two-character != string). Conditional expressions typically involve macro-expanded variables. For example, $REGTMR1 gt 300 and $PRVTMR gt 1200 and "$EXTIP" ne "" $SWVER ge 2.0.6 and "$CCERT" eq "Installed" It is important to enclose macro variables in double quotes where a string literal is expected. Do not do so doing so where a number or version number is expected. For legacy support of firmware versions prior to 2.0.6, a relational expression with no left-hand-side operand assumes $SWVER as the implicit left-hand-side. For example, ! 1.0.33 is equivalent to: $SWVER != 1.0.33. When used in the context of the Profile_Rule* and Upgrade_Rule parameters, conditional expressions must be enclosed within the syntax "( expr )?" as in the following upgrade rule example: ( $SWVER ne 2.0.6 )? http://ps.tell.com/sw/spa021024.bin On the other hand, the syntax above using parentheses should not be used when configuring the Resync_Trigger_* parameters. Assignment Expressions Arbitrary parameters can be pre-assigned values within the context of Profile_Rule* and Upgrade_Rule parameter. This causes the assignment to be performed before the profile if retrieved. The syntax for performing these assignments is a list of individual parameter assignments, enclosed within parentheses ( assignments )!, with each assignment taking the form: ParameterXMLName = "Value" ; Note that the recognized parameter names correspond to the names as for XML-based profiles. Version 3.0 Linksys SPA Provisioning Guide 2-11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
2-11
Linksys SPA Provisioning Guide
Version 3.0
Chapter 2
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
2.0.6
Quoted strings can be compared for equality or inequality. Integers and version numbers can also be
compared arithmetically. The comparison operators can be expressed as symbols or as acronyms, as
indicated in the table below. Acronyms are particularly convenient when expressing the condition in an
XML-style profile.
For legacy support to firmware versions prior to 2.0.6, the not-equal-to operator can also be expressed
as a single ! character (in place of the two-character != string).
Conditional expressions typically involve macro-expanded variables. For example,
$REGTMR1 gt 300 and $PRVTMR gt 1200 and “$EXTIP” ne “”
$SWVER ge 2.0.6 and “$CCERT” eq “Installed”
It is important to enclose macro variables in double quotes where a string literal is expected. Do not do
so doing so where a number or version number is expected.
For legacy support of firmware versions prior to 2.0.6, a relational expression with no left-hand-side
operand assumes $SWVER as the implicit left-hand-side. For example, ! 1.0.33 is equivalent to:
$SWVER != 1.0.33.
When used in the context of the Profile_Rule* and Upgrade_Rule parameters, conditional expressions
must be enclosed within the syntax “( expr )?” as in the following upgrade rule example:
On the other hand, the syntax above using parentheses should not be used when configuring the
Resync_Trigger_* parameters.
Assignment Expressions
Arbitrary parameters can be pre-assigned values within the context of Profile_Rule* and Upgrade_Rule
parameter. This causes the assignment to be performed before the profile if retrieved.
The syntax for performing these assignments is a list of individual parameter assignments, enclosed
within parentheses ( assignments )!, with each assignment taking the form:
ParameterXMLName = “Value” ;
Note that the recognized parameter names correspond to the names as for XML-based profiles.
Table 2-2
Comparison Operators for Conditional Expressions
Operator
Alternate
Syntax
Description
Applicable to Integer
and Version Operands
Applicable to Quoted
String Operands
=
eq
equal to
Yes
Yes
!=
ne
not equal to
Yes
Yes
<
lt
less than
Yes
No
<=
le
less than or
equal to
Yes
No
>
gt
greater than
Yes
No
>=
ge
greater than or
equal to
Yes
No