cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1163
Views
0
Helpful
6
Replies

ACS riddles

bhrx735
Level 1
Level 1

Hi,

after installing an ACS appliance, and reading the manual, I still wonder about some details. First, a few days after installing the ACS, suddenly I was

unable to log in via the web interface. I got the login page, but the login/password combination appeared to be wrong. So I opened a telnet

session to the ACS, logged in and restarted the server. The solved the login

problem, but created a new problem. I could not open a telnet session.

A second question which is not documented is what happens with the logs after a period of time. Are they cleaned up? I found a document in which is

described that the filesystem is not approachable. So I also wonder what happens when de filesystem is full.

Thx,

Bart.

6 Replies 6

drolemc
Level 6
Level 6

To prevent the ACS system logs from growing too large, you need to specify what action needs to be taken on older messages. To do this, go to "system configuration", Click on "logging", Click on any log listed there and on the option "manage directory", check the box "delete files older than 7 days"

When i look at the logging config, i can 'enable logging' and 'select column to log'. There's nothing about directory managing. Is this an option which has to be enabled somewhere before i can use it?

How did you get this to work in the end?

We are have the same problem - can;t login via the GUI.

Thanks in advance..

Had same problem here some time back. The message I got though was that "the machine I was using could not be used for administration" After doing someresearch I found out that a new Java version I had installed (after installing nGenius) was not working right with my proxy server here. To get around I did a "bypass proxy server and reset the java cache"

The odd thing was that I could telnet to the ACS device and issue commands. After I got GUI access (and rebooted the ACS device) I can no longer telnet to the device. TAC had told me THIS was normal .. telnet is not allowed, but they could not explain why I was able to telnet for some time and not any more.

It seems that the loging problem (if it is about the 'protocol error') is a bug. Possibly an upgrade could help...

it should be under "system configuration" and called

"service control". If you don't get this option "service control" should be ticked for your userid in "administration control".

Serhat