From: Eric M. <er...@je...> - 2006-01-27 05:12:30
|
Thanks for bringing this up. I knew it was coming when Nortel announced name changes for everything including the company itself. I guess the marketing gurus didn't think customers knew they were buying an Ethernet switch unless they named it Ethernet Switch :-> I have modified snmp-info to recognize the new names and models. I have also modified it to work with 5510/5520/5530 in Layer 3. These changes have been uploaded to CVS. If you have a 5520 actually performing Layer 3 functions, I would like to validate that services reports correctly. We are not using the functionality and all out 5510's report they only perform Layer 2. I have also uploaded the newer SYNOPTICS-ROOT-MIB (synro.mib) to CVS this will eliminate the sysObjectID issue. I have validated the changes did not break any existing functionality, I would appreciate if you could validate it corrects your issues. Thanks, Eric Quoting Russ Forthofer <ru...@fo...>: > Brian - > Thanks. Right before I got your note, I made a similar change. It > appears to me that on the 5510, sysObjectID (I think that's the right > MIB) contains enterprises.45.3.52.1 in the older versions and > enterprises.45.3.53.1 in the newer versions. I could not figure out > how the older versions converted this to "5510" (is it actually > stored in the MIBS on the device?). I don't know enough about SNMP > to make sense of this, but checking specifically for 45.3.53.1 > worked for me. > > I am also not convinced (in fact I'm nearly certain) this is not the > right way to deal with this, but it works for now. My hope is that > either someone will delve into all this, or I will somehow find time > to raise my Perl and SNMP skills to a point that I can make a better > change that will be of value to others. > > Russ > > Brian Chow <bc...@ry...> wrote: > Hi Russ, > > I've had the same problem. We don't use the 5510 or the 5520 for > Layer3 either. > > I am not 100% sure if i'm doing this correctly but it worked and it > acutally put them back into their category. It used to show up as > registration.59.2 > > Here's the code I added in Info.pm and Baystack.pm > > Around Line 815 (Info.pm) > > I added below > > # BayStack Numbered > $objtype = 'SNMP::Info::Layer2::Baystack' if ($desc =~ > /BayStack\s[345]\d/); > > $objtype = 'SNMP::Info::Layer2::Baystack' if ($desc =~ > /Ethernet\sRouting\sSwitch/i); > > $objtype = 'SNMP::Info::Layer2::Baystack' if ($desc =~ > /Ethernet\sSwitch/i); > > > Around Line 87 (Baystack.pm in Layer2 Folder) > > sub os { > my $baystack = shift; > my $descr = $baystack->description(); > my $model = $baystack->model(); > > if ((defined $model and $model =~ > /(470|460|BPS|5510|5520|registration.59.2)/) and (defined $descr and > $descr =~ m/SW:v[3-5]/i)) { > return 'boss'; > } > return 'baystack'; > } > > Line 146 area > > added the following line > > return '5520' if ($model =~ /registration.59.2/i); > > Hope this helps. > > Brian. > > > > ----- Original Message ----- > From: Russ Forthofer > To: net...@li... > Sent: Wednesday, January 18, 2006 1:39 PM > Subject: [Netdisco] Nortel 5510 switch support > > > I have found that some newer Nortel 5510 switches are not being > recognized correctly by Netdisco. It appears that Nortel has changed > the SysDescr value from "Baystack 5510-48T" (for example) to > "Ethernet Routing Switch 5510-48T". In the past, the 5510 was a > Layer2 device only. Now it can act as a Layer3 device. > > Netdisco is keying off the "Baystack" value, and does not recognize > the "Ethernet Routing Switch" tag. Unfortunately, I am not a Perl > programmer, so I don't know how to change Netdisco to deal with this. > Can anyone help - or has anyone already developed the changes > required to support a Layer3 5510? (Actually, in my case, even > treating them as Layer2 5510s would be helpful, since we typically > are not using the layer 3 capability.) > > > I can see that a change needs to be made in Info.pm to recognize > this as a 5510, but after that I have no idea what needs to be > changed. Any help would be greatly appreciated. I would be happy to > provide debug or snmpwalk output, as needed. > > Russ > > > > |