Domande frequenti sul servizio Cloudcenter Manager-4.8.2 e sulla posizione dei file modificata

Opzioni per il download

  • PDF     (154.3 KB)
    Visualizza con Adobe Reader su diversi dispositivi
  • ePub     (88.8 KB)
    Visualizza in diverse app su iPhone, iPad, Android, Sony Reader o Windows Phone
  • Mobi (Kindle)     (82.3 KB)
    Visualizza su dispositivo Kindle o tramite app Kindle su più dispositivi
Aggiornato:28 marzo 2018
ID documento:212929

Linguaggio senza pregiudizi

La documentazione per questo prodotto è stata redatta cercando di utilizzare un linguaggio senza pregiudizi. Ai fini di questa documentazione, per linguaggio senza di pregiudizi si intende un linguaggio che non implica discriminazioni basate su età, disabilità, genere, identità razziale, identità etnica, orientamento sessuale, status socioeconomico e intersezionalità. Le eventuali eccezioni possono dipendere dal linguaggio codificato nelle interfacce utente del software del prodotto, dal linguaggio utilizzato nella documentazione RFP o dal linguaggio utilizzato in prodotti di terze parti a cui si fa riferimento. Scopri di più sul modo in cui Cisco utilizza il linguaggio inclusivo.

Informazioni su questa traduzione

Cisco ha tradotto questo documento utilizzando una combinazione di tecnologie automatiche e umane per offrire ai nostri utenti in tutto il mondo contenuti di supporto nella propria lingua. Si noti che anche la migliore traduzione automatica non sarà mai accurata come quella fornita da un traduttore professionista. Cisco Systems, Inc. non si assume alcuna responsabilità per l’accuratezza di queste traduzioni e consiglia di consultare sempre il documento originale in inglese (disponibile al link fornito).

    Introduzione

    Questo documento descrive il percorso dei file che sono stati modificati.

    Come verificare se il server di gestione funziona correttamente?

      

    1. Accedere a CloudCenter Manager con SSH.
       
    2. Verificare che il server di gestione venga eseguito utilizzando il comando.
    [root@ip-172-31-78-238 sysconfig]# systemctl  status mgmtserver.service
    ● mgmtserver.service - Management Server
       Loaded: loaded (/etc/systemd/system/mgmtserver.service; enabled; vendor preset: disabled)
       Active: inactive (dead) since Fri 2017-11-10 16:55:31 UTC; 15s ago
      Process: 2732 ExecStart=/bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/mgmtserver.war (code=killed, signal=TERM)
     Main PID: 2732 (code=killed, signal=TERM)

    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: / ____| |               | |/ ____|         | |            |  \/  |
    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: | |    | | ___  _   _  __| | |     ___ _ __ | |_ ___ _ __  | \  / | __ _ _ __   __ _  __ _  ___ _ __
    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: | |    | |/ _ \| | | |/ _` | |    / _ \ '_ \| __/ _ \ '__| | |\/| |/ _` | '_ \ / _` |/ _` |/ _ \ '__|
    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: | |____| | (_) | |_| | (_| | |___|  __/ | | | ||  __/ |    | |  | | (_| | | | | (_| | (_| |  __/ |
    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: \_____|_|\___/ \__,_|\__,_|\_____\___|_| |_|\__\___|_|    |_|  |_|\__,_|_| |_|\__,_|\__, |\___|_|
    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: __/ |
    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: |___/
    Nov 10 16:54:48 ip-172-31-78-238.ec2.internal sh[2732]: packager : (v4.8.2-SNAPSHOT), Powered by Spring Boot : 1.5.8.RELEASE
    Nov 10 16:55:31 ip-172-31-78-238.ec2.internal systemd[1]: Stopping Management Server...
    Nov 10 16:55:31 ip-172-31-78-238.ec2.internal systemd[1]: Stopped Management Server.
    [root@ip-172-31-78-238 sysconfig]#

    Come riavviare il server di gestione?

    Tutti i servizi sono stati modificati in systemctl, pertanto è necessario eseguire il comando systemctl per riavviare il server di gestione.

    [root@ip-172-31-78-238 sysconfig]# systemctl  restart mgmtserver.service
    [root@ip-172-31-78-238 sysconfig]#

    ----------------------------------

    [root@ip-172-31-78-238 sysconfig]# systemctl status mgmtserver
    ● mgmtserver.service - Management Server
       Loaded: loaded (/etc/systemd/system/mgmtserver.service; enabled; vendor preset: disabled)
       Active: active (running) since Fri 2017-11-10 15:19:20 UTC; 1h 27min ago
     Main PID: 601 (sh)
       CGroup: /system.slice/mgmtserver.service
               ├─601 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/mgmtserver.war
               ├─611 /bin/bash /usr/local/cliqr/apps/mgmtserver.war
               └─667 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xms2048m -Xmx4096m -Djava.security.egd=file:/dev/./urandom -jar /usr/local/cliqr/apps/mgmtserver.war

    Nov 10 15:19:20 ip-172-31-78-238.ec2.internal sh[601]: logger: Executing configuration set by user
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: _____ _                 _  _____           _              __  __
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: / ____| |               | |/ ____|         | |            |  \/  |
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: | |    | | ___  _   _  __| | |     ___ _ __ | |_ ___ _ __  | \  / | __ _ _ __   __ _  __ _  ___ _ __
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: | |    | |/ _ \| | | |/ _` | |    / _ \ '_ \| __/ _ \ '__| | |\/| |/ _` | '_ \ / _` |/ _` |/ _ \ '__|
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: | |____| | (_) | |_| | (_| | |___|  __/ | | | ||  __/ |    | |  | | (_| | | | | (_| | (_| |  __/ |
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: \_____|_|\___/ \__,_|\__,_|\_____\___|_| |_|\__\___|_|    |_|  |_|\__,_|_| |_|\__,_|\__, |\___|_|
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: __/ |
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: |___/
    Nov 10 15:19:53 ip-172-31-78-238.ec2.internal sh[601]: packager : (v4.8.2-SNAPSHOT), Powered by Spring Boot : 1.5.8.RELEASE
    [root@ip-172-31-78-238 sysconfig]#

    Come riavviare hazelcast-server?

    [root@ip-172-31-78-238 sysconfig]# systemctl restart hazelcast-server
    [root@ip-172-31-78-238 sysconfig]#
    [root@ip-172-31-78-238 sysconfig]# systemctl status  hazelcast-server
    ● hazelcast-server.service - Hazelcast Server
       Loaded: loaded (/etc/systemd/system/hazelcast-server.service; enabled; vendor preset: disabled)
       Active: active (running) since Fri 2017-11-10 16:54:37 UTC; 14s ago
     Main PID: 2731 (sh)
       CGroup: /system.slice/hazelcast-server.service
               ├─2731 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/hazelcast-server.jar
               ├─2735 /bin/bash /usr/local/cliqr/apps/hazelcast-server.jar
               └─2760 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xms256m -Xmx256m -Djava.security.egd=file:/dev/./urandom -jar /usr/local/cliqr/apps/hazelcast-server.jar

    Nov 10 16:54:37 ip-172-31-78-238.ec2.internal systemd[1]: Started Hazelcast Server.
    Nov 10 16:54:37 ip-172-31-78-238.ec2.internal systemd[1]: Starting Hazelcast Server...
    Nov 10 16:54:39 ip-172-31-78-238.ec2.internal sh[2731]: 16:54:39.116 [main] INFO  com.cisco.cloudcenter.hazelcast.HazelcastServer - Starting Hazelcast Server..
    Nov 10 16:54:43 ip-172-31-78-238.ec2.internal sh[2731]: _    _               _               _      _____                 _
    Nov 10 16:54:43 ip-172-31-78-238.ec2.internal sh[2731]: | |  | |             | |             | |    / ____|               (_)
    Nov 10 16:54:43 ip-172-31-78-238.ec2.internal sh[2731]: | |__| | __ _ _______| | ___ __ _ ___| |_  | (___   ___ _ ____   ___  ___ ___
    Nov 10 16:54:43 ip-172-31-78-238.ec2.internal sh[2731]: |  __  |/ _` |_  / _ \ |/ __/ _` / __| __|  \___ \ / _ \ '__\ \ / / |/ __/ _ \
    Nov 10 16:54:43 ip-172-31-78-238.ec2.internal sh[2731]: | |  | | (_| |/ /  __/ | (_| (_| \__ \ |_   ____) |  __/ |   \ V /| | (_|  __/
    Nov 10 16:54:43 ip-172-31-78-238.ec2.internal sh[2731]: |_|  |_|\__,_/___\___|_|\___\__,_|___/\__| |_____/ \___|_|    \_/ |_|\___\___|
    Nov 10 16:54:43 ip-172-31-78-238.ec2.internal sh[2731]: CliQr Hazelcast Server : (v4.8.2-SNAPSHOT), Powered by Spring Boot : 1.5.8.RELEASE
    [root@ip-172-31-78-238 sysconfig]#

    ---------------------------------
    [root@ip-172-31-78-238 sysconfig]# ps -ef | grep hazelcast
    cliqrus+  2731     1  0 16:54 ?        00:00:00 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/hazelcast-server.jar
    cliqrus+  2735  2731  0 16:54 ?        00:00:00 /bin/bash /usr/local/cliqr/apps/hazelcast-server.jar
    cliqrus+  2760  2735  6 16:54 ?        00:00:14 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xms256m -Xmx256m -Djava.security.egd=file:/dev/./urandom -jar /usr/local/cliqr/apps/hazelcast-server.jar
    root      3024  1854  0 16:58 pts/0    00:00:00 grep --color=auto hazelcast
    [root@ip-172-31-78-238 sysconfig]#

    Come riavviare il server di configurazione in CCM?

    [root@ip-172-31-78-238 sysconfig]# systemctl restart config-server
    [root@ip-172-31-78-238 sysconfig]#

    ----------------------------------

    [root@ip-172-31-78-238 sysconfig]# ps -ef | grep config-server
    cliqrus+  3096     1  0 17:00 ?        00:00:00 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/config-server.jar
    cliqrus+  3100  3096  0 17:00 ?        00:00:00 /bin/bash /usr/local/cliqr/apps/config-server.jar
    cliqrus+  3177  3100 48 17:00 ?        00:00:16 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xmx256m -jar /usr/local/cliqr/apps/config-server.jar
    root      3300  1854  0 17:00 pts/0    00:00:00 grep --color=auto config-server
    [root@ip-172-31-78-238 sysconfig]#

    ----------------------------------

    [root@ip-172-31-78-238 sysconfig]# systemctl status config-server
    ● config-server.service - Config Server
       Loaded: loaded (/etc/systemd/system/config-server.service; enabled; vendor preset: disabled)
       Active: active (running) since Fri 2017-11-10 17:00:14 UTC; 1min 12s ago
     Main PID: 3096 (sh)
       CGroup: /system.slice/config-server.service
               ├─3096 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/config-server.jar
               ├─3100 /bin/bash /usr/local/cliqr/apps/config-server.jar
               └─3177 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xmx256m -jar /usr/local/cliqr/apps/config-server.jar

    Nov 10 17:00:14 ip-172-31-78-238.ec2.internal systemd[1]: Starting Config Server...
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: _____             __ _                       _   _                _____
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: / ____|           / _(_)                     | | (_)              / ____|
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: | |     ___  _ __ | |_ _  __ _ _   _ _ __ __ _| |_ _  ___  _ __   | (___   ___ _ ____   _____ _ __
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: | |    / _ \| '_ \|  _| |/ _` | | | | '__/ _` | __| |/ _ \| '_ \   \___ \ / _ \ '__\ \ / / _ \ '__|
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: | |___| (_) | | | | | | | (_| | |_| | | | (_| | |_| | (_) | | | |  ____) |  __/ |   \ V /  __/ |
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: \_____\___/|_| |_|_| |_|\__, |\__,_|_|  \__,_|\__|_|\___/|_| |_| |_____/ \___|_|    \_/ \___|_|
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: __/ |
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: |___/
    Nov 10 17:00:34 ip-172-31-78-238.ec2.internal sh[3096]: CliQr Configuration Server : (v4.8.2-SNAPSHOT) , Powered by Spring Boot : 1.5.8.RELEASE
    [root@ip-172-31-78-238 sysconfig]#

    Come riavviare il server di notifica in CCM?

    [root@ip-172-31-78-238 sysconfig]# systemctl restart notification
    [root@ip-172-31-78-238 sysconfig]#

    -----------------------------------
    [root@ip-172-31-78-238 sysconfig]# ps -ef | grep notification
    cliqrus+  3572     1  0 17:02 ?        00:00:00 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/notification-server.jar
    cliqrus+  3574  3572  0 17:02 ?        00:00:00 /bin/bash /usr/local/cliqr/apps/notification-server.jar
    cliqrus+  3587  3574 68 17:02 ?        00:00:31 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xms256m -Xmx256m -Djava.security.egd=file:/dev/./urandom -jar /usr/local/cliqr/apps/notification-server.jar
    root      3704  1854  0 17:03 pts/0    00:00:00 grep --color=auto notification
    [root@ip-172-31-78-238 sysconfig]#

    -----------------------------------

    [root@ip-172-31-78-238 sysconfig]#
    [root@ip-172-31-78-238 sysconfig]# systemctl status notification
    ● notification.service - Notification Server
       Loaded: loaded (/etc/systemd/system/notification.service; enabled; vendor preset: disabled)
       Active: active (running) since Fri 2017-11-10 17:02:57 UTC; 1min 16s ago
     Main PID: 3572 (sh)
       CGroup: /system.slice/notification.service
               ├─3572 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/notification-server.jar
               ├─3574 /bin/bash /usr/local/cliqr/apps/notification-server.jar
               └─3587 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xms256m -Xmx256m -Djava.security.egd=file:/dev/./urandom -jar /usr/local/cliqr/apps/notification-server.jar

    Nov 10 17:02:57 ip-172-31-78-238.ec2.internal systemd[1]: Started Notification Server.
    Nov 10 17:02:57 ip-172-31-78-238.ec2.internal systemd[1]: Starting Notification Server...
    Nov 10 17:03:04 ip-172-31-78-238.ec2.internal sh[3572]: _   _       _   _  __ _           _   _                _____
    Nov 10 17:03:04 ip-172-31-78-238.ec2.internal sh[3572]: | \ | |     | | (_)/ _(_)         | | (_)              / ____|
    Nov 10 17:03:04 ip-172-31-78-238.ec2.internal sh[3572]: |  \| | ___ | |_ _| |_ _  ___ __ _| |_ _  ___  _ __   | (___   ___ _ ____   _____ _ __
    Nov 10 17:03:04 ip-172-31-78-238.ec2.internal sh[3572]: | . ` |/ _ \| __| |  _| |/ __/ _` | __| |/ _ \| '_ \   \___ \ / _ \ '__\ \ / / _ \ '__|
    Nov 10 17:03:04 ip-172-31-78-238.ec2.internal sh[3572]: | |\  | (_) | |_| | | | | (_| (_| | |_| | (_) | | | |  ____) |  __/ |   \ V /  __/ |
    Nov 10 17:03:04 ip-172-31-78-238.ec2.internal sh[3572]: |_| \_|\___/ \__|_|_| |_|\___\__,_|\__|_|\___/|_| |_| |_____/ \___|_|    \_/ \___|_|
    Nov 10 17:03:04 ip-172-31-78-238.ec2.internal sh[3572]: osmosix-notification : (v4.8.2-SNAPSHOT), Powered by Spring Boot : 1.5.8.RELEASE
    [root@ip-172-31-78-238 sysconfig]#

    Come riavviare il servizio cliqr-admin in CCM?

    [root@ip-172-31-78-238 sysconfig]# systemctl restart cliqr-admin
    [root@ip-172-31-78-238 sysconfig]#

    -------------------------------------

    [root@ip-172-31-78-238 sysconfig]# ps -ef | grep cliqr-admin
    cliqrus+  3736     1  0 17:05 ?        00:00:00 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/cliqr-admin.jar
    cliqrus+  3737  3736  0 17:05 ?        00:00:00 /bin/bash /usr/local/cliqr/apps/cliqr-admin.jar
    cliqrus+  3750  3737 69 17:05 ?        00:00:22 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xms256m -Xmx256m -Djava.security.egd=file:/dev/./urandom -jar /usr/local/cliqr/apps/cliqr-admin.jar
    root      3779  1854  0 17:05 pts/0    00:00:00 grep --color=auto cliqr-admin
    [root@ip-172-31-78-238 sysconfig]#

    -------------------------------------

    [root@ip-172-31-78-238 sysconfig]# systemctl status cliqr-admin
    ● cliqr-admin.service - Cliqr Admin
       Loaded: loaded (/etc/systemd/system/cliqr-admin.service; enabled; vendor preset: disabled)
       Active: active (running) since Fri 2017-11-10 17:05:28 UTC; 1min 2s ago
     Main PID: 3736 (sh)
       CGroup: /system.slice/cliqr-admin.service
               ├─3736 /bin/sh -c . /etc/profile.d/jdk.sh;/usr/local/cliqr/apps/cliqr-admin.jar
               ├─3737 /bin/bash /usr/local/cliqr/apps/cliqr-admin.jar
               └─3750 /usr/lib/jvm/java-8-sun/bin/java -Dsun.misc.URLClassPath.disableJarChecking=true -Xms256m -Xmx256m -Djava.security.egd=file:/dev/./urandom -jar /usr/local/cliqr/apps/cliqr-admin.jar

    Nov 10 17:05:28 ip-172-31-78-238.ec2.internal systemd[1]: Started Cliqr Admin.
    Nov 10 17:05:28 ip-172-31-78-238.ec2.internal systemd[1]: Starting Cliqr Admin...
    Nov 10 17:05:31 ip-172-31-78-238.ec2.internal sh[3736]: i   _____ _                 _                _                          _           _
    Nov 10 17:05:31 ip-172-31-78-238.ec2.internal sh[3736]: / ____| |               | |              | |                /\      | |         (_)
    Nov 10 17:05:31 ip-172-31-78-238.ec2.internal sh[3736]: | |    | | ___  _   _  __| | ___ ___ _ __ | |_ ___ _ __     /  \   __| |_ __ ___  _ _ __
    Nov 10 17:05:31 ip-172-31-78-238.ec2.internal sh[3736]: | |    | |/ _ \| | | |/ _` |/ __/ _ \ '_ \| __/ _ \ '__|   / /\ \ / _` | '_ ` _ \| | '_ \
    Nov 10 17:05:31 ip-172-31-78-238.ec2.internal sh[3736]: | |____| | (_) | |_| | (_| | (_|  __/ | | | ||  __/ |     / ____ \ (_| | | | | | | | | | |
    Nov 10 17:05:31 ip-172-31-78-238.ec2.internal sh[3736]: \_____|_|\___/ \__,_|\__,_|\___\___|_| |_|\__\___|_|    /_/    \_\__,_|_| |_| |_|_|_| |_|
    Nov 10 17:05:31 ip-172-31-78-238.ec2.internal sh[3736]: Powered by Spring Boot : 1.5.8.RELEASE
    [root@ip-172-31-78-238 sysconfig]#

    Dove si trovano i file di log di CloudCenter?

    Si è verificata una modifica nei percorsi di log per CloudCenter Manager nella versione 4.8.2. Attualmente, i registri si trovano in

    directory /usr/local/cliqr/logs

     Il file include capacity-manager.log, config-server.log, mgmtserver.log, notification-server.log, cliqr-admin.log, hazelcast-server.log

    [root@ip-172-31-78-238 logs]# ls -l
    total 109472
    -rw-r--r--. 1 cliqruser cliqruser   250936 Nov 10 17:01 capacity-manager.log
    -rw-r--r--. 1 cliqruser cliqruser   161563 Nov 10 17:05 cliqr-admin.log
    -rw-r--r--. 1 cliqruser cliqruser   124466 Nov 10 17:05 config-server.log
    -rw-r--r--. 1 cliqruser cliqruser    92667 Nov 10 17:03 hazelcast-server.log
    -rw-r--r--. 1 cliqruser cliqruser 10485969 Nov 10 16:55 mgmtserver-1.log
    -rw-r--r--. 1 cliqruser cliqruser 10705871 Nov 10 16:57 mgmtserver-2.log
    -rw-r--r--. 1 cliqruser cliqruser 10485969 Nov 10 16:57 mgmtserver-3.log
    -rw-r--r--. 1 cliqruser cliqruser 10485802 Nov 10 16:57 mgmtserver-4.log
    -rw-r--r--. 1 cliqruser cliqruser 10485988 Nov 10 16:58 mgmtserver-5.log
    -rw-r--r--. 1 cliqruser cliqruser 10485953 Nov 10 17:01 mgmtserver-6.log
    -rw-r--r--. 1 cliqruser cliqruser 10485791 Nov 10 17:01 mgmtserver-7.log
    -rw-r--r--. 1 cliqruser cliqruser 10485825 Nov 10 17:02 mgmtserver-8.log
    -rw-r--r--. 1 cliqruser cliqruser 10485876 Nov 10 17:02 mgmtserver-9.log
    -rw-r--r--. 1 cliqruser cliqruser  8147705 Nov 10 17:13 mgmtserver.log
    -rw-r--r--. 1 cliqruser cliqruser   383964 Nov 10 17:09 notification-server.log

    Posizione della Configurazione guidata CloudCenter CCM

    Tutti i file di configurazione si trovano nella directory /usr/local/cliqr/bin

    Dove vengono salvate le configurazioni CCM dopo l'esecuzione della Configurazione guidata?

    Tutte le impostazioni verranno salvate nel file mgmtserver.conf che si troverà nella directory /etc/sysconfig.

    Dove viene salvata la configurazione ELK logstash in CCM?

    Il file di configurazione ELK logstash si trova nella directory /etc/sysconfig/ con nome file filebeat.

    Versione applicazione: 4.8.2 / 4.8.2.x

    TAC Authored

    Contributo dei tecnici Cisco

    • Vihar Kuruppathukattil
      Cisco TAC Engineer

    Questo documento ti è stato utile?

    FeedbackFeedback

    Contattaci

    Questo documento si applica a questi prodotti