[ixpmanager] update-l2database.pl not updating database

Brian Thompson brian.thompson at iovation.com
Wed Sep 25 20:54:58 IST 2013


My understanding of Juniper is without the dot is layer 2 switching and
with the dot is layer 3 routing.

Hopefully this is an easy fix for Nick in his script to adjust.

*Brian Thompson*
Senior Infrastructure Engineer // Senior Second Guesser

Direct: 503.943.6779
Mobile: 503.707.9018 // Twitter: iovation
*www.iovation.com*



On Wed, Sep 25, 2013 at 12:48 PM, Barry O'Donovan <barry.odonovan at inex.ie>wrote:

>
>
> On 25/09/13 20:32, Brian Thompson wrote:
>
>> No I was trying to give as much detail as possible.
>>
>
> Cool, my misunderstanding.
>
>
>  [1] http://git.io/dmWA6g  updates switchports table to ge-0/0/0
>>
>
>  [2] http://git.io/7ZPmUw  updates macaddress table discovers
>> macaddresses at ge0/0/0.0
>>
>
> I think you have these references wrong?
>
> Both of these use the same backend code and neither touch the macaddress
> table. I suspect you mean:
>
> http://git.io/dmWA6g and http://git.io/7ZPmUw updates switchports table
> to ge-0/0/0
>
> Where as:
>
> updates macaddress table discovers macaddresses at ge0/0/0.0?
>
>
> Now, looking at the SNMP dump you posted previously (
> https://gist.github.com/**pdxmaverick/6597601<https://gist.github.com/pdxmaverick/6597601>),
> it looks like Juniper are reporting ifDescriptions (switchport.name) such
> as:
>
> .1.3.6.1.2.1.2.2.1.2.602 = STRING: "ge-0/0/2"
> .1.3.6.1.2.1.2.2.1.2.603 = STRING: "ge-0/0/2.0"
>
> and ifNames (switchport.ifName) as:
>
> .1.3.6.1.2.1.31.1.1.1.1.602 = STRING: "ge-0/0/2"
> .1.3.6.1.2.1.31.1.1.1.1.603 = STRING: "ge-0/0/2.0"
>
>
> It's not important that these are the same but it is important that these
> appear to be two references to the same port?
>
> I suspect that when adding these switches in IXP Manager you're also
> looking at a port entry for ge-0/0/2 and ge-0/0/2.0?
>
>
>
>  - Barry
>
>
> PS: if anyone is wondering why ifDesc is confusingly named 'name' in the
> switchport database, it's an unfortunate legacy that would be a boat load
> of work to change.
>
>
> ______________________________**_________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/**listinfo/ixpmanager<https://www.inex.ie/mailman/listinfo/ixpmanager>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20130925/7ec98dd7/attachment.html>


More information about the ixpmanager mailing list