Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix find for system uptime element #1675

Merged

Conversation

mayuresh82
Copy link
Contributor

Certain junos platforms with more than 1 RE return the system uptime information in a different structure. Here is an example from a QFX5100:

<rpc-reply xmlns:junos="http://xml.juniper.net/junos/20.2R0/junos">
    <multi-routing-engine-results>

        <multi-routing-engine-item>

            <re-name>localre</re-name>

            <system-uptime-information xmlns="http://xml.juniper.net/junos/20.2R0/junos">
                <current-time>
                    <date-time junos:seconds="1655920775">2022-06-22 10:59:35 PDT</date-time>
                </current-time>
                <time-source> NTP CLOCK </time-source>
                <system-booted-time>
                    <date-time junos:seconds="1639095204">2021-12-09 16:13:24 PST</date-time>
                    <time-length junos:seconds="16825571">27w5d 17:46</time-length>

This change will enable the match for current-time/date-time to work for multi levels deep while still also working for single RE outputs.

@mirceaulinic mirceaulinic merged commit ea13a89 into napalm-automation:develop Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants