quote:Originally posted by aLTeReGoI just bought this product and I'm very disappointed that the port descriptions on my Cat6500 series switches are not populated automatically. As I have well over 100 ports per 6500 this is a huge pain in the ass.How about before we trick this product out with all sorts of cool new features like syslog and such, we nail down the basics first.
quote:Originally posted by Network_Guru
quote:Originally posted by webcrawlr quote:Originally posted by aLTeReGoI just bought this product and I'm very disappointed that the port descriptions on my Cat6500 series switches are not populated automatically. As I have well over 100 ports per 6500 this is a huge pain in the ass.How about before we trick this product out with all sorts of cool new features like syslog and such, we nail down the basics first.
quote:Originally posted by iunderwoJust a comment in here on the anti-IIS comment...The problem isn't with IIS per-se. The problem lies with the default security model being very lax, and with admins who don't keep up with server patch levels. To dismiss the program on the grounds that it runs on a Microsoft platform is faulty logic, because any platform can be open to exploit.The beauty of Orion is that you don't need to be an expert to set it up and start collecting data.// Ian Underwood - Service Management// Level 3 Communications
quote:Originally posted by angusIn order of preference:1. Port monitoring with predefined stuff for protocols like SNMP,http, https, sql and DNS2. Netflow3. Policy based approach to alert definition. The polices can then be applied to the monitored objects. Unless I am missing someting, the current method is tedius and cumbersome and would the chances of alert "noise".Nice to haveDynamic baselining - there is a radical change in traffic profile between work hours and non off hours. This creates a problem for us when setting alerts. Suggestions workarround are welcommed
quote:Originally posted by gonzajohI don't agree I'm afraid. In order of importance IMO....1. Custom Mib reporting / alerting2. TRAP HANDLING (can't believe they missed that one!!)3. Device GroupingOne could argue that NPM is a NETWORK performance monitor (up to L3 OSI). What you are requesting is monitoring APPLICATIONS (ports and services) - not the same thing.I agree however that it would be a 'nice to have' - and in fact, should not be too difficult to achieve
quote:Better device inventory report (serial numbers)
quote:(Suppress Alert until X)We reboot equipment from time to time and it's a real pain that everyone's pager/cell phone has to go off because someone rebooted a server. It would be nice to have a method of saying "do not alert unless the node has been down for at least "x" ammount of time".
quote:Originally posted by rixSign if you think the biggest feature improvement to Orionshould be service/port monitoring ala WUG.I personally think it would be incredible then.Strength in numbers, make yourself heard.maybe v7.5Thanks,-Network Janitor(time to empty the bit bucket)
quote:Originally posted by aSquaredSidetrack a little. Has anyone here overcome the issue of ORION not able to monitor Service ports. Do you have any alternatives to this?
quote:Originally posted by 2020 quote:Originally posted by aSquaredSidetrack a little. Has anyone here overcome the issue of ORION not able to monitor Service ports. Do you have any alternatives to this?