<div dir="ltr">Nick,<div><br></div><div>First I brought up my installation from 3.5.4 to 3.6.5 one version at a time.</div><div><br></div><div>After checking out the im-juniper-ex-sflow-support fork I tested the script.</div>
<div><br></div><div><div>root@portal:/usr/local/ixp# /usr/local/bin/<a href="http://update-l2database.pl">update-l2database.pl</a> --debug --vlan 998</div><div>DEBUG: processing NWAX-Inband</div><div>SNMPWALK Problem for .1.3.6.1.2.1.2.2.1.2 on xxxxxx@NWAX-Inband: No response from remote host "NWAX-Inband" at /usr/share/perl5/Net_SNMP_util.pm line 1851</div>
<div><span class="" style="white-space:pre"> </span>Net_SNMP_util::snmpwalk_flg('xxxxx@NWAX-Inband', undef, .1.3.6.1.2.1.2.2.1.2) called at /usr/share/perl5/Net_SNMP_util.pm line 786</div><div><span class="" style="white-space:pre"> </span>Net_SNMP_util::snmpwalk('xxxxxx@NWAX-Inband', .1.3.6.1.2.1.2.2.1.2) called at /usr/local/bin/<a href="http://update-l2database.pl">update-l2database.pl</a> line 245</div>
<div><span class="" style="white-space:pre"> </span>main::snmpwalk2hash('NWAX-Inband', 'xxxxxxx', .1.3.6.1.2.1.2.2.1.2) called at /usr/local/bin/<a href="http://update-l2database.pl">update-l2database.pl</a> line 165</div>
<div><span class="" style="white-space:pre"> </span>main::trawl_switch_snmp('NWAX-Inband', 'xxxxxxx', 998) called at /usr/local/bin/<a href="http://update-l2database.pl">update-l2database.pl</a> line 75</div>
<div>cannot read ifDescr from NWAX-Inband at /usr/local/bin/<a href="http://update-l2database.pl">update-l2database.pl</a> line 165.</div></div><div><br></div><div>I see there is a name resolution issue. After resolving it. I get...</div>
<div><br></div><div><div>root@portal:/usr/local/ixp# /usr/local/bin/<a href="http://update-l2database.pl">update-l2database.pl</a> --debug --vlan 998</div><div>DEBUG: processing NWAX-Inband</div><div>cannot read dot1dBasePortIfIndex from NWAX-Inband at /usr/local/bin/<a href="http://update-l2database.pl">update-l2database.pl</a> line 166.</div>
</div><div><br></div><div>NWAX-Inband is a Cisco WS-C4948 we have added to handle our copper and peering.<br></div><div><br></div><div>So it looks like the code isn't detecting that it is a Cisco.</div><div><br></div>
<div>Thanks, Brian</div><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Dec 14, 2013 at 9:05 PM, Brian Thompson <span dir="ltr"><<a href="mailto:brian.thompson@iovation.com" target="_blank">brian.thompson@iovation.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Yes tomorrow morning</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Dec 14, 2013 3:16 PM, "Nick Hilliard" <<a href="mailto:nick@inex.ie" target="_blank">nick@inex.ie</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 25/09/2013 22:12, Nick Hilliard wrote:<br>
> without the dot is the physical port. With the dot is the L2 or L3<br>
> interface. If the number after the dot is zero, then it's a non .1q-tagged<br>
> port. If the number after the dot is >= 0, then that refers to the logical<br>
> unit of the interface, which will often (but not necessarily) be the same<br>
> as the vlan tag.<br>
<br>
Brian,<br>
<br>
Can you check out commit fa302a3<br>
(<a href="https://github.com/inex/IXP-Manager/commit/fa302a30bc" target="_blank">https://github.com/inex/IXP-Manager/commit/fa302a30bc</a>) on github to see if<br>
this fixes the problem.<br>
<br>
Nick<br>
<br>
<br>
_______________________________________________<br>
INEX IXP Manager mailing list<br>
<a href="mailto:ixpmanager@inex.ie" target="_blank">ixpmanager@inex.ie</a><br>
<a href="https://www.inex.ie/mailman/listinfo/ixpmanager" target="_blank">https://www.inex.ie/mailman/listinfo/ixpmanager</a><br>
</blockquote></div>
</div></div></blockquote></div><br></div></div>