Preview Tool

Cisco Bug: CSCuq28909 - Removing conflict from txp/mxp controller can lose port-mode config

Last Modified

Jul 31, 2018

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases


Description (partial)


When configuring an nV Optical Controller, the configuration can be dropped/lost.

For example, the following configuration would be dropped/lost and not present in <CmdBold>show running-config<NoCmdBold>:
<CmdBold>controller optics 100/2/0/2
    port-mode ethernet<NoCmdBold>

nV Optical controllers have the following format:
<CmdBold>Optics<NoCmdBold>  <CmdArg>100-65535/....<NoCmdArg>
<CmdBold>otu4<NoCmdBold>  <CmdArg>100-65535/....<NoCmdArg>
<CmdBold>otu2<NoCmdBold>  <CmdArg>100-65535/....<NoCmdArg>
<CmdBold>odu4<NoCmdBold>  <CmdArg>100-65535/....<NoCmdArg>
<CmdBold>odu2<NoCmdBold>  <CmdArg>100-65535/....<NoCmdArg>


The problem occurs if there is both a <CmdBold>transponder<NoCmdBold> and a <CmdBold>muxponder<NoCmdBold> on the same satellite slot and the user removes one of the 
<CmdBold>transponder<NoCmdBold> or <CmdBold>muxponder<NoCmdBold> conflicting lines of config and configures nV Optical controllers in the same commit.

For example, both the transponder and muxponder specify the same satellite slot of <CmdArg>3/0/2<NoCmdArg>.

nv sat 100
   type ons15454-m6
   transponder 100g 3/0/2
   muxponder 10x10g 3/0/2 client-slot 2
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.