VMWare Conductor Deployment Guide#1031
Conversation
|
|
||
| <!---### VM Options (Boot Settings) | ||
|
|
||
| 9. Click the **VM Options** tab. |
There was a problem hiding this comment.
Why is this section included and commented out? The numbers don't line up.
|
|
||
|  | ||
|
|
||
| These messages appear due to the instance attempting to connect to the Mist Cloud. The `mist-agent` is enabled by default and will continue to reach out to Mist to connect. In Conductor-managed air-gap networks where there is never any intent to connect to Mist, disabling the Mist Agent has no operational impact, and is actually desirable. Stopping the Mist Agent stops the messages, allowing you to continue the process. |
There was a problem hiding this comment.
This statement is somewhat redundant with the one just a few lines above. Do you need both?
|
|
||
| The message `Device successfully initialized` is displayed after the process completes. The conductor VM will reboot, and then reboot a second time. | ||
|
|
||
| After the second reboot, the login screen appears. Open a browser window and enter the URL https://192.168.100.10. |
There was a problem hiding this comment.
This URL will fail the link checker.
|
|
||
| Conductor deployments currently include VMware ESXi. In this guide the conductor will have a configuration ready for a branch router to onboard and come online, managed by the conductor, forwarding internet traffic for LAN users, and reachable by the conductor over the same WAN interface used for internet breakout. | ||
|
|
||
| Router deployments are currently under development. |
There was a problem hiding this comment.
"are currently under development." Is this what we want here? Why not just remove this sentence and once the other deployment guides get published, the content will exist. You won't have to go back to remove this line.
There was a problem hiding this comment.
In the first line we announce that both Conductor and Router guides are provided, which is the intent. My thought is that as soon as a reader sees just the VMWare conductor guide they are going to want to know why there is not a router guide. And since the vmware router and 130 router guide are well into development, I expect at least one of them to follow shortly.
|
|
||
| The following values are used in this configuration. Substitute your own values where noted. | ||
|
|
||
| | Parameter | Example Value | Description | |
There was a problem hiding this comment.
is it possible to use the docs/_deploy_vmware_conductor_network_design.md file here? The contents are almost identical.
| title: "VMware ESXi Conductor Deployment Guide" | ||
| sidebar_label: Overview | ||
| --- | ||
| import Mermaid from '@theme/Mermaid'; |
There was a problem hiding this comment.
remove this line. mermaid is now natively supported in docusaurus
|
|
||
| The diagram below shows the logical network this guide builds. | ||
|
|
||
| <Mermaid chart={` |
There was a problem hiding this comment.
mermaid is natively supported in docusaurus. Please look at other examples within the docs.
|
|
||
| - **VMware ESXi 7.0 or later** — administrative access to an ESXi host. | ||
| - **SSR 7.1.4-3r2 Universal ISO** — downloaded from [software.128technology.com](https://software.128technology.com/artifactory/list/generic-128t-isos-release-local/) using your Juniper software access credentials. | ||
| - **Juniper software access credentials** — Artifactory username and password for software downloads and token provisioning. |
There was a problem hiding this comment.
this should be the 2nd step
| This guide uses **SSR 7.1.4-3r2** on the conductor. | ||
|
|
||
| :::note | ||
| The router software version cannot be higher than the conductor software version. |
There was a problem hiding this comment.
this would read better if it was positive logic:
The router software version must be lower than or equal to the conductor software version.
2 participants
No description provided.