User guide

3-135
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 3 Using CTM GateWay/CORBA Interfaces
3.9.13 getSNC
Throws
globaldefs::ProcessingFailureException
EXCPT_INTERNAL_ERROR - Raised in case of nonspecific EMS internal failure.
EXCPT_INVALID_INPUT - Raised when subnetName does not reference a multiLayerSubnetwork
object.
EXCPT_UNABLE_TO_COMPLY – Raised when invoked on SNC on Ethernet equipment or STS-1 SNC on
DS1 equipment.
EXCPT_ENTITY_NOT_FOUND - Raised when sncName references an SNC object that does not exist.
EXCPT_NE_COMM_LOSS - Raised when communication to the managed element is lost.
Compliance
CTM-defined.
3.9.13 getSNC
Synopsis
void getSNC(
in globaldefs::NamingAttributes_T sncName,
out subnetworkConnection::SubnetworkConnection_T snc)
raises(globaldefs::ProcessingFailureException);
Description
This interface returns the SNC structure for the SNC whose name is supplied as a parameter.
• For the ONS 15310 CL, this method does not report STS-1 SNC on CTX using DS1 ports.
• For the ONS 15310 MA SONET, this method does not report STS-1 SNC on DS1 ports of DS1_xx
cards.
• For the ONS 15310 MA SDH, this method does not report VC4 SNC on E1 ports of E1_63_E3_3
cards.
• For the ONS 15327, this method does not report STS-1 SNC on XTC using DS1 ports.
• For the ONS 15454 SONET, this method does not report STS-1 SNC on DS1 equipment.
• For the ONS 15454 SDH, this method does not report VC-4 SNC on E1 or E1_42 equipment.
This interface does not report VCAT SNCs.
A processing failure exception is returned with an EXCPT_UNABLE_TO_COMPLY exception in all of
the preceding conditions.
Parameters
For details about the SubnetworkConnection_T structure, see 3.8.2 getAllSNCs, page 3-83.
Name Type Input/Output Description
sncName globaldefs::NamingAttributes_T In Name of the subnetwork connection.
snc subnetworkConnection::SubnetworkConnection_T Out SNC structure retrieved.