Hi,
have a look at the rule “Network interface and switch port discovery”. You can select index, alias or description as service name. And of course read this excellent blog article written by Alex Wilms:
The problem is another. It’s not showing the aliases.
I access the switches by ssh, and do a “nsaliasshow” and see all the aliases. There are specific names for each port. Not that strange number.
Is there something wrong with our Brocade switches?
I’m not sure about FC ports, but have a look at the inventory of the device. In the interface table you will find the index/description/alias of each interface, so you can easily see what to expect from the interface check.
Hi,
you have to setup the inventory rule: Setup > Do hardware/software inventory. After activating the changes you should get a new service called Check_MK HW/SW Inventory. In the the action menu of this service there should be an additional icon:
Why? is there any company in the planet that do that?
We never used hard zoning.
Alias. You use aliases. Always. They are related to the WWN. You can change the fibre, between ports, and it keeps running perfectly. Why would you set a name to a port? That’s not every useful.
Guys… there is no way to get the alias by default with Check_MK then?
@aeckstein , exactly!!
“Zoning is not related to portname”. Never said better before.
The magic of Aliases, is that are “target wwn” related. You can change the fibre 20 times, 20 different ports. The zone still works, perfectly. No port bond. Never.
just because you can change your physical ports with wwpn zoning as often as you want to in a fabric, doesn’t mean it’s reality in practice.
For documentation, troubleshooting, and stability reasons fabrics tend to be more static.
But this discussion is out of scope of checkmk monitoring.
It is the way it is, portnames are used for the service name and imho that is not a bad decision.