Start a Conversation

Unsolved

This post is more than 5 years old

D

2334

January 29th, 2008 05:00

SVIF-EBROKER-Cannot connect to DM Broker at 'localhost:426/dmbroker

INCHARGE-SA.log
SVIF-EBROKER-Cannot connect to DM Broker at 'localhost:426/dmbroker
when a failover process is tested on the secondary server which is also a broker
Also another error mesaage [29-Jan-2008 11:42:40+652ms WAT] t@27 INCHARGE-OI_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-OI'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:40+735ms WAT] t@30 INCHARGE-MPLS_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-MPLS'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker
ther error message
All in the INCHARGE-SA.log

89 Posts

January 30th, 2008 02:00

hi dele,

did you install 2 brokers in different systems? is/are your broker/s started?
do your servers point to the correct broker?

cheers

1 Rookie

 • 

79 Posts

January 30th, 2008 03:00

the true story is that we have two servers one primary and the other one secondary server with a broker installed on it(secondary) .The primary was stoped and the secondary kick off which is fine, the INCHARGE-SA started which we expected but the other domain such as INCHARGE-AM.PM, INCHARGE-MPLS INCHARGE-BGP etc would not start and in the INCHARGE-SA.log file
this is the output
[29-Jan-2008 11:40:26+135ms WAT] t@17 InCharge Framework
ICS-W-EINITMESSAGE-ics-init.asl: Executing ICS initialization

ICNF-N-ICS_CONF_PROCESSING_FILE-Processing configuration file
'/opt/InCharge6/SAM/smarts/local/conf/ics/ics.conf'

ICNF-N-ICS_CONF_PROCESSING_FILE-Processing configuration file
'/opt/InCharge6/SAM/smarts/conf/ics/weights.conf'

[29-Jan-2008 11:40:27+656ms WAT] t@17 InCharge Framework
ICS-W-ESTARTINGDRIVER-ICS_ParseConf.asl: Starting Impact Adapter

[29-Jan-2008 11:40:27+680ms WAT] t@17 InCharge Framework
ICS-W-ESTARTINGDRIVER-ICS_ParseConf.asl: Starting Business Impact Adapter

ICNF-N-ICS_CONF_SECTION_UPDATED-Successfully processed 'SystemDefaultsSection'

ICNF-N-ICS_CONF_SECTION_UPDATED-Successfully processed 'TagSection'

[29-Jan-2008 11:40:27+838ms WAT] t@17 InCharge Framework
ICS-W-ERECONFIGURING-ICS_ParseConf.asl: Reconfiguring domain 'INCHARGE-AM-PM'

[29-Jan-2008 11:40:27+870ms WAT] t@17 InCharge Framework
ICS-W-ERECONFIGURING-ICS_ParseConf.asl: Reconfiguring domain 'INCHARGE-OI'

[29-Jan-2008 11:40:27+882ms WAT] t@17 InCharge Framework
ICS-W-ERECONFIGURING-ICS_ParseConf.asl: Reconfiguring domain 'INCHARGE-BGP'

[29-Jan-2008 11:40:27+895ms WAT] t@17 InCharge Framework
ICS-W-ERECONFIGURING-ICS_ParseConf.asl: Reconfiguring domain 'INCHARGE-OSPF'

[29-Jan-2008 11:40:27+907ms WAT] t@17 InCharge Framework
ICS-W-ERECONFIGURING-ICS_ParseConf.asl: Reconfiguring domain 'INCHARGE-MPLS'

[29-Jan-2008 11:40:27+920ms WAT] t@17 InCharge Framework
ICS-W-ERECONFIGURING-ICS_ParseConf.asl: Reconfiguring domain 'INCHARGE-PROV'

[29-Jan-2008 11:40:27+933ms WAT] t@17 InCharge Framework
ICS-W-ERECONFIGURING-ICS_ParseConf.asl: Reconfiguring domain 'INCHARGE-SDI'

ICNF-N-ICS_CONF_SECTION_UPDATED-Successfully processed 'DomainSection'

ICNF-N-ICS_CONF_SECTION_UPDATED-Successfully processed 'BusinessSection'

ICNF-N-ICS_CONF_PROCESSING_FILE-Processing configuration file
'/opt/InCharge6/SAM/smarts/local/conf/ics/service-map.conf'

ICNF-N-ICS_CONF_PROCESSING_FILE-Processing configuration file
'/opt/InCharge6/SAM/smarts/conf/ics/tiered-application-map.conf'

ICNF-N-ICS_CONF_PROCESSING_FILE-Processing configuration file
'/opt/InCharge6/SAM/smarts/conf/ics/hsrp-group-map.conf'

ICNF-N-ICS_CONF_PROCESSING_FILE-Processing configuration file
'/opt/InCharge6/SAM/smarts/conf/ics/application-relationship-map.conf'

ICF-N-RECONFIGURESTART-PolicyManager: reconfigure started at 29-Jan-2008
11:42:36 WAT
ICF-N-RECONFIGUREFINISH-PolicyManager: reconfigure finished at 29-Jan-2008
11:42:36 WAT
[29-Jan-2008 11:42:35+852ms WAT]
RSRV-N-DMSTARTED-Domain Manager INCHARGE-SA started on iky-smarts-sec:9100
V6.5 SP3 RP13(68072), 07-Dec-2006 20:35:49 - SmartPack 3, Build 13
[29-Jan-2008 11:42:36+856ms WAT] t@27 INCHARGE-OI_Driver
ICS-W-ESUBSCRIBING-ics-event-driver.asl: 'INCHARGE-OI' - Subscribing to
Notification List 'Default'

[29-Jan-2008 11:42:40+652ms WAT] t@27 INCHARGE-OI_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-OI'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:40+735ms WAT] t@30 INCHARGE-MPLS_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-MPLS'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:40+928ms WAT] t@31 INCHARGE-PROV_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-PROV'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:42+933ms WAT] t@28 INCHARGE-BGP_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-BGP'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:43+609ms WAT] t@30 INCHARGE-MPLS_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-MPLS'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:43+774ms WAT] t@31 INCHARGE-PROV_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-PROV'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:43+894ms WAT] t@47 INCHARGE-PROV_Event-Driver
ICS-W-EDISCONNECTED-ics-event-processing.asl: DISCONNECT 'INCHARGE-PROV'

[29-Jan-2008 11:42:44+109ms WAT] t@27 INCHARGE-OI_Driver
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server
'INCHARGE-OI'
SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker

[29-Jan-2008 11:42:44+136ms WAT] t@46 INCHARGE-MPLS_Event-Driver
ICS-W-EDISCONNECTED-ics-event-processing.asl: DISCONNECT 'INCHARGE-MPLS'
--More--(59%)

89 Posts

January 30th, 2008 04:00

Well,

did u check your config files for each domain ?

like runcmd_env.sh to check if the domains are pointing to the right broker ...
or ics.conf and icoi.conf for SAM ?

/opt/InCharge6/SAM/smarts/local/conf/runcmd_env.sh
/opt/InCharge6/SAM/smarts/local/conf/ics/ics.conf
/opt/InCharge6/SAM/smarts/local/conf/icoi/icoi.conf

it looks like SAM is not capable to see any other domain

cheers

1 Rookie

 • 

79 Posts

January 30th, 2008 08:00

thye files are fine and are the same with secondary .The problem is that the secondary server starts the INCHARGE-SA starts but not the am-pm,mpls and bgp
the files are being copied accross as a .rps is formed on the secondary but i am not sure if the right files and directory are copied accross.
PLEASE HELP I AM stuck

89 Posts

January 31st, 2008 01:00

Hi dele,


i think that you´re trying to do a kind of standby ... but a manual one ... cold standby?
Several problems you might encounter there ...
-Config files must be moved from stanby server to backup. Check your local folders ( \SAM\smarts\local, \IP\smarts\local, etc ...)
Licenses - Licenses are bound to the host id, so if you move to another server you need new licenses
-Repositories - I`m not quite sure but i think you can not use a repository from one system in a different one.
- if SAM does not start try ro restart with a new topology using the --cleantopology and previously exporting all your configs through sm_config and then importing back them as soon as the service starts. If this works, don´t forget to remove the --cleantopology flag from your sm_server command
Try to use one of the migrations guides in order to copy the files you need to your backup enviroment ... you can find then in the pdf documents as sa_install.pdf or sa_migration.pdf

cheers

89 Posts

January 31st, 2008 08:00

Well,

let me try to understand ...
you have 2 servers ... One primary and one backup.
SMARTS is installed in both servers and you copy over the repositories adn then start it whenever you needed !

Do you have the EMC SMARTS Redundancy product?

are both servers in the same smarts version?

can you try to explain your enviroment a bit better?

the documentation is under \SAM\smarts\doc\pdf or \SAM\smarts\doc\html

cheers

1 Rookie

 • 

79 Posts

January 31st, 2008 08:00

ada,

thanks we have licenses for the second server including sa because sa was started when the secondary was up which means the notification log console was up but the INCHARGE-AM>PM was not running .
I dont know where i can find these sa_migration. pdf
PLEASE HELP

1 Rookie

 • 

79 Posts

February 1st, 2008 01:00

we have two servers one primary which has the INCHARGE-SA,INCHARGE-AM.PM,INCHARGE-MPLS & co . we also have a secondary server similar but as a backup where the services are not running but has a broker on it when the primary failed as a test the secondary server picks up with the INCHARGE-SA starting but the rest services are not e.g INCHARGE-MPLS, INCHARGE-AM.PM, on the secondary server even though the broker is also installed on the secondary
it is 6.5

89 Posts

February 1st, 2008 01:00

Hi dele,

did you check if all configuration files are copied over the backup server?
are the domains (AM-PM, MPLS, etc ...) pointing to the proper broker?
Did you check if your licenses are a copycat of your primary server licenses?

type brcontrol on a terminal window and check the output

cheers

F.

1 Rookie

 • 

79 Posts

February 1st, 2008 02:00

i thought a failover should automatically copy content of the conf from primary to secondary.
i don,t know if this sa_migration could do it.

89 Posts

February 1st, 2008 02:00

Well, if you have the failover solution from SMARTS, all should be automatic.
I don´t know how the product is workin and i heard that EMC Profesional services must install and configure it ...
So if you're using that i advise you to contact with EMC suppor and open a case

sa_migration is just a document that explains how to migrate the product from version x to version x+1 and the files you need to migrate from one side to the other
I advised you to use this document because explains all files needed to install the product from scratch and use the previous version config files ...

cheers

27 Posts

February 12th, 2008 08:00

Gentlemen - Just to let you know. .rps files a hard coded to the server that the repository is on. If you copy the repository to another machine "It will NOT work". I spent 4 months proving that this is so. The broker repository has an entry for each programmed service and is hard coded for the server that is supplying that service. Each of the service repositories have hard coded server names in them so they also cannot be moved. The best level of duplication that can be done is for the ACM signatures and IP discovery entries. Any movement of a repository from one machine to another will fail.
No Events found!

Top