Routing

last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  IPFIX mpls-traffic from MX80

    Posted 04-30-2015 05:30

    Hello!

    After migrate bras to MPLS-backbone, MX80 cant send ipfix-statistics  OUTPUT subscribers traffic  to collector.

    But IN traffic to subscriber good send to flow-collector.

     

     

     

    bras> show version
    Hostname: BRAS
    Model: mx5-t
    JUNOS Base OS boot [12.3R8.7]
    JUNOS Base OS Software Suite [12.3R8.7]
    JUNOS Kernel Software Suite [12.3R8.7]
    JUNOS Crypto Software Suite [12.3R8.7]
    JUNOS Packet Forwarding Engine Support (MX80) [12.3R8.7]
    JUNOS Online Documentation [12.3R8.7]
    JUNOS Routing Software Suite [12.3R8.7]
    
    bras> show services accounting flow inline-jflow
      Flow information
        TFEB Slot: 0
        Flow Packets: 1087219872600, Flow Bytes: 1156730277987742
        Active Flows: 475193, Total Flows: 24461525508
        Flows Exported: 24456424476, Flow Packets Exported: 4892091134
        Flows Inactive Timed Out: 24234446760, Flows Active Timed Out: 226627770
    
    bras> show configuration forwarding-options
    sampling {
        instance {
            JFLOW {
                input {
                    rate 1;
                }
                family inet {
                    output {
                        flow-server 192.168.147.6 {
                            port 10031;
                            version-ipfix {
                                template {
                                    IPv4-TEMPLATE;
                                }
                            }
                        }
                        inline-jflow {
                            source-address 192.168.62.22;
                            flow-export-rate 2;
                        }
                    }
                }
            }
        }
    }
    
    bras> show configuration interfaces xe-0/0/0
    mtu 9000;
    unit 0 {
        family inet {
            filter {
                input MARK_MCAST;
            }
            sampling {
                input;
                output;
            }
            address 192.168.62.22/30;
        }
        family mpls;
    }
    
    bras>
    
    bras>
    
    bras> show route 0.0.0.0 table inet.0
    
    inet.0: 6609 destinations, 6615 routes (6609 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both
    
    0.0.0.0/0          *[Static/5] 7w6d 14:31:14
                          to table MPLS-L3VPN_NAT.inet.0
                        [BGP/170] 4w6d 16:46:09, localpref 120, from 172.16.16.2
                          AS path: I, validation-state: unverified
                        > to table MPLS-L3VPN_NAT.inet.0
                        [BGP/170] 4w4d 14:09:55, localpref 100, from 172.16.16.6
                          AS path: I, validation-state: unverified
                        > to 192.168.62.21 via xe-0/0/0.0, label-switched-path MX_Butovo>M10
    
    bras> show route table MPLS-L3VPN_NAT.inet.0 extensive 0.0.0.0
    
    MPLS-L3VPN_NAT.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
    0.0.0.0/0 (2 entries, 1 announced)
    TSI:
    KRT in-kernel 0.0.0.0/0 -> {indirect(1048577)}
            *BGP    Preference: 170/-121
                    Route Distinguisher: 172.16.16.2:4
                    Next hop type: Indirect
                    Address: 0x4b264e0
                    Next-hop reference count: 6
                    Source: 172.16.16.2
                    Next hop type: Router, Next hop index: 1387
                    Next hop: 192.168.62.21 via xe-0/0/0.0 weight 0x1, selected
                    Label-switched-path Butovo>M9
                    Label operation: Push 22
                    Label TTL action: prop-ttl
                    Session Id: 0x18
                    Protocol next hop: 172.16.16.2
                    Push 22
                    Indirect next hop: 47c82c4 1048577 INH Session ID: 0x36
                    State: <Secondary Active Int Ext ProtectionCand>
                    Peer AS: 29069
                    Age: 1w4d 20:57:52      Metric2: 1
                    Validation State: unverified
                    Task: BGP_29069_29069.172.16.16.2+179
                    Announcement bits (2): 0-RT 1-KRT
                    AS path: I
                    AS path: Recorded
                    Communities: target:29069:202
                    Import Accepted
                    VPN Label: 22
                    Localpref: 120
                    Router ID: 172.16.16.2
                    Primary Routing Table bgp.l3vpn.0
                    Indirect next hops: 1
                            Protocol next hop: 172.16.16.2 Metric: 1
                            Push 22
                            Indirect next hop: 47c82c4 1048577 INH Session ID: 0x36
                            Indirect path forwarding next hops: 1
                                    Next hop type: Router
                                    Next hop: 192.168.62.21 via xe-0/0/0.0 weight 0x1
                                    Session Id: 0x18
                            172.16.16.2/32 Originating RIB: inet.3
                              Metric: 1                       Node path count: 1
                              Forwarding nexthops: 1
                                    Nexthop: 192.168.62.21 via xe-0/0/0.0
             BGP    Preference: 170/-101
                    Route Distinguisher: 172.16.16.6:4
                    Next hop type: Indirect
                    Address: 0x447782c
                    Next-hop reference count: 2
                    Source: 172.16.16.6
                    Next hop type: Router, Next hop index: 2395
                    Next hop: 192.168.62.21 via xe-0/0/0.0 weight 0x1, selected
                    Label-switched-path MX_Butovo>M10
                    Label operation: Push 17, Push 321808(top)
                    Label TTL action: prop-ttl, prop-ttl(top)
                    Session Id: 0x18
                    Protocol next hop: 172.16.16.6
                    Push 17
                    Indirect next hop: 47c8588 1048596 INH Session ID: 0x37
                    State: <Secondary Int Ext ProtectionCand>
                    Inactive reason: Local Preference
                    Peer AS: 29069
                    Age: 1w4d 20:57:52      Metric2: 2
                    Validation State: unverified
                    Task: BGP_29069_29069.172.16.16.6+179
                    AS path: I
                    AS path: Recorded
                    Communities: target:29069:202
                    Import Accepted
                    VPN Label: 17
                    Localpref: 100
                    Router ID: 172.16.16.6
                    Primary Routing Table bgp.l3vpn.0
                    Indirect next hops: 1
                            Protocol next hop: 172.16.16.6 Metric: 2
                            Push 17
                            Indirect next hop: 47c8588 1048596 INH Session ID: 0x37
                            Indirect path forwarding next hops: 1
                                    Next hop type: Router
                                    Next hop: 192.168.62.21 via xe-0/0/0.0 weight 0x1
                                    Session Id: 0x18
                            172.16.16.6/32 Originating RIB: inet.3
                              Metric: 2                       Node path count: 1
                              Forwarding nexthops: 1
                                    Nexthop: 192.168.62.21 via xe-0/0/0.0
    
    bras>
    
    
    
    
    
    bras> show configuration services
    flow-monitoring {
        version-ipfix {
            template IPv4-TEMPLATE {
                flow-active-timeout 600;
                flow-inactive-timeout 60;
                template-refresh-rate {
                    seconds 30;
                }
                option-refresh-rate {
                    packets 50000;
                    seconds 30;
                }
                ipv4-template;
            }
        }
    }
    
    bras>

     



  • 2.  RE: IPFIX mpls-traffic from MX80
    Best Answer

    Posted 05-08-2015 06:04

    Hello,

     


    @radeon-1 wrote:

    Hello!

    After migrate bras to MPLS-backbone, MX80 cant send ipfix-statistics  OUTPUT subscribers traffic  to collector.

    But IN traffic to subscriber good send to flow-collector.

     

     

     


    If Your OUT traffic arrives at the jflow-sampling router as MPLS-encapsulated IPv4, then inline IPFIX support for MPLS sampling is a roadmap item, please contact Your JNPR SE for exact planned JUNOS release.

    Inline Jflowv9 for MPLS sampling is supported from JUNOS 13.2R1.

    HTH

    Thanks

    Alex