You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(8) |
Sep
(5) |
Oct
(7) |
Nov
|
Dec
|
|---|
|
From: Joe C. <ma...@ma...> - 2001-10-05 16:21:31
|
Sure, let me know where specifically you want me to look. Joe On Fri, 5 Oct 2001, Thomas, Nick wrote: > I am stuck on the DB.pm if you could look at it and help I would appreciate > it. Like I said before I am not that good at perl and a lot of what I am > doing is hard to figure out for me. > > Thanks > Nick > > -----Original Message----- > From: Joe Clarke [mailto:ma...@ma...] > Sent: Friday, October 05, 2001 11:13 AM > To: Julien Pasquier > Cc: cos...@li... > Subject: Re: [Cosi-nms-saa-dev] web interface > > > > > On Fri, 5 Oct 2001, Julien Pasquier wrote: > > > Hi everybody, > > Sorry, I'm very busy and I have not begun to code the html interface, I'll > do it as soon as I can. > > What should it be like? Like ciscoworks2000 user interface? > > I think the best thing to do is make it simple an usable. I like the idea > of a menu on the left (like CW2K) with a main frame to do all of the > configuration in. There needs to be a login screen as well. > > Since this will be a sans Java project, having JavaScript form validation > where possible would be a good idea. There needs to be options for > setting up and listing all of the available SAA objects (Source, Target, > Operation, Collector) as well as application-specific administration like > adding users, and backing up the database. > > Joe > > > > > Julien > > > > > > > _______________________________________________ > Cosi-nms-saa-dev mailing list > Cos...@li... > https://lists.sourceforge.net/lists/listinfo/cosi-nms-saa-dev > > _______________________________________________ > Cosi-nms-saa-dev mailing list > Cos...@li... > https://lists.sourceforge.net/lists/listinfo/cosi-nms-saa-dev > > |
|
From: Thomas, N. <Th...@me...> - 2001-10-05 16:15:08
|
I am stuck on the DB.pm if you could look at it and help I would appreciate it. Like I said before I am not that good at perl and a lot of what I am doing is hard to figure out for me. Thanks Nick -----Original Message----- From: Joe Clarke [mailto:ma...@ma...] Sent: Friday, October 05, 2001 11:13 AM To: Julien Pasquier Cc: cos...@li... Subject: Re: [Cosi-nms-saa-dev] web interface On Fri, 5 Oct 2001, Julien Pasquier wrote: > Hi everybody, > Sorry, I'm very busy and I have not begun to code the html interface, I'll do it as soon as I can. > What should it be like? Like ciscoworks2000 user interface? I think the best thing to do is make it simple an usable. I like the idea of a menu on the left (like CW2K) with a main frame to do all of the configuration in. There needs to be a login screen as well. Since this will be a sans Java project, having JavaScript form validation where possible would be a good idea. There needs to be options for setting up and listing all of the available SAA objects (Source, Target, Operation, Collector) as well as application-specific administration like adding users, and backing up the database. Joe > > Julien > > _______________________________________________ Cosi-nms-saa-dev mailing list Cos...@li... https://lists.sourceforge.net/lists/listinfo/cosi-nms-saa-dev |
|
From: Joe C. <ma...@ma...> - 2001-10-05 16:12:37
|
On Fri, 5 Oct 2001, Julien Pasquier wrote: > Hi everybody, > Sorry, I'm very busy and I have not begun to code the html interface, I'll do it as soon as I can. > What should it be like? Like ciscoworks2000 user interface? I think the best thing to do is make it simple an usable. I like the idea of a menu on the left (like CW2K) with a main frame to do all of the configuration in. There needs to be a login screen as well. Since this will be a sans Java project, having JavaScript form validation where possible would be a good idea. There needs to be options for setting up and listing all of the available SAA objects (Source, Target, Operation, Collector) as well as application-specific administration like adding users, and backing up the database. Joe > > Julien > > |
|
From: Julien P. <jul...@if...> - 2001-10-05 14:53:40
|
Hi everybody, Sorry, I'm very busy and I have not begun to code the html interface, = I'll do it as soon as I can. What should it be like? Like ciscoworks2000 user interface? Julien |
|
From: Joe C. <ma...@ma...> - 2001-10-04 02:25:17
|
It does. Collector->source()->name() Collector->target()->name() should give you that info. Of course, the target maybe undef for a DHCP, DNS, FTP, or HTTP collector. Joe On Wed, 3 Oct 2001, Thomas, Nick wrote: > Shouldn't the collector object contain the name of the target and source > objects it should use? So that we can call the Target and Source info from > the Database. > > Nick > > _______________________________________________ > Cosi-nms-saa-dev mailing list > Cos...@li... > https://lists.sourceforge.net/lists/listinfo/cosi-nms-saa-dev > > |
|
From: Thomas, N. <Th...@me...> - 2001-10-04 02:24:09
|
uhhh... Duh... they are already in there. Nevermind.... -----Original Message----- From: Thomas, Nick To: 'cos...@li...' Sent: 10/3/01 9:19 PM Subject: Collectors.pm Shouldn't the collector object contain the name of the target and source objects it should use? So that we can call the Target and Source info from the Database. Nick |
|
From: Thomas, N. <Th...@me...> - 2001-10-04 02:22:31
|
Shouldn't the collector object contain the name of the target and source objects it should use? So that we can call the Target and Source info from the Database. Nick |
|
From: Joe C. <ma...@ma...> - 2001-09-26 17:06:37
|
I'm pleased to announce the SAA API is done*. * Most Operations can be set on the router (those excluded are jitter, and any kind of SNA operation). That said, I'd like to get to the database interface as well as the user interface. I'm going to start writing some CGI glue for the API. Julien, can you start working on some of the HTML pages? The user interface will be mostly form-based. They have to connfigure source routers, target nodes, operations, and then tie everything together into collectors. At that point, they can install the collectors on the source routers. Please feel free to ask any questions. Joe |
|
From: Thomas, N. <Th...@me...> - 2001-09-24 21:18:36
|
At this point we have decided to use Mysql, but we are using the perl DBI module for access so any database can be used later on. I am currently building (slowly but surely) a interface to provide easier access to the DB than what DBI gives us. If I can at least get a skeleton out of what the DB module will do, and what it will look like, maybe you can use it in the start of the web interface. Too busy to finish this mail so I will re-email it later. -----Original Message----- From: Julien Pasquier [mailto:jul...@if...] Sent: Monday, September 24, 2001 4:53 AM To: cos...@li... Subject: [Cosi-nms-saa-dev] Web interface Hi everybody, I'm ok to work on the web interface, just explain me what are the other components of the project (what is the database, on which OS is it installed, what are the SNMP components? ...). Julien |
|
From: Joe C. <ma...@ma...> - 2001-09-24 15:36:31
|
The project is designed to run on just about any OS out there. Right now, development is being done on FreeBSD and Linux. The database being used is MySQL, however, any database could be substituted. The SNMP engine is net-snmp (http://net-snmp.sourceforge.net). The goal of this project for now is to create a SAA configurator. We will not be doing any of the device polling and statistics collection right away. We will be translating the RTTMON-MIB into Perl code, and presenting the user a web interface to turn on and off SAA properties. The configuration is divided into four parts: Source, Target, Operation, and Collector. A Source is a Cisco router with SAA capabilities. A Target is any IP-addressable node. An Operation is a SAA function (e.g. an ICMP echo, TCP connect, or jitter probe). A Collector is a Source + (optional) Target + Operation. You should checkout the CVS source to this point. The instructions can be found at https://sourceforge.net/cvs/?group_id=25401, and the module name is saaconfig. We'd like to limit the interface to HTML and JavaScript to keep it as compatible as possible. I'm sure you'll have questions, so please don't hesitate to ask. Joe On Mon, 24 Sep 2001, Julien Pasquier wrote: > Hi everybody, > > I'm ok to work on the web interface, just explain me what are the other components of the project (what is the database, on which OS is it installed, what are the SNMP components? ...). > > Julien > > |
|
From: Julien P. <jul...@if...> - 2001-09-24 09:53:22
|
Hi everybody, I'm ok to work on the web interface, just explain me what are the other = components of the project (what is the database, on which OS is it = installed, what are the SNMP components? ...).=20 Julien |
|
From: Joe C. <ma...@ma...> - 2001-09-23 18:21:09
|
Julien, welcome. I want to reiterate things thus far. Nick and I have been working on the project backend. None of the web interface has been done. The project, as it stands now, is in CVS off of the cosi-nms page. The name of the project is saaconfig. Nick is working on the database components, and I'm working more on the SNMP side. I am coding the SAA Collector component. The MIB that this project is based on can be found at ftp://ftp.cisco.com/pub/mibs/v2/CISCO-RTTMON-MIB.my. Julien, if you want to work on the web interface, that would be great. Joe |
|
From: Joe C. <ma...@ma...> - 2001-08-25 19:27:33
|
Attached is a guide on setting up various SAA collectors via SNMP. These steps can be modified to use the net-snmp Perl API. Joe |
|
From: Joe C. <ma...@ma...> - 2001-08-10 19:06:09
|
Not a problem. I have updated the Echo.pm code. That operation is done. I have to start on writing code to build collectors. The collecotr code should handle the actual SNMP SETs, I guess.... Joe Clarke On Fri, 10 Aug 2001, Thomas, Nick wrote: > Oops I didn't even see what you were trying to say. I understand completely > now. > > -----Original Message----- > From: Joe Clarke [mailto:ma...@ma...] > Sent: Friday, August 10, 2001 1:59 PM > To: Thomas, Nick > Cc: 'cos...@li...' > Subject: RE: More project direction > > > Like I said, don't worry about collecting the data that the router > gathers. Right now, we need a database schema that will save the > configuration data. That data is a collection of SAA source routers, SAA > target devices, SAA operations, and SAA collectors. A collector is a > source + target + operation (not always as with DNS, DHCP, and HTTP > operations). > > So, for instance, the Sources table in the database will have something > like: > > ID, Name, Address, Community, SNMP_Version, SAA_Version, IOS_Version, > Status > > Joe Clarke > > On Fri, 10 Aug 2001, Thomas, Nick wrote: > > > Okay to build a DB that works for us instead of against us I need an > example > > of some sort. I was looking at that stuff on Cisco's page about SAA, but > I > > still don't understand what kind of info will be reported back to the > > collector. If you could send me some data. I have setup my cisco to do > > some simple test, but I am not sure how to collect it. Looks like this is > > my next step :) > > > > Nick > > > > -----Original Message----- > > From: Joe Clarke [mailto:ma...@ma...] > > Sent: Friday, August 10, 2001 1:13 PM > > To: cos...@li... > > Cc: Thomas, Nick > > Subject: More project direction > > > > > > Don't worry about the data for write now. Let's focus on creating the > > collectors. We will need a simple DB schema for this. The DB will > > contain tables for each object: > > > > Sources > > Targets > > Operations* > > Collectors > > > > The '*' for Operations is where things could get a little more complex. > > Should we create a table for each type of operation? Each operation will > > have different properties. > > > > Joe Clarke > > > > On Fri, 10 Aug 2001, Thomas, Nick wrote: > > > > > I will start working on a package that will let us call the different > SNMP > > > calls. I can also start working on a mysql DB if you can fill me in how > > > what data will be stored in it. I understand the Network side of what > the > > > rtr commands are doing, but I don't understand the bucket history and > life > > > history, or how to actually look at the data that the router should be > > > generating. > > > > > > Nick > > > > > > -----Original Message----- > > > From: Joe Clarke [mailto:ma...@ma...] > > > Sent: Friday, August 10, 2001 1:04 PM > > > To: Thomas, Nick > > > Subject: Re: your mail > > > > > > > > > Nick, I've removed the ping stuff from the API. It wasn't really needed > > > anyway. I've also done the crypto change from ECB to CBC. > > > > > > Joe > > > > > > On Thu, 9 Aug 2001, Thomas, Nick wrote: > > > > > > > Joe, > > > > > > > > Hey I just wanted to write and find out when we could talk about > > what > > > we > > > > want to do with SAAConfig and where we want to start. I will be > moving > > > this > > > > Weekend so I may not be around, but I have started looking into the > SAA > > > this > > > > thing is great, I can't believe I never saw it. :) I have some ideas > > and > > > > the like. > > > > > > > > Talk to Ya Later, > > > > Nick > > > > > > > > > > > > > > > > > > > > _______________________________________________ > Cosi-nms-saa-dev mailing list > Cos...@li... > http://lists.sourceforge.net/lists/listinfo/cosi-nms-saa-dev > > |
|
From: Thomas, N. <Th...@me...> - 2001-08-10 19:01:38
|
Oops I didn't even see what you were trying to say. I understand completely now. -----Original Message----- From: Joe Clarke [mailto:ma...@ma...] Sent: Friday, August 10, 2001 1:59 PM To: Thomas, Nick Cc: 'cos...@li...' Subject: RE: More project direction Like I said, don't worry about collecting the data that the router gathers. Right now, we need a database schema that will save the configuration data. That data is a collection of SAA source routers, SAA target devices, SAA operations, and SAA collectors. A collector is a source + target + operation (not always as with DNS, DHCP, and HTTP operations). So, for instance, the Sources table in the database will have something like: ID, Name, Address, Community, SNMP_Version, SAA_Version, IOS_Version, Status Joe Clarke On Fri, 10 Aug 2001, Thomas, Nick wrote: > Okay to build a DB that works for us instead of against us I need an example > of some sort. I was looking at that stuff on Cisco's page about SAA, but I > still don't understand what kind of info will be reported back to the > collector. If you could send me some data. I have setup my cisco to do > some simple test, but I am not sure how to collect it. Looks like this is > my next step :) > > Nick > > -----Original Message----- > From: Joe Clarke [mailto:ma...@ma...] > Sent: Friday, August 10, 2001 1:13 PM > To: cos...@li... > Cc: Thomas, Nick > Subject: More project direction > > > Don't worry about the data for write now. Let's focus on creating the > collectors. We will need a simple DB schema for this. The DB will > contain tables for each object: > > Sources > Targets > Operations* > Collectors > > The '*' for Operations is where things could get a little more complex. > Should we create a table for each type of operation? Each operation will > have different properties. > > Joe Clarke > > On Fri, 10 Aug 2001, Thomas, Nick wrote: > > > I will start working on a package that will let us call the different SNMP > > calls. I can also start working on a mysql DB if you can fill me in how > > what data will be stored in it. I understand the Network side of what the > > rtr commands are doing, but I don't understand the bucket history and life > > history, or how to actually look at the data that the router should be > > generating. > > > > Nick > > > > -----Original Message----- > > From: Joe Clarke [mailto:ma...@ma...] > > Sent: Friday, August 10, 2001 1:04 PM > > To: Thomas, Nick > > Subject: Re: your mail > > > > > > Nick, I've removed the ping stuff from the API. It wasn't really needed > > anyway. I've also done the crypto change from ECB to CBC. > > > > Joe > > > > On Thu, 9 Aug 2001, Thomas, Nick wrote: > > > > > Joe, > > > > > > Hey I just wanted to write and find out when we could talk about > what > > we > > > want to do with SAAConfig and where we want to start. I will be moving > > this > > > Weekend so I may not be around, but I have started looking into the SAA > > this > > > thing is great, I can't believe I never saw it. :) I have some ideas > and > > > the like. > > > > > > Talk to Ya Later, > > > Nick > > > > > > > > > > > > |
|
From: Joe C. <ma...@ma...> - 2001-08-10 18:59:23
|
Like I said, don't worry about collecting the data that the router gathers. Right now, we need a database schema that will save the configuration data. That data is a collection of SAA source routers, SAA target devices, SAA operations, and SAA collectors. A collector is a source + target + operation (not always as with DNS, DHCP, and HTTP operations). So, for instance, the Sources table in the database will have something like: ID, Name, Address, Community, SNMP_Version, SAA_Version, IOS_Version, Status Joe Clarke On Fri, 10 Aug 2001, Thomas, Nick wrote: > Okay to build a DB that works for us instead of against us I need an example > of some sort. I was looking at that stuff on Cisco's page about SAA, but I > still don't understand what kind of info will be reported back to the > collector. If you could send me some data. I have setup my cisco to do > some simple test, but I am not sure how to collect it. Looks like this is > my next step :) > > Nick > > -----Original Message----- > From: Joe Clarke [mailto:ma...@ma...] > Sent: Friday, August 10, 2001 1:13 PM > To: cos...@li... > Cc: Thomas, Nick > Subject: More project direction > > > Don't worry about the data for write now. Let's focus on creating the > collectors. We will need a simple DB schema for this. The DB will > contain tables for each object: > > Sources > Targets > Operations* > Collectors > > The '*' for Operations is where things could get a little more complex. > Should we create a table for each type of operation? Each operation will > have different properties. > > Joe Clarke > > On Fri, 10 Aug 2001, Thomas, Nick wrote: > > > I will start working on a package that will let us call the different SNMP > > calls. I can also start working on a mysql DB if you can fill me in how > > what data will be stored in it. I understand the Network side of what the > > rtr commands are doing, but I don't understand the bucket history and life > > history, or how to actually look at the data that the router should be > > generating. > > > > Nick > > > > -----Original Message----- > > From: Joe Clarke [mailto:ma...@ma...] > > Sent: Friday, August 10, 2001 1:04 PM > > To: Thomas, Nick > > Subject: Re: your mail > > > > > > Nick, I've removed the ping stuff from the API. It wasn't really needed > > anyway. I've also done the crypto change from ECB to CBC. > > > > Joe > > > > On Thu, 9 Aug 2001, Thomas, Nick wrote: > > > > > Joe, > > > > > > Hey I just wanted to write and find out when we could talk about > what > > we > > > want to do with SAAConfig and where we want to start. I will be moving > > this > > > Weekend so I may not be around, but I have started looking into the SAA > > this > > > thing is great, I can't believe I never saw it. :) I have some ideas > and > > > the like. > > > > > > Talk to Ya Later, > > > Nick > > > > > > > > > > > > |
|
From: Thomas, N. <Th...@me...> - 2001-08-10 18:40:43
|
Okay to build a DB that works for us instead of against us I need an example of some sort. I was looking at that stuff on Cisco's page about SAA, but I still don't understand what kind of info will be reported back to the collector. If you could send me some data. I have setup my cisco to do some simple test, but I am not sure how to collect it. Looks like this is my next step :) Nick -----Original Message----- From: Joe Clarke [mailto:ma...@ma...] Sent: Friday, August 10, 2001 1:13 PM To: cos...@li... Cc: Thomas, Nick Subject: More project direction Don't worry about the data for write now. Let's focus on creating the collectors. We will need a simple DB schema for this. The DB will contain tables for each object: Sources Targets Operations* Collectors The '*' for Operations is where things could get a little more complex. Should we create a table for each type of operation? Each operation will have different properties. Joe Clarke On Fri, 10 Aug 2001, Thomas, Nick wrote: > I will start working on a package that will let us call the different SNMP > calls. I can also start working on a mysql DB if you can fill me in how > what data will be stored in it. I understand the Network side of what the > rtr commands are doing, but I don't understand the bucket history and life > history, or how to actually look at the data that the router should be > generating. > > Nick > > -----Original Message----- > From: Joe Clarke [mailto:ma...@ma...] > Sent: Friday, August 10, 2001 1:04 PM > To: Thomas, Nick > Subject: Re: your mail > > > Nick, I've removed the ping stuff from the API. It wasn't really needed > anyway. I've also done the crypto change from ECB to CBC. > > Joe > > On Thu, 9 Aug 2001, Thomas, Nick wrote: > > > Joe, > > > > Hey I just wanted to write and find out when we could talk about what > we > > want to do with SAAConfig and where we want to start. I will be moving > this > > Weekend so I may not be around, but I have started looking into the SAA > this > > thing is great, I can't believe I never saw it. :) I have some ideas and > > the like. > > > > Talk to Ya Later, > > Nick > > > > > > |
|
From: Joe C. <ma...@ma...> - 2001-08-10 18:13:24
|
Don't worry about the data for write now. Let's focus on creating the collectors. We will need a simple DB schema for this. The DB will contain tables for each object: Sources Targets Operations* Collectors The '*' for Operations is where things could get a little more complex. Should we create a table for each type of operation? Each operation will have different properties. Joe Clarke On Fri, 10 Aug 2001, Thomas, Nick wrote: > I will start working on a package that will let us call the different SNMP > calls. I can also start working on a mysql DB if you can fill me in how > what data will be stored in it. I understand the Network side of what the > rtr commands are doing, but I don't understand the bucket history and life > history, or how to actually look at the data that the router should be > generating. > > Nick > > -----Original Message----- > From: Joe Clarke [mailto:ma...@ma...] > Sent: Friday, August 10, 2001 1:04 PM > To: Thomas, Nick > Subject: Re: your mail > > > Nick, I've removed the ping stuff from the API. It wasn't really needed > anyway. I've also done the crypto change from ECB to CBC. > > Joe > > On Thu, 9 Aug 2001, Thomas, Nick wrote: > > > Joe, > > > > Hey I just wanted to write and find out when we could talk about what > we > > want to do with SAAConfig and where we want to start. I will be moving > this > > Weekend so I may not be around, but I have started looking into the SAA > this > > thing is great, I can't believe I never saw it. :) I have some ideas and > > the like. > > > > Talk to Ya Later, > > Nick > > > > > > |
|
From: Joe C. <ma...@ma...> - 2001-08-10 14:59:00
|
Right now, the idea is to create a configurator. I already have some sample MRTG configs that will work with the data. A responder would be a cool idea, but I think Cisco might have a problem with it. I'd like to extend things into a program the collects data, and reports on it, but most SAA users I talk to now want something (cheap) that can configure the collectors. It's a pain to do it by hand, and buying IPM can cost up to $20,000. Joe Clarke On Fri, 10 Aug 2001, Thomas, Nick wrote: > Should we move this over to the mailing list? > > I need to understand one thing. I went and read some more about SAA. I now > have a vague understanding of what it does. I know we are going to create a > Interface to "Config" SAA, but I have a few questions. Do we want to create > a program that will store the information from a SAA and do various things > with it(trend analysis, etc...)? Or are we going to actually create a > reponder for another router to talk to? > > Nick > -----Original Message----- > From: Joe Clarke [mailto:ma...@ma...] > Sent: Thursday, August 09, 2001 11:04 PM > To: Thomas, Nick > Subject: Re: your mail > > > Cool, let me know when will be good for you. I have been thinking about > redoing the cipher code in CBC mode instead of ECB. However, this is > small in the grand scheme of things. What we need to do is start to > design the database schema, and start writing code to setup the various > collectors. I think we should start with the ipEcho operation, and build > off of that. > > Joe > > On Thu, 9 Aug 2001, Thomas, Nick wrote: > > > Joe, > > > > Hey I just wanted to write and find out when we could talk about what > we > > want to do with SAAConfig and where we want to start. I will be moving > this > > Weekend so I may not be around, but I have started looking into the SAA > this > > thing is great, I can't believe I never saw it. :) I have some ideas and > > the like. > > > > Talk to Ya Later, > > Nick > > > > > > |
|
From: Thomas, N. <Th...@me...> - 2001-08-07 17:31:15
|
Hello everyone. Just want to post a message make sure I was on the list. Talk to ya all later. Nick -----Original Message----- From: cos...@li... [mailto:cos...@li...] Sent: Tuesday, August 07, 2001 12:30 PM To: Thomas, Nick Subject: Welcome to the "Cosi-nms-saa-dev" mailing list Welcome to the Cos...@li... mailing list! Welcome to SAA-DEV. Please make sure you are a registered COSI developer and have CVS up and running. Checkout the saaconfig project from COSI CVS to get started. To post to this list, send your email to: cos...@li... General information about the mailing list is at: http://lists.sourceforge.net/lists/listinfo/cosi-nms-saa-dev If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://lists.sourceforge.net/lists/options/cosi-nms-saa-dev/thomasn%40memori alhealthsource.com You can also make such adjustments via email by sending a message to: Cos...@li... with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: blah If you forget your password, don't worry, you will receive a monthly reminder telling you what all your lists.sourceforge.net mailing list passwords are, and how to unsubscribe or change your options. There is also a button on your options page that will email your current password to you. You may also have your password mailed to you automatically off of the Web page noted above. |