Cisco Switches - LLD of Trunk Ports

[jasonwirz]

Hello,

I am migrating our company from What's Up to Zabbix. We have several thousand Cisco switches of varying models. My goal is to have zabbix automatically discover only the trunk ports. From what I have gathered so far, this needs to be done inside the discovery section of a template. I have not succeeded in finding any existing threads that explain the setup in enough detail.

The OID I need to use is 1.3.6.1.4.1.9.5.1.9.3.1.8. This will return a value of 1 for trunking and 2 for not trunking. The end of the OID also lines up with the interface. Where I'm stuck is the logic to tell Zabbix to monitor the interfaces that respond with 1

Example SNMPwalk response for interfaces 23-26 of a Cisco switch.


SNMPv2-SMI::enterprises.9.5.1.9.3.1.8.1.23 = INTEGER: 2
SNMPv2-SMI::enterprises.9.5.1.9.3.1.8.1.24 = INTEGER: 2
SNMPv2-SMI::enterprises.9.5.1.9.3.1.8.1.25 = INTEGER: 1
SNMPv2-SMI::enterprises.9.5.1.9.3.1.8.1.26 = INTEGER: 1



Thanks in advance for any assistance.

[jlopes]

Hello jasonwirz,
I got it too but there is a problem with this same OID that you are using. Please, make this test too and share the result. When I shutdown the interface trunk, the last value change to Number 2 like access mode. Really strange!!!

1. I created one Discovery Rule.
2. After that I created two item prototypes. One to discovery all trunk interfaces(Work fine). Other to get the OperationalStatus, if up or down.
3. I created one Trigger Prototype where I checkd if the Item Descovered 1 is like 1(Trunk) and Dicovered 2 is like 2(Down) then shows a Disaster.

I know that the logic is ok, but didn't work. When I checked the Latest Data, the last value from thare Interface trunk setted as shutdown changed to 2(Access power).

So, lets share more experiences my email is [email protected].

[allexpetrov]

Items aren't discovering anything, the Discovery Rule does.
Show your item and trigger.
BTW, when you shutdown what, the port or you change interface mode from being a trunk to the access? Zabbix isn't a magic stick and does not provide you with the metric which doesn't exist. The software only fetches the value from the host, so it is a question for Cisco - why do they perform such a trick.

I believe every experience sharing regarding Zabbix should be here, on community pages because Zabbix is an Open Source product.

Regards,
Alex!

[jlopes]

Cisco Switches - LLD of Trunk Ports

Hi alex petrov,
Thank you for your help. As I said before, I have created two Prototype Itens, one that get the interfaces mode[ Trunk(1) or Access(2) ] in according to the jasonwirz's tip, and other that get the Operational Status from interfaces.

A Trigger Prototype verify constantly this following Logic:

If the Interface Mode is Trunk(1) and the Operational Status is Down(2), then register a Disaster Event.

The problem is that when the network interface in mode trunk from the cisco switch is changed to down(Off, Disabled or UTP Cable removed, for example), the Interface Mode is changed to Access(2). So due to this the Disaster event never run.

Refer in attached the evidences.
Note: Change the Extension from file "Evidences (2).pdf" to "Evidences (2).pptx"

Best regards

[jasonwirz]

jlopes

I've confirmed you are correct that the status does indeed change to non-trunking when the interface is down. Unfortunately this probably means zabbix will stop monitoring that port on the next round of discovery. Would you be willing to share your template? I'm finding it difficult to find good examples for LLD. I may just discover all interfaces on the switch and find a way to trigger on just the trunk ports going down.

Thanks
Jason

[ravshan]

Hi,
How to available only trunk ports from Huawei switche on zabbix server