Skip to content

Commit a467649

Browse files
committed
corrected the comments from review
1 parent f9941a3 commit a467649

File tree

3 files changed

+18
-20
lines changed

3 files changed

+18
-20
lines changed
Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: How to replace a terminal server within Nexus Network Fabric
3-
description: Process of replacing a terminal server within Nexus Network Fabric
2+
title: How to replace a terminal server within Azure Operator Nexus Network Fabric
3+
description: Process of replacing a terminal server within Azure Operator Nexus Network Fabric
44
author: sushantjrao
55
ms.author: sushrao
66
ms.service: azure-operator-nexus
@@ -11,13 +11,13 @@ ms.custom: template-how-to, devx-track-azurecli
1111

1212
# Replacing a terminal server
1313

14-
This guide provides a step-by-step process for replacing a Terminal Server (TS) within nexus network fabric. The procedure includes cleaning up the existing TS, removing the TS, installing a new TS, and configuring the Terminal Server.
14+
This guide provides a step-by-step process for replacing a Terminal Server (TS) within Azure Operator Nexus Network Fabric. The procedure includes cleaning up the existing TS, removing the TS, installing a new TS, and configuring the Terminal Server.
1515

16-
## Pre-Replacement Cleanup (Customer Action)
16+
## Pre-replacement cleanup (Customer action)
1717

1818
Before initiating the Return Merchandise Authorization (RMA) for the existing Terminal Server, ensure a thorough cleanup of the device. This step is crucial if the TS is still accessible.
1919

20-
### Manual Cleanup Tasks:
20+
### Manual cleanup tasks
2121

2222
1. Verify TS Password in KeyVault
2323

@@ -37,32 +37,32 @@ Before initiating the Return Merchandise Authorization (RMA) for the existing Te
3737

3838
Access the /mnt/nvram/ directory to ensure all configuration files, certificates, and the Open Gear file are deleted, leaving no traces of previous configurations.
3939

40-
### Device Removal (Customer Action)
40+
### Device removal (Customer action)
4141

4242
Once the cleanup is complete, proceed with physically removing the existing Terminal Server from the rack.
4343

44-
### Installation of New Device (Customer Action)
44+
### Installation of new device (Customer action)
4545

4646
After the old TS is removed, install the new Terminal Server in the rack. Follow the guidelines provided in the public documentation for [Terminal Server setup](howto-platform-prerequisites.md)
4747

4848
Validate the connectivity of both Net1 and Net2 interfaces to ensure proper network functionality.
4949

5050
Set up the terminal server device with the same password and username as before. This password can be obtained from the customer Network Fabric Controller (NFC) KeyVault secrets. The username can be obtained by doing an ARM GET on the network fabric resource.
5151

52-
### Microsoft Engineering Support
52+
### Microsoft engineering support
5353

5454
After the new Terminal Server is installed and configured, open a support ticket with Microsoft to complete the setup. Microsoft engineers will trigger a lockbox action for *Reprovisioning Terminal Server Device*.
5555

56-
>[!Note:]
56+
>[!Note]
5757
>The user is expected to setup the terminal server with the same username and password as stored in customer NFC key vault.
5858

5959
Wait for the operation to complete.
6060

61-
[!Note:] The lockbox operation will execute the following tasks:
62-
> Configure's essential services, including httpd and dhcpd.
63-
> Set's up the Net3 interface.
64-
> Copies necessary OS, dhcpd configuration, device configurations, and certificate files to the appropriate directories.
65-
> Transfers the configuration files and certificates to the /mnt/nvram/conf directory.
66-
> Restarts the DHCPD service.
67-
> Ensures that configuration files are accessible via the HTTP service for further validation.
61+
>[!Note] The lockbox operation will execute the following tasks:
62+
> - Configure's essential services, including httpd and dhcpd.<br>
63+
> - Set's up the Net3 interface.<br>
64+
> - Copies necessary OS, dhcpd configuration, device configurations, and certificate files to the appropriate directories.<br>
65+
> - Transfers the configuration files and certificates to the /mnt/nvram/conf directory.<br>
66+
> - Restarts the DHCPD service.<br>
67+
> - Ensures that configuration files are accessible via the HTTP service for further validation.<br>
6868

articles/operator-nexus/howto-restrict-serial-port-access-and-set-timeout-on-terminal-server.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
---
2-
title: How to restrict serial port access and set time-out on terminal server
3-
titleSuffix: Azure Operator Nexus
2+
title: "Azure Operator Nexus: How to restrict serial port access and set time-out on terminal server"
43
description: Process of configuring serial port access restrictions and time-out settings on terminal server
54
author: sushantjrao
65
ms.author: sushrao

articles/operator-nexus/howto-upgrade-os-of-terminal-server.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
---
2-
title: How to Upgrade the operating system of a Terminal Server
3-
titleSuffix: Azure Operator Nexus
2+
title: "Azure Operator Nexus: How to upgrade the operating system of a Terminal Server"
43
description: Learn the process for upgrading the operating system of a Terminal Server
54
author: sushantjrao
65
ms.author: sushrao

0 commit comments

Comments
 (0)