Cli - Architecture, Access & Conventions; Cli Architecture - Avaya P333R User Manual

Chapter 4
CLI – Architecture, Access & Conventions
This chapter describes the P332G-ML CLI architecture and conventions, and
provides instructions for accessing the P332G-ML for configuration purposes.
The configuration procedure involves establishing a Telnet session or a serial
connection and then using the P330's internal CLI. The CLI is command-line driven
and does not have any menus. To activate a configuration option, you must type the
desired command at the prompt and press Enter. You can also configure your
P332G-ML using the P330 Manager with its graphical user interface. For details, see
the P330 Device Manager Appendix and the Avaya Multi-Service Network
Manager P330 Device Manager User Guide on the Documentation and Utilities CD.

CLI Architecture

The P330 stack supports both Layer 2 switching and Layer 3 switching.
The P332G-ML CLI includes two CLI entities to support this functionality.
• The Switch CLI entity is used to manage Layer 2 switching of the entire stack.
The Switch CLI entity is identical to the CLI of a P330 Layer 2 modules.
CLI commands for managing Layer 2 switching are described in Chapter 6.
• The Router CLI entity is used to manage Layer 3 switching of a single module.
The Router CLI entity exists in P330R and P332G-ML Layer 3 modules and
supports different sets of commands depending on the device mode of the
module.
Router mode commands are described in Chapter 8.
If the P332G-ML module is the Master of the stack, then the Switch CLI entity and
the Router CLI entity co-exist on the same module.
To switch between the entities, use the session command. Refer to P330
Sessions.
Configuration of the password commands and community commands in one
entity is automatically attributed to the other entity in the stack.
Initial access to the stack can be established via a serial connection or a Telnet
connection to any one of the entities.
P333R User's Guide 27