US7185075B1 - Element management system with dynamic database updates based on parsed snooping - Google Patents
Element management system with dynamic database updates based on parsed snooping Download PDFInfo
- Publication number
- US7185075B1 US7185075B1 US09/580,519 US58051900A US7185075B1 US 7185075 B1 US7185075 B1 US 7185075B1 US 58051900 A US58051900 A US 58051900A US 7185075 B1 US7185075 B1 US 7185075B1
- Authority
- US
- United States
- Prior art keywords
- meta
- select
- netsmart
- click
- nes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 claims abstract description 111
- 230000008569 process Effects 0.000 claims abstract description 48
- 230000015654 memory Effects 0.000 claims description 63
- 238000012544 monitoring process Methods 0.000 claims description 34
- 230000006854 communication Effects 0.000 claims description 32
- 238000004891 communication Methods 0.000 claims description 31
- 230000008859 change Effects 0.000 claims description 28
- 230000004044 response Effects 0.000 claims description 26
- 238000013459 approach Methods 0.000 abstract description 4
- 238000007726 management method Methods 0.000 description 114
- 239000000306 component Substances 0.000 description 96
- 230000006870 function Effects 0.000 description 37
- 230000000694 effects Effects 0.000 description 23
- 238000007639 printing Methods 0.000 description 23
- 230000004913 activation Effects 0.000 description 21
- 239000000835 fiber Substances 0.000 description 15
- 238000012423 maintenance Methods 0.000 description 13
- 230000001052 transient effect Effects 0.000 description 13
- 230000009471 action Effects 0.000 description 12
- 230000014509 gene expression Effects 0.000 description 12
- 230000003287 optical effect Effects 0.000 description 12
- 238000013461 design Methods 0.000 description 11
- 230000000712 assembly Effects 0.000 description 10
- 238000000429 assembly Methods 0.000 description 10
- 238000012790 confirmation Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 10
- 238000001914 filtration Methods 0.000 description 10
- 238000009434 installation Methods 0.000 description 10
- 238000012360 testing method Methods 0.000 description 10
- 238000012550 audit Methods 0.000 description 9
- 230000002457 bidirectional effect Effects 0.000 description 9
- 238000013499 data model Methods 0.000 description 9
- 238000012217 deletion Methods 0.000 description 8
- 230000037430 deletion Effects 0.000 description 8
- 230000003068 static effect Effects 0.000 description 8
- 238000013507 mapping Methods 0.000 description 7
- 238000012546 transfer Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 6
- 238000011156 evaluation Methods 0.000 description 6
- 230000008676 import Effects 0.000 description 6
- 230000001419 dependent effect Effects 0.000 description 5
- 206010010099 Combined immunodeficiency Diseases 0.000 description 4
- 230000001174 ascending effect Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 4
- 239000000969 carrier Substances 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 4
- 150000004945 aromatic hydrocarbons Chemical class 0.000 description 3
- 125000000524 functional group Chemical group 0.000 description 3
- 239000000203 mixture Substances 0.000 description 3
- 230000002085 persistent effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000000717 retained effect Effects 0.000 description 3
- 239000007787 solid Substances 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000013024 troubleshooting Methods 0.000 description 3
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 239000010949 copper Substances 0.000 description 2
- 229910052802 copper Inorganic materials 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000018109 developmental process Effects 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000002955 isolation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 238000005192 partition Methods 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 206010009192 Circulatory collapse Diseases 0.000 description 1
- 241000295146 Gallionellaceae Species 0.000 description 1
- 101710104937 Non-specific acid phosphatase Proteins 0.000 description 1
- 101150067286 STS1 gene Proteins 0.000 description 1
- 101100028967 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) PDR5 gene Proteins 0.000 description 1
- 101150027289 Ubash3b gene Proteins 0.000 description 1
- 102100040338 Ubiquitin-associated and SH3 domain-containing protein B Human genes 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003542 behavioural effect Effects 0.000 description 1
- 229910052729 chemical element Inorganic materials 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000001360 collision-induced dissociation Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 229910003460 diamond Inorganic materials 0.000 description 1
- 239000010432 diamond Substances 0.000 description 1
- 239000006185 dispersion Substances 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 230000003370 grooming effect Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000009474 immediate action Effects 0.000 description 1
- 238000005304 joining Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000010813 municipal solid waste Substances 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 230000003362 replicative effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
- 230000003442 weekly effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0681—Configuration of triggering conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/20—Network management software packages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- Backward compatibility allows NETSMART to manage an NE as if its software were at a higher release level than it actually is.
- Forward compatibility allows NETSMART to manage an NE as if its software were at a lower release level than it actually is.
NETSMART also provides Fujitsu Generic Support (FGS) for unknown Fujitsu NEs. FGS includes:
-
- Management of up to 4000 NEs from a single server platform
- Support for OSI DCN connectivity
- TL1 command line and batch file support
- Generic NE icon capability
- Distributed and scalable architecture
- Support for up to 50 simultaneous users
- Support for IP DCN connectivity
- TL1 console allows users to monitor TL1 communication between the NETSMART server and one or more managed NEs
- Intelligent uninterrupted power supply (UPS) support for greatly decreased start-up times after power failure and for enhanced protection from file system corruption
-
- Topological link and physical link views
- User-defined groups of NEs with the ability to easily move NEs between groups
- Tree-widget view of groups, similar to Windows® Explorer, allowing easy viewing and manipulation of managed NEs
- Tabular view of network information
-
- NE definition, profiles, and configuration autodiscovery
- Add user-defined NE or group attributes
- User-defined NE audit and reconciliation
- Select autonomous messages to be allowed upon NETSMART login
- Manual or automatic database reconciliation; option to update NE or NETSMART.
- NE shelf display with visual indications of equipment states
- GUI-based provisioning of attributes and services states for shelves, plug-in units, and facilities
- GUI-based cross-connect management, providing comprehensive management tools, including redline, DS0, hairpinning, FASTLANE™, and transmux cross-connect management
- Toolbar shortcuts (1-way, 2-way, 2-way add/drop, 1-way drop and continue, 2-way drop and continue)
- Bulk cross-connect operations
- Ability to assign a name to cross-connects
- DWDM wavelength management reports
-
- Remote NE software upgrades via OSI DCN
- Remote NE database backup and restoration via OSI DCN
- Ability to restore database to a different NE for rapid NE turn-up
- Remote NE software upgrades via IP DCN (FLASH-192 Release 4.2 and
FLM 2400 Release 14.2BS only) - Remote NE database backup and restoration via IP DCN (FLASH-192 Release 4.2 and
FLM 2400 Release 14.2BS only)
-
- Network wide inventory of NEs, shown in
FIG. 5 : TID, NE type, release level, audit state, DCN type. - E level inventory reports: CLEI code, part number, equipment service state, date of manufacture, etc.
- Equipment find function: Network-wide search for CLEI code or part number
- Network wide inventory of NEs, shown in
-
- An alarm banner at the top of the Topology window containing summary alarm counts and one-click access to alarm reports
- An active alarm list containing current alarms, standing conditions, alarm acknowledgment information, and alarm record annotations
- An alarm history log showing cleared alarms and cleared standing conditions.
- A transient condition log maintaining records of transient condition alarms (TCAs) received from managed NEs.
- and transient conditions
- Alarm-sensitive topology map and shelf views
- Audible alarm indications
- Customized alarm viewing options allowing user-defined sorting, filtering, column display/placement, and report layout
- One-click navigation from alarm record to Shelf view.
-
- Protection switch operation and release
- Facility loopback operation and release
- STS path trace
- DWDM section trace for the detection and isolation of errors between DWDM fiber facilities
-
- Enabling and disabling performance measurement collection from the NETSMART GUI
- Collection of both equipment- and facility-related measures with a 15-minute resolution
- Selection and display of PM information through customized NETSMART reports
- Printing and storage to external files through the NETSMART GUI
-
- GUI-based functional user profile management allows the customizing of roles through the combination of individual application features.
- Common user roles, such as server admin, client admin, cross-connect user, and alarms user are predefined and available out of the box.
- GUI-based user account management, including the ability to enable and disable accounts either on an on-demand or scheduled basis, are provided.
- Comprehensive security reporting, including reports listing defined users, users with active sessions, and historical user activity is provided.
Platform Requirements
- 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.
The disk size, tape and monitor can vary.
- Full Support: All NETSMART functions are available.
- Forward-Compatible Support:
- 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.
Using NETSMART
The following section describes:
-
- Only the client initiating the request will receive a response.
- Autonomous alarms sent from the NE will be received by all workstations.
- 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.
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.
Exiting the NETSMART Application
-
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
NETSMART Window Elements
Several types of Windows elements may appear in the NETSMART window area when commands are selected. These elements are:
-
- Main menu, the horizontal list of command names located immediately below the window title
- Associated drop-down menus for each main menu selection
- Pop-up menus, usually displayed from a mouse right-click action
-
- Note: Most of the main NETSMART™ 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.
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.
- Note: Most of the main NETSMART™ 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.
-
- 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.
-
- 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.
-
- Note: Deleting a parent group results in deletion of all groups under the parent group.
-
- Note: The selected group and NE will determine the contents of the fields on the Add Link dialog.
Tasks:
- Note: The selected group and NE will determine the contents of the fields on the Add Link dialog.
- 1 From the NETSMART Topology window, log on all NEs to be included in the link.
- 2 Select Add Link from the Edit menu or select the Link tool from the toolbar.
- 3 Using the Search button, select information in the following fields:
-
Group 1—Use this field along with the Search button to select a parent group. - 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.
-
Group 2—Use this field along with the Search button to select a parent group. -
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. - 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.
- 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.
-
- 4 Make a connection between the NEs using one of the following methods:
- 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.
- 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.
- 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.
Once a link is successfully created, connection lines will indicate link direction(s), as shown inFIG. 7 . Additional links can be added until all connections have been defined.
- 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.
- 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.
- 7 From the View menu, select Graphical to return to the Topology map display. The link displays on the topology map.
-
- An EditName tool can be used to change a physical link name.
- Multiple selection of rows can be used with the Delete and EditName operations.
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.
-
- Hold down the SHIFT key and click on the desired rows to select a contiguous set of records.
- Hold down the CTRL key and click on the desired rows to select a non contiguous set of records.
To view the Display Link dialog for the two NEs in the selected physical link, double-click on a row.
- Print Print up to 100 lines of the current information. Refer to Printing Overview for more information.
- Filter Display a dialog where you can specify criteria to filter the information in the display. Refer to Filtering Tabular Information for more information.
- Sort Display a dialog where you can specify criteria to sort the information in the display. Refer to Sorting Information.
- Columns Display a dialog where you can specify information to be shown or hidden. Refer to Setting Column Displays for more information.
- Deselect Deselect any selected rows.
- Reload Update the display with information from the database.
- Delete Delete selected physical links from the database.
- 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).
-
- The configurations for the specified NEs are not compatible.
- High-speed links already exist between two or more of the specified NEs.
- High-speed rates are not compatible for two or more of the specified NEs.
- The directions of the high-speed ports are not compatible for two or more of the specified NEs.
- The payloads of the high-speed ports are not compatible for two or more of the specified NEs.
- The port sequences of the high-speed ports are not compatible for two or more of the specified NEs.
-
- The configurations for the specified NEs are not compatible.
- High-speed links already exist between two or more of the specified NEs.
- High-speed rates are not compatible for two or more of the specified NEs.
- Directions of the high-speed ports are not compatible for two or more of the specified NEs.
- Payloads of the high-speed ports are not compatible for two or more of the specified NEs.
- Port sequences of the high-speed ports are not compatible for two or more of the specified NEs.
-
- Note: The squelch table may take some time to display because the information is retrieved from the NE.
-
- Note: Protection switching is not available on all facilities and equipment.
-
- 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.
- Note: Synchronization switching is not available on all NEs.
-
- Note: All crossconnects must be removed before a shelf can be deleted.
- 1 Log on the NE to be provisioned.
- 2 From the Configuration Manager window, select the Equipment tab.
- 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. - 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.
- 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.
-
- 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.
- 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.
- The total number of NEs is the total count of NEs in the system. 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.
- 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.
-
- The remote machine must be running with the FTP Server daemon active.
- You need log on access to the machine.
- You need to know the directory path on the remote machine where the generics reside.
-
- The remote machine must be running with the FTP Server daemon active.
- You need log-on access to the machine.
- You need to know the directory path on the remote machine where the generics reside.
-
- 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
- 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”.
- 1. The files are copied from NMS to the IP gateway NE RAM Disk.
- 2. Then files are copied from the gateway NE RAM Disk onto the IP subtending NE RAM Disk.
- 3. Finally, files are copied from the subtending NE RAM Disk to the corresponding CPUs on the IP subtending NE.
-
- The configuration files are copied to the RAM disk on the NE from active memory.
- The files are copied from the NE's RAM disk to NETSMART using the OSI FTAM protocol.
-
- The configuration files are copied to the RAM disk on the NE from active memory.
- The files are copied from the NE's RAM disk to NETSMART using the FTP protocol.
-
- The configuration files are copied to the RAM disk on the NE from active memory.
- Using the OSI FTAM protocol, the configuration files are copied from the subtending NE's RAM disk to its gateway NE's RAM disk.
- The configuration files are then copied to NETSMART using the FTP protocol.
-
- The configuration files are copied from NETSMART to the NE's RAM disk.
- The configuration files are copied from the RAM disk on the NE to standby memory.
- An activation of the standby memory needs to performed. Refer to Software Activation for information on software activation.
-
- The configuration files are copied from NETSMART to the NE's RAM disk using the FTP protocol.
- The configuration files are copied from the RAM disk on the NE to standby memory.
- An activation of the standby memory needs to performed. Refer to Software Activation for more information on software activation.
-
- The configuration files are copied from NETSMART to the gateway NE's RAM.
- 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.
- The configuration files are copied from the RAM disk on the subtending NE to standby memory.
- An activation of the standby memory on the subtending NE needs to performed. Refer to Software Activation for more information on software activation.
-
- 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.
- TR-008 (Mode I)—Choose an available feeder DS1 (A, B, C, or D).
- TR-008 (Mode II or III)—Choose an available feeder DS1 (A or C).
- TR-303—Choose an available DS1 (1 through 28).
- INA—The T1 crossconnects are automatically created between the feeder of the INA interface group and the VT1 of the low-speed group when the first DS0 crossconnect is created. You cannot create them, but they can be displayed.
Tasks:
1 Log on the NE to be crossconnected.- a. If Crossconnect Manager was selected from the NETSMART menu, the Configuration window displays. In the Configuration window, select the DS0 XC tab.
- 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.
- c. Click on the DS1 box to be connected, then drag the line to the port and click again. A dotted black line appears.
- Note: If the interface group or port (rectangle) is yellow, then it is already in use (possibly at a different speed).
- d. To complete the connection, click the Update tool or select Update NE from the Operations menu. The Confirmation dialog displays
- 1 Log on the NE to be crossconnected
- 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. - 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.
- 4 Select or type values in the following fields:
- 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.
- PCR—Type the Peak Cell Rate (PCR) per second.
- SCR—Type the Sustained Cell Rate (SCR) per second.
- Congestion Control—Select whether congestion control should be enabled or not.
- AAL-Type—Select the ATM Adaptation Layer (AAL). Only AAL5 is valid.
- From NE TID—The starting NE TID is the default value.
- To NE TID—Select the ending NE TID from the list.
- 5 Click Ok to add the ring VC and close the Ring VC creation dialog.
- 6 Click Apply to add the ring VC and leave the Ring VC creation dialog displayed.
- 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.
- 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.
- 9 To complete the connection, click the Update tool or select Update NE from the Operations menu. The crossconnect Confirmation dialog displays
-
- 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.
Tasks:
- Note: For
- 1 Log on the NE to be crossconnected
- 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. - 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.
- Note: Not all types of crossconnect are available at all times (depending on the NE type and the configuration).
- 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.
- 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).
- 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).
- 6 To complete the connection, click the Update tool or select Update NE from the Operations menu. The crossconnect Confirmation dialog displays
-
- 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.
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.
Tasks:
- Note: Hairpin crossconnects are supported for FLASH XC MV architecture. The FACTR or
- 1 Log on the NE to be crossconnected.
- 2 If Crossconnect Manager was selected from the NETSMART menu, the Configuration window displays. In the Configuration window, select the SONET XC tab
- 3 Select the Hairpinning option from the Operations menu. The HairPinning view (
FIG. 22 ) displays. - 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.
- 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.
- 6 When all of the crossconnects have been defined, click on the Update tool or select Update NE from the Operations menu.
- 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.
- 1 Log on the NE to be crossconnected
- 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. - 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.
- 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.
- 4 To complete the crossconnect, click on the Update tool or select Update NE from the Operations menu.
- 1 Log on the NE whose path is to be modified.
- 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.
- 3 Select the 1-way drop crossconnect to be bridged.
- 4 Click the Bridge tool or select Bridge from the Operations menu.
- 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.
- 6 To complete the connection, click the Update NE tool or select Update NE from the Operations menu.
- 1 Log on the NE whose path is to be modified.
- 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.
- 3 Select the 1-way crossconnect to be rolled from.
- 4 Click the Roll tool or select Roll from the Operations menu. A prompt displays directing you to select the destination time slot.
- 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.
- 6 To complete the connection, click the Update NE tool or select Update NE from the Operations menu.
- 1 To complete the crossconnect, click on the Update tool or select Update NE from the Operations menu. The crossconnect Confirmation dialog displays.
- 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.
- 3 Click the Close button to close the Crossconnect Report.
FIG. 24 shows the Crossconnect Report.
- 1 Log on the NE with the crossconnect(s).
- 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.
- 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.
- 4 Type a new name.
- 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.
- 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.
- 7 The Messages dialog box displays with the new name shown in the table. Click Ok.
- 1 Log on the NE with the crossconnect(s
- 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. - 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.
- 4 To complete the redline designation, click on the Update tool or select Update NE from the Operations menu.
- 1 Log on the NE where the crossconnect is to be deleted.
- 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.
- 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.
- 4 Click Ok to remove the redline.
- 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.
- 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.
- 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.
- 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.
- 1 Log on the NE where the SSDEF is to be reset. Access the appropriate crossconnect window.
- 2 Right-click on a crossconnect to display a menu.
- 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.
- 1 Log on the NE where the holdoff timer is to be set. Access the appropriate crossconnect window.
- 2 Right-click on a crossconnect to display a menu.
- 3 Select Holdoff Timer. Type a value for the reset interval.
- 1 Log on the NE. Access the appropriate crossconnect window.
- 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.
Manage Facilities
- 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). - 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.
- 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.
- 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.
- 1 From the Configuration Manager, select the Groups/Facilities tab.
- 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).
- 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.
- 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.
- 1 From any tab in the Configuration Manager, select the Managing Facilities option from the NE menu. The Managing Facilities dialog displays.
- 2 Select the shelf from the Shelf drop-down 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.
- Note: If there are no existing (created) facilities, there will be nothing in this list.
- 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
- 1 From any tab in the Configuration Manager, select the Manage FFP option from the NE menu. The Manage FFP dialog displays.
- 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.
- 3 Click the Create tool.
- 4 The FFP will move from the Non-Existing FFP to the Existing FFP column and will become active.
- 1 From the Configuration Manager, select the FFP tab
- 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.
- 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.
- 4 Click the Modify tool to download the changes to the NE. The changed values will be displayed in the Value column.
- 1 In any tab in the Configuration Manager, select the Manage FFP option from the NE menu. The Manage FFP dialog displays.
- 2 Select the shelf from the Shelf drop-down list.
- 3 Select the rate from the Rate drop-down list.
- 4 Select the FFP in the Existing FFP column.
- 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.
Managing Wavelengths
-
- 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.
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. | ||
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 | ||
If you open this window from the Topology window, the following selections are available:
- 1 From the NETSMART menu, select Wavelength Management. The Wavelength Management window displays.
- 2 The list area contains a list of all FLASHWAVE terminal NEs. Click on an NE to display its data.
- 3 To filter the columns of the data display, select the Filter tool from the toolbar.
- 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.
- 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:
- contains
- !contains
- starts with
- !starts with
- ends with
- ends with
- 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.
- 7 Once all filtering values are selected, click Ok to redisplay the Wavelength Management values with the filter(s) applied.
NGDLC Services
- 1 Log on the NE.
- 2 From the Configuration Manager, select the Interface Type tab. The Interface Type tab displays.
- 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.
- 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
- 5 Click the Modify tool or select the Update option from the Operations menu to make the changes.
- 6 Click to select the tool for the correct operation: InServ, OOSMA, OOSMT. The same options can also be chosen from the Operations menu.
- 1 Log on the NE.
- 2 From the Configuration Manager, select the Interface Type tab.
- 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.
- 4 The Attributes dialog (
FIG. 27 ) displays. - 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.
- 6 Click the Modify tool to complete the changes.
- 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.
Performance Management
- Element View: Accessing Performance Manager from the Topology window displays the Element View.
- Equipment View: Accessing Performance Manager from the Configuration Manager—Equipment Tab displays the Equipment View.
- Groups/Facilities View: Accessing Performance Manager from the Configuration Manager Groups/Facilities tab displays the Groups/Facilities View.
- 1 To begin monitoring, select the Monitors tab in the Performance Manager window. This is the default tab for the Element view.
- 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.
- 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.
- 4 To add all items to the Selected Elements column, click the Add All button.
- 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.
- 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
- 7 Click the Mon On tool in the toolbar or select Turn Performance Monitoring On from the Operations menu (
FIG. 28 ). - 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.
- 1 Select the Registers tab in the Element view (
FIG. 29 ). - 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.
- 3 To remove an item from the Selected Elements column, highlight the item in the Selected Elements column and click the Remove button.
- 4 To add all items to the Selected Elements column, click the Add All button.
- 5 To remove all the items in the Selected Elements column, click the Remove All button.
- 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.
- 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
- 1 Select the Database tab in the Element view (
FIG. 30 ). - 2 Select the element(s) from the Available Elements list.
- 3 Use the Add button to add it to the Selected Elements column.
- 4 To remove an item from the Selected Elements column, highlight the item in the Selected Elements column and click the Remove button.
- 5 To add all items to the Selected Elements column, click the Add All button.
- 6 To remove all the items in the Selected Elements column, click the Remove All button.
- 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.
- 7 Select or type values in the following fields:
- 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.
- NMS Start Date—Select the date when NETSMART started receiving data from the NE. A default format is provided.
- NMS Start Time—Select the time when NETSMART started receiving data from the NE.
- NMS End Date—Select the date when NETSMART stopped receiving data from the NE.
- NMS End Time—Select the time when NETSMART stopped receiving data from the NE.
- 8 Select Reload from the Operations menu or click the Reload tool from the toolbar to start retrieving data.
-
- NMS Time—NETSMART time.
- NE Time—The time on the NE.
- AID Type—Type of Access Identifier.
- AID—Access Identifier name.
- Register—Register name.
- Value—Value of the register that was retrieved.
- Range—Allowable range for the register Value.
- Threshold—Indicator to the NE to regenerate the threshold report if the threshold was exceeded.
- 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”.
- 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.
- Location—This value indicates where the data is coming from (near-end or far-end). Equipment registers will always be far-end.
- 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.
- 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.
- 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.
- 1 Select equipment from the Available Equipment list and click the Add button to add the equipment to the Selected Equipment list
- 2 Select a numbered row in the report and then click the Set tool in the toolbar. The Set Thresholds dialog displays.
- 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.
- 4 Click OK to select the threshold and close the dialog.
- 1 Select equipment from the Available Equipment list and click the Add button to add them to the Selected Equipment list.
- 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.
-
- NMS Time—NETSMART time.
- NE Time—The time on the NE.
- AID Type—Type of Access Identifier.
- AID—Access Identifier name.
- Register—Register name.
- Value—Value of the register that was retrieved.
- Range—Allowable range for the register Value.
- Threshold—Indicator to the NE to regenerate the threshold report if the threshold was exceeded.
- 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”.
- 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.
- Location—This value indicates where the data is coming from (near-end NEND or far-end FEND).
- Direction—Typically the value reported for facilities will be Tx or Rx.
- Time Interval—For facilities the time reporting interval will be displayed as either 15 MIN or 1 DAY.
- Index—For facilities, the current register (0) plus
previous registers 1 to 32 will be displayed
- 1 To start monitoring, select the Monitors tab in the Performance Manager Groups/Facilities view. The reporting status is automatically retrieved and displayed.
- 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.
- 3 To remove an item from the Selected Facilities column, highlight it in the Selected Facilities column and click the Remove button.
- 4 To add all the items to the Selected Facilities column, click the Add All button.
- 5 To remove all the items in the Selected Facilities column, click the Remove All button.
- 6 Choose the location by selecting one of the Location radio buttons. Possible choices are NEND (near-end) or FEND (far-end).
- 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.
- 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.
- 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.
- 10 Click the Mon On tool in the toolbar to start monitoring.
- 11 To stop monitoring, select the Monitors tab and then click the Mon Off tool in the toolbar
- 1 Select the Registers tab in the Groups/Facilities view.
- 2 Select the Init tool in the toolbar. Selecting this option will initialize all the selected NE facility registers to zero.
- 1 Select the facilities from the Available Facilities list and click the Add button to add them to the Selected Facilities list.
- 2 Choose the location by selecting one of the Location radio buttons. Possible choices are NEND (near-end) or FEND (far-end).
- 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.
- 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.
- 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.
- 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.
- 1 Select the Registers tab in the Groups/Facilities view.
- 2 Select facilities from the Available Facilities list and use the Add button to add them to the Selected Facilities list.
- 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.
- 4 Click Ok to save the changes and close the dialog.
- 1 Select the Database tab in the Groups/Facilities view.
- 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.
- 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.
- 4 Type values in the following fields:
- NMS Start Date—Select the date when NETSMART started receiving data from the NE.
- NMS Start Time—Select the time when NETSMART started receiving data from the NE.
- NMS End Date—Select the date when NETSMART stopped receiving data from the NE.
- NMS End Time—Select the time when NETSMART stopped receiving data from the NE.
- 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, NMS Start Date, NMS Start Time, NMS End Date, and NMS End Time.
TL1 Command and Batch Processing
-
- The upper part will contain any commands that were typed in the TL1 Command text entry area
- The middle part will contain any results/responses generated by this command.
- 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.
- 1 In the Raw TL-1/TL-1 Batch Window, type in the TL1 command in the TL1 Command field.
- 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.
- 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 (
FIG. 4-144 ). - 2 Select TIDs from the Batch menu. The TID List dialog displays.
- 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.
- 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.
- 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.
- 6 Click Ok to select the TID(s).
- 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.
- 8 Click to select the file to be imported or exported. Only one file at a time can be selected.
- 9 Click OK to select the file and close the dialog.
- 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.
- 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.
- 12 Select or type values in the following fields:
- 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.
- Owner—Displays the user name that logged on NETSMART. Data cannot be entered in this field.
- 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.
- 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.
- 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.
- Password:—Enter the password for the User ID that was typed in the UID field.
- 13 Click Ok to save the property settings or Cancel to close the dialog without making changes.
- 14 To save the batch file, click the Save As tool or select Save As from the File menu.
- 1 When the Save As . . . dialog displays, type a value in the Batch name field. The file will be saved using this name.
- 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.
- 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.
- 2 To add or change TIDs, select TIDs from the Batch menu. The TID List dialog displays.
- 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.
- 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.
- 5 Click Ok to select the TID(s).
- 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.
- 7 Click to select the file to be imported or exported. Only one file at a time can be selected.
- 8 Click OK to select the file and close the dialog.
- 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.
- 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.
- 11 Select or type to change values in the following fields:
- 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.
- Owner—Displays the user name that logged on to NETSMART. Data cannot be entered in this field.
- 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.
- 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.
- 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.
- Password:—Enter the password for the User ID that was typed in the UID field.
- 12 Click Ok to save the property settings or Cancel to close the dialog without making changes.
- 13 To save the batch file, click the Save As tool or select Save As from the File menu.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 3 To remove an attribute from the Selected List, highlight the attribute in the Selected List and then click the Remove button.
- 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.
- 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.
- 6 Click OK to save the settings and close this dialog or click Cancel to cancel all changes and close this dialog.
- 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.
- 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:
- Starts with—If you want the NE to start with the specified value.
- Ends With—If you want the NE to end with the specified value.
- 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.
- 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 TL1Console 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.
- 4 Click OK to make the changes and close the dialog or click Cancel to close the dialog without making any changes.
Reports
-
- A global view (all physical links in the system)
- A group link view (all physical links belonging to a particular link that is displayed on the Topology map window)
- 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. - 2 Use the tools on the toolbar or select Operations menu items to perform the following functions.
- Select the Print tool to display the Print dialog to print a report.
- Select the Filter tool to display the Filter dialog to filter the information displayed.
- Select the Sort tool to display the Sort dialog to sort the information displayed.
- Select the Columns tool to display the Column Settings dialog to determine the columns to be displayed.
- 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.
- Select the Reload tool to reload information from the NETSMART database.
- 3 Once you have completed operations in this dialog, click Close to close the report.
- 1 Access this dialog by selecting Query NE from the Topology view Edit Menu.
- 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.
- 3 Click Ok to produce the report or click Cancel to cancel and close this dialog.
- 4 The NETSMART Crossconnect Report window displays.
- 5 Use the tools on the toolbar or select Operations menu items to perform the following functions.
- Select the Print tool or select Print from the Operations menu to display the Print dialog to print a report.
- Select the Filter tool or select Filter from the Operations menu to display the Filter dialog to filter the information displayed.
- Select the Sort tool or select Sort from the Operations menu to display the Sort dialog to sort the information displayed.
- 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.
- In a multipage report, use the Previous and Next tools to go to the previous and next page of the report.
- Use the DelXC tool to delete a crossconnect.
- 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.
- Select the Reload tool to reload information from the NETSMART database.
- 6 When completing operations in this window, select Close from the File menu to close the report.
- 1 After the NETSMART Crossconnect Trail Report displays, select the row(s) to delete using the mouse. For multiple selections, you have two options:
- Hold down the SHIFT key and click on the desired rows to select a contiguous set of records.
- Hold down the CTRL key and click on the desired rows to select a non contiguous set of records.
- 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.
- 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.
- 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.
Printing
-
- Note: A maximum of 100 lines of output is produced for each report.
- 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.
- 2 Select or type values in the following fields:
- Print To—Select the output format: Printer, Text File, or PostScript File.
- 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.
- File Name:—If you are printing to a file, use this field to type a file name.
- Orientation—For printer output, select whether the printed output should be in landscape or portrait format.
- Paper Size—For printer output, select the size of paper for the printed report.
- 3 Use the Preview . . . button to display a print preview.
- 4 Use the Setup . . . button to set up printing parameters.
- 5 Click Ok to send the data to the specified output device.
- 6 Click Apply to apply the changes and leave the dialog open.
- 7 Click Cancel to close the dialog without sending the data to the output device.
- 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.
- 2 Select or type values in the following fields:
- Print To—Select one of Text Fi 1 e or PostScript File.
- Printer Command:—For text/postscript file output, this field will be grayed-out and unavailable.
- 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.
- Orientation—This field is grayed out and not available for text/postscript file output.
- Paper Size—This field is grayed out and not available for text/postscript file output.
- 3 Use the Preview . . . button to display a print preview.
- 4 Use the Setup . . . button to set up printing parameters.
- 5 Click Ok to save the data to the specified location.
- 6 Click Apply to apply the changes and leave the dialog open.
- 7 Click Cancel to close the dialog without saving any data.
- 1 After displaying a graphical view, print the view by selecting the Print View option on the File menu. The NETSMART Print dialog.
- 2 Select or type values in the following fields:
- Print To—Select the output format: Printer, Text File or PostScript File.
- 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.
- File Name:—If you are printing to a file, use this field to type a file name.
- Orientation—For printer output, select whether the printed output should be in landscape or portrait format.
- Paper Size—For printer output, select the size of paper for the printed report.
- 3 Use the Preview . . . button to display a print preview.
- 4 Use the Setup . . . button to set up printing parameters.
- 5 Click Ok to send the data to the specified output device.
- 6 Click Apply to apply the changes and leave the dialog open.
- 7 Click Cancel to close the dialog without sending the data to the output device.
- 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.
- 2 Select a row or rows for printing. For multiple print elections, you have two options:
- Hold down the SHIFT key and click on the desired rows to select a contiguous set of records.
- 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.
- 3 Click on the File menu, then select the Print menu item.
- 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.
- 1 After displaying a report with the appropriate data, select the Print Preview option from the File menu. The NETSMART Print Preview dialog displays.
- 2 Select the Print button to display the Print dialog.
- 3 Click the Close button to close the Print Preview dialog.
- 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.
- 2 Click to select the Setup . . . button. The NETSMART Page Setup dialog displays.
- 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.
- 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.
- 5 In the Header field, type a value that will be used as the header information for the print output.
- 6 In the Footer field, type a value that will be used as the footer information for the print output.
- 7 Check the Fit Page Width box to fit the print output within the page width.
- 8 Click Ok to send the output to the selected printer.
- 9 Click Apply to make the changes but keep this dialog open.
- 10 Click Cancel to close the dialog without printing.
Filtering Tabular Information
- 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.
- 2 Click on a button beneath the Field label to display a drop-down list to select a field.
- 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:
- contains
- !contains
- starts with
- !starts with
- ends with
- !ends with
- 4 Use Boolean values to filter by selecting one of AND/OR from the choice boxes beneath the Logic button.
- 5 Once all filtering values are selected, click Ok to redisplay the information with the filter(s) applied.
Sorting Information
- 1 Click on the Sort tool or select Sort from the Operations menu. The Sort dialog displays.
- 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.
- 3 Select the sort parameters. The order in which you select the Sort By buttons will determine the sort order.
- 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).
- 5 Click Ok to begin the sort. The data will redisplay in the sort order that you specified.
Setting Column Displays
- 1 Click on the Columns tool or select Column Settings from the Operations menu. The Column Settings dialog displays.
- 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.
- 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.
- 4 Click Ok to confirm the column settings.
View Logs
-
- Activity Log Manager
- Fault Manager
- TL1 Log Manager
- 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.
- 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.
- 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.
- Note: It takes approximately 30 seconds to 1 minute for an action to be added to the Activity Log.
- 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.
- 1 From the NETSMART menu, select Log Managers. From the cascading menu to the right of Log Managers select TL1 Log Manager.
- 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.
Introduction to Meta Model
-
- Provide the application with the ability to design using typed interfaces while maintaining the models generically.
-
- 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.
- 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
- 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.
- Implementing a data cache java class for fetching configuration information from network element during the process of Autodiscovery.
- Testing autodiscovery for the network element.
- Code review for the model.
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— | varchar2(15) | The type value used by the |
TYPE | application for this compo- | |
nent. (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 APPLICA- | ||
TION_TYPE. | ||
NAMING_KEY | varchar2(15) | Some components have a naming |
key. It is analogous to the appli- | ||
cations 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. | ||
Constraints:
Table Column | Datatype | Description |
NE_BASE | varchar2(32) | The base network element identi- |
fier (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 |
Constraints:
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 appli- | ||
cation 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. | ||
Constraints:
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. | ||
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 ele- |
ment 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) | ||
Constraints:
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 prop- | |
erty name. Used to distinguish | ||
identical property names with | ||
conditions. | ||
CONDITION | A condition expression which | |
can optionally be attached | ||
to the property. The dynamic | ||
evaluation of the conditional | ||
expression must be evaluted | ||
to true in order for the com- | ||
ponent to access this property. | ||
Constraints:
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 PROP- | ||
ERTY_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 | Although the data model, |
(256) | 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 | ||
| ||
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. | ||
The following are | ||
not available in 2.i. | ||
PROPERTYKEY | A unique identifier for a prop- | |
erty name. Used to distinguish | ||
identical properly names with | ||
conditions. | ||
ATTRKEY | A unique identifier for an | |
attribute name. Used to | ||
distinguish identical attri- | ||
bute name with conditions. | ||
META_COMP_ID | The component identifier | |
which is associated with | ||
this properly. 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. | ||
Constraints:
-
- Primary key: NE_BASE, META_ATTRIBUTE_ID
- Foreign key: (NE_BASE, META_PROPERTY_ID) references meta_property(NE_BASE, META_PROPERTY_ID)
- ATTRNAME is NOT NULL
- TYPE must be in (‘String’, ‘Integer’, ‘Boolean’, ‘Float’, ‘Enum’, ‘Class’)
- READ_ONLY must be either in ‘true’ or ‘false
- Valid values for REQUIRED must be either ‘true’ or ‘false’
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 condi- | ||
tional expression must be | ||
evaluated to true for the | ||
component instance to | ||
access this attribute. | ||
Constraints:
-
- Primary key: NE_BASE, META_ID, META_ATTRIBUTE_ID
- Foreign key: (NE_BASE, META_ATTRIBUTE_ID) references meta_attribute(NE_BASE, META_ATTRIBUTE_ID)
- Foreign key: (NE_BASE, META_ID) may reference either meta_instance(NE_BASE, META_INST_ID) or meta_instance(NE_BASE, META_COMP_ID)
Table Column | Datatype | Description |
NE_BASE | varchar2(32) | The base network element identi- |
fier (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. | ||
Constraints:
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 Relative- | ||
ComponentID. | ||
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 speci- | ||
fies the relative priority. | ||
INHERITED | varchar2(5) | Specifies whether value for |
RelativeComponentID is | ||
inherited from ancestor. | ||
Constraints
-
- Foreign key: (NE_BASE, META_INST_ID) references meta_instance(NE_NBASE, META_INST_ID)
- INC should not be <0 or > MAX
- INHERITED must be either ‘true’ or ‘false’
- MAX should not be less than MIN
Table Column | Datatype | Description |
NAME | varchar2(256) | Used as a temporary work space |
during data load pro-cess. | ||
Table Column | Datatype | Description | ||
NAME | varchar2(700) | Temporary | ||
ID | integer | Used to identify NAME | ||
Constraints:
Table Column | Description |
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. | |
- CONTAINS Used to model containment between two objects.
- 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.
- 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.
- IS_SUPPORTED_BY Used to capture relationship between functional groups and slots supporting those groups.
- HAS_WORKING_PARTICIPANT Used to capture relationship between a protection group (equipment or facility) and working object in that group.
- HAS_PROTECTING_PARTICIPANT Used to capture relationship between a protection group (equipment or facility) and protecting object in that group.
- SUPPORTS_PORT Used to capture relationship between port and equipment supporting that port.
- 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.
- 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.
- IS_DEFAULT_WAY_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.
- CONTAINS_AS_WORKING Used to model relationship between line termination point and working time slot groups contained in it.
- CONTAINS_AS_WORKING_DEFAULT Used to model relationship between line termination point and default working time slot groups (if any) contained in it.
- CONTAINS_FOR_PROTECTING Used to model relationship between line termination point and protecting time slot groups contained in it.
-
- 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. - 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.
- 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’.
- 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’.
- 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.
- 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.
- 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.
- 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.
- 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, pl see FLM600/*.db files.
- MetaObjects to represent CPUs have to be named as <string1>–<string2> While <
-
- 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.
- 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(“CONF5”)==“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 DataObject4 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. 4 DataObject is a java class in NETSMART.
- 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 ComponentID5. 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. 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.
- 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:
- 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. - 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
- 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.
- 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.
- 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.
- 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
- 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.
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.
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. 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.
Process Architecture
- Access identifier (AID)—AIDs are address information identifying a specific equipment slot or facility (traffic or overhead channel).
- 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.
- Common Language Equipment Identifier (CLEI®)—CLEI is a standard code used by suppliers to identify equipment parts and system configurations.
- Correlation tag (CTAG)—CTAGs are required by TL1 and are used to correlate the input TL1 and response messages.
- Equipment protection group (EPG)—The EPG is used to establish the working/protection relationship between two cards.
- Equipment—Equipment consists of the NEs and related hardware within the telecommunications network.
- Facility—The facility is the fiber or copper transmission media used between NEs to transport telecommunications signals.
- Fiber facility protection (FFP)—FFP is used to establish a working/protection relationship between two or more facilities.
- 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.
- 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.
- 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.
- Link—A link is a communications channel or circuit that carries a telecommunications signal between two NEs.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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/or DS3s) is mapped into these dedicated time slots in the high-speed multiplexed signal.
- 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.
- 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.
Claims (11)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/580,519 US7185075B1 (en) | 1999-05-26 | 2000-05-25 | Element management system with dynamic database updates based on parsed snooping |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13588399P | 1999-05-26 | 1999-05-26 | |
US09/580,519 US7185075B1 (en) | 1999-05-26 | 2000-05-25 | Element management system with dynamic database updates based on parsed snooping |
Publications (1)
Publication Number | Publication Date |
---|---|
US7185075B1 true US7185075B1 (en) | 2007-02-27 |
Family
ID=37769757
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/580,519 Expired - Fee Related US7185075B1 (en) | 1999-05-26 | 2000-05-25 | Element management system with dynamic database updates based on parsed snooping |
Country Status (1)
Country | Link |
---|---|
US (1) | US7185075B1 (en) |
Cited By (71)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040109683A1 (en) * | 2002-08-21 | 2004-06-10 | Meriton Networks Inc. | Non-disruptive lightpath routing changes in WDM networks |
US20040120270A1 (en) * | 2002-12-18 | 2004-06-24 | Bellsouth Intellectual Property Corporation | System and method for enhanced sonet network analysis |
US20040158455A1 (en) * | 2002-11-20 | 2004-08-12 | Radar Networks, Inc. | Methods and systems for managing entities in a computing device using semantic objects |
US20050010929A1 (en) * | 2003-06-20 | 2005-01-13 | Gongqian Wang | System and method for electronic event logging |
US20050025068A1 (en) * | 2003-07-30 | 2005-02-03 | Alcatel | Network element with autodiscovery of link connections |
US20050050196A1 (en) * | 2003-08-25 | 2005-03-03 | Lucent Technologies Inc. | Method and apparatus for managing and graphically representing elements in a network |
US20050086236A1 (en) * | 2003-10-20 | 2005-04-21 | International Business Machines Corporation | Systems and methods for providing autonomous persistent storage systems |
US20050135276A1 (en) * | 2003-12-18 | 2005-06-23 | Alcatel | Network with spanning tree for guiding information |
US20050198581A1 (en) * | 2004-03-05 | 2005-09-08 | Soderberg Eric M. | Copy-and-paste functionality for network reconfiguration |
US20050198216A1 (en) * | 2004-02-02 | 2005-09-08 | Behera Manas K. | Method for managing a network using a plurality of databases |
US20050232168A1 (en) * | 2004-04-15 | 2005-10-20 | Citrix Systems, Inc. | Methods and apparatus for synchronization of data set representations in a bandwidth-adaptive manner |
US20060020696A1 (en) * | 2004-07-20 | 2006-01-26 | Fang-Pang Lin | Wireless remote control system and method thereof |
US20060026272A1 (en) * | 2004-07-29 | 2006-02-02 | Nortel Networks Limited | Method and apparatus for efficient communication of management data |
US20060041567A1 (en) * | 2004-08-19 | 2006-02-23 | Oracle International Corporation | Inventory and configuration management |
US20060190578A1 (en) * | 2005-01-28 | 2006-08-24 | Nelson Ellen M | Method for implementing TopN measurements in operations support systems |
US20060195891A1 (en) * | 2005-02-25 | 2006-08-31 | Freyman Phillip K | Network status indication system |
US20070011356A1 (en) * | 2005-05-26 | 2007-01-11 | Citrix Systems, Inc. | A method and system for synchronizing presentation of a dynamic data set to a plurality of nodes |
US20070090951A1 (en) * | 2005-10-25 | 2007-04-26 | Sap Ag | Systems and methods for visualizing auto-id data |
US20070255827A1 (en) * | 2006-04-26 | 2007-11-01 | Microsoft Corporation | Termination of a security association between devices |
US20070271599A1 (en) * | 2003-05-28 | 2007-11-22 | Citrix Silicon Valley | Systems and methods for state signing of internet resources |
US20080010497A1 (en) * | 2006-06-12 | 2008-01-10 | Curtis Duane Kronlund | Selecting a Logging Method via Metadata |
US20080065756A1 (en) * | 2006-09-08 | 2008-03-13 | Frances Jean Hardwick | Method and system for presenting network devices on a display screen of a network management system |
US20080082535A1 (en) * | 2006-09-29 | 2008-04-03 | Sven-Eric Eigemann | Method and system for automatically generating a communication interface |
US7380244B1 (en) * | 2004-05-18 | 2008-05-27 | The United States Of America As Represented By The Secretary Of The Navy | Status display tool |
US20080189267A1 (en) * | 2006-08-09 | 2008-08-07 | Radar Networks, Inc. | Harvesting Data From Page |
US20080228772A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods of prefreshening cached objects based on user's current web page |
US20080229025A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods of using the refresh button to determine freshness policy |
US20080225728A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods for providing virtual fair queueing of network traffic |
US20080229024A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods of dynamically checking freshness of cached objects based on link status |
US20080250138A1 (en) * | 2007-04-03 | 2008-10-09 | Alcatel Lucent | Multiple displays of large dynamic alarm windows |
US20080306959A1 (en) * | 2004-02-23 | 2008-12-11 | Radar Networks, Inc. | Semantic web portal and platform |
US20090030982A1 (en) * | 2002-11-20 | 2009-01-29 | Radar Networks, Inc. | Methods and systems for semantically managing offers and requests over a network |
US20090077062A1 (en) * | 2007-09-16 | 2009-03-19 | Nova Spivack | System and Method of a Knowledge Management and Networking Environment |
US20090106307A1 (en) * | 2007-10-18 | 2009-04-23 | Nova Spivack | System of a knowledge management and networking environment and method for providing advanced functions therefor |
US20090112908A1 (en) * | 2007-10-30 | 2009-04-30 | Sap Ag | Method and System for Generic Extraction of Business Object Data |
US20090119768A1 (en) * | 2004-06-30 | 2009-05-07 | Walters Robert V | Using Application Gateways to Protect Unauthorized Transmission of Confidential Data Via Web Applications |
US20090172528A1 (en) * | 2007-12-31 | 2009-07-02 | Ramprasad S | System and method for dynamically presenting a software system landscape |
US20090287842A1 (en) * | 2007-03-12 | 2009-11-19 | Robert Plamondon | Systems and methods of prefetching objects for caching using qos |
US20100004975A1 (en) * | 2008-07-03 | 2010-01-07 | Scott White | System and method for leveraging proximity data in a web-based socially-enabled knowledge networking environment |
US7673139B1 (en) * | 2004-05-06 | 2010-03-02 | Symantec Corporation | Protecting administrative privileges |
WO2010028380A2 (en) * | 2008-09-08 | 2010-03-11 | Futurewei Technologies, Inc. | Object modeling scheme for next generation network wavelength division multiplexing |
US20100088398A1 (en) * | 2007-03-12 | 2010-04-08 | Robert Plamondon | Systems and methods for domain name resolution interception caching |
US20100268596A1 (en) * | 2009-04-15 | 2010-10-21 | Evri, Inc. | Search-enhanced semantic advertising |
US20100268702A1 (en) * | 2009-04-15 | 2010-10-21 | Evri, Inc. | Generating user-customized search results and building a semantics-enhanced search engine |
US20100268720A1 (en) * | 2009-04-15 | 2010-10-21 | Radar Networks, Inc. | Automatic mapping of a location identifier pattern of an object to a semantic type using object metadata |
US20100268700A1 (en) * | 2009-04-15 | 2010-10-21 | Evri, Inc. | Search and search optimization using a pattern of a location identifier |
US7827139B2 (en) | 2004-04-15 | 2010-11-02 | Citrix Systems, Inc. | Methods and apparatus for sharing graphical screen data in a bandwidth-adaptive manner |
US20100281112A1 (en) * | 2007-03-12 | 2010-11-04 | Robert Plamondon | Systems and methods of revalidating cached objects in parallel with request for object |
US7924884B2 (en) | 2005-12-20 | 2011-04-12 | Citrix Systems, Inc. | Performance logging using relative differentials and skip recording |
US20110179371A1 (en) * | 2010-01-19 | 2011-07-21 | Verizon Patent And Licensing, Inc. | Provisioning Workflow Management Methods and Systems |
US20110179037A1 (en) * | 2008-07-30 | 2011-07-21 | Hironori Mizuguchi | Data classifier system, data classifier method and data classifier program |
US8060600B1 (en) * | 2007-03-02 | 2011-11-15 | Sprint Communications Company L.P. | Network element management system |
US8103783B2 (en) | 2007-03-12 | 2012-01-24 | Citrix Systems, Inc. | Systems and methods of providing security and reliability to proxy caches |
US20120082169A1 (en) * | 2009-06-09 | 2012-04-05 | Zte Corporation | Method and apparatus for fast passing through services for synchronous digital hierarchy device |
CN102571440A (en) * | 2012-01-19 | 2012-07-11 | 中兴通讯股份有限公司 | Network management operation method and system |
US20120324456A1 (en) * | 2011-06-16 | 2012-12-20 | Microsoft Corporation | Managing nodes in a high-performance computing system using a node registrar |
US20130086130A1 (en) * | 2011-09-30 | 2013-04-04 | Oracle International Corporation | Executor for software configuration automation |
US8462631B2 (en) | 2007-03-12 | 2013-06-11 | Citrix Systems, Inc. | Systems and methods for providing quality of service precedence in TCP congestion control |
US20140317487A1 (en) * | 2000-05-24 | 2014-10-23 | Clickfox, Llc | System and method for modifying links within a web site |
US20150127790A1 (en) * | 2013-11-05 | 2015-05-07 | Harris Corporation | Systems and methods for enterprise mission management of a computer nework |
US9342589B2 (en) | 2008-07-30 | 2016-05-17 | Nec Corporation | Data classifier system, data classifier method and data classifier program stored on storage medium |
US20170033864A1 (en) * | 2015-07-30 | 2017-02-02 | Infinera Corporation | Digital link viewer for data center interconnect nodes |
US20170060383A1 (en) * | 2009-12-08 | 2017-03-02 | Hand Held Products, Inc. | Remote device management interface |
US9621426B1 (en) * | 2007-04-18 | 2017-04-11 | Grass Valley USA, LLC | Switching facility having a control panel with relegendable buttons |
US9629928B1 (en) * | 2008-03-31 | 2017-04-25 | Symantec Corporation | Hash-based inventory identification |
US20170223075A1 (en) * | 2014-10-22 | 2017-08-03 | Huawei Technologies Co., Ltd. | Streaming Application Upgrading Method, Master Node, and Stream Computing System |
US10277485B1 (en) * | 2015-08-21 | 2019-04-30 | Amazon Technologies, Inc. | Network device testing using non-destructive techniques |
CN110750425A (en) * | 2019-10-25 | 2020-02-04 | 上海中通吉网络技术有限公司 | Database monitoring method, device and system and storage medium |
US10628246B1 (en) * | 2013-05-20 | 2020-04-21 | The Boeing Company | Methods and systems for prioritizing corrective actions in a troubleshooting chart |
US11126323B2 (en) | 2004-11-09 | 2021-09-21 | Blackberry Limited | Dynamic bar oriented user interface |
US11507262B2 (en) * | 2017-02-22 | 2022-11-22 | Ciena Corporation | Methods and systems for managing optical network services including capacity mining and scheduling |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5726979A (en) | 1996-02-22 | 1998-03-10 | Mci Corporation | Network management system |
US5761432A (en) | 1996-07-15 | 1998-06-02 | At&T Corp | Method and apparatus for providing an efficient use of telecommunication network resources |
US5892950A (en) | 1996-08-09 | 1999-04-06 | Sun Microsystems, Inc. | Interface for telecommunications network management |
US5953347A (en) | 1994-09-19 | 1999-09-14 | Crosskeys Systems Corporation | Integrated management of multiple networks with different topologies |
US6038301A (en) | 1997-12-31 | 2000-03-14 | Alcatel Usa Sourcing, L.P. | Method and system for engineering a service in an advanced intelligent network |
US6094145A (en) * | 1995-09-11 | 2000-07-25 | Alcatel Cit | Telecommunication management system |
US6108309A (en) * | 1997-12-08 | 2000-08-22 | Mci Communications Corporation | SONET network element simulator |
US6128656A (en) * | 1998-09-10 | 2000-10-03 | Cisco Technology, Inc. | System for updating selected part of configuration information stored in a memory of a network element depending on status of received state variable |
US6222827B1 (en) * | 1995-12-28 | 2001-04-24 | Nokia Telecommunications Oy | Telecommunications network management system |
US6240174B1 (en) | 1998-05-14 | 2001-05-29 | International Business Machines Corporation | Two way transmission of subscriber provisional data for an intelligent peripheral in an advanced intelligent network (AIN) |
US6363421B2 (en) * | 1998-05-31 | 2002-03-26 | Lucent Technologies, Inc. | Method for computer internet remote management of a telecommunication network element |
US6393481B1 (en) | 1997-10-06 | 2002-05-21 | Worldcom, Inc. | Method and apparatus for providing real-time call processing services in an intelligent network |
US6477566B1 (en) * | 1997-12-10 | 2002-11-05 | Nortel Networks Limited | Method and system of providing improved network management data between a plurality of network elements and a management system for increasing a flow and decreasing an amount of data transfer |
US6512824B1 (en) * | 1998-08-10 | 2003-01-28 | Adc Services Fulfillment, Inc. | Proxy database for element management system of telephone switching network |
-
2000
- 2000-05-25 US US09/580,519 patent/US7185075B1/en not_active Expired - Fee Related
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5953347A (en) | 1994-09-19 | 1999-09-14 | Crosskeys Systems Corporation | Integrated management of multiple networks with different topologies |
US6094145A (en) * | 1995-09-11 | 2000-07-25 | Alcatel Cit | Telecommunication management system |
US6222827B1 (en) * | 1995-12-28 | 2001-04-24 | Nokia Telecommunications Oy | Telecommunications network management system |
US5726979A (en) | 1996-02-22 | 1998-03-10 | Mci Corporation | Network management system |
US5761432A (en) | 1996-07-15 | 1998-06-02 | At&T Corp | Method and apparatus for providing an efficient use of telecommunication network resources |
US5892950A (en) | 1996-08-09 | 1999-04-06 | Sun Microsystems, Inc. | Interface for telecommunications network management |
US6393481B1 (en) | 1997-10-06 | 2002-05-21 | Worldcom, Inc. | Method and apparatus for providing real-time call processing services in an intelligent network |
US6108309A (en) * | 1997-12-08 | 2000-08-22 | Mci Communications Corporation | SONET network element simulator |
US6477566B1 (en) * | 1997-12-10 | 2002-11-05 | Nortel Networks Limited | Method and system of providing improved network management data between a plurality of network elements and a management system for increasing a flow and decreasing an amount of data transfer |
US6038301A (en) | 1997-12-31 | 2000-03-14 | Alcatel Usa Sourcing, L.P. | Method and system for engineering a service in an advanced intelligent network |
US6240174B1 (en) | 1998-05-14 | 2001-05-29 | International Business Machines Corporation | Two way transmission of subscriber provisional data for an intelligent peripheral in an advanced intelligent network (AIN) |
US6363421B2 (en) * | 1998-05-31 | 2002-03-26 | Lucent Technologies, Inc. | Method for computer internet remote management of a telecommunication network element |
US6512824B1 (en) * | 1998-08-10 | 2003-01-28 | Adc Services Fulfillment, Inc. | Proxy database for element management system of telephone switching network |
US6128656A (en) * | 1998-09-10 | 2000-10-03 | Cisco Technology, Inc. | System for updating selected part of configuration information stored in a memory of a network element depending on status of received state variable |
Cited By (133)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140317487A1 (en) * | 2000-05-24 | 2014-10-23 | Clickfox, Llc | System and method for modifying links within a web site |
US10496726B2 (en) * | 2000-05-24 | 2019-12-03 | Clickfox, Llc | System and method for modifying links within a web site |
US20040109683A1 (en) * | 2002-08-21 | 2004-06-10 | Meriton Networks Inc. | Non-disruptive lightpath routing changes in WDM networks |
US8965979B2 (en) | 2002-11-20 | 2015-02-24 | Vcvc Iii Llc. | Methods and systems for semantically managing offers and requests over a network |
US20090192972A1 (en) * | 2002-11-20 | 2009-07-30 | Radar Networks, Inc. | Methods and systems for creating a semantic object |
US9020967B2 (en) * | 2002-11-20 | 2015-04-28 | Vcvc Iii Llc | Semantically representing a target entity using a semantic object |
US20040158455A1 (en) * | 2002-11-20 | 2004-08-12 | Radar Networks, Inc. | Methods and systems for managing entities in a computing device using semantic objects |
US20090192976A1 (en) * | 2002-11-20 | 2009-07-30 | Radar Networks, Inc. | Methods and systems for creating a semantic object |
US20090030982A1 (en) * | 2002-11-20 | 2009-01-29 | Radar Networks, Inc. | Methods and systems for semantically managing offers and requests over a network |
US8161066B2 (en) | 2002-11-20 | 2012-04-17 | Evri, Inc. | Methods and systems for creating a semantic object |
US8190684B2 (en) | 2002-11-20 | 2012-05-29 | Evri Inc. | Methods and systems for semantically managing offers and requests over a network |
US7640267B2 (en) * | 2002-11-20 | 2009-12-29 | Radar Networks, Inc. | Methods and systems for managing entities in a computing device using semantic objects |
US20100057815A1 (en) * | 2002-11-20 | 2010-03-04 | Radar Networks, Inc. | Semantically representing a target entity using a semantic object |
US10033799B2 (en) | 2002-11-20 | 2018-07-24 | Essential Products, Inc. | Semantically representing a target entity using a semantic object |
US20040120270A1 (en) * | 2002-12-18 | 2004-06-24 | Bellsouth Intellectual Property Corporation | System and method for enhanced sonet network analysis |
US7447161B2 (en) * | 2002-12-18 | 2008-11-04 | Atct Intellectual Property I, L.P | System and method for enhanced SONET network analysis |
US20070271599A1 (en) * | 2003-05-28 | 2007-11-22 | Citrix Silicon Valley | Systems and methods for state signing of internet resources |
US7861087B2 (en) | 2003-05-28 | 2010-12-28 | Citrix Systems, Inc. | Systems and methods for state signing of internet resources |
US7415505B2 (en) * | 2003-06-20 | 2008-08-19 | Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd. | System and method for electronic event logging |
US20050010929A1 (en) * | 2003-06-20 | 2005-01-13 | Gongqian Wang | System and method for electronic event logging |
US20050025068A1 (en) * | 2003-07-30 | 2005-02-03 | Alcatel | Network element with autodiscovery of link connections |
US20050050196A1 (en) * | 2003-08-25 | 2005-03-03 | Lucent Technologies Inc. | Method and apparatus for managing and graphically representing elements in a network |
US7877390B2 (en) * | 2003-10-20 | 2011-01-25 | International Business Machines Corporation | Systems and methods for providing autonomous persistent storage systems |
US20050086236A1 (en) * | 2003-10-20 | 2005-04-21 | International Business Machines Corporation | Systems and methods for providing autonomous persistent storage systems |
US20050135276A1 (en) * | 2003-12-18 | 2005-06-23 | Alcatel | Network with spanning tree for guiding information |
US20050198216A1 (en) * | 2004-02-02 | 2005-09-08 | Behera Manas K. | Method for managing a network using a plurality of databases |
US8275796B2 (en) | 2004-02-23 | 2012-09-25 | Evri Inc. | Semantic web portal and platform |
US9189479B2 (en) | 2004-02-23 | 2015-11-17 | Vcvc Iii Llc | Semantic web portal and platform |
US20080306959A1 (en) * | 2004-02-23 | 2008-12-11 | Radar Networks, Inc. | Semantic web portal and platform |
US20050198581A1 (en) * | 2004-03-05 | 2005-09-08 | Soderberg Eric M. | Copy-and-paste functionality for network reconfiguration |
US8650500B2 (en) * | 2004-03-05 | 2014-02-11 | Hewlett-Packard Development Company, L.P. | Copy-and-paste functionality for network reconfiguration |
US20050232168A1 (en) * | 2004-04-15 | 2005-10-20 | Citrix Systems, Inc. | Methods and apparatus for synchronization of data set representations in a bandwidth-adaptive manner |
US7827139B2 (en) | 2004-04-15 | 2010-11-02 | Citrix Systems, Inc. | Methods and apparatus for sharing graphical screen data in a bandwidth-adaptive manner |
US7680885B2 (en) | 2004-04-15 | 2010-03-16 | Citrix Systems, Inc. | Methods and apparatus for synchronization of data set representations in a bandwidth-adaptive manner |
US8375087B2 (en) | 2004-04-15 | 2013-02-12 | Citrix Systems Inc. | Methods and apparatus for synchronization of data set representations in a bandwidth-adaptive manner |
US7673139B1 (en) * | 2004-05-06 | 2010-03-02 | Symantec Corporation | Protecting administrative privileges |
US7380244B1 (en) * | 2004-05-18 | 2008-05-27 | The United States Of America As Represented By The Secretary Of The Navy | Status display tool |
US20090119768A1 (en) * | 2004-06-30 | 2009-05-07 | Walters Robert V | Using Application Gateways to Protect Unauthorized Transmission of Confidential Data Via Web Applications |
US8458783B2 (en) | 2004-06-30 | 2013-06-04 | Citrix Systems, Inc. | Using application gateways to protect unauthorized transmission of confidential data via web applications |
US20060020696A1 (en) * | 2004-07-20 | 2006-01-26 | Fang-Pang Lin | Wireless remote control system and method thereof |
US7925727B2 (en) * | 2004-07-29 | 2011-04-12 | Nortel Networks Limited | Method and apparatus for efficient communication of management data in a telecommunications network |
US20060026272A1 (en) * | 2004-07-29 | 2006-02-02 | Nortel Networks Limited | Method and apparatus for efficient communication of management data |
US8010576B2 (en) * | 2004-08-19 | 2011-08-30 | Oracle International Corporation | Inventory and configuration management |
US20060041567A1 (en) * | 2004-08-19 | 2006-02-23 | Oracle International Corporation | Inventory and configuration management |
US11126323B2 (en) | 2004-11-09 | 2021-09-21 | Blackberry Limited | Dynamic bar oriented user interface |
US8108510B2 (en) * | 2005-01-28 | 2012-01-31 | Jds Uniphase Corporation | Method for implementing TopN measurements in operations support systems |
US20060190578A1 (en) * | 2005-01-28 | 2006-08-24 | Nelson Ellen M | Method for implementing TopN measurements in operations support systems |
US20060195891A1 (en) * | 2005-02-25 | 2006-08-31 | Freyman Phillip K | Network status indication system |
US8443040B2 (en) | 2005-05-26 | 2013-05-14 | Citrix Systems Inc. | Method and system for synchronizing presentation of a dynamic data set to a plurality of nodes |
US20070011356A1 (en) * | 2005-05-26 | 2007-01-11 | Citrix Systems, Inc. | A method and system for synchronizing presentation of a dynamic data set to a plurality of nodes |
US7378969B2 (en) * | 2005-10-25 | 2008-05-27 | Sap Ag | Systems and methods for visualizing auto-id data |
US20070090951A1 (en) * | 2005-10-25 | 2007-04-26 | Sap Ag | Systems and methods for visualizing auto-id data |
US7924884B2 (en) | 2005-12-20 | 2011-04-12 | Citrix Systems, Inc. | Performance logging using relative differentials and skip recording |
US7650406B2 (en) * | 2006-04-26 | 2010-01-19 | Microsoft Corporation | Termination of a security association between devices |
US20070255827A1 (en) * | 2006-04-26 | 2007-11-01 | Microsoft Corporation | Termination of a security association between devices |
US20080010497A1 (en) * | 2006-06-12 | 2008-01-10 | Curtis Duane Kronlund | Selecting a Logging Method via Metadata |
US20080189267A1 (en) * | 2006-08-09 | 2008-08-07 | Radar Networks, Inc. | Harvesting Data From Page |
US8924838B2 (en) | 2006-08-09 | 2014-12-30 | Vcvc Iii Llc. | Harvesting data from page |
US20080065756A1 (en) * | 2006-09-08 | 2008-03-13 | Frances Jean Hardwick | Method and system for presenting network devices on a display screen of a network management system |
US8433729B2 (en) * | 2006-09-29 | 2013-04-30 | Sap Ag | Method and system for automatically generating a communication interface |
US20080082535A1 (en) * | 2006-09-29 | 2008-04-03 | Sven-Eric Eigemann | Method and system for automatically generating a communication interface |
US8060600B1 (en) * | 2007-03-02 | 2011-11-15 | Sprint Communications Company L.P. | Network element management system |
US20080225728A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods for providing virtual fair queueing of network traffic |
US20080228772A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods of prefreshening cached objects based on user's current web page |
US8531944B2 (en) | 2007-03-12 | 2013-09-10 | Citrix Systems, Inc. | Systems and methods for providing virtual fair queuing of network traffic |
US8504775B2 (en) | 2007-03-12 | 2013-08-06 | Citrix Systems, Inc | Systems and methods of prefreshening cached objects based on user's current web page |
US8462631B2 (en) | 2007-03-12 | 2013-06-11 | Citrix Systems, Inc. | Systems and methods for providing quality of service precedence in TCP congestion control |
US7796510B2 (en) | 2007-03-12 | 2010-09-14 | Citrix Systems, Inc. | Systems and methods for providing virtual fair queueing of network traffic |
US10911520B2 (en) | 2007-03-12 | 2021-02-02 | Citrix Systems, Inc. | Systems and methods of using the refresh button to determine freshness policy |
US8037126B2 (en) | 2007-03-12 | 2011-10-11 | Citrix Systems, Inc. | Systems and methods of dynamically checking freshness of cached objects based on link status |
US20090287842A1 (en) * | 2007-03-12 | 2009-11-19 | Robert Plamondon | Systems and methods of prefetching objects for caching using qos |
US8103783B2 (en) | 2007-03-12 | 2012-01-24 | Citrix Systems, Inc. | Systems and methods of providing security and reliability to proxy caches |
US8615583B2 (en) | 2007-03-12 | 2013-12-24 | Citrix Systems, Inc. | Systems and methods of revalidating cached objects in parallel with request for object |
US20080229024A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods of dynamically checking freshness of cached objects based on link status |
US20100088398A1 (en) * | 2007-03-12 | 2010-04-08 | Robert Plamondon | Systems and methods for domain name resolution interception caching |
US20080229025A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods of using the refresh button to determine freshness policy |
US20100281112A1 (en) * | 2007-03-12 | 2010-11-04 | Robert Plamondon | Systems and methods of revalidating cached objects in parallel with request for object |
US8364785B2 (en) | 2007-03-12 | 2013-01-29 | Citrix Systems, Inc. | Systems and methods for domain name resolution interception caching |
US8701010B2 (en) | 2007-03-12 | 2014-04-15 | Citrix Systems, Inc. | Systems and methods of using the refresh button to determine freshness policy |
US8275829B2 (en) | 2007-03-12 | 2012-09-25 | Citrix Systems, Inc. | Systems and methods of prefetching objects for caching using QoS |
US8266530B2 (en) * | 2007-04-03 | 2012-09-11 | Alcatel Lucent | Multiple displays of large dynamic alarm windows |
US20080250138A1 (en) * | 2007-04-03 | 2008-10-09 | Alcatel Lucent | Multiple displays of large dynamic alarm windows |
US9621426B1 (en) * | 2007-04-18 | 2017-04-11 | Grass Valley USA, LLC | Switching facility having a control panel with relegendable buttons |
US8868560B2 (en) | 2007-09-16 | 2014-10-21 | Vcvc Iii Llc | System and method of a knowledge management and networking environment |
US8438124B2 (en) | 2007-09-16 | 2013-05-07 | Evri Inc. | System and method of a knowledge management and networking environment |
US20090077062A1 (en) * | 2007-09-16 | 2009-03-19 | Nova Spivack | System and Method of a Knowledge Management and Networking Environment |
US20090077124A1 (en) * | 2007-09-16 | 2009-03-19 | Nova Spivack | System and Method of a Knowledge Management and Networking Environment |
US20090076887A1 (en) * | 2007-09-16 | 2009-03-19 | Nova Spivack | System And Method Of Collecting Market-Related Data Via A Web-Based Networking Environment |
US20090106307A1 (en) * | 2007-10-18 | 2009-04-23 | Nova Spivack | System of a knowledge management and networking environment and method for providing advanced functions therefor |
US8577837B2 (en) * | 2007-10-30 | 2013-11-05 | Sap Ag | Method and system for generic extraction of business object data |
US20090112908A1 (en) * | 2007-10-30 | 2009-04-30 | Sap Ag | Method and System for Generic Extraction of Business Object Data |
US20090172528A1 (en) * | 2007-12-31 | 2009-07-02 | Ramprasad S | System and method for dynamically presenting a software system landscape |
US9629928B1 (en) * | 2008-03-31 | 2017-04-25 | Symantec Corporation | Hash-based inventory identification |
US20100004975A1 (en) * | 2008-07-03 | 2010-01-07 | Scott White | System and method for leveraging proximity data in a web-based socially-enabled knowledge networking environment |
US20110179037A1 (en) * | 2008-07-30 | 2011-07-21 | Hironori Mizuguchi | Data classifier system, data classifier method and data classifier program |
US9342589B2 (en) | 2008-07-30 | 2016-05-17 | Nec Corporation | Data classifier system, data classifier method and data classifier program stored on storage medium |
US9361367B2 (en) * | 2008-07-30 | 2016-06-07 | Nec Corporation | Data classifier system, data classifier method and data classifier program |
WO2010028380A3 (en) * | 2008-09-08 | 2010-05-14 | Futurewei Technologies, Inc. | Object modeling for next generation network wavelength division multiplexing |
US20100061728A1 (en) * | 2008-09-08 | 2010-03-11 | Futurewei Technologies, Inc. | Object Modeling Scheme For Next Generation Network Wavelength Division Multiplexing |
WO2010028380A2 (en) * | 2008-09-08 | 2010-03-11 | Futurewei Technologies, Inc. | Object modeling scheme for next generation network wavelength division multiplexing |
US8352537B2 (en) | 2008-09-08 | 2013-01-08 | Futurewei Technologies, Inc. | Object modeling scheme for next generation network wavelength division multiplexing |
US8200617B2 (en) | 2009-04-15 | 2012-06-12 | Evri, Inc. | Automatic mapping of a location identifier pattern of an object to a semantic type using object metadata |
US20100268596A1 (en) * | 2009-04-15 | 2010-10-21 | Evri, Inc. | Search-enhanced semantic advertising |
US9607089B2 (en) | 2009-04-15 | 2017-03-28 | Vcvc Iii Llc | Search and search optimization using a pattern of a location identifier |
US10628847B2 (en) | 2009-04-15 | 2020-04-21 | Fiver Llc | Search-enhanced semantic advertising |
US9613149B2 (en) | 2009-04-15 | 2017-04-04 | Vcvc Iii Llc | Automatic mapping of a location identifier pattern of an object to a semantic type using object metadata |
US9037567B2 (en) | 2009-04-15 | 2015-05-19 | Vcvc Iii Llc | Generating user-customized search results and building a semantics-enhanced search engine |
US20100268700A1 (en) * | 2009-04-15 | 2010-10-21 | Evri, Inc. | Search and search optimization using a pattern of a location identifier |
US20100268720A1 (en) * | 2009-04-15 | 2010-10-21 | Radar Networks, Inc. | Automatic mapping of a location identifier pattern of an object to a semantic type using object metadata |
US20100268702A1 (en) * | 2009-04-15 | 2010-10-21 | Evri, Inc. | Generating user-customized search results and building a semantics-enhanced search engine |
US8862579B2 (en) | 2009-04-15 | 2014-10-14 | Vcvc Iii Llc | Search and search optimization using a pattern of a location identifier |
US8798079B2 (en) * | 2009-06-09 | 2014-08-05 | Zte Corporation | Method and apparatus for fast passing through services for synchronous digital hierarchy device |
US20120082169A1 (en) * | 2009-06-09 | 2012-04-05 | Zte Corporation | Method and apparatus for fast passing through services for synchronous digital hierarchy device |
US10976891B2 (en) * | 2009-12-08 | 2021-04-13 | Hand Held Products, Inc. | Remote device management interface |
US20170060383A1 (en) * | 2009-12-08 | 2017-03-02 | Hand Held Products, Inc. | Remote device management interface |
US20110179371A1 (en) * | 2010-01-19 | 2011-07-21 | Verizon Patent And Licensing, Inc. | Provisioning Workflow Management Methods and Systems |
US8645854B2 (en) * | 2010-01-19 | 2014-02-04 | Verizon Patent And Licensing Inc. | Provisioning workflow management methods and systems |
US20120324456A1 (en) * | 2011-06-16 | 2012-12-20 | Microsoft Corporation | Managing nodes in a high-performance computing system using a node registrar |
US9747130B2 (en) | 2011-06-16 | 2017-08-29 | Microsoft Technology Licensing, Llc | Managing nodes in a high-performance computing system using a node registrar |
US20130086130A1 (en) * | 2011-09-30 | 2013-04-04 | Oracle International Corporation | Executor for software configuration automation |
US9298713B2 (en) * | 2011-09-30 | 2016-03-29 | Oracle International Corporation | Executor for software configuration automation |
CN102571440A (en) * | 2012-01-19 | 2012-07-11 | 中兴通讯股份有限公司 | Network management operation method and system |
US10628246B1 (en) * | 2013-05-20 | 2020-04-21 | The Boeing Company | Methods and systems for prioritizing corrective actions in a troubleshooting chart |
US20150127790A1 (en) * | 2013-11-05 | 2015-05-07 | Harris Corporation | Systems and methods for enterprise mission management of a computer nework |
US9503324B2 (en) * | 2013-11-05 | 2016-11-22 | Harris Corporation | Systems and methods for enterprise mission management of a computer network |
US10785272B2 (en) * | 2014-10-22 | 2020-09-22 | Huawei Technologies Co., Ltd. | Streaming application upgrading method, master node, and stream computing system |
US20170223075A1 (en) * | 2014-10-22 | 2017-08-03 | Huawei Technologies Co., Ltd. | Streaming Application Upgrading Method, Master Node, and Stream Computing System |
US10153861B2 (en) * | 2015-07-30 | 2018-12-11 | Infinera Corporation | Digital link viewer for data center interconnect nodes |
US20170033864A1 (en) * | 2015-07-30 | 2017-02-02 | Infinera Corporation | Digital link viewer for data center interconnect nodes |
US10277485B1 (en) * | 2015-08-21 | 2019-04-30 | Amazon Technologies, Inc. | Network device testing using non-destructive techniques |
US11507262B2 (en) * | 2017-02-22 | 2022-11-22 | Ciena Corporation | Methods and systems for managing optical network services including capacity mining and scheduling |
US11914855B2 (en) | 2017-02-22 | 2024-02-27 | Ciena Corporation | Methods and systems for managing optical network services including capacity mining and scheduling |
CN110750425A (en) * | 2019-10-25 | 2020-02-04 | 上海中通吉网络技术有限公司 | Database monitoring method, device and system and storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7185075B1 (en) | Element management system with dynamic database updates based on parsed snooping | |
US7366989B2 (en) | Element management system with data-driven interfacing driven by instantiation of meta-model | |
US7113934B2 (en) | Element management system with adaptive interfacing selected by last previous full-qualified managed level | |
US7363359B1 (en) | Element management system with automatic remote backup of network elements' local storage | |
US7403987B1 (en) | Transactional SAN management | |
US7328260B1 (en) | Mapping discovered devices to SAN-manageable objects using configurable rules | |
US7774444B1 (en) | SAN simulator | |
US8019849B1 (en) | Server-side storage area network management interface | |
US7401338B1 (en) | System and method for an access layer application programming interface for managing heterogeneous components of a storage area network | |
US6880086B2 (en) | Signatures for facilitating hot upgrades of modular software components | |
US7177924B2 (en) | Command line interface processor with dynamic update of attribute dependencies | |
US20030202645A1 (en) | Element management system with adaptive interface based on autodiscovery from element identifier | |
US7167483B1 (en) | System and method for managing subrate services in an optical network | |
US7124368B1 (en) | System and method for displaying usage information in a data network | |
Cisco | Using Cisco Transport Manager | |
Cisco | ViewRunner for HP OpenView Overview | |
Cisco | ViewRunner for HP OpenView Overview | |
Cisco | Managing and Configuring Network Elements | |
Cisco | CiscoView 4.0(1) Release Notes | |
Cisco | CiscoView 4.0(1) Release Notes | |
Cisco | CiscoView 4.0(1) Release Notes | |
Cisco | CiscoView 4.0(1) Release Notes | |
Cisco | CiscoView 4.0(1) Release Notes | |
Cisco | CiscoView 4.0(1) Release Notes | |
Cisco | Release Notes for CWSI UNIX Version 1.1 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FUJITSU NETWORK COMMUNICATIONS, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MISHRA, ATUL;LEVESQUE, GILBERT;GALOU, SALIM;REEL/FRAME:011129/0407;SIGNING DATES FROM 20000811 TO 20000815 |
|
AS | Assignment |
Owner name: FUJITSU LIMITED, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU NETWORK COMMUNICATIONS, INC.;REEL/FRAME:017091/0577 Effective date: 20051116 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20190227 |