Hi,
I'm a newbee. I have Solarwinds Engineers toolset and Cirrus. What is required to make Orion 8.1 work in a cisco environment? I am aware of Netflow, but have never had the need to implement it. Our company is basically to large campus's with about 700 employees. Any comments are appreciated,..thanks.
Hi,I'm a newbee. I have Solarwinds Engineers toolset and Cirrus. What is required to make Orion 8.1 work in a cisco environment? I am aware of Netflow, but have never had the need to implement it. Our company is basically to large campus's with about 700 employees. Any comments are appreciated,..thanks.
All you need is SNMP enabled on your devices and allow pings/snmp requests to those devices as well. Pretty simple stuff.BB
Hhhmm,...So why all the talk of Netflow? Does Orion need Netflow to produce real0time data?
thanks
No, Orion does not need NetFlow to produce real time data. The NetFlow module allows users to see NetFlow data in the routers. NetFlow reveals traffic information. Orion can tell you how much bandwidth is being used by an interface. NetFlow tells you how that bandwidth is being used.
Do(s) and Don't(s) while your waiting for the "Executing SQL File: onCoreDatabaseScheme" to complete during the initial run of the Configuration Wizard...
Don't:
Hold your breath...
Freakout...
Cancel the Configuration Wizard (even though it looks like the Config Wizard is not responding)
Do:
Make sure there is allot of available free space on your SQL server (at least 3x the total size of your NetPerfMon.mdf & .ldf files)
RDP into your DB server and watch the tempdb.mdf file grow and grow and grow... (\Program Files\Microsoft SQL Server\MSSQL\Data\tempdb.mdf) Once it stops growing the table splits and DB re-org is almost complete.
Bring up perfmon and watch the avg disk queue length sit well above 100% for a while, once it starts dropping below 100 consistently the table split(s) are almost done
These are just a few suggestions to ease the wait... if you have a large DB
PS: It's going to sit on this screen for a long time (don't let your session timeout!)