- Table of Contents
-
- H3C SecPath M9000 Multi Service Security Gateway Configuration Examples(V7)(E9X71)-6W700
- 00-Preface
- 01-About the configuration examples
- 02-Web Login Configuration Examples
- 03-Internet Access Through a Static IP Address Configuration Examples
- 04-Internet access through PPPoE configuration examples
- 05-License Configuration Examples
- 06-Signature Library Upgrade Configuration Examples
- 07-Software Upgrade Examples
- 08-Routing deployment configuration examples
- 09-Transparent deployment configuration examples
- 10-Static routing configuration examples
- 11-RIP configuration examples
- 12-OSPF configuration examples
- 13-BGP configuration examples
- 14-Policy-based routing configuration examples
- 15-Security Policy Configuration Examples
- 16-APR-Based Security Policy Configuration Examples
- 17-Object Group Configuration Examples
- 18-User identification configuration examples
- 19-Attack defense configuration examples
- 20-Request Limit Configuration Examples
- 21-IPS Configuration Examples
- 22-URL Filtering Configuration Examples
- 23-Anti-Virus Configuration Examples
- 24-File Filtering Configuration Examples
- 25-Data Filtering Configuration Examples
- 26-WAF Configuration Examples
- 27-IP Reputation Configuration Examples
- 28-APT Defense Configuration Examples
- 29-NetShare Control Configuration Examples
- 30-Bandwidth Management Configuration Examples
- 31-IPsec configuration examples
- 32-SSL VPN IP access configuration examples
- 32-SSL VPN TCP access configuration examples
- 32-SSL VPN Web access configuration examples
- 33-L2TP Configuration Examples
- 34-NAT configuration examples
- 35-NPTv6 Configuration Examples
- 36-Policy-based NAT configuration examples
- 37-NAT hairpin configuration examples
- 38-NAT Flow Logging Configuration Examples
- 39-Inbound Link Load Balancing Configuration Examples
- 40-Outbound Link Load Balancing Configuration Examples
- 41-Server Load Balancing Configuration Examples
- 42-Transparent DNS Proxy Configuration Examples
- 43-Hot Backup Configuration Examples
- 44-Context Configuration Examples
- 45-DNS configuration examples
- 46-Server Connection Detection Configuration Examples
- 47-Connection Limit Configuration Examples
- 48-Public key management configuration examples
- 49-SSL Decryption Configuration Examples
- 50-MAC Address Learning Through a Layer 3 Device Configuration Examples
- 51-4G Configuration Examples
- 52-WLAN Configuration Examples
- Related Documents
-
Title | Size | Download |
---|---|---|
00-Preface | 99.39 KB |
Preface
The configuration examples include the network configuration requirements, procedure, and verification
This preface includes the following topics about the documentation:
· Audience.
· Conventions.
Audience
This documentation is intended for:
· Network planners.
· Field technical support and servicing engineers.
· Network administrators.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention |
Description |
Boldface |
Bold text represents commands and keywords that you enter literally as shown. |
Italic |
Italic text represents arguments that you replace with actual values. |
[ ] |
Square brackets enclose syntax choices (keywords or arguments) that are optional. |
{ x | y | ... } |
Braces enclose a set of required syntax choices separated by vertical bars, from which you select one. |
[ x | y | ... ] |
Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none. |
{ x | y | ... } * |
Asterisk marked braces enclose a set of required syntax choices separated by vertical bars, from which you select a minimum of one. |
[ x | y | ... ] * |
Asterisk marked square brackets enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none. |
&<1-n> |
The argument or keyword and argument combination before the ampersand (&) sign can be entered 1 to n times. |
# |
A line that starts with a pound (#) sign is comments. |
GUI conventions
Convention |
Description |
Boldface |
Window names, button names, field names, and menu items are in Boldface. For example, the New User window opens; click OK. |
> |
Multi-level menus are separated by angle brackets. For example, File > Create > Folder. |
Symbols
Convention |
Description |
An alert that calls attention to important information that if not understood or followed can result in personal injury. |
|
An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software. |
|
An alert that calls attention to essential information. |
|
NOTE: |
An alert that contains additional or supplementary information. |
An alert that provides helpful information. |
Network topology icons
Convention |
Description |
Represents a generic network device, such as a router, switch, or firewall. |
|
Represents a routing-capable device, such as a router or Layer 3 switch. |
|
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features. |
|
Represents an access controller, a unified wired-WLAN module, or the access controller engine on a unified wired-WLAN switch. |
|
Represents an access point. |
|
Represents a wireless terminator unit. |
|
Represents a wireless terminator. |
|
Represents a mesh access point. |
|
Represents omnidirectional signals. |
|
Represents directional signals. |
|
Represents a security product, such as a firewall, UTM, multiservice security gateway, or load balancing device. |
|
Represents a security module, such as a firewall, load balancing, NetStream, SSL VPN, IPS, or ACG module. |
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model, configuration, or software version. It is normal that the port numbers, sample output, screenshots, and other information in the examples differ from what you have on your device.
Documentation feedback
You can e-mail your comments about product documentation to [email protected].
We appreciate your comments.