From 824a6db3ff111f8d2427ac5adad0362bf078630a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= Date: Thu, 2 Sep 2010 15:44:33 +0200 Subject: Add test suite for xmerl --- lib/xmerl/test/xmerl_SUITE_data/cpd.tar.gz | Bin 0 -> 2128 bytes lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml | 30261 +++++++++++++++++++ .../test/xmerl_SUITE_data/eventp/CelloMOM.stub | 14 + .../test/xmerl_SUITE_data/eventp/CelloMOM.xml | 30261 +++++++++++++++++++ lib/xmerl/test/xmerl_SUITE_data/eventp/mp.dtd | 274 + lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.stub | 5 + lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.xml | 9 + lib/xmerl/test/xmerl_SUITE_data/misc.tar.gz | Bin 0 -> 47121 bytes .../test/xmerl_SUITE_data/xpath/documentRoot.xml | 43 + lib/xmerl/test/xmerl_SUITE_data/xpath/e1074.xml | 18 + lib/xmerl/test/xmerl_SUITE_data/xpath/e1075.xml | 18 + lib/xmerl/test/xmerl_SUITE_data/xpath/e1076.xml | 13 + lib/xmerl/test/xmerl_SUITE_data/xpath/e1077.xml | 16 + lib/xmerl/test/xmerl_SUITE_data/xpath/e1078.xml | 11 + .../test/xmerl_SUITE_data/xpath/motorcycles.xml | 25 + .../test/xmerl_SUITE_data/xpath/myBS_model.xml | 6 + .../test/xmerl_SUITE_data/xpath/purchaseOrder.xml | 36 + lib/xmerl/test/xmerl_SUITE_data/xpath/xpath.xml | 25 + .../test/xmerl_SUITE_data/xpath/xpath_abbrev.erl | 266 + .../test/xmerl_SUITE_data/xpath/xpath_lib.erl | 184 + .../test/xmerl_SUITE_data/xpath/xpath_text.erl | 28 + 21 files changed, 61513 insertions(+) create mode 100644 lib/xmerl/test/xmerl_SUITE_data/cpd.tar.gz create mode 100644 lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.stub create mode 100644 lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/eventp/mp.dtd create mode 100644 lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.stub create mode 100644 lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/misc.tar.gz create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/documentRoot.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/e1074.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/e1075.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/e1076.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/e1077.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/e1078.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/motorcycles.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/myBS_model.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/purchaseOrder.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/xpath.xml create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_abbrev.erl create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_lib.erl create mode 100644 lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_text.erl (limited to 'lib/xmerl/test/xmerl_SUITE_data') diff --git a/lib/xmerl/test/xmerl_SUITE_data/cpd.tar.gz b/lib/xmerl/test/xmerl_SUITE_data/cpd.tar.gz new file mode 100644 index 0000000000..c750e14adf Binary files /dev/null and b/lib/xmerl/test/xmerl_SUITE_data/cpd.tar.gz differ diff --git a/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml b/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml new file mode 100644 index 0000000000..7c64046897 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml @@ -0,0 +1,30261 @@ + + + + + + + + + + Exception thrown when an attribute is missing during upgrade. + + + + Exception thrown when enabling of existing programs fails. + + + + + + + Exception thrown when copying of files fails. + + + + Exception thrown when the specified file does not exist. + + + + + + + Exception thrown when the heap or pool setting is incorrect. + + + + Exception thrown when an attribute value is out of range. + + + + Exception thrown when a cancel install equest for some reason fails. + + + + Exception thrown when the control of checksum for loadmodules has been rejaected due to 'null' recieved from resource layer. + + + + Exception thrown when its not possible to clear all PiuTypes referenced by PlugInUnit. + + + + Exception thrown when an conditional mandatory attribute (or element) is missing. + + + + Exception thrown when the creation of a CV during upgrade fails. + + + + + + + Exception thrown when the creation of a load module fails. + + + + Exception thrown when disabling of existing programs for some reason fails. + + + + + + + Exception thrown when replacement of existing RPU information fails. + + + + Exception thrown when the installation of Load Modules is cancelled. + + + + Exception thrown when the installment of Load Modules is only partly executed. + + + + Exception thrown when the install of Load Modules is rejected. + + + + Exception thrown when the install is rejected due to FTP server is not accessible. + + + + Exception thrown when the install is rejected due to error when trying to retreive Load Module. + + + + Exception thrown when install is rejected due to erronous IP address. + + + + Exception thrown when the install is rejected due to insufficient disk space. + + + + + + + Exception thrown when the installation of a Load Module fails. + + + + Exception thrown when the disk space is insufficient. + + + + + + + Exception thrown when file path for the Load Module is out of length. + + + + + + + + + + + + + Exception thrown when the merger of control files fails. + + + + + + + + + + + + + Exception thrown when PiuType definitions is missing in the UCF file. + + + + + + + Exception thrown when the product number and revision is already used. + + + + + + + Exception thrown when reconfiguration of programs fails. + + + + Exception thrown when the referenced element is missing. + + + + + + + + + + Exception thrown when reserving a Load Module fails. + + + + Exception thrown when a selective install fails. + + + + + + + + + + Exception thrown when an unexpected attribute occurs at upgrade. + + + + Exception thrown when an unexpected format of the attribute occurs. + + + + Exception thrown when + + + + + + + + + + + + + Exception thrown when its not possible to delete the upgrade package. + + + + Exception thrown when its not allowed to delete the upgrade package. + + + + Exception thrown when the specified upgrade package does not exist. + + + + Exception thrown when an error in the file system occurs. + + + + Exception thrown when the upgrade is rejected. + + + + + + + Exception thrown when the checksum is incorrect. + + + + Exception thrown when its not possible to verify the creation of CV's. + + + + + + + + + + + + + + + + + + + + + + The upgrade trace log file is not accessible i.e. the log file exists but it is not possible to access it with write permission. + + + + The file parser has found that the UpgradeControlFile is incorrect. + + + + + + + + + Before an upgrade is started it was found that the upgrade can not take place. A possible reason is that the upgrade package that is running in the node is not in the upgrade window of this upgrade package. + + + + + + + + + The upgrade trace output is currently not directed to a file. + +This is a property that can be changed in the trace property file (Trace_01.prop). + + + + + + The upgrade package is not installed. + 0 + + + The upgrade package is completely installed. + 1 + + + Upgrade is executing. + 2 + + + The execution of upgrade needs confirmation before it proceeds. + 3 + + + In this state an Upgrade Package can only be deleted. Its actions, when invoked, will throw the exception ActionNotAllowed. + 4 + + + Installation of the upgrade package is executing. + 5 + + + The upgrade package is not completely installed i.e. parts of it has been installed. + 6 + + + The upgrade has been successfully executed. + 7 + + + + + + No action is in progress. + 0 + + + Downloading of files (load modules) in progress. + 1 + + + Saving a Configuration Version. + 2 + + + Operation ReplaceConfigSupportMOs detected in upgrade. + 3 + + + Trigger Initiate detected in upgrade sequence. + 4 + + + Trigger Preload detected in upgrade sequence. + 5 + + + 6 + + + 'Unique trigger' for an application detected in upgrade sequence. + 7 + + + 8 + + + 9 + + + The error handling is switched back to normal. + 10 + + + 11 + + + Indicates that the execution of an install or an upgrade action has failed. + 12 + + + Indicates that cancellation of an ongoing installation is in progress. + 13 + + + Indicates that the execution of a cancel install action failed. + 14 + + + 15 + + + 16 + + + 17 + + + 18 + + + 19 + + + 20 + + + 21 + + + 22 + + + + + + The verifyUpgrade action has been invoked. + 1 + + + An upgrade action (one of the variants) has been invoked. + 2 + + + An install action (one of the variants) has been invoked. + 3 + + + The cancelInstall action has been invoked. + 4 + + + + + + A timestamp. + +Format: "Date: 2003-04-24, Time: 20:52:11.182" + + "" + + + + + VERIFY_UPGRADE + + + + + EXECUTED + + + + This id is used to link more than one result to one action + + 1 + + + + + "" + + + + + + + The invoked action has been successfully executed without warnings.One of three possible main results of executed action. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 0 + + + A not specified error/ warning has been detected (see additional info for further details) + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 1 + + + A load module checksum verification has failed. + +Value valid for type of invoked action: +INSTALL +VERIFY_UPGRADE +UPGRADE + 2 + + + There is not enough available disk space for the required number of new CVs (configuration versions) to be created automatically during an upgrade. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 3 + + + The maximum number of allowed CVs (configuration versions) will be exceeded if the required number of new CVs is created automatically during an upgrade. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 4 + + + The Upgrade Window element in the Upgrade Control File does not specify the current Upgrade Package as a valid 'upgrade from' version. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 5 + + + A non supported Plug In Unit (PIU) has been detected i.e. the PIU in the node is not defined in the Upgrade Control File. +This is not a fault that prevents an upgrade from being executed. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 6 + + + A faulty Plug In Unit (PIU) has been detected. +This is not a fault that prevents an upgrade from being executed. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 7 + + + The auto-creation of an install CV failed. + +Value valid for type of invoked action: +INSTALL + + 8 + + + The requested action is not allowed due to an other action already is in progress for an other UP MO. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 9 + + + An ongoing installation has been cancelled (aborted) due to request from client. + +Value valid for type of invoked action: +INSTALL + 10 + + + The FTP server to be used for downloads of load modules is not accessible. + +Value valid for type of invoked action: +INSTALL + 11 + + + The required disk space for load modules to be installed is insufficient. + +Value valid for type of invoked action: +INSTALL + 12 + + + Error detected in the IP address of the FTP server. + +Value valid for type of invoked action: +INSTALL + 13 + + + The install of the delta Upgrade Control File (UCF) failed i.e. the analysis of the delta UCF together with current active UP's UCF failed. + +Value valid for type of invoked action: +INSTALL + 14 + + + Error detected during the selection phase of an install. + +Value valid for type of invoked action: +INSTALL + + + 15 + + + The execution of invoked action failed.One of three possible main results of executed action. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 16 + + + The action has been successfully executed but with warnings.One of three possible main results of executed action. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE + 17 + + + + + Ftp server is not accessible. This may depend on erroneous IP address, username, password, or that the IP communication with the Ftp server is down, or that the Ftp server itself is malfunctioning. + + + + + + + + + An error was encountered during FTP get file. A filePath in the upgradeControlFile may be inconsistent with a filepath on the Ftp server. + + + + + + + + + + The tag is used as a reference between the PiuType MO and the Repertoire MO to find out how to create the program object under a PlugInUnit MO. + + + + Local distinguished name of the program parent from the PlugInUnit. + +Example: +1. "Spu=1,Spm=2" (the program is to be created under: ...PlugInUnit=2,Spu=1,Spm=2") +2. "" (empty string - the program is to be created directly under the PlugInUnit) + + + + The name of the Program MO that will be created. + + + + The loadableProcessorName is a user friendly name of the processor. + + + + + + This structure contains load module data that belongs to a piu type. + + + The distinguished name of the load module, which is needed and sufficient to convert the load module to a real object reference. + + + + The tag is used as a reference between the PiuType MO and the Repertoire MO to find out how to create the program object under a PlugInUnit MO. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0 + + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + + + + 0 + + + 1 + + + 2 + + + 3 + + + 99 + + + 4 + + + 5 + + + + + + 0 + + + 1 + + + 2 + + + + + This attribute can have the following values: + +AtPiuFault = Indicates the MP (where the normal RPU is configured) is faulty (HW error). This is the default value. + +AtPiuRestart = Indicates the MP (where the normal RPU is configured) is restarted. + + 1 + + + 2 + + + + + This enumeration can have the following values: + +Manual = Indicates that no normalisation is performed by cello until the operator issues a "switch" action. + +Automatic = Indicates that Cello performs the normalisation automatically, after the failed RPU is available again. This is the default value. + + 1 + + + 2 + + + + + This enumaration contains the following values: + +Always = Data replication is always performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + +Never = Data replication is never performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + +AtShutdown = Each time the RSH (which handles the RPU) is shut down, a complete snapshot is taken and replicated to the other MP, if necessary. Otherwise, the replication is performed according to the characteristics set on each container ( that is associated with the RPU ). + +ApplControlled = The data replication is made according to the characteristics set on each container ( that is associated with the RPU ). This is the default value. + + Always = Data replication is always performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + 1 + + + Data replication is never performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + 2 + + + AtShutdown = Each time the RSH (which handles the RPU) is shut down, a complete snapshot is taken and replicated to the other MP, if necessary. Otherwise, the replication is performed according to the characteristics set on each container ( that is associated with the RPU ). + 3 + + + ApplControlled = The data replication is made according to the characteristics set on each container ( that is associated with the RPU ). This is the default value. + 4 + + + + + This enumeration contains the following values: + +AsConfigured = The RSHs runs as the RPU is configured. +SwitchOver = The RSHs has been switched over. +Unavailable = No RSHs, that uses this RPU, are running. + + 1 + + + 2 + + + 3 + + + + + + + + + + + + + + + + + Control value for the fan unit. Needed by cooling function. + + + Control value for the fan unit running in normal autonomous mode. +This parameter is the subrack/fanunit airflow value that is required to achieve sufficient cooling at 20 degree +centigrade or lower ambient temperature of the most demanding plug in unit (PIU) in the subrack. This airflow value +shall be sufficient (but not unnecessarily large) to secure that no "normal overtemp" fault indication is issued. +Default values = 250 m3/h. (value >=0) + + + 250 + + + + Control value for the fan unit running in normal autonomous mode. This parameter is the subrack/fanunit airflow +value that is required to achieve sufficient cooling at 50 degree centigrade ambient temperature of the most +demanding plug in unit (PIU) in the subrack. This airflow value shall be sufficient (but not unnecessarily large) to +secure that no "normal overtemp" fault indication is issued. +Default values = 400 m3/h. (value >=0) + + 400 + + + + Control value for the fan unit running in noise reduction mode. This parameter is the subrack/fanunit airflow value +that is required to achieve sufficient cooling at 20 degree centigrade or lower ambient temperature of the most +demanding plug in unit (PIU) in the subrack. This airflow value shall be sufficient (but not unnecessarily large) to +secure that no "exceptional overtemp" fault indication is issued +Default values = 250 m3/h. (value >=0) + + 250 + + + + Control value for the fan unit running in noise reduction mode. This parameter is the subrack/fanunit airflow value +that is required to achieve sufficient cooling at 50 degree centigrade ambient temperature of the most demanding +plug in unit (PIU) in the subrack. This airflow value shall be sufficient (but not unnecessarily large) to secure +that no "exceptional overtemp" fault indication is issued. +Default values = 400 m3/h. (value >=0) + + 400 + + + + + + Erroneous Ip Address Format + + + + + + + + + An application upgrade engine has reported a failure. + + + + + + + + + The action is not allowed, the UpgradePackage MO is in wrong state. + +For example if you try 'upgrade()' before an 'install()' or 'forcedInstall()' has been done. + + + + + + + + + Exception thrown upon file system Error. + + + + + + + + + Data Base Error Exception (error when creating database backup). + + + + + + + + + LLP Error Exception (error when creating ARMAMENT and LLP.LMID files). + + + + + + + + + The configuration version already exists (e.g. message at create). + + + + + + + + + The configuration version does not exist (e.g. message at setCVAsStartable). + + + + + + + + + It is not allowed to delete the configuration version, because it is in use (used as startable or in rollback list). + + + + + + + + + The configuration version is not valid (due to missing files). + + + + + + + + + + + Format Error in given configuration version name. + +The following characters are allowed within the name: +[0-9], [A-Z], [a-z] and '&','%',':','.','_', '-' + +Note! For comment and operatorName spaces (' ') are also allowed within the strings. + + + + + + + + + Error Exception. + + + + + + + + + Indicates that an error in an installation has occurred. + + The message of the exception. + + + + + + + + Exception thrown when a database error occurs. + + + + Exception thrown when an invalid drive name is specified or when a data base error occurs. + + + + + + + Exception thrown when the log file path is wrong. + + + + Exception thrown when max number of CV's in the system has been reached. + + + + + + + "" + + + + + + + + + + "" + + + + + + + + + + + + + Indicates an invalid priority level, i.e. the priority in question is out of the defined range. + + + + + + + + + This struct contains the values applicable for QoS Class A. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + + 0 1000000000 + + 500000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + 0 1000000000 + + 500000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + + 0 10000 + + 5000 + + + + + + This struct contains the values applicable for QoS Class B. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + 0 1000000000 + + 500000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + + 0 1000000000 + + 500000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + + 0 20000 + + 15000 + + + + + + This struct contains the values applicable for QoS Class C. + +NOTE: The attribute 'boundONodeDelay' is not applicable for QoS Class C so setting of this attribute will have no effect. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + 0 1000000000 + + 1000000000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + + 0 1000000000 + + 1000000000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + 25000 + + + + + + This struct contains the values applicable for QoS Class D. + +NOTE: The attribute 'boundONodeDelay' is not applicable for QoS Class D so setting of this attribute will have no effect. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + 1 1000000000 + + 1000000000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + 0 1000000000 + + 1000000000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + 50000 + + + + + + + 0 + + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + 6 + + + 7 + + + 8 + + + 9 + + + 10 + + + 11 + + + 12 + + + 13 + + + 14 + + + 15 + + + + + Exception thrown when an attempt is made to set or change the aal2PathId of an Aal2PathVccTp while its reserved by an other Aal2PathGrp + + + + Exception thrown when an attempt is made to set or change the aal2PathOwner of an Aal2PathVccTp while its not LOCKED. + + + + + + + It is free to be pre-configured with a new PlugInUnit. + 0 + + + A PlugInUnit is inserted in the slot or the slot is pre-configured with a PlugInUnit. + 1 + + + Currently not supported. + 2 + + + + + + The product number of the product or document. + +Examples: ABC 101 001, CXC 123 456, 1/BFD 101 999 + +In the case of UpgradePackage this is the document number of the upgrade package. + + + 1 24 + + + + + The revision of the product number. + +Examples: R1, r1a, R1A02, P7B + + + 1 7 + + + + + A user-friendly name of the product. + + + 1 12 + + "" + + + + User-friendly information about the product. + + "" + + + + The production date can be represented in two ways. + +1) The preferable syntax is a four-digit representation of the year, and a two-digit representation of the month and a two-digit representation of the day. The numbers of characters in this case, is eight. +Example: +19991231 + +2) The date can also consist of two digits for the year, followed by the letter W for week and two digits for the number of week. The numbers of characters in this case, is five. +Example: +99W12 + + + + 1 8 + + "" + + + + + + + A user-friendly name of the product. + + + + + + + 1 12 + + + + + Unique identity for each product, which is constituted by the Ericsson product number (ABC number). + +The maximum number of characters for a product number is 24 including 2 slashes, 2 spaces and 2 characters for origination notation. + +Example of product number: +ABC 101 001 +(1/ABC 101 01/1234) +123/ABCDE 101 1010/12345 + +. + + + 1 24 + + + + + Indicates the revision state of the product. It consists of a letter R or P, one or two digits and/or one or two letters. The maximum number of characters is four inclusive R or P. +Example: R1A, R1A02, P7B + +A suffix may be added to the revision state. The suffix may consists of one or two digits or one letter. + + + + + + 1 7 + + + + + The serial number consists of 13 alphanumerical characters grouped as 6 plus 7 characters. The first 6 characters are to be used for factory codes and the last 7 characters are used for an individual number or batch number. + + + + + + The production date can be represented in two ways. + +1) The preferable syntax is a four-digit representation of the year, and a two-digit representation of the month and a two-digit representation of the day. The numbers of characters in this case, is eight. +Example: +19991231 + +2) The date can also consist of two digits for the year, followed by the letter W for week and two digits for the number of week. The numbers of characters in this case, is five. +Example: +99W12 + + + + + 5 8 + + + + + + + Defines the phase in the load and start sequence. + + + 10 + + + 50 + + + 100 + + + 200 + + + 300 + + + 400 + + + 500 + + + 600 + + + + + + 0 + + + 1 + + + + + + 0 + + + 1 + + + + + + The board is a Main processor. + 1 + + + The board is a device board. + 2 + + + The board is not a Main processor or a device board. + 3 + + + + + This attribute indicates the restart cause of plugInUnit. The defined values are: +1. piuRestartError: restart because of error. +2. piuRestartUpgrade: restart because of system upgrade. + + + This attributes indicates that the Piu restart cause is upgrade. + 2 + + + This attributes indicates that the Piu restart cause is error. + 1 + + + + + The Fan can be in one of three controlling state: +- standalone: not manageable, full speed fans +- autonomous: manageable, air-flow control +- noiseReduced: time-limited low speed fan + + It's running on itself, not manageable. + 1 + + + Manageable state. + 2 + + + Temporary state with reduced cooling. + 3 + + + + + + This attributes indicates unlimited restarts and no faulty marking of the PIU. Used for critical PIU's such as TUBs, SCBs and some ET-boards. + + -1 + + + This attributes indicates the following sequential restarts: +-warm +-refresh +-cold +-cold with fault marked (not loaded). Alarm sent. + 3 + + + This attributes indicates the following sequential restarts: +-refresh +-cold +-cold with fault marked (not loaded). Alarm sent. + 2 + + + This attributes indicates the following sequential restarts: +-cold +-cold with fault marked (not loaded). Alarm sent. + 1 + + + This attributes indicates the following sequential restarts: +-cold with fault marked (not loaded). Alarm sent. + 0 + + + + + This class is an exception class thrown when a equipment specific error occurs. + + + + + This class is an exception class thrown when a equipment specific error occurs. + + + + + This class is an exception class thrown when failed to configure the webserver root path + + + + + + + + + + + + + + + + + + 0 + + + 1 + + + + + + 0 + + + 1 + + + 2 + + + + + + + + + + + + + + Indication of Switch Internal Link port status. + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + + + Index specified is invalid, i.e. it is out of the range of valid indices. + + The exception message. + + + + + + + + + + + Exception thrown when MO is not possible to delete. + + + + Exception that is thrown when a FRO (Facade Resource Object in the resource layer) cannot be accessed. + + + + Exception that is thrown when the result of a request to a FRO (Facade Resource Object in the resource layer) is not ok. + + + + Exception thrown when the MO is already reserved by another user (MO). + + + + Exception class thrown when an MO is requested to be deleted, but the MO has children, which must be deleted first. + + + + Exception thrown when trying to delete an MO that is reserved by another MO (user). + + + + Exception thrown when the maximum number of childrens for an MO is exceeded. + + + + Exception thrown when a value of an attribute is not unique. + + + + + + + + + + + + + Exception class thrown when an MO is accessed outside a transaction but the access method requires a transaction. + + + + Exception thrown when an MO attribute is requested to be set, but the requested value is not accepted. + + + + Exception thrown when an MO attribute is requested to be set, but the requested value is of the wrong type. + + + + Exception class thrown when an attribute of not handled type is requested. + + + + Exception class thrown when a Struct is accessed but the reqested Struct element is not found. + + + + + + + Exception thrown when an MO attribute is requested to be accessed but the access +method for the is not defined (the attribute can not be accessed) + + + + Exception class thrown when the creation of an MO fails due to child - parent +cardinality violation. The cardinality is specified in the MIM. + + + + Exception thrown when the parent of the MO is of the wrong type. + + + + Exception thrown when a create is ordered with +attribute values that are not settable at create. + + + + Exception thrown when an attribute that is mandatory at create is missing. + + + + Exception thrown when an MO is created and the distinguished name of the MO is already in use. + + + + Exception thrown if the argument supplied is of the wrong type, for example in an action. + + + + Exception thrown if the value of the attribute is not valid. + + + + + 0 + + + 1 + + + 2 + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + 1 + + + 2 + + + 4 + + + 8 + + + 16 + + + 64 + + + 128 + + + 256 + + + 544 + + + 1056 + + + 2080 + + + 0 + + + + + Exception thrown when the submitted MO reference is invalid. + + + + Exception thrown when a fRo cannot be accessed. + + + + Exception thrown by an MO when there is a general error. + + + + Exception thrown when an identity (LDN) specified at create is not allowed. + + + + Exception thrown when a reference to an MO is of a unexpected/wrong MO type. + + + + Exception thrown when gathering of ATM info fails. + + + + Exception thrown when its not possible to delete an MO. + + + + Exception thrown when by an MO if its not possible to reserve the MO. + + + + Exception thrown when a user tries to release an MO that is not reserved by this user. + + + + Exception thrown when there is no hard disk. + + + + Exception thrown when an element cannot be removed from a sequence. + + + + Exception thrown when restart of the PlugInUnit is not allowed. + + + + The Sync Mode Operation of the node. + + 0 + + + 1 + + + 2 + + + + + + SUERM parameter T. +Measured in SU units. + + + 1 511 + + 64 + + + + SUREM parameter D. +Measurement units are in SUs. + + + 1 256 + + 256 + + + + SUERM parameter N. +Measurement units are in SUs. + + + 1 256 + + 16 + + + + Normal AERM threshold, Tin. Number of signal errors that cause abortion of a normal proving peroid. + +Measurement units are SUs. + + + 1 7 + + 4 + + + + Emergency AERM threshold, Tie. Number of signal units errors that cause abortion of an emergency proving period. + +Measurement units are SUs. + + + 1 7 + + 1 + + + + Proving abort limit. Number of consecutive aborted proving periods that will cause a return to the Out Of Service state. + +Measurement units are the number of proving periods. + + + 1 7 + + 5 + + + + Maximum time to stay in Aligned Ready state before signalling link failure. + +Measurement units are milliseconds. + + + 10 16300 + + 12900 + + + + Maximum time to stay in Not Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 32700 + + 5000 + + + + Maximum time to stay in Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 16300 + + 11500 + + + + Length of the normal proving period. + +Measurement units are milliseconds. + + + 10 4000 + + 2300 + + + + Length of the emergengcy proving period. + +Measurement units are milliseconds. + + + 10 4000 + + 600 + + + + Time between sending Status Indication "B" while in the Congested state. + +Measurement units are milliseconds. + + + 1 255 + + 80 + + + + Maximum time a remote site may remain in the congestated state before signalling link failure. + +Measurement units are milliseconds. + + + 10 8100 + + 1000 + + + + Maximum time to wait for an expected acknowledgement of an MSU before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 500 + + + + The speed of the link. Only supported values are 64 and 56 kbit/s. +0 = 64 kbit/s. +1 = 56 kbit/s. + + + + + 0 1 + + 0 + + + + The error correction algorithm to use. Only Basic Error Correction (BEC) is supported. +0 = BEC + + + + 0 1 + + 0 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 1 messages towards client. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 2 messages towards client. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 3 messages towards client. + + + 1 100 + + 90 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 1 messages. + + + 1 100 + + 60 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 2 messages. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 3 messages. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 1 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 2 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 3 is discarded by MTP2. + + + 1 100 + + 100 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 60 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 70 + + + + + + + SUERM parameter T. +Measured in SU units. + + + 1 64 + + 64 + + + + SUREM parameter D. +Measurement units are in SUs. + + + 1 256 + + 256 + + + + SUERM parameter N. +Measurement units are in SUs. + + + 1 256 + + 16 + + + + Normal AERM threshold, Tin. Number of signal errors that cause abortion of a normal proving peroid. + +Measurement units are SUs. + + + 1 7 + + 4 + + + + Emergency AERM threshold, Tie. Number of signal units errors that cause abortion of an emergency proving period. + +Measurement units are SUs. + + + 1 7 + + 1 + + + + Proving abort limit. Number of consecutive aborted proving periods that will cause a return to the Out Of Service state. + +Measurement units are the number of proving periods. + + + 1 7 + + 5 + + + + Maximum time to stay in Aligned Ready state before signalling link failure. + +Measurement units are milliseconds. + + + 10 65500 + + 40000 + + + + Maximum time to stay in Not Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 262000 + + 5000 + + + + Maximum time to stay in Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 1000 + + + + Length of the normal proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 7500 + + + + Length of the emergengcy proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 400 + + + + Time between sending Status Indication "B" while in the Congested state. + +Measurement units are milliseconds. + + + 1 255 + + 80 + + + + Maximum time a remote site may remain in the congestated state before signalling link failure. + +Measurement units are milliseconds. + + + 10 8100 + + 3000 + + + + Maximum time to wait for an expected acknowledgement of an MSU before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 500 + + + + The speed of the link. Only supported values are 64 and 56 kbit/s. +0 = 64 kbit/s. +1 = 56 kbit/s. + + + + + 0 1 + + 0 + + + + The error correction algorithm to use. Only Basic Error Correction (BEC) is supported. +0 = BEC + + + + 0 1 + + 0 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 1 messages towards client. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 2 messages towards client. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 3 messages towards client. + + + 1 100 + + 90 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 1 messages. + + + 1 100 + + 60 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 2 messages. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 3 messages. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 1 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 2 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 3 is discarded by MTP2. + + + 1 100 + + 100 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 60 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 70 + + + + + + + The speed of the link. Only supported values are 64 and 56 kbit/s. +0 = 64 kbit/s. +1 = 56 kbit/s. + + + + + 0 1 + + 0 + + + + The error correction algorithm to use. Only Basic Error Correction (BEC) is supported. +0 = BEC + + + 0 1 + + 0 + + + + Proving abort limit. Number of consecutive aborted proving periods that will cause a return to the Out Of Service state. + +Measurement units are the number of proving periods. + + + 1 7 + + 5 + + + + SUERM parameter D. +Measurement units are in SUs. + + + 1 256 + + 256 + + + + SUERM parameter N. +Measurement units are in SUs. + + + 1 256 + + 16 + + + + SUERM parameter T. +Measured in SU units. + + + 1 64 + + 64 + + + + Emergency AERM threshold, Tie. Number of signal units errors that cause abortion of an emergency proving period. + +Measurement units are SUs. + + + 1 7 + + 1 + + + + Maximum time to stay in Aligned Ready state before signalling link failure. + +Measurement units are milliseconds. + + + 10 65500 + + 45000 + + + + Maximum time to stay in Not Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 262000 + + 132000 + + + + Maximum time to stay in Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 1000 + + + + Length of the emergengcy proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 500 + + + + Length of the normal proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 8200 + + + + Time between sending Status Indication "B" while in the Congested state. + +Measurement units are milliseconds. + + + 1 255 + + 100 + + + + Maximum time a remote site may remain in the congestated state before signalling link failure. + +Measurement units are milliseconds. + + + 10 8100 + + 5000 + + + + Maximum time to wait for an expected acknowledgement of an MSU before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 2000 + + + + Normal AERM threshold, Tin. Number of signal errors that cause abortion of a normal proving peroid. + +Measurement units are SUs. + + + 1 7 + + 4 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 1 messages towards client. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 2 messages towards client. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 3 messages towards client. + + + 1 100 + + 90 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 1 messages. + + + 1 100 + + 60 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 2 messages. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 3 messages. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 1 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 2 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 3 is discarded by MTP2. + + + 1 100 + + 100 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 60 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 70 + + + + + + This enumeration specifies the different stages of the emergency state. + + Emergency state has not been activated since installation of license key file. + 0 + + + All capacity restrictions removed and all features enabled. The maximum time in this state is 7 days. + 1 + + + A new license key file has to be istalled in order not to jopardize future use and performance. +The maximum time in this state is 7 days. + 2 + + + All features enabled again for a maximum period of 7 days then a new license key file has to be installed in order to be able to use this node. + 3 + + + Use of the node is no longer allowed since no new license key file has been installed. + 4 + + + + + This attribute provides information about the current EmergencyState. + +Note: for the states NEVER_USED and USE_DISABLED the return value for time is insignificant. + + The current emergency state of the license server. + + NEVER_USED + + + + This attribute holds information on the time elapsed in this state. + +Note: The time out values for the states ALL_OPEN, DEGADED and PROLONGED is 7 days. The unit for this attribute is seconds. +1 day = 86400 seconds +7 days = 604800 seconds. + + 0 + + + + + + + Warm node restart at restart of the last PIU. + 4 + + + Cold node restart at restart of the last PIU. + 3 + + + Warm node restart at fault mark of the last PIU. + 2 + + + Cold node restart at fault mark of the last PIU. + 1 + + + + + + Maximum number of SD PDUs before a poll is sent. + +maxPD < initialCredit + + + 10 10000 + + 25 + + + + Maximum number, odd integer value, of list elements placed in a STAT PDU. + +Note: The maxStat attribute is dependent on the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The maxStat times 4 (octets) plus additional 12 octets (for header) must not exceed the AAL5 maximum SDU size (lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). +The consistency control is not performed until the UniSaalTp MO is created since there is no relation between the UniSaalProfile MO and the Aal5TpVccTp MO. + + + 3 1001 + + 67 + + + + Initial number of credits. + +Note: For 64 kbit/s use 30. + +Note! The value for initialCredit must be larger than the value of maxPD. + + + + 10 1000 + + 250 + + + + Timer to be used during a period of no outstanding acknowledgements or new data pending receipt of credit. At timeout the peer is polled to see if it is alive. The timer determines the interval between polls in transient phase. This timer should be greater than the roundtripdelay and also greater than timerpoll. Time unit = milliseconds. + + + + 10 10000 + + 2000 + + + + Timer to determine the maximum time interval during which at least one STAT PDU reception is expected as a response to a poll. This timer should be equal to timerKeepAlive+roundtripdelay. Time unit = milliseconds. + + + 10 100000 + + 7000 + + + + Timer running when there are no PDUs to transmit and there are no outstanding acknowledgements or data pending for credit. When this timer is running, no POLL PDUs are sent. This timer should be significantly greater than timerKeepAlive value. Time unit = milliseconds. + + + 1000 600000 + + 15000 + + + + Timer determining the time between re-transmission of PDUs: BGN, END, ER, RS. Should be slightly more than the roundtripdelay. Time unit = milliseconds. + + + 10 10000 + + 1000 + + + + Timer that specifies the maximum time between sending of POLL PDUs to the peer receiver during other traffic (active phase). Time unit = milliseconds. + + + 10 100000 + + 750 + + + + Maximum number of re-transmissions of PDUs: BGN, END, ER, RS. Time unit = milliseconds. + + + 0 100 + + 4 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationAbatement < congestationOnSet <= 100. + + + 0 100 + + 70 + + + + Attribute specifying the percentage of the buffer for which congestion is stopped. If the congestionAbatement level is lesser but almost equal to congestionOnSet, congestion alarms might be raised and ceased very often. + +This attribute should follow the rule 0 <= congestationAbatement < congestationOnSet <= 100. + + + 0 100 + + 60 + + + + + + Struct holding the values for an NniSaalProfile. + +NOTE: Congestition Level 1 - 3 is supported. + + Timer that specifies the maximum time between sending of POLL PDUs to the peer receiver during other traffic (active phase). Time unit = milliseconds. + + + 10 100000 + + 50 + + + + Maximum number of re-transmissions of PDUs: BGN, END, ER, RS. + + + 0 100 + + 4 + + + + Maximum number of SD PDUs before a poll is sent. + +maxPD < initialCredit + + + 0 10000 + + 25 + + + + Maximum number, odd integer value, of list elements placed in a STAT PDU. + +Note: The maxStat attribute is controlled by the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The maxStat times 4 (octets) plus additional 12 octets (for header) must not exceed the AAL5 maximum SDU size (lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). + +The consistency control is not performed until the NniSaalTp MO is created since there is no relation between the NniSaalProfile MO and the Aal5TpVccTp MO. + + + 3 1001 + + 67 + + + + Initial number of credits. + +Note: For 64 kbit/s use 30. + +Note! The value for initialCredit must be larger than the value of maxPD. + + + 10 1000 + + 250 + + + + Timer to be used during a period of no outstanding acknowledgements or new data pending receipt of credit. At timeout the peer is polled to see if it is alive. The timer determines the interval between polls in transient phase. This timer should be greater than the roundtripdelay and also greater than timerpoll. Time unit = milliseconds. + + + 10 10000 + + 100 + + + + Timer to determine the maximum time interval during which at least one STAT PDU reception is expected as a response to a poll.This timer should be equal to timerKeepAlive+roundtripdelay. Time unit = milliseconds. + + + 10 100000 + + 500 + + + + Timer running when there are no PDUs to transmit and there are no outstanding acknowledgements or data pending for credit. When this timer is running, no POLL PDUs are sent. This timer should be significantly greater than timerKeepAlive value. Time unit = milliseconds. + + + 10 10000 + + 100 + + + + Timer determining the time between re-transmission of PDUs: BGN, END, ER, RS. Time unit = milliseconds. +Should be more than the roundtrip delay. + + + 10 10000 + + 200 + + + + Management Proving Status which is used to decide if proving is done or not during SAAL connection setup. + + + 0 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationLevel1OnSet <= congestationLevel2OnSet <= congestationLevel3OnSet <= 100. + + + 0 100 + + 70 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationLevel1OnSet <= congestationLevel2OnSet <= congestationLevel3OnSet <= 100. + + + 0 100 + + 80 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationLevel1OnSet <= congestationLevel2OnSet <= congestationLevel3OnSet <= 100. + + + 0 100 + + 90 + + + + Attribute specifying the percentage of the buffer for which congestionLevel1 is stopped. If the congestionAbatement level is lesser but almost equal to congestionOnSet, congestion alarms might be raised and ceased very often. + + + + 0 100 + + 60 + + + + The length of proving in terms of number of transmitted PDUs (n1). +noOfPDUsDuringProving x T3 < T2 + +For the TTC standard the only allowed value is 0 (which means no proving). + + + 0 100000 + + 1000 + + + + State variable which defines max number of retransmissions of PDUs during proving to consider proving successful. + + + + 0 100 + + 0 + + + + Maximum time of no credit. If the timer expires, the assured data transfer mode is released. + + + 0 100000 + + 1500 + + + + Timer which is set whenever a report of SSCOP recovery is received from the SSCF. If the timer is running when another report of recovery is received, the assured data transfer mode is released. If the timer expires, nothing is done. Time unit = milliseconds. + + + 0 86400000 + + 3600000 + + + + Timer between the link release action and the next link re-establish action during the alignment. At expiry of timer T1, a new attempt to setup assured data transfer mode to the peer is done. Time unit = milliseconds. + + + + 10 100000 + + 5000 + + + + Total time that SSCF will attempt alignment. At expiry of timer T2, the alignment procedure will be interrupted. + Time unit = milliseconds. + + + + 10 200000 + + 30000 + + + + Time between proving PDUs. The timer is set such that loading of the signalling link is approximately 50% of its nominal rate. +Time unit = milliseconds. + + + 5 1000 + + 5 + + + + + + Exception thrown when a time slot appears more than once in the time slot list. + + + + RefActivity can have the following values: + +inactive = Synchronization reference is currently not used in system clock generation. +active = Synchronization is used in system clock generation. + + + 1 + + + 2 + + + + + RefState can have the following values: +failed = synchronization reference is not capable to perform its required tasks. +degraded = capability of synchronization reference to perform its required tasks is degraded e.g. because of signal level degradation. This value is only applicable for traffic carrying (ET physical path termination) synchronization references. Note: attribute degradationIsFault controls whether synchronization reference degradation is interpreted as a synchronization reference fault or not. +lossOfTracking = system clock regulation algorithm on TU board can not follow the 8kHz synchronization reference signal either because of the poor quality of the signal or because of a HW fault at TU board. If all synchronization references repeatedly end up to state lossOfTracking, fault is likely in TU HW. +ok = synchronization reference is capable of performing its required tasks. + + + 0 + + + 1 + + + 2 + + + 3 + + + + + FaultCriteria can have the following values: +degrNotFault = synchronization reference degradation is NOT interpreted as a synchronization reference fault. +degrIsFault = synchronization reference degradation is interpreted as a synchronization reference fault. + + 0 + + + 1 + + + + + ClockState can have the following values: +startUp = +locked = system clock signal on Timing Unit is locked: a synchronization reference is used in the system clock generation, clock accuracy is 50 ppb or better. +holdOver = system clock signal on Timing Unit is hold-over: no synchronization reference is used in system clock generation, clock accuracy is 50 ppb or better. +freeRunning = system clock signal on Timing Unit is free running: no synchronization reference is used in system clock generation, clock accuracy is 4.6 ppm or better. +failed = system clock signal on Timing Unit is failed: fault in system clock generation function, no quarantee of clock accuracy level. +not Applicable = system clock signal on Timing Unit is not applicable: TU board not present. + + 0 + + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + 6 + + + 7 + + + + + Exception thrown when an object is already registered. + + + + Exception thrown when the maximum number of references is reached. + + + + Exception thrown when a priority is already in use. + + + + Exception thrown when the priority is out of range. + + + + Exception thrown when an reference is not valid, null or of incorrect type. + + + + Exception thrown when trying to de-register an object that is not registered in the database. + + + + + 0 + + + 1 + + + 2 + + + + + Exception thrown when a fro Id is not unique. + + + + + 0 + + + 1 + + + 2 + + + + + A predefined group consisting of working links and their corresponding protecting links. These links form the n+m link redundancy. + + Defines physical link status. + + 1 + + + Defines physical link status. + + 2 + + + Defines physical link status. + + 3 + + + + + + Global title indicator should have following values for both ITU and TTC: + +The values for the GT Indicator + +Value Comment + +0 No new global title +2 TT only +3 TT-NP-ES +4 TT-NP-ES-NOA + +Explanation: + +TT = translation type +NP = numbering plan +ES = encoding scheme +NOA = nature of address indication + + + 0 4 + + 0 + + + + Indicates number type, i.e. national or international number. +Coding of the Nature Address: + +0 = "unknown" +1 = "Subscriber number" +2 = "Reserved for national use" +3 = "National significant number" +4 = "International number" + + + 0 4 + + 0 + + + + Indicates which numbering plan that is used. + +Coding of the Numbering Plan: + +0 = "Unknown" +1 = "ISDN/Telephony Numbering Plan" +3 = "Data Numbering Plan" +4 = "Telex Numbering Plan" +5 = "Maritime Mobile Numbering Plan" +6 = "Land Mobile Numbering Plan" +7 = "ISDN/Mobile Numbering Plan" + + + + 0 7 + + 0 + + + + Used to direct the message to the appropriate Global Title translation function. + + + 0 254 + + + + + Digit string of 1-37 digits, where each digit is 0-9, and B, C. B and C are for Code 11 and Code 12. +The addressInformation may also contain wild card symbols: "*" or "?". Wild cards are only allowed for defining Global Title Translations, they are not allowed for specifying SCCP SAPs (built with SPC and Global Title or SPC + SSN + Global Title). + + + 1 37 + + + + + Indicates if the number of address signals are an odd or even number, and is coded as follows: + +0 = "Unknown" +1 = "BCD, odd number of digits" +2 = "BCD, even number of digits" + +Other values in the encoding scheme will result in the error "Wrong Nature Of Address", (Routing failure reason=No translation for an address of such nature). + + + 0 2 + + 0 + + + + + + + The when sharing mode is set to loadShare the SCCP traffic is load shared between the two entities (access points). + 0 + + + When the sharing mode is set to dupliDominant the second entity (access point) is a backup for the first entity. + 1 + + + + + Possible values for number signalling. + + Unkown encoding scheme. + 0 + + + BCD, odd number of digits. + 1 + + + BCD, even number of digits. + 2 + + + + + Global title indicator values for China, ITU, TTC and ANSI. + +Note: China, ITU and TCC will use TT_ONLY, TT_NP_ES, TT_NP_ES_NOA, NOA_ONLY. + +ANSI will use: +ANSI_TT_NP_ES = 5 +ANSI_TT_ONLY = 6 + + + Translation Type only. + +Only valid for China, ITU and TTC. + 2 + + + Translation Type, Numbering Plan and Encoding Scheme. + +Only valid for China, ITU and TTC. + 3 + + + Translation Type, Numbering Plan, Encoding Scheme, and Nature Of Address indication. + +Only valid for China, ITU and TTC. + 4 + + + Nature of Address indicator only. + +Only valid for China, ITU and TTC. + 1 + + + Translation Type, Numbering Plan and Encoding Scheme. + +Only valid for ANSI. + + 5 + + + Translation Type only. + +Only valid for ANSI. + + 6 + + + + + Phone number types. + + Unknown number type. + 0 + + + Subscriber number type. + + 1 + + + Reserved for national use, number type. + 2 + + + National Significant Number type. + 3 + + + International number type. + 4 + + + + + Numbering plans. + + Unknown numbering plan. + 0 + + + ISDN/Telephony numbering plan. + + 1 + + + Data numbering plan. + 2 + + + Telex numbering plan. + + 3 + + + Maritime mobile numering plan. + + 4 + + + Land mobile numbering plan. + + 5 + + + ISDN/Mobile numbering plan. + 6 + + + + + + 0 + + + 1 + + + + + + Controls when to send SST (SCCP Subsystem Test message). + +0 = Wait for tStatInfo timer to expire once after MTP_RESUME before sending SST. +1 = Send SST immediately after MTP_RESUME, then start tStatInfo timer. + + 1 + + + + Controls when to send SSA (SCCP Subsystem Allowed message). + +0 = Do not send SSA when client attaches, wait until SST is received. (default for ANSI/CHINA/ITU/TTC) +1 = Send SSA immediately when client attaches. + + 0 + + + + Controls whether to send SSP (SCCP Subsystem Prohibited message). + +0 = Do not send SSP when client detaches. (default for TTC) +1 = Send SSP immediately when client detaches. (default for ANSI/CHINA/ITU) + + 1 + + + + Controls whether to send SST messages or not (SCCP Subsystem Test message). + +0 = Send SST as indicated by sendSST. (default for ANSI/CHINA/ITU) +1 = (not used) +2 = (not used) +3 = Do not initiate SST messages at all, ie. do not start timer tStatInfo nor send any SST at MTP_RESUME. (default for TTC) + + 0 + + + + Controls the remote broadcast. + +0 = allow remote broadcast. (default for ANSI/CHINA/ITU/TTC) +1 = do not allow remote broadcast + + 0 + + + + Controls whether to initiate hardcoded congestion timer or not. + +0 = start timer when SSC is received. (default for CHINA/ITU/TTC) +1 = do not start timer + +Note! This attribute is not valid for the ANSI standard. + + 0 + + + + + + + 0 + + + 1 + + + + + + + + + + + J1Type can have the following values: +J1_G = 0 according to TTC JT-G703/G704 +J1_I = 1 according to TCC JT-I431 + + J1 according to TTC JT-G703/G704 + 0 + + + J1 according to TCC JT-I431 + 1 + + + + + Indicates what standard the MAO is operating to. + + The standard mode is Telecommunication Technology Committee (TTC). + 2 + + + The standard mode ANSI. + 0 + + + The standard mode is ETSI. + 1 + + + + + Indicates what multiplexing is being used. + + Standby for protection. + 0 + + + Multiplexing terminated at the E1/J1/T1 level. + 1 + + + Multiplexing terminated at the VC-4/STS3CSPE level. + 2 + + + + + The loopback method available for use by the Os155SpiTtp MO. + + No loopback in use. + 0 + + + Loopingback using line. + 1 + + + + + The switch modes. + + Automatic switching. + 0 + + + Locked for swtiching. + 1 + + + + + + + + + + + + + + + + + + + + Path Trace Formats. + + 16 byte path trace format according to ITU-T G707 table 4. + 16 + + + 64 byte path trace format according to section 3.3.2.3, Telecordia GR-253-CORE. + 64 + + + + + Cyclical Redundancy Checks 4 modes. + + CRC 4 is off. + 0 + + + CRC 4 is on. + 1 + + + CRC 4 is automatic. + 2 + + + + + Idle patterns. + + A law idle pattern. + 1 + + + Micro law idle pattern. + 2 + + + Undefined idle pattern. + 0 + + + + + The possible loopback states for E1/J1/T1/E3/T3PhysPathTerm MOs. + + This is the normal state, no loop back is preformed (and ordinary traffic is running). + 0 + + + The phyiscal path is looped on the line side, the external incoming path is looped back to the external outgoing path. + 1 + + + The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + 2 + + + + + L stands for long haul interface and S stands for short haul interface. +The subsequent figure specifies the cable distance in feets. + + Long Haul 6000 ft, -0 dB + 8 + + + Long Haul 4000 ft, -7 dB + 7 + + + Long Haul 2000 ft, -15 dB + 6 + + + Long Haul 0 ft, -22 dB + 5 + + + Short Haul 0..133 ft + 0 + + + Short Haul 134..266 ft + 1 + + + Short Haul 267..399 ft + 2 + + + Short Haul 400..533 ft + 3 + + + Short Haul 534..655 ft + 4 + + + + + Priority attributes for MTP3b SP of the ITU standard. + + The prioSlt attribute sets the priority for the + Signalling Link Test Message and Acknowledge (SLTM / SLTA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioTra attribute sets the priority for the +Traffic Restart Allowed signal (TRA) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioUpu attribute sets the priority for the + User Part Unavailable (UPU) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioLink attribute sets the priority for link related messages when issued by the MTP3b itself. The messages are : + +Link INhibit (LIN), Link UNinhibit (LUN), +Link Inhibit Denied (LID), +Link Inhibit Acknowledge (LIA), +Link Uninhibit Acknowledge (LUA), +Link Forced Uninhibit (LFU), +Link Local inhibit Test (LLT) and +Link Remote inhibit Test (LRT) + +When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + + + ITU timers for MTP3bSpItu. Timervalues in 1/10 s (deciseconds). + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, second attempt + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Waiting for uninhibit acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for force uninhibit. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for inhibition acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Supervision timer for the first phase of a restarting STP. This is an STP specific parameter, which is ignored when configured as an endpoint. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + + 1 65535 + + 550 + + + + Controlling the response of the receipt of a traffic restart message from an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 680 + + + + Overall MTP restart timer at the restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 600 + + + + Overall MTP restart timer at an adjacent signalling point to a restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 640 + + + + Local inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Remote inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Supervision timer for SLTA message (time within SLTA should arrive). + +Timer T1 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer for sending SLTM periodically. + +Timer T2 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Timer used for message acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for audit procedure. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay to avoid mis-sequencing of messages when an association fails. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing of messages when an association becomes active. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to prohibit sending of DUNA messages via the response method. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Delay to avoid message mis-sequencing on controlled/forced rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlloing the traffic activation delay during restart phase. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + The forever interval period for trying association after an unsiccessfull trial. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlling the period a route set is considered congested when a SCON message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for SCTP_ASSOCIATE_REQ message acknowledgement. This is the maximum time to wait for the SCTP_COMMUP_IND mesage before considering it to be an error. +It should be longer than the time a message spends to reach the most distant destination, be processed and returned. + + + 1 65535 + + 20 + + + + + + The supported congestion levels. + + No Congestion. + 0 + + + Congestion level low. + 1 + + + Congestion level medium. + 2 + + + Congestion level high. + 3 + + + + + + + + + + + + 0 + + + 1 + + + + + Indicates which type of geographical network, e.g. national, international, etc.. + +Note: Not applicable for TTC. + + International Network. + 0 + + + Spare (for international use only). + 1 + + + National network. + 2 + + + Reserved for national use. + 3 + + + + + Indicates how a TransFer Restricted (TFR) signal is handled. + + Treat the TransFer Restricted (FTR) signal as a TransFer Allowed (TFA) signal. + 1 + + + Ignore the TransFer Restricted (TFR) signal. + 0 + + + Handle the incoming TRF messages according to the standard. + 2 + + + + + Indicates whether the two spare bits in the Service Information Octet (SIO) should be treated as spare or for indicating a priority level. + + The two spare bits in the SIO are treated as spare. + 0 + + + The two spare bits in the SIO are to be used for indicating a priority level. + 1 + + + + + Indicates which version of the ITU standard. + + ITU-T -88. + 0 + + + ITU-T 03/93. + 1 + + + ITU-T 07/96 + 2 + + + + + ANSI timers for MTP3bSpAnsi. Timervalues in 1/10 s (deciseconds). + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, second attempt + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Waiting for uninhibit acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for force uninhibit. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for inhibition acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer to limit sending of TFPs and TFRs in response to unexpected TRA and TRW. This timer is specific for STP functionality and is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay extension timer invoked on reciept of a Traffic Restart Waiting message from an adjacent SP which is restarting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Controlling the periodic resend of Traffic Restart Waiting messages during restart of the local node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 120 + + + + Timer enforcing a minimum node unavailablility period during MTP restart. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Delay timer controlling a timed reaction of the restart of an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Timer controlling the response of the receipt of Traffic Restart messages from an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 600 + + + + Controlling the periodic resend of Local Inhibit Change Message. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1000 + + + + Controlling the periodic resend of Remote Inhibit Test Message. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1000 + + + + Delay on commencement of MTP Restart to allow the node to rebuild an accurate routing table based on messages for adjacent nodes. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 600 + + + + Supervision timer for routing updates on MTP Restart. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 40 + + + + Timer controlling the detection of false link congestion. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer for sending SLTM periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Supervision timer for SLTA message (time within SLTA should arrive). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer used for message acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for audit procedure. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay to avoid mis-sequencing of messages when an association fails. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing of messages when an association becomes active. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to prohibit sending of DUNA messages via the response method. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Delay to avoid message mis-sequencing on controlled/forced rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlloing the traffic activation delay during restart phase. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + The forever interval period for trying association after an unsiccessfull trial. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlling the period a route set is considered congested when a SCON message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer used for SCTP_ASSOCIATE_REQ message acknowledgement. This is the maximum time to wait for the SCTP_COMMUP_IND mesage before considering it to be an error. +It should be longer than the time a message spends to reach the most distant destination, be processed and returned. + + + 1 65535 + + 20 + + + + + + TTC timers for MTP3bSpTtc. Timervalues in 1/10 s (deciseconds). + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer pending a Signalling Route Test Acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + + + Priority attributes for MTP3b SP of the ANSI standard. + + The prioSlt attribute sets the priority for the + Signalling Link Test Message and Acknowledge (SLTM / SLTA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) + + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioTra attribute sets the priority for the +Traffic Restart Allowed signal (TRA) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioUpu attribute sets the priority for the + User Part Unavailable (UPU) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioLink attribute sets the priority for link related messages when issued by the MTP3b itself. The messages are : + +Link INhibit (LIN), Link UNinhibit (LUN), +Link Inhibit Denied (LID), +Link Inhibit Acknowledge (LIA), +Link Uninhibit Acknowledge (LUA), +Link Forced Uninhibit (LFU), +Link Local inhibit Test (LLT) and +Link Remote inhibit Test (LRT) + +When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + + + Priority attributes for MTP3b SP of the TTC standard. + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) +. + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioTfa attribute sets the priority for the Transfer Allowed, TFA, messages. + + + HIGHEST + + + + The priority indicator used for indicating message priority for signalling route test messages (SRT/SRA). + + + HIGHEST + + + + The priority indicator used for indicating the message prioirity for TFC. + + + HIGHEST + + + + + + Indicates the priority level for MTP 3. + + Lowest priority setting. + 0 + + + Low priority setting. + 1 + + + High priority setting. + 2 + + + Highest priority setting. + 3 + + + + + China timers for MTP3bSpChina. Timervalues in 1/10 s (deciseconds). + + Supervision timer for SLTA message (time within SLTA should arrive). + +Timer T1 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer for sending SLTM periodically. + +Timer T2 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Waiting for uninhibit acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for force uninhibit. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for inhibition acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Supervision timer for the first phase of a restarting STP. This is an STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + + 1 65535 + + 200 + + + + Controlling the response of the receipt of a traffic restart message from an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 40 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Overall MTP restart timer at the restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 40 + + + + Overall MTP restart timer at an adjacent signalling point to a restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Local inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Remote inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, second attempt + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Timer used for message acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for audit procedure. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay to avoid mis-sequencing of messages when an association fails. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing of messages when an association becomes active. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to prohibit sending of DUNA messages via the response method. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Delay to avoid message mis-sequencing on controlled/forced rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlloing the traffic activation delay during restart phase. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + The forever interval period for trying association after an unsiccessfull trial. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlling the period a route set is considered congested when a SCON message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for SCTP_ASSOCIATE_REQ message acknowledgement. This is the maximum time to wait for the SCTP_COMMUP_IND mesage before considering it to be an error. +It should be longer than the time a message spends to reach the most distant destination, be processed and returned. + + + 1 65535 + + 20 + + + + + + Indicates which type of geographical network, e.g. national, international, etc.. + +Note: Only for TTC. + + National network. + 0 + + + Spare (for international use only). + 1 + + + International Network. + 2 + + + Spare. + 3 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + idle, the Mtp3bSl carries no traffic. + 0 + + + active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. + 1 + + + busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + 2 + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + 0 - not initialized. + 0 + + + 1 - initialized. + 1 + + + + + The nodeBehaviorType attribute represents the MTP3b node type. + + Signaling End Point. + 0 + + + Signalling Transfer and End Point, i.e the signalling point is of both type Signalling End Point (SEP) and Signalling Transfer Point (STP). + 4 + + + Signaling GateWay, Signaling End Point and Signalling Transfer Point, i.e the signalling point is of both type Signalling Transfer Point (STP), Signaling End Point (SEP) and Signaling GateWay (SGW). + 5 + + + + + Priority attributes for MTP3b SP of the China standard. + + The prioSlt attribute sets the priority for the + Signalling Link Test Message and Acknowledge (SLTM / SLTA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioTra attribute sets the priority for the +Traffic Restart Allowed signal (TRA) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioUpu attribute sets the priority for the + User Part Unavailable (UPU) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioLink attribute sets the priority for link related messages when issued by the MTP3b itself. The messages are : + +Link INhibit (LIN), Link UNinhibit (LUN), +Link Inhibit Denied (LID), +Link Inhibit Acknowledge (LIA), +Link Uninhibit Acknowledge (LUA), +Link Forced Uninhibit (LFU), +Link Local inhibit Test (LLT) and +Link Remote inhibit Test (LRT) + +When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + + + The type of Signalling Route. + + 0 + + + 1 + + + + + + Single-homed with ipAddress1. + 1 + + + Single-homed with ipAddress2. + 2 + + + Multihomed association with ipAddress1 and +ipAddress2 + + 3 + + + + + The state of the signaling route. + + The signaling route is not blocked. + 0 + + + The signaling route is blocked. + 1 + + + + + + 0 + + + 1 + + + + + Open Shortest Path First metric type. + + 0 + + + 1 + + + + + The types of the routes found in the IP routing table. + + The source of information is unknown. + 1 + + + Route created from local configuration data (both static and interface routes). +Each interface created gets an entry in the routing table of the RO. + 2 + + + Route added by SNMP. + 3 + + + Route added by OSPF. + 13 + + + Route added by ICMP redirect message. + 4 + + + + + Invalid IP route has been given as a parameter to an action. + + Exception message. + + + + + + + + Invalid IP route has been given as a parameter to an action. + + + + + + + + + + 0 + + + 1 + + + + + The controller mode of a physical interface. + + 1 + + + 2 + + + 3 + + + + + ipAddress - the subnet address of the range. +subnetMask - IP subnet mask of the range to be added. +advertise - indicates whether the area range should be advertised into OSPF. + + + + + + Note! The subnet has to be contigious. That is, has the LSB set to 0 (zero). + +Example: + +255.255.255.X + +Contiguous subnet mask: +11111111.11111111.11111111.11111110 (X = 254) +11111111.11111111.11111111.11111100 (X = 252) + +Not-contiguous subnet mask: +11111111.11111111.11111111.11111010 (X = 250) + + + + + + + + + + IP routing table entry. + + The destination IP address. + + + + The destination IP network mask. + + + + The next hop IP address. + + + + The route metric. + + + + The route type. + + + + + The interface name. + + + + Indicates if the route should be redistributed. + + + + Indicates if the route is active. + + + + + + Denotes whether the autoConfiguration mode for the IpAccessHost is turned on or off. + + 1 + + + 2 + + + + + In case 'NO_PREFERENCE', 'LOCAL_MP_SELECT_VCC_AT_LINK_UP', LOCAL_MP_PEER_SELECTION_VCC' or 'LOCAL_MP_ACTIVE_RESELECTION' is selected the IpAtmLink MO will prefer Aal5TpVccTp on local MP (i.e. Aal5TpVccTp executing on the same MP as the IpAtmLink), but other Aal5TpVccTp will be accepted if needed. + +In case 'ONLY_LOCAL_MP' is selected, the ipAtmLink (Inet Link) will consider Aal5TpVccTp residing on other MPs as a malfunction and discard the usage of them. No InvArp sending will be performed on them and all incomming trafic on them will be discarded. If no local Aal5TpVccTp exists the operational state of the link will be changed to disabled. + + 0 + + + Prefer termination on local MP, select Vcc when link goes up. + 1 + + + Prefer termination on local MP, follow peer selection of Vcc. + 2 + + + Prefer termination on local MP, active reselection to new Aal5TpVccTp as soon as a better choice exists. + 3 + + + Restricted to local MP, follow peer selection if termination is on local MP. + + 4 + + + + + Alarm report for the Virtual path connection termination point. +RDI - Remote defect indication +LOC - Loss of continuity +AIS - Alarm indication signal + + For alarms of type Loss of continuity. + 2 + + + For alarms of type Loss of continuity and Remote defect indication. + 3 + + + For alarms of type Alarm indication signal and Loss of continuity. + 6 + + + For alarms of type Alarm indication signal, Remote defect indication and Loss of continuity. + 7 + + + + + + Performance monitoring is turned off. PM counters give irrelevant values. + 0 + + + Performance monitoring counters are active + + 1 + + + FPM, Forward Performance Monitoring activated. + +Performance monitoring counters are active + + 2 + + + Backward reporting, BR, cells are generated. + +Performance monitoring counters are active + + 4 + + + FPM, Forward Performance Monitoring activated. + +Backward reporting, BR, cells are generated. + +Performance monitoring counters are active + + 6 + + + + + Nominal performance monitoring, PM, blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + Nominal performance monitoring, PM, block size, 2e7 (2 to the power of 7). + 128 + + + Nominal performance monitoring, PM, block size, 2e8 (2 to the power of 8). + 256 + + + Nominal performance monitoring, PM, block size, 2e9 (2 to the power of 9). + 512 + + + Nominal performance monitoring, PM, block size, 2e10 (2 to the power of 10). + 1024 + + + Nominal performance monitoring, PM, block size, 2e11 (2 to the power of 11). + 2048 + + + Nominal performance monitoring, PM, block size, 2e12 (2 to the power of 12). + 4096 + + + Nominal performance monitoring, PM, block size, 2e13 (2 to the power of 13). + 8192 + + + Nominal performance monitoring, PM, block size, 2e14 (2 to the power of 14). + 16384 + + + Nominal performance monitoring, PM, block size, 2e15 (2 to the power of 15). + 32768 + + + + + + Service category Constant Bit rate, CBR. + 1 + + + Service category Unspecified Bit rate, UBR. + 2 + + + Service category Unspecified Bit rate+, UBR+. UBR+ guarantees a certain bandwidth. If higher bandwidth is used it will be handled as UBR. + 3 + + + + + ATM's Quality of Service classes. + +The ATM layer system provides four QoS classes, numbered 1 to 4, where CLASS_ONE gives the best QoS in regards to Cell Loss Ratio <CLR> and Cell Delay Variation <CDV> and CLASS_FOUR doesn't give any QoS guarantees. CLASS_ONE and CLASS_TWO are the only classes applicable for real time traffic. + + CDV < 1 ms (milliseconds), CLR < 10e-8. Typically used by timing unit. + 1 + + + CDV < 1 ms, CLR < 10e-7. Typically used for speech. + 2 + + + CLR < 10e-5. Typically used for signalling. + 3 + + + Typically used for IP. + 4 + + + + + The attributes in this struct represents the ATM header, (vpi, vci, pti), of the last recieved unexpected cell. + + The ATM header vpi. + + 0 + + + + The ATM header vci. + + 0 + + + + The ATM header pti. + + 0 + + + + + + This MO structures the transport network of the managed element. It is created automatically and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, TransportNetwork=1. + + + Label free for use. + + + "" + + + + + + + + + + + + + This action returns a sequnce of Aal5TpVccTp MOs that is unreserved and executes on an MP. + +Also the following condition has to be fullfilled: + +MinAal5Sdu = min (fromUserMaxSduSize, toUserMaxSduSize) + +roundedDownSdu = (MinAal5Sdu - (MinAal5Sdu modulo 4) +4) + +roundedDownSdu > low boundry for maxSduSize (in NniSaalTp) + +Note that the values for fromUserMaxSduSize and toUserMaxSduSize is the actual values set in the Aal5TpVccTp MO. +Also note that the attributes minAal5Sdu and roundedDownSdu is used internaly in this action. + +Note! This action requires a transaction. + + + + + + + + This action returns a sequnce of Aal5TpVccTp MOs that is unreserved and executes on an MP. + +Also the following condition has to be fullfilled: + +MinAal5Sdu = min (fromUserMaxSduSize, toUserMaxSduSize) + +roundedDownSdu = (MinAal5Sdu - (MinAal5Sdu modulo 4) +4) + +roundedDownSdu > low boundry for maxSduSize (in UniSaalTp) + +Note that the values for fromUserMaxSduSize and toUserMaxSduSize is the actual values set in the Aal5TpVccTp MO. +Also note that the attributes minAal5Sdu and roundedDownSdu is used internaly in this action. + +Note! This action requires a transaction. + + + + + + + + This action returns a sequence of all unreserved Aal2PathVccTp's that have an Aal2PathId that has not been +used by another Aal2PathDistributionUnit under the same parent (Aal2Ap). + +Note! This action requires a transaction. + + + + + + + + + + + + + + This action returns a sequence of all ReliableProgramUniters that has not reached the maximun number of possible reservations +and has not already been used by other Aal2PathDistributionUnit MO's (if exists) under the same parent (Aal2Ap MO). + +Note! This action requires a transaction. + + + + + + + + + + + + + + This action returns a sequence of PlugInUnits that is unreserved. + +Note! This action requires a transaction. + + + + + + + + This action returns a sequence of Ds0Bundle MOs that is unreserved and only has one (1) timeSlot set in the listOfTimeSlots. +The attribute tdmMode in these Ds0Bundles must be enabled. + +Note! This action requires a transaction. + + + + + + + + + + The Slot MO is used to represent a slot in a subrack. A slot can hold a plug-in-unit, a board, (represented by PlugInUnit MOs). + +The number of slots in a subrack is specified when defining the subrack. + +The system will automatically create the right number of Slot MOs in the subrack at creation of the Subrack MO. +This MO cannot be deleted by an operator. + +The local distinguished names of this MO's are select with identity Slot=1 in the leftmost slot with incremental numbering towards the right in the subrack.. + + + A user friendly name associated to the managed object + + + + + "" + + + + + Gives the state of the slot. + + + + + + + free + + + + + The number of the position from the left side, starting from 1. + + + + + + + + + + + + + + + + + List of reserving MOs. + + + + + + + + + + This product data describes the plug-in-unit that is presently inserted. The information is only available when slotState = used. + + + + + + + + + + + The upgradeGroupId is able to group a number of PIUs, all in the group can be upgraded at the same time. + +If upgradeGroupTypeName is "", this attribute is not used. + + + + 0 + + + + + The upgradeGroupTypeName, together with the upgradeGroupId, define an upgrade group. + + + + "" + + + + + + + The Managed Object MO is not part of the model. It is only used to have valid reference types for certain attributes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO is used to represent the termination of an external VC link in the node. + +Note that a maximum of 10 000 MO of this kind may be configured in a node. + +Note! The performance monitoring counters in the VclTp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + For free use. + + + "" + + + + + Virtual Channel Idenitifier, VCI, value for this Virtual Channel Link, VCL. + +Range: 32 - 65535. + + + + + + + 32 65535 + + + + + + Reference to the AtmTrafficDescriptor profile. + + + + + + + + + User that have reserved this VclTp. + + + + + + + + + The operational state of the VclTp. + + + + + + disabled + + + + + Performance monitoring counter for number of received ATM cells. + + + + + + + + 0 + + + + + Performance monitoring counter for number of transmitted ATM cells. + + + + + + + + 0 + + + + + The availability status of the VclTp. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + Used by VclTp to inforce a Virtual Channel end-to-end loopback. +false=Failed, true=Succeded. + +Note! This action requires a transaction. + + + + + + + + + + The Managed Element MO is the top MO in the MOM. A management application will communicate with the Managed Element MO for the purpose of monitoring it and controlling it. + +The ManagedElement MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1. + + + For free use. + + + "" + + + + + This attribute gives information about geographical location (e.g. place name). + + + + 0 255 + + "" + + + + + This attribute gives a logical name of a site. + + + + + + 0 255 + + "" + + + + + This attribute describes the product type and is always set to the value "Node". + + + + + Node + + + + + This attribute describes the implemented functionality. + + + + 0 12 + + "" + + + + + This attribute uniquely identifies the product (e.g. ROF123). + + + + 0 24 + + "" + + + + + This attribute identifies the version of the product (e.g. R2A). + + + + 0 7 + + "" + + + + + + + + + + + + + Restart the node with an unconditional reload. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + This Managed Object is used as a structural element for the network element, i.e. it only acts as a container for other MO:s. This MO structures the equipment of the network element. + +The local distinguished name of this MO is ManagedElement=1, Equipment=1. + + + Label free for use. + + + "" + + + + + + + + + + + + + + + This MO is used to represent a subrack. + + + A free tag that a user can associated to the this managed object. The value has no relevance for the managed system. + + + "" + + + + + A reference to a SwitchModule ManagedObject, from which the SwitchModule number can be retrived. That number describes how the subrack is connected to the node, i.e. how the subracks cables are connected to the hub subrack. (The hub subrack has switch module number 0). + + + + + + + + + There can only be one hub subrack in the node. The hub subrack is used to control switching and synchronization for the complete node. + + + + + + + + + + + This attribute describes the product type and is always set to the value "HW". + + + + + + "HW" + + + + + This product data describes the subrack that is configured to be installed. + + + + + + + + + The position of this subrack within a cabinet. +The purpose of this attribute is to help an operator locate the source of an error by letting the system put this +information in alarms. The system does not use this information in any other way i.e. it does not affect the +operation of the system. +The subrack position is an integer (1-n) stating the cabinet Id, starting from the left and a letter (A-Z) stating +the Subrack vertical position starting from the ground, e.g. 5C. + + + "" + + + + + The position of the cabinet (within a group of other cabinets) in which this subrack is placed. +The purpose of this attribute is to help an operator locate the source of an error by letting the system put this information in alarms. The system does not use this information in any other way i.e. it does not affect the operation of the system. + + + "" + + + + + + + + + + + + + Defines the number of slot in the subrack. The default value is 28. + + + + + + + + 1 28 + + 28 + + + + + The operational product data describes the subrack that is actually installed. + + + + + + + + + + + + A reference to the SwAllocation MO that has reserved this Subrack for Fan MO upgrades.. +The attribute is set/cleared by internal actions. + + + + + + + + Removes the given number of Slot MOs from the model. The Slots with the highest slotNumber are removed. After the action no Slot will have apn = 0. +The attribute numberOfSlots will be udated. + +If there is a child MO the action will fail and the MOHasChildrenException is thrown. + +Note! This action requires a transaction. + + + + + The number of slots to remove. + + + + + + + + + + This MO is used to represent software installed in the file system. + +LoadModule MO can represent files with executable code, files with text information +(COI) or directories in Cello file system. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + +Note! In order for a program to be reliable the following conditions must be fulfilled: + +1. The attribute 'loaderType' must be set to 'OseLoader'. +2. The attribute 'oseProgramLoadClass' must be set to a value > 100. +3. The program must execute on a MP (Main Processor). + + + + Free tag for marking this managed object. + + + "" + + + + + Product information data. + + + + + + + + + The path to this load module in the file system, including the file name. + +Example: /c/load_modules/CXC112874R1A01 +where /c/load_modules/ is the directory and CXC112874R1A01 is the file name. + + + + + + + + + The type of the program loader. + +Note! This corresponds to LoaderName in the Upgrade Control File (UCF). + + + + + OseLoader + + + + + This attribute must have a value if the loaderType attribute equals other. + + + + + "" + + + + + A recommendation to the system to (if possible) cache this load module close to where its program(s) execute(s), e.g. in a flash file system. The purpose of this attribute is to enable faster loading at restart of programs referring to this load module. + + + + + + + + no + + + + + The file format (RPDOUT, html, java, fpga, ...). + + + "" + + + + + Specifies in which load phase programs of this load module should be started. + +Note: If the LoadModule is a java archive file (.jar) it will be loaded in the load phase of the java machine rather than according to its own oseProgramLoadClass. + + + + + application + + + + + Reliable program identity. +Compare this to the reliableProgramLabel in ReliableProgramUniter MO. + + + + + "" + + + + + Indicates if the load module is a file or directory. + + + + + false + + + + + This attribute sets the size of the program pool size. In the referenced loadModule there is +possible to set this value at create. +This value will then be fetched by program and used at create if no value is submitted at +create of the program Mo. +The referenced load module has a default size defined at compile time which is used if no +value is submitted at create of loadModule or the program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Unit is byte. + + + + + 0 + + + + + This attribute sets the size of the program heap size. In the referenced loadModule there is possible to set this value at create. This value will then be fetched by program and used at create if no value is submitted at create of the program Mo. +The referenced load module has a default size defined at compile time which is used if no value is submitted at create of loadModule or the program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Unit is byte. + + + + + 0 + + + + + Indicator whether the (OSE) program must be a singleton or not. + + + + + false + + + + + Contains all class that are to be initialised and started when the JVM restarts. +Technical note: The class name must specify the full package and class name in standard Java syntax, e.g. "se.ericsson.cello.X" ; must implement the se.ericsson.cello.moframework.Mopplet interface and be found in this LoadModule. + + + + + + + + + + + + + + + + + + + + Indicates whether this MO has been reserved by the UpgradePackage MO or not. + + + + + false + + + + + + + This MO is used to administer synchronization references for the network synchronization function and to view the system clock state of Timing Unit boards. + +Synchronization can have 0 to 8 relations to other MOs. The only valid MOs where relations can exist are E1Physpathterm, J1Physpathterm, T1Physpathterm, Os155SpiTtp, TU Synchronization Reference, and ManagedObject (for the non-Cello RXI820 MO) MOs. Note that maximum number of relations to these MOs is 8 all together. + +The synchronization MO is automatically created and cannot be deleted. + +Note: An external ManagedObject that wishes to be connected to the Synchronization MO must implement the following interface se.ericsson.cello.equipment.SyncReservable! + +The local distinguished name of this MO is ManagedElement=1,TransportNetwork=1,Synchronization=1 + +. + + + Label free for use. + + + "" + + + + + Controls whether synchronization reference degradation (e.g. signal level degradation) is interpreted as a synchronization reference fault or not. Attribute value is only applicable for traffic carrying synchronization references + + + degrNotFault + + + + + State of system clock signal on Timing Unit A. +Note that system clock generated by TU A (TU in slot 4) has higher priority than TU B (TU in slot 5) system clock, i.e. each device board uses system clocks according to this priority order. + + + + + unknownMode + + + + + State of system clock signal on Timing Unit B. Note that system clock generated by TU A (TU in slot 4) has higher priority than TU B (TU in slot 5) system clock, i.e. each device board uses system clocks according to this priority order. + + + + + unknownMode + + + + + Set of synchronization reference physical resources. An MO reference to an TU synchronization reference MO implementation. +A synchronization reference in added to the system by using action AddSyncRefResource. +Note: if this attributes has value "Non-existing MO reference" then all the respective attributes of type sequence of 8 are not applicable. + +Note: The length of this sequence is always 8. + + + + + + 8 + + + + + + Synchronization reference priority. +1 represents the highest and 8 the lowest priority. Every synchronization reference must have unique priority value. Value 0 means not applicable, that no synchronization with this priority is defined. +This attribute is mandatory when adding a synchronization reference to the system (by using action addSyncRefResource). +A priority value can be changed with the changeSyncRefPriority action provided that the priority is not already assigned to some other SyncRefResource. + +Note: The length of this sequence is always 8. + + + + + + 0 8 + + 0 + + 8 + + + + + Set of synchronization reference activity attributes. + +Note: The length of this sequence is always 8. + + + + + + + inactive + + 8 + + + + + + Set of synchronization reference status attributes. + +Note: The length of this sequence is always 8. + + + + + + + failed + + 8 + + + + + + + + + + + + + + Indicates if the node is redundant from Network Synchronization functions point of view. + + + SYSTEM_CLOCK_USERS_USE_PLANE_A + + + + + This action adds one synchronization reference to the system. As a result of successful action, one set of attributes (attributes of type sequence of 8) is added to Synchronization MO. +Parameters: +syncReference: Managed object implementation, to which a mo-reference is to be added. See description of attribute SyncReference. +syncPriority: Priority of synchronization reference. Each synchronization reference must have unique priority value, this must be checked by synchronization MO. + +Description of exceptions: +- AlreadyRegistered: this reference is already registered +- MaxNoOfRefRegistered: maximum number (8) of synchronization references already present +- PriorityAlreadyInUse: syncPriority is identical with an existing synchronization reference priority +- PriorityOutOfRange: invalid syncPriority value +- InvalidMoReference: invalid syncReference for registration as a synchronization reference (invalid MO type) +- NotPermitted: syncReference does not allow SyncReserve to be performed + +Note: An external ManagedObject that wishes to be connected to the Synchronization MO must implement the following interface se.ericsson.cello.equipment.SyncReservable! + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + This action removes one synchronization reference that has previously been added. +(In future releases, this action should include a check whether the synchronization reference to be removed is the only existing synchronization reference. In that case, the user is asked for a confirmation to remove the last synchronization reference.) +Parameters: +syncReference: Managed object implementation, to which a mo-reference currently exists, but is now to be removed. See description of attribute SyncReference. + +Description of exceptions: +- NotRegistered: synchronization reference is not registered + +Note! This action requires a transaction. + + + + + + + + + + + + + This action changes the synchronization priority of one previously registered synchronization reference resource. +Parameters: +syncReference: Managed object implementation, for which the synchronization priority is to be changed. See description of attribute syncReference. +syncPriority: The new priority of synchronization reference. Each synchronization reference must have unique priority value, this must be checked by synchronization MO. + +Description of exceptions: +- PriorityAlreadyInUse: syncPriority is identical with an existing synchronization reference priority +- PriorityOutOfRange: invalid syncPriority value +- NotRegistered: synchronization reference is not registered + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + This action resets the detected Loss of Tracking error condition of one synchronization reference. After reset the synchronization reference is usable again. +Parameters: +syncReference: Specifies the synchronization reference for which the Loss of Tracking status is to be reset. + +Description of exceptions: +- NotRegistered: synchronization reference is not registered + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This Managed Object represents an SCCP Local Access Point. An SCCP AP instance is a logical point in the SCCP network at which an SCCP user can access the services provided by the SCCP and the SCCP can deliver its services to the SCCP user. The SCCP Access Point is identified by a SubSystem Number (SSN). + +A local SccpAp represents an access point in the own node. + +The performance monitoring counters found in SccpApLocal MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a shutdown request from the CLI (Cluster Interface). + + + + + + + + + + User label for free use. + + + "" + + + + + The operational state of the SCCP AP. The operability of the SCCP AP is described by this attribute which has two possible values: + +Disabled: The SCCP AP is totally inoperable and unable to provide the service to the user. + +Enabled: The SCCP AP is partly or fully operable and available for use. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The sub system number, SSN, of the SCCP Access Point. Note that this has to be a unique number. + +If the SccpAp is local then the SSN has to be unique among all other SccpAp MOs under the same SccpSp MO. + + + + + + + 2 255 + + + + + + The maxConn attribute specifies the max number of connections allowed for this SCCP Access Point. It is only valid for local SCCP Access Points. + + + + + + + 1 524288 + + + + + + List of reserving MOs. + + + + + + + + + + Controls adding of OPC from routing label to Calling Party Address if absent. + +False = Do not add OPC to Calling Part Address. +True = Add OPC to Calling Part Address. + + + + + + false + + + + + + + The Signalling Connection Control Part, SCCP, Signalling Point, SP, MO is the placeholder for all SCCP related managed objects. + +Startime for accounting is set by attributes accountDateFileOutput and accountTimeFileOutput. +The attribute accountPeriodFileOutput sets period for the accounting record to be stored on the /c file system. +The accounting is stopped by setting the accountPeriodFileOutput to zero (0). +NOTE: The SRP function and SccpAccountingCriteria MO's should only be created for one signalling stack, i.e one PIU. + +Note! The guiding values that can be found for some attributes is to be regarded as a recommendation for these attributes. +Depending on the size of the network, traffic load, use and so forth it might be neccesary to set values for these attributes outside the guiding values. + + + + + + + + + + For free use. + + + "" + + + + + The operational state of the SCCP SP. The operability of the SCCP SP is described by this attribute which has two possible values: + +Disabled: The SCCP SP is totally inoperable and unable to provide the service to the user (e.g. if the processor is not usable). + +Enabled: The SCCP SP is partly or fully operable and available for use. + + + + + + disabled + + + + + The identity of the L3 Signaling Point used by this MO. + + + + + + + + + This attribute sets the priority for the Subsystem Test message when issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. +Coding of the message priority: +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 1 + + + + + This attribute sets the priority for the Inactivity Test message when issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. +Coding of the message priority: +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 1 + + + + + This attribute sets the priority for the connection release message when issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. +Coding of the message priority: +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 1 + + + + + This attribute sets the priority for all the other messages which are issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. + +Coding of the message priority: + +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 0 + + + + + Date for accounting file output. +Format in ASCI-code: yyyymmdd +yyyy = 0000-9999 +mm = 01-12 +dd = 01-31 + +Note! This is the start date for the output. + + + "00000000" + + + + + Time for accounting file output. +Format in ASCI-code: hhmm +hh = 00-23 +mm = 00-59 + + + "0000" + + + + + Period for accounting file output. +Format: number of half hour. +Range = 0, 1, 2, 4, 6, 8, 12, 16, 24, 48 + +Note! if set to 0 (zero) the output will be stopped. + + + 0 + + + + + The upper connection threshold allow the user to specify the level at which the upper connection threshold notification is triggered. The thresholds must be given as a percentage of the maximum number of connection resources made available for the entire SCCP. + + + + 0 100 + + 80 + + + + + The lower connection threshold allow the user to specify the level at which the lower connection threshold notification is triggered. The thresholds must be given as a percentage of the maximum number of connection resources made available for the entire SCCP. The value must be less then UpperConnThres. + +The maximum value is less or equal to the upper connection threshold + + + + 0 100 + + 50 + + + + + There are two ways to construct a UDTS from a UDT, the XUDTS will be constructed in the same way. One way is to only swap the pointers to Called Party Address and Calling Party Address in a UDT message when constructing a UDTS. The other way is to swap data. How this is done in the SCCP is configurable. The coding and interpretation is as follows: +0, swap data Called party Address will be sent before Calling party Address +1, swap pointers Called party Address will be sent after Calling party Address. + + + + 0 1 + + 1 + + + + + The SCLC hop counter is a parameter that is decremented for each performed GT translation for SCLC messages on the way to the end destination. If decrementing the counter results in the value of zero in a non-end destination node, the SCCP initiates the appropriate error procedure. + + + + 1 15 + + 8 + + + + + The SCOC hop counter is a parameter that is decremented for each performed GT translation for SCOC messages on the way to the end destination. If decrementing the counter results in the value of zero in no end destination node, the SCCP initiates the appropriate error procedure. + + + + 1 15 + + 8 + + + + + Connection establishment control timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 600 - 1200, Default 600 + + + + + 1 65535 + + 600 + + + + + Send inactivity control timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 3000-6000 +Default 3000 + + + + 1 65535 + + 3000 + + + + + Receive inactivity control timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 6600-12600 +Default 6600 + + + + 1 65535 + + 6600 + + + + + Connection release timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 100-200 +Default 100 + + + + 1 65535 + + 100 + + + + + Congestion timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 10-2550 +Default 300 + + + + 1 65535 + + 300 + + + + + Subsystem Status Test timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 10-2550 +Default 300 + + + + 1 65535 + + 300 + + + + + Connection response waiting timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 100-200 +Default 150 + + + + 1 65535 + + 150 + + + + + Reassembly timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 100-200 +Default 150 + + + + 1 65535 + + 150 + + + + + Guard timer for program restart not applicable for this CPP version. Instead a restart counter is used to improve restart performance. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 13800-15000 (23-25 minutes) +Default 1380 (23 minutes) + + + + + 1 65535 + + 13800 + + + + + The SMI (Subsystem Multiplicity Indicator) is always ignored for incoming messages. This SCCP can however be configured to insert a specific SMI value in outgoing messages. The coding and interpretation is as follows: + +Coding Comment + 0 | Affected Subsystem multiplicity unknown. + 1 | Affected Subsystem is solitary. + 2 | Affected Subsystem is duplicated. + 3 | Spare. + + + + 0 3 + + 0 + + + + + The use of SCMG functions. + +SST = SCCP Subsystem Test message. +SSA = SCCP Subsystem Allowed message. +SSP = SCCP Subsystem Prohibited message. +SSC = SCCP Subsystem Congested message. + +The attributes contained in the struct is: +initiateTimerTcon, +allowRemoteBroadcast, +useSST, +useSSP, +sendSSA, +sendSST + + + + + + + + Connection Oriented SCCP Signaling Relay Point (SRP-CO) and Maximum number of Relayed Connections is not used in this CPP version. + + + + + + + 1 524288 + + + + + + The identity of the reserving MO. + + + + + + + + + + Performance monitoring counter for number of sent UDT's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received UDT's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent UDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received UDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent XUDT's. + + + + + + + + 0 + + + + + Performance management counter for number of received XUDT's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent XUDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received XUDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent CR's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received CR's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent DT1's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received DT1's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent ERR's. + + + + + + + + 0 + + + + + Performance monitoring counter for number of received ERR's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent SSA's, subsystem allowed. + + + + + + + 0 + + + + + Performance monitoring counter for number of CREF messages received from NL. + + + + + + + 0 + + + + + Performance monitoring counter for number of CREF messages sent to NL. + + + + + + + + 0 + + + + + Performance monitoring counter for number of RLSD messages received from NL. + + + + + + + 0 + + + + + Performance monitoring counter for number of RLSD messages sent to NL. + + + + + + + 0 + + + + + Performance monitoring counter for number of connections in use that has exceeded the high watermark threshold. + + + + + + + 0 + + + + + Performance monitoring counter for number of connections in use that has receded the low watermark threshold. + + + + + + + 0 + + + + + Performance monitoring counter for number of received LUDT messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent LUDTS messages. + + + + + + + 0 + + + + + + + The Signalling Connection Control Part Routing Control (SCCP SCRC) MO holds information about the SCCP routing control. + + For free use. + + + "" + + + + + + + + + + + + + Performance monitoring counter for number of routing failures. + + + + + + + 0 + + + + + Performance monitoring counter for number of connect failures. + + + + + + + 0 + + + + + Performance monitoring counter for number of Hop counter violations. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to no translation for Nature of Address field. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to no translation of specific address. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to destination point code not available. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to network congestion. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to destination subsystem unavailable. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to unknown reason. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to unequipped subsystem. + + + + + + + 0 + + + + + + + The Program MO represent the executable software on the target hardware. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + +Note! Some programs are not possible to restart or can take part in an RPU. For more information please refer to the LoadModule MO. + + + + Label free for use. + + + "" + + + + + This attribute gives information about which load module the program is instantiated from. + + + + + + + + + This attribute shows whether the program has normal performance capability or not. + + + + + + disabled + + + + + This attribute shows whether the program is permitted to enter operational state enabled or not after a PIU restart. The default state is disabled in order to avoid that an operating program and a new version of the same program have its startState enabled at the same time. + +It is used on all types of node restarts and restart of PlugInUnit with restartCause = piuRestartUpgrade. + + + disabled + + + + + This attribute sets the size of the program heap size. + +The value in the referenced LoadModule is fetched by program and used at create if no value is submitted at create of the program MO. + +The referenced load module has a default size defined at compile time wich is used if no value is submitted at create of loadModule or the program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + +Note: Setting of this attribute will have no effect until the program is restarted. + + + 0 + + + + + This attribute sets the size of the program pool size. In the referenced LoadModule there is possible to set this value at create. + +The value in the referenced LoadModule is fetched by program and used at create if no value is submitted at create of the program MO. + +The referenced load module has a default size defined at compile time wich is used if no value is submitted at create of +LoadModule or the Program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Only working for MP-Program + +Unit is bytes. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + +Note: Setting of this attribute will not have any effect until the program is restarted. + + + + + 0 + + + + + This type specifies the time that a program have to execute without faults, until the restart counter is reset. The time value is interpreted as seconds. + +restartTimer= -1 : Forever, implies that the restart counter is only reset when the PIU is restarted. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + + + + -1 + + 60 + + + + + This attribute specifies the number of times that a program can restart, without escalation to a PIU restart. The possible values are: + +restartCounterLimit = -1 : Unlimited, means never restart PIU, regardless of the number of times the specific program restarts. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + +Note! The value 3 means 3 restarts, hot, warm and finally as a last resort PIU restart. + +Note! The program escalates to a PIU restart when the number of restarts reaches the value set for this attribute. +I.e. if for example the value is set to 5, escalation to PIU restart will occur at the fifth restart. + + + + -1 + + 3 + + + + + + + + + + + + + Request to restart the program. +Only valid for MP programs. + +Note! This action does not require a transaction. + + + + + + + + The UniSaal Profile MO represent and keeps attribute values used by one or more UNI SAAL termination point MOs. + + Label free for use. + + + "" + + + + + List of reserving MOs. + + + + + + + + + + See structure UniSaalProfileData + + + + + + + + + + + + + + + + + + The MO represents an access point for a user where a UNI SAAL connection is terminated. The access point depends +on an AAL5 connection termination located on the same processor. + +UniSaalTp can only terminate on a Mp processor. + +Note! The performance monitoring counters found in NniSaalTp MO is set to zero when the Mo and its RO is created. +These counters are not reset unless there occurs a fault situation that demands a restart and recreation of the ROs. +Also note that some of these counters are reset based on other conditions. For more details please refer to the +descriptions of the performance monitoring counters in this MO. + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the UniSaalTp MO. + + + + + + disabled + + + + + The identity of the reserving MO. + + + + + + + + + Reference to a UniSaalProfile MO. + +The maxStat attribute defined in the UniSaalProfile MO is dependent on the AAL5 SDU size defined in the Aal5TpVccTp MO. See the description of the maxStat attribute in the UniSaalProfile MO. + + + + + + + + + + + Reference to an Aal5TpVccTpMo. + +Note: The Aal5 termination point must terminate on a main processor, MP. + + + + + + + + + Maximum SAAL SDU size. The attribute is dependent on the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The 'maxSduSize' may not exceed the AAL5 maximum SDU size (the lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). + +Example: If 'fromUserMaxSduSize' is set to 256 and 'toUserMaxSduSize' is set to 512 in the Aal5TpVccTp MO, the ' maxSduSize' in the UniSaalTp MO may not exceed 252. + +(i.e. maxSduSize <= the aal5MaxSduSize - 4 bytes) + +Note! When setting the value of 'maxSduSize' the 4 bytes used by the SAAL layer for the SAAL header has to be considered. + +Note! The upper limit of 2044 (2048 including the SAAL header) is due to limitations on the AAL5 layer. + + + + + + + 128 2044 + + 128 + + + + + Number of successfully sent SDUs. +Counts the number of successfully sent messages to the +application using SAAL. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of successfully received SDUs. +Counts the number of successfully received messages from + the application using SAAL. Reset when the link goes + InService or the counter "overflows". + + + + + + 0 + + + + + The accumulated time (in seconds) the signalling link has + been in service (in assured data transfer mode) since it was created. If the link is down the value 0 is returned. + + + + + + 0 + + + + + Number of all Signalling Link failures. +Is a total sum of the error counters: + - Number of protocol errors + - Number of unsuccessfully retransmissions + - Number of NoResponses + - Number of other errors + + + + + + 0 + + + + + Number of no response. This counter is increased when SSCOP (Service Specific Connection Oriented Protocol) +send an MaaError with error code P. +For details refer to ITU-T Q.2110 - B-ISDN AATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP); (7/94). +Counts the number of no responses detected the last 30 minutes. + + + + + + 0 + + + + + Number of local congestions. +This counter is increased when the sum of SAAL send and retransmission buffers are filled to more than 90%. + + + + + + 0 + + + + + Number of remote congestions. +This counter is increased when the remote side gives SAAL no credit. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of sequences data loss. +Counts the number of SD loss detected the last 30 minutes + + + + + + 0 + + + + + Number of unsolicited or inappropriate PDUs. This counter is increased when SSCOP (Service Specific Connection Oriented Protocol) +send an MaaError with error code Q. +For details refer to ITU-T Q.2110 - B-ISDN AATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP); (7/94). +Counts the number of protocol errors detected the last 30 minutes. + + + + + + 0 + + + + + Number of unsuccessful retransmissions. +Counts the number of unsuccessfully retransmissions detected the last 30 minutes. + + + + + + 0 + + + + + Number of other list element errors. This counter is increased when SSCOP (Service Specific Connection Oriented Protocol) +send an MaaError with error code Q-U. +For details refer to ITU-T Q.2110 - B-ISDN AATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP); (7/94). +Counts the number of other errors detected the last 30 minutes. + + + + + + 0 + + + + + + + This MO represents an E1 (i.e. 2 Mbit/s) physical interface in the node. The E1PhysPathTerm MO does not define which type of traffic (TDM or ATM) that the interface should support. +Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +Note! The performance monitoring counters in the E1PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + User label for free use. + + + "" + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The actual Line number on the board. + + + + + + + + 1 8 + + + + + + The identity of the reserving AtmPort MO. + + + + + + + + This attribute describes the current Loopback State of this physical path termination. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + The administrative state. + + + locked + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + + + + + + + + + Indicates what Cyclical Redundancy Check 4 Mode that is being used. + + + AUTOMATIC + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + + + + + 0 100 + + 30 + + + + + How many bad seconds in a row that causes a Degraded Signal alarm. + + + + + + 2 10 + + 7 + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The identity of the reserving Synchronization MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO represents an J1 (i.e. 1.5 Mbit/s) physical interface in the node. The J1PhysPathTerm MO does not define which type of traffic (TDM or ATM) that the interface should support. +Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +The performance monitoring counters in the J1PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + User label for free use. + + + "" + + + + + The actual Line number on the board. + + + + + + + + 1 8 + + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The administrative state. + + + locked + + + + + Supported interfaces is defined in J1Types + + + j1_G + + + + + The identity of the reserving AtmPort MO. + + + + + + + + + + Maximum allowed BER(Bit Error Rate). Degraded signal (DEG) if BER > degThreshold. The attribute gives a maximum BER of 10e-X, where X ranges from 5 to 9 (default 6) + + + + + 3 9 + + 6 + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + Performance monitoring counter for Errored Seconds, ES. + + + + + + + 0 + + + + + Performance monitoring counter for Severly Errored Seconds, SES. + + + + + + 0 + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The identity of the reserving Synchronization MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO is used to represent the point in the node where an AAL0 connection is terminated. At this point the user exchange SDUs with its peer at the remote end of the AAL0 connection. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + + + Label free for use. + + + "" + + + + + This attribute specifies on what processor the termination point resides. It could either be a board processor or main processor (MO type PlugInUnit), or a SP processor (MO type Spm). + + + + + + + + + The operational State reflects the operational state of the end points and the belonging node connections. + + + + + + + + disabled + + + + + The identity of the reserving MO. + + + + + + + + The virtual channel to which this MO is termination. + + + + + + + + + + + + + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. + +Activates VC end to end continuityCheck according to ITU.T rec I.610. + + + false + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + NOM_PM_BLKSIZE_2_10 + + + + + PM mode is set to indicate type of performance monitoring mode (i.e. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Performance monitoring counter for forwarded lost cells. + + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + + + This MO is used to represent the point in the node where an AAL5 connection is terminated. At this point the user exchanges SDUs with its peer at the remote end of the AAL5 connection. + +Note! The 'mtuSize' on the IpAtmLink MO does not include 8 bytes required for the LLC/SNAP header and this should be taken into consideration when setting the SduSize on the Aal5TpVccTp MO. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0.. + + User label for free use. + + + "" + + + + + This attribute specifies on what processor the protocol is terminated. It could either be a board processor or main processor (PlugInUnit) or a SP processor (Spm). + + + + + + + + + The virtual channel to which this MO is termination. + + + + + + + + + The operational State reflects the operational state of the end points and the belonging node connections. + + + + + + + + disabled + + + + + The maximum SDU size in number of octets received from the user (called maxIngressSduSize in the FRO domain). + +The allowed range is dependent on the processorType. +SP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +BP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +MP:LowestMaxSduSize =1, HighestMaxSduSize=2048 + + + + + + + 1 2048 + + + + + + The maximum SDU size in number of octets sent to the user (called maxEgressSduSize in the FRO domain). This attribute is controlled by the processor type. + +The allowed range is dependent on the processorType. +SP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +BP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +MP:LowestMaxSduSize =1, HighestMaxSduSize=2048 + + + + + + + 1 2048 + + + + + + The attribute is set by the action reserve from a user of Aal5TpVccTp. It could either be a Cello user like IpAtmLink/UniSaalTp or a node application. + + + + + + + + + + + + + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. Continuity check both enables generation of CC cells as well as detection of LOC + + + + false + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + + NOM_PM_BLKSIZE_2_10 + + + + + PM mode is set to indicate type of performance monitoring mode (i.e. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Performance monitoring counter for number of lost forward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM, cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + + + The AtmPort MO is used to configure a physical port for ATM traffic. +ATM can be transported accross the physical layer in three distinct and different ways: + +- Normal mode + +An AtmPort MO is created with a reference to physical layer object (any of E1PhysPathTerm, +J1PhysPathTerm, T1PhysPathTerm, E3PhysPathTerm, T3PhysPathTerm, Sts3CspeTtp, E1Ttp, T1Ttp or Vc4Ttp). +The payload of that physical layer object is used to transport the ATM traffic. + +- Fractional ATM mode + +An AtmPort MO is created with a reference to a Ds0Bundle object. The Ds0Bundle specifies +in this case the timeslots on the physical layer (any of E1PhysPathTerm,J1PhysPathTerm, +T1PhysPathTerm, T1Ttp or E1Ttp) that should be used for ATM traffic. The remaining timeslots +are not used at all. +I.e. when fractional ATM is used only one Ds0Bundle can exist as a child to a physical port MO. + +- IMA mode + +In IMA mode, a number of physical ports are grouped together to form one "virtual" physical +ATM pipe. In this mode the AtmPort MO is created with a reference to an IMAGroup MO. +Please refer to the ImaGroup MO for further details. + +Note! The performance monitoring counters in the AtmPort MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again.. + + + + + For free use. + + + "" + + + + + + + + + + + + + The operational state of the ATM port. + + + + + + disabled + + + + + The availability status of the AtmPort. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for number of transmitted ATM cells through the ATM port. + + + + + + 0 + + + + + Performance monitoring counter for number of received ATM cells through the ATM port. + + + + + + 0 + + + + + This attribute returns the ATM header, (vpi, vci, pti), of the last received unexpected cell. + + + + + + + + + Reference to the physical port, IMA Group or Ds0Bundle used by the ATM port. + +The possible MOs are: +E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E3PhysPathTerm, T3PhysPathTerm, Sts3CspeTtp, Sts1SpeTtp, Vc4Ttp, E1Ttp, T1Ttp, Ds0Bundle and ImaGroup. + + + + + + + + + + Performance monitoring counter for errored seconds with discarded cells due to protocol errors (unexpected, UNEX, events). + +I.610: With protcol errors is meant the reception of cells with either a non-standardized or a non-currently allocated header value. + + + + + + 0 + + + + + Header Error Correction. + +This attribute specifies if the AtmPort should detect and correct single bit errors or detect multiple bit errors in the ATM header. + + + + + + true + + + + + + + This MO represents an MTP3b Access Point (in a remote node). An MTP3b AP is a logical point in the MTP network at which an +MTP3b user can access the services provided by MTP3b and the MTP3b can deliver its services to the MTP3b user. + +The performance monitoring counters found in Mtp3Ap MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + + + + User label for free use. + + + "" + + + + + The routeSetId attribute points out the MTP3b Signalling Route Set (SRS) to which the Mtp3bAp MO is connected. + + + + + + + + + The serviceInd attribute (Service Indicator, SI) is used by traffic handling functions to perform message distribution. +Only SI=3 for SCCP usage and SI=12 for Q.2630.1 usage and SI=14 for GCP (H.248) usage have any meaning in this case. + +Full range of values for attribute SI: +0 = Signalling network management messages +1 = Signalling network testing & maintenance regular messages +2 = Signalling network testing & maintenance special messages* +3 = SCCP +4 = Telephone User Part (TUP) +5 = ISDN User Part (ISUP) +6 = Data User Part, call and circuit related messages +7 = Data User Part, facility registration and cancellation messages +8 = MTP Testing User Part +9 = Broadband ISDN User Part +10 = Satellite ISDN User Part +11 = Spare +12 = Q.2630.1 +13 = Spare +14 = H.248 +15 = Spare + +Note! The serviceIndicator has to be unique for each Mtp3bAp witin the same Mtp3bSrs. + + + + + + + 0 15 + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + List of reserving MOs. + + + + + + + + + + The operationalState attribute determines the operational status of the MTP3b AP . + + + + + + + + disabled + + + + + + + + + + + + + A performance management counter for number of received User Part Unavailable messages. + + + + + + + 0 + + + + + Performance management counter for number of Adjacent SP's that are not accessible via direct links. + + + + + + + 0 + + + + + + + The NniSaal Profile MO represents and keeps attribute values used by one or more NNI SAAL termination point MOs. + + Label for free use. + + + "" + + + + + List of NniSaalTps that have reserved this NniSaalProfile. + + + + + + + + + + See structure NniSaalProfileData. + + + + + + + + + + + + + + + + + + The MO represents an access point for a user where a NNI SAAL connection is terminated. The access point depends +on an AAL5 connection termination located on the same processor. + +NniSaalTp can only terminate on a Mp processor. + +Note! The performance monitoring counters found in NniSaalTp MO is set to zero when the Mo and its RO is created. +These counters are not reset unless there occurs a fault situation that demands a restart and recreation of the ROs. +Also note that some of these counters are reset based on other conditions. For more details please refer to the +descriptions of the performance monitoring counters in this MO. + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the NniSaalTp MO. + + + + + + disabled + + + + + The reserving MO. + + + + + + + + Reference to a NniSaalProfile MO. + +The maxStat attribute defined in the NniSaalProfile MO is controlled by the AAL5 SDU size defined in the Aal5TpVccTp MO. See the description of the maxStat attribute in the NniSaalProfile MO. + +Note! The consistency check of the attributes in the two MOs mentioned above could not be performed until the NniSaalTp MO was created since there is no direct relation between the objects. It is therefore the responsibility of NniSaalTp to verify the consistency. + + + + + + + + + Reference to a Aal5TpVccTp MO. + +Note: The Aal5 termination point must terminate on a main processor, MP. + + + + + + + + + Maximum SAAL SDU size. The attribute is dependent on the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The 'maxSduSize' may not exceed the AAL5 maximum SDU size (the lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). + +Example: If 'fromUserMaxSduSize' is set to 256 and 'toUserMaxSduSize' is set to 512 in the Aal5TpVccTp MO, the ' maxSduSize' in the NniSaalTp MO may not exceed 252. + +(i.e. maxSduSize <= the aal5MaxSduSize - 4 bytes) + +Note! When setting the value of 'maxSduSize' the 4 bytes used by the SAAL layer for the SAAL header has to be considered. + +Note! The upper limit of 2044 (2048 including the SAAL header) is due to limitations on the AAL5 layer. + + + + + + 128 2044 + + 128 + + + + + Number of successfully sent SDUs. +Counts the number of successfully sent messages to the +application using SAAL. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of successfully received SDUs. +Counts the number of successfully received messages from + the application using SAAL. Reset when the link goes + InService or the counter "overflows". + + + + + + 0 + + + + + The accumulated time (in seconds) the signalling link has + been in service (in assured data transfer mode) since it was created. If the link is down the value 0 is returned. + + + + + + 0 + + + + + Number of all Signalling Link failures. +Is a total sum of the error counters: + - Number of protocol errors + - Number of unsuccessfully retransmissions + - Number of NoResponses + - Number of other errors + + + + + + 0 + + + + + Number of no response. +Counts the number of no responses detected the last 30 minutes. + + + + + + 0 + + + + + Number of local congestions. +This counter is increased when the sum of SAAL send and retransmission buffers are filled to more than the congestionOnSet attribute is configured to.. + + + + + + 0 + + + + + Number of remote congestions. +This counter is increased when the remote side gives SAAL no credit. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of alignment or proving failures. This counter is +increased when "alignment not successful". +The counter is reset when the link is created or the counter "overflows". + + + + + + 0 + + + + + Number of sequences data loss. +Counts the number of SD loss detected the last 30 minutes + + + + + + 0 + + + + + Number of unsolicited or inappropriate PDUs. +Counts the number of protocol errors detected the last 30 minutes. + + + + + + 0 + + + + + Number of unsuccessful retransmissions. +Counts the number of unsuccessfully retransmissions detected the last 30 minutes. + + + + + + 0 + + + + + Number of other list element errors. +Counts the number of other errors detected the last 30 minutes. + + + + + + 0 + + + + + + + This MO specifies traffic and QoS parameters for virtual channel connections. + +The attributes can only be set in certain combinations: + +CBR: +ingressAtmQos /egressAtmQos: +1, 2 + +ingressAtmPcr /egressAtmPcr: +mandatory (must be specified) + +ingressAtmMcr /egressAtmMcr: +optional (not used, any value submitted will be ignored) + +UBR+: +ingressAtmQos /egressAtmQos: +3 + +ingressAtmPcr /egressAtmPcr: +optional (if shaping is used the desired rate is specified, 0 means no shaping) + +ingressAtmMcr /egressAtmMcr: +mandatory (must be specified) + +UBR: +ingressAtmQos /egressAtmQos: +4 + +ingressAtmPcr /egressAtmPcr: +optional (not used, any value submitted will be ignored) + +ingressAtmMcr /egressAtmMcr: +optional (not used, any value submitted will be ignored) + +Note that the VP sub layer only supports ServiceCategory = CBR and QoS = 1. + +Note! The performance monitoring counters in the AtmTrafficDescriptor MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + This MO's user label. + + + "" + + + + + Ingress ATM Peak cell rate (cells/s). + +Only positive values are allowed. This attribute is only mandatory when serviceCategory is CBR or UBR_PLUS. + +Note! When 'serviceCategory' is set to UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! When 'serviceCategory' is set to UBR+ the value 0 (zero) means that shaping is not used. A value larger than the minimum desired cell rate enables shaping to the rate specified. + + + + + 0 + + + + + Ingress ATM quality of service. + +This attribute can be set to Class 1 and 2 if attribute serviceCategory is set to CBR. + +This attribute can be set to Class 3 if attribute serviceCategory is set to UBR+. + +This attribute can be set to Class 4 if attribute serviceCategory is set to UBR. + + + + + + + + + + Egress ATM Peak cell rate (cells/s). + +Only positive values allowed. + +This attribute is only mandatory when serviceCategory is CBR or UBR_PLUS. + +Note! When 'serviceCategory' is set to UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! When 'serviceCategory' is set to UBR+ the value 0 (zero) means that shaping is not used. A value larger than the minimum desired cell rate enables shaping to the rate specified. + + + + + 0 + + + + + Egress ATM quality of service. + +This attribute can be set to Class 1 and 2 if attribute serviceCategory is set to CBR. + +This attribute can be set to Class 3 if attribute serviceCategory is set to UBR+. + +This attribute can be set to Class 4 if attribute serviceCategory is set to UBR. + + + + + + + + + + + Sequence of Users that are using this AtmTrafficDescriptor. + + + + + + + + + + + + Egress ATM minimum desired cell rate. + +Only positive values allowed. The attribute is only mandatory when serviceCategory is UBR+. + +Note! When 'serviceCategory' is set to CBR or UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! This attribute cannot have a value larger than for 'egressAtmPcr'. + + + + + 0 + + + + + Ingress minimum desired cell rate (cells/s). + +Only positive vaues allowed. This attribute is mandatory only when serviceCategory is UBR+. + +Note! When 'serviceCategory' is set to CBR or UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! This attribute cannot have a value larger than for 'ingressAtmPcr'. + + + + + 0 + + + + + The service category. + + + + + + + + + + + + This MO represents/models a MTP3b Signalling Route Set. + +The performance monitoring counters found in Mtp3Srs MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + + + + + + + + + + User label for free use. + + + "" + + + + + The operational state of the Mtp3bSrs MO. + +There are two possible states for the operationalState attribute: + +- enabled, the MO is partly or fully operational. +- disabled, the MO is not operational. + + + + + + disabled + + + + + The attribute is set by the local action Reserve. + + + + + + + + + + + + This flag indicates Whether automatic rerouting is performed(true) or not(false), between IP and ATM/TDM +routes when configuration is made. If set to 'false', it has to be done manually, for ex. by management actions(orders). + +Note! The attribute 'autoReroute' will always be set to 'false' regardless of value submitted. This attribute is to be removed in coming releases. + + + + + + + + + The destPointCode attribute (destination point code, DPC) represents the point code of this Mtp3b SRS MO. +The Destination Point Code in a Route Set has to be unique within each Signaling Point. + +Note! The format of destPointCode must correspond to the signallingPointCode format in the Mtp3bSp, i.e. ITU, ANSI, TTC or China. + + + + + + + 1 16777215 + + + + + + There are two possible states for the congestedLevel attribute: + +- notCongested, no change in congestion level. +- congested, change in congestion level has occurred. + + + + + + notCongested + + + + + Performance management counter for number of messages discarded from broadband to narrowband. + + + + + + 0 + + + + + Performance monitoring counter for number of received Transfer Control (TFC) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of received Transfer Prohibited (TFP) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of received Transfer Allowed (TFA) messages. + + + + + + + 0 + + + + + The route set test is only available for the Japanese Mtp3b, TTC. + +See JT-Q.707 for details. + +The test selects a route in the route set and tests it. + +Possible return codes are: + +0 : successful test +48 : unsuccessful test + +Note! This action does not require a transaction. + + + + + + The route set test is only available for the Japanese Mtp3b, TTC. + +See JT-Q.707 for details. + +The test tests the specified route. + +Possible return codes are: + +0 : successful test +48 : unsuccessful test + +Note! This action does not require a transaction. + + + + + + + + + + + + + + This MO is used to represent a plug-in-unit, that is a board inserted in a slot in a subrack. + +Note! Before deleting the PlugInUnit MO, administrativeState must be set to locked. + + + + + + + + + + A free tag that a user can associated to the this managed object. The value has no relevance for the managed system. + + + "" + + + + + The administrative state of the PlugInUnit. + +The possibility to rollback the setting of this attribute is limited. + + + locked + + + + + The operational state is set to 'enabled' when the plug-in-unit has loaded and started its 'Basic' load module. + + + + + disabled + + + + + This attribute describes the product type and is always set to the value "HW". + + + + + "HW" + + + + + A reference to an available PiuType at create of a PIU. + + + + + + + + + + Indicates which restart group the plug-in unit belongs to. +Such a group consists of a number of plug-in units where at least one must be enabled (working) or performing recovery. When all plug-in units in a group are out of function, the node is restarted. + +Must have a positive value. + +Zero indicates no group. + + + + 0 65536 + + 0 + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. It is a bit mapped CORBA long, where one or more of the bits may be set. If none of the bits are set then the availability status is considered to be undefined. + + + + + + NO_STATUS + + + + + List of managed objects depending on PlugInUnit + + + + + + + + + + The measurement is done over 100 ms, and returns the sum of load on processes up to, and including process priority 23. The sum is expressed in % + +Supported on MP, BP and SP boards. + +In case of SP boards the returned processor load is the load of the BP. + + + + + + + 0 100 + + 0 + + + + + The number of automatic (do not require intervention from a human operator) sequential restarts that are allowed for a PIU. When this number of automatic restarts has been exceeded, the automatic restarting halts and the PIU is faulty marked. + +The time limit between two restarts is 5 minutes. This means that if the time between two restarts +is less then 5 minutes the restarts are counted, otherwise the restart counter is reset. + +For example, 3 means 3 restarts with time limit < 5 minutes are accepted but when the 4:th occurs within 5 minutes the board is considered faulty and an alarm is generated. + + + RESTARTS_WITH_WARM + + + + + +Note! The restartCause can have the following values: +1 = restart error +2 = restart upgrade + +Note! The restartCause piuRestartUpgrade overrides the restartRank value and gives mainly restartRank=warm (or restartRank=refresh in some upgrade situations. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + This MO represents the SS7 Signalling Link Set as defined in Recommendation Q.704 Ver. 3, April 28 1992 (ITU) T1.111-1996 (ANSI), JT-Q.704 Ver. 3, April 28 1992 (TTC) or GF001-9001 1990 (China). + +It provides information about a set of signalling links between an OPC/Adjacent PC pair. A link set is constructed from between 1 to16 Signalling Links (for China, Itu, Ttc and the ANSI standard), all of which have the same two end points (signalling points) as the Signalling Link Set. A Signalling LInk Set may be part of many routes. + + + + + + + + + + Use label for free use. + + + "" + + + + + The operational state of the MTP3B SLS. + +The operability of the MTP3B SLS is described by the operationalState attribute which has two possible values: + +- Enabled: The MTP3B SLS is partly or fully operable and available for use. At least one of the belonging links (SL) is enabled. +- Disabled: The MTP3B SLS is totally inoperable and unable to provide service to the user. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The usageState reflects the usage state of the links in the link set. There are three possible values: + +- Active: At least one of the belonging SLs of the SLS is Active and no link is Busy. +- Busy: If one of the belonging links is Busy. +- Idle: All SLs of the SLS are Unavailable. + + + + + + + + IDLE + + + + + The periodicLinkTestFlag indicates if periodic sending of SLTM/SLTA messages are used or not. The SLTM message will be sent on every link which is "aligned" at an interval of (SLTM timer). The answer, SLTA is supposed to arrive within (SLTA timer). If this doesnt happen, or if the received SLTA doesnt match the sent SLTM a second SLTM will be sent. If this SLTM also fail then the link will be considered 'out-of-service' and a restart of that link will begin. + +ANSI: true is default. +ITU: true is default. +China: true is default. +TTC: false is default. + +Note that TTC does not use this feature. + + + + + + true + + + + + The mtp3bSrsId attribute points out the corresponding MTP3b Signalling Route Set MO (adjacentDPC). + + + + + + + + + List of reserving MOs. + + + + + + + + + + This action deactivates a link set, which means the containing signalling links are taken out of service. + +Note! This action requires a transaction. + + + + + + + + A linkset containing signalling links which are all out of service, is called a deactivated linkset. In order to start up the signalling links and get them into service, there is an Activate Link Set action, or rather, there are two similar actions for activation of a link set. + +If the action fails to activate a link the ActivationFailed exception is raised. + +Note! This action requires a transaction. + + + + + + + + This action activates the signalling link with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + + + + + This MO represents a MTP3b Signalling Route. A Signalling Route is used to convey MTP3b User messages from a origin SP to a destination SP (Signalling Point). This MO is multiple instansiated and is contained in the MO MTP3b Signalling Route Set. A Signalling Route is from a network point of view the sequence of link sets from a originating signalling point to a destination signalling point. + +Note! At least one signalling route in the signalling route set must have priority = 1. +If lower priorities are defined the next level must be priority=2. (e.g. routes with priority =1 and =3 in a route set will not work). + +Note! Signalling Routes belonging to the same route set with the same priority must have the same type of bearer (Broad Band or Narrow Band). + + + + + + + + + + User label for free use. + + + "" + + + + + The MTP3b Signalling Link Set (MTP3bSls) or M3uAssociation to which the MTP3bSr MO is connected. + + + + + + + + + + Operational state notification.There are two possible states for the operationalState attribute: +- enabled, possible to perform operations on the MTP3b SR. +- disabled, not possible to perform operations on the MTP3b SR. + + + + + + disabled + + + + + There are three possible states for the usageState attribute: + +-active, route is active. +-busy, route is congested. +-idle, route not in use. + +(idle=0, active=1, busy=2) + + + + + + + IDLE + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The priority of the alternative route. The traffic is directed to the highest priority route(s) available in the route set. If more than one route has the same priority within a route set then loadsharing is permitted between these routes. +The value 1 is considered as the highest priority. + + + + + 1 5 + + + + + + The type of the route. + + + + + TDM_ATM + + + + + + + + + NOT_BLOCKED + + + + + The number of seconds (accumulated) route unavailable. + + + + + + 0 + + + + + This action blocks the Signaling Route. + +Note! This action requires a transaction. + + + + + + This action deblocks the Signaling Route. + +Note! This action requires antransaction. + + + + + + + + The IP System MO constitutes the top structure level for IP related MOs in a Cello node. + +The IpSystem MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, IpSystem=1. + + + + An operator defined label. + + + "" + + + + + + + + + + + + + Ping - used to call a host or router to find out if it is present in the network. The following input parameter is used by the Ping action: +The domain name or IP address to the host that shall be called. + +The following parameter is returned: +Ping result: 'IP address/domain name' - is alive or no answer. + +Note! This action requires a transaction. + + + + + + + + + + + + + Trace route - used to get information about the route through the IP network that is used for a destination with a specific IP address. + +The following input parameter is used by the trace route action: +The domain name or IP address to a host that shall be trace-routed. + +The following parameter is returned: +Trace result - list of IP addresses/domain names or path not found. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This MO represents an Internet Protocol over ATM link. LLC/SNAP encapsulated packets over Atm Adaptation Layer 5, AAL5, ATM PVCs are used. + +Note: The performance monitoring counters in the IpAtmLink MO has a "Wrap-around time" of approximately 2 hours. + +Note! When setting the 'fromUserMaxSduSize' and 'toUserMaxSduSize' on the Aal5TpVccTp MO the defined SduSize should be 8 bytes larger then the 'mtuSize' on the IpAtmLink. + +Note! Only Aal5TpVccTp's that terminates on an MP (Main Processor) may be used when setting up IpAtmLink's. + + + + + + + + + + The User Label attribute gives the operator the possibility to label the links. + + + + "" + + + + + The operational state of the IP over ATM link is dependent of the operational states of the underlying AAL5 termination points that are used to transport IP datagrams. If at least one operational AAL5 termination point (MO: AAL5 TP VCC TP) exists, the operational state of the IP over ATM Link is set to "ENABLED" + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. It is a bit mapped CORBA long, where one or more of the bits may be set. If none of the bits are set then the availability status is considered to be undefined. + + + + + + NO_STATUS + + + + + If set, indicates that this IpAtmLink is reserved by the OspfInterface represented by this attribute. + + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + + + + + The attribute subnetMask states the subnet mask of the IP over ATM link (point to point link). + +The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. +For a point to point link, the subnetmask 255.255.255.252 is very likely. + +Note! The subnet mask has to be contiguos. That is, it has the LSB's set to 0 (zero). + +Example: + +255.255.255.X + +Contiguous subnet mask: +11111111.11111111.11111111.11111110 (X = 254) +11111111.11111111.11111111.11111100 (X = 252) + +Not-contiguous subnet mask: +11111111.11111111.11111111.11111010 (X = 250) + + + + + + + + + + The attribute mtuSize states the maximum IP datagram size that may be sent on the IP over ATM link in bytes, without fragmentation. Recommended MTU size is 1500 bytes to prevent IP fragmentation. + +Note that the size of the IP datagram does not include the 8 Bytes added for the LLC/SNAP header before putting the IP datagram in AAL5 SDU. + + + + + 576 2040 + + 1500 + + + + + The attribute metric states the metric "cost" of the IP over ATM link. The metric value is calculated as 10^8 /link bit speed. + +For example: +Metric for 10 Mbps Ethernet = 10^8/10^7 = 10 +Metric for 100 Mbps Ethernet = 10^8/10^8 = 1 + + + + 1 32767 + + 1 + + + + + This attribute indicates whether InvATMARP monitor is turned on or off. + + + true + + + + + The interval between sending monitor packets. +Unit is seconds. + + + + 1 60 + + 10 + + + + + The number of retries when sending monitor packets. + + + + 1 255 + + 10 + + + + + The interface name. + + + + + + + "" + + + + + The selection mode for the Aal5TpVccTp's used by the IpAtmLink MO. Determines how the IpAtmLink MO selects the Aal5 termination points used. + +In case 'NO_PREFERENCE', 'LOCAL_MP_SELECT_VCC_AT_LINK_UP', LOCAL_MP_PEER_SELECTION_VCC' or 'LOCAL_MP_ACTIVE_RESELECTION' is selected the IpAtmLink MO will prefer Aal5TpVccTp on local MP (i.e. Aal5TpVccTp MOs executing on the same MP as the IpAtmLink), but other Aal5TpVccTp will be accepted if needed. + +In case 'ONLY_LOCAL_MP' is selected, the ipAtmLink (Inet Link) will consider Aal5TpVccTp residing on other MPs as a malfunction and discard the usage of them. No InvArp sending will be performed on them and all incomming trafic on them will be discarded. If no local Aal5TpVccTp exists the operational state of the link will be changed to disabled. + + + + + NO_PREFERENCE + + + + + References to MOs of type Aal5TpVccTp representing the underlying AAL5 termination points (of a AAL5 PVC:s) for the IP over Atm link. + +The operator gives a list of relative distinguished names of the Aal5TpVccTp MO's to be used by the IP over ATM link. +An Aal5TpVccTp MO may only be specified once in the list. + +To change in the set of Aal5TpVccTp MO's related to the IP over ATM link the link has to be deleted and then created with the desired set of AAL5 TP. + +Note! Only Aal5TpVccTp's that terminates on an MP (Main Processor) may be used when setting up IpAtmLink's. + + + + + + + 4 + + + + + Performance monitoring counter for the number of input unicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of out unicast packets deliverred to higher layer + + + + + + 0 + + + + + Performance monitoring counter for the number of output broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to any error. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of outbound packets discarded due to resource limitations. + + + + + + 0 + + + + + This action sets the IP address and the subnet mask. + +The changing of the IP address with the operation assignIpAddress, it might cause an interruption of the communication between the node and the network management tool. If an incorrect or erroneous IP address is configured, the communication with the node might be lost until the node is restarted or the IP address is changed to the correct value. + +Note! This action requires a transaction. + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + + + + The Ethernet Link MO represents the Internet Protocol over Ethernet link. There is only one Ethernet link MO per Cello node. + +The changing of the IP address with operation assignIpAddress might cause interruption of the communication if the network management tool is connected via the ethernet link. + +Note: The EthernetLink MO can not be deleted! + +Note: The performance monitoring counters in the EthernetLink MO has a "Wrap-around time" of approximately 2 hours. + + + The User Label attribute gives the operator the possibility to label the links. + + + + + "" + + + + + The attribute ipAddress states the IP address of the Ethernet link, it is also the IP address for the O&M host.. + +The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. +It must not be a broadcast or multicast address. + + + + + + + + + + + The attribute subnetMask states the subnet mask of the Ethernet link. + +The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + +Note! The subnet mask has to contiguos. That is, it has the LSB set to 0 (zero). + +Example: + +255.255.255.X + +Contiguous subnet mask: +11111111.11111111.11111111.11111110 (X = 254) +11111111.11111111.11111111.11111100 (X = 252) + +Not-contiguous subnet mask: +11111111.11111111.11111111.11111010 (X = 250) + + + + + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + The IP layer expects the Ethernet link to have an MTU size (maximum Ethernet frame size without fragmentization) of 1500 bytes. + +The value is always the default value. + + + + + + 1500 + + + + + The attribute metric states the metric of the Ethernet link. The metric value is calculated as 10^8/link bit speed. + +For example: +Metric for 10 Mbps Ethernet = 10^8/10^7 = 10 +Metric for 100 Mbps Ethernet = 10^8/10^8 = 1 + + + + 1 32767 + + 1 + + + + + The operational state of the Ethernet link is dependent of the operational states of the underlying MAU:s that represents the Ethernet transceiver function. If at least one operational MAU exists, the operational state of the Ethernet Link is set to "ENABLED" + + + + + + disabled + + + + + The interface name. + + + + + "" + + + + + The mac address is persistently stored in flash prom on the MP where the IP stack resides. It is stored there at manufacturing. + + + + + + + 6 + + + + + + If set, indicates that this EthernetLink is reserved by the OspfInterface MAO represented by this attribute. + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + Performance monitoring counter for the number of input unicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of out unicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to any error. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of output broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of outbound packets discarded due to resource limitations. + + + + + + 0 + + + + + This action sets the IP address and the subnet mask. + +The changing of the IP address with the operation assignIpAddress, +causes an interruption of the communication between the node and +the network management tool. If an incorrect or erroneous IP address +is configured, the communication with the node might be lost until +the node is restarted or the IP address is changed to the correct +value. + +Note! This action requires a transaction. + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + + + + This MO holds the IP routing table. + +The IpRoutingTable MO is automatically created when the Ip MO is created. +The IpRoutingTable MO can not be created manually. +The IpRoutingTable MO can not be deleted. + + + + Label free for use. + + + "" + + + + + This attribute gives the indexes for the static routes that are possible to delete by the operator. + + + + + + 0 + + + + + + + + + + + + + + Used to add a new static route to the routing table. It can be +indicated if the static route should be redistributed by OSPF. +When adding a static route with an ipaddress, which is not a subnet +address, the ipaddress is recalculated to the corresponding subnet +address, based on the ipaddress and the subnet mask. So when looking +for this route using the action 'getRoutingTableEntry' it is in fact +the recalculated ipaddress, that is displayed and not the ip address +entered with addStaticRoute. This is an automatic correction. + +Note! If an attempt is made to add a static route with hopIpAddress starting with 0.0 an exception will be thrown. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + List routes actions is used to list all routes in the routing table. It requires no input parameters. + +The output is a formatted string, indicating the number of routes in the table followed by route information for each of these routes. + +The number of routes in the table is found at the very start of the returned string. Immediately following this is the information on each route in the list in turn. The route information for each route begins with a new line character ("\n") and is followed by the following data items (in the order written below), which are separated from each other by a SPACE character: + +- Destination IP address +- Destination Network mask +- Next hop IP address/Interface index of connected networks in dot-decimal format +- Route metric +- Route type +- Interface name +- Redistribute +- Active + +Note that the next hop ipaddress is not an ipaddress per se, it is the subnet on wich the host/router to route to resides. + +Below is an example list of routes that could be returned from this action: + +"\n123.123.123.123 234.234.234.234 0.0.0.7 10 13 LE0 FALSE active\n122.122.122.122 233.233.233.233 0.0.0.6 2 8 LE0 TRUE active\n132.132.132.132 243.243.243.243. 0.0.0.7 9 13 LE0 TRUE inactive" + +In this case, there are three routes in the routing table. The first route has destination IP address of 123.123.123.123, the second route has it set to 122.122.122.122, while finally the third has it set to 132.132.132.132. + +NOTE that the route types can be of the following types: + +INET_RTPROTO_OTHER 1 +INET_RTPROTO_LOCAL 2 +INET_RTPROTO_NETMGMT 3 +INET_RTPROTO_ICMP 4 +INET_RTPROTO_OSPF 13 + +The types listed above also denote the origin of the routing entry. + +Note! This action does not require a transaction. + + + + + + + Returns a RoutingTableEntry according to the specified index. + +Should be used with action 'numberOfRoutes' within a transaction. To refresh the routing table stored in the MO, invoke the action 'numberOfRoutes'. + +Precondition: 0 <= index <= numberOfRoutes() - 1 + +Note! This action does not require a transaction. + + + + + + + + + + + + + Returns the number of entries in the routing table. + +Each time this action is invoked, the MO retrieves routing table information from the resource layer and then builds a new array of RoutingTable structs to store this information. + +This action along with getRoutingTableEntry(), which allows one to iterate through the array stored in the MO, should be used together with a transaction. + + + + + + Removes the RoutingTableEntry submitted as a parameter from the Routing Table, if it is found in the table. + +Note that only static roues, previously added, can be deleted with this action. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + The Ip MO represents the IP protocol layer with IP forwarding functionality. + +Note: The performance monitoring counters in the Ip MO has a "Wrap-around time" of approximately 2 hours. + + + + + + + + + + + + User label for free use. + + + "" + + + + + The workingMode of the IP MO controls if the IP stack in the node will work as a combined host/router (routerMode) or only as a host (hostMode). + + + + + + + + The retransmission interval. The units are seconds. +Must be a value > 0. + + + 4 + + + + + The number of retransmissions. +Must be a value > 0. + + + 5 + + + + + The Domain Name Server IP address. + +The IP address must be a Unicast IP address. + + + + "127.0.0.1" + + + + + Holds information about how the DNS client wants the DNS server do the search for the IP address in the network . It can be either Recursive search or Non-recursive search. + + + true + + + + + Holds information about whether to use subsets of the fully qualified domain name to reach the simple domain name. It can be either Use subsets of domain name or Not use subsets of domain name. + + + true + + + + + Holds information about whether the default domain name is present. It can be Present or Not present. + + + + + false + + + + + Contains default domain name. +If 'isDefDomainName' is set to 'true' the domain name found in this attribute is used by the DNS resolver and there is no need to submit the complete domain name. If the domain name is for example 'ws5741.uab.ericsson.se' then the default domain name would be '.uab.ericsson.se'. If 'isDefDomainName' is set to true the there is no need for using '.uab.ericsson.se'. If set to false then the complete domain name has to be used. +A valid domain name consists of 1 or more labels separated by dots ("."). +Valid characters for a label shall be limited to letters 'a' - 'z', 'A' - 'Z', digits '0' - '9', the character '-' ("dash"). +Character case shall be preserved. Labels shall start with a letter. Total length of a label shall not exceed 255 characters. + +Note! The first and last character in the domain name has to be within the following alphabet: letters 'a' - 'z', 'A' - 'Z' and digits '0' - '9'. For more information refer to RFC 952 and 1101. + + + "" + + + + + The operational state of the IP MO is ENABLED if at least one link is operational. + +Shows whether the MO is OK (enabled) or failed (disabled). The values are set by the system. + + + + + + disabled + + + + + Represents the number of interfaces (Ethernet and IP over +ATM links) which has registered to the IP MO. + + + + + + + 0 + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + If set, indicates that this Ip is reserved by the Ospf represented by this attribute. + + + + + + + + Indicates if the hosts file should be used or not. The hostFile is used by the resolver and +chosen as a source of information before querying a DNS server. + +true - use the host file. +false - do not use the host file. + + + true + + + + + The DiffServ CodePoint. +The code point values are used by DiffServ enabled hosts and router to identify different service levels. +When set, the DSCPs are mapped to PHBs (Per Hop Behaviours) by forwarding devices along the path +between the source and destination. PHBs dictates how each packet will be handled i.e. what type of +service that is applied to the packet when it is forwarded. + +Note! Only traffic originated from the node is tagged with the dscp value. The Cello router does not implement functionality for handling different service levels when routing IP traffic. + + + + 0 63 + + 0 + + + + + Indicates if ICMP redirects is sent out or not. + + + true + + + + + Enable/Disable generation of UDP checksum. +0 = disabled +1 = enabled + +The UDP checksum is used for verifying that the UDP header has not been damaged during transmit. + + + 1 + + + + + The time that elapses before a connection (TCP) attempt times out. + +Unit is seconds. + + + 75 + + + + + The maximum number of retransmission attempts before a TCP connection is dropped. +The default value is 10 attempts, which is around 5 minutes. +Setting this attribute value to -1 means infinity, and TCP will never give up in trying +to establish a connection. + + + + -1 + + 10 + + + + + Performance monitoring counter for total number of datagrams received. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams discarded due to format error. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams discarded due to misdelivery. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams forwarded. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams dascarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams discarded due to lack of resources. + + + + + + 0 + + + + + Performance monitoring counter for the number of fragments received needing reassembly. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams successfully reassembled. + + + + + + 0 + + + + + + + This MO represents an SCCP EntitySet which is made of one SCCP Entity. An SCCP Entity is a local MTP-SAP + a DPC + possibly an SSN, i.e an SCCP EntitySet identifies the set of access points that result from a global title translation. An SCCP EntitySet may also be made of two SCCP Entities of the same type (if an SSN is present in one SCCP Entity, then an SSN shall also be present in the other). In the latter case the two SCCP entities may be considered either as a "primary" SCCP Entity and a "backup" SCCP Entity (dupli-dominant mode) or may be interpreted as two equal SCCP entities that can be used for outgoing loadsharing purpose. In this implementation they can only be considered as "primary" and "backup".The Routing Indicator (RI) in the Called Party Address is normally not set by the SCCP for outgoing messages and should therefore be set by the user. This means that if the user has set "Route on SSN" this will be the case after the GTT also even if the set consist of MTP-3b Access Points. However, if the set consists of SCCP Access Points the RI is implicitly set to "Route on SSN" by SCCP. + +DPC Destination Point Code +GTT Global Title Translation +MTP Message Transfer Part +SAP Signalling Access Point +SSN Subsystem Number + +Note: the SccpEntitySet MO depends either on MAOs of type SccpApLocal OR SccpApRemote, not on a mixture of these MAO types. + + For free use. + + + "" + + + + + The Entity Set routeId is an array of maximum two instances of Sccp ApLocal MO's OR two instances of SccpApRemote MO's OR two instances of Mtp3bAp MO's OR one instance of SccpSP MO. + + + + + + + 2 + + + + + The sharingMode attribute controls the distribution of SCCP traffic over the entities (Access Points) in the set. + + + + + + + + + + The new sub system number attribute is only valid if the Mtp3b Access Points are used in the set. In that case the SSN attribute allows to optionally set the subsystem number in the Called Party Address as a result of a Global Title Translation. If the set consists of SCCP Access Points the subsystem number in the Called Party Address is always implicitly set to the SCCP Access Point SAP (SSN) as a result of a Global Title Translation. +This attribute is controlled by the type of AP(s) that the EntitySet refers to. + +The default value 0 means no new subsystem number. + + + + + + 0 254 + + 0 + + + + + The New Global Title attribute allows to optionally replace the global title in the Called Party Address as a result of a Global Title Translation (GTT). If the GT resulting from a GTT is different from the GT previously included in the Called Party Address, the newly produced GT replaces the existing one. The gtIndicator attribute is read-only and is derived from the combination of Nature Of Address, the Translation Type and Numbering Plan used. + +Default value is considered as no new Global Title. + + + + + + + + Holds a list of the reserving MO's. + + + + + + + + + + + + + + + + + + + + The SCCP Global Title MO represents a combination of a global title translator and a global title rule. If no Destination Point Code (DPC) is present in the Called Party Address, a Global Title (GT) is needed. Then a global title must be present in the Called Party Address, otherwise a routing error occurs. A global title translator is selected by SCCP based on a combination of the values of the Nature Of Address (NA), the translation type (TT), and the Numbering Plan (NP) if available, in this MO matched with the same information in the Called Party Address provided by an SCCP user. A global title translation rule is selected by SCCP by matching the Global Title Address Information and possibly the Encoding Scheme in this MO, with the same information in the Called Party Address provided by an SCCP user. A global title translation rule points to the SCCP Entity Set resulting from the global title translation (GTT). +The translation results in a DPC and possibly a new Sub System Number (SSN) or GT or both (decided by the SCCP Entity Set it refers to). If the GT and/or SSN resulting from a GTT is different from the GT and/or SSN previously included in the Called Party Address, the newly produced GT and/or SSN replaces the existing one. + +GT - Global Title +SCCP - Signalling Connection Control Part +SSN - Sub System Number +DPC - Destination Point Code +TT - Translation Type +GTT - Global Title Translation + + For free use. + + + "" + + + + + Global title indicator for China, ITU, TTC and ANSI. + + + + + + + + + + + + + Indicates number type, i.e. national or international number. + + + + + + + + + + + Indicates which numbering plan that is used. + + + + + + UNKNOWN + + + + + Used to direct the message to the appropriate Global Title translation function. + + + + + + + 0 254 + + + + + + Digit string of 1-37 digits, where each digit is 0-9, and "B", "C". "B" and "C" are for Code 11 and Code 12. +The addressInformation may also contain wild card symbols: "*" or "?". Wild cards are only allowed for defining Global Title Translations, they are not allowed for specifying SCCP SAPs (built with SPC and Global Title or SPC + SSN + Global Title). + + + + + + + 1 37 + + + + + + Indicates if the number of address signals are an odd or even number. + + + + + + + UNKNOWN + + + + + The sccpEntitySetId attribute points out the corresponding SccpEntitySet MO. + +Note! This attribute is only optional if this MO is used by Policing. In all other cases it has to be set. + + + + + + + + + + + + + + + List of reserving MOs. + + + + + + + + + + + + This MO is used to represent an AAL2 Path, i.e. an ATM VC connection that carries multiplexed AAL2 links. + +VCC TP - Virtual Channel Connection Termination Point. + +The total number of Aal2PathVccTps associated to an Aal2Ap, by connecting them to Aal2PathDistributionUnits under that Aal2Ap, must not exceed 632. + +The total number of Aal2PathVccTps associated to a ReliableProgramUniter, by connecting them to Aal2PathDistributionUnits associated to the ReliableProgramUniter, must not exceed 280. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + + + + + + + + + + For free use. + + + "" + + + + + Reference to the VclTp to be used by this Aal2PathVccTp. + + + + + + + + + The administrative state of the termination point. + + + unlocked + + + + + Operational state of the termination point. + + + + + + disabled + + + + + The identity of the reserving Aal2PathDistribution MO. + + + + + + + + + The availability status of Aal2PathVccTp. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. + +Activates VC end to end continuityCheck according to ITU.T rec I.610. + + + false + + + + + PM mode is set to indicate type of performance monitoring mode (ie. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + NOM_PM_BLKSIZE_2_10 + + + + + Timer that assures that CPS-packets with one or more octets already packed in the ATM cell wait at most the duration of timerCu before being scheduled for transmission. + +Units for timerCu is 10 to the power of -4 seconds. This value can be set in steps of 10 to the power of -4. + + + + + + 1 100 + + 10 + + + + + This attribute is used to identify the path in the Q.2630.1 protocol. + +The pathId value must be unique within all Aal2PathDistributionUnits under the same Aal2Ap + +All integers > 0 are allowed (not 0). + +The Aal2PathId is used by the Aal2 connection control function in two Aal2 nodes to uniquely identify an AAL2 path between the two nodes. This means that the value of the attribute Aal2PathId for an Aal2 path must be the same in each of the two nodes. + +In order to set this attribute, the Aal2PathVccTp may not be reserved. If an attempt is made, an "IsReservedCanNotSetPathId" exception is thrown. + +Note! Setting of this attribute will not have any effect until 'actionAddPath' in Aal2PathDistributionUnit MO' is called adding this MO to the list of Aal2PathVccTp MO's. + + + + + 1 2147483647 + + + + + + This attribute indicates whether this Aal2 Path VCC Termination Point is considered the owner of the Aal2 Path in order to decide channel selection procedure in the Q.2630.1 protocol. + +Note! In order to set this attribute, the Aal2PathVccTp may not be reserved. If an attempt is made, an "IsReservedCanNotSetPathId" exception is thrown. + +Note! The administrativeState has to be LOCKED when this attribute is set, if not the "IsUnlockedCanNotSetPathOwner" exception is thrown. + +Note! Setting of this attribute will not have any effect until 'actionAddPath' in Aal2PathDistributionUnit MO' is called adding this MO to the list of Aal2PathVccTp MO's. + + + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + The identity of the QosProfile used by the Aal2PathVccTp. + + + + + + + This attribute specifies which QoSClass that can be supported by this Aal2Path. + + + + CLASS_A_B_C_D + + + + + Performance monitoring counter for forwarded lost cells. + + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + + + This MO represents a AAL2 routing case which points out an AAL2 access point. + + + + + + + + + + For free use + + + "" + + + + + An array of alternative routes identified by the concerned Aal2Ap MOs. A routeList can have 0 to 5 Aal2Aps. +The Aal2Ap must be unique. +Note! if this attribute is set, the routePriorityList also must be se with the same number of values ( if the routeList +contains 3 routes, the routePriorityList must contain 3 prioritys). + + + + + + + + + + + A list of all the Aal2Ap priorities. +The priority values can be in the range 1 to 5, one beeing the highest priority. +The Aal2Aps can have the same priorities. + + + + + + + + 0 5 + + + + + + + Defines the possible set of AAL type 2 Service Endpoint Addresses (A2EA) that match the routing case. + +The number direction of a routing case shall be interpreted as all AAL type 2 Service Endpoint Addresses +starting with the string of numbers defined in the number direction. For example, the AAL2 End System +Addresses "12340" and "123400" will both match the number direction "1234". + +The AAL2 routing function uses a longest match comparison to select between routing cases with overlapping +number directions. For example, given two routing cases A with the number direction "1234" and B with the number +direction "12345" the AAL2 End System Address "12345" will be routed using routing case B, whereas the AAL +type 2 Service Endpoint Addresses "12344" and "12346" will be routed using routing case A. + +NOTE: It is not allowed to use leading zeros when configuring this attribute. + +NOTE: It is not possible to replace an existing routing case by creating routing cases with number directions that +completely overlap the number direction of the existing routing case. + +NOTE: It is not possible to create two routing cases with the exact same number directions in a node. + +NOTE: It is possible to create one or more routing cases with number directions that partially overlap the number +direction of an existing routing case. + +Length range 1..15 +Alphabet: "0123456789" + + + + + + + + 1 15 + + + + + + Adds the identified (and existing) Aal2Ap MO to the routeList. This action should also be used when changing the priority for an existing Aal2Ap MO. When submitting an existing Aal2Ap MO with a new priority the routing list will be updated with the new priority for the specified Aal2Ap MO. + +Note! In order to be able to update the priority for a routing entry, the routing entry first has to be deleted and then submitted with the new priority. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + Removes the identified Aal2Ap MO from the routeList. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + The Aal2Sp (AAL2 Signalling Point) MO is used to represent the AAL type 2 Service Endpoint Address of the node in the AAL2 network. +There is one and only one instance of this MO in the ATM NE system. + + For free use + + + "" + + + + + An E.164 format number that specifies the AAL type 2 Service Endpoint Address of the node. + +Length Range: 1..15 +Alphabet: "0123456789" + +Note! It is not allowed to use leading zeros when configuring this attribute. + + + + + 1 15 + + + + + + + + + + + + + + Performance monitoring counter for the number of unsuccessful attempts to establish connections due to node internal problems. + + + + + + 0 + + + + + + + This MO represents a AAL2 Access Point signalling function associated with a single AAL2 signalling relationship to a remote peer AAL2 acess point signalling function. An AAL2 access point is either a high rate access point that uses MTP-3B for signalling or a low rate access point that uses UNI-SAAL for signalling. + +Aal2Ap - Aal2 Access Point + +Note! The performance monitoring counters in the AalAp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Free for use + + + "" + + + + + This attribute holds a list of the reserving MOs. + + + + + + + + + + Operational state of the AAL2 AP. + + + + + + disabled + + + + + The availability status of the Aal2Ap. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Q.2630.2 establishment request timer. Unit is milli seconds. + + + + + + 5000 30000 + + 5000 + + + + + Q.2630.2 release request timer. Unit is milli seconds. + + + + + + 2000 60000 + + 2000 + + + + + Reference to a UniSaalTp or Mtp3bAp MO that provides a signalling link for the Aal2Ap. + + + + + + + + + Reference to a secondary signalling link MO of type UniSaalTp. This attribute can only be set when sigLinkId is of type UniSaalTp. + + + + + + + + The physical location of an AP (Access Point) LR/HR (Low Rate/ High Rate) program represented by a reference to a RPU (ReliableProgramUniter) MO. + + + + + + + + + The identity of the QoSCodePointProfile used by this MO. + + + + + + Performance monitoring counter pmExisOrigConns. +Number of existing connections for the AP originating in this node. + + + + + + + 0 + + + + + The total number of Aal2PathVccTp MOs configured on this Aal2 Ap. + + + + + 0 + + + + + The total number of unavailable Aal2PathVccTp's on this Aal2 Ap, i.e. the number of Aal2PathVccTp MOs connectected to this Aal2Ap with 'administrativeState' LOCKED. + + + + + 0 + + + + + Performance monitoring counter pmExisTermConns. +Number of existing connections for the AP terminating in this node. + + + + + + 0 + + + + + Performance monitoring counter pmExisTransConns. +Number of existing connections for the AP transiting in this node. + + + + + + 0 + + + + + Performance monitoring counter pmSuccOutConnsRemote. +Number of successful establishment of outgoing connections on this AP + + + + + + 0 + + + + + Performance monitoring counter pmSuccInConnsRemote. +Number of successful establishment of incoming connections on this AP. + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccInConnsRemote. + +Number of unsuccessful establishment of incoming connections on this AP caused by reject from beyond this node. + + + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccOutConnsRemote. + +Number of unsuccessful establishment of outgoing connections on this AP caused by reject from remote side, reset from remote side, no reply or signalling link failure. + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccInConnsLocal. +Number of unsuccessful attempts to allocate Common Part Sublayer, CPS, resources during establishment of incoming connections on this AP caused by Channel Identifier, CID, and/or bandwidth collision or mismatch of Call Admission Control, CAC, between peers. + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccOutConnsLocal. + +Number of unsuccessful attempts to allocate CPS resources during establishment of outgoing connections on this AP. Caused by rejects in CAC (Connections Admission Control). + + + + + + 0 + + + + + Performance monitoring counter pmUnRecMessages. + +Number of received unrecognized Q.2630.1 messages on this AP. + + + + + + 0 + + + + + Performance monitoring counter pmUnRecParams. + +Number of received Q.2630.1 messages with unrecognized parameters on this AP. + + + + + + 0 + + + + + + + This MO represents the hardware of the ET-M1 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-M1 board contains 8 physical ports that can be configured as either E1 (ETSI), J1 (TTC) or T1(ANSI). The board does not allow for a mix of E1, J1 and T1 ports, thus all configured ports on the board must be configured to the same standard. + +Each of the ports on the ET-M1 board can be used to carry either ATM traffic or circuit orientated (Nx64 Kbits/s connections) traffic. + +Each port can support up to 30 ATM VC connections. Two of these connections are reserved for AAL2 paths, and therefore two AAL2 multiplexers per port are available. + +Each port can support up to 2 VP connections. + +The ET-M1 board supports 1 bidirectional F4/F5 PM flow per port. + +Other restrictions: +- All ports (configured for ATM) on the board must have the same value for the hecCorrection attribute (ATM Port MO). +- It is possible to configure UBR+ traffic, but there is no guarantee on the minimum cell rate. +- VP shaping is not supported (it is recommended to configure at most one VP per physical port). +- VC shaping is not supported with an exception for AAL2 path traffic. This is shaped to the peak bandwidth on the VC connection. +- When using the Etm1 board the performance monitoring counters in the transmit direction found on the AtmPort MO does not show the following cells: CC cells and OAM FPM cells. + +Note! IMA is not applicable for the ETM1 board. + +Note! When using fractional atm, timeslot 1 must be a part of the fraction. + +Note! ETM1 does not support EPD and PPD + +Note! ETM1 does not have a proper buffer management. Thus fairness of UBR+ traffic can not be guaranteed and shaping on UBR+ traffic is not possible. + +Note! The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 1 per port. + + + user label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the Etm1 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + This MO is used to administer synchronization reference (a synchronization input with support for 2MHz and 10MHz signals) on Timing Unit board. + + Label for free use. + + + "" + + + + + Operational state of TU synchronization reference + + + + + + disabled + + + + + Administrative state of TU synchronization reference + + + locked + + + + + The availability status of the TuSyncRef. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + When the TU synchronization reference is registered in the system as an usable synchronization reference, this MO reference is set by using "local" operation syncReserve(). When synchronization reference is de registered, "local" operation syncRelease is used. Note that the only valid user of these operations is Synchronization MO. + + + + + + + + + + + + + + + + + + The Special purpose Processor Module MO, Spm, represents one of the Special Purpose Processors and its connected hardware. This object is used for SW management and restart. Hardware failure indications are sent to Spu. + +Note! If the board is of type SPB1 the maximum number of Spm MO's that is possible to create under the Spu MO is 3. +If the board is of type SPB2 the maximum number of Spm MO's that is possible to create under the Spu MO is 5. + + + + + + + + + + user label for free use. + + + "" + + + + + The operational state of the SPM + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Switch Module Number + + + + + 0 + + + + + ASCI Port Number + + + + + 0 + + + + + The identity of the SPM on the Special purpose Processor Unit (SPU). + + + + + + + 0 + + 0 + + + + + The list of identities of running Spm's + + + + + + + + + + + The list of identities of installed Spm's in the system. + + + + + + + + + + The uniqe name of the link between the SP and BP. + + + + + "" + + + + + The identity of the reserving MO. + + + + + + + + Restarts the SP. + +Note! This action requires a transaction. + + + + + + + + + The Special purpose Processor Unit MO, Spu, represents the board specific HW on SPB. This objects collects HW failure indications on the board and issues/ceases alarms. + + user label for free use. + + + "" + + + + + The operational state of the SPB board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The special purpose processor link name. + + + + + "" + + + + + + + + + + + + + Restarts all SPs on the board (but not the BP). + +Note! This action requires a transaction. + + + + + + + + + This MO is used to represent the point-to-point ATM cross-connect relationship between two VCL termination points. + + For free use. + + + "" + + + + + Operational state for the cross connection. + + + + + + disabled + + + + + Identifies the VclTp managed object involved in the A side of the cross connection (which consists of an A and B side). + +Must not be the same as vclTpBId. + + + + + + + + + Identifies the VclTp managed object involved in the B side of the cross connection (which consists of an A and B side). + +Must not be the same as vclTpAId. + + + + + + + + + + + + + + + + + + + The Configuration Version, CV, is an MO managing all on disk saved node configuration. This MO keeps all administrative data about the CV's including path and file-names of the configuration files. There may be more than one CV on the disk but only one is used at the time. A CV is always based on one Upgrade Package. + +The local distinguished name of this MO is ManagedElement=1, SwManagement=1, ConfigurationVersion=1. + + + Configuration version MO's id. + + + + + + + + + For free use. + + + "" + + + + + List of stored configuration versions in the node. + +Stored in and read from the file system. + +List of stored configuration versions (CV) in the node. + +The list is a sequence of CVs. +Each CV is presented as structure. A CV structure has following fields: + 1. Name + 2. Identity + 3. Type + 4. UpgradePackageId + 5. Operator name + 6. Comment + 7. Date + 8. Status + +The CV list is formatted as a sequence of ConfigurationVersionAttributes. +Each struct contains one CV. + +The following characters are allowed within the struct members below. + +[0-9], [A-Z], [a-z] and '&' , '%' , ':' , '.' , '_' , '-' + +Note! For comment and operatorName spaces (' ') are also allowed within the strings. + +Struct element description : +-Name is in string format, max length is 40. +-Identity is in string format, max length is 40. +-Type is in string format, max length is 40. +-UpgradePackageId is in string format, max length is 40. +-Operator name is in string format, max length is 40. +-Comment is in string format, max length is 40. +-Date is in string format, max length is 40. Format for date is: weekday month date hour:min:seconds year. +-Status is in string format, max length is 40. + +Note! The identity can not be the same as name. Identity should contain the product identity. + + + + + + + + + + + + The name of the current loaded configuration version. + +Stored in and read from the file system. + +This is the configuration version that the system started with, i.e. the configuration version that was startable at the last node restart. + + + + "" + + + + + The name of the configuration version that will be used at next node restart. + +Stored in and read from the file system. + +This attribute is set by the action "setStartable( name of cv)". +Also set at rollback by the system. The first CV in the rollback list is then used. + + + + "" + + + + + A list of configuration versions to rollback to (configuration version name). + +The configuration version on the first line is used at the next rollback. That line is then automatically removed from the rollback list. + +This attribute is modified by actions setFirstRollbackList() and removeFromRollbackList() + + + + + "" + + + + + + A reference to current executing upgrade package. + + + + + + + Flag that indicates that a configuration version will be created automatically once a day. + + + true + + + + + Time for the automatic creation of configuration versions once a day. + +The string must be specified as "HH:MM" to be accepted at set. + +See also Class Attribute autoCreatedCVIsTurnedOn. +The time is UTC time. + +Note! If changing the clock on the node, this attribute must be set or +the JVM MP must be reastarted. + + + + + + "04:00" + + + + + Flag that indicates if rollback is enabled or not. +When true the system will automatically set the rollback counter. In case of cyclic restarts a rollback will be issued after x restarts. x is defined by the rollbackInitCounterValue. + + + true + + + + + Used by the system when rollback is switched on (autoRollbackOn=true). After the given time the node is considered not in a cyclic restart mode. The rollback counter will then be reset to its initial value (rollbackInitCounterValue). + +Timer value in minutes. + + + + 1 10000 + + 30 + + + + + Initial value for the rollback counter. Used when rollback is switched on (autoRollbackOn=true). + + + + + + 1 10000 + + 5 + + + + + An attribute to indicate status of command log. +It can be ON/OFF(true/false). + + + + + + true + + + + + The name of the executing Configuration Version, CV. + +Same as 'currentLoadedConfigurationVersion' after a node restart, changed to the value of lastCreatedCv when a CV is created. + + + + + "" + + + + + The name of the last created Configuration Version, CV. + + + + + "" + + + + + The CV given will be the one used at the normal node restarts. Only A CV with status = OK can be set as startable. + +This action does not require a transaction. + + + + + + + + + + + + A new CV directory will be created. A DB backup from the current RAM CV, +an ARMAMENT file and the file LLP:LMid is created at the directory. The current +command log file is copied to the CV directory first, then it removes the file from +the current directory. + +Note: The file cmdlog.properties under /c/ will not be saved to the CV. + +The following characters are allowed in the Strings: + +[0-9], [A-Z], [a-z] and '&' , '%' , ':' , '.' , '_' , '-' + +Note! For comment and operatorName spaces (' ') are also allowed within the strings + +-configurationVersionName is in string format, max length is 40 characters. +-identity is in string format, max length is 40 characters. +-operatorName is in string format, max length is 40 characters. +-comment is in string format, max length is 40 characters. + +This action does not require a transaction. + +Note! The configurationVersionName and identity can not be the same. The identity should be the product identity. + + + + + + One ASCII text string. It must be possible to create a directory with string. Do not use string "autocreated1" and "autocreated2" as cv name. They are used by the system. + + + + + + + + + + + + + Type of the configuration version [ standard | test | other ]. + + + + other + + + + + The operator's name. + + + + + + + The operator's comment. + + + + + + + + + Delete a configuration version (CV) permanently. + +If CV is referenced in the startable or in the rollback list, the action is not performed (an exception is thrown instead). + +Note! The latest created CV is not deletable until a node restart is performed or a new CV is created. Also note that a CV is not possible to delete when it has one of the folowing properties: +- "loaded" +- "startable" +- The CV is found in the "rollbacklist" + +This action does not require a transaction. + + + + + + + + + + + + Removes a Configuration Version (CV) from the rollback list. + +This action does not require a transaction. + + + + + + + + + + + + Adds a Configuration Version (CV) first in the rollback list. This will cause the node to chose this CV at the next rollback. A CV with status NOK, can't be put in the rollback list. + +This action does not require a transaction. + + + + + + + + + + + + This action activates the log. + +The inparameter is the drive name (where the command log file should be stored). + +Default command log is drive /c/. + +Note! Invoking this action affects the attribute'commandLogStatus'. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + This action deactivates the logging of configuration commands. + +Please note that uncommited data will be lost. + +Note! Invoking this action affects the attribute'commandLogStatus'. + +Note! This action does not require a transaction. + + + + + + + + + This MO is used as a structural element for the SW managed object. The MO structures the software resources of the node. + +Note that the SwManagement MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, SwManagement=1. + + + For free use. + + + "" + + + + + + + + + + + + + This action will normalize all RPUs in the node. + +Note! This action requires a transaction. + + + + + + + + The UpgradePackage, UP, represents an upgrade package as stored in the node file system and as stored on the ftp server that it is/shall be fetched from. + +There may be more than one UP at the same time on the disk. One UP represents the running system issue in the node. That one is pointed out by the Configuration Version MO. + +The actions on an UpgradePackage MO, are actions that can be called to take that particular UpgradePackage into operation on the node. + +The deletion of the Upgrade Package on disk is performed when the associated Upgrade Package MO is deleted. The Upgrade Package's unique LoadModule MOs and files are deleted. ConfigurationVersions in otherReferringCVs are deleted. + + +The UP MO refers to all load modules used in the UP. One load module may by used in more than one UP. + +Note at the start-up of the system/database/loading of a Configuration Version, special Upgrade Package MOs are created to represent Upgrade Packages that are stored on the disk but do not have an MO in the current Configuration Version. These special Upgrade Package MOs have are in the "onlyDeletable" state. In this state, the MO will throw ActionNotAllowedException on all its actions! + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + + The identity of the MO. + + + + + + + + + Label free of use. + + + "" + + + + + List of references to load modules that belong to this upgrade package. + +The list will be null until a successful install has been performed. + + + + + + + + + + + Path to the .xml file on the node once it has been fetched from the FTP server. + + + + + "" + + + + + Contains the state of this upgrade package. + +The management system and/or operator need to act on some changes in the state attribute. + +This attribute is used to accept/reject and modify behavior of actions. For example action 'upgrade' is not allowed in state notInstalled. Furthermore, action 'upgrade' does not behave the same if state == 'Installed' compared to if state == 'executingUpgrade' or 'awaitingConfirm'. + +To continue and conclude the upgrade sequence when in state == 'awaitingConfirm', action 'confirmUpgrade()' must be called. In this state it is also advisable to check attribute 'confirmationDeadline' to see how much time it is left before automatic rollback is done. + +Upgrade Package MOs that are stored on disk but do not have an MO in the current Configuration Version are in state "onlyDeletable". An MO in this state will throw the exception ActionNotAllowedException on all its actions. + + + + + + NOT_INSTALLED + + + + + Header enum describing the current progress indication. +Note that this is only progress information, that should be shown to a human operator, because some operations may take time. + +Changes in the progress header NEVER entails that the operator or management system need to perform any particular actions. + + + + IDLE + + + + + +This notification attribute is used to indicate progress for different steps in the upgrade sequence. The value gives the total number of steps that is to be performed in current step. + +This attribute is changed whenever 'progressHeader' is changed and indicates a maximum count for the progress of the progress counter. What items that are counted is specific for each case. For some cases, the counter is not yet implemented. In these cases, the progressTotal is set to zero (0) when the progressHeader is set. + + + + + + 0 + + + + + This attribute is used to indicate progress for different steps in the upgrade sequence. The value is separated in increments from 0 to progressTotal. + +The value of progressCount never exceeds the value of 'progressTotal'. + +For some cases, the counter is not yet implemented. In these cases, the progressCount is set to zero (0) when the progressHeader is set. + + + + 0 + + + + + Contains product data for this upgrade package. This information is extracted from the upgrade control file. + + + + + + + + This attribute contains the deadline date and time for an operator confirmation. If the deadline is not met, then an automatic rollback to a previous configuration is issued by the system. + + + + + + "" + + + + + Ip address to the ftp server where the upgrade package is stored. + +The input format used by the operator is four fields of digits, separated by a dot. + + + + + + + + + + File path on the FTP server to the upgrade control file. + + + + + + + + + User id. to be used for logging in to the FTP server. + + + + + anonymous + + + + + Password to the FTP server. This attribute is only supplied at create and is not readable. + + + + + anonymous + + + + + The document number and revision of the uppgrade package where the white spaces has been removed and underscore between the document number and revision has been inserted e.g. 19089-CSX10901/1_A. + + + + + "" + + + + + The list containing the names of the Configuration Versions that stop the Upgrade Package MO from being deleted. + + + + + + + + + + The list of names of Configuration Versions that refer to the Upgarde Package MO, but do not affect the deletable status of the Upgrade Package MO. + + + + + + + + + + Indicates if the Upgrade Package MO can be deleted. + + + + + false + + + + + This attribute is only valid for Upgrade Packages of type Delta.It contains the merge history of this upgrade package. + +Example: [Product Data for normal UP (non Delta UP), Product Data for Delta UP1, Product Data for Delta UP2]. + + + + + + + + + + This attribute states a compatibility index. + +If specified, it may be used when verifying that an upgrade 'from' state is valid for this Upgrade Package. + +Note: It is only used when the Upgrade Control File element upgrade window contains this type of information. + + + + + "" + + + + + This attribute states the CPP upgrade package version of this Upgrade Package + + + + + + + + The attribute contains the result from the latest four invoked actions. + +This attribute is only valid for actions:: +- install (all variants) +- cancelInstall +- verifyUpgrade +- upgrade (all variants, Note that the attribute is only valid when the verification phase discovers that upgrade is not possible'). + + + + + + + + + Load modules defined in the Upgrade Package Control file will only be downloaded to the node if the Load Module MO representing the load module file doesn't already exist. +The result of this action is indicated in the attribute ActionResult. In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'.Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action will be removed in a later version. +Note! This action does not require a transaction. + + + + + + + + + + + + Verifies that an upgrade is possible. + +The operation is not blocked while the verification is executing i.e. after basic controls the operation initiates the verification and returns 'void'. + +The progress of this action is indicated in the attribute ProgressHeader.The result of this action is indicated in the attribute ActionResult. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note: This action does not require a transaction. + + + + + + + + + + + + Upgrades the node. The operation is not blocked while upgrade is executing i.e. after basic controls the operation initiates the upgrade and returns 'void'. + +Before the real upgrade is started a verification phase is executed. + +The progress of this action is indicated in the attribute ProgressHeader. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +The result of this action is only indicated in attribute ActionResult in case the verification phase discovers that upgrade is not possible. + +Note: This action does not require a transaction. + + + + + + + + + + The same as upgrade except that the hard upgrade sequence is always chosen. + +It could be helpful to use this method if the application has start- or upgrade- synchronization problems when using a soft upgrade sequence. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +The result of this action is only indicated in attribute ActionResult in case the verification phase discovers that upgrade is not possible. + +Note: This action does not require a transaction. + + + + + + + + The operator invokes this method when the trial period is over. +The operation is not blocked while upgrade is executing i.e. after basic controls the operation initiates the upgrade and returns 'void'.In case the upgrade fails after 'void' has been returned the attribute ProgressHeader will be set to 'UpgradeExecutionFailed'. + +Note! This action does not require a transaction. + + + + + + + + Cancels an executing upgrade or an upgrade that is awaiting confirm. + +Note: This action performs a node restart so that the CV pointed out in the ConfigurationVersion MO is rolled back. + +Note! This action does not require a transaction. + + + + + + + All load modules defined in the Upgrade Package Control file will be downloaded to the node even if the Load Module MO representing the load module already exists i.e. existing load module files are replaced. +The result of this action is indicated in the attribute ActionResult.In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'.Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action will be removed in a later version. +Note! This action does not require a transaction. + + + + + + + + + + + + Load modules defined in the Upgrade Package Control file will only be downloaded to the node if the Load Module MO representing the load module doesn't already exist. + +This action is non-blocking i.e. the action initiates the installation and returns 'void' immediately without waiting for the installation to be completed. + +In case the installation fails after 'void' has been returned, this will be indicated by change of the value of attribute 'ProgressHeader' to 'ExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + + + All load modules defined in the Upgrade Package Control file will be downloaded to the node even if the Load Module MO representing the load module already exists i.e. existing load module files are replaced. +This action is non-blocking i.e. the action initiates the installation and returns 'void' immediately without waiting for the installation to be completed. +The result of this action is indicated in the attribute ActionResult.In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + + This action only installs the load modules that are required in this node i.e. the load modules required after successful execution of action upgrade on this upgrade package. + +A load module is considered to be required if one of the following criteria is fulfilled: +a) The load module is included in a Repertoire MO where the Repertoire MO is connected to a SwAllocation MO and the SwAllocation MO is connected to a Slot MO, a Fan MO, a Jvm MO, a Webserver MO or an applicable type of application MO. +b) The load module is of type 'other'. + +All required load modules will be downloaded to the node even if the Load Module MO representing the load module already exists i.e. existing load module files are replaced. + +This operation is non-blocking i.e. the action initiates the installation and returns "void" immediately without waiting for the installation to be completed. +The result of this action is indicated in the attribute ActionResult.In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + +Note. The behaviour described for this action is also obtained for the other installation actions if the Upgrade Control File indicates that the upgrade package is of type selective (which is recommended). + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + + This action only installs the load modules defined in the Upgrade Package Control file that are required in this node i.e. the load modules required after successful execution of action upgrade on this upgrade package. + +A load module is considered to be required if one of the following criteria is fulfilled: +a) The load module is included in a Repertoire MO where the Repertoire MO is connected to a SwAllocation MO and the SwAllocation MO is connected to a Slot MO, a Fan MO, a Jvm MO, a Webserver MO or an applicable type of application MO. +b) The load module is of type 'other'. + +Returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute +actionResult. + +The required load modules will only be downloaded to the node if the Load Module MO representing the load module doesn't already exist. + +This action is non-blocking i.e. the action initiates the installation and returns 'void' immediately without waiting for the installation to be completed. + +The result of this action is indicated in the attribute ActionResult. In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure.long + +Note. The behaviour described for this action is also obtained for the other installation actions if the Upgrade Control File indicates that the upgrade package is of type selective (which is recommended). +Note! This action does not require a transaction. + + + + + + + + This action interrupts an ongoing installation of an upgrade package. + +Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at execution of this action. + +This action is non-blocking i.e. the action initiates the cancel of the installation and returns 'void' immediately without waiting for the cancellation to be completed. + +During execution of this action the value of attribute 'ProgressHeader' is set to 'CancelOfInstallationIsExecuting'. + +In case the cancellation fails after 'void' has been returned this will be indicated by change of the value of attribute 'ProgressHeader' to 'CancelOfInstallationFailed'. + +Note! This action does not require a transaction. + +This action interrupts an ongoing installation of an upgrade package. +Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at execution of this action. +This action is non-blocking i.e. the action initiates the cancel of the installation and returns 'void' immediately without waiting for the cancellation to be completed. +During execution of this action the value of attribute 'ProgressHeader' is set to 'CancelOfInstallationIsExecuting'.The result of this action is indicated in the attribute ActionResult.In case the cancellation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'CancelOfInstallationFailed'. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + Is used to clear the contents of current upgrade log file. + +Note! This action does not require a transaction. + + + + + + + + + + The Repertoire is an abstraction of a functionality represented by a plug in unit type (PiuType MO) and one or more load modules (LoadModule MO). The repertoire also provides rules for PiuType/ Load Module combinations valid for a specific function where one function can be provided by one or many PiuType-Load Module combinations. +These rules are used to load the correct software (Load Modules) to a PlugInUnit. This could be used as operator configuration support and/or in situations where automatic re-configuration is required (hot repair). + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade is recommended to create them. + + A user friendly name associated to the managed object. + + + "" + + + + + A function friendly name associated to the repertoire. The value must be unique with respect to all repertoires with the same install state. + + + + + + + + + Information regarding the function. + + + + + "" + + + + + A list containing all PiuType references that has been added to this repertoire. + + + + + + + + + + + + + + + + + + List of reserving SwAllocation MOs. + + + + + + + + + + + + The OSPF Interface MO represents an interface that is used by the OSPF protocol to communicate with a neighbour node. By connecting an OSPF interface to a Link MO that Link is defined as a link to be used by OSPF. + +Each OspfInterface MO must always be connected to a OspfArea MO. + + + User label for free use. + + + "" + + + + + The identity of the OspfArea connected to this OspfInterface. The default value is the default OspfArea MO. + + + + + + The time, in seconds, between LSA re-transmissions over the interface - default value 5 seconds. + + + 5 + + + + + The time, in seconds, between sending OSPF Hello-packets over the interface. Default value 10 seconds. + +Note! Must be a positive value. + + + 10 + + + + + The time, in seconds, after which a neighbor router is declared dead when not heard from. + + + + 40 + + + + + Estimated delay, in seconds, for the transmission of a link state update package over the interface. + + + + 1 + + + + + The interface priority. Each router is configured with a priority configured from 0 - 255 where 0 is the lowest priority and 255 the highest. + +Note! Must be a positive value. + + + + 0 255 + + 1 + + + + + Each OSPF interface is connected to one IP link. +The relatedLink can be either an IpAtmLink or an EthernetLink MO +reference. + + + + + + + + + + + + + + + + + Performance monitoring counter for the number of times this OSPF interface has changed its state or an error has occured. + +See RFC 1850. + + + + + + 0 + + + + + + + The Ospf MO represents an instance of the Open Shortest Path First (OSPF) routing protocol running in a Cello node. + +When the Ospf MO is created a default OspfArea MO is also created. This OspfArea has the areaId 000.000.000.000. + +The attribute range0 in the default OspfArea will contain the following values: +advertise = false +ipAddress = 000.000.000.000 +subnetMask = 000.000.000.000 + + + + + + + + + + + User label for free use. + + + "" + + + + + The ospfRouterId attribute is in the form of an IP address. +In order to able to set ospfRouterId the attribute +administrativeState has to be set to locked. The ospfRouterId +is uniquely identifying the router in the Autonomous System. By +convention to ensure uniqueness, this should be configured to the +value of one of the routers IP interface addresses. + + + + + + + The ospfASBdrRtrStatus attribute controls, whether this router is configured as an Autonomous System border router (Routers connected to multiple areas are called area border routers). The attribute must be set to 'True' if the user wants to configure static routes, which should be distributed to other OSPF routes as external routes. Configuration of static routes is the same as adding and deleting static routes to the IpRoutingTable Mo. + + + false + + + + + The operational state of the MO. +The operationalState can only be enabled when the IP MO is in workingMode routerMode. + + + + + + disabled + + + + + The administrative state of the MO. + + + locked + + + + + Area border router flag - indicates whether the router is acting as an area border router or not. + + + + + false + + + + + The name of the Ip MO that the Ospf MO is to use + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. It is a bit mapped CORBA long, where one or more of the bits may be set. If none of the bits are set then the availability status is considered to be undefined. + + + + + + NO_STATUS + + + + + The number of new link-state advertisments that have been originated. This number is incremented each time the router originates a new LSA. + +For more detailed information, see RFC 1850. + + + + + + 0 + + + + + The number of link-state advertisments received determined to be new instantiations. This number does not include newer instantiations of self-originated link-state advertisments. + +For more detailed information, see RFC 1850. + + + + + + 0 + + + + + Indicates whether the topology database is to be recovered from the database at restart. + + + true + + + + + The interval, in seconds, with which the topology database will be stored. + + + 60 + + + + + + + An OSPF autonomous system is divided into OSPF areas. The OSPF Area MO represents such OSPF areas. + +A default OspfArea MO is automatically created when the Ospf MO is created. +It has the identity = 1, so LDN of this MO will be +ManagedElement=1,IpSystem=1,Ospf=1,OspfArea=1. + +Note! A maximum of 4 OspfAreas can be configured each with a maximum of 8 interfaces. + + + + + + + + + + Label free for use. + + + "" + + + + + Indicates whether the OSPF area is a stub area or not. + + + false + + + + + Indicates whether importing Autonomous System external LSA's is supported. + + + true + + + + + Import Area summary - indicates whether the router will originate and propagate summary LSAs into a stub-area. + + + false + + + + + Cost for default route that the router advertises into the area if the area is a stub area and the router is an area border router. By default set to the least metric among the interfaces to other areas. + + + 1 + + + + + Stub Area metric type. + +RFC 1850 (OSPF V2 MIB): + +comparableCost (external type 1) +nonComparable (external type 2) + + + comparableCost + + + + + Area Lsa checksum - 32-bit unsigned sum of the link-state advertisements LS check sums contained in this area's link-state database. + + + + + 0 + + + + + The OSPF area identity in form of an IP address. This areId uniquely identifies the area. +AreaId 0.0.0.0 is used for the OSPF backbone. +Range: 000.000.000.000 to 255.255.255.255. + + + + + + + + + OspfArea IP address range zero (0). + + + + + + + + OspfArea IP address range one (1). + + + + + + + + OspfArea IP address range two (2). + + + + + + + + The number of times that the intra-area route table has been calculated using this area's link-state database. This is typically done using Dijkstra's algorithm. + +For more detailed information, see RFC 1850. + + + + + + 0 + + + + + Holds a list of the reserving OspfInterface MOs. + + + + + + + + + + Add aggregation range. Used to add a range of IP addresses to an OSPF area. + +Note! This action requires a transaction. + + + + + + The area range aggregation. + + + + + + + + + + + + + + + + + + + + Delete an IP address range. Used to remove a range of IP addresses from an OSPF area. + +Input is the area aggregation range index. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + The Switch Core Unit MO, SCU, represents the board specific HW on the SCB. This object collects HW failure on the board and sends alarms. It is also used for configuration of board specific FW. +This board can only be fitted in slot 1 and 28 in a standards subrack. +The board has a number of switch internal link ports. + alarm + + user label for free use. + + + "" + + + + + The administrative state of the switch internal link ports on the switch board. The attribute refers to all ports (locking will lock all ports, unlocking unlock all ports). +SILI -switch internal link interface. + + + + locked + + + + + Operational state indicates the the traffic handling capability of all ports as a group on the board, i.e it is enabled if one or more of the eight ports is enabled. The purpose of this attribute is only for test. + + + + + + disabled + + + + + Operational State for network synchronization distribution. + + + + + + disabled + + + + + The availability status of the switch internal link (SIL) ports.. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Availability state for network synchronization distribution. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + A list of the reserving MO's. + + + + + + + + + + The attribute provides a list of port numbers. +The port number is between 0-7 and is used to read state of the switch internal port. +See action getSilPortState, getOperState and getAvailState. + + + + + + + + + + + Returns status of the switch internal link port, which is the same as the LEDs on the unit. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns operational status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns availability status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + The General purpose Processor Unit MO, GPU, represents the board specific HW on the GPB; hard disk, ethernet and serial port etc. + +Note! The 'availabilityStatus' for the GeneralProcessorUnit MO is retreived from the PlugInUnit MO. + + + + + + + + + + Label free for use. + + + "" + + + + + Indicates if the function provided by the managed object is capable of performing its normal functions or not. + +Note! The value for operationalState is retrived from the GeneralProcessorUnit's parent, i.e. the PlugInUnit. + + + + + + disabled + + + + + The total size in bytes of the D volume. + + + + + + 0 + + + + + The amount in bytes of freespace available on the D volume. + + + + + + 0 + + + + + The total size in bytes of the P volume. + + + + + + 0 + + + + + The amount in bytes of freespace available on the P volume. + + + + + + 0 + + + + + Holds the identity of the reserving MO. + + + + + + + + + + The JVM MO is used to represent the Java Virtual Machine. This object is used for configuration JVM parameters, including SW management of Java class libraries used in the machine. + +The local distinguished name of this MO is ManagedElement=1, Equipment=1, JVM=1. + + + Label free for use. + + + "" + + + + + Current classpath, the JVM is using + + + + + "" + + + + + New classpath that will be activated at next restart of JVM. The classpath has a directory, which contains the load module, i.e. the classpath references the load module. + + + + + + + + Free memory in the java machine, in bytes. + +NOTE: Before this value is read from the system the action 'garbageCollect' is invoked. + + + + + 0 + + + + + Total amount of memory allocated to the java machine, in bytes. + + + + + 0 + + + + + Contains all classes that are to be initilised and started when the JVM restarts. + +Technical note: The specified classes must implement the se.ericsson.cello.moframework.Mopplet interface and be found in a jar/zip-file pointed out by the classpath. + + + + + + + + + + + Defines the start class name. +e.g. "se.ericsson.cello.oms.Oms" + + + + + "" + + + + + Current options: + -D<property>=<value> Set a system property value. Commonly java.class.path +-Xms<size> Specify the size, in bytes, of the memory allocation pool. +-Xss<size> Set thread stack size in bytes. +-Xverify:[all | remote | none] Verify classes according to the suboption. + -Xverify:all verifies all classes. + -Xverify:remote verifies remote classes only. + -Xverify:none turns off class verification. + + + + + "" + + + + + + + + + + + + + Determines the current system properties. + + + + + + + + + + + + A reference to the ReliableProgramUniter that refers to the programs in the which the JVM executes. + + + + + + + + New start class that will be activated at next restart of the JVM. +e.g. "se.ericsson.cello.oms.Oms" + + + "" + + + + + This attribute is used when setting one or more administrative options. + +A set option is operational after the next Java Machine restart. + +See also attribute 'options' + +One or more options can be set, one option in each string of the +sequence according to description below: + +Current options: + -D<property>=<value> Set a system property value. Commonly java.class.path +-Xms<size> Specify the size, in bytes, of the memory allocation pool. +-Xss<size> Set thread stack size in bytes. +-Xverify:[all | remote | none] Verify classes according to the suboption. + -Xverify:all verifies all classes. + -Xverify:remote verifies remote classes only. + -Xverify:none turns off class verification. + + + + + + + + This attribute holds the identity of the reserving MO. + + + + + + + + + + Runs the garbage collector. + +Note! This action does not require a transaction. + + + + + + Sets a system property (i.e. propertys in the operating system). +Note! The valeus set with this action is not saved in the database. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + + + + Restart of executing JVM instance. + +Note! This action does not require a transaction. + + + + + + + + This MO represents the switch of a Cello node. It is used for general switch configuration. + +The system creates automatically one instance of this MO at restart. + +Today, only a maximum of 32 Switch Modules MOs and 2 SwitchInternalLinks MOs per InternalLinkGroup MOs are allowed in a Cello node. However, in theory the switch addressing space in the system allows up to 256 SwitchModules MOs. This would then mean there are 255 InternalLinkGroup MOs, each of which is allowed 256 SwitchInternalLink MOs by the addressing. + +The local distinguished name of this MO is ManagedElement=1, SwitchFabric=1. + + + + + For free use. + + + "" + + + + + + + + + + + + + + + This MO represents two switch planes of one sub-rack, i.e. either the main switch or an external switch. + +Note! In a non-redundant system the administrativeStateSwitchPlaneA/B has to be set to locked for the non-present plane. + + For free use. + + + "" + + + + + Indicates the number of the switch module, SMN. + +switchModuleNumber &gt;= 0 + +The main switch module, with one or two TimingUnits, is given SMN = 0. SMN for extension switch modules depends on the port pair that the extension switch module is connected to in the main switch module. + +The SMN is calculated according to the following formula: + +Switch module number [1..255] = int (APN/2)*8 + ISL-port in main [1..8] + +APN - ASCC port number +ISL - inter-switch link + + + + + + + 0 255 + + + + + + secondSmnEvaluation - There are two cables that +are relevant for Switch Module Number (smn) numbering +If the cabling is wrong secondSmnEvaluation +will show the second opinion about smn. +Under normal conditions secondSmnEvaluation = smn. + + + + + + 0 + + + + + The administrative state of the switch module. + +Note! When setting the 'administrativeState' to shutting down a notification about that the state has changed to 'locked' will be sent towards the operator. There is however no guarantee that this operation has been succesful despite the notification and state change due to limitations in the resource layer + + + + unlocked + + + + + The administrative state of switch plane A. +It is not allowed to lock both switch plane A and B. + +Note! When setting the 'administrativeState' to shutting down a notification about that the state has changed to 'locked' will be sent towards the operator. There is however no guarantee that this operation has been succesful despite the notification and state change due to limitations in the resource layer + + + unlocked + + + + + The administrative state of switch plane B. +It is not allowed to lock both switch plane A and B. + +Note! When setting the 'administrativeState' to shutting down a notification about that the state has changed to 'locked' will be sent towards the operator. There is however no guarantee that this operation has been succesful despite the notification and state change due to limitations in the resource layer + + + unlocked + + + + + The operational state of the Switch Module. At least one of switch plane is enabled. + + + + + + disabled + + + + + The operational state of Switch Module plane A. The state is disabled if any switch ports is faulty. But switch may still be used. + + + + + + disabled + + + + + The operational state of Switch Module plane B. The state is disabled if any switch ports is faulty. But switch may still be used. + + + + + + disabled + + + + + The availability status of the Switch Module. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The availability status of the Switch Plane A. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The availability status of the Switch Plane B. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The active switch plane: A, B. During multiple faults, both plan A and B may be used. + + + + + + switchPlaneA + + + + + List of reserving MOs. + + + + + + + + + + + + + + + + + + + + The Internal Link Group MO represents all switch internal links connecting the main switch to an external switch. + +Switch internal links are automatically grouped in Reliable Groups for redundancy. + + For free use. + + + "" + + + + + Reference to the SwitchModule MO that is interconnected by the link in the InternalLinkGroup. + + + + + + + + + Reference to the SwitchModule MO that is interconnected by the link in the InternalLinkGroup. + + + + + + + + + The administrative status of internal link group. + + + unlocked + + + + + The operational status of internal link group. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + Returns a list of resource instance identities of the switch internal links in the specified Reliable Group. + +The existing Reliable Groups are listed with action getReliableLinkGroups. + +Note! This action is transactional. + + + + + + + Reliable link group number. + + + + + + + + + Returns the status of the specified switch internal link, within the specified Reliable Group. + +Note! This action is transactional. + + + + + + + + + + + + Reliable link group number. + + + + + + + + + Returns a sequence of Reliable Group numbers. + +Each Reliable Group is identified by a unique number which can be used to read out the identities of the switch internal links that are allocated to the Reliable Group. This is done with action getRlgLinks. + +The allocation of switch internal links to Reliable Groups is automatic. + +Note! This action is transactional. + + + + + + + + + + + + This MO represents a link interconnecting the from either a SCB or SXB port on the main switch to a SCB on an external switch. + +The main switch is located in the hub subrack. + +The SCB is represented by the SwitchCoreUnit MO, while the SXB is represented by the SwitchExtensionUnit MO. + +Switch internal links are automatically grouped in Reliable Groups for redundancy. + + Label free for use. + + + "" + + + + + + + + + + + + + The reference of one connection point for a SwitchCoreUnit or SwitchExtensionUnit. + + + + + + + + + The reference of one connection point for a SwitchCoreUnit or SwitchExtensionUnit. + + + + + + + + + Switch internal port number on PlugInUnit1. + +Note! +On a standard SCB/SXB board, the ports are labeled from the bottom to the top. + +Port nr -> label: + '0' 'D' + '1' 'C' + '2' 'B' + '3' 'A' + +Also note that his mapping will change when adding/removing a board. + + + + + + + 0 3 + + + + + + Switch internal port number on PlugInUnit2. + +Note! +On a standard SCB/SXB board, the ports are labeled from the bottom to the top. + +Port nr -> label: + '0' 'D' + '1' 'C' + '2' 'B' + '3' 'A' + +Also note that his mapping will change when adding/removing a board. + + + + + + + 0 3 + + + + + + The administrative state of switch internal link. + + + unlocked + + + + + The operational state of switch internal link. There is no traffic if the link is disabled. + + + + + + disabled + + + + + The availabilityl status of switch internal link. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The operational state of sync link. There is no clock distribution if the link is disabled. + + + + + + disabled + + + + + The availability state of sync link. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + This MO represents the hardware of the ET-M4 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-M4 board contains 2 physical ports that can be configured as either STM1(ETSI/TTC) or OC3C (ANSI). The board supports unchannelised ATM access (i.e. it maps ATMs cells directly into an SDH VC4 container). + +The board supports up to 1800 ATM VC connections. +The number of terminated VPs are limited to 48/board. +The board supports up to 750 VC UBR+ connections. + +The ET-M4 board contains 128 AAL2 multiplexers. +The ET-M4 board supports up to 256 bidirectional F4/F5 PM flow per port. + +Note! IMA is not applicable for the ETM4 board. + +Note! The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 256 per board. + +Note! When using the Etm4 board the performance monitoring counters in the transmit direction found on the AtmPort MO does not show the following cells: CC cells and OAM FPM cells. + + User label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the hardware ETM4. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + Virtual path connection termination point, VpcTp, is used to represent the point where the VPC and associated overhead (F4 OAM cells) are terminated/originated. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + Label for free use. + + + "" + + + + + + + + + + + + + enabled or disabled according to the actual operational state of the VpcTp + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Continuity checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. Continuity check both enables generation of CC cells as well as detection of LOC + + + false + + + + + PM mode is set to indicate type of performance monitoring mode (i.e. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + + NOM_PM_BLKSIZE_2_10 + + + + + Performance monitoring counter for number of lost forward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM, cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + This action performs VC end to end loopback from this VpcTp. +false=Failed, true=Succeded + +Note! This action requires a transaction. + + + + + + + + + This MO is used to represent the termination of a VP link. + +Note that a maximum of 999 MO's of this type may be configured. + +Note! For information on how many VplTp's that can be configured under the AtmPort MO please refer to the board that is parent to the termination reserved by the AtmPort MO. + +The performance monitoring counters in the VplTp MO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + This MOs user label. + + + "" + + + + + Reference to the Atm Traffic Descriptor. + + + + + + + enabled or disabled according to the actual operational state of the VplTp. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This is the virtual path identifier for the external ATM cells. + + + + + + + 0 255 + + + + + + Performance monitoring counter for number of received ATM cells for the VplTp. + + + + + + + + 0 + + + + + Performance monitoring counter for number of transmitted ATM cells. + + + + + + + 0 + + + + + + + + + + + + + + + This MO represents a timing unit (reference clock) in the node. + +The corresponding Program shall be of LoadModuleLoaderType, SpmFpgaLoader. + + Label for free use. + + + "" + + + + + Operational state of TimingUnit + + + + + + disabled + + + + + The availability status of the TimingUnit. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + The PiuType is an MO that holds product information about a PlugInUnit and the execution resources of the PlugInUnit. It is created/deleted during a software upgrade. +The PiuType is used when creating execution MOs connected to a PlugInUnit and when allocating software to this resource. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + + + + + A user friendly name associated to the managed object. + + + "" + + + + + The productData describes the product number, short product revision, product name and product information of the PlugInUnit. The production date is not used. + +Trailing letters in the revision is recommended to be excluded in the PiuType. Example: R2B will be R2 without trailing letter, R2B/3 must be R2B/3 in the PiuType, R2B/A should be R2 in the PiuType. + + + + + + + + + + The width of the PlugInUnit board in steps of 5 mm. +A PlugInUnit can use/cover more than the slot that it occupies. + +Example: boardWidth=3 corresponds to 3*5 = 15 mm. + + + + + + + + + Control value m3/h for the fan unit. Needed by cooling function. + + + + + + + + + + + + + + + + The value will be MP if a board has the role of a Main processor. +The value will be BP if a board has the role of a device board +Otherwise the value will be OTHERS. + + + + + + + + + + The identity's of the reserving MO's. + + + + + + + + + + Returns the number of entries in the PIUTypeConfigurationArray. + +Note! This action requires a transaction. + + + + + + Returns a struct of a specific MoConfiguration at a given index. +The moConfiguration holds information about how to create the +subordinate objects for a specific piu type. + +Precondition: 0 <= index <= numberOfMoConfigurations() - 1 + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This MO is primarily used to handle data for automatic configuration of load modules. Automatic in the meaning that the system selects the appropriate load module and revision. A SWA may be related to a slot, indicating that a specific functionality is requested at this location. The SWA is manually created by the operator. + +The SWA object is related to (one or more) repertoires, which hold information on possible PIU-type/revisions and load module combinations. + +In some cases (e.g multi-purpose boards, boards with processor/FPGA-pools) it may not be possible to completely configure the PIU without instructions from the operator (e.g which load module runs on which processor/FPGA). In these cases a specialization of the SWA has to be designed in such a way that it can be manually configured. + +When a SwAllocation MO depends on a ManagedObject MO, this ManagedObject actually represents a RBS Fan. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade is recommended to create them. + + Free for use. + + + "" + + + + + The role of a slot/PIU. The role must be unique with respect to other SwAllocations in the node. + +This is a preparation to introduce predefined SwAllocation in future upgrade packages. + + + + + + + A list of references to repertoires. + + + + + + + + + A list of references to mainly slots in a subrack, e.g. Slot or Fan MO. It may also refer to other objects handling auxiliary units, e.g. RBS Fan. + + + + + + + + + + + + + + + + + Adds the specifed repertoire to this list. + +Note! This action does not require a transaction. + + + + + + + + + + + + + Removes the first occurrence of the specified repertoire from this list. + +Notw! This action does not require a transaction. + + + + + + + + + + + + Adds the specified Slot to the slotList. +The slot can only be of type Slot MO, Fan MO, WebServer MO, JVM MO or an applicable type of application MO (e.g. for "RBS Fans"). + +Note! This action requires a transaction. + + + + + + + + + + + + + Removes the first occurrence of the specified slot from this list. +The slot can only be of type Slot MO, Fan MO, WebServer MO or an +applicable type of application MO (e.g. for "RBS Fans"). + +Note! This action requires a transaction. + + + + + + + + + + + + Removes all repertoires from this list and sets its size to zero. + +Note! This action requires a transaction. + + + + + + Removes all slots from this list and sets its size to zero. + +Note! This action requires a transaction. + + + + + + Adds the specified Slot to the slotList. +The slot can only be of type Slot MO, Fan MO, WebServer MO, JVM MO or an applicable type of application MO (e.g. for "RBS Fans"). +If the slot exists in the list, the object is ignored. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + Adds the specifed repertoire to this list. + +If the repertoires exist in the list the repertoire is ignored. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + The Medium Access Unit (MAU) MO represents the Ethernet transceiver function on a General Processor Board (GPB). + +Note! Ethernet links which are modelled by a MediumAccessUnit MO are used for O&M IP traffic only. MediumAccessUnit MOs must not be configured under a GeneralProcessorUnit MO which have a IpAccessHostGpb referring to it. + +Note! This object is known in standards as "MediumAttachmentUnit". + + + Label for free use. + + + + "" + + + + + Description of operational state which has an enumerated datatype + + + + + + disabled + + + + + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This attribute is used by a management system to show the label on the port the connector is attached to. + + + + + Eth + + + + + Performance management counter for the number of times that a collision was detected on the interface after the minimum length of a frame. + + + + + + 0 + + + + + Performance management counter for the number of frames that did not pass the FCS check. + + + + + + 0 + + + + + The Link Speed, measurment unit is Mb/s.. + + + + + + 0 + + + + + The duplex mode used. + + + + + + + + FULL_DUPLEX + + + + + + + A Reliable Program Uniter (RPU) is a controlling and addressing entity providing one common addressing unit for two Reliable Programs. Or more correctly for parts of two Reliable Programs, each part is called a Resource Suite Handler (RSH). The RSH is implemented and owned by the application. It is not a function or a concept within Cello. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + + For free use. + + + "" + + + + + Reliable Program Label. +Compare this to the reliableProgramLabel in LoadModule MO. + + + + + + + + + Reference to slot, contains the running "Normal" relation to a slot. If the reference is set to the passive slot, the passive slot will be cleared and only one relation will be set. + + + + + + + Reference to slot, contains the running "Stand-by" relation to a slot. If the reference is set to the active slot or a null value, the passive slot will be cleared. + + + + + + This attribute controls when to switchover the RPU, if a certain type error situation occurs. + + + AtPiuFault + + + + + This attribute controls when to switch back the RPU, after error recovery has been done. + + + Automatic + + + + + This attribute indicates that which level of data replication that is associated with the RPU. + + + + + ApplControlled + + + + + This attribute indicates if the RSH execution mode (active/passive) in the two Reliable Program, matches the normal/stand-by relations set on the corresponding RPU. + + + + + + Unavailable + + + + + + + + + + + + + + List of reserving MOs. + + + + + + + + + + This action will force the two corresponding RSHs to change their execution mode (active/passive). It will lead either to a switchover or to a switchback, depending of what value the operational Mode attribute is showing. + +Note! This action requires a transaction. + + + + + + + + + This object contains attributes and actions on Cello node-level. + +The ManagedElementData MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, ManagedElementData=1. + + + + + + + + + + + This attribute specifies if the system is allowed to auto create detected objects. Note that slots will always be auto created. + +Note! When setting this attribute from true to false the system creates a new CV. + + + false + + + + + The base URL for the documentation server (ALEX). The attribute is read by Element Management application to find the documentation server in the network. + + + "" + + + + + A list of node names or IP addresses of the single logon servers (SLSs). The list uses commas to seperate the single logon server addresses, e.g. "https://SLS1,https://SLS2,https://SLS3", these addresses consists of the URLs to the concerned SLS servers. The attribute is read by Element Management application to find the single logon server in the network. + + + "" + + + + + IP addresses to the DHCP server, used by the DHCP Relay Agent. + +Default is an empty array. + +Adding and removing addresses is done through the actions addDhcpServerAddress() and removeDhcpServerAddress(). + + + + + + + + empty + + 10 + + + + + This attribute is used by the internal performance management service +to know where to store it's data files. The attribute is the name of +a path in the node. + +Example: /c/public_html/cello/XML_files/ + + + "" + + + + + This is the IP address to the NTP server + + + "" + + + + + This is a boolean that controls if the node should poll the primary NTP server for information. + + + false + + + + + This value states the minimum interval (in seconds) for polling the primary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 64 + + + + + This value states the maximum interval (in seconds) for polling the primary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 1024 + + + + + This is the burst flag used towards the primary NTP server. + + + false + + + + + This is an alternative IP address to a NTP server + + + "" + + + + + This is a boolean that controls if the node should poll the secondary NTP server for information. + + + false + + + + + This value states the minimum interval (in seconds) for polling the secondary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 64 + + + + + This value states the maximum interval (in seconds) for polling the secondary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 1024 + + + + + This is the burst flag used towards the secondary NTP server. + + + false + + + + + This attribute specifies the UTC time used in the node. The attribute value is milliseconds since epoch (January 1, 1970, 00:00:00 GMT). +The value may only be set while ntpServiceActive both for primary and secondary is false. + + + 0 + + + + + This value states in what time zone the node is located. This attribute is needed by management application to convert UTC time from a log or NTP service to local time. +It will not change the real time clock on the node. + +The timeZone is represented by three characters, example GMT. + +Available options are: + +TimeZone ID Offset +GMT (Greenwich Mean Time) 0 +UTC (Coordinated Universal Time) 0 +ECT ( Central European Standard Time) + 1 +EET (Eastern European Time) + 2 +ART (Eastern European Time) + 2 +EAT (Eastern African Time) + 3 +MET (Iran Time) + 3.5 +NET (Armenia Time) + 4 +PLT (Pakistan Time) + 5 +IST (India Standard Time) + 5.5 +BST (Bangladesh Time) + 6 +VST (Indochina Time) + 7 +CTT (China Standard Time) + 8 +JST (Japan Standard Time) + 9 +CST (Central Standard Time) + 9.5 +EST (Eastern Standard Time) + 10 +AET (Eastern Standard Time) + 10 +SST (Solomon Is. Time) + 11 +NST (New Zealand Standard Time) + 12 +CAT (Central Alaska Time) - 1 +AGT (Argentina Time) - 3 +BET (Brazil Time) - 3 +CNT (Newfoundland Standard Time) - 3.5 +PRT (Atlantic Standard Time) - 4 +IET (Eastern Standard Time) - 5 +ACT (Central Standard Time) - 6 +PNT (Mountain Standard Time) - 7 +MST (Mountain Standard Time) - 7 +PST (Pacific Standard Time) - 8 +AST (Alaska Standard Time) - 9 +HST (Hawaii Standard Time) - 10 +MIT (West Saoma Time) - 11 +-- + +Reference: http://www.greenwichmeantime.com + + + + "" + + + + + This attribute states weather daylight saving time is used on this node. It is used to by the management application and will not change the real time clock on the node. + + + false + + + + + The total size of the C volume on the Cello node in bytes. The C volume may be replicated on several hard disks. + + + + + + 0 + + + + + The number of bytes of free space available on the C volume. The C volume may be replicated on several hard disks in a Cello node. + + + + + + 0 + + + + + This is a unique node identity to be set only in the factory. + + + + + "" + + + + + A list of URLs of external server for downloading of software. A comma-separated list or URLs, complete with path and name of property file. + +Note: For downloading of software for system upgrade, see attribute ftpServerIpAddress in MO UpdradePackage. + + + "" + + + + + The type of node restart when it is a problem with the last PIU in a PIU group. + + + WARM_AT_PIU_RESTART + + + + + The sync mode operation of the node. Note that this attribute is only relevant when the node contains CBU board. For all other cases the value shall be set to NOT_USED. + + + NOT_USED + + + + + This action creates the primary Network Time Protocol. There can only exist one primary and one secondary ntp. + +Once the ntp is created it is possible to change the attributes, i.e ip address, burst flag, max- and min poll and which is the active one. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This action creates the secondary/alterative Network Time Protocol. +There can only exist one primary and one secondary ntp. + +Once the ntp is created it is possible to change the attributes, i.e ip address, burst flag, max- and min poll and which is the active one. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This action deletes the primary NTP. + +An exception will be thrown if the primary attributes are accessed (set and get). + +Note! This action requires a transaction. + + + + + + + This action deletes the secondary NTP. + +An exception will be thrown if the secondary attributes are accessed (set and get). + +Note! This action requires a transaction. + + + + + + Takes an array of Ip addresses (Strings), and adds them to the list held by the Dhcp Relay Agent fRO. + +Note! This action requires a transaction. + + + + + Elements are assumed to have the format of a String with 4 fields of numerics, each field separated with a dot. E.g. 123.322.34.123. An empty array or empty string in first element is not allowed. Max 10 elements. + + + + + + + + + + + Takes an array of Ip addresses (Strings), and removes them from the list held by the Dhcp Relay Agent fRO. + +Note! This action requires a transaction. + + + + + Elements are assumed to have the format of a String with 4 fields of numerics, each field separated with a dot. E.g. 123.322.34.123. An empty array or empty string in first element is not allowed. Max 10 elements. + + + + + + + + + + Used for setting the nodeUniqueId attribute. This method should only be used in the factory, i.e. it is not for general use by the operator. + +Note! This action requires a transaction. + + + + + + + + + + + + + + This MO represents the Switch Extension Unit, SXU, board. The board may only be inserted in slot 2-27 (in a standard subrack). +If redundant links are used, two boards must be inserted next to each other. +The board has a number of switch internal link ports. + + + + + + + + + + This attribute is used to hold a user friendly name of the object if needed. + + + "" + + + + + The administrative state of switch internal link ports on the switch board. +The attribute refers to all ports (locking will lock all ports, unlocking will unlock all ports). +SIL- switch internal link. + + + + + unlocked + + + + + Operational State for all ports. Operational state is enabled if one of the eight ports is enabled. + + + + + + disabled + + + + + Operational State for network synchronization distribution + + + + + + disabled + + + + + The availability state of switch internal link (sil) ports. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The availability state of the sync link. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The attribute is set by the action Reserve. + + + + + + + + + + The attribute provides a list of port numbers. +The port number is between 0-7 and is used to read state of the switch internal port. +Se action getSilPortState, getSilOperState and getSilAvailState. + + + + + + + + + + + Returns status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns operational status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns availability status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This MO is used to represent an AAL2 Path Distribution Unit. Such a unit handles a set of Aal2PathVccTps that belong to the same Aal2 AP and that are handled by the same Path Resource Handling Program. +This Path Resource Handling Program is referenced by the rpuId attribute. + + + + + + + + + + Label for free use. + + + "" + + + + + The physical location of a CPS RC (Common Part Sub-Layer Resource Control) program represented by a reference to a ReliableProgramUniter. + +Note that one ReliableProgramUniter MO may only be referenced once under one Aal2Ap. That means all Aal2PathDistributionUnits must reference different ReliableProgramUniter MO's. + +Two Aal2PathDistributionUnits under different Aal2Ap's may however reference the same ReliableProgramUniter MO. + + + + + + + + + List of references to Aal2PathVccTp MO:s. +Note that setting of this attribute removes the current list of Aal2PathVccTp's. +Each reference must be unique among all paths within all Aal2PathDistributionUnit's belonging to the same Aal2Ap. + + + + + + + + This action adds a list of Aal2PathVccTps to an Aal2PathDistributionUnit. + +If the data contains a reference to a non existing path, the exception InvalidReference is raised. + +If the path list contains a path that has a non-unique aal2PathId value, then the exception Aal2PathIdNotUnique is raised. The pathId value must be unique within all Aal2PathDistributionUnits under the same Aal2Ap. + +If the path list contains a path that already belongs to a Aal2PathDistributionUnit, then the exception PathAlreadyRegistered is raised. + +Note! Adding one or more Aal2PathVccTps using this action updates the attribute 'Aal2PathVccTpList'. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + This action removes a list (sequence) of AAL2 path's from the Aal2PathDistributionUnit. + +If the path list contains a path that is not in this Aal2PathDistributionUnit, the exception NotInGroup is raised. + +Note! Removing one or more Aal2PathVccTps using this action updates the attribute 'Aal2PathVccTpList'. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + The Fan is used for cooling the Cello-subrack and is connected to one or two +SCU (switch core board). This MO is used for controlling and sending alarm from +the Fan. + +Note, either the fan can be supplied by Cello and Fan MO is used, or alternatively the fan can supplied by a source external to Cello and therefore a ManagedObject MO is used to represent the fan. + + + + + + + + + + + + user label for free use. + + + "" + + + + + The administrativeState of Fan MO. + + + locked + + + + + A Fan must always be connected to a Switch Core unit that mediates the communication with a main processor. + +In this attribute it is possible to see which SwichCoreUnit that the fan is connected to. + + + + + + + + + + The operational state is set to 'enabled' when the Fan has loaded and started its load module. + + + + + + disabled + + + + + A reference to an available PiuType at create of a Fan. + + + + + + + + The application that controls the Fan has three main states: +- standalone: running on itself, not manageable +- autonomous: manageable state +- noiseReduced: temporary state with reduced cooling + +NOTE: This attribute is not supported in CPP 4. + + + + + + standalone + + + + + The physical address of the RS-485 communication link. +Incorrect setting of the address can cause collision with other connected auxiliary units or lost connection. The default value should be suitable for most configurations. + + + + + + 1 255 + + 7 + + + + + The identity of the reserving MO. + + + + + + + + A restart will cause the Fan to be initiated, re-booted and all load modules to be reloaded from persistent memory. This is also known as a forced reload. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + This MO represents a MTP2 Termination Point for the ITU standard, as defined in Recommendation Q.703 07/96. + +The performance monitoring counters found in Mtp2Itu MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a hardware fault, aal1 server/adm restart or node restart. + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard +which is NOT the ITU standard. + +NOTE: There is a restriction of a maximum of 32 Mtp2Tp's per MP. + + Free tag for marking this managed object. + + + "" + + + + + + + + + + + + + The operational state of the MTP2 Signalling Terminal. + + + + + + disabled + + + + + Reference to a Mtp2ProfileItu MO. + +Note: The bitRate can not be changed. + + + + + + + + Number of re-transmitted octets. + + + + + + 0 + + + + + Number of negative acknowledgements received. + + + + + + 0 + + + + + Number of signal units received in error. + + + + + + 0 + + + + + Number of started local RB congestions. + + + + + + 0 + + + + + Number of octets in send buffer. + + + + + + 0 + + + + + Total time in local SIB (Sending). + + + + + + 0 + + + + + Total time in remote SIB (Receiving). + + + + + + 0 + + + + + Number of SIO & SIF octets transmitted. + + + + + + 0 + + + + + The attribute is set by the list of reserving MO's. + + + + + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + The PlugInUnit MO that this MO references. +It indicates on which processor the Termination Point will be. + +Note: The PlugInUnit must be of type GPB. + + + + + + + + + Number of MSUs transmitted. + + + + + + 0 + + + + + Number of SIO and SIF octets received. + + + + + + 0 + + + + + Number of MSUs received.. + + + + + + 0 + + + + + + + This MO represents a MTP2 Termination Point for the ANSI standard , as defined in T1.111-1996. + +The performance monitoring counters found in Mtp2Ansi MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a hardware fault, aal1 server/adm restart or node restart. + +NOTE: This MO cannot in anyway be related (either contained by or dependent on) an MO that belongs to a +standard which is NOT the ANSI standard. + +NOTE: There is a restriction of a maximum of 32 Mtp2Tp's per MP. + + Free tag for marking this managed object. + + + "" + + + + + + + + + + + + + The operational state of the MTP2 Signalling Terminal. + + + + + + disabled + + + + + Reference to a Mtp2ProfileAnsi MO. + +Note: The bitRate can not be changed. + + + + + + + + Number of re-transmitted octets. + + + + + + 0 + + + + + Number of negative acknowledgements received. + + + + + + 0 + + + + + Number of signal units received in error. + + + + + + 0 + + + + + Number of started local RB congestions. + + + + + + 0 + + + + + Number of octets in send buffer. + + + + + + 0 + + + + + Total time in local SIB (Sending). + + + + + + + 0 + + + + + Total time in remote SIB (Receiving). + + + + + + 0 + + + + + Number of SIO & SIF octets transmitted. + + + + + + 0 + + + + + Number of MSUs received.. + + + + + + 0 + + + + + List of reserving MO. + + + + + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + The PlugInUnit MO that this MO references. +It indicates on which processor the Termination Point will be. + +Note: The PlugInUnit must be of type GPB. + + + + + + + + + Number of MSUs transmitted. + + + + + + 0 + + + + + Number of SIO and SIF octets received. + + + + + + 0 + + + + + + + The Ds0Bundle, Digital Signalling Level 0, MO represents a number of timeslots on a physical port. +Any of E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp or T1Ttp. +The Ds0Bundle can be used in three different ways: + +- Fractional ATM + +Please refer to the AtmPort MO for details. Note that the TdmMode attribute +must be disabled. + +-Circuit emulation + +Please refer to Aal1VccTp MO for details. Note that the TdmMode attribute +must be disabled. Note that only 4 Ds0Bundle's per port can be configured +when running circuit emulation. + +- TDM Switching + +The Ds0Bundle is reserved for switching node internal Ds0 connections. In +this mode, the tdmMode attribute should be enabled. + + + + + + + + + + + + + Free tag for marking this managed object. + + + "" + + + + + The availabiltity status of Ds0Bundle. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The operational state of Ds0Bundle. + + + + + + disabled + + + + + The list gives the time slots (within ATM traffic fraction) that are to be allocated to the Ds0Bundle. + +When a Ds0Bundle is contained by a E1PhysPathTerm the slots that can be placed in this list are 1 to 31. +When a Ds0Bundle is contained by a J1PhysPathTerm then the slots that can be placed in this list are 1 to 24. +When a Ds0Bundle is contained by a T1PhysPathTerm then the slots that can be placed in this list are 1 to 24. +When a Ds0Bundle is contained by a E1Ttp the slots that can be placed in this list are 1 to 31. + +Note: the same timeslot cannot appear more than once in the list! If a E1/J/T1PhysPathTerm contains more than +one Ds0Bundle, then the Ds0Bundles listOfTimeSlots must be mutually exclusive (i.e. slots in one list cannot be used in another list). + +Note! If the Ds0Bundle is used for carrying SS7 traffic, the listOfTimeSlots can only contain 1 (one) time slot. +In this case that is if the Ds0Bundle is reserved by an Mtp2TpAnsi, Mtp2TpItu or Mtp2TpChina. + + + + + + + + 0 31 + + + + + + + The state of tdmMode (Time Division Multiplexing), can be disabled/enabled. + + + + + + + + + + + The identity of the reserving MO. + + + + + + + + + + + + The Aal1TpVccTp MO represents the Aal1 interworking function in a circuit emulation. The object refers to a Ds0Bundle which represents one end of the circuit emulation, and a VclTp which represents the other end. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + Free tag for marking this managed object. + + + "" + + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + Indicates how many bytes are filled in each ATM cell. The value 47 indicates that the partial filled cells is not used, i.e. all the cells are filled completely. + +Partial filling of cells in used in circuit emulation. It is used to reduce packetisation delay. Refer to the ATM Forum specifications for more details. + + + + + + + 23 47 + + 47 + + + + + Specifies the cell delay variation tolerance. Refer to ATM Forum specifications for more details. + +Unit is micro seconds. + + + + + + 100 4000 + + 1000 + + + + + The operational state of Aal1TpVccTp. + + + + + + disabled + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. + +Activates VC end to end continuityCheck according to ITU.T rec I.610. + + + false + + + + + Controls the activation of PM counters and F5 PM flow on the VC connection. + + + PM_MODE_OFF + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + NOM_PM_BLKSIZE_2_10 + + + + + Performance monitoring counter for forwarded lost cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + + + + + + + + + The VclTp MO that this MO references. + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + + + Mtp3b Signalling Point for the ANSI standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the Ansi standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpAnsi MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ANSI standard. + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + + + + + + + + + + User label for free use. + + + "" + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + The network indicator, NI, is used for discrimination of messages between functionally different networks. + + + + + + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 24)-1 (16777215). +The SignallingPointCode (SPC) is normally grouped together as three numbers wich correspond to network identifier, network cluster, network cluster member. The three numbers are coded as 8-8-8 bits in the total SPC. To enter the SPC-value, you have to convert the 3 numbers to their binary code and then convert the whole 24-bit patterna as an integer. Sometimes the SPC is used as a whole uniqe number (no internal structure). + + + + + + + + 1 16777215 + + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +Minimum string length 2 characters, maximum 30 characters. Allowed characters are 0-9, A-F. +Only even number of characters is allowed. + + + + 2 30 + + "A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5" + + + + + The nodeBehaviour attribute represents the MTP3b node type. + + + + + SEP + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + Determines how a TransFer Restricted signal (TFR) should be treated. + + + + IGNORED + + + + + The sioSpare2 attribute determines if the two spare bits in the SIO (Service Information Octet) should be treated as spare. + + + PRIO + + + + + For M3UA, number of attempts to send the DAUD message. + + + + 1 65535 + + 5 + + + + + Number of attempts to send the SCTP_ASSOCIATE_REQ message. + + + + 0 65535 + + 4 + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The sendSltmBefLink attribute determines if the SLTM (Signalling Link Test Message) should be sent and a SLTA received before the link is considered to be in service. + +Note! It is not recommended nor is it in accordance with standard to set the value of this attribute to 'false' + + + true + + + + + Struct containing the ANSI priority attributes. + + + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 1 + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Struct containing ANSI specific timer data. + + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of received CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of times the timer T21 was started (i.e. how many times the remote inhibit test message has been sent). + + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + The number of successful abortions of signalling associations. + + + + + 0 + + + + + The number of succesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of unsuccessful abortions of signalling associations. + + + + + 0 + + + + + The number of unsuccesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of incoming request for association establishment when state on the association is 'DOWN' and establishment of associations is blocked. + + + + + 0 + + + + + The number of times that the max limit for trying to establish an association has been reached. + + + + + 0 + + + + + The number of times that the max limit for trying to activate an association has been reached. + + + + + 0 + + + + + The number of messages with low priority that has been discarded. + + + + + 0 + + + + + + + Mtp3b Signalling Point for the ITU standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the ITU standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpItu MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ITU standard. + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + +NOTE: The value of the attribute 'version' is valid for all SPs (Mtp3bSpItu MOs) and the value of the last created or changed SP will be used for all SPs. + + + + + + + + + + User label for free use. + + + "" + + + + + The networkInd attribute (NI) is used by signalling message handling functions in MTP3b + + + + + + + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 14)-1 (16383). +The SignallingPointCode (SPC) is normally used as a whole unique number (no internal structure). But sometimes the SPC is grouped together as three numbers which corresponds to zone, area/network, signalling point. If this is the case the three numbers are coded as 3-8-3 bits in the total SPC. To enter the SPC-value then you have to convert the three numbers to their binary code and then convert the whole 14-bit pattern as an integer. + + + + + + + 1 16383 + + + + + + This attribute shows what MTP3b ITU standard the system follows. With ITU, it is possible using this attribute to set which of the ITU standard versions that shall be followed. + +Note! Setting of another value than 'ITU_T_07_96' at create will have no effect. The Signaling Point will always be created with the value 'ITU_T_07_96'. + +Note! It is not possible to hav signaling points with different versions in the node so setting of this attribute will effect all signaling points. The value for the last created or changed signaling point will be used for all signaling points. + + + ITU_T_07_96 + + + + + The nodeBehaviour attribute represents the MTP3b node type. + + + + + + + SEP + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 1 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + Determines if a TransFer Restricted signal (TFR) should be treated as a TFA (TransFer Allowed signal) or be ignored. + + + + IGNORED + + + + + The sioSpare2 attribute determines if the two spare bits in the SIO (Service Information Octet) should be treated as spare. + + + PRIO + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + The sendSltmBefLink attribute determines if the SLTM (Signalling Link Test Message) should be sent and a SLTA received before the link is considered to be in service. + +Note! It is not recommended nor is it in accordance with standard to set the value of this attribute to 'false' + + + true + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +Minimum string length 2 characters, maximum 30 characters. Allowed characters are 0-9, A-F. +Only even number of characters is allowed. + + + + + + 2 30 + + "A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5" + + + + + Struct containing the priority attributes. + + + + + + + Struct containing ITU specific timer attributes + + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + For M3UA, number of attempts to send the DAUD message. + + + + 1 65535 + + 5 + + + + + Number of attempts to send the SCTP_ASSOCIATE_REQ message. + + + + 0 65535 + + 4 + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of received CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of times the timer T21 was started (i.e. adjacent SP restarted). + + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + The number of successful abortions of signalling associations. + + + + + 0 + + + + + The number of succesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of unsuccessful abortions of signalling associations. + + + + + 0 + + + + + The number of unsuccesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of incoming request for association establishment when state on the association is 'DOWN' and establishment of associations is blocked. + + + + + 0 + + + + + The number of times that the max limit for trying to establish an association has been reached. + + + + + 0 + + + + + The number of times that the max limit for trying to activate an association has been reached. + + + + + 0 + + + + + The number of messages with low priority that has been discarded. + + + + + 0 + + + + + + + Mtp3b Signalling Point for the TTC standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the TTC standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpTtc MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a +standard which is NOT the TTC standard. + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + + + + + + + + + + User label for free use. + + + "" + + + + + The networkInd attribute (NI) is used by signalling message handling functions in MTP3b. + + + + + + + + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 16)-1 (65535). +The SignallingPointCode (SPC) is always used as a whole unique number (no internal structure). + + + + + + + 1 65535 + + + + + + The nodeBehaviour attribute represents the MTP3b node type. + +Note! Only SEP and STP is supported for the Ttc standard. + + + + + + SEP + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 0 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +String length 4 characters. Allowed characters are 0-9, A-F. + + + + + + 4 4 + + "7711" + + + + + Struct containing the TTC priority attributes. + + + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + Struct containing TTC timer attributes. + + + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of received CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + + + This MO represents an MTP3b Signalling Link for the ANSI standard. It represents the termination of the signalling link within the signalling point as defined in T1.111-1996. + +The total amount of links between any two specific nodes in the network shall not be more than 80 independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. A maximum of five linksets with a maximum of 16 links in each linkset can be configured. A maximum of 16 links between two adjacent nodes can be configured. + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ANSI standard. + +The performance monitoring counters found in Mtp3SlAnsi MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + + + + + + + + + + User label for free use. + + + "" + + + + + This attribute reflects the operational status of the Mtp3bSlAnsi. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The tpId attribute points out the termination point of the lower layer protocol. + +For narrowband this signalling link will be connected to an MTP L2 termination point (Mtp2Tp MO). And for broadband it will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + The link state of the Mtp3bSlAnsi. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + The signalling link code, SLC, used for this link. +The signLinkCode for a link must be unique between the nodes, +independent on in which linkSet the link belongs. + + + + + + + 0 15 + + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + + NOT_INITIALIZED + + + + + The congestion level of the link. + + + + + + level_0 + + + + + Controls if the Mtp3bSL should be activated at create. + + + + + true + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + +Note! This counter is incremented every time a link out of service indication is received for the link. + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + This action deactivates the signalling link. + It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + This action activates the signalling link with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + This action activates the signalling link with emergency alignment. + It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + This action inhibits the Mtp3bSlAnsi. Signalling link management inhibiting is requested by management when it becomes necessary, e.g for maintenance or testing purposes to make or keep a signalling link unavailable to User Part-generated signalling traffic. +Inhibiting of a signalling link may be requested by management function at either end of the link. The request is granted, provided that the inhibiting action does not cause any previously accessible destinations to become inaccessible at either end of the signalling link. The request may also be refused under certain circumstances such as congestion. +Exception FroRequestFailed if it was not possible to inhibit. + +Note! This action requires a transaction. + + + + + + + + This action uninhibits the Mtp3bSlAnsi. + +Exception FrorequestFailed if it was not possible to uninhibit. + +Note! This action requires a transaction. + + + + + + + + + + This MO represents an MTP3b Signalling Link for the ITU standard. It represents the termination of the signalling link within the signalling point as defined in Q.704 and Q.2210 (07/96). + +The total amount of links between any two specific nodes in the network shall not be more than 16, independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. + +The performance monitoring counters found in Mtp3SlItu MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ITU standard. + + User label for free use. + + + "" + + + + + The tpId attribute points out the termination point of the lower layer protocol. + +For narrowband this signalling link will be connected to an MTP L2 termination point (Mtp2Tp MO). And for broadband it will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + This attribute reflects the operational status of the Mtp3bSl. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The link state of the Mtp3bSl. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + The signalling link code, SLC, used for this link. +The signLinkCode for a link must be unique between the nodes, +independent on in which linkSet the link belongs. + + + + + + + 0 15 + + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + + NOT_INITIALIZED + + + + + The congestion level of the link. + + + + + + level_0 + + + + + Controls if the Mtp3b Signalling Link should be activated at create. + + + + + true + + + + + This Boolean tells if the message priority shall be inserted in an octet before the Service Indicator Octet (SIO). + +ITU default is false. + + + + false + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + +Note! This counter is incremented every time a link out of service indication is received for the link. + + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + + + + + + + + + This action inhibits the Mtp3bSlItu. Signalling link management inhibiting is requested by management when it becomes necessary, e.g for maintenance or testing purposes to make or keep a signalling link unavailable to User Part-generated signalling traffic. +Inhibiting of a signalling link may be requested by management function at either end of the link. The request is granted, provided that the inhibiting action does not cause any previously accessible destinations to become inaccessible at either end of the signalling link. The request may also be refused under certain circumstances such as congestion. +Exception FroRequestFailed if it was not possible to inhibit. + +Note! This action requires a transaction. + + + + + + + + This action uninhibits the Mtp3bSlItu. + +Exception FrorequestFailed if it was not possible to uninhibit. + +Note! This action requires a transaction. + + + + + + + This action deactivates the Mtp3bSl. +It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + This action activates the Mtp3bSl with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + This action activates the Mtp3bSl with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + + + This MO represents an MTP3b Signalling Link for the TTC standard. It represents the termination of the signalling link within the signalling point as defined in JT-Q.704 Ver. 3, April 28 1992 and JT-Q.2210 Ver.1 April 24 1996. + +The total amount of links between any two specific nodes in the network shall not be more than 16, independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. + +The performance monitoring counters found in Mtp3SlTtc MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the TTC standard. + + User label for free use. + + + "" + + + + + The tpId attribute points out the termination point of the lower layer protocol. Only BroadBand is supported for TTC. The MO will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + This attribute reflects the operational status of the Mtp3bSl. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The link state of the Mtp3bSl. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + The signalling link code, SLC, used for this link. +The code have to be uniqe in this signal link set, i.e the signallingLinkCode for +all the Mtp3bSl that belongs to the same Mtp3bSls must be unique(mutual exclusive). + + + + + + + 0 15 + + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + + NOT_INITIALIZED + + + + + The congestion level of the link. + + + + + + level_0 + + + + + Controls if the Mtp3b Signalling Link should be activated at create. + + + + + true + + + + + This Boolean tells if the message priority shall be inserted in an octet before the Service Indicator Octet (SIO). + + + + + true + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + + + + + + + + + This action deactivates the Mtp3bSl. +It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + + + This action activates the signalling link with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + + + This action activates the signalling link with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + + + + + The MTP 2 Profile MO represents and keeps attribute values used by one or more MTP 2 ANSI termination point MOs. + + This MOs user label. + + + "" + + + + + + + + + + + + + Struct containing profile data. + + + + + + + + List of Mtp2TpAnsi MOs that have reserved this Mtp2TpProfileAnsi MO. + + + + + + + + + + + + The MTP 2 Profile MO represents and keeps attribute values used by one or more MTP 2 ITU termination point MOs. + + The MOs user label. + + + "" + + + + + + + + + + + + + Struct containing profile data. + + + + + + + + List of Mtp2TpItu MOs that have reserved this Mtp2TpProfileItu MO. + + + + + + + + + + + + This MO represents a channelised E1 interface in the node. The E1Ttp (Trail Termination Point) MO +does not define which type of traffic (TDM or ATM) that the interface should support. Please refer to +the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +The performance monitoring counters in the E1Ttp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! This MO is automatically created as a consequence of creating an Os155SpiTtpMo +Please refer to the Os155SpiTtpMo for more details. + + + + + The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + + + + + 0 100 + + 30 + + + + + How many bad seconds in a row that causes a Degraded Signal alarm. + + + + + + + 2 10 + + 7 + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates what Cyclical Redundancy Check 4 Mode that is being used. + + + AUTOMATIC + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + The operational state. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter of Errored Seconds (ES). + + + + + + 0 + + + + + Performance monitoring counter for Severely Errored Seconds. + + + + + + 0 + + + + + User label for free use. + + + "" + + + + + + + + + + + + + The identityof the reserving MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO is automatically created as a consequence of creating an Os155SpiTtp object if any of the following conditions are true: +a) standardmode = ETSI or +b) standardmode = TTC and muxmode = VC4_STS3CSPE_LEVEL. + +It represents the termination of the SDH VC-4 path layer. The VC-4 can either be used for channelised access, in which case VC-12 MOs are created as children to the Vc4Ttp MO, or be used to carry ATM traffic, in which case there is a relationship between the AtmPort MO and the Vc4Ttp MO. + +Note! The performance monitoring counters in the Vc4TtpMO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + Indicates the format of the expectedPathtrace and transmittedPathtrace attributes. The format may be in 16 or 64 characters. Usually 16 is used for ETSI and 64 for ANSI/TTC. + +ITU_T_G707=16 +GR_253_CORE=64 + +Note that the 16 characters format requires the operator to specify 15 characters where no character contains the null character (the 16th character is added automatically). + +Note that the 64 characters format requires the operator to specify 62 ASCII characters all different from null followed by CR/LF. + + + ITU_T_G707 + + + + + The transmitted path trace. +Can be defined in two formats. The format may be in 16 or 64 characters. Usually 16 is used for ETSI and 64 for ANSI/TTC. + +Note: The string must be of 15 or 62 characters length, or empty string (""). + + + + + + 0 64 + + "" + + + + + Expected path trace. + +The string can be of 15 or 62 characters length, or empty string (""). + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. This attribute is set to empty string every time attribute pathTraceFormat is set. + + + + + + 0 64 + + "" + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + This threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +The attribute value is in unit of % (percent). + + + + 0 100 + + 30 + + + + + Indicates how many bad seconds in a row that causes a Degraded Signal alarm. + + + + 2 10 + + 7 + + + + + AU AIS reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + VC RDI reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + The operational state. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for Virtual Container 4, VC4, Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Virtual Container 4, VC4, Severely Errored Seconds, SES. + + + + + + 0 + + + + + User label for free use. + + + "" + + + + + + + + + + + + + The identity of the reserving MO. + + + + + + + + + + This MO represents the physical interface and the termination of the SDH Regenerator and Multiplexer Section Layers. + +When creating the Os155SpiTtp a number of additional objects will be created. Depending on the values of standardmode and muxmode different objects will be created as described below: + +muxmode = standby +standardmode = ETSI, TTC, ANSI +No objects under the Os155SpiTtp is created. + +muxmode = VC4_STS3CSPE_LEVEL +standardmode = ETSI, TTC +A Vc4 MO is created under the Os155SpiTtp MO. + +muxmode = VC4_STS3CSPE_LEVEL +standardmode = ANSI +A Sts3CspeTtp MO is created under the Os155SpiTtp MO. + +The following two configurations is only applicable for the ET-MC41 board. + +muxmode = E1_J1_T1_LEVEL +standardmode = ETSI +A Vc4 MO, 63 Vc12Ttp MO's and 63 E1Ttp MO's is created under the Os155SpiTtp MO + +muxmode = E1_J1_T1_LEVEL +standardmode = ANSI +3 Sts1CspeTtp MO's, 3*28 Vt15Ttp MO's and 3*28 TiTtp MO's is created under the Os155SpiTtp MO. + +The performance monitoring counters in the Os155SpiTtp MO is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! If the Os155SpiTtp is configured as part of an Mspg protection group and is configured as standby, muxMode set to standby, no children's to this MO will be created. + + + + + + + + + + The actual line number. + + + + + + + + 1 2 + + + + + + The standard that this MO is operating to. + + + + + + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The level at which the STM-1/OC3 signal is demultiplexed. + +If parent is of type Etmc41, the valid muxMode is STANDBY or E1_J1_T1_LEVEL. +If parent is of type Etm4, the valid muxMode is STANDBY or VC4_STS3CSPE_LEVEL. + + + + + + + + + + MS - multiplexer section. + +The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + +Note: When operating to the ANSI standard, this attribute has no meaning. + + + + + 0 100 + + 30 + + + + + MS - multiplexer section. + +How many bad seconds in a row that causes a Degraded Signal alarm. + +Note: When operating to the ANSI standard, this attribute has no meaning. + + + + 2 10 + + 7 + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Enables or disables line loopback, i.e. the received signal is returned in the transmitted direction. + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + NONE + + + + + The administrative state. + + + locked + + + + + The operational state. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for Multiplexer Section, MS, Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Multiplexer Section, MS, Severely Errored Seconds, SES. + + + + + + 0 + + + + + List of reserving MOs. + + + + + + + + + + User label for free use. + + + "" + + + + + The identity of the reserving Synchronization MO. + + + + + + + + + + This MO is automatically created when the configuring the Os155SpiTtp. It represents the termination of the SDH VC-12 path layer. + +Note: This MO is only valid when the ETSI standard is in use. + +The performance monitoring counters in the Vc12TtpMO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + The transmitted path trace. + +Note: when 16 byte tracing is used, only 15 bytes should be used in the set action for this attribute. + + + + + + + 0 64 + + "" + + + + + Expected path trace. + +Note: when 16 byte tracing is used, only 15 bytes should be used in the set action for this attribute. + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. + + + + + 0 64 + + "" + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + This threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +The attribute value is in unit of % (percent). + + + + 0 100 + + 30 + + + + + Indicates how many bad seconds in a row that causes a Degraded Signal alarm. + + + + 2 10 + + 7 + + + + + Timing Unit Alarm Indication Signal (TU AIS) reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + VC RDI reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + The administrative state. + + + locked + + + + + The operational state. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for Virtual Container 12, VC12, Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Virtual Container 12, VC12, Severely Errored Seconds, SES. + + + + + + 0 + + + + + User label for free use. + + + "" + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + + + This MO represents the hardware of the ET-MC1 board type. It only represents the ET specific hardware, the DBM module of the board is represented by the PlugInUnit MO. + +The ET-MC1 board contains 8 phyiscal ports that can be configured as either E1 (ETSI), J1 (TTC) or T1(ANSI). The board does not allow for a mix of E1, J1 and T1 ports, thus all configured ports on the board must be configured to the same standard. + +Each port on the ET-MC1 board can be used to carry either ATM traffic or circuit orientated (Nx64 Kbits/s connections) traffic. + +Each port can support up to 30 ATM VC connections. Two of these connections are reserved for AAL2 paths, and therefore two AAL2 multiplexers per port are available. + +Each port can support up to 2 VP connections. + +The ET-MC1 port supports one bidirectional F4/F5 PM flow per port. + +At the VP/VC endpoints, the Lost FPM/BR cells counters are not available. + +Note! The ETMC1 supports IMA. + +For more details on restrictions please refer to 155 17-21/CSX 101 09 Uen. + +Note! When the Etmc1 is part of the Cbu it is only possible to configure 4 physical ports of type E1, J1 or T1 on the Etmc1 board. + + User label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the ETMC1 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + This MO represents the hardware of the ET-MC41 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-MC41 board contains a 155 Mbits/s physical optical port. The board can be configured as a E1 channelised board providing 63 logical E1 interfaces. + +Each E1 logical channel on the ET-MC41 can be used to carry either ATM traffic or circuit oriented (Nx64 kbit/s) traffic. + +Each E1 logical channel can support up to 30 ATM VC connections. Two of these connections are reserved for aal2 paths, and therefore two AAL2 multiplexers per E1/DS1/J1 channel are available. + +Each E1/DS1/J1 channel can suport up to 2 VP connections. + +The ET-MC41 board support one biderectional F4/F5 PM flow per E1 channel. + +Note! The ETMC41 supports IMA. However the E1 ports being part of the same IMA group can not be selected randomly. + +Note! The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 1 / port + +For more details on restrictions please refer to 155 17-21/CSX 101 09 Uen. + + User label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the ET-MC41 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + The MTP2 Profile MO represents and keeps attribute values used by one or more MTP2 China termination point MOs. + + + + + + + + + + + + + + + + + List of Mtp2TpChina MOs that have reserved this Mtp2TpProfileChina MO. + + + + + + + + + + The MOs user label. + + + "" + + + + + + + This MO represents a MTP 2 termination point for the China standard, as defined in GF001-9001, plus supplement 1-3. + +The performance monitoring counters found in Mtp2China MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a hardware fault, aal1 server/adm restart or node restart. + +NOTE: This MO cannot in anyway be related (either contained by or dependent on) an MO that belongs to a standard +which is NOT the China standard. + +NOTE: There is a restriction of a maximum of 32 Mtp2Tp's per MP. + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + Reference to a Mtp2ProfileChina MO. + +Note: The bitRate can not be changed. + + + + + + + + + + + + + + + + The operational state of the MTP2 Signalling Terminal. + + + + + + disabled + + + + + Total time in local SIB (Sending). + + + + + + 0 + + + + + Number of MSUs transmitted. + + + + + + 0 + + + + + Number of negative acknowledgements received. + + + + + + 0 + + + + + Number of signal units received in error. + + + + + + 0 + + + + + Number of re-transmitted octets. + + + + + + 0 + + + + + Number of octets in send buffer. + + + + + + 0 + + + + + Number of SIO and SIF octets received. + + + + + + 0 + + + + + Number of SIO & SIF octets transmitted. + + + + + + 0 + + + + + Number of started local RB congestions. + + + + + + 0 + + + + + Total time in remote SIB (Receiving). + + + + + + 0 + + + + + List of reserving MO. + + + + + + + + Free tag for marking this managed object. + + + "" + + + + + The PlugInUnit MO that this MO references. +It indicates on which processor the Termination Point will be. + +Note: The PlugInUnit must be of type GPB. + + + + + + + + + Number of MSUs received.. + + + + + + 0 + + + + + + + This MO represents an MTP3b Signalling Link for the China standard. It represents the termination of the signalling link within the signalling point as defined in GF001-9001, plus supplement 1-3. + +The total amount of links between any two specific nodes in the network shall not be more than 16, independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. + +The performance monitoring counters found in Mtp3SlChina MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard that is NOT the China standard. + + + + + + + + + + User label for free use. + + + "" + + + + + This attribute reflects the operational status of the Mtp3bSl. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Controls if the Mtp3b Signalling Link should be activated at create. + + + + + true + + + + + The congestion level of the link. + + + + + + level_0 + + + + + The link state of the Mtp3bSl. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + This Boolean tells if the message priority shall be inserted in an octet before the Service Indicator Octet (SIO). + +China default is false. + + + false + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + NOT_INITIALIZED + + + + + The signalling link code, SLC, used for this link. +The signLinkCode for a link must be unique between the nodes, +independent on in which linkSet the link belongs. + + + + + + + 0 15 + + + + + + The tpId attribute points out the termination point of the lower layer protocol. + +For narrowband this signalling link will be connected to an MTP L2 termination point (Mtp2Tp MO). And for broadband it will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + +Note! This counter is incremented every time a link out of service indication is received for the link. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + This action activates the Mtp3bSl with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + This action deactivates the Mtp3bSl. +It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + This action activates the Mtp3bSl with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + This action inhibits the Mtp3bSlChina. Signalling link management inhibiting is requested by management when it becomes necessary, e.g for maintenance or testing purposes to make or keep a signalling link unavailable to User Part-generated signalling traffic. +Inhibiting of a signalling link may be requested by management function at either end of the link. The request is granted, provided that the inhibiting action does not cause any previously accessible destinations to become inaccessible at either end of the signalling link. The request may also be refused under certain circumstances such as congestion. +Exception FroRequestFailed if it was not possible to inhibit. + +Note! This action requires a transaction. + + + + + + + + This action uninhibits the Mtp3bSlItu. + +Exception FrorequestFailed if it was not possible to uninhibit. + +Note! This action requires a transaction. + + + + + + + + + Mtp3b Signalling Point for the China standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the China standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpChina MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the China standard. + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + + + + + + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The network indicator, NI, is used for discrimination of messages between functionally different networks. + + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + The sendSltmBefLink attribute determines if the SLTM (Signalling Link Test Message) should be sent and a SLTA received before the link is considered to be in service. + +Note! It is not recommended nor is it in accordance with standard to set the value of this attribute to 'false' + + + true + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 24)-1 (16777215). +The SignallingPointCode (SPC) is nornally used as a whole unique number (no internal structure). But sometimes the SPC is grouped together as three numbers which corresponds to zone, area/network, signalling point. If this is the case the three numbers are coded as 8-8-8 bits in the total SPC. To enter the SPC-value then you have to convert the three numbers to their binary code and then convert the whole 24-bit pattern as an integer. + + + + + + + + 1 16777215 + + + + + + The nodeBehaviour attribute represents the MTP3b node type. + + + + + + SEP + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 1 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The sioSpare attribute determines if the two spare bits in the SIO (Service Information Octet) should be treated as spare. + + + SPARE + + + + + Struct containing the priority attributes. + +Note: The China and ITU priorityData is identical so the ItuPriorityData is used for China to avoid duplication of data. + + + + + + Struct containing China specific timer attributes + + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +Minimum string length 2 characters, maximum 30 characters. Allowed characters are 0-9, A-F. +Only even number of characters is allowed. + + + + + + 2 30 + + "A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5" + + + + + Determines if a TransFer Restricted signal (TFR) should be treated as a TFA (TransFer Allowed signal) or be ignored. + + + + IGNORED + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + User label for free use. + + + "" + + + + + For M3UA, number of attempts to send the DAUD message. + + + + 1 65535 + + 5 + + + + + Number of attempts to send the SCTP_ASSOCIATE_REQ message. + + + + 0 65535 + + 4 + + + + + This attribute shows what MTP3b ITU standard the system follows. With ITU, it is possible using this attribute to set which of the ITU standard versions that shall be followed. + +Note! Setting of another value than 'ITU_T_07_96' at create will have no effect. The Signaling Point will always be created with the value 'ITU_T_07_96'. + +Note! It is not possible to hav signaling points with different versions in the node so setting of this attribute will effect all signaling points. The value for the last created or changed signaling point will be used for all signaling points. + + + + + ITU_T_07_96 + + + + + Performance management counter for number of received CBA messages. + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + 0 + + + + + Performance monitoring counter for number of times the timer T21 was started (i.e. adjacent SP restarted). + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + The number of successful abortions of signalling associations. + + + + + 0 + + + + + The number of succesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of unsuccessful abortions of signalling associations. + + + + + 0 + + + + + The number of unsuccesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of incoming request for association establishment when state on the association is 'DOWN' and establishment of associations is blocked. + + + + + 0 + + + + + The number of times that the max limit for trying to establish an association has been reached. + + + + + 0 + + + + + The number of times that the max limit for trying to activate an association has been reached. + + + + + 0 + + + + + The number of messages with low priority that has been discarded. + + + + + 0 + + + + + + + The MSPG (Multiplex Section Protection Group) object enables two different protection mechanism in Cello. First it enables a standard 1+1 MSP mechanism. A failure on the working line will thus cause a sub 50 ms switch to the standby line. +Secondly the MSPG is used to enable equipment protection, whereas a failure of the working board will cause a switch to the standby board. While executing an equipment protection switch, the node on the other end of the multiplexer section, will experience a standard 1+1 MSP switch. + +It is possible to force traffic to one port/board by using administrative state. +Setting administrative state to locked on the working board, will automatically cause an equipment switch to the standby board. Similarily setting administrative state to locked on the working port, will cause an MSP switch to the standby port. + +The process of configuring a MSP protection interface is as follows: +1) Create the working interface as normal. +2) Create the standby interface by creating an Os155SpiTtp with mux mode set to STANDBY (standby for protection). +3) Create a MSPG object with references to the two Os155SpiTtp objects. + +Note! The ports selected for MSPG must be have the attribute standardMode configured in exactly the same way. + +Note! The Os155SpiTtp created for standby will not create any children, i.e no Vc4Ttp or Vc4Ttp, Vc12Ttp and E1Ttp will be created. Nor will object of type Sts1SpeTtp, Vt15Ttp or T1Ttp be created. + + The working OS155 pyhiscal path termination. +This is the administrative value. + +To retrive the Id of the current working port, use the selectedPort. + + + + + + + + + The standby OS155 physical path termination. +This is the administrative value. + + + + + + + + + The switching mode. + + + + + AUTOMATIC + + + + + The operational state of the Mspg. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + User label for free use. + + + "" + + + + + + + + + + + + + The port currently selected by the MSPG. The selected port can only +change due to a MSP or equipment switch. + + + + + + + + The board currently providing the user traffic interface to the Cello switch. +The only action that can change the selected board is an equipment switch. + + + + + + + + If set to true, then a swith is performed upon detection of DEG. + + + false + + + + + Initiates a switch when there does not exist a defect. + +This action can fail for the following reasons: +FailedResource - the switch was not possible due to a traffic affecting fault on the port to which the switch was requested (i.e. the one not currently selected). +LockedResource - the port to which the switch is intended is administratively locked. +UnknownReason - there exists another fault that prevents the action. + +Note! This action requires a transaction. + + + + + + + + + + + This MO represents an T1 (i.e. 1.5 Mbit/s) physical interface in the node. The T1PhysPathTerm MO does not define which type of traffic (TDM or ATM) that the interface should support. +Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + + + + User label for free use. + + + "" + + + + + + + + + + + + + The actual Line number on the board. + + + + + + + + 1 8 + + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + The administrative state. + + + locked + + + + + Performance monitoring counter for Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Severly Errored Seconds, SES. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + Enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + The type of transmission media. +Refer to the TransmissionMode enumeration for details. + + + + + S_133 + + + + + The identity of the reserving Synchronization MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + IMA, Inverse Multiplexing for ATM, makes it possible to group several physical +interfaces together to form a virtual physical pipe for atm. The capacity of this +pipe is equal to the sum of each of the physical interfaces included in the +group. + +When IMA should be configured, an ATMPort MO is created with reference to an +IMAGroup MO rather than a pure physical interface MO. +The IMAGroup MO in turn is created with a list of the physical port MO's that +are included in the group. The physical port MO's must be of the same type +and be located on the same ET board. + +For each of the physical port MO's included in the IMAGroup, an IMALink object +is automatically created. The IMALink object is responsible for handling link +specific performance and fault management related to IMA. + +The ports can be of type E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp, T1Ttp. + +The performance monitoring counters in the ImaGroup MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! A general restriction in Cello is that ports being part of the same IMA group +must be located on the same board. + +Note! Only termination points on Etmc1 and Etmc41 boards are allowed as ImaLinks. + +Note! At least two links has to be configured in an Ima Group. + + The identity of the MO. + + + + + + + + + Label free for use. + + + "" + + + + + Holds a list of the physical ports connected to the ImaGroup. +Can be of type: +E1PhysPathTerm, +J1PhysPathTerm, +T1PhysPathTerm, +E1Ttp, +T1Ttp. + + + + + + + + + + The required number of links specifies the number of IMALinks that needs to be +operational in order for the complete group to be operational. The bandwidth +available for the ATMPort (and thus for creating VP/VC connections) is defined +by this number. +Setting the requiredNumberOfLinks field to K less than the number of physical +links included in the IMAGroup, will reduce the bandwidth available to the atmport +with the corresponding bandwidth but will also give the effect that K links +failures can be tolerated with virtually no traffic disturbance. + + + + 1 8 + + 1 + + + + + The number of active links in the ImaGroup. + + + + + 0 + + + + + Enabled or disabled according to the actual operational state of the ImaGroup. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This performance counter reflects the GrUasLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the GrFc attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the GrFcFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + The identity of the reserving MO. + + + + + + + + + + This MO is automatically created as a consequence of creating an IMAGroup or +adding links to an IMAGroup. +It provides IMA Link specific performance and fault management information. + +The links can be of type E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp or T1Ttp. + +The performance monitoring counters in the ImaLink MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! A general restriction in Cello is that ports being part of the same IMA group +must be located on the same board. + + Enabled or disabled according to the actual operational state of the ImaLink. +If the operationalState is disabled the ImaLink will be blocked for traffic. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This performance counter reflects the LvLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + Label free for use. + + + "" + + + + + The identity of the MO. + + + + + + + + + This performance counter reflects the OifLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the SesLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the SesLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the UasLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the UasLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxUusLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxUusLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxUusLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxUusLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxFc attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxFc attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxFcFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxFcFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxStuffLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxStuffLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + Reference to the physical port represented by this MO. +Can be of types E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp or T1Ttp. + + + + + + + + + + + This MO represents the termination of the SONET higher order paths. +This MO is automatically created when creating the OS155SPITTP with mux mode +set to VC4_STS3CSPE_LEVEL and standardMode set to ANSI. + +The performance monitoring counters in the Sts3CspeTtp MO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + User label for free use. + + + "" + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + enabled or disabled according to the actual operational state of the Sts3CspeTtp. + + + + + + disabled + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + Expected path trace. + +The string can be of 64 characters length, or empty string (""). +The string shall consist of 62 ASCII characters followed by CR/LF. +The empty string shall be coded with the first character equal to ASCII null (i.e. byte value 0) and the rest dummy or non-existing. + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. This attribute is set to empty string every time attribute pathTraceFormat is set. + + + + 0 64 + + "" + + + + + The transmitted path trace. + +The string shall consist of 62 ASCII characters followed by CR/LF. +The empty string shall be coded with the first character equal to ASCII null (i.e. byte value 0) and the rest dummy or non-existing. + + + + 0 64 + + "" + + + + + Identity of the AtmPort reserving this MO. + + + + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + + + The WebServer MO represents the WebServer in the node. + +This object is used for configuration of the WebServer paths. By connecting this object to a +SwAllocation MO that is connected to a Repertoire MO the WebServer paths will be +automatically configured during system upgrade. + +The local distinguished name of this MO is ManagedElement=1, WebServer=1. + +The WebServer MO is created automatically by the system. + + + + + + + + + + + Label free for use. + + + "" + + + + + Paths that shall be used by the WebServer separated by the delimiter character ":". + + + "" + + + + + List of reserving MOs. + + + + + + + + + + + + This MO represents the Auto Configuration feature for the IpAccessHost's in Cello. + + + + + + + + + + + + Label for free use. + + + "" + + + + + Hold a list of the identitys of the reserving IpAccessHost's. + + + + + + + + + + The network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + + + + + + + 0 32 + + + + + + The number of addresses in the range that are not used. + + + + + 0 + + + + + The total number of addresses in the range. + +Note that the first address in the range will be the same one as the one for networkAddress. + + + + + 0 + + + + + The lowest value that can be used as host IP address. If autoConfig=ON for an IpAccessHost, the operator does not explicitly have to assign an Ip Address and prefixLength to the host. This is done by the Control Plane, based on the IpAccesAutoConfig identity specified for the IpAccessHost. + + + + + + + + + The highest value that can be used as host IP address. If autoConfig=ON for an IpAccessHost, the operator does not explicitly have to assign an Ip Address and prefixLength to the host. This is done by the Control Plane, based on the IpAccesAutoConfig identity specified for the IpAccessHost. + + + + + + + + + + + This MO represents the Ip Access Host used for payload. This host type executes on a MSB board (Media Stream Board used by Media Gateway). + +Note! If autoConfig is set to ON, the Ip Addresses and the Prefixes for this MO is set by the IpAccessAutoConfig MO. + +Note! There can be a maximum of 128 host's in the node. + +Note! The references to Aal5TpVccTp MO's has to be set in pairs. + +Note! The IpAccessMsbHost must execute on the sam MP as the Aal5TpVccTp that are defined in the attributes 'aal5TpVccTpRef1' and 'aal5TpVccTpRef2'. + +Note! The 'administrativeState' has to be set to LOCKED in order to be able to delete this host. + + Label for free use. + + + "" + + + + + The operational state of the Ip Access Host. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + DEGRADED + + + + + The administrative state of the Ip Access Host. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + 10 + + + + + The identity of the DSP (Digital Signalling Processor) on a MSB board. + +Note! The value of this attribute has to be unique among the host's that execute on the same board. + + + + + + + + 1 16 + + + + + + Holds a reference to an Aal5 termination point (Aal5TpVccTp MO). + +Note! The Aal5TpVccTp references are mutually exclusive. + + + + + + + + + Holds a reference to an Aal5 termination point (Aal5TpVccTp MO). + +Note! The Aal5TpVccTp references are mutually exclusive. + + + + + + + + + This attribute specifies whether the auto configuration feature for the Ip Access Host is used or not. + + + + + OFF + + + + + The identity of the IpAccessAutoConfig MO used by this host. + +Note! This attribute can only be set if 'autoConfig' is set to 'ON'. + + + + + + + + The IpAddress. + +Note! If autoConfig = OFF this attribute is mandatory. + +Note! If the autoConfiguration is used for this IpAccessHost (autoConfig = ON) this attribute cannot be set. This attribute is then set by the 'IpAccessAutoConfig MO'. + +Note! The IpAddress has to be unique within the node. + + + + + "" + + + + + The network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + +Note! If auto configuration is used (autoConfig = ON) this attribute cannot be set, the networkPrefix is then set in the ipAccessAutoConfig MO class. + +Note! If auto configuration is not used (autoConfig = OFF) this attribute must be set. + + + + + + + 0 32 + + + + + + The link Status for Ip Address. + + + + + + disabled + + + + + The maximum transfer unit. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + + + 72 2048 + + 1024 + + + + + The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, +whenever a TTL value is not supplied by the transport layer protocol. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + 1 255 + + 50 + + + + + The total number of input datagrams received from interfaces, including those received in error. + + + + + + 0 + + + + + The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number +mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc. + + + + + + 0 + + + + + The number of input datagrams discarded because the IP address in their IP header's destination field was not a +valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of +unsupported Classes (e.g., Class E). For entities which are not IP routers and therefore do not forward datagrams, +this counter includes datagrams discarded because the destination address was not a local address. + + + + + + 0 + + + + + The number of locally-addressed datagrams received successfully but discarded because of an unknown or +unsupported protocol. + + + + + + 0 + + + + + The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which +were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while +awaiting re-assembly. + + + + + + 0 + + + + + The total number of input datagrams successfully delivered to IP user-protocols (including ICMP). + + + + + + 0 + + + + + The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for +transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams + + + + + + 0 + + + + + The number of output IP datagrams for which no problem was encountered to prevent their transmission to their +destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include +datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion. + + + + + + 0 + + + + + The total number of ICMP messages which the entity received. +Note that this counter includes all those counted by icmpInErrors + + + + + + 0 + + + + + The number of ICMP messages which the entity received but determined as having +ICMP-specific errors (bad ICMP checksums, bad length, etc.). + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages received. + + + + + + 0 + + + + + The number of ICMP Time Exceeded messages received. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages received. + + + + + + 0 + + + + + The number of ICMP Source Quench messages received. + + + + + + 0 + + + + + The number of ICMP Redirect messages received. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages received. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages received. + + + + + + 0 + + + + + The total number of ICMP messages which this entity attempted to send. +Note that this counter includes all those counted by icmpOutErrors. + + + + + + 0 + + + + + The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of +buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the +resultant datagram. In some implementations there may be no types of error which contribute to this counter's value. + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages sent. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages sent. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages sent. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages sent. + + + + + + 0 + + + + + The total number of UDP datagrams delivered to UDP users. + + + + + + 0 + + + + + The total number of received UDP datagrams for which there was no application at the destination port. + + + + + + 0 + + + + + The number of received UDP datagrams that could not be delivered for +reasons other than the lack of an application at the destination port. + + + + + + 0 + + + + + The total number of UDP datagrams sent from this entity. + + + + + + 0 + + + + + + + + + + + + + The identity of the reserving MO. + + + + + + + + Holds a reference to the PlugInUnit. + +Note that the 'plugInUnitId has to be the same as the one defined in the attribute 'processorId' found on the Aal5TpVccTpMo. + + + + + + + + + + + This MO represents the definitions of properties for a set of Aal2 quality of service classes. + + + + + + + + + + Label for free use. + + + "" + + + + + This attribute holds the values applicable for QoS Class A. + + + + + + + + This attribute holds the values applicable for QoS Class B. + + + + + + + + This attribute holds the values applicable for QoS Class C. + + + + + + + + This attribute holds the values applicable for QoS Class D. + + + + + + + + List of reserving Aal2PathVccTp MOs. + + + + + + + + + + + + This MO represents the QoS CodePoints for the different Aal2 QoS classes. + + + + + + + + + + Label free for use. + + + "" + + + + + The Code Point for Class A. + +Recommended value for Class A, 128. + + + + + + + 0 255 + + + + + + The Code Point for Class B. + +Recommended value for Class B, 129. + + + + + + + 0 255 + + + + + + The Code Point for Class C. + +Recommended value for Class C, 130. + + + + + + + 0 255 + + + + + + The Code Point for Class D. + +Recommended value for Class D, 131. + + + + + + + 0 255 + + + + + + Holds the identity of the reserving Aal2Ap Mo. + + + + + + + + + + + + This MO represents the M3UA Association part of the M3UA (MTP3-User Adaptaion Layer) that is a protocol +for the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services +of the Stream Control Transmission Protocol. + +Note that the local port number is hard coded to 2905. + + + + + + + + + + + + + Label free for use. + + + "" + + + + + Holds a list of the reserving Signaling Route's (Mtp3bSr MO). + + + + + + + + + + + The Operational State of the M3Ua + + + + + + disabled + + + + + The identity of the Signalling Route Set used. + + + + + + + + + + The SctpHost used by this association. + + + + + + + + + The DSCP, DiffServCodePoint, for the internal M3UA user. +Only one DSCP value is valid and set by the first defined MO 'instance'. + +NOTE: The value set for the 'dscp' when creating the first M3uAssociation under a signaling point will also be used for all other M3uAssociation MO's that are created under this signaling point. So setting the value for the 'dscp' on other instances than the first one created will have no effect. Note that associations created under a different signaling point can have a different dscp-value. + + + + + + 0 63 + + 0 + + + + + The possible states of an M3Ua association. + +Bit 1 = 1 indicates INACTIVE +Bit 2 = 1 indicates ACTIVE +Bit 3 = 1 indicates ESTABLISHED +Bit 4 = 1 indicates DOWN + +These values are mutually exclusive. + + + + + + 0 15 + + 0 + + + + + This attribute denotes whether single or multi homing is used. + +Note! that all M3uAssociations that refers to the same SCTP MO must have this attribute set to the same value. + +Note! If localipMask=2 or localipMask=3 . the attribute ipAddress2 or autoConfigIdentity2 in IpAccessHostGpb MO must be defined. + + + + + + SINGLE_HOMED_1 + + + + + If true, the M3ua layer in the stack will after a restart, start up all signalling associations. + + + + + true + + + + + The port number of the remote signalling point (SP). + + + + + + 1 65535 + + 2905 + + + + + Remote IpAddress 1, if not used the value should be an empty string. +Range is 0.0.0.0 - 255.255.255.255 + +Note! This address is concidered as the primary IP-address. In case of association establisment failure 'remoteIpAddress2' will be used. + + + + + + + + + Remote IpAddress 2, if not used the value should be an empty string. +Range is 0.0.0.0 - 255.255.255.255 + +Note! This address cannot be the same as remoteIpAddress1. This address is used when trying to establish association in case association attempt using 'remoteIpAddress1' fails. + + + + + "" + + + + + Number of communication losses. + + + + + + 0 + + + + + Number of congestions. + + + + + + 0 + + + + + Number of DUNA messages received through the association. + + + + + + 0 + + + + + Number of DAVA messages received through the association. + + + + + + 0 + + + + + Number of SCON messages received through the association. + + + + + + 0 + + + + + Number of DUPU messages received through the association. + + + + + + 0 + + + + + The number of data messages sent on the associations related to this signalling point. + + + + + 0 + + + + + Number of DUNA messages sent through the association. + + + + + 0 + + + + + Number of DAVA messages sent through the association. + + + + + 0 + + + + + Number of SCON messages sent through the association. + + + + + 0 + + + + + Number of DUPU messages sent through the association. + + + + + 0 + + + + + Number of DATA (payload data) messages received through the association. + + + + + 0 + + + + + Number of ERROR messages received through the association. + + + + + 0 + + + + + Number of ERROR messages sent through the association. + + + + + 0 + + + + + Number of NOTIFY messages received through the association. + + + + + 0 + + + + + The number of daud messages sent on the associations related to this signalling point. + + + + + 0 + + + + + The number of daud messages received on the associations related to this signalling point. + + + + + 0 + + + + + The number of ASPUP sent. + + + + + 0 + + + + + The number of ASPUP received. + + + + + 0 + + + + + The number of ASPDN sent. + + + + + 0 + + + + + The number of ASPDN received. + + + + + 0 + + + + + The number of ASPAC sent. + + + + + 0 + + + + + The number of ASPAC received. + + + + + 0 + + + + + The number of ASPIA sent. + + + + + 0 + + + + + The number of ASPIA received. + + + + + 0 + + + + + The number of ASPUP_Ack sent. + + + + + 0 + + + + + The number of ASPUP_Ack received. + + + + + 0 + + + + + The number of ASPDN_Ack sent. + + + + + 0 + + + + + The number of ASPDN_Ack received. + + + + + 0 + + + + + The number of ASPAC_Ack sent. + + + + + 0 + + + + + The number of ASPAC_Ack received. + + + + + 0 + + + + + The number of ASPIA_Ack sent. + + + + + 0 + + + + + The number of ASPIA_Ack received. + + + + + 0 + + + + + The number of data Messages discarded. + + + + + 0 + + + + + This action starts the association. + +Note! This action requires a transaction. + + + + + + This action stops the association. + +Note! This action requires a transaction. + + + + + + + + This MO represents the SCTP, Stream Control Transmission Protocol in Cello. +SCTP is designed to transport signaling messages over IP networks. + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the Ip Access Host. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The maximum number of M3uAssociations that can be handled by this SCTP MO. + + + + + + + 1 512 + + + + + + Holds a list of the M3Ua's handled by the SCTP. + + + + + + + + + + The identity of the IpAccessHostGbp reserved by this MO. + + + + + + + + + The minimum value for RTO (Retransmission time-out). +The minimumRto shall be larger than tSack + expected Round Trip Time. + +Unit is second/100. + + + + + 4 500 + + 8 + + + + + The maximum value for RTO (Retransmission time-out). + +Unit is second/100. + +maximumRto must be larger than minimumRto. + + + + 4 180000 + + 15 + + + + + The initial value that the RTO (Retransmission time-out) will take prior to the first RTT (Round Trip Time) measure. + +Note that the value for 'initialRto' has to be equal to or greater than 'minimumRto'. + +Unit is seconds/100. + + + + 4 180000 + + 8 + + + + + This parameter is used for computing the value of the SRTT (Smoothed Round Trip Time) for a specific destination +address. Is is used to weight the RTT values, and it's value must be between 0 and 1 (0 < rtoAlpha < 1). A value +close to 1 gives a higher importance to the last RTT measurement. +The range of possible values in the configuration file and the actual value given to this parameter within the module +are the following: + +rtoAlphaIndex = 1 -> RTO-Alpha = 1/2 +rtoAlphaIndex = 2 -> RTO-Alpha = 1/4 +rtoAlphaIndex = 3 -> RTO-Alpha = 1/8 +rtoAlphaIndex = 4 -> RTO-Alpha = 1/16 + + + + 1 4 + + 3 + + + + + This parameter is used for computing the the value of RTTVar (Round Trip Time Variation) of a destination +address. +It's value must be between 0 and 1 (0 < rtoBetaIndex < 1). A value close to 1 gives more importance to the +last observed variation. +The range of possible values in the configuration file and the actual value given to this parameter within the module +are the following: + +rtoBetaIndex = 1 -> RTO-Beta = 1/2 +rtoBetaIndex = 2 -> RTO-Beta = 1/4 +rtoBetaIndex = 3 -> RTO-Beta = 1/8 +rtoBetaIndex = 4 -> RTO-Beta = 1/16 + + + + + 1 4 + + 2 + + + + + This parameter sets up the lifespan of the State Cookie sent in the INIT_ACK chunk. It is used for limiting the +the valid amount of time between sending the INIT_ACK and the reception of a COOKIE_ECHO chunk when +establishing an association. +If a COOKIE_ECHO chunk arrives after 'validCookieLife' has expired when sending an INIT_ACK chunk, the +COOKIE_ECHO shall be discarded and no association will be established. + +Unit is seconds. + + + + 1 180 + + 60 + + + + + The sender of an INIT chunk may request to the remote endpoint a cookie life-span increase (for example, if a previous attempt to +connect failed due to a state-cookie error). If the value sent in the "Cookie Preservative field" of the INIT chunk is less or equal to +this parameter, the reciver of the INIT chunk will increase the 'validCookieLife' with the number of seconds specified. If the value +present in the "Cookie Preservative field" is higher than this parameter, the cookie life should be incremented with the number of +seconds specified by the parameter. + +Unit is seconds. + + + + 0 180 + + 30 + + + + + Defines how often the secret key used for computing the MAC (Message Authentication Code) on the State Cookie is changed. + +Unit is seconds. + + + + 1 180 + + 4 + + + + + This is the maximum number of consecutive retransmissions to a remote peer (on all the destination transport addresses of the peer, if it's multi homed). If the number of retransmissions becomes higher than this value, the remote peer shall be considered unreachable and the association shall be closed down. + +The value of this attribute should be greater than, or equal to the value of the attribute 'pathMaxRtx'. + +Note that for a specific association, it might happen that all the remote addresses (if the the remote end is multi homed) becomes unreachable without exceeding the 'associationMaxRtx'. In such a case the association will be closed down. + +Note! The value need to be increased to avoid frequent CommLost's in case of an unstable network. + + + + 1 20 + + 2 + + + + + Maximum number of consecutive retransmissions to a remote transport address. If the number of retransmissions becomes higher than this value, the remote transport address shall be considered as "inactive" and no data shall be sent to it. If all of the remote transport addresses becomes "inactive", tha association will be closed down. + +Note! The value need to be increased to avoid frequent CommLost's in case of an unstable network. + + + + 1 20 + + 2 + + + + + The maximum nimber of retransmissions allowed for both INIT and COOKIE_ECHO chunks. If the number of retransmissions +exceeds this value, then the SCTP must abort the initialization of the association and report the error to the user. + + + + 1 16 + + 8 + + + + + The maximum number of retransmission during the shutdown phase of an association. + + + + 1 16 + + 5 + + + + + The amount of time added to the RTO (Retransmission Time Out) of a specific address when setting up the period of +time between sending heartbeats. Small values can lead to an earlier detection of unreachable addresses than higher +values. Note that sendig often might lead to performace penalty. + +Unit is seconds. + + + + 1 1800 + + 30 + + + + + This attribute enables/disables heartbeats for associations. + +True = Enables + + + true + + + + + This is the maximum incoming streams (MIS) for an association. Established associations might have an IS less or equal to +this, but it's MIS can never be higher than the value of this attribute. + + + + 1 16384 + + 17 + + + + + The maximum number of outgonig streams for an association. + + + + 1 16384 + + 17 + + + + + The maximum number of bytes a user is allowed to pass as a non fragmentable user data in a SCTP_SEND_REQ message +(fixed user MTU): +The values for this attribute is 'user' data and do not include IP header (20 bytes), SCTP header (12 bytes) or DATA chunk +header (16 bytes). + +Unit is bytes. + + + + 528 65484 + + 1432 + + + + + This attribute sets the size of the buffer used for storing user data pending to be sent or retransmitted in an association. I.e. establish the maximum amount of user data that SCTP shall buffer before discarding user messages. + +The Unit is in kilo bytes. + +Note! The restriction on this attribute is: +mBuffer x number of M3uAssociation MOs connected to this Sctp + 20 Mb <= the heap for Sctp program. + +Note! The value may need to be increased to ensure stable dataflow at high load. + + + + 1 2048 + + 128 + + + + + This attribute sets the value of the threshold used by SCTP to stop the delivery of data on anassociation. +Once nThreshold or more bytes are queued and pending to be sent, the SCTP layer shall issue an indication to the user. +The value of nThreshold should be less than mBuffer in order to be effective. A normal value for nThreshold is 3/4 * mBuffer. + +Unit is kilo bytes. + +Note! The value may need to be increased to ensure stable dataflow at high load. + + + + 1 2048 + + 96 + + + + + The delay of sending the SACK. I.e. the time from DATA chunk reception to Sack chunk sending. + +Unit is second/100 + + + + 2 50 + + 4 + + + + + The maximum number of bytes SCTP shall be able to fetch every time it reads from the socket. + +Note! This value includes the Ip header, 20 bytes. + + + + 1500 65535 + + 8192 + + + + + The value of the initial advertised reciver window. + +Note! The range is 1500 to maxDataSizeIp. + +Unit is bytes. + + + + 1500 65535 + + 8192 + + + + + The number of seconds for the interval for which the counter for out of the blue chunks will be reset. + +Unit is seconds. + + + + 1 6500 + + 3600 + + + + + The number of seconds for the interval for which the SCTP will decide that the SCTP user that lost the +connection is dead. After the time specified in this attribute has elapsed, all associations related to the +SCTP user will be destroyed. + + + + 0 3600 + + 5 + + + + + The number of packages that will be sent during the fast retransmit phase when a SACK is processed. + + + + 1 16384 + + 4 + + + + + The size of 'n' inpercentage when SCTP_CONGESTION_CEASE_IND is sent. At 100 percent the +primitive will buffer usage goes below 'nThreshold'. + + + + 1 100 + + 85 + + + + + This attribute enables/disables the use of bundling. +Valid values: +1: enabled. +0: disabled. + + + + 0 1 + + 1 + + + + + This attribute specifies maximum SCTP bundling delay. +Value=0 means that SCTP will only bundle what is available and send directly (no delay). +Unit is milliseconds + + + + 0 1000 + + 10 + + + + + Number of SCTP associations for which the current state is either ESTABLISHED, SHUTDOWN-PENDING, or SHUTDOWN-RECEIVED. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the COOKIE-ECHOED state. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the CLOSED state. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the CLOSED state from any state using the primitive ABORT. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the CLOSED state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state. + + + + + + 0 + + + + + Number of out of the blue packets (SCTP packet correctly formed-right checksum- but the receiver is not able to identify the association to which this packet belongs) received by the host. + + + + + + 0 + + + + + Number of complete data chunks sent to the peers (no retransmissions included). + + + + + + 0 + + + + + Number of complete data chunks received from the peers (no retransmissions included). + + + + + + 0 + + + + + Number of unordered chunks sent to the peers. + + + + + + 0 + + + + + Number of unordered chunks received from the peers. + + + + + + 0 + + + + + Number of SCTP packets received from the peers with an invalid checksum. + + + + + + 0 + + + + + Number of data chunks retransmitted to the peers. + + + + + + 0 + + + + + Number of datagrams sent with chunk type id > 0. + + + + + + 0 + + + + + Number of datagrams Receivedwith chunk type id > 0. + + + + + + 0 + + + + + Number of fragmented user messages, incremented when the first data chunk of a fragmented message is sent. + + + + + + 0 + + + + + Number of reassembled user messages, incremented when the first data chunk of a fragmented message is received. + + + + + + 0 + + + + + Number of SCTP packages sent. + + + + + + 0 + + + + + Number of SCTP packages Received. + + + + + + 0 + + + + + Number of times the SCTP has sent a communication stop indication to the user. + + + + + + 0 + + + + + Number of times SCTP has sent a communication resume indication to the user. + + + + + + 0 + + + + + Number of sent chunks that SCTP has been forced to drop due to buffer overflow in the sending buffer. + + + + + + 0 + + + + + Number of received chunks that SCTP has been forced to drop due to buffer overflow in the receiving buffer. + + + + + + 0 + + + + + + + This MO represents the termination of the SONET higher order paths. +This MO is automatically created when creating the OS155SPITTP with mux mode +set to E1_J1_T1_LEVEL and standardmode set to ANSI. + +The performance monitoring counters in the Sts1SpeTtp MO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Label free for use. + + + "" + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + enabled or disabled according to the actual operational state of the Sts3CspeTtp. + + + + + + disabled + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + Expected path trace. + +The string can be of 64 characters length, or empty string (""). + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. This attribute is set to empty string every time attribute pathTraceFormat is set. + + + + 0 64 + + "" + + + + + The transmitted path trace. +Can be defined in two formats. The format may be in 16 or 64 characters. Usually 16 is used for ETSI and 64 for ANSI/TTC. + +Note: The string must be of 15 or 62 characters length, or empty string (""). + + + + 0 64 + + "" + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + + + This MO is automatically created when the configuring the Os155SpiTtp. It represents the termination of the SONET VP 1.5 path layer. + +This MO is automatically created when creating the Os155SpiTtp MO with the following conditions: +muxmode = E1_J1_T1_LEVEL +standardmode = ANSI + +The performance monitoring counters in the Vt15Ttp is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + This timer defines the time that elapses before shut down when administrativeState is se to 'shuttingDown'. + + + + 1 100000 + + 1800 + + + + + The operational state of the Vt15Ttp MO. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The administrative state of the Vt15Ttp MO. + + + locked + + + + + Performance monitoring counter of Errored Seconds (ES). + + + + + + 0 + + + + + Performance monitoring counter for Serverely Errored Seconds. + + + + + + 0 + + + + + Label free for use. + + + "" + + + + + + + This MO represents a channelised T1 interface in the node. The T1Ttp MO does not define which type of traffic (TDM or ATM) that the interface should support. Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +The performance monitoring counters in the T1Ttp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! This MO is automatically created as a consequence of creating an Os155SpiTtpMo +Please refer to the Os155SpiTtpMo for more details. + + + + + + + + + + + Label free for use. + + + "" + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The operational state of the T1Ttp MO. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter of Errored Seconds (ES). + + + + + + 0 + + + + + Performance monitoring counter for Serverely Errored Seconds. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO represents an E3 (i.e. 34 Mbit/s) physical interface in the node. Please refer to the AtmPort object for details about configuration of traffic type. + +Note! The performance monitoring counters in the E3PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Label for free use. + + + "" + + + + + The administrative state of the E3PhysPathTerm. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The actual Line number on the board. + + + + + + + 1 2 + + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + + + + 0 100 + + 30 + + + + + How many bad seconds in a row that causes a Degraded Signal alarm. + + + + 2 10 + + 7 + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + The identity of the reserving Synchronization MO. + + + + + + + + + + This MO represents an T3 (i.e. 45 Mbit/s) physical interface in the node. Please refer to the AtmPort object for details about configuration of traffic type. + +Note! The performance monitoring counters in the T3PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Label free for use. + + + "" + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The administrative state of the T3PhysPathTerm MO. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The actual Line number on the board. + + + + + + + 1 2 + + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Performance Monitoring counter for ES, Errored Seconds based on C-bit parity. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES based on C-bit parity. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + The identity of the reserving Synchronization MO. + + + + + + + + + + This MO represents the hardware of the ET-M3 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-M3 board contains 2 physical ports that can be configured as either E3 (ETSI) or T3(ANSI). + +Each port on the ET-M3 board can be used to carry ATM traffic. + +At the VP/VC endpoints, the Lost FPM/BR cells counters are not available. + +IMA is not applicable for theETM3 board. + +The ET-M3 board supports eight bidirectional F4/F5 PM flow per port. + +The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 8/port. + +Each port can support up to 240 ATM VC connections. Sixteen of these connections are reserved for AAL2 paths, and therefore sixteen AAL2 multiplexers per port are available. + +Each port can support up to 16 VP connections. + + + + + + + + + + Enabled or disabled according to the actual operational state of the Etm3 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Label for free use. + + + "" + + + + + + + This Managed Object represents an SCCP Remote Access Point. An SCCP AP instance is a logical point in the SCCP network at which an SCCP user can access the services provided by the SCCP and the SCCP can deliver its services to the SCCP user. The SCCP Remote Access Point is identified by a SubSystem Number (SSN). + +A remote SccpAp represents an access point in another node and is related to a Mtp3bAp MO. + +The performance monitoring counters found in SccpAp MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a shutdown request from the CLI (Cluster Interface). + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the SCCP AP. The operability of the SCCP AP is described by this attribute which has two possible values: + +Disabled: The SCCP AP is totally inoperable and unable to provide the service to the user (e.g. if the MTP-3b AP is not usable). + +Enabled: The SCCP AP is partly or fully operable and available for use. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Holds a list of the reserving MOs. + + + + + + + + + + The identity of the Mtp3bAp used by this MO. + + + + + + + + + The sub system number, SSN, of the SCCP Access Point. Note that this has to be a unique number. + +The SSN has to be unique among all other SccpApRemote MOs that has the same DPC in their corresponding Mtp3bSrs MOs. + + + + + + + 2 255 + + + + + + + + This MO represents the Ip Access Host used for payload. This host type executes on a GPB board (GeneralPocessorUnit). + +Note! If autoConfig is set to ON, the Ip Addresses and the Prefixes for this MO is set by the IpAccessAutoConfig MO. + +Note! There can be a maximum of 128 host's in the node, and only one host on each main processor. + +Note! The host cannot be configured on a MP which have a MediumAccessUnit-child MO. They are exclusive. + +Note! The 'administrativeState' has to be set to LOCKED in order to be able to delete this host. + + + + + + + + + + Label for free use. + + + "" + + + + + The identity of the reserving MO, can be of type Sctp. + + + + + + + + The operational state of the Ip Access Host. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + DEGRADED + + + + + The administrative state of the Ip Access Host. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + 10 + + + + + The link status for IpAddress1. + + + + + + disabled + + + + + The link status for IpAddress2, only valid if 2 IpAddresses are configured for this host. + + + + + + disabled + + + + + Holds a reference to the GPU (GenerelProcessorUnit). + + + + + + + + + This attribute specifies whether the auto configuration feature for the Ip AccessHost is used or not. + + + + + OFF + + + + + The identity of the IpAccessAutoConfig MO used by this host. + +Note! This attribute is mandatory if 'autoConfig' is set to ON. + + + + + + + + The identity of the IpAccessAutoConfig MO used by this host. + +Note! This attribute can only be set if 'autoConfig' is set to 'ON'. This attribute is not neccesary to set if 'autoConfig' is set to ON, unless the host shall have two Ip Addresses automatically assigned. + + + + + + + + The IpAddress. + +Note! If autoConfig = OFF this attribute is mandatory. +Note! If the autoConfiguration is used for this IpAccessHostGpb (autoConfig = ON) this attribute cannot be set. This attribute is then set by the 'IpAccessAutoConfig MO'. +Note! If the attribute is set, its value must not be the same as for attribute ipAddress2. + + + + + "" + + + + + The second IpAddress. + +Note! If autoConfig = OFF this attribute is possible to set. This attribute should only be set if multi-homing is used for this host (i.e. two addresses defined). +Note! If the autoConfiguration is used for this IpAccessHostGpb (autoConfig = ON) this attribute cannot be set. This attribute is then set by the 'IpAccessAutoConfig MO'. +Note! If the attribute is set, its value must not be the same as for attribute 'ipAddress'. + + + + + "" + + + + + Specifies whether path MTU discovery should be used by this host. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + false + + + + + The maximum transfer unit. + +The MTU has a initial value of 1452 if pathMTUDiscovery is set to false. +If pathMTUDiscovery is set to true, the initial value of MTU is 1452. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + 72 2048 + + 1452 + + + + + The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, +whenever a TTL value is not supplied by the transport layer protocol. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + 1 255 + + 50 + + + + + The maximum number of seconds which received fragments are +held while they are awaiting reassembly at this entity. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + +Note! The value for this attribute has to be positive. + + + 300 + + + + + The next hop IP address. + + + + + + + + + The secondary next hop IP address. + +Note! This attribute must only be set if one of the following conditions are fulfilled: +1. Attribute 'ipAddress2' is set. +2. Attribute 'autoConfig' = 'ON' and attribute 'autoConfigIdentity2' is set. + + + + + "" + + + + + The network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + +Note! The default value 0 (zero) is most likely not possible to use and an other value should be submitted if this attribute is configured manually. +Note! If auto configuration is not used (autoConfig = OFF) this attribute must be set (i.e. this attribute is then 'mandatory'). +Note! If auto configuration is used (autoConfig = ON) this attribute cannot be set, networkPrefix is then set by the ipAccessAutoConfig MO class. + + + + + + + 0 32 + + 0 + + + + + The second network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + +Note! The default value 0 (zero) is most likely not possible to use and an other value should be submitted if this attribute is configured manually. +Note! If auto configuration is not used (autoConfig = OFF) and ipAddress2 is set this attribute must be set (i.e. this attribute is then 'mandatory'). +Note! If auto configuration is used (autoConfig = ON) this attribute cannot be set, networkPrefix2 is then set by the ipAccessAutoConfig MO class. + + + + + + 0 32 + + 0 + + + + + The total number of input datagrams received from interfaces, including those received in error. + + + + + + 0 + + + + + The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number +mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc. + + + + + + 0 + + + + + The number of input datagrams discarded because the IP address in their IP header's destination field was not a +valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of +unsupported Classes (e.g., Class E). For entities which are not IP routers and therefore do not forward datagrams, +this counter includes datagrams discarded because the destination address was not a local address. + + + + + + 0 + + + + + The number of locally-addressed datagrams received successfully but discarded because of an unknown or +unsupported protocol. + + + + + + 0 + + + + + The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which +were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while +awaiting re-assembly. + + + + + + 0 + + + + + The total number of input datagrams successfully delivered to IP user-protocols (including ICMP). + + + + + + 0 + + + + + The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for +transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams + + + + + + 0 + + + + + The number of output IP datagrams for which no problem was encountered to prevent their transmission to their +destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include +datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion. + + + + + + 0 + + + + + The number of IP fragments received which needed to be reassembled at this entity. + + + + + + + 0 + + + + + The number of IP datagrams successfully re-assembled. + + + + + + + 0 + + + + + The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc). +Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm +in RFC 815) can lose track of the number of fragments by combining them as they are received. + + + + + + + 0 + + + + + The number of IP datagrams that have been successfully fragmented at this entity. + + + + + + + 0 + + + + + The number of IP datagrams that have been discarded because they needed to be fragmented +at this entity but could not be, e.g., because their Don't Fragment flag was set. + + + + + + + 0 + + + + + The number of IP datagram fragments that have been generated as a result of fragmentation at this entity. + + + + + + + 0 + + + + + The total number of ICMP messages which the entityreceived. +Note that this counter includes all those counted by icmpInErrors + + + + + + 0 + + + + + The number of ICMP messages which the entity received but determined as having +ICMP-specific errors (bad ICMP checksums, bad length, etc.). + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages received. + + + + + + 0 + + + + + The number of ICMP Time Exceeded messages received. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages received. + + + + + + 0 + + + + + The number of ICMP Source Quench messages received. + + + + + + 0 + + + + + The number of ICMP Redirect messages received. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages received. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages received. + + + + + + 0 + + + + + The total number of ICMP messages which this entity attempted to send. +Note that this counter includes all those counted by icmpOutErrors. + + + + + + 0 + + + + + The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of +buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the +resultant datagram. In some implementations there may be no types of error which contribute to this counter's value. + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages sent. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages sent. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages sent. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages sent. + + + + + + 0 + + + + + The total number of UDP datagrams delivered to UDP users. + + + + + + 0 + + + + + The total number of received UDP datagrams for which there was no application at the destination port. + + + + + + 0 + + + + + The number of received UDP datagrams that could not be delivered for +reasons other than the lack of an application at the destination port. + + + + + + 0 + + + + + The total number of UDP datagrams sent from this entity. + + + + + + 0 + + + + + Performance monitoring counter for the number of input unicast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of out unicast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to any error. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of input broadcast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input multicast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of output broadcast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of output multicast packets delivered to higher layer. + + + + + + 0 + + + + + + + This MO structures the SystemFunctions of the managed element. It is created automatically and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, SystemFunctions=1. + + + Label free for use. + + + "" + + + + + + + + + + + + + + + This MO represents the Licensing (Software Keys) functions in Cello. + + + + + + + + + + + Label free for use. + + + "" + + + + + This attribute holds information about the emergency status and the time remaining in the current state. + +Note! If the node is in emergency state USE_DEGRADED, or the emergency state is USE_DISABLED, the the value of'time' is insignificant. + + + + + + + + This attribute returns the URL to the License Key File so it can be viewed with an XML capable web browser +in case this is a licensed node. + +Note! In case the node is not licensed, an empty string will be returned. + + + + + + 0 256 + + "" + + + + + This action sends a request to the FTP/SFTP server to update the license key file. + +User Id for login to FTP/SFTP server where license key files are located. +If a null string userId is given, anonymous FTP/SFTP transfer is assumed. +Max length is 20 characters. + +Password for login to the FTP/SFTP server where license key files are located. +Max length is 20 characters. + +The IpAddress of the FTP/SFTP server where license key files are located. +Max length is 16 characters. + +Source name and path of the license key file on the FTP/SFTP server. +Max length is 256 charcters. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This action sets the license server into emergency state. +I.e. opens up all licensed features and capacity restrictions. +Disabling emergency state is done by loading a new license key file. + +Note! This action does not require a transaction. + + + + + + + + This MO represents a timing unit2 (reference clock) in the node. + +The corresponding Program shall be of LoadModuleLoaderType, SpmFpgaLoader. + + Label for free use. + + + "" + + + + + Operational state of TimingUnit + + + + + + disabled + + + + + The availability status of the TimingUnit. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + The SccpPolicing MO represents the policing function in CPP. + +The originatingMtp3bSpc is a madatory attribute for policing in one local node (i.e. a SRP in one NI). +For policing between two local nodes (i.e. a SRP between two NIs) the originatingMtp3bSpc can be replaced by the originatingSccpSpId. +Optional attributes for policing in one local node (i.e a SRP in one NI) are destinationMtp3bSpc, destinationSccpSsn, originatingSccpSsn and policingGlobalTitle. +For policing between two local nodes (i.e. a SRP between two NIs) the destinationMtp3bSpc can be replaced by the destinationSccpSpId. + + + + + + + + + + Label free for use. + + + "" + + + + + The value of the SPC (Signaling Point Code). + +Note! If the 'originatingSccpSpId' is specified the 'originatingMtp3bSpc' is invalid. + + + + + + + 0 16777215 + + 0 + + + + + The value of the destination SPC (Signaling Point Code). + +Note! The default value 0 (zero) means that no SPC is defined. +Note! If no 'destinationSccpSp' is defined and the value of 'destinationMtp3bSpc' is set to 0 (zero), all Signalling Point Codes (SPC) are valid. + + + + + + 0 16777215 + + 0 + + + + + The identity of the originating SccpSp MO must be used for policing between local nodes. + +Note! If the 'originatingSccpSpId' is specified the 'originatingMtp3bSpc' is invalid. + + + + + + + + + The value of SSN in CgPA (Calling Party Address) + +Note! The value 0 (zero) means that all ssN (Sub System Number) are valid. + + + + + + 0 + + + + + The identity of the destination SccpSp MO can be used for policing between local nodes. + +Note! If the 'destinationSccpSpId' is specified the 'destinationMtp3bSpc' is invalid. +Note! If no destination 'destinationSccpSp' is defined and the value of 'destinationMtp3bSpc' is set to 0, all local nodes are valid. + + + + + + + + + The value of SSN inCdPA (Called Party Address). + +Note! The valu 0 (zero) means tha all ssN (Sub System Number) are valid. + + + + + 0 + + + + + The Policing Global Title attribute allows to optionally police on Global Title + +Default value is considered as no policing Global Title and all GTs are valid. + + + + + + + + For a policing case whether to discard or return Service Messages, if the return option is set. + + + DISCARD + + + + + Performance monitoring counter for the number of rejected messages. + + + + + + 0 + + + + + + + The SccpAccountingCriteria MO and the SccpSp MO represents the accounting function in CPP. + +Attribute usageType specifies Accounting Remuneration (incoming GT messages) or Verification (outgoing GT messages). + +For Remuneration a SccpGlobalTitle MOId in attribute globalTitleId must be defined. +For Verification a SccpGlobalTitle MOid is defined in attribute globalTitleId, or a SccpEntitySet MOid is defined if accounting shall be made on the resulting new GT. + +The attribute ssN is optional . +The Mtp3bSrs MOid (including an SPC) in attribute pointerId is optional for accounting in one local node (SRP in one NI). +The SccpSp MOid in attribute pointerId is optional for accounting between two local nodes (SRP between two NIs). +Attribute countType specifies if Messages och Octets shall be counted. +Start and stop of accounting and output period for the accounting file is specified in the SccpSp MO. + + + + + + + + + + Label free for use. + + + "" + + + + + This attribute specifies if the MO is used for renumeration or verification. + +0 = Verification Criteria to detect outgoing massages that will be charged in the next relay node. + +1 = Renumeration Criteria to detect incoming messages for relaying, that will be charged. + + + + + + + + + Subsystem Number this Accounting Criteria applies to. +SubSystem Number 0 (zero) means that any SSN in CdPA (Called Party Address) is valid. + + + + + + 0 255 + + 0 + + + + + Specifies type of countes that should be activated. + + + + + MESSAGES + + + + + The identity of the SccpGlobalTitle MO or the SccpEntitySet MO used by this MO. + + + + + + + + + Performance monitoring counter for the number of messages, both incoming and outgoing. + +Note! If 'countType' is set to 'OCTETS' this counter is not valid. + + + + + + 0 + + + + + Performance monitoring counter for the number of octets, both incoming and outgoing. + +Note! If 'countType' is set to 'MESSAGES this counter is not valid. + + + + + + 0 + + + + + The pointer is an instance of a Mtp3bSrs MO OR an instance of a SccpSP MO. + +Note! If no pointerId is set all Signaling Point Codes (SPC) and all Sccp SP identities are valid. +Note! It is not possible to submit the Id of the SccpSp that the SccpAccountingCriteria belongs to. + + + + + + + + + + This MO models the Cbu (Node Control Board) board in CPP. +The Cbu board integrates the functionality of TUB, SCB, GPB and ETB (ET-MC1) into one Plug-In Unit. + +Note! The 'operationalState' is set to disabled if one of the functional parts is faulty. Even if the Cbu is marked with 'operationalState' DISABLED, parts of the Cbu can still be operational. + +Note! A functional part on a Cbu board can only be redundant with the same functional part on another Cbu board and thus not with that functional part implemented on a discrete board. Also note that redundancy is only applicable for the GPB part and the TimingUnit part of the Cbu board.. + +Note! On the Cbu board it is only possible to configure a maximum of 4 physical path terminations. These can be of type E1PhysPathTerm, J1PhyspathTerm or T1PhyspathTerm. It is not possible to create physical path terminations of different standards on the same board. + +Note! The Gpu part of the Cbu board (General Processor Unit) retrieves its 'availabilityStatus' from the PlugInUnit MO, thus not represented on the Cbu MO. + +Note! When the ET-MC1 is part of the Cbu board it is only possible to configure 4 physical ports as either E1 (ETSI), J1 (TTC) or T1 (ANSI). + +Note! This unit may only be inserted in slot 1 and 24 (or more accurately at APN=1 and 0 in a non-standard subrack). If redundant configuration is needed, two Cbu's must be inserted in the subrack. +If only one Cbu is used it must be placed in slot 1 (in a non-standard subrack) to be able to read the product information data of the subrack + + + + + + + + + + Provides the possibility to put a user-friendly label on the MO instance. + +Note! This attribute cannot be used for uniquely identifing the MO. + + + + 0 128 + + "" + + + + + Enabled or disabled according to the actual operational state of the NCB board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. +The 'availabilityStatusEt' gives the availability status for the ET part of the NCB board. + + + + + + NO_STATUS + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. +The 'availabilityStatusTu' gives the availability status for the Timing Unit part of the NCB board. + + + + + + NO_STATUS + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 300 + + + + + + + + + + + + + + 0 4800 + + + + + + + + + + + + + + 0 2200 + + + + + + + + + + + + + + 0 6000 + + + + + + + + + + + + + + 0 500 + + + + + + + + + + + + + + 0 50 + + + + + + + + + + + + + + 0 600 + + + + + + + + + + + + + + 0 1000 + + + + + + + + + + + + + + 0 2000 + + + + + + + + + + + + + + 0 900 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 5000 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 1000 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 200 + + + + + + + + + + + + + + 0 20 + + + + + + + + + + + + + + 0 20 + + + + + + + + + + + + + + 0 10 + + + + + + + + + + + + + + 1 28 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This containment relation indicated that any kind of board may be used to specilize PlugInUnit. + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 5000 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 9 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 + + + + + + + The SccpApLocal represents a local SSN, no relation exists to an Mtp3bAp + +Of the possible 216 SccpAps allowed on a node, a maximum of 16 are allowed to be local, and a maximum of 200 are allowed to be remote. + + + + + + + + 0 16 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 2048 + + + + + + + + + + + + + + 0 2048 + + + + + + + + + + + + + + 0 200 + + + + + + + + + + + + + + 0 1024 + + + + + + + + + + + + + + 0 100 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 1 2 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 31 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 5 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 16 + + + + + + + Multiplicity: 0..16 + + + + + + + + 0 16 + + + + + + + Multiplicity: 0..16 + + + + + + + + 0 16 + + + + + + + + + + + + + + 0 16 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 32 + + + + + + + + + + + + + + 0 128 + + + + + + + + + + + + + + 0 128 + + + + + + + + + + + + + + 0 500 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 850 + + + + + + + + + + + + + + 0 26 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 0 5 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 32 + + + + + + + + + + + + + + 1 4 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 32 + + + + + + + + + + + + + + 0 31 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 31 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 512 + + + + + + + + + + + + + + 0 512 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 63 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 3 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 512 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 28 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.stub b/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.stub new file mode 100644 index 0000000000..754b1ecded --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.stub @@ -0,0 +1,14 @@ + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml b/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml new file mode 100644 index 0000000000..8f8cf54505 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml @@ -0,0 +1,30261 @@ + + + + + + + + + + Exception thrown when an attribute is missing during upgrade. + + + + Exception thrown when enabling of existing programs fails. + + + + + + + Exception thrown when copying of files fails. + + + + Exception thrown when the specified file does not exist. + + + + + + + Exception thrown when the heap or pool setting is incorrect. + + + + Exception thrown when an attribute value is out of range. + + + + Exception thrown when a cancel install equest for some reason fails. + + + + Exception thrown when the control of checksum for loadmodules has been rejaected due to 'null' recieved from resource layer. + + + + Exception thrown when its not possible to clear all PiuTypes referenced by PlugInUnit. + + + + Exception thrown when an conditional mandatory attribute (or element) is missing. + + + + Exception thrown when the creation of a CV during upgrade fails. + + + + + + + Exception thrown when the creation of a load module fails. + + + + Exception thrown when disabling of existing programs for some reason fails. + + + + + + + Exception thrown when replacement of existing RPU information fails. + + + + Exception thrown when the installation of Load Modules is cancelled. + + + + Exception thrown when the installment of Load Modules is only partly executed. + + + + Exception thrown when the install of Load Modules is rejected. + + + + Exception thrown when the install is rejected due to FTP server is not accessible. + + + + Exception thrown when the install is rejected due to error when trying to retreive Load Module. + + + + Exception thrown when install is rejected due to erronous IP address. + + + + Exception thrown when the install is rejected due to insufficient disk space. + + + + + + + Exception thrown when the installation of a Load Module fails. + + + + Exception thrown when the disk space is insufficient. + + + + + + + Exception thrown when file path for the Load Module is out of length. + + + + + + + + + + + + + Exception thrown when the merger of control files fails. + + + + + + + + + + + + + Exception thrown when PiuType definitions is missing in the UCF file. + + + + + + + Exception thrown when the product number and revision is already used. + + + + + + + Exception thrown when reconfiguration of programs fails. + + + + Exception thrown when the referenced element is missing. + + + + + + + + + + Exception thrown when reserving a Load Module fails. + + + + Exception thrown when a selective install fails. + + + + + + + + + + Exception thrown when an unexpected attribute occurs at upgrade. + + + + Exception thrown when an unexpected format of the attribute occurs. + + + + Exception thrown when + + + + + + + + + + + + + Exception thrown when its not possible to delete the upgrade package. + + + + Exception thrown when its not allowed to delete the upgrade package. + + + + Exception thrown when the specified upgrade package does not exist. + + + + Exception thrown when an error in the file system occurs. + + + + Exception thrown when the upgrade is rejected. + + + + + + + Exception thrown when the checksum is incorrect. + + + + Exception thrown when its not possible to verify the creation of CV's. + + + + + + + + + + + + + + + + + + + + + + The upgrade trace log file is not accessible i.e. the log file exists but it is not possible to access it with write permission. + + + + The file parser has found that the UpgradeControlFile is incorrect. + + + + + + + + + Before an upgrade is started it was found that the upgrade can not take place. A possible reason is that the upgrade package that is running in the node is not in the upgrade window of this upgrade package. + + + + + + + + + The upgrade trace output is currently not directed to a file. + +This is a property that can be changed in the trace property file (Trace_01.prop). + + + + + + The upgrade package is not installed. + 0 + + + The upgrade package is completely installed. + 1 + + + Upgrade is executing. + 2 + + + The execution of upgrade needs confirmation before it proceeds. + 3 + + + In this state an Upgrade Package can only be deleted. Its actions, when invoked, will throw the exception ActionNotAllowed. + 4 + + + Installation of the upgrade package is executing. + 5 + + + The upgrade package is not completely installed i.e. parts of it has been installed. + 6 + + + The upgrade has been successfully executed. + 7 + + + + + + No action is in progress. + 0 + + + Downloading of files (load modules) in progress. + 1 + + + Saving a Configuration Version. + 2 + + + Operation ReplaceConfigSupportMOs detected in upgrade. + 3 + + + Trigger Initiate detected in upgrade sequence. + 4 + + + Trigger Preload detected in upgrade sequence. + 5 + + + 6 + + + 'Unique trigger' for an application detected in upgrade sequence. + 7 + + + 8 + + + 9 + + + The error handling is switched back to normal. + 10 + + + 11 + + + Indicates that the execution of an install or an upgrade action has failed. + 12 + + + Indicates that cancellation of an ongoing installation is in progress. + 13 + + + Indicates that the execution of a cancel install action failed. + 14 + + + 15 + + + 16 + + + 17 + + + 18 + + + 19 + + + 20 + + + 21 + + + 22 + + + + + + The verifyUpgrade action has been invoked. + 1 + + + An upgrade action (one of the variants) has been invoked. + 2 + + + An install action (one of the variants) has been invoked. + 3 + + + The cancelInstall action has been invoked. + 4 + + + + + + A timestamp. + +Format: "Date: 2003-04-24, Time: 20:52:11.182" + + "" + + + + + VERIFY_UPGRADE + + + + + EXECUTED + + + + This id is used to link more than one result to one action + + 1 + + + + + "" + + + + + + + The invoked action has been successfully executed without warnings.One of three possible main results of executed action. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 0 + + + A not specified error/ warning has been detected (see additional info for further details) + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 1 + + + A load module checksum verification has failed. + +Value valid for type of invoked action: +INSTALL +VERIFY_UPGRADE +UPGRADE + 2 + + + There is not enough available disk space for the required number of new CVs (configuration versions) to be created automatically during an upgrade. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 3 + + + The maximum number of allowed CVs (configuration versions) will be exceeded if the required number of new CVs is created automatically during an upgrade. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 4 + + + The Upgrade Window element in the Upgrade Control File does not specify the current Upgrade Package as a valid 'upgrade from' version. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 5 + + + A non supported Plug In Unit (PIU) has been detected i.e. the PIU in the node is not defined in the Upgrade Control File. +This is not a fault that prevents an upgrade from being executed. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 6 + + + A faulty Plug In Unit (PIU) has been detected. +This is not a fault that prevents an upgrade from being executed. + +Value valid for type of invoked action: +VERIFY_UPGRADE +UPGRADE + 7 + + + The auto-creation of an install CV failed. + +Value valid for type of invoked action: +INSTALL + + 8 + + + The requested action is not allowed due to an other action already is in progress for an other UP MO. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 9 + + + An ongoing installation has been cancelled (aborted) due to request from client. + +Value valid for type of invoked action: +INSTALL + 10 + + + The FTP server to be used for downloads of load modules is not accessible. + +Value valid for type of invoked action: +INSTALL + 11 + + + The required disk space for load modules to be installed is insufficient. + +Value valid for type of invoked action: +INSTALL + 12 + + + Error detected in the IP address of the FTP server. + +Value valid for type of invoked action: +INSTALL + 13 + + + The install of the delta Upgrade Control File (UCF) failed i.e. the analysis of the delta UCF together with current active UP's UCF failed. + +Value valid for type of invoked action: +INSTALL + 14 + + + Error detected during the selection phase of an install. + +Value valid for type of invoked action: +INSTALL + + + 15 + + + The execution of invoked action failed.One of three possible main results of executed action. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE +UPGRADE + 16 + + + The action has been successfully executed but with warnings.One of three possible main results of executed action. + +Value valid for type of invoked action: +INSTALL +CANCEL_INSTALL +VERIFY_UPGRADE + 17 + + + + + Ftp server is not accessible. This may depend on erroneous IP address, username, password, or that the IP communication with the Ftp server is down, or that the Ftp server itself is malfunctioning. + + + + + + + + + An error was encountered during FTP get file. A filePath in the upgradeControlFile may be inconsistent with a filepath on the Ftp server. + + + + + + + + + + The tag is used as a reference between the PiuType MO and the Repertoire MO to find out how to create the program object under a PlugInUnit MO. + + + + Local distinguished name of the program parent from the PlugInUnit. + +Example: +1. "Spu=1,Spm=2" (the program is to be created under: ...PlugInUnit=2,Spu=1,Spm=2") +2. "" (empty string - the program is to be created directly under the PlugInUnit) + + + + The name of the Program MO that will be created. + + + + The loadableProcessorName is a user friendly name of the processor. + + + + + + This structure contains load module data that belongs to a piu type. + + + The distinguished name of the load module, which is needed and sufficient to convert the load module to a real object reference. + + + + The tag is used as a reference between the PiuType MO and the Repertoire MO to find out how to create the program object under a PlugInUnit MO. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0 + + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + + + + 0 + + + 1 + + + 2 + + + 3 + + + 99 + + + 4 + + + 5 + + + + + + 0 + + + 1 + + + 2 + + + + + This attribute can have the following values: + +AtPiuFault = Indicates the MP (where the normal RPU is configured) is faulty (HW error). This is the default value. + +AtPiuRestart = Indicates the MP (where the normal RPU is configured) is restarted. + + 1 + + + 2 + + + + + This enumeration can have the following values: + +Manual = Indicates that no normalisation is performed by cello until the operator issues a "switch" action. + +Automatic = Indicates that Cello performs the normalisation automatically, after the failed RPU is available again. This is the default value. + + 1 + + + 2 + + + + + This enumaration contains the following values: + +Always = Data replication is always performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + +Never = Data replication is never performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + +AtShutdown = Each time the RSH (which handles the RPU) is shut down, a complete snapshot is taken and replicated to the other MP, if necessary. Otherwise, the replication is performed according to the characteristics set on each container ( that is associated with the RPU ). + +ApplControlled = The data replication is made according to the characteristics set on each container ( that is associated with the RPU ). This is the default value. + + Always = Data replication is always performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + 1 + + + Data replication is never performed. This overrides the characteristics set on the each container ( that is associated with the RPU ). + 2 + + + AtShutdown = Each time the RSH (which handles the RPU) is shut down, a complete snapshot is taken and replicated to the other MP, if necessary. Otherwise, the replication is performed according to the characteristics set on each container ( that is associated with the RPU ). + 3 + + + ApplControlled = The data replication is made according to the characteristics set on each container ( that is associated with the RPU ). This is the default value. + 4 + + + + + This enumeration contains the following values: + +AsConfigured = The RSHs runs as the RPU is configured. +SwitchOver = The RSHs has been switched over. +Unavailable = No RSHs, that uses this RPU, are running. + + 1 + + + 2 + + + 3 + + + + + + + + + + + + + + + + + Control value for the fan unit. Needed by cooling function. + + + Control value for the fan unit running in normal autonomous mode. +This parameter is the subrack/fanunit airflow value that is required to achieve sufficient cooling at 20 degree +centigrade or lower ambient temperature of the most demanding plug in unit (PIU) in the subrack. This airflow value +shall be sufficient (but not unnecessarily large) to secure that no "normal overtemp" fault indication is issued. +Default values = 250 m3/h. (value >=0) + + + 250 + + + + Control value for the fan unit running in normal autonomous mode. This parameter is the subrack/fanunit airflow +value that is required to achieve sufficient cooling at 50 degree centigrade ambient temperature of the most +demanding plug in unit (PIU) in the subrack. This airflow value shall be sufficient (but not unnecessarily large) to +secure that no "normal overtemp" fault indication is issued. +Default values = 400 m3/h. (value >=0) + + 400 + + + + Control value for the fan unit running in noise reduction mode. This parameter is the subrack/fanunit airflow value +that is required to achieve sufficient cooling at 20 degree centigrade or lower ambient temperature of the most +demanding plug in unit (PIU) in the subrack. This airflow value shall be sufficient (but not unnecessarily large) to +secure that no "exceptional overtemp" fault indication is issued +Default values = 250 m3/h. (value >=0) + + 250 + + + + Control value for the fan unit running in noise reduction mode. This parameter is the subrack/fanunit airflow value +that is required to achieve sufficient cooling at 50 degree centigrade ambient temperature of the most demanding +plug in unit (PIU) in the subrack. This airflow value shall be sufficient (but not unnecessarily large) to secure +that no "exceptional overtemp" fault indication is issued. +Default values = 400 m3/h. (value >=0) + + 400 + + + + + + Erroneous Ip Address Format + + + + + + + + + An application upgrade engine has reported a failure. + + + + + + + + + The action is not allowed, the UpgradePackage MO is in wrong state. + +For example if you try 'upgrade()' before an 'install()' or 'forcedInstall()' has been done. + + + + + + + + + Exception thrown upon file system Error. + + + + + + + + + Data Base Error Exception (error when creating database backup). + + + + + + + + + LLP Error Exception (error when creating ARMAMENT and LLP.LMID files). + + + + + + + + + The configuration version already exists (e.g. message at create). + + + + + + + + + The configuration version does not exist (e.g. message at setCVAsStartable). + + + + + + + + + It is not allowed to delete the configuration version, because it is in use (used as startable or in rollback list). + + + + + + + + + The configuration version is not valid (due to missing files). + + + + + + + + + + + Format Error in given configuration version name. + +The following characters are allowed within the name: +[0-9], [A-Z], [a-z] and '&','%',':','.','_', '-' + +Note! For comment and operatorName spaces (' ') are also allowed within the strings. + + + + + + + + + Error Exception. + + + + + + + + + Indicates that an error in an installation has occurred. + + The message of the exception. + + + + + + + + Exception thrown when a database error occurs. + + + + Exception thrown when an invalid drive name is specified or when a data base error occurs. + + + + + + + Exception thrown when the log file path is wrong. + + + + Exception thrown when max number of CV's in the system has been reached. + + + + + + + "" + + + + + + + + + + "" + + + + + + + + + + + + + Indicates an invalid priority level, i.e. the priority in question is out of the defined range. + + + + + + + + + This struct contains the values applicable for QoS Class A. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + + 0 1000000000 + + 500000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + 0 1000000000 + + 500000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + + 0 10000 + + 5000 + + + + + + This struct contains the values applicable for QoS Class B. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + 0 1000000000 + + 500000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + + 0 1000000000 + + 500000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + + 0 20000 + + 15000 + + + + + + This struct contains the values applicable for QoS Class C. + +NOTE: The attribute 'boundONodeDelay' is not applicable for QoS Class C so setting of this attribute will have no effect. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + 0 1000000000 + + 1000000000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + + 0 1000000000 + + 1000000000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + 25000 + + + + + + This struct contains the values applicable for QoS Class D. + +NOTE: The attribute 'boundONodeDelay' is not applicable for QoS Class D so setting of this attribute will have no effect. + + Represents the upper bound on the probability that the delay in the node exceeds the delay limit given by the attribute "boundOnNodeDelay". + +Unit is 1/1000000000. + + + 1 1000000000 + + 1000000000 + + + + Represents the upper bound of the cell loss probability in the current node. + +Unit is 1/1000000000. + + + 0 1000000000 + + 1000000000 + + + + The upper bound on the delay (delay=queueing and serving of Aal2 packets in an Aal2 mux + delay on ATM layer) through the current node. +Unit is micro seconds. + + 50000 + + + + + + + 0 + + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + 6 + + + 7 + + + 8 + + + 9 + + + 10 + + + 11 + + + 12 + + + 13 + + + 14 + + + 15 + + + + + Exception thrown when an attempt is made to set or change the aal2PathId of an Aal2PathVccTp while its reserved by an other Aal2PathGrp + + + + Exception thrown when an attempt is made to set or change the aal2PathOwner of an Aal2PathVccTp while its not LOCKED. + + + + + + + It is free to be pre-configured with a new PlugInUnit. + 0 + + + A PlugInUnit is inserted in the slot or the slot is pre-configured with a PlugInUnit. + 1 + + + Currently not supported. + 2 + + + + + + The product number of the product or document. + +Examples: ABC 101 001, CXC 123 456, 1/BFD 101 999 + +In the case of UpgradePackage this is the document number of the upgrade package. + + + 1 24 + + + + + The revision of the product number. + +Examples: R1, r1a, R1A02, P7B + + + 1 7 + + + + + A user-friendly name of the product. + + + 1 12 + + "" + + + + User-friendly information about the product. + + "" + + + + The production date can be represented in two ways. + +1) The preferable syntax is a four-digit representation of the year, and a two-digit representation of the month and a two-digit representation of the day. The numbers of characters in this case, is eight. +Example: +19991231 + +2) The date can also consist of two digits for the year, followed by the letter W for week and two digits for the number of week. The numbers of characters in this case, is five. +Example: +99W12 + + + + 1 8 + + "" + + + + + + + A user-friendly name of the product. + + + + + + + 1 12 + + + + + Unique identity for each product, which is constituted by the Ericsson product number (ABC number). + +The maximum number of characters for a product number is 24 including 2 slashes, 2 spaces and 2 characters for origination notation. + +Example of product number: +ABC 101 001 +(1/ABC 101 01/1234) +123/ABCDE 101 1010/12345 + +. + + + 1 24 + + + + + Indicates the revision state of the product. It consists of a letter R or P, one or two digits and/or one or two letters. The maximum number of characters is four inclusive R or P. +Example: R1A, R1A02, P7B + +A suffix may be added to the revision state. The suffix may consists of one or two digits or one letter. + + + + + + 1 7 + + + + + The serial number consists of 13 alphanumerical characters grouped as 6 plus 7 characters. The first 6 characters are to be used for factory codes and the last 7 characters are used for an individual number or batch number. + + + + + + The production date can be represented in two ways. + +1) The preferable syntax is a four-digit representation of the year, and a two-digit representation of the month and a two-digit representation of the day. The numbers of characters in this case, is eight. +Example: +19991231 + +2) The date can also consist of two digits for the year, followed by the letter W for week and two digits for the number of week. The numbers of characters in this case, is five. +Example: +99W12 + + + + + 5 8 + + + + + + + Defines the phase in the load and start sequence. + + + 10 + + + 50 + + + 100 + + + 200 + + + 300 + + + 400 + + + 500 + + + 600 + + + + + + 0 + + + 1 + + + + + + 0 + + + 1 + + + + + + The board is a Main processor. + 1 + + + The board is a device board. + 2 + + + The board is not a Main processor or a device board. + 3 + + + + + This attribute indicates the restart cause of plugInUnit. The defined values are: +1. piuRestartError: restart because of error. +2. piuRestartUpgrade: restart because of system upgrade. + + + This attributes indicates that the Piu restart cause is upgrade. + 2 + + + This attributes indicates that the Piu restart cause is error. + 1 + + + + + The Fan can be in one of three controlling state: +- standalone: not manageable, full speed fans +- autonomous: manageable, air-flow control +- noiseReduced: time-limited low speed fan + + It's running on itself, not manageable. + 1 + + + Manageable state. + 2 + + + Temporary state with reduced cooling. + 3 + + + + + + This attributes indicates unlimited restarts and no faulty marking of the PIU. Used for critical PIU's such as TUBs, SCBs and some ET-boards. + + -1 + + + This attributes indicates the following sequential restarts: +-warm +-refresh +-cold +-cold with fault marked (not loaded). Alarm sent. + 3 + + + This attributes indicates the following sequential restarts: +-refresh +-cold +-cold with fault marked (not loaded). Alarm sent. + 2 + + + This attributes indicates the following sequential restarts: +-cold +-cold with fault marked (not loaded). Alarm sent. + 1 + + + This attributes indicates the following sequential restarts: +-cold with fault marked (not loaded). Alarm sent. + 0 + + + + + This class is an exception class thrown when a equipment specific error occurs. + + + + + This class is an exception class thrown when a equipment specific error occurs. + + + + + This class is an exception class thrown when failed to configure the webserver root path + + + + + + + + + + + + + + + + + + 0 + + + 1 + + + + + + 0 + + + 1 + + + 2 + + + + + + + + + + + + + + Indication of Switch Internal Link port status. + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + + + Index specified is invalid, i.e. it is out of the range of valid indices. + + The exception message. + + + + + + + + + + + Exception thrown when MO is not possible to delete. + + + + Exception that is thrown when a FRO (Facade Resource Object in the resource layer) cannot be accessed. + + + + Exception that is thrown when the result of a request to a FRO (Facade Resource Object in the resource layer) is not ok. + + + + Exception thrown when the MO is already reserved by another user (MO). + + + + Exception class thrown when an MO is requested to be deleted, but the MO has children, which must be deleted first. + + + + Exception thrown when trying to delete an MO that is reserved by another MO (user). + + + + Exception thrown when the maximum number of childrens for an MO is exceeded. + + + + Exception thrown when a value of an attribute is not unique. + + + + + + + + + + + + + Exception class thrown when an MO is accessed outside a transaction but the access method requires a transaction. + + + + Exception thrown when an MO attribute is requested to be set, but the requested value is not accepted. + + + + Exception thrown when an MO attribute is requested to be set, but the requested value is of the wrong type. + + + + Exception class thrown when an attribute of not handled type is requested. + + + + Exception class thrown when a Struct is accessed but the reqested Struct element is not found. + + + + + + + Exception thrown when an MO attribute is requested to be accessed but the access +method for the is not defined (the attribute can not be accessed) + + + + Exception class thrown when the creation of an MO fails due to child - parent +cardinality violation. The cardinality is specified in the MIM. + + + + Exception thrown when the parent of the MO is of the wrong type. + + + + Exception thrown when a create is ordered with +attribute values that are not settable at create. + + + + Exception thrown when an attribute that is mandatory at create is missing. + + + + Exception thrown when an MO is created and the distinguished name of the MO is already in use. + + + + Exception thrown if the argument supplied is of the wrong type, for example in an action. + + + + Exception thrown if the value of the attribute is not valid. + + + + + 0 + + + 1 + + + 2 + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + 1 + + + 2 + + + 4 + + + 8 + + + 16 + + + 64 + + + 128 + + + 256 + + + 544 + + + 1056 + + + 2080 + + + 0 + + + + + Exception thrown when the submitted MO reference is invalid. + + + + Exception thrown when a fRo cannot be accessed. + + + + Exception thrown by an MO when there is a general error. + + + + Exception thrown when an identity (LDN) specified at create is not allowed. + + + + Exception thrown when a reference to an MO is of a unexpected/wrong MO type. + + + + Exception thrown when gathering of ATM info fails. + + + + Exception thrown when its not possible to delete an MO. + + + + Exception thrown when by an MO if its not possible to reserve the MO. + + + + Exception thrown when a user tries to release an MO that is not reserved by this user. + + + + Exception thrown when there is no hard disk. + + + + Exception thrown when an element cannot be removed from a sequence. + + + + Exception thrown when restart of the PlugInUnit is not allowed. + + + + The Sync Mode Operation of the node. + + 0 + + + 1 + + + 2 + + + + + + SUERM parameter T. +Measured in SU units. + + + 1 511 + + 64 + + + + SUREM parameter D. +Measurement units are in SUs. + + + 1 256 + + 256 + + + + SUERM parameter N. +Measurement units are in SUs. + + + 1 256 + + 16 + + + + Normal AERM threshold, Tin. Number of signal errors that cause abortion of a normal proving peroid. + +Measurement units are SUs. + + + 1 7 + + 4 + + + + Emergency AERM threshold, Tie. Number of signal units errors that cause abortion of an emergency proving period. + +Measurement units are SUs. + + + 1 7 + + 1 + + + + Proving abort limit. Number of consecutive aborted proving periods that will cause a return to the Out Of Service state. + +Measurement units are the number of proving periods. + + + 1 7 + + 5 + + + + Maximum time to stay in Aligned Ready state before signalling link failure. + +Measurement units are milliseconds. + + + 10 16300 + + 12900 + + + + Maximum time to stay in Not Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 32700 + + 5000 + + + + Maximum time to stay in Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 16300 + + 11500 + + + + Length of the normal proving period. + +Measurement units are milliseconds. + + + 10 4000 + + 2300 + + + + Length of the emergengcy proving period. + +Measurement units are milliseconds. + + + 10 4000 + + 600 + + + + Time between sending Status Indication "B" while in the Congested state. + +Measurement units are milliseconds. + + + 1 255 + + 80 + + + + Maximum time a remote site may remain in the congestated state before signalling link failure. + +Measurement units are milliseconds. + + + 10 8100 + + 1000 + + + + Maximum time to wait for an expected acknowledgement of an MSU before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 500 + + + + The speed of the link. Only supported values are 64 and 56 kbit/s. +0 = 64 kbit/s. +1 = 56 kbit/s. + + + + + 0 1 + + 0 + + + + The error correction algorithm to use. Only Basic Error Correction (BEC) is supported. +0 = BEC + + + + 0 1 + + 0 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 1 messages towards client. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 2 messages towards client. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 3 messages towards client. + + + 1 100 + + 90 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 1 messages. + + + 1 100 + + 60 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 2 messages. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 3 messages. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 1 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 2 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 3 is discarded by MTP2. + + + 1 100 + + 100 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 60 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 70 + + + + + + + SUERM parameter T. +Measured in SU units. + + + 1 64 + + 64 + + + + SUREM parameter D. +Measurement units are in SUs. + + + 1 256 + + 256 + + + + SUERM parameter N. +Measurement units are in SUs. + + + 1 256 + + 16 + + + + Normal AERM threshold, Tin. Number of signal errors that cause abortion of a normal proving peroid. + +Measurement units are SUs. + + + 1 7 + + 4 + + + + Emergency AERM threshold, Tie. Number of signal units errors that cause abortion of an emergency proving period. + +Measurement units are SUs. + + + 1 7 + + 1 + + + + Proving abort limit. Number of consecutive aborted proving periods that will cause a return to the Out Of Service state. + +Measurement units are the number of proving periods. + + + 1 7 + + 5 + + + + Maximum time to stay in Aligned Ready state before signalling link failure. + +Measurement units are milliseconds. + + + 10 65500 + + 40000 + + + + Maximum time to stay in Not Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 262000 + + 5000 + + + + Maximum time to stay in Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 1000 + + + + Length of the normal proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 7500 + + + + Length of the emergengcy proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 400 + + + + Time between sending Status Indication "B" while in the Congested state. + +Measurement units are milliseconds. + + + 1 255 + + 80 + + + + Maximum time a remote site may remain in the congestated state before signalling link failure. + +Measurement units are milliseconds. + + + 10 8100 + + 3000 + + + + Maximum time to wait for an expected acknowledgement of an MSU before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 500 + + + + The speed of the link. Only supported values are 64 and 56 kbit/s. +0 = 64 kbit/s. +1 = 56 kbit/s. + + + + + 0 1 + + 0 + + + + The error correction algorithm to use. Only Basic Error Correction (BEC) is supported. +0 = BEC + + + + 0 1 + + 0 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 1 messages towards client. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 2 messages towards client. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 3 messages towards client. + + + 1 100 + + 90 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 1 messages. + + + 1 100 + + 60 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 2 messages. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 3 messages. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 1 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 2 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 3 is discarded by MTP2. + + + 1 100 + + 100 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 60 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 70 + + + + + + + The speed of the link. Only supported values are 64 and 56 kbit/s. +0 = 64 kbit/s. +1 = 56 kbit/s. + + + + + 0 1 + + 0 + + + + The error correction algorithm to use. Only Basic Error Correction (BEC) is supported. +0 = BEC + + + 0 1 + + 0 + + + + Proving abort limit. Number of consecutive aborted proving periods that will cause a return to the Out Of Service state. + +Measurement units are the number of proving periods. + + + 1 7 + + 5 + + + + SUERM parameter D. +Measurement units are in SUs. + + + 1 256 + + 256 + + + + SUERM parameter N. +Measurement units are in SUs. + + + 1 256 + + 16 + + + + SUERM parameter T. +Measured in SU units. + + + 1 64 + + 64 + + + + Emergency AERM threshold, Tie. Number of signal units errors that cause abortion of an emergency proving period. + +Measurement units are SUs. + + + 1 7 + + 1 + + + + Maximum time to stay in Aligned Ready state before signalling link failure. + +Measurement units are milliseconds. + + + 10 65500 + + 45000 + + + + Maximum time to stay in Not Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 262000 + + 132000 + + + + Maximum time to stay in Aligned state before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 1000 + + + + Length of the emergengcy proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 500 + + + + Length of the normal proving period. + +Measurement units are milliseconds. + + + 10 16300 + + 8200 + + + + Time between sending Status Indication "B" while in the Congested state. + +Measurement units are milliseconds. + + + 1 255 + + 100 + + + + Maximum time a remote site may remain in the congestated state before signalling link failure. + +Measurement units are milliseconds. + + + 10 8100 + + 5000 + + + + Maximum time to wait for an expected acknowledgement of an MSU before signalling link failure. + +Measurement units are milliseconds. + + + 10 2000 + + 2000 + + + + Normal AERM threshold, Tin. Number of signal errors that cause abortion of a normal proving peroid. + +Measurement units are SUs. + + + 1 7 + + 4 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 1 messages towards client. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 2 messages towards client. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer that will cause MTP2 to signal congestion for prio 3 messages towards client. + + + 1 100 + + 90 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 1 messages. + + + 1 100 + + 60 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 2 messages. + + + 1 100 + + 70 + + + + Percentage of the Transmit Buffer that ceases congestion for prio 3 messages. + + + 1 100 + + 80 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 1 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 2 is discarded by MTP2. + + + 1 100 + + 100 + + + + Percentage of the Transmit Buffer where messages sent to MTP2 from client with priority less than 3 is discarded by MTP2. + + + 1 100 + + 100 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 60 + + + + Number of MSUs in ReTransmit Buffer before onset of preventive retransmission in PCR. +NOTE: Only valid if errorCorrection==SCC_MTP2_ERROR_CORRECTION_PCR. +This value is ignored otherwise. + + + 1 100 + + 70 + + + + + + This enumeration specifies the different stages of the emergency state. + + Emergency state has not been activated since installation of license key file. + 0 + + + All capacity restrictions removed and all features enabled. The maximum time in this state is 7 days. + 1 + + + A new license key file has to be istalled in order not to jopardize future use and performance. +The maximum time in this state is 7 days. + 2 + + + All features enabled again for a maximum period of 7 days then a new license key file has to be installed in order to be able to use this node. + 3 + + + Use of the node is no longer allowed since no new license key file has been installed. + 4 + + + + + This attribute provides information about the current EmergencyState. + +Note: for the states NEVER_USED and USE_DISABLED the return value for time is insignificant. + + The current emergency state of the license server. + + NEVER_USED + + + + This attribute holds information on the time elapsed in this state. + +Note: The time out values for the states ALL_OPEN, DEGADED and PROLONGED is 7 days. The unit for this attribute is seconds. +1 day = 86400 seconds +7 days = 604800 seconds. + + 0 + + + + + + + Warm node restart at restart of the last PIU. + 4 + + + Cold node restart at restart of the last PIU. + 3 + + + Warm node restart at fault mark of the last PIU. + 2 + + + Cold node restart at fault mark of the last PIU. + 1 + + + + + + Maximum number of SD PDUs before a poll is sent. + +maxPD < initialCredit + + + 10 10000 + + 25 + + + + Maximum number, odd integer value, of list elements placed in a STAT PDU. + +Note: The maxStat attribute is dependent on the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The maxStat times 4 (octets) plus additional 12 octets (for header) must not exceed the AAL5 maximum SDU size (lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). +The consistency control is not performed until the UniSaalTp MO is created since there is no relation between the UniSaalProfile MO and the Aal5TpVccTp MO. + + + 3 1001 + + 67 + + + + Initial number of credits. + +Note: For 64 kbit/s use 30. + +Note! The value for initialCredit must be larger than the value of maxPD. + + + + 10 1000 + + 250 + + + + Timer to be used during a period of no outstanding acknowledgements or new data pending receipt of credit. At timeout the peer is polled to see if it is alive. The timer determines the interval between polls in transient phase. This timer should be greater than the roundtripdelay and also greater than timerpoll. Time unit = milliseconds. + + + + 10 10000 + + 2000 + + + + Timer to determine the maximum time interval during which at least one STAT PDU reception is expected as a response to a poll. This timer should be equal to timerKeepAlive+roundtripdelay. Time unit = milliseconds. + + + 10 100000 + + 7000 + + + + Timer running when there are no PDUs to transmit and there are no outstanding acknowledgements or data pending for credit. When this timer is running, no POLL PDUs are sent. This timer should be significantly greater than timerKeepAlive value. Time unit = milliseconds. + + + 1000 600000 + + 15000 + + + + Timer determining the time between re-transmission of PDUs: BGN, END, ER, RS. Should be slightly more than the roundtripdelay. Time unit = milliseconds. + + + 10 10000 + + 1000 + + + + Timer that specifies the maximum time between sending of POLL PDUs to the peer receiver during other traffic (active phase). Time unit = milliseconds. + + + 10 100000 + + 750 + + + + Maximum number of re-transmissions of PDUs: BGN, END, ER, RS. Time unit = milliseconds. + + + 0 100 + + 4 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationAbatement < congestationOnSet <= 100. + + + 0 100 + + 70 + + + + Attribute specifying the percentage of the buffer for which congestion is stopped. If the congestionAbatement level is lesser but almost equal to congestionOnSet, congestion alarms might be raised and ceased very often. + +This attribute should follow the rule 0 <= congestationAbatement < congestationOnSet <= 100. + + + 0 100 + + 60 + + + + + + Struct holding the values for an NniSaalProfile. + +NOTE: Congestition Level 1 - 3 is supported. + + Timer that specifies the maximum time between sending of POLL PDUs to the peer receiver during other traffic (active phase). Time unit = milliseconds. + + + 10 100000 + + 50 + + + + Maximum number of re-transmissions of PDUs: BGN, END, ER, RS. + + + 0 100 + + 4 + + + + Maximum number of SD PDUs before a poll is sent. + +maxPD < initialCredit + + + 0 10000 + + 25 + + + + Maximum number, odd integer value, of list elements placed in a STAT PDU. + +Note: The maxStat attribute is controlled by the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The maxStat times 4 (octets) plus additional 12 octets (for header) must not exceed the AAL5 maximum SDU size (lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). + +The consistency control is not performed until the NniSaalTp MO is created since there is no relation between the NniSaalProfile MO and the Aal5TpVccTp MO. + + + 3 1001 + + 67 + + + + Initial number of credits. + +Note: For 64 kbit/s use 30. + +Note! The value for initialCredit must be larger than the value of maxPD. + + + 10 1000 + + 250 + + + + Timer to be used during a period of no outstanding acknowledgements or new data pending receipt of credit. At timeout the peer is polled to see if it is alive. The timer determines the interval between polls in transient phase. This timer should be greater than the roundtripdelay and also greater than timerpoll. Time unit = milliseconds. + + + 10 10000 + + 100 + + + + Timer to determine the maximum time interval during which at least one STAT PDU reception is expected as a response to a poll.This timer should be equal to timerKeepAlive+roundtripdelay. Time unit = milliseconds. + + + 10 100000 + + 500 + + + + Timer running when there are no PDUs to transmit and there are no outstanding acknowledgements or data pending for credit. When this timer is running, no POLL PDUs are sent. This timer should be significantly greater than timerKeepAlive value. Time unit = milliseconds. + + + 10 10000 + + 100 + + + + Timer determining the time between re-transmission of PDUs: BGN, END, ER, RS. Time unit = milliseconds. +Should be more than the roundtrip delay. + + + 10 10000 + + 200 + + + + Management Proving Status which is used to decide if proving is done or not during SAAL connection setup. + + + 0 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationLevel1OnSet <= congestationLevel2OnSet <= congestationLevel3OnSet <= 100. + + + 0 100 + + 70 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationLevel1OnSet <= congestationLevel2OnSet <= congestationLevel3OnSet <= 100. + + + 0 100 + + 80 + + + + Attribute specifying the percentage of the buffer that must be filled in order to cause congestion. +Congestion is notified to the users of this protocol layer. The part of the buffer above the congestion +level is used to take care of messages that were sent before the users stopped sending. + +This attribute should follow the rule 0 <= congestationLevel1OnSet <= congestationLevel2OnSet <= congestationLevel3OnSet <= 100. + + + 0 100 + + 90 + + + + Attribute specifying the percentage of the buffer for which congestionLevel1 is stopped. If the congestionAbatement level is lesser but almost equal to congestionOnSet, congestion alarms might be raised and ceased very often. + + + + 0 100 + + 60 + + + + The length of proving in terms of number of transmitted PDUs (n1). +noOfPDUsDuringProving x T3 < T2 + +For the TTC standard the only allowed value is 0 (which means no proving). + + + 0 100000 + + 1000 + + + + State variable which defines max number of retransmissions of PDUs during proving to consider proving successful. + + + + 0 100 + + 0 + + + + Maximum time of no credit. If the timer expires, the assured data transfer mode is released. + + + 0 100000 + + 1500 + + + + Timer which is set whenever a report of SSCOP recovery is received from the SSCF. If the timer is running when another report of recovery is received, the assured data transfer mode is released. If the timer expires, nothing is done. Time unit = milliseconds. + + + 0 86400000 + + 3600000 + + + + Timer between the link release action and the next link re-establish action during the alignment. At expiry of timer T1, a new attempt to setup assured data transfer mode to the peer is done. Time unit = milliseconds. + + + + 10 100000 + + 5000 + + + + Total time that SSCF will attempt alignment. At expiry of timer T2, the alignment procedure will be interrupted. + Time unit = milliseconds. + + + + 10 200000 + + 30000 + + + + Time between proving PDUs. The timer is set such that loading of the signalling link is approximately 50% of its nominal rate. +Time unit = milliseconds. + + + 5 1000 + + 5 + + + + + + Exception thrown when a time slot appears more than once in the time slot list. + + + + RefActivity can have the following values: + +inactive = Synchronization reference is currently not used in system clock generation. +active = Synchronization is used in system clock generation. + + + 1 + + + 2 + + + + + RefState can have the following values: +failed = synchronization reference is not capable to perform its required tasks. +degraded = capability of synchronization reference to perform its required tasks is degraded e.g. because of signal level degradation. This value is only applicable for traffic carrying (ET physical path termination) synchronization references. Note: attribute degradationIsFault controls whether synchronization reference degradation is interpreted as a synchronization reference fault or not. +lossOfTracking = system clock regulation algorithm on TU board can not follow the 8kHz synchronization reference signal either because of the poor quality of the signal or because of a HW fault at TU board. If all synchronization references repeatedly end up to state lossOfTracking, fault is likely in TU HW. +ok = synchronization reference is capable of performing its required tasks. + + + 0 + + + 1 + + + 2 + + + 3 + + + + + FaultCriteria can have the following values: +degrNotFault = synchronization reference degradation is NOT interpreted as a synchronization reference fault. +degrIsFault = synchronization reference degradation is interpreted as a synchronization reference fault. + + 0 + + + 1 + + + + + ClockState can have the following values: +startUp = +locked = system clock signal on Timing Unit is locked: a synchronization reference is used in the system clock generation, clock accuracy is 50 ppb or better. +holdOver = system clock signal on Timing Unit is hold-over: no synchronization reference is used in system clock generation, clock accuracy is 50 ppb or better. +freeRunning = system clock signal on Timing Unit is free running: no synchronization reference is used in system clock generation, clock accuracy is 4.6 ppm or better. +failed = system clock signal on Timing Unit is failed: fault in system clock generation function, no quarantee of clock accuracy level. +not Applicable = system clock signal on Timing Unit is not applicable: TU board not present. + + 0 + + + 1 + + + 2 + + + 3 + + + 4 + + + 5 + + + 6 + + + 7 + + + + + Exception thrown when an object is already registered. + + + + Exception thrown when the maximum number of references is reached. + + + + Exception thrown when a priority is already in use. + + + + Exception thrown when the priority is out of range. + + + + Exception thrown when an reference is not valid, null or of incorrect type. + + + + Exception thrown when trying to de-register an object that is not registered in the database. + + + + + 0 + + + 1 + + + 2 + + + + + Exception thrown when a fro Id is not unique. + + + + + 0 + + + 1 + + + 2 + + + + + A predefined group consisting of working links and their corresponding protecting links. These links form the n+m link redundancy. + + Defines physical link status. + + 1 + + + Defines physical link status. + + 2 + + + Defines physical link status. + + 3 + + + + + + Global title indicator should have following values for both ITU and TTC: + +The values for the GT Indicator + +Value Comment + +0 No new global title +2 TT only +3 TT-NP-ES +4 TT-NP-ES-NOA + +Explanation: + +TT = translation type +NP = numbering plan +ES = encoding scheme +NOA = nature of address indication + + + 0 4 + + 0 + + + + Indicates number type, i.e. national or international number. +Coding of the Nature Address: + +0 = "unknown" +1 = "Subscriber number" +2 = "Reserved for national use" +3 = "National significant number" +4 = "International number" + + + 0 4 + + 0 + + + + Indicates which numbering plan that is used. + +Coding of the Numbering Plan: + +0 = "Unknown" +1 = "ISDN/Telephony Numbering Plan" +3 = "Data Numbering Plan" +4 = "Telex Numbering Plan" +5 = "Maritime Mobile Numbering Plan" +6 = "Land Mobile Numbering Plan" +7 = "ISDN/Mobile Numbering Plan" + + + + 0 7 + + 0 + + + + Used to direct the message to the appropriate Global Title translation function. + + + 0 254 + + + + + Digit string of 1-37 digits, where each digit is 0-9, and B, C. B and C are for Code 11 and Code 12. +The addressInformation may also contain wild card symbols: "*" or "?". Wild cards are only allowed for defining Global Title Translations, they are not allowed for specifying SCCP SAPs (built with SPC and Global Title or SPC + SSN + Global Title). + + + 1 37 + + + + + Indicates if the number of address signals are an odd or even number, and is coded as follows: + +0 = "Unknown" +1 = "BCD, odd number of digits" +2 = "BCD, even number of digits" + +Other values in the encoding scheme will result in the error "Wrong Nature Of Address", (Routing failure reason=No translation for an address of such nature). + + + 0 2 + + 0 + + + + + + + The when sharing mode is set to loadShare the SCCP traffic is load shared between the two entities (access points). + 0 + + + When the sharing mode is set to dupliDominant the second entity (access point) is a backup for the first entity. + 1 + + + + + Possible values for number signalling. + + Unkown encoding scheme. + 0 + + + BCD, odd number of digits. + 1 + + + BCD, even number of digits. + 2 + + + + + Global title indicator values for China, ITU, TTC and ANSI. + +Note: China, ITU and TCC will use TT_ONLY, TT_NP_ES, TT_NP_ES_NOA, NOA_ONLY. + +ANSI will use: +ANSI_TT_NP_ES = 5 +ANSI_TT_ONLY = 6 + + + Translation Type only. + +Only valid for China, ITU and TTC. + 2 + + + Translation Type, Numbering Plan and Encoding Scheme. + +Only valid for China, ITU and TTC. + 3 + + + Translation Type, Numbering Plan, Encoding Scheme, and Nature Of Address indication. + +Only valid for China, ITU and TTC. + 4 + + + Nature of Address indicator only. + +Only valid for China, ITU and TTC. + 1 + + + Translation Type, Numbering Plan and Encoding Scheme. + +Only valid for ANSI. + + 5 + + + Translation Type only. + +Only valid for ANSI. + + 6 + + + + + Phone number types. + + Unknown number type. + 0 + + + Subscriber number type. + + 1 + + + Reserved for national use, number type. + 2 + + + National Significant Number type. + 3 + + + International number type. + 4 + + + + + Numbering plans. + + Unknown numbering plan. + 0 + + + ISDN/Telephony numbering plan. + + 1 + + + Data numbering plan. + 2 + + + Telex numbering plan. + + 3 + + + Maritime mobile numering plan. + + 4 + + + Land mobile numbering plan. + + 5 + + + ISDN/Mobile numbering plan. + 6 + + + + + + 0 + + + 1 + + + + + + Controls when to send SST (SCCP Subsystem Test message). + +0 = Wait for tStatInfo timer to expire once after MTP_RESUME before sending SST. +1 = Send SST immediately after MTP_RESUME, then start tStatInfo timer. + + 1 + + + + Controls when to send SSA (SCCP Subsystem Allowed message). + +0 = Do not send SSA when client attaches, wait until SST is received. (default for ANSI/CHINA/ITU/TTC) +1 = Send SSA immediately when client attaches. + + 0 + + + + Controls whether to send SSP (SCCP Subsystem Prohibited message). + +0 = Do not send SSP when client detaches. (default for TTC) +1 = Send SSP immediately when client detaches. (default for ANSI/CHINA/ITU) + + 1 + + + + Controls whether to send SST messages or not (SCCP Subsystem Test message). + +0 = Send SST as indicated by sendSST. (default for ANSI/CHINA/ITU) +1 = (not used) +2 = (not used) +3 = Do not initiate SST messages at all, ie. do not start timer tStatInfo nor send any SST at MTP_RESUME. (default for TTC) + + 0 + + + + Controls the remote broadcast. + +0 = allow remote broadcast. (default for ANSI/CHINA/ITU/TTC) +1 = do not allow remote broadcast + + 0 + + + + Controls whether to initiate hardcoded congestion timer or not. + +0 = start timer when SSC is received. (default for CHINA/ITU/TTC) +1 = do not start timer + +Note! This attribute is not valid for the ANSI standard. + + 0 + + + + + + + 0 + + + 1 + + + + + + + + + + + J1Type can have the following values: +J1_G = 0 according to TTC JT-G703/G704 +J1_I = 1 according to TCC JT-I431 + + J1 according to TTC JT-G703/G704 + 0 + + + J1 according to TCC JT-I431 + 1 + + + + + Indicates what standard the MAO is operating to. + + The standard mode is Telecommunication Technology Committee (TTC). + 2 + + + The standard mode ANSI. + 0 + + + The standard mode is ETSI. + 1 + + + + + Indicates what multiplexing is being used. + + Standby for protection. + 0 + + + Multiplexing terminated at the E1/J1/T1 level. + 1 + + + Multiplexing terminated at the VC-4/STS3CSPE level. + 2 + + + + + The loopback method available for use by the Os155SpiTtp MO. + + No loopback in use. + 0 + + + Loopingback using line. + 1 + + + + + The switch modes. + + Automatic switching. + 0 + + + Locked for swtiching. + 1 + + + + + + + + + + + + + + + + + + + + Path Trace Formats. + + 16 byte path trace format according to ITU-T G707 table 4. + 16 + + + 64 byte path trace format according to section 3.3.2.3, Telecordia GR-253-CORE. + 64 + + + + + Cyclical Redundancy Checks 4 modes. + + CRC 4 is off. + 0 + + + CRC 4 is on. + 1 + + + CRC 4 is automatic. + 2 + + + + + Idle patterns. + + A law idle pattern. + 1 + + + Micro law idle pattern. + 2 + + + Undefined idle pattern. + 0 + + + + + The possible loopback states for E1/J1/T1/E3/T3PhysPathTerm MOs. + + This is the normal state, no loop back is preformed (and ordinary traffic is running). + 0 + + + The phyiscal path is looped on the line side, the external incoming path is looped back to the external outgoing path. + 1 + + + The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + 2 + + + + + L stands for long haul interface and S stands for short haul interface. +The subsequent figure specifies the cable distance in feets. + + Long Haul 6000 ft, -0 dB + 8 + + + Long Haul 4000 ft, -7 dB + 7 + + + Long Haul 2000 ft, -15 dB + 6 + + + Long Haul 0 ft, -22 dB + 5 + + + Short Haul 0..133 ft + 0 + + + Short Haul 134..266 ft + 1 + + + Short Haul 267..399 ft + 2 + + + Short Haul 400..533 ft + 3 + + + Short Haul 534..655 ft + 4 + + + + + Priority attributes for MTP3b SP of the ITU standard. + + The prioSlt attribute sets the priority for the + Signalling Link Test Message and Acknowledge (SLTM / SLTA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioTra attribute sets the priority for the +Traffic Restart Allowed signal (TRA) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioUpu attribute sets the priority for the + User Part Unavailable (UPU) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioLink attribute sets the priority for link related messages when issued by the MTP3b itself. The messages are : + +Link INhibit (LIN), Link UNinhibit (LUN), +Link Inhibit Denied (LID), +Link Inhibit Acknowledge (LIA), +Link Uninhibit Acknowledge (LUA), +Link Forced Uninhibit (LFU), +Link Local inhibit Test (LLT) and +Link Remote inhibit Test (LRT) + +When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + + + ITU timers for MTP3bSpItu. Timervalues in 1/10 s (deciseconds). + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, second attempt + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Waiting for uninhibit acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for force uninhibit. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for inhibition acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Supervision timer for the first phase of a restarting STP. This is an STP specific parameter, which is ignored when configured as an endpoint. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + + 1 65535 + + 550 + + + + Controlling the response of the receipt of a traffic restart message from an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 680 + + + + Overall MTP restart timer at the restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 600 + + + + Overall MTP restart timer at an adjacent signalling point to a restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 640 + + + + Local inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Remote inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Supervision timer for SLTA message (time within SLTA should arrive). + +Timer T1 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer for sending SLTM periodically. + +Timer T2 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Timer used for message acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for audit procedure. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay to avoid mis-sequencing of messages when an association fails. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing of messages when an association becomes active. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to prohibit sending of DUNA messages via the response method. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Delay to avoid message mis-sequencing on controlled/forced rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlloing the traffic activation delay during restart phase. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + The forever interval period for trying association after an unsiccessfull trial. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlling the period a route set is considered congested when a SCON message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for SCTP_ASSOCIATE_REQ message acknowledgement. This is the maximum time to wait for the SCTP_COMMUP_IND mesage before considering it to be an error. +It should be longer than the time a message spends to reach the most distant destination, be processed and returned. + + + 1 65535 + + 20 + + + + + + The supported congestion levels. + + No Congestion. + 0 + + + Congestion level low. + 1 + + + Congestion level medium. + 2 + + + Congestion level high. + 3 + + + + + + + + + + + + 0 + + + 1 + + + + + Indicates which type of geographical network, e.g. national, international, etc.. + +Note: Not applicable for TTC. + + International Network. + 0 + + + Spare (for international use only). + 1 + + + National network. + 2 + + + Reserved for national use. + 3 + + + + + Indicates how a TransFer Restricted (TFR) signal is handled. + + Treat the TransFer Restricted (FTR) signal as a TransFer Allowed (TFA) signal. + 1 + + + Ignore the TransFer Restricted (TFR) signal. + 0 + + + Handle the incoming TRF messages according to the standard. + 2 + + + + + Indicates whether the two spare bits in the Service Information Octet (SIO) should be treated as spare or for indicating a priority level. + + The two spare bits in the SIO are treated as spare. + 0 + + + The two spare bits in the SIO are to be used for indicating a priority level. + 1 + + + + + Indicates which version of the ITU standard. + + ITU-T -88. + 0 + + + ITU-T 03/93. + 1 + + + ITU-T 07/96 + 2 + + + + + ANSI timers for MTP3bSpAnsi. Timervalues in 1/10 s (deciseconds). + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, second attempt + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Waiting for uninhibit acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for force uninhibit. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for inhibition acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer to limit sending of TFPs and TFRs in response to unexpected TRA and TRW. This timer is specific for STP functionality and is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay extension timer invoked on reciept of a Traffic Restart Waiting message from an adjacent SP which is restarting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Controlling the periodic resend of Traffic Restart Waiting messages during restart of the local node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 120 + + + + Timer enforcing a minimum node unavailablility period during MTP restart. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Delay timer controlling a timed reaction of the restart of an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Timer controlling the response of the receipt of Traffic Restart messages from an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 600 + + + + Controlling the periodic resend of Local Inhibit Change Message. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1000 + + + + Controlling the periodic resend of Remote Inhibit Test Message. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1000 + + + + Delay on commencement of MTP Restart to allow the node to rebuild an accurate routing table based on messages for adjacent nodes. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 600 + + + + Supervision timer for routing updates on MTP Restart. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 40 + + + + Timer controlling the detection of false link congestion. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer for sending SLTM periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Supervision timer for SLTA message (time within SLTA should arrive). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer used for message acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for audit procedure. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay to avoid mis-sequencing of messages when an association fails. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing of messages when an association becomes active. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to prohibit sending of DUNA messages via the response method. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Delay to avoid message mis-sequencing on controlled/forced rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlloing the traffic activation delay during restart phase. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + The forever interval period for trying association after an unsiccessfull trial. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlling the period a route set is considered congested when a SCON message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer used for SCTP_ASSOCIATE_REQ message acknowledgement. This is the maximum time to wait for the SCTP_COMMUP_IND mesage before considering it to be an error. +It should be longer than the time a message spends to reach the most distant destination, be processed and returned. + + + 1 65535 + + 20 + + + + + + TTC timers for MTP3bSpTtc. Timervalues in 1/10 s (deciseconds). + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +The value for this timer should be less than the value for timerT2. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer pending a Signalling Route Test Acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + + + Priority attributes for MTP3b SP of the ANSI standard. + + The prioSlt attribute sets the priority for the + Signalling Link Test Message and Acknowledge (SLTM / SLTA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) + + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioTra attribute sets the priority for the +Traffic Restart Allowed signal (TRA) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioUpu attribute sets the priority for the + User Part Unavailable (UPU) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioLink attribute sets the priority for link related messages when issued by the MTP3b itself. The messages are : + +Link INhibit (LIN), Link UNinhibit (LUN), +Link Inhibit Denied (LID), +Link Inhibit Acknowledge (LIA), +Link Uninhibit Acknowledge (LUA), +Link Forced Uninhibit (LFU), +Link Local inhibit Test (LLT) and +Link Remote inhibit Test (LRT) + +When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + + + Priority attributes for MTP3b SP of the TTC standard. + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) +. + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + + + HIGHEST + + + + The prioTfa attribute sets the priority for the Transfer Allowed, TFA, messages. + + + HIGHEST + + + + The priority indicator used for indicating message priority for signalling route test messages (SRT/SRA). + + + HIGHEST + + + + The priority indicator used for indicating the message prioirity for TFC. + + + HIGHEST + + + + + + Indicates the priority level for MTP 3. + + Lowest priority setting. + 0 + + + Low priority setting. + 1 + + + High priority setting. + 2 + + + Highest priority setting. + 3 + + + + + China timers for MTP3bSpChina. Timervalues in 1/10 s (deciseconds). + + Supervision timer for SLTA message (time within SLTA should arrive). + +Timer T1 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 100 + + + + Timer for sending SLTM periodically. + +Timer T2 in ITU Q.707 standard. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Delay to avoid message mis-sequencing on changeover. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting to repeat sending of RST periodically. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 400 + + + + Waiting for uninhibit acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for force uninhibit. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for inhibition acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 30 + + + + Delay to avoid oscillation of initial alignment failure and link restart. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Supervision timer for the first phase of a restarting STP. This is an STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + + 1 65535 + + 200 + + + + Controlling the response of the receipt of a traffic restart message from an adjacent node. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 40 + + + + Timer for waiting for a COO or a COA. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Overall MTP restart timer at the restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 40 + + + + Overall MTP restart timer at an adjacent signalling point to a restarting MTP. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Local inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Remote inhibit test timer. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 2500 + + + + Delay to avoid message mis-sequencing on a time controlled diversion change back. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, first attempt. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for waiting for CBA, second attempt + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for delay to avoid message mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 9 + + + + Timer for delay to prohibit sending of TFP messages via the response method. This is a STP specific parameter, which is ignored when configured as an endpoint. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Waiting for BSNT value from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Controlling the period a route set is considered congested when a Transfer Controlled message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer for waiting for completion of buffer retrieval from MTP-2 or SAAL (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 10 + + + + Timer for retransmission of DL_START_req if no answer received. Started when timerT17 expires. (not standard timer). + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 1200 + + + + Timer used for message acknowledgement. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for audit procedure. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 300 + + + + Delay to avoid mis-sequencing of messages when an association fails. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing of messages when an association becomes active. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to avoid mis-sequencing on controlled rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 5 + + + + Delay to prohibit sending of DUNA messages via the response method. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Delay to avoid message mis-sequencing on controlled/forced rerouting. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlloing the traffic activation delay during restart phase. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + The forever interval period for trying association after an unsiccessfull trial. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 8 + + + + Timer controlling the period a route set is considered congested when a SCON message has been received. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 50 + + + + Timer waiting to start signaling route set congestiontest. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test". + +Guiding value 20 - 30. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer waiting for route set congestion status update. Used only if the Route Set +Congestion Test Selectoption is set to "Use Route Set Congestion test" + +Guiding value 14 - 22. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 14 + + + + Timer pending an acknowledge from the network layer for a DL_ACK_REQ. + +Unit: deciseconds (1/10 second). + + + 1 65535 + + 20 + + + + Timer used for SCTP_ASSOCIATE_REQ message acknowledgement. This is the maximum time to wait for the SCTP_COMMUP_IND mesage before considering it to be an error. +It should be longer than the time a message spends to reach the most distant destination, be processed and returned. + + + 1 65535 + + 20 + + + + + + Indicates which type of geographical network, e.g. national, international, etc.. + +Note: Only for TTC. + + National network. + 0 + + + Spare (for international use only). + 1 + + + International Network. + 2 + + + Spare. + 3 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + idle, the Mtp3bSl carries no traffic. + 0 + + + active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. + 1 + + + busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + 2 + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + 0 - not initialized. + 0 + + + 1 - initialized. + 1 + + + + + The nodeBehaviorType attribute represents the MTP3b node type. + + Signaling End Point. + 0 + + + Signalling Transfer and End Point, i.e the signalling point is of both type Signalling End Point (SEP) and Signalling Transfer Point (STP). + 4 + + + Signaling GateWay, Signaling End Point and Signalling Transfer Point, i.e the signalling point is of both type Signalling Transfer Point (STP), Signaling End Point (SEP) and Signaling GateWay (SGW). + 5 + + + + + Priority attributes for MTP3b SP of the China standard. + + The prioSlt attribute sets the priority for the + Signalling Link Test Message and Acknowledge (SLTM / SLTA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCo attribute sets the priority for the ChangeOver Order and Acknowledge (COO/COA) or eXtended Change over Order and Acknowledge (XCO/XCA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet) + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioCb attribute sets the priority for the + Change Back Declaration and Acknowledge (CBD / CBA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioEc attribute sets the priority for the +Emergency Change over Order and Acknowledge (ECO / ECA) messages when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioRst attribute sets the priority for the +signalling Route Set Test (RST) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioTra attribute sets the priority for the +Traffic Restart Allowed signal (TRA) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioUpu attribute sets the priority for the + User Part Unavailable (UPU) message when issued by the MTP3b itself. When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + The prioLink attribute sets the priority for link related messages when issued by the MTP3b itself. The messages are : + +Link INhibit (LIN), Link UNinhibit (LUN), +Link Inhibit Denied (LID), +Link Inhibit Acknowledge (LIA), +Link Uninhibit Acknowledge (LUA), +Link Forced Uninhibit (LFU), +Link Local inhibit Test (LLT) and +Link Remote inhibit Test (LRT) + +When a message is transferred from the MTP3b the message priority uses the two spare bits in the SIO (Service Information Octet). + +lowest:0 +low:1 +high:2 +highest:3 + + HIGHEST + + + + + + The type of Signalling Route. + + 0 + + + 1 + + + + + + Single-homed with ipAddress1. + 1 + + + Single-homed with ipAddress2. + 2 + + + Multihomed association with ipAddress1 and +ipAddress2 + + 3 + + + + + The state of the signaling route. + + The signaling route is not blocked. + 0 + + + The signaling route is blocked. + 1 + + + + + + 0 + + + 1 + + + + + Open Shortest Path First metric type. + + 0 + + + 1 + + + + + The types of the routes found in the IP routing table. + + The source of information is unknown. + 1 + + + Route created from local configuration data (both static and interface routes). +Each interface created gets an entry in the routing table of the RO. + 2 + + + Route added by SNMP. + 3 + + + Route added by OSPF. + 13 + + + Route added by ICMP redirect message. + 4 + + + + + Invalid IP route has been given as a parameter to an action. + + Exception message. + + + + + + + + Invalid IP route has been given as a parameter to an action. + + + + + + + + + + 0 + + + 1 + + + + + The controller mode of a physical interface. + + 1 + + + 2 + + + 3 + + + + + ipAddress - the subnet address of the range. +subnetMask - IP subnet mask of the range to be added. +advertise - indicates whether the area range should be advertised into OSPF. + + + + + + Note! The subnet has to be contigious. That is, has the LSB set to 0 (zero). + +Example: + +255.255.255.X + +Contiguous subnet mask: +11111111.11111111.11111111.11111110 (X = 254) +11111111.11111111.11111111.11111100 (X = 252) + +Not-contiguous subnet mask: +11111111.11111111.11111111.11111010 (X = 250) + + + + + + + + + + IP routing table entry. + + The destination IP address. + + + + The destination IP network mask. + + + + The next hop IP address. + + + + The route metric. + + + + The route type. + + + + + The interface name. + + + + Indicates if the route should be redistributed. + + + + Indicates if the route is active. + + + + + + Denotes whether the autoConfiguration mode for the IpAccessHost is turned on or off. + + 1 + + + 2 + + + + + In case 'NO_PREFERENCE', 'LOCAL_MP_SELECT_VCC_AT_LINK_UP', LOCAL_MP_PEER_SELECTION_VCC' or 'LOCAL_MP_ACTIVE_RESELECTION' is selected the IpAtmLink MO will prefer Aal5TpVccTp on local MP (i.e. Aal5TpVccTp executing on the same MP as the IpAtmLink), but other Aal5TpVccTp will be accepted if needed. + +In case 'ONLY_LOCAL_MP' is selected, the ipAtmLink (Inet Link) will consider Aal5TpVccTp residing on other MPs as a malfunction and discard the usage of them. No InvArp sending will be performed on them and all incomming trafic on them will be discarded. If no local Aal5TpVccTp exists the operational state of the link will be changed to disabled. + + 0 + + + Prefer termination on local MP, select Vcc when link goes up. + 1 + + + Prefer termination on local MP, follow peer selection of Vcc. + 2 + + + Prefer termination on local MP, active reselection to new Aal5TpVccTp as soon as a better choice exists. + 3 + + + Restricted to local MP, follow peer selection if termination is on local MP. + + 4 + + + + + Alarm report for the Virtual path connection termination point. +RDI - Remote defect indication +LOC - Loss of continuity +AIS - Alarm indication signal + + For alarms of type Loss of continuity. + 2 + + + For alarms of type Loss of continuity and Remote defect indication. + 3 + + + For alarms of type Alarm indication signal and Loss of continuity. + 6 + + + For alarms of type Alarm indication signal, Remote defect indication and Loss of continuity. + 7 + + + + + + Performance monitoring is turned off. PM counters give irrelevant values. + 0 + + + Performance monitoring counters are active + + 1 + + + FPM, Forward Performance Monitoring activated. + +Performance monitoring counters are active + + 2 + + + Backward reporting, BR, cells are generated. + +Performance monitoring counters are active + + 4 + + + FPM, Forward Performance Monitoring activated. + +Backward reporting, BR, cells are generated. + +Performance monitoring counters are active + + 6 + + + + + Nominal performance monitoring, PM, blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + Nominal performance monitoring, PM, block size, 2e7 (2 to the power of 7). + 128 + + + Nominal performance monitoring, PM, block size, 2e8 (2 to the power of 8). + 256 + + + Nominal performance monitoring, PM, block size, 2e9 (2 to the power of 9). + 512 + + + Nominal performance monitoring, PM, block size, 2e10 (2 to the power of 10). + 1024 + + + Nominal performance monitoring, PM, block size, 2e11 (2 to the power of 11). + 2048 + + + Nominal performance monitoring, PM, block size, 2e12 (2 to the power of 12). + 4096 + + + Nominal performance monitoring, PM, block size, 2e13 (2 to the power of 13). + 8192 + + + Nominal performance monitoring, PM, block size, 2e14 (2 to the power of 14). + 16384 + + + Nominal performance monitoring, PM, block size, 2e15 (2 to the power of 15). + 32768 + + + + + + Service category Constant Bit rate, CBR. + 1 + + + Service category Unspecified Bit rate, UBR. + 2 + + + Service category Unspecified Bit rate+, UBR+. UBR+ guarantees a certain bandwidth. If higher bandwidth is used it will be handled as UBR. + 3 + + + + + ATM's Quality of Service classes. + +The ATM layer system provides four QoS classes, numbered 1 to 4, where CLASS_ONE gives the best QoS in regards to Cell Loss Ratio <CLR> and Cell Delay Variation <CDV> and CLASS_FOUR doesn't give any QoS guarantees. CLASS_ONE and CLASS_TWO are the only classes applicable for real time traffic. + + CDV < 1 ms (milliseconds), CLR < 10e-8. Typically used by timing unit. + 1 + + + CDV < 1 ms, CLR < 10e-7. Typically used for speech. + 2 + + + CLR < 10e-5. Typically used for signalling. + 3 + + + Typically used for IP. + 4 + + + + + The attributes in this struct represents the ATM header, (vpi, vci, pti), of the last recieved unexpected cell. + + The ATM header vpi. + + 0 + + + + The ATM header vci. + + 0 + + + + The ATM header pti. + + 0 + + + + + + This MO structures the transport network of the managed element. It is created automatically and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, TransportNetwork=1. + + + Label free for use. + + + "" + + + + + + + + + + + + + This action returns a sequnce of Aal5TpVccTp MOs that is unreserved and executes on an MP. + +Also the following condition has to be fullfilled: + +MinAal5Sdu = min (fromUserMaxSduSize, toUserMaxSduSize) + +roundedDownSdu = (MinAal5Sdu - (MinAal5Sdu modulo 4) +4) + +roundedDownSdu > low boundry for maxSduSize (in NniSaalTp) + +Note that the values for fromUserMaxSduSize and toUserMaxSduSize is the actual values set in the Aal5TpVccTp MO. +Also note that the attributes minAal5Sdu and roundedDownSdu is used internaly in this action. + +Note! This action requires a transaction. + + + + + + + + This action returns a sequnce of Aal5TpVccTp MOs that is unreserved and executes on an MP. + +Also the following condition has to be fullfilled: + +MinAal5Sdu = min (fromUserMaxSduSize, toUserMaxSduSize) + +roundedDownSdu = (MinAal5Sdu - (MinAal5Sdu modulo 4) +4) + +roundedDownSdu > low boundry for maxSduSize (in UniSaalTp) + +Note that the values for fromUserMaxSduSize and toUserMaxSduSize is the actual values set in the Aal5TpVccTp MO. +Also note that the attributes minAal5Sdu and roundedDownSdu is used internaly in this action. + +Note! This action requires a transaction. + + + + + + + + This action returns a sequence of all unreserved Aal2PathVccTp's that have an Aal2PathId that has not been +used by another Aal2PathDistributionUnit under the same parent (Aal2Ap). + +Note! This action requires a transaction. + + + + + + + + + + + + + + This action returns a sequence of all ReliableProgramUniters that has not reached the maximun number of possible reservations +and has not already been used by other Aal2PathDistributionUnit MO's (if exists) under the same parent (Aal2Ap MO). + +Note! This action requires a transaction. + + + + + + + + + + + + + + This action returns a sequence of PlugInUnits that is unreserved. + +Note! This action requires a transaction. + + + + + + + + This action returns a sequence of Ds0Bundle MOs that is unreserved and only has one (1) timeSlot set in the listOfTimeSlots. +The attribute tdmMode in these Ds0Bundles must be enabled. + +Note! This action requires a transaction. + + + + + + + + + + The Slot MO is used to represent a slot in a subrack. A slot can hold a plug-in-unit, a board, (represented by PlugInUnit MOs). + +The number of slots in a subrack is specified when defining the subrack. + +The system will automatically create the right number of Slot MOs in the subrack at creation of the Subrack MO. +This MO cannot be deleted by an operator. + +The local distinguished names of this MO's are select with identity Slot=1 in the leftmost slot with incremental numbering towards the right in the subrack.. + + + A user friendly name associated to the managed object + + + + + "" + + + + + Gives the state of the slot. + + + + + + + free + + + + + The number of the position from the left side, starting from 1. + + + + + + + + + + + + + + + + + List of reserving MOs. + + + + + + + + + + This product data describes the plug-in-unit that is presently inserted. The information is only available when slotState = used. + + + + + + + + + + + The upgradeGroupId is able to group a number of PIUs, all in the group can be upgraded at the same time. + +If upgradeGroupTypeName is "", this attribute is not used. + + + + 0 + + + + + The upgradeGroupTypeName, together with the upgradeGroupId, define an upgrade group. + + + + "" + + + + + + + The Managed Object MO is not part of the model. It is only used to have valid reference types for certain attributes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO is used to represent the termination of an external VC link in the node. + +Note that a maximum of 10 000 MO of this kind may be configured in a node. + +Note! The performance monitoring counters in the VclTp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + For free use. + + + "" + + + + + Virtual Channel Idenitifier, VCI, value for this Virtual Channel Link, VCL. + +Range: 32 - 65535. + + + + + + + 32 65535 + + + + + + Reference to the AtmTrafficDescriptor profile. + + + + + + + + + User that have reserved this VclTp. + + + + + + + + + The operational state of the VclTp. + + + + + + disabled + + + + + Performance monitoring counter for number of received ATM cells. + + + + + + + + 0 + + + + + Performance monitoring counter for number of transmitted ATM cells. + + + + + + + + 0 + + + + + The availability status of the VclTp. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + Used by VclTp to inforce a Virtual Channel end-to-end loopback. +false=Failed, true=Succeded. + +Note! This action requires a transaction. + + + + + + + + + + The Managed Element MO is the top MO in the MOM. A management application will communicate with the Managed Element MO for the purpose of monitoring it and controlling it. + +The ManagedElement MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1. + + + For free use. + + + "" + + + + + This attribute gives information about geographical location (e.g. place name). + + + + 0 255 + + "" + + + + + This attribute gives a logical name of a site. + + + + + + 0 255 + + "" + + + + + This attribute describes the product type and is always set to the value "Node". + + + + + Node + + + + + This attribute describes the implemented functionality. + + + + 0 12 + + "" + + + + + This attribute uniquely identifies the product (e.g. ROF123). + + + + 0 24 + + "" + + + + + This attribute identifies the version of the product (e.g. R2A). + + + + 0 7 + + "" + + + + + + + + + + + + + Restart the node with an unconditional reload. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + This Managed Object is used as a structural element for the network element, i.e. it only acts as a container for other MO:s. This MO structures the equipment of the network element. + +The local distinguished name of this MO is ManagedElement=1, Equipment=1. + + + Label free for use. + + + "" + + + + + + + + + + + + + + + This MO is used to represent a subrack. + + + A free tag that a user can associated to the this managed object. The value has no relevance for the managed system. + + + "" + + + + + A reference to a SwitchModule ManagedObject, from which the SwitchModule number can be retrived. That number describes how the subrack is connected to the node, i.e. how the subrack’s cables are connected to the hub subrack. (The hub subrack has switch module number ’0’). + + + + + + + + + There can only be one hub subrack in the node. The hub subrack is used to control switching and synchronization for the complete node. + + + + + + + + + + + This attribute describes the product type and is always set to the value "HW". + + + + + + "HW" + + + + + This product data describes the subrack that is configured to be installed. + + + + + + + + + The position of this subrack within a cabinet. +The purpose of this attribute is to help an operator locate the source of an error by letting the system put this +information in alarms. The system does not use this information in any other way i.e. it does not affect the +operation of the system. +The subrack position is an integer (1-n) stating the cabinet Id, starting from the left and a letter (A-Z) stating +the Subrack vertical position starting from the ground, e.g. 5C. + + + "" + + + + + The position of the cabinet (within a group of other cabinets) in which this subrack is placed. +The purpose of this attribute is to help an operator locate the source of an error by letting the system put this information in alarms. The system does not use this information in any other way i.e. it does not affect the operation of the system. + + + "" + + + + + + + + + + + + + Defines the number of slot in the subrack. The default value is 28. + + + + + + + + 1 28 + + 28 + + + + + The operational product data describes the subrack that is actually installed. + + + + + + + + + + + + A reference to the SwAllocation MO that has reserved this Subrack for Fan MO upgrades.. +The attribute is set/cleared by internal actions. + + + + + + + + Removes the given number of Slot MOs from the model. The Slots with the highest slotNumber are removed. After the action no Slot will have apn = 0. +The attribute numberOfSlots will be udated. + +If there is a child MO the action will fail and the MOHasChildrenException is thrown. + +Note! This action requires a transaction. + + + + + The number of slots to remove. + + + + + + + + + + This MO is used to represent software installed in the file system. + +LoadModule MO can represent files with executable code, files with text information +(COI) or directories in Cello file system. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + +Note! In order for a program to be reliable the following conditions must be fulfilled: + +1. The attribute 'loaderType' must be set to 'OseLoader'. +2. The attribute 'oseProgramLoadClass' must be set to a value > 100. +3. The program must execute on a MP (Main Processor). + + + + Free tag for marking this managed object. + + + "" + + + + + Product information data. + + + + + + + + + The path to this load module in the file system, including the file name. + +Example: /c/load_modules/CXC112874R1A01 +where /c/load_modules/ is the directory and CXC112874R1A01 is the file name. + + + + + + + + + The type of the program loader. + +Note! This corresponds to LoaderName in the Upgrade Control File (UCF). + + + + + OseLoader + + + + + This attribute must have a value if the loaderType attribute equals other. + + + + + "" + + + + + A recommendation to the system to (if possible) cache this load module close to where its program(s) execute(s), e.g. in a flash file system. The purpose of this attribute is to enable faster loading at restart of programs referring to this load module. + + + + + + + + no + + + + + The file format (RPDOUT, html, java, fpga, ...). + + + "" + + + + + Specifies in which load phase programs of this load module should be started. + +Note: If the LoadModule is a java archive file (.jar) it will be loaded in the load phase of the java machine rather than according to its own oseProgramLoadClass. + + + + + application + + + + + Reliable program identity. +Compare this to the reliableProgramLabel in ReliableProgramUniter MO. + + + + + "" + + + + + Indicates if the load module is a file or directory. + + + + + false + + + + + This attribute sets the size of the program pool size. In the referenced loadModule there is +possible to set this value at create. +This value will then be fetched by program and used at create if no value is submitted at +create of the program Mo. +The referenced load module has a default size defined at compile time which is used if no +value is submitted at create of loadModule or the program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Unit is byte. + + + + + 0 + + + + + This attribute sets the size of the program heap size. In the referenced loadModule there is possible to set this value at create. This value will then be fetched by program and used at create if no value is submitted at create of the program Mo. +The referenced load module has a default size defined at compile time which is used if no value is submitted at create of loadModule or the program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Unit is byte. + + + + + 0 + + + + + Indicator whether the (OSE) program must be a singleton or not. + + + + + false + + + + + Contains all class that are to be initialised and started when the JVM restarts. +Technical note: The class name must specify the full package and class name in standard Java syntax, e.g. "se.ericsson.cello.X" ; must implement the se.ericsson.cello.moframework.Mopplet interface and be found in this LoadModule. + + + + + + + + + + + + + + + + + + + + Indicates whether this MO has been reserved by the UpgradePackage MO or not. + + + + + false + + + + + + + This MO is used to administer synchronization references for the network synchronization function and to view the system clock state of Timing Unit boards. + +Synchronization can have 0 to 8 relations to other MOs. The only valid MOs where relations can exist are E1Physpathterm, J1Physpathterm, T1Physpathterm, Os155SpiTtp, TU Synchronization Reference, and ManagedObject (for the non-Cello RXI820 MO) MOs. Note that maximum number of relations to these MOs is 8 all together. + +The synchronization MO is automatically created and cannot be deleted. + +Note: An external ManagedObject that wishes to be connected to the Synchronization MO must implement the following interface se.ericsson.cello.equipment.SyncReservable! + +The local distinguished name of this MO is ManagedElement=1,TransportNetwork=1,Synchronization=1 + +. + + + Label free for use. + + + "" + + + + + Controls whether synchronization reference degradation (e.g. signal level degradation) is interpreted as a synchronization reference fault or not. Attribute value is only applicable for traffic carrying synchronization references + + + degrNotFault + + + + + State of system clock signal on Timing Unit A. +Note that system clock generated by TU A (TU in slot 4) has higher priority than TU B (TU in slot 5) system clock, i.e. each device board uses system clocks according to this priority order. + + + + + unknownMode + + + + + State of system clock signal on Timing Unit B. Note that system clock generated by TU A (TU in slot 4) has higher priority than TU B (TU in slot 5) system clock, i.e. each device board uses system clocks according to this priority order. + + + + + unknownMode + + + + + Set of synchronization reference physical resources. An MO reference to an TU synchronization reference MO implementation. +A synchronization reference in added to the system by using action AddSyncRefResource. +Note: if this attributes has value "Non-existing MO reference" then all the respective attributes of type sequence of 8 are not applicable. + +Note: The length of this sequence is always 8. + + + + + + 8 + + + + + + Synchronization reference priority. +1 represents the highest and 8 the lowest priority. Every synchronization reference must have unique priority value. Value 0 means not applicable, that no synchronization with this priority is defined. +This attribute is mandatory when adding a synchronization reference to the system (by using action addSyncRefResource). +A priority value can be changed with the changeSyncRefPriority action provided that the priority is not already assigned to some other SyncRefResource. + +Note: The length of this sequence is always 8. + + + + + + 0 8 + + 0 + + 8 + + + + + Set of synchronization reference activity attributes. + +Note: The length of this sequence is always 8. + + + + + + + inactive + + 8 + + + + + + Set of synchronization reference status attributes. + +Note: The length of this sequence is always 8. + + + + + + + failed + + 8 + + + + + + + + + + + + + + Indicates if the node is redundant from Network Synchronization functions point of view. + + + SYSTEM_CLOCK_USERS_USE_PLANE_A + + + + + This action adds one synchronization reference to the system. As a result of successful action, one set of attributes (attributes of type sequence of 8) is added to Synchronization MO. +Parameters: +syncReference: Managed object implementation, to which a mo-reference is to be added. See description of attribute SyncReference. +syncPriority: Priority of synchronization reference. Each synchronization reference must have unique priority value, this must be checked by synchronization MO. + +Description of exceptions: +- AlreadyRegistered: this reference is already registered +- MaxNoOfRefRegistered: maximum number (8) of synchronization references already present +- PriorityAlreadyInUse: syncPriority is identical with an existing synchronization reference priority +- PriorityOutOfRange: invalid syncPriority value +- InvalidMoReference: invalid syncReference for registration as a synchronization reference (invalid MO type) +- NotPermitted: syncReference does not allow SyncReserve to be performed + +Note: An external ManagedObject that wishes to be connected to the Synchronization MO must implement the following interface se.ericsson.cello.equipment.SyncReservable! + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + This action removes one synchronization reference that has previously been added. +(In future releases, this action should include a check whether the synchronization reference to be removed is the only existing synchronization reference. In that case, the user is asked for a confirmation to remove the last synchronization reference.) +Parameters: +syncReference: Managed object implementation, to which a mo-reference currently exists, but is now to be removed. See description of attribute SyncReference. + +Description of exceptions: +- NotRegistered: synchronization reference is not registered + +Note! This action requires a transaction. + + + + + + + + + + + + + This action changes the synchronization priority of one previously registered synchronization reference resource. +Parameters: +syncReference: Managed object implementation, for which the synchronization priority is to be changed. See description of attribute syncReference. +syncPriority: The new priority of synchronization reference. Each synchronization reference must have unique priority value, this must be checked by synchronization MO. + +Description of exceptions: +- PriorityAlreadyInUse: syncPriority is identical with an existing synchronization reference priority +- PriorityOutOfRange: invalid syncPriority value +- NotRegistered: synchronization reference is not registered + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + This action resets the detected Loss of Tracking error condition of one synchronization reference. After reset the synchronization reference is usable again. +Parameters: +syncReference: Specifies the synchronization reference for which the Loss of Tracking status is to be reset. + +Description of exceptions: +- NotRegistered: synchronization reference is not registered + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This Managed Object represents an SCCP Local Access Point. An SCCP AP instance is a logical point in the SCCP network at which an SCCP user can access the services provided by the SCCP and the SCCP can deliver its services to the SCCP user. The SCCP Access Point is identified by a SubSystem Number (SSN). + +A local SccpAp represents an access point in the own node. + +The performance monitoring counters found in SccpApLocal MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a shutdown request from the CLI (Cluster Interface). + + + + + + + + + + User label for free use. + + + "" + + + + + The operational state of the SCCP AP. The operability of the SCCP AP is described by this attribute which has two possible values: + +Disabled: The SCCP AP is totally inoperable and unable to provide the service to the user. + +Enabled: The SCCP AP is partly or fully operable and available for use. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The sub system number, SSN, of the SCCP Access Point. Note that this has to be a unique number. + +If the SccpAp is local then the SSN has to be unique among all other SccpAp MOs under the same SccpSp MO. + + + + + + + 2 255 + + + + + + The maxConn attribute specifies the max number of connections allowed for this SCCP Access Point. It is only valid for local SCCP Access Points. + + + + + + + 1 524288 + + + + + + List of reserving MOs. + + + + + + + + + + Controls adding of OPC from routing label to Calling Party Address if absent. + +False = Do not add OPC to Calling Part Address. +True = Add OPC to Calling Part Address. + + + + + + false + + + + + + + The Signalling Connection Control Part, SCCP, Signalling Point, SP, MO is the placeholder for all SCCP related managed objects. + +Startime for accounting is set by attributes accountDateFileOutput and accountTimeFileOutput. +The attribute accountPeriodFileOutput sets period for the accounting record to be stored on the /c file system. +The accounting is stopped by setting the accountPeriodFileOutput to zero (0). +NOTE: The SRP function and SccpAccountingCriteria MO's should only be created for one signalling stack, i.e one PIU. + +Note! The guiding values that can be found for some attributes is to be regarded as a recommendation for these attributes. +Depending on the size of the network, traffic load, use and so forth it might be neccesary to set values for these attributes outside the guiding values. + + + + + + + + + + For free use. + + + "" + + + + + The operational state of the SCCP SP. The operability of the SCCP SP is described by this attribute which has two possible values: + +Disabled: The SCCP SP is totally inoperable and unable to provide the service to the user (e.g. if the processor is not usable). + +Enabled: The SCCP SP is partly or fully operable and available for use. + + + + + + disabled + + + + + The identity of the L3 Signaling Point used by this MO. + + + + + + + + + This attribute sets the priority for the Subsystem Test message when issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. +Coding of the message priority: +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 1 + + + + + This attribute sets the priority for the Inactivity Test message when issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. +Coding of the message priority: +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 1 + + + + + This attribute sets the priority for the connection release message when issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. +Coding of the message priority: +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 1 + + + + + This attribute sets the priority for all the other messages which are issued by the SCCP itself. When a message is transferred from the SCCP the message priority uses the two spare bits in the SIO. + +Coding of the message priority: + +0 Lowest priority +1 +2 +3 Highest priority + + + + 0 3 + + 0 + + + + + Date for accounting file output. +Format in ASCI-code: yyyymmdd +yyyy = 0000-9999 +mm = 01-12 +dd = 01-31 + +Note! This is the start date for the output. + + + "00000000" + + + + + Time for accounting file output. +Format in ASCI-code: hhmm +hh = 00-23 +mm = 00-59 + + + "0000" + + + + + Period for accounting file output. +Format: number of half hour. +Range = 0, 1, 2, 4, 6, 8, 12, 16, 24, 48 + +Note! if set to 0 (zero) the output will be stopped. + + + 0 + + + + + The upper connection threshold allow the user to specify the level at which the upper connection threshold notification is triggered. The thresholds must be given as a percentage of the maximum number of connection resources made available for the entire SCCP. + + + + 0 100 + + 80 + + + + + The lower connection threshold allow the user to specify the level at which the lower connection threshold notification is triggered. The thresholds must be given as a percentage of the maximum number of connection resources made available for the entire SCCP. The value must be less then UpperConnThres. + +The maximum value is less or equal to the upper connection threshold + + + + 0 100 + + 50 + + + + + There are two ways to construct a UDTS from a UDT, the XUDTS will be constructed in the same way. One way is to only swap the pointers to “Called Party Address” and “Calling Party Address” in a UDT message when constructing a UDTS. The other way is to swap data. How this is done in the SCCP is configurable. The coding and interpretation is as follows: +0, swap data –“Called party Address” will be sent before “Calling party Address” +1, swap pointers–“Called party Address” will be sent after “Calling party Address”. + + + + 0 1 + + 1 + + + + + The SCLC hop counter is a parameter that is decremented for each performed GT translation for SCLC messages on the way to the end destination. If decrementing the counter results in the value of zero in a non-end destination node, the SCCP initiates the appropriate error procedure. + + + + 1 15 + + 8 + + + + + The SCOC hop counter is a parameter that is decremented for each performed GT translation for SCOC messages on the way to the end destination. If decrementing the counter results in the value of zero in no end destination node, the SCCP initiates the appropriate error procedure. + + + + 1 15 + + 8 + + + + + Connection establishment control timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 600 - 1200, Default 600 + + + + + 1 65535 + + 600 + + + + + Send inactivity control timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 3000-6000 +Default 3000 + + + + 1 65535 + + 3000 + + + + + Receive inactivity control timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 6600-12600 +Default 6600 + + + + 1 65535 + + 6600 + + + + + Connection release timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 100-200 +Default 100 + + + + 1 65535 + + 100 + + + + + Congestion timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 10-2550 +Default 300 + + + + 1 65535 + + 300 + + + + + Subsystem Status Test timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 10-2550 +Default 300 + + + + 1 65535 + + 300 + + + + + Connection response waiting timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 100-200 +Default 150 + + + + 1 65535 + + 150 + + + + + Reassembly timer. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 100-200 +Default 150 + + + + 1 65535 + + 150 + + + + + Guard timer for program restart not applicable for this CPP version. Instead a restart counter is used to improve restart performance. + +Unit: deciseconds (0.1 seconds). + +Guiding values; +Range 13800-15000 (23-25 minutes) +Default 1380 (23 minutes) + + + + + 1 65535 + + 13800 + + + + + The SMI (Subsystem Multiplicity Indicator) is always ignored for incoming messages. This SCCP can however be configured to insert a specific SMI value in outgoing messages. The coding and interpretation is as follows: + +Coding Comment + 0 | Affected Subsystem multiplicity unknown. + 1 | Affected Subsystem is solitary. + 2 | Affected Subsystem is duplicated. + 3 | Spare. + + + + 0 3 + + 0 + + + + + The use of SCMG functions. + +SST = SCCP Subsystem Test message. +SSA = SCCP Subsystem Allowed message. +SSP = SCCP Subsystem Prohibited message. +SSC = SCCP Subsystem Congested message. + +The attributes contained in the struct is: +initiateTimerTcon, +allowRemoteBroadcast, +useSST, +useSSP, +sendSSA, +sendSST + + + + + + + + Connection Oriented SCCP Signaling Relay Point (SRP-CO) and Maximum number of Relayed Connections is not used in this CPP version. + + + + + + + 1 524288 + + + + + + The identity of the reserving MO. + + + + + + + + + + Performance monitoring counter for number of sent UDT's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received UDT's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent UDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received UDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent XUDT's. + + + + + + + + 0 + + + + + Performance management counter for number of received XUDT's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent XUDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received XUDTS's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent CR's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received CR's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent DT1's. + + + + + + + 0 + + + + + Performance monitoring counter for number of received DT1's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent ERR's. + + + + + + + + 0 + + + + + Performance monitoring counter for number of received ERR's. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent SSA's, subsystem allowed. + + + + + + + 0 + + + + + Performance monitoring counter for number of CREF messages received from NL. + + + + + + + 0 + + + + + Performance monitoring counter for number of CREF messages sent to NL. + + + + + + + + 0 + + + + + Performance monitoring counter for number of RLSD messages received from NL. + + + + + + + 0 + + + + + Performance monitoring counter for number of RLSD messages sent to NL. + + + + + + + 0 + + + + + Performance monitoring counter for number of connections in use that has exceeded the high watermark threshold. + + + + + + + 0 + + + + + Performance monitoring counter for number of connections in use that has receded the low watermark threshold. + + + + + + + 0 + + + + + Performance monitoring counter for number of received LUDT messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent LUDTS messages. + + + + + + + 0 + + + + + + + The Signalling Connection Control Part Routing Control (SCCP SCRC) MO holds information about the SCCP routing control. + + For free use. + + + "" + + + + + + + + + + + + + Performance monitoring counter for number of routing failures. + + + + + + + 0 + + + + + Performance monitoring counter for number of connect failures. + + + + + + + 0 + + + + + Performance monitoring counter for number of Hop counter violations. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to no translation for Nature of Address field. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to no translation of specific address. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to destination point code not available. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to network congestion. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to destination subsystem unavailable. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to unknown reason. + + + + + + + 0 + + + + + Performance monitoring counter for number of routing failures due to unequipped subsystem. + + + + + + + 0 + + + + + + + The Program MO represent the executable software on the target hardware. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + +Note! Some programs are not possible to restart or can take part in an RPU. For more information please refer to the LoadModule MO. + + + + Label free for use. + + + "" + + + + + This attribute gives information about which load module the program is instantiated from. + + + + + + + + + This attribute shows whether the program has normal performance capability or not. + + + + + + disabled + + + + + This attribute shows whether the program is permitted to enter operational state enabled or not after a PIU restart. The default state is disabled in order to avoid that an operating program and a new version of the same program have its startState enabled at the same time. + +It is used on all types of node restarts and restart of PlugInUnit with restartCause = piuRestartUpgrade. + + + disabled + + + + + This attribute sets the size of the program heap size. + +The value in the referenced LoadModule is fetched by program and used at create if no value is submitted at create of the program MO. + +The referenced load module has a default size defined at compile time wich is used if no value is submitted at create of loadModule or the program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + +Note: Setting of this attribute will have no effect until the program is restarted. + + + 0 + + + + + This attribute sets the size of the program pool size. In the referenced LoadModule there is possible to set this value at create. + +The value in the referenced LoadModule is fetched by program and used at create if no value is submitted at create of the program MO. + +The referenced load module has a default size defined at compile time wich is used if no value is submitted at create of +LoadModule or the Program Mo. + +Note! The value of this attribute is overwritten during Software Upgrade. + +Only working for MP-Program + +Unit is bytes. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + +Note: Setting of this attribute will not have any effect until the program is restarted. + + + + + 0 + + + + + This type specifies the time that a program have to execute without faults, until the restart counter is reset. The time value is interpreted as seconds. + +restartTimer= -1 : Forever, implies that the restart counter is only reset when the PIU is restarted. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + + + + -1 + + 60 + + + + + This attribute specifies the number of times that a program can restart, without escalation to a PIU restart. The possible values are: + +restartCounterLimit = -1 : Unlimited, means never restart PIU, regardless of the number of times the specific program restarts. + +Note: If the program is a child to a Fan Mo this attribute is irrelevant. + +Note! The value 3 means 3 restarts, hot, warm and finally as a last resort PIU restart. + +Note! The program escalates to a PIU restart when the number of restarts reaches the value set for this attribute. +I.e. if for example the value is set to 5, escalation to PIU restart will occur at the fifth restart. + + + + -1 + + 3 + + + + + + + + + + + + + Request to restart the program. +Only valid for MP programs. + +Note! This action does not require a transaction. + + + + + + + + The UniSaal Profile MO represent and keeps attribute values used by one or more UNI SAAL termination point MOs. + + Label free for use. + + + "" + + + + + List of reserving MOs. + + + + + + + + + + See structure UniSaalProfileData + + + + + + + + + + + + + + + + + + The MO represents an access point for a user where a UNI SAAL connection is terminated. The access point depends +on an AAL5 connection termination located on the same processor. + +UniSaalTp can only terminate on a Mp processor. + +Note! The performance monitoring counters found in NniSaalTp MO is set to zero when the Mo and its RO is created. +These counters are not reset unless there occurs a fault situation that demands a restart and recreation of the ROs. +Also note that some of these counters are reset based on other conditions. For more details please refer to the +descriptions of the performance monitoring counters in this MO. + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the UniSaalTp MO. + + + + + + disabled + + + + + The identity of the reserving MO. + + + + + + + + + Reference to a UniSaalProfile MO. + +The maxStat attribute defined in the UniSaalProfile MO is dependent on the AAL5 SDU size defined in the Aal5TpVccTp MO. See the description of the maxStat attribute in the UniSaalProfile MO. + + + + + + + + + + + Reference to an Aal5TpVccTpMo. + +Note: The Aal5 termination point must terminate on a main processor, MP. + + + + + + + + + Maximum SAAL SDU size. The attribute is dependent on the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The 'maxSduSize' may not exceed the AAL5 maximum SDU size (the lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). + +Example: If 'fromUserMaxSduSize' is set to 256 and 'toUserMaxSduSize' is set to 512 in the Aal5TpVccTp MO, the ' maxSduSize' in the UniSaalTp MO may not exceed 252. + +(i.e. maxSduSize <= the aal5MaxSduSize - 4 bytes) + +Note! When setting the value of 'maxSduSize' the 4 bytes used by the SAAL layer for the SAAL header has to be considered. + +Note! The upper limit of 2044 (2048 including the SAAL header) is due to limitations on the AAL5 layer. + + + + + + + 128 2044 + + 128 + + + + + Number of successfully sent SDUs. +Counts the number of successfully sent messages to the +application using SAAL. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of successfully received SDUs. +Counts the number of successfully received messages from + the application using SAAL. Reset when the link goes + InService or the counter "overflows". + + + + + + 0 + + + + + The accumulated time (in seconds) the signalling link has + been in service (in assured data transfer mode) since it was created. If the link is down the value 0 is returned. + + + + + + 0 + + + + + Number of all Signalling Link failures. +Is a total sum of the error counters: + - Number of protocol errors + - Number of unsuccessfully retransmissions + - Number of NoResponses + - Number of other errors + + + + + + 0 + + + + + Number of no response. This counter is increased when SSCOP (Service Specific Connection Oriented Protocol) +send an MaaError with error code P. +For details refer to ITU-T Q.2110 - B-ISDN AATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP); (7/94). +Counts the number of no responses detected the last 30 minutes. + + + + + + 0 + + + + + Number of local congestions. +This counter is increased when the sum of SAAL send and retransmission buffers are filled to more than 90%. + + + + + + 0 + + + + + Number of remote congestions. +This counter is increased when the remote side gives SAAL no credit. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of sequences data loss. +Counts the number of SD loss detected the last 30 minutes + + + + + + 0 + + + + + Number of unsolicited or inappropriate PDUs. This counter is increased when SSCOP (Service Specific Connection Oriented Protocol) +send an MaaError with error code Q. +For details refer to ITU-T Q.2110 - B-ISDN AATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP); (7/94). +Counts the number of protocol errors detected the last 30 minutes. + + + + + + 0 + + + + + Number of unsuccessful retransmissions. +Counts the number of unsuccessfully retransmissions detected the last 30 minutes. + + + + + + 0 + + + + + Number of other list element errors. This counter is increased when SSCOP (Service Specific Connection Oriented Protocol) +send an MaaError with error code Q-U. +For details refer to ITU-T Q.2110 - B-ISDN AATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP); (7/94). +Counts the number of other errors detected the last 30 minutes. + + + + + + 0 + + + + + + + This MO represents an E1 (i.e. 2 Mbit/s) physical interface in the node. The E1PhysPathTerm MO does not define which type of traffic (TDM or ATM) that the interface should support. +Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +Note! The performance monitoring counters in the E1PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + User label for free use. + + + "" + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The actual Line number on the board. + + + + + + + + 1 8 + + + + + + The identity of the reserving AtmPort MO. + + + + + + + + This attribute describes the current Loopback State of this physical path termination. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + The administrative state. + + + locked + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + + + + + + + + + Indicates what Cyclical Redundancy Check 4 Mode that is being used. + + + AUTOMATIC + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + + + + + 0 100 + + 30 + + + + + How many bad seconds in a row that causes a Degraded Signal alarm. + + + + + + 2 10 + + 7 + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The identity of the reserving Synchronization MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO represents an J1 (i.e. 1.5 Mbit/s) physical interface in the node. The J1PhysPathTerm MO does not define which type of traffic (TDM or ATM) that the interface should support. +Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +The performance monitoring counters in the J1PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + User label for free use. + + + "" + + + + + The actual Line number on the board. + + + + + + + + 1 8 + + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The administrative state. + + + locked + + + + + Supported interfaces is defined in J1Types + + + j1_G + + + + + The identity of the reserving AtmPort MO. + + + + + + + + + + Maximum allowed BER(Bit Error Rate). Degraded signal (DEG) if BER > degThreshold. The attribute gives a maximum BER of 10e-X, where X ranges from 5 to 9 (default 6) + + + + + 3 9 + + 6 + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + Performance monitoring counter for Errored Seconds, ES. + + + + + + + 0 + + + + + Performance monitoring counter for Severly Errored Seconds, SES. + + + + + + 0 + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The identity of the reserving Synchronization MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO is used to represent the point in the node where an AAL0 connection is terminated. At this point the user exchange SDUs with its peer at the remote end of the AAL0 connection. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + + + Label free for use. + + + "" + + + + + This attribute specifies on what processor the termination point resides. It could either be a board processor or main processor (MO type PlugInUnit), or a SP processor (MO type Spm). + + + + + + + + + The operational State reflects the operational state of the end points and the belonging node connections. + + + + + + + + disabled + + + + + The identity of the reserving MO. + + + + + + + + The virtual channel to which this MO is termination. + + + + + + + + + + + + + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. + +Activates VC end to end continuityCheck according to ITU.T rec I.610. + + + false + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + NOM_PM_BLKSIZE_2_10 + + + + + PM mode is set to indicate type of performance monitoring mode (i.e. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Performance monitoring counter for forwarded lost cells. + + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + + + This MO is used to represent the point in the node where an AAL5 connection is terminated. At this point the user exchanges SDUs with its peer at the remote end of the AAL5 connection. + +Note! The 'mtuSize' on the IpAtmLink MO does not include 8 bytes required for the LLC/SNAP header and this should be taken into consideration when setting the SduSize on the Aal5TpVccTp MO. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0.. + + User label for free use. + + + "" + + + + + This attribute specifies on what processor the protocol is terminated. It could either be a board processor or main processor (PlugInUnit) or a SP processor (Spm). + + + + + + + + + The virtual channel to which this MO is termination. + + + + + + + + + The operational State reflects the operational state of the end points and the belonging node connections. + + + + + + + + disabled + + + + + The maximum SDU size in number of octets received from the user (called maxIngressSduSize in the FRO domain). + +The allowed range is dependent on the processorType. +SP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +BP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +MP:LowestMaxSduSize =1, HighestMaxSduSize=2048 + + + + + + + 1 2048 + + + + + + The maximum SDU size in number of octets sent to the user (called maxEgressSduSize in the FRO domain). This attribute is controlled by the processor type. + +The allowed range is dependent on the processorType. +SP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +BP: LowestMaxSduSize =1, HighestMaxSduSize=1600 +MP:LowestMaxSduSize =1, HighestMaxSduSize=2048 + + + + + + + 1 2048 + + + + + + The attribute is set by the action reserve from a user of Aal5TpVccTp. It could either be a Cello user like IpAtmLink/UniSaalTp or a node application. + + + + + + + + + + + + + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. Continuity check both enables generation of CC cells as well as detection of LOC + + + + false + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + + NOM_PM_BLKSIZE_2_10 + + + + + PM mode is set to indicate type of performance monitoring mode (i.e. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Performance monitoring counter for number of lost forward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM, cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + + + The AtmPort MO is used to configure a physical port for ATM traffic. +ATM can be transported accross the physical layer in three distinct and different ways: + +- Normal mode + +An AtmPort MO is created with a reference to physical layer object (any of E1PhysPathTerm, +J1PhysPathTerm, T1PhysPathTerm, E3PhysPathTerm, T3PhysPathTerm, Sts3CspeTtp, E1Ttp, T1Ttp or Vc4Ttp). +The payload of that physical layer object is used to transport the ATM traffic. + +- Fractional ATM mode + +An AtmPort MO is created with a reference to a Ds0Bundle object. The Ds0Bundle specifies +in this case the timeslots on the physical layer (any of E1PhysPathTerm,J1PhysPathTerm, +T1PhysPathTerm, T1Ttp or E1Ttp) that should be used for ATM traffic. The remaining timeslots +are not used at all. +I.e. when fractional ATM is used only one Ds0Bundle can exist as a child to a physical port MO. + +- IMA mode + +In IMA mode, a number of physical ports are grouped together to form one "virtual" physical +ATM pipe. In this mode the AtmPort MO is created with a reference to an IMAGroup MO. +Please refer to the ImaGroup MO for further details. + +Note! The performance monitoring counters in the AtmPort MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again.. + + + + + For free use. + + + "" + + + + + + + + + + + + + The operational state of the ATM port. + + + + + + disabled + + + + + The availability status of the AtmPort. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for number of transmitted ATM cells through the ATM port. + + + + + + 0 + + + + + Performance monitoring counter for number of received ATM cells through the ATM port. + + + + + + 0 + + + + + This attribute returns the ATM header, (vpi, vci, pti), of the last received unexpected cell. + + + + + + + + + Reference to the physical port, IMA Group or Ds0Bundle used by the ATM port. + +The possible MOs are: +E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E3PhysPathTerm, T3PhysPathTerm, Sts3CspeTtp, Sts1SpeTtp, Vc4Ttp, E1Ttp, T1Ttp, Ds0Bundle and ImaGroup. + + + + + + + + + + Performance monitoring counter for errored seconds with discarded cells due to protocol errors (unexpected, UNEX, events). + +I.610: With protcol errors is meant the reception of cells with either a non-standardized or a non-currently allocated header value. + + + + + + 0 + + + + + Header Error Correction. + +This attribute specifies if the AtmPort should detect and correct single bit errors or detect multiple bit errors in the ATM header. + + + + + + true + + + + + + + This MO represents an MTP3b Access Point (in a remote node). An MTP3b AP is a logical point in the MTP network at which an +MTP3b user can access the services provided by MTP3b and the MTP3b can deliver its services to the MTP3b user. + +The performance monitoring counters found in Mtp3Ap MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + + + + User label for free use. + + + "" + + + + + The routeSetId attribute points out the MTP3b Signalling Route Set (SRS) to which the Mtp3bAp MO is connected. + + + + + + + + + The serviceInd attribute (Service Indicator, SI) is used by traffic handling functions to perform message distribution. +Only SI=3 for SCCP usage and SI=12 for Q.2630.1 usage and SI=14 for GCP (H.248) usage have any meaning in this case. + +Full range of values for attribute SI: +0 = Signalling network management messages +1 = Signalling network testing & maintenance regular messages +2 = Signalling network testing & maintenance special messages* +3 = SCCP +4 = Telephone User Part (TUP) +5 = ISDN User Part (ISUP) +6 = Data User Part, call and circuit related messages +7 = Data User Part, facility registration and cancellation messages +8 = MTP Testing User Part +9 = Broadband ISDN User Part +10 = Satellite ISDN User Part +11 = Spare +12 = Q.2630.1 +13 = Spare +14 = H.248 +15 = Spare + +Note! The serviceIndicator has to be unique for each Mtp3bAp witin the same Mtp3bSrs. + + + + + + + 0 15 + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + List of reserving MOs. + + + + + + + + + + The operationalState attribute determines the operational status of the MTP3b AP . + + + + + + + + disabled + + + + + + + + + + + + + A performance management counter for number of received User Part Unavailable messages. + + + + + + + 0 + + + + + Performance management counter for number of Adjacent SP's that are not accessible via direct links. + + + + + + + 0 + + + + + + + The NniSaal Profile MO represents and keeps attribute values used by one or more NNI SAAL termination point MOs. + + Label for free use. + + + "" + + + + + List of NniSaalTp’s that have reserved this NniSaalProfile. + + + + + + + + + + See structure NniSaalProfileData. + + + + + + + + + + + + + + + + + + The MO represents an access point for a user where a NNI SAAL connection is terminated. The access point depends +on an AAL5 connection termination located on the same processor. + +NniSaalTp can only terminate on a Mp processor. + +Note! The performance monitoring counters found in NniSaalTp MO is set to zero when the Mo and its RO is created. +These counters are not reset unless there occurs a fault situation that demands a restart and recreation of the ROs. +Also note that some of these counters are reset based on other conditions. For more details please refer to the +descriptions of the performance monitoring counters in this MO. + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the NniSaalTp MO. + + + + + + disabled + + + + + The reserving MO. + + + + + + + + Reference to a NniSaalProfile MO. + +The maxStat attribute defined in the NniSaalProfile MO is controlled by the AAL5 SDU size defined in the Aal5TpVccTp MO. See the description of the maxStat attribute in the NniSaalProfile MO. + +Note! The consistency check of the attributes in the two MOs mentioned above could not be performed until the NniSaalTp MO was created since there is no direct relation between the objects. It is therefore the responsibility of NniSaalTp to verify the consistency. + + + + + + + + + Reference to a Aal5TpVccTp MO. + +Note: The Aal5 termination point must terminate on a main processor, MP. + + + + + + + + + Maximum SAAL SDU size. The attribute is dependent on the AAL5 maximum SDU size defined in the Aal5TpVccTp MO. The 'maxSduSize' may not exceed the AAL5 maximum SDU size (the lower of the two directions, fromUserMaxSduSize and toUserMaxSduSize). + +Example: If 'fromUserMaxSduSize' is set to 256 and 'toUserMaxSduSize' is set to 512 in the Aal5TpVccTp MO, the ' maxSduSize' in the NniSaalTp MO may not exceed 252. + +(i.e. maxSduSize <= the aal5MaxSduSize - 4 bytes) + +Note! When setting the value of 'maxSduSize' the 4 bytes used by the SAAL layer for the SAAL header has to be considered. + +Note! The upper limit of 2044 (2048 including the SAAL header) is due to limitations on the AAL5 layer. + + + + + + 128 2044 + + 128 + + + + + Number of successfully sent SDUs. +Counts the number of successfully sent messages to the +application using SAAL. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of successfully received SDUs. +Counts the number of successfully received messages from + the application using SAAL. Reset when the link goes + InService or the counter "overflows". + + + + + + 0 + + + + + The accumulated time (in seconds) the signalling link has + been in service (in assured data transfer mode) since it was created. If the link is down the value 0 is returned. + + + + + + 0 + + + + + Number of all Signalling Link failures. +Is a total sum of the error counters: + - Number of protocol errors + - Number of unsuccessfully retransmissions + - Number of NoResponses + - Number of other errors + + + + + + 0 + + + + + Number of no response. +Counts the number of no responses detected the last 30 minutes. + + + + + + 0 + + + + + Number of local congestions. +This counter is increased when the sum of SAAL send and retransmission buffers are filled to more than the congestionOnSet attribute is configured to.. + + + + + + 0 + + + + + Number of remote congestions. +This counter is increased when the remote side gives SAAL no credit. Reset when the link goes InService or the counter "overflows". + + + + + + 0 + + + + + Number of alignment or proving failures. This counter is +increased when "alignment not successful". +The counter is reset when the link is created or the counter "overflows". + + + + + + 0 + + + + + Number of sequences data loss. +Counts the number of SD loss detected the last 30 minutes + + + + + + 0 + + + + + Number of unsolicited or inappropriate PDUs. +Counts the number of protocol errors detected the last 30 minutes. + + + + + + 0 + + + + + Number of unsuccessful retransmissions. +Counts the number of unsuccessfully retransmissions detected the last 30 minutes. + + + + + + 0 + + + + + Number of other list element errors. +Counts the number of other errors detected the last 30 minutes. + + + + + + 0 + + + + + + + This MO specifies traffic and QoS parameters for virtual channel connections. + +The attributes can only be set in certain combinations: + +CBR: +ingressAtmQos /egressAtmQos: +1, 2 + +ingressAtmPcr /egressAtmPcr: +mandatory (must be specified) + +ingressAtmMcr /egressAtmMcr: +optional (not used, any value submitted will be ignored) + +UBR+: +ingressAtmQos /egressAtmQos: +3 + +ingressAtmPcr /egressAtmPcr: +optional (if shaping is used the desired rate is specified, 0 means no shaping) + +ingressAtmMcr /egressAtmMcr: +mandatory (must be specified) + +UBR: +ingressAtmQos /egressAtmQos: +4 + +ingressAtmPcr /egressAtmPcr: +optional (not used, any value submitted will be ignored) + +ingressAtmMcr /egressAtmMcr: +optional (not used, any value submitted will be ignored) + +Note that the VP sub layer only supports ServiceCategory = CBR and QoS = 1. + +Note! The performance monitoring counters in the AtmTrafficDescriptor MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + This MO's user label. + + + "" + + + + + Ingress ATM Peak cell rate (cells/s). + +Only positive values are allowed. This attribute is only mandatory when serviceCategory is CBR or UBR_PLUS. + +Note! When 'serviceCategory' is set to UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! When 'serviceCategory' is set to UBR+ the value 0 (zero) means that shaping is not used. A value larger than the minimum desired cell rate enables shaping to the rate specified. + + + + + 0 + + + + + Ingress ATM quality of service. + +This attribute can be set to Class 1 and 2 if attribute serviceCategory is set to CBR. + +This attribute can be set to Class 3 if attribute serviceCategory is set to UBR+. + +This attribute can be set to Class 4 if attribute serviceCategory is set to UBR. + + + + + + + + + + Egress ATM Peak cell rate (cells/s). + +Only positive values allowed. + +This attribute is only mandatory when serviceCategory is CBR or UBR_PLUS. + +Note! When 'serviceCategory' is set to UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! When 'serviceCategory' is set to UBR+ the value 0 (zero) means that shaping is not used. A value larger than the minimum desired cell rate enables shaping to the rate specified. + + + + + 0 + + + + + Egress ATM quality of service. + +This attribute can be set to Class 1 and 2 if attribute serviceCategory is set to CBR. + +This attribute can be set to Class 3 if attribute serviceCategory is set to UBR+. + +This attribute can be set to Class 4 if attribute serviceCategory is set to UBR. + + + + + + + + + + + Sequence of Users that are using this AtmTrafficDescriptor. + + + + + + + + + + + + Egress ATM minimum desired cell rate. + +Only positive values allowed. The attribute is only mandatory when serviceCategory is UBR+. + +Note! When 'serviceCategory' is set to CBR or UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! This attribute cannot have a value larger than for 'egressAtmPcr'. + + + + + 0 + + + + + Ingress minimum desired cell rate (cells/s). + +Only positive vaues allowed. This attribute is mandatory only when serviceCategory is UBR+. + +Note! When 'serviceCategory' is set to CBR or UBR this attribute has no relevance and the value submitted is ignored by the system. + +Note! This attribute cannot have a value larger than for 'ingressAtmPcr'. + + + + + 0 + + + + + The service category. + + + + + + + + + + + + This MO represents/models a MTP3b Signalling Route Set. + +The performance monitoring counters found in Mtp3Srs MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + + + + + + + + + + User label for free use. + + + "" + + + + + The operational state of the Mtp3bSrs MO. + +There are two possible states for the operationalState attribute: + +- enabled, the MO is partly or fully operational. +- disabled, the MO is not operational. + + + + + + disabled + + + + + The attribute is set by the local action Reserve. + + + + + + + + + + + + This flag indicates Whether automatic rerouting is performed(true) or not(false), between IP and ATM/TDM +routes when configuration is made. If set to 'false', it has to be done manually, for ex. by management actions(orders). + +Note! The attribute 'autoReroute' will always be set to 'false' regardless of value submitted. This attribute is to be removed in coming releases. + + + + + + + + + The destPointCode attribute (destination point code, DPC) represents the point code of this Mtp3b SRS MO. +The Destination Point Code in a Route Set has to be unique within each Signaling Point. + +Note! The format of destPointCode must correspond to the signallingPointCode format in the Mtp3bSp, i.e. ITU, ANSI, TTC or China. + + + + + + + 1 16777215 + + + + + + There are two possible states for the congestedLevel attribute: + +- notCongested, no change in congestion level. +- congested, change in congestion level has occurred. + + + + + + notCongested + + + + + Performance management counter for number of messages discarded from broadband to narrowband. + + + + + + 0 + + + + + Performance monitoring counter for number of received Transfer Control (TFC) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of received Transfer Prohibited (TFP) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of received Transfer Allowed (TFA) messages. + + + + + + + 0 + + + + + The route set test is only available for the Japanese Mtp3b, TTC. + +See JT-Q.707 for details. + +The test selects a route in the route set and tests it. + +Possible return codes are: + +0 : successful test +48 : unsuccessful test + +Note! This action does not require a transaction. + + + + + + The route set test is only available for the Japanese Mtp3b, TTC. + +See JT-Q.707 for details. + +The test tests the specified route. + +Possible return codes are: + +0 : successful test +48 : unsuccessful test + +Note! This action does not require a transaction. + + + + + + + + + + + + + + This MO is used to represent a plug-in-unit, that is a board inserted in a slot in a subrack. + +Note! Before deleting the PlugInUnit MO, administrativeState must be set to locked. + + + + + + + + + + A free tag that a user can associated to the this managed object. The value has no relevance for the managed system. + + + "" + + + + + The administrative state of the PlugInUnit. + +The possibility to rollback the setting of this attribute is limited. + + + locked + + + + + The operational state is set to 'enabled' when the plug-in-unit has loaded and started its 'Basic' load module. + + + + + disabled + + + + + This attribute describes the product type and is always set to the value "HW". + + + + + "HW" + + + + + A reference to an available PiuType at create of a PIU. + + + + + + + + + + Indicates which restart group the plug-in unit belongs to. +Such a group consists of a number of plug-in units where at least one must be enabled (working) or performing recovery. When all plug-in units in a group are out of function, the node is restarted. + +Must have a positive value. + +Zero indicates no group. + + + + 0 65536 + + 0 + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. It is a bit mapped CORBA long, where one or more of the bits may be set. If none of the bits are set then the availability status is considered to be undefined. + + + + + + NO_STATUS + + + + + List of managed objects depending on PlugInUnit + + + + + + + + + + The measurement is done over 100 ms, and returns the sum of load on processes up to, and including process priority 23. The sum is expressed in % + +Supported on MP, BP and SP boards. + +In case of SP boards the returned processor load is the load of the BP. + + + + + + + 0 100 + + 0 + + + + + The number of automatic (do not require intervention from a human operator) sequential restarts that are allowed for a PIU. When this number of automatic restarts has been exceeded, the automatic restarting halts and the PIU is faulty marked. + +The time limit between two restarts is 5 minutes. This means that if the time between two restarts +is less then 5 minutes the restarts are counted, otherwise the restart counter is reset. + +For example, 3 means 3 restarts with time limit < 5 minutes are accepted but when the 4:th occurs within 5 minutes the board is considered faulty and an alarm is generated. + + + RESTARTS_WITH_WARM + + + + + +Note! The restartCause can have the following values: +1 = restart error +2 = restart upgrade + +Note! The restartCause piuRestartUpgrade overrides the restartRank value and gives mainly restartRank=warm (or restartRank=refresh in some upgrade situations. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + This MO represents the SS7 Signalling Link Set as defined in Recommendation Q.704 Ver. 3, April 28 1992 (ITU) T1.111-1996 (ANSI), JT-Q.704 Ver. 3, April 28 1992 (TTC) or GF001-9001 1990 (China). + +It provides information about a set of signalling links between an OPC/Adjacent PC pair. A link set is constructed from between 1 to16 Signalling Links (for China, Itu, Ttc and the ANSI standard), all of which have the same two end points (signalling points) as the Signalling Link Set. A Signalling LInk Set may be part of many routes. + + + + + + + + + + Use label for free use. + + + "" + + + + + The operational state of the MTP3B SLS. + +The operability of the MTP3B SLS is described by the operationalState attribute which has two possible values: + +- Enabled: The MTP3B SLS is partly or fully operable and available for use. At least one of the belonging links (SL) is enabled. +- Disabled: The MTP3B SLS is totally inoperable and unable to provide service to the user. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The usageState reflects the usage state of the links in the link set. There are three possible values: + +- Active: At least one of the belonging SLs of the SLS is Active and no link is Busy. +- Busy: If one of the belonging links is Busy. +- Idle: All SLs of the SLS are Unavailable. + + + + + + + + IDLE + + + + + The periodicLinkTestFlag indicates if periodic sending of SLTM/SLTA messages are used or not. The SLTM message will be sent on every link which is "aligned" at an interval of (SLTM timer). The answer, SLTA is supposed to arrive within (SLTA timer). If this doesn’t happen, or if the received SLTA doesn’t match the sent SLTM a second SLTM will be sent. If this SLTM also fail then the link will be considered 'out-of-service' and a restart of that link will begin. + +ANSI: true is default. +ITU: true is default. +China: true is default. +TTC: false is default. + +Note that TTC does not use this feature. + + + + + + true + + + + + The mtp3bSrsId attribute points out the corresponding MTP3b Signalling Route Set MO (adjacentDPC). + + + + + + + + + List of reserving MOs. + + + + + + + + + + This action deactivates a link set, which means the containing signalling links are taken out of service. + +Note! This action requires a transaction. + + + + + + + + A linkset containing signalling links which are all out of service, is called a deactivated linkset. In order to start up the signalling links and get them into service, there is an Activate Link Set action, or rather, there are two similar actions for activation of a link set. + +If the action fails to activate a link the ActivationFailed exception is raised. + +Note! This action requires a transaction. + + + + + + + + This action activates the signalling link with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + + + + + This MO represents a MTP3b Signalling Route. A Signalling Route is used to convey MTP3b User messages from a origin SP to a destination SP (Signalling Point). This MO is multiple instansiated and is contained in the MO MTP3b Signalling Route Set. A Signalling Route is from a network point of view the sequence of link sets from a originating signalling point to a destination signalling point. + +Note! At least one signalling route in the signalling route set must have priority = 1. +If lower priorities are defined the next level must be priority=2. (e.g. routes with priority =1 and =3 in a route set will not work). + +Note! Signalling Routes belonging to the same route set with the same priority must have the same type of bearer (Broad Band or Narrow Band). + + + + + + + + + + User label for free use. + + + "" + + + + + The MTP3b Signalling Link Set (MTP3bSls) or M3uAssociation to which the MTP3bSr MO is connected. + + + + + + + + + + Operational state notification.There are two possible states for the operationalState attribute: +- enabled, possible to perform operations on the MTP3b SR. +- disabled, not possible to perform operations on the MTP3b SR. + + + + + + disabled + + + + + There are three possible states for the usageState attribute: + +-active, route is active. +-busy, route is congested. +-idle, route not in use. + +(idle=0, active=1, busy=2) + + + + + + + IDLE + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The priority of the alternative route. The traffic is directed to the highest priority route(s) available in the route set. If more than one route has the same priority within a route set then loadsharing is permitted between these routes. +The value 1 is considered as the highest priority. + + + + + 1 5 + + + + + + The type of the route. + + + + + TDM_ATM + + + + + + + + + NOT_BLOCKED + + + + + The number of seconds (accumulated) route unavailable. + + + + + + 0 + + + + + This action blocks the Signaling Route. + +Note! This action requires a transaction. + + + + + + This action deblocks the Signaling Route. + +Note! This action requires antransaction. + + + + + + + + The IP System MO constitutes the top structure level for IP related MOs in a Cello node. + +The IpSystem MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, IpSystem=1. + + + + An operator defined label. + + + "" + + + + + + + + + + + + + Ping - used to call a host or router to find out if it is present in the network. The following input parameter is used by the Ping action: +The domain name or IP address to the host that shall be called. + +The following parameter is returned: +Ping result: 'IP address/domain name' - is alive or no answer. + +Note! This action requires a transaction. + + + + + + + + + + + + + Trace route - used to get information about the route through the IP network that is used for a destination with a specific IP address. + +The following input parameter is used by the trace route action: +The domain name or IP address to a host that shall be trace-routed. + +The following parameter is returned: +Trace result - list of IP addresses/domain names or path not found. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This MO represents an Internet Protocol over ATM link. LLC/SNAP encapsulated packets over Atm Adaptation Layer 5, AAL5, ATM PVCs are used. + +Note: The performance monitoring counters in the IpAtmLink MO has a "Wrap-around time" of approximately 2 hours. + +Note! When setting the 'fromUserMaxSduSize' and 'toUserMaxSduSize' on the Aal5TpVccTp MO the defined SduSize should be 8 bytes larger then the 'mtuSize' on the IpAtmLink. + +Note! Only Aal5TpVccTp's that terminates on an MP (Main Processor) may be used when setting up IpAtmLink's. + + + + + + + + + + The User Label attribute gives the operator the possibility to label the links. + + + + "" + + + + + The operational state of the IP over ATM link is dependent of the operational states of the underlying AAL5 termination points that are used to transport IP datagrams. If at least one operational AAL5 termination point (MO: AAL5 TP VCC TP) exists, the operational state of the IP over ATM Link is set to "ENABLED" + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. It is a bit mapped CORBA long, where one or more of the bits may be set. If none of the bits are set then the availability status is considered to be undefined. + + + + + + NO_STATUS + + + + + If set, indicates that this IpAtmLink is reserved by the OspfInterface represented by this attribute. + + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + + + + + The attribute subnetMask states the subnet mask of the IP over ATM link (point to point link). + +The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. +For a point to point link, the subnetmask 255.255.255.252 is very likely. + +Note! The subnet mask has to be contiguos. That is, it has the LSB's set to 0 (zero). + +Example: + +255.255.255.X + +Contiguous subnet mask: +11111111.11111111.11111111.11111110 (X = 254) +11111111.11111111.11111111.11111100 (X = 252) + +Not-contiguous subnet mask: +11111111.11111111.11111111.11111010 (X = 250) + + + + + + + + + + The attribute mtuSize states the maximum IP datagram size that may be sent on the IP over ATM link in bytes, without fragmentation. Recommended MTU size is 1500 bytes to prevent IP fragmentation. + +Note that the size of the IP datagram does not include the 8 Bytes added for the LLC/SNAP header before putting the IP datagram in AAL5 SDU. + + + + + 576 2040 + + 1500 + + + + + The attribute metric states the metric "cost" of the IP over ATM link. The metric value is calculated as 10^8 /link bit speed. + +For example: +Metric for 10 Mbps Ethernet = 10^8/10^7 = 10 +Metric for 100 Mbps Ethernet = 10^8/10^8 = 1 + + + + 1 32767 + + 1 + + + + + This attribute indicates whether InvATMARP monitor is turned on or off. + + + true + + + + + The interval between sending monitor packets. +Unit is seconds. + + + + 1 60 + + 10 + + + + + The number of retries when sending monitor packets. + + + + 1 255 + + 10 + + + + + The interface name. + + + + + + + "" + + + + + The selection mode for the Aal5TpVccTp's used by the IpAtmLink MO. Determines how the IpAtmLink MO selects the Aal5 termination points used. + +In case 'NO_PREFERENCE', 'LOCAL_MP_SELECT_VCC_AT_LINK_UP', LOCAL_MP_PEER_SELECTION_VCC' or 'LOCAL_MP_ACTIVE_RESELECTION' is selected the IpAtmLink MO will prefer Aal5TpVccTp on local MP (i.e. Aal5TpVccTp MOs executing on the same MP as the IpAtmLink), but other Aal5TpVccTp will be accepted if needed. + +In case 'ONLY_LOCAL_MP' is selected, the ipAtmLink (Inet Link) will consider Aal5TpVccTp residing on other MPs as a malfunction and discard the usage of them. No InvArp sending will be performed on them and all incomming trafic on them will be discarded. If no local Aal5TpVccTp exists the operational state of the link will be changed to disabled. + + + + + NO_PREFERENCE + + + + + References to MOs of type Aal5TpVccTp representing the underlying AAL5 termination points (of a AAL5 PVC:s) for the IP over Atm link. + +The operator gives a list of relative distinguished names of the Aal5TpVccTp MO's to be used by the IP over ATM link. +An Aal5TpVccTp MO may only be specified once in the list. + +To change in the set of Aal5TpVccTp MO's related to the IP over ATM link the link has to be deleted and then created with the desired set of AAL5 TP. + +Note! Only Aal5TpVccTp's that terminates on an MP (Main Processor) may be used when setting up IpAtmLink's. + + + + + + + 4 + + + + + Performance monitoring counter for the number of input unicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of out unicast packets deliverred to higher layer + + + + + + 0 + + + + + Performance monitoring counter for the number of output broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to any error. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of outbound packets discarded due to resource limitations. + + + + + + 0 + + + + + This action sets the IP address and the subnet mask. + +The changing of the IP address with the operation assignIpAddress, it might cause an interruption of the communication between the node and the network management tool. If an incorrect or erroneous IP address is configured, the communication with the node might be lost until the node is restarted or the IP address is changed to the correct value. + +Note! This action requires a transaction. + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + + + + The Ethernet Link MO represents the Internet Protocol over Ethernet link. There is only one Ethernet link MO per Cello node. + +The changing of the IP address with operation assignIpAddress might cause interruption of the communication if the network management tool is connected via the ethernet link. + +Note: The EthernetLink MO can not be deleted! + +Note: The performance monitoring counters in the EthernetLink MO has a "Wrap-around time" of approximately 2 hours. + + + The User Label attribute gives the operator the possibility to label the links. + + + + + "" + + + + + The attribute ipAddress states the IP address of the Ethernet link, it is also the IP address for the O&M host.. + +The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. +It must not be a broadcast or multicast address. + + + + + + + + + + + The attribute subnetMask states the subnet mask of the Ethernet link. + +The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + +Note! The subnet mask has to contiguos. That is, it has the LSB set to 0 (zero). + +Example: + +255.255.255.X + +Contiguous subnet mask: +11111111.11111111.11111111.11111110 (X = 254) +11111111.11111111.11111111.11111100 (X = 252) + +Not-contiguous subnet mask: +11111111.11111111.11111111.11111010 (X = 250) + + + + + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + The IP layer expects the Ethernet link to have an MTU size (maximum Ethernet frame size without fragmentization) of 1500 bytes. + +The value is always the default value. + + + + + + 1500 + + + + + The attribute metric states the metric of the Ethernet link. The metric value is calculated as 10^8/link bit speed. + +For example: +Metric for 10 Mbps Ethernet = 10^8/10^7 = 10 +Metric for 100 Mbps Ethernet = 10^8/10^8 = 1 + + + + 1 32767 + + 1 + + + + + The operational state of the Ethernet link is dependent of the operational states of the underlying MAU:s that represents the Ethernet transceiver function. If at least one operational MAU exists, the operational state of the Ethernet Link is set to "ENABLED" + + + + + + disabled + + + + + The interface name. + + + + + "" + + + + + The mac address is persistently stored in flash prom on the MP where the IP stack resides. It is stored there at manufacturing. + + + + + + + 6 + + + + + + If set, indicates that this EthernetLink is reserved by the OspfInterface MAO represented by this attribute. + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + Performance monitoring counter for the number of input unicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of out unicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to any error. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of output broadcast/multicast packets deliverred to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of outbound packets discarded due to resource limitations. + + + + + + 0 + + + + + This action sets the IP address and the subnet mask. + +The changing of the IP address with the operation assignIpAddress, +causes an interruption of the communication between the node and +the network management tool. If an incorrect or erroneous IP address +is configured, the communication with the node might be lost until +the node is restarted or the IP address is changed to the correct +value. + +Note! This action requires a transaction. + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + The input format used by the operator is four fields of digits, separated by a dot. Each field consists of three digits. + + + + + + + + + + This MO holds the IP routing table. + +The IpRoutingTable MO is automatically created when the Ip MO is created. +The IpRoutingTable MO can not be created manually. +The IpRoutingTable MO can not be deleted. + + + + Label free for use. + + + "" + + + + + This attribute gives the indexes for the static routes that are possible to delete by the operator. + + + + + + 0 + + + + + + + + + + + + + + Used to add a new static route to the routing table. It can be +indicated if the static route should be redistributed by OSPF. +When adding a static route with an ipaddress, which is not a subnet +address, the ipaddress is recalculated to the corresponding subnet +address, based on the ipaddress and the subnet mask. So when looking +for this route using the action 'getRoutingTableEntry' it is in fact +the recalculated ipaddress, that is displayed and not the ip address +entered with addStaticRoute. This is an automatic correction. + +Note! If an attempt is made to add a static route with hopIpAddress starting with 0.0 an exception will be thrown. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + List routes actions is used to list all routes in the routing table. It requires no input parameters. + +The output is a formatted string, indicating the number of routes in the table followed by route information for each of these routes. + +The number of routes in the table is found at the very start of the returned string. Immediately following this is the information on each route in the list in turn. The route information for each route begins with a new line character ("\n") and is followed by the following data items (in the order written below), which are separated from each other by a SPACE character: + +- Destination IP address +- Destination Network mask +- Next hop IP address/Interface index of connected networks in dot-decimal format +- Route metric +- Route type +- Interface name +- Redistribute +- Active + +Note that the next hop ipaddress is not an ipaddress per se, it is the subnet on wich the host/router to route to resides. + +Below is an example list of routes that could be returned from this action: + +"\n123.123.123.123 234.234.234.234 0.0.0.7 10 13 LE0 FALSE active\n122.122.122.122 233.233.233.233 0.0.0.6 2 8 LE0 TRUE active\n132.132.132.132 243.243.243.243. 0.0.0.7 9 13 LE0 TRUE inactive" + +In this case, there are three routes in the routing table. The first route has destination IP address of 123.123.123.123, the second route has it set to 122.122.122.122, while finally the third has it set to 132.132.132.132. + +NOTE that the route types can be of the following types: + +INET_RTPROTO_OTHER 1 +INET_RTPROTO_LOCAL 2 +INET_RTPROTO_NETMGMT 3 +INET_RTPROTO_ICMP 4 +INET_RTPROTO_OSPF 13 + +The types listed above also denote the origin of the routing entry. + +Note! This action does not require a transaction. + + + + + + + Returns a RoutingTableEntry according to the specified index. + +Should be used with action 'numberOfRoutes' within a transaction. To refresh the routing table stored in the MO, invoke the action 'numberOfRoutes'. + +Precondition: 0 <= index <= numberOfRoutes() - 1 + +Note! This action does not require a transaction. + + + + + + + + + + + + + Returns the number of entries in the routing table. + +Each time this action is invoked, the MO retrieves routing table information from the resource layer and then builds a new array of RoutingTable structs to store this information. + +This action along with getRoutingTableEntry(), which allows one to iterate through the array stored in the MO, should be used together with a transaction. + + + + + + Removes the RoutingTableEntry submitted as a parameter from the Routing Table, if it is found in the table. + +Note that only static roues, previously added, can be deleted with this action. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + The Ip MO represents the IP protocol layer with IP forwarding functionality. + +Note: The performance monitoring counters in the Ip MO has a "Wrap-around time" of approximately 2 hours. + + + + + + + + + + + + User label for free use. + + + "" + + + + + The workingMode of the IP MO controls if the IP stack in the node will work as a combined host/router (routerMode) or only as a host (hostMode). + + + + + + + + The retransmission interval. The units are seconds. +Must be a value > 0. + + + 4 + + + + + The number of retransmissions. +Must be a value > 0. + + + 5 + + + + + The Domain Name Server IP address. + +The IP address must be a Unicast IP address. + + + + "127.0.0.1" + + + + + Holds information about how the DNS client wants the DNS server do the search for the IP address in the network . It can be either Recursive search or Non-recursive search. + + + true + + + + + Holds information about whether to use subsets of the fully qualified domain name to reach the simple domain name. It can be either Use subsets of domain name or Not use subsets of domain name. + + + true + + + + + Holds information about whether the default domain name is present. It can be Present or Not present. + + + + + false + + + + + Contains default domain name. +If 'isDefDomainName' is set to 'true' the domain name found in this attribute is used by the DNS resolver and there is no need to submit the complete domain name. If the domain name is for example 'ws5741.uab.ericsson.se' then the default domain name would be '.uab.ericsson.se'. If 'isDefDomainName' is set to true the there is no need for using '.uab.ericsson.se'. If set to false then the complete domain name has to be used. +A valid domain name consists of 1 or more labels separated by dots ("."). +Valid characters for a label shall be limited to letters 'a' - 'z', 'A' - 'Z', digits '0' - '9', the character '-' ("dash"). +Character case shall be preserved. Labels shall start with a letter. Total length of a label shall not exceed 255 characters. + +Note! The first and last character in the domain name has to be within the following alphabet: letters 'a' - 'z', 'A' - 'Z' and digits '0' - '9'. For more information refer to RFC 952 and 1101. + + + "" + + + + + The operational state of the IP MO is ENABLED if at least one link is operational. + +Shows whether the MO is OK (enabled) or failed (disabled). The values are set by the system. + + + + + + disabled + + + + + Represents the number of interfaces (Ethernet and IP over +ATM links) which has registered to the IP MO. + + + + + + + 0 + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + If set, indicates that this Ip is reserved by the Ospf represented by this attribute. + + + + + + + + Indicates if the hosts file should be used or not. The hostFile is used by the resolver and +chosen as a source of information before querying a DNS server. + +true - use the host file. +false - do not use the host file. + + + true + + + + + The DiffServ CodePoint. +The code point values are used by DiffServ enabled hosts and router to identify different service levels. +When set, the DSCPs are mapped to PHBs (Per Hop Behaviours) by forwarding devices along the path +between the source and destination. PHBs dictates how each packet will be handled i.e. what type of +service that is applied to the packet when it is forwarded. + +Note! Only traffic originated from the node is tagged with the dscp value. The Cello router does not implement functionality for handling different service levels when routing IP traffic. + + + + 0 63 + + 0 + + + + + Indicates if ICMP redirects is sent out or not. + + + true + + + + + Enable/Disable generation of UDP checksum. +0 = disabled +1 = enabled + +The UDP checksum is used for verifying that the UDP header has not been damaged during transmit. + + + 1 + + + + + The time that elapses before a connection (TCP) attempt times out. + +Unit is seconds. + + + 75 + + + + + The maximum number of retransmission attempts before a TCP connection is dropped. +The default value is 10 attempts, which is around 5 minutes. +Setting this attribute value to -1 means infinity, and TCP will never give up in trying +to establish a connection. + + + + -1 + + 10 + + + + + Performance monitoring counter for total number of datagrams received. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams discarded due to format error. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams discarded due to misdelivery. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams forwarded. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams dascarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams discarded due to lack of resources. + + + + + + 0 + + + + + Performance monitoring counter for the number of fragments received needing reassembly. + + + + + + 0 + + + + + Performance monitoring counter for the number of datagrams successfully reassembled. + + + + + + 0 + + + + + + + This MO represents an SCCP EntitySet which is made of one SCCP Entity. An SCCP Entity is a local MTP-SAP + a DPC + possibly an SSN, i.e an SCCP EntitySet identifies the set of access points that result from a global title translation. An SCCP EntitySet may also be made of two SCCP Entities of the same type (if an SSN is present in one SCCP Entity, then an SSN shall also be present in the other). In the latter case the two SCCP entities may be considered either as a "primary" SCCP Entity and a "backup" SCCP Entity (dupli-dominant mode) or may be interpreted as two equal SCCP entities that can be used for outgoing loadsharing purpose. In this implementation they can only be considered as "primary" and "backup".The Routing Indicator (RI) in the Called Party Address is normally not set by the SCCP for outgoing messages and should therefore be set by the user. This means that if the user has set "Route on SSN" this will be the case after the GTT also even if the set consist of MTP-3b Access Points. However, if the set consists of SCCP Access Points the RI is implicitly set to "Route on SSN" by SCCP. + +DPC Destination Point Code +GTT Global Title Translation +MTP Message Transfer Part +SAP Signalling Access Point +SSN Subsystem Number + +Note: the SccpEntitySet MO depends either on MAOs of type SccpApLocal OR SccpApRemote, not on a mixture of these MAO types. + + For free use. + + + "" + + + + + The Entity Set routeId is an array of maximum two instances of Sccp ApLocal MO's OR two instances of SccpApRemote MO's OR two instances of Mtp3bAp MO's OR one instance of SccpSP MO. + + + + + + + 2 + + + + + The sharingMode attribute controls the distribution of SCCP traffic over the entities (Access Points) in the set. + + + + + + + + + + The new sub system number attribute is only valid if the Mtp3b Access Points are used in the set. In that case the SSN attribute allows to optionally set the subsystem number in the Called Party Address as a result of a Global Title Translation. If the set consists of SCCP Access Points the subsystem number in the Called Party Address is always implicitly set to the SCCP Access Point SAP (SSN) as a result of a Global Title Translation. +This attribute is controlled by the type of AP(s) that the EntitySet refers to. + +The default value 0 means no new subsystem number. + + + + + + 0 254 + + 0 + + + + + The New Global Title attribute allows to optionally replace the global title in the Called Party Address as a result of a Global Title Translation (GTT). If the GT resulting from a GTT is different from the GT previously included in the Called Party Address, the newly produced GT replaces the existing one. The gtIndicator attribute is read-only and is derived from the combination of Nature Of Address, the Translation Type and Numbering Plan used. + +Default value is considered as no new Global Title. + + + + + + + + Holds a list of the reserving MO's. + + + + + + + + + + + + + + + + + + + + The SCCP Global Title MO represents a combination of a global title translator and a global title rule. If no Destination Point Code (DPC) is present in the Called Party Address, a Global Title (GT) is needed. Then a global title must be present in the Called Party Address, otherwise a routing error occurs. A global title translator is selected by SCCP based on a combination of the values of the Nature Of Address (NA), the translation type (TT), and the Numbering Plan (NP) if available, in this MO matched with the same information in the Called Party Address provided by an SCCP user. A global title translation rule is selected by SCCP by matching the Global Title Address Information and possibly the Encoding Scheme in this MO, with the same information in the Called Party Address provided by an SCCP user. A global title translation rule points to the SCCP Entity Set resulting from the global title translation (GTT). +The translation results in a DPC and possibly a new Sub System Number (SSN) or GT or both (decided by the SCCP Entity Set it refers to). If the GT and/or SSN resulting from a GTT is different from the GT and/or SSN previously included in the Called Party Address, the newly produced GT and/or SSN replaces the existing one. + +GT - Global Title +SCCP - Signalling Connection Control Part +SSN - Sub System Number +DPC - Destination Point Code +TT - Translation Type +GTT - Global Title Translation + + For free use. + + + "" + + + + + Global title indicator for China, ITU, TTC and ANSI. + + + + + + + + + + + + + Indicates number type, i.e. national or international number. + + + + + + + + + + + Indicates which numbering plan that is used. + + + + + + UNKNOWN + + + + + Used to direct the message to the appropriate Global Title translation function. + + + + + + + 0 254 + + + + + + Digit string of 1-37 digits, where each digit is 0-9, and "B", "C". "B" and "C" are for Code 11 and Code 12. +The addressInformation may also contain wild card symbols: "*" or "?". Wild cards are only allowed for defining Global Title Translations, they are not allowed for specifying SCCP SAPs (built with SPC and Global Title or SPC + SSN + Global Title). + + + + + + + 1 37 + + + + + + Indicates if the number of address signals are an odd or even number. + + + + + + + UNKNOWN + + + + + The sccpEntitySetId attribute points out the corresponding SccpEntitySet MO. + +Note! This attribute is only optional if this MO is used by Policing. In all other cases it has to be set. + + + + + + + + + + + + + + + List of reserving MOs. + + + + + + + + + + + + This MO is used to represent an AAL2 Path, i.e. an ATM VC connection that carries multiplexed AAL2 links. + +VCC TP - Virtual Channel Connection Termination Point. + +The total number of Aal2PathVccTps associated to an Aal2Ap, by connecting them to Aal2PathDistributionUnits under that Aal2Ap, must not exceed 632. + +The total number of Aal2PathVccTps associated to a ReliableProgramUniter, by connecting them to Aal2PathDistributionUnits associated to the ReliableProgramUniter, must not exceed 280. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + + + + + + + + + + For free use. + + + "" + + + + + Reference to the VclTp to be used by this Aal2PathVccTp. + + + + + + + + + The administrative state of the termination point. + + + unlocked + + + + + Operational state of the termination point. + + + + + + disabled + + + + + The identity of the reserving Aal2PathDistribution MO. + + + + + + + + + The availability status of Aal2PathVccTp. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. + +Activates VC end to end continuityCheck according to ITU.T rec I.610. + + + false + + + + + PM mode is set to indicate type of performance monitoring mode (ie. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + NOM_PM_BLKSIZE_2_10 + + + + + Timer that assures that CPS-packets with one or more octets already packed in the ATM cell wait at most the duration of timerCu before being scheduled for transmission. + +Units for timerCu is 10 to the power of -4 seconds. This value can be set in steps of 10 to the power of -4. + + + + + + 1 100 + + 10 + + + + + This attribute is used to identify the path in the Q.2630.1 protocol. + +The pathId value must be unique within all Aal2PathDistributionUnits under the same Aal2Ap + +All integers > 0 are allowed (not 0). + +The Aal2PathId is used by the Aal2 connection control function in two Aal2 nodes to uniquely identify an AAL2 path between the two nodes. This means that the value of the attribute Aal2PathId for an Aal2 path must be the same in each of the two nodes. + +In order to set this attribute, the Aal2PathVccTp may not be reserved. If an attempt is made, an "IsReservedCanNotSetPathId" exception is thrown. + +Note! Setting of this attribute will not have any effect until 'actionAddPath' in Aal2PathDistributionUnit MO' is called adding this MO to the list of Aal2PathVccTp MO's. + + + + + 1 2147483647 + + + + + + This attribute indicates whether this Aal2 Path VCC Termination Point is considered the owner of the Aal2 Path in order to decide channel selection procedure in the Q.2630.1 protocol. + +Note! In order to set this attribute, the Aal2PathVccTp may not be reserved. If an attempt is made, an "IsReservedCanNotSetPathId" exception is thrown. + +Note! The administrativeState has to be LOCKED when this attribute is set, if not the "IsUnlockedCanNotSetPathOwner" exception is thrown. + +Note! Setting of this attribute will not have any effect until 'actionAddPath' in Aal2PathDistributionUnit MO' is called adding this MO to the list of Aal2PathVccTp MO's. + + + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + The identity of the QosProfile used by the Aal2PathVccTp. + + + + + + + This attribute specifies which QoSClass that can be supported by this Aal2Path. + + + + CLASS_A_B_C_D + + + + + Performance monitoring counter for forwarded lost cells. + + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + + + This MO represents a AAL2 routing case which points out an AAL2 access point. + + + + + + + + + + For free use + + + "" + + + + + An array of alternative routes identified by the concerned Aal2Ap MOs. A routeList can have 0 to 5 Aal2Aps. +The Aal2Ap must be unique. +Note! if this attribute is set, the routePriorityList also must be se with the same number of values ( if the routeList +contains 3 routes, the routePriorityList must contain 3 prioritys). + + + + + + + + + + + A list of all the Aal2Ap priorities. +The priority values can be in the range 1 to 5, one beeing the highest priority. +The Aal2Aps can have the same priorities. + + + + + + + + 0 5 + + + + + + + Defines the possible set of AAL type 2 Service Endpoint Addresses (A2EA) that match the routing case. + +The number direction of a routing case shall be interpreted as all AAL type 2 Service Endpoint Addresses +starting with the string of numbers defined in the number direction. For example, the AAL2 End System +Addresses "12340" and "123400" will both match the number direction "1234". + +The AAL2 routing function uses a longest match comparison to select between routing cases with overlapping +number directions. For example, given two routing cases A with the number direction "1234" and B with the number +direction "12345" the AAL2 End System Address "12345" will be routed using routing case B, whereas the AAL +type 2 Service Endpoint Addresses "12344" and "12346" will be routed using routing case A. + +NOTE: It is not allowed to use leading zeros when configuring this attribute. + +NOTE: It is not possible to replace an existing routing case by creating routing cases with number directions that +completely overlap the number direction of the existing routing case. + +NOTE: It is not possible to create two routing cases with the exact same number directions in a node. + +NOTE: It is possible to create one or more routing cases with number directions that partially overlap the number +direction of an existing routing case. + +Length range 1..15 +Alphabet: "0123456789" + + + + + + + + 1 15 + + + + + + Adds the identified (and existing) Aal2Ap MO to the routeList. This action should also be used when changing the priority for an existing Aal2Ap MO. When submitting an existing Aal2Ap MO with a new priority the routing list will be updated with the new priority for the specified Aal2Ap MO. + +Note! In order to be able to update the priority for a routing entry, the routing entry first has to be deleted and then submitted with the new priority. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + Removes the identified Aal2Ap MO from the routeList. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + The Aal2Sp (AAL2 Signalling Point) MO is used to represent the AAL type 2 Service Endpoint Address of the node in the AAL2 network. +There is one and only one instance of this MO in the ATM NE system. + + For free use + + + "" + + + + + An E.164 format number that specifies the AAL type 2 Service Endpoint Address of the node. + +Length Range: 1..15 +Alphabet: "0123456789" + +Note! It is not allowed to use leading zeros when configuring this attribute. + + + + + 1 15 + + + + + + + + + + + + + + Performance monitoring counter for the number of unsuccessful attempts to establish connections due to node internal problems. + + + + + + 0 + + + + + + + This MO represents a AAL2 Access Point signalling function associated with a single AAL2 signalling relationship to a remote peer AAL2 acess point signalling function. An AAL2 access point is either a high rate access point that uses MTP-3B for signalling or a low rate access point that uses UNI-SAAL for signalling. + +Aal2Ap - Aal2 Access Point + +Note! The performance monitoring counters in the AalAp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Free for use + + + "" + + + + + This attribute holds a list of the reserving MOs. + + + + + + + + + + Operational state of the AAL2 AP. + + + + + + disabled + + + + + The availability status of the Aal2Ap. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Q.2630.2 establishment request timer. Unit is milli seconds. + + + + + + 5000 30000 + + 5000 + + + + + Q.2630.2 release request timer. Unit is milli seconds. + + + + + + 2000 60000 + + 2000 + + + + + Reference to a UniSaalTp or Mtp3bAp MO that provides a signalling link for the Aal2Ap. + + + + + + + + + Reference to a secondary signalling link MO of type UniSaalTp. This attribute can only be set when sigLinkId is of type UniSaalTp. + + + + + + + + The physical location of an AP (Access Point) LR/HR (Low Rate/ High Rate) program represented by a reference to a RPU (ReliableProgramUniter) MO. + + + + + + + + + The identity of the QoSCodePointProfile used by this MO. + + + + + + Performance monitoring counter pmExisOrigConns. +Number of existing connections for the AP originating in this node. + + + + + + + 0 + + + + + The total number of Aal2PathVccTp MOs configured on this Aal2 Ap. + + + + + 0 + + + + + The total number of unavailable Aal2PathVccTp's on this Aal2 Ap, i.e. the number of Aal2PathVccTp MOs connectected to this Aal2Ap with 'administrativeState' LOCKED. + + + + + 0 + + + + + Performance monitoring counter pmExisTermConns. +Number of existing connections for the AP terminating in this node. + + + + + + 0 + + + + + Performance monitoring counter pmExisTransConns. +Number of existing connections for the AP transiting in this node. + + + + + + 0 + + + + + Performance monitoring counter pmSuccOutConnsRemote. +Number of successful establishment of outgoing connections on this AP + + + + + + 0 + + + + + Performance monitoring counter pmSuccInConnsRemote. +Number of successful establishment of incoming connections on this AP. + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccInConnsRemote. + +Number of unsuccessful establishment of incoming connections on this AP caused by reject from beyond this node. + + + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccOutConnsRemote. + +Number of unsuccessful establishment of outgoing connections on this AP caused by reject from remote side, reset from remote side, no reply or signalling link failure. + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccInConnsLocal. +Number of unsuccessful attempts to allocate Common Part Sublayer, CPS, resources during establishment of incoming connections on this AP caused by Channel Identifier, CID, and/or bandwidth collision or mismatch of Call Admission Control, CAC, between peers. + + + + + + 0 + + + + + Performance monitoring counter pmUnSuccOutConnsLocal. + +Number of unsuccessful attempts to allocate CPS resources during establishment of outgoing connections on this AP. Caused by rejects in CAC (Connections Admission Control). + + + + + + 0 + + + + + Performance monitoring counter pmUnRecMessages. + +Number of received unrecognized Q.2630.1 messages on this AP. + + + + + + 0 + + + + + Performance monitoring counter pmUnRecParams. + +Number of received Q.2630.1 messages with unrecognized parameters on this AP. + + + + + + 0 + + + + + + + This MO represents the hardware of the ET-M1 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-M1 board contains 8 physical ports that can be configured as either E1 (ETSI), J1 (TTC) or T1(ANSI). The board does not allow for a mix of E1, J1 and T1 ports, thus all configured ports on the board must be configured to the same standard. + +Each of the ports on the ET-M1 board can be used to carry either ATM traffic or circuit orientated (Nx64 Kbits/s connections) traffic. + +Each port can support up to 30 ATM VC connections. Two of these connections are reserved for AAL2 paths, and therefore two AAL2 multiplexers per port are available. + +Each port can support up to 2 VP connections. + +The ET-M1 board supports 1 bidirectional F4/F5 PM flow per port. + +Other restrictions: +- All ports (configured for ATM) on the board must have the same value for the hecCorrection attribute (ATM Port MO). +- It is possible to configure UBR+ traffic, but there is no guarantee on the minimum cell rate. +- VP shaping is not supported (it is recommended to configure at most one VP per physical port). +- VC shaping is not supported with an exception for AAL2 path traffic. This is shaped to the peak bandwidth on the VC connection. +- When using the Etm1 board the performance monitoring counters in the transmit direction found on the AtmPort MO does not show the following cells: CC cells and OAM FPM cells. + +Note! IMA is not applicable for the ETM1 board. + +Note! When using fractional atm, timeslot 1 must be a part of the fraction. + +Note! ETM1 does not support EPD and PPD + +Note! ETM1 does not have a proper buffer management. Thus fairness of UBR+ traffic can not be guaranteed and shaping on UBR+ traffic is not possible. + +Note! The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 1 per port. + + + user label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the Etm1 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + This MO is used to administer synchronization reference (a synchronization input with support for 2MHz and 10MHz signals) on Timing Unit board. + + Label for free use. + + + "" + + + + + Operational state of TU synchronization reference + + + + + + disabled + + + + + Administrative state of TU synchronization reference + + + locked + + + + + The availability status of the TuSyncRef. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + When the TU synchronization reference is registered in the system as an usable synchronization reference, this MO reference is set by using "local" operation syncReserve(). When synchronization reference is de registered, "local" operation syncRelease is used. Note that the only valid user of these operations is Synchronization MO. + + + + + + + + + + + + + + + + + + The Special purpose Processor Module MO, Spm, represents one of the Special Purpose Processors and its connected hardware. This object is used for SW management and restart. Hardware failure indications are sent to Spu. + +Note! If the board is of type SPB1 the maximum number of Spm MO's that is possible to create under the Spu MO is 3. +If the board is of type SPB2 the maximum number of Spm MO's that is possible to create under the Spu MO is 5. + + + + + + + + + + user label for free use. + + + "" + + + + + The operational state of the SPM + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Switch Module Number + + + + + 0 + + + + + ASCI Port Number + + + + + 0 + + + + + The identity of the SPM on the Special purpose Processor Unit (SPU). + + + + + + + 0 + + 0 + + + + + The list of identities of running Spm's + + + + + + + + + + + The list of identities of installed Spm's in the system. + + + + + + + + + + The uniqe name of the link between the SP and BP. + + + + + "" + + + + + The identity of the reserving MO. + + + + + + + + Restarts the SP. + +Note! This action requires a transaction. + + + + + + + + + The Special purpose Processor Unit MO, Spu, represents the board specific HW on SPB. This objects collects HW failure indications on the board and issues/ceases alarms. + + user label for free use. + + + "" + + + + + The operational state of the SPB board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The special purpose processor link name. + + + + + "" + + + + + + + + + + + + + Restarts all SPs on the board (but not the BP). + +Note! This action requires a transaction. + + + + + + + + + This MO is used to represent the point-to-point ATM cross-connect relationship between two VCL termination points. + + For free use. + + + "" + + + + + Operational state for the cross connection. + + + + + + disabled + + + + + Identifies the VclTp managed object involved in the A side of the cross connection (which consists of an A and B side). + +Must not be the same as vclTpBId. + + + + + + + + + Identifies the VclTp managed object involved in the B side of the cross connection (which consists of an A and B side). + +Must not be the same as vclTpAId. + + + + + + + + + + + + + + + + + + + The Configuration Version, CV, is an MO managing all on disk saved node configuration. This MO keeps all administrative data about the CV's including path and file-names of the configuration files. There may be more than one CV on the disk but only one is used at the time. A CV is always based on one Upgrade Package. + +The local distinguished name of this MO is ManagedElement=1, SwManagement=1, ConfigurationVersion=1. + + + Configuration version MO's id. + + + + + + + + + For free use. + + + "" + + + + + List of stored configuration versions in the node. + +Stored in and read from the file system. + +List of stored configuration versions (CV) in the node. + +The list is a sequence of CVs. +Each CV is presented as structure. A CV structure has following fields: + 1. Name + 2. Identity + 3. Type + 4. UpgradePackageId + 5. Operator name + 6. Comment + 7. Date + 8. Status + +The CV list is formatted as a sequence of ConfigurationVersionAttributes. +Each struct contains one CV. + +The following characters are allowed within the struct members below. + +[0-9], [A-Z], [a-z] and '&' , '%' , ':' , '.' , '_' , '-' + +Note! For comment and operatorName spaces (' ') are also allowed within the strings. + +Struct element description : +-Name is in string format, max length is 40. +-Identity is in string format, max length is 40. +-Type is in string format, max length is 40. +-UpgradePackageId is in string format, max length is 40. +-Operator name is in string format, max length is 40. +-Comment is in string format, max length is 40. +-Date is in string format, max length is 40. Format for date is: weekday month date hour:min:seconds year. +-Status is in string format, max length is 40. + +Note! The identity can not be the same as name. Identity should contain the product identity. + + + + + + + + + + + + The name of the current loaded configuration version. + +Stored in and read from the file system. + +This is the configuration version that the system started with, i.e. the configuration version that was startable at the last node restart. + + + + "" + + + + + The name of the configuration version that will be used at next node restart. + +Stored in and read from the file system. + +This attribute is set by the action "setStartable( name of cv)". +Also set at rollback by the system. The first CV in the rollback list is then used. + + + + "" + + + + + A list of configuration versions to rollback to (configuration version name). + +The configuration version on the first line is used at the next rollback. That line is then automatically removed from the rollback list. + +This attribute is modified by actions setFirstRollbackList() and removeFromRollbackList() + + + + + "" + + + + + + A reference to current executing upgrade package. + + + + + + + Flag that indicates that a configuration version will be created automatically once a day. + + + true + + + + + Time for the automatic creation of configuration versions once a day. + +The string must be specified as "HH:MM" to be accepted at set. + +See also Class Attribute autoCreatedCVIsTurnedOn. +The time is UTC time. + +Note! If changing the clock on the node, this attribute must be set or +the JVM MP must be reastarted. + + + + + + "04:00" + + + + + Flag that indicates if rollback is enabled or not. +When true the system will automatically set the rollback counter. In case of cyclic restarts a rollback will be issued after x restarts. x is defined by the rollbackInitCounterValue. + + + true + + + + + Used by the system when rollback is switched on (autoRollbackOn=true). After the given time the node is considered not in a cyclic restart mode. The rollback counter will then be reset to its initial value (rollbackInitCounterValue). + +Timer value in minutes. + + + + 1 10000 + + 30 + + + + + Initial value for the rollback counter. Used when rollback is switched on (autoRollbackOn=true). + + + + + + 1 10000 + + 5 + + + + + An attribute to indicate status of command log. +It can be ON/OFF(true/false). + + + + + + true + + + + + The name of the executing Configuration Version, CV. + +Same as 'currentLoadedConfigurationVersion' after a node restart, changed to the value of lastCreatedCv when a CV is created. + + + + + "" + + + + + The name of the last created Configuration Version, CV. + + + + + "" + + + + + The CV given will be the one used at the normal node restarts. Only A CV with status = OK can be set as startable. + +This action does not require a transaction. + + + + + + + + + + + + A new CV directory will be created. A DB backup from the current RAM CV, +an ARMAMENT file and the file LLP:LMid is created at the directory. The current +command log file is copied to the CV directory first, then it removes the file from +the current directory. + +Note: The file cmdlog.properties under /c/ will not be saved to the CV. + +The following characters are allowed in the Strings: + +[0-9], [A-Z], [a-z] and '&' , '%' , ':' , '.' , '_' , '-' + +Note! For comment and operatorName spaces (' ') are also allowed within the strings + +-configurationVersionName is in string format, max length is 40 characters. +-identity is in string format, max length is 40 characters. +-operatorName is in string format, max length is 40 characters. +-comment is in string format, max length is 40 characters. + +This action does not require a transaction. + +Note! The configurationVersionName and identity can not be the same. The identity should be the product identity. + + + + + + One ASCII text string. It must be possible to create a directory with string. Do not use string "autocreated1" and "autocreated2" as cv name. They are used by the system. + + + + + + + + + + + + + Type of the configuration version [ standard | test | other ]. + + + + other + + + + + The operator's name. + + + + + + + The operator's comment. + + + + + + + + + Delete a configuration version (CV) permanently. + +If CV is referenced in the startable or in the rollback list, the action is not performed (an exception is thrown instead). + +Note! The latest created CV is not deletable until a node restart is performed or a new CV is created. Also note that a CV is not possible to delete when it has one of the folowing properties: +- "loaded" +- "startable" +- The CV is found in the "rollbacklist" + +This action does not require a transaction. + + + + + + + + + + + + Removes a Configuration Version (CV) from the rollback list. + +This action does not require a transaction. + + + + + + + + + + + + Adds a Configuration Version (CV) first in the rollback list. This will cause the node to chose this CV at the next rollback. A CV with status NOK, can't be put in the rollback list. + +This action does not require a transaction. + + + + + + + + + + + + This action activates the log. + +The inparameter is the drive name (where the command log file should be stored). + +Default command log is drive /c/. + +Note! Invoking this action affects the attribute'commandLogStatus'. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + This action deactivates the logging of configuration commands. + +Please note that uncommited data will be lost. + +Note! Invoking this action affects the attribute'commandLogStatus'. + +Note! This action does not require a transaction. + + + + + + + + + This MO is used as a structural element for the SW managed object. The MO structures the software resources of the node. + +Note that the SwManagement MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, SwManagement=1. + + + For free use. + + + "" + + + + + + + + + + + + + This action will normalize all RPUs in the node. + +Note! This action requires a transaction. + + + + + + + + The UpgradePackage, UP, represents an upgrade package as stored in the node file system and as stored on the ftp server that it is/shall be fetched from. + +There may be more than one UP at the same time on the disk. One UP represents the running system issue in the node. That one is pointed out by the Configuration Version MO. + +The actions on an UpgradePackage MO, are actions that can be called to take that particular UpgradePackage into operation on the node. + +The deletion of the Upgrade Package on disk is performed when the associated Upgrade Package MO is deleted. The Upgrade Package's unique LoadModule MOs and files are deleted. ConfigurationVersions in otherReferringCVs are deleted. + + +The UP MO refers to all load modules used in the UP. One load module may by used in more than one UP. + +Note at the start-up of the system/database/loading of a Configuration Version, special Upgrade Package MOs are created to represent Upgrade Packages that are stored on the disk but do not have an MO in the current Configuration Version. These special Upgrade Package MOs have are in the "onlyDeletable" state. In this state, the MO will throw ActionNotAllowedException on all its actions! + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + + The identity of the MO. + + + + + + + + + Label free of use. + + + "" + + + + + List of references to load modules that belong to this upgrade package. + +The list will be null until a successful install has been performed. + + + + + + + + + + + Path to the .xml file on the node once it has been fetched from the FTP server. + + + + + "" + + + + + Contains the state of this upgrade package. + +The management system and/or operator need to act on some changes in the state attribute. + +This attribute is used to accept/reject and modify behavior of actions. For example action 'upgrade' is not allowed in state notInstalled. Furthermore, action 'upgrade' does not behave the same if state == 'Installed' compared to if state == 'executingUpgrade' or 'awaitingConfirm'. + +To continue and conclude the upgrade sequence when in state == 'awaitingConfirm', action 'confirmUpgrade()' must be called. In this state it is also advisable to check attribute 'confirmationDeadline' to see how much time it is left before automatic rollback is done. + +Upgrade Package MOs that are stored on disk but do not have an MO in the current Configuration Version are in state "onlyDeletable". An MO in this state will throw the exception ActionNotAllowedException on all its actions. + + + + + + NOT_INSTALLED + + + + + Header enum describing the current progress indication. +Note that this is only progress information, that should be shown to a human operator, because some operations may take time. + +Changes in the progress header NEVER entails that the operator or management system need to perform any particular actions. + + + + IDLE + + + + + +This notification attribute is used to indicate progress for different steps in the upgrade sequence. The value gives the total number of steps that is to be performed in current step. + +This attribute is changed whenever 'progressHeader' is changed and indicates a maximum count for the progress of the progress counter. What items that are counted is specific for each case. For some cases, the counter is not yet implemented. In these cases, the progressTotal is set to zero (0) when the progressHeader is set. + + + + + + 0 + + + + + This attribute is used to indicate progress for different steps in the upgrade sequence. The value is separated in increments from 0 to progressTotal. + +The value of progressCount never exceeds the value of 'progressTotal'. + +For some cases, the counter is not yet implemented. In these cases, the progressCount is set to zero (0) when the progressHeader is set. + + + + 0 + + + + + Contains product data for this upgrade package. This information is extracted from the upgrade control file. + + + + + + + + This attribute contains the deadline date and time for an operator confirmation. If the deadline is not met, then an automatic rollback to a previous configuration is issued by the system. + + + + + + "" + + + + + Ip address to the ftp server where the upgrade package is stored. + +The input format used by the operator is four fields of digits, separated by a dot. + + + + + + + + + + File path on the FTP server to the upgrade control file. + + + + + + + + + User id. to be used for logging in to the FTP server. + + + + + anonymous + + + + + Password to the FTP server. This attribute is only supplied at create and is not readable. + + + + + anonymous + + + + + The document number and revision of the uppgrade package where the white spaces has been removed and underscore between the document number and revision has been inserted e.g. 19089-CSX10901/1_A. + + + + + "" + + + + + The list containing the names of the Configuration Versions that stop the Upgrade Package MO from being deleted. + + + + + + + + + + The list of names of Configuration Versions that refer to the Upgarde Package MO, but do not affect the deletable status of the Upgrade Package MO. + + + + + + + + + + Indicates if the Upgrade Package MO can be deleted. + + + + + false + + + + + This attribute is only valid for Upgrade Packages of type Delta.It contains the merge history of this upgrade package. + +Example: [Product Data for normal UP (non Delta UP), Product Data for Delta UP1, Product Data for Delta UP2]. + + + + + + + + + + This attribute states a compatibility index. + +If specified, it may be used when verifying that an upgrade 'from' state is valid for this Upgrade Package. + +Note: It is only used when the Upgrade Control File element upgrade window contains this type of information. + + + + + "" + + + + + This attribute states the CPP upgrade package version of this Upgrade Package + + + + + + + + The attribute contains the result from the latest four invoked actions. + +This attribute is only valid for actions:: +- install (all variants) +- cancelInstall +- verifyUpgrade +- upgrade (all variants, Note that the attribute is only valid when the verification phase discovers that upgrade is not possible'). + + + + + + + + + Load modules defined in the Upgrade Package Control file will only be downloaded to the node if the Load Module MO representing the load module file doesn't already exist. +The result of this action is indicated in the attribute ActionResult. In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'.Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action will be removed in a later version. +Note! This action does not require a transaction. + + + + + + + + + + + + Verifies that an upgrade is possible. + +The operation is not blocked while the verification is executing i.e. after basic controls the operation initiates the verification and returns 'void'. + +The progress of this action is indicated in the attribute ProgressHeader.The result of this action is indicated in the attribute ActionResult. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note: This action does not require a transaction. + + + + + + + + + + + + Upgrades the node. The operation is not blocked while upgrade is executing i.e. after basic controls the operation initiates the upgrade and returns 'void'. + +Before the real upgrade is started a verification phase is executed. + +The progress of this action is indicated in the attribute ProgressHeader. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +The result of this action is only indicated in attribute ActionResult in case the verification phase discovers that upgrade is not possible. + +Note: This action does not require a transaction. + + + + + + + + + + The same as upgrade except that the hard upgrade sequence is always chosen. + +It could be helpful to use this method if the application has start- or upgrade- synchronization problems when using a soft upgrade sequence. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +The result of this action is only indicated in attribute ActionResult in case the verification phase discovers that upgrade is not possible. + +Note: This action does not require a transaction. + + + + + + + + The operator invokes this method when the trial period is over. +The operation is not blocked while upgrade is executing i.e. after basic controls the operation initiates the upgrade and returns 'void'.In case the upgrade fails after 'void' has been returned the attribute ProgressHeader will be set to 'UpgradeExecutionFailed'. + +Note! This action does not require a transaction. + + + + + + + + Cancels an executing upgrade or an upgrade that is awaiting confirm. + +Note: This action performs a node restart so that the CV pointed out in the ConfigurationVersion MO is rolled back. + +Note! This action does not require a transaction. + + + + + + + All load modules defined in the Upgrade Package Control file will be downloaded to the node even if the Load Module MO representing the load module already exists i.e. existing load module files are replaced. +The result of this action is indicated in the attribute ActionResult.In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'.Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action will be removed in a later version. +Note! This action does not require a transaction. + + + + + + + + + + + + Load modules defined in the Upgrade Package Control file will only be downloaded to the node if the Load Module MO representing the load module doesn't already exist. + +This action is non-blocking i.e. the action initiates the installation and returns 'void' immediately without waiting for the installation to be completed. + +In case the installation fails after 'void' has been returned, this will be indicated by change of the value of attribute 'ProgressHeader' to 'ExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + + + All load modules defined in the Upgrade Package Control file will be downloaded to the node even if the Load Module MO representing the load module already exists i.e. existing load module files are replaced. +This action is non-blocking i.e. the action initiates the installation and returns 'void' immediately without waiting for the installation to be completed. +The result of this action is indicated in the attribute ActionResult.In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + + This action only installs the load modules that are required in this node i.e. the load modules required after successful execution of action upgrade on this upgrade package. + +A load module is considered to be required if one of the following criteria is fulfilled: +a) The load module is included in a Repertoire MO where the Repertoire MO is connected to a SwAllocation MO and the SwAllocation MO is connected to a Slot MO, a Fan MO, a Jvm MO, a Webserver MO or an applicable type of application MO. +b) The load module is of type 'other'. + +All required load modules will be downloaded to the node even if the Load Module MO representing the load module already exists i.e. existing load module files are replaced. + +This operation is non-blocking i.e. the action initiates the installation and returns "void" immediately without waiting for the installation to be completed. +The result of this action is indicated in the attribute ActionResult.In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure. + +Note. The behaviour described for this action is also obtained for the other installation actions if the Upgrade Control File indicates that the upgrade package is of type selective (which is recommended). + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + + This action only installs the load modules defined in the Upgrade Package Control file that are required in this node i.e. the load modules required after successful execution of action upgrade on this upgrade package. + +A load module is considered to be required if one of the following criteria is fulfilled: +a) The load module is included in a Repertoire MO where the Repertoire MO is connected to a SwAllocation MO and the SwAllocation MO is connected to a Slot MO, a Fan MO, a Jvm MO, a Webserver MO or an applicable type of application MO. +b) The load module is of type 'other'. + +Returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute +actionResult. + +The required load modules will only be downloaded to the node if the Load Module MO representing the load module doesn't already exist. + +This action is non-blocking i.e. the action initiates the installation and returns 'void' immediately without waiting for the installation to be completed. + +The result of this action is indicated in the attribute ActionResult. In case the installation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'InstallationExecutionFailed'. Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at installation failure.long + +Note. The behaviour described for this action is also obtained for the other installation actions if the Upgrade Control File indicates that the upgrade package is of type selective (which is recommended). +Note! This action does not require a transaction. + + + + + + + + This action interrupts an ongoing installation of an upgrade package. + +Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at execution of this action. + +This action is non-blocking i.e. the action initiates the cancel of the installation and returns 'void' immediately without waiting for the cancellation to be completed. + +During execution of this action the value of attribute 'ProgressHeader' is set to 'CancelOfInstallationIsExecuting'. + +In case the cancellation fails after 'void' has been returned this will be indicated by change of the value of attribute 'ProgressHeader' to 'CancelOfInstallationFailed'. + +Note! This action does not require a transaction. + +This action interrupts an ongoing installation of an upgrade package. +Already downloaded load modules (the downloaded file and the Load Module MO representing it) are not removed at execution of this action. +This action is non-blocking i.e. the action initiates the cancel of the installation and returns 'void' immediately without waiting for the cancellation to be completed. +During execution of this action the value of attribute 'ProgressHeader' is set to 'CancelOfInstallationIsExecuting'.The result of this action is indicated in the attribute ActionResult.In case the cancellation fails after 'void' has been returned the attribute 'ProgressHeader' is set to 'CancelOfInstallationFailed'. + +This action returns an actionID (created by the server). This actionID shall be used to locate the result of the action in attribute actionResult. + +Note! This action does not require a transaction. + + + + + + + Is used to clear the contents of current upgrade log file. + +Note! This action does not require a transaction. + + + + + + + + + + The Repertoire is an abstraction of a functionality represented by a plug in unit type (PiuType MO) and one or more load modules (LoadModule MO). The repertoire also provides rules for PiuType/ Load Module combinations valid for a specific function where one function can be provided by one or many PiuType-Load Module combinations. +These rules are used to load the correct software (Load Modules) to a PlugInUnit. This could be used as operator configuration support and/or in situations where automatic re-configuration is required (hot repair). + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade is recommended to create them. + + A user friendly name associated to the managed object. + + + "" + + + + + A function friendly name associated to the repertoire. The value must be unique with respect to all repertoires with the same install state. + + + + + + + + + Information regarding the function. + + + + + "" + + + + + A list containing all PiuType references that has been added to this repertoire. + + + + + + + + + + + + + + + + + + List of reserving SwAllocation MOs. + + + + + + + + + + + + The OSPF Interface MO represents an interface that is used by the OSPF protocol to communicate with a neighbour node. By connecting an OSPF interface to a Link MO that Link is defined as a link to be used by OSPF. + +Each OspfInterface MO must always be connected to a OspfArea MO. + + + User label for free use. + + + "" + + + + + The identity of the OspfArea connected to this OspfInterface. The default value is the default OspfArea MO. + + + + + + The time, in seconds, between LSA re-transmissions over the interface - default value 5 seconds. + + + 5 + + + + + The time, in seconds, between sending OSPF Hello-packets over the interface. Default value 10 seconds. + +Note! Must be a positive value. + + + 10 + + + + + The time, in seconds, after which a neighbor router is declared dead when not heard from. + + + + 40 + + + + + Estimated delay, in seconds, for the transmission of a link state update package over the interface. + + + + 1 + + + + + The interface priority. Each router is configured with a priority configured from 0 - 255 where 0 is the lowest priority and 255 the highest. + +Note! Must be a positive value. + + + + 0 255 + + 1 + + + + + Each OSPF interface is connected to one IP link. +The relatedLink can be either an IpAtmLink or an EthernetLink MO +reference. + + + + + + + + + + + + + + + + + Performance monitoring counter for the number of times this OSPF interface has changed its state or an error has occured. + +See RFC 1850. + + + + + + 0 + + + + + + + The Ospf MO represents an instance of the Open Shortest Path First (OSPF) routing protocol running in a Cello node. + +When the Ospf MO is created a default OspfArea MO is also created. This OspfArea has the areaId 000.000.000.000. + +The attribute range0 in the default OspfArea will contain the following values: +advertise = false +ipAddress = 000.000.000.000 +subnetMask = 000.000.000.000 + + + + + + + + + + + User label for free use. + + + "" + + + + + The ospfRouterId attribute is in the form of an IP address. +In order to able to set ospfRouterId the attribute +administrativeState has to be set to locked. The ospfRouterId +is uniquely identifying the router in the Autonomous System. By +convention to ensure uniqueness, this should be configured to the +value of one of the routers IP interface addresses. + + + + + + + The ospfASBdrRtrStatus attribute controls, whether this router is configured as an Autonomous System border router (Routers connected to multiple areas are called area border routers). The attribute must be set to 'True' if the user wants to configure static routes, which should be distributed to other OSPF routes as external routes. Configuration of static routes is the same as adding and deleting static routes to the IpRoutingTable Mo. + + + false + + + + + The operational state of the MO. +The operationalState can only be enabled when the IP MO is in workingMode routerMode. + + + + + + disabled + + + + + The administrative state of the MO. + + + locked + + + + + Area border router flag - indicates whether the router is acting as an area border router or not. + + + + + false + + + + + The name of the Ip MO that the Ospf MO is to use + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. It is a bit mapped CORBA long, where one or more of the bits may be set. If none of the bits are set then the availability status is considered to be undefined. + + + + + + NO_STATUS + + + + + The number of new link-state advertisments that have been originated. This number is incremented each time the router originates a new LSA. + +For more detailed information, see RFC 1850. + + + + + + 0 + + + + + The number of link-state advertisments received determined to be new instantiations. This number does not include newer instantiations of self-originated link-state advertisments. + +For more detailed information, see RFC 1850. + + + + + + 0 + + + + + Indicates whether the topology database is to be recovered from the database at restart. + + + true + + + + + The interval, in seconds, with which the topology database will be stored. + + + 60 + + + + + + + An OSPF autonomous system is divided into OSPF areas. The OSPF Area MO represents such OSPF areas. + +A default OspfArea MO is automatically created when the Ospf MO is created. +It has the identity = 1, so LDN of this MO will be +ManagedElement=1,IpSystem=1,Ospf=1,OspfArea=1. + +Note! A maximum of 4 OspfAreas can be configured each with a maximum of 8 interfaces. + + + + + + + + + + Label free for use. + + + "" + + + + + Indicates whether the OSPF area is a stub area or not. + + + false + + + + + Indicates whether importing Autonomous System external LSA's is supported. + + + true + + + + + Import Area summary - indicates whether the router will originate and propagate summary LSAs into a stub-area. + + + false + + + + + Cost for default route that the router advertises into the area if the area is a stub area and the router is an area border router. By default set to the least metric among the interfaces to other areas. + + + 1 + + + + + Stub Area metric type. + +RFC 1850 (OSPF V2 MIB): + +comparableCost (external type 1) +nonComparable (external type 2) + + + comparableCost + + + + + Area Lsa checksum - 32-bit unsigned sum of the link-state advertisements LS check sums contained in this area's link-state database. + + + + + 0 + + + + + The OSPF area identity in form of an IP address. This areId uniquely identifies the area. +AreaId 0.0.0.0 is used for the OSPF backbone. +Range: 000.000.000.000 to 255.255.255.255. + + + + + + + + + OspfArea IP address range zero (0). + + + + + + + + OspfArea IP address range one (1). + + + + + + + + OspfArea IP address range two (2). + + + + + + + + The number of times that the intra-area route table has been calculated using this area's link-state database. This is typically done using Dijkstra's algorithm. + +For more detailed information, see RFC 1850. + + + + + + 0 + + + + + Holds a list of the reserving OspfInterface MOs. + + + + + + + + + + Add aggregation range. Used to add a range of IP addresses to an OSPF area. + +Note! This action requires a transaction. + + + + + + The area range aggregation. + + + + + + + + + + + + + + + + + + + + Delete an IP address range. Used to remove a range of IP addresses from an OSPF area. + +Input is the area aggregation range index. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + The Switch Core Unit MO, SCU, represents the board specific HW on the SCB. This object collects HW failure on the board and sends alarms. It is also used for configuration of board specific FW. +This board can only be fitted in slot 1 and 28 in a standards subrack. +The board has a number of switch internal link ports. + alarm + + user label for free use. + + + "" + + + + + The administrative state of the switch internal link ports on the switch board. The attribute refers to all ports (locking will lock all ports, unlocking unlock all ports). +SILI -switch internal link interface. + + + + locked + + + + + Operational state indicates the the traffic handling capability of all ports as a group on the board, i.e it is enabled if one or more of the eight ports is enabled. The purpose of this attribute is only for test. + + + + + + disabled + + + + + Operational State for network synchronization distribution. + + + + + + disabled + + + + + The availability status of the switch internal link (SIL) ports.. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Availability state for network synchronization distribution. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + A list of the reserving MO's. + + + + + + + + + + The attribute provides a list of port numbers. +The port number is between 0-7 and is used to read state of the switch internal port. +See action getSilPortState, getOperState and getAvailState. + + + + + + + + + + + Returns status of the switch internal link port, which is the same as the LEDs on the unit. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns operational status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns availability status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + The General purpose Processor Unit MO, GPU, represents the board specific HW on the GPB; hard disk, ethernet and serial port etc. + +Note! The 'availabilityStatus' for the GeneralProcessorUnit MO is retreived from the PlugInUnit MO. + + + + + + + + + + Label free for use. + + + "" + + + + + Indicates if the function provided by the managed object is capable of performing its normal functions or not. + +Note! The value for operationalState is retrived from the GeneralProcessorUnit's parent, i.e. the PlugInUnit. + + + + + + disabled + + + + + The total size in bytes of the D volume. + + + + + + 0 + + + + + The amount in bytes of freespace available on the D volume. + + + + + + 0 + + + + + The total size in bytes of the P volume. + + + + + + 0 + + + + + The amount in bytes of freespace available on the P volume. + + + + + + 0 + + + + + Holds the identity of the reserving MO. + + + + + + + + + + The JVM MO is used to represent the Java Virtual Machine. This object is used for configuration JVM parameters, including SW management of Java class libraries used in the machine. + +The local distinguished name of this MO is ManagedElement=1, Equipment=1, JVM=1. + + + Label free for use. + + + "" + + + + + Current classpath, the JVM is using + + + + + "" + + + + + New classpath that will be activated at next restart of JVM. The classpath has a directory, which contains the load module, i.e. the classpath references the load module. + + + + + + + + Free memory in the java machine, in bytes. + +NOTE: Before this value is read from the system the action 'garbageCollect' is invoked. + + + + + 0 + + + + + Total amount of memory allocated to the java machine, in bytes. + + + + + 0 + + + + + Contains all classes that are to be initilised and started when the JVM restarts. + +Technical note: The specified classes must implement the se.ericsson.cello.moframework.Mopplet interface and be found in a jar/zip-file pointed out by the classpath. + + + + + + + + + + + Defines the start class name. +e.g. "se.ericsson.cello.oms.Oms" + + + + + "" + + + + + Current options: + -D<property>=<value> Set a system property value. Commonly java.class.path +-Xms<size> Specify the size, in bytes, of the memory allocation pool. +-Xss<size> Set thread stack size in bytes. +-Xverify:[all | remote | none] Verify classes according to the suboption. + -Xverify:all verifies all classes. + -Xverify:remote verifies remote classes only. + -Xverify:none turns off class verification. + + + + + "" + + + + + + + + + + + + + Determines the current system properties. + + + + + + + + + + + + A reference to the ReliableProgramUniter that refers to the programs in the which the JVM executes. + + + + + + + + New start class that will be activated at next restart of the JVM. +e.g. "se.ericsson.cello.oms.Oms" + + + "" + + + + + This attribute is used when setting one or more administrative options. + +A set option is operational after the next Java Machine restart. + +See also attribute 'options' + +One or more options can be set, one option in each string of the +sequence according to description below: + +Current options: + -D<property>=<value> Set a system property value. Commonly java.class.path +-Xms<size> Specify the size, in bytes, of the memory allocation pool. +-Xss<size> Set thread stack size in bytes. +-Xverify:[all | remote | none] Verify classes according to the suboption. + -Xverify:all verifies all classes. + -Xverify:remote verifies remote classes only. + -Xverify:none turns off class verification. + + + + + + + + This attribute holds the identity of the reserving MO. + + + + + + + + + + Runs the garbage collector. + +Note! This action does not require a transaction. + + + + + + Sets a system property (i.e. propertys in the operating system). +Note! The valeus set with this action is not saved in the database. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + + + + Restart of executing JVM instance. + +Note! This action does not require a transaction. + + + + + + + + This MO represents the switch of a Cello node. It is used for general switch configuration. + +The system creates automatically one instance of this MO at restart. + +Today, only a maximum of 32 Switch Modules MOs and 2 SwitchInternalLinks MOs per InternalLinkGroup MOs are allowed in a Cello node. However, in theory the switch addressing space in the system allows up to 256 SwitchModules MOs. This would then mean there are 255 InternalLinkGroup MOs, each of which is allowed 256 SwitchInternalLink MOs by the addressing. + +The local distinguished name of this MO is ManagedElement=1, SwitchFabric=1. + + + + + For free use. + + + "" + + + + + + + + + + + + + + + This MO represents two switch planes of one sub-rack, i.e. either the main switch or an external switch. + +Note! In a non-redundant system the administrativeStateSwitchPlaneA/B has to be set to locked for the non-present plane. + + For free use. + + + "" + + + + + Indicates the number of the switch module, SMN. + +switchModuleNumber &gt;= 0 + +The main switch module, with one or two TimingUnits, is given SMN = 0. SMN for extension switch modules depends on the port pair that the extension switch module is connected to in the main switch module. + +The SMN is calculated according to the following formula: + +Switch module number [1..255] = int (APN/2)*8 + ISL-port in main [1..8] + +APN - ASCC port number +ISL - inter-switch link + + + + + + + 0 255 + + + + + + secondSmnEvaluation - There are two cables that +are relevant for Switch Module Number (smn) numbering +If the cabling is wrong secondSmnEvaluation +will show the second opinion about smn. +Under normal conditions secondSmnEvaluation = smn. + + + + + + 0 + + + + + The administrative state of the switch module. + +Note! When setting the 'administrativeState' to shutting down a notification about that the state has changed to 'locked' will be sent towards the operator. There is however no guarantee that this operation has been succesful despite the notification and state change due to limitations in the resource layer + + + + unlocked + + + + + The administrative state of switch plane A. +It is not allowed to lock both switch plane A and B. + +Note! When setting the 'administrativeState' to shutting down a notification about that the state has changed to 'locked' will be sent towards the operator. There is however no guarantee that this operation has been succesful despite the notification and state change due to limitations in the resource layer + + + unlocked + + + + + The administrative state of switch plane B. +It is not allowed to lock both switch plane A and B. + +Note! When setting the 'administrativeState' to shutting down a notification about that the state has changed to 'locked' will be sent towards the operator. There is however no guarantee that this operation has been succesful despite the notification and state change due to limitations in the resource layer + + + unlocked + + + + + The operational state of the Switch Module. At least one of switch plane is enabled. + + + + + + disabled + + + + + The operational state of Switch Module plane A. The state is disabled if any switch ports is faulty. But switch may still be used. + + + + + + disabled + + + + + The operational state of Switch Module plane B. The state is disabled if any switch ports is faulty. But switch may still be used. + + + + + + disabled + + + + + The availability status of the Switch Module. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The availability status of the Switch Plane A. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The availability status of the Switch Plane B. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The active switch plane: A, B. During multiple faults, both plan A and B may be used. + + + + + + switchPlaneA + + + + + List of reserving MOs. + + + + + + + + + + + + + + + + + + + + The Internal Link Group MO represents all switch internal links connecting the main switch to an external switch. + +Switch internal links are automatically grouped in Reliable Groups for redundancy. + + For free use. + + + "" + + + + + Reference to the SwitchModule MO that is interconnected by the link in the InternalLinkGroup. + + + + + + + + + Reference to the SwitchModule MO that is interconnected by the link in the InternalLinkGroup. + + + + + + + + + The administrative status of internal link group. + + + unlocked + + + + + The operational status of internal link group. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + Returns a list of resource instance identities of the switch internal links in the specified Reliable Group. + +The existing Reliable Groups are listed with action getReliableLinkGroups. + +Note! This action is transactional. + + + + + + + Reliable link group number. + + + + + + + + + Returns the status of the specified switch internal link, within the specified Reliable Group. + +Note! This action is transactional. + + + + + + + + + + + + Reliable link group number. + + + + + + + + + Returns a sequence of Reliable Group numbers. + +Each Reliable Group is identified by a unique number which can be used to read out the identities of the switch internal links that are allocated to the Reliable Group. This is done with action getRlgLinks. + +The allocation of switch internal links to Reliable Groups is automatic. + +Note! This action is transactional. + + + + + + + + + + + + This MO represents a link interconnecting the from either a SCB or SXB port on the main switch to a SCB on an external switch. + +The main switch is located in the hub subrack. + +The SCB is represented by the SwitchCoreUnit MO, while the SXB is represented by the SwitchExtensionUnit MO. + +Switch internal links are automatically grouped in Reliable Groups for redundancy. + + Label free for use. + + + "" + + + + + + + + + + + + + The reference of one connection point for a SwitchCoreUnit or SwitchExtensionUnit. + + + + + + + + + The reference of one connection point for a SwitchCoreUnit or SwitchExtensionUnit. + + + + + + + + + Switch internal port number on PlugInUnit1. + +Note! +On a standard SCB/SXB board, the ports are labeled from the bottom to the top. + +Port nr -> label: + '0' 'D' + '1' 'C' + '2' 'B' + '3' 'A' + +Also note that his mapping will change when adding/removing a board. + + + + + + + 0 3 + + + + + + Switch internal port number on PlugInUnit2. + +Note! +On a standard SCB/SXB board, the ports are labeled from the bottom to the top. + +Port nr -> label: + '0' 'D' + '1' 'C' + '2' 'B' + '3' 'A' + +Also note that his mapping will change when adding/removing a board. + + + + + + + 0 3 + + + + + + The administrative state of switch internal link. + + + unlocked + + + + + The operational state of switch internal link. There is no traffic if the link is disabled. + + + + + + disabled + + + + + The availabilityl status of switch internal link. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The operational state of sync link. There is no clock distribution if the link is disabled. + + + + + + disabled + + + + + The availability state of sync link. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + This MO represents the hardware of the ET-M4 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-M4 board contains 2 physical ports that can be configured as either STM1(ETSI/TTC) or OC3C (ANSI). The board supports unchannelised ATM access (i.e. it maps ATMs cells directly into an SDH VC4 container). + +The board supports up to 1800 ATM VC connections. +The number of terminated VPs are limited to 48/board. +The board supports up to 750 VC UBR+ connections. + +The ET-M4 board contains 128 AAL2 multiplexers. +The ET-M4 board supports up to 256 bidirectional F4/F5 PM flow per port. + +Note! IMA is not applicable for the ETM4 board. + +Note! The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 256 per board. + +Note! When using the Etm4 board the performance monitoring counters in the transmit direction found on the AtmPort MO does not show the following cells: CC cells and OAM FPM cells. + + User label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the hardware ETM4. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + Virtual path connection termination point, VpcTp, is used to represent the point where the VPC and associated overhead (F4 OAM cells) are terminated/originated. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + Label for free use. + + + "" + + + + + + + + + + + + + enabled or disabled according to the actual operational state of the VpcTp + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Continuity checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. Continuity check both enables generation of CC cells as well as detection of LOC + + + false + + + + + PM mode is set to indicate type of performance monitoring mode (i.e. activation of bidirectional PM measurements). + + + + + PM_MODE_OFF + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + + NOM_PM_BLKSIZE_2_10 + + + + + Performance monitoring counter for number of lost forward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM, cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + This action performs VC end to end loopback from this VpcTp. +false=Failed, true=Succeded + +Note! This action requires a transaction. + + + + + + + + + This MO is used to represent the termination of a VP link. + +Note that a maximum of 999 MO's of this type may be configured. + +Note! For information on how many VplTp's that can be configured under the AtmPort MO please refer to the board that is parent to the termination reserved by the AtmPort MO. + +The performance monitoring counters in the VplTp MO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + This MOs user label. + + + "" + + + + + Reference to the Atm Traffic Descriptor. + + + + + + + enabled or disabled according to the actual operational state of the VplTp. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This is the virtual path identifier for the external ATM cells. + + + + + + + 0 255 + + + + + + Performance monitoring counter for number of received ATM cells for the VplTp. + + + + + + + + 0 + + + + + Performance monitoring counter for number of transmitted ATM cells. + + + + + + + 0 + + + + + + + + + + + + + + + This MO represents a timing unit (reference clock) in the node. + +The corresponding Program shall be of LoadModuleLoaderType, SpmFpgaLoader. + + Label for free use. + + + "" + + + + + Operational state of TimingUnit + + + + + + disabled + + + + + The availability status of the TimingUnit. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + The PiuType is an MO that holds product information about a PlugInUnit and the execution resources of the PlugInUnit. It is created/deleted during a software upgrade. +The PiuType is used when creating execution MOs connected to a PlugInUnit and when allocating software to this resource. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + + + + + A user friendly name associated to the managed object. + + + "" + + + + + The productData describes the product number, short product revision, product name and product information of the PlugInUnit. The production date is not used. + +Trailing letters in the revision is recommended to be excluded in the PiuType. Example: R2B will be R2 without trailing letter, R2B/3 must be R2B/3 in the PiuType, R2B/A should be R2 in the PiuType. + + + + + + + + + + The width of the PlugInUnit board in steps of 5 mm. +A PlugInUnit can use/cover more than the slot that it occupies. + +Example: boardWidth=3 corresponds to 3*5 = 15 mm. + + + + + + + + + Control value m3/h for the fan unit. Needed by cooling function. + + + + + + + + + + + + + + + + The value will be MP if a board has the role of a Main processor. +The value will be BP if a board has the role of a device board +Otherwise the value will be OTHERS. + + + + + + + + + + The identity's of the reserving MO's. + + + + + + + + + + Returns the number of entries in the PIUTypeConfigurationArray. + +Note! This action requires a transaction. + + + + + + Returns a struct of a specific MoConfiguration at a given index. +The moConfiguration holds information about how to create the +subordinate objects for a specific piu type. + +Precondition: 0 <= index <= numberOfMoConfigurations() - 1 + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This MO is primarily used to handle data for automatic configuration of load modules. Automatic in the meaning that the system selects the appropriate load module and revision. A SWA may be related to a slot, indicating that a specific functionality is requested at this location. The SWA is manually created by the operator. + +The SWA object is related to (one or more) repertoires, which hold information on possible PIU-type/revisions and load module combinations. + +In some cases (e.g multi-purpose boards, boards with processor/FPGA-pools) it may not be possible to completely configure the PIU without instructions from the operator (e.g which load module runs on which processor/FPGA). In these cases a specialization of the SWA has to be designed in such a way that it can be manually configured. + +When a SwAllocation MO depends on a ManagedObject MO, this ManagedObject actually represents a RBS Fan. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade is recommended to create them. + + Free for use. + + + "" + + + + + The role of a slot/PIU. The role must be unique with respect to other SwAllocations in the node. + +This is a preparation to introduce predefined SwAllocation in future upgrade packages. + + + + + + + A list of references to repertoires. + + + + + + + + + A list of references to mainly slots in a subrack, e.g. Slot or Fan MO. It may also refer to other objects handling auxiliary units, e.g. RBS Fan. + + + + + + + + + + + + + + + + + Adds the specifed repertoire to this list. + +Note! This action does not require a transaction. + + + + + + + + + + + + + Removes the first occurrence of the specified repertoire from this list. + +Notw! This action does not require a transaction. + + + + + + + + + + + + Adds the specified Slot to the slotList. +The slot can only be of type Slot MO, Fan MO, WebServer MO, JVM MO or an applicable type of application MO (e.g. for "RBS Fans"). + +Note! This action requires a transaction. + + + + + + + + + + + + + Removes the first occurrence of the specified slot from this list. +The slot can only be of type Slot MO, Fan MO, WebServer MO or an +applicable type of application MO (e.g. for "RBS Fans"). + +Note! This action requires a transaction. + + + + + + + + + + + + Removes all repertoires from this list and sets its size to zero. + +Note! This action requires a transaction. + + + + + + Removes all slots from this list and sets its size to zero. + +Note! This action requires a transaction. + + + + + + Adds the specified Slot to the slotList. +The slot can only be of type Slot MO, Fan MO, WebServer MO, JVM MO or an applicable type of application MO (e.g. for "RBS Fans"). +If the slot exists in the list, the object is ignored. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + Adds the specifed repertoire to this list. + +If the repertoires exist in the list the repertoire is ignored. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + The Medium Access Unit (MAU) MO represents the Ethernet transceiver function on a General Processor Board (GPB). + +Note! Ethernet links which are modelled by a MediumAccessUnit MO are used for O&M IP traffic only. MediumAccessUnit MOs must not be configured under a GeneralProcessorUnit MO which have a IpAccessHostGpb referring to it. + +Note! This object is known in standards as "MediumAttachmentUnit". + + + Label for free use. + + + + "" + + + + + Description of operational state which has an enumerated datatype + + + + + + disabled + + + + + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This attribute is used by a management system to show the label on the port the connector is attached to. + + + + + Eth + + + + + Performance management counter for the number of times that a collision was detected on the interface after the minimum length of a frame. + + + + + + 0 + + + + + Performance management counter for the number of frames that did not pass the FCS check. + + + + + + 0 + + + + + The Link Speed, measurment unit is Mb/s.. + + + + + + 0 + + + + + The duplex mode used. + + + + + + + + FULL_DUPLEX + + + + + + + A Reliable Program Uniter (RPU) is a controlling and addressing entity providing one common addressing unit for two Reliable Programs. Or more correctly for parts of two Reliable Programs, each part is called a Resource Suite Handler (RSH). The RSH is implemented and owned by the application. It is not a function or a concept within Cello. + +MOs of this type are created automatically during system upgrade. +MOs of this type are possible to create manually but a system upgrade +is recommended to create them. + + For free use. + + + "" + + + + + Reliable Program Label. +Compare this to the reliableProgramLabel in LoadModule MO. + + + + + + + + + Reference to slot, contains the running "Normal" relation to a slot. If the reference is set to the passive slot, the passive slot will be cleared and only one relation will be set. + + + + + + + Reference to slot, contains the running "Stand-by" relation to a slot. If the reference is set to the active slot or a null value, the passive slot will be cleared. + + + + + + This attribute controls when to switchover the RPU, if a certain type error situation occurs. + + + AtPiuFault + + + + + This attribute controls when to switch back the RPU, after error recovery has been done. + + + Automatic + + + + + This attribute indicates that which level of data replication that is associated with the RPU. + + + + + ApplControlled + + + + + This attribute indicates if the RSH execution mode (active/passive) in the two Reliable Program, matches the normal/stand-by relations set on the corresponding RPU. + + + + + + Unavailable + + + + + + + + + + + + + + List of reserving MOs. + + + + + + + + + + This action will force the two corresponding RSHs to change their execution mode (active/passive). It will lead either to a switchover or to a switchback, depending of what value the operational Mode attribute is showing. + +Note! This action requires a transaction. + + + + + + + + + This object contains attributes and actions on Cello node-level. + +The ManagedElementData MO is automatically created and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, ManagedElementData=1. + + + + + + + + + + + This attribute specifies if the system is allowed to auto create detected objects. Note that slots will always be auto created. + +Note! When setting this attribute from true to false the system creates a new CV. + + + false + + + + + The base URL for the documentation server (ALEX). The attribute is read by Element Management application to find the documentation server in the network. + + + "" + + + + + A list of node names or IP addresses of the single logon servers (SLSs). The list uses commas to seperate the single logon server addresses, e.g. "https://SLS1,https://SLS2,https://SLS3", these addresses consists of the URLs to the concerned SLS servers. The attribute is read by Element Management application to find the single logon server in the network. + + + "" + + + + + IP addresses to the DHCP server, used by the DHCP Relay Agent. + +Default is an empty array. + +Adding and removing addresses is done through the actions addDhcpServerAddress() and removeDhcpServerAddress(). + + + + + + + + empty + + 10 + + + + + This attribute is used by the internal performance management service +to know where to store it's data files. The attribute is the name of +a path in the node. + +Example: /c/public_html/cello/XML_files/ + + + "" + + + + + This is the IP address to the NTP server + + + "" + + + + + This is a boolean that controls if the node should poll the primary NTP server for information. + + + false + + + + + This value states the minimum interval (in seconds) for polling the primary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 64 + + + + + This value states the maximum interval (in seconds) for polling the primary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 1024 + + + + + This is the burst flag used towards the primary NTP server. + + + false + + + + + This is an alternative IP address to a NTP server + + + "" + + + + + This is a boolean that controls if the node should poll the secondary NTP server for information. + + + false + + + + + This value states the minimum interval (in seconds) for polling the secondary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 64 + + + + + This value states the maximum interval (in seconds) for polling the secondary NTP server. + +Note! This value has to be > 0. + + + + 16 131072 + + 1024 + + + + + This is the burst flag used towards the secondary NTP server. + + + false + + + + + This attribute specifies the UTC time used in the node. The attribute value is milliseconds since epoch (January 1, 1970, 00:00:00 GMT). +The value may only be set while ntpServiceActive both for primary and secondary is false. + + + 0 + + + + + This value states in what time zone the node is located. This attribute is needed by management application to convert UTC time from a log or NTP service to local time. +It will not change the real time clock on the node. + +The timeZone is represented by three characters, example GMT. + +Available options are: + +TimeZone ID Offset +GMT (Greenwich Mean Time) 0 +UTC (Coordinated Universal Time) 0 +ECT ( Central European Standard Time) + 1 +EET (Eastern European Time) + 2 +ART (Eastern European Time) + 2 +EAT (Eastern African Time) + 3 +MET (Iran Time) + 3.5 +NET (Armenia Time) + 4 +PLT (Pakistan Time) + 5 +IST (India Standard Time) + 5.5 +BST (Bangladesh Time) + 6 +VST (Indochina Time) + 7 +CTT (China Standard Time) + 8 +JST (Japan Standard Time) + 9 +CST (Central Standard Time) + 9.5 +EST (Eastern Standard Time) + 10 +AET (Eastern Standard Time) + 10 +SST (Solomon Is. Time) + 11 +NST (New Zealand Standard Time) + 12 +CAT (Central Alaska Time) - 1 +AGT (Argentina Time) - 3 +BET (Brazil Time) - 3 +CNT (Newfoundland Standard Time) - 3.5 +PRT (Atlantic Standard Time) - 4 +IET (Eastern Standard Time) - 5 +ACT (Central Standard Time) - 6 +PNT (Mountain Standard Time) - 7 +MST (Mountain Standard Time) - 7 +PST (Pacific Standard Time) - 8 +AST (Alaska Standard Time) - 9 +HST (Hawaii Standard Time) - 10 +MIT (West Saoma Time) - 11 +-- + +Reference: http://www.greenwichmeantime.com + + + + "" + + + + + This attribute states weather daylight saving time is used on this node. It is used to by the management application and will not change the real time clock on the node. + + + false + + + + + The total size of the C volume on the Cello node in bytes. The C volume may be replicated on several hard disks. + + + + + + 0 + + + + + The number of bytes of free space available on the C volume. The C volume may be replicated on several hard disks in a Cello node. + + + + + + 0 + + + + + This is a unique node identity to be set only in the factory. + + + + + "" + + + + + A list of URLs of external server for downloading of software. A comma-separated list or URLs, complete with path and name of property file. + +Note: For downloading of software for system upgrade, see attribute ftpServerIpAddress in MO UpdradePackage. + + + "" + + + + + The type of node restart when it is a problem with the last PIU in a PIU group. + + + WARM_AT_PIU_RESTART + + + + + The sync mode operation of the node. Note that this attribute is only relevant when the node contains CBU board. For all other cases the value shall be set to NOT_USED. + + + NOT_USED + + + + + This action creates the primary Network Time Protocol. There can only exist one primary and one secondary ntp. + +Once the ntp is created it is possible to change the attributes, i.e ip address, burst flag, max- and min poll and which is the active one. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This action creates the secondary/alterative Network Time Protocol. +There can only exist one primary and one secondary ntp. + +Once the ntp is created it is possible to change the attributes, i.e ip address, burst flag, max- and min poll and which is the active one. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This action deletes the primary NTP. + +An exception will be thrown if the primary attributes are accessed (set and get). + +Note! This action requires a transaction. + + + + + + + This action deletes the secondary NTP. + +An exception will be thrown if the secondary attributes are accessed (set and get). + +Note! This action requires a transaction. + + + + + + Takes an array of Ip addresses (Strings), and adds them to the list held by the Dhcp Relay Agent fRO. + +Note! This action requires a transaction. + + + + + Elements are assumed to have the format of a String with 4 fields of numerics, each field separated with a dot. E.g. 123.322.34.123. An empty array or empty string in first element is not allowed. Max 10 elements. + + + + + + + + + + + Takes an array of Ip addresses (Strings), and removes them from the list held by the Dhcp Relay Agent fRO. + +Note! This action requires a transaction. + + + + + Elements are assumed to have the format of a String with 4 fields of numerics, each field separated with a dot. E.g. 123.322.34.123. An empty array or empty string in first element is not allowed. Max 10 elements. + + + + + + + + + + Used for setting the nodeUniqueId attribute. This method should only be used in the factory, i.e. it is not for general use by the operator. + +Note! This action requires a transaction. + + + + + + + + + + + + + + This MO represents the Switch Extension Unit, SXU, board. The board may only be inserted in slot 2-27 (in a standard subrack). +If redundant links are used, two boards must be inserted next to each other. +The board has a number of switch internal link ports. + + + + + + + + + + This attribute is used to hold a user friendly name of the object if needed. + + + "" + + + + + The administrative state of switch internal link ports on the switch board. +The attribute refers to all ports (locking will lock all ports, unlocking will unlock all ports). +SIL- switch internal link. + + + + + unlocked + + + + + Operational State for all ports. Operational state is enabled if one of the eight ports is enabled. + + + + + + disabled + + + + + Operational State for network synchronization distribution + + + + + + disabled + + + + + The availability state of switch internal link (sil) ports. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The availability state of the sync link. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The attribute is set by the action Reserve. + + + + + + + + + + The attribute provides a list of port numbers. +The port number is between 0-7 and is used to read state of the switch internal port. +Se action getSilPortState, getSilOperState and getSilAvailState. + + + + + + + + + + + Returns status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns operational status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + Returns availability status of the switch internal link port. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + This MO is used to represent an AAL2 Path Distribution Unit. Such a unit handles a set of Aal2PathVccTps that belong to the same Aal2 AP and that are handled by the same Path Resource Handling Program. +This Path Resource Handling Program is referenced by the rpuId attribute. + + + + + + + + + + Label for free use. + + + "" + + + + + The physical location of a CPS RC (Common Part Sub-Layer Resource Control) program represented by a reference to a ReliableProgramUniter. + +Note that one ReliableProgramUniter MO may only be referenced once under one Aal2Ap. That means all Aal2PathDistributionUnits must reference different ReliableProgramUniter MO's. + +Two Aal2PathDistributionUnits under different Aal2Ap's may however reference the same ReliableProgramUniter MO. + + + + + + + + + List of references to Aal2PathVccTp MO:s. +Note that setting of this attribute removes the current list of Aal2PathVccTp's. +Each reference must be unique among all paths within all Aal2PathDistributionUnit's belonging to the same Aal2Ap. + + + + + + + + This action adds a list of Aal2PathVccTps to an Aal2PathDistributionUnit. + +If the data contains a reference to a non existing path, the exception InvalidReference is raised. + +If the path list contains a path that has a non-unique aal2PathId value, then the exception Aal2PathIdNotUnique is raised. The pathId value must be unique within all Aal2PathDistributionUnits under the same Aal2Ap. + +If the path list contains a path that already belongs to a Aal2PathDistributionUnit, then the exception PathAlreadyRegistered is raised. + +Note! Adding one or more Aal2PathVccTps using this action updates the attribute 'Aal2PathVccTpList'. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + This action removes a list (sequence) of AAL2 path's from the Aal2PathDistributionUnit. + +If the path list contains a path that is not in this Aal2PathDistributionUnit, the exception NotInGroup is raised. + +Note! Removing one or more Aal2PathVccTps using this action updates the attribute 'Aal2PathVccTpList'. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + The Fan is used for cooling the Cello-subrack and is connected to one or two +SCU (switch core board). This MO is used for controlling and sending alarm from +the Fan. + +Note, either the fan can be supplied by Cello and Fan MO is used, or alternatively the fan can supplied by a source external to Cello and therefore a ManagedObject MO is used to represent the fan. + + + + + + + + + + + + user label for free use. + + + "" + + + + + The administrativeState of Fan MO. + + + locked + + + + + A Fan must always be connected to a Switch Core unit that mediates the communication with a main processor. + +In this attribute it is possible to see which SwichCoreUnit that the fan is connected to. + + + + + + + + + + The operational state is set to 'enabled' when the Fan has loaded and started its load module. + + + + + + disabled + + + + + A reference to an available PiuType at create of a Fan. + + + + + + + + The application that controls the Fan has three main states: +- standalone: running on itself, not manageable +- autonomous: manageable state +- noiseReduced: temporary state with reduced cooling + +NOTE: This attribute is not supported in CPP 4. + + + + + + standalone + + + + + The physical address of the RS-485 communication link. +Incorrect setting of the address can cause collision with other connected auxiliary units or lost connection. The default value should be suitable for most configurations. + + + + + + 1 255 + + 7 + + + + + The identity of the reserving MO. + + + + + + + + A restart will cause the Fan to be initiated, re-booted and all load modules to be reloaded from persistent memory. This is also known as a forced reload. + +Note! This action requires a transaction. + + + + + + + + + + + + + + + + + This MO represents a MTP2 Termination Point for the ITU standard, as defined in Recommendation Q.703 07/96. + +The performance monitoring counters found in Mtp2Itu MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a hardware fault, aal1 server/adm restart or node restart. + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard +which is NOT the ITU standard. + +NOTE: There is a restriction of a maximum of 32 Mtp2Tp's per MP. + + Free tag for marking this managed object. + + + "" + + + + + + + + + + + + + The operational state of the MTP2 Signalling Terminal. + + + + + + disabled + + + + + Reference to a Mtp2ProfileItu MO. + +Note: The bitRate can not be changed. + + + + + + + + Number of re-transmitted octets. + + + + + + 0 + + + + + Number of negative acknowledgements received. + + + + + + 0 + + + + + Number of signal units received in error. + + + + + + 0 + + + + + Number of started local RB congestions. + + + + + + 0 + + + + + Number of octets in send buffer. + + + + + + 0 + + + + + Total time in local SIB (Sending). + + + + + + 0 + + + + + Total time in remote SIB (Receiving). + + + + + + 0 + + + + + Number of SIO & SIF octets transmitted. + + + + + + 0 + + + + + The attribute is set by the list of reserving MO's. + + + + + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + The PlugInUnit MO that this MO references. +It indicates on which processor the Termination Point will be. + +Note: The PlugInUnit must be of type GPB. + + + + + + + + + Number of MSUs transmitted. + + + + + + 0 + + + + + Number of SIO and SIF octets received. + + + + + + 0 + + + + + Number of MSUs received.. + + + + + + 0 + + + + + + + This MO represents a MTP2 Termination Point for the ANSI standard , as defined in T1.111-1996. + +The performance monitoring counters found in Mtp2Ansi MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a hardware fault, aal1 server/adm restart or node restart. + +NOTE: This MO cannot in anyway be related (either contained by or dependent on) an MO that belongs to a +standard which is NOT the ANSI standard. + +NOTE: There is a restriction of a maximum of 32 Mtp2Tp's per MP. + + Free tag for marking this managed object. + + + "" + + + + + + + + + + + + + The operational state of the MTP2 Signalling Terminal. + + + + + + disabled + + + + + Reference to a Mtp2ProfileAnsi MO. + +Note: The bitRate can not be changed. + + + + + + + + Number of re-transmitted octets. + + + + + + 0 + + + + + Number of negative acknowledgements received. + + + + + + 0 + + + + + Number of signal units received in error. + + + + + + 0 + + + + + Number of started local RB congestions. + + + + + + 0 + + + + + Number of octets in send buffer. + + + + + + 0 + + + + + Total time in local SIB (Sending). + + + + + + + 0 + + + + + Total time in remote SIB (Receiving). + + + + + + 0 + + + + + Number of SIO & SIF octets transmitted. + + + + + + 0 + + + + + Number of MSUs received.. + + + + + + 0 + + + + + List of reserving MO. + + + + + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + The PlugInUnit MO that this MO references. +It indicates on which processor the Termination Point will be. + +Note: The PlugInUnit must be of type GPB. + + + + + + + + + Number of MSUs transmitted. + + + + + + 0 + + + + + Number of SIO and SIF octets received. + + + + + + 0 + + + + + + + The Ds0Bundle, Digital Signalling Level 0, MO represents a number of timeslots on a physical port. +Any of E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp or T1Ttp. +The Ds0Bundle can be used in three different ways: + +- Fractional ATM + +Please refer to the AtmPort MO for details. Note that the TdmMode attribute +must be disabled. + +-Circuit emulation + +Please refer to Aal1VccTp MO for details. Note that the TdmMode attribute +must be disabled. Note that only 4 Ds0Bundle's per port can be configured +when running circuit emulation. + +- TDM Switching + +The Ds0Bundle is reserved for switching node internal Ds0 connections. In +this mode, the tdmMode attribute should be enabled. + + + + + + + + + + + + + Free tag for marking this managed object. + + + "" + + + + + The availabiltity status of Ds0Bundle. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The operational state of Ds0Bundle. + + + + + + disabled + + + + + The list gives the time slots (within ATM traffic fraction) that are to be allocated to the Ds0Bundle. + +When a Ds0Bundle is contained by a E1PhysPathTerm the slots that can be placed in this list are 1 to 31. +When a Ds0Bundle is contained by a J1PhysPathTerm then the slots that can be placed in this list are 1 to 24. +When a Ds0Bundle is contained by a T1PhysPathTerm then the slots that can be placed in this list are 1 to 24. +When a Ds0Bundle is contained by a E1Ttp the slots that can be placed in this list are 1 to 31. + +Note: the same timeslot cannot appear more than once in the list! If a E1/J/T1PhysPathTerm contains more than +one Ds0Bundle, then the Ds0Bundles listOfTimeSlots must be mutually exclusive (i.e. slots in one list cannot be used in another list). + +Note! If the Ds0Bundle is used for carrying SS7 traffic, the listOfTimeSlots can only contain 1 (one) time slot. +In this case that is if the Ds0Bundle is reserved by an Mtp2TpAnsi, Mtp2TpItu or Mtp2TpChina. + + + + + + + + 0 31 + + + + + + + The state of tdmMode (Time Division Multiplexing), can be disabled/enabled. + + + + + + + + + + + The identity of the reserving MO. + + + + + + + + + + + + The Aal1TpVccTp MO represents the Aal1 interworking function in a circuit emulation. The object refers to a Ds0Bundle which represents one end of the circuit emulation, and a VclTp which represents the other end. + +Note! The performance monitoring counters in this MO is set to 0 when counterMode is set to PM_MODE_ON. +In PM_MODE_OFF no information at all is retrived. So any value for pm-monitoring is measured from the time +of setting counterMode to PM_MODE_ON. +At node restart these performance monitoring counters is reset to 0. + + Free tag for marking this managed object. + + + "" + + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + Indicates how many bytes are filled in each ATM cell. The value 47 indicates that the partial filled cells is not used, i.e. all the cells are filled completely. + +Partial filling of cells in used in circuit emulation. It is used to reduce packetisation delay. Refer to the ATM Forum specifications for more details. + + + + + + + 23 47 + + 47 + + + + + Specifies the cell delay variation tolerance. Refer to ATM Forum specifications for more details. + +Unit is micro seconds. + + + + + + 100 4000 + + 1000 + + + + + The operational state of Aal1TpVccTp. + + + + + + disabled + + + + + Continuitiy checking means that a cell is sent downstream when no user cell has been sent for a period of nominally 1 second. + +Activates VC end to end continuityCheck according to ITU.T rec I.610. + + + false + + + + + Controls the activation of PM counters and F5 PM flow on the VC connection. + + + PM_MODE_OFF + + + + + Nominal performance monitoring (PM) blocksize. The minimum number of ATM cells to send before sending a Forward Performance Monitoring, FPM, cell. + + + NOM_PM_BLKSIZE_2_10 + + + + + Performance monitoring counter for forwarded lost cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of forwarded errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Forward Performance Monitoring, FPM cells. + + + + + + 0 + + + + + Performance monitoring counter for number of lost backward cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward missinserted cells. + + + + + + 0 + + + + + Performance monitoring counter for number of backward errored blocks. + + + + + + 0 + + + + + Performance monitoring counter for number of lost Backward Reporting, BR, cells. + + + + + + 0 + + + + + + + + + + + + + The VclTp MO that this MO references. + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Attribute to decide what type of alarms to be reported. + + + ALARM_LOC + + + + + + + Mtp3b Signalling Point for the ANSI standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the Ansi standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpAnsi MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ANSI standard. + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + + + + + + + + + + User label for free use. + + + "" + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + The network indicator, NI, is used for discrimination of messages between functionally different networks. + + + + + + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 24)-1 (16777215). +The SignallingPointCode (SPC) is normally grouped together as three numbers wich correspond to network identifier, network cluster, network cluster member. The three numbers are coded as 8-8-8 bits in the total SPC. To enter the SPC-value, you have to convert the 3 numbers to their binary code and then convert the whole 24-bit patterna as an integer. Sometimes the SPC is used as a whole uniqe number (no internal structure). + + + + + + + + 1 16777215 + + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +Minimum string length 2 characters, maximum 30 characters. Allowed characters are 0-9, A-F. +Only even number of characters is allowed. + + + + 2 30 + + "A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5" + + + + + The nodeBehaviour attribute represents the MTP3b node type. + + + + + SEP + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + Determines how a TransFer Restricted signal (TFR) should be treated. + + + + IGNORED + + + + + The sioSpare2 attribute determines if the two spare bits in the SIO (Service Information Octet) should be treated as spare. + + + PRIO + + + + + For M3UA, number of attempts to send the DAUD message. + + + + 1 65535 + + 5 + + + + + Number of attempts to send the SCTP_ASSOCIATE_REQ message. + + + + 0 65535 + + 4 + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The sendSltmBefLink attribute determines if the SLTM (Signalling Link Test Message) should be sent and a SLTA received before the link is considered to be in service. + +Note! It is not recommended nor is it in accordance with standard to set the value of this attribute to 'false' + + + true + + + + + Struct containing the ANSI priority attributes. + + + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 1 + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Struct containing ANSI specific timer data. + + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of received CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of times the timer T21 was started (i.e. how many times the remote inhibit test message has been sent). + + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + The number of successful abortions of signalling associations. + + + + + 0 + + + + + The number of succesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of unsuccessful abortions of signalling associations. + + + + + 0 + + + + + The number of unsuccesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of incoming request for association establishment when state on the association is 'DOWN' and establishment of associations is blocked. + + + + + 0 + + + + + The number of times that the max limit for trying to establish an association has been reached. + + + + + 0 + + + + + The number of times that the max limit for trying to activate an association has been reached. + + + + + 0 + + + + + The number of messages with low priority that has been discarded. + + + + + 0 + + + + + + + Mtp3b Signalling Point for the ITU standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the ITU standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpItu MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ITU standard. + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + +NOTE: The value of the attribute 'version' is valid for all SPs (Mtp3bSpItu MOs) and the value of the last created or changed SP will be used for all SPs. + + + + + + + + + + User label for free use. + + + "" + + + + + The networkInd attribute (NI) is used by signalling message handling functions in MTP3b + + + + + + + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 14)-1 (16383). +The SignallingPointCode (SPC) is normally used as a whole unique number (no internal structure). But sometimes the SPC is grouped together as three numbers which corresponds to zone, area/network, signalling point. If this is the case the three numbers are coded as 3-8-3 bits in the total SPC. To enter the SPC-value then you have to convert the three numbers to their binary code and then convert the whole 14-bit pattern as an integer. + + + + + + + 1 16383 + + + + + + This attribute shows what MTP3b ITU standard the system follows. With ITU, it is possible using this attribute to set which of the ITU standard versions that shall be followed. + +Note! Setting of another value than 'ITU_T_07_96' at create will have no effect. The Signaling Point will always be created with the value 'ITU_T_07_96'. + +Note! It is not possible to hav signaling points with different versions in the node so setting of this attribute will effect all signaling points. The value for the last created or changed signaling point will be used for all signaling points. + + + ITU_T_07_96 + + + + + The nodeBehaviour attribute represents the MTP3b node type. + + + + + + + SEP + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 1 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + Determines if a TransFer Restricted signal (TFR) should be treated as a TFA (TransFer Allowed signal) or be ignored. + + + + IGNORED + + + + + The sioSpare2 attribute determines if the two spare bits in the SIO (Service Information Octet) should be treated as spare. + + + PRIO + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + The sendSltmBefLink attribute determines if the SLTM (Signalling Link Test Message) should be sent and a SLTA received before the link is considered to be in service. + +Note! It is not recommended nor is it in accordance with standard to set the value of this attribute to 'false' + + + true + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +Minimum string length 2 characters, maximum 30 characters. Allowed characters are 0-9, A-F. +Only even number of characters is allowed. + + + + + + 2 30 + + "A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5" + + + + + Struct containing the priority attributes. + + + + + + + Struct containing ITU specific timer attributes + + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + For M3UA, number of attempts to send the DAUD message. + + + + 1 65535 + + 5 + + + + + Number of attempts to send the SCTP_ASSOCIATE_REQ message. + + + + 0 65535 + + 4 + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of received CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of times the timer T21 was started (i.e. adjacent SP restarted). + + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + The number of successful abortions of signalling associations. + + + + + 0 + + + + + The number of succesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of unsuccessful abortions of signalling associations. + + + + + 0 + + + + + The number of unsuccesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of incoming request for association establishment when state on the association is 'DOWN' and establishment of associations is blocked. + + + + + 0 + + + + + The number of times that the max limit for trying to establish an association has been reached. + + + + + 0 + + + + + The number of times that the max limit for trying to activate an association has been reached. + + + + + 0 + + + + + The number of messages with low priority that has been discarded. + + + + + 0 + + + + + + + Mtp3b Signalling Point for the TTC standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the TTC standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpTtc MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a +standard which is NOT the TTC standard. + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + + + + + + + + + + User label for free use. + + + "" + + + + + The networkInd attribute (NI) is used by signalling message handling functions in MTP3b. + + + + + + + + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 16)-1 (65535). +The SignallingPointCode (SPC) is always used as a whole unique number (no internal structure). + + + + + + + 1 65535 + + + + + + The nodeBehaviour attribute represents the MTP3b node type. + +Note! Only SEP and STP is supported for the Ttc standard. + + + + + + SEP + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 0 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +String length 4 characters. Allowed characters are 0-9, A-F. + + + + + + 4 4 + + "7711" + + + + + Struct containing the TTC priority attributes. + + + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + Struct containing TTC timer attributes. + + + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of received CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + + + This MO represents an MTP3b Signalling Link for the ANSI standard. It represents the termination of the signalling link within the signalling point as defined in T1.111-1996. + +The total amount of links between any two specific nodes in the network shall not be more than 80 independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. A maximum of five linksets with a maximum of 16 links in each linkset can be configured. A maximum of 16 links between two adjacent nodes can be configured. + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ANSI standard. + +The performance monitoring counters found in Mtp3SlAnsi MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + + + + + + + + + + User label for free use. + + + "" + + + + + This attribute reflects the operational status of the Mtp3bSlAnsi. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The tpId attribute points out the termination point of the lower layer protocol. + +For narrowband this signalling link will be connected to an MTP L2 termination point (Mtp2Tp MO). And for broadband it will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + The link state of the Mtp3bSlAnsi. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + The signalling link code, SLC, used for this link. +The signLinkCode for a link must be unique between the nodes, +independent on in which linkSet the link belongs. + + + + + + + 0 15 + + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + + NOT_INITIALIZED + + + + + The congestion level of the link. + + + + + + level_0 + + + + + Controls if the Mtp3bSL should be activated at create. + + + + + true + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + +Note! This counter is incremented every time a link out of service indication is received for the link. + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + This action deactivates the signalling link. + It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + This action activates the signalling link with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + This action activates the signalling link with emergency alignment. + It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + This action inhibits the Mtp3bSlAnsi. Signalling link management inhibiting is requested by management when it becomes necessary, e.g for maintenance or testing purposes to make or keep a signalling link unavailable to User Part-generated signalling traffic. +Inhibiting of a signalling link may be requested by management function at either end of the link. The request is granted, provided that the inhibiting action does not cause any previously accessible destinations to become inaccessible at either end of the signalling link. The request may also be refused under certain circumstances such as congestion. +Exception FroRequestFailed if it was not possible to inhibit. + +Note! This action requires a transaction. + + + + + + + + This action uninhibits the Mtp3bSlAnsi. + +Exception FrorequestFailed if it was not possible to uninhibit. + +Note! This action requires a transaction. + + + + + + + + + + This MO represents an MTP3b Signalling Link for the ITU standard. It represents the termination of the signalling link within the signalling point as defined in Q.704 and Q.2210 (07/96). + +The total amount of links between any two specific nodes in the network shall not be more than 16, independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. + +The performance monitoring counters found in Mtp3SlItu MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the ITU standard. + + User label for free use. + + + "" + + + + + The tpId attribute points out the termination point of the lower layer protocol. + +For narrowband this signalling link will be connected to an MTP L2 termination point (Mtp2Tp MO). And for broadband it will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + This attribute reflects the operational status of the Mtp3bSl. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The link state of the Mtp3bSl. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + The signalling link code, SLC, used for this link. +The signLinkCode for a link must be unique between the nodes, +independent on in which linkSet the link belongs. + + + + + + + 0 15 + + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + + NOT_INITIALIZED + + + + + The congestion level of the link. + + + + + + level_0 + + + + + Controls if the Mtp3b Signalling Link should be activated at create. + + + + + true + + + + + This Boolean tells if the message priority shall be inserted in an octet before the Service Indicator Octet (SIO). + +ITU default is false. + + + + false + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + +Note! This counter is incremented every time a link out of service indication is received for the link. + + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + + + + + + + + + This action inhibits the Mtp3bSlItu. Signalling link management inhibiting is requested by management when it becomes necessary, e.g for maintenance or testing purposes to make or keep a signalling link unavailable to User Part-generated signalling traffic. +Inhibiting of a signalling link may be requested by management function at either end of the link. The request is granted, provided that the inhibiting action does not cause any previously accessible destinations to become inaccessible at either end of the signalling link. The request may also be refused under certain circumstances such as congestion. +Exception FroRequestFailed if it was not possible to inhibit. + +Note! This action requires a transaction. + + + + + + + + This action uninhibits the Mtp3bSlItu. + +Exception FrorequestFailed if it was not possible to uninhibit. + +Note! This action requires a transaction. + + + + + + + This action deactivates the Mtp3bSl. +It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + This action activates the Mtp3bSl with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + This action activates the Mtp3bSl with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + + + This MO represents an MTP3b Signalling Link for the TTC standard. It represents the termination of the signalling link within the signalling point as defined in JT-Q.704 Ver. 3, April 28 1992 and JT-Q.2210 Ver.1 April 24 1996. + +The total amount of links between any two specific nodes in the network shall not be more than 16, independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. + +The performance monitoring counters found in Mtp3SlTtc MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the TTC standard. + + User label for free use. + + + "" + + + + + The tpId attribute points out the termination point of the lower layer protocol. Only BroadBand is supported for TTC. The MO will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + This attribute reflects the operational status of the Mtp3bSl. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The link state of the Mtp3bSl. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + The signalling link code, SLC, used for this link. +The code have to be uniqe in this signal link set, i.e the signallingLinkCode for +all the Mtp3bSl that belongs to the same Mtp3bSls must be unique(mutual exclusive). + + + + + + + 0 15 + + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + + NOT_INITIALIZED + + + + + The congestion level of the link. + + + + + + level_0 + + + + + Controls if the Mtp3b Signalling Link should be activated at create. + + + + + true + + + + + This Boolean tells if the message priority shall be inserted in an octet before the Service Indicator Octet (SIO). + + + + + true + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + + + + + + + + + This action deactivates the Mtp3bSl. +It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + + + This action activates the signalling link with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + + + This action activates the signalling link with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + + + + + The MTP 2 Profile MO represents and keeps attribute values used by one or more MTP 2 ANSI termination point MOs. + + This MOs user label. + + + "" + + + + + + + + + + + + + Struct containing profile data. + + + + + + + + List of Mtp2TpAnsi MOs that have reserved this Mtp2TpProfileAnsi MO. + + + + + + + + + + + + The MTP 2 Profile MO represents and keeps attribute values used by one or more MTP 2 ITU termination point MOs. + + The MOs user label. + + + "" + + + + + + + + + + + + + Struct containing profile data. + + + + + + + + List of Mtp2TpItu MOs that have reserved this Mtp2TpProfileItu MO. + + + + + + + + + + + + This MO represents a channelised E1 interface in the node. The E1Ttp (Trail Termination Point) MO +does not define which type of traffic (TDM or ATM) that the interface should support. Please refer to +the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +The performance monitoring counters in the E1Ttp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! This MO is automatically created as a consequence of creating an Os155SpiTtpMo +Please refer to the Os155SpiTtpMo for more details. + + + + + The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + + + + + 0 100 + + 30 + + + + + How many bad seconds in a row that causes a Degraded Signal alarm. + + + + + + + 2 10 + + 7 + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates what Cyclical Redundancy Check 4 Mode that is being used. + + + AUTOMATIC + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + The operational state. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter of Errored Seconds (ES). + + + + + + 0 + + + + + Performance monitoring counter for Severely Errored Seconds. + + + + + + 0 + + + + + User label for free use. + + + "" + + + + + + + + + + + + + The identityof the reserving MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO is automatically created as a consequence of creating an Os155SpiTtp object if any of the following conditions are true: +a) standardmode = ETSI or +b) standardmode = TTC and muxmode = VC4_STS3CSPE_LEVEL. + +It represents the termination of the SDH VC-4 path layer. The VC-4 can either be used for channelised access, in which case VC-12 MOs are created as children to the Vc4Ttp MO, or be used to carry ATM traffic, in which case there is a relationship between the AtmPort MO and the Vc4Ttp MO. + +Note! The performance monitoring counters in the Vc4TtpMO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + Indicates the format of the expectedPathtrace and transmittedPathtrace attributes. The format may be in 16 or 64 characters. Usually 16 is used for ETSI and 64 for ANSI/TTC. + +ITU_T_G707=16 +GR_253_CORE=64 + +Note that the 16 characters format requires the operator to specify 15 characters where no character contains the null character (the 16th character is added automatically). + +Note that the 64 characters format requires the operator to specify 62 ASCII characters all different from null followed by CR/LF. + + + ITU_T_G707 + + + + + The transmitted path trace. +Can be defined in two formats. The format may be in 16 or 64 characters. Usually 16 is used for ETSI and 64 for ANSI/TTC. + +Note: The string must be of 15 or 62 characters length, or empty string (""). + + + + + + 0 64 + + "" + + + + + Expected path trace. + +The string can be of 15 or 62 characters length, or empty string (""). + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. This attribute is set to empty string every time attribute pathTraceFormat is set. + + + + + + 0 64 + + "" + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + This threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +The attribute value is in unit of % (percent). + + + + 0 100 + + 30 + + + + + Indicates how many bad seconds in a row that causes a Degraded Signal alarm. + + + + 2 10 + + 7 + + + + + AU AIS reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + VC RDI reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + The operational state. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for Virtual Container 4, VC4, Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Virtual Container 4, VC4, Severely Errored Seconds, SES. + + + + + + 0 + + + + + User label for free use. + + + "" + + + + + + + + + + + + + The identity of the reserving MO. + + + + + + + + + + This MO represents the physical interface and the termination of the SDH Regenerator and Multiplexer Section Layers. + +When creating the Os155SpiTtp a number of additional objects will be created. Depending on the values of standardmode and muxmode different objects will be created as described below: + +muxmode = standby +standardmode = ETSI, TTC, ANSI +No objects under the Os155SpiTtp is created. + +muxmode = VC4_STS3CSPE_LEVEL +standardmode = ETSI, TTC +A Vc4 MO is created under the Os155SpiTtp MO. + +muxmode = VC4_STS3CSPE_LEVEL +standardmode = ANSI +A Sts3CspeTtp MO is created under the Os155SpiTtp MO. + +The following two configurations is only applicable for the ET-MC41 board. + +muxmode = E1_J1_T1_LEVEL +standardmode = ETSI +A Vc4 MO, 63 Vc12Ttp MO's and 63 E1Ttp MO's is created under the Os155SpiTtp MO + +muxmode = E1_J1_T1_LEVEL +standardmode = ANSI +3 Sts1CspeTtp MO's, 3*28 Vt15Ttp MO's and 3*28 TiTtp MO's is created under the Os155SpiTtp MO. + +The performance monitoring counters in the Os155SpiTtp MO is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! If the Os155SpiTtp is configured as part of an Mspg protection group and is configured as standby, muxMode set to standby, no children's to this MO will be created. + + + + + + + + + + The actual line number. + + + + + + + + 1 2 + + + + + + The standard that this MO is operating to. + + + + + + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The level at which the STM-1/OC3 signal is demultiplexed. + +If parent is of type Etmc41, the valid muxMode is STANDBY or E1_J1_T1_LEVEL. +If parent is of type Etm4, the valid muxMode is STANDBY or VC4_STS3CSPE_LEVEL. + + + + + + + + + + MS - multiplexer section. + +The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + +Note: When operating to the ANSI standard, this attribute has no meaning. + + + + + 0 100 + + 30 + + + + + MS - multiplexer section. + +How many bad seconds in a row that causes a Degraded Signal alarm. + +Note: When operating to the ANSI standard, this attribute has no meaning. + + + + 2 10 + + 7 + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Enables or disables line loopback, i.e. the received signal is returned in the transmitted direction. + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + NONE + + + + + The administrative state. + + + locked + + + + + The operational state. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for Multiplexer Section, MS, Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Multiplexer Section, MS, Severely Errored Seconds, SES. + + + + + + 0 + + + + + List of reserving MOs. + + + + + + + + + + User label for free use. + + + "" + + + + + The identity of the reserving Synchronization MO. + + + + + + + + + + This MO is automatically created when the configuring the Os155SpiTtp. It represents the termination of the SDH VC-12 path layer. + +Note: This MO is only valid when the ETSI standard is in use. + +The performance monitoring counters in the Vc12TtpMO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + The transmitted path trace. + +Note: when 16 byte tracing is used, only 15 bytes should be used in the set action for this attribute. + + + + + + + 0 64 + + "" + + + + + Expected path trace. + +Note: when 16 byte tracing is used, only 15 bytes should be used in the set action for this attribute. + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. + + + + + 0 64 + + "" + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + This threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +The attribute value is in unit of % (percent). + + + + 0 100 + + 30 + + + + + Indicates how many bad seconds in a row that causes a Degraded Signal alarm. + + + + 2 10 + + 7 + + + + + Timing Unit Alarm Indication Signal (TU AIS) reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + VC RDI reporting. + +True - enable reporting. +False - disable reporting. + + + false + + + + + The administrative state. + + + locked + + + + + The operational state. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter for Virtual Container 12, VC12, Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Virtual Container 12, VC12, Severely Errored Seconds, SES. + + + + + + 0 + + + + + User label for free use. + + + "" + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + + + This MO represents the hardware of the ET-MC1 board type. It only represents the ET specific hardware, the DBM module of the board is represented by the PlugInUnit MO. + +The ET-MC1 board contains 8 phyiscal ports that can be configured as either E1 (ETSI), J1 (TTC) or T1(ANSI). The board does not allow for a mix of E1, J1 and T1 ports, thus all configured ports on the board must be configured to the same standard. + +Each port on the ET-MC1 board can be used to carry either ATM traffic or circuit orientated (Nx64 Kbits/s connections) traffic. + +Each port can support up to 30 ATM VC connections. Two of these connections are reserved for AAL2 paths, and therefore two AAL2 multiplexers per port are available. + +Each port can support up to 2 VP connections. + +The ET-MC1 port supports one bidirectional F4/F5 PM flow per port. + +At the VP/VC endpoints, the Lost FPM/BR cells counters are not available. + +Note! The ETMC1 supports IMA. + +For more details on restrictions please refer to 155 17-21/CSX 101 09 Uen. + +Note! When the Etmc1 is part of the Cbu it is only possible to configure 4 physical ports of type E1, J1 or T1 on the Etmc1 board. + + User label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the ETMC1 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + This MO represents the hardware of the ET-MC41 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-MC41 board contains a 155 Mbits/s physical optical port. The board can be configured as a E1 channelised board providing 63 logical E1 interfaces. + +Each E1 logical channel on the ET-MC41 can be used to carry either ATM traffic or circuit oriented (Nx64 kbit/s) traffic. + +Each E1 logical channel can support up to 30 ATM VC connections. Two of these connections are reserved for aal2 paths, and therefore two AAL2 multiplexers per E1/DS1/J1 channel are available. + +Each E1/DS1/J1 channel can suport up to 2 VP connections. + +The ET-MC41 board support one biderectional F4/F5 PM flow per E1 channel. + +Note! The ETMC41 supports IMA. However the E1 ports being part of the same IMA group can not be selected randomly. + +Note! The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 1 / port + +For more details on restrictions please refer to 155 17-21/CSX 101 09 Uen. + + User label for free use. + + + "" + + + + + Enabled or disabled according to the actual operational state of the ET-MC41 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + The MTP2 Profile MO represents and keeps attribute values used by one or more MTP2 China termination point MOs. + + + + + + + + + + + + + + + + + List of Mtp2TpChina MOs that have reserved this Mtp2TpProfileChina MO. + + + + + + + + + + The MOs user label. + + + "" + + + + + + + This MO represents a MTP 2 termination point for the China standard, as defined in GF001-9001, plus supplement 1-3. + +The performance monitoring counters found in Mtp2China MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a hardware fault, aal1 server/adm restart or node restart. + +NOTE: This MO cannot in anyway be related (either contained by or dependent on) an MO that belongs to a standard +which is NOT the China standard. + +NOTE: There is a restriction of a maximum of 32 Mtp2Tp's per MP. + + + + The Ds0Bundle MO that this MO references. + + + + + + + + + Reference to a Mtp2ProfileChina MO. + +Note: The bitRate can not be changed. + + + + + + + + + + + + + + + + The operational state of the MTP2 Signalling Terminal. + + + + + + disabled + + + + + Total time in local SIB (Sending). + + + + + + 0 + + + + + Number of MSUs transmitted. + + + + + + 0 + + + + + Number of negative acknowledgements received. + + + + + + 0 + + + + + Number of signal units received in error. + + + + + + 0 + + + + + Number of re-transmitted octets. + + + + + + 0 + + + + + Number of octets in send buffer. + + + + + + 0 + + + + + Number of SIO and SIF octets received. + + + + + + 0 + + + + + Number of SIO & SIF octets transmitted. + + + + + + 0 + + + + + Number of started local RB congestions. + + + + + + 0 + + + + + Total time in remote SIB (Receiving). + + + + + + 0 + + + + + List of reserving MO. + + + + + + + + Free tag for marking this managed object. + + + "" + + + + + The PlugInUnit MO that this MO references. +It indicates on which processor the Termination Point will be. + +Note: The PlugInUnit must be of type GPB. + + + + + + + + + Number of MSUs received.. + + + + + + 0 + + + + + + + This MO represents an MTP3b Signalling Link for the China standard. It represents the termination of the signalling link within the signalling point as defined in GF001-9001, plus supplement 1-3. + +The total amount of links between any two specific nodes in the network shall not be more than 16, independent on how many linksets that are defined between the two nodes. The signalLinkCode for a link must be unique between the nodes, independent on which linkSet the link belongs to. + +The performance monitoring counters found in Mtp3SlChina MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard that is NOT the China standard. + + + + + + + + + + User label for free use. + + + "" + + + + + This attribute reflects the operational status of the Mtp3bSl. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Controls if the Mtp3b Signalling Link should be activated at create. + + + + + true + + + + + The congestion level of the link. + + + + + + level_0 + + + + + The link state of the Mtp3bSl. + +The link state is a bit map which contains a combination of the following values: (in hexadecimal format) + +0x00 Available +0x01 Failed +0x02 Remotely blocked +0x04 Locally blocked +0x08 Remotely inhibited +0x10 Locally inhibited +0x20 Deactivated + + + + + + 1 + + + + + This Boolean tells if the message priority shall be inserted in an octet before the Service Indicator Octet (SIO). + +China default is false. + + + false + + + + + The procedural state of the link. + +0 - not initialized +1 - initialized + + + + + + + NOT_INITIALIZED + + + + + The signalling link code, SLC, used for this link. +The signLinkCode for a link must be unique between the nodes, +independent on in which linkSet the link belongs. + + + + + + + 0 15 + + + + + + The tpId attribute points out the termination point of the lower layer protocol. + +For narrowband this signalling link will be connected to an MTP L2 termination point (Mtp2Tp MO). And for broadband it will be connected to a NNI SAAL termination point (NniSaalTp Mo). + + + + + + + + + There are three possible states for the usageState attribute: + +- idle, the Mtp3bSl carries no traffic. +- active, the Mtp3bSl is working normally, and there is traffic, and it is not congested. +- busy, the Mtp3bSl is working but is congested (traffic is routed on other links). + + + + + + + + IDLE + + + + + Performance management counter for number of received link-in-service indications. + + + + + + + 0 + + + + + Performance management counter for number of received link-out-of-service indications. + +Note! This counter is incremented every time a link out of service indication is received for the link. + + + + + + + 0 + + + + + Performance management counter for number of sent CBD messages. + + + + + + + 0 + + + + + Performance management counter for number of sent change over order (COO/XCO) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion ceased primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of local link congestion primitives received. + + + + + + + 0 + + + + + Performance monitoring counter for number of received MSU's on this signalling link. + + + + + + 0 + + + + + Performance monitoring counter for number of sent MSU's on this signalling link. + + + + + + + 0 + + + + + This action activates the Mtp3bSl with normal alignment. It will also set autoStartLink = true. + +Note! This action requires a transaction. + + + + + + This action deactivates the Mtp3bSl. +It will also set autoStartLink = false. + +Note! This action requires a transaction. + + + + + + This action activates the Mtp3bSl with emergency alignment. +It will also set autoStartLink = true + +Note! This action requires a transaction. + + + + + + This action inhibits the Mtp3bSlChina. Signalling link management inhibiting is requested by management when it becomes necessary, e.g for maintenance or testing purposes to make or keep a signalling link unavailable to User Part-generated signalling traffic. +Inhibiting of a signalling link may be requested by management function at either end of the link. The request is granted, provided that the inhibiting action does not cause any previously accessible destinations to become inaccessible at either end of the signalling link. The request may also be refused under certain circumstances such as congestion. +Exception FroRequestFailed if it was not possible to inhibit. + +Note! This action requires a transaction. + + + + + + + + This action uninhibits the Mtp3bSlItu. + +Exception FrorequestFailed if it was not possible to uninhibit. + +Note! This action requires a transaction. + + + + + + + + + Mtp3b Signalling Point for the China standard. + +This MO represents/models the MTP3b Signaling Point characteristics/functions according to the China standard. +A signaling point is a logical node in the signaling network. The combination of signaling points and their interconnecting +signaling links form the SS No. 7 signaling network. The signaling point represented by this object is a Local Signaling Point. + +The performance monitoring counters found in Mtp3SpChina MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is shutdown request from CLI (Cluster Interface). + +NOTE: IT IS NOT POSSIBLE TO CREATE SIGNALLING POINTS OF DIFFERENT STANDARDS! + +NOTE: This MO cannot in anyway be related (either contain or by dependence) to an MO that belongs to a standard which is NOT the China standard. + +NOTE: The combination of network indicator (networkInd) and Signalling Point Code (signallingPointCode) has to be unique for each Signalling Point. + +NOTE: A maximum of 15 instances of this MO can be created on (referencing) the same PlugInUnit. + +NOTE: The maximum number of Signalling Points that can be created in a CPP based node is 24. + +NOTE: Deleting a singel L3 Signal Point is not possible, if it necessary to delete a Signal Point then all Signal Points has to be deleted. This also has to be done whitin the same transaction. + +NOTE: Any object created under a certain SP (Signaling Point) cannot refer to an object created under another SP. Nor can it refer to an object created under another SP. + + + + + + + + + + The maxSizeChangeBuf attribute represents the maximum size (in kB) of the changeover buffer. + + + + 0 5000 + + 2000 + + + + + The maxSizeReroutBuf attribute represents the maximum size (in kB) of the rerouting buffer. + + + + 0 5000 + + 2000 + + + + + The network indicator, NI, is used for discrimination of messages between functionally different networks. + + + + + + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The operationalState attribute reflects the operational status of the MTP3b SP. + + + + + + disabled + + + + + Holds a list of the reserving MO's. Can be of type SccpSp. + + + + + + + + + + The sendSltmBefLink attribute determines if the SLTM (Signalling Link Test Message) should be sent and a SLTA received before the link is considered to be in service. + +Note! It is not recommended nor is it in accordance with standard to set the value of this attribute to 'false' + + + true + + + + + The signallingPointCode (Local Point Code) attribute (SPC) is used together with the network indicator (NI, networkInd attribute) to uniquely identify the MTP Signalling Point, SP. +SP = NI-SPC. +Size (2 exp 24)-1 (16777215). +The SignallingPointCode (SPC) is nornally used as a whole unique number (no internal structure). But sometimes the SPC is grouped together as three numbers which corresponds to zone, area/network, signalling point. If this is the case the three numbers are coded as 8-8-8 bits in the total SPC. To enter the SPC-value then you have to convert the three numbers to their binary code and then convert the whole 24-bit pattern as an integer. + + + + + + + + 1 16777215 + + + + + + The nodeBehaviour attribute represents the MTP3b node type. + + + + + + SEP + + + + + Defines the number of congestion levels for NI. + + + + 1 3 + + 1 + + + + + Selection of which procedure to use during congestion handling if the national option with priorities is used. + +0, use TcTimer as described by the TTC standard. +1, use Route Set Congestion Test as described by the ANSI, ITU and China Standard. + + + + 0 1 + + 1 + + + + + Send TFC back to originating signalling point code for every n:th message when +the destination is congested. Set to 0 will suppress sending of TFC. + + + + 0 255 + + 8 + + + + + The sioSpare attribute determines if the two spare bits in the SIO (Service Information Octet) should be treated as spare. + + + SPARE + + + + + Struct containing the priority attributes. + +Note: The China and ITU priorityData is identical so the ItuPriorityData is used for China to avoid duplication of data. + + + + + + Struct containing China specific timer attributes + + + + + + The statusIndInterval attribute sets the interval for sending MTP-STATUS indication, i.e. send indication every Nth message . + + + + 0 255 + + 4 + + + + + The testPatternSltm attribute represents a string testpattern in the Signalling Link Test Message. + +Minimum string length 2 characters, maximum 30 characters. Allowed characters are 0-9, A-F. +Only even number of characters is allowed. + + + + + + 2 30 + + "A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5" + + + + + Determines if a TransFer Restricted signal (TFR) should be treated as a TFA (TransFer Allowed signal) or be ignored. + + + + IGNORED + + + + + Holds a reference to the Reliable Program Uniter. +The RPU is at the server. + + + + + + + + + User label for free use. + + + "" + + + + + For M3UA, number of attempts to send the DAUD message. + + + + 1 65535 + + 5 + + + + + Number of attempts to send the SCTP_ASSOCIATE_REQ message. + + + + 0 65535 + + 4 + + + + + This attribute shows what MTP3b ITU standard the system follows. With ITU, it is possible using this attribute to set which of the ITU standard versions that shall be followed. + +Note! Setting of another value than 'ITU_T_07_96' at create will have no effect. The Signaling Point will always be created with the value 'ITU_T_07_96'. + +Note! It is not possible to hav signaling points with different versions in the node so setting of this attribute will effect all signaling points. The value for the last created or changed signaling point will be used for all signaling points. + + + + + ITU_T_07_96 + + + + + Performance management counter for number of received CBA messages. + + + + + + 0 + + + + + Performance management counter for number of sent CBA messages. + + + + + + + 0 + + + + + Performance management counter for number of received change Back Declarations (CBD) messages. + + + + + + 0 + + + + + Performance counter for number of changeOver order messages (COO/XCO) received. + + + + + + 0 + + + + + Performance management counter for number of received COA/XCA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent COA/XCA messages. + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed controlled rerouting. + + + + + + + 0 + + + + + Performance management counter for number of sent ECA messages. + + + + + + 0 + + + + + Performance management counter for number of received ECA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent ECO messages. + + + + + + 0 + + + + + Performance management counter for number of received emergency changeOver orders (ECO) messages. + + + + + + + 0 + + + + + Performance monitoring counter for number of successfully performed forced rerouting. + + + + + + + 0 + + + + + Performance management counter for number of SLTA first time out received. + + + + + + + 0 + + + + + Performance management counter for number of SLTA second time out received. + + + + + + 0 + + + + + Performance monitoring counter for number of times the timer T21 was started (i.e. adjacent SP restarted). + + + + + + + 0 + + + + + Performance management counter for number of received TRA messages. + + + + + + + 0 + + + + + Performance management counter for number of sent TRA messages. + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed controlled reroutings. + + + + + + 0 + + + + + Performance monitoring counter for number of unsuccessfully performed forced reroutings. + + + + + + 0 + + + + + Performance monitoring counter for number of UP (user part) messages (MTP_TRANSFER_req) discarded due to routing error. + + + + + + + 0 + + + + + Performance management counter for number of successful association establishment. + + + + + + 0 + + + + + Performance management counter for number of unsuccessful association establishment. + + + + + + 0 + + + + + Performance management counter for number of SCTP communication error. + + + + + + 0 + + + + + Performance management counter for number of SCTP send failure. + + + + + + 0 + + + + + Performance management counter for number of SCTP stop sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP resume sending data. + + + + + + 0 + + + + + Performance management counter for number of SCTP network status change. + + + + + + 0 + + + + + Performance management counter for number of SCTP association restart. + + + + + + 0 + + + + + The number of successful abortions of signalling associations. + + + + + 0 + + + + + The number of succesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of unsuccessful abortions of signalling associations. + + + + + 0 + + + + + The number of unsuccesful shutdowns of signalling associations. + + + + + 0 + + + + + The number of incoming request for association establishment when state on the association is 'DOWN' and establishment of associations is blocked. + + + + + 0 + + + + + The number of times that the max limit for trying to establish an association has been reached. + + + + + 0 + + + + + The number of times that the max limit for trying to activate an association has been reached. + + + + + 0 + + + + + The number of messages with low priority that has been discarded. + + + + + 0 + + + + + + + The MSPG (Multiplex Section Protection Group) object enables two different protection mechanism in Cello. First it enables a standard 1+1 MSP mechanism. A failure on the working line will thus cause a sub 50 ms switch to the standby line. +Secondly the MSPG is used to enable equipment protection, whereas a failure of the working board will cause a switch to the standby board. While executing an equipment protection switch, the node on the other end of the multiplexer section, will experience a standard 1+1 MSP switch. + +It is possible to force traffic to one port/board by using administrative state. +Setting administrative state to locked on the working board, will automatically cause an equipment switch to the standby board. Similarily setting administrative state to locked on the working port, will cause an MSP switch to the standby port. + +The process of configuring a MSP protection interface is as follows: +1) Create the working interface as normal. +2) Create the standby interface by creating an Os155SpiTtp with mux mode set to STANDBY (standby for protection). +3) Create a MSPG object with references to the two Os155SpiTtp objects. + +Note! The ports selected for MSPG must be have the attribute standardMode configured in exactly the same way. + +Note! The Os155SpiTtp created for standby will not create any children, i.e no Vc4Ttp or Vc4Ttp, Vc12Ttp and E1Ttp will be created. Nor will object of type Sts1SpeTtp, Vt15Ttp or T1Ttp be created. + + The working OS155 pyhiscal path termination. +This is the administrative value. + +To retrive the Id of the current working port, use the selectedPort. + + + + + + + + + The standby OS155 physical path termination. +This is the administrative value. + + + + + + + + + The switching mode. + + + + + AUTOMATIC + + + + + The operational state of the Mspg. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + User label for free use. + + + "" + + + + + + + + + + + + + The port currently selected by the MSPG. The selected port can only +change due to a MSP or equipment switch. + + + + + + + + The board currently providing the user traffic interface to the Cello switch. +The only action that can change the selected board is an equipment switch. + + + + + + + + If set to true, then a swith is performed upon detection of DEG. + + + false + + + + + Initiates a switch when there does not exist a defect. + +This action can fail for the following reasons: +FailedResource - the switch was not possible due to a traffic affecting fault on the port to which the switch was requested (i.e. the one not currently selected). +LockedResource - the port to which the switch is intended is administratively locked. +UnknownReason - there exists another fault that prevents the action. + +Note! This action requires a transaction. + + + + + + + + + + + This MO represents an T1 (i.e. 1.5 Mbit/s) physical interface in the node. The T1PhysPathTerm MO does not define which type of traffic (TDM or ATM) that the interface should support. +Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + + + + User label for free use. + + + "" + + + + + + + + + + + + + The actual Line number on the board. + + + + + + + + 1 8 + + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + The administrative state. + + + locked + + + + + Performance monitoring counter for Errored Seconds, ES. + + + + + + 0 + + + + + Performance monitoring counter for Severly Errored Seconds, SES. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + Enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The idle pattern. + +NOTE: Going from A_LAW or U_LAW to UNDEFINED is always allowed but setting up one ET board with +both U_LAW and A_LAW is not allowed. +E.g. If you want to change from A_LAW to U_LAW on one ET board you have to change idlePattern +on each physical port belonging to the board to UNDEFINED first. +A_LAW -> UNDEFINED -> U_LAW or U_LAW -> UNDEFINED -> A_LAW + + + UNDEFINED + + + + + The type of transmission media. +Refer to the TransmissionMode enumeration for details. + + + + + S_133 + + + + + The identity of the reserving Synchronization MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + IMA, Inverse Multiplexing for ATM, makes it possible to group several physical +interfaces together to form a virtual physical pipe for atm. The capacity of this +pipe is equal to the sum of each of the physical interfaces included in the +group. + +When IMA should be configured, an ATMPort MO is created with reference to an +IMAGroup MO rather than a pure physical interface MO. +The IMAGroup MO in turn is created with a list of the physical port MO's that +are included in the group. The physical port MO's must be of the same type +and be located on the same ET board. + +For each of the physical port MO's included in the IMAGroup, an IMALink object +is automatically created. The IMALink object is responsible for handling link +specific performance and fault management related to IMA. + +The ports can be of type E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp, T1Ttp. + +The performance monitoring counters in the ImaGroup MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! A general restriction in Cello is that ports being part of the same IMA group +must be located on the same board. + +Note! Only termination points on Etmc1 and Etmc41 boards are allowed as ImaLinks. + +Note! At least two links has to be configured in an Ima Group. + + The identity of the MO. + + + + + + + + + Label free for use. + + + "" + + + + + Holds a list of the physical ports connected to the ImaGroup. +Can be of type: +E1PhysPathTerm, +J1PhysPathTerm, +T1PhysPathTerm, +E1Ttp, +T1Ttp. + + + + + + + + + + The required number of links specifies the number of IMALinks that needs to be +operational in order for the complete group to be operational. The bandwidth +available for the ATMPort (and thus for creating VP/VC connections) is defined +by this number. +Setting the requiredNumberOfLinks field to K less than the number of physical +links included in the IMAGroup, will reduce the bandwidth available to the atmport +with the corresponding bandwidth but will also give the effect that K links +failures can be tolerated with virtually no traffic disturbance. + + + + 1 8 + + 1 + + + + + The number of active links in the ImaGroup. + + + + + 0 + + + + + Enabled or disabled according to the actual operational state of the ImaGroup. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This performance counter reflects the GrUasLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the GrFc attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the GrFcFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + The identity of the reserving MO. + + + + + + + + + + This MO is automatically created as a consequence of creating an IMAGroup or +adding links to an IMAGroup. +It provides IMA Link specific performance and fault management information. + +The links can be of type E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp or T1Ttp. + +The performance monitoring counters in the ImaLink MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! A general restriction in Cello is that ports being part of the same IMA group +must be located on the same board. + + Enabled or disabled according to the actual operational state of the ImaLink. +If the operationalState is disabled the ImaLink will be blocked for traffic. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + This performance counter reflects the LvLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + Label free for use. + + + "" + + + + + The identity of the MO. + + + + + + + + + This performance counter reflects the OifLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the SesLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the SesLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the UasLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the UasLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxUusLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxUusLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxUusLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxUusLmaFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxFc attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxFc attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxFcFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxFcFe attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the TxStuffLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + This performance counter reflects the RxStuffLma attribute as defined by Inverse Multiplexing for ATM(IMA) specification ver. 1.1, AF-PHY-0086.001 + + + + + + 0 + + + + + Reference to the physical port represented by this MO. +Can be of types E1PhysPathTerm, J1PhysPathTerm, T1PhysPathTerm, E1Ttp or T1Ttp. + + + + + + + + + + + This MO represents the termination of the SONET higher order paths. +This MO is automatically created when creating the OS155SPITTP with mux mode +set to VC4_STS3CSPE_LEVEL and standardMode set to ANSI. + +The performance monitoring counters in the Sts3CspeTtp MO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + User label for free use. + + + "" + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + enabled or disabled according to the actual operational state of the Sts3CspeTtp. + + + + + + disabled + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + Expected path trace. + +The string can be of 64 characters length, or empty string (""). +The string shall consist of 62 ASCII characters followed by CR/LF. +The empty string shall be coded with the first character equal to ASCII null (i.e. byte value 0) and the rest dummy or non-existing. + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. This attribute is set to empty string every time attribute pathTraceFormat is set. + + + + 0 64 + + "" + + + + + The transmitted path trace. + +The string shall consist of 62 ASCII characters followed by CR/LF. +The empty string shall be coded with the first character equal to ASCII null (i.e. byte value 0) and the rest dummy or non-existing. + + + + 0 64 + + "" + + + + + Identity of the AtmPort reserving this MO. + + + + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + + + The WebServer MO represents the WebServer in the node. + +This object is used for configuration of the WebServer paths. By connecting this object to a +SwAllocation MO that is connected to a Repertoire MO the WebServer paths will be +automatically configured during system upgrade. + +The local distinguished name of this MO is ManagedElement=1, WebServer=1. + +The WebServer MO is created automatically by the system. + + + + + + + + + + + Label free for use. + + + "" + + + + + Paths that shall be used by the WebServer separated by the delimiter character ":". + + + "" + + + + + List of reserving MOs. + + + + + + + + + + + + This MO represents the Auto Configuration feature for the IpAccessHost's in Cello. + + + + + + + + + + + + Label for free use. + + + "" + + + + + Hold a list of the identitys of the reserving IpAccessHost's. + + + + + + + + + + The network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + + + + + + + 0 32 + + + + + + The number of addresses in the range that are not used. + + + + + 0 + + + + + The total number of addresses in the range. + +Note that the first address in the range will be the same one as the one for networkAddress. + + + + + 0 + + + + + The lowest value that can be used as host IP address. If autoConfig=ON for an IpAccessHost, the operator does not explicitly have to assign an Ip Address and prefixLength to the host. This is done by the Control Plane, based on the IpAccesAutoConfig identity specified for the IpAccessHost. + + + + + + + + + The highest value that can be used as host IP address. If autoConfig=ON for an IpAccessHost, the operator does not explicitly have to assign an Ip Address and prefixLength to the host. This is done by the Control Plane, based on the IpAccesAutoConfig identity specified for the IpAccessHost. + + + + + + + + + + + This MO represents the Ip Access Host used for payload. This host type executes on a MSB board (Media Stream Board used by Media Gateway). + +Note! If autoConfig is set to ON, the Ip Addresses and the Prefixes for this MO is set by the IpAccessAutoConfig MO. + +Note! There can be a maximum of 128 host's in the node. + +Note! The references to Aal5TpVccTp MO's has to be set in pairs. + +Note! The IpAccessMsbHost must execute on the sam MP as the Aal5TpVccTp that are defined in the attributes 'aal5TpVccTpRef1' and 'aal5TpVccTpRef2'. + +Note! The 'administrativeState' has to be set to LOCKED in order to be able to delete this host. + + Label for free use. + + + "" + + + + + The operational state of the Ip Access Host. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + DEGRADED + + + + + The administrative state of the Ip Access Host. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + 10 + + + + + The identity of the DSP (Digital Signalling Processor) on a MSB board. + +Note! The value of this attribute has to be unique among the host's that execute on the same board. + + + + + + + + 1 16 + + + + + + Holds a reference to an Aal5 termination point (Aal5TpVccTp MO). + +Note! The Aal5TpVccTp references are mutually exclusive. + + + + + + + + + Holds a reference to an Aal5 termination point (Aal5TpVccTp MO). + +Note! The Aal5TpVccTp references are mutually exclusive. + + + + + + + + + This attribute specifies whether the auto configuration feature for the Ip Access Host is used or not. + + + + + OFF + + + + + The identity of the IpAccessAutoConfig MO used by this host. + +Note! This attribute can only be set if 'autoConfig' is set to 'ON'. + + + + + + + + The IpAddress. + +Note! If autoConfig = OFF this attribute is mandatory. + +Note! If the autoConfiguration is used for this IpAccessHost (autoConfig = ON) this attribute cannot be set. This attribute is then set by the 'IpAccessAutoConfig MO'. + +Note! The IpAddress has to be unique within the node. + + + + + "" + + + + + The network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + +Note! If auto configuration is used (autoConfig = ON) this attribute cannot be set, the networkPrefix is then set in the ipAccessAutoConfig MO class. + +Note! If auto configuration is not used (autoConfig = OFF) this attribute must be set. + + + + + + + 0 32 + + + + + + The link Status for Ip Address. + + + + + + disabled + + + + + The maximum transfer unit. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + + + 72 2048 + + 1024 + + + + + The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, +whenever a TTL value is not supplied by the transport layer protocol. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + 1 255 + + 50 + + + + + The total number of input datagrams received from interfaces, including those received in error. + + + + + + 0 + + + + + The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number +mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc. + + + + + + 0 + + + + + The number of input datagrams discarded because the IP address in their IP header's destination field was not a +valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of +unsupported Classes (e.g., Class E). For entities which are not IP routers and therefore do not forward datagrams, +this counter includes datagrams discarded because the destination address was not a local address. + + + + + + 0 + + + + + The number of locally-addressed datagrams received successfully but discarded because of an unknown or +unsupported protocol. + + + + + + 0 + + + + + The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which +were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while +awaiting re-assembly. + + + + + + 0 + + + + + The total number of input datagrams successfully delivered to IP user-protocols (including ICMP). + + + + + + 0 + + + + + The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for +transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams + + + + + + 0 + + + + + The number of output IP datagrams for which no problem was encountered to prevent their transmission to their +destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include +datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion. + + + + + + 0 + + + + + The total number of ICMP messages which the entity received. +Note that this counter includes all those counted by icmpInErrors + + + + + + 0 + + + + + The number of ICMP messages which the entity received but determined as having +ICMP-specific errors (bad ICMP checksums, bad length, etc.). + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages received. + + + + + + 0 + + + + + The number of ICMP Time Exceeded messages received. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages received. + + + + + + 0 + + + + + The number of ICMP Source Quench messages received. + + + + + + 0 + + + + + The number of ICMP Redirect messages received. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages received. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages received. + + + + + + 0 + + + + + The total number of ICMP messages which this entity attempted to send. +Note that this counter includes all those counted by icmpOutErrors. + + + + + + 0 + + + + + The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of +buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the +resultant datagram. In some implementations there may be no types of error which contribute to this counter's value. + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages sent. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages sent. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages sent. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages sent. + + + + + + 0 + + + + + The total number of UDP datagrams delivered to UDP users. + + + + + + 0 + + + + + The total number of received UDP datagrams for which there was no application at the destination port. + + + + + + 0 + + + + + The number of received UDP datagrams that could not be delivered for +reasons other than the lack of an application at the destination port. + + + + + + 0 + + + + + The total number of UDP datagrams sent from this entity. + + + + + + 0 + + + + + + + + + + + + + The identity of the reserving MO. + + + + + + + + Holds a reference to the PlugInUnit. + +Note that the 'plugInUnitId has to be the same as the one defined in the attribute 'processorId' found on the Aal5TpVccTpMo. + + + + + + + + + + + This MO represents the definitions of properties for a set of Aal2 quality of service classes. + + + + + + + + + + Label for free use. + + + "" + + + + + This attribute holds the values applicable for QoS Class A. + + + + + + + + This attribute holds the values applicable for QoS Class B. + + + + + + + + This attribute holds the values applicable for QoS Class C. + + + + + + + + This attribute holds the values applicable for QoS Class D. + + + + + + + + List of reserving Aal2PathVccTp MOs. + + + + + + + + + + + + This MO represents the QoS CodePoints for the different Aal2 QoS classes. + + + + + + + + + + Label free for use. + + + "" + + + + + The Code Point for Class A. + +Recommended value for Class A, 128. + + + + + + + 0 255 + + + + + + The Code Point for Class B. + +Recommended value for Class B, 129. + + + + + + + 0 255 + + + + + + The Code Point for Class C. + +Recommended value for Class C, 130. + + + + + + + 0 255 + + + + + + The Code Point for Class D. + +Recommended value for Class D, 131. + + + + + + + 0 255 + + + + + + Holds the identity of the reserving Aal2Ap Mo. + + + + + + + + + + + + This MO represents the M3UA Association part of the M3UA (MTP3-User Adaptaion Layer) that is a protocol +for the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services +of the Stream Control Transmission Protocol. + +Note that the local port number is hard coded to 2905. + + + + + + + + + + + + + Label free for use. + + + "" + + + + + Holds a list of the reserving Signaling Route's (Mtp3bSr MO). + + + + + + + + + + + The Operational State of the M3Ua + + + + + + disabled + + + + + The identity of the Signalling Route Set used. + + + + + + + + + + The SctpHost used by this association. + + + + + + + + + The DSCP, DiffServCodePoint, for the internal M3UA user. +Only one DSCP value is valid and set by the first defined MO 'instance'. + +NOTE: The value set for the 'dscp' when creating the first M3uAssociation under a signaling point will also be used for all other M3uAssociation MO's that are created under this signaling point. So setting the value for the 'dscp' on other instances than the first one created will have no effect. Note that associations created under a different signaling point can have a different dscp-value. + + + + + + 0 63 + + 0 + + + + + The possible states of an M3Ua association. + +Bit 1 = 1 indicates INACTIVE +Bit 2 = 1 indicates ACTIVE +Bit 3 = 1 indicates ESTABLISHED +Bit 4 = 1 indicates DOWN + +These values are mutually exclusive. + + + + + + 0 15 + + 0 + + + + + This attribute denotes whether single or multi homing is used. + +Note! that all M3uAssociations that refers to the same SCTP MO must have this attribute set to the same value. + +Note! If localipMask=2 or localipMask=3 . the attribute ipAddress2 or autoConfigIdentity2 in IpAccessHostGpb MO must be defined. + + + + + + SINGLE_HOMED_1 + + + + + If true, the M3ua layer in the stack will after a restart, start up all signalling associations. + + + + + true + + + + + The port number of the remote signalling point (SP). + + + + + + 1 65535 + + 2905 + + + + + Remote IpAddress 1, if not used the value should be an empty string. +Range is 0.0.0.0 - 255.255.255.255 + +Note! This address is concidered as the primary IP-address. In case of association establisment failure 'remoteIpAddress2' will be used. + + + + + + + + + Remote IpAddress 2, if not used the value should be an empty string. +Range is 0.0.0.0 - 255.255.255.255 + +Note! This address cannot be the same as remoteIpAddress1. This address is used when trying to establish association in case association attempt using 'remoteIpAddress1' fails. + + + + + "" + + + + + Number of communication losses. + + + + + + 0 + + + + + Number of congestions. + + + + + + 0 + + + + + Number of DUNA messages received through the association. + + + + + + 0 + + + + + Number of DAVA messages received through the association. + + + + + + 0 + + + + + Number of SCON messages received through the association. + + + + + + 0 + + + + + Number of DUPU messages received through the association. + + + + + + 0 + + + + + The number of data messages sent on the associations related to this signalling point. + + + + + 0 + + + + + Number of DUNA messages sent through the association. + + + + + 0 + + + + + Number of DAVA messages sent through the association. + + + + + 0 + + + + + Number of SCON messages sent through the association. + + + + + 0 + + + + + Number of DUPU messages sent through the association. + + + + + 0 + + + + + Number of DATA (payload data) messages received through the association. + + + + + 0 + + + + + Number of ERROR messages received through the association. + + + + + 0 + + + + + Number of ERROR messages sent through the association. + + + + + 0 + + + + + Number of NOTIFY messages received through the association. + + + + + 0 + + + + + The number of daud messages sent on the associations related to this signalling point. + + + + + 0 + + + + + The number of daud messages received on the associations related to this signalling point. + + + + + 0 + + + + + The number of ASPUP sent. + + + + + 0 + + + + + The number of ASPUP received. + + + + + 0 + + + + + The number of ASPDN sent. + + + + + 0 + + + + + The number of ASPDN received. + + + + + 0 + + + + + The number of ASPAC sent. + + + + + 0 + + + + + The number of ASPAC received. + + + + + 0 + + + + + The number of ASPIA sent. + + + + + 0 + + + + + The number of ASPIA received. + + + + + 0 + + + + + The number of ASPUP_Ack sent. + + + + + 0 + + + + + The number of ASPUP_Ack received. + + + + + 0 + + + + + The number of ASPDN_Ack sent. + + + + + 0 + + + + + The number of ASPDN_Ack received. + + + + + 0 + + + + + The number of ASPAC_Ack sent. + + + + + 0 + + + + + The number of ASPAC_Ack received. + + + + + 0 + + + + + The number of ASPIA_Ack sent. + + + + + 0 + + + + + The number of ASPIA_Ack received. + + + + + 0 + + + + + The number of data Messages discarded. + + + + + 0 + + + + + This action starts the association. + +Note! This action requires a transaction. + + + + + + This action stops the association. + +Note! This action requires a transaction. + + + + + + + + This MO represents the SCTP, Stream Control Transmission Protocol in Cello. +SCTP is designed to transport signaling messages over IP networks. + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the Ip Access Host. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The maximum number of M3uAssociations that can be handled by this SCTP MO. + + + + + + + 1 512 + + + + + + Holds a list of the M3Ua's handled by the SCTP. + + + + + + + + + + The identity of the IpAccessHostGbp reserved by this MO. + + + + + + + + + The minimum value for RTO (Retransmission time-out). +The minimumRto shall be larger than tSack + expected Round Trip Time. + +Unit is second/100. + + + + + 4 500 + + 8 + + + + + The maximum value for RTO (Retransmission time-out). + +Unit is second/100. + +maximumRto must be larger than minimumRto. + + + + 4 180000 + + 15 + + + + + The initial value that the RTO (Retransmission time-out) will take prior to the first RTT (Round Trip Time) measure. + +Note that the value for 'initialRto' has to be equal to or greater than 'minimumRto'. + +Unit is seconds/100. + + + + 4 180000 + + 8 + + + + + This parameter is used for computing the value of the SRTT (Smoothed Round Trip Time) for a specific destination +address. Is is used to weight the RTT values, and it's value must be between 0 and 1 (0 < rtoAlpha < 1). A value +close to 1 gives a higher importance to the last RTT measurement. +The range of possible values in the configuration file and the actual value given to this parameter within the module +are the following: + +rtoAlphaIndex = 1 -> RTO-Alpha = 1/2 +rtoAlphaIndex = 2 -> RTO-Alpha = 1/4 +rtoAlphaIndex = 3 -> RTO-Alpha = 1/8 +rtoAlphaIndex = 4 -> RTO-Alpha = 1/16 + + + + 1 4 + + 3 + + + + + This parameter is used for computing the the value of RTTVar (Round Trip Time Variation) of a destination +address. +It's value must be between 0 and 1 (0 < rtoBetaIndex < 1). A value close to 1 gives more importance to the +last observed variation. +The range of possible values in the configuration file and the actual value given to this parameter within the module +are the following: + +rtoBetaIndex = 1 -> RTO-Beta = 1/2 +rtoBetaIndex = 2 -> RTO-Beta = 1/4 +rtoBetaIndex = 3 -> RTO-Beta = 1/8 +rtoBetaIndex = 4 -> RTO-Beta = 1/16 + + + + + 1 4 + + 2 + + + + + This parameter sets up the lifespan of the State Cookie sent in the INIT_ACK chunk. It is used for limiting the +the valid amount of time between sending the INIT_ACK and the reception of a COOKIE_ECHO chunk when +establishing an association. +If a COOKIE_ECHO chunk arrives after 'validCookieLife' has expired when sending an INIT_ACK chunk, the +COOKIE_ECHO shall be discarded and no association will be established. + +Unit is seconds. + + + + 1 180 + + 60 + + + + + The sender of an INIT chunk may request to the remote endpoint a cookie life-span increase (for example, if a previous attempt to +connect failed due to a state-cookie error). If the value sent in the "Cookie Preservative field" of the INIT chunk is less or equal to +this parameter, the reciver of the INIT chunk will increase the 'validCookieLife' with the number of seconds specified. If the value +present in the "Cookie Preservative field" is higher than this parameter, the cookie life should be incremented with the number of +seconds specified by the parameter. + +Unit is seconds. + + + + 0 180 + + 30 + + + + + Defines how often the secret key used for computing the MAC (Message Authentication Code) on the State Cookie is changed. + +Unit is seconds. + + + + 1 180 + + 4 + + + + + This is the maximum number of consecutive retransmissions to a remote peer (on all the destination transport addresses of the peer, if it's multi homed). If the number of retransmissions becomes higher than this value, the remote peer shall be considered unreachable and the association shall be closed down. + +The value of this attribute should be greater than, or equal to the value of the attribute 'pathMaxRtx'. + +Note that for a specific association, it might happen that all the remote addresses (if the the remote end is multi homed) becomes unreachable without exceeding the 'associationMaxRtx'. In such a case the association will be closed down. + +Note! The value need to be increased to avoid frequent CommLost's in case of an unstable network. + + + + 1 20 + + 2 + + + + + Maximum number of consecutive retransmissions to a remote transport address. If the number of retransmissions becomes higher than this value, the remote transport address shall be considered as "inactive" and no data shall be sent to it. If all of the remote transport addresses becomes "inactive", tha association will be closed down. + +Note! The value need to be increased to avoid frequent CommLost's in case of an unstable network. + + + + 1 20 + + 2 + + + + + The maximum nimber of retransmissions allowed for both INIT and COOKIE_ECHO chunks. If the number of retransmissions +exceeds this value, then the SCTP must abort the initialization of the association and report the error to the user. + + + + 1 16 + + 8 + + + + + The maximum number of retransmission during the shutdown phase of an association. + + + + 1 16 + + 5 + + + + + The amount of time added to the RTO (Retransmission Time Out) of a specific address when setting up the period of +time between sending heartbeats. Small values can lead to an earlier detection of unreachable addresses than higher +values. Note that sendig often might lead to performace penalty. + +Unit is seconds. + + + + 1 1800 + + 30 + + + + + This attribute enables/disables heartbeats for associations. + +True = Enables + + + true + + + + + This is the maximum incoming streams (MIS) for an association. Established associations might have an IS less or equal to +this, but it's MIS can never be higher than the value of this attribute. + + + + 1 16384 + + 17 + + + + + The maximum number of outgonig streams for an association. + + + + 1 16384 + + 17 + + + + + The maximum number of bytes a user is allowed to pass as a non fragmentable user data in a SCTP_SEND_REQ message +(fixed user MTU): +The values for this attribute is 'user' data and do not include IP header (20 bytes), SCTP header (12 bytes) or DATA chunk +header (16 bytes). + +Unit is bytes. + + + + 528 65484 + + 1432 + + + + + This attribute sets the size of the buffer used for storing user data pending to be sent or retransmitted in an association. I.e. establish the maximum amount of user data that SCTP shall buffer before discarding user messages. + +The Unit is in kilo bytes. + +Note! The restriction on this attribute is: +mBuffer x number of M3uAssociation MOs connected to this Sctp + 20 Mb <= the heap for Sctp program. + +Note! The value may need to be increased to ensure stable dataflow at high load. + + + + 1 2048 + + 128 + + + + + This attribute sets the value of the threshold used by SCTP to stop the delivery of data on anassociation. +Once nThreshold or more bytes are queued and pending to be sent, the SCTP layer shall issue an indication to the user. +The value of nThreshold should be less than mBuffer in order to be effective. A normal value for nThreshold is 3/4 * mBuffer. + +Unit is kilo bytes. + +Note! The value may need to be increased to ensure stable dataflow at high load. + + + + 1 2048 + + 96 + + + + + The delay of sending the SACK. I.e. the time from DATA chunk reception to Sack chunk sending. + +Unit is second/100 + + + + 2 50 + + 4 + + + + + The maximum number of bytes SCTP shall be able to fetch every time it reads from the socket. + +Note! This value includes the Ip header, 20 bytes. + + + + 1500 65535 + + 8192 + + + + + The value of the initial advertised reciver window. + +Note! The range is 1500 to maxDataSizeIp. + +Unit is bytes. + + + + 1500 65535 + + 8192 + + + + + The number of seconds for the interval for which the counter for out of the blue chunks will be reset. + +Unit is seconds. + + + + 1 6500 + + 3600 + + + + + The number of seconds for the interval for which the SCTP will decide that the SCTP user that lost the +connection is dead. After the time specified in this attribute has elapsed, all associations related to the +SCTP user will be destroyed. + + + + 0 3600 + + 5 + + + + + The number of packages that will be sent during the fast retransmit phase when a SACK is processed. + + + + 1 16384 + + 4 + + + + + The size of 'n' inpercentage when SCTP_CONGESTION_CEASE_IND is sent. At 100 percent the +primitive will buffer usage goes below 'nThreshold'. + + + + 1 100 + + 85 + + + + + This attribute enables/disables the use of bundling. +Valid values: +1: enabled. +0: disabled. + + + + 0 1 + + 1 + + + + + This attribute specifies maximum SCTP bundling delay. +Value=0 means that SCTP will only bundle what is available and send directly (no delay). +Unit is milliseconds + + + + 0 1000 + + 10 + + + + + Number of SCTP associations for which the current state is either ESTABLISHED, SHUTDOWN-PENDING, or SHUTDOWN-RECEIVED. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the COOKIE-ECHOED state. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the CLOSED state. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the CLOSED state from any state using the primitive ABORT. + + + + + + 0 + + + + + Number of times that SCTP associations have made a direct transition to the CLOSED state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state. + + + + + + 0 + + + + + Number of out of the blue packets (SCTP packet correctly formed-right checksum- but the receiver is not able to identify the association to which this packet belongs) received by the host. + + + + + + 0 + + + + + Number of complete data chunks sent to the peers (no retransmissions included). + + + + + + 0 + + + + + Number of complete data chunks received from the peers (no retransmissions included). + + + + + + 0 + + + + + Number of unordered chunks sent to the peers. + + + + + + 0 + + + + + Number of unordered chunks received from the peers. + + + + + + 0 + + + + + Number of SCTP packets received from the peers with an invalid checksum. + + + + + + 0 + + + + + Number of data chunks retransmitted to the peers. + + + + + + 0 + + + + + Number of datagrams sent with chunk type id > 0. + + + + + + 0 + + + + + Number of datagrams Receivedwith chunk type id > 0. + + + + + + 0 + + + + + Number of fragmented user messages, incremented when the first data chunk of a fragmented message is sent. + + + + + + 0 + + + + + Number of reassembled user messages, incremented when the first data chunk of a fragmented message is received. + + + + + + 0 + + + + + Number of SCTP packages sent. + + + + + + 0 + + + + + Number of SCTP packages Received. + + + + + + 0 + + + + + Number of times the SCTP has sent a communication stop indication to the user. + + + + + + 0 + + + + + Number of times SCTP has sent a communication resume indication to the user. + + + + + + 0 + + + + + Number of sent chunks that SCTP has been forced to drop due to buffer overflow in the sending buffer. + + + + + + 0 + + + + + Number of received chunks that SCTP has been forced to drop due to buffer overflow in the receiving buffer. + + + + + + 0 + + + + + + + This MO represents the termination of the SONET higher order paths. +This MO is automatically created when creating the OS155SPITTP with mux mode +set to E1_J1_T1_LEVEL and standardmode set to ANSI. + +The performance monitoring counters in the Sts1SpeTtp MO is set to 0 (zero) at start or restart of the node. +When the value is to large to fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Label free for use. + + + "" + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + enabled or disabled according to the actual operational state of the Sts3CspeTtp. + + + + + + disabled + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Trace Identifier Mismatch (TIM) consequent action, i.e. for generation of Alarm Indication Signal (AIS) downstream and Remote Defect Indication (RDI) upstream as a consequence of the TIM detection. + +True - enabled. +False - disabled. + + + false + + + + + Expected path trace. + +The string can be of 64 characters length, or empty string (""). + +Note: An empty string for this attribute means that the detection of Trace Identifier Mismatch (TIM) should be disabled. This attribute is set to empty string every time attribute pathTraceFormat is set. + + + + 0 64 + + "" + + + + + The transmitted path trace. +Can be defined in two formats. The format may be in 16 or 64 characters. Usually 16 is used for ETSI and 64 for ANSI/TTC. + +Note: The string must be of 15 or 62 characters length, or empty string (""). + + + + 0 64 + + "" + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + + + This MO is automatically created when the configuring the Os155SpiTtp. It represents the termination of the SONET VP 1.5 path layer. + +This MO is automatically created when creating the Os155SpiTtp MO with the following conditions: +muxmode = E1_J1_T1_LEVEL +standardmode = ANSI + +The performance monitoring counters in the Vt15Ttp is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + This timer defines the time that elapses before shut down when administrativeState is se to 'shuttingDown'. + + + + 1 100000 + + 1800 + + + + + The operational state of the Vt15Ttp MO. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The administrative state of the Vt15Ttp MO. + + + locked + + + + + Performance monitoring counter of Errored Seconds (ES). + + + + + + 0 + + + + + Performance monitoring counter for Serverely Errored Seconds. + + + + + + 0 + + + + + Label free for use. + + + "" + + + + + + + This MO represents a channelised T1 interface in the node. The T1Ttp MO does not define which type of traffic (TDM or ATM) that the interface should support. Please refer to the Ds0Bundle, AtmPort, IMALink and IMAGroup objects for details about configuration of traffic type. + +The performance monitoring counters in the T1Ttp MO is set to 0 (zero) at start or restart of the node. +When the value is to large too fit in to a long (31bit) the counter turns over and starts from 0 again. + +Note! This MO is automatically created as a consequence of creating an Os155SpiTtpMo +Please refer to the Os155SpiTtpMo for more details. + + + + + + + + + + + Label free for use. + + + "" + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + The operational state of the T1Ttp MO. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Performance monitoring counter of Errored Seconds (ES). + + + + + + 0 + + + + + Performance monitoring counter for Serverely Errored Seconds. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + The identity of the reserving ImaLink MO. + + + + + + + + + + This MO represents an E3 (i.e. 34 Mbit/s) physical interface in the node. Please refer to the AtmPort object for details about configuration of traffic type. + +Note! The performance monitoring counters in the E3PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Label for free use. + + + "" + + + + + The administrative state of the E3PhysPathTerm. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The actual Line number on the board. + + + + + + + 1 2 + + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + The threshold decides how many of the received blocks that are allowed to have bit errors. The measurement is made on a per-second basis and if the threshold is passed the second is considered bad. + +This is a percentage value. + + + + 0 100 + + 30 + + + + + How many bad seconds in a row that causes a Degraded Signal alarm. + + + + 2 10 + + 7 + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Performance Monitoring counter for ES, Errored Seconds. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + The identity of the reserving Synchronization MO. + + + + + + + + + + This MO represents an T3 (i.e. 45 Mbit/s) physical interface in the node. Please refer to the AtmPort object for details about configuration of traffic type. + +Note! The performance monitoring counters in the T3PhysPathTerm MO is set to 0 (zero) at start or restart of the node. +When the value is too large too fit in to a long (31bit) the counter turns over and starts from 0 again. + + + + + + + + + + Label free for use. + + + "" + + + + + enabled or disabled according to the actual operational state of the Physical Line Termination. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + The administrative state of the T3PhysPathTerm MO. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + + 0 100000 + + 1800 + + + + + The actual Line number on the board. + + + + + + + 1 2 + + + + + + Possible values + +none - This is the normal state, no loop back is performed (and ordinary traffic is running). + +line - The physical path is looped on the line side, the external incoming path is looped back to the external outgoing path. + +system - The physical path is looped on the system side, the (node-) internal incoming path is looped back to the internal outgoing path. + +Note! administrativeStatus must be set to locked when setting loopback attribute. + + + none + + + + + Indicates whether Alarm Indication Signal, AIS, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Indicates whether Remote Defect Indication, RDI, alarms are to be issued. + +true - reporting enabled. +false - reporting disabled. + + + false + + + + + Performance Monitoring counter for ES, Errored Seconds based on C-bit parity. + + + + + + 0 + + + + + Performance Monitoring counter for Severely Errored Seconds, SES based on C-bit parity. + + + + + + 0 + + + + + The identity of the reserving AtmPort MO. + + + + + + + + The identity of the reserving Synchronization MO. + + + + + + + + + + This MO represents the hardware of the ET-M3 board type. It only represents the ET specific hardware, while the DBM module of the board is represented by the PlugInUnit MO. + +The ET-M3 board contains 2 physical ports that can be configured as either E3 (ETSI) or T3(ANSI). + +Each port on the ET-M3 board can be used to carry ATM traffic. + +At the VP/VC endpoints, the Lost FPM/BR cells counters are not available. + +IMA is not applicable for theETM3 board. + +The ET-M3 board supports eight bidirectional F4/F5 PM flow per port. + +The number of VCC TP+VPC TP with performance monitoring enabled (i.e. PM mode <> off) is restricted to 8/port. + +Each port can support up to 240 ATM VC connections. Sixteen of these connections are reserved for AAL2 paths, and therefore sixteen AAL2 multiplexers per port are available. + +Each port can support up to 16 VP connections. + + + + + + + + + + Enabled or disabled according to the actual operational state of the Etm3 board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Label for free use. + + + "" + + + + + + + This Managed Object represents an SCCP Remote Access Point. An SCCP AP instance is a logical point in the SCCP network at which an SCCP user can access the services provided by the SCCP and the SCCP can deliver its services to the SCCP user. The SCCP Remote Access Point is identified by a SubSystem Number (SSN). + +A remote SccpAp represents an access point in another node and is related to a Mtp3bAp MO. + +The performance monitoring counters found in SccpAp MO is reset, set to zero, when the object is created. +These counters will not be reset again unless there is a shutdown request from the CLI (Cluster Interface). + + + + + + + + + + Label free for use. + + + "" + + + + + The operational state of the SCCP AP. The operability of the SCCP AP is described by this attribute which has two possible values: + +Disabled: The SCCP AP is totally inoperable and unable to provide the service to the user (e.g. if the MTP-3b AP is not usable). + +Enabled: The SCCP AP is partly or fully operable and available for use. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + Holds a list of the reserving MOs. + + + + + + + + + + The identity of the Mtp3bAp used by this MO. + + + + + + + + + The sub system number, SSN, of the SCCP Access Point. Note that this has to be a unique number. + +The SSN has to be unique among all other SccpApRemote MOs that has the same DPC in their corresponding Mtp3bSrs MOs. + + + + + + + 2 255 + + + + + + + + This MO represents the Ip Access Host used for payload. This host type executes on a GPB board (GeneralPocessorUnit). + +Note! If autoConfig is set to ON, the Ip Addresses and the Prefixes for this MO is set by the IpAccessAutoConfig MO. + +Note! There can be a maximum of 128 host's in the node, and only one host on each main processor. + +Note! The host cannot be configured on a MP which have a MediumAccessUnit-child MO. They are exclusive. + +Note! The 'administrativeState' has to be set to LOCKED in order to be able to delete this host. + + + + + + + + + + Label for free use. + + + "" + + + + + The identity of the reserving MO, can be of type Sctp. + + + + + + + + The operational state of the Ip Access Host. + + + + + + disabled + + + + + The availability status. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + DEGRADED + + + + + The administrative state of the Ip Access Host. + + + locked + + + + + The shut-down timer. It is used when the administrativeState is set to shutdown. + +Value in seconds, must be a positive value. + + + 10 + + + + + The link status for IpAddress1. + + + + + + disabled + + + + + The link status for IpAddress2, only valid if 2 IpAddresses are configured for this host. + + + + + + disabled + + + + + Holds a reference to the GPU (GenerelProcessorUnit). + + + + + + + + + This attribute specifies whether the auto configuration feature for the Ip AccessHost is used or not. + + + + + OFF + + + + + The identity of the IpAccessAutoConfig MO used by this host. + +Note! This attribute is mandatory if 'autoConfig' is set to ON. + + + + + + + + The identity of the IpAccessAutoConfig MO used by this host. + +Note! This attribute can only be set if 'autoConfig' is set to 'ON'. This attribute is not neccesary to set if 'autoConfig' is set to ON, unless the host shall have two Ip Addresses automatically assigned. + + + + + + + + The IpAddress. + +Note! If autoConfig = OFF this attribute is mandatory. +Note! If the autoConfiguration is used for this IpAccessHostGpb (autoConfig = ON) this attribute cannot be set. This attribute is then set by the 'IpAccessAutoConfig MO'. +Note! If the attribute is set, its value must not be the same as for attribute ipAddress2. + + + + + "" + + + + + The second IpAddress. + +Note! If autoConfig = OFF this attribute is possible to set. This attribute should only be set if multi-homing is used for this host (i.e. two addresses defined). +Note! If the autoConfiguration is used for this IpAccessHostGpb (autoConfig = ON) this attribute cannot be set. This attribute is then set by the 'IpAccessAutoConfig MO'. +Note! If the attribute is set, its value must not be the same as for attribute 'ipAddress'. + + + + + "" + + + + + Specifies whether path MTU discovery should be used by this host. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + false + + + + + The maximum transfer unit. + +The MTU has a initial value of 1452 if pathMTUDiscovery is set to false. +If pathMTUDiscovery is set to true, the initial value of MTU is 1452. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + 72 2048 + + 1452 + + + + + The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, +whenever a TTL value is not supplied by the transport layer protocol. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + + + + 1 255 + + 50 + + + + + The maximum number of seconds which received fragments are +held while they are awaiting reassembly at this entity. + +Note! in order to be able to set the value for this attribute, the administrative state has to be locked. + +Note! The value for this attribute has to be positive. + + + 300 + + + + + The next hop IP address. + + + + + + + + + The secondary next hop IP address. + +Note! This attribute must only be set if one of the following conditions are fulfilled: +1. Attribute 'ipAddress2' is set. +2. Attribute 'autoConfig' = 'ON' and attribute 'autoConfigIdentity2' is set. + + + + + "" + + + + + The network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + +Note! The default value 0 (zero) is most likely not possible to use and an other value should be submitted if this attribute is configured manually. +Note! If auto configuration is not used (autoConfig = OFF) this attribute must be set (i.e. this attribute is then 'mandatory'). +Note! If auto configuration is used (autoConfig = ON) this attribute cannot be set, networkPrefix is then set by the ipAccessAutoConfig MO class. + + + + + + + 0 32 + + 0 + + + + + The second network prefix. + +The prefix denotes how many bits that are used for calculating the subnet mask. + +Note! The default value 0 (zero) is most likely not possible to use and an other value should be submitted if this attribute is configured manually. +Note! If auto configuration is not used (autoConfig = OFF) and ipAddress2 is set this attribute must be set (i.e. this attribute is then 'mandatory'). +Note! If auto configuration is used (autoConfig = ON) this attribute cannot be set, networkPrefix2 is then set by the ipAccessAutoConfig MO class. + + + + + + 0 32 + + 0 + + + + + The total number of input datagrams received from interfaces, including those received in error. + + + + + + 0 + + + + + The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number +mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc. + + + + + + 0 + + + + + The number of input datagrams discarded because the IP address in their IP header's destination field was not a +valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of +unsupported Classes (e.g., Class E). For entities which are not IP routers and therefore do not forward datagrams, +this counter includes datagrams discarded because the destination address was not a local address. + + + + + + 0 + + + + + The number of locally-addressed datagrams received successfully but discarded because of an unknown or +unsupported protocol. + + + + + + 0 + + + + + The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which +were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while +awaiting re-assembly. + + + + + + 0 + + + + + The total number of input datagrams successfully delivered to IP user-protocols (including ICMP). + + + + + + 0 + + + + + The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for +transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams + + + + + + 0 + + + + + The number of output IP datagrams for which no problem was encountered to prevent their transmission to their +destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include +datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion. + + + + + + 0 + + + + + The number of IP fragments received which needed to be reassembled at this entity. + + + + + + + 0 + + + + + The number of IP datagrams successfully re-assembled. + + + + + + + 0 + + + + + The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc). +Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm +in RFC 815) can lose track of the number of fragments by combining them as they are received. + + + + + + + 0 + + + + + The number of IP datagrams that have been successfully fragmented at this entity. + + + + + + + 0 + + + + + The number of IP datagrams that have been discarded because they needed to be fragmented +at this entity but could not be, e.g., because their Don't Fragment flag was set. + + + + + + + 0 + + + + + The number of IP datagram fragments that have been generated as a result of fragmentation at this entity. + + + + + + + 0 + + + + + The total number of ICMP messages which the entityreceived. +Note that this counter includes all those counted by icmpInErrors + + + + + + 0 + + + + + The number of ICMP messages which the entity received but determined as having +ICMP-specific errors (bad ICMP checksums, bad length, etc.). + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages received. + + + + + + 0 + + + + + The number of ICMP Time Exceeded messages received. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages received. + + + + + + 0 + + + + + The number of ICMP Source Quench messages received. + + + + + + 0 + + + + + The number of ICMP Redirect messages received. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages received. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages received. + + + + + + 0 + + + + + The total number of ICMP messages which this entity attempted to send. +Note that this counter includes all those counted by icmpOutErrors. + + + + + + 0 + + + + + The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of +buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the +resultant datagram. In some implementations there may be no types of error which contribute to this counter's value. + + + + + + 0 + + + + + The number of ICMP Destination Unreachable messages sent. + + + + + + 0 + + + + + The number of ICMP Parameter Problem messages sent. + + + + + + 0 + + + + + The number of ICMP Echo (request) messages sent. + + + + + + 0 + + + + + The number of ICMP Echo Reply messages sent. + + + + + + 0 + + + + + The total number of UDP datagrams delivered to UDP users. + + + + + + 0 + + + + + The total number of received UDP datagrams for which there was no application at the destination port. + + + + + + 0 + + + + + The number of received UDP datagrams that could not be delivered for +reasons other than the lack of an application at the destination port. + + + + + + 0 + + + + + The total number of UDP datagrams sent from this entity. + + + + + + 0 + + + + + Performance monitoring counter for the number of input unicast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of out unicast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to any error. + + + + + + 0 + + + + + Performance monitoring counter for the number of input packets discarded due to resource limitations. + + + + + + 0 + + + + + Performance monitoring counter for the number of input broadcast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of input multicast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of output broadcast packets delivered to higher layer. + + + + + + 0 + + + + + Performance monitoring counter for the number of output multicast packets delivered to higher layer. + + + + + + 0 + + + + + + + This MO structures the SystemFunctions of the managed element. It is created automatically and cannot be deleted. + +The local distinguished name of this MO is ManagedElement=1, SystemFunctions=1. + + + Label free for use. + + + "" + + + + + + + + + + + + + + + This MO represents the Licensing (Software Keys) functions in Cello. + + + + + + + + + + + Label free for use. + + + "" + + + + + This attribute holds information about the emergency status and the time remaining in the current state. + +Note! If the node is in emergency state USE_DEGRADED, or the emergency state is USE_DISABLED, the the value of'time' is insignificant. + + + + + + + + This attribute returns the URL to the License Key File so it can be viewed with an XML capable web browser +in case this is a licensed node. + +Note! In case the node is not licensed, an empty string will be returned. + + + + + + 0 256 + + "" + + + + + This action sends a request to the FTP/SFTP server to update the license key file. + +User Id for login to FTP/SFTP server where license key files are located. +If a null string userId is given, anonymous FTP/SFTP transfer is assumed. +Max length is 20 characters. + +Password for login to the FTP/SFTP server where license key files are located. +Max length is 20 characters. + +The IpAddress of the FTP/SFTP server where license key files are located. +Max length is 16 characters. + +Source name and path of the license key file on the FTP/SFTP server. +Max length is 256 charcters. + +Note! This action does not require a transaction. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This action sets the license server into emergency state. +I.e. opens up all licensed features and capacity restrictions. +Disabling emergency state is done by loading a new license key file. + +Note! This action does not require a transaction. + + + + + + + + This MO represents a timing unit2 (reference clock) in the node. + +The corresponding Program shall be of LoadModuleLoaderType, SpmFpgaLoader. + + Label for free use. + + + "" + + + + + Operational state of TimingUnit + + + + + + disabled + + + + + The availability status of the TimingUnit. + +The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. + + + + + + NO_STATUS + + + + + + + + + + + + + + + The SccpPolicing MO represents the policing function in CPP. + +The originatingMtp3bSpc is a madatory attribute for policing in one local node (i.e. a SRP in one NI). +For policing between two local nodes (i.e. a SRP between two NIs) the originatingMtp3bSpc can be replaced by the originatingSccpSpId. +Optional attributes for policing in one local node (i.e a SRP in one NI) are destinationMtp3bSpc, destinationSccpSsn, originatingSccpSsn and policingGlobalTitle. +For policing between two local nodes (i.e. a SRP between two NIs) the destinationMtp3bSpc can be replaced by the destinationSccpSpId. + + + + + + + + + + Label free for use. + + + "" + + + + + The value of the SPC (Signaling Point Code). + +Note! If the 'originatingSccpSpId' is specified the 'originatingMtp3bSpc' is invalid. + + + + + + + 0 16777215 + + 0 + + + + + The value of the destination SPC (Signaling Point Code). + +Note! The default value 0 (zero) means that no SPC is defined. +Note! If no 'destinationSccpSp' is defined and the value of 'destinationMtp3bSpc' is set to 0 (zero), all Signalling Point Codes (SPC) are valid. + + + + + + 0 16777215 + + 0 + + + + + The identity of the originating SccpSp MO must be used for policing between local nodes. + +Note! If the 'originatingSccpSpId' is specified the 'originatingMtp3bSpc' is invalid. + + + + + + + + + The value of SSN in CgPA (Calling Party Address) + +Note! The value 0 (zero) means that all ssN (Sub System Number) are valid. + + + + + + 0 + + + + + The identity of the destination SccpSp MO can be used for policing between local nodes. + +Note! If the 'destinationSccpSpId' is specified the 'destinationMtp3bSpc' is invalid. +Note! If no destination 'destinationSccpSp' is defined and the value of 'destinationMtp3bSpc' is set to 0, all local nodes are valid. + + + + + + + + + The value of SSN inCdPA (Called Party Address). + +Note! The valu 0 (zero) means tha all ssN (Sub System Number) are valid. + + + + + 0 + + + + + The Policing Global Title attribute allows to optionally police on Global Title + +Default value is considered as no policing Global Title and all GTs are valid. + + + + + + + + For a policing case whether to discard or return Service Messages, if the return option is set. + + + DISCARD + + + + + Performance monitoring counter for the number of rejected messages. + + + + + + 0 + + + + + + + The SccpAccountingCriteria MO and the SccpSp MO represents the accounting function in CPP. + +Attribute usageType specifies Accounting Remuneration (incoming GT messages) or Verification (outgoing GT messages). + +For Remuneration a SccpGlobalTitle MOId in attribute globalTitleId must be defined. +For Verification a SccpGlobalTitle MOid is defined in attribute globalTitleId, or a SccpEntitySet MOid is defined if accounting shall be made on the resulting new GT. + +The attribute ssN is optional . +The Mtp3bSrs MOid (including an SPC) in attribute pointerId is optional for accounting in one local node (SRP in one NI). +The SccpSp MOid in attribute pointerId is optional for accounting between two local nodes (SRP between two NIs). +Attribute countType specifies if Messages och Octets shall be counted. +Start and stop of accounting and output period for the accounting file is specified in the SccpSp MO. + + + + + + + + + + Label free for use. + + + "" + + + + + This attribute specifies if the MO is used for renumeration or verification. + +0 = Verification Criteria to detect outgoing massages that will be charged in the next relay node. + +1 = Renumeration Criteria to detect incoming messages for relaying, that will be charged. + + + + + + + + + Subsystem Number this Accounting Criteria applies to. +SubSystem Number 0 (zero) means that any SSN in CdPA (Called Party Address) is valid. + + + + + + 0 255 + + 0 + + + + + Specifies type of countes that should be activated. + + + + + MESSAGES + + + + + The identity of the SccpGlobalTitle MO or the SccpEntitySet MO used by this MO. + + + + + + + + + Performance monitoring counter for the number of messages, both incoming and outgoing. + +Note! If 'countType' is set to 'OCTETS' this counter is not valid. + + + + + + 0 + + + + + Performance monitoring counter for the number of octets, both incoming and outgoing. + +Note! If 'countType' is set to 'MESSAGES this counter is not valid. + + + + + + 0 + + + + + The pointer is an instance of a Mtp3bSrs MO OR an instance of a SccpSP MO. + +Note! If no pointerId is set all Signaling Point Codes (SPC) and all Sccp SP identities are valid. +Note! It is not possible to submit the Id of the SccpSp that the SccpAccountingCriteria belongs to. + + + + + + + + + + This MO models the Cbu (Node Control Board) board in CPP. +The Cbu board integrates the functionality of TUB, SCB, GPB and ETB (ET-MC1) into one Plug-In Unit. + +Note! The 'operationalState' is set to disabled if one of the functional parts is faulty. Even if the Cbu is marked with 'operationalState' DISABLED, parts of the Cbu can still be operational. + +Note! A functional part on a Cbu board can only be redundant with the same functional part on another Cbu board and thus not with that functional part implemented on a discrete board. Also note that redundancy is only applicable for the GPB part and the TimingUnit part of the Cbu board.. + +Note! On the Cbu board it is only possible to configure a maximum of 4 physical path terminations. These can be of type E1PhysPathTerm, J1PhyspathTerm or T1PhyspathTerm. It is not possible to create physical path terminations of different standards on the same board. + +Note! The Gpu part of the Cbu board (General Processor Unit) retrieves its 'availabilityStatus' from the PlugInUnit MO, thus not represented on the Cbu MO. + +Note! When the ET-MC1 is part of the Cbu board it is only possible to configure 4 physical ports as either E1 (ETSI), J1 (TTC) or T1 (ANSI). + +Note! This unit may only be inserted in slot 1 and 24 (or more accurately at APN=1 and 0 in a non-standard subrack). If redundant configuration is needed, two Cbu's must be inserted in the subrack. +If only one Cbu is used it must be placed in slot 1 (in a non-standard subrack) to be able to read the product information data of the subrack + + + + + + + + + + Provides the possibility to put a user-friendly label on the MO instance. + +Note! This attribute cannot be used for uniquely identifing the MO. + + + + 0 128 + + "" + + + + + Enabled or disabled according to the actual operational state of the NCB board. + + + + + + disabled + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. +The 'availabilityStatusEt' gives the availability status for the ET part of the NCB board. + + + + + + NO_STATUS + + + + + The availability status is used to qualify the operational state. It indicates why the operational state has changed its value to disabled. +The 'availabilityStatusTu' gives the availability status for the Timing Unit part of the NCB board. + + + + + + NO_STATUS + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 300 + + + + + + + + + + + + + + 0 4800 + + + + + + + + + + + + + + 0 2200 + + + + + + + + + + + + + + 0 6000 + + + + + + + + + + + + + + 0 500 + + + + + + + + + + + + + + 0 50 + + + + + + + + + + + + + + 0 600 + + + + + + + + + + + + + + 0 1000 + + + + + + + + + + + + + + 0 2000 + + + + + + + + + + + + + + 0 900 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 5000 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 1000 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 256 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 200 + + + + + + + + + + + + + + 0 20 + + + + + + + + + + + + + + 0 20 + + + + + + + + + + + + + + 0 10 + + + + + + + + + + + + + + 1 28 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This containment relation indicated that any kind of board may be used to specilize PlugInUnit. + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 5000 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 9 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 + + + + + + + The SccpApLocal represents a local SSN, no relation exists to an Mtp3bAp + +Of the possible 216 SccpAps allowed on a node, a maximum of 16 are allowed to be local, and a maximum of 200 are allowed to be remote. + + + + + + + + 0 16 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 2048 + + + + + + + + + + + + + + 0 2048 + + + + + + + + + + + + + + 0 200 + + + + + + + + + + + + + + 0 1024 + + + + + + + + + + + + + + 0 100 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 1 2 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 31 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 510 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 5 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 255 + + + + + + + + + + + + + + 0 16 + + + + + + + Multiplicity: 0..16 + + + + + + + + 0 16 + + + + + + + Multiplicity: 0..16 + + + + + + + + 0 16 + + + + + + + + + + + + + + 0 16 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 32 + + + + + + + + + + + + + + 0 128 + + + + + + + + + + + + + + 0 128 + + + + + + + + + + + + + + 0 500 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 850 + + + + + + + + + + + + + + 0 26 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 0 5 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + 0 32 + + + + + + + + + + + + + + 1 4 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 32 + + + + + + + + + + + + + + 0 31 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 31 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 24 + + + + + + + + + + + + + + 0 512 + + + + + + + + + + + + + + 0 512 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 63 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 1 + + + + + + + + + + + + + + 0 3 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 0 512 + + + + + + + + + + + + + + 0 8 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 28 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 0 2 + + + + + + + + + + + + + + 1 1 + + + + + + + + + + + + + + 1 1 + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/eventp/mp.dtd b/lib/xmerl/test/xmerl_SUITE_data/eventp/mp.dtd new file mode 100644 index 0000000000..1f6e31e772 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/eventp/mp.dtd @@ -0,0 +1,274 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.stub b/lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.stub new file mode 100644 index 0000000000..78d980d5b7 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.stub @@ -0,0 +1,5 @@ + + + +]> diff --git a/lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.xml b/lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.xml new file mode 100644 index 0000000000..ea96469af3 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/eventp/wurfl.xml @@ -0,0 +1,9 @@ + + + +]> + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/misc.tar.gz b/lib/xmerl/test/xmerl_SUITE_data/misc.tar.gz new file mode 100644 index 0000000000..c48a6f897b Binary files /dev/null and b/lib/xmerl/test/xmerl_SUITE_data/misc.tar.gz differ diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/documentRoot.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/documentRoot.xml new file mode 100644 index 0000000000..667a44b7fe --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/documentRoot.xml @@ -0,0 +1,43 @@ + + + + + + Some Text + + + + + + + + + + + + + Large dog! + + + + + + + + + Hates dogs! + + + + + + Likes all animals - especially dogs! + + + + + + + + \ No newline at end of file diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/e1074.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1074.xml new file mode 100644 index 0000000000..920a9e67e1 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1074.xml @@ -0,0 +1,18 @@ + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/e1075.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1075.xml new file mode 100644 index 0000000000..920a9e67e1 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1075.xml @@ -0,0 +1,18 @@ + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/e1076.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1076.xml new file mode 100644 index 0000000000..c9ffebb202 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1076.xml @@ -0,0 +1,13 @@ + + + cat + dog + + cat + + cat + + dog + + Cat + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/e1077.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1077.xml new file mode 100644 index 0000000000..9aa548e13c --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1077.xml @@ -0,0 +1,16 @@ + + + + ]> + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/e1078.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1078.xml new file mode 100644 index 0000000000..a90db50145 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/e1078.xml @@ -0,0 +1,11 @@ + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/motorcycles.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/motorcycles.xml new file mode 100644 index 0000000000..b3629dce34 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/motorcycles.xml @@ -0,0 +1,25 @@ + + + + + Suzuki + Suzuki VL 1500 + Intruder + + V-engine, 2-cylinders, 1500 cc + custom + cardan + Sissy bar, luggage carrier,V&H exhaust pipes + + 2004.08.25 + + + Yamaha + XJ 400 + + 4 cylinder, 400 cc + alround + chain + Good shape! + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/myBS_model.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/myBS_model.xml new file mode 100644 index 0000000000..58f90662a4 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/myBS_model.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/purchaseOrder.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/purchaseOrder.xml new file mode 100644 index 0000000000..a5ae223d65 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/purchaseOrder.xml @@ -0,0 +1,36 @@ + + + + Robert Smith + 8 Oak Avenue + + Old Town + PA + 95819 + + Hurry, my lawn is going wild! + + Alice Smith + 123 Maple Street + + Mill Valley + CA + 90952 + + + + + Lawnmower + 1 + 148.95 + Confirm this is electric + + + Baby Monitor + 1 + 39.98 + 1999-05-21 + + + diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath.xml b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath.xml new file mode 100644 index 0000000000..248fbd413d --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath.xml @@ -0,0 +1,25 @@ + + + + + + + + here are some text + + + + + here are some more text + + + + + + + + here are some additional text + + + + \ No newline at end of file diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_abbrev.erl b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_abbrev.erl new file mode 100644 index 0000000000..850b7f8135 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_abbrev.erl @@ -0,0 +1,266 @@ +%%%------------------------------------------------------------------- +%%% File : xpath_abbrev.erl +%%% Author : Bertil Karlsson +%%% Description : +%%% +%%% Created : 17 Jan 2006 by Bertil Karlsson +%%%------------------------------------------------------------------- +-module(xpath_abbrev). + +-export([test/0, check_node_set/2, ticket_6873/0, ticket_7496/0, functions/0]). + +-include("test_server.hrl"). +-include_lib("xmerl/include/xmerl.hrl"). + +test() -> + ?line {E,_} = xmerl_scan:file("xpath.xml"), + + ?line Res1 = xmerl_xpath:string("blipp",E), + ?line ok = check_node_set("blipp",Res1), + ?line Res2 = xmerl_xpath:string("*",E), + ?line ok = check_node_set("*",Res2), + ?line Res3 = xmerl_xpath:string("blipp/blupp/plopp/text()",E), + ?line ok = check_node_set("blipp/blupp/plopp/text()",Res3), + ?line Res4 = xmerl_xpath:string("blipp/blupp/@att2",E), + ?line ok = check_node_set("blipp/blupp/@att2",Res4), + ?line Res5 = xmerl_xpath:string("blipp/@*",E), + ?line ok = check_node_set("blipp/@*",Res5), + ?line Res6 = xmerl_xpath:string("blipp[2]",E), + ?line ok = check_node_set("blipp[2]",Res6), + ?line Res7 = xmerl_xpath:string("blipp[last()]",E), + ?line ok = check_node_set("blipp[last()]",Res7), + ?line Res8 = xmerl_xpath:string("*/blupp",E), + ?line ok = check_node_set("*/blupp",Res8), + ?line Res9 = xmerl_xpath:string("/myBS_model/blipp[3]/blupp[2]",E), + ?line ok = check_node_set("/myBS_model/blipp[3]/blupp[2]",Res9), + ?line Res10 = xmerl_xpath:string("blipp//plopp",E), + ?line ok = check_node_set("blipp//plopp",Res10), + ?line Res11 = xmerl_xpath:string("//plopp",E), + ?line ok = check_node_set("//plopp",Res11), + ?line Res12 = xmerl_xpath:string("//blupp/plopp",E), + ?line ok = check_node_set("//blupp/plopp",Res12), + ?line Res13 = xmerl_xpath:string(".",E), + ?line ok = check_node_set(".",Res13), + ?line Res14 = xmerl_xpath:string(".//blipp2",E), + ?line ok = check_node_set(".//blipp2",Res14), + ?line Res15 = xmerl_xpath:string(".//blipp2/blupp/plopp/..",E), + ?line ok = check_node_set(".//blipp2/blupp/plopp/..",Res15), + ?line Res16 = xmerl_xpath:string(".//blipp[2]/blupp/plopp/../@att2",E), + ?line ok = check_node_set(".//blipp[2]/blupp/plopp/../@att2",Res16), + ?line Res17 = xmerl_xpath:string(".//blipp/blupp/plopp[2]/../@att2",E), + ?line ok = check_node_set(".//blipp/blupp/plopp[2]/../@att2",Res17), + ?line Res18 = xmerl_xpath:string("blipp[@id='name2']",E), + ?line ok = check_node_set("blipp[@id='name2']",Res18), + ?line Res19 = xmerl_xpath:string("blipp[@id='name2'][3]",E), + ?line ok = check_node_set("blipp[@id='name2'][3]",Res19), + ?line Res20 = xmerl_xpath:string("//blupp[plopp=\"here are some more text\"]",E), + ?line ok = check_node_set("//blupp[plopp=\"here are some more text\"]",Res20), + ?line Res21 = xmerl_xpath:string("//blupp[plopp]",E), + ?line ok = check_node_set("//blupp[plopp]",Res21), + ?line Res22 = xmerl_xpath:string("blipp[@id and @test]",E), + ?line ok = check_node_set("blipp[@id and @test]",Res22). + +check_node_set("blipp",[E1,E2,E3]) -> + ?line ok = xml_element_name(E1,blipp), + ?line ok = xml_element_name(E2,blipp), + ?line ok = xml_element_name(E3,blipp), + ok; +check_node_set("*",[E1,E2,E3,E4]) -> + ?line ok = xml_element_name(E1,blipp), + ?line ok = xml_element_name(E2,blipp), + ?line ok = xml_element_name(E3,blipp), + ?line ok = xml_element_name(E4,blipp2), + ok; +check_node_set("blipp/blupp/plopp/text()",[T1,T2]) -> + ?line #xmlText{value="here are some text"} = T1, + ?line #xmlText{value="here are some more text"} = T2, + ok; +check_node_set("blipp/blupp/@att2",[A1,A2]) -> + ?line #xmlAttribute{name=att2} = A1, + ?line #xmlAttribute{name=att2} = A2, + ok; +check_node_set("blipp/@*",[A1,A2,A3,A4]) -> + ?line #xmlAttribute{} = A1, + ?line #xmlAttribute{} = A2, + ?line #xmlAttribute{} = A3, + ?line #xmlAttribute{} = A4, + ok; +check_node_set("blipp[2]",[E]) -> + ?line #xmlElement{name=blipp, + attributes=[#xmlAttribute{name=id,value="name2"}]} = E, + ok; +check_node_set("blipp[last()]",[E]) -> + ?line #xmlElement{name=blipp, + attributes=[#xmlAttribute{name=id,value="name3"}|_]} = E, + ok; +check_node_set("*/blupp",[E1,E2,E3,E4,E5,E6]) -> + ?line ok = xml_element_name(E1,blupp), + ?line ok = xml_element_name(E2,blupp), + ?line ok = xml_element_name(E3,blupp), + ?line ok = xml_element_name(E4,blupp), + ?line ok = xml_element_name(E5,blupp), + ?line ok = xml_element_name(E6,blupp), + ok; +check_node_set("/myBS_model/blipp[3]/blupp[2]",[E]) -> + ?line #xmlElement{name=blupp, + attributes=[#xmlAttribute{name=att,value="bluppc2"}]}=E, + ok; +check_node_set("blipp//plopp",[#xmlElement{name=plopp},#xmlElement{name=plopp}]) -> + ok; +check_node_set("//plopp",[E1,E2,E3]) -> + ?line ok = xml_element_name(E1,plopp), + ?line ok = xml_element_name(E2,plopp), + ?line ok = xml_element_name(E3,plopp), + ok; +check_node_set("//blupp/plopp",[E1,E2,E3]) -> + ?line ok = xml_element_name(E1,plopp), + ?line ok = xml_element_name(E2,plopp), + ?line ok = xml_element_name(E3,plopp), + ok; +check_node_set(".",[#xmlElement{name=myBS_model}]) -> + ok; +check_node_set(".//blipp2",[#xmlElement{name=blipp2}]) -> + ok; +check_node_set(".//blipp2/blupp/plopp/..",[#xmlElement{name=blupp}]) -> + ok; +check_node_set(".//blipp[2]/blupp/plopp/../@att2",[#xmlAttribute{name=att2,value="bluppb"}]) -> + ok; +check_node_set(".//blipp/blupp/plopp[2]/../@att2",[#xmlAttribute{name=att2,value="bluppc"}]) -> + ok; +check_node_set("blipp[@id='name2']",[E]) -> + ?line #xmlElement{name=blipp, + attributes=[#xmlAttribute{name=id,value="name2"}]}=E, + ok; +check_node_set("blipp[@id='name2'][3]",[]) -> + ok; +check_node_set("//blupp[plopp=\"here are some more text\"]",[E]) -> + ?line #xmlElement{name=blupp, + content=[_T,#xmlElement{name=plopp,content=C}|_]} = E, + ?line true = lists:keymember("here are some more text",#xmlText.value,C), + ok; +check_node_set("//blupp[plopp]",[E1,E2,E3]) -> + ?line #xmlElement{name=blupp, + content=C1} = E1, + ?line true = lists:keymember(plopp,#xmlElement.name,C1), + ?line #xmlElement{name=blupp, + content=C2} = E2, + ?line true = lists:keymember(plopp,#xmlElement.name,C2), + ?line #xmlElement{name=blupp, + content=C3} = E3, + ?line true = lists:keymember(plopp,#xmlElement.name,C3), + ok; +check_node_set("blipp[@id and @test]",[E]) -> + ?line #xmlElement{name=blipp, + attributes=Atts} = E, + ?line true = lists:keymember(id,#xmlAttribute.name,Atts), + ?line true = lists:keymember(test,#xmlAttribute.name,Atts), + ok; +check_node_set(Pattern,NodeSet) -> + io:format("Pattern: ~p~nNodeSet: ~p~n",[Pattern,NodeSet]), + error. + +xml_element_name(E,N) -> + ?line #xmlElement{name=N} = E, + ok. + +ticket_6873() -> + ?line [#xmlElement{}] = xmerl_xpath:string("//foo[contains(@bar, 'oe')]",element(1,xmerl_scan:string(""))), + ok. + +ticket_7496() -> + Test = fun(Doc, XPath, Exp) -> + Result = xmerl_xpath:string(XPath, Doc), + ?line Exp = [Name || #xmlElement{name = Name} <- Result], + ok + end, + ?line {Doc1,_} = xmerl_scan:string(" "), + ?line ok = Test(Doc1, "//b/following::*", [c, d, e]), + ?line ok = Test(Doc1,"//b/following::*[1]", [c]), + ?line ok = Test(Doc1,"//b/following::*[position()=1]", [c]), + ?line ok = Test(Doc1,"//b/following::*[3]", [e]), + ?line ok = Test(Doc1,"//b/following::*[position()=3]", [e]), + ?line ok = Test(Doc1,"//e/preceding::*", [b, c, d]), + ?line ok = Test(Doc1,"//e/preceding::*[1]", [d]), + ?line ok = Test(Doc1,"//e/preceding::*[position()=1]", [d]), + ?line ok = Test(Doc1,"//e/preceding::*[3]", [b]), + ?line ok = Test(Doc1,"//e/preceding::*[position()=3]", [b]), + ?line ok = Test(Doc1,"//b/following::*[position() mod 2=0]", [d]), + ?line ok = Test(Doc1,"//b/self::*", [b]), + + ?line {Doc2,_} = xmerl_scan:string(" "), + ?line ok = Test(Doc2,"//g/preceding::*", [b, c, d, e]), + ?line ok = Test(Doc2, "//g/following::*", [h, i, j, k]), + ?line ok = Test(Doc2,"//g/ancestor::*", [a, f]), + ?line ok = Test(Doc2,"//g/ancestor::*[1]", [f]), + ?line ok = Test(Doc2,"//g/ancestor::*[2]", [a]), + ?line ok = Test(Doc2,"//g/ancestor-or-self::*", [a, f, g]), + ?line ok = Test(Doc2,"//g/ancestor-or-self::*[1]", [g]), + ?line ok = Test(Doc2,"//g/ancestor-or-self::*[2]", [f]), + ?line ok = Test(Doc2,"//g/ancestor-or-self::*[3]", [a]), + ?line ok = Test(Doc2,"/descendant::*", [a, b, c, d, e, f, g, h, i, j, k]), + ?line ok = Test(Doc2,"//f/preceding-sibling::*", [b, c, e]), + ?line ok = Test(Doc2,"//f/following-sibling::*", [h, i, k]), + ?line ok = Test(Doc2,"//f/self::*", [f]), + ?line ok = Test(Doc2,"//f/ancestor::*", [a]), + ?line ok = Test(Doc2,"//f/descendant::*", [g]), + ?line ok = Test(Doc2,"//f/preceding::*", [b, c, d, e]), + ?line ok = Test(Doc2,"//f/following::*", [h, i, j, k]), + ?line ok = Test(Doc2,"//text()[1]/following-sibling::*", [c, e, f, h, i, k]), + + ?line {Doc3,_} = xmerl_scan:file("documentRoot.xml"), + ?line ok = Test(Doc3,"//child",[child,child,child]), + ?line ok = Test(Doc3,"//child[@name='beta']",[child]), + ?line [{xmlAttribute,id,[],[],[],[],1,[],"2",false}] = + xmerl_xpath:string("/documentRoot/parent/child[@name='beta']/@id",Doc3), + ?line ok = Test(Doc3,"/documentRoot/parent/child|/documentRoot/parent/pet", + [child,child,child,pet,pet]), + ?line ok = Test(Doc3,"//*[starts-with(local-name(),'p')]", + [parent,pet,pet]). + + +functions() -> + Test = fun(Doc, XPath, Exp) -> + Result = xmerl_xpath:string(XPath, Doc), + ?line Exp = [begin + case Obj of + #xmlElement{name = EName} -> + EName; + #xmlAttribute{name = AName} -> + AName; + #xmlText{value=Text} -> + Text + end + end|| Obj <- Result], + ok + end, + Foo = + "" + " " + " Xml" + " 1" + " " + " " + " Xpath" + " 2" + " " + " " + " Erlang" + " 3" + " " + "", + {Doc,_} = xmerl_scan:string(Foo), + ?line ok = Test(Doc,"/foo/bar[name = 'Xml']/value/text()",["1"]), + ?line ok = Test(Doc,"/foo/bar/node()/text()", + ["Xml","1","Xpath","2","Erlang","3"]), + ?line ok = Test(Doc,"/foo/bar[contains(name, 'path')]",[bar]), + ?line ok = Test(Doc,"/foo/bar[starts-with(name, 'X')]",[bar,bar]), + ?line ok = Test(Doc,"/foo/bar[value = string(1)]/value/text()",["1"]), + + + {Doc2,_}= xmerl_scan:file("purchaseOrder.xml"), + ?line ok = Test(Doc2,"//*[starts-with(local-name(),'c')]", + ['apo:comment',city,city,comment]), + ?line ok = Test(Doc2,"//*[starts-with(name(),'c')]", + [city,city,comment]), + ?line ok = Test(Doc2,"//*[starts-with(name(),'{http://www.example.com/PO1')]", + ['apo:purchaseOrder','apo:comment']). diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_lib.erl b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_lib.erl new file mode 100644 index 0000000000..4cde46826e --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_lib.erl @@ -0,0 +1,184 @@ +%%%------------------------------------------------------------------- +%%% File : xpath_lib.erl +%%% Author : Bertil Karlsson +%%% Description : +%%% +%%% Created : 13 Jan 2006 by Bertil Karlsson +%%%------------------------------------------------------------------- +-module(xpath_lib). + +-export([test/0,check_node_set/2,ticket_6873/0]). + +-include("test_server.hrl"). +-include_lib("xmerl/include/xmerl.hrl"). + +test() -> + ?line {E,_} = xmerl_scan:file("myBS_model.xml"), + ?line Res1 = xmerl_xpath:string("blipp",E), + ?line ok = check_node_set("blipp",Res1), + ?line Res2 = xmerl_xpath:string("//blipp",E), + ?line ok = check_node_set("//blipp",Res2), + ?line Res3 = xmerl_xpath:string("/myBS_model/blipp",E), + ?line ok = check_node_set("/myBS_model/blipp",Res3), + ?line Res4 = xmerl_xpath:string("blipp[@id=\"name1\"]",E), + ?line ok = check_node_set("blipp[@id=\"name1\"]",Res4), + ?line Res5 = xmerl_xpath:string("//blipp[@id=\"name1\"]",E), + ?line ok = check_node_set("//blipp[@id=\"name1\"]",Res5), + ?line Res6 = xmerl_xpath:string("/myBS_model/blipp[@id=\"name1\"]",E), + ?line ok = check_node_set("/myBS_model/blipp[@id=\"name1\"]",Res6). + + +check_node_set("blipp",[H1,H2]) -> + ?line #xmlElement{name = blipp} = H1, + ?line #xmlElement{name = blipp} = H2, + ok; +check_node_set("//blipp",[H1,H2]) -> + ?line #xmlElement{name = blipp} = H1, + ?line #xmlElement{name = blipp} = H2, + ok; +check_node_set("/myBS_model/blipp",[H1,H2]) -> + ?line #xmlElement{name = blipp} = H1, + ?line #xmlElement{name = blipp} = H2, + ok; +check_node_set("blipp[@id=\"name1\"]",[H]) -> + ?line H#xmlElement{attributes=#xmlAttribute{name=id,value="name1"}}, + ok; +check_node_set("//blipp[@id=\"name1\"]",[H]) -> + ?line H#xmlElement{attributes=#xmlAttribute{name=id,value="name1"}}, + ok; +check_node_set("/myBS_model/blipp[@id=\"name1\"]",[H]) -> + ?line H#xmlElement{attributes=#xmlAttribute{name=id,value="name1"}}, + ok. + +ticket_6873() -> + GetId = + fun(Atts) -> + case lists:keysearch(id,#xmlAttribute.name,Atts) of + {value,#xmlAttribute{value=AttV}} -> AttV; + _ -> novalue + end + end, + Test = + fun(Doc, XPath, Exp) -> + Result = xmerl_xpath:string(XPath, Doc), + Exp = [begin + case Obj of + #xmlElement{name = EName,attributes=Atts} -> + {EName,GetId(Atts)}; + #xmlAttribute{name = AName} -> + AName; + #xmlText{value=Text} -> + Text + end + end|| Obj <- Result], + ok + end, + + + + Doc1 = get_doc("e1074"), + ?line ok = Test(Doc1,"/*",[{root,"1"}]), + ?line ok = Test(Doc1,"/root",[{root,"1"}]), + ?line ok = Test(Doc1,"/root/*",[{elem1,"2"},{elem1,"8"},{e,"12"}]), + ?line ok = Test(Doc1,"/root/e",[{e,"12"}]), + ?line ok = Test(Doc1,"//e",[{e,"12"},{e,"4"},{e,"6"},{e,"10"},{e,"11"}]), + ?line ok = Test(Doc1,"//*[name() != 'e']", + [{root,"1"},{elem1,"2"},{elem1,"8"},{elem2,"3"}, + {elem3,"5"},{elem3,"7"},{elem2,"9"}]), + ?line ok = Test(Doc1,"//elem1/e",[{e,"10"},{e,"11"}]), + ?line ok = Test(Doc1,"//elem1//e",[{e,"4"},{e,"6"},{e,"10"},{e,"11"}]), + ?line ok = Test(Doc1,"//*[*]", + [{root,"1"},{elem1,"2"},{elem1,"8"}, + {elem2,"3"},{elem3,"5"}]), + ?line ok = Test(Doc1,"//*[not(*)]", + [{e,"12"},{e,"4"},{elem3,"7"},{e,"6"}, + {elem2,"9"},{e,"10"},{e,"11"}]), + %% contents would be empty in the above expression + ?line [#xmlElement{content=[]}|_] = xmerl_xpath:string("//*[not(*)]",Doc1), + ?line ok = Test(Doc1,"//*[e]",[{root,"1"},{elem1,"8"},{elem2,"3"},{elem3,"5"}]), + ?line ok = Test(Doc1,"//*[count(e)>1]",[{elem1,"8"}]), + ?line ok = Test(Doc1,"//*[not(e) and name() != 'e']", + [{elem1,"2"},{elem3,"7"},{elem2,"9"}]), + ?line ok = Test(Doc1,"/*/*/*/e",[{e,"4"}]), + ?line ok = Test(Doc1,"//*[starts-with(name(), 'el')]", + [{elem1,"2"},{elem1,"8"},{elem2,"3"}, + {elem3,"5"},{elem3,"7"},{elem2,"9"}]), + ?line ok = Test(Doc1,"//*[contains(name(), 'lem1')]", + [{elem1,"2"},{elem1,"8"}]), + ?line ok = Test(Doc1,"/*/e | //elem2/e",[{e,"4"},{e,"12"}]), + + io:format("Tested ~p~n",[e1074]), + + Doc2 = get_doc("e1075"), + ?line ok = Test(Doc2,"/*/*[1]",[{elem1,"2"}]), + ?line ok = Test(Doc2,"/root/elem1[2]",[{elem1,"8"}]), + + %% Get all first-born e elements in the document; that is, for all + %% e elements with e element siblings, include only the first + %% sibling.Note that //e[1] does not return the first e element in + %% the document because the [1] predicate applies to e, which + %% represents the set of e elements under one element and not to + %% //e, which represents the set of e elements in the document. + %% ?line ok = Test(Doc2,"//e[1]",[{e,"4"},{e,"6"},{e,"10"},{e,"12"}]), + + %% The following expression retrieves the first e element in the + %% document: + %% ?line ok = Test(Doc2,"(//e)[1]",[{e,4}]), + + %% For all e elements with e element siblings, include only the + %% first 3 siblings + %% ?line ok = Test(Doc2,"//e[position() <= 3]",[{e,"4"},{e,"6"},{e,"10"},{e,"11"},{e,"12"}]), + + %% Get all last-born e elements in the document; that is, for all + %% e elements with e element siblings, include only the last + %% sibling + %% ?line ok = Test(Doc2,"//e[last()]",[{e,"4"},{e,"6"},{e,"11"},{e,"12"}]), + + %% Get the last e element in the document + %% ?line ok = Test(Doc2,"(//e)[last()]", [{e,"12"}]), + + + io:format("Tested ~p~n",[e1075]), + + + Doc3 = get_doc("e1076"), + ?line ok = Test(Doc3,"//*[.='cat']",[{elem1,"2"},{elem3,"6"}]), + ?line ok = Test(Doc3,"//*[.='dog']",[]), + ?line ok = Test(Doc3,"//*[contains(.,'cat')]", + [{elem1,"2"},{elem1,"4"},{elem3,"6"}]), + ?line ok = Test(Doc3,"//elem3[contains(.,'cat')]",[{elem3,"6"}]), + ?line ok = Test(Doc3,"//*[contains(child::text(),'cat')]",[{elem1,"2"},{elem1,"4"},{elem3,"6"}]), + ?line ok = Test(Doc3,"//*[count(*)=0 and contains(.,'cat')]",[{elem1,"2"},{elem3,"6"}]), + ?line ok = Test(Doc3,"//*[contains(translate(.,'abcdefghijklmnopqrstuvwxyz', 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'),'CAT')]",[{elem1,"2"},{elem1,"4"},{elem1,"7"},{elem3,"6"}]), + + io:format("Tested ~p~n",[e1076]), + + Doc4 = get_doc("e1078"), + ?line ok = Test(Doc4,"//*[@pet='cat']",[{elem1,"2"}]), + ?line ok = Test(Doc4,"//*[@pet='dog']",[{elem1,"7"}]), + ?line ok = Test(Doc4,"//*[contains(@pet,'dog')]", + [{elem1,"3"},{elem1,"7"}]), + ?line ok = Test(Doc4,"//*[@age]",[{elem1,"3"},{elem3,"6"}]), + ?line ok = Test(Doc4,"//elem1[@age]",[{elem1,"3"}]), + ?line ok = Test(Doc4,"//*[@pet and @age]",[{elem1,"3"}]), + ?line ok = Test(Doc4,"//*[contains(translate(@pet,'abcdefghijklmnopqrstuvwxyz', 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'),'CAT')]",[{elem1,"2"},{elem1,"4"}]), + + io:format("Tested ~p~n",[e1078]), + + + Doc5 = get_doc("e1077"), + ?line ok = Test(Doc5,"id('3')",[{e,"3"}]), + + %% Get all e elements directly under element id 3 + %% ?line ok = Test(Doc5,"id('two')/e",[{e,"3"},{e,"4"},{e,"6"}]), + ?line ok = Test(Doc5,"id('two 3 seven the fifth')",[{e,"seven"},{e,"3"},{e,"two"}]), + ?line ok = Test(Doc5,"id('100')",[]), + + io:format("Tested ~p~n",[e1077]), + ok. + + + +get_doc(Name) -> + ?line {Doc,_} = xmerl_scan:file(Name++".xml"), + Doc. diff --git a/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_text.erl b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_text.erl new file mode 100644 index 0000000000..e39ad6bcb0 --- /dev/null +++ b/lib/xmerl/test/xmerl_SUITE_data/xpath/xpath_text.erl @@ -0,0 +1,28 @@ +%%%------------------------------------------------------------------- +%%% File : xpath_text.erl +%%% Author : Bertil Karlsson +%%% Description : +%%% +%%% Created : 14 Dec 2004 by Bertil Karlsson +%%%------------------------------------------------------------------- +-module(xpath_text). + +-compile(export_all). + +-include("test_server.hrl"). +-include_lib("xmerl/include/xmerl.hrl"). + +-import(xmerl_xs, + [ xslapply/2, value_of/1, select/2, built_in_rules/2 ]). + + +one() -> + ?line {A,_}=xmerl_scan:file('motorcycles.xml'), + ?line [["Suzuki","Yamaha"]] = template(A), + ok. + +%%% templates, test of OTP-5268 +template(E = #xmlElement{name='motorcycles'}) -> + [value_of(select("bike/name/manufacturer/text()",E))]; +template(E) -> built_in_rules(fun template/1, E). + -- cgit v1.2.3