| Lelio Fulgenzi 2006-02-19, 8:45 pm |
| I think I've seen that before. I'd like to see something a litte more 'human readable' though, so it has the user and the action they took. Is that on the plans anytime soon? Something like transaction logging.
----- Original Message -----
From: Wes Sisk
To: Lelio Fulgenzi
Cc: Ed Leatherman ; cisco-voip@puck.nether.net
Sent: Sunday, February 19, 2006 8:31 PM
Subject: Re: [cisco-voip] change management documentation
every update/change you make is documented in the iis logs under c:\winnt\system32\logfiles\w3svc1
it's not in the nicest format, but there's enough there for you two gents as sharp as you to figure out the rest.
this is among my favorite tools when someone calls TAC and says 'nothing changed' 
/Wes
On Feb 19, 2006, at 9:52 AM, Lelio Fulgenzi wrote:
Regarding MLA, all I've seen is which pages have been accessed. Even with it on debug mode, nothing like what phone was deleted, or line was added, nothing! Very dissappointed in that. But I was more concerned with system changes. I can come up with a spreadsheet or something like that, but I was hoping for something pre-configured so that I don't miss an important field or something.
----- Original Message -----
From: Ed Leatherman
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Sent: Sunday, February 19, 2006 8:56 AM
Subject: Re: [cisco-voip] change management documentation
Kinda old fashioned, but I have a notebook i write down significant changes, patches, and so forth in. I've been wanting to put together an internal Wiki for change logs, documentation, etc but I just havent had the time to learn how to do it =\.
Callmanager doesnt audit changes anywhere with MLA does it?
On 2/18/06, Lelio Fulgenzi <lelio@uoguelph.ca > wrote:
Just wondering what others are using out there to document changes to
their system . For example, we have a route filter to restrict access to
900 and 976 numbers, but as we add to that, I'd like to be able to
document what the changes were, who suggested them, who authorized them
and more importantly why the changes were made.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|