sonicwall:basic_configurations_support_site_and_vpn_scenarios
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sonicwall:basic_configurations_support_site_and_vpn_scenarios [2025/02/23 18:38] – aperez | sonicwall:basic_configurations_support_site_and_vpn_scenarios [2025/09/12 14:43] (current) – aperez | ||
|---|---|---|---|
| Line 30: | Line 30: | ||
| Connect a computer to the SonicWall' | Connect a computer to the SonicWall' | ||
| - | Ping the Gateway (**192.168.1.254**). | + | Ping the Gateway (**https://192.168.1.254**). |
| The SonicWall security appliance supports the following management protocols: **HTTP**, **HTTPS**, **SSH**, **Ping**, and **SNMP**. | The SonicWall security appliance supports the following management protocols: **HTTP**, **HTTPS**, **SSH**, **Ping**, and **SNMP**. | ||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | |||
| + | Type: config (hit enter) | ||
| + | -----------config(C0EAE4009930)# | ||
| + | | ||
| + | Type: interface and name of the interface e.g. X3 (hit enter) | ||
| + | -----------config(C0EAE4009930)# | ||
| + | Type: ip-assignment WAN static | ||
| + | ... hit enter) | ||
| + | ----------(edit-WAN-static[X3])# | ||
| + | Type: ip 60.60.60.60 netmask 255.255.255.0 (hit enter) | ||
| + | Type: commit | ||
| + | | ||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | * config(18C2419C0C60_CCBZF1-BOGOTA-WH)# | ||
| + | * config(18C2419C0C60_CCBZF1-BOGOTA-WH)# | ||
| + | * config(18C2419C0C60_CCBZF1-BOGOTA-WH)# | ||
| + | * config(18C2419C0C60_CCBZF1-BOGOTA-WH)# | ||
| + | |||
| + | |||
| + | The show **service-objects** and **service-groups** are copied into separate **.txt** files. | ||
| + | |||
| + | **Update ubuntu Linux:** | ||
| + | |||
| + | * **sudo -s** | ||
| + | * **apt update** | ||
| + | * **apt upgrade** | ||
| + | * **apt install vim** | ||
| + | |||
| + | Itemaperez@APEREZ: | ||
| + | |||
| + | **Note: _ = space, quantity to replace: four.** | ||
| + | |||
| + | **Format** that the **Sonicwall CLI processes without problems** is: | ||
| + | |||
| + | service-object HTTP | ||
| + | TCP 80 80 | ||
| + | exit | ||
| + | | ||
| + | service-object "HTTP Management" | ||
| + | TCP 80 80 | ||
| + | exit | ||
| + | | ||
| + | service-object HTTPS | ||
| + | TCP 443 443 | ||
| + | exit | ||
| + | |||
| + | |||
| + | service-group "AD Directory Services" | ||
| + | service-object "RPC Services (IANA)" | ||
| + | service-object "RPC Services" | ||
| + | service-object "DCE EndPoint" | ||
| + | service-object NTP | ||
| + | service-object LDAPS | ||
| + | service-object "LDAP (UDP)" | ||
| + | service-object LDAP | ||
| + | service-group "AD NetBios Services" | ||
| + | service-group "Host Name Server" | ||
| + | service-group Kerberos | ||
| + | service-group "DNS (Name Service)" | ||
| + | exit | ||
| + | |||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | {{ : | ||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | {{ : | ||
| ---- | ---- | ||
| Line 39: | Line 115: | ||
| **[[https:// | **[[https:// | ||
| + | |||
| + | **[[https:// | ||
| Line 68: | Line 146: | ||
| **[[https:// | **[[https:// | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | ** | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **VOIP** | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | **Note: | ||
| + | |||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **Guest access services** | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **Bandwidth management** | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | |||
| + | {{pdfjs 46em >: | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | {{pdfjs 46em >: | ||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | |||
| + | **FEC** on an SFP port refers to **Forward Error Correction (FEC)**, which is a technique used in fiber optic and Ethernet networks to enhance data transmission reliability by detecting and correcting errors without the need for retransmission. | ||
| + | |||
| + | **FEC (Forward Error Correction)**: | ||
| + | FEC is a mechanism that adds redundant information to the transmitted data. This redundancy allows the receiving end to detect and correct errors caused by signal degradation or noise during transmission. | ||
| + | |||
| + | Purpose: FEC is essential for high-speed data links (e.g., 10G, 25G, 40G, 100G Ethernet) to improve link quality and performance. | ||
| + | |||
| + | Types: Different FEC modes can be used depending on the standard and speed of the connection (e.g., Reed-Solomon FEC). | ||
| + | |||
| + | |||
| + | * | ||
| + | * | ||
| + | * | ||
| + | * | ||
| + | |||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | |||
| + | **Benefits of FEC on SFP Ports**: | ||
| + | |||
| + | * Error Correction: FEC can correct errors due to signal attenuation or interference. | ||
| + | * Better Link Performance: | ||
| + | * No Retransmissions: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | **Aruba Switch 6400:** | ||
| + | |||
| + | |||
| + | CS-2P-MDFHA-A# | ||
| + | ----------------------------------------------------------------------------- | ||
| + | ArubaOS-CX | ||
| + | (c) Copyright 2017-2024 Hewlett Packard Enterprise Development LP | ||
| + | ----------------------------------------------------------------------------- | ||
| + | Version | ||
| + | Build Date : 2024-04-09 00:34:12 UTC | ||
| + | Build ID : ArubaOS-CX: | ||
| + | Build SHA : ef21093778805e954ec130b0939d34927bb7ba19 | ||
| + | Hot Patches | ||
| + | Active Image : primary | ||
| + | | ||
| + | Service OS Version : FL.01.14.0002 | ||
| + | BIOS Version | ||
| + | |||
| + | CS-2P-MDFHA-A(config)# | ||
| + | |||
| + | **error-control** | ||
| + | |||
| + | CS-2P-MDFHA-A(config-if)# | ||
| + | auto Use the transceiver default | ||
| + | base-r-fec | ||
| + | none Do not use any FEC | ||
| + | rs-fec | ||
| + | |||
| + | ---- | ||
| + | |||
| + | **C9500 Cisco Catalyst** | ||
| + | |||
| + | C9500-N# | ||
| + | Cisco IOS XE Software, **Version 17.12.03** | ||
| + | Cisco IOS Software [Dublin], Catalyst L3 Switch Software (CAT9K_IOSXE), | ||
| + | |||
| + | interface TwentyFiveGigE1/ | ||
| + | | ||
| + | | ||
| + | | ||
| + | mtu 9100 | ||
| + | | ||
| + | | ||
| + | udld port aggressive | ||
| + | fec cl74 | ||
| + | |||
| + | C9500-N(config-if)# | ||
| + | | ||
| + | C9500-N(config-if)# | ||
| + | auto | ||
| + | cl108 Enable clause108 with 25G | ||
| + | cl74 | ||
| + | off Turn FEC off, FEC is mandatory for speeds 50G or higher | ||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | **Global VPN:** | ||
| + | |||
| + | As per your request sharing configuration of Global VPN client. | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | **[[https:// | ||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | ---- | ||
| + | ---- | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | ---- | ||
| + | ---- | ||
sonicwall/basic_configurations_support_site_and_vpn_scenarios.1740353904.txt.gz · Last modified: 2025/02/23 18:38 by aperez
