All MIBs › CISCO-APS-EXT-MIB › cApsConfigYcable
cApsConfigYcable
Module: CISCO-APS-EXT-MIB
OID (symbolic): CISCO-APS-EXT-MIB::cApsConfigYcable
OID (numeric): 1.3.6.1.4.1.9.10.72.1.2.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-create
Description: The Y-cable configuration for the APS group associated with user channels.
noYcable
The APS channels in the APS group are not connected to an external Y-cable.
ycable
Two user-side interfaces (not necessarily SONET or CDL) are connected to an external y-cable and are grouped into an APS group for endToEnd APS. The received user signal is split in the y-cable coupler and is received on both the interfaces. However, only one interface must transmit toward the user at any given time. With cApsConfigYcable set to 'ycable', the cApsConfigSpan must be set to 'endToEnd'. There must be only two APS channels in an APS group with cApsConfigYcable set to 'ycable'.
ycableXconnectCommon
This refers to a configuration where two user-side interfaces are connected to an external y-cable. The two signals received on these interface are connected to the same cross connect in the switch. The switch fabric selects one of the two received signals, duplicates it, and forwards it to two network side interfaces grouped for 1+1 linear APS. The received signal from the network side is transmitted to only one user-side interface. cApsConfigSpan is ignored if cApsConfigYcable is set to 'ycableXconnectCommon'. There must be only two APS channels in an APS group with cApsConfigYcable set to 'ycableXconnectCommon'.
This object may not be modified if the associated cApsConfigRowStatus object is equal to 'active'.
If this object is set to 'ycable' or 'ycableXconnectCommon', the user must shut one of the two channels before setting cApsConfigRowStatus to 'notInService'.
What is cApsConfigYcable?
This configures whether this APS group's user-side interfaces are connected via an external Y-cable splitter -- noYcable meaning no such external cable is used, ycable meaning two user-side interfaces are physically joined by a Y-cable coupler that splits the received signal so both interfaces see the same incoming traffic, and ycableXconnectCommon representing a cross-connected common variant. This matters operationally because when a Y-cable is in use, the protection scheme relies on that physical coupler to duplicate the incoming signal rather than any electronic replication inside the device, so this setting must accurately reflect the actual cabling in the rack or protection switching will not behave as configured. For example, if two user interfaces are physically wired together through an external Y-cable splitter for endToEnd APS protection, this must be set to ycable(2) for the device's APS logic to correctly understand how the split signal it's receiving relates to that protection group.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.10 | ciscoExperiment | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.10.72 | cApsExtMIB | CISCO-APS-EXT-MIB |
| 1.3.6.1.4.1.9.10.72.1 | cApsExtMIBObjects | CISCO-APS-EXT-MIB |
| 1.3.6.1.4.1.9.10.72.1.2 | cApsConfigExtTable | CISCO-APS-EXT-MIB |
| 1.3.6.1.4.1.9.10.72.1.2.1 | cApsConfigExtEntry | CISCO-APS-EXT-MIB |
| 1.3.6.1.4.1.9.10.72.1.2.1.2 | cApsConfigYcable | CISCO-APS-EXT-MIB |