NEtO installation files are not bundled with the NSP and must be separately obtained as a part of the node software SWP, or as part of the TCO suite downloaded from the customer support portal for the node. When using the TCO suite, perform the following:

1. Locate the NEtO files in the WebEML directory of the TCO suite

2. Copy the files to the following directory of the client system:

   \local_path\nsp\nms\thirdparty\neto

   where local_path is the location where the NSP client is installed

You can launch the NEtO from the NFM-P GUI; see To cross-launch NEtO from NFM-P .

For the Wavence SA, NEtO cross-launch is possible only if the registration table entry has not reached the limit of 15 entries. Additionally, cross-launch to a node using IPv6 is successful only if the node can be reached from the NFM-P client initiating the cross-launch, and an IPv6 route exists.

NEtO cross-launch tasks are recorded in the NFM-P user activity log. To view the task status, choose Administration→Security→User Activity from the NFM-P main menu. The log indicates whether the cross-launch was successful.

NFM-P manages the distribution of the NEtO application and all related profiles. Any discovered Wavence NE has all cross-launch paths automatically configured in database so that no user configuration is required to use the NEtO. The cross-launch function also supports the option to run TACACS+ in the network, in which case NEtO has a NULL authentication when cross-launched, and the user is prompted for a username and password.

The NFM-P supports the selection of user profiles to access the NEtO. The Admin NEtO launch, Viewer NEtO launch, and Default NEtO launch are the NFM-P scope of command roles that allow access to the NEtO for a specific user profile. See the NSP System Administrator Guide for the list of scope of command roles. See To configure a scope of command role for NEtO access for information about configuring a scope of command role for access to the NEtO for the required user profile.

You can use the Wavence element manager to manage services on the Wavence. The use of an external element manager to change key network management information usually managed by NFM-P (such as service IDs, SAP or site information, or VLAN information) could result in data loss or corruption. To avoid this problem, site information persists so that management actions (such as moving service access from one DS1 port to another) do not result in data loss.

Configuration of the following can only be performed using a Wavence element manager:

• cards

• port usage

• Radio LAGs

• port and card protection

NFM-P takes the following additional actions to accommodate service changes made using the Wavence element manager:

• A move between ports generates an alarm. The new port attachment is discovered and the deleted port is retained. The user can copy provisioning information to the new port in the NFM-P or manually reverse the change, if required.

• A move between radio backhaul paths generates an alarm and is accepted. The alarm message retains the old and new path information, allowing the user to change the service back to its original form, if required.

• A move between radio and Ethernet backhaul paths generates an alarm and is accepted. The alarm message retains the old and new path information, allowing the user to change the service back to its original form, if required.

• When using a Wavence element manager to change VLAN IDs for a service, the new service is discovered and alarms are generated for both services. An informational alarm is generated for the new service, and a major alarm is generated for the old service.

• A cleanup on the service deletes all new discovery alarms and old SAPs, and accepts the new SAPs.

• Service changes from the Wavence element manager are not supported for ERPS (radio or fiber).