Re: [c-nsp] netflow real AS instead of uplink provider?

On 15 June 2016 at 14:36, Lukas Tribus wrote: >> 4.3.1 is quite crusty. If you need to stay in 4.3.x perhaps 4.3.4. I would >> avoid 5.3.3. > > About to deploy 5.3.3 (+ SMUs) here. Can you elaborate the problems in 5.3.3? 4.3.4 is a dire image and should be avoided like

Re: [c-nsp] netflow real AS instead of uplink provider?

> 4.3.1 is quite crusty.  If you need to stay in 4.3.x perhaps 4.3.4.  I would > avoid 5.3.3. About to deploy 5.3.3 (+ SMUs) here. Can you elaborate the problems in 5.3.3? Thanks, Lukas ___ cisco-nsp mailing list cisco-nsp@puck.nether.net

Re: [c-nsp] netflow real AS instead of uplink provider?

I would consider upgrading to at least 5.3.1 + SMUs or 6.0.1. I seem to recall a number of issues back in the 4.3.x images. 4.3.1 is quite crusty. If you need to stay in 4.3.x perhaps 4.3.4. I would avoid 5.3.3. - Jared > On Jun 15, 2016, at 9:09 AM, Nemeth Laszlo wrote:

Re: [c-nsp] netflow real AS instead of uplink provider?

Hello Yes, it is in my BGP session. Laszlo 2016-06-15 15:04 időpontban Christian Kildau ezt írta: > Do you have "bgp attribute-download" under router bgp ? > > Best regards, > Chris > > On Wed, Jun 15, 2016 at 2:57 PM, Nemeth Laszlo wrote: > >> Hello >> >> I tried

Re: [c-nsp] netflow real AS instead of uplink provider?

Do you have "bgp attribute-download" under router bgp ? Best regards, Chris On Wed, Jun 15, 2016 at 2:57 PM, Nemeth Laszlo wrote: > Hello > > I tried to get the source or destianton AS of a flow from our ASR9001 > (iosxr 4.3.1) router. > > But i got this: > >

[c-nsp] netflow real AS instead of uplink provider?

Hello I tried to get the source or destianton AS of a flow from our ASR9001 (iosxr 4.3.1) router. But i got this: RP/0/RSP0/CPU0:asr0#sh flow monitor netflow-monitor cache location 0/0/CPU IPV4SrcAddr IPV4DstAddr L4SrcPort L4DestPort BGPDstPeerAS BGPSrcPeerAS BGPNextHopV4