
Configuring Service Assurance Agent
Configuring Service Assurance Agent
page 36-6
OmniSwitch AOS Release 7 Network Configuration Guide
June 2013
Configuring an ETH-LB SAA
To configure an ETH-LB SAA, use the
command. For example:
-> saa saa1 type ethoam-loopback target-endpoint 10 source endpoint 1 domain md1
association ma1 vlan-priority 5 drop-eligible false
In this example, “saa1” is an existing SAA ID that is configured to run ETH-LB assurance iterations. The
additional command parameters apply to the specific loopback operation. Note that these parameters are
similar to those specified with the
ethoam loopback
command.
Configuring a ETH-DMM SAA
To configure a ETH-DMM SAA, use the
command. For example:
-> saa saa2 type ethoam-two-way-delay target-endpoint 10 source endpoint 1
domain md1 association ma1 vlan-priority 5
In this example, “saa2” is an existing SAA ID that is configured to run two-way ETH-DMM assurance test
iterations. The additional command parameters apply to the specific delay measurement operation. Note
that these parameters are similar to those specified with the
ethoam two-way-delay
command.
Starting and Stopping SAAs
Once an SAA ID is created and the type of SAA is configured, the SAA start and stop parameters are
defined using the
commands. For example:
-> saa saa1 start
-> saa saa1 stop
Both commands provide the ability to define a specific start and stop time for the SAA. For example:
-> saa saa2 start at 2010-09-12,09:00:00
-> saa saa2 stop at 2010-09-19,09:00:00
In addition, the
saa stop
command provides a
never
parameter to specify that the SAA will not stop unless
a specific date and time is specified with the
saa stop
command. For example:
1
-> saa saa2 start
2
-> saa saa2 stop never
3
-> saa saa2 stop (
SAA does not stop
)
4
-> saa saa2 stop at 2010-09-19,09:00:00 (
SAA stops
)
In this example, the first command starts “saa2”. Note that because a date and time was not specified, the
SAA starts immediately. The second command specifies that “saa2” will never stop unless a date and time
is specified. As a result, the third command will fail because it does not specify a date and time. The fourth
command, however, will successfully stop the SAA at the specified date and time.
Configuring SAA SPB Session Parameters
The Shortest Path Bridging (SPB) feature dynamically discovers SPB-enabled switches. Each discovered
switch is identified by the pairing of an SPB VLAN (BVLAN) and the backbone MAC address (BMAC)
for the switch. SPB advertises these BVLAN-BMAC pairs to the SAA feature, which in turn creates and
starts MAC ping sessions based on the parameters configured with this command.