Merge pull request #16792 from sethmanheim/frsh1-17

Hub freshness

Author: sethmanheim

.openpublishing.redirection.json

@@ -1051,6 +1051,16 @@
       "redirect_url":"/azure-stack/operator/azure-stack-servicing-policy", 
       "redirect_document_id":true 
     },
+    { 
+      "source_path":"azure-stack/operator/azure-stack-train-and-cert.md", 
+      "redirect_url":"/azure-stack/operator/index", 
+      "redirect_document_id":true 
+    },
+    { 
+      "source_path":"azure-stack/operator/azure-stack-powershell-install.md", 
+      "redirect_url":"/azure-stack/operator/powershell-install-az-module", 
+      "redirect_document_id":true 
+    },
     { 
       "source_path":"azure-stack/ruggedized/customer-replaceable-unit/emc-poweredge-tactical-indicators-and-codes.md", 
       "redirect_url":"/azure-stack/ruggedized/customer-replaceable-unit/indicators-and-codes", 

azure-stack/asdk/asdk-post-deploy.md

@@ -2,9 +2,8 @@
 title: Post deployment configurations for the ASDK 
 description: Learn about the recommended configuration changes to make after installing the Azure Stack Development Kit (ASDK).
 author: sethmanheim
-
 ms.topic: article
-ms.date: 12/03/2020
+ms.date: 01/17/2025
 ms.author: sethm
 ms.reviewer: misainat
 ms.lastreviewed: 12/03/2020
@@ -33,8 +32,8 @@ Use API version profiles to specify Azure Stack compatible Az modules.  API vers
 
 You can install the latest Azure Stack PowerShell module with or without internet connectivity to the ASDK host computer.
 
-1.  Validate your prerequisites on your Windows machine. For instructions see [Prerequisites for Windows](../operator/powershell-install-az-module.md#prerequisites-for-windows).
-2. Before installing the required PowerShell version, make sure that you [uninstall any existing Azure PowerShell modules](../operator/powershell-install-az-module.md#3-uninstall-existing-versions-of-the-azure-stack-hub-powershell-modules). 
+1. Validate your prerequisites on your Windows machine. For instructions see [Prerequisites for Windows](../operator/powershell-install-az-module.md#prerequisites-for-windows).
+2. Before installing the required PowerShell version, make sure that you [uninstall any existing Azure PowerShell modules](../operator/powershell-install-az-module.md#uninstall-existing-versions-of-the-azure-stack-hub-powershell-modules).
 
 - **With an internet connection** from the ASDK host computer: Run the following PowerShell script to install these modules on your ASDK installation:
 

azure-stack/mdc/azure-stack-capacity-planning-overview.md

@@ -1,14 +1,12 @@
 ---
-title: Overview - Capacity planning for Azure Stack Hub | Microsoft Docs
-description: Learn about capacity planning for Azure Stack Hub deployments, including compute and storage information.
+title: Overview - Capacity planning for Azure Stack Hub Modular Data Center (MDC) deployments
+description: Learn about capacity planning for Azure Stack Hub MDC deployments, including compute and storage information.
 services: azure-stack
 author: sethmanheim
-manager: femila
 ms.service: azure-stack-hub
 ms.topic: article
-ms.date: 01/10/2020
+ms.date: 01/17/2025
 ms.author: sethm
-ms.reviewer: prchint
 ms.lastreviewed: 01/10/2020
 ---
 

azure-stack/mdc/azure-stack-gpu.md

@@ -1,48 +1,43 @@
 --- 
-title: GPU VMs on Azure Stack | Microsoft Docs 
-description: Reference for GPU computing in Azure Stack. 
+title: GPU VMs on Azure Stack Hub
+description: Reference for GPU computing in Azure Stack Hub. 
 services: azure-stack 
 author: sethmanheim 
-manager: femila 
 ms.service: azure-stack-hub
 ms.topic: article 
-ms.date: 01/02/2020 
+ms.date: 01/17/2025
 ms.author: sethm 
-ms.reviewer: kivenkat 
 ms.lastreviewed: 01/02/2020
 
 # Content note: This topic has been copied/refactored in to commercial.
 
 --- 
 
-# GPU VMs on Azure Stack 
+# GPU VMs on Azure Stack Hub
 
-*Applies to: Azure Stack integrated systems* 
+This article describes how to manage GPU VMs on Azure Stack Hub.
 
-This topic covers how to manage GPU VMs on Azure Stack Hub.
+## Partitioned GPU VM size
 
+The NVv4-series virtual machines are powered by AMD Radeon Instinct MI25 GPUs. With the NVv4-series, Azure Stack Hub introduces virtual machines with partial GPUs. This size can be used for GPU accelerated graphics applications and virtual desktops. NVv4 virtual machines currently support only Windows guest operating system.
 
-## Partitioned GPU VM size 
+| Size | vCPU | Memory: GiB | Temp storage (SSD) GiB | GPU | GPU memory: GiB | Max data disks | Max NICs |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| Standard_NV4as_v4 |4 |14 |88 | 1/8 | 2 | 4 | 2 |
 
-The NVv4-series virtual machines are powered by AMD Radeon Instinct MI25 GPUs. With NVv4-series Azure Stack Hub is introducing virtual machines with partial GPUs. This size can be used for GPU accelerated graphics applications and virtual desktops. NVv4 virtual machines currently support only Windows guest operating system. 
+## Patch and Update, FRU behavior of VMs
 
-| Size | vCPU | Memory: GiB | Temp storage (SSD) GiB | GPU | GPU memory: GiB | Max data disks | Max NICs | 
-| --- | --- | --- | --- | --- | --- | --- | --- |   
-| Standard_NV4as_v4 |4 |14 |88 | 1/8 | 2 | 4 | 2 | 
+GPU VMs undergo downtime during operations such as patch and update (PnU), and hardware replacement (FRU) of Azure Stack Hub. The following table describes the state of the VM as observed during these activities and also the manual action that the user can do to make these VMs available again post these operations.
 
-## Patch and Update, FRU behavior of VMs 
+| Operation | PnU - Express Update | PnU - Full Update, OEM update | FRU |
+| --- | --- | --- | --- |
+| VM state  | Unavailable during and post update without manual start operation | Unavailable during update. Available post update with manual operation | Unavailable during update. Available post update with manual operation|
+| Manual operation | If the VM needs to be made available during the update, if there are available GPU partitions, the VM can be restarted from the portal by clicking the "Restart" button. The VM needs to be restarted post update from the portal using the "Restart" button | VM can't be made available during the update. After the update completes, the VM must be stop-deallocated using the "Stop" button and started backup using the "Start" button | VM can't be made available during the update. After the update completes, the VM needs to be stop-deallocated using the "Stop" button and started backup using the "Start" button.|
 
-GPU VMs will undergo downtime during operations such as patch and update (PnU) as well as hardware replacement (FRU) of Azure Stack Hub. The following table goes over the state of the VM as observed during these activities as well as the manual action that the user can do to make these VMs available again post these operations. 
+## Guest driver installation
 
-| Operation | PnU - Express Update | PnU - Full Update, OEM update | FRU | 
-| --- | --- | --- | --- | 
-| VM state  | Unavailable during and post update without manual start operation | Unavailable during update. Available post update with manual operation | Unavailable during update. Available post update with manual operation| 
-| Manual operation | If the VM needs to be made available during the update, if there are available GPU partitions, the VM can be restarted from the portal by clicking the "Restart" button. VM needs to be restarted post update from the portal using the "Restart" button | VM cannot be made available during the update. Post update completion, VM needs to be stop-deallocated using the "Stop" button and started back up using the "Start" button | VM cannot be made available during the update.Post update completion, VM needs to be stop-deallocated using the "Stop" button and started back up using the "Start" button.| 
+[This](/azure/virtual-machines/windows/n-series-amd-driver-setup) document goes over setting up the AMD guest driver inside the NVv4 GPU-P enabled VM along with steps on how to verify driver installation.
 
-## Guest driver installation 
-
-[This](/azure/virtual-machines/windows/n-series-amd-driver-setup) document goes over setting up the AMD guest driver inside the NVv4 GPU-P enabled VM along with steps on how to verify driver installation. 
-
-## Next steps 
+## Next steps
 
 [Azure Stack VM features](azure-stack-vm-considerations.md)

azure-stack/mdc/network-appendix.md

@@ -2,22 +2,22 @@
 title: Modular Data Center (MDC) networking appendix
 description: Appendices for MDC networking. 
 author: sethmanheim
-ms.author: sethm
 ms.service: azure-stack-hub
+ms.author: sethm
 ms.topic: conceptual
-ms.date: 12/30/2019
+ms.date: 01/17/2025
 ms.lastreviewed: 12/30/2019
 ---
 
 # MDC network appendix
 
-The appendix provides device parameter and identity information for MDC hardware.
+This appendix provides device parameter and identity information for MDC hardware.
 
 ## Technical device parameters
 
 ### Cisco 93360YC-FX2 & Cisco 9348GC-FXP
 
-| **Feature** | **Cisco Nexus 93360YC-FX2** | **Cisco Nexus 9348GC-FXP** |
+| Feature | Cisco Nexus 93360YC-FX2 | Cisco Nexus 9348GC-FXP |
 |---|---|---|
 | Ports | 96 x 1/10/25-Gbps and 12 x 40/100-Gbps QSFP28 ports | 48 x 1-GBASE-T ports, 4 x 1/10/25-Gbps SFP28 ports and 2 x 40/100 QSFP28 ports |
 | Supported speeds | 1/10/25-Gbps on downlinks, 40/100-Gbps on uplinks, Breakout supported ports, 97-108: 4x10/25G | 100-Mbps and 1-Gbps speeds |
@@ -148,13 +148,13 @@ The appendix provides device parameter and identity information for MDC hardware
         NEBS
     :::column-end:::
     :::column span="2":::
-        • GR-1089-Core EMC and Electrical Safety
+        * GR-1089-Core EMC and Electrical Safety
 
-        • Common Bonding Network (CBN)
+        * Common Bonding Network (CBN)
 
-        • National Electrical Code (NEC)
+        * National Electrical Code (NEC)
 
-        • GR-63-Core Physical Protection
+        * GR-63-Core Physical Protection
     :::column-end:::
 :::row-end:::
 
@@ -180,21 +180,21 @@ Specifications:
 - S4112 (DC): -40V/5A, -48V/4.2A, -72V/2.8A 
 
 Maximum operating specifications:
+
 - Operating temperature: 41° to 104° F (5° to 40° C)
 - Operating humidity: 5% to 85% (RH), non- condensing 
 
 Maximum non-operating specifications:
+
 - Storage temperature: -40° to 149°F (-40° C to 65° C) 
 - Storage humidity: 5% to 95% (RH), non-condensing
 
-
 ## Identity
 
 All network devices are designed to work with Terminal Access Controller Access-Control System (TACACS). TACACS provides a centralized identity experience. The TACACS server must be supplied as part of the initial configuration.
 
 Notice once the TACACS server isn't available, the devices will fall back to the local identities listed below. During normal operation, those accounts are disabled.
 
-
 The following user accounts do exit per device:
 
 | Device | Username | Default password |

azure-stack/mdc/network-configuration-lifecycle-management.md

@@ -5,7 +5,7 @@ author: sethmanheim
 ms.author: sethm
 ms.service: azure-stack-hub
 ms.topic: conceptual
-ms.date: 01/02/2020
+ms.date: 01/17/2025
 ms.lastreviewed: 01/02/2020
 ---
 
@@ -17,25 +17,16 @@ This article covers network configuration lifecycle management for Azure Modular
 
 This methodology for updating switch configurations in the field applies to all and any type of configuration updates. Because of many unknown variables outside of our control, like manual configurations applied by customers or by the OEM, this manual process has multiple steps. At this time, there's no guarantee of uptime. Updates should be performed during a maintenance window.
 
-1. Make a backup of the current configuration files for edge1, edge2, tor1, tor2, and BMC switches. Copy these files off the switch.
-
-1. Make a note of the toolkit build number of the existing configuration. All configurations should have this number in the **motd** banner. Do a search for **BUILDNUMBER**.
-
-1. Regenerate the initial configurations by using the same toolkit version from step 2.
-
-1. Load the configurations from step 3 onto their respective switches. The point of this action is to *wash* the config generated by our tools through a switch to get a baseline. This action could be performed by the OEM on separate hardware, like in the OEM's lab, or onsite with the customer.
-
-1. Make a backup of the config file from step 4. Copy it to a remote location.
-
-1. Using the diff tool of your choice, compare the backup of the current config from step 1 to the backup of the baseline configuration from step 5. Make a note or copy of all the differences that should be carried over to the upgraded switch configuration per device.
-
-1. Run the new toolkit that will generate the updated switch configurations.
-
-1. Merge the differences from step 6 into the new switch configurations.
-
-1. Load the new configurations onto the respective switches. Run the post-validation commands provided in the output directory from our tooling.
-
-1. Save the configurations.
+- Make a backup of the current configuration files for edge1, edge2, tor1, tor2, and BMC switches. Copy these files off the switch.
+- Make a note of the toolkit build number of the existing configuration. All configurations should have this number in the **motd** banner. Do a search for **BUILDNUMBER**.
+- Regenerate the initial configurations by using the same toolkit version from step 2.
+- Load the configurations from step 3 onto their respective switches. The point of this action is to *wash* the config generated by our tools through a switch to get a baseline. This action could be performed by the OEM on separate hardware, like in the OEM's lab, or onsite with the customer.
+- Make a backup of the config file from step 4. Copy it to a remote location.
+- Using the diff tool of your choice, compare the backup of the current config from step 1 to the backup of the baseline configuration from step 5. Make a note or copy of all the differences that should be carried over to the upgraded switch configuration per device.
+- Run the new toolkit that will generate the updated switch configurations.
+- Merge the differences from step 6 into the new switch configurations.
+- Load the new configuration onto the respective switches. Run the post-validation commands provided in the output directory from our tooling.
+- Save the configuration.
 
 ## NTP
 
@@ -51,7 +42,6 @@ Azure Stack supports synchronizing time with only one time server (NTP). You can
 ### Update NTP post deployment
 
 1. Connect to the PEP. You don't need to open a support ticket to unlock it.
-
 1. Run the following command to review the current configured NTP server.
 
     ```powershell
@@ -64,8 +54,8 @@ Azure Stack supports synchronizing time with only one time server (NTP). You can
     Set-AzsTimeSource -Timeserver NEWTIMESERVER -resync
     ```
 
->[!NOTE]
->This procedure doesn't update the time server on the physical switches.
+> [!NOTE]
+> This procedure doesn't update the time server on the physical switches.
 
 ## DNS