{"id":368,"date":"2020-11-03T09:36:52","date_gmt":"2020-11-03T08:36:52","guid":{"rendered":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/?p=368"},"modified":"2021-02-08T14:24:27","modified_gmt":"2021-02-08T13:24:27","slug":"fortianalyzer-deploiement-de-limage-kvm-sur-proxmox","status":"publish","type":"post","link":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/fortianalyzer-deploiement-de-limage-kvm-sur-proxmox\/","title":{"rendered":"fortianalyzer &#8211; deploiement de l&rsquo;image kvm sur proxmox"},"content":{"rendered":"<p>FortiAnalyzer assure un traitement analytique des donn\u00e9es de s\u00e9curit\u00e9 pour am\u00e9liorer la d\u00e9tection des intrusions et des malware.  Il permet de collecter, d&rsquo;analyser et de corr\u00e9ler les donn\u00e9es de logs de votre r\u00e9seau distribu\u00e9 de firewalls. Pour cela, FortiAnalyzer existe sous 2 formats ; boitier physique ou VM. Dans notre cas, nous allons d\u00e9tailler l&rsquo;installation du type VM sur un h\u00f4te Proxmox.<\/p>\n<p><!--more--><\/p>\n<h1>Installation<\/h1>\n<p>Cr\u00e9er une VM type KVM avec les pr\u00e9-requis suivant depuis votre interface Proxmox avec les param\u00e8tres suivants. Il faut activer le disque local du votre h\u00f4te Proxmox afin de pouvoir remplacer le disque cr\u00e9\u00e9 par celui de Fortinet.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-content\/uploads\/sites\/2\/2020\/11\/2020-11-03-11.31.19.png\" alt=\"2020-11-03 11.31.19\" \/><\/p>\n<p>R\u00e9cup\u00e9rer la VM au format KVM depuis le support Fortinet <a href=\"\">https:\/\/support.fortinet.com <\/a> et envoy\u00e9 le fichier t\u00e9l\u00e9charg\u00e9 sur le noeud o\u00f9 vous avez pr\u00e9c\u00e9demment install\u00e9 la VM.<\/p>\n<pre><code>proxmox # unzip \/root\/FAZ_VM64_KVM-v6-build2201-FORTINET.out.kvm.zip\nproxmox # qemu-img convert \/root\/faz.qcow2 \/var\/lib\/vz\/images\/100\/vm-100-disk-0.raw\n<\/code><\/pre>\n<p>Lancer la VM et connectez-vous via la console :<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-content\/uploads\/sites\/2\/2020\/11\/faz-boot-avant-repair-disk.png\" alt=\"faz-boot-avant-repair-disk\" \/><\/p>\n<pre><code>login : admin \npassword : appuyer sur entrer\n<\/code><\/pre>\n<p>Activer et configurer le port1 avec une @IP<\/p>\n<pre><code>FAZVM64-KVM # config system interface\n(interface) # edit port1\n(port1) # set mode static\n(port1) # set ip 192.168.1.10 255.255.255.0\n(port1) # set allowaccess http https ssh ping\n(port1) # end\n<\/code><\/pre>\n<p>Lancer la v\u00e9rification du disque<\/p>\n<pre><code>FAZVM64-KVM # diagnose system fsck harddisk\n<\/code><\/pre>\n<p><img decoding=\"async\" src=\"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-content\/uploads\/sites\/2\/2020\/11\/faz-boot-repair-disk.png\" alt=\"faz-boot-repair-disk\" \/><\/p>\n<p><strong>Si vous avez ajout\u00e9 le second disque dans un second temps<\/strong>, vous avez du rencontrer une erreur de montage \/var sur le prompt. Dans ce cas connectez-vous \u00e0 la console et saisir la commande suivante :<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-content\/uploads\/sites\/2\/2020\/11\/faz-error-var.png\" alt=\"faz-error-var\" \/><\/p>\n<pre><code>FAZVM64-KVM # execute lvm inf\n<\/code><\/pre>\n<p>La VM va rebooter. Apr\u00e8s reboot, connectez-vous de nouveau \u00e0 la console et v\u00e9rifier la pr\u00e9sence du disk1 :<\/p>\n<pre><code>FAZVM64-KVM # execute lvm inf\nLVM Status: OK\nLVM Raw Size: 500GB\nFile System: ext4 491GB\n\nDisk1 :         Used      500GB\nDisk2 :  Unavailable        0GB\nDisk3 :  Unavailable        0GB\nDisk4 :  Unavailable        0GB\nDisk5 :  Unavailable        0GB\nDisk6 :  Unavailable        0GB\nDisk7 :  Unavailable        0GB\nDisk8 :  Unavailable        0GB\nDisk9 :  Unavailable        0GB\nDisk10:  Unavailable        0GB\nDisk11:  Unavailable        0GB\nDisk12:  Unavailable        0GB\nDisk13:  Unavailable        0GB\nDisk14:  Unavailable        0GB\nDisk15:  Unavailable        0GB\n<\/code><\/pre>\n<p>Enfin il ne vous reste plus qu&rsquo;\u00e0 importer la licence. Il faut au pr\u00e9alable avoir g\u00e9n\u00e9r\u00e9 celle-ci sur le site du support Fortinet afin de l&rsquo;importer depuis un navigateur (ex : http:\/\/192.168.1.10).<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-content\/uploads\/sites\/2\/2020\/11\/2020-11-03-11.03.17.png\" alt=\"2020-11-03 11.03.17\" \/><\/p>\n<h1>R\u00e9f\u00e9rences<\/h1>\n<p><a href=\"\">https:\/\/docs.fortinet.com\/document\/fortianalyzer\/6.0.0\/fortianalyzer-vm-on-kvm\/553674\/configuring-hardware-settings<\/a><br \/>\n<a href=\"\">https:\/\/kb.fortinet.com\/kb\/documentLink.do?externalID=FD40848<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>FortiAnalyzer assure un traitement analytique des donn\u00e9es de s\u00e9curit\u00e9 pour am\u00e9liorer la d\u00e9tection des intrusions et des malware. Il permet de collecter, d&rsquo;analyser et de corr\u00e9ler les donn\u00e9es de logs de votre r\u00e9seau distribu\u00e9 de firewalls. Pour cela, FortiAnalyzer existe sous 2 formats ; boitier physique ou VM. Dans notre cas, nous allons d\u00e9tailler l&rsquo;installation [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[11,37,13],"tags":[42,40,39,41],"class_list":["post-368","post","type-post","status-publish","format-standard","hentry","category-linux","category-networking","category-proxmox","tag-firewall","tag-fortianalyzer","tag-fortinet","tag-logs"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/paBEVZ-5W","jetpack_likes_enabled":false,"_links":{"self":[{"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/posts\/368","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/comments?post=368"}],"version-history":[{"count":7,"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/posts\/368\/revisions"}],"predecessor-version":[{"id":375,"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/posts\/368\/revisions\/375"}],"wp:attachment":[{"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/media?parent=368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/categories?post=368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/homepages.lcc-toulouse.fr\/colombet\/wp-json\/wp\/v2\/tags?post=368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}