Chapters Download(857 KB)
Table of Contents
Chapter 1 H3C XE 200/2000 IP PBX Overview
Chapter 2 Command Line Interface for Configuration
2.1 Setting Up the Configuration Environment
2.1.1 Configuring the XE IP PBX through the CONSOLE Port
2.1.2 Configuring the XE IP PBX through the AUX Port
2.1.3 Configuring the XE IP PBX through Telnet
2.2.2 Command Line Online Help
2.2.3 Command Line Error Information
2.3.3 Configuring Command Alias
3.1 Basic Configuration of Comware
3.2 Ethernet Interface Configuration
3.2.1 Introduction to the Ethernet Interface
3.2.2 Configuring the Ethernet Interface
3.2.3 Displaying and Debugging Ethernet Interface
3.3 Static Route Configuration
3.3.1 Introduction to the Static Route
3.3.2 Introduction to the Default Route
3.3.3 Configuring a Static Route
3.3.4 Configuring a Default Route
3.3.5 Deleting all Static Routes
3.3.6 Displaying and Debugging Routing Table
H3C XE 200/2000 IP PBX (hereinafter referred to as XE IP PBX) is a part of H3C’s integrated cross-industry VoIP solution designed for enterprise users. It can integrate a large number of voice devices into a voice network that is easy to maintain, manage and upgrade. With the XE IP PBX, you can make full use of the functions available with the voice gateways and IP telephone terminals and even obtain function enhancement. Thus, your investment can be protected to the maximum extent.
As a VoIP server, the XE IP PBX can centralize management of devices such as voice gateways and IP telephone terminals and uniformly process VoIP services. The major functions that it provides include registration management, dialing routing management, call control, and service processing:
1) Registration management: When receiving a register request from a voice gateway or terminal, the XE IP PBX accepts or rejects the request according to the registration management policy and records the dynamic information such as the online state of the gateway or terminal as well.
2) Dialing routing management: The XE IP PBX maintains the number information of voice gateways and terminals and a mapping table from number to IP address and port. When a voice gateway or terminal receives a dialed number, it sends a call request to the XE IP PBX. Then the XE IP PBX searches for the number mapping table to find the IP address and port number mapped to the dialed number.
3) Call control: The XE IP PBX supports call tracing, statistics in addition to call connection, maintenance, and release. The XE IP PBX provides two approaches: redirection and routing.
4) Service processing: Besides the basic call services, the XE IP PBX provides the traditional PBX service. Service information can be set by administrators or users through the GUI client or a terminal.
Table 1-1 Functionality of the XE IP PBX
Attribute |
Description |
|
Connectivity |
LAN protocol |
Ethernet_II Ethernet_SNAP IEEE802.2 IEEE802.3 |
Network protocol |
IP service |
ARP Static DNS service |
IP routing |
Static routing management |
|
Security |
AAA |
Local authentication and authorization |
Reliability |
Dual power redundancy (XE 2000) Automatic temperature sensor inside the chassis (XE 2000) |
|
Configuration and management |
Command line interface (CLI) |
Local configuration through the CONSOLE port Remote configuration through the AUX port Local and remote configuration through Telnet Command protection hierarchy where only authorized users can access the critical configurations of the XE IP PBX Telnet to other devices to manage them User-interface configuration, providing multiple login authentication and authorization approaches |
File system |
FTP Server/Client that provides configuration file/application upload and download File upload and download with TFTP File system management |
|
Test and debugging |
Network test tools such as tracert and ping for quick diagnosis on the network status Abundant debugging information for troubleshooting Logging function, allowing logging information to be retained on the local hard disk |
|
SNMPv3, compatible with SNMPv2c and SNMPv1 |
The XE IP PBX provides the configuration command line interface, with which you can configure the XE IP PBX locally or remotely through:
l CONSOLE port
l AUX port
l Telnet
Step 1: Connect the serial port on a PC (or terminal) to the CONSOLE port on the XE IP PBX using a console cable, as shown in Figure 2-1.
Figure 2-1 Set up a local configuration environment through the CONSOLE port
Step 2: Run the terminal emulation program (HyperTerminal of Win9X for example) on the PC and set the terminal communications parameters as follows:
Bits per second: 9600 bps
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Terminal emulation type: VT100
See Figure 2-2 through Figure 2-4.
Figure 2-2 Set up a new connection
Figure 2-3 Select the desired COM port
Step 3: Power up the XE IP PBX. The system runs the power-on self-test (POST), and then prompts you to press <Enter> until the command line prompt (<XE> for example) appears.
Step 4: Enter commands to configure the XE IP PBX or view its running status. If you need help, enter “?”. For more information about the commands, refer to the following chapters.
To configure the XE IP PBX through the AUX port, attach a modem to the serial port on the PC and one to the AUX port on the XE IP PBX, as shown in Figure 2-5.
Step 1: Attach a modem to the AUX port.
Figure 2-5 Set up a remote configuration environment
Step 2: Dial on the terminal to set up a connection to the XE IP PBX through the terminal emulation program (such as HyperTerminal of Windows 9X), as shown in Figure 2-6 and Figure 2-7. In the terminal emulation program, select the RS-232 serial port of the PC to be used for connection, and set the terminal communications parameters as follows:
Bits per second: 9600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None (or Hardware)
Terminal emulation type: VT100
See Figure 2-3 and Figure 2-4.
Figure 2-6 Set the dialup number
Figure 2-7 Dial on the remote PC
Step 3: Enter the correct username and password, and proceed to configure or manage the XE IP PBX when the command line prompt (<XE> for example) appears in the remote terminal emulation program.
& Note:
Before setting up a Telnet connection, make sure that:
l An IP address has been assigned to the XE IP PBX.
l VTY login authentication mode and the incoming and outgoing call restriction rules have been configured.
l There is a reachable route between the console terminal and the XE IP PBX.
Step 1: If the PC and the XE IP PBX are located in the same LAN, connect the Ethernet interfaces on them through the LAN, as shown in Figure 2-8. Otherwise, connect the PC to the XE IP PBX through the WAN, as shown in Figure 2-9.
Figure 2-8 Set up a Telnet configuration environment through the LAN
Figure 2-9 Set up a remote Telnet configuration environment through the WAN
Step 2: Run the Telnet program on the PC and set its terminal type to VT100, as shown in Figure 2-10.
Figure 2-10 Run the Telnet program
Step 3: Select [Connect\Remote system] in the Telnet window, and enter the IP address of the Ethernet interface on the XE IP PBX in the dialog box as shown in Figure 2-11.
Figure 2-11 Set up a Telnet connection with the XE IP PBX
& Note:
Host Name in Figure 2-11 refers to the IP address of the XE IP PBX.
Step 4: After telnetting to the XE IP PBX, you are prompted for the username and password. If the authentication is passed, the command line prompt (<XE> for example) appears for you to configure the XE IP PBX or view its running status.
& Note:
When you configure the XE IP PBX through telnet, be careful of modifying its IP address as such modification may result in Telnet disconnection. If such modification is required, you need to enter a new IP address of the IP BPX and make a new connection.
The system provides a wide range of configuration commands and the command line interface (CLI) through which you can configure and manage the XE IP PBX. The CLI supports:
l Local configuration through the CONSOLE port.
l Remote configuration through the AUX port.
l Remote configuration through Telnet.
l Management of the configurations of terminal users in user interface view.
l Hierarchical command protection in which users can only execute the commands commensurate with their levels.
l Local, password, and AAA authentication modes that safeguard the XE IP PBX against intrusion of unauthorized users and guarantee system security.
l Easy access to on-line help by entering “?”.
l Commands such as tracert and ping to provide quick network test.
l Abundant debugging information for fault diagnosis.
l The telnet client function that allows you to telnet from the XE IP PBX to other devices for management.
l FTP services that facilitate file upload and download.
l Ability to execute a previously executed command.
l Command line interpreter that provides multiple intelligent command parse methods such as fuzzy match and context association for the convenience of input.
& Note:
You are not allowed to configure IDs or numbers that may conflict with command keywords for XE IP PBX; otherwise, when any of the keywords including, without limitation, active, all, allowable, callin, callout, config, h323, list, sip, subscriber and bind is used, the system prompts error messages in the CLI.
The system commands implement the hierarchical protection model with four levels: visit, monitor, system, and manage.
l Visit: Includes network diagnosis commands such as ping and tracert, and the commands for accessing external devices, such as telnet and rlogin. No commands at this level can be used to save the configuration files.
l Monitor: Provides the commands used for system maintenance and service fault diagnosis, including the display and debugging commands. No commands at this level can be used to save the configuration files.
l System: Includes routing and other service configuration commands that cover all the layers of a network to provide direct network services for users.
l Manage: Includes the commands essential to system operations and support modules. They are service support commands that involve file system, FTP, TFTP, configuration file switch, user management, level setting, as well as the parameter setting within a system (the last case involves those non-protocol or non-RFC specifications) commands.
Commensurate with the command levels, login users are divided into four levels, namely that they can only use the commands at their own, or lower levels.
To prevent intrusion of unauthorized users, a user must undergo authentication when switching to a higher level. In this case, the user must input the higher-level user password, provided one has been set using the super password [ level user-level ] { simple | cipher } text command. Only when the correct password is provided can the user switch to the higher level. Otherwise, the original user level remains unchanged.
& Note:
For the sake of privacy, the system does not display the password that the user has entered.
The user is allowed to make up to three attempts after an incorrect password input.
The command views are implemented according to different configuration requirements. They provide different functions but are still related to each other. For example, after setting up a connection with the XE IP PBX, you enter user view where you can simply view the running status and statistics. By entering system-view in user view, you go to the system view, where you can input different configuration commands to enter the corresponding protocol, interface or functional module view.
Command lines are associated with the following command views:
l User view
l System view
l Interface views including GE interface view and virtual interface view.
l PS view
l LS view
l MS view
l MA view
l OverLoad Protection view
l GUI Server view
l User interface view
Table 2-1 shows the functionality of these command views and the commands for entering them.
Table 2-1 Command view functionality
In command view |
To do… |
Prompt |
Accessed by entering the command |
Exit with the command |
User view |
View brief operating information and statistics about the XE IP PBX |
<XE> |
None (the system accesses user view immediately after a connection is set up with the XE IP PBX) |
quit to disconnect from the XE IP PBX |
System view |
Configure system parameters |
[XE] |
system-view in user view |
quit to return to user view |
User interface view |
Manage the asynchronous and logical interfaces on the XE IP PBX |
[XE-ui0] |
user-interface 0 in system view |
quit to return to the system view |
Interface view |
Configure interface parameters |
[XE-Ethernet1/0] |
interface Ethernet 1/0 in system view |
quit to return to system view |
PS view |
Configure process server |
[XE-ps] |
process-server in system view |
quit to return to system view |
LS view |
Configure location server |
[XE-ls] |
location-server in system view |
quit to return to system view |
MS view |
Configure media server |
[XE-ms] |
media-server in system view |
quit to return to system view |
MA view |
Configure media ability |
[XE-ma] |
media-ability in system view |
quit to return to system view |
OverLoad protection view |
Configure overload protection |
[XE-olp] |
overload-protection in system view |
quit to return to system view |
GUI server view |
Configure GUI server |
[XE-gui] |
gui in system view |
quit to return to system view |
& Note:
The command line prompt uses IP PBX name as prefix (which defaults to H3C), view name as suffix, a pair of parentheses to denote the current view, a pair of point brackets (“<>”) to denote user view, and a pair of square brackets (“[ ]”) to denote system view or any other configuration views.
CLI offers the following online help types:
l Full help
l Fuzzy help
To obtain the desired help information, you can:
1) Enter “?” in any views, and you will obtain all the commands in this view and their simple descriptions as well. For example, <XE> ?.
2) Enter a command and a “?” separated by a space, <XE> display ?. for example. If "?" is at the position of a keyword, all the keywords and their brief descriptions are shown.
3) Enter a command and a “?” separated by a space. If "?" is at the position of a parameter, descriptions of these parameters are shown. For example:
[XE] interface ethernet ?
<0-0> Slot number
[XE] interface ethernet 0?
/
[XE] interface ethernet 0/?
<0-1>
[XE] interface ethernet 0/0 ?
<cr>
<cr> here indicates that no parameter is at this position. In this case, the command is repeated in the next command line and executed if <Enter> is input.
4) Enter a character string followed by a “?”. All the commands starting with this string are displayed. For example:
<XE> d?
debugging delete dir display
5) Enter a command followed by a character string and “?”. All the keywords starting with this string are listed. For example:
<XE> display h?
history-command hotkey
6) Press <Tab> after entering the first several letters of a keyword to have the system display the complete keyword. If more than one keyword has the same letters at the front, press <Tab> repeatedly until the one that you need is displayed.
The commands are executed only if they have no grammar error. Otherwise, error information is reported, as shown in Table 2-2.
Table 2-2 Common command line errors
Error information |
Cause |
Unrecognized command |
The command was not found. |
The keyword was not found. |
|
Wrong parameter |
Parameter type error |
Parameter value overflow |
|
Incomplete command |
Incomplete command |
Too many parameters |
Too many parameters |
Ambiguous command |
Ambiguous parameters |
With the function similar to Doskey, the CLI can automatically save previously executed commands and repeat execution. By default, it saves up to ten history commands for each user. Table 2-3 lists the operations that a user can perform.
Table 2-3 Retrieve history commands
To do… |
Enter the command or press the key |
Result |
View history commands |
display history-command |
Display the history commands that the user has entered and executed successfully. |
Retrieve the previous history command |
Up arrow key or <Ctrl+P> |
Retrieve the previous history command, if there is any. Otherwise, the system rings alarm. |
Retrieve the next history command |
Down arrow key or <Ctrl+N> |
Retrieve the next history command, if there is any. Otherwise, the system rings alarm. |
& Note:
The arrow keys can be used to retrieve history commands in Terminal and Telnet of Windows 3.X. However, the up arrow key is invalid in the HyperTerminal of Windows 9X, because it is interpreted in a different way. In this case, you can use <Ctrl+P> instead.
The display history-command command can only display the successfully executed commands. An end user can use the up arrow key (or <Ctrl+P>) and the down arrow key (or <Ctrl+N>) to display those commands.
The CLI provides the basic command editing features and supports multi-line edit. The maximum length of each command is 254 characters. Table 2-4 shows these functions.
Key |
Function |
Common keys |
If the edit buffer is not full, insert the character at current cursor position and move the cursor to the right. Otherwise, the alarm rings. |
Backspace key |
Delete the character to the left of the cursor and move the cursor back. If the cursor gets to the beginning of the command line, the alarm rings. |
Left-arrow key or <Ctrl+B> |
Move the cursor backward one character, and the alarm rings when the cursor gets to the beginning of the command line. |
Right-arrow key or <Ctrl+F> |
Move the cursor forward one character, and the alarm rings when the cursor gets to end of the command line. |
Tab key |
Press <Tab> after entering part of a keyword to get fuzzy help. If finding a unique match, the system substitutes the complete keyword for the incomplete one and displays it on the next line. If there are several matches, press <Tab> repeatedly until the one that you need is displayed. If a parameter has no match, your original input will remain unchanged and be displayed again on the next line after you press <Tab>. |
The CLI provides the following display features:
When the information displayed exceeds one screen page, the display is paused. In this case, three options shown in Table 2-5 are available.
Key |
Function |
<Ctrl+C> when information is being displayed |
Stop the display and the command execution. |
<Space> when information display pauses |
Continue to display the next screen. |
<Enter> when information display pauses |
Continue to display the next line. |
Regular expressions are a powerful and flexible tool for pattern matching and substitution. They are not restricted to a language or system and have been widely accepted.
When using a regular expression, you need to construct a matching pattern according to a certain rule, and then compare the matching pattern with the target object. The simplest regular expressions exclude all metacharacters. For example, you can specify a regular expression “hello”, which only matches the character string “hello”.
For flexible matching mode construction, regular expressions are allowed to contain some special characters, called metacharacters, to define how other characters appear in the target object. The following table describes the metacharacters.
Metacharacter |
Description |
\ |
Escape character |
. |
Matches any single character except for “\n”, including spaces. |
! |
The character to the left of the exclamation mark in the expression should have no match or one match in the target object. |
* |
The character to the left of the asterisk in the expression should have no match or sequence of matches one after another in the target object. |
+ |
The character to the left of the plus sign in the expression should have one match or sequence of matches one after another in the target object. |
| |
Allows either expression on the side of the alternation character to match the target object. |
^ |
The characters following the ^ sign must appear at the beginning of the target object. |
$ |
The characters before the dollar sign must appear at the end of the target object. |
(xyz) |
The target object must contain the character string in the parenthesis. |
[xyz] |
Matches any character contained in the square brackets. |
[^xyz] |
Matches any character except for those contained in the square brackets. |
[a-z] |
Matches any character within the specified range. |
[^a-z] |
Matches any character beyond the specified range. |
{n} |
The “n” in the brace brackets is a non-negative integer, indicating that there are consecutive n matches for a character string. |
{n,} |
The “n” in the brace brackets is a non-negative integer, indicating that there are consecutive n or more than n matches for a character string. |
{n,m} |
The “m” and “n” in the brace brackets are non-negative integers, with n<=m. It indicates that the consecutive matches are in the range n to m. Note that no space is allowed on either side of the comma. |
For example:
^ip: to match the target object starting with the character string “ip”.
ip$: to match the target object ending with the character string “ip”.
You can use regular expressions to filter out uninterested information when a large amount of information is present.
1) Specify filtering mode between screens
If enormous information is present and output in multiple screens, you can filter information after the prompt ”---- More ----” between screens appears by entering a regular expression in one of the following forms:
l /regular-expression: to output all lines starting with the line that matches the specified regular expression.
l -regular-expression: to output all lines that do not match the specified regular expression.
l +regular-expression: to output only the lines that match the specified regular expression.
For example, you can use the following command to view the current configuration information:
<XE> display current-configuration
#
sysname XE2000
#
interface Aux0
async mode flow
#
interface GigabitEthernet0/0
ip address 192.168.80.50 255.255.255.0
#
interface GigabitEthernet0/1
#
interface NULL0
#
user-interface con 0
user-interface aux 0
user-interface vty 0 4
#
process-server
ps-config gkserver interface GigabitEthernet0/0
heartbeat password xe2000
start
#
gatekeeper
When the prompt “---- More ----” appears, you can manually enter a plus sign (+) and then a regular expression to filter information to be displayed. To output only the lines that contain the character string “gate”, for example:
---- More ----
+interface (manually entered)
filtering...
gateway gw01
gateway gw02
<XE>
The hot keys in the system fall into two types: user-configurable and system.
The user-configurable hot keys include CTRL_G, CTRL_L, CTRL_O, CTRL_T and CTRL_U. You can associate these hot keys with any commands for automatic execution.
The system hot keys have fixed functions and do not allow customization, as shown in Table 2-7.
Keys or commands |
Function |
CTRL_A |
Move the cursor to the beginning of current line |
CTRL_B |
Move the cursor one character leftward |
CTRL_C |
Terminate the running function |
CTRL_D |
Delete the character at the cursor |
CTRL_E |
Move the cursor to the end of current line |
CTRL_F |
Move the cursor one character rightward |
CTRL_H |
Delete the character to the left of the cursor |
CTRL_K |
Terminate the outbound connection |
CTRL_N |
Display the next command in the history command buffer |
CTRL_P |
Display the previous command in the history command buffer |
CTRL_R |
Refresh the information of current line |
CTRL_V |
Pasts the contents on the clipboard |
CTRL_W |
Delete the word to the left of the cursor |
CTRL_X |
Delete all the characters to the left of the cursor |
CTRL_Y |
Delete all the characters to the right of the cursor |
CTRL_Z |
Return to user view |
CTRL_] |
Terminate or re-direct the inbound connection |
ESC_B |
Move the cursor one word leftward |
ESC_D |
Delete the word to the right of the cursor |
ESC_F |
Move the cursor one word rightward |
ESC_N |
Move the cursor downward to the next line |
ESC_P |
Move the cursor upward to the previous line |
ESC_< |
Set the cursor’s location to the beginning of the clipboard |
ESC_> |
Set the cursor’s location to the end of the clipboard |
l You can press a hot key combination wherever you are allowed to enter a command. Then the system displays the corresponding command as if you have entered the complete command.
l If you have entered part of a command without pressing <Enter>, you can delete the input characters and enter a complete command simply by pressing the hot key for this new command.
l Similar to executing a command, after a shortcut key is executed, its corresponding command prototype is retained in the history command buffer and log for retrieving and locating problem.
& Note:
The functionality of a hot key may be the user terminal dependent, for example, the hot key assigned from the terminal may conflict with the one on XE IP PBX. In this case, the application on the terminal responds to the hot key press.
Perform the following configuration in system view.
Operation |
Command |
Define a hot key. |
hotkey { CTRL_G | CTRL_L | CTRL_O | CTRL_T | CTRL_U } command_text |
Restore the default values in the system. |
undo hotkey { CTRL_G | CTRL_L | CTRL_O | CTRL_T | CTRL_U } |
By default, the system assigns defaults to the hot keys of CTRL_G, CTRL_L and CTRL_O as follows:
CTRL_G: display current-configuration
CTRL_L: display ip routing-table
CTRL_O: undo debugging all
The default values of the other hot keys are null by default.
Perform the following configuration in any view.
Table 2-9 Display the hot keys and their definitions
Operation |
Command |
Display the hot keys and their functions. |
display hotkey |
The command alias configuration enables you to replace common Comware commands by what command formats you prefer.
Perform the following configurations in system view.
Table 2-10 Enabling command alias
Operation |
Command |
Enable command alias |
enable command-alias |
Disable command alias |
undo enable command-alias |
By default, the command alias function is disabled.
Perform the following configuration in system view.
Table 2-11 Specifying a command alias
Operation |
Command |
Specify a command alias |
command-alias alias currentfirstcmdkey |
Cancel the configured command alias |
undo command-alias alias |
By default, no command alias is configured.
Perform the following configuration in any view.
Table 2-12 Displaying and Debugging
Operation |
Command |
Display the current alias setting |
display command-alias |
After the XE IP PBX is powered on and you log into the XE IP PBX via the CONSOLE port, the system displays user view with the prompt <H3C>. You can perform the following operation to enter and exit system view.
Table 3-1 Enter and exit system view
Operation |
Command |
Enter system view from user view |
system-view |
Returning to the view of an upper level |
quit |
Return to user view |
return |
Use the quit command to return to an upper level view. If you are in user view, you can use this command to exit the system. You can also run the return command by pressing <Ctrl+Z>.
The name of an IP PBX appears in command prompt. You can change it if necessary.
Perform the following configuration in system view.
Table 3-2 Set the name of an XE IP PBX
Operation |
Command |
Set the name of an XE IP PBX |
sysname sysname |
You must set system clock to the correct time in order to work with other devices properly.
Perform the following configuration in user view.
Operation |
Command |
Set standard time |
clock datetime HH:MM:SS YYYY/MM/DD |
Set time zone |
clock timezone time-zone-name { add | minus } HH:MM:SS |
Remove the setting of time zone |
undo clock timezone |
Set daylight saving time |
clock summer-time summer-time-zone-name { one-off | repeating } start-time start-date end-time end-date add-time |
Remove the setting of daylight saving time |
undo clock summer-time |
Caution:
Be cautious to modify the system clock, which requires shutdown of the LS when the system is running.
The banner text is a message that the system displays after connecting to the XE IP PBX, login authentication, and interactive configuration.
Perform the following configuration in system view.
Operation |
Command |
Set the banner text that will be displayed when entering terminal user interface |
header incoming text |
Set the banner text that will be displayed during authentication |
header login text |
Set the banner text that will displayed upon configuration |
header shell text |
Remove the banner text that has been set |
undo header { incoming | login | shell } |
If you log in as a user with a lower level and want to switch to a higher level, you need to enter the password of a higher level, which should be set previously.
Perform the following configuration in system view.
Table 3-5 Set the password used for switching the user level
Operation |
Command |
Set the password used for switching the user level |
super password [ level user-level ] { simple | cipher } password |
Remove the password that has been set |
undo super password [ level user-level ] |
To switch to a higher user level, you must enter a corresponding password.
Perform the following configuration in user view.
Operation |
Command |
Switch user level |
super [ level ] |
When you are temporarily leaving, to prevent unauthorized access to the terminal interface, you can lock user interface. You must enter and confirm a password to lock user interface. To unlock and enter the user interface again, you must provide the correct password.
Perform the following configuration in user view.
Operation |
Command |
Lock user interface |
lock |
All commands fall into four levels, which are visit, monitor, system, and manage, whose identifier ranges from 0 to 3. Administrators can assign the level of a command and the view it belongs to as needed.
Perform the following configuration in system view.
Table 3-8 Set command privilege
Operation |
Command |
Set command privilege in a view |
command-privilege level level view view command-key |
Reset the default command privilege |
undo command-privilege view view command-key |
Table 3-9 Default command privilege
Code |
Level |
Command |
0 |
Visit |
ping, tracert, telnet |
1 |
Monitor |
display, debugging |
2 |
System |
All configuration commands except for those of manage level |
3 |
Manage |
File System commands, FTP commands, and TFTP commands |
& Note:
Each command belongs to its default view and has corresponding privilege; therefore it is not necessary to reset them.
Use the display command to collect system status information, which can be classified as follows:
l Commands that display system configuration information
l Commands that display the status of system operation
l Commands that display system statistics
For the details of the display command of various protocols and interfaces, refer to corresponding chapters. The table below lists some system-related display commands.
Perform the following configuration in any view.
Table 3-10 Display system status information
Operation |
Command |
Display system version |
display version |
Display system clock |
display clock |
Display terminal user |
display users [ all ] |
Display the saved configuration |
display saved-configuration |
Display current configuration |
display current-configuration |
Display debugging status |
display debugging [ interface { interface-type interface-number | interface-name } ] [ module-name ] |
Display operating configuration of the current view |
display this |
Display diagnostic information |
display diagnostic-information |
Display the contents on clipboard |
display clipboard |
Display the statistics about CPU usage |
display cpu-usage-for-user [ configuration | number [ offset ] [ verbose ] [ from-device ] ] |
When troubleshooting or daily maintenance is required, a lot of information should be collected. But there are multiple display commands and it is difficult to collect all information needed by running one command. You can run the display diagnostic-information command to collect the current running information of each module of the system.
The display diagnostic-information command can list the information displayed after running the following commands: display clock, display version, vrbd, display interface, display current-configuration, display saved-configuration, display ip interface, display ip statistics, display exception 10, display exception 3 verbose , display logbuffer, display history all, etc.
An XE 200 IP PBX has two fast Ethernet (FE) interfaces (electrical) compliant with 100Base-TX physical layer specification; while an XE 2000 has two Gigabit Ethernet (GE) interfaces, one is 1000Base-TX-compliant GE electrical interface and the other is 1000Base-LX and 1000Base-SX-compliant GE optical interface.
The FE electrical interface operates at a speed of 10 Mbps or 100 Mbps, and GE electrical interface at a speed of 10 Mbps, 100 Mbps or 1000 Mbps.
Both FE electrical interface and GE electrical interface support half-duplex and full-duplex modes.
To simplify the configuration and management, both FE electrical interface and GE electrical interface can operate in auto-negotiation mode to negotiate with other network devices to determine the most suitable mode and transmission speed.
Optical interface can only operate in full-duplex mode, and its transmission speed cannot be changed via configuration. GE optical interface can only operate at a speed of 1000 Mbps. The operating mode of the optical interface connecting the XE IP PBX to a network can be aggressive or auto-negotiate, but it must be the same as that of the peer interface.
Both FE and GE Ethernet interface can receive and recognize the Ethernet frame with frame format of Ethernet_II or Ethernet_SNAP, and send frames in Ethernet_II format.
Ethernet interface configuration tasks are described in the following sections:
l Entering the specified Ethernet interface view
l Setting the IP address of the interface
l Enabling/disabling local loopback
You should configure FE interface in Ethernet interface view and GE interface in GE interface view. Every configuration parameter has a default value, so, generally, you need only to configure the IP address to make the system operate normally in most cases.
Perform the following configuration in system view.
Table 3-11 Enter the view of specified Ethernet interface
Operation |
Command |
Enter FE interface view |
interface ethernet number |
Enter GE interface view |
interface GigabitEthernet number |
Perform the following configuration in Ethernet interface view.
Table 3-12 Set the IP address of the interface
Operation |
Command |
Set the IP address of the interface |
ip address ip-address mask |
Remove the IP address of the interface |
undo ip address [ ip-address mask ] |
The parameter of maximum transmission unit (MTU) affects the fragmentation and reassembly of IP packets.
Perform the following configuration in Ethernet interface view.
Operation |
Command |
Set MTU |
mtu size |
Restore to the default value |
undo mtu |
By default, the MTU is in Ethernet_II frame format. The MTU size ranges from 46 to 1500 bytes for FE interface, and 46 to 16384 bytes for GE interface.
An Ethernet interface can operate at multiple speeds. FE interface can operate at 10 Mbps and 100 Mbps, and GE electrical interface at 10 Mbps, 100 Mbps, and 1000 Mbps.
Perform the following configuration in Ethernet interface view.
Table 3-14 Choose transmission speed
Operation |
Command |
Choose the transmission speed of an Ethernet interface |
speed { 10 | 100 | 1000 | negotiation } |
The default is negotiation, which means the system automatically negotiates the optimal speed. You can also specify a speed which must be equal to the actual speed of the network.
As previously mentioned, the Ethernet interface can operate in full and half duplex modes. The Ethernet interface of an XE IP PBX must operate in half duplex mode when connected to a Hub and full duplex mode when connected to a switched Ethernet switch. Perform the following configuration in Ethernet interface view.
Table 3-15 Choose the operating mode
Operation |
Command |
Choose the operating mode of an Ethernet interface |
duplex { negotiation | full | half } |
The default is negotiation, which means the system automatically negotiates the optimal operating mode.
You may need to enable the local loopback when testing some special functions of the Ethernet interface.
Perform the following configuration in the Ethernet interface view.
Table 3-16 Enable/disable local loopback
Operation |
Command |
Enable local loopback |
loopback |
Disable local loopback |
undo loopback |
By default, loopback is disabled.
When the Ethernet interface operates in the promiscuous mode, it receives all correct Ethernet packets without checking their MAC addresses. This mode is applied to traffic monitoring on the network.
Perform the following configuration in Ethernet interface view.
Table 3-17 Configure the operating mode of the Ethernet interface
Operation |
Command |
Enable the Ethernet interface to operate in the promiscuous mode. |
promiscuous |
Disable the Ethernet interface from operating in the promiscuous mode. |
undo promiscuous |
By default, the Ethernet interface operates in the non-promiscuous mode.
Perform the following configuration in any view.
Table 3-18 Display the status of a specified Ethernet interface
Operation |
Command |
Display the status of a specified Ethernet interface |
display interfaces ethernet number |
The configuration of static route includes:
l Configuring a static route
l Configuring a default route
l Configuring static route privileges
l Deleting a static route
Static routes are routes which the administrator configures manually. Through the configuration of static routes, you can build an interconnected network. Each static route has one of the following properties, so there are three kinds of routes:
l Reachable route: which is the case for common routes, that is, IP packets are sent to the next hop along the route marked by the destination.
l Destination unreachable route: When a static route to a destination has the property of reject, any IP packet bound for it will be discarded, and the source will be informed that the destination is unreachable.
l Blackhole route: When a static route to a destination has the property of blackhole, any IP packet bound for it will be discarded, and the source will not be informed.
Among the properties, the reject and blackhole are commonly used to control the range of destination that the XE IP PBX can reach and can help troubleshoot the network.
The default route is a special case of static route, which is used when no matched route is found. In a routing table, a default route has a routing address/mask pair of 0.0.0.0/0.0.0.0. You can view the destination of a default route by running the display ip routing-table command.
If the destination address of a packet does not match any route, the default route will be used to forward this packet. If the default route does not exist and the destination of the packet is not in routing table, the packet will be discarded, and an ICMP destination unreachable message will be returned.
Perform the following configuration in system view.
Table 3-19 Configure static route
Operation |
Command |
Add a static route |
ip route-static ip-address { mask | mask-length } { interface-name | nexthop-address } [ preference preference-value ] [ reject | blackhole ] |
Delete a static route |
undo ip route-static ip-address { mask | mask-length } [ interface-name | nexthop-address ] [ preference preference-value ] |
Perform the following configuration in system view.
Table 3-20 Configure a default route
Operation |
Command |
Configure a default route |
ip route-static 0.0.0.0 { 0.0.0.0 | 0 } {interface-name | nexthop-address } [ preference value ] [ reject | blackhole ] |
Delete a default route |
undo ip route-static 0.0.0.0 { 0.0.0.0 | 0 } [interface-name | nexthop-address] [ preference value | reject | blackhole ] |
Perform the following configuration in system view.
Table 3-21 Delete all static routes
Operation |
Command |
Delete all static routes |
delete static-routes all |
You can delete all configured static routes by running this command, including the default route.
After the previous configuration, you can view the information of the configured static route in any views by running the display command to verify the configuration.
Perform the following configuration in system view.
Table 3-22 Display and debug routing table
Operation |
Command |
View the routing table summary |
display ip routing-table |