Unless I'm missing something, it sounds like you have a transaction model- where each "dial-up" operation is a transaction. In such a model, you'd prolly like to have a service-date/time and a service completion date-time.
If I was tasked with this, I'd start with adding data columns for these two items.
The design issue you didn't provide is how long each server "transaction" lasts. If each server is online for less than a minute, you can swepp thru your server base in less than 12 hours- otherwise, it might take days.
Is logging-on guaranteed? You'll prolly want to also store transaction status, time on-line, etc. Then move on to data mining issues, like avg transaction speed, errs encountered, etc.
Good luck,
KC
It's been a long while since I've posted to PERL user group, its good to be back.
I've run into another project that I must complete however I have not found a way to automate dial up networking. We have about 1500 or so servers that are running dial up networking and the only way to make a connection is obviously to dial in. Its just a standard dial up that requires 3 parameters, "phone number","username", and "password". Currently I have about 1500 or so RAS phone book entries, but I want to get away from that. I have a database with all this information for each server.
The ultimate result is extracting out my params from DB, editing 1 RAS phone book entry, invoking the dial connection, running my stuff, and disconnecting, then on to the next one…
Has anyone run into this situation before? If so, would you mind pointing me in the right direction so that I may start down a path of a good solution?
Thanks in advance,
Dan J. Rychlik
Is Duane Kielty still around?
_______________________________________________
Perl-Win32-Users mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
