bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Servers & Workflows/Windows/Windows Server/Virtualization/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md

Browse Source
This commit is contained in:
Nicole Rappe
2024-09-02 14:28:36 -06:00
parent b809793f28
commit c81b1c8608
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Servers & Workflows/Windows/Windows Server/Virtualization/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md
View File

@ -65,7 +65,7 @@ You may be booted out of the Remote Desktop session at this time due to how the
| IP ADDRESS | SUBNET MASK | GATEWAY | PRIMARY DNS | SECONDARY DNS | | IP ADDRESS | SUBNET MASK | GATEWAY | PRIMARY DNS | SECONDARY DNS |
| ----------- | ------------- | ----------- | ------------ | ------------- | | ----------- | ------------- | ----------- | ------------ | ------------- |
| 192.168.3.4 | 255.255.255.0 | 192.168.3.1 | 192.168.3.25 | 192.168.3.26 | | 192.168.3.5 | 255.255.255.0 | 192.168.3.1 | 192.168.3.25 | 192.168.3.26 |
### Configure iSCSI Initiator to Connect to TrueNAS Core Server ### Configure iSCSI Initiator to Connect to TrueNAS Core Server
At this point, now that we have verified that the 10GbE NICs can ping their respective iSCSI target server IP addresses, we can add them to the iSCSI Initiator in Server Manager which will allow us to mount the cluster storage for the Hyper-V Failover Cluster. At this point, now that we have verified that the 10GbE NICs can ping their respective iSCSI target server IP addresses, we can add them to the iSCSI Initiator in Server Manager which will allow us to mount the cluster storage for the Hyper-V Failover Cluster.