解决了

AHV部署FortiAuthenticator

  • 2019年3月14日
  • 4回复
  • 1760的浏览量
cmcgee
  • cmcgee
  • “航行者”号
  • 1回复
我试图部署FortiAuthenticator v5.5虚拟机，但在AHV上遇到了问题。

我已经尝试使用Fortinet文件创建虚拟机，但没有说明使用AHV时，按本指南:
https://s3.amazonaws.com/fortinetweb/docs.fortinet.com/v2/attachments/5795878a-1f78-11e9-b6f6-f8bc1258b856/fac-vm-install-guide-43.pdf

我使用的文件如下:
  • KVM - fackvm。qcow2, datadrive.qcow2
  • Vmware -前沿空中管制官。vmdk, datadrive.vmdk
  • 附上我从Fortinet选择的截图
  1. 使用上述文件添加克隆磁盘创建虚拟机
  2. 设置vCPU、Mem、添加的网卡
Fortinet建议我使用vmdk文件，但仍然在截图中得到错误。我是新的AHV，所以任何帮助将感激。


图标

最佳答案MMSW_DE2019年3月15日14:38

\r\n
\r\nForti Authenticator 6.0 KVM image seems to work though. At least it boots to a login prompt.","className":"post__content__best_answer"}">
查看原始
2个附件
\r\n
\r\nI've tried creating the VM using the files from Fortinet but no instructions when using AHV per this guide:
\r\nhttps:\/\/s3.amazonaws.com\/fortinetweb\/docs.fortinet.com\/v2\/attachments\/5795878a-1f78-11e9-b6f6-f8bc1258b856\/fac-vm-install-guide-43.pdf<\/a>
\r\n
\r\nThe files I've used are the following:
\r\n

4回复

ddubuque
Userlevel 3
徽章 + 10
AHV无法读取vdisk，所以可能有驱动程序问题。

询问该公司是否有办法将virtIO驱动程序放入图像中。
如果你需要，你可以把它部署到VMWare工作站或Oracle Virtualbox，并尝试自己安装virtIO驱动程序，(或只是安装Nutanix Guest Tools)然后导出虚拟机(VMDK格式)并从该磁盘克隆。我觉得如果你这么做了，就更有可能让它运行起来。

如果你有一个专用的VMWare环境，你可以尝试对系统使用Xtract，它会确保它放置了必要的驱动程序。你也可以在VMWare工作站上做同样的事情。
David Dubuque || BKD || Nutanix NTC 2019 & 2020 || Nutanix技术咨询委员会成员|| https://darklinkrising.com
\r\n
\r\nAsk the company if they have any way to put virtIO drivers into the image.
\r\nIf you need to, you can go as far as deploying this to VMWare workstation or Oracle Virtualbox and trying to install the virtIO drivers yourself, (Or just install Nutanix Guest Tools) then export the the VM (in VMDK format) and clone from that disk. I think if you do this, you have a higher chance of getting it to run.
\r\n
\r\nIf you have a dedicated VMWare environment, you could attempt to use Xtract against the system and it will make sure it places the necessary drivers. really you could do the same thing I suggested on VMWare workstation as well.","quoteUsername":"ddubuque","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
米
Userlevel 2
徽章 ＋5
我们没有使用FortiAuthenticator，但已经成功地部署了FortiManager和FortiAnalyzer虚拟机到我们的AHV集群。我刚刚尝试了Forti Authenticator 5.5 KVM图像，得到了和您一样的错误。

Forti验证器6.0 KVM图像似乎工作虽然。至少它会引导到登录提示符。
\r\n
\r\nForti Authenticator 6.0 KVM image seems to work though. At least it boots to a login prompt.","quoteUsername":"MMSW_DE","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
cmcgee
谢谢 @ddubuque＆ @MMSW_DE为了得到快速的答复。我是OoO一周，刚刚能够使用3月14日发布的v6。现在我也能够获得一个登录屏幕;希望配置的其余部分能够顺利进行。
@ddubuque<\/user-mention> & @MMSW_DE<\/user-mention> for the quick replies. I was OoO for a week and just now was able to use v6 which was released 3\/14. I too am able to get a login screen now; hoping the rest of the config goes smoothly.","quoteUsername":"cmcgee","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
年代
供参考- FortiGate发布的KB解释了一些FortiStuff在Nutanix / KVM上失败的根本原因。看看这里-https://kb.fortinet.com/kb/documentLink.do?externalID=FD40080

这是由于FortiStuff (Manager, Reporter)无法识别Nutanix提供的SCSI磁盘。诀窍是使用PCI磁盘类型。确保您在Node上手动上传qcow2映像(使用Element Manager而不是Central)，并将其放到正确的存储容器中。PRISM Central将把qcow2映像放到SelfService中，一旦克隆成功，新的设备也会留在SelfService存储桶中!

快速KBFD40080总结如下:
＃＃＃
由于没有存储，并且引导是在只读qcow2映像上进行的，因此在重新引导之后，对VM所做的任何更改都将丢失。

解决方案

这个问题是由于磁盘是通过SCSI总线连接到这个VM的。即使映像部署在KVM管理程序上，问题也完全相同。

解决此问题的方法如下:

1.创建/更新虚拟机，并移除所有磁盘(如果它们已经绑定)
2.将引导盘(2GB)附加为PCI
3.创建一个最小30GB的新数据磁盘，并将其连接到PCI总线上
4.为虚拟机绑定网卡
5.启动虚拟机
＃＃＃

1)附件
https:\/\/kb.fortinet.com\/kb\/documentLink.do?externalID=FD40080<\/a>
\r\n
\r\nThis is due to FortiStuff (Manager, Reporter) failing to recognize SCSI disks presented by Nutanix. The trick is to use PCI disk type. Make sure you upload qcow2 image manually on the Node (using Element Manager rather then Central) and drop it to right storage container. PRISM Central will drop the qcow2 image to SelfService and once cloned new appliance will stay on SelfService storage bucket as well!
\r\n
\r\nquick KB FD40080<\/a> summary below:
\r\n###
\r\nSince there is no storage and the boot is happening from a read-only qcow2 image, then any changes made to the VM would get lost after the reboot.
\r\n
\r\nSolution<\/u>
\r\n
\r\nThe problem is due to the fact that the disks are attached to this VM over SCSI bus. The problem is exactly the same even if the image is deployed on KVM hypervisor.
\r\n
\r\nTo resolve the issue, do the following:
\r\n
\r\n1. Create \/ Update the VM and remove all the disk (if they are already attached)
\r\n2. Attach the boot disk (2GB) as PCI
\r\n3. Create a new data disk of minimum 30GB and attach it over PCI bus as well
\r\n4. Attach a NIC to the VM
\r\n5. Boot the VM
\r\n###
\r\n
\r\n

<\/a><\/p>","quoteUsername":"Sergej","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


Baidu