Multiplexer Profile Database Information; Device Profile Information For Multiplexers - Paradyne COMSPHERE 6800 Series Multiplexer Management And Configuration Manual

COMSPHERE 6800 Series Nework Management System

Multiplexer Profile Database Information

The 6800 Series NMS device, site, facility and vendor profiles are used to store information
relevant to specific multiplexer nodes and facilities. The profiles are created, respectively, using
the Create Device Profile (crdp), Create Site Profile (crsp), Create Facility Profile (crfp) and
Create Vendor Profile (crvp) commands.
These profiles are discussed in the COMSPHERE 6800 Series Network Management System
User's/System Administrator's Guide, and the commands are described in greater detail in the
COMSPHERE 6800 Series Network Management System Core Command Reference Manual. The
profiles need to contain specific data in them for multiplexer support. The following sections
identify the required fields that must be completed for multiplexers in the profile database.

Device Profile Information for Multiplexers

Device profile data maintains synchronization with internal multiplexer node connectivity data and
channel group tables according to the following guidelines.
Specific device profile fields are required by NMS for Series 700 multiplexers. If the device exists,
the NMS automatically retrieves model numbers and software versions for the device profile when
you execute the Create Device Profile (crdp) or Edit Device Profile (eddp) command for that node.
Here is a list of possibilities:
The COMSPHERE 6800 Series Network Management System Core Command Reference Manual
provides the detailed information needed for these required fields on the Create Device Profile
input form. The required fields in the device profile record for each multiplexer are briefly
identified here.
Inventory State
1-8
You are not permitted to delete a device profile for a multiplexer node if the current channel
group tables indicate that a channel group is configured with a fixed route that contains the
node requested for deletion. This also applies for the endpoint nodes of automatic routes. If
you attempt to delete a profile, the NMS returns a message indicating that channel groups
passing through the node must be deleted before the profile can be deleted.
Successfully adding, deleting, and editing device profiles causes NMS to appropriately
update its poll list for multiplexer nodes.
NMS does not allow device profiles to be deleted if the device has active alerts, opened or
closed trouble tickets, or associated facility profiles.
If the model/version is known to NMS, the fields are automatically completed in the profile.
If the model/version is unknown to NMS, the fields remain unchanged.
If a node is not available, a warning box appears indicating no response was received from
the node. You can still enter the model/version manually by using either the Create Device
Profile (crdp) command or the Edit Device Profile (eddp) command.
This field indicates if the multiplexer node is being used in the network. The inventory
state of the mux can be active, on order, stock, repair, or removed.
August 1994 6800-A2-GB21-10