You bet. This is an authentication problem. We've got a PM
here that screws up in just this way when we "set s0 security on"
(for example). Our RADIUS servers are set correctly, the RADIUS secret
is set properly, and we have 2 other PM's functioning perfectly.
Livingston initially said it was a configuration problem, but this unit
is a replacement PM, and I'd used pmreadconf to save the config of the
old unit and pmconsole to put it on the new one. Same ComOS (though
I've tried 3 different versions), and brought it down to a basic level.
I'd reinitialize the flash RAM, install a ComOS and set just enough
info to have the unit be seen on our net and to handle RADIUS
authentication.
It's currently an open issue with Livingston, and has baffled some
of their best folks so far.