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

XR 7+: get_lldp_neighbors_detail query only the NodeTable #1404

Merged
merged 1 commit into from
Mar 26, 2021

Conversation

mirceaulinic
Copy link
Member

It looks like in newer XR systems, just querying LLDP at the top level
throws this error:

xml-schema[oper]:> walkdata LLDP
%MGBL-SCHBRO-7-GET : [xml-schema] While fetching object LLDP.GlobalLLDP.LLDPInfo the following error occurred:
Invalid argument

And over the XML mode:

XML> <?xml version="1.0" encoding="UTF-8"?><Request MajorVersion="1" MinorVersion="0"><Get><Operational><LLDP></LLDP></Operational></Get></Request>
<?xml version="1.0" encoding="UTF-8"?>
<Response MajorVersion="1" MinorVersion="0">
    <Get ErrorCode="0x43679000" ErrorMsg="&apos;XML Service Library&apos; detected the &apos;warning&apos; condition &apos;An error was encountered in the XML beneath this operation tag&apos;" ItemNotFound="true">
        <Operational>
            <LLDP MajorVersion="1" MinorVersion="1">
                <GlobalLLDP>
                    <LLDPInfo ErrorCode="0x16" ErrorMsg="Invalid argument"/>
                </GlobalLLDP>
            </LLDP>
        </Operational>
    </Get>
    <ResultSummary ErrorCount="1"/>
</Response>

Re-scoping the request to gather explicitly the NodeTable not only that
reduces the reply whenever there's more available under the LLDP
operational level, but also prevents us from bumping into this error,
while returning the neighbours as required.

It looks like in newer XR systems, just querying LLDP at the top level
throws this error:

```
xml-schema[oper]:> walkdata LLDP
%MGBL-SCHBRO-7-GET : [xml-schema] While fetching object LLDP.GlobalLLDP.LLDPInfo the following error occurred:
Invalid argument
```

And over the XML mode:

```
XML> <?xml version="1.0" encoding="UTF-8"?><Request MajorVersion="1" MinorVersion="0"><Get><Operational><LLDP></LLDP></Operational></Get></Request>
<?xml version="1.0" encoding="UTF-8"?>
<Response MajorVersion="1" MinorVersion="0">
    <Get ErrorCode="0x43679000" ErrorMsg="&apos;XML Service Library&apos; detected the &apos;warning&apos; condition &apos;An error was encountered in the XML beneath this operation tag&apos;" ItemNotFound="true">
        <Operational>
            <LLDP MajorVersion="1" MinorVersion="1">
                <GlobalLLDP>
                    <LLDPInfo ErrorCode="0x16" ErrorMsg="Invalid argument"/>
                </GlobalLLDP>
            </LLDP>
        </Operational>
    </Get>
    <ResultSummary ErrorCount="1"/>
</Response>
```

Re-scoping the request to gather explicitly the NodeTable not only that
reduces the reply whenever there's more available under the LLDP
operational level, but also prevents us from bumping into this error,
while returning the neighbours as required.
@ktbyers
Copy link
Contributor

ktbyers commented Mar 24, 2021

LGTM

@mirceaulinic mirceaulinic merged commit 183432d into develop Mar 26, 2021
@mirceaulinic mirceaulinic deleted the lldp-xr7 branch March 26, 2021 12:08
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.

None yet

2 participants