If it was made apparent, could you point to any public documentation that 
states that? I've scoured Cisco's site, google, and mail archives, and can't 
find any mention (other than specific caveats) that state that NDE and hardware 
assisted nat are not supported on the same interface. In fact, it took TAC 
almost two weeks of escalation before anyone would state it wasn't supported 
and they couldn't find any documentation that stated that. 

As far as speaking to a TME, I work in small trading firm. We don't have the 
luxury of long, involved RFP with detailed descriptions or time to work with a 
TME to discuss every detail of every configuration we use. We expect if a 
vendor advertise features, that they should work, except when they are 
documented (like caveats). Having two major features (and they are both listed 
as major features in Cisco's marketing literature for the RSP720) that won't 
coexist should be pointed out very obviously in their literature. 



-----Original Message-----
From: Dale W. Carder [mailto:dwcar...@wisc.edu] 
Sent: Saturday, August 27, 2011 5:13 PM
To: Matthew Huff
Cc: 'cisco-nsp@puck.nether.net'
Subject: Re: [c-nsp] WARNING: Netflow Data Export & Hardware assisted NAT not 
supported on 76xx/65xx on the same interface


On Aug 26, 2011, at 11:25 AM, Matthew Huff wrote:

> Last winter we purchased a pair of 7606 routers to use out at the NYSE colo 
> facility. We connect via a 1gb fiber to the SFTI LCN for market data and FIX 
> traffic. We fully expected to be able to use hardware assisted NAT and NDE to 
> monitor the traffic. The netflow output we get is random, sporadic and very 
> incomplete. After dealing with our Sales team and TAC, we have finally got 
> them to admit that it doesn't work when NAT and NDE are configured on the 
> same interface.

I seem to remember that being made apparent when the sup720 was first 
announced, and I also think it was presented in the cat6k architecture
session at networkers when I went in 2005.

Sounds to me that you really need a better sales team that can engage 
the right TME.

Dale

_______________________________________________
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to