Juniper / open-nti

Open Network Telemetry Collector build with open source tools
Apache License 2.0
231 stars 93 forks source link

qfx5100 stops sending data after upgrading from junos version 17.x to18.x and later - before it was working fine #276

Closed kikoshiro closed 2 years ago

kikoshiro commented 3 years ago

Hello,

prior to Junos 18.x my qfx5100 was sending data to opennti and grafa was showing nice graphs. After upgrading to junos 18.x, and later, no data is going to be sent from the qfx5100 to opennti anymore. I checked with tcpdump the opennti-server. When I enter show analytics status on the clie, i get:

junos 18.x

{master:0}
admin@qfxa3> show analytics status
error: peer_daemon: bad daemon: analyticsd

master:0}
admin@qfxa3> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfxa3
Model: qfx5100-48s-6q
Junos: 18.4R3.3
JUNOS Base OS Software Suite [18.4R3.3]
JUNOS Base OS boot [18.4R3.3]
JUNOS Crypto Software Suite [18.4R3.3]
JUNOS Crypto Software Suite [18.4R3.3]
JUNOS Online Documentation [18.4R3.3]
JUNOS Kernel Software Suite [18.4R3.3]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [18.4R3.3]
JUNOS Routing Software Suite [18.4R3.3]
JUNOS jsd [i386-18.4R3.3-jet-1]
JUNOS SDN Software Suite [18.4R3.3]
JUNOS Enterprise Software Suite [18.4R3.3]
JUNOS Web Management Platform Package [18.4R3.3]
JUNOS Openconfig [18.4R3.3]
JUNOS py-base-i386 [18.4R3.3]
JUNOS py-extensions-i386 [18.4R3.3]
JUNOS Host Software [18.4R3.3]

Junos 17.x:

{master:0}
admin@qfxa3> show analytics status
Traffic monitoring status is auto
Traffic monitoring pollng interval : 2 seconds
Queue monitoring status is auto
Queue monitoring polling interval : 50 milliseconds
Latency high threshold : 1000000 nanoseconds
Latency low threshold : 100 nanoseconds

Interface     Traffic    Queue      Queue depth             Latency
            Statistics Statistics    threshold             threshold
                                   High       Low        High      Low
                                      (bytes)            (nanoseconds)
ge-0/0/0   enabled    enabled     n/a        n/a        2300      20
ge-0/0/2    disabled   disabled    n/a        n/a        1000000   100
et-0/0/48   enabled    enabled     n/a        n/a        2300      20
et-0/0/49   disabled   disabled    n/a        n/a        1000000   100

{master:0}
admin@qfxa3> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfxa3
Model: qfx5100-48s-6q
Junos: 17.4R3.16
JUNOS Base OS boot [17.4R3.16]
JUNOS Base OS Software Suite [17.4R3.16]
JUNOS Crypto Software Suite [17.4R3.16]
JUNOS Crypto Software Suite [17.4R3.16]
JUNOS Online Documentation [17.4R3.16]
JUNOS Kernel Software Suite [17.4R3.16]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [17.4R3.16]
JUNOS Routing Software Suite [17.4R3.16]
JUNOS jsd [i386-17.4R3.16-jet-1]
JUNOS SDN Software Suite [17.4R3.16]
JUNOS Enterprise Software Suite [17.4R3.16]
JUNOS Web Management Platform Package [17.4R3.16]
JUNOS py-base-i386 [17.4R3.16]
JUNOS py-extensions-i386 [17.4R3.16]
JUNOS Host Software [17.4R3.16]

Analytics-Config:

show configuration services analytics
export-profiles {
    default {
        stream-format json;
        interface {
            information;
            statistics {
                traffic;
                queue;
            }
            status {
                link;
            }
        }
        system {
            information;
            status {
                traffic;
                queue;
            }
        }
    }
}
resource-profiles {
    default {
        queue-monitoring;
        traffic-monitoring;
        latency-threshold high 2300 low 20;
    }
}
resource {
    system {
        polling-interval {
            traffic-monitoring 2;
            queue-monitoring 50;
        }
    }
    interfaces {
        ge-0/0/0 {
            resource-profile default;
        }
        ge-0/0/2 {
            resource-profile default;
        }
        et-0/0/48 {
            resource-profile default;
        }
        et-0/0/49 {
            resource-profile default;
        }
    }
}
collector {
    address 192.168.200.188 {
        port 50020 {
            transport udp {
                export-profile default;
            }
        }
    }
}

So far i couldnt find any information why and what changed at junos 18.x regarding the analytics-feature.

davidmeeker commented 2 years ago

Ran into this same issue, opened a case with the TAC. Juniper advises this feature was removed as of 18.1.

kikoshiro commented 2 years ago

too sad