I have two Cisco 800 series ISDN routers connected together. I have configured them so that after 5 minutes of idle-time, the connection goes down. When the connection goes down, the the uptime is logged. However, looking at logging, I see where the connection connects and then disconnects after 5 minutes of idle-time many times during a 24-hour period. This occurs mainly during non-working hours. Is there a way, to find out the cumulative uptime. I need to make sure that we are not exceeding our allowable hours. This connection was originally done with non-Cisco routers and I did not have this problem. The connection would go down and not start back up until needed by the user. Any suggestions?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How can I log cumulative uptime on ISDN routers?
- Thread starter ankle
- Start date
Two suggestions:
First, if time is critical, why allow 5 minutes of idle time before disconnecting the call? With the right configuration, calls can be reestablished in seconds. You do have to consider long distance, if that plays any roll. You could be billed 2 minutes long-distance for a 1 minute 1 second transmission. I would disconnect the call sooner.
Second, Logging time, we utilize the console logging. I have a single router with a PRI and it can receive or make multiple calls instantly. In my network an ISDN call means another circuit is in trouble. We keep a Hyper Terminal attached to the console. It doesn’t even have to be logged into the CLI. We enable “Capture” to file on the Hyper terminal and can access data no-longer in the buffer. It’s low-tech but very cheap. You also have to be relatively close to one of the ISDN routers.
First, if time is critical, why allow 5 minutes of idle time before disconnecting the call? With the right configuration, calls can be reestablished in seconds. You do have to consider long distance, if that plays any roll. You could be billed 2 minutes long-distance for a 1 minute 1 second transmission. I would disconnect the call sooner.
Second, Logging time, we utilize the console logging. I have a single router with a PRI and it can receive or make multiple calls instantly. In my network an ISDN call means another circuit is in trouble. We keep a Hyper Terminal attached to the console. It doesn’t even have to be logged into the CLI. We enable “Capture” to file on the Hyper terminal and can access data no-longer in the buffer. It’s low-tech but very cheap. You also have to be relatively close to one of the ISDN routers.
- Thread starter
- #3
Long-distance is not involved. The remote site is about 10 miles away. They connect to us through a local ISDN line. We just have a certain number of connect hours allowed per month. I don't want to exceed that. Thanks for ideas. Heppy Holidays.
- Status
Similar threads
- Locked
- Question
- Locked
- Question