BRIDE-MIB dot1dTpFdbTable parsing between 6.1.3 and 6.3.1
Posted: 28 Jul 2008 14:39
I've been writing some perl scripts to mimic the Locator function in OmniVista, and I came across something interesting. It looks like Alcatel-Lucent made some changes in how the BRIDGE-MIB dot1dTpFdbTable is accessed between earlier AOS versions and the latest 6.3.1 code.
It looks like anything in anything before 6.3.1, the dot1dTpFdbTable dot1dTpFdbPort value is the same is ifIndex, which is nice. That makes it easy to find out what ifIndex a MAC addresses is learned on. In the 6.3.1 code, the value is some arbitrary number (not the ifIndex). Actually, it turns out that the number is (slot number) * 128 + (port number - 1) .
In any event, I found that I can go back to the dot1dBasePort table to get the ifIndex value from the dot1dTpFdbPort value. (Which is probably what I should be doing anyway).
It looks like anything in anything before 6.3.1, the dot1dTpFdbTable dot1dTpFdbPort value is the same is ifIndex, which is nice. That makes it easy to find out what ifIndex a MAC addresses is learned on. In the 6.3.1 code, the value is some arbitrary number (not the ifIndex). Actually, it turns out that the number is (slot number) * 128 + (port number - 1) .
In any event, I found that I can go back to the dot1dBasePort table to get the ifIndex value from the dot1dTpFdbPort value. (Which is probably what I should be doing anyway).