VCoP smart SFP provides support for the following features:

• Supports configuration on Gigabit Ethernet(GE) and TenGigabit Ethernet(10GE) ports of the chassis.

• OC-3 or OC-12 mode supports 15-km Duplex over GE and 10GE.

• T3 mode supports 450ft over GE and 10GE.

• VCoP smart SFP on OCn mode supports 1310nm laser optics and is multi source agreement (MSA) compliant.

• Supports SONET CEP (IETF RFC 4842).

• For peer end, supports use of any SFP or interface module that supports CEP protocol.

• Supports pseudowire configuration.

• Supports Online Insertion and Removal (OIR).

  Note	If after configuring a VCoP smart SFP, you remove and reinsert the VCoP smart SFP, the configuration persists. But, if you insert a non-VCoP SFP, the configuration is removed.

• Supports packetization, de-packetization, and clock recovery.

• Supports Explicit Pointer Adjustment Relay (EPAR).

• Supports alarms and performance monitoring.

• Supports loopback and BERT.

• Supports the following jitter buffer values:

  • OC-3 - 8ms

  • OC-12 - 4ms

  • T3 - 8ms

• Both OCx and PDH are supported on Cisco NCS 4201 and NCS 4202 Routers.

• The Multi-Protocol Label Switching (MPLS) and Interior Gateway Protocol (IGP) endpoints are up and running fine between the PE nodes.

• Ensure that SyncE is configured.

• Use the PTP Telecom profile, G.8265.1 for frequency synchronization, for CEM.

• VCoP smart SFP on OCn mode supports single-mode optical fiber cables.

• Port interface is set as default by using the default int Gig 0/0/8 command before inserting VCoP smart SFP on GE or 10GE port.

• The GE or 10GE port interface is brought up using the no shutdown command.

• In cases where a non-VCoP SFP is to be inserted on any port from which any VCoP smart SFP is removed, then before inserting non-VCoP SFP, the VCoP smart SFP configuration is removed using the below commands:

  • For OC-3

    no platform smart-sfp interface Gig x/y/z type oc3

  • For OC-12

    no platform smart-sfp interface Gig x/y/z type oc12

  • For T3

    no platform smart-sfp interface Gig x/y/z type ds3

  • For T1

    no platform smart-sfp interface Gig x/y/z type t1

  Note

  Replace GE with 10GE in the above commands to configure VCoP as 10GE port interface when inserted in a 10GE port. There is no need to remove platform smart-sfp interface Gig/TenGig x/y/z type oc3/oc12/ds3 command for OC-3 and OC-12 modes and platform smart-sfp interface Gig/TenGig x/y/z type T1 for T1 mode if you are replacing one VCoP smart SFP with the same or another VCoP smart SFP. Recovered clock configuration needs to be removed before applying the no platform command.

• To connect the CE nodes, VCoP smart SFP uses single mode fiber (SMF) over the LC optical interface for OCx mode and DIN 1.0/2.3 Coaxial connector cable for T3 mode.

  Note	Recommended interfacing connector for the T3 VCoP SFP is Compel 1.0/2.3 Coaxial connector P/N 350.064.621.

• The payload size is fixed to STS1 and is 783 bytes.

• VCoP smart SFP does not support Stateful Switchover (SSO).

• For QoS, VCoP smart SFP supports only the default MPLS experimental marking.

• At a time, OC-3/OC-12 supports BERT at any one path. T3 supports BERT only at one port.

• VCoP smart SFP does not support E3 mode.

• The chassis supports up to 12 VCoP smart SFPs.

• The T3 mode supports 1 CEP circuit and can sustain the traffic up to 45mbps.

• The Cisco NCS 4201 supports a maximum of 12 VCoP smart SFPs and only on GE ports of the top row.

• The Cisco NCS 4202 supports a maximum of eight VCoP smart SFPs and on all GE and 10GE ports.

• BERT on OCn VCoP is supported only at STS-1 path level. VCoP hardware does not support BERT at concatenated paths.

• BERT on DS3 VCoP is supported only in the Line direction.

• The VCoP CEM counters do not support L-bit and R-bit counters.

VCoP smart SFP supports the following alarms on OC-3 or OC-12 mode:

• Loss of Signal (LOS)

• Loss of Frame (LOF)

• Alarm Indication Signal (MS-AIS, AU-AIS)

• Remote Defect Indication Line (RDI-L)

• Loss of Pointer (AU-LOP)

• Path Unequipped Indication Signal (PUNEQ)

VCoP smart SFP supports the following alarms on T3 mode:

• Loss of Signal (LOS)

• Loss of Frame (LOF)

• Alarm Indication Signal (MS-AIS, AU-AIS)

• Remote Alarm Indication (RAI)

Note	Starting with Cisco IOS XE Amsterdam 17.3.1, Loss of Frame (LOF) is not supported on T3 mode.

Note	In case of RDI-L (remote alarm), SONET controller does not go down as this is not a critical alarm.

The VCoP smart SFP supports the performance monitoring counter to maintain the path quality of the link.

You can view the statistics or error count that is generated on the VCoP smart SFP, if you have the configuration that is described:

enable
configure terminal
controller SONET 0/0/8
threshold b1-tca 8
threshold  b2-tca 8
framing  sonet
overhead j0 6 
overhead s1s0 2 
!
sts-1  1
overhead  c2 2  
threshold b3-ber_sd 8 
threshold b3-ber_sf 8 
overhead  1 message PATH_TRACEj
threshold  b3-tca 8
mode unframed
cem-group0 cep 
!

The following parameters affect SONET configuration:

• Overhead - Sets the SONET overhead bytes in the frame header to a specific standards requirement, or to ensure interoperability with equipment from another vendors.

  • J0 - Sets the J0/C1 byte value in the SONET section overhead.

    Note	1 byte, 16 bytes, and 64 bytes are the supported values for J0.

  • J1 - Path Trace Byte

  • C2- Path Signal label

  • S1S0 - Sets the SS bits value of the H1 byte in the SONET line overhead

• Alarm Reporting - Enables reporting for all or selected alarms.

  • B1 - Section BIP Error (SF/SD)

  • B2 - Line BIP Error (SF/SD)

  • B3 (SF/SD) - STS Path BIP Error

  • sd-ber - Sets Signal Degrade BER threshold

  • sf-ber - Sets Signal failure BER threshold

The performance monitoring result is displayed using the show controller command. The following snippets are the performance monitoring details when the show controller command is executed.

Router# show controller sonet 0/0/8
SONET 0/0/8 is up.
  Hardware is 12xGE-4x10GE-FIXED

 Port configured rate: OC3
 Applique type is Channelized Sonet/SDH
 Clock Source is Line
Medium info:
  Type: Sonet, Line Coding: NRZ, 
 SECTION:
  LOS = 0          LOF = 0                           BIP(B1) = 0  

SONET/SDH Section Tables
  INTERVAL       CV    ES   SES  SEFS                    
  12:25-12:25     0     0     0     0

LINE:
  AIS = 0          RDI = 0          REI = 0          BIP(B2) = 0       
Active Defects: None
Detected Alarms: None
Asserted/Active Alarms: None
Alarm reporting enabled for: SLOS SLOF SF B1-TCA B2-TCA 
BER thresholds:  SF = 10e-3  SD = 10e-6   
TCA thresholds:  B1 = 10e-8  B2 = 10e-8   
Rx: S1S0 = 40
    K1 = 00,   K2 = 00
    J0 = 01                               
    RX S1 = 00

Tx: S1S0 = 02
    K1 = 00,   K2 = 00
    J0 = 06                          

SONET/SDH Line Tables
  INTERVAL       CV    ES   SES   UAS
  12:25-12:25     0     0     0     0


High Order Path:

PATH 1:
  AIS = 0          RDI = 0          REI = 0          BIP(B3) = 0           
  LOP = 0          PSE = 0          NSE = 0          NEWPTR = 0         
  LOM = 0          PLM = 0          UNEQ = 0         

Active Defects: None
Detected Alarms: PAIS 
Asserted/Active Alarms: PAIS 
Alarm reporting enabled for: PLOP LOM B3-TCA 

TCA threshold:  B3 = 10e-6    
Rx: C2 = 00
Tx: C2 = 02                 

PATH TRACE BUFFER : UNSTABLE 

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................       
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  
SONET/SDH Path Tables
  INTERVAL       CV    ES   SES   UAS
  12:25-12:25     0     0     0     0

PATH 2:
  AIS = 0          RDI = 0          REI = 0          BIP(B3) = 0         
  LOP = 0          PSE = 0          NSE = 0          NEWPTR = 0         
  LOM = 0          PLM = 0          UNEQ = 0         

Active Defects: None
Detected Alarms: None
Asserted/Active Alarms: None
Alarm reporting enabled for: PLOP LOM B3-TCA 

TCA threshold:  B3 = 10e-6
Rx: C2 = 00
Tx: C2 = 02

PATH TRACE BUFFER : UNSTABLE 

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  
SONET/SDH Path Tables
  INTERVAL       CV    ES   SES   UAS
  12:25-12:25     0     0     0     0

PATH 3:
  AIS = 0          RDI = 0          REI = 0          BIP(B3) = 0         
  LOP = 0          PSE = 0          NSE = 0          NEWPTR = 0         
  LOM = 0          PLM = 0          UNEQ = 0         

Active Defects: None
Detected Alarms: None
Asserted/Active Alarms: None
Alarm reporting enabled for: PLOP LOM B3-TCA 

TCA threshold:  B3 = 10e-6
Rx: C2 = 00
Tx: C2 = 02

PATH TRACE BUFFER : UNSTABLE 

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
  
SONET/SDH Path Tables
  INTERVAL       CV    ES   SES   UAS
  12:25-12:25     0     0     0     0


STS-1 1 mode UNFRAMED
  cep is configured: TRUE cem_id  :0

STS-1 2 mode UNFRAMED
  cep is configured: FALSE cem_id  :0

STS-1 3 mode UNFRAMED
  cep is configured: FALSE cem_id  :0

Bit Error Rate Testing (BERT) is supported on VCoP smart SFP at the STS-1 path level. The OCn VCoP hardware does not support BERT at the concatenated level paths like STS-3c or STS-12c. The interfaces contain onboard BERT circuitry to send and detect a pattern.

When running a BERT test, your system expects to receive the same pattern that it is transmitting. To help ensure that the two common options are available:

• Use a loopback somewhere in the link or network.

• Configure remote testing equipment to transmit the same BERT test pattern at the same time.

VCoP smart SFP supports Pseudo Random Binary Sequence (PRBS) pattern.

Both the total number of error bits received and the total number of error bits received are available for analysis. You can select the testing period to be from 1 minute to 24 hours, and you can also retrieve the error statistics anytime during the BERT test.

BERT is supported in two directions:

• Line - supports BERT in TDM direction.

• System - supports BERT in PSN direction.

Note	When the BERT is configured towards system direction, it internally loopbacks the TDM side locally.

Note	DS3 VCoP supports BERT only in the Line direction.

Note	Running BERT on DS3 VCoP triggers LOF alarm and it is cleared when BERT is over.

VCoP smart SFP supports two types of loopback configurations:

• Local loopback - In local loopback, the transmitting signal is looped back to the receiver signal.

• Network loopback - In network loopback, the receiving signal is looped back to the transmitting signal.