Chapters Download(3 MB)
Table of Contents
1.1 Introduction to Voice Gateway
Chapter 2 Fundamental Configuration
2.1 Setting up Configuration Environment
2.1.1 Setting up Local Configuration Environment through the Console Port
2.1.2 Setting up the Local or Remote Configuration Environment by Using Telnet
2.2 Command Line Interface (CLI)
2.2.4 Displaying History Configuration
2.3.2 Terminal Security Features
2.3.3 Configuring Login Authentication and Authorization
2.4 Basic System Configuration
2.4.1 Basic System Configuration and Management
2.4.2 Displaying the Statistics of VG
2.5.1 Configuring Ethernet Interface
2.5.2 Displaying and Debugging Ethernet Interface
2.5.3 DHCP Client Configuration Example
2.6 Default Route Configuration
H3C VG Voice Gateway (hereinafter referred to as VG), developed by H3C Technology Co., Ltd. (hereinafter referred to as H3C) for industrial and SOHO (small office/home office) users, is a new-generation access device which supports integration of voice and fax.
VG implements the access of voice or fax signals and converts them into digital signals. It then encapsulates these digital signals into IP packets and transfers them to IP network via the Ethernet interfaces.
The cost-effective VG supports multiple IP telephony attributes, for example, voice over IP (VoIP), fax over IP (FoIP), call control, resource management, maintenance and management. It supports diversified codec types and can obtain IP address as a Dynamic Host Configuration Protocol (DHCP) Client. .
VG uses ITU-T Recommendation H.323, high-performance DSP chips and coding/decoding algorithm of high compression ratio. It also supports echo cancellation, silence suppression, comfortable noise, jitter buffer. These measures, combined with security and QoS attributes, can guarantee transmission quality of voice and fax services over IP network.
The VG supports both normal and fast connection modes. With tunneling technology, it achieves out-of-band transmission of DTMF (dual-tone multi-frequency) code. The VG also provides busy tone detection, dedicated line dial, as well as some peculiar services, including do-not-disturb, call forwarding on busy, alarm call service, group line access, etc.
Currently VG provides Ethernet interfaces, FXS interfaces, FXO interfaces and E1VI trunk interfaces, which can connect with common phone sets or Private Branch Exchanges (PBX) or Local Area Network (LAN) or Wide Area Network (WAN).
A typical networking of VG is illustrated in Figure 1-1.
Figure 1-1 Typical networking of VG
Functional module |
Attributes |
|
Voice attributes |
IP voice |
Supports silence suppression, echo cancellation, comfortable noise, jitter buffer and volume turning. Supports special PBX functions (do-not-disturb, call forwarding on busy, unconditional call forwarding, alarm call service, group line access). Supports fast connection and tunneling function. Supports caller identification display (CID). Supports voice communication via Loopback interfaces. Supports manual detection and auto detection on busy tone. Supports such policies as PSTN backup and GK backup. Supports static, dynamic and hybrid VoIP routing policies. Supports fast and normal transceiving of voice and data packets. |
Fax |
In compliance with ITU-T Recommendations T.30 and T.38. Multiple fax parameters can be customized. Supports fax communication over IP network. |
|
Call control protocol |
H.323 |
|
Voice CODEC mode |
G.711 A, G.711U, G.723r53, G.723r63, G.729A, and G.729r8 |
|
Voice RADIUS |
Supports voice RADIUS authentication, authorization and accounting. Supports prior authentication of local voice users. Supports user authentication based on account/password, caller number and voice caller number process. Supports one-stage dialing and two-stage dialing. Supports interworking with RADIUS servers of various types. |
|
GK Client |
Serves as GK client for exchanging RAS messages with GK server |
|
Link layer protocol |
LAN |
Supports Ethernet_II and Ethernet_SNAP frame structure. In compliance with IEEE 802.2 and IEEE 802.3 |
Network layer protocol |
IP service |
Dynamic ARP and static ARP. IP address management. |
IP performance |
Supports IP fast forwarding. |
|
IP routing |
Supports static route. |
|
Filtering with firewall |
Supports standard and extended ACL. |
|
Data security |
Supports terminal access control protection (hierarchical user protection and login authentication). |
|
Maintenance and management |
Configuration management |
Supports local and remote configuration via Console port or using Telnet. Supports maintenance and management in Web interface and CLI mode. Displays prompt and help information in both Chinese and English. |
System management |
Supports uploading, downloading and configuring program files using XModem, FTP and TFTP. |
|
Network management |
Supports SNMP v1, v2 and v3. |
|
Maintenance and test |
Provides detailed debug information, for convenience of locating network faults. Provides network diagnostic tool tracert and ping. Supports log function. |
Connect the serial port of the workstation to the Console port of the VG to set up local configuration environment.
Step 1: Connect the serial port of the workstation to the Console port of the VG with RS-232 cable. See Figure 2-1.
Figure 2-1 Setting up local configuration environment through Console port
Step 2: Start terminal emulation program on the workstation, for example, HyperTerminal on Windows 9x, to set up new connection. Configure the following parameters for the RS232 serial port: Baudrate as 9600, data bit as 8, stop bit as 1, parity as none, flow control as none and terminal emulation type as VT100. See Figure 2-2, Figure 2-3, Figure 2-4 and Figure 2-5 (HyperTerminal on Windows 9x).
Figure 2-2 Setting up new connection
Figure 2-3 Selecting serial port for the connection
Figure 2-4 Setting parameters for the serial port
Figure 2-5 Selecting terminal emulation type
Step 3: Power on the VG and it begins the self-test and load system programs. After the startup is completed, the VG prompts you to press <Enter> to enter the system view. For the initial use, no user name and password are configured. If you have configured the user account and configured to authenticate the user logging onto the console port, you need to input the username and password to enter the system view.
Step 4: You can configure the VG or view its running status through entering corresponding commands. Also you can enter “?” for online help.
Connect the serial port of the workstation to the Console port of the VG to set up the local configuration environment.
Step 1: Connect the serial port of the workstation to the Console port of the VG with an RS-232 cable. See Figure 2-1.
Step 2: Start terminal emulation program on the workstation, for example, HyperTerminal on Windows 9x, to set up a new connection. Configure the following parameters for the RS232 serial port: Baudrate as 9600, data bit as 8, stop bit as 1, parity as none, flow control as none and terminal emulation type as VT100. See Figure 2-6 through Figure 2-11 (HyperTerminal on Windows XP).
Figure 2-6 Set up new connection
Figure 2-7 Location Information window
Figure 2-8 Select a PC port for connection
Figure 2-9 Set parameters for the port
Figure 2-11 Select the type of terminal emulation program
Step 3: Power on the VG and it begins the self-test and load the system programs.
After the startup is completed, the VG prompts you to press <Enter> to enter the system view. For the initial use, no user name and password are configured. If you have configured the user account and configured to authenticate the user logging onto the console port, you need to input the username and password to enter the system view.
Step 4: You can configure the VG or view its running status through entering corresponding commands. Also you can enter “?” for online help.
You can set up connection over LAN and WAN (wide area network) with the VG using Telnet client program and log onto it for further configuration.
Step 1: Connect the Ethernet port of the workstation through LAN or WAN to the VG. See Figure 2-12 and Figure 2-13.
Figure 2-12 Set up local configuration environment using Telnet
Figure 2-13 Set up remote configuration environment using Telnet
& Note:
For the connection through WAN, make sure the VG is reachable to the workstation.
Step 2: Start Telnet client program on the workstation and set terminal emulation type as VT100. See Figure 2-14 and Figure 2-15 (Telnet on Windows 9x).
Figure 2-14 Start Telnet program
Figure 2-15 Set up Telnet connection with the VG
& Note:
In the above figure, the host name is the IP address of the WAN interface for remote connection with the VG.
After you set up the Telnet connection successfully, the system will prompt you to enter the username and password. If the authentication succeeds, the command line prompt ([VG], for example) appears. The message “Too many users or telnet permit!” means that you cannot log onto the VG due to too many registered users. Telnet generally supports five users at most.
Step 3: Enter corresponding commands to configure the VG or view its running status. You can also enter “?” for online help.
& Note:
In the whole process of configuring the VG through Telnet connection, do not change the IP address of the VG interface used in Telnet connection, otherwise the Telnet connection will terminate. If it is unavoidable, you should enter the new IP address of the Ethernet interface after modifying the VG IP address to set up the Telnet connection again. You must configure at least one user when logging using Telnet.
The VG provides a set of commands for configuration and management of network devices. The CLI is characterized by the following features:
l Local configuration through Console port
l Remote configuration using Telnet
l Providing online help any time the user keys in “?”
l Providing commands tracert, ping to test if the network is normal
l Supporting TFTP and FTP for convenient uploading and downloading of program files and configuration file
l Fuzzy matching of keywords (not in conflict) in search for commands. For example, you can input dis to search for the command display.
A view is a CLI interface of the VG. You can execute most commands in specific views. For example, you can configure voice-related functions and parameters only in voice view. For easy operations, some basic configuration commands are available in any view.
The CLI views are in different levels. From the system view, you can enter any other views and then into sub-functional views. The view architecture is detailed in Figure 2-16.
Figure 2-16 View architecture of the VG
The functions and corresponding commands for different CLI views are listed in Table 2-1.
Table 2-1 Attribute list of CLI views
View |
Function |
Prompt |
Enter command |
Exit command |
System view |
Configures system parameters |
[VG] |
Enter upon successful login |
Use the logout command to disconnect Telnet connection with the VG |
Ethernet interface view |
Configures parameters for Ethernet interface |
[VG-Ethernet0] |
Enter “interface ethernet 0” in any view |
Use the quit command to return to the system view |
Loopback interface view |
Configures parameters for Loopback interface |
[VG-LoopBack1] |
Enter “interface loopback 1” in any view |
Use the quit command to return to the system view |
ACL view |
Configures ACL rules |
[VG-acl-2000] |
Enter “acl 2000” in system view |
Use the quit command to return to the system view |
Voice view |
Configures voice parameters |
[VG-voice] |
Enter “voice-setup” in system view |
Use the quit command to return to the system view |
Voice dialup program view |
Configures voice dialing policy. |
[VG-voice-dial] |
Enter “dial-program” in the voice view |
Use the quit command to return to the system view |
Voice line view |
Configures voice line parameters |
[VG-voice-line0] |
Enter “subscriber-line0” in system view or voice view |
Use the quit command to return to the voice view |
Voice entity view |
Configures parameters for voice entity |
[VG-voice-dial-entity1] |
Enter “entity 1 port” or “entity 1 voip” in voice dialing policy view |
Use the quit command to return to voice dialing policy view |
Voice AAA view |
Configures voice AAA service |
[VG-voice-aaa] |
Enter “aaa-client” in voice view |
Use the quit command to return to the voice view |
Access number view |
Configures parameters for access number |
[VG-voice-dial-anum12345] |
Enter “gw-access-number 12345” in the voice dialing policy view |
Use the quit command to return to voice dialing policy view |
Voice gatekeeper view |
Configures parameters for voice gatekeeper |
[VG-voice-gk] |
Enter “gk-client” in voice view |
Use the quit command to return to the voice view |
& Note:
l The command prompt is expressed by network device name (VG by default) plus CLI view name, fox example, [VG-route-policy].
l Some commands can only be executed in the specific views, while others, including ping, display, debugging, reset, save and interface, are available in any view.
l Some views require you to enable the corresponding functions or configure related restrictive conditions before entering.
l In any view except system view, you can use the quit command to return to the upper-level view, and use the return command to directly return to the system view.
The VG provides the following two types of CLI online help:
l Full help
l Partial help
With the help, you can get the following information:
Full help ---- You can get all commands available in a certain view and simple description by entering “?”.
[VG] ?
aaa-enable Enable Authentication, Authorization, Accounting
acl Specify access-list configuration
arp Add an ARP entry
……
Partial help ---- You can get all keywords available (if there are any) and simple description by entering a command and a "?" which is separated by a space from the command.
[VG] display ?
aaa AAA information
acl Display access-list information
arp ARP table
base-information Some essential system information
client Current client information
clock Current router clock information
……
Partial help ---- You can get all commands starting with the string by entering a string and “?” which follows the string.
[VG] d?
debugging delete display download
Partial help ---- You can get all keywords starting with the string by entering a command and a string immediately followed by “?”.
[VG] display a?
aaa acl arp
Only those commands in correct syntax can be executed. Otherwise the system prompts error information. Table 2-2 lists common CLI error information.
Table 2-2 Common CLI error information
Error information |
Explanation |
Incorrect command |
No matching command is found. |
No matching keyword is found. |
|
Parameter type is wrong. |
|
Incomplete command |
The command is incomplete. |
Invalid parameters |
Parameter value is beyond the range. |
Too many parameters |
You have input too many parameters. |
A maximum of 20 history commands you have entered can be saved in the CLI for later use or repeated execution.
Perform the following configuration in any view.
Table 2-3 Display history commands
Operation |
Command |
Display history command |
display history-command |
Press the following composite keys in any CLI view to call the history commands.
Table 2-4 View history commands
Operation |
Composite key |
remarks |
View the previous history command |
Up arrow key or <Ctrl+P> |
If there is history command used earlier, then it recalls the previous one. |
View the next history command |
Down arrow key or <Ctrl+N> |
If there is history command used later, then it recalls the next one. |
The VG also supports command editing, with up to 255 characters for each command.
To edit commands, press the following keys in any CLI view.
Key |
Function |
Common keys |
If the edit buffer is not filled up, the corresponding character will be added at the current position of the cursor and the cursor moves to the right. Otherwise, it gives alert. |
BackSpace |
Delete the character before the cursor. It gives alert when the curser reaches the beginning of a command line. |
Delete |
Delete the character after the cursor. It gives alert when the cursor reaches the end of a command line. |
¬ or <Ctrl+B> |
The cursor moves to the left the length of character. It gives alert when the curser reaches the beginning of a command line. |
® or <Ctrl+F> |
The cursor moves to the right the length of a character. It gives alert when the cursor reaches the end of a command line. |
When the information to be displayed exceeds the screen size, three options may be involved.
Table 2-6 Function keys for terminal display
Operation |
Key(s) |
Stop display |
Press <Ctrl+C> during pause |
Continue display in next screen |
Press spacebar during pause |
Continue display in next line |
Press <Enter> during pause |
Table 2-7 Shortcut keys for VG
Operation |
Key(s) |
Display the current configurations |
Ctrl+A |
Close all debugging |
Ctrl+D |
Switch to system view |
Ctrl+Z |
Display the route table |
Ctrl+R |
Enter for confirmation |
Ctrl+J or Ctrl+M |
Backspace |
Ctrl+H |
Three kinds of users are involved in VG management: administrator, operator and guest. They are authorized with different rights.
An administrator can execute all commands available in the VG. Only an administrator can configure all of the functions and parameters for the VG and enter the aforementioned CLI views.
l An operator is authorized with the right to view system status and perform debugging. An operator can execute the following commands only:
debugging Enable system debugging functions
display Display system running information
language Switch language mode
logout logout
ping Send ICMP ECHO_REQUEST packets to network hosts
telnet Telnet to a remote host
tracert Trace the route taken by packets to reach a network host
undo Remove a command or restore its defaults
l A guest can only perform remote test on the VG and execute these commands:
language Switch language mode
logout logout
ping Send ICMP ECHO_REQUEST packets to network hosts
telnet Telnet to a remote host
tracert Trace the route taken by packets to reach a network host
Perform the following configuration in system view.
Operation |
Command |
Add a user |
local-user user-name [ service-type type ] [ password { simple | cipher } password ] |
Delete a user |
undo local-user user-name |
By default, no user is configured on the VG.
If no administrator is configured on the VG after the AAA function is enabled through the aaa-enable command, then any user who logs on from the Console port will directly log onto the system, as an administrator without user authentication (the system do not prompt you to enter username and password). But other login modes (except HTTP) require user authentication by default.
& Note:
l At least one administrator should be configured on the VG. Otherwise, anyone can log onto the system from the Console port without authentication.
l At least one user should be configured. Otherwise, no login mode (except HTTP) is available, except the login from the Console port.
& Note:
l If the password of an administrator is lost, you can log onto the system as other administrator to modify the password. If only one administrator is configured, then the only way available is to enter Boot menu upon system startup and clear the username and password. Then restart the VG. Now you can directly log onto the system as administrator without being prompted to enter username and password.
l For details about the Boot menu, see the corresponding H3C VG voice gateway installation manual.
Perform the following configuration in system view.
Operation |
Command |
Add a user |
local-user user-name [ service-type type ] [ password { simple | cipher } password ] |
Delete a user |
undo local-user user-name |
By default, no user is configured.
l Nothing is displayed when the user is entering the password.
l The terminal user will be disconnected after entering wrong password for three times.
l After the idle-timeout command is executed, if the terminal user enters nothing within five minutes, he/she will be disconnected.
The terminal users can log onto the system from the Console port, using Telnet and through Web. Correspondingly they are called Console users, Telnet users and Web users respectively.
The operation tasks include:
l Configuring login authentication and authorization scheme list
l Starting login authentication and authorization scheme list
You can configure user login authentication and authorization as local database authentication and authorization, RADIUS server authentication and authorization, or none.
Perform the following configuration in system view.
Table 2-10 Configure AAA login authentication and authorization
Operation |
Command |
Configure login authentication and authorization scheme list |
aaa authentication-scheme login { default | scheme-name } { method [ method ] } |
Delete authentication and authorization scheme list of a specified user |
undo aaa authentication-scheme login { default | scheme-name } |
By default, the login authentication and authorization scheme list is aaa authentication-scheme login default local.
You can also define a scheme list name scheme-name.
method refers to the authentication and authorization scheme list and must be set as one or two among the following methods:
local: Perform authentication and authorization locally.
radius: Perform authentication and authorization using RADIUS server.
none: Perform no authentication and authorization, thus any user can access the VG without authentication and authorization.
If the scheme list name scheme-name is not defined, execution order for authentication and authorization in the default scheme list will be adopted.
You start login authentication and authorization when you select login authentication and authorization scheme list.
The VG supports four login modes: console (Console port), telnet (Telnet), http (HTTP) and ftp (FTP). They can use different login authentication and authorization scheme lists.
& Note:
If no administrator is configured, console login mode requires no authentication and authorization while telnet login mode still requires.
Perform the following configuration in system view.
Table 2-11 Specify login authentication and authorization scheme list
Operation |
Command |
Specify a login authentication and authorization scheme list |
login-method authentication-mode login-type { default | scheme-name } |
Use default scheme list for login authentication and authorization |
undo login-method authentication-mode login-type |
For console (Console port), telnet (Telnet) and ftp (FTP) login users, authentication and authorization is required and default scheme is selected by default. However, http (HTTP) login users can log in without authentication and authorization.
The basic system configuration and management tasks include
l Configuring system name
l Setting system clock
l Rebooting the system
Perform the following configuration in system view.
Table 2-12 Configure system name
Operation |
Command |
Configure system name |
sysname sysname |
By default, the system name is “VG”.
Perform the following configuration in system view.
Operation |
Command |
Set system clock |
clock { systime HH:MM:SS YYYY MM DD | timezone name { add | minus } HH:MM:SS } |
Restore default system clock |
undo clock timezone |
By default, the initial system time is 01:00:00 Jan 1 1998.
& Note:
The system clock will return to the initial time when you first clear clock configuration in Boot menu or run the delete command and then restart the VG.
Perform the following configuration in system view.
Operation |
Command |
Reboot the system |
reboot [ reason reason-string ] |
Set system rebooting after a preset period |
reboot mode interval { hh:mm | mmm } [ reason-string ] |
Set system rebooting at a preset time |
reboot mode time hh:mm [ dd/mm/yyyy ] [ reason-string ] |
Cancel system rebooting |
reboot cancel |
& Note:
Save the configuration file with the save command first before rebooting the system. Otherwise, the configurations will be lost after rebooting.
Perform the following configuration in any view.
Table 2-15 Display statistics of the VG
Operation |
Command |
Display current date and clock |
display clock |
Display the time from system startup to executing the command |
display duration |
Display system name |
display sysname |
Display system CPU |
display system cpu |
Display system memory |
display system memory { all | blksize size } [ detail ] |
Display basic information about VG |
display base-information [ page ] |
Display system version |
display version |
Display software version |
version |
See H3C VG Series Voice Gateways Command Manual for details about the commands listed above and the corresponding terminal display information.
Ethernet interface configuration tasks include:
l Entering a specified Ethernet interface view
l Setting network protocol address
l Setting an Ethernet interface to obtain its IP address through DHCP
l Setting frame format for sending messages
l Setting MTU
l Setting speed for an FE interface
l Setting Ethernet interface mode
l Setting Ethernet interface mode
l Enabling or disabling loopback on an Ethernet interface
l Configuring work mode of the VG
To configure the Ethernet interface, you should first enter a specified Ethernet interface view. Then just configure IP address and use the default values for other parameters. If necessary, you can also modify the parameters.
Perform the following configuration in any view.
Table 2-16 Enter a specified Ethernet interface view
Operation |
Command |
Enter a specified Ethernet interface view |
interface ethernet number |
The Ethernet interface of the VG only supports Internet Protocol (IP).
Please perform the following configurations in Ethernet interface view.
Table 2-17 Set IP address for an Ethernet interface
Operation |
Command |
Set IP address for an Ethernet interface |
ip address ip-address mask [ sub ] |
Delete IP address of an Ethernet interface |
undo ip address [ ip-address mask ] [ sub ] |
When configuring two or more IP addresses for an Ethernet interface, the second and the followed ones (secondary IP address) must be added with the keyword sub. The secondary IP address becomes primary one automatically if no primary address is available.
When the factory default settings are adopted, or after you use the reset saved-configuration command to reset all settings and reboot the VG, the system automatically assigns the default IP addresses for the Ethernet interfaces to ensure the management through Web-based interfaces.
For VG with two Ethernet interfaces:
Default IP address of the WAN interface: 192.168.192.1, the subnet mask is: 255.255.255.0
Default IP address of the LAN interface: 192.168.193.1, the subnet mask is: 255.255.255.0
For VG with one Ethernet interfaces:
Default IP address of the ETH interface: 192.168.192.1, the subnet mask is: 255.255.255.0
Caution:
l Do not modify the IP address for the Ethernet interface on the VG during an ongoing voice call. Otherwise, the call may be interrupted.
l When the VG adopts factory default settings, the Ethernet interface has a default IP address. If you modify the address or delete it using the undo ip address command and save your configurations, the default IP address will be lost.
Perform the following configuration in Ethernet interface view.
Table 2-18 Set an Ethernet interface to obtain its IP address through DHCP
Operation |
Command |
Set an Ethernet interface to obtain its IP address through DHCP |
ip address dhcp-alloc |
Cancel an Ethernet interface to obtain its IP address through DHCP |
undo ip address dhcp-alloc |
By default, the Ethernet interface is not set to obtain its IP address through DHCP.
& Note:
l You cannot use the ip address dhcp-alloc command and the ip address ip-address { mask | mask-length } command at the same time.
l The ip address dhcp-alloc command does not support setting the secondary IP address.
Perform the following configuration in system view.
Table 2-19 Configure the descriptive string for an interface
Operation |
Command |
Configure the descriptive string for an interface |
description string |
Delete the descriptive string of an interface |
undo description |
The Ethernet interface supports both Ethernet_II and Ethernet_SNAP frames for receiving messages, but only one of them for sending messages.
Perform the following configuration in Ethernet interface view.
Table 2-20 Set frame format for sending messages
Operation |
Command |
Set frame format for sending messages |
send-frame-type { ethernet_ii | ethernet_snap } |
Reset frame format to the default value |
undo send-frame-type |
By default, messages are sent in Ethernet_II frames.
The parameter MTU (maximum transmission unit) affects segmentation and reassembly of IP packets.
Perform the following configurations in Ethernet interface view.
Operation |
Command |
Set MTU |
mtu size |
Reset MTU to the default value |
undo mtu |
By default, the MTU size for Ethernet_II frame is 1500 bytes and that for Ethernet_SNAP frame is 1492 bytes.
The FE interface can run at the rate of 10 Mbps or 100 Mbps.
Perform the following configuration in Ethernet interface view.
Table 2-22 Set speed for an FE interface
Operation |
Command |
Set speed for an FE interface |
speed { 100 | 10 | negotiation } |
By default, the speed is set as negotiation. You can also set a value for the speed, but note that the value should be equal to the actual speed.
The Ethernet interface can runs in both full duplex and half duplex modes. When connected with Hub, it runs in half duplex mode. When connected with LAN Switch, it runs in full duplex mode.
Perform the following configuration in Ethernet interface view.
Table 2-23 Set Ethernet interface mode
Operation |
Command |
Set Ethernet interface mode |
duplex { negotiation | full | half } |
The Ethernet interface runs in negotiation mode by default.
Loopback is required at the Ethernet interface in testing some special functions.
Perform the following configurations in Ethernet interface view.
Table 2-24 Enable or disabling loopback on an Ethernet interface
Operation |
Command |
Enable loopback on the interface |
loopback |
Disable loopback on the interface |
undo loopback |
By default, loopback is disabled.
The VG can work in one of two modes as required. In the HUB mode, the VG receives data through one Ethernet interface and send it through another directly. In the router mode, the VG forwards data based on the route table.
Perform the following configurations in system view.
Table 2-25 Configure work mode of the VG
Operation |
Command |
Configure the VG to work in HUB mode |
hub-enable |
Restore the default work mode of the VG |
undo hub-enable |
By default, the VG works in the route mode.
Perform the following configuration in any view.
Table 2-26 Display status of a specific Ethernet interface
Operation |
Command |
Display status of a specific Ethernet interface |
display interfaces ethernet number |
Enable debugging on the dhcp client side |
debugging dhcp client { event | packet | error | all } |
Enable debugging on the Ethernet interface |
|
Enable debugging on packets received at the physical layer |
debugging physical { all | receive | transmit } [ interface ethernet interface-number ] |
DHCP client obtains its IP address from the DHCP server in the same network segment. The address pool (with the segment 10.1.1.0/24) of the DHCP server consists of two segments: 10.1.1.0/25 and 10.1.1.128/25. The IP addresses of two Ethernet interfaces of the DHCP server are 10.1.1.1/25 and 10.1.1.129/25 respectively.
Figure 2-17 Network diagram for DHCP client
# Set the Ethernet interface of the VG to obtain its IP address dynamically through DHCP.
[VG] interface ethernet 0
[VG-Ethernet0] ip address dhcp-alloc
Default route is a kind of static route. It will be used when no matching route is found in the IP routing table. In the IP routing table, its destination address and mask both are 0.0.0.0. You can use the command display ip routing-table to check if the default route has been configured. If the destination of a packet is absent in the IP routing table and no default route is configured, then the packet will be discarded and an ICMP message will be returned to the source end to indicate that the destination or the network is unreachable.
In general, it’s enough to configure one default route for the VG. For more details about routes, refer to Configuring Data Network of this manual.
Perform the following configuration in system view.
Table 2-27 Configure default route
Operation |
Command |
Configure default route |
ip route-static 0.0.0.0 { 0.0.0.0 | 0 } nexthop-address [ preference value ] [ reject ] [ blackhole ] |
Delete default route |
undo ip route-static 0.0.0.0 { 0.0.0.0 | 0 } [ interface-type interface-number | nexthop-address ] [ preference value ] |
& Note:
For PPPoE-supported VG 10-40 and VG 10-41 configured with the Dialer interface, the ip route-static 0.0.0.0 { 0.0.0.0 | 0 } { nexthop-address | dialer 0 ] } [ preference value ] [ reject ] [ blackhole ] command can be used to configure the default route.
By default, no default route is configured.