port-stack for Mikrotik

You can filter by ifType = l2vlan to ensure it is a vlan

This just a suggestion to be able to see the relation of a vlan and physical port correctly as how it is used on Huawei and others.

This is not port stacks.
You propose to make vlan association with ports by mac addresses.

But really in this idea bad in all ways.
No way be sure that port is vlan (you can rename port in device config), mac address is very bad ident for any purpose.

Apologies, i mean MAC address of VLAN interfaces are taken from the physical port MAC address, so it would be ideal to match MAC Address of VLAN interface and physical port and to match them together as a port stack

e.g:

eth1 - 00:01:02:03:04:01

eth2 - 00:01:02:03:04:02

eth3 - 00:01:02:03:04:03

eth4 - 00:01:02:03:04:04

vlan100 - 00:01:02:03:04:02

vlan101 - 00:01:02:03:04:02{}

by checking mac address above, you would know vlan100 and vlan101 interfaces are sub interfaces of eth2, hence add them to a port-stack.

It's not at all clear what you mean.

You need to assume we do not have the device you have, and know nothing about it at all.

General questions and device support can be discussed in our Discord channel, click here to join.

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

  If device not support SNMP version 2c, replace -v2c with -v1.

• If you have problems with discovery or poller processes, please do and attach these debugs:

  ./discovery.php -d -h <device>

  ./poller.php -d -h <device>

• additionally attach device and/or vendor specific MIB files

This comment is added automatically.