cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Peevandepee
Engaged Sweeper

There is no indication in what VLAN an interface is for Extreme Switches.
While with our HPE-switches we have.
Is this something related to OID and how can we see the VLAN the interface resides in for Extreme switches?

Extreme

Peevandepee_0-1689321036789.png

HPE

Peevandepee_1-1689321109681.png

 

4 REPLIES 4
edconant
Engaged Sweeper

Just checking in on this.  we just deployed our first Extreme switches and having the VLAN identification is very helpful.  The info is there because in ExtremeCloud IQ Site Engine, the VLANs are listed by port and that is scanning using SNMP albeit v3.

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

Here are some troubleshooting steps you might want to try:

  • Make sure that your Lansweeper installation is on the latest version. If needed, you can update to the latest Lansweeper version by following the steps in this guide: https://www.lansweeper.com/knowledgebase/updating-your-installation/
  • When your Lansweeper installation is up to date, click the Rescan Asset option on the left-hand side of the switch's web page. And wait for the Last successful scan date to update. Verify if the VLAN information is now available.
  • If the info is still missing, check which data is retrieved from the switch by running the InterfaceScanDebugger tool. The tool can be found here https://www.dropbox.com/s/x1fmhvw7baqlhug/InterfaceScanDebugger.7z?dl=0
    • Run the tool directly from your Lansweeper scanning server to your switch with the same SNMP credentials you entered within Lansweeper. Check if the same information is returned in the tool as in Lansweeper.

The interfacescandebugger (mentioned above) can simulate how Lansweeper scans a device. If this tool also does not return the VLANs, it's possible that the device does not provide this information through the standard SNMP scan.  As Lansweeper is not doing an SNMP Walk but an SNMP GET, we scan specific OIDs to get this information. So if the VLAN OID is located in a non-standard location on the Asset, we will not be able to retrieve it with our standard SNMP scan. 

Alternatively, if the standard SNMP scan routine does not retrieve this information, we recommend trying our custom OID scanning to obtain the VLAN info. More information on custom OID scanning is in the KB article below:



Thx, but all of the suggested steps don't work.

Peevandepee_5-1689583706949.png

Peevandepee_6-1689583748409.png

with extra OID-rule:

Peevandepee_8-1689584062069.png

Peevandepee_7-1689584035813.png

 


result Extreme:

Peevandepee_0-1689582717149.png

result HPE:

Peevandepee_1-1689582873420.png

Custom OID (SNPM GET) is no option > we have stacks with +200 interfaces

Peevandepee_4-1689583590697.png

Peevandepee_2-1689583214247.png

Interface 4:8 (4008) has several VLANs:

Peevandepee_3-1689583340498.png

 

 

 

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

The "NOSUCHINSTANCE" errors indeed confirm that the data is not present in the queries OIDs, and as such Lansweeper will not be able to retrieve this data.