BMC Communities Banner

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (5 pts)
7 Replies Last post: Nov 6, 2009 2:29 PM by carslone  
14rich Participant 13 posts since
Jul 12, 2002
Currently Being Moderated

Oct 23, 2009 2:18 PM

Passive Cell Issue --- Cell connection refused

Hello,


Setting up the passive setup between two cells on seperate sides of a firewall and the destination cell is rejecting the event.  On e the destination in the Details tab we get the  following data


Cell Disallowed Connect  -----    Reason not allowed


Cell Client       

Cleint Location   ----- xxx.xxx.xxx.xxx/2038

Client Name       ---- msend

Client Type        ---- adapter


On the sending side we are using the gateway.eif with the following info


protocol=EIF
cond.new=propagate
cond.mod=always
slots.new=[$ALL]
slots.mod=[$MODS]
init.new=$CLASS;\n
init.mod=modify $GHANDLE;\n
body=\t$NAME=$VALUE;\n
term=END\n
openquote='
closequote='
escapequote='


the sending client has the info in the mcell.dir and using the send_to in a rule for the cell just to get started. The mcell.dir is below for the gateway


gateway.eif        [cell_name_destination]      0       [name of firewall]:1830


On the destination side we also have the

 

mc_evtdata_internal.baroc

     MC_DATA_CLASS:

          MC_CELL_HEARTBEAT ISA MC_CELL_DATA

          .....

END

 

MC_DATA_CLASS :

     MC_CELL_PASSIVE_CLEINT ISA MC_CELL_HEARTBEAT;

END

 

MC_CELL_PASSIVE_CLIENT;
     cell = OutsideFW; # Source/destination cell name
     enable = 1; # 0 = disabled / 1 = enabled
     interval = 10 m; # Interval between heartbeats (s)
     missed_warning = 1; # Number of misses for WARNING event
     missed_minor = 2; # Number of misses for MINOR event
     missed_critical = 3; # Number of misses for CRITICAL event
END


The firewall recieve the packet and moves it through and resends it to the destinataion, so we have eliminated it as the issue.  Also, using a packet capture tool on the destination we see the packet come in.    We are getting ready to change direction and use the tcpserver adapter to get the packet since we can capture the packet on the destination but this should work.  We have even moved away from the firewall to two servers sitting side by side and get the same error.

fthomae Enthusiast 33 posts since
Jan 24, 2006
Currently Being Moderated
1. Oct 26, 2009 2:43 AM in response to: 14rich
Re: Passive Cell Issue --- Cell connection refused

Hi,

 

I'm not 100% sure, but I think that passive connections are not supported over the EIF protocol.

 

HTH,

Frank

ma14pg6 HotShot 250 posts since
Jun 11, 2002
Currently Being Moderated
2. Oct 27, 2009 5:56 AM in response to: 14rich
Re: Passive Cell Issue --- Cell connection refused

Why do you use EIF as protocol?

 

As you wrote, the client name is "msend". msend doesn't support EIF.

 

Try to use MCELL instead of EIF.

s197 Participant 27 posts since
Oct 25, 2006
Currently Being Moderated
3. Nov 4, 2009 5:00 PM in response to: ma14pg6
Re: Passive Cell Issue --- Cell connection refused

Do you have the following license key info defined in mcell.conf for the receiving server?

 

#CellEIFLicenseKey=

s197 Participant 27 posts since
Oct 25, 2006
Currently Being Moderated
6. Nov 5, 2009 7:00 AM in response to: 14rich
Re: Passive Cell Issue --- Cell connection refused

This was a license key I had to get from BMC Support in order to use msend. It's a long alphanumeric string.

 

Steve Ferrara

ESM Monitoring

Lowe's Companies

704-758-5329

carslone HotShot 92 posts since
Sep 20, 2006
Currently Being Moderated
7. Nov 6, 2009 2:29 PM in response to: 14rich
Re: Passive Cell Issue --- Cell connection refused

Rich,

 

mc is the encryption key used by BEM (assuming you're using the default).  The EIF license key is, like Steve said, a long alphanumeric string.

 

The good thing is that the license key is available for free; you just need to request it from support.

 

 

 

Carlos.

More Like This

  • Retrieving data ...