I implement VBN's (Visitor Based Gateways) in places such as MDUs, Hotels, College Campuses for internet access. We have been using 3024/3048 switches using RFC1493 bridging to pass port data to our Linux-based gateway server - i.e. Room/unit number, etc. for billing purposes.
Last order - I can no longer get the 30xx switches - had to buy 33xx switches. Now, I can not get the SNMP info to pass to the gateway server correctly. Used to take less than 20 seconds to configure the switch for our application. After plowing through this for some time today - still at a loss as to what's up. Any ideas??
EDIT: I can query the switch via the standard MIB2 extensions with the community public but as soon as I specify the 1493 extensions (17.4.3.1) nothing is returned.
I'm stumped.
Thanks!
Message Edited by rkymtnman on 09-24-2003 10:26 PM
Message Edited by rkymtnman on 09-24-2003 11:01 PM
Thanks for all the help and assistance. I am packaging up these 5 switches I recently recieved and will be returning them tomorrow. Why they don't suport standards-based RFCs are beyond me and apparantly, you as well.
Apologies for the delays in getting this information. Unfortunately, we just received an answer late yesterday.
According to engineering, the relevant equivalent MIB for what you are attempting to do is dot1qTpFdbTable (Extension 17.7.1.2.1.1), which is part of the VLAN-based bridging model (RFC2674). A change in your monitoring application to access the table may be needed in order to get the information you seek.
I hope this provides the information you required. Again, we apologize for the lengthy wait in getting you an answer. If more timely resolution to a problem or question is required, we usually recommend calling our technical support group at 1-800-822-8965. Choose the server option, then the PowerConnect option.
Message Edited by DELL-AndrewH on 10-01-2003 09:27 AM
Thanks for the reply and assistance. I did have one of my team members chase this down through "normal" phone support channels to no avail. It is not a monitoring system that I need to integrate with and the "fix" won't be that easy to implement but it should work.
I apologize for the stong wording - I hate chasing my tail for hours on end when a vendor "updates" a product line.
Have about 35-40 of the 30xx line of switches in exactly the same application. We had standardized on Dell switches for our application.
As soon as I installed the 3300 line of switches, I realized we had a problem. RFC1493 port information not being returned. Randy Gutierrez - Engineer Tech/Senior Analyst suggested I change my method of polling. I refuse to request a firmware upgrade for my gateway. There are many other switches that follow the standard.
Seems the 30xx line was oem by Delta Networks. The design was purchased by Dell. There is still product around, but doesn't seem a good idea to continue our standards on a discontinued product that Dell has squashed. The new line is oem by another manufactor or direct by Dell with Dell listed in the mac address as manufactor. Not sure at this point. As far as I can tell, or have been told, the 3300 line of switches won't work in my application due to them not following standards.
Have you found a solution. I have rma in process for 5 switches of my own and am in process of testing new switches.
SMC (www.smc.com) has switches that work fine and are as cost effective. If Dell can't figure out how to release a switch that follows standards, then I don't know that I have any choice other then to go to another product.
Our software engineering team has tested and verified this issue. The RFC 1493 MIB extensions (17.4.3.1) should remain intact as RFC 2674 only supplements the older standard, not replaces it. However, queries to the dot1dTpFdbTable do in fact return a void object. This issue has been submitted to our sustaining group and will be fixed in the next revision of the firmware.
There is currently no ETA on the release date of the next firmware revision. Currently, the only workaround is to configure the SNMP management tool to query the RFC 2674 equivalent, dot1qTpFdbTable (17.7.1.2.1.1), as stated earlier.
I am running into this issue, and just found this posting...has a new firmware been realeased yet? I have the only version available for download, and it does not have this fix in it. Is there a beta available? I have just purchased 20 of these switches and the software we use for network mapping does not work because of this missing MIB. Thanks
Our test engineers are expecting the new code drop from the vendor by the end of next week. The code will need to be tested extensively, so there is currently no ETA on the official release or even a limited-deployment release. This issue should be resolved in the next firmware drop, but we have not received a list on the bug fixes or feature enhancements.
rkymtnman
8 Posts
374
0
Posted September 25th, 2003 20:00