Here is a quick question for all of the technically minded folks who have BAM running on non RH Enterprise servers (or even on it, in fact).
Currently, I have both the BAM server and the license server installed on an RH9 machine - after the now legendary fights with the Java installer for the licensing!
My problem is that nothing is listening on udp port 1234 - which seems to be the one that the APs are initially trying to talk to, so obviously things aren’t working.
A quick strace on engined and ssed at startup show neither of them trying to doing anything with udp/1234. Is there another daemon which should be running and is failing?
As an aside, I know that RH9 is ancient, and we are not intending to use is in production - but I didn’t feel like the pain of making BAM work under FreeBSD without a quick sanity checking install under Redhat first!
Thanks,
Paul.
Paul_Thornton wrote: Here is a quick question for all of the technically minded folks who have BAM running on non RH Enterprise servers (or even on it, in fact).
Currently, I have both the BAM server and the license server installed on an RH9 machine - after the now legendary fights with the Java installer for the licensing!
My problem is that nothing is listening on udp port 1234 - which seems to be the one that the APs are initially trying to talk to, so obviously things aren't working.
A quick strace on engined and ssed at startup show neither of them trying to doing anything with udp/1234. Is there another daemon which should be running and is failing?
As an aside, I know that RH9 is ancient, and we are not intending to use is in production - but I didn't feel like the pain of making BAM work under FreeBSD without a quick sanity checking install under Redhat first!
Thanks,
Paul.
I am having the same problem even though I am using RH Enterprise Linux V3. I can't see where the problem is since I have successfully installed all the required softwares. I have checked the canopy.log file and the BAM, Auth Server, and the AP checks out licenses for themselves but not the SM even though the SM is listed in the BAM database. Re-Reg counts fire up when authentication is required in the AP.
Whereelse can I verify if the BAM is really running? Can tech support please assist?
For the record, and for anyone searching, I gave up and ran this on CentOS.
BAM server now functions fine.
The usefulness of BAM 2.0 is, however, a different question - the documentation seems to promise a lot but the application delivers little. It is just an over complex replacement for a radius server with a database and a front end, with the added disadvantage that the protocol between AP and BAM is proprietory so you can’t replace it 
Prizm adds an entry to your /etc/service called “ap” on port 1234.
But some distros (Fedora 6) already have a service named “ap” (Alc Protocol 47806) on a different port!! Check that and if it exists remove the 47806 entry. Else prizm will get confused and listen on a different port.