You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
15
15
16
-
## Pre-Replacement Cleanup (Customer Action)
16
+
## Pre-replacement cleanup (Customer action)
17
17
18
18
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.
19
19
20
-
### Manual Cleanup Tasks:
20
+
### Manual cleanup tasks
21
21
22
22
1. Verify TS Password in KeyVault
23
23
@@ -37,32 +37,32 @@ Before initiating the Return Merchandise Authorization (RMA) for the existing Te
37
37
38
38
Access the /mnt/nvram/ directory to ensure all configuration files, certificates, and the Open Gear file are deleted, leaving no traces of previous configurations.
39
39
40
-
### Device Removal (Customer Action)
40
+
### Device removal (Customer action)
41
41
42
42
Once the cleanup is complete, proceed with physically removing the existing Terminal Server from the rack.
43
43
44
-
### Installation of New Device (Customer Action)
44
+
### Installation of new device (Customer action)
45
45
46
46
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)
47
47
48
48
Validate the connectivity of both Net1 and Net2 interfaces to ensure proper network functionality.
49
49
50
50
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.
51
51
52
-
### Microsoft Engineering Support
52
+
### Microsoft engineering support
53
53
54
54
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*.
55
55
56
-
>[!Note:]
56
+
>[!Note]
57
57
>The user is expected to setup the terminal server with the same username and password as stored in customer NFC key vault.
58
58
59
59
Wait for the operation to complete.
60
60
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>
0 commit comments