Junos
Junos

Flow monitoring on MX204

[ Edited ]
‎01-10-2019 06:58 PM

Hello,

 

I am having trouble getting flow monitoring to work properly on Juniper MX204. After applying configuration on the router, I can see about 6Mb/s of flow (which is too less) on flow server. It supposes to be Gb/s. I would much appreciate if anyone could help and advise if the following config is correct or not.

 

set forwarding-options sampling input rate 1024
set forwarding-options sampling instance NFSEN1 input rate 1024
set forwarding-options sampling instance NFSEN1 family inet output flow-server 172.16.1.112 port 2055
set forwarding-options sampling instance NFSEN1 family inet output flow-server 172.16.1.112 version9 template NFSEN1
set forwarding-options sampling instance NFSEN1 family inet output inline-jflow source-address 192.168.1.1

set services flow-monitoring version9 template NFSEN1 ipv4-template
set chassis fpc 0 sampling-instance NFSEN1
set chassis fpc 0 inline-services flow-table-size ipv4-flow-table-size 5

set interfaces et-0/0/0 unit 0 family inet sampling input
set interfaces et-0/0/0 unit 0 family inet sampling output

Also, from Juniper document, they mention as below

NOTE: Monitoring Services PICs, AS PICs, and Multiservices PICs must be mounted on an Enhanced Flexible PIC Concentrator (FPC) in an M Series or T Series router.
Multiservices DPCs installed in Juniper Networks MX Series 5G Universal Routing Platforms support the same functionality, with the exception of the passive monitoring and flow-tap features.

Does this mean Juniper MX  Seriees 5G does not support passive monitoring and flow-tap features?

 

Thanks,

 

Seyma
JNCIP-ENT, SEC, SP
4 REPLIES 4
Junos

Re: Flow monitoring on MX204

‎01-10-2019 09:28 PM

Hi Seyma,

 

In this case rate it is configured 1024 which mean 1 out of 1024 packets will be sampled.Rate indicates the sampling rate.

Jflow exports the Flow records to collector. Are you doing high flow scale and the flows are exporting to collector in less rate?

 

Are you seeing any errors on MX?

 

  • show services accounting status inline-jflow fpc-slot 3
  • show services accounting flow inline-jflow fpc-slot 3
  • show services accounting errors inline-jflow fpc-slot 3

 

 

Regards,
Rahul

Junos

Re: Flow monitoring on MX204

[ Edited ]
‎01-10-2019 10:44 PM

Hello Rahul,

 

Rate 1024 is what I get from our previous router and it was working fine with that value. So you mean if I lower the rate value, more flow would be sent to collector, is that what you suggested?

 

Here is the output from some show commands

> show services accounting status inline-jflow fpc-slot 0  
  Status information
    FPC Slot: 0
    IPV4 export format: Version9, IPV6 export format: Not set
    VPLS export format: Not set, MPLS export format: Not set
    IPv4 Route Record Count: 725062, IPv6 Route Record Count: 0, MPLS Route Record Count: 0
    Route Record Count: 725062, AS Record Count: 218394
    Route-Records Set: Yes, Config Set: Yes
    Service Status: PFE-0: Steady 
    Using Extended Flow Memory?: PFE-0: No 
    Flex Flow Sizing ENABLED?: PFE-0: No 
    IPv4 MAX FLOW Count: 1831940, IPv6 MAX FLOW Count: 1024
    VPLS MAX FLOW Count: 1024, MPLS MAX FLOW Count: 1024

> show services accounting flow inline-jflow fpc-slot 0  
  Flow information
    FPC Slot: 0
    Flow Packets: 256950401, Flow Bytes: 189918607240
    Active Flows: 36406, Total Flows: 219539779
    Flows Exported: 479584424, Flow Packets Exported: 96384248
    Flows Inactive Timed Out: 105479689, Flows Active Timed Out: 113646563
    Total Flow Insert Count: 105893216

    IPv4 Flows:
    IPv4 Flow Packets: 256950401, IPv4 Flow Bytes: 189918607240
    IPv4 Active Flows: 36406, IPv4 Total Flows: 219539779
    IPv4 Flows Exported: 479584424, IPv4 Flow Packets exported: 96384248
    IPv4 Flows Inactive Timed Out: 105479689, IPv4 Flows Active Timed Out: 113646563
    IPv4 Flow Insert Count: 105893216

> show services accounting errors inline-jflow fpc-slot 0 
  Error information
    FPC Slot: 0
    Flow Creation Failures: 1891898
    Route Record Lookup Failures: 344604, AS Lookup Failures: 344604
    Export Packet Failures: 1024
    Memory Overload: No, Memory Alloc Fail Count: 0

    IPv4:
    IPv4 Flow Creation Failures: 1891898
    IPv4 Route Record Lookup Failures: 344604, IPv4 AS Lookup Failures: 344604
    IPv4 Export Packet Failures: 1024

Is there any missing point you could advise?

 

Thanks and regards,

 

 

 

Seyma
JNCIP-ENT, SEC, SP
Junos

Re: Flow monitoring on MX204

‎01-11-2019 04:20 AM

 Hi,

 

That throughput for flow packets is reasonable for that sampling rate.

Normally you adjust the sampling rate depending on the flow appliance license limit. So yes, if your flow analysis platform can handle it then you can make the sampling more aggressive.

 

So in as much as you want to see more flow packets be aware that if the flow rate license is exceeded then those packets would be aggressively dropped as well.

 

Regards,

Francis.

Junos

Re: Flow monitoring on MX204

‎01-11-2019 04:30 AM

Hello,

Please see if this helps https://puck.nether.net/pipermail/juniper-nsp/2019-January/036920.html

HTH

Thx
Alex

_____________________________________________________________________

Please ask Your Juniper account team about Juniper Professional Services offerings.
Juniper PS can design, test & build the network/part of the network as per Your requirements

+++++++++++++++++++++++++++++++++++++++++++++

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !