content-update

584F525F · Oct 28, 2024 · 94e565d · 94e565d
1 parent 96e0057
commit 94e565d
Show file tree

Hide file tree

Showing 10 changed files with 310 additions and 242 deletions.
diff --git a/...PE/Aruba_Central_Instant_Cluster/Upgrade_Procedure_Aruba_Central_and_Instant.md b/...PE/Aruba_Central_Instant_Cluster/Upgrade_Procedure_Aruba_Central_and_Instant.md
@@ -59,44 +59,44 @@
 
     ###### URL Format 1
 
-    http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_NAME_VersionNumber
+    [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_NAME_VersionNumber](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_NAME_VersionNumber)
 
-    Below links are examples of the different version names available for firmware version 8.7.1.6_81786
+    **Below links are examples of the different version names available for firmware version 8.7.1.6_81786**
 
-    Ursa http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Ursa_8.7.1.6_81786
+    Ursa [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Ursa_8.7.1.6_81786](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Ursa_8.7.1.6_81786)
 
-    Draco http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Draco_8.7.1.6_81786
+    Draco [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Draco_8.7.1.6_81786](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Draco_8.7.1.6_81786)
 
-    Hercules http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Hercules_8.7.1.6_81786
+    Hercules [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Hercules_8.7.1.6_81786](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Hercules_8.7.1.6_81786)
 
-    Gemini http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Gemini_8.7.1.6_81786
+    Gemini [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Gemini_8.7.1.6_81786](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Gemini_8.7.1.6_81786)
 
-    Lupus http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Lupus_8.7.1.6_81786
+    Lupus [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Lupus_8.7.1.6_81786](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Lupus_8.7.1.6_81786)
 
-    Scorpio http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Scorpio_8.7.1.6_81786
+    Scorpio [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Scorpio_8.7.1.6_81786](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Scorpio_8.7.1.6_81786)
 
-    Vela http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Vela_8.7.1.6_81786
+    Vela [http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Vela_8.7.1.6_81786](http://d2vxf1j0rhr3p0.cloudfront.net/fwfiles/ArubaInstant_Vela_8.7.1.6_81786)
 
 
     ###### URL Format 2
 
-    http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_NAME_VersionNumber
+    [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_NAME_VersionNumber](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_NAME_VersionNumber)
 
-    Below links are examples of the different version names available for firmware version 8.10.0.1_84079
+    **Below links are examples of the different version names available for firmware version 8.10.0.1_84079**
 
-    Ursa http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Ursa_8.10.0.1_84079
+    Ursa [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Ursa_8.10.0.1_84079](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Ursa_8.10.0.1_84079)
 
-    Draco http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Draco_8.10.0.1_84079
+    Draco [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Draco_8.10.0.1_84079](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Draco_8.10.0.1_84079)
 
-    Hercules http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Hercules_8.10.0.1_84079
+    Hercules [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Hercules_8.10.0.1_84079](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Hercules_8.10.0.1_84079)
 
-    Gemini http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Gemini_8.10.0.1_84079
+    Gemini [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Gemini_8.10.0.1_84079](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Gemini_8.10.0.1_84079)
 
-    Lupus http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Lupus_8.10.0.1_84079
+    Lupus [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Lupus_8.10.0.1_84079](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Lupus_8.10.0.1_84079)
 
-    Scorpio http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Scorpio_8.10.0.1_84079
+    Scorpio [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Scorpio_8.10.0.1_84079](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Scorpio_8.10.0.1_84079)
 
-    Vela http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Vela_8.10.0.1_84079
+    Vela [http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Vela_8.10.0.1_84079](http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Vela_8.10.0.1_84079)
 
 
     ##### Test the URL
@@ -108,13 +108,13 @@
 
     #### Step 4: The upgrade
 
-    3- Login to the Virtual controller Web GUI
+    1. Login to the Virtual controller Web GUI
 
-    4- Go to Maintenance > Firmware
+    2. Go to Maintenance > Firmware
 
-    5- From the manual option, enter the respective URL for the models in the tab. using the URL that was generated in point number 1.
+    3. From the manual option, enter the respective URL for the models in the tab. using the URL that was generated in point number 1.
 
-    6- Make sure to enable the reboot AP option > Click on the upgrade now
+    4. Make sure to enable the reboot AP option > Click on the upgrade now
 
     - The loading page should change to Downloading then Upgrading.
     - You will need to wait for an Upgrade Successful message.
@@ -129,16 +129,14 @@
 
 !!! bug ""
 
-    **If you're having an issue and the upgrade is failing you can do a few things to check.**
+    #### If you're having an issue and the upgrade is failing you can do a few things to check.
 
     - Log in to FTP Server with the user you created and make sure you are able to gain access and view configuration and files.
     - If you're trying to upgrade multiple Images through the CLI command ```upgrade-image```
             
         Abort this as this only supports single image clusters.
 
-    ---
-
-    **If you try to upgrade through the web with a link [ftp, TFTP, http] and receive an error similar to the one below**
+    #### If you try to upgrade through the web with a link [ftp, TFTP, http] and receive an error similar to the one below
 
     ![aruba_upgrade_troubleshooting_00](/Knowledge_Base/images/aruba_upgrade_troubleshooting_00.png)
 
@@ -148,9 +146,7 @@
 
     ![aruba_upgrade_troubleshooting_0](/Knowledge_Base/images/aruba_upgrade_troubleshooting_0.png)
 
-    ---
-
-    **Is the Virtual Controller having problems obtaining the image?**
+    #### Is the Virtual Controller having problems obtaining the image?
 
     that's where you can do something similar to running [replace <url> with the URL you're using for the firmware upgrade]
 
@@ -173,7 +169,7 @@
 
     ![aruba_upgrade_troubleshooting_2](/Knowledge_Base/images/aruba_upgrade_troubleshooting_2.png)
 
-    **Other commands**
+    #### Other commands
 
     ```bash
     show log provision

diff --git a/docs/Knowledge_Base/Network/Vendor/Juniper/Juniper_Configuration_Generator.md b/docs/Knowledge_Base/Network/Vendor/Juniper/Juniper_Configuration_Generator.md
@@ -4,7 +4,9 @@
 
     #### Official Tools
 
-    Make sure to check the **`About this tool section'** ![alt text](/Knowledge_Base/images/Juniper_Configuration_Generator.png) as it might state each Tool's limitations.
+    Make sure to check the **`About this tool section'** as it might state each Tool's limitations.
+
+    ![alt text](/Knowledge_Base/images/Juniper_Configuration_Generator.png)
 
     - [SRX HA Configuration Generator](https://support.juniper.net/support/tools/srxha/#)
     - [SRX & J Series Site-to-Site VPN Configuration Generator](https://support.juniper.net/support/tools/vpnconfig/)

diff --git a/..._Base/Network/Vendor/Ruckus/Access_Points/AP_Firmware_Recovery_CLI_Ruckus_SZ.md b/..._Base/Network/Vendor/Ruckus/Access_Points/AP_Firmware_Recovery_CLI_Ruckus_SZ.md
@@ -14,7 +14,7 @@ To recover an Access Point whereby the management interface can no longer be acc
 
     Before you can tell the AP's to manually downgrade there firmware you must first create a file called fwcntrl.rcks and use your favourite text editor to modify the contents.
 
-    The contents must contain the following:
+    The contents must contain the following
 
     ```bash
     [rcks_fw.main]

diff --git a/...nowledge_Base/Network/Vendor/Ruckus/Access_Points/AP_TX_Power_EIRP_Ruckus_SZ.md b/...nowledge_Base/Network/Vendor/Ruckus/Access_Points/AP_TX_Power_EIRP_Ruckus_SZ.md
@@ -1,33 +1,34 @@
 !!! info ""
 
-    EIRP (dBm) = Conducted Power (dBm) + Antenna Gain (dBi) – Cable loss (dB)
+    **EIRP (dBm)** = Conducted Power (dBm) + Antenna Gain (dBi) – Cable loss (dB)
 
     Max EIRP allowed by FCC on Access Points
 
-    2.4 GHz Channels 1 – 11 (36 dBm)
-    5 GHz U-NII-1 channels 36 – 48 (36 dBm)
-    5 GHz U-NII-2A channels 52 – 64 (30 dBm)
-    5 GHz U-NII-2C channels 100 – 144 (30 dBm)
-    5 GHz U-NII-3 channels 149 – 165 (36 dBm)
+    - 2.4 GHz Channels 1 – 11 (36 dBm)
+    - 5 GHz U-NII-1 channels 36 – 48 (36 dBm)
+    - 5 GHz U-NII-2A channels 52 – 64 (30 dBm)
+    - 5 GHz U-NII-2C channels 100 – 144 (30 dBm)
+    - 5 GHz U-NII-3 channels 149 – 165 (36 dBm)
+
+    **Antenna Gain**
 
-    Antenna Gain
     This is where Ruckus shines with the Beamflex gain. Beamflex adaptive antenna will get you approx. 3 dBi gain per 2 radio chains on most models. This will be added to the conductive power you set on the management interface and will make sure the EIRP is less than the FCC limit.
 
 !!! info ""
 
     #### How to find the conducted power of your Ruckus Unleashed AP?
 
-    run the below command on WAP
+    Run the below commands on WAP
 
     ```bash
     ruckus> en
     ruckus# debug
-    ruckus(debug)# rksap_cli -A -s “iwconfig”
+    ruckus(debug)# rksap_cli -A -s "iwconfig"
     ```
 
     Below is a H510 AP configured with maximum Tx power. It shows 2.4 GHz using Tx power as 16 dBm and 5 GHz at 19 dBm.
 
-    ![alt text](/Knowledge_Base/images//Knowledge_Base/images/Ruckus_WAP_image.png)
+    ![alt text](/Knowledge_Base/images/Ruckus_WAP_image.png)
 
     R710 shows 2.4 GHz at 22 dBm and 5 GHz at 20 dBm.
 
@@ -101,15 +102,15 @@
 
 !!! info ""
 
-    #### Actual WAP Power vs datasheet
+    #### Actual WAP Power vs Datasheet
 
-    I was working a case about a year ago channelizaing over 100 WAPs at this single location, i had to set the power on each WAP seperatly based on our ekahau WiFi Survey report, i am not one to do such task from GUI, therefor I scripted the whole thing to run on the SmartZone.
+    I was working a case about a year ago Channelizing over 100 WAPs at this single location, i had to set the power on each WAP separately based on our ekahau WiFi Survey report, i am not one to do such task from GUI, therefor I scripted the whole thing to run on the SmartZone.
 
     Anyway, I found that after settings the power on all WAPs and monitoring the clients, nothing was making sense. I looked into the datasheet for each WAP model we had at this location and tried checking the calculations I made based on the information I was fed by our CWNE Network Architect and still something didn't make sense.
 
-    I reached out to Ruckus support asking on how I can check the actual Tx Power on the WAP and that's when he hopped on and gave me access to the support shell to get the infomation I need.
+    I reached out to Ruckus support asking on how I can check the actual Tx Power on the WAP and that's when he hopped on and gave me access to the support shell to get the information I need.
 
-    This is when I found out that the actual data provided by Ruckus on theor datasheets, doesnt really match what you get from the Access Point, I was kind of shocked. Below are some of the values I obtained while doing my checks on the WAP, you can see what power level you get based on the select settings i had at the time.
+    This is when I found out that the actual data provided by Ruckus on the Datasheets, doesn't really match what you get from the Access Point, I was kind of shocked. Below are some of the values I obtained while doing my checks on the WAP, you can see what power level you get based on the select settings i had at the time.
 
     ##### H550
 
@@ -124,7 +125,7 @@
     ![alt text](/Knowledge_Base/images/Ruckus_WAP_image-4.png)
 
     ##### R350
-    
+
     ```bash
     2.4GHz Max 20  2 gain
     5GHz Max 20 gain 3
@@ -141,14 +142,14 @@
     ![alt text](/Knowledge_Base/images/Ruckus_WAP_image-5.png)
 
     ##### T350c
-    
+
     ```bash
     2.4Ghz 23dBm
     5Ghz 22dBm
     ```
 
     ##### T310c
-    
+
     ```bash
     2.4Ghz 20dBm
     5Ghz 22dBm 
@@ -197,4 +198,4 @@
 
     Looks for
     2.4GHZ TX POWER TARGET > MCS0 HT20 > Pout dBm Value that's the Max
-    5GHZ TX POWER TARGET > MCS0 VHT20 > Pout dBm Value that's the Max
+    5GHZ TX POWER TARGET > MCS0 VHT20 > Pout dBm Value that's the Max
diff --git a/..._Points/CLI_General_Commands_Ruckus_SZ.md → .../Ruckus/Access_Points/Ruckus_AP_CLI_SZ.md b/..._Points/CLI_General_Commands_Ruckus_SZ.md → .../Ruckus/Access_Points/Ruckus_AP_CLI_SZ.md
diff --git a/...ts/Ruckus_Access_Point_compatibility_-_ZoneDirector_ZD_SmartZone_SZ_Firmware.md b/...ts/Ruckus_Access_Point_compatibility_-_ZoneDirector_ZD_SmartZone_SZ_Firmware.md
@@ -1,6 +1,6 @@
 !!! info ""
 
-    ** AP Firmware Compatability to Join ZD **
+    ** AP Firmware compatibility to Join ZD **
 
     ZD firmware version 9.13.x or lower > AP with Standalone Firmware 100.x is supported.
     ZD firmware version 10.x or later   > AP with Standalone Firmware 104.x or above is supported.
@@ -11,26 +11,30 @@
     - APs running SZ 5.x and above
     - APs running Unleashed 200.x and newer
         
-    AP utilizes LWAPP to communicate with the controller
+    AP utilizes `LWAPP` to communicate with the controller
 
     - APs running ZD 9.x
     - APs running solo 104.x or prior
 
     ++++++++++
 
-    In SmartZone under Cluster Information > Only first time config you can enable the AP Conversion (This enables LWAPP) > if not enabled then, you can re-enable it from GUI, you have to go to CLI
-    You can enable this option or disable it through CLI when onboarding APs depending on compatabiliy
+    In SmartZone under `Cluster Information` > Only first time config you can enable the AP Conversion (This enables `LWAPP`) > if not enabled then, you can re-enable it from GUI, you have to go to CLI
+    You can enable this option or disable it through CLI when onboarding APs depending on compatibility
 
+    ```bash
     >enable
     >Show run lwapp2scg
+    ```
+
     check the policy if deny all or allow all
 
+    ```bash
     #config
     #lwapp2scg
     #policy accept-all          >  choose this depending on what you need 
     #policy deny-all            >  choose this depending on what you need
     #end
-
+    ```
 
     It is similar for vSZ/SZ, so for SZ/vSZ lower than 3.6.x, the AP standalone firmware 100.x is supported and for the firmware version higher than 5.x, the AP firmware version 104.x or higher is supported.
 
@@ -40,19 +44,15 @@
     will have issue 5.1 or 5.2 SZ
     So you need to have only IPv4
 
-    Latest APs should be on 114 but older try either 104 or 110 solo fimrware version
+    Latest APs should be on 114 but older try either 104 or 110 solo Firmware version
 
-    on AP having issue with run
-    get syslog log
+    on AP having issue with run `get syslog log`
 
+    ```bash
     #set Controller IP
     set scg ip
-    ping controller also if needed to check if you can reach it out
-
-
-
-    ------------------------------
+    ```
 
+    ping controller also if needed to check if you can reach it out
 
     Controller upgrade then you need to upgrade the APs
-
diff --git a/..._Points/Ruckus_ICX_Brocade_CLI_Dot1x_Ruckus_MAC_Authentication_Security_Port.md b/..._Points/Ruckus_ICX_Brocade_CLI_Dot1x_Ruckus_MAC_Authentication_Security_Port.md
@@ -1,6 +1,6 @@
 !!! info ""
 
-    http://docs.ruckuswireless.com/fastiron/08.0.60/fastiron-08060-securityguide/GUID-173BF914-D248-4CAE-9D80-B036E8EC54E6.htmlhttp://docs.ruckuswireless.com/fastiron/08.0.60/fastiron-08060-securityguide/GUID-173BF914-D248-4CAE-9D80-B036E8EC54E6.html
+    [fastiron-08060-securityguide](http://docs.ruckuswireless.com/fastiron/08.0.60/fastiron-08060-securityguide/GUID-173BF914-D248-4CAE-9D80-B036E8EC54E6.htmlhttp://docs.ruckuswireless.com/fastiron/08.0.60/fastiron-08060-securityguide/GUID-173BF914-D248-4CAE-9D80-B036E8EC54E6.html)
 
     ```bash
     conf t