Non-NMS service is a service created from node or any other vendor NMS and discovered in Tejas NMS.
Perform the following steps for changing the non-NMS service to NMS service:
Go to Configuration > Layer 2 > Services menu and click Complete Services option. The Complete Services page is displayed.
Select the desired service with TJ5500 Service status as false and click on (Toggle Service non-NMS to NMS) and select the option non-NMS to NMS Service. A confirmation window is displayed.
Click OK. Successful message is displayed.
Click OK. The service changes to NMS service for which TJ5500 Service status will be true.
Toggle Service NMS to non-NMS
NMS service is a service created from Tejas NMS.
Perform the following steps for changing the NMS service to non-NMS service:
Go to Configuration > Layer 2 > Services menu and click Complete Services option. The Complete Services page is displayed.
Select the desired service with TJ5500 Service status as true and click on (Toggle Service non-NMS to NMS) and select the option NMS to non-NMS Service. A confirmation window is displayed.
Click OK. Successful message is displayed.
Click OK. The service changes to non-NMS service for which TJ5500 Service status will be false.
In case of non-NMS created services, new parameter DELETE_NON_NMS_CREATED_SERVICE will be displayed at backend in common.properties file at /opt/nms/release/config location. Acceptable values are true and false.
true: If user send DE-activation command from TJ5500 UI, the selected service will get deleted from node and will be shown as PENDING state in TJ5500 UI and will not be deleted from TJ5500 database.
false: If user send DE-activation command from TJ5500 UI, the selected service will get deleted from node and as well as from database of TJ5500.
New parameter ONT_AUTO_ACCEPT will be displayed in common.properties file at /opt/nms/release/config location that can be configured as true or false. Two implementations of this parameter are explained below:
ONT_AUTO_ACCEPT= true
Implication 1: Right-click Accept ONT option on Manage ONTs page. If an ONT is connected to a node already added in NMS, the parameters NMS State, Admin State, and Physical Status of that ONT will be displayed as Activate, Enable, and Activated respectively on successful connection.
Implication 2: ONT connected to Node A (for example) is in Activate state. If the ONT is removed and connected to Node B, the NMS State of that ONT on both Node A and Node B will be displayed as Conflict.
i) Case 1: If ONT is deleted from Node B, NMS State of the ONT on Node A will be back to Activate state, while the Physical State will be Deactivated.
ii) Case 2: If ONT is deleted from Node A, NMS State of the ONT on Node B will be in Deactivate state.
ONT_AUTO_ACCEPT= false
Implication 1: When an ONT is connected to a node already added in NMS, the NMS State, Admin State, and Physical Status of that ONT will be displayed as Pending, Disable, and Deactivated respectively. Right-click on the ONT and select Accept ONT option on Manage ONTs page. State of all three parameters gets updated on successful connection. This is a default behavior (same as previous when this parameter was not present in backend).
Implication 2: ONT connected to Node A (for example) is in Activate state. Now if the ONT is removed and connected to Node B, the NMS State of that ONT on both Node A and Node B will be displayed as Conflict.
i) Case 1, if ONT is deleted from Node B, NMS State of the ONT on Node A will be back to Activate state, while the Physical State will be Deactivated.
ii) Case 2, if ONT is deleted from Node A, NMS State of the ONT on Node B will be in Acceptance Pending state.
NOTE:ONT_AUTO_ACCEPT is set as true by default in this release and is recommended to retain as true.
(Toggle Service non-NMS to NMS) and select the option non-NMS to NMS Service. A confirmation window is displayed.