Package sas
The XML API OSS interface uses the sas package for service assurance operations,
OAM maintenance tests, and test suite management. This package defines common interfaces
and operations for service assurance, OAM tests, test policies, and test suites. Specific tests
are defined in the package of the objects they test. For example, LSP Ping and LSP Trace are
defined in the mpls package.
The sas package ensures that the
- service is operational
- paths are passing traffic
- FIB information is correct
For in-band, packet-based testing, the OAM test packets closely resemble customer
packets to effectively test the customer's forwarding path. However, these packets
are distinguishable from customer packets, so they are kept within the service
provider's network and not forwarded to the customer.
Service assurance tests are divided into the following broad categories:
- ping tests (subclasses of
sas.Ping)
- trace tests (subclasses of
sas.Trace)
- actions (subclasses of
sas.Action).
Each test comes in three varieties -- a test (a subclass of sas.Test), a deployed test
(a subclass of sas.DeployedTest), or a test definition (a subclass of sas.TestDefinition).
Generally, deployed tests are transient objects that are created
when the sas.Test is executed. The deployed test is then removed when the test completes
and the results are retrieved from the node and associated with the sas.Test.
Test definitions are used in conjunction with test policy and test suites.
A test policy is used to group a set of related sas.TestDefinitions.
The test suite is then bound to a specific sas.TestPolicy and
a sas.TestedEntity (which points a managed object to be tested). The relevant
tests (sas.Test) may then be generated from the test policy and the tested
entity. This avoids the need to manually configure many tests who only differ
on the object they test.
Threshold crossing events may be configured on NE schedulable tests (and test policies).
Threshold events are available for rising and falling jitter (inbound, outbound, roundtrip),
loss (inbound, outbound, roundtrip), and latency (inbound, outbound, roundtrip).
The threshold events are configured to generate/clear alarms when the thresholds
are crossed.
The TWAMP Server may be configured for the Network Element.
The following service assurance tests are supported:
- Service Site Ping (
service.SitePing)
- MAC Ping (
service.MacPing)
- MAC Trace (
service.MacTrace)
- MAC Populate (
service.MacPopulate)
- MAC Purge (
service.MacPurge)
- CPE Ping (
service.CpePing)
- VPRN Ping (
vprn.VprnPing)
- VPRN Trace (
vprn.VprnTrace)
- VCCV Ping (
svt.VccvPing)
- MTU Ping (
svt.MtuPing)
- Tunnel Ping (
svt.TunnelPing)
- LSP Ping (
mpls.LspPing)
- LSP Trace (
mpls.LspTrace)
- ATM Ping (
atm.AtmPing)
- DNS Ping (
icmp.DnsPing)
- ICMP Ping (
icmp.IcmpPing)
- ICMP Trace (
icmp.IcmpTrace)
- MFib Ping (
multicast.MfibPing)
- Multicast Router Info (
multicast.Mrinfo)
- Multicast Trace (
multicast.Mtrace)
See the appropriate RFS, IEEE, or IETF standards for more details on the operation of
each OAM diagnostic.