DX Infrastructure Management

Expand all | Collapse all

Configuring Forwarding and Replication in NAS probe

  • 1.  Configuring Forwarding and Replication in NAS probe

    Posted 12-10-2018 03:36 PM

    Hi all.

    I have this situation. 

    *uim-server (nas): With principal nas

    *hub-a (nas): When deploy the nas probe, it create 2 subscriber (nas and alarm_enrichment), and this configuration its function ok, but when I check the console IM, see that are create 2 alarm with 2 nas.

     

     

    I don't know if this is normal, because on the portal UMP, only see 1 alarm.

     

     

    I think that this problem can be resolved with forwarding and replication option (nas probe).

    I am trying set up the option forwarding and replication of nas to nas but the probe fail, after a while, the nas probe are in the down state and I don't know why.

     

     

    Note: before of configure I disable the subscriber (nas - alarm_enrichment) and configure the replication.

     

    Any idea?



  • 2.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-10-2018 08:32 PM

    Try restarting secondary hub robot and see what happens.



  • 3.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-11-2018 08:30 AM

    if the restart does not resolve it then consider:

    forwarding/replication will not prevent nas from starting

    the real problem is nas at the secondary hub fails to start

    the rest about forwarding/replication only serves to confuse and distract from the real problem

    set nas to deactivate

    set alarm_enrichment to deactivate

    activate alarm_enrichment

    after it has both pid & port activate nas

    if nas still doesn't activate set it for log level 5 log size at least 1000

    do the above steps and check the logs

    if the nas log only shows max restarts then do it again with controller set for log level 3 and check its log

     

    another thing to try is go back to the default config

    rename the two local .db files and in the cfg set all the rules and profiles to be disabled

    if it starts things can be added back till the problem is found



  • 4.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-11-2018 10:56 AM

    Hi Yu_Ishitani and DavidM 

     

    Thank for your time and support.

     

    What is the best practice ? for this situation,

     

    uimserver - hubsecondary - hubsecondary

         nas    <---     nas         <---      nas

     

    *Configure forwarding/replication or standar configuration with the 2 subscribers (nas and alarm_enrichment)?



  • 5.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-11-2018 11:05 PM

    Hi, I don't think there are specific secondary nas guidelines.

    Someone does and someone does not.

    One specific senario you would utilize secondary nas is ToT (Time Over Threshold) feature.

    The feature need alarm_enrichment on secondary hub so you'll see nas there as well.



  • 6.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-11-2018 11:35 AM

    Hi before configured forwarding/replication againg and restart the server. The problem is the same.

     

    I configure the logs on nas like loglevel = 5 | logsize = 100000

     

    I see this line on the logs ---->

     

    Dec 11 11:18:48:700 [140446160381696] nas: SREQUEST: _close ->192.168.90.13/48002
    Dec 11 11:18:48:700 [140446160381696] nas: Failed in attaching to HUB, retry #101   ----> This appear in the logs, from #01 until #101,  to the 101 the state of the nas pass to red
    Dec 11 11:18:48:968 [140446151988992] nas: SqliteExecuteCallback: sqlite3_finalize returned:0
    Dec 11 11:18:48:968 [140446151988992] nas: SqliteExecuteCallback: sqlite3_finalize returned:0
    Dec 11 11:18:49:157 [140446135203584] nas: SqliteExecuteCallback: sqlite3_finalize returned:0
    Dec 11 11:18:50:158 [140446135203584] nas: SqliteExecuteCallback: sqlite3_finalize returned:0
    Dec 11 11:18:51:159 [140446135203584] nas: WaitLock: CARENATAHUB: _replPostQueue

     

    I attach the logs maybe you can see something different and help me with this.



  • 7.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-11-2018 02:56 PM

    Just want to make sure my understanding of your configuration is correct.

    uimserver - hubsecondary - hubsecondary

         nas    <---     nas         <---      nas

    renaming

    primary hub - nas 2     - nas 3

    does nas 3 only have communication to nas 2 and then nas 2 to primary hub

    or

    are nas 2 & nas 3 setup for HA and both communicate to primary hub

     

    based on the log it looks like nas can't connect to its queue and the messages are typical to what shows up in a HA setup.



  • 8.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-11-2018 05:12 PM

    David.

     

    My configuration is 

     

    primaryhub - secondaryhubA - secondaryhubB

         nas    <---     nasA         <---      nasB

     

    The nasB only have communication to nasA and nasA only with nas (primaryhub).

     

    the (primaryhub) compund to 1 server (window).

    the (secondaryhubA) compund to 2 servers in cluster of microsoft.

    the (secondaryhubB) compund to 1 server (linux).



  • 9.  Re: Configuring Forwarding and Replication in NAS probe

    Posted 12-12-2018 05:01 PM

    Next most likely cause is either something blocking nas access to the port or a problem with the local db files.

    To test the later

    deactivate

    rename database.db & transactionlog.db

    activate

    If it stays running there was a problem with one or both of those dbs.