Table Of Contents
General
This chapter provides a top-level view of the components, excluding the specific requirement issues.
Background
The system is comprised of the following main components, which require command-line management:
•Cisco ANA Shell client.
•Unit process/VNE.
All of these components should support the same interface behavior.
Users
Two types of users are expected to use the Cisco ANA Shell interface:
•Network Operators—Responsible for network operation tasks like surveillance and provisioning.
•Cisco Technicians—Responsible for low-level system maintenance, debugging and fine-tuning.
Goals
•IOS based Command Line Interface for all aspects of the system.
•Enable multi-level management: Network, and VNE perspectives.
Role
The Cisco ANA Shell serves as the front-end of the system and therefore only provides services to the end-user. In view of the fact that it unifies the operations of all the system components, it requires the following services to be supported by the system components:
Glossary
This section defines the different types of parameters that can be used as arguments to the Cisco ANA Shell commands. All the parameters of the commands are strings in one of the formats provided in this document.
Type
name
Description
The same as string. Used for clarity (for example as device name)
Format
Example
user1
Type
VC
Description
Identifier of an ATM VC
Format
<Integer>["/"<Integer>]
Both integers must be at the range specified by ATM.
Example
1/102
Type
filename
Description
A valid filename on the operating system on which the client is running.
Format
String
Example
path1.snc
/export/home/sheer1.3/Main/path2.snc
Type
Date
Description
String representing date and time
Format
Unix "date" format in the default "C" locale
Example
Mon Jul 22 16:56:25 IDT 2002