I had just gone home (that seems to be when most problems crop up, right
after I leave) and it stopped authenticating. All of our other pops were
fine so I knew it wasn't the radius server.
I came back in and telneted to the pm. I did a show global and it
showed that the radius and accounting ip's (and their alt's) were set to
0.0.0.0 Very strange since I hadn't touched this portmaster for weeks.
Ok, so I set the radius and acc server ip's to what they were and I did a
save all. Then it stopped working even more. After I rebooted a show
global would totaly skip the radius and accounting lines, it went from
telnet access port to disabled modules.
That was when I knew something was screwed up big time. I decided to
upgrade the ComOS to 3.3.3 from 3.3.2 and see if that helped. That just
made it worse. When ever I would do a show glo or show all it would just
display a bunch of SYSMESG002 or SYSMESG938, etc insted of the text.
Then on a hunch I downgraded back to 3.3.2 and it worked fine. I put the
settings back in and it is working like old.
Does Anyone have a clue what happened here? Should I send the PM back
before it happens again. Should I upgrade to 3.3.3 and hope it works ok
this time?
Mike Pistone
Systems Administrator
Eureka Networks