
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
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.
Hi,
I'm not 100% sure, but I think that passive connections are not supported over the EIF protocol.
HTH,
Frank
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.
Do you have the following license key info defined in mcell.conf for the receiving server?
#CellEIFLicenseKey=
Hello I am using the EIF since it does not require a response after sending out the packet. The packet leaves on firewalled off network and arrives at the second firewalled off network and goes to the server running the mcell.
Does that explain why I am using this instead of normal communications.
Thanks,
Rich
.
Hi,
I do not have that line in the reciever... So I am assuminig that we should have
CellEIFLicenseKey=mc
Is that correct?
Thanks,
Rich
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
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.