11-6
Cisco ONS 15454 DWDM Reference Manual, R8.5
78-18343-02
Chapter 11 Optical Channel Circuits and Virtual Patchcords Reference
11.1.5 Creating and Deleting OCHCCs
11.1.5 Creating and Deleting OCHCCs
To create an OCHCC, you must know the client port states and their parameters. If the client port state
is IS/Unlocked, OCHCC creation will fail if the OTN line parameters (ITU-T G.709, FEC, signal fail bit
error rate (SF BER), and signal degrade bit error rate (SD BER) on the OCHCC differ from what is
provisioned on the trunk port. The port state must be changed to OOS-DSLB/Locked,disabled in order
to complete the OCHCC.
If you delete an OCHCC, you can specify the administrative state to apply to the client card ports. For
example, you can have the ports placed in OOS,DSBLD/Locked,disabled state after an OCHCC is
deleted. If you delete an OCHCC that originates and terminates on MXP cards, the MXP trunk port states
can only be changed if the trunk ports do not carry other OCHCCs.
11.1.6 OCHCCs and Service and Communications Channels
Although optical service channels (OSCs), generic communications channels (GCCs), and data
communications channels (DCCs) are not managed by OCHCCs, the following restrictions must be
considered when creating or deleting OCHCCs on ports with service or communication channels:
• Creating an OCHCC when the port has a service or a communications channel is present—OCHCC
creation will fail if the OCHCC parameters are incompatible with the GCC/DCC/GCC. For
example, you cannot disable ITU-T G.709 on the OCHCC if a GCC carried by the port requires the
parameter to be enabled.
• Creating a service or communications channel on ports with OCHCCs—OCHCC creation will fail
if the GCC/DCC/GCC parameters are incompatible with the OCHCC.
• Deleting an OCHCC on ports with service or communications channels—If an OSC/GCC/DCC is
present on a TXP, MXP, GE_XP, 20GE_XP, or ITU-T line card client or trunk port, you cannot set
these ports to the OOS,DSBLD/Locked,disabled state after the OCHCC circuit is deleted.
11.2 Virtual Patchcords
TXP, MXP, TXPP, MXPP, GE_XP, 10GE_XP, and ADM-10G client ports and DWDM filter ports can
be located in different nodes or in the same single-shelf or multishelf node. ITU-T line card trunk ports
and the corresponding DWDM filter ports are usually located in different nodes.
OCHCC provisioning requires a virtual patchcord between the client card trunk ports and the DWDM
filter ports. Depending on the physical layout, this can be an internal patchcord or a provisionable
(external) patchcord (PPC). Both patchcord types are bidirectional. However, each direction is managed
as a separate patchcord.
Internal patchcords provide virtual links between the two sides of a DWDM shelf, either in single-shelf
or multishelf mode. They are viewed and managed on the Provisioning > WDM-ANS >
Internal Patchcords tab (Figure 11-3).
To Next Page
Loading...
Need help?
General
