Extreme Networks

Nealo · ‎10-17-2019

Hello,

I’ve been trying to get a list of the VLANs on a VSP device.

The device is a VSP-8404 with 6.1.6.0 firmware, and the XMC version is 8.2.4.55.

I know of two ways to get them.

The first one would be to send a CLI command with emc_cli, and get the output, then filter it to get a list.

cli_output = emc_cli.send("show vlan basic").getOutput().encode('ascii', 'ignore')

The second one is using emc_nbi and sending a query to get the VLANs ID

var_query = '''query{network{device(ip: "DeviceIP"){deviceData{vlans{vid}}}}}'''
var_result = emc_nbi.query(var_query)
vlans_id = var_result['network']['device']['deviceData']['vlans']

But, I noticed that using NBI doesn’t give me the same result as using CLI.

With CLI, I get this list : 1, 2, 49, 170, 180, 190, 4049, 4051, 4052

With NBI, I get this list : 1, 2, 49, 170, 180, 666, 4049

The NBI is not correct, as I don’t get the 190, 4051 and 4052, and it adds the 666.

I don’t understand why this difference is present. Is there something I’m doing wrong ?

Thanks a lot for the help

rbrt · ‎10-17-2019

Hey everyone,

I had the same problem with the NBI and, together with GTAC, found out that refreshing the device with a mutation and querying the right context within the NBI solves it - at least for EXOS and EOS. Try this (replace the IP with the management IP of the switch in question):

mutation {
  network {
    rediscoverDevices(input: {devices: [{ipAddress: "10.0.0.1"}]}) {
      status
      message
    }
  }
}

After firing this mutation, wait for 15 minutes (or check the Operations view) and try the following GraphiQL query (again, replace the IP).

query {
  network {
    deviceVlans(ip: "10.0.0.1") {
      name
      vid
      primaryIp
      netmask
      ipForward
    }
  }
}

See https://link.medium.com/m5yqUU15y0 for an in-depth story on that topic.

View solution in original post

Nealo · ‎10-18-2019

Thanks a lot for all those information !

rbrt · ‎10-18-2019

There is a lengthy, open GTAC case regarding API behaviour, which I condensed in the article I shared above. To summarize it for the context question: The API is still in development and deviceVlans is the right context to use for now. Out of the case, from Engineering:

In a nutshell, the query is for deviceData which internally is cached mainly for provisioning/ZTP and should not technically be used for reading device info

As far as I know there is a CR to remove the deviceData/vlans context from the GraphQL API, targeted for XMC 8.4 or 8.5. So this issue will be “solved” soon.

Nealo · ‎10-18-2019

I have a question about that request.

The output is different if I use

network {deviceVlans {vid or

network {device {deviceData {vlans {vid

Shouldn’t both give the same result ?

Thanks

rbrt · ‎10-18-2019

The mutation above just triggers a refresh device within XMC, so no changes are done to either the device or XMC.

Extreme Networks

GraphiQL doesn't give a correct list of VLANs ID

GraphiQL doesn't give a correct list of VLANs ID