My company is presently supporing the US Navy with its new computer systems roll out, and part of that is the use of IBM blade centers with the 8GB SAN Fibrechannel Switches from Brocade.
Currently we're running firmware version 6.4.2b4 on them.
Our current problem is this:
On most switches they take the Navy specified snmpv3 username and password, which is a mix of numbers, letters, and special characters with no problems; both are over 15 characters. However, we have one switch that will not take this username and password no matter what we try (reinstalling the FabricOS, snmpconfig --default snmpv3); it simply fails to configure the snmpv3 information. However, when we knock the character amount back a bit (less than 14 characters), it takes it just fine. No, under no circumstances can we deviate the Navy's CM on a single switch, and it still doesn't explain why this one switch will not take the information and every other switch will.
If some other switch running the same, snmp confing, fos release and being the same model work, you should be able to do it on that one as well. You could try to disable/enable snmv3
snmpconfig --disable snmv3
snmpconfig --enable snmv3
or reboot the switch.
What error do you get? any info on errdump?
The rebooting we've done several times with no effect.
--enable and --disable resulted in the error message (and yes, I used the correct spelling for snmpv3 there): Options are invalid
Checked the errdump. The only error message that pertained to it was this one:
2014/10/15-16:46:46, [KSWD-1002], 1456, FFDC | CHASSIS, WARNING, brocade8Gb, Detected termination of process snmpd:2145
Indeed, one would think if it works on other switches it would work on this one as well.
Brocade Solution SLN1980 reports that a switch may find problems when configuring SNMP users longer than 15 characters. If the issue is caused by a code defect, you could try to upgrade FOS. Also you can try to configure that user in different positions inside snmpconfig. Or maybe cleanup some space to see if that could help out.
If no luck, then I'd start thinking of opening a case with Brocade/OEM...
Navy Config Management will not allow me to change code like that, unfortunately. Though it may be possible to upgrade to a higher version and then downgrade to see if the problem goes away. It's a little dicier than I'd like, but I'll keep that option open.
You mentioned 'freeing up space'. How would one go about doing that?
Also can you point me to where you found Brocade Solution SLN1980? I can't seem to locate that notice anywhere.
Thanks for your help.
If you have root access to the switch, you can run non-disruptive command 'cleanup' in order to free up space. If not, you can execute 'supportsave -R' to clear the dumps and free some space there.
Brocade SLN1980 reports the following:
Upgrade to a version of FOS that contains the fix.
These documents are provided "as is" and without any warranty of any kind, expressed or implied, including, without limitation, any warranty of non-infringement, merchantability, or fitness for a particular purpose. All warranties are expressly disclaimed. User assumes the full risk of using these instructions. In no event shall Brocade be liable for any actual, direct, indirect, punitive, or consequential damages arising from such use, even if advised of the possibility of such damages.
The 'cleanup' command was not a valid command in this FOS, but the 'supportsave -R' worked. The device still will not take the long snmp user/pass. However, with SLN1980 that you provided I was able to recommend an engineering change with either an FOS upgrade or a change for the username/pass. This isn't the only device that's had issues with the USN required lengths, so it's likely engineering and IA will need to hash that out...problem being that they work at geologic speeds. There's also the fact that this is an IBM rebranded Brocade product for their blade centers, so they will likely need to be involved as well.
Thanks for your help on this.