Cisco SPA2102-AU Provisioning Guide - Page 43

Profile Rules

Page 43 highlights

Chapter 2 Creating Provisioning Scripts Using Provisioning Parameters In this example, the SPA periodically resyncs every hour (plus an additional random delay of up to 10 minutes). In case of resync failure, the SPA retries in 30 minutes (plus up to five minutes more). If it fails again, it waits an additional hour (plus up to 10 minutes). If again unsuccessful, it waits two more hours (plus up to 15 minutes), and so also thereafter, until it successfully resyncs. The following is another example: Upgrade_Error_Retry_Delay = 1800,3600,7200,14400+3600 In this example, if a remote upgrade attempt fails, the SPA retries the upgrade in 30 minutes, then again after one more hour, then in two hours. If it still fails, it subsequently retries every four to five hours, until it succeeds. Profile Rules The SPA provides multiple remote configuration profile parameters (Profile_Rule*). This means that each resync operation can retrieve multiple files, potentially managed by different servers. In the simplest scenario, the SPA resyncs periodically to a single profile on a central server, which updates all pertinent internal parameters. Alternatively, the profile can be split between different files. One file is common for all the SPAs in a deployment, while a separate file is provided that is unique for each account. Encryption keys and certificate information could be supplied by still another profile, stored on a separate server. Whenever a resync operation is due, the SPA evaluates the four Profile_Rule* parameters in sequence: 1. Profile_Rule 2. Profile_Rule_B 3. Profile_Rule_C 4. Profile_Rule_D Each evaluation may result in a profile being retrieved from a remote provisioning server, possibly updating some number of internal parameters. If any of these evaluations fails, the resync sequence is interrupted, and is retried again from the beginning specified by the Resync_Error_Retry_Delay parameter (seconds). If all evaluations succeed, the SPA waits for the second specified by the Resync_Periodic parameter, and then resync once more. The contents of each Profile_Rule* parameter consist of a set of alternatives. The alternatives are separated by the | character. Each alternative consists of a conditional expression, an assignment expression, a profile URL, and any associated URL options. All these components are optional within each alternative. The following are the valid combinations, and the order in which they must appear, if present: [ conditional-expr ] [ assignment-expr ] [[ options ] URL ] Within each Profile_Rule* parameter, all of the alternatives except the last one must provide a conditional expression. This expression is evaluated and processed as follows: 1. Conditions are evaluated from left to right, until one is found that evaluates as true (or until one alternative is found with no conditional expression) 2. Any accompanying assignment expression is evaluated, if present 3. If a URL is specified as part of that alternative, an attempt is made to download the profile located at the specified URL, and update the internal parameters accordingly. Version 3.0 Linksys SPA Provisioning Guide 2-17

  • 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-17
Linksys SPA Provisioning Guide
Version 3.0
Chapter 2
Creating Provisioning Scripts
Using Provisioning Parameters
In this example, the SPA periodically resyncs every hour (plus an additional random delay of up to 10
minutes). In case of resync failure, the SPA retries in 30 minutes (plus up to five minutes more).
If it fails again, it waits an additional hour (plus up to 10 minutes). If again unsuccessful, it waits two
more hours (plus up to 15 minutes), and so also thereafter, until it successfully resyncs.
The following is another example:
Upgrade_Error_Retry_Delay
=
1800,3600,7200,14400+3600
In this example, if a remote upgrade attempt fails, the SPA retries the upgrade in 30 minutes, then again
after one more hour, then in two hours. If it still fails, it subsequently retries every four to five hours,
until it succeeds.
Profile Rules
The SPA provides multiple remote configuration profile parameters (Profile_Rule*). This means that
each resync operation can retrieve multiple files, potentially managed by different servers.
In the simplest scenario, the SPA resyncs periodically to a single profile on a central server, which
updates all pertinent internal parameters. Alternatively, the profile can be split between different files.
One file is common for all the SPAs in a deployment, while a separate file is provided that is unique for
each account. Encryption keys and certificate information could be supplied by still another profile,
stored on a separate server.
Whenever a resync operation is due, the SPA evaluates the four Profile_Rule* parameters in sequence:
1.
Profile_Rule
2.
Profile_Rule_B
3.
Profile_Rule_C
4.
Profile_Rule_D
Each evaluation may result in a profile being retrieved from a remote provisioning server, possibly
updating some number of internal parameters. If any of these evaluations fails, the resync sequence is
interrupted, and is retried again from the beginning specified by the Resync_Error_Retry_Delay
parameter (seconds). If all evaluations succeed, the SPA waits for the second specified by the
Resync_Periodic parameter, and then resync once more.
The contents of each Profile_Rule* parameter consist of a set of alternatives. The alternatives are
separated by the | character. Each alternative consists of a conditional expression, an assignment
expression, a profile URL, and any associated URL options. All these components are optional within
each alternative. The following are the valid combinations, and the order in which they must appear, if
present:
[ conditional-expr ] [ assignment-expr ] [[ options ] URL ]
Within each Profile_Rule* parameter, all of the alternatives except the last one must provide a
conditional expression. This expression is evaluated and processed as follows:
1.
Conditions are evaluated from left to right, until one is found that evaluates as true (or until one
alternative is found with no conditional expression)
2.
Any accompanying assignment expression is evaluated, if present
3.
If a URL is specified as part of that alternative, an attempt is made to download the profile located
at the specified URL, and update the internal parameters accordingly.