Goline Logo

Home

    About Us

      Services

      Solutions

      Systems Architecture

      Support

      FAQ

      News

      • Route RPKI validation April 1st, 2022
        RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
      • RIPE – Atlas Anchor February 17th, 2022
        We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
      • MANRS June 20th, 2020
        GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

      VMware ESXi: System logs are stored on non-persistent storage

      Gianni Ricca VMware 22 June 2022

      Problema:
      Dopo uno spegnimento o un riavvio di un ESXi viene visualizzato l'errore "System logs are stored on non-persistent storage"

      Risoluzione da SSH

      Check
      vim-cmd hostsvc/advopt/view ScratchConfig.ConfiguredScratchLocation

      Write
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/busev7-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/busev12-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/busev13-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/busev21-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/esxi01-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/esxi02-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/esxi03-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/esxi04-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/esxi05-log
      vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/UTXT_07_VMware/esxi06-log

       

      Risoluzione da pagina WEB

      Nell'host ESXi in questione aprire il seguente menu:
      System
      Configure
      Advanced System Settings
      e cercare la variabile Syslog.global.logDir

      Default, in locale su /scratch/log
      [] /scratch/log

      Settare lo storage corrispondente all'host su un
      [UTXT_07_VMware] /busev7-log
      [UTXT_07_VMware] /busev12-log
      [UTXT_07_VMware] /busev13-log
      [UTXT_07_VMware] /busev21-log
      [UTXT_07_VMware] /esxi01-log
      [UTXT_07_VMware] /esxi02-log
      [UTXT_07_VMware] /esxi03-log
      [UTXT_07_VMware] /esxi04-log
      [UTXT_07_VMware] /esxi05-log
      [UTXT_07_VMware] /esxi06-log

      0 0 votes
      Article Rating
      Subscribe
      Notify of
      guest
      0 Comments
      Inline Feedbacks
      View all comments
      0
      Would love your thoughts, please comment.x
      ()
      x