problem with NAM for Cat 6500s?

[Microbyte]

Does anybody have issues with NAM for either v3.1(1a) or v3.3(1)?

Any input would help!
Thanks!

Microbyte

 

[BuckWeet]

what kind of issues.

we're running htem but haven't utilized them enough to know of any problems..

 

[Microbyte]

Issues like the system reboots when it is view from web interface.
or
the system crashes when same command is entered repeatedly numerous times.

Stuff like that.

I like to know if other users are having such problems, or others. And how often.

Microbyte

 

[BuckWeet]

hrm, can't say we've had those problems

what chassis/supervisor/ios are you running??

we're running them in 6509-E with sup720-3bxl, 12.2.18SXD


BuckWEet

 

[vipergg]

We haven't seen many issues with whatever code we are running now but early on we had all sorts of problems , in my personal opinion they were the biggest waste of money we have ever done . They don't work worth a darn , ours when we try to use the packet capture capability it takes like 30 minutes for it to come back with the decoded packets and generally just slow as death . Much better off getting a standalone packet analyzer like Observer 10 and then using span .

 

[Microbyte]

Buck:
We are using 6509 with Sup-2. I get to you on IOS version later on if I can. That switch far away from me right now.


Viper:
I was afraid of that. Packet capture process taking 30 minutes is rediculous. Link you, I would go for stand-alone packet analyzer as well but we already own one NAM version 3.1(1a). Now the question comes to this - does it create/fix more bugs by upgrading it to version 3.3(1)? Would that long packet capture time be shorten a bit?

Microbyte

 

[vipergg]

Don't know about that version , if you have a CCO account you can probably take a look and see if there are any known bugs .