v
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
New in this release
0
The following sections detail what’s new in
Fault Management - Customer
Visible Logs
, 323-1851-840 Standard Issue 1 for Release 6.0.
New features
No new logs have been added in this issue.
vi New in this release
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
1-1
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
Introduction to customer visible logs
1-
This section provides an introduction to the use of customer visible logs in
troubleshooting failures related to the Domain Optical Controller.
323-1851-840
1-2 Introduction to customer visible logs
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
Domain Optical Controller Customer Visible Logs
The Domain Optical Controller (DOC) provides a number of customer visible
alarms to signal fault conditions. These alarms include:
• DOC Action Failed: Add
• DOC Action Failed: Delete
• DOC Action Failed: Monitor
• DOC Action Failed: Optimize
• DOC Action: Fault Detected
• DOC Domain Not Optimized
• Channel Controller: Unexpected Loss Detected
• Invalid Photonic Domain
Faults that result in one of these alarms prevent DOC from continuing a
re-optimization as this could result in worse performance conditions for
surviving traffic.
DOC maintains logs detailing any failure of previously executed commands
that can result in the above listed alarms. The DOC Customer Visible Logs
are retrievable from the Site Manager DOC application and the “Logs” button.
The DOC logs are used to determine the fault responsible for the DOC alarm
on the network element. The procedures contained in this guide outline the
steps required to clear the faults based on the content of the logs. Once the
fault is cleared DOC can re-attempt the channel action.
DOC Log Description
The DOC logs are displayed by opening the Configuration -> Photonic
Services -> Domain Optical Controller (DOC) tab in Site Manager for a
network element containing a DOC site. Once a DOC instance is selected the
user can Click the "Logs" button to view the CVLs.
In the case of any DOC Failure the DOC Logs should be retrieved and saved
for investigation before any troubleshooting steps are taken. DOC logs are
updated when a DOC action failure occurs. The logs remain until either the
next failure or when the "Clear DOC Logs" button is selected in Site Manager.
DOC Logs report details for 5 sections:
• Domain Optical Control Topology Log
• Domain Optical Control Command Log
• Section Optical Control Command Log
• Network Topology Log
Introduction to customer visible logs 1-3
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
• Section Topology Log.
The topology logs outline the system and channel topologies for the DOC,
Network and Section. The Command logs outline the steps taken, and the
faults detected, that resulted in the alarm being raised.
For details on Domain and Sections see the Photonic services - Photonic
advanced optical control section of the OME 6500 Planning Guide (Part 2 of
3).
DOC Log Format
An example of the DOC Log window is shown below. The format of the DOC
logs are also described in this section.
***************************************************************************************
***************************************************************************************
1-4 Introduction to customer visible logs
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
<TID-SHELF> DOC Log generated at <hh:mm:ss> on <MM-DD-YYYY>.
Logs for <TID-SHELF>
***************************************************************************************
* Domain Optical Control Topology Log.
*
***************************************************************************************
DOC topology at <YYYY-MM-DD> <hh:mm:ss>
DOC Site <TID>-<SHELF>
Configuration: <Configuration>
List of SOC Sites
TID-Shelf
========
<TID>-<SHELF>-<PATH ID> (repeated for all SOC Sites)
Network Channel AID Optimization State SHELF (Add & Drop)
NC-<SHELF>-<SITEID>-<Remote Shelf>-<Remote Path>-<Wavelength>
<Optimization State of Channel> <TID of Add Shelf>-<SHELF>-<PATH ID>
<TID of Drop Shelf>-<SHELF>-<PATH ID> (repeated for all defined
channels)
***************************************************************************************
* Domain Optical Control Command Log.
*
***************************************************************************************
<YYYY-MM-DD> <hh:mm:ss> DOC command log (repeated for all logs)
***************************************************************************************
Introduction to customer visible logs 1-5
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
* Section Optical Control Command Log.
*
***************************************************************************************
<YYYY-MM-DD> <hh:mm:ss> SOC command log (repeated for all logs)
***************************************************************************************
***************************************************************************************
<TID>-<SHELF> Topology Log generated at <hh:mm:ss> on MM-DD-YYYY.
Logs for <TID>-<SHELF>
***************************************************************************************
* Network Topology Log.
*
***************************************************************************************
<YYYY-MM-DD> <hh:mm:ss> Network Topology log (repeated for all logs)
***************************************************************************************
* Section Topology Log.
*
***************************************************************************************
<YYYY-MM-DD> <hh:mm:ss> Section Topology log (repeated for all logs)
DOC Log Troubleshooting Documents
The procedures contained in this guide contain details on how to troubleshoot
failures based on the contents of the DOC Logs. The procedures are
presented in the following format:
Log text - The text presented to the user in the DOC Log
Description/Probable cause - Outlines the cause of the fault
Troubleshooting information - Details on resolving the fault
1-6 Introduction to customer visible logs
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
Commonly Used Terminology
The procedures contained in this guide use the following terms when
describing directions in the photonic network:
Upstream: Components that exists prior to the current point in the optical
traffic path
Downstream: Components that exists after the current point in the optical
traffic path.
Example
TX CMD44(1) WSS(1) MLA(1) MLA(2) WSS(2) CMD44(2) RX
The TX is upstream of CMD44(1).
CMD44(2) is downstream of WSS(2).
2-1
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
Domain Optical Controller (DOC) logs
2-
This section provides detailed information on DOC logs. That information is to
be used for troubleshooting purposes.
323-1851-840
2-2 Domain Optical Controller (DOC) logs
Optical Multiservice Edge 6500
Fault Management - Customer Visible Logs
323-1851-840 Iss 1 Standard
Release 6.0 Sep 2009
Copyright 2004-2009, Nortel Networks
Unique log Identifier: 65537
Log text
Topology Routing Failure - Routing message failed to sent to:
<TID>-<SHELF>, rem_path <PATH>.
Software area
To p o lo g y
Associated alarms
DOC Invalid Photonic Domain
Description/Probable cause
A failure occurred while trying to send Routing message to the next node with
<TID>-<SHELF> and rem_path <PATH>. The probable cause is a
communication error between network elements in the section.
A retry mechanism will ensure that routing message is eventually sent once
the error condition is resolved.
Troubleshooting information
• Determine if all nodes in the network can be accessed. If access is not
available, a condition might exists on the network which is preventing
normal communication between network elements. This should be
addressed using network troubleshooting techniques.
• Clear any alarms raised in the network using the published trouble
clearing procedures.
• Verify the software release which is running on all NEs in the network. If
any NE is running an older release, proceed with the appropriate upgrade
procedure to upgrade all NEs to the same software release.
• Verify the OSC equipment and facilities are present and in-service for all
nodes in the network.
• Ensure that no more than 2 DOC sites are present in each domain.
• Verify that all nodes in the network are displayed as expected in the
Visualization tool (Network View). If the Visualization tool is not available
issue the command RTRV-TOPO-OST and verify that all nodes in the
network are listed as expected.
• Contact Nortel Global Product Support for further assistance.
—end—
Additional information
CVL 65546 might be seen before this one is generated. CVL 65820 will be
seen after this one.
Không có nhận xét nào:
Đăng nhận xét