Filter
Top Products
2-30 Operation, administration, and maintenance (OAM) features
OPTera Metro 3500 Multiservice Platform NTRN10AN Rel 12.1 Standard Iss 1 Apr 2004
BLSR configuration distribution
The distribution process of a BLSR configuration from the NPx to the other
nodes in the BLSR is controlled by the combinations of results arising from the
following user-initiated actions:
• creating/deleting/editing a BLSR ring
• creating/deleting a BLSR configuration
• checking/loading/invoking/committing a BLSR configuration
• canceling a BLSR configuration (valid at any point before ‘commit’)
When a new BLSR configuration is provisioned, a ‘temporary’ BLSR
configuration is created. This BLSR configuration is activated when the
‘Invoke’ button is clicked in Site Manager. Any prior BLSR configuration is
deleted after the ‘Commit’ button is clicked in Site Manager.
BLSR configuration and connection audit
The BLSR configuration and connection audit feature is enabled by default.
Both audits are run by the system once every 1440 minutes (24 hours) by
default. This period is provisionable with a range of 15 minutes to 10080
minutes (7 days) in 15 minute increments.
The BLSR configuration and connection audit feature performs two tasks:
• The BLSR configuration audit function determines if the working BLSR
configuration on the NPx (master copy) is the same as the BLSR
configurations on the SPx circuit packs around the BLSR ring.
• The BLSR connection audit function determines if pass-through
connections in the BLSR have the proper End NE A and End NE Z
information provisioned.
BLSR configuration audit
If there is a discrepancy discovered in the configuration audit, the "BLSR
Configuration Audit Fail" alarm is raised on the SPx. At this time, the user is
able to force down the master copy of the BLSR configuration from the NPx
to the faulty SPx by going through the loading, invoking, and committing steps
on the NPx.