U.S. patent application number 10/159972 was filed with the patent office on 2003-07-17 for element management system with adaptive interface based on autodiscovery from element identifier.
Invention is credited to Galou, Salim, Levesque, Gilbert, Naik, Dharmendra, Wong, Malais, Zaeh, Rick.
Application Number | 20030133556 10/159972 |
Document ID | / |
Family ID | 22470187 |
Filed Date | 2003-07-17 |
United States Patent
Application |
20030133556 |
Kind Code |
A1 |
Naik, Dharmendra ; et
al. |
July 17, 2003 |
Element management system with adaptive interface based on
autodiscovery from element identifier
Abstract
A network element management system which automatically
configures itself, when an operator enters a component identifier,
for optimal full-featured management of the identified component.
This is preferably done by an autodiscovery process, and not by any
mere lookup.
Inventors: |
Naik, Dharmendra; (San Jose,
CA) ; Levesque, Gilbert; (Mountainview, CA) ;
Galou, Salim; (San Jose, CA) ; Wong, Malais;
(Sunnyvale, CA) ; Zaeh, Rick; (US) |
Correspondence
Address: |
Terry J. Stalford, Esq.
Baker Botts L. L. P.
Suite 600
2001 Ross Avenue
Dallas
TX
75201-2980
US
|
Family ID: |
22470187 |
Appl. No.: |
10/159972 |
Filed: |
May 30, 2002 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10159972 |
May 30, 2002 |
|
|
|
09975676 |
Oct 10, 2001 |
|
|
|
09975676 |
Oct 10, 2001 |
|
|
|
09580521 |
May 25, 2000 |
|
|
|
60135883 |
May 26, 1999 |
|
|
|
Current U.S.
Class: |
379/201.12 ;
379/201.01 |
Current CPC
Class: |
H04L 41/0806 20130101;
H04L 41/50 20130101; H04L 41/0886 20130101; H04L 41/0856 20130101;
H04L 41/0873 20130101; H04L 41/0853 20130101; H04L 41/22 20130101;
H04L 41/0883 20130101; H04L 41/0659 20130101; H04L 41/0843
20130101; H04L 41/082 20130101; H04L 41/0681 20130101; H04L 41/024
20130101; H04M 3/247 20130101; H04L 41/12 20130101; H04L 41/0866
20130101; H04L 41/0893 20130101; H04L 41/044 20130101 |
Class at
Publication: |
379/201.12 ;
379/201.01 |
International
Class: |
H04M 003/42 |
Claims
What is claimed is:
1. A computer/software system for managing telecommunication
network elements, comprising: one or more operator-driven processes
which monitor and manage network elements; and an operator
interface which permits operators to work from graphical
representations of connection topology, and which also, when an
operator properly inputs identification of a specific network
element, automatically performs discovery of characteristics of
said specific network element, and presents said specific network
element, in a way which is dependent on said characteristics, for
the operator to monitor or manage.
2. The system of claim 1, wherein the system automatically
configures itself to support all features of the discovered NE.
3. The system of claim 1, further comprising a database which
reports attributes of ones of said network elements in response to
queries from ones of said operator-driven processes, and which is
transparently updated.
Description
CROSS-REFERENCE TO OTHER APPLICATION
[0001] This application claims priority from Claims Priority From
No. 60/135,883 Filed May 26, 1999, filed May 26, 1999, which is
hereby incorporated by reference.
BACKGROUND AND SUMMARY OF THE INVENTION
[0002] The present application relates to telecommunication
systems, and particularly to element management systems which
remotely manage telecommunications network elements.
Background: Telecommunications Network Structure
[0003] The advance of modern telecommunications technology, and the
increasing use of data bandwidth by many businesses, has resulted
in an increasing amount of traffic flowing to an increasing number
of nodes. The data bandwidths which can be handled by fiber optic
lines have made long-distance data transmission much cheaper, but
have required complex electronics for combining substreams of data
and routing each to its proper destination. The telecommunications
infrastructure includes a wide variety of network elements, each of
which may include a number of complex programmable subsystems. With
the explosive growth in technological capabilities, many vendors
have been making rapid improvements in their network element
components.
[0004] Telecommunications networks are complex to design, build,
and maintain. Ever increasing demands for improvements, greater
bandwidth, ease of use, and interoperability add to this complexity
and require increasingly capable network management. Service
providers require network management systems that can accommodate
equipment and components that comply with a variety of interface
standards.
Background: Developments in Diversity of Network Elements
[0005] It should be noted that the terms "network element" and
"element manager" are also sometimes used in reference to computer
networks rather than telecommunications networks. However, the
requirements for element management in such networks are vastly
different from those relevant to telecommunications networks.
First, telecommunications networks are normally have a far larger
number of nodes. Second, data stream routing is the primary purpose
of telecommunications networks, while in computing networks
switching is performed merely when required to link resources
demanded by a particular task. (Indeed a WAN will typically be
implemented using data channels provided by a telecommunications
network operator, so it can be seen that the telecommunications
network, in such cases is regarded as a more "fundamental" level on
which the connectivity of the WAN can be allowed to depend.) Third,
the reliability requirements of telecommunications networks are
extremely high, and can be much higher than those of some computer
networks. Fourth, a telecommunications network typically includes
far more nodes which are physically remote. Fifth, the ratio of
processor operations to data bits transmitted is typically
different by many orders of magnitude.
[0006] The network elements are each a complex system which
includes many complex programmable subsystems. These programmable
subsystems have local memories which store their programming and
maintain a record of their operating history. The data in these
many local memories is important for auditing system integrity and
reliability.
Background: Element Management Systems (EMSs)
[0007] Element management systems are used by telecommunications
system operators to monitor telecommunications network elements,
and change signal switching and routing as required. Conventionally
a single "network element" is considered to include a number of
independently programmable switching cards (typically one or more
shelves full, i.e. tens of cards). Since each card is itself a
complex programmable system, the total programmability of a modern
network element is very large.
[0008] Element management is not a trivial task, since each network
element includes many complex programmable subsystems, and since
very high reliability is required. Element management is rapidly
becoming more difficult, since the number of possible programmed
states in each network element is steadily increasing.
[0009] For example, a typical card might have four bidirectional
OC-3 interfaces, for a total bandwidth of more than half a gigabaud
in each direction. Each OC-3 data stream is resolved into three
STS-1 data streams, which in turn are each resolved into 28 data
streams at T1 rate (approximately 1.5 million bits per second
each). Thus the card can redirect 84 different channels within each
of its four data connections. Even without cross-connect options,
the theoretically possible number of in/out switching states is 336
factorial (336.times.335.times.334.times. . . .
.times.3.times.2.times.1). The theoretically possible number of
switching states for a network element which includes 30 such cards
will be in the neighborhood of this number raised to the 30th
power, which is a very large number (of the order of
10.sup.21138).
[0010] As the demand for bandwidth increases, hierarchical
switching relations are appearing. For example, currently proposed
WDM cards would handle routing of 168 OC-192 channels, each
carrying about 10 gigabaud (ten billion bits per second). Each of
those OC-192 data streams would then be further manipulated by an
OC-192 switching card, which would divide the OC-192 data streams
down into (for example) OC-3 data streams, for routing to an OC-3
switching card. (For comparison, ordinary voice connections require
only about 56 kilobits per second each, which is much smaller than
the smallest data channel of the OC-3 card mentioned above.)
[0011] An opposite trend, which also makes element management more
difficult, is the larger size of networks. Telecommunications
networks underwent a fundamental change in their locational
economics in the last decades of the 20th century. This change
began when microwave links replaced copper, but in recent years has
been driven by the very high bandwidths provided by fiber optic
trunk lines. In this new era of locational economics, the physical
distance between signal origination and destination points became
much less important than it had been previously; and a corollary of
this was that economies of scale drove telecommunications networks
to increasingly larger sizes (whether measured geographically, or
by numbers of nodes, or by bandwidth switched).
[0012] The trend to larger networks has also been driven by the
increasingly global span of telecommunications carriers. Large
carriers have networks which extend over tens of thousands of
miles, and they need reliable tools for monitoring and controlling
these very large and very far-flung networks.
[0013] The larger sizes of networks, in turn, mean that a
state-of-the-art network element management system must be able to
cope with thousands of network elements, each containing tens of
cards which each are programmable to switch hundreds of
channels.
[0014] A further pressure on element management systems is applied
by customer demand for fast response: a corporate user of bandwidth
which requests additional capacity will be severely hampered if the
response is not prompt.
[0015] The telecommunications network is never static, but is
continually changing, in response to operator inputs as well as to
equipment changes. Conventionally the operator inputs which command
changes have been stored in a log file; but this results in a large
text file which is extremely difficult to search. While in theory
such a large text file can be searched for debugging or to
ascertain the current state, in practice the present inventors have
found that this is difficult.
[0016] Conventional element management systems (EMSs) have been
vendor-specific, so that a network management system must interface
to multiple different EMSs. (A model of this interface structure is
shown in FIG. 1A.)
Background: Cross-Connect Management
[0017] The number of links in a complex cross-connect cannot
usefully be viewed at once, so an operator interface for
cross-connect management must provide some way to reduce the number
of links seen at once. This is typically done by using multiple
windows to view different subsets of links in detail. However, the
increasing number of windows means the operators have more
difficulty in bringing up the appropriate display view to see the
selected link in detail.
Background: Network, Service, and Business Management: TMN
[0018] The TMN architecture is a reference model for a hierarchical
telecommunications management approach. Its purpose is to partition
the functional areas of management into layers. See e.g. ITU-T
Recommendation M.3010; Divakara K. Udupa, TMN: Telecommunications
Management Network (1999); and the Internet-published tutorial
articles http://www.webproforum.com/acrobat/fund_telecom.pdf,
http://www.webproforum.com/acrobat/oss.pdf,
http://www.webproforum.com/ac- robat/tmn.pdf,
http://www.webproforum.com/acrobat/ems.pdf; all of which are hereby
incorporated by reference.
[0019] The TMN architecture identifies five functional levels of
telecommunications management: business management layer (BML),
service management layer (SML), network management layer (NML),
element management layer (EML), and the (increasingly intelligent)
NEs in the network element layer (NEL). TMN segregates (or at least
distinguishes) the management responsibilities based on these
layers. This makes it possible to distribute these functions or
applications over the multiple disciplines of a service provider
and use different operating systems, different databases, and
different programming languages. In the TMN architecture, the
element management layer is the only low-level interface to the
network elements, but needs to give the higher layers smooth access
to information about the network elements.
Background: CORBA
[0020] One important component of the software architecture for
modern telecommunications has been the object-oriented software
relations defined by CORBA (Common Object Request Brokered
Architecture). This standard is particularly useful in
telecommunications, where it provides a basic framework for
interfacing between element management functions and other
functions (e.g. network management software and system management
software functions).
Background: Optical Telecommunications Standards and
Terminology
[0021] The role of telecommunications network management is
changing due to new requirements for speed, increased bandwidth,
and capacity to carry video, digital, and internet data. To provide
the needed functions, protocols such as ATM, SONET, and SDH are
emerging. Network management systems must accommodate these new
technologies and standards.
[0022] The demand for bandwidth has driven many service providers
to use optical communication systems. A typical set of standards
fox optical synchronization and interconnectivity is SONET
(Synchronous Optical Network). SONET is a family of fiber-optic
transmission rates designed to transport many digital signals with
different capacities and to provide a design standard for
manufacturers. These design standards provide an optical interface
that allows interoperating of transmission products from different
multiple vendors, supports new broadband services, and allows
enhanced OAM&P (Operations, Administration, Maintenance, and
Provisioning).
[0023] SONET has a base rate of 51.84 Mbps, with higher rates being
multiples of the base rate. The architecture has four layers, these
layers being topped by ATM (Asynchronous Transfer Mode) layers. The
photonic layer is the physical layer and includes specifications
for the fiber optics, transmitter characteristics (such as
dispersion of the transmitter), and receiver characteristics (such
as sensitivity). The section layer converts electric signals to
photonic signals and creates SONET frames. The line layer performs
functions such as synchronization, multiplexing of data to SONET
frames, switching, etc. The path layer performs end to end
transport of data.
[0024] Open Systems Interconnection (OSI) is an internationally 5
accepted framework for communication standards between different
systems made by different vendors. The OSI model is designed to
create an open system networking environment where any vendor's
computer system can freely share data with other systems on the
network. The model organizes the communication process into seven
10 different categories and places these categories in a layered
sequence based on their relation to the user. Layers 7-4 deal with
end to end communications, and layers 3-1 deal with network
access.
Element Management System with Adaptive Interface Based on
Autodiscovery from Element Identifier
[0025] The present application describes a network element
management system which automatically configures itself, when an
operator enters a component identifier, for optimal full-featured
management of the identified component. This is preferably done by
an autodiscovery process, and not by any mere lookup. This provides
new efficiencies in an element management system which can provide
a fully functional and optimized interface to network elements from
many vendors in many versions.
BRIEF DESCRIPTION OF THE DRAWINGS
[0026] The disclosed inventions will be described with reference to
the accompanying drawings, which show important sample embodiments
of the invention and which are incorporated in the specification
hereof by reference, wherein:
[0027] FIG. 1 shows NETSMART connectivity to NEs.
[0028] FIG. 1a shows a network management diagram with vendors
using vendor specific or standard interfaces to communicate with a
multi-vendor network.
[0029] FIG. 1b shows the typical layer architecture for management
of telecommunication networks.
[0030] FIG. 2 shows NETSMART window layout.
[0031] FIG. 3 shows NETSMART topology with drop-down file menu.
[0032] FIG. 4 shows the filter dialog, a sample of NETSMART dialog
elements.
[0033] FIG. 5 shows the topology manager (with NEs created).
[0034] FIG. 6 shows the topology search NE dialog.
[0035] FIG. 7 shows the result of selection using the search NE
dialog.
[0036] FIG. 8 shows the link report in the topoloigy manager/
[0037] FIG. 9 shows OC-192 2F-BLSR.
[0038] FIG. 10 shows the configuration of the equipment tab
view.
[0039] FIG. 11 shows the configuration of the properties view.
[0040] FIG. 12 shows the systemadministration view from the
administration manager window.
[0041] FIG. 13 shows the address mangement view from the
administration manager window.
[0042] FIG. 14 shows the all-view of the address list.
[0043] FIG. 15 shows the NEU management view.
[0044] FIG. 16 shows the concept of installing generics from a
local machine.
[0045] FIG. 17 shows installation of generics from a remote
machine.
[0046] FIG. 18 show sthe remote memory backup and restore
window.
[0047] FIG. 19 shows the crossconnects: DS0 XC tab.
[0048] FIG. 20 shows the crossconnects: FASTLANE XC tab.
[0049] FIG. 21 shows the crossconnects: SONET XC tab.
[0050] FIG. 22 shows the crossconnects: SONET XC tab hairpinning
view.
[0051] FIG. 23 shows the crossconnects: SONET XC tab.
[0052] FIG. 24 shows the crossconnects: crossconnect report.
[0053] FIG. 25 shows the crossconnects: DS0 XC tab.
[0054] FIG. 26 shows the managing facilities dialog.
[0055] FIG. 27 shows the interface tab: INA attributes view.
[0056] FIG. 28 show sthe PM element view (from NETSMART menu):
monitors tab.
[0057] FIG. 29 shows the performance manager elelemt
view--registers tab.
[0058] FIG. 30 shows the performance manager element view--database
tab.
[0059] FIG. 31 shows the performance manger equipment view.
[0060] FIG. 32 shows the performance manager groups/facilities
view.
[0061] FIG. 33 shows the crossconnect report dialog (by
crossconnect type).
[0062] FIG. 34 shows the architecture components of NETSMART.
[0063] FIG. 35 shows the NETSMART process architecture.
[0064] FIG. 36 shows the a hardware architecture for one embodiment
of the present application.
[0065] FIG. 37 shows the NETSMART server architecture.
[0066] FIG. 38 shows a meta model class diagram.
[0067] FIG. 39 shows a meta base assembly class diagram.
[0068] FIG. 40 shows a meta base assembly state transition
diagram.
[0069] FIG. 41 shows a meta node class diagram.
[0070] FIG. 42 shows a meta assembly loading diagram.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
[0071] The numerous innovative teachings of the present application
will be described with particular reference to the presently
preferred embodiment (by way of example, and not of
limitation).
[0072] Overview of NETSMART.RTM.
[0073] NETSMART is a true carrier-class network management system
capable of managing very large Fujitsu-based SONET deployments
while simultaneously supporting many active users. NETSMART helps
build a business by providing the tools to monitor, provision, and
troubleshoot the network with unprecedented scalability, graphical
interface simplicity, and reliability. As with other user-friendly
network management software products, the NETSMART system has an
easy-to-use, intuitive graphical user interface (GUI) that allows
the user to display a hierarchical view of the network down to the
shelf and card level. NETSMART will also permit the user to obtain
graphical control over surveillance, provisioning, software
download (SWDL), remote memory backup (RMBU), and remote memory
restore (RMR). This feature-rich interface allows the user to
perform operational tasks without entering data or TL1 commands.
Point and click operations allow the user to accomplish the vast
majority of all tasks without typing.
[0074] The NETSMART system runs on SUN.RTM. Enterprise servers
sized to meet system requirements. It supports Fujitsu's FLM
add/drop multiplexers, FACTR.RTM. universal transport and access
platform (all the way down to DS0 level), FLASH.TM.-192 lightwave
add/drop multiplexers, and FLASHWAVE wavelength division
multiplexer (WDM).
[0075] NE Support
[0076] NETSMART supports many earlier NE releases. For those NEs
not directly supported by this version of NETSMART, NETSMART also
provides backward and forward NE compatibility.
[0077] Backward compatibility allows NETSMART to manage an NE as if
its software were at a higher release level than it actually
is.
[0078] Forward compatibility allows NETSMART to manage an NE as if
its software were at a lower release level than it actually is.
[0079] NETSMART also provides Fujitsu Generic Support (FGS) for
unknown Fujitsu NEs. FGS includes:
[0080] Login/logoff
[0081] Receive, store, and display alarms
[0082] Display of generic NE icon on the Topology Display
[0083] Allow/inhibit alarm reports
[0084] NETSMART Features
[0085] NETSMART combines the functions of both the element
management and network management layers of the Telecommunications
Management Network model to provide comprehensive management
capabilities to the users of Fujitsu networking products.
[0086] General Application Features
[0087] NETSMART provides the following general application features
as part of a comprehensive and robust element and network
management solution:
[0088] Management of up to 4000 NEs from a single server
platform
[0089] Support for OSI DCN connectivity
[0090] TL1 command line and batch file support
[0091] Generic NE icon capability
[0092] Distributed and scalable architecture
[0093] Support for up to 50 simultaneous users
[0094] Support for IP DCN connectivity
[0095] TL1 console allows users to monitor TL1 communication
between the NETSMART server and one or more managed NEs
[0096] Intelligent uninterrupted power supply (UPS) support for
greatly decreased start-up times after power failure and for
enhanced protection from file system corruption
[0097] Configuration Management
[0098] NETSMART provides the following configuration management
features to support easy and rapid provisioning and inventory
management for both individual NEs and entire transport
networks.
[0099] Flexible Topology Management
[0100] Topological link and physical link views
[0101] User-defined groups of NEs with the ability to easily move
NEs between groups
[0102] Tree-widget view of groups, similar to Windows.RTM.
Explorer, allowing easy viewing and manipulation of managed NEs
[0103] Tabular view of network information
[0104] Comprehensive Network Element Management
[0105] NE definition, profiles, and configuration autodiscovery
[0106] Add user-defined NE or group attributes
[0107] User-defined NE audit and reconciliation
[0108] Select autonomous messages to be allowed upon NETSMART
login
[0109] Manual or automatic database reconciliation; option to
update NE or NETSMART.
[0110] NE shelf display with visual indications of equipment
states
[0111] GUI-based provisioning of attributes and services states for
shelves, plug-in units, and facilities
[0112] GUI-based cross-connect management, providing comprehensive
management tools, including redline, DS0, hairpinning,
FASTLANE.TM., and transmux cross-connect management
[0113] Toolbar shortcuts (1-way, 2-way, 2-way add/drop, 1-way drop
and continue, 2-way drop and continue)
[0114] Bulk cross-connect operations
[0115] Ability to assign a name to cross-connects
[0116] DWDM wavelength management reports
[0117] Network Element Software Management
[0118] Remote NE software upgrades via OSI DCN
[0119] Remote NE database backup and restoration via OSI DCN
[0120] Ability to restore database to a different NE for rapid NE
turn-up
[0121] Remote NE software upgrades via IP DCN (FLASH-192 Release
4.2 and FLM 2400 Release 14.2BS only)
[0122] Remote NE database backup and restoration via IP DCN
(FLASH-192 Release 4.2 and FLM 2400 Release 14.2BS only)
[0123] Full-Featured Network Inventory Management
[0124] Network wide inventory of NEs, shown in FIG. 5: TID, NE
type, release level, audit state, DCN type.
[0125] NE level inventory reports: CLEI code, part number,
equipment service state, date of manufacture, etc.
[0126] Equipment find function: Network-wide search for CLEI code
or part number
[0127] Fault Management
[0128] NETSMART provides the following network surveillance and
troubleshooting features to allow fast and reliable tracking of
network alarms and to provide network operators with tools to
quickly and easily isolate network troubles.
[0129] Network Surveillance
[0130] An alarm banner at the top of the Topology window containing
summary alarm counts and one-click access to alarm reports
[0131] An active alarm list containing current alarms, standing
conditions, alarm acknowledgment information, and alarm record
annotations
[0132] An alarm history log showing cleared alarms and cleared
standing conditions.
[0133] A transient condition log maintaining records of transient
condition alarms (TCAs) received from managed NEs.
[0134] and transient conditions
[0135] Alarm-sensitive topology map and shelf views
[0136] Audible alarm indications
[0137] Customized alarm viewing options allowing user-defined
sorting, filtering, column display/placement, and report layout
[0138] One-click navigation from alarm record to Shelf view.
[0139] Network Troubleshooting
[0140] Protection switch operation and release
[0141] Facility loopback operation and release
[0142] STS path trace
[0143] DWDM section trace for the detection and isolation of errors
between DWDM fiber facilities
[0144] Performance Management
[0145] NETSMART provides the following performance management (PM)
features to support rapid and accurate detection, isolation, and
correction of network performance problems:
[0146] Enabling and disabling performance measurement collection
from the NETSMART GUI
[0147] Collection of both equipment- and facility-related measures
with a 15-minute resolution
[0148] Selection and display of PM information through customized
NETSMART reports
[0149] Printing and storage to external files through the NETSMART
GUI
[0150] Security Management
[0151] NETSMART provides the following security management
features, which allow quick and accurate administration of user
privileges while ensuring robust operation within a secure network
operations environment.
[0152] GUI-based functional user profile management allows the
customizing of roles through the combination of individual
application features.
[0153] Common user roles, such as server admin, client admin,
cross-connect user, and alarms user are predefined and available
out of the box.
[0154] GUI-based user account management, including the ability to
enable and disable accounts either on an on-demand or scheduled
basis, are provided.
[0155] Comprehensive security reporting, including reports listing
defined users, users with active sessions, and historical user
activity is provided.
[0156] Platform Requirements
[0157] The recommended platform configurations for NETSMART 1.2.2
are:
[0158] The server should be sized (CPU and memory) to meet
application requirements (number of NEs, number of users) with an
even number of CPUs and with 2 GB of memory for each pair of
CPUs.
[0159] The disk size, tape and monitor can vary.
Detailed Description of NETSMART
[0160] NETSMART is the next-generation network element management
software application for the Fujitsu FLM, FACTR.RTM., and
FLASH.RTM. product lines. In addition, Fujitsu network elements
(NEs) that are not fully supported by NETSMART, but conform to a
set of basic TL1 commands, are minimally supported for alarm and
configuration purposes. The NETSMART client/server configuration
supports up to 25 simultaneous users. Further details can be found
in the NETSMART 1.2 Installation and Administration Guide
(FJTU-320-940-150) and NETSMART 1.2 Users Guide (FJTU-320-940-100),
both of which are hereby incorporated by reference.
[0161] The graphical user interface (GUI) allows:
[0162] Display and update of network topology
[0163] Creation of uniquely named NE nodes, groups of NEs, and
links
[0164] Propagation of alarms to network topology icons
[0165] Management of NE configurations, including
cross-connects
[0166] Monitoring of alarms
[0167] Performance of troubleshooting procedures
[0168] Execution of remote NE memory backup and software
downloads
[0169] Management of user security
[0170] Retrieval of performance management reports
[0171] Wavelength management
[0172] NETSMART is designed to operate on a dedicated Sun.RTM.
server/workstation. The application uses the TL1 Operational
Support System (OSS) language over an Open Systems Interconnect
(OSI) protocol stack to communicate with remote NEs. Management of
NEs is accomplished over a combination of wide area networks
(WANs), local area networks (LANs), and data communications
channels (DCCs), as shown in the example configuration, FIG. 1.
[0173] Network Elements Supported
[0174] NETSMART software supports Fujitsu NE releases at three
different levels:
[0175] Full Support: All NETSMART functions are available.
[0176] Forward-Compatible Support:
[0177] Download forward-compatible release level to the NE
[0178] Log on and maintain a session with the NE
[0179] Monitor alarms from the NE (new alarm types may not be
recognized)
[0180] Display the shelf view of the NE
[0181] Provision the NE capabilities that were available in the
previous release
[0182] Perform remote memory backup and restore (if the NE supports
it)
[0183] Support other features previously supported
[0184] Backward-Compatible Support: NETSMART treats an earlier
release of an NE as the immediate later major release and processes
autonomous messages and command responses as if they were from the
more recent version of the NE. Commands that cannot be carried out
by the earlier release would be denied, but NETSMART would continue
to function.
[0185] Using NETSMART
[0186] The following section describes:
[0187] The common desktop environment (CDE);
[0188] How to start the NETSMART.TM. application on a server and a
client;
[0189] How to log on and off;
[0190] How to turn off the workstation.
[0191] Common Desktop Environment
[0192] The CDE is a basic component of the Sun UNIX platform and
provides access to start and stop the desktop applications, one of
which is NETSMART. The CDE toolbar is located at the bottom of the
computer screen. The server CDE toolbar has the Heartbeat icon on
the left that provides access to administration type functions.
These functions are covered in the NETSMART Administration and
Installation Guide. To learn about the various applications
available through the toolbar, access the Help menu by clicking the
books and question mark icon next to the trash can icon. Several
topics display that explain the CDE and its applications.
[0193] NETSMART User Levels
[0194] Three levels of NETSMART users are defined:
[0195] System Administrator--is the top-level UNIX operator. The
System Administrator is responsible for loading the NETSMART
software onto the server and other related tasks.
[0196] NETSMART User Administrator--is the top-level NETSMART
operator. The NETSMART User Administrator has all NETSMART
privileges within the application, including the ability to create
other NETSMART user accounts.
[0197] NETSMART User--is the operator-level user. The rights of
these users are defined by a role description, which is classified
by the NETSMART User Administrator. For example, an Alarms User is
restricted to using only those commands related to responding to
alarms. This user will not be allowed to perform
cross-connects.
[0198] Starting the NETSMART Application
[0199] A central station called the server runs the NETSMART server
application and, optionally, the client user interface(s). After
NETSMART is started on the server, it can be started on the
client(s). Each client can perform functions independently of the
other clients. Running NETSMART on a client has the following
effects:
[0200] Only the client initiating the request will receive a
response.
[0201] Autonomous alarms sent from the NE will be received by all
workstations.
[0202] Depending on the user security level, a user can configure
NEs; however, only one user at a time can access the following
functions: log on an NE, log off an NE, add NE, delete NE, software
download, and NE security.
[0203] NETSMART automatically logs on the NEs defined as autologon
before the user logs on NETSMART. As each NE is logged on, its
alarm status is downloaded to NETSMART.
[0204] Exiting the NETSMART Application
[0205] Exiting NETSMART closes the NETSMART user interface software
program. The network is not affected and the NETSMART server will
continue to monitor the network. Normally NETSMART runs
continuously on the Sun workstation. However, if it becomes
necessary to turn off the server, shutdown procedures are included
in the System Administration and Installation Guide.
[0206] The NETSMART.TM. user interface allows quick identification
of and response to alarm conditions in a monitored network. The
system uses windows and a mouse to minimize keyboard use and
training requirements for users.
[0207] NETSMART Window Layout
[0208] The Topology window (FIG. 2) displays after the user has
logged on the NETSMART application. As additional operations are
started up, additional windows can be opened, including multiple
occurrences of the same window. Windows can be resized and moved to
allow multiple views of the network. For example, a shelf that is
in an alarmed state can be displayed in one window and a listing of
related alarms can be displayed in another. FIG. 2 is an example of
different element positions in the major NETSMART windows. The
NETSMART window elements are:
[0209] Title bar--The title in the title bar can reflect the
top-level element, the component, and the federation being viewed
or the type of report or operation being performed. For example,
the topology map displays "NETSMART:federation1:Topology" to
reflect the top level of network elements, the component, and the
federation. If the view was switched to the DSO XC tab for an NE in
the Configuration Manager, the title reflects the NE TID, such as
"FLM150J." Log Managers will display the type of log, such as
"Activity Log."
[0210] 1. Menu bar--The menu bar wording defines categories of
NETSMART commands. Clicking and holding down the cursor on a menu
word displays a drop-down list of the available commands for that
category. Continuing to hold down the button, dragging the pointer
to highlight the desired command, and then releasing the button
causes the command to start executing.
[0211] 2. Toolbar--The toolbar displays the tools, which are
command buttons that provide quick access to frequently used
functions. For example, on the Topology window, this area is used
for NE logon, NE logoff, deleting an NE, adding a ring, and adding
a chain. On the right-hand side of the toolbar are the four alarm
condition tools. The alarm tools display the number of current
alarms and will flash if there are alarms that have not been
cleared or acknowledged.
[0212] 3. Tree--In the Topology window, this area displays a
hierarchical list of NEs and groups of NEs. In the Configuration
window, this area lists cards or facilities, depending on the
selection. In the Security window, this area lists users, roles, or
user sessions.
[0213] 4. Graphical area--This area is used to display large
graphical information such as network maps, shelf views, icons, or
reports. Dialog and message boxes can also be displayed on top of
this area.
[0214] 5. Icons--An icon is a graphic representation of an object.
Icons are described in legends that are available on related
windows and are described in Appendix A of this document.
[0215] 6. Status bar--The status bar is used to display useful
information such as the results of the last command or the current
status of the selected NE.
[0216] 7. Scroll bars--Scroll bars can be used to reposition a
portion of the window when the displayed information exceeds the
size of the window. Either clicking on an arrow or dragging the
scroll button will move the display.
[0217] NETSMART Window Elements
[0218] Several types of Windows elements may appear in the NETSMART
window area when commands are selected. These elements are:
[0219] 1. Dialogs--NETSMART uses dialogs to request information
from the user. After supplying the requested information, click on
a command button to execute the command. The Tab and SHIFT+Tab keys
move the cursor between entry fields in the box.
[0220] 2. Message Boxes--A message box is displayed to explain why
a command cannot be completed, to inform the user of an action in
progress, or to remind the user of the possible consequences of a
choice.
[0221] 3. Command buttons--Such as OK, Cancel, Apply, and Help
(located across the bottom of a dialog or message boxes) initiate
an immediate action when chosen.
[0222] 4. Reports--NETSMART can display data about NEs,
provisioning parameters, or conditions in a tabular form. Often
that data can be saved as a file and/or printed.
[0223] Menu Conventions
[0224] Many NETSMART commands are available from the toolbar or
from NETSMART menus (FIG. 3). There are three types of NETSMART
menus:
[0225] Main menu, the horizontal list of command names located
immediately below the window title
[0226] Associated drop-down menus for each main menu selection
[0227] Pop-up menus, usually displayed from a mouse right-click
action
[0228] NETSMART Dialog Elements
[0229] NETSMART dialog elements are the building blocks that are
used on the base dialog window to add functionality to each dialog.
Different dialogs contain different elements to reflect the
particular action(s) to be caused by activating the dialog
information.
[0230] Dialog Title
[0231] Most NETSMART dialogs have a dialog title or name displayed
in the top portion of the dialog border. In some instances, the
dialog title may contain the name of a selected element, rather
than a constant single title. Other dialogs may have both a
constant title and a variable name of a selected element.
[0232] Dialog Entities
[0233] A dialog may contain field labels, data/text entry fields,
radio buttons, check boxes, list boxes, drop-own menus, slider
bars, and command buttons.
[0234] The data/text entry field is designed for the user to type
information.
[0235] Radio buttons are mutually exclusive groups of buttons.
Selecting one button in the group will deselect all other buttons
in the group. Check boxes are used to indicate one or more
choices.
[0236] List boxes display a list of values from which the user can
select a single value or a group of values. Contiguous (adjacent)
groups of values are selected by holding down the SHIFT key while
selecting the values with the mouse. Noncontiguous groups of values
are selected by holding down the CONTROL key while selecting the
values with the mouse.
[0237] Drop-down menus are menus that display when a selection is
made from a list box (FIG. 4).
[0238] Slider bars are used to set levels. For example, the
NETSMART General User Preference dialog uses a slider bar to set
the number of minutes that NETSMART can be idle before the NETSMART
application screen locks.
[0239] Command buttons are located at the bottom of dialog boxes.
They are used to indicate what action NETSMART should take with the
information that the user entered in the dialog.
[0240] NETSMART Message Boxes
[0241] NETSMART message boxes are a form of dialog designed to
alert the user to an impending condition that may alter the current
state of NETSMART or NETSMART elements. Message boxes can be one of
three types:
[0242] Acknowledgement--displays a message that must be
acknowledged before continuing. This is usually a "wake-up" type of
message and is not associated with any potentially system-affecting
actions.
[0243] Decision--requires the user to decide how to proceed by
selecting a command button.
[0244] In Progress--Displays a message stating that an event is
occurring and a moving bar to indicate that the process is still
continuing. Closing the message box does not stop the process.
[0245] NETSMART Procedures
[0246] The Topology window displays when NETSMART is started for
the first time. If no network elements (NEs) have been created, no
NEs will display in the Topology window on start-up. FIG. 5 shows
Topology with NEs already created.
[0247] Note: Most of the main NETSMART.TM. windows are accessed
through the different software managers. These managers are listed
on and accessed through the NETSMART menu. Therefore, in the
following procedures, the relevant manager is indicated in the
first steps. If the proper manager window is not open, it can be
opened by selecting the NETSMART menu option and then clicking the
appropriate manager option.
[0248] A variety of methods can be used to perform these functions;
however, the procedures here are written to offer the most direct
methods. References to applicable windows are included in the
procedures. As NEs are created, they are, by default,
autodiscovered and logged on. NEs will not be automatically
discovered if the user specifically deactivates the default Auto
Logon field during NE creation.
[0249] Some dialogs are available from several different manager
screens because of their general nature. They allow the user to set
environmental preferences and lock/unlock the NETSMART screens for
security purposes.
[0250] Create and Manage NEs
[0251] This section describes how NEs are added, modified,
maintained and deleted in the NETSMART database. Only Fujitsu NEs
are supported in this release and they must have already been
physically configured in the network using either TL1 commands or
the FLEXR.RTM. interface. Fujitsu NEs that are not currently in the
supported list, but comply with Telcordia TL1 grammar, are
supported as generic NEs for commands such as ACT-USER,
RTRV-ALM-ALL, and INH-DBREPT-ALL.
[0252] Find NE or Group
[0253] This procedure helps to locate an NE or a group of NEs.
[0254] Add an NE
[0255] This procedure adds an NE definition to the NETSMART
database. However, to become active, the NE must already be
physically in the network and configured using either the FLEXR
interface or TL1 commands.
[0256] Clone an NE
[0257] Use the Clone NE dialog to make a copy of an existing NE
definition. Make changes to the clone to identify a new NE in the
network.
[0258] Edit NE Parameters
[0259] Editing an NE allows changes to be made to some basic NE
parameters in the NETSMART database.
[0260] Note: The contents of the User ID and Password fields cannot
be changed for an active NE. If these are to be changed, the NE
must be logged off and deleted and added once again with the new
User ID and Password information.
[0261] Delete an NE
[0262] Note: NEs should not be deleted during logon (the NE icon
background is white). Wait until the server has finished logging
on, then proceed with the delete operation. Deleting an NE during
logon could cause the NE to be deleted partially. If the NE is
partially deleted, you need to restart NETSMART to resolve the
problem.
[0263] Deleting an NE logs the user off the NE and removes it from
the NETSMART database. Deleting an NE also deletes any links
associated with the NE. The NE is still physically in the network,
but is removed from the NETSMART database.
[0264] Log On an NE
[0265] The user must log on an NE to perform configuration changes
and receive alarm information. Only NEs that are in an inactive
state can be logged on. If this is the first time this NE has been
logged on, autodiscovery is invoked (NETSMART communicates with the
NE database and loads the configuration information into the
NETSMART database). If you select Auto Logon in the Add NE dialog,
the log-on process will start as soon as you click Ok or Apply in
the Add NE dialog.
[0266] Log Off an NE
[0267] Logging off an NE ends communications between NETSMART and
this NE, but the NE is still defined in the NETSMART database and
is functioning in the network.
[0268] Audit an NE
[0269] Auditing an NE compares the information contained in the
NETSMART database with the information stored in the NE. The
results of the audit are displayed. When you audit an NE using the
following procedure, the Audit/Reconcile level that you set will
apply only to this audit. The Audit level that you set when you
created or edited an NE will apply only when the NE is
restarted.
[0270] View the NE State
[0271] The current state of any NE in the network can be
viewed.
[0272] Resynchronize an NE
[0273] Database resynchronization ensures consistency between the
NE database and the NETSMART database. Resynchronization involves
retrieving the entire database or distinct portions of that
database from the NE and comparing this information with that
contained in the NETSMART database. Either the NE database or the
NETSMART database may be the master data source, depending on the
type of data.
[0274] Resynchronization can be a time and resource intensive
process.
[0275] Managing Groups of NEs
[0276] Groups are used to organize NEs and partition the network. A
group icon can represent one or more NEs or groups of NEs. The
background color of the group icon reflects a highest
unacknowledged alarm level of NEs in the group.
[0277] Find a Group of NEs
[0278] Finding a single NE and a group of NEs is accomplished using
the same dialog.
[0279] Add a Group Definition
[0280] A group definition can be created and then a group of NEs
can be defined or moved into the new group.
[0281] Edit Group Parameters
[0282] Editing a group allows the user to change group parameters.
The group parent can also be changed either by dragging the group
icon under a new parent in the tree area or by typing a new parent
name in the Parent Group field on the Edit Group dialog.
[0283] Delete a Group Definition
[0284] Note: Deleting a parent group results in deletion of all
groups under the parent group.
[0285] This selection deletes a group definition from the NETSMART
database. If the group has NEs assigned, a warning is displayed and
must be acknowledged before the delete is completed. The group icon
will be removed from the topology map and tree structure.
[0286] Use a Different Background Map for Each NE Group
[0287] A different background map can be established for each group
of NEs so that when the group is selected, the NEs will be
displayed on an appropriate map. The map file(s) must be in "jpg"
format and must be accessible by the server. The file can be on a
server drive, on a CD ROM or on a floppy disk that has been placed
in the floppy disk drive (use the UNIX volcheck command to
recognize the floppy disk).
[0288] Search NE Dialog
[0289] The Search NE dialog displays whenever the related Search
button is selected in another dialog that requires an NE name be
provided (for example, in the Add Link dialog). The following
procedure assumes that you are currently working in a dialog with a
Search button. FIG. 6 shows the Topology Search NE Dialog.
[0290] Search Group Dialog
[0291] The Search Group dialog displays whenever you click on the
related Search button in another dialog that requires a group name
be provided (for example, in the Add NE dialog). The following
procedure assumes that you are currently working in a dialog with a
Search button.
[0292] Connect NEs (Links, Chains, Rings)
[0293] Network Elements (NEs) are connected to provide various
telecommunications services. Connection procedures add information
about the different types of connections to the NETSMART database.
They do not affect the NEs and physical network because the work
defined in these procedures must be completed by on-site field
technicians.
[0294] Within NETSMART, a single connection between two NEs is
referred to as a physical link. The display of this information on
the topology map is referred to as a logical link. There may be
more than one physical link between two NEs, but it will be
displayed as a single line on the topology map unless the
connections form a ring. If a ring is formed using only two NEs,
both links are displayed as angled lines, showing as a diamond
pattern.
[0295] In NETSMART, a link in one direction only is a
unidirectional link. A link in both directions is a bidirectional
link.
[0296] In NETSMART, a connection is fully protected only if there
are two separate routes and these routes do not share any link. A
connection is partially protected if there are two separate routes
but these routes do share a link.
[0297] Add a Link
[0298] A link represents a physical connection between two NEs,
including generic NEs. This procedure adds the link information to
the NETSMART database to represent the connections in the network.
It does not affect the networks.
[0299] Note: The selected group and NE will determine the contents
of the fields on the Add Link dialog.
[0300] Tasks:
[0301] 1 From the NETSMART Topology window, log on all NEs to be
included in the link.
[0302] 2 Select Add Link from the Edit menu or select the Link tool
from the toolbar.
[0303] 3 Using the Search button, select information in the
following fields:
[0304] Group 1--Use this field along with the Search button to
select a parent group.
[0305] NE1--Use this field along with the Search button to select
an NE. After the NE has been selected, available ports are
displayed in the Linkable Termination Ports section of this
dialog.
[0306] Group 2--Use this field along with the Search button to
select a parent group.
[0307] NE 2--Use this field along with the Search button to select
an NE. After the NE has been selected, available ports are
displayed in the Linkable Termination Ports section of this
dialog.
[0308] Linkable Termination Ports--This field displays a graphic
representation of the ports that are available for connection for
both selected NEs. If a connection is already in use, the box is
grayed out. If a link needs to be created to a generic NE, the
facility (for example, HS1-1, 1-P) port must be typed into the text
field at the top of the Linkable Termination Ports area, followed
by a carriage return.
[0309] Under each text field, a set of boxes is displayed. Each box
displays the RATE (for example OC3), AID (for example 1P) and two
direction buttons: Tx (Transmit) and Rx (Receive). Direction
buttons are used to make the connection. These buttons also
indicate if a port is unidirectional or bidirectional. If both Tx
and Rx are enabled, the port is bidirectional. If either Tx or Rx
is grayed out, the port is unidirectional.
[0310] 4 Make a connection between the NEs using one of the
following methods:
[0311] To create a unidirectional link from Tx to Rx, click on the
Tx button for a linkable port for the first NE to select it. Then
move the mouse to the linkable port for the other NE and click on
the Rx button if it is not grayed out. A line displays showing the
link, and the Tx and Rx buttons for those ports will be grayed
out.
[0312] To create a unidirectional link from Rx to Tx, click on the
Rx button for a linkable port for the first NE to select it. Then
move the mouse to the linkable port for the other NE and click on
the Tx button. A line displays showing the link, and the Tx and Rx
buttons for those ports will be grayed out.
[0313] To create two unidirectional links for a bidirectional port
at the same time, click in an area in the box outside the Tx or Rx
buttons for a bidirectional port for the first NE. Then move the
mouse to a bidirectional port for the other NE and click in an area
in the box outside the Tx or Rx buttons. A line displays showing
the link, and the Tx and Rx buttons for those ports will be grayed
out.
[0314] Once a link is successfully created, connection lines will
indicate link direction(s), as shown in FIG. 7. Additional links
can be added until all connections have been defined.
[0315] Note: To deselect a box or button, click on it.
[0316] 5 If the last connection needs to be removed (and Apply or
Ok has not been selected), click Undo. If all connections need to
be removed, click on Clear All.
[0317] 6 Click Apply to add this link information and leave the Add
Link window displayed. Click Ok to add the link information and
close the Add Link dialog.
[0318] 7 From the View menu, select Graphical to return to the
Topology map display. The link displays on the topology map.
[0319] Display Link Information
[0320] A link represents a physical connection between two NEs.
This is NETSMART database information and may not reflect actual
physical network connections. To display the link information for a
single link, double-click on the link or right-click and select
Link Report from the menu.
[0321] To display the link information for all the links, from the
NETSMART Topology window, select Links Report from the View menu.
The tabular view of the Links report (FIG. 8) displays.
[0322] Note the new features of the Link reports in this
release:
[0323] An EditName tool can be used to change a physical link
name.
[0324] Multiple selection of rows can be used with the Delete and
EditName operations.
[0325] To select a row on the Link Report, click on the row header
(numbered from 1 up to the number of physical links displayed) and
the row will become highlighted.
[0326] For multiple selections, two options are available:
[0327] Hold down the SHIFT key and click on the desired rows to
select a contiguous set of records.
[0328] Hold down the CTRL key and click on the desired rows to
select a non contiguous set of records.
[0329] To view the Display Link dialog for the two NEs in the
selected physical link, double-click on a row.
[0330] The Link Report toolbar offers the following functions:
[0331] Print Print up to 100 lines of the current information.
Refer to Printing Overview for more information.
[0332] Filter Display a dialog where you can specify criteria to
filter the information in the display. Refer to Filtering Tabular
Information for more information.
[0333] Sort Display a dialog where you can specify criteria to sort
the information in the display. Refer to Sorting Information.
[0334] Columns Display a dialog where you can specify information
to be shown or hidden. Refer to Setting Column Displays for more
information.
[0335] Deselect Deselect any selected rows.
[0336] Reload Update the display with information from the
database.
[0337] Delete Delete selected physical links from the database.
[0338] EditName Change the name for selected physical links. Use
the Edit Name dialog to type a new link name. Click on Ok to
confirm the change(s).
[0339] Edit a Link Name
[0340] The link name defaults to the format <TID
>:<port>:<Tx or Rx>::<TID>:<port>:<Tx
or Rx> of the connection (for example, FLASH-G:HS1-1:
Tx::FLASH-F:HS1-2:Rx). This link name can be changed to reflect
user preference.
[0341] Delete a Link
[0342] A link can consist of a number of connections between two
NEs. This procedure describes how to select an individual
connection within a link before deleting the information from the
NETSMART database. The procedure does not affect the actual
physical connections, so links are referred to as "topology
links."
[0343] Add a Chain
[0344] Chains use high-speed links to connect terminal and linear
NEs. This procedure describes adding the link information to the
NETSMART database. The actual physical connections are not
performed using this procedure. All NEs that will be included in
the chain must be logged on. Generic NEs cannot be included in a
chain because the NE type cannot be accurately determined. An NE at
the end of a chain must be configured as a terminal type of NE.
[0345] The Add Chain function is a "best-effort" operation. If two
or more of the NEs specified in the list of TIDs encounter a
compatibility error during ring creation, a dialog box will
display. This dialog reports which links were created successfully
and which links encountered errors. The chain will be displayed as
lines between NEs. To access the Add Chain dialog, first display
the Topology window, and ensure that all NEs targeted for the chain
have been autodiscovered.
[0346] When the dialog closes, the chain displays on the Topology
map. The corresponding links are added to the NETSMART database.
Those links that were created will be displayed on the Topology
map. For those links that generated errors, one or more of the
following self-explanatory error messages may display:
[0347] The configurations for the specified NEs are not
compatible.
[0348] High-speed links already exist between two or more of the
specified NEs.
[0349] High-speed rates are not compatible for two or more of the
specified NEs.
[0350] The directions of the high-speed ports are not compatible
for two or more of the specified NEs.
[0351] The payloads of the high-speed ports are not compatible for
two or more of the specified NEs.
[0352] The port sequences of the high-speed ports are not
compatible for two or more of the specified NEs.
[0353] Add a Ring
[0354] A ring provides alternative routing in case of a single
failure within a network. This procedure adds a ring definition to
the NETSMART database. The actual physical connections are not
performed using this procedure.
[0355] The Add Ring function is a "best-effort" operation. If two
or more of the NEs specified in the list of TIDs encounter a
compatibility error during ring creation, a dialog box will
display, reporting which links were created successfully and which
links encountered errors. Those links that were created will be
displayed on the Topology map. For those links that generated the
errors, one or more of the following self-explanatory error
messages may display:
[0356] The configurations for the specified NEs are not
compatible.
[0357] High-speed links already exist between two or more of the
specified NEs.
[0358] High-speed rates are not compatible for two or more of the
specified NEs.
[0359] Directions of the high-speed ports are not compatible for
two or more of the specified NEs.
[0360] Payloads of the high-speed ports are not compatible for two
or more of the specified NEs.
[0361] Port sequences of the high-speed ports are not compatible
for two or more of the specified NEs.
[0362] Build a BLSR
[0363] A bidirectional line switched ring provides alternative
routing in case of a single network failure as shown in FIG. 9,
OC-192 2F-BLSR. The BLSR provides ring protection switching by
detecting OC-192 line-level failures. Ring protection involves
bridging (transmitting identical traffic on both the working and
protection channels) and switching (selecting traffic from the
protection channel instead of the working channel). In a bridge and
switch, the 96 working time slots (1 through 96) are bridged onto
the 96 protection time slots (97 through 192) and transmitted away
from the failure.
[0364] Each 2F-BLSR can contain up to 16 nodes, labeled uniquely 0
through 15 in the ring. The ring topology table contains the order
of the nodes in the ring.
[0365] Squelching prevents traffic misconnections during node
failure by inserting STS-1 path AIS at the switching nodes into the
time slots. Each node on the ring has the identities of the entry
and exit nodes for all services passing through the node. The
squelch table keeps track of these entry and exit points by time
slot.
[0366] Only the channels that are added or dropped at the isolated
nodes or used for extra traffic need to be squelched. The squelch
table has an entry for each STS-1 time slot that the node is
terminating or passing through and the source and destination node
IDs.
[0367] Note: The squelch table may take some time to display
because the information is retrieved from the NE.
[0368] Add a Node to a BLSR
[0369] Nodes may occasionally need to be added to a BLSR. This
procedure adds a node to an existing BLSR definition in the
NETSMART database.
[0370] Delete a Node from a BLSR
[0371] Nodes may occasionally need to be deleted from a BLSR. This
procedure deletes a node from an existing BLSR definition in the
NETSMART database.
[0372] Set/Release Loopbacks
[0373] A loopback tests the transmit and receive capabilities of
the facilities at both remote and local terminals. A loopback test
causes the transmitted signal to be returned to the sending device
after passing through all or a portion of a data communications
link or NE.
[0374] Loopback testing is not available on all NE components. An
NE component is a facility, equipment and/or termination point. If
the NE component is available, right-click on the NE component in
the tree area to display a menu containing Loopback.
[0375] The NE must be placed in a maintenance state before a
loopback can be performed. Placing an NE in maintenance state is
not service affecting. However, once an NE has been placed in a
maintenance state, actions performed on that NE may be service
affecting (a loopback, for instance, is service affecting).
[0376] Set and Get a Path Trace
[0377] Path trace is a signal sent on the SONET overhead and is
only supported at the EML layer. It allows the user to assign a
unique path trace message to the transmit NE and the destination
NE.
[0378] Tracing a path involves assigning the outgoing trace message
(TRC) at the transmit NE, assigning the same message for the
incoming trace message (EXPTRC) at the path destination NE, and
viewing results in the incoming trace (INCTRC). If the message is
received correctly, the path trace is successful.
[0379] Note: Path tracing is not available on all NE
components.
[0380] Set and Get a Section Trace
[0381] In SONET, the terms section, line and path refer to the
subsections of a route that a signal takes when traveling from
origin to destination.
[0382] A section is the segment of fiber between two repeater NEs.
It is possible for a signal to be corrupted or degraded over the
span of a section. To troubleshoot a particular section for signal
quality problems, a test signal can be sent on the section and the
returned signal is compared to an expected trace. This is the
essence of section trace.
[0383] Use the Section Trace window to view and modify the
attributes related to section trace on a selected facility on an
NE.
[0384] Note: Section trace is not available on all NEs.
[0385] Protection Switching
[0386] Protection switching allows a transfer of service between
working and protection facilities or equipment. Protection
switching allows plug-ins to be removed and replaced without
affecting traffic. This feature also allows editing of the FFP
attributes of facilities and equipment within the optical facility
and equipment protection groups.
[0387] Note: Protection switching is not available on all
facilities and equipment.
[0388] Synchronize Timing
[0389] Timing attributes that will define the synchronization
timing source for the NE and the facility over which the output
clock signal is sent, can be set by the user. The synchronization
reference can also be switched to another source. Choices of
primary, secondary or internal clock references are available to an
NE.
[0390] Note: It is dangerous to set the NE timing reference to
internal clock timing reference. NEs using internal clock reference
can easily become out-of-sync with other NEs.
[0391] Note: Synchronization switching is not available on all
NEs.
[0392] Equipment Maintenance
[0393] NETSMART can be used to perform basic maintenance on the NE
hardware. These include:
[0394] Adding and deleting a shelf for an existing NE
[0395] Provisioning a plug-in unit
[0396] Modifying equipment parameters
[0397] Creating and deleting equipment protection groups (EPGs)
[0398] Add a Shelf to an Existing NE
[0399] The shelf should be installed on an NE before adding it to
NETSMART. A NETSMART user can add or remove shelves from an
existing NE. For instance, to add a new Narrowband shelf (NBS) to
an existing FACTR NE, NETSMART will need to autodiscover the shelf
and its components such as slots, cards, facilities and cross
connects.
[0400] Delete a Shelf from an Existing NE
[0401] A NETSMART user can remove shelves from an existing NE.
[0402] Note: All crossconnects must be removed before a shelf can
be deleted.
[0403] Provision a Plug-In Unit (Put In Service)
[0404] A main shelf for a FLASH-192 (Release 2.1) or a FACTR Common
shelf (CMS) or NBS can have some plug-in slots provisioned. The
shelf must already be installed, but the plug-in does not need to
be installed. Provisioning can also be accomplished by selecting
the card or port and changing the required attribute to In Service
(IS). FIG. 10 shows the Equipment Tab View for Provisioning.
[0405] Modify Equipment (Card and Port Attributes)
[0406] Individual cards and ports have attributes that can be
modified. These attributes are shown in blue on the Properties
window for the card or port. Values that are displayed in red are
critical. Changing a critical value will trigger an automatic
resynchronization.
[0407] Tasks
[0408] 1 Log on the NE to be provisioned.
[0409] 2 From the Configuration Manager window, select the
Equipment tab.
[0410] 3 Open the tree. From the tree area, select the card or port
to be modified. The view in the window changes to the Properties
view. Otherwise, select the card in the graphical shelf view, then
right-click to display a menu where you can select Display
Properties. The Properties view (FIG. 11) displays.
[0411] 4 Modifiable attributes are shown in red and blue. Black
text cannot be changed. In the Value column, click on the selection
to be changed. A button appears to the right of the text. Type or
select an option. Click on the button to display a drop-down list
of available options. Select an option from the list. Repeat this
step for all attributes that need to be changed for this card or
port.
[0412] 5 Click on the Modify tool, or select the Update option from
the Operations menu. The Modify Attributes Operation progress
dialog displays. When it closes, the attributes have been
changed.
[0413] Create or Delete an EPG
[0414] Redundant equipment provides a level of protection against
failure of certain plug-in units. For some types of NEs like
FLASH-192s, EPGs can be activated or deactivated using this
procedure. For FLM and similar NEs, EPG are automatically created
and cannot be deleted or modified.
[0415] Using the Administration Manager
[0416] The Administration Manager provides the ability to:
[0417] View administrative details about a selected NE.
[0418] Manage NE addressing.
[0419] View information about NE use.
[0420] Select Administration Manager from the NETSMART menu to
display administration management tabs.
[0421] Use the System Administration Tab
[0422] The System Administration tab displays details about the
different NETSMART processes that are running on the server. The
NETSMART version that is currently installed and the most recent
start time are shown in the heading.
[0423] Process monitoring can be enabled or disabled.
[0424] System monitoring checks the status of the servers (active
or inactive) You would disable monitoring only in extreme cases
such as an urgent need for resources. If monitoring is enabled (the
default setting) and a server goes down, NETSMART will detect
state, and issues a message and attempts to restart the server. If
monitoring is disabled and a server goes down, NETSMART will not
detect its state change and will not issue a message or attempt to
restart the server. FIG. 12 shows the Administration
Managerview.
[0425] Administration Manager Set Password Dialog
[0426] From the System menu, select the FTP submenu. There are two
cascading selections, Set Password, and Show Password. Select Set
Password to change the password for security protection during an
FTP transmission.
[0427] Use the Address Management Tab
[0428] The Address Management tab provides details about each NE.
Information includes the TID, the communications protocol, the
originating address type and the address.
[0429] All system-resolved or manually created OSI addresses are
defined as TARP (Target ID Address Resolution Protocol). All IP
addresses are defined as NETSMART. When the server restarts, all
NETSMART addresses are retained; all TARP addresses are lost and
must be re-resolved as part of the login process.
[0430] From the NETSMART System Administration window, select the
Address Management tab (FIG. 13).
[0431] Add an OSI Address
[0432] Every NE in a NETSMART network configuration must have an
OSI or an IP address. To enable communications within a ring
configuration, the gateway NE must be configured as an IP NE.
[0433] If the NE is not a gateway NE, set an OSI address using the
following procedure to configure an OSI NE:
[0434] View an OSI Address
[0435] Use this procedure to view an existing OSI address.
[0436] Add an IP Address
[0437] Every NE in a NETSMART network configuration must have an
OSI or an IP address. When enabling communications within a ring
configuration, the gateway NE must be configured as an OSI NE. If
the NE is not a gateway NE, set an IP address for the NE. FIG. 14
shows the Administration Address List--All View.
[0438] View an IP Address
[0439] Use this procedure to view an existing IP address.
[0440] Delete an IP Address
[0441] Use this procedure to delete an existing IP address.
[0442] Use the NEU Management Tab
[0443] The NETSMART hardware platform being used will support a
maximum number of NE units (NEUs). When this number is exceeded,
the database may not function properly. The NEU Management tab
provides information about this usage, allowing for monitoring and
managing network capacity.
[0444] The NETSMART NE Utilization window (FIG. 15) is divided into
three areas:
[0445] The top part of the window contains the window title. The
Max Capacity field shows the maximum capacity of the network. The
Current Utilization field shows the current NEU count for the
network. The Available Capacity field shows how many more NEUs can
be supported within this network.
[0446] The Summary portion of the window shows summary information,
including the Total Number Of NEs, the number Managed, the number
Logged-in, the number Logged-out and the number Not Managed.
[0447] The total number of NEs is the total count of NEs in the
system.
[0448] This includes NEs that are both managed and not managed.
Managed NEs are those that the NETSMART system is aware of and has
management control over. Logged-in are NEs that are logged in and
active in NETSMART. Logged-out are NEs that are logged out and
inactive. Not Managed are NEs that NETSMART is aware of but does
not manage or control.
[0449] The Details portion of the window provides detail
information, including the NE Type, the NE Weight, Number of NEs of
this type in this network and the NEU Count. The capacity of
NETSMART systems is based on Network Element Units (NEUs). Each
type of NE is assigned an NEU value based on the number of objects
to be managed.
[0450] Use the NEU Management view to monitor the number of NEUs
currently logged on the system. Once the maximum capacity is
reached, the system will deny creation of any new NEs.
[0451] Manage NE Software
[0452] This section provides procedures describing:
[0453] How to download software generics to an NE
[0454] How to perform NE memory backups
[0455] How to restore Service Database files to the NE
[0456] How to activate the software generics
[0457] NETSMART uses an intermediate database called Software
Repository to store and retrieve generic and service database
files. This section describes procedures you will perform to
install and extract software generic and service database files
using the Software Repository.
[0458] About the Software Repository
[0459] The Software Repository is an internal database that
NETSMART maintains in order to store software generic and service
database files. It provides a way to extract files from the
database to the file system. It also provides the means to remove
generic and service database files from the database.
[0460] The Software Repository works off-line with the NE, so it is
not necessary to log on to the NE to use this component. Once the
generic or service database is installed in the repository, it can
be downloaded to the NE using the Software Download (SWDL)
component.
[0461] About Remote Memory Backup and Restore (RMBU)
[0462] Remote Memory Backup and Restore (RMBU) is used to make an
NE memory backup and to restore the backup to the NE, when
required. To use the SWDL and RMBU components, you must log on the
NE. See Section Remote Memory Backup and Remote Memory Restore for
details about using these features.
[0463] An RMBU Scheduler feature lets you schedule RMBU in advance.
Scheduling options include weekly, monthly or one-time backups. See
the Installation and Administration Guide, Scheduling Remote Memory
Backups for NEs for details about using this feature.
[0464] Install Generics
[0465] Generics are software files that are specific to a
particular NE and version. To upgrade the NE to a different
version, the new version of the generics must be downloaded to the
NE. Generics are supplied by Fujitsu Network Communications, Inc.
(FNC) and are available to the customer:
[0466] On a floppy diskette
[0467] On a CD ROM
[0468] From a local or remote machine, using FTP file transfer
[0469] See the Installation and Administration Guide, Installing NE
Software Generics for procedures on installing software generics
from a CD ROM or floppy.
[0470] Install Generics from a Local Machine
[0471] Installing generics from a local machine is a single-step
process because generics were already copied into the NETSMART
client machine file system. Whether the installation is done using
FTP, floppy disk or CD ROM, the NETSMART server copies the generic
files into the repository. FIG. 16 illustrates the concept.
[0472] Install Generics from a Remote Machine
[0473] Installing generics from a remote machine is a single-step
process. Generics can be directly picked up from the remote
machine. In the following information, generics are available on a
remote machine (where the NETSMART client is not running) that is
connected to the network. FIG. 17 illustrates the concept of
installing generics from a remote machine. The following are
required before installing generics from the Client machine:
[0474] The remote machine must be running with the FTP Server
daemon active.
[0475] You need log on access to the machine.
[0476] You need to know the directory path on the remote machine
where the generics reside.
[0477] Extract Generics
[0478] If software generics are installed in the software
repository, they can be extracted. The local file system can be
extracted (where the NETSMART client is running) to any other
remote machine where you have log on access, or can be copied onto
a floppy disk or CD ROM for distribution purposes.
[0479] Remove Generics
[0480] If software generics are installed in the software
repository, they can be removed. Be sure to remove the generics
from the server machine.
[0481] Install the Service Database
[0482] You can install the service database files in the software
repository for downloading to the NE in extreme cases such as NE
memory corruption. To install the service database files, you need
to have a valid set of database files from a previous NE backup
created with the RMBU manager. Typically, if a memory backup of the
NE has been taken, its service database files are stored in the
software repository. It is possible that these files were extracted
to the file system. In this case, install the files into the
repository to download them to the NE.
[0483] Install from a Remote Machine
[0484] If the service database files are available on a remote
machine file system, they can be installed directly into the
software repository. The following are required before installing
generics from the NETSMART client machine:
[0485] The remote machine must be running with the FTP Server
daemon active.
[0486] You need log-on access to the machine.
[0487] You need to know the directory path on the remote machine
where the generics reside.
[0488] Extract the Service Database
[0489] If the service database files are installed in the software
repository, they can be extracted so that they can be saved on the
file system or copied onto a floppy disk or CD ROM for distribution
purposes. Extract the files to the local file system (where the
NETSMART client is running) or to any other remote machine where
you have log-on access.
[0490] Remove the Service Database
[0491] If the service database is already installed in the software
repository on the server machine, it can be removed. Be sure to
remove the service database, as others (those using NETSMART
servers) may want to use the machine.
[0492] Software Download
[0493] SWDL is used to download new generic software releases
(software generics) onto an NE using File Transfer Access and
Management (FTAM) and FTP. As a precondition for SWDL, the generic
should be installed in the Software Repository. For details about
installing the generic on the Software Repository, refer to Install
Generics for more details.
[0494] During the Software Download process, files are copied to
the RAM Disk on the NE in the first step and then onto the CPUs.
There are three different categories of NEs.
[0495] OSI NEs
[0496] IP gateway NE
[0497] IP subtending NEs.
[0498] Software Download on an OSI NE
[0499] The SWDL to Open Systems Interconnect (OSI) NEs is
accomplished in the following way.
[0500] The files are copied to the RAM Disk on the NE and then the
files are copied to the standby memory of the NE, or
[0501] Files are copied from Network Management System (NMS) to the
RAM Disk on the OSI NE using FTAM (for IP gateway NEs this is done
using FTP). At this stage, the software download is in a pending
state; it will become active when the software is activated. For
activation information, refer to "Configuring Scheduled Remote
Memory Backups".
[0502] Software Download on IP Gateway NE
[0503] SWDL on an IP gateway NE is accomplished in the same way as
the OSI NE.
[0504] Software Download on IP Subtending NE
[0505] For subtending NEs, an IP gateway NE is used as a
pass-through for the files to be copied from the NMS to the
destination NE. The procedure is accomplished in three steps.
[0506] 1. The files are copied from NMS to the IP gateway NE RAM
Disk.
[0507] 2. Then files are copied from the gateway NE RAM Disk onto
the IP subtending NE RAM Disk.
[0508] 3. Finally, files are copied from the subtending NE RAM Disk
to the corresponding CPUs on the IP subtending NE.
[0509] Consecutive Operations
[0510] From a user perspective, software download can be initiated
only on a single NE at a time. Initiating software download on
several NEs at the same time is not supported; however, you can
start software download on different NEs, running one after
another. Software download cannot be initiated on any NE while the
NE is performing a remote backup or a restore.
[0511] For IP subtending NEs, an IP gateway NE is used as a
pass-through for copying the files. An IP Gateway NE can be a
gateway for several NEs, meaning that all the NEs under this
gateway NE are dependent on this gateway NE for software management
operations.
[0512] Details Dialog
[0513] Once an NE is selected from the Software Download dialog and
the download is started, you can monitor the download. Select the
Details dialog by clicking the Details button in the Software
Download dialog.
[0514] The Details dialog displays the number of files to be
transferred in each step and also the number of files currently
transferring. Status strings on the Details dialog help you to
understand the operation.
[0515] An important string called Failure Reason is displayed on
the Details window if the SWDL is aborted. The failure reason will
help you to understand why the SWDL failed.
[0516] Abort Operation
[0517] After SWDL is started, the Software Download can be aborted.
Select the Abort button to display a status string on the SWDL
window, indicating that the abort has initiated. It may take
several minutes for the abort operation to be completed, depending
on the stage of the SWDL.
[0518] Once the abort is completed, the status string contents will
change to inform the user that the abort has completed. The message
will provide the time of the abort. You can now schedule an
activation and set the validation time. For more details about
activation, refer to "Configuring Scheduled Remote Memory
Backups".
[0519] Remote Memory Backup
[0520] Remote memory backup (RMBU) backs up the configuration
database on an NE to the NETSMART database. At any time, only the
last two versions of backup (per NE) are stored in the database.
The backed-up NE configuration information can either be extracted
onto any machine (with an active FTP daemon) or can be restored
from the NE database. Refer to Extract the Service Database for
details about extracting backed-up files onto a remote machine.
Refer to Remote Memory Restore for details about restoring the NE
database.
[0521] During the backup process, files are copied from CPUs to NE
RAM Disk. There are three different categories of NEs.
[0522] OSI NEs
[0523] IP gateway NE
[0524] IP subtending NEs
[0525] Remote Memory Backups from an OSI NE
[0526] A remote memory backup from an OSI NE is accomplished in the
following way:
[0527] The configuration files are copied to the RAM disk on the NE
from active memory.
[0528] The files are copied from the NE's RAM disk to NETSMART
using the OSI FTAM protocol.
[0529] Remote Memory Backup from an IP Gateway NE
[0530] A remote memory backup from an IP gateway NE is accomplished
in the following way:
[0531] The configuration files are copied to the RAM disk on the NE
from active memory.
[0532] The files are copied from the NE's RAM disk to NETSMART
using the FTP protocol.
[0533] Remote Memory Backup from an IP Subtending NE
[0534] A remote memory backup from an IP subtending NE is
accomplished in the following way:
[0535] The configuration files are copied to the RAM disk on the NE
from active memory.
[0536] Using the OSI FTAM protocol, the configuration files are
copied from the subtending NE's RAM disk to its gateway NE's RAM
disk.
[0537] The configuration files are then copied to NETSMART using
the FTP protocol.
[0538] Concurrent Operations
[0539] Backup can be initiated on up to 100 NEs. These NEs include
OSI NEs, gateway NEs and IP subtending NEs. If backup is initiated
on an IP subtending NE, this operation locks its gateway NE and
transfers files through the gateway NE. If backup is initiated on
multiple NEs within a ring, the gateway NE is shared across these
backup operations.
[0540] At any time, backup for 10 NEs can be initiated in parallel.
If backup for more than 10 NEs is requested, backups are
serialized.
[0541] During either of the SWDL/RMR (Remote Memory Restore)
operations on a gateway or subtending NE, you cannot initiate a
backup on any of the NEs in that ring. If the NE database is being
restored onto a gateway NE or a subtending NE, a backup cannot be
initiated on any of the NEs in that ring.
[0542] Details Dialog
[0543] The Details dialog displays the number of files to be
transferred in each step and also the number of files currently
transferring. Status strings on the Details dialog help you to
understand the operation.
[0544] An important string called Failure Reason is displayed on
the Details window if the SWDL is aborted. The failure reason will
help you to understand why the SWDL failed.
[0545] Abort Operation
[0546] You can select an NE and click the AbortBkp tool. Status
messages for this NE indicate initiation and completion of the
abort operation. FIG. 18 shows the Remote Memory Backup and Restore
Window.
[0547] Remote Memory Restore
[0548] If database corruption occurs on an NE, remote memory
restore allows a previously stored configuration database for that
NE to be used. The configuration files for an NE are stored either
from the backup operation or by installing NE database files from a
remote machine (with the FTP daemon running). Refer to Remote
Memory Backup for details about backing up NE configuration files
from an NE. Refer to Remote Memory Restore for details about
installing these files.
[0549] Log on the NE to be restored. During the restore process,
files are copied from NMS to NE RAM Disk and then onto CPUs. There
are three different categories of NEs.
[0550] OSI NEs
[0551] IP gateway NE
[0552] IP subtending NEs
[0553] Remote Memory Restore to an OSI NE
[0554] A remote memory restore to an OSI NE is accomplished in the
following way:
[0555] The configuration files are copied from NETSMART to the NE's
RAM disk.
[0556] The configuration files are copied from the RAM disk on the
NE to standby memory.
[0557] An activation of the standby memory needs to performed.
Refer to Software Activation for information on software
activation.
[0558] Remote Memory Restore to an IP Gateway NE
[0559] A remote memory restore to an IP Gateway NE is accomplished
in the following way:
[0560] The configuration files are copied from NETSMART to the NE's
RAM disk using the FTP protocol.
[0561] The configuration files are copied from the RAM disk on the
NE to standby memory
[0562] An activation of the standby memory needs to performed.
Refer to Software Activation for more information on software
activation.
[0563] Remote Memory Restore to an IP Subtending NE
[0564] A remote memory restore to an IP subtending NE is
accomplished in the following way:
[0565] The configuration files are copied from NETSMART to the
gateway NE's RAM.
[0566] The configuration files are copied from the RAM disk on the
gateway NE to the RAM disk on the subtending NE using the OSI FTAM
protocol.
[0567] The configuration files are copied from the RAM disk on the
subtending NE to standby memory.
[0568] An activation of the standby memory on the subtending NE
needs to performed. Refer to Software Activation for more
information on software activation.
[0569] Consecutive Operations
[0570] A restore can be initiated on only one NE at a time. If any
software management operation is running on any NE in a ring, you
cannot initiate a restore operation on any of the NEs in that
ring.
[0571] Backup Details Dialog
[0572] The Details dialog displays the number of files to be
transferred in each step and also the number of files currently
transferring. Status strings on the Details dialog help you to
understand the restore operation. An important string called
Failure Reason is displayed on the Details window if the restore
operation is aborted. The failure reason will help you to
understand why the restore failed.
[0573] Abort Backup Operation
[0574] While the restore process is active, you can select an NE
and click on the AbortBkp tool to abort the backup process. Status
messages for this NE indicate initiation and completion of the
abort operation.
[0575] Software Activation
[0576] After the generic or database is loaded into memory, you
need to schedule an activation.
[0577] Note: When activating either a software download or a remote
memory restore, activation time can be selected based on the NE
time. NETSMART reads the time from the TL1 response and places the
NE time plus 2 minutes in the Time field. This is to prevent the
SWDL or RMR activation time from being the exact current time. If
this was the case, by the time the user finished selecting
activation time, the time would now be in the past.
[0578] Managing Crossconnects
[0579] This section provides the procedures for creating NE
crossconnects. Crossconnect commands perform changes to the network
and update the NETSMART database. NE crossconnect management
provides the ability to modify the route for a circuit by changing
the NEs and links where a signal is carried. NETSMART's graphical
crossconnection feature lets you create crossconnects using a mouse
click interface and lets you view and report on an end-to-end
circuit through a SONET network.
[0580] Circuits may span multiple NEs and multiple interconnected
rings and virtual rings. You can select the appropriate
pass-through, drop-and-continue and service selector to assign.
[0581] Pending, active and errored connection states are supported.
A pending connection state is one in which the crossconnects
associated with a connection are defined in the database, but have
not been configured in the NEs. In an active connection, the
crossconnects associated with a connection are defined in the
database and also configured in the NEs. An errored connection
exists when there is a discrepancy between the definition of the
connection in NETSMART and the actual crossconnects in NEs.
[0582] Crossconnect windows can be accessed from the Configuration
Manager or by selecting Crossconnect Manager from the NETSMART
menu. The crossconnect windows all bear the title
"Configuration".
[0583] Add a DS0 Crossconnect
[0584] Use this procedure to create redline and regular DS0
crossconnects that drop off from the FACTR low-speed group (Group
3, 4, and 5) feeder to the Remote Digital Terminal (RDT)
interface/NBS. T1 crossconnects are created using the procedure
found in Add a T1 Crossconnect, below.
[0585] If the interface group is Integrated Network Access (INA) or
TR-008 Mode I or III, the next available DS0 time slot will be
presented. If the interface group is TR-303 or TR-008 Mode II, the
next Call Reference Value (CRV) number will be presented, and can
be overridden. NETSMART determines the DS0 facility AIDs and sends
the appropriate TL1 commands. FIG. 19 shows the DSO XC crossconnect
tab.
[0586] Add a T1 Crossconnect
[0587] Use this procedure to create the redline and regular DS1
feeder side of an interface group and the T1 facility in the FACTR
low-speed group (Groups 3, 4, and 5) feeder for DS0 services.
[0588] Crossconnects are limited by the following types of
interface groups:
[0589] TR-008 (Mode I)--Choose an available feeder DS1 (A, B, C, or
D).
[0590] TR-008 (Mode II or III)--Choose an available feeder DS1 (A
or C).
[0591] TR-303--Choose an available DS1 (1 through 28).
[0592] INA--The T1 crossconnects are automatically created between
the feeder of the INA interface group and the VT1 of the low-speed
15 group when the first DS0 crossconnect is created. You cannot
create them, but they can be displayed.
[0593] Tasks:
[0594] 1 Log on the NE to be crossconnected.
[0595] a. If Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the DS0 XC tab.
[0596] b. If the crossconnect needs to be a redline, click the
Redline tool or select Redline from the Create XC selection on the
Operations menu.
[0597] c. Click on the DS1 box to be connected, then drag the line
to the port and click again. A dotted black line appears.
[0598] Note: If the interface group or port (rectangle) is yellow,
then it is already in use (possibly at a different speed).
[0599] d. To complete the connection, click the Update tool or
select Update NE from the Operations menu. The Confirmation dialog
displays
[0600] Add a FASTLANE Crossconnect
[0601] FASTLANE crossconnects are used to map Ethernet and DS3 UNI
services into an STS-1. FASTLANE.TM. service is only available for
functional groups 4 and 5 configured as D3U or LAN bridge port
(LBP). At least one dedicated STS-1 channel across the SONET ring
must be available to carry the FASTLANE traffic. Two types of
FASTLANE crossconnects are supported:
[0602] Ethernet Port-Mapped Bridge (EPMB)--an entity connecting an
EPMB to a ring-side Asynchronous Transfer Mode virtual channel
(ATMVC)
[0603] DS3 User Network Interface (D3UNI)--an entity connected to a
particular ATMVC supported by a D3 UNI port to a ring-side ATMVC
Ethernet port provisioning and ATMVC provisioning are performed
independently of establishing crossconnects. Create ring-side
ATMVCs to create a path through the network between the switches.
The D3 UNI ATMVC ports are created by NETSMART. The value is shown
for the next available Virtual Channel Identifier (VCI). You may
override that channel selection.
[0604] Tasks:
[0605] 1 Log on the NE to be crossconnected
[0606] 2 If the Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the FASTLANE XC tab. The Fastlane XC view (FIG. 20)
displays.
[0607] 3 Select Create ring VC from the Operations menu or
right-click and select Create Ring VC from the drop-down menu. The
Ring VC creation dialog displays.
[0608] 4 Select or type values in the following fields:
[0609] Ring VC VPI (0-0)--Type the Virtual Path Identifier (VPI).
Only 0 is valid. Ring VC VCI (34-1023)--Type the VCI of the virtual
channel.
[0610] PCR--Type the Peak Cell Rate (PCR) per second.
[0611] SCR--Type the Sustained Cell Rate (SCR) per second.
[0612] Congestion Control--Select whether congestion control should
be enabled or not.
[0613] AAL-Type--Select the ATM Adaptation Layer (AAL). Only AAL5
is valid.
[0614] From NE TID--The starting NE TID is the default value.
[0615] To NE TID--Select the ending NE TID from the list.
[0616] 5 Click Ok to add the ring VC and close the Ring VC creation
dialog.
[0617] 6 Click Apply to add the ring VC and leave the Ring VC
creation dialog displayed.
[0618] 7 Click Cancel to cancel any changes and close the Ring VC
creation dialog. If Ok or Apply was selected, the new VC displays
in the middle of the FASTLANE XC window.
[0619] 8 Click on the appropriate port in the Group Configuration.
On the FASTLANE XC tab, drag the mouse to the appropriate ring VC,
then click again. A dotted line(s) will show the connection.
[0620] 9 To complete the connection, click the Update tool or
select Update NE from the Operations menu. The crossconnect
Confirmation dialog displays
[0621] Add a SONET Crossconnect
[0622] A SONET crossconnect connects STS or VT time-slot
facilities. A SONET crossconnect can connect a high-speed time slot
to another high-speed time slot (pass-through), a high-speed time
slot to a low-speed time slot (add and drop), and a low-speed time
slot to another low-speed time slot (hairpinning). Time slot rates
must match for all SONET crossconnects.
[0623] Note: For FLASH 192 2.x and 3.x NEs, not all AIDs can be
interconnected. Only those AIDs that fan out from a SONET line that
is green in color are open for crossconnects.
[0624] Tasks:
[0625] 1 Log on the NE to be crossconnected
[0626] 2 If the Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the SONET XC tab. The SONET XC view (FIG. 21)
displays.
[0627] 3 Select the type of crossconnect (OneWay, TwoWay,
OneWayBroadcast, TwoWayDropAndContinue, TwoWayAddAndDrop, or
Service Selector) from the Create XC option of the Operations menu
or by clicking on the corresponding tool.
[0628] Note: Not all types of crossconnect are available at all
times (depending on the NE type and the configuration).
[0629] 4 If the crossconnect also needs to be a redline, click on
the Redline tool or select Redline from the Create XC option on the
Operations menu.
[0630] 5 Click on the first STS or VT1 group to be connected, then
drag the line to the far-end STS or VT1 group and click. A dotted
line shows the connection. If a drop-type connection is required,
click on the first STS or VT1 group (left- or right-hand side),
then click on the drop port along the bottom of the window and
dotted lines will be generated (including the appropriate
right-hand group).
[0631] Note: The time slot rates on both ends of this crossconnect
must be equal. If the time-slot rectangle is yellow, then it is
already in use (possibly at a different speed).
[0632] 6 To complete the connection, click the Update tool or
select Update NE from the Operations menu. The crossconnect
Confirmation dialog displays
[0633] Add a Hairpin Crossconnect
[0634] A hairpin is a crossconnect between two low-speed SONET
termination points.
[0635] Note: Hairpin crossconnects are supported for FLASH XC MV
architecture. The FACTR or FLM 150 must have a TS1A-ENH2 (time slot
assignment) unit, which allows the low-speed crossconnects. The
system type must be linear or Unidirectional Path Switched Ring
(UPSR) and the NE device system parameter TSTYPE must be
provisioned as ENH2.
[0636] One-way, 2-way, bridge and roll crossconnects can be
created, modified and deleted. Creation and deletion of redline
crossconnects is supported. If a crossconnect is redlined, the
redline must be removed before deletion.
[0637] Tasks:
[0638] 1 Log on the NE to be crossconnected.
[0639] 2 If Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the SONET XC tab
[0640] 3 Select the Hairpinning option from the Operations menu.
The HairPinning view (FIG. 22) displays.
[0641] 4 Depending on the type of crossconnect, select the One way
or Two way tool or select the corresponding menu option from the
Operations menu. If the crossconnect also needs to be a redline,
click on the Redline tool or select Redline from the Create XC
option on the Operations menu.
[0642] 5 Click on the first group to be connected from the From TP
line, then drag the mouse to the appropriate group in the To TP
group and click again. A dotted line will appear.
[0643] 6 When all of the crossconnects have been defined, click on
the Update tool or select Update NE from the Operations menu.
[0644] 7 Verify the connections. If the connections are correct,
click Ok. If the crossconnect was created successfully on the NE,
the line(s) will change from dashed to solid. If the crossconnect
on the NE fails, the crossconnect lines will remain dotted. If
connections are not correct, click Cancel and then change the
connections. The Confirm Connection dialog displays, indicating the
success or failure of the crossconnect.
[0645] Add a One-Way Service Selector Crossconnect
[0646] The one-way service selector is used for the BLSR
configuration for FLASH-192 and FLM-2400 SONET NEs.
[0647] Tasks:
[0648] 1 Log on the NE to be crossconnected
[0649] 2 If Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the SONET XC tab. The SONET XC view (FIG. 23)
displays.
[0650] 3 Select the One Way service selector tool. Click on the
low-speed port, then click on the destination high-speed port. The
crossconnect displays as a dotted line.
[0651] Note: The default Service Selector and Holdoff times can be
changed at this time by right-clicking on a crossconnect and
selecting the appropriate menu item.
[0652] 4 To complete the crossconnect, click on the Update tool or
select Update NE from the Operations menu.
[0653] Perform a Bridge on an Existing Crossconnect
[0654] Bridge crossconnect functionality is supported for BLSR
configurations of FLASH-192 and FLM 2400 SONET NEs. By setting up a
bridge, traffic from one termination point is routed to two other
termination points. Bridge and roll operations are performed on two
NEs to complete the entire task. First do a bridge on a
crossconnect on one NE and then do the roll on the other NE. After
the roll is performed, clear the bridge on the first NE.
[0655] 1 Log on the NE whose path is to be modified.
[0656] 2 If Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the SONET XC tab. The SONET XC view displays.
[0657] 3 Select the 1-way drop crossconnect to be bridged.
[0658] 4 Click the Bridge tool or select Bridge from the Operations
menu.
[0659] 5 Select the destination time slot. The display will show
the new bridge connection as a dotted line on the window when the
operation is completed.
[0660] 6 To complete the connection, click the Update NE tool or
select Update NE from the Operations menu.
[0661] Perform a Roll on an Existing Crossconnect
[0662] Roll crossconnect functionality is supported for the
FLASH-192 and FLM 2400 SONET NEs. On an FLM 2400 SONET NE, this
functionality is available only when the NE is configured as a
BLSR. Rolling facilitates switching the source AID from one time
slot to another time slot without loss of signal. Traffic is
buffered by the NE during the roll operation.
[0663] The roll operation can be performed by selecting a 1-way
crossconnect and then clicking the Roll tool or by selecting the
Roll menu item from the Operations menu. After you select Roll,
rubber banding starts and you can select a new origination point. A
pending roll crossconnect is created You can then activate the roll
crossconnect, which results in deletion of the original
crossconnect and creation of a new roll crossconnect. Bridge and
roll operations are performed on two NEs to complete the entire
task.
[0664] First set a bridge on a crossconnect on one NE and then set
a roll on the other NE. After the roll is performed, clear the
bridge on the first NE.
[0665] 1 Log on the NE whose path is to be modified.
[0666] 2 If Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the SONET XC tab. The SONET XC view displays.
[0667] 3 Select the 1-way crossconnect to be rolled from.
[0668] 4 Click the Roll tool or select Roll from the Operations
menu. A prompt displays directing you to select the destination
time slot.
[0669] 5 Select the destination time slot. The display will show
the new connection as a dotted line on the window when the
operation is completed. The old connection will be displayed as a
solid line.
[0670] 6 To complete the connection, click the Update NE tool or
select Update NE from the Operations menu.
[0671] Crossconnect Confirmation
[0672] The same dialog displays to confirm all types of
crossconnects.
[0673] 1 To complete the crossconnect, click on the Update tool or
select Update NE from the Operations menu. The crossconnect
Confirmation dialog displays.
[0674] 2 Verify the connections. If the connections are correct,
click Ok. If the crossconnect was created successfully on the NE,
the line(s) will change from dashed to solid. If the crossconnect
on the NE fails, the crossconnect lines will remain dotted. If
connections are not correct, click Cancel and then change the
connections. The Confirm Connection dialog displays, indicating the
success or failure of the crossconnect.
[0675] 3 Click the Close button to close the Crossconnect Report.
FIG. 24 shows the Crossconnect Report.
[0676] Update the Crossconnect Name
[0677] Crossconnects are not given a name when they are created.
The name can be structured to conform to the user's own network
naming convention; however, crossconnect names must be
alphanumeric, with no special characters. Several crossconnects can
be updated at the same time.
[0678] Note: A crossconnect name must be alphanumeric and cannot
contain any special characters.
[0679] 1 Log on the NE with the crossconnect(s).
[0680] 2 If Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the SONET XC tab. The SONET XC view displays.
[0681] 3 Select the crossconnect that needs a new name. Select Set
Name from the Operations menu, or right-click on the crossconnect
and choose Set Name . . . . The Set Crossconnect Names dialog
displays.
[0682] 4 Type a new name.
[0683] 5 Select the Set All button to move the crossconnect name to
the Crossconnect Name field in the Set Crossconnect Names dialog.
Click Ok to close the Set Crossconnect Names dialog.
[0684] 6 The cross-connect displays as a dotted line. Click on the
Update tool. The Confirmation dialog displays. Verify that the
information is correct and click Ok.
[0685] 7 The Messages dialog box displays with the new name shown
in the table. Click Ok.
[0686] Adding Redline Designation to an Existing Crossconnect
[0687] Adding a redline designation to a crossconnect indicates
that it is a critical circuit and care should be taken when changes
or disconnects are issued that affect the crossconnect.
[0688] 1 Log on the NE with the crossconnect(s
[0689] 2 From the Configuration Manager, select the SONET XC tab or
DS0 XC tab, depending on the type of crossconnect to be redlined.
FIG. 25 shows the DS0 XC display.
[0690] 3 Select the crossconnect that needs to be redlined. Click
the SetRedl tool or select Set Redline from the Operations menu.
Multiple crossconnects can be chosen by holding down the SHIFT and
CTRL keys, then clicking on the crossconnect lines. The
crossconnect line will change to a dotted red line.
[0691] 4 To complete the redline designation, click on the Update
tool or select Update NE from the Operations menu.
[0692] Delete a Crossconnect
[0693] Most crossconnects can be deleted using this procedure. If
the crossconnect is redlined, the redlining must be removed, as
described this procedure.
[0694] 1 Log on the NE where the crossconnect is to be deleted.
[0695] 2 If Crossconnect Manager was selected from the NETSMART
menu, the Configuration window displays. In the Configuration
window, select the appropriate tab: SONET XC, DS0, or FASTLANE.
[0696] 3 If the crossconnect is redlined, the redline designation
must be removed first. Select the crossconnect and click the NoRed
tool or select Unset Redline from the Operations menu. Click on the
Update NE tool or select Update NE from the Operations menu. The
Confirmation dialog displays.
[0697] 4 Click Ok to remove the redline.
[0698] 5 Click on the crossconnect to be deleted. Multiple
crossconnects can be selected by holding down the CTRL and SHIFT
keys and then clicking on each crossconnect to be deleted.
[0699] 6 Click on the DelXC tool or select Delete XC from the
Operations menu. The crossconnect line changes from solid to
dashed, indicating a pending change of state.
[0700] 7 After all crossconnects have been marked for deletion in
the GUI, make the changes to the NE by clicking the Update tool or
select Update NE from the Operations menu. The crossconnect
Confirmation dialog displays.
[0701] 8 Verify that the appropriate crossconnects are listed, then
click Ok to complete the deletion. If the crossconnections are not
correct, click Cancel and reselect the connections. If you cancel
the deletion, click the Undo tool to reinstate the connection.
[0702] Changing SSDEF
[0703] The Service Selector Definition (SSDEF) is, by default, set
to Insert. To reset the SSDEF to Thru, perform the following
procedure:
[0704] 1 Log on the NE where the SSDEF is to be reset. Access the
appropriate crossconnect window.
[0705] 2 Right-click on a crossconnect to display a menu.
[0706] 3 Select Set SS to Thru. The menu selection Set SS to Thru
changes to Set SS to Insert. You can toggle this selection between
the two items. Only the inactive selection will display in the
menu..
[0707] Changing the Holdoff Timer Value
[0708] The holdoff timer is used to set the time interval after a
protection switch when the NE will check the traffic origin and
reset to that origin if possible. To change the holdoff timer
value, perform the following procedure:
[0709] 1 Log on the NE where the holdoff timer is to be set. Access
the appropriate crossconnect window.
[0710] 2 Right-click on a crossconnect to display a menu.
[0711] 3 Select Holdoff Timer. Type a value for the reset
interval.
[0712] Trace from a Time Slot
[0713] If you are viewing a crossconnect with one termination
point, but no crossconnect visible, you can discover the other end
of this crossconnect.
[0714] 1 Log on the NE. Access the appropriate crossconnect
window.
[0715] 2 Right-click to select a crossconnect and display a menu
where you will choose Trace XC. A label will display beside the
crossconnect termination point where you right-clicked. This label
identifies the other end of this crossconnect..
[0716] Manage Facilities
[0717] This section provides the procedures for defining and
managing facilities for FLASH-192, FLM and FLASHWAVE NEs. Primary
states for facilities are: In Service (IS), Out of Service
Autonomous (OOS-AU), Out of Service Management or Memory
Administration (OOS-MA) and Out of Service Autonomous Management
(OOS-AUMA). Facilities can also have a secondary state of Out of
Service Management Unassigned (OOS-MA:UAS) when they are manually
deleted.
[0718] Facilities can have secondary states of active (ACTI),
normal (NR), abnormal (ANR), standby-hot (STBH), supporting entity
outage (SGEO), facility failure (FAF), unassigned (UAS), and
automatic in service (AINS).
[0719] Add a Facility (FLASHWAVE or FLASH-192)
[0720] Use this procedure to add fiber facilities for a FLASHWAVE
or FLASH-192 NE.
[0721] Note: Facilities cannot be created unless supporting
equipment has been created.
[0722] Note: When creating or modifying OC-48/OC-192 facilities in
a Transponder type of FLASHWAVE NE a message will ask you to
provide directional attribute information. Always input the
attributes (UNI or BI, for example) in upper case.
[0723] 1 From any tab in the Configuration Manager, select the
Managing Facilities . . . option from the NE menu. The Managing
Facilities dialog displays (FIG. 26, Managing Facilities
Dialog).
[0724] 2 Click on the rate and select the rate from the Rate
drop-down list. Select the shelf from the Shelf drop-down list.
Select the facility in the Non-existing Facilities column. Click
the Create tool.
[0725] Note: If there are no nonexisting (deleted) facilities,
there will be nothing in this list
[0726] 3 If this facility has any key attributes whose value should
be specified at creation time, a dialog containing the key
attributes will display. Enter the values for these attributes and
click Ok.
[0727] 4 The selected attributes of the selected facility will
display in the Attributes table. Click the Create tool. A Manage
Facilities message box displays: Creating Facilities. The facility
will be moved from the Non-existing to the Existing column and will
be activated.
[0728] Modify a Facility
[0729] This procedure allows you to modify facilities.
[0730] Note: When creating or modifying OC-48/OC-192 facilities in
a Transponder type of FLASHWAVE NE a message will ask you to
provide directional attribute information. Always input the
attributes (UNI or BI, for example) in upper case.
[0731] 1 From the Configuration Manager, select the
Groups/Facilities tab.
[0732] 2 Select the facility from the expanded tree or from the
graphic area. The Attributes view displays. This display will vary
slightly, depending on the command origin (issued from the tree or
graphic area).
[0733] 3 Modify the required values shown in blue or red, then
click the Modify tool or select the Update option from the
Operations menu. Available operations include InServ, OOSMA, OOSMT,
InServ, Operate PSW and Release PSW (the particular operation(s)
available will depend on the facility). The same options can also
be chosen from the Operations menu.
[0734] 4 The values will be modified in the NE and the NETSMART
database Delete a Facility. This procedure allows you to delete
facilities for a FLASHWAVE or FLASH-192 NE.
[0735] Delete a Facility
[0736] 1 From any tab in the Configuration Manager, select the
Managing Facilities option from the NE menu. The Managing
Facilities dialog displays.
[0737] 2 Select the shelf from the Shelf drop-own list. Click on
the rate and select a rate from the Rate drop-down list. Select the
facility in the Existing Facilities column. Click the Create
tool.
[0738] Note: If there are no existing (created) facilities, there
will be nothing in this list.
[0739] 3 A confirmation dialog displays. Click Ok to delete the
facility. The facility will be moved from the Existing Facilities
to the Non-existing Facilities column and will be deactivated
[0740] Activate an FFP Group (FLASH-192)
[0741] Fiber Facility Protection (FFP) groups are available for
FLASH-192. The equipment and the facilities to support the FFP
group must already be created. A list of FFP pairs is displayed and
you will select the FFP to be created.
[0742] Note: Changing FFP groups may change system configurations,
which can cause system configuration inconsistencies.
[0743] 1 From any tab in the Configuration Manager, select the
Manage FFP option from the NE menu. The Manage FFP dialog
displays.
[0744] 2 Select the shelf from the Shelf drop-down list. Click on
the rate and select the rate from the Rate drop-down list. Select
the FFP in the Non-existing FFP column.
[0745] Note: The list will be empty If there are no nonexisting
(deleted) FFPs.
[0746] 3 Click the Create tool.
[0747] 4 The FFP will move from the Non-Existing FFP to the
Existing FFP column and will become active.
[0748] Modify (or View) an FFP Group
[0749] The FFP group attributes for NEs can be modified, by
performing the following tasks:
[0750] 1 From the Configuration Manager, select the FFP tab
[0751] 2 Select the FFP group from the expanded tree or
double-click on the FFP in the graphic area. The Attributes tab for
the group displays.
[0752] 3 Modify the required values shown in blue and red by
clicking on the value, then select the new option from the
drop-down list.
[0753] 4 Click the Modify tool to download the changes to the NE.
The changed values will be displayed in the Value column.
[0754] Deactivate an FFP Group (FLASH-192)
[0755] Active FFPs for a FLASH-192 can be deactivated, by
performing the following tasks:
[0756] 1 In any tab in the Configuration Manager, select the Manage
FFP option from the NE menu. The Manage FFP dialog displays.
[0757] 2 Select the shelf from the Shelf drop-down list.
[0758] 3 Select the rate from the Rate drop-down list.
[0759] 4 Select the FFP in the Existing FFP column.
[0760] 5 Select Delete from the Edit menu. The FFP will be moved
from the Existing FFP to the Non-Existing FFP column and will be
deactivated.
[0761] Managing Wavelengths
[0762] Use the NETSMART Wavelength Management feature to produce a
report about wavelength inventory in your network. The report
includes:
[0763] Wavelength (in nm)
[0764] Frequency (in THz)
[0765] Part number for narrowband optics or transponder card
AID
[0766] Wavelength availability and primary status
[0767] OCN WLR (Optical Carrier Level n Wavelength Received)
[0768] OCN OPR (Optical Carrier Level n Optical Power Received)
[0769] WCH OPT (Wavelength Channel Optical Power Transmitted)
[0770] WDM OPR (Wavelength Division Multiplexer Optical Power
Received)
[0771] WDM OPT (Wavelength Division Multiplexer Optical Power
Transmitted)
[0772] Note: To avoid confusion, the window display is static (is
not updated) once the view is requested. You must use the Reload
tool or the Reload NE List command to redisplay the window and view
updated information.
[0773] Wavelength Support
[0774] The following wavelengths are supported:
1 Wavelength (nm) Frequency (THz) 10G Part Number 1535.82 195.2 08
1536.60 195.1 09 1537.39 195 10 1538.18 194.9 11 1538.97 194.8 12
1539.76 194.7 13 1540.55 194.6 14 1541.34 194.5 15 1542.14 194.4
16.
[0775] Produce a Wavelength Inventory Report
[0776] The Wavelength Management window can be started from any
application with a NETSMART menu item.
2 Wavelength (nm) Frequency (THz) 10G Part Number. 1542.93 194.3 17
1543.73 194.2 18 1544.52 194.1 19 1545.32 194 20 1546.11 193.9 21
1546.91 193.8 22 1547.71 193.7 23 1548.51 193.6 24 1549.31 193.5 25
1550.11 193.4 26 1550.91 193.3 27 1551.72 193.2 28 1552.52 193.1 29
1553.32 193 30 1554.13 192.9 31 1554.94 192.8 32 1555.74 192.7 33
1556.55 192.6 34 1557.36 192.5 35 1558.17 192.4 36 1558.98 192.3 37
1559.79 192.2 38 1560.60 192.1 39
[0777] If you open this window from the Topology window, the
following selections are available:
[0778] Select a number of NEs.
[0779] Select a number of groups.
[0780] Select a number of NEs and groups.
[0781] Select the Network group.
[0782] If any of these selections are made, the Wavelength
Management window displays with only the selected FLASHWAVE
terminals.
[0783] Otherwise, all existing FLASHWAVE terminals are displayed To
produce a wavelength inventory report, perform the following
tasks:
[0784] 1 From the NETSMART menu, select Wavelength Management. The
Wavelength Management window displays.
[0785] 2 The list area contains a list of all FLASHWAVE terminal
NEs. Click on an NE to display its data.
[0786] 3 To filter the columns of the data display, select the
Filter tool from the toolbar.
[0787] 4 Click on the first button below the Field label. A list of
values to filter with displays. Values include Wavelength (nm),
Frequency (THz), Transponder or I0 G part #, AID, Status, OCN WLR,
OCN OPR, WCH OPT, WDM OPR, and WDM OPT. Click to select one of
these values.
[0788] 5 Once a filtering value has been selected, the Test button
becomes active. Click on the Test button to display a series of
values to test against for filtering; one of:
[0789] contains
[0790] !contains
[0791] starts with
[0792] !starts with
[0793] ends with
[0794] ends with
[0795] 6 Click to select one of the values listed above. Boolean
values can be used to filter by selecting one of and/or from the
Logic button.
[0796] 7 Once all filtering values are selected, click Ok to
redisplay the Wavelength Management values with the filter(s)
applied.
[0797] NGDLC Services
[0798] Next generation digital loop carrier (NGDLC) systems enable
carriers to provide integrated access between the customer premises
and the public network. NGDLC supports concentration of switched
traffic and grooming of non-switched traffic.
[0799] You may view and edit Next Generation Digital Loop Carrier
services including the TR-008, TR-303, or INA interface groups for
a FACTR NE. Each of these groups is created by autodiscovery.
Choose the mode (I, II, or III), the mapping sequence (D1D or D4)
and the bypass pair option (1 or 2). TR-303 defines an interface
between a central office switch and a remote terminal to handle all
call processing and operational functions for the DLC system.
TR-303 is a versatile interface supporting a large number of
subscribers and transport bandwidth, providing carriers with the
ability to choose a concentration ratio geared to traffic
engineering guidelines. For TR-303 DS0s, the NETSMART user can see
the assigned Call Reference Value (CRV), which is a number between
1 and 2016 that is assigned to a TR-303 DS0.
[0800] Edit a TR-008 or TR-303 Interface Group
[0801] This procedure edits TR-008 and TR-303 parameters for those
NEs that support these interfaces. It also places the interface in
service or, for maintenance purposes, out of service. Placing an NE
in maintenance state is not service affecting. However, once an NE
has been placed in a maintenance state, actions performed on that
NE may be service affecting (a loopback, for instance, is service
affecting).
[0802] 1 Log on the NE.
[0803] 2 From the Configuration Manager, select the Interface Type
tab. The Interface Type tab displays.
[0804] 3 A blue dot in the upper right-hand corner indicates that
an interface group has children. Double-click the TR-008 or TR-303
box in the graphical area or, in the expanded tree, select the item
that corresponds to the interface to be modified. The Attributes
dialog displays.
[0805] 4 Click on the interface option to be changed. Only
interface options displayed in blue can be changed. Select the new
option from the drop-down list
[0806] 5 Click the Modify tool or select the Update option from the
Operations menu to make the changes.
[0807] 6 Click to select the tool for the correct operation:
InServ, OOSMA, OOSMT. The same options can also be chosen from the
Operations menu.
[0808] Edit an INA Interface Group
[0809] This procedure allows the user to modify INA interface
attributes and put T1s in service or take them out of service for
maintenance. Placing an NE in maintenance state is not service
affecting. However, once an NE has been placed in a maintenance
state, actions performed on that NE may be service affecting (a
loopback, for instance, is service affecting).
[0810] 1 Log on the NE.
[0811] 2 From the Configuration Manager, select the Interface Type
tab.
[0812] 3 A plus sign to the left of an interface group indicates
that this interface group has children. Expand the tree list and
select the T1 to be modified.
[0813] 4 The Attributes dialog (FIG. 27) displays.
[0814] 5 Only interface options displayed in red or blue can be
changed. Select a new option from the drop-down list that is
displayed when the value is clicked.
[0815] 6 Click the Modify tool to complete the changes.
[0816] 7 Click to select the tool for the correct operation:
InServ, OOSMA, or OOSMT. The same options can also be chosen from
the Operations menu.
[0817] Performance Management
[0818] Performance Management is an optional feature and is started
using a different NETSMART command than the regular startup
command. If you cannot access this feature, please contact your
NETSMART administrator. For information about enabling and
disabling Performance Management, refer to "NETSMART Optional
Features"in the NETSMART Installation and Administration Guide
(FJTU-320-940-150).
[0819] A NETSMART user needs a way of accessing the PM Monitoring
parameters on a Network Element (NE) to determine how an NE is
performing in the network. The PM feature provides the mechanism
for the user to query and set PM Monitoring parameters on one or
more NE(s). A comprehensive listing of PM parameters for each NE
can be found in the appropriate NE manual. Most PM operations may
be applied to one or more NE(s), to multiple cards or facilities on
a single NE, or to a single card or facility on a single NE. Use
Performance Manager to:
[0820] Enable and disable a performance monitoring report
[0821] Retrieve performance monitor reporting status
[0822] Initialize the performance registers for an NE
[0823] Set individual threshold values
[0824] Retrieve current threshold values
[0825] Retrieve historical performance data
[0826] Operations that can be applied only to a single card or
facility on a single NE are:
[0827] Setting of individual threshold values
[0828] Retrieval of current threshold values
[0829] Retrieval of performance data
[0830] Management Procedures
[0831] This section describes the procedures for using the
Performance Manager. Performance Manager is supported for the
following NEs:
[0832] FLASH-192 (02.03)
[0833] FLASH-192 (04.02)
[0834] FLASHWAVE (02.01)
[0835] FLASHWAVE (01.03)
[0836] FLM 2400 ADM (14.02S).
[0837] FLM 2400 ADM (14.02BS)
[0838] FLM 600 ADM (14.02)
[0839] You can display the Performance Manager window in three
different views, depending on how the window is accessed. Views
include: Element View, Equipment View and Groups/Facilities
View.
[0840] Element View: Accessing Performance Manager from the
Topology window displays the Element View.
[0841] Equipment View: Accessing Performance Manager from the
Configuration Manager--Equipment Tab displays the Equipment
View.
[0842] Groups/Facilities View: Accessing Performance Manager from
the Configuration Manager Groups/Facilities tab displays the
Groups/Facilities View.
[0843] Performance Manager Element View
[0844] To display Performance Manager in Element View, select an NE
or several NEs in the Topology window and then select Performance
Management from the NETSMART menu. If no NEs are selected, a list
of available NEs will be displayed in the Performance Manager
window after it is launched. The view is divided into two main
parts. The Selection area in the top portion of the view displays
selected elements in the Selected Elements list. Radio buttons to
the right of the Interval label are used to define a monitoring
interval. The bottom portion of the view displays monitoring
data.
[0845] Start and Stop Monitoring
[0846] Note: If the Performance Manager was started from a selected
NE or NEs, there will be no elements in the Available Elements list
and the selected NE(s) will be displayed in the Selected Elements
list. If you started Performance Management from the NETSMART menu
with no NE selected, all NEs will be displayed in the Available
Elements list. The following information assumes that Performance
Management was selected from the Operations menu with no NE
selected (all NEs will appear in the Available Elements list).
[0847] 1 To begin monitoring, select the Monitors tab in the
Performance Manager window. This is the default tab for the Element
view.
[0848] 2 To select NEs to monitor, select an item in the Available
Elements column and use the Add button to add it to the Selected
Elements column.
[0849] 3 To remove an item from the Selected Elements column,
highlight the item in the Selected Elements column and click the
Remove button. After the in-progress message bar disappears, the
entry is added to the monitoring data area. Verify the status of
the initialization in the third column.
[0850] 4 To add all items to the Selected Elements column, click
the Add All button.
[0851] 5 To remove all the items in the Selected Elements column,
click the Remove All button. After the in-progress message bar
disappears, the entry stays in the list, but the status is changed
to Disable.
[0852] Note: When it is impossible to use a selection, that
selection is grayed-out. For example, in PM Element View from NE):
Monitors Tab the Add and Add All buttons cannot be used because
there is nothing in the Available Elements: list to add. The Remove
button cannot be used until an element in the Selected Elements:
list is selected.
[0853] 6 Define the interval for monitoring using the Interval
radio button. Options are 15 Min. (15-minute intervals) or 1 Day.
The default value is 15 minutes. If you select 15 Min., data is
retrieved from the NE 15-minute registers. If you select 1 Day,
data is retrieved from the NE 1-day registers
[0854] 7 Click the Mon On tool in the toolbar or select Turn
Performance Monitoring On from the Operations menu (FIG. 28).
[0855] 8 To stop monitoring, select the Monitors tab and then click
the Mon Off tool in the toolbar or select Turn Performance
Monitoring Off from the Operations menu.
[0856] Initialize Registers
[0857] To reset all registers to zero values, you will initialize
the registers. To initialize registers:
[0858] 1 Select the Registers tab in the Element view (FIG.
29).
[0859] 2 To select NEs to initialize, select an item in the
Available Elements column and use the Add button to add it to the
Selected Elements column.
[0860] 3 To remove an item from the Selected Elements column,
highlight the item in the Selected Elements column and click the
Remove button.
[0861] 4 To add all items to the Selected Elements column, click
the Add All button.
[0862] 5 To remove all the items in the Selected Elements column,
click the Remove All button.
[0863] Note: When it is impossible to use a selection, that
selection is grayed out. For example, in PM Element View (from NE):
Monitors Tab the Add and Add All buttons cannot be used because
there is nothing in the Available Elements: list to add. The Remove
button cannot be used until an element in the Selected Elements:
list is selected.
[0864] 6 Select the Init tool in the toolbar or select Initialize
Performance Registers from the Operations menu. Selecting this
option will initialize all the registers in the NEs to zero
(Initialized
[0865] Retrieve Performance Data
[0866] Occasionally you will want to retrieve performance data for
reporting or analysis. To retrieve performance data, perform the
following tasks:
[0867] 1 Select the Database tab in the Element view (FIG. 30).
[0868] 2 Select the element(s) from the Available Elements
list.
[0869] 3 Use the Add button to add it to the Selected Elements
column.
[0870] 4 To remove an item from the Selected Elements column,
highlight the item in the Selected Elements column and click the
Remove button.
[0871] 5 To add all items to the Selected Elements column, click
the Add All button.
[0872] 6 To remove all the items in the Selected Elements column,
click the Remove All button.
[0873] Note: When it is impossible to use a selection, that
selection is grayed out. For example, in PM Element View (from NE):
Monitors Tab the Add and Add All buttons cannot be used because
there is nothing in the Available Elements: list to add. The Remove
button cannot be used until an element in the Selected Elements:
list is selected.
[0874] 7 Select or type values in the following fields:
[0875] Interval--Displays the time period interval. Possible
options are 15 Min. or 1 Day. The default is 15 minutes. If you
select 15 Min. the collected data will be divided into 15-minute
periods. If you select 1 Day, the collected data will be reported
in 1-day periods.
[0876] NMS Start Date--Select the date when NETSMART started
receiving data from the NE. A default format is provided.
[0877] NMS Start Time--Select the time when NETSMART started
receiving data from the NE.
[0878] NMS End Date--Select the date when NETSMART stopped
receiving data from the NE.
[0879] NMS End Time--Select the time when NETSMART stopped
receiving data from the NE.
[0880] 8 Select Reload from the Operations menu or click the Reload
tool from the toolbar to start retrieving data.
[0881] Performance Manager Equipment View
[0882] To display the Performance Manager Equipment view, select a
card in the Configuration Manager Equipment tab and then click on
the Retrieve tool in the toolbar. Otherwise, right-click to display
a pop-up menu and then select Display PM from the pop-up menu. If a
card does not have PM registers, the PM tool will not be displayed
in the toolbar FIG. 31 shows the Performance Manager Equipment
view. The Equipment view displays only the Registers tab and
facilitates setting register thresholds and retrieving current
performance registers. Fields in the display include:
[0883] NMS Time--NETSMART time.
[0884] NE Time--The time on the NE.
[0885] AID Type--Type of Access Identifier.
[0886] AID--Access Identifier name.
[0887] Register--Register name.
[0888] Val ue--Value of the register that was retrieved.
[0889] Range--Allowable range for the register Value.
[0890] Threshold--Indicator to the NE to regenerate the threshold
report if the threshold was exceeded.
[0891] Default Threshold--When an NE is first started, this is the
default value set by the NE. This value can be reset using the
procedure described in "Set Threshold".
[0892] Validity--This value is valid only for FLASH-192 and
FLASHWAVE NEs. Under normal operating conditions, this value should
be FALSE. PM registers are accumulated in 15-minute intervals; if
any data being reported is not for the full 15-minute interval this
value will be reported as TRUE.
[0893] Location--This value indicates where the data is coming from
(near-end or far-end). Equipment registers will always be
far-end.
[0894] Direction--For equipment, this will always report N/A as the
physical characteristics of equipment have no direction. Typically
the value reported for facilities will be Tx or Rx.
[0895] Time Interval--This value is always N/A for equipment. For
facilities the time reporting interval will be displayed as either
15 MIN or 1 DAY.
[0896] Index--This value will always be 0 for equipment. For
facilities, the current register (0) plus previous registers 1 to
32 will be displayed. The Monitors and Database tabs cannot be
selected, because equipment registers are not counters; they are
current operating levels for items such as Laser Bias Current
Normalized (LBCN). Because of this, monitoring cannot be turned on
or off and the database will not contain any historical data.
[0897] Set Threshold
[0898] Performance monitoring registers can, potentially, be
collected for thousands of circuits, creating an overwhelming
amount of data. To limit this data, thresholds for data collection
can be set. If these thresholds are not crossed, the assumption is
that the NE performance is acceptable. A default threshold value
exists for each register. The threshold for any register can be set
and changed. To set thresholds:
[0899] 1 Select equipment from the Available Equipment list and
click the Add button to add the equipment to the Selected Equipment
list
[0900] 2 Select a numbered row in the report and then click the Set
tool in the toolbar. The Set Thresholds dialog displays.
[0901] 3 Type a new value for the threshold. Threshold ranges are
NE-dependent and are displayed when you select the row that you
will set registers for. You can also refer to the System
Engineering section of the Fujitsu Network Communications web site
for the TL1 threshold value specification for each NE.
[0902] 4 Click OK to select the threshold and close the dialog.
[0903] Retrieve New Data
[0904] To retrieve new performance data:
[0905] 1 Select equipment from the Available Equipment list and
click the Add button to add them to the Selected Equipment
list.
[0906] 2 Select the Reload tool from the toolbar. The Reload tool
updates the report for the equipment contained in the Selected
Equipment list and for the values specified in the Location,
Direction, Time Interval, and Index fields.
[0907] Performance Manager Groups/Facilities View
[0908] To display Performance Manager in the Groups/Facilities
View, select a facility in the Configuration Manager
Groups/Facilities tab and then click on the Retrieve tool in the
toolbar. Otherwise, right-click to display the pop-up menu and then
select Display Performance from that pop-up menu. The Monitor tab
is the default initial display.
[0909] If a facility has PM registers, when that facility is
selected, the PM tool will become active in the toolbar. FIG. 32
shows the Performance Manager window in the Groups/Facilities view.
The Groups/Facilities view contains the Monitors, Registers, and
Database tabs and allows you to turn reporting on or off, to
retrieve current PM registers from the facility and to retrieve
historical data from the database. The Monitors tab is grayed-out
on any group/facility that does not support performance monitoring.
By default, the facility selected in Configuration Manager is the
one displayed in Performance Manager and the Interval option is set
to 15 Min. (the default). Fields in the display include:
[0910] NMS Time--NETSMART time.
[0911] NE Time--The time on the NE.
[0912] AID Type--Type of Access Identifier.
[0913] AID--Access Identifier name.
[0914] Register--Register name.
[0915] Value--Value of the register that was retrieved.
[0916] Range--Allowable range for the register Value.
[0917] Threshold--Indicator to the NE to regenerate the threshold
report if the threshold was exceeded.
[0918] Default Threshold--When an NE is first started, this is the
default value set by the NE. This value can be reset using the
procedure described in "Set Threshold".
[0919] Validity--This value is valid only for FLASH-192 and
FLASHWAVE NEs. Under normal operating conditions, this value should
be FALSE. PM registers are accumulated in 15-minute intervals; if
any data being reported is not for the full 15-minute interval this
value will be reported as TRUE.
[0920] Location--This value indicates where the data is coming from
(near-end NEND or far-end FEND).
[0921] Direction--Typically the value reported for facilities will
be Tx or Rx.
[0922] Time Interval--For facilities the time reporting interval
will be displayed as either 15 MIN or 1 DAY.
[0923] Index--For facilities, the current register (0) plus
previous registers 1 to 32 will be displayed
[0924] Start and Stop Monitoring
[0925] 1 To start monitoring, select the Monitors tab in the
Performance Manager Groups/Facilities view. The reporting status is
automatically retrieved and displayed.
[0926] 2 To select NEs for monitoring, select an item in the
Available Facilities list and use the Add button to add it to the
Selected Facilities list. By default, the facility that is selected
when Performance Manager is launched is already in the Selected
Facilities list.
[0927] 3 To remove an item from the Selected Facilities column,
highlight it in the Selected Facilities column and click the Remove
button.
[0928] 4 To add all the items to the Selected Facilities column,
click the Add All button.
[0929] 5 To remove all the items in the Selected Facilities column,
click the Remove All button.
[0930] 6 Choose the location by selecting one of the Location radio
buttons. Possible choices are NEND (near-end) or FEND
(far-end).
[0931] 7 Choose the direction by selecting one of the Direction
radio buttons. Possible choices are Receive, Transmit or NA (Not
Applicable). This list is dynamically updated based on the selected
facility.
[0932] 8 Select the interval for monitoring using the Interval:
radio button. Options are 15 Min. or 1 Day. The default is 15
minutes. If you select 15 Min., data is retrieved from the NE
15-minute registers. If you select 1 Day, data is retrieved from
the NE 1-day registers.
[0933] 9 In the Start Index and End Index fields, select a value
between 0 and 32 for registers. 0 is the current register and there
may be up to 32 previous registers. The End Index value must always
be higher than the Start Index value.
[0934] 10 Click the Mon On tool in the toolbar to start
monitoring.
[0935] 11 To stop monitoring, select the Monitors tab and then
click the Mon Off tool in the toolbar
[0936] Initialize Performance Registers
[0937] To initialize performance registers:
[0938] 1 Select the Registers tab in the Groups/Facilities
view.
[0939] 2 Select the Init tool in the toolbar. Selecting this option
will initialize all the selected NE facility registers to zero.
[0940] Retrieve Register Data
[0941] To retrieve register data, select the Registers tab in the
PM Groups/Facilities view. Once this tab is selected, a command is
sent to the NE to retrieve register data for the selected facility.
This data is displayed using the default parameters for Location,
Direction, Interval and Start and Stop Indexes.
[0942] Reload Register Data in the Report
[0943] To reload new register data while in the Registers tab:
[0944] 1 Select the facilities from the Available Facilities list
and click the Add button to add them to the Selected Facilities
list.
[0945] 2 Choose the location by selecting one of the Location radio
buttons. Possible choices are NEND (near-end) or FED (far-end).
[0946] 3 Choose the direction by selecting one of the Direction
radio buttons. Possible choices are Receive, Transmit or NA (Not
Applicable). This list is dynamically updated based on the selected
facility.
[0947] 4 Select the interval for monitoring using the Interval
radio button. Options are 15 Min. or 1 Day. The default is 15 Min.
If you select 15 Min., data is retrieved from the NE 15-minute
registers. If you select 1 Day, data is retrieved from the NE 1-day
registers.
[0948] 5 In the Start Index and End Index fields of the Registers
tab, select a value between 0 and 32 for registers. 0 is the
current register and there may be up to 32 previous registers. The
End Index value must always be higher than the Start Index value.
These choices may be dynamically updated, depending on the selected
type of facility.
[0949] 6 Select the Reload tool in the toolbar. Selecting this tool
will reload the register data for the selected facility for the
index selected in Step 2 and will display the results in the
window..
[0950] Set Threshold
[0951] You can set and change the current threshold for any
register. To set thresholds, from the Performance Manager:
[0952] 1 Select the Registers tab in the Groups/Facilities
view.
[0953] 2 Select facilities from the Available Facilities list and
use the Add button to add them to the Selected Facilities list.
[0954] 3 Select a numbered row in the report and then click the Set
tool in the toolbar. After the Set Thresholds dialog displays, type
a new value for the threshold.
[0955] 4 Click Ok to save the changes and close the dialog..
[0956] Retrieve Historical Data
[0957] To retrieve historical data for the selected facility in the
Facility View:
[0958] 1 Select the Database tab in the Groups/Facilities view.
[0959] 2 Select elements from the Available Elements list and click
the Add button to add them to the Selected Elements list. Select
Add All to add all elements.
[0960] 3 Select the interval for monitoring using the Interval
radio button. Options are 15 Min. or 1 Day. The default is 15
minutes. If you select 15 Min., data is retrieved from the NE
15-minute registers. If you select 1 Day, data is retrieved from
the NE 1-day registers.
[0961] 4 Type values in the following fields:
[0962] NMS Start Date--Select the date when NETSMART started
receiving data from the NE.
[0963] NMS Start Time--Select the time when NETSMART started
receiving data from the NE.
[0964] NMS End Date--Select the date when NETSMART stopped
receiving data from the NE.
[0965] NMS End Time--Select the time when NETSMART stopped
receiving data from the NE.
[0966] 5 Click the Reload tool from the toolbar to begin retrieving
data. The resulting report is updated for the elements in the
Selected Elements list and for the specified Interval, AMS Start
Date, NMS Start Time, NMS End Date, and NMS End Time.
[0967] TL1 Command and Batch Processing
[0968] This section provides the procedures for entering and
executing both batch and online TL1 commands. Batch TL1 commands
can be saved as a file and executed at a later time.
[0969] To start the TL-1 Editor, from the Configuration Manager
NETSMART menu, select TL1 Editor. The Raw TL-1/TL-1 Batch window
displays. There are three main display areas on this window.
[0970] The upper part will contain any commands that were typed in
the TL1 Command text entry area
[0971] The middle part will contain any results/responses generated
by this command.
[0972] The lower part contains the TL1 Command text entry area, the
Active Sessions list area and the list of saved batch files. This
procedure refers to the upper portion of this window as the history
area and the middle portion is referred to as the results/responses
area. The lower portion of the window is referred to as the batch
listing area.
[0973] Enter Single TL1 Commands
[0974] Use the Raw TL-1/TL-1 Batch window to enter and execute
individual TL1 commands. Using individual TL1 commands is the
simplest way to interact with a single NE and will ensure that the
command executes properly before using it in a batch file
(especially one that will be executed on multiple NEs). When
executing time-consuming TL1 commands, it is best to use a TL1
batch (when individual TL1 commands are sent for execution, the TL1
Editor remains busy waiting for command response).
[0975] 1 In the Raw TL-1/TL-1 Batch Window, type in the TL1 command
in the TL1 Command field.
[0976] 2 Press the ENTER key to execute the command. The command
displays in the history area of the TL1 window. The command and the
results display in the results/responses area of the TL1 window.
Each TL1 session corresponds to a user ID that is logged on a
specific NE. Multiple sessions can exist. An active session must
exist to send a command. If no sessions exist, one can be created
by issuing the ACT-USER TL1 command.
[0977] Enter TL1 Commands in Batch Mode
[0978] TL1 commands can be entered into a batch file for immediate
execution or can be saved in a batch file for a scheduled
execution. Before a batch can execute, at least one TID must be
selected. In addition, the batch must have the UID and Password
properties set before the batch can execute.
[0979] Batch commands can be exported as a file, in which case the
TID and Properties values will not be retained. Importing a TL1
file into the TL-1 Batch Editor will override any existing commands
in the editor. The command syntax for TL1 commands is described in
Bellcore document GR-831-CORE Issue 1 (November 1996).
[0980] 1 In the Raw TL-1/TL-1 Batch window, select New from the
Batch menu to display the NETSMART TL-1 Batch Editor window, where
you can create a new batch. To edit an existing batch, double-click
on an existing batch in the batch listings at the bottom of the
window or click on a batch name and select Edit from the Batch
menu. The NETSMART TL-1 Batch Editor window displays (FIGS.
4-144).
[0981] 2 Select TIDs from the Batch menu. The TID List dialog
displays.
[0982] 3 Select the TID(s) for the batch by clicking to highlight
the TID to which the TL1 commands will be sent. Multiple TIDs can
be selected. Click a second time on the TID to deselect any
unwanted values.
[0983] 4 If the TID that is needed is not in this list, type the
name of the TID in the list to the left of the Add TID to List
button.
[0984] 5 Click the Add TID to List button to add the TID to the
list. If there are no TIDs to add, this button is grayed out and
unavailable.
[0985] 6 Click Ok to select the TID(s).
[0986] 7 Use the Import Batch tool to display the Import Batch
dialog where the file to be imported can be identified, or use the
Export Batch tool to display the Import Batch dialog where the
location and file name for data to be exported can be
identified.
[0987] 8 Click to select the file to be imported or exported. Only
one file at a time can be selected.
[0988] 9 Click OK to select the file and close the dialog.
[0989] 10 Click the mouse to place the cursor in the free-form area
of the NETSMART TL-1 Batch Editor (the main part of the window) and
type TL1 commands in this area.
[0990] 11 To set the properties for the batch, click on the Props
tool or select Properties from the Batch menu. The Batch Properties
dialog displays. Values must be entered in the UID and Password
fields for the batch to execute.
[0991] 12 Select or type values in the following fields:
[0992] Name:--If this is a new batch, this field is blank. If this
is an existing batch, this field displays the name of the batch.
Data cannot be entered in this field.
[0993] Owner--Displays the user name that logged on NETSMART. Data
cannot be entered in this field.
[0994] Privilege:--Select PRIVATE if only the person who created
the batch file can execute it or PUBLIC if any user with TL1
privileges can execute the batch file.
[0995] Send Mode:--Select SERIAL if the TL1 batch of commands is to
be sent to one NE at a time or PARALLEL if the batch file is to be
sent to all NEs in the TID list at the same time.
[0996] UID:--Type the user ID that will be used to create a new
session for batch execution. This user ID must be valid for each
TID that was selected using the TID List dialog. If a command
within the batch file specifies another user ID, the user ID within
the batch file will override this user ID.
[0997] Password:--Enter the password for the User ID that was typed
in the UID field.
[0998] 13 Click Ok to save the property settings or Cancel to close
the dialog without making changes.
[0999] 14 To save the batch file, click the Save As tool or select
Save As from the File menu.
[1000] The Save as Dialog
[1001] Use the Save As . . . dialog to save a file with the
existing namie (overwrites the existing file) or to type a new
filename and save the file with the new name.
[1002] 1 When the Save As . . . dialog displays, type a value in
the Batch name field. The file will be saved using this name.
[1003] 2 In the Raw TL-1/TL-1 Batch window, double-click to select
a saved batch file from the listing area (the lowest portion of the
TL1 window). If there is more than one session active, select the
active session TID from the Active Sessions list. Click the Send
tool or select Send from the Batch menu to transmit the TL1
commands.
[1004] Edit TL1 Batch Commands
[1005] The TL1 batch file can be edited and saved in the original
file or in a new batch file for a scheduled execution. The new
batch must have the UID and Password properties set before the
batch can execute. Batch commands can be exported as a file, in
which case the TID and Properties values will not be retained.
Importing a TL1 file into the Batch Editor will override any
existing commands in the editor. The command syntax for TL1
commands is described in Bellcore document GR-831 -CORE Issue 1
(November 1996), which is hereby incorporated by reference.
[1006] 1 In the Raw TL-1/TL-1 Batch window, either double-click on
an existing batch in the batch listings at the bottom of the window
or click on a batch name and select Edit from the Batch menu. The
NETSMART TL-1 Batch Editor window displays.
[1007] 2 To add or change TIDs, select TLDs from the Batch menu.
The TID List dialog displays.
[1008] 3 Select the TID(s) for the batch by clicking to highlight
the TID to which the TL1 commands will be sent. Multiple TIDs can
be selected. Click a second time on the TID to deselect any
unwanted values.
[1009] 4 If the TID that is needed is not in this list, type the
name of the TID in the list to the left of the Add TID to List
button. Click the Add TID to List button to add the TID to the
list. If there are no TIDs to add, this button is grayed out and
unavailable.
[1010] 5 Click Ok to select the TID(s).
[1011] 6 Use the Import Batch tool to display the Import Batch
dialog where the file to be imported can be identified, or use the
Export Batch tool to display the Import Batch dialog where the
location and file name for data to be exported can be
identified.
[1012] 7 Click to select the file to be imported or exported. Only
one file at a time can be selected.
[1013] 8 Click OK to select the file and close the dialog.
[1014] 9 Click the mouse to place the cursor in the free-form area
of the NETSMART TL-1 Batch Editor (the main part of the window) and
type TL1 commands in this area.
[1015] 10 To modify the properties for the batch, click on the
Props tool or select Properties from the Batch menu. The Batch
Properties dialog displays. Values in the UID and Password fields
must be changed so that the batch can execute.
[1016] 11 Select or type to change values in the following
fields:
[1017] Name:--If this is a new batch, this field is blank. If this
is an existing batch, this field displays the name of the batch.
Data cannot be entered in this field.
[1018] Owner--Displays the user name that logged on to NETSMART.
Data cannot be entered in this field.
[1019] Privilege:--Select PRIVATE if only the person who created
the batch file can execute it or PUBLIC if any user with TL1
privileges can execute the batch file.
[1020] Send Mode:--Select SERIAL if the TL1 batch of commands is to
be sent to one NE at a time or PARALLEL if the batch file is to be
sent to all NEs in the TID list at the same time.
[1021] UID:--Type the user ID that will be used to create a new
session for batch execution. This user ID must be valid for each
TID that was selected using the TID List dialog. If a command
within the batch file specifies another user ID, the user ID within
the batch file will override this user ID.
[1022] Password:--Enter the password for the User ID that was typed
in the UID field.
[1023] 12 Click Ok to save the property settings or Cancel to close
the dialog without making changes.
[1024] 13 To save the batch file, click the Save As tool or select
Save As from the File menu.
[1025] 14 When the Save As . . . dialog displays, type a value in
the Batch name field or leave the old name if you do not want to
change it. The file will be saved using this name.
[1026] 15 In the Raw TL-1 /TL-1 Batch window, double-click to
select a saved batch file from the listing area (the lowest portion
of the TL1 window). If there is more than one session active,
select the active session TID from the Active Sessions list. Click
on the Send tool or select Send from the Batch menu to transmit the
TL1 commands.
[1027] Using the TL1 Console
[1028] This section provides the procedures for using the TL1
Console. The TL1 Console window allows a user to view the TL1
activity generated due to a user's actions; for example, log on to
NE, create crossconnect, etc. System-level TL1 activities include
all the TL1 activities that are sent to or received from the NEs
being managed, such as TL1 command and response, autonomous
messages (REPT-*), raw TL1 command and response, and RTRV-HDR.
[1029] By default, all security roles defined in NETSMART have the
TL1Console user function, which allows users to view the TL1
activities that they generated. The NetSmartUserAdmin role has the
TL1SuperConsole function, which allows users to view the system TL1
activities. If the role includes the TL1SuperConsole user function,
the user with this role can use the TL1 Console window to view
system-level TL1 activities. As a TL1SuperConsole user, up to five
TL1 Console windows can be started. By default, the TL1 messages
viewed by the TL1Console user include the command and response
received from the NE. For information about viewing other TL1
record attributes or changing the order of the displayed
attributes, refer to Section A.13.1, TL1 Console Rearrange
Attributes Dialog. As a TL1Console user, you can start only one TL1
Console window.
[1030] For information about modifying the security roles, refer to
Roles Tab. To start the TL1 Console, from the NETSMART menu, select
TL1 Console. The TL1 Console window displays. As soon as you open
the TL1 Console, the display of TL1 events begins and scrolls
automatically to display additional events. The TL1 Console window
displays a maximum of 1000 records at a time.
[1031] Display TL1 Messages
[1032] The display can be started, stopped or paused by selecting
Start, Stop or Pause from the Operations menu or by selecting one
of the Start, Stop, or Pause tools from the toolbar.
[1033] 1 The TL1 console starts with the default setting, which
displays TL1 messages. The server will start sending messages to
the console. To add, remove, or rearrange the attributes to be
displayed, use the Rearrange Attributes dialog. For more
information, refer to Rearrange TL1 Attributes. If the display was
paused earlier by selecting the Pause button, the console will
display the messages that were sent during the pause and will then
start to display new messages. If the display was stopped earlier
by selecting the Stop button, the new real-time messages will begin
to display. The Start button becomes active only when the display
has been paused or stopped.
[1034] 2 To pause the message display, select Pause from the
Operations menu or click the Pause tool. This option pauses the
display of TL1 events to the console. Internally, the messages are
buffered for up to 1000 records; these records will be displayed
when you select Start to restart the display.
[1035] 3 To stop display of any messages in the console, select
Stop from the Operations menu or select the Stop tool in the
toolbar. The server stops sending messages to the console.
[1036] Rearrange TL1 Attributes
[1037] Adding, removing, or rearranging the attributes to be
displayed in TL1 Console is accomplished by using the Rearrange
Attributes dialog.
[1038] 1 To open this dialog, select Rearrange Log Attributes from
the View menu or click the Rearran . . . tool in the toolbar. The
Rearrange Attributes dialog displays.
[1039] 2 To add an attribute to the Selected List, highlight the
attribute in the selections beneath the Attribute List and then
click the Add button.
[1040] 3 To remove an attribute from the Selected List, highlight
the attribute in the Selected List and then click the Remove
button.
[1041] 4 To add or remove all attributes, use the AddAll button or
the RemoveAll button. TL1Msg is the default item in the Selected
List and cannot be removed.
[1042] 5 To change the order of the attributes in the list, select
an attribute and then click the Up button to move the attribute up
in the list or the Down button to move the attribute down in the
list.
[1043] 6 Click OK to save the settings and close this dialog or
click Cancel to cancel all changes and close this dialog.
[1044] Filter TL1 Messages
[1045] Messages to be displayed in the TL1 Console can be filtered
using the Filter TL1 Messages dialog.
[1046] 1 To open the Filter TL1 Messages dialog, select Filter from
the Operations menu in the TL1 Console window or click the Filter
tool in the toolbar. The following dialog displays.
[1047] 2 Messages can be filtered based on the NE TID or the
message type. Select the filter from the NE ID drop-down list. To
filter the TL1 message display based on the NE TID, select:
[1048] Starts with--If you want the NE to start with the specified
value.
[1049] Ends With--If you want the NE to end with the specified
value.
[1050] Contains--If you want the NE to contain the specified value.
Type the text relevant to your NE ID selection in the Value field
(for example, FLM) and check the Case Sensitive box to search for
the NE using the case-sensitivity specified for the typed
value.
[1051] 3 To filter messages based on the message type, in the
Message Type screen area, select the message type(s) that you want
to be displayed in the TL1 Console window. The TL1SuperConsole user
can filter all message types. The TL1 Console user can only view
and filter the following messages: Command, Response and
Acknowledgement. The complete list of message types includes:
Unparsed, Send Raw, Autonomous, Received Raw, Command,
Acknowledgement, and Response.
[1052] 4 Click OK to make the changes and close the dialog or click
Cancel to close the dialog without making any changes.
[1053] Reports
[1054] This section provides the procedures for reporting
information from the NETSMART databases. All the reports are
similar in functionality and access methods.
[1055] Link Report
[1056] Use the Link Report window to view and edit physical link
information in the NETSMART database. Read-only (view) functions
include filtering and sorting of displayed physical links. Edit
functions include modification of physical link names and deletion
of physical links from the system. The Link Report can be displayed
as either:
[1057] A global view (all physical links in the system)
[1058] A group link view (all physical links belonging to a
particular link that is displayed on the Topology map window)
[1059] NETSM ART Crossconnect Report
[1060] The crossconnect Report dialog displays a report containing
information about a selected type of crossconnect.
[1061] 1 In one of the Crossconnect tabs, select Report from the
Operations menu or select the Report tool from the toolbar. In the
cascade to the right of the Report menu label, select the type of
crossconnect to report. The Crossconnect Report dialog (FIG. 33)
displays.
[1062] 2 Use the tools on the toolbar or select Operations menu
items to perform the following functions.
[1063] Select the Print tool to display the Print dialog to print a
report.
[1064] Select the Filter tool to display the Filter dialog to
filter the information displayed.
[1065] Select the Sort tool to display the Sort dialog to sort the
information displayed.
[1066] Select the Columns tool to display the Column Settings
dialog to determine the columns to be displayed.
[1067] Select the Deselect tool to remove the selection shading
from any selected screen area(s). The tool will be grayed out and
unavailable if no selection has been made.
[1068] Select the Reload tool to reload information from the
NETSMART database.
[1069] 3 Once you have completed operations in this dialog, click
Close to close the report.
[1070] NETSMART Crossconnect Trail Report
[1071] The Crossconnect Trail window displays a report containing
information about all the crossconnects in all the NEs that are
autodiscovered in the Topology window.
[1072] 1 Access this dialog by selecting Query NE from the Topology
view Edit Menu.
[1073] 2 In the dialog, select Crossconnect Name from the choice
box labeled Query by and type the Crossconnect name or another
valid value in the adjoining text field. Wild card searches are
allowed, so the entry can either be a name or part of a name
followed by a % sign. A % sign can be entered alone, in which case
all the crossconnects will be retrieved from the database. The text
field cannot be left blank. Apostrophes cannot be used. The
apostrophe interferes with Oracle semantics. For either of the two
cases, a popup dialog prompts you to enter a name or to refrain
from using an apostrophe in the search name.
[1074] 3 Click Ok to produce the report or click Cancel to cancel
and close this dialog.
[1075] 4 The NETSMART Crossconnect Report window displays.
[1076] 5 Use the tools on the toolbar or select Operations menu
items to perform the following functions.
[1077] Select the Print tool or select Print from the Operations
menu to display the Print dialog to print a report.
[1078] Select the Filter tool or select Filter from the Operations
menu to display the Filter dialog to filter the information
displayed.
[1079] Select the Sort tool or select Sort from the Operations menu
to display the Sort dialog to sort the information displayed.
[1080] Select the Columns tool or select Column Settings . . . from
the Operations menu to display the Column Settings dialog to
determine the columns to be displayed.
[1081] In a multipage report, use the Previous and Next tools to go
to the previous and next page of the report.
[1082] Use the DelXC tool to delete a crossconnect.
[1083] Select the Deselect tool or select Deselect from the
Operations menu to remove the selection shading from any selected
screen area(s). The tool and the menu selection will be grayed out
and unavailable if no selection has been made.
[1084] Select the Reload tool to reload information from the
NETSMART database.
[1085] 6 When completing operations in this window, select Close
from the File menu to close the report.
[1086] Delete a Crossconnect from the Trail Report
[1087] A crossconnect can be deleted from the NETSMART Crossconnect
Trail Report. In the NETSMART Crossconnect Trail Report, each of
the rows represents one crossconnect record. Crossconnects can be
deleted from the NETSMART Crossconnect Trail Report by selecting
the appropriate row(s).
[1088] 1 After the NETSMART Crossconnect Trail Report displays,
select the row(s) to delete using the mouse. For multiple
selections, you have two options:
[1089] Hold down the SHIFT key and click on the desired rows to
select a contiguous set of records.
[1090] Hold down the CTRL key and click on the desired rows to
select a non contiguous set of records.
[1091] 2 Either select the tool labeled DelXC from the toolbar, or
from the Operations menu select Crossconnect. From the Crossconnect
runoff menu, select Delete XC.
[1092] 3 Once the row(s) have been selected from the table in the
report panel, select either the tool labeled DelXC, or from the
Operations menu select Crossconnect and from the runoff menu select
Delete XC. Some of the crossconnects may be redlined. If so, when
the Ok button is clicked on the Confirmation dialog, an Information
Message box indicates that some of the crossconnects selected could
be set to redline, and asks whether you would like to delete the
Crossconnects not redlined and skip the redlined ones. If the Y
(Yes) option is selected, the unredlined crossconnects are deleted.
If N (No) is selected, control is returned to the table in the
Report from where the selections were made. If Yes was selected,
the report will redisplay without the deleted crossconnect. If Y
(Yes) is selected, the crossconnects should be deleted. However,
there could be reasons for which the delete operation for a few
crossconnects might fail. In that case a dialog provides a list of
failed crossconnect deletes and the reason why that delete from the
report failed.
[1093] 4 To verify that the changes have been made, select Report
from the Operations menu, then select the appropriate type of
crossconnect. A report is displayed showing all the selected types
of crossconnects.
[1094] Printing
[1095] This section describes the procedures associated with
printing NETSMART information. This information includes:
[1096] Printing a report
[1097] Saving a report to a disk
[1098] Printing a graphical view
[1099] Selecting a table area for printing
[1100] Previewing print output
[1101] Setting up a page for printing
[1102] Printing Overview
[1103] Use the NETSMART Print dialog to enter print commands and to
print reports to a file or to a printer. The following describes
page layout and wrapping:
[1104] By default, if a row is wider than a page, the data is
wrapped inside the cell.
[1105] Table rows are wrapped into multiple table regions, but only
one table region is printed on each page, regardless of how many
table regions can fit into one page. Table rows that extend beyond
a single page are broken into side-by-side pages on cell
boundaries
[1106] A Fit Page Width button is provided in the Page Setup
dialog. When this button is selected, regardless of how wide a
table row is, the table width is set to the same as the page
width.
[1107] Note: A maximum of 100 lines of output is produced for each
report.
[1108] Print a Report
[1109] 1 After displaying a tabular report, print the data by
selecting either the Print option on the File menu or by selecting
the Print tool from the toolbar. The Print option on the File menu
is not always available. The NETSMART Print dialog displays.
[1110] 2 Select or type values in the following fields:
[1111] Print To--Select the output format: Printer, Text File, or
PostScript File.
[1112] Printer Command:--For text/postscript file output, this
field will be grayed-out and unavailable. For printed output, type
any valid printer command(s) in this field.
[1113] File Name:--If you are printing to a file, use this field to
type a file name.
[1114] Orientation--For printer output, select whether the printed
output should be in landscape or portrait format.
[1115] Paper Size--For printer output, select the size of paper for
the printed report.
[1116] 3 Use the Preview . . . button to display a print
preview.
[1117] 4 Use the Setup... button to set up printing parameters.
[1118] 5 Click Ok to send the data to the specified output
device.
[1119] 6 Click Apply to apply the changes and leave the dialog
open.
[1120] 7 Click Cancel to close the dialog without sending the data
to the output device.
[1121] Save a Report to a Disk
[1122] Certain tabular style reports can be saved to a disk in text
file (.txt) or PostScript (.ps) format.
[1123] 1 After displaying a tabular report, click the Print tool or
select the Print Table option from the File menu. The NETSMART
Print dialog displays.
[1124] 2 Select or type values in the following fields:
[1125] Print To--Select one of Text File or PostScript File.
[1126] Printer Command:--For text/postscript file output, this
field will be grayed-out and unavailable.
[1127] File Name:--Type the name of the file to be created. Click
on the button to the right of this field to display the File
Selection dialog where you can select a location for the file.
[1128] Orientation--This field is grayed out and not available for
text/postscript file output.
[1129] Paper Size--This field is grayed out and not available for
text/postscript file output.
[1130] 3 Use the Preview . . . button to display a print
preview.
[1131] 4 Use the Setup . . . button to set up printing
parameters.
[1132] 5 Click Ok to save the data to the specified location.
[1133] 6 Click Apply to apply the changes and leave the dialog
open.
[1134] 7 Click Cancel to close the dialog without saving any
data.
[1135] Print a Graphical View
[1136] The Print View option on the File menu lets you print what
you see on the screen. This option is available in components that
have graphic images (such as Topology). It is also enabled in some
components that produce reports. If this selection is not
available, it is grayed-out.
[1137] 1 After displaying a graphical view, print the view by
selecting the Print View option on the File menu. The NETSMART
Print dialog.
[1138] 2 Select or type values in the following fields:
[1139] Print To--Select the output format: Printer, Text File or
PostScript File.
[1140] Printer Command:--For text/postscript file output, this
field will be grayed-out and unavailable. For printed output, type
any valid printer command(s) in this field.
[1141] File Name:--If you are printing to a file, use this field to
type a file name.
[1142] Orientation--For printer output, select whether the printed
output should be in landscape or portrait format.
[1143] Paper Size--For printer output, select the size of paper for
the printed report.
[1144] 3 Use the Preview . . . button to display a print
preview.
[1145] 4 Use the Setup . . . button to set up printing
parameters.
[1146] 5 Click Ok to send the data to the specified output
device.
[1147] 6 Click Apply to apply the changes and leave the dialog
open.
[1148] 7 Click Cancel to close the dialog without sending the data
to the output device.
[1149] Print Area
[1150] Use the Print Area option on the File menu to select an area
of a table for printing. Both Set Print Area and Clear Print Area
options may be available. The Print Area option is only available
for tables.
[1151] 1 Display the table that you want to print. Select Print
Area from the File menu, and select Set Print Area from the Print
Area menu.
[1152] 2 Select a row or rows for printing. For multiple print
elections, you have two options:
[1153] Hold down the SHIFT key and click on the desired rows to
select a contiguous set of records.
[1154] Hold down the CTRL key and click on the desired rows to
select a non-contiguous set of records. When you select an area for
printing, no visual changes occur.
[1155] 3 Click on the File menu, then select the Print menu
item.
[1156] 4 Process printing as normal. When printing, only the
selected region is taken into account. For example, the Print
Preview option will show only the selected region. The Clear Print
Area option will clear the selected area..
[1157] Print Preview
[1158] Use the Print Preview option on the File menu to view what
will be sent to the printer or file. The Print Preview option is
available for any tabular data displayed on the screen.
[1159] Note: A maximum of 100 lines of tabular output is produced
for each report.
[1160] 1 After displaying a report with the appropriate data,
select the Print Preview option from the File menu. The NETSMART
Print Preview dialog displays.
[1161] 2 Select the Print button to display the Print dialog.
[1162] 3 Click the Close button to close the Print Preview
dialog.
[1163] NETSMART Page Setup
[1164] Each Print dialog in NETSMART contains a Setup . . . button.
Selecting this button displays a dialog where you can select
parameters that affect printed output.
[1165] 1 After displaying a report with the appropriate data,
select the Print tool from the toolbar or click on one of the print
options on the File menu. The NETSMART Print dialog displays.
[1166] 2 Click to select the Setup . . . button. The NETSMART Page
Setup dialog displays.
[1167] 3 In the Font area in this dialog, click in the selection
list to the right of the Name label and select the font name to be
used for printing. In the selection list to the right of the Style
label, select the font style to be used for printing. In the
selection list to the right of the Size label, select the font size
to be used for printing.
[1168] 4 In the Title field, either select the default window title
or type a new value that will be the title for the print
output.
[1169] 5 In the Header field, type a value that will be used as the
header information for the print output.
[1170] 6 In the Footer field, type a value that will be used as the
footer information for the print output.
[1171] 7 Check the Fit Page Width box to fit the print output
within the page width.
[1172] 8 Click Ok to send the output to the selected printer.
[1173] 9 Click Apply to make the changes but keep this dialog
open.
[1174] 10 Click Cancel to close the dialog without printing.
[1175] Filtering Tabular Information
[1176] Use the Filter tool and/or select Filter from the Operations
menu to refine the data that you want to see in a report or other
tabular information. Many of the reports in NETSMART provide this
option including the Log Manager and Fault Manager reports.
[1177] 1 After displaying a report with the appropriate data,
select the Filter tool from the toolbar or, if it is available,
select the Filter option from the Operations menu. The Filter
dialog displays.
[1178] 2 Click on a button beneath the Field label to display a
dropdown list to select a field.
[1179] 3 Select a field to be filtered. The Test button becomes
active. Click on this button to display a series of values to test
against for filtering, one of:
[1180] contains
[1181] !contains
[1182] starts with
[1183] !starts with
[1184] ends with
[1185] !ends with
[1186] Click to select one of these values.
[1187] 4 Use Boolean values to filter by selecting one of AND/OR
from the choice boxes beneath the Logic button.
[1188] 5 Once all filtering values are selected, click Ok to
redisplay the information with the filter(s) applied.
[1189] Sorting Information
[1190] Use the Sort dialog to specify sorting criteria in most
tabular views.
[1191] Note: There are two types of Sort dialogs. One type allows
you to sort using a single argument, while another type (the Fault
Manager, for instance) allows selection of multiple sort arguments.
In the second type (multiple arguments), it may sometimes appear
that the data is not ordered correctly..
[1192] 1 Click on the Sort tool or select Sort from the Operations
menu. The Sort dialog displays.
[1193] 2 The sort will consider case on string sorts. To turn off
case-sensitivity, select the Ignore Case? (valid only for strings)
box at the top of the dialog.
[1194] 3 Select the sort parameters. The order in which you select
the Sort By buttons will determine the sort order.
[1195] 4 Use the Order button to indicate the sort order for the
Sort By parameters. Select one of Ascending (lowest to highest) or
Descending (highest to lowest).
[1196] 5 Click Ok to begin the sort. The data will redisplay in the
sort order that you specified.
[1197] Sorting by Time
[1198] In a tabular display, where data can be sorted on multiple
criteria, the results of a sort may appear erroneous because the
system measures time in milliseconds, while NETSMART reports time
in seconds. For example, the following Sort dialog shows the
sorting criteria that were used to sort Fault Manager alarms
information. First, the time the alarm was raised was selected and
then the severity of the alarm was selected. The resulting output
looks to be incorrect for the 10:31:44 time slot. The results of
the sort in the following figure shows that a condition (NA) is
inserted between two major alarms. The condition was raised
milliseconds before the second major alarm, so it appears in the
list before the second major alarm.
[1199] Ordering Sort Parameters
[1200] The order in which the Sort By buttons are selected will
determine the sort order. The first (top) sort parameter has
precedence over the second, the second has precedence over the
third, and so forth. When the sort takes place, the NMS Raise Time
will be sorted first. Because the Ascending button wasselected, the
sort will be from the earliest time to the most recent time. Next,
the severity level of each alarm will be sorted in descending order
within each NMS raise time. Alarm conditions will be sorted next in
descending order within each severity level (which was sorted
within each NMS raise time). Service Effect is the last button
selected, and will be sorted last. Because the Ascending button is
selected, the processing will sort service effects in ascending
order, within each condition.
[1201] Cutting and Pasting Information
[1202] Support for Copy and Paste is available in editable fields
such as the ones in Edit NE and the Raw TL1 editor, using the
system clipboard.
[1203] Use CTRL+C to copy the information, and CTRL+V to paste it
into a text area. From tables, right clicking on a cell lets you
see the text in a separate dialog. Select the text in this dialog
that you want to copy and press CTRL+C to copy. The text can then
be pasted by pressing CTRL+V in a text destination field. There is
no menu item or toolbar tool to support this action.
[1204] Setting Column Displays
[1205] You can define which columns will be displayed and which
will be hidden in most tabular views. To display the Column
Settings dialog, either click on the Columns tool in the toolbar or
select Column Settings from the Operations menu. Use the Column
Settings dialog to specify display criteria. The order for column
display can be changed by selecting the heading field and dragging
the field to a different position in the display.
[1206] 1 Click on the Columns tool or select Column Settings from
the Operations menu. The Column Settings dialog displays.
[1207] 2 By default, all columns are listed in the Visible Columns
list. Click to select a column in the Visible Columns list and then
select the Hide button to move the column to the Hidden Columns
list. To show a hidden column, click to select a column in the
Hidden Columns list and then select the Show button to move the
column to the Visible Columns list.
[1208] 3 Highlight a visible column and then use the Move Up or
Move Down button to move the order of the column in the list. This
will change the display order for the columns.
[1209] 4 Click Ok to confirm the column settings.
[1210] View Logs
[1211] Use the Log Managers to view NETSMART logs. Available logs
include:
[1212] Activity Log Manager
[1213] Fault Manager
[1214] TL1 Log Manager
[1215] Transient Event Log Manager Each of these logs can be viewed
from the NETSMART menu's Log Manager selection. All logs maintain a
maximum of 30 days worth of records.
[1216] Note: There are two types of Sort dialogs. One type allows
you to sort using a single argument, while another type (the Fault
Manager, for instance) allows you to select multiple sort
arguments. In the second type (multiple arguments), it may
sometimes appear that the data is not ordered correctly.
[1217] View Activity Log
[1218] The Activity Log provides a summary list of operator
activities and NE state changes. For performance reasons, the
Activity Log is buffered and the user may experience a delay of at
least 1 minute before the log appears in the database. This delay
is to accommodate transient log messages. The Activity Log is
sorted based on a descending timestamp order. The record with the
newest timestamp is displayed first. Because the system measures
time in milliseconds while NETSMART reports time in seconds, some
sort ordering may appear erroneous.
[1219] 1 From the NETSMART menu, select Log Managers. From the
menu, select Activity Log Manager to display the Activity Log
Manager window. The selected log displays. By default, the Activity
log is sorted in Timestamp Descending order.
[1220] Note: It takes approximately 30 seconds to 1 minute for an
action to be added to the Activity Log.
[1221] View Fault History Log
[1222] Once an NE alarm has been cleared, the record is stored in
the Fault History database. For performance reasons, the Fault
History Log is buffered and the user may experience a delay of at
least 1 minute before the log appears in the database. This delay
is to accommodate transient log messages.
[1223] 1 From the NETSMART menu, select Log Managers. From the
cascading menu to the right of Log Managers select the Fault
History Log Manager. The following window displays. The menu bar
and toolbar for the Fault History Log Manager are identical to the
Activity Log Manager.
[1224] View TL1 Commands
[1225] Both user-generated and NE-originated TL1 commands can be
viewed in the TL1 Log. 1 From the NETSMART menu, select Log
Managers. From the cascading menu to the right of Log Managers
select TL1 Log Manager.
[1226] View Transient Events
[1227] The Transient Log Manager allows viewing, filtering and
sorting of all the Transient Condition events from the Fault
History log. Transient Condition records are those that are
reported but do not have any clearing event associated with them.
It is similar to the Fault History log manager except for the
condition that is a Transient event. For performance reasons, the
Transient Event Log report is buffered and the user may experience
a delay of at least one minute before the log appears in the
database.
[1228] 1 From the NETSMART menu, select Log Managers. From the
cascading menu to the right of Log Managers select Transient Log
Manager. The toolbar and menu bar are the same the Activity
Manager.
[1229] Introduction to Meta Model
[1230] This section provides overview and design information about
Meta Model component of NETSMART. The Meta Model provides an
instantiated means of describing any specific network element and
generic. The meta model captures the physical and logical
components that comprise the NE.
[1231] This meta model is used by the application to access meta
information for an NE and any specific instance of a component
supported by the NE. One challenge and objective for NETSMART is to
provide a generic solution for introducing new NE assemblies. The
design of the meta model was intended to satisfy this goal. Other
applications within NETSMART also face this similar challenge.
[1232] It is been widely accepted that a network element suites a
generic assembly tree pattern very well. Ideally, applications like
auto discovery, auditing, reconciliation, database change handling,
configuration management should all provide generic solutions (i.e.
non-type specific). Type specific traversal is supported by the
meta model for those applications that find it difficult to design
generically.
[1233] Scope
[1234] This document describes the NE Meta Model design with some
coverage on related applications (e.g. Autodiscovery). It does not
cover details on aspects related to other components. It is
acknowledged that additional requirements for the Meta Model will
arise during the remaining development phases of NETSMART. The NE
Meta Model is very flexible and extensible. It is expected that as
additional requirements are identified they will be added to
subsequent revisions of this document.
[1235] Overview
[1236] This section provides an overview for the Meta Model
component of NETSMART. Meta Model is the core the data driven
approach of NETSMART. Various semantic details of a network element
are captured in Meta Model, such as different objects managed by
network element (e.g shelves, equipment, facilities etc.),
relationships between these objects, various attribute applicable
to these managed objects etc. The containment hierarchies between
managed objects is also captured in Meta Model. The meta model
provides a type of management information base for the application.
If something changes between two successive releases of a network
element, it can be handled in Meta Model by just incorporating
these changes to the network element model. Following are few
examples of the kind of information captured in this component:
[1237] Equipment contained in a shelf
[1238] Different facilities available on a network element.
[1239] Different values which an equipment attribute can take
[1240] Working and Protect participant in an EPG or FFP
[1241] The following depict the major design objectives for the
meta model.
[1242] Easy introduction of new network elements.
[1243] Allow the applications to traverse the meta model
hierarchically and generically.
[1244] Allow the applications to define various data model, and
meta model, relationships which will help satisfy their specific
requirements. Note: These may and probably will be unrelated to the
assembly containment. For example, a MetaSection is a way to group
MetaSlot(s) for alarm correlation but a MetaSection has nothing to
do with the assembly hierarchy.
[1245] Provide the application with the ability to design using
typed interfaces while maintaining the models generically.
[1246] Each managed object on network element is represented by a
Meta Object in the Meta Model which contains all relevant meta
information about that managed object. There are different Meta
Objects for different type of facilities, equipment, EPGs etc. Each
Meta Object for a given NE type in the meta model, is identified by
Meta Instance Id which is just a label given to Meta Objects for
identification. If there are multiple Meta Objects of the same type
(e.g. two STS1 facilities) which have same characteristics, they
are mapped to the same Meta Component. Meta Component represents
`Type` of Meta Object. The attributes can be defined against a Meta
Object as well as Meta Component. Attributes defined against a Meta
Component are applicable to all Meta Objects related to that Meta
Component. All common attributes of similar Meta Objects are
defined against Meta Component whereas, if there are any specific
attributes applicable to a particular Meta Object only, they can be
defined against Meta Object itself. Meta Model also captures some
information which does not pertain to network element directly, for
example the name of the java class to be used for address
translation for a particular NE is also captured in meta model.
[1247] In the overall picture of NETSMART, meta model resides in
Application Server. Configuration Manager is the main user of meta
model. All other components access meta model via Configuration
Manager. The usage of meta model can be divided into two major
parts:
[1248] Autodiscovery/Resync/Audit/Reconcile
[1249] Providing specific meta information
[1250] The meta model knows nothing about the current state of a
network element. It maintains only a static representation of a
network element. The Autodiscovery.sup.1 application uses the meta
model to drive the building of the dynamic view of the network
element. Only the dynamic view of a network element provides
current state. The dynamic view of a network element is captured in
another component namely the Configuration Manager. Fundamentally,
the dynamic view of a network element is a subset of the meta model
containment tree. During autodiscovery, the containment hierarchy
modeled in meta model is used to build the containment tree
(dynamic view) of application objects in Configuration Manager. The
containment hierarchy in meta model dictates the containment
hierarchy in configuration manager. Only containment relationships
in meta model are used for autodiscovery. Other relationships in
the meta model relationship tree are not used during autodiscovery.
.sup.1 Autodiscovery is the process of obtaining configuration
information from NE and persisting in Configuration Manager.
[1251] Once autodiscovery is done, configuration manager can obtain
any specific meta information from meta model. For example, while
displaying equipment and ports in configuration manager GUI,
configuration manager needs to find out various ports supported by
a particular equipment. This information is obtained by
configuration manager from meta model on need basis. Another
example is that when user wants to change some provisioning
attribute on a facility or equipment, configuration manager GUI
presents list of valid values for that attribute. This list of
valid values is obtained from meta model on need basis.
[1252] Meta Model can be divided into two parts on broad basis:
[1253] Meta Model Data
[1254] Meta Model Engine
[1255] Meta Model data contains all the static modeling information
about the network element. It models all the Meta Objects,
relationships between them, various applicable attributes on Meta
Objects, valid values for these attributes etc. This data is
captured in oracle database tables as per the data model.
Initially, this data is recorded in .db files, one corresponding to
each table in data model. These .db files are loaded into oracle
database using some awk scripts during NETSMART installation. Once
this data is loaded into oracle database, during Application server
startup this information is read by Meta Model engine and cached in
memory in form of relationship tree. Once loaded into memory, Meta
Model engine uses this cache for future refer-ence. It is possible
to delay loading of this information into memory Meta Model engine
is the executable part in meta model which implements all the
interfaces exposed. It also implements semantic interpretation of
Meta Model data, loading of meta model data from database to
memory.
[1256] Feature Dependencies
[1257] In order to be able to support autodiscovery, Meta Model is
dependent on support from COMMS for that NE type.
[1258] Process Overview
[1259] This section addresses process of adding support for a new
network element assembly. Following are main steps involved in
supporting new network element in netsmart from meta-model point of
view:
[1260] Understanding the network element: This involves reading the
documentation (e.g. Architecture and design documents, TL1 document
etc.) available on network element to be supported. This helps
build the general understanding of the network element. This also
involves trying TL1 commands on the NE and/or interacting with NE
people to clarify some behavioral doubts.
[1261] Modeling meta objects and relations: This involves
abstracting the containment and other relation-ships between
various objects to be modeled. Various relationships and objects to
be supported depends on the NETSMART requirements. NETSMART RSA
dictates the type and level of support required in NETSMART for a
network element. Please refer to Appendix A for list of various
objects and relationships commonly modeled for network assemblies.
It may be required to modeled additional relationships or objects
depending on the requirements defined by RSA. This
object-relation-ship model is captured in meta_assembly.db
file.
[1262] Modeling other characteristics of meta objects: This
includes filling up other.db files for support of network element
in question. This includes meta_instance.db, meta component.db,
meta_property.db, meta_attribute.db, meta_attr_map,
meta_collapsed_naming key and meta_eqpt_type_map.
[1263] Implementing a data cache java class for fetching
configuration information from network element during the process
of Autodiscovery.
[1264] Testing autodiscovery for the network element.
[1265] Code review for the model.
[1266] Assumptions
[1267] Modeling of a new NE assembly assumes that the documentation
for the network element is available (e.g. NMIS, PDS etc). Also, it
is assumed for modeling of new assemblies that access to network
element is also available.
[1268] Data Model
[1269] This section defines the data model which is used to
instantiate the meta model. The assemblies for all net-work element
types supported by NETSMART will be stored in the database
(Oracle). A specific NE meta model can be loaded into memory on
demand or pre-loaded during the Application Server initialization.
SQL queries are used to retrieve the assembly data and instantiate
the meta model. The data model has been updated for the 2.i
release. Changes for 2.i included (a) adding newer columns to
existing tables (b) dropping columns which existed prior to 2.i and
(c) introducing new tables. Table and column definitions which
existed prior to 2.i are mentioned in italics. This is expected to
serve as a reference for developers.
[1270] The following sections describe the data model and how the
meta model uses it to instantiate a network element assembly:
[1271] Schema definition
[1272] Query model.
[1273] Schema Definition
[1274] The following tables are used to define all network element
assemblies which are managed by NETSMART. The meta model is built
by querying the following tables:
[1275] meta_component
[1276] meta_instance
[1277] meta_assembly
[1278] meta_class
[1279] meta_property
[1280] meta_attribute
[1281] meta_assembly_map
[1282] meta_collapsed_naming keys
[1283] meta_attr_map
[1284] meta_eqpt_type_map
[1285] The following tables have been eliminated in 2.i:
[1286] meta_revision
[1287] meta_component
[1288] The Component table is the catalogue of all available part
types for a network element. Each part for a given base network
element (e.g. FACTR) is assigned an component identifier that is a
unique primary key to the Component table. Following table lists
the different columns in the table and their descriptions:
3 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). META_COMP_ID varchar2(32)
A unique component identifier. APPL_CLASS varchar2(75) The name of
the java class used to create application object during
autodiscovery. META_CLASS_ID varchar2(32) An enumerated meta class
identifier. This field references the meta_class table.
APPLICATION_TYPE varchar2(15) The type value used by the
application for this component. (e.g. EQPT, TP, etc.). COMM_TYPE
varchar2(15) The type value used by the communications layer for
this component. (e.g. EQPT, TP, etc.) There is not a one to one
mapping with the APPLICATION_TYPE. NAMING_KEY varchar2(15) Some
components have a naming key. It is analogous to the applications
ComponentType in the Relative-ComponentID. (e.g. Shelf, Slot,
Group, etc.). Any given instance of this component may provide a
NAMING_VALUE which is used in combination with this naming key.
[1289] Constraints:
[1290] Primary key: NE_BASE, META_COMP_ID
[1291] Foreign key: META_CLASS_ID references
meta_class(meta_class_id)
[1292] meta_instance
[1293] The Instance table is the inventory of all available parts.
An instance refers to the particular existence of a component
(MetaObject) in relationship tree identified uniquely by
META_INST_ID for a particular NE type.
4 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). META_INST_ID varchar2(32)
A unique instance identifier for a specific component. META_COMP_ID
varchar2(32) This instance's component identifier. NAMING_VALUE
varchar2(32) Specifies complete Component ID for the meta object.
INSTANCE TYPE varchar2(15) Indicates if instance is a standard
MetaObject, a collapsed MetaObject or an expandable collapsed
MetaObject. AUTO_CREATE a varchar2(16) Indicates when an instance
gets created. case-1: when the configuration permits it case-2:
always created automatically case-3: created by default if no data
object exists a This information is used by Autodiscovery service.
Refer to Appendix I: for details.
[1294] Constraints:
[1295] Primary key: NE_BASE, META_INST_ID
[1296] NE_BASE, META_COMP_ID references meta_component(NE_BASE,
META_COMP_ID
[1297] instance_type can be in (`single`, `expand`, `collapse`)
[1298] auto_create can be in (`normal`, `auto_create`,
`default_create`)
[1299] meta_assembly
[1300] The assembly table describes the complete hierarchical
composition of a network element assembly. The composition is based
on instance identifiers. The composition of an assembly uses named
relationships (or edges) with possible conditional expressions.
5 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). PARENT varchar2(32) A
instance identifier for a specific assembly component. This
instance of a component is the direct predecessor to the
corresponding NODE identifier in the assembly hierarchy. NODE
varchar2(32) A instance identifier for a specific assembly
component. This NODE identifier is the successor to the PARENT
identifier. EDGE varchar2(32) The EDGE defines a named relationship
between the PARENT and the NODE. The reasons and usage of
relationships is dependent upon application usage. For instance the
Autodiscovery application is primarily concerned with CONTAINMENT
type relationships. Refer to appendix A for various relationships
modeled in meta model. PRIORITY integer This determines the order
in which rows are returned from database at the time of loading
meta model into application memory. CONDITION varchar2(1024) The
condition is an optional expression which can be attached to an
edge. The dynamic evaluation of the conditional expression must be
evaluated to true in order for the relationship between the PARENT
and the NODE to hold.
[1301] Constraints:
[1302] Primary key: NE_BASE, PARENT, NODE, EDGE
[1303] Foreign key: (NE_BASE, PARENT) references
meta_instance(NE_BASE, META_INST_ID)
[1304] Foreign key: (NE_BASE, NODE) references
meta_instance(NE_BASE, META_INST_ID)
[1305] EDGE must be one of (`IS_A`, `IS_A_DEFAULT`, `CONTAINS`,
`CONTAINS_ONE_OF`, `CONTAINS_ONE_OF_DEFAULT`,
`CONTAINS_FOR_NAMING`,`CONT- AINS_AS_WORKING`,
`CONTAINS_AS_WORKING_DEFAULT`, `CONTAINS.sub.--FOR_PROTE- CTING`,
`IS_NAMED_BY`, `SUPPORTS_PORT`, `SectionToEquipment`,`SectionEquip-
mentDefault`, `SectionToType`, `HAS_PROT_PARTICIPANT`, `HAS
_PROTECTING_PARTICIPANT`, `HAS_WORKING_PARTICIPANT`,
`IS_SUPPORTED_BY`, `IS_XCONNECTABLE_TO`,
`IS_DEFAULT_XCONNECTABLE_TO`,
`IS_DEFAULT.sub.--1WAY_XCONNECTABLE_TO`
[1306] meta_class
[1307] The meta_class table provides the information needed to
instantiate MetaObject(s). MetaObject(s) are the instantiated
representation of a component instance. The MetaObject models
static information about a component. The MetaObject(s) are
sub-classed (e.g. MetaShelf, MetaFunctionalGroup, MetaEquipment,
etc.) and provide a typed hierarchical representation of an
assembly.
6 Table Column Datatype Description META_CLASS_ID varchar2(32) An
enumerated meta class identifier. META_CLASS varchar2(75) The
actual JAVA class name, including package information. These
classes are implemented in the meta_model package and are
instantiated using JAVA reflection.
[1308] meta_assembly_map
[1309] The meta_assembly_map defines the assemblies managed by
FENICS. It also provides for the mapping of assembly id. That is, a
particular assembly can be managed as another. In addition, this
table provides the weight assigned to a particular assembly, the
managed level and auto load flag.
7 Table Column Datatype Description. TYPE varchar2(32) The network
element type as retrieved from the NE (e.g. FACTR). The complete
assembly id consists of the TYPE, CONF, MAJOR, and MINOR fields
(e.g. FACTR UPSR 05 02). TO_TYPE varchar2(32) Mapped network
element type. MINMAJOR varchar2(5) The major and minor network
element revision number AUTO_LOAD varchar2(5) Flag indicating
whether the mapped assembly should be auto loaded during
initialization. The following are not available in 2.i: CONF The
network element configuration as retrieved from the NE (e.g. UPSR).
MAJOR The network element major revision as retrieved from the NE
(e.g. 05). MINOR The network element minor revision as retrieved
from the NE (e.g. 02). TO_BASE Map the above assembly to this base
network element id. (e.g. FACTR). The mapped assembly id consists
of the TO_BASE, TO_MAJOR and TO_MINOR fields (e.g. FACTR 05 02).
TO_MAJOR Map the above assembly to this major network element
revision. (e.g. 05) TO_MINOR Map the above assembly to this minor
network element revision. (e.g. 02) WEIGHT The weight assigned to
the complete assembly id. MANAGE_LEVEL The managed level of the
mapped assembly id (e.g. 5S)
[1310] Constraints:
[1311] Primary key:
[1312] AUTO_LOAD must be either `true` or `false`
[1313] meta_property
[1314] The meta_property table captures the properties.sup.2 for a
specific component. A property is a generic way of grouping
attributes of a component. The grouping of attributes into
properties is application dependent. For example, the attributes
which are used to describe a components current state and
configuration are grouped into the ATTR_LIST property. .sup.2
Properties can be visualized as category of attributes. There are
various categories of attributes modeled in meta model e.g. TL1
related attributes, attributes required to control behavior of
other components etc.
8 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). META_PROPERTY_ID
varchar2(32) Unique identifier for the property. PROPERTY_NAME
varchar2(32) The name assigned to this property. (e.g. ATTR_LIST)
The following are not available in 2.i META_COMP_ID The component
identifier which is associated with this property. This may also be
a META_CLASS_ID. If it is a META_CLASS_ID, all instances of the
particular META_CLASS receive this property. PROPERTY_KEY A unique
identifier for a property name. Used to distinguish identical
property names with conditions. CONDITION A condition expression
which can optionally be attached to to the property. The dynamic
evaluation of the conditional expression must be evaluated to true
in order for the component to access this property.
[1315] Constraints:
[1316] Primary key: NE_BASE, META_PROPERTY_ID
[1317] meta_attribute
[1318] The meta_attribute table captures the attributes for a
specific property. The meta_attribute table provides the capability
of describing the characteristics of any given attribute. This
table serves as inventory of different attributes applicable to NE
types.
9 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). META_ATTRIBUTE_ID
varchar2(32) Unique identifier for the attribute. PROPERTY_ID
varchar2(32) Prior to release 2.i, this column was called
PROPERTY_NAME. Together with NE_BASE, references meta_property
(ne_base, meta_property_id) ATTR_NAME varchar2(32) The name
assigned to this attribute. TYPE varchar2(10) The application type
of the attribute. For example, String, Integer, Boolean, Float,
Enum. VALUE varchar2(256) Although the data model, and meta model
do not know the current state of any components attributes. Some
attribute have a static value. This value is not expected to
change. DEFLT varchar2(20) The default attribute value.
VALID_VALUES varray called A list of valid values for str_list_t
this attribute. This is currently limited to 15 elements of maximum
length 15. MIN varchar2(20) A minimum value for this attribute.
Used for Integer and Float only. MAX varchar2(20) A maximum value
for this attribute. Used for Integer and Float only. INCR
varchar2(20) A increment value for this attribute. Used for Integer
and Float only. READ_ONLY varchar2(5) A boolean flag indicating
whether this attribute may be changed or not. REQUIRED varchar2(5)
A boolean flag indicating that this attribute is required.
[1319] The following are not available in 2.i:
10 PROPERTYKEY A unique identifier for a property name. Used to
distinguish identical property names with conditions. ATTRKEY A
unique identifier for an attribute name. Used to distinguish
identical attribute name with conditions. META_COMP_ID The
component identifier which is associated with this property. This
may also be a META_CLASS_ID. If it is a META_CLASS_ID, all
instances of the particular META_CLASS receive this property.
CONDITION A condition expression which can optionally be attached
to the attribute. The dynamic evaluation of the conditional
expression must be evaluated to true in order for the component to
access this attribute.
[1320] Constraints:
[1321] Primary key: NE_BASE, META_ATTRIBUTE_ID
[1322] Foreign key: (NE_BASE, META_PROPERTY_ID) references
meta_property(NE_BASE, META_PROPERTY_ID)
[1323] ATTRNAME is NOT NULL
[1324] TYPE must be in (`String`, `Integer`, `Boolean`, `Float`,
`Enum`, `Class`)
[1325] READ_ONLY must be either in `true` or `false
[1326] Valid values for REQUIRED must be either `true` or
`false`
[1327] meta_attr_map
[1328] This table is new for the 2.i release. It links
meta_attribute with either meta_component or meta_instance.
11 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). META_ID varchar2(32)
Identifies the meta_component or meta_instance to which the
attribute is assigned, META_ATTRIBUTE_ID varchar2(32) Unique
identifier for the attribute. CONDITION An optional condition
expression. The dynamic evaluation of the conditional expression
must be evaluated to true for the component instance to access this
attribute.
[1329] Constraints:
[1330] Primary key: NE_BASE, META_ID, META_ATTRIBUTE_ID
[1331] Foreign key: (NE_BASE, META_ATTRIBUTE_ID) references
meta_attribute(NE_BASE, META_ATTRIBUTE_ID)
[1332] Foreign key: (NE_BASE, META_ID) may reference either
meta_instance(NE_BASE, META_INST_ID) or meta_instance(NE_BASE,
META_COMP_ID)
[1333] meta_eqpt_type_map
[1334] This table is new for release 2.i. contains a vendor ID/CLEI
to equipment type mapping.
12 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). VENDOR_ID varchar2(32)
Vendor Id (or CLEI) that uniquely identifies an equipment type.
NE_EQPT_TYPE varchar2(32) Equipment type. This doesn't have to be
unique since different vendor IDs/CLEI codes can map to the same
equipment type.
[1335] Constraints:
[1336] Primary key: NE_BASE, VENDOR_ID
[1337] meta_collapsed_naming_keys
[1338] This table is new for release 2.i. Specifies for a collapsed
meta instance what are its naming keys that must be resolved. E.g.
the collapsed object representing an ATM VC on the SONET ring, the
unresolved naming key would be vci.
13 Table Column Datatype Description NE_BASE varchar2(32) The base
network element identifier (e.g. FACTR). META_INST_ID varchar2(32)
Specifies a given instance. Together with NE_BASE, references
meta_instance(ne_base, meta_inst_id) NAMING_KEY varchar2(15) This
is similar to the application ComponentType in the
RelativeComponentID (e.g. Shelf, Slot, Group etc.). MIN integer The
minimum valid value for the RelativeComponen-tID. MAX integer The
maximum value for the RelativeComponentID. INC integer Incremental
value for the RelativeComponentID PREFIX varchar2(32) String that
may have to be prepended to the RelativeComponentID. POSTFIX
varchar2(32) String that may have to be appended to the
RelativeComponentID. PRIORITY integer A collapsed meta object may
have multiple naming keys. This specifies the relative priority.
INHERITED varchar2(5) Specifies whether value for
RelativeComponentID is inherited from ancestor.
[1339] Constraints
[1340] Foreign key: (NE_BASE, META_INST_ID) references
meta_instance(NE_NBASE, META_INST_ID)
[1341] INC should not be <0 or >MAX
[1342] INHERITED must be either `true` or `false`
[1343] MAX should not be less than MIN
[1344] meta_tmp
[1345] This is a temporary table. It is used by Meta Model awhile
populating its tables with data
14 Table Column Datatype Description NAME varchar2(256) Used as a
temporary work space during data load pro-cess.
[1346] meta_strings
[1347] Another Temporary Table.
15 Table Column Datatype Description NAME varchar2(700) Temporary
ID integer Used to identify NAME
[1348] Constraints:
[1349] Primary key: NAME
[1350] meta_revision
[1351] This table has been eliminated in release 2.i.
[1352] The meta_revision table captures the possible revisions of
components. Since network elements have revisions this table allows
for the definition of the components which comprise a particular
network element revision. Each network element revision must define
a list of valid components which are used to define the
assembly.
16 NE_BASE The base network element identifier (e.g. FACTR).
META_COMP_ID The component identifier. MJ_REV The network element
major revision which requires this component. (e.g. FACTR 05). This
field is used in con-junction with the MN_REV. MN_REV The network
element minor revision which requires this component. (e.g. FACTR
05 02). This field is used in conjunction with the MJ_REV.
[1353] Query Model
[1354] This section describes database queries performed by Meta
Model to instantiate a network element assem-bly. The following
sections describe how the meta model is built:
[1355] Retrieving the Assembly Data
[1356] Retrieving an Assembly Base
[1357] Retrieving the Assembly Root Node
[1358] Retrieving the Assembly Hierarchy
[1359] Each SQL statement and its corresponding result set are
discussed below.
[1360] Retrieving the Assembly Data
[1361] SQL:
[1362] SELECT * from meta_assembly_map;
[1363] Results:
[1364] The result is a collection of MetaAssemblyData objects. This
collection of MetaAssemblyData define the net-work element
assemblies which are managed by FENICS. This collection also
provides a way to map a par-ticular assembly to another. That is,
to manage a particular assembly as if it was another. For example,
FACTR 05 02 may be managed as a FACTR 05 01. Each MetaAssemblyData
assigns a weight to a particular assembly. In addition, the managed
level and auto load flag is provided in the MetaAssemblyData.
[1365] Retrieving an Assembly Base
[1366] SQL:
[1367] SELECT mi.meta_inst_id, mi.meta_comp_id, mi.naming_value,
mc.appl_class,mc.meta_class_id,mc.application_type,mc.comm_type,
mc.naming_key, mc.auto_create, ml.meta_class
[1368] FROM meta_instance mi, meta_component mc, meta_class ml
[1369] WHERE mi.ne_base=:1 AND mc.ne_base=mi.ne_base AND
mc.meta_comp_id=mi.meta_comp id AND
ml.meta_class_id=mc.meta_class_id;
[1370] Results:
[1371] The result of this query is all of the components for a
specified base assembly. This becomes a cache of Met-aNode( s)
which is used by the individual assemblies under the base.
[1372] Retrieving the Assembly Root Node
[1373] SQL:
[1374] SELECT mi.meta_inst_id, mi.meta_comp_id, mi.naming_value,
mc.appl_class,mc.meta_class_id, mc.application_type,mc.comm_type,
mc.naming_key, mc.inherited_nk, mc.auto_create, ml.meta_class
[1375] FROM meta_instance mi, meta_component mc, meta_revision mr,
meta_class ml
[1376] WHERE mi.meta_inst_id=:1
[1377] AND mc.meta_comp_id=mi.meta_comp_id
[1378] AND mc.ne_base=mi.meta_inst_id
[1379] AND mr.meta comp_id=mi.meta_comp_id
[1380] AND mr.ne_base=mi.meta_inst_id
[1381] AND mr.mj_rev=:2
[1382] AND mr.mn_rev=:3
[1383] AND ml.meta_class_id=mc.meta_class_id;
[1384] Results:
[1385] The result of this query is a particular revision of a
network element assembly. This is expected to return the single
result set associated with a particular base, major and minor
revision of an assembly. This result set is used to create the
MetaNe root node in the assembly hierarchy.
[1386] Retrieving the Assembly Hierarchy
[1387] SQL:
[1388] SELECT ma.ne_base, ma.parent, ma.node, ma.edge,
ma.condition
[1389] FROM meta_assembly ma, meta_instance mi, meta_revision
mr
[1390] WHERE ma.ne_base=:1 AND ma.parent=:2 AND mi.ne
base=ma.ne_base AND mi. meta_inst_id=ma. node AND
mr.ne_base=ma.ne_base AND mr.meta_comp_id=mi.meta_comp_id AND
mr.mj_rev=:3 AND mr.mn_rev=:4;
[1391] Results:
[1392] The result of this query are the successors to the specified
parent and ne_base parameters. This SQL is recursively called in
order to build the assembly hierarchy. It is started at the root
MetaNe node and traverses depth first until it reaches leaf nodes
and the entire tree is instantiated. NOTE: This is the most
expensive, time consuming, part of building the meta model.
[1393] Retrieving object-attribute assignment
[1394] SQL:
[1395] Please refer to LOAD_ALL_OBJECTS_ATTR_MAP inside
[1396] MetaObjectLoader.java
[1397] SELECT mi.meta_inst_id, mam.meta_attribute_id,
mam.condition, ma.meta_property_id
[1398] FROM meta_instance mi, meta_attr_map mam, meta_attribute
ma
[1399] WHERE mi.ne_base=:1 AND ((mi.meta_inst_id=mam.meta_id) OR
(mi.meta_comp_id=mam.meta_id)) AND mam.ne_base=mi.ne_base AND
mam.meta_attribute_id=ma.meta_attribute_id AND
ma.ne_base=mi.ne_base
[1400] Results:
[1401] Loads all attribute_id values for every component inside an
assembly.
[1402] Retrieve a Specific Object in an Assembly
[1403] SQL:
[1404] Please refer to LOAD_INSTANCE in MetaObjectLoader.java
[1405] SELECT mi.meta_inst_id, mc.meta_comp_id, mi.naming_value,
mc.appl_class,mc.meta_class_id,mc.application_type,mc.comm_type,
mc.naming_key, mi.auto_create, mcl.meta_class, mi.instance_type
[1406] FROM meta_instance mi, meta_component mc, meta_class mcl
[1407] WHERE mi.ne_base=:1 AND mi.meta_inst_id=:2 AND
mi.meta_comp_id=mc.meta_comp_id AND mc.ne_base=mi.ne_base AND
mc.meta_class_id=mcl.meta_class_id
[1408] Results:
[1409] Loads a specific object in an assembly.
[1410] Loading an Attribute for an Assembly Component
[1411] SQL:
[1412] Please refer to LOAD_OBJECT_ATTRIBUTES in
MetaObjectLoader.java
[1413] SELECT ma.ne_base, ma.meta_attribute_id,
ma.meta_property_id, ma.attrName, ma.type, ma.value, ma.deflt,
ma.valid_values, ma.min, ma.max, ma.inc, ma.read_only, ma.required,
mam.condition
[1414] FROM meta_instance mi, meta_attr_map mam, meta_attribute
ma
[1415] WHERE mi.ne base=:1 AND mi.meta_inst_id=:2 AND
((mi.meta_inst_id=mam.meta_id) OR (mi.meta_comp_id=mam.meta_id))
AND mam.ne_base=mi.ne_base AND
mam.meta_attribute_id=ma.meta_attribute_id AND
ma.ne_base=mi.ne_base
[1416] Results:
[1417] Loads all meta_attributes of a specified object in a given
assembly for a particular network element.
[1418] Loading Specific Object in an Assembly
[1419] SQL:
[1420] Please refer to LOAD_INSTANCE inside
MetaObjectLoader.java
[1421] SELECT mi.meta_inst_id, mc.meta_comp_id, mi.naming_value,
mc.appl_class,mc.meta_class_id,mc.application_type,mc.comm_type,
mc.naming_key, mi.auto_create, mcl.meta_class, mi.instance_type
[1422] FROM meta_instance mi, meta_component mc, meta_class mcl
[1423] WHERE mi.ne_base=:1 AND. mi.meta_inst_id=:2 AND
mi.meta_comp_id=mc.meta_comp_id AND mc.ne_base=mi.ne_base AND
mc.meta_class_id=mcl.meta_class_id
[1424] Results:
[1425] Loads a specific meta_instance object by relating the
meta_instance with meta_class and meta_component.
[1426] Retrieve Assembly for a Network Element
[1427] SQL:
[1428] Please refer to LOAD_ASSEMBLY in MetaObjectLoader.java
[1429] SELECT parent, node, edge, condition, priority from
meta_assembly
[1430] WHERE ne_base=:1 ORDER BY parent, priority, node
[1431] Results:
[1432] Loads the ordered assembly data for a specific network
element.
[1433] Retrieving meta_collapsed_naming_keys
[1434] SQL:
[1435] Please refer to LOAD_ALL_COLLAPSED_NAMING_KEYS in
MetaObjectLoader.java.
[1436] SELECT * from meta_collapsed_naming_keys where
ne_base=:1
[1437] ORDER by priority;
[1438] Results:
[1439] Loads information that will help to resolve naming_keys for
a collapsed meta instance.
[1440] Meta Model
[1441] The MetaModelFactory is a singleton object which requires
initialization in each process space that requires meta model
access. The MetaModelFactory creates a MetaBaseAssembly for each
base network element supported by the system (e.g. FACTR, FLM150,
etc.). In addition, the MetaModelFactory assigns MetaAssembly(s) to
each MetaBaseAssembly reflecting the network element revisons that
are supported by NETSMART (e.g. FACTR 05 01, FACTR 05 02, FLM150 11
02, FLM150 12 02, etc.). Each MetaAssembly evaluates its auto load
flag. If it is True, the MetaAssembly will initiate the
instantiation of the assembly. The instantiation of the assembly
starts at the MetaNe root node and instantiates a tree of
MetaNode(s). The tree of MetaNode(s) include named relationships
between nodes called MetaEdge(s).
[1442] Each MetaEdge may have a condition expression which must be
evaluated to true in order for the relationship to be valid. The
instantiated assembly provides an application information base for
a network element. It is static network element data that is used
for autodiscovery, configuration management and various other
application components. The assembly tree may be traversed
generically or via a typed interface.
[1443] If the auto load flag is False, the MetaNe root node is the
only node that is instantiated. The rest of the assembly tree is
instantiated on demand by the Application. The Application which
requires access to an assembly obtains it via a MetaNeFactory. The
Application provides the necessary data to identify an assembly and
acquires a MetaNe reference. If the assembly was not auto loaded it
is loaded at this time. FIG. 38 shows the MetaModel class diagram
for this process.
[1444] Meta Base Assembly
[1445] The MetaBaseAssembly represents a base network element (e.g.
FACTR).The MetaBaseAssembly is multithreaded and synchronized and
is created during process initialization. MetaBaseAssembly has
state which is represented by MBA_State. At the time of
initialization, the state is set to MBA_Inactive. If
Meta-BaseAssembly is auto load, a MetaBaseAssemblyLoader is created
and the state gets transitioned to MBA_Loading. If it is not a case
of auto load, then it is loaded on demand. The MetaBaseAssembly is
only loaded once in the process space. If there is a second request
to load a MetaBaseAssembly in MBA_Loading state, the invoker is
blocked until loading is complete. MBA_NotFound represents absence
of MetaBaseAssembly in database. When the load is successful, the
state is transitioned to MBA_Loaded.
[1446] If load fails due to some reason, the state is transitioned
to MBA_Not_Loaded. FIG. 39 shows the MetaBase Assembly class
diagram. FIG. 40 shows the Meta Base Asembly state transition
diagram.
[1447] Meta Object
[1448] The MetaNode is an abstration which allows for
generic/hierarchical traversal of a network element assembly. The
MetaNe is the root MetaNode. The typed specific behavior is defined
by the MetaObject subclasses. A MetaObject is a generalization of
the things that comprise a network element. The MetaObject may
contain properties, or lists of attributes, called MetaProperty(s).
The MetaProperty contains MetaAttribute(s). The MetaProperty and
MetaAttribute may contain a Condition. The Condition must be
evaluated at run time with context. Only if the Condition is true
does the MetaObject recognize that MetaProperty or MetaAttribute. A
MetaObject is created by the MetaReflector using Java reflection.
The MetaObject is a abstract class used to define generic behavior
for typed network element objects. The network element assembly is
a generic tree pattern implemented by the MetaNode and MetaEdge
relationships. The network element assembly is also typed. Each
MetaNode is implemented as a MetaObject and subclass. FIG. 41 shows
the MetaNode class diagram.
[1449] Loading a Meta Assembly
[1450] The network element assembly is a generic tree pattern
implemented by the MetaNode and MetaEdge relationships. The network
element assembly is also typed. Each MetaNode is implemented as a
MetaObject and subclass. At the time of meta assembly loading,
objects and relationships are retrieved from the meta_assembly
database table and a relationship tree is constructed in
application address space.
[1451] FIG. 42 depicts a small portion of a FACTR assembly.
Starting at the root MetaNode (e.g. FACTR.sub.--5.sub.--2), the
meta model is hierarchically built depth first. The root node
contains a PHYSICAL_SIDE and a LOGICAL_SIDE. From the
PHYSICAL_SIDE, the hierarchy continues by working its way down
through the shelves, sections and equipments, etc.
[1452] The hierarchy of the assembly is totally driven by the data
model. The loading of the meta model is strictly a reflection of
what has been modelled in the meta_assembly table.
[1453] Note the relationships between any predecessor and its
successors are named and may optionally have a conditional
expression on them. The condition expression is evaluated
dynamically at run time. The condition must be evaluated to true in
order for the relationship to exist.
[1454] Objects & Relationships Modelled in Meta Model
[1455] This section provides list of various objects and
relashionships modelled in meta model. The list of objects and
relashioships provided here covers most of the common scenarios
which apply to most of network assemblies. It is important to
understand that need for modelling new objects and relationships
may arise in future depending on the assembly and the kind of
support required in NETSMART for that assembly. Depending on the
kind of support provided for an assembly, every relationships
object may not be applicable. Following is the list of commonly
modelled objects in meta model:
[1456] Shelves
[1457] Equipment
[1458] Facilities.sup.3
[1459] Equipment Protection Groups
[1460] Facility Fibre Protection Groups
[1461] Functional Groups
[1462] Clocks
[1463] CPU .sup.3 This includes all different types of facilities
(e.g. ports, termination points etc) which are required to be
supported for the particular network element assembly.
[1464] In addition to that, there are some pseudo objects which can
be modelled to organize the hierarchy better. These objects are
Sections and Groups. Sections are primarily used to group related
equipment together and Group is a more general notion to group set
of related meta objects together in meta_assembly. Following is
list of relationships modelled in meta model:
[1465] CONTAINS Used to model containment between two objects.
[1466] CONTAINS_ONE_OF If a parent object in the containment
hierarchy can have only one of possible children (in dynamic view)
then this relationship is used between parent object and individual
children objects.
[1467] CONTAINS_ONE_OF_DEFAULT Used to relate a parent object to
the child object which will be default child in case when multiple
children objects are related to the parent by CONTAINS_ONE_OF
rela-tionship.
[1468] IS_SUPPORTED_BY Used to capture relationship between
functional groups and slots supporting those groups.
[1469] HAS_WORKING_PARTICIPANT Used to capture relationship between
a protection group (equipment or facility) and working object in
that group.
[1470] HAS_PROTECTING_PARTICIPANT Used to capture relationship
between a protection group (equipment or facility) and protecting
object in that group.
[1471] SUPPORTS_PORT Used to capture relationship between port and
equipment supporting that port.
[1472] IS_XCONNECTABLE_TO Used to model the relationship between
two time slot groups which can have cross con-nects between them.
Used in case of FLASH192 only at present.
[1473] IS_DEFAULT_XCONNECTABLE_TO Used to model the relationship
between two time slot groups which can have cross connects between
them by default. Used in case of FLASH192 only at present.
[1474] IS_DEFAULT.sub.--1WAY_XCONNECTABLE_TO Used to model the
relationship between two time slot groups which can have one way
cross connects between them by default. Used in case of FLASH192
only at present.
[1475] CONTAINS_AS_WORKING Used to model relationship between line
termination point and working time slot groups contained in it.
[1476] CONTAINS_AS_WORKING_DEFAULT Used to model relationship
between line termination point and default working time slot groups
(if any) contained in it.
[1477] CONTAINS_FOR_PROTECTING Used to model relationship between
line termination point and protecting time slot groups contained in
it.
[1478] Modelling Tips
[1479] Following are some tips and guidelines for modeliing of
network elements:
[1480] MetaObjects to represent CPUs have to be named as
<string1>-<string2>While <string 1>can be
anything (usually "Cpu" or "CPU"), <string2>has to be the AID
of the CPU. Because this is the logic used to get the CPU aid
during a SWDL/RMBU! The existing metamodels follow this rule.
[1481] There are MetaObjects for which we will not create any
application object in the dynamic tree. Exam-ples are
PHYSICAL_SIDE, LOGICAL_SIDE, CPUs etc. You can give `none` as their
naming_value in meta_instance.db Also make sure that you leave the
naming_key of the corresponding meta_component entry as empty.
[1482] Any MetaObject contained by another MetaObject that has been
marked as `expand` (ie, instance_type is `expand` in
meta_instance.db) should itself be given the instance_type
`expand`.
[1483] Any MetaObject contained by another MetaObject that has been
marked as `collapse` (ie, instance_type is `collapse` in
meta_instance.db) should itself be given the instance_type
`collapse`.
[1484] Make sure that CID+Type will be a unique key to identify a
MetaObject. CID is the naming_value col-umn in meta_instance. And
Type is the comm_type column in meta component. In other words,
there should not be more than one MetaObject with the same CID and
the same Type.
[1485] While assigning the meta attribute LINKABLE to MetaObjects,
do NOT use any conditions. This is because when Topology queries CM
for all linkable facilities, CM does a direct DB query by joining
pnecomponent table with metamodel tables. Conditions cannot be
evaluated during this. Again, existing metamodel does not use
conditions for LINKABLE attr; so we can keep it that way.
[1486] Now we can assign meta attributes to meta_component_id's or
meta_instance_id's. So it is better to keep these two ids
distinct.
[1487] Use comments generously in the db files. It would be useful
later on, if we can put the schema of the corresponding table at
the beginning of each db file.
[1488] Try to organize the db files into different logical blocks.
Use blank comment lines to visually separate diff blocks. Give
useful comments for each block. For examples, p1 see FLM600/*.db
files.
[1489] Conditions and Their Evaluation
[1490] While modelling a network element assembly, conditions can
be used where ever some concept is applicable based on condition.
In current design following things can be qualified with
conditions:
[1491] Relationship between two meta objects could be conditional.
While meta model relationship tree tra-versal, relationships
qualified with conditions are only traversed if the condition is
met. Traversal logic does not reach a node, if there was a
condition on its predecessor edge (i.e. relationship to parent)
which is evaluated to `false`. Similar logic applies to traversal
from a child to parent object as well. This kind of conditional
relationships are covered in meta_assembly.
[1492] Applicability of an attribute to a Meta Component or Meta
Instance could be conditional. An attribute and all its
characteristics (e.g. vaild values, read only etc) will apply to a
Meta Component or Meta Instance only if the associated condition
(if any) evaluates to true. The conditions in meta model look like
DataObject.getAttributeValueString("CO- NF5")=="D1" This implies
that if the value of attribute `CONF5` is equal to `D1` in an
object of class DataObject then this will evaluate to `true`. In
order to evaluate conditions, meta model needs `context`. A
component which invokes an interface on meta model, needs to
provide context as well so that meta model can evaluate any related
conditions. `Context` is a generic concept and is a vector of
objects. In the example of condition above, the `context` is
expected to be a vector of DataObject.sup.4 objects. The framework
component responsi-ble for evaluation of conditions, will invoke
`getAttributeValueString("CONF5")` method on each object in
con-text and compare the return value with `D1`. If there was any
object in the context for which this comparison succeeds the
condition will be evaluated to true. .sup.4 DataObject is a java
class in NETSMART.
[1493] Autodiscovery Overview
[1494] This section presents overview of the autodiscovery process
and involvement of meta model in this process. When user adds a
network element and performs `login` from NETSMART GUI, ACT-USER
TL1 command is sent by NETSMART to log into the network element.
Autodiscovery process is triggered, once successful login and some
basic initialization is achieved. Autodiscovery process can be
divided into three major phases as described below:
[1495] 1. Retrieving configuration information from the NE being
autodiscovered--During this phase all con-figuration information is
retrieved from network element by sending appropriate TL1 commands
for retrieval (e.g. RTRV-EQPT etc.). Communication Server provides
interfaces to the application server for these TL1 commands. As a
result of invocation of these interfaces on COMMS, Application
Server gets collection of dataobjects. COMMS returns one dataobject
for each aid fetched from the network element. These dataobjects
are created by COMMS after parsing the TL1 responses. Each
KEYWORD-DOMAIN pair in TL1 response is translated to a
Attribute-Value pair. Each dataobject contains collection of such
Attribute-Value pairs. In addition to collection of Attribute-Value
pairs, dataobject also contains aid and ComponentID.sup.5. During
this phase information about all entities (i.e. equipment,
facilities, EPGs etc) is retrieved from network element. This
information retrieval is driven by DataCache. Their are subclasses
of DataCache for each NE type supported by NETSMART. For example,
there is FACTRDataCache which drives this information retrieval for
FACTR NEs during Autodiscovery. It is responsibility of the meta
model person who is modelling a new NE type to implement a subclass
of DataCache for that NE type. From the dataobjects received from
COMMS, the DataCache build a hashmap of these dataobjects with
CompinentID being the key. DataCache also supports interface to
obtain a dataobject based on its ComponentID, which is used by
Autodiscovery in second phase. .sup.5 ComponentID is internal to
NETSMART and can be treated as a unique identifier for a dataobject
for a given TID. AddressTranslator in COMMS translates the aid in
TL1 response to corresponding COmponentID by following some
predefined rules.
[1496] 2. Traversing the meta model relationship tree and creating
application objects 2 --Once the DataCache has retrieved all the
information and built a hashmap of dataobjects, Autodiscovery
traverses the meta model relationship tree and creates application
objects. These application objects are passed to Configuration
Manager, which holds and manages them. The traversal starts from
the root node and for every node following steps are taken to
create application objects:
[1497] If the meta object is marked as auto_create (i.e.
auto_create column in meta_instance is set to `auto_create` for the
meta object) then a default application 3 object is created for
that meta object.
[1498] If the meta object is marked as normal (i.e. auto_create
column in meta_instance is set to `normal` for the meta object)
then ComponentID for that meta object is obtained. If there is a
dataobject for this ComponentID in the DataCache then an
application object is created for the meta object using
[1499] 1. ComponentID is internal to NETSMART and can be treated as
a unique identifier for a dataobject for a given TID.
AddressTranslator in COMMS translates the aid in TL1 response to
corresponding COmponen-tID by following some predefined rules.
[1500] 2. Application objects are held by Configuration Manager.
Each application object hold reference to corresponding meta object
and data object. 3. In default creation a dummy data object is
created in order. the dataobject otherwise no application object is
created corresponding to the meta object.
[1501] If the meta object is marked default_create (i.e.
auto_create column in meta_instance is set to `default_create` for
the meta object) then ComponentID for that meta object is obtained.
If there is a dataobject for this ComponentID in the DataCache then
an application object is created for the meta object using the
dataobject otherwise a default application object is created.
[1502] 3. Configuration Manager builds a containment tree of
application objects created by Autodiscovery. The containment
relations in this tree of application objects (also called as
dynamic tree or dynamic view of the NE) are same as modelled in
meta model. When autodiscovery passes an application object to
configuration manager, it also passes reference of parent
application object.
[1503] Collapsed Meta Objects
[1504] Collapsed Meta Objects are specialized Meta Objects which
represent multiple objects of the same type. The behavior of a
collapsed MetaObject similar to a standard MetaObject with one
major difference. A standard MetaObject has a fully qualified
ComponentID, invoking getCID( ) will return a complete ComponentID
(e.g shelf=NBS-1:slot=CH-1:port=3). However, a collapsed MetaObject
can not return a fully qualified ComponentID because it represents
multiple objects. For those RelativeComponentIDs that cannot be
resolved, a wildcard value (`*`), is returned (e.g.
group=1:sts=1:vtg=*:vt=*, group=4:sts=1:vpi=0:vci=*).
[1505] However, any ComponentID will always resolve to a
MetaObject. For example, ComponentID group=1:sts=1:vtg=2:vt=4 will
resolve to the MetaObject with ComponentID
group=:sts=1:vtg=*:vt=Note that ComponentID
group=1:sts=1:vtg=3:vt=2 would also resolve to the same
MetaObject.
[1506] To determine if a MetaObject is a collapsed object, a new
interface has been provided on MetaObject: isCollapsedObject(
).
[1507] A collapsed MetaObject can be designated as "expandable".
Unlike the previous version of the MetaModel, expansion in this
case does not mean replicating the MetaObject ntimes. Instead, the
collapsed MetaObject will fully expand all possible ComponentIDs
and that list of expanded CIDs can be retrieved via a new
MetaObject interface getAllInstances( ). For collapsed MetaObjects
not designated as "expandable", an attempt to retrieve all possible
ComponentIDs will return an empty list. To detemine if a collapsed
MetaObject is expandable an application can invoke the MetaObject
interface: isExpandedObject( ).
[1508] Summary of the interfaces changed or added on
MetaObject.java to support collapsed objects:
[1509] ComponentID getCID( )
[1510] In the case of a normal MetaObject getCID( ) will return the
fully resolved ComponentID. If it is a col-lapsed MetaObject,
whether that MetaObject is expandable or not, the ComponentID
returned will not be fully resolved. Wild card values will appear
for those RelativeComponentIDs that could not be resolved.
[1511] boolean isCollapsedObject( )
[1512] Return true if the MetaObject is a collapsed object; false
otherwise.
[1513] boolean isExpandedObject( )
[1514] Returns true if the MetaObject is a collapsed object and its
ComponentID can be fully expanded to all possible ComponentIDs.
[1515] Vector getAllInstances( )
[1516] If the MetaObject is a collapsed object and it can be
expanded, then a list containing the fully expanded list of
ComponentIDs is returned. Otherwise an empty list is returned. In
most cases applications will not care about whether the MetaObject
is collapsed or not since all other interfaces remain unchanged.
Applications that are most likely to be affected are those that
create and main-tain the NE configuration (e.g. autodiscovery,
configuration or provisioning changes).
[1517] FIG. 34 shows architecture components for an embodiment of
the disclosed innovations. Oracle databases are used for persistent
storage, accessed via SQL (Structured Query Language). Lower
applications interface to the databases through FDBC (Fujitsu
DataBase Connectivity) and use FORA (Fujitsu Object Relational
Adaptor) for mapping objects to the database.
[1518] The network manager applications include topology (used to
manage groups, NEs, and links), a software repository, a fault
manager that manages fault for the network, raw TL1 and TL1 batch
that provide raw TL1 interfaces and batch capability, and software
download and remote backup manager.
[1519] The element manager applications include a meta model that
describes an NE for a given release, autodiscovery that identifies
and discovers NEs, configuration manager for the NEs, crossconnect
manager that manages the NE crossconnects, a fault manager, and
software download and remote backup manager for the NEs.
[1520] The framework components include event service, query and
client persistency which provides object query service and column
query service to the client, transaction and concurrency which
provides transaction services, security, thread which provides
threading policy and CORBA request dispatching, connection (Life
Cycle Service) which provides services for server activation, log
and trace, directory naming service (used to locate server object),
and cluster agent framework which provides HA services and process
management.
[1521] The communication subsystem includes a session manager that
manages the TL1 sessions to NEs, a session which provide TL1
sessions to NEs and performs CORBA IDL to TL1 command/response and
autonomous message mediation, a raw session, an address manager
that provides TID to network address mapping (source can be TARP or
NETSMART database), and an OSI.
[1522] Process Architecture
[1523] FIG. 35 shows an overview of the process architecture for
NETSMART. NETSMART process architecture is divided into CORBA
services, Framework, Process Activation and Monitoring,
Application, and Communications.
[1524] The CORBA services include Naming Service (provides name
resolution service for NETSMART CORBA objects), Event Service
(provides COS event channels for autonomous communication in
NETSMART), and orbixd (orbix demon provides CORBA client/server
connection management for the object request broker).
[1525] The Framework core includes Framework and Security.
Framework consists of a LogManager (provides high speed logging
service to NETSMART application components), Broker (provides CORBA
object location and activation services to application components),
Client Persistency (provides remote persistency services to GUI
client) and Client Query (provides remote Query service to GUI
Clients). Security consists of a User Manager (provides management
of NETSMART users), Access Control Manager (provides management of
user security profiles to control access to NETSMART
functionality), and User Session Manager (manages all active
NETSMART sessions).
[1526] Process Activation and Monitoring consists of the fenicsd
and daemon monitor. NETSMART daemon processes monitor the health of
all NETSMART processes, and identify process failure and restart
them. The fenicsd an daemon monitor also monitor each other and
relaunch of one of them dies.
[1527] Optional application services include UPS manager (listens
to trap notifications from the UPS for power down events, and
manages the shutdown of NETSMART under power failure conditions),
emlnml server (provides an interface to NETSMART for NML systems),
and performance management (collects performance data from the NES
and persists them into Oracle database for later analysis.
[1528] Core application services include the topology server
(provides interfaces to manage NEs, groups, and links; provides
services to establish raw TL1 sessions to the NEs, and provides
integrated network level fault query, management, and count
service), the application server (various components of which
perform the following: model the physical NE; manage NE
configuration in databases; maintain the metadata for each type of
NE managed by NETSMART; use static metamodel definition to
instantiate NE specific objects by fetching information from the
physical NE; identify discrepancies and reconcile the differences
between the physical NE and the NETSMART view of the NE; manage
crossconnects in database and the physical NE; and store the NEs
faults in databases), and the software manager server (which
provides services to manage software generics, provides NE level
services to download and activate software generic, and
back-up/restore of NE database; these interfaces are provided at
the network level).
[1529] Core communication services include the communication server
(provides command/response/event and raw TL1 sessions to the NEs,
and provides IDL to TL1 and vice-versa mediation), the session
manager (manages communication sessions to NEs and provides a
lookup service from TID to NSAP/IP). Communication may be provided
via TARP (Target Address Resolution Protocol), FTAM (File Transfer
and Access Management), and OSI standards.
[1530] FIG. 36 shows a hardware architecture for an embodiment of
the presently disclosed innovations. The Enterprise-5500/6500
configuration shows one example of hardware implementation for the
server. The server networks with individual NEs by a 100 base-T NE
communication network, and with client machines via a client
communication network, using OSI and IP LAN cards respectively. The
server also has an uninterruptable power supply (UPS) and an L280
Autoloader backup system connected by a small computer system
interface (SCSI). This figure shows the framework, applications,
and communications blocks of the server. Oracle database using
redundant array of inexpensive disks (RAID) serves as persistent
backup.
[1531] FIG. 37 depicts the server architecture for a given NETSMART
application component. An application component (for example,
topology server, communication server, etc.) interfaces with the
Oracle database through FDBC and uses FORA for mapping objects to
the database. FDBC uses JNI (Java Native Interface) to call OCI
(Oracle Call Interface) functions. OCI functions are written in C
and allow database manipulation and management.
[1532] The thread filters define the threading semantics for a
given application. Thread filters are used to deliver CORBA
requests to CORBA objects.
[1533] The utilities are available for various tasks. They include
asyncworker (the worker thread pattern that executes user commands
entered through the GUI), object pool (a pattern for optimal
performance containing a pool of objects which can be reused),
inventory (lists of related objects), licensing service (restricts
usage of installation based on the NETSMART licensing purchased by
the user), task management (pattern for multi-thread programming),
and collection (extension and Java collection, generates collection
objects to transmit over CORBA).
[1534] The helpers include DNSHelper (Directory Naming Service,
used to look up CORBA objects in NETSMART), authenticator (provides
authentication services when users request restricted privileges),
eventservice (asynchronous communication between various components
in NETSMART), registry (lookup service for CORBA for objects in
NETSMART), and log/trace (logging and tracing to NETSMART
application components).
[1535] Definitions:
[1536] Following are short definitions of the usual meanings of
some of the technical terms which are used in the present
application. (However, those of ordinary skill will recognize
whether the context requires a different meaning.) Additional
definitions can be found in the standard technical dictionaries and
journals.
[1537] The NETSMART terminology may have meanings that are slightly
different from standard telephony terms. The terms used are defined
below.
[1538] Access identifier (AID)--AIDs are address information
identifying a specific equipment slot or facility (traffic or
overhead channel).
[1539] Bidirectional line-switched ring (BLSR)--A BLSR is a ring
that provides working and protection fibers between nodes. If the
working fiber between nodes is cut, traffic is automatically routed
onto the protection fiber.
[1540] Common Language Equipment Identifier (CLEI.RTM.)--CLEI is a
standard code used by suppliers to identify equipment parts and
system configurations.
[1541] Correlation tag (CTAG)--CTAGs are required by TL1 and are
used to correlate the input TL1 and response messages.
[1542] Equipment protection group (EPG)--The EPG is used to
establish the working/protection relationship between two
cards.
[1543] Equipment--Equipment consists of the NEs and related
hardware within the telecommunications network.
[1544] Facility--The facility is the fiber or copper transmission
media used between NEs to transport telecommunications signals.
[1545] Fiber facility protection (FFP)--FFP is used to establish a
working/protection relationship between two or more facilities.
[1546] Fujitsu minimum support NE--A Fujitsu NE that is not on the
officially supported list but conforms to a basic set of TL1
commands will be managed as a minimally supported Fujitsu NE.
Support consists of logging on, adding links, displaying as an icon
on the topology map, and displaying alarms.
[1547] Group--Groups are logical associations of NEs to facilitate
NE management. For example, NEs can be placed in a group based on
location or type of NE.
[1548] Tool Action/Function Previous Select Previous to return to
the previous displayed topic. Next Select Next to reverse direction
and return to the topic where you first used Previous, one topic at
a time. Print Displays the Print dialog and allows you to print the
on-line help.
[1549] Link--A link is a communications channel or circuit that
carries a telecommunications signal between two NEs.
[1550] Logical link--The line displayed on the Topology window that
depicts one or more physical connections between NEs and/or groups
of NEs is referred to as a logical link. The line only represents
the actual network and can be removed without affecting the
network. Logical link names can be edited to conform to the
customer's particular naming convention.
[1551] NE--The term NE refers to hardware only or a combination
hardware and software system that is primarily designed to directly
perform a telecommunications service function. For example, an NE
is the part of the network equipment where a transport entity (such
as a line, path, or section) is terminated and monitored.
[1552] Path--A path at a given rate is a logical connection between
the points at which a standard frame format for the signal at the
given rate is assembled and disassembled.
[1553] Physical link--The line displayed on the Display Link window
that depicts a physical connection between the ports of two
different NEs is referred to as a physical link. The line only
represents the actual network and can be removed without affecting
the network. Physical link names, which are in the format
<TID>:<port>::<TID>:<- port>, are not
editable.
[1554] Port--In transmission control/Internet protocol (TCP/IP) and
user data protocol (UDP) networks, this is an end point to a
logical connection. The port number identifies what type of port it
is. For example, port 80 is used for HTTP traffic.
[1555] Synchronous Transport Signal Level 1 (STS-1)--The STS-1
signal is the basic logical building block of the SONET signal
structure. It consists of lower-order signals, payload, and
transport overhead for a combined signal rate of 51.84 Mb/s.
[1556] Target identifier (TID)--TIDs uniquely identify NEs. Fujitsu
NEs require from 7 to 20 alphanumeric characters. NETSMART allows
from 1 to 20 alphanumeric characters to address non-Fujitsu
NEs.
[1557] Time-slot assignment (TSA)--TSA allows STS-1 level traffic
to be added, dropped, or passed through a selected SONET NE. Time
slots are assigned on a dedicated basis. Service (i.e., DS1s
and/orDS3s) is mapped into these dedicated time slots in the
high-speed multiplexed signal.
[1558] Unidirectional path-switched ring (UPSR)--A UPSR consists of
a 2-fiber ring. The input signal is bridged in both directions to
provide redundant bandwidth. If a fiber is cut or a disruption
affects one direction, the signal is available from the other
direction.
[1559] Virtual tributaries (VTs)--VTs are structures designed to
transport and switch sub-STS-1 payloads. There are currently four
VT sizes: VT1.5 (VT container for a DS1 in SONET), VT2, VT3, and
VT6.
[1560] The preferred embodiment described above (Netsmart.TM.) does
not delimit the claimed inventions, but does provide a good
indication of their advantages, and of the capabilities which can
be included in a system implementing the claimed inventions.
Netsmart.TM. combines features of both network management and
element management layers of TMN model to provide comprehensive
management capabilities. Netsmart.TM. can manage very large
deployments (thousands of network elements, including both Fujitsu
and non-Fujitsu elements) while supporting many active users.
Netsmart.TM. provides a hierarchical view of the network from large
scale configuration down to the shelf and card level, all with a
GUI that displays the different scales. Several different views
make it easier for managers to monitor and control what is going on
in the system. Netsmart.TM. also provides graphical control over
surveillance, provisioning, software download (SWDL), remote memory
backup (RMBU), and remote memory restore (RMR). Netsmart.TM. also
features a rich graphical user interface which allows user to
perform operational tasks without entering data or TL1
Commands.
[1561] Modifications and Variations
[1562] As will be recognized by those skilled in the art, the
innovative concepts described in the present application can be
modified and varied over a tremendous range of applications, and
accordingly the scope of patented subject matter is not limited by
any of the specific exemplary teachings given.
[1563] Although the presently preferred embodiment has been
implemented as an EMS which is designed to interface to an NMS, the
disclosed innovations can be implemented with other choices as to
the software-hierarchy. For example, it is quite possible to
combine an NMS with EMS functionality, and the dividing line
between EMS and NMS is not a sharp divide. Similarly numerous other
functions (such as fault, configuration, account, performance,
and/or security management) can be combined if desired with the
primary functions of element management functions, and the
disclosed inventions can be applied to such expanded architectures
in various ways.
[1564] The TMN standard describes an overall software architecture
concept which interrelates the various components of
telecommunications system management. in addition to element
management and neetwork management layers, layers are also reserved
for business management and service management. Other functions can
also be combined into this hierarchy. The disclosed innovations are
not limited to a system which is solely an Element Manager System,
but can also be applied to other systems which include element
management functionality, even though such systems may not be EMS
systems strictly speaking.
[1565] None of the description in the present application should be
read as implying that any particular element, step, or function is
an essential element which must be included in the claim scope: THE
SCOPE OF PATENTED SUBJECT MATTER IS DEFINED ONLY BY THE ALLOWED
CLAIMS. Moreover, none of these claims are intended to invoke
paragraph six of 35 USC section 112 unless the exact words "means
for" are followed by a participle.
* * * * *
References