|
|
Table Of Contents
2.2.5 Graphical User Interface Types
2.2.7 List of Possible Network Element IP Addresses
2.2.8 Configuration Download and Upload
2.2.9 Software, Firmware and Licenses Download
2.2.11 Alarm and Event Notifications Presentation
2.2.12 Presentation of Performance Data
2.2.13 Management Configuration
2.2.17 Alarm and Event Filtering Configuration
2.2.18 SDH Ports Configuration
2.2.19 PDH Ports Configuration
2.2.20 MSP and SNCP Configuration
2.2.21 SDH Synchronization Configuration
2.2.22 LAN Ports Configuration
2.2.23 WAN Ports Configuration
2.2.24 Test Loops Configuration
2.2.25 Cross-Connect (XC) Configuration
Software Description
This section gives an overview of the Cisco Edge Craft.
2.1 Introduction
Cisco Edge Craft is used to operate a single network element and provides a real-time snapshot of the network element. Cisco Edge Craft can only present and work on information that is stored on the network element. A user must be logged into the Cisco Edge Craft graphical user interface (GUI) for it to function. The GUI presents alarms if Cisco Edge Craft is connected to the network element. Performance data can be loaded from the network element.
Cisco Edge Craft is a single user system. It is a standalone application running on Windows or Solaris platforms. Cisco Edge Craft is not dependent on any other system to be able to perform its tasks. The laptop or a PC where Cisco Edge Craft is running can be attached to the network element directly through the management port or through a LAN ( Figure 2-1).
Figure 2-1 Cisco Edge Craft Connection Possibilities
Cisco Edge Craft can co-exist with other management products from Cisco ( Figure 2-2). The SNMP Agent used by Cisco Edge Craft for communication with the network element handles multiple SNMP managers.
Figure 2-2 Cisco Edge Craft in Co-existence with Other Management Systems
Table 2-1 displays the capabilities of the Cisco Edge Craft.
2.2 Product Features
Some of the feature listed here are only applicable to Cisco Edge Craft (CEC) if the feature is available on the network element.
2.2.1 Network Element Access
CEC communicates with the network element through the embedded SNMP Agent. To establish this communication line the network element must have an IP address. If an IP address has not been assigned, a separate communication line on the serial port can assign the IP address and other related parameters.
2.2.2 Information Model
CEC has its own internal representation (information model) of the network elements. This is an object-oriented model and is identical to the information model used by all Cisco products.
2.2.3 Single User
Only one user can be logged into CEC at one time.
2.2.4 Single Network Element
CEC can only communicate with one network element at a time. The user must close the connection to one NE before connecting to a new NE.
2.2.5 Graphical User Interface Types
The GUI presents the network element in accordance with the information model and has no knowledge about the SNMP MIBs used by the embedded Agent.
The GUI cannot be customized by the user.
CEC has two different types of graphical user interfaces (GUI):
•
The Network Element Topology Browser (NETB) is a hierarchical presentation of the managed objects in the network element.
•
2.2.6 No Persistency
CEC has no persistent storage of operations and notifications.
2.2.7 List of Possible Network Element IP Addresses
CEC stores the IP address of accessed network elements. The operator can choose the IP address of the current network element in the start up window for CEC.
2.2.8 Configuration Download and Upload
CEC can initiate upload of the complete configuration from one network element and store it on the local or remote computer. The remote computer is identified by its IP address.
CEC can initiate download of the complete configuration from a local or remote computer to the network element. The remote computer is identified by its IP address.
The uploaded configuration cannot be edited.
2.2.9 Software, Firmware and Licenses Download
CEC can initiate download of software, firmware, and licenses on the network element. The location of the software, firmware, and licenses can either be on the same computer as CEC or on a remote computer. The remote computer is identified by its IP address; both the local and remote computers must be TFTP servers.
The restart of the equipment that uses new downloaded software/firmware can be scheduled.
2.2.10 User Access
CEC supports user authentication through user identification (community string).
Initial access of the network element is through public access.
2.2.11 Alarm and Event Notifications Presentation
CEC presents all alarms and events that are generated while the user is logged intoCEC. The alarms are presented in a tabular view. If the received traps from the network element cannot be mapped to an alarm or an event, the trap is still presented to the operator.
CEC presents the alarm history stored on the network element. The alarm history is presented in a tabular view.
2.2.12 Presentation of Performance Data
CEC has no analysis of performance management data.
The user can read the current registered performance data on the network element, view it in a GUI, and copy it to file. The file can be read or edited in any word processing tool, such as Microsoft Excel.
Supported performance data are: G.826, MIB-II (RFC1213), and RMON counters.
2.2.13 Management Configuration
CEC supports configuration of the DCN management traffic settings.
2.2.14 Physical Inventory
The physical inventory gives an overview of the installed parts on the network element and the currently running software or firmware. Software and firmware packages that have been downloaded but not activated are also presented.
2.2.15 Logical Inventory
The logical inventory gives an overview of the managed entities in the network element. The logical entities may agree with the physical parts, but not necessarily.
2.2.16 Global Settings
The network element has some configurations that are not related to the user traffic on the network element. These are parameters such as location, owner, time server, LED settings, power modules.
2.2.17 Alarm and Event Filtering Configuration
The alarm reporting from some managed entities on the network elements can be filtered out.
2.2.18 SDH Ports Configuration
CEC supports configuration of the SDH ports. The SDH ports have two main configuration areas.
•
•
2.2.19 PDH Ports Configuration
CEC supports configuration of PDH port properties. The properties can be viewed and edited.
2.2.20 MSP and SNCP Configuration
CEC supports MSP and SNCP set up, which means the user can view, create, modify, and delete.
2.2.21 SDH Synchronization Configuration
The network element can have more than one synchronization source for the SDH traffic. The sources are prioritized. CEC helps the user in the set up of these rules.
2.2.22 LAN Ports Configuration
CEC supports the configuration of LAN port properties. The properties can be viewed and edited.
2.2.23 WAN Ports Configuration
CEC supports configuration of WAN port properties. The properties can be viewed and edited. CEC also supports configuration of WAN bandwidth.
2.2.24 Test Loops Configuration
CEC supports configuration of test loops.
2.2.25 Cross-Connect (XC) Configuration
CEC supports cross connection management for the SDH ports. The cross-connects can be set, deleted, and updated. Two supported cross-connects are point-to-point and WAN to SDH mapping.
2.2.26 Bridge Configuration
CEC supports bridge set up.
2.2.27 VLAN Configuration
CEC supports VLAN configuration, meaning the user can create, remove, and update VLANs.
2.2.28 Security
The security of Cisco Edge Craft is based on the SNMP v.1 security (community string).
2.2.29 Data Communication
Cisco Edge Craft can communicate with the network elements
•
•
•
2.2.30 Reliability
This section lists the reliability requirements and know bugs on CEC.
One or more Cisco Edge Craft users can be connected to the same network element at the same time if the network element is connected to a LAN, but the users they will have no visibility to each other.
Known bugs are presented with a workaround in the release notes.
2.2.31 Maintenance
Debugging and system logging are realized through log4j, open source code.
2.2.31.1 Debugging
•
•
•
2.2.31.2 System Logging
•
•
•
2.2.31.3 New Releases and Patches
The new releases or patches are available for download from the support pages on http://www.cisco.com.
Posted: Fri Sep 14 11:29:13 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
