[F10-nsp] Re: force10-nsp Digest, Vol 6, Issue 4
Keith ONeill
keith at pando.com
Fri Feb 10 13:26:57 EST 2006
Hi Andy,
I have a couple of S50s on the way in to start messing with them. What
are your plans for them? Do you need to use 10gb links?
I wasnt planning on using the 10gb links, I was going to create 4 gig-e
lags instead and have them connect to our E300s.
Anyone have anythoughts on this?
force10-nsp-request at puck.nether.net wrote:
>Send force10-nsp mailing list submissions to
> force10-nsp at puck.nether.net
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://puck.nether.net/mailman/listinfo/force10-nsp
>or, via email, send a message with subject or body 'help' to
> force10-nsp-request at puck.nether.net
>
>You can reach the person managing the list at
> force10-nsp-owner at puck.nether.net
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of force10-nsp digest..."
>
>
>Today's Topics:
>
> 1. Re: port numbler/mac address (Ron Lewkiewicz)
> 2. Re: port numbler/mac address (o k)
> 3. experience with S50? (Andy Myers)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 09 Feb 2006 17:02:27 -0800
>From: Ron Lewkiewicz <ron.nsp at force10networks.com>
>Subject: Re: [F10-nsp] port numbler/mac address
>To: o k <fungk124_2hot at hotmail.co.jp>
>Cc: force10-nsp at puck.nether.net
>Message-ID: <43EBE623.1090107 at force10networks.com>
>Content-Type: text/plain; charset=UTF-8
>
>Keio-san,
>
>I'm not entirely clear that I'm understanding your question, but in
>general use:
>
>- dot1qTpFdbPort : to see MAC addresses learned on non-default VLAN.
>- dot1dTpFdbPort : to see MAC addresses learned on default VLAN
>- dot1dBasePortIfIndex : to map dot1 indexes to ifIndex
>- f10LinkAggMib : to see MAC addresses learned on LAG interfaces
>
>Hope this helps.
>
>-Ron
>
>
>o k wrote:
>
>
>>Hi,
>>
>>I'm trying to get the port number on which a MAC address has been learned,
>>by using SNMP.
>>But when I snmpwalk, E300 responds like this:
>>
>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.4.3.1.1
>> BRIDGE-MIB::dot1dTpFdbAddress = No Such Instance currently exists at this
>>OID
>>
>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.4.3.1.2
>> BRIDGE-MIB::dot1dTpFdbPort = No Such Instance currently exists at this
>>OID
>>
>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.7.1.2.2.1.1
>> Q-BRIDGE-MIB::dot1qTpFdbAddress = No Such Object available on this agent
>>at this OID
>>
>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.7.1.2.2.1.2
>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'...-..' = INTEGER: 1
>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'....y.' = INTEGER: 1
>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'......' = INTEGER: 18
>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'.....V' = INTEGER: 209
>> :
>> (snip)
>> :
>>
>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.2.2.1.1
>> IF-MIB::ifIndex.33865785 = INTEGER: 33865785
>> :
>> (snip)
>> :
>>
>>There are some vlans (ID 20,21,,,). And no port is associated with the
>>default vlan.
>>The only OID that shows me MAC addresses connected to E300 is
>>"ipNetToMediaPhysAddress".
>>But it doesn't give the information about ports. I can know only about the
>>VLAN-IP-MAC relationships from the OID.
>>
>>Any ideas?
>>
>>Regards
>>keio
>>
>>_________________________________________________________________
>>??????????????????MSN Hotmail?
>>http://promotion.msn.co.jp/hotmail/
>>
>>_______________________________________________
>>force10-nsp mailing list
>>force10-nsp at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/force10-nsp
>>
>>
>>
>
>
>------------------------------
>
>Message: 2
>Date: Fri, 10 Feb 2006 19:24:19 +0900
>From: "o k" <fungk124_2hot at hotmail.co.jp>
>Subject: Re: [F10-nsp] port numbler/mac address
>To: force10-nsp at puck.nether.net
>Message-ID: <BAY110-F90E0E775A07AAC69858FECE020 at phx.gbl>
>Content-Type: text/plain; charset=iso-2022-jp; format=flowed
>
>Ron-san,
>
>Thank you.
>
>I'll put the SNMP get-responses I've got from my E300 between the OIDs you
>presented.
>So, I want to know where MAC Addresses are. :-)
>
>
>
>>- dot1qTpFdbPort : to see MAC addresses learned on non-default VLAN.
>>
>>
>
>$ snmpwalk -v 2c -c public 192.168.1.1 dot1qTpFdbPort
>Q-BRIDGE-MIB::dot1qTpFdbPort.20.'...-..' = INTEGER: 1
> :
>(snip)
> :
>
>* dot1qTpFdbPort --> OID
>* 20 --> VLAN ID
>* '...-..' --> Is this a MAC Address? I don't know well SNMP, but I assumed
>there is a Hex or Dec value...
>* 1 --> Port Number? gig0/0? If so, I want to know the mapping between
>this number and ifIndex.
>
>
>
>>- dot1dTpFdbPort : to see MAC addresses learned on default VLAN
>>
>>
>
>$ snmpwalk -v 2c -c public 192.168.1.1 dot1dTpFdbPort
>BRIDGE-MIB::dot1dTpFdbPort = No Such Instance currently exists at this OID
>
> #There is no port associated with the default VLAN in my E300.
>
>
>
>>- dot1dBasePortIfIndex : to map dot1 indexes to ifIndex
>>
>>
>
>$ snmpwalk -v 2c -c public 192.168.1.1 dot1dBasePortIfIndex
>BRIDGE-MIB::dot1dBasePortIfIndex.0 = INTEGER: 33865785
>
> #It prints this one line only.
>
>
>
>>- f10LinkAggMib : to see MAC addresses learned on LAG interfaces
>>
>>
>
>$ snmpwalk -v 2c -c public 192.168.1.1 f10LinkAggMib
>F10-LINK-AGGREGATION-MIB::dot3aClearFdb.0 = INTEGER: no(2)
>
> #There is no LAG interface configured.
>
>
>Regards,
>
>keio
>
>
>
>>Hope this helps.
>>
>>-Ron
>>
>>
>>o k wrote:
>>
>>
>>>Hi,
>>>
>>>I'm trying to get the port number on which a MAC address has been
>>>
>>>
>learned,
>
>
>>>by using SNMP.
>>>But when I snmpwalk, E300 responds like this:
>>>
>>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.4.3.1.1
>>> BRIDGE-MIB::dot1dTpFdbAddress = No Such Instance currently exists at
>>>
>>>
>this
>
>
>>>OID
>>>
>>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.4.3.1.2
>>> BRIDGE-MIB::dot1dTpFdbPort = No Such Instance currently exists at
>>>
>>>
>this
>
>
>>>OID
>>>
>>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.7.1.2.2.1.1
>>> Q-BRIDGE-MIB::dot1qTpFdbAddress = No Such Object available on this
>>>
>>>
>agent
>
>
>>>at this OID
>>>
>>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.17.7.1.2.2.1.2
>>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'...-..' = INTEGER: 1
>>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'....y.' = INTEGER: 1
>>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'......' = INTEGER: 18
>>> Q-BRIDGE-MIB::dot1qTpFdbPort.20.'.....V' = INTEGER: 209
>>> :
>>> (snip)
>>> :
>>>
>>> $ snmpwalk -v 2c -c public 192.168.1.1 1.3.6.1.2.1.2.2.1.1
>>> IF-MIB::ifIndex.33865785 = INTEGER: 33865785
>>> :
>>> (snip)
>>> :
>>>
>>>There are some vlans (ID 20,21,,,). And no port is associated with the
>>>default vlan.
>>>The only OID that shows me MAC addresses connected to E300 is
>>>"ipNetToMediaPhysAddress".
>>>But it doesn't give the information about ports. I can know only about
>>>
>>>
>the
>
>
>>>VLAN-IP-MAC relationships from the OID.
>>>
>>>Any ideas?
>>>
>>>Regards
>>>keio
>>>
>>>_________________________________________________________________
>>>????????????????????????????????SN Hotmail??>
>>>
>>>
>>http://promotion.msn.co.jp/hotmail/
>>
>>
>>>_______________________________________________
>>>force10-nsp mailing list
>>>force10-nsp at puck.nether.net
>>>https://puck.nether.net/mailman/listinfo/force10-nsp
>>>
>>>
>>>
>
>_________________________________________________________________
>??????????????????MSN Hotmail?
>http://promotion.msn.co.jp/hotmail/
>
>
>
>------------------------------
>
>Message: 3
>Date: Fri, 10 Feb 2006 10:25:18 -0500
>From: Andy Myers <acm at dullroar.org>
>Subject: [F10-nsp] experience with S50?
>To: force10-nsp at puck.nether.net
>Message-ID: <1139585118.15005.38.camel at ti63>
>Content-Type: text/plain
>
>Hi,
>
>We're thinking of deploying a ring of S50's with 10 gig optics. Anyone
>have experience with this switch?
>
>Thanks,
>Andy
>
>
>
>
>------------------------------
>
>_______________________________________________
>force10-nsp mailing list
>force10-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/force10-nsp
>
>
>End of force10-nsp Digest, Vol 6, Issue 4
>*****************************************
>
>
More information about the force10-nsp
mailing list