[j-nsp] MS-DPC and netflow.

bit gossip bit.gossip at chello.nl
Thu Jul 15 10:18:41 EDT 2010


Hi Peter,
this should be working
Thanks,
Luca.

forwarding-options {
    sampling {
        input {
            rate 1;
            run-length 0;
        }
        family inet {
            output {
                flow-server 1.1.1.66 {
                    port 3333;
                    autonomous-system-type origin;
                    no-local-dump;
                    version9 {
                        template {
                            PIPPO_V9;
                        }
                    }
                }
                flow-server 1.1.1.194 {
                    port 3333;
                    autonomous-system-type origin;
                    no-local-dump;
                    version9 {
                        template {
                            PIPPO_V9;
                        }
                    }
                }
                interface sp-2/0/0 {
                    source-address 1.1.1.1;
                }
            }
        }
        family inet6 {
            output {
                flow-server 1.1.1.66 {
                    port 3333;
                    autonomous-system-type origin;
                    no-local-dump;
                    version9 {
                        template {
                            PIPPO-INET6-V9;
                        }
                    }
                }                       
                flow-server 1.1.1.194 {
                    port 3333;
                    autonomous-system-type origin;
                    no-local-dump;
                    version9 {
                        template {
                            PIPPO-INET6-V9;
                        }
                    }
                }
                interface sp-2/0/0 {
                    source-address 1.1.1.1;
                }
            }
        }
    }
}
services {
    flow-monitoring {
        version9 {
            template PIPPO_V9 {
                ipv4-template;
            }
            template PIPPO-INET6-V9 {
                ipv6-template;
            }
        }
    }
}

On Thu, 2010-07-15 at 10:58 +0200, Peter Krupl wrote:
> Hi guys,
> 
> Im at a complete loss regarding this issue. And the documentation at J is
> a bad mess of RE based flow sampling, and M series stuff mixed with 
> MX/MS-DPC stuff.
> 
> 1 .Do I need to prep the MS-DPC more than ? :
> aggregated-devices {
>     ethernet {
>         device-count 1;
>     }
> }
> fpc 1 {
>     pic 0 {
>         adaptive-services {
>             service-package layer-3;
>         }
>     }
>     pic 1 {
>         adaptive-services {
>             service-package layer-3;
>         }
>     }
> }
> network-services ip;
> 
> 2. Anyone has a working configuration for netflow v9 on MX ? 
> 
> 3. And what is the purpose of the source address statement under / forwarding-options/output/interface,
> where is this address used ?
> 
> Im running 10.1R1.8 and the suggested config in the docs for 10.1 gives me a 
> deprecated warning.
> 
> Here is my config:
> 
> forwarding-options {
>     sampling {
>         input {
>             family inet {
>                 rate 1;
>             }
>             family mpls {
>                 rate 1;
>             }
>         }
>         output { ## Warning: 'output' is deprecated
>             flow-inactive-timeout 30;
>             flow-active-timeout 60;
>             flow-server 213.173.238.14 {
>                 port 9990;
>                 version9 {
>                     template {
>                         ip-template;
>                     }
>                 }
>             }
>             interface sp-1/0/0 {
>                 source-address 1.1.1.1;
>             }
>         }
>     }
> }
> 
> Kind regards,
> Peter Krupl
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp




More information about the juniper-nsp mailing list