How to add/reconfig network switches and ports

[ssax]

Hmm, that's interesting. I'll take a look. Please PM me your the service configs from a working one and one that has the "UNKNOWN: could not retrive ifdescr/iftype snmpkey - 0-0" error so that I can debug.

[ssax]

Also, PM me your /etc/mrtg/conf.d/switchname.cfg file.

[CFT6Server]

Any luck? I also had a thought. This might be a suggestion for later versions of this wizard. Since we have duplicate alias names, it would be nice to match existing service name to the port description/alias so that it knows which interface to update, rather than creating a new one or having to manually update it. Unless the wizard can actually use the full "title" name that MRTG has for that port. Seems like port index would be the key identifier, but the name could be dynamic.

Here's what I mean:

Wizard/SNMPwalk - noticed duplication descriptions

Duplicate Service Name.JPG

What I do here is end up manually append the Port name to the Service Description:
ie. U: Uplink Port Channel 31 / U: Uplink Port Channel 32

If you review the MRTG configuration file, it actually shows a full description that is unique.

Code: Select all

Title[fptpwxucs01-a_369098782]: port-channel31 U: Uplink  -- fptpwxucs01-A

 <tr>
  <td>Description:</td>
  <td>port-channel31 U: Uplink </td>
</tr>

So if MRTG sets it according to the Description, then it would eliminate the duplicate name and when the wizard is re-ran, it can also pickup the port properly rather than having me manually match the service description to the server name.

Thoughts?

Currently this service check shows up as this with my manual name change

Uplink.JPG

[ssax]

That's a great idea, I'll put in a feature request for it.

It looks like MRTG is causing the issue because in the MRTG config files it is showing the proper case. I'll have to dig more into where/why it is converting it to lowercase.

[ssax]

This should take care of the case differences:

switch.zip

[ssax]

The other error is going to be quite a bit trickier. The problem is that the port name/description has special characters removed by MRTG so it doesn't have the actual name. Do you use any underlines in your naming scheme?

[CFT6Server]

I think we have underlines in our naming as well. UCS Domain _1 FI-B. I will give the new switch wizard a try and report back.

[CFT6Server]

One more question: Will this update redo the underline MRTG configuration when it is re-ran? For example, an existing port is configured and when we re-run this wizard, and some threshold changed, will anything affect the MRTG configuration of that port? Also if a new port is detected, will it update the MRTG configuration also?

[ssax]

Yes, it overwrites the current configuration you have.

I'm not sure I'm going to be able to get this to work with the current MRTG implementation. The underscores will be a problem.

I'll take a look on Monday though and give you a definitive answer before it's sent off to the devs.

[CFT6Server]

Just a note, when you run MRTG a second time, it seems like it updates the XI configurations (ie. add new ports and updates thresholds etc.), but it doesn't update the actual MRTG configuration file. So for any new interface, it is just report that it cannot find the RRD file. I think this could be inherit to how current MRTG works? or is it suppose to overwrite the configuration file?