XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. semarie
    3. Best
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 12
    • Groups 3

    Posts

    Recent Best Controversial
    • RE: Adding new host to pool fails - Stunnel SSL certiticate verification failure

      Just my 2 cents, but with SSL involved time is important: could you check the date is accurate on the two hosts ?

      having the output of the following commands might help too:

      • stat /etc/stunnel/xapi-stunnel-ca-bundle.pem
      • openssl x509 -in /etc/stunnel/xapi-stunnel-ca-bundle.pem -noout -text
      posted in XCP-ng
      semarieS
      semarie
    • RE: XCP-ng 8.3 updates announcements and testing

      after testing (with net-snmp-utils 5.9.3), I have no problem with snmpv3 and SHA/AES.

      On my testing host, snmpd server (OpenBSD):

      • User: user1
      • auth: AES with password123
      • priv: AES with 321drowssap

      From XCP-ng 8.3, with net-snmp-utils 5.9.3:
      $ snmpbulkwalk -v3 -a SHA -A password123 -l authPriv -x AES -X 321drowssap -u user1 192.168.1.80

      so the net-snmp client itself seems fine with SHA/AES.

      could you share more elements ?

      posted in News
      semarieS
      semarie
    • RE: Build number cloud vs Build number 8.3.0

      Bonjour,

      Apparemment, la valeur vient de la xapi :

      $ xe host-list params=uuid,software-version
      uuid ( RO)                : 9940971b-45f6-4225-aaef-ddb0668e3734
          software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; xapi: 26.1; build_number: 8.3.0; git_id: 3; hostname: localhost; date: 20260430T09:28:41Z; dbv: 0.0.1; xapi_build: 26.1.3; xen: 4.17.6-6; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.793
      
      
      uuid ( RO)                : 5f16a481-103e-4ca8-a0e2-b708d2c26437
          software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; xapi: 26.1; build_number: 8.3.0; git_id: 3; hostname: localhost; date: 20260430T09:28:41Z; dbv: 0.0.1; xapi_build: 26.1.3; xen: 4.17.6-6; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.793
      

      qui prend l'information depuis le fichier /etc/xensource-inventory (sur le host):

      # grep BUILD_NUMBER /etc/xensource-inventory
      BUILD_NUMBER='8.3.0'
      

      Ce fichier est mis à jour par le script de post-config du package rpm xcp-ng-release (voir le script utilisé ici)

      La valeur a été mise à jour la dernière fois en 2023 (voir le changelog pour 8.3.0-13).
      La valeur acutelle est définie dans la variable BUILD_NUMBER rpm variable du package.

      Cela veut dire que le host avec Build number = cloud ne semble pas à jour ? Pouvez-vous vérifier la version installée du package xcp-ng-release, en utilisant la commande rpm -q xcp-ng-release ?

      posted in French (Français)
      semarieS
      semarie