If it might help someone:
pvesm add iscsi <youriD> --portal <PortalHostName> --target <target name> --content none
You can then simply create your volume group:
# Retrieve mounted path
lsblk
# Create physical volume and corresponding volume group
pvcreate /dev/sdb
vgcreate sandisk /dev/sdb
Hello,
I ran into the same problem while trying to add a new iscsi storage to my cluster after upgrading to 6.3.2.
I found the command to add a new storage via CLI:
# Retrieve target
pvesm scan <PortalHostName>
# Add storage
pvesm add iscsi <youriD> --portal <PortalHostName> --target <target...
PS: main trick in the above post are the few lines in the interface file that enable routing of the failover IP:
(...)
pointopoint <GATEWAY FOR YOUR MAIN PUBLIC ADDRESS>
(...)
up ip route add 10.0.0.0/24 via <YOUR FAILOVER IP> dev vmbr1
up sysctl -w net.ipv4.ip_forward=1...
OK, after more research:
- I realized I should have put this in the other Category, sorry for this.
- I found some solution in the German version of the forum
- I finally rather use Opnsensethan pfsense; it's smoother.
... And I solved my problems and if it might help anyone here are the main...
Hello,
I have been using a Proxmox for a while with a very simple network configuration, with only one NIC and one bridge that NAT the traffic to a private VLAN like this: (/etc/network/interfaces of the host)
auto eno1
# internet facing interface
iface eno1 inet static
address...
Just for anyone hitting the same problem...
The answer comes with "Response Policy Zones": the idea is to overwrite public DNS with a local one (typically bind9 does the job) when you are trying to reach a machine that is in your local private VLAN using its public name.
This post explains it...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.