[c-nsp] netflow accouting incompatibilities (on vaccess if)

Gert Doering gert at greenie.muc.de
Tue Jun 7 17:36:26 EDT 2005


Hi,

On Tue, Jun 07, 2005 at 11:16:43PM +0200, Hakan Lindholm wrote:
> >On Tue, Jun 07, 2005 at 10:45:23PM +0200, Gert Doering wrote:
> >>ist there a document somewhere that describes under which conditions
> >>netflow exporting suddenly can go inactive on virtual-access interfaces?
> >
> >... on a related tangent: is there any IOS available that has
> >"ip flow egress"?
> 
> You may be looking for 12.3(11)T, or 12.4 :)
> Listed at 
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hnf_c/nfb_rmap.htm

Thanks, that document is very helpful.

Especially the section about "12.2(14)S having netflow subinterface
support", didn't know that, and ran into that barrier quite recently
on a 12.2(18)S router - the fun part is that it is accepted only
with "ip flow ingress" syntax, and not with "ip route-cache flow"
(while the physical interface understands "ip route-cache flow" just
fine).  Using "ip flow ingress" it works... nice.

Intersting, though, that neither 12.0S nor 12.2S get the "ip netflow
egress" feature.  12.0S has "MPLS egress netflow", so one would expect
"ip flow egress" to show up there eventually as well...

> I can't say 12.3T nor 12.4 are cans of worms neither, sorry :(

The usual problem with "T"error releases...

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de


More information about the cisco-nsp mailing list