Ismo

Comments

  • Title should be chanced to show what supervisor is connected to that switch. Core itself doesn't tell much about "intelligence" of switch. Those commands doesn't work in new supervisors, sup-2T for example. You have to use flexible netflow and flow records.
  • Title should be chanced to show what supervisor is connected to that switch. That's because those commands doesn't work in new supervisors, 2T for example. You have to use flexible netflow and flow records.
  • About Cisco thing you mentioned in the beginning... Cisco supports netflow the best way in the market. We have pure Cisco environment, thats the reason I choose NTA and not some RMON hardware-software-combination. So right tools to right use. But that's not necessarily SW:'s fault. Shouldn't use complain to other network…
  • I think I found the settings in NCM settings -> comparison criteria.
  • I'll answer to myself... I made alert triggers that depend on custom properties that makes groups for devices (for example printers, servers, switches, wan routers etc.) Lots of job to do before everything is ready, but I think that's the only and best way to do that. It would be great to be able to adjust triggers…
  • I got this problem: UDT loses device information
  • I don't know about best practice, but here's how I use Orion. I use Orion to several needs, I would say: 1. Normal Orion use, to see what's going on in network. 2. To save historical traffic data to see trends and when network should be updated, which of course mean big DB (about 70 GB now). 3. As alert system for device…
  • Another thing: If I make a white list considering every workstation in our company to get alerts from real rogue computers, I would have to use wildcards in computer dns name. Is it possible? Didn't get % or * to work... I found answer to this one. Didn't notice "custom" option...
  • This probably doesn't help in your case, but I had this interesting issue couple of days ago: I had email alert as: 1. [Type] (=custon property) is equal to NetworkDevice 2. OR [Type] is equal to AP 3. Status is equal to Down I tried to change alert from custom property to group like: 1. Group Name is equal to…
  • Solved. I had to create a record. Normally "netflow-original" should do the job, but in Supervisor 2T there is no such a command at all. It's replaced with "platform-original" and I think it doesn't work correctly with NTA. Platform-original configuration sends netflow to NTA but Orion doesn't understand it, I don't know…
  • I'm getting this event: You have not enabled NetFlow data export on 192.168.200.1 device. For more information, see "Enabling NetFlow and NetFlow Data Export (NDE) on Cisco Catalyst Switches" in the Support - Product Documentation area of www.solarwinds.com. This must be some kind of bug in NTA, because clearly server…
  • That's quite confusing for me too. I always have to deep think from which side I should seek for some anomalies on traffic to find them. Can't remember what does it means: Do I look it from interface point of view or network point of view. ...Is ingress traffic actually the traffic coming to INTERFACE (means out from sub…
  • I don't understand what are you trying to do. What do you mean by compilation?
  • We have couple of 3750G's running 12.2(58)SE2 and I'm getting port information as should. So no problems. (No names, but that's because we have no DNS available in that network. IP's and MAC's shows normally. )
  • Solved! I recently moved SQL to another server, and forgot to tell new server path to flow storage database. Stupid me!
  • I think I found a reason, I had chosen enable level and enable password. Tricky case because that authentication actually already gives me enable level access, so I thought that "enable level" should be chosen. But apparently CLI password is enough. Hopefully SW explains it better in future. Now decription field explains…