Chapter 1
Using the CLI
This chapter describes the Avaya P330 CLI architecture and conventions, and provides instructions for accessing the Avaya P330 for configuration purposes.
The configuration procedure involves establishing a Telnet session or a serial connection and then using the Avaya P330’s internal CLI.
The CLI is
You can also configure your Avaya P330 using the P330 Manager with its graphical user interface. For details, see the switch User’s Guide and the Avaya™ MultiService Network Manager P330 Device Manager User’s Guide on the Documentation and Utilities CD.
CLI Architecture
The P330 stack supports both Layer 2 switching and Layer 3 routing (Layer 3 functionality depends on the module type).
The P330 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 2.
•The Router CLI entity is used to manage Layer 3 routing of a single module. The Router CLI entity exists only in Layer 3 modules (P333R,
If the Layer 3 module is the Stack Master, then the Switch CLI entity and the Router CLI entity
To switch between the entities, use the session command.
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.
Avaya | 1 |