Versions Compared

Old Version 9

changes.mady.by.user Sabine Engel

Saved on

compared with

New Version 10

changes.mady.by.user Dominik Karch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scanner Issues

...

Critical configurations are listed on top of the page. There are two buttons for each scan category (Toplogy, Performance, Event, HFTCS): The left one shows the scan status, the right one the persist status.




Click on a red icon to see the log file for the selected item.

Set severity to "Error" to limit the amount of information. 

Image RemovedImage Added


In most cases, the error can now be narrowed down to either a configuration issue or a product defect:

...

Expand
titleBrocade (REST)

Error Message: "Max limit for REST sessions reached"

No Format
Got error from Brocade Switch with IP 10.10.101.147! (body: {
 "errors": {
  "error": [
   {
    "error-type": "application",
    "error-tag": "operation-failed",
    "error-app-tag": "Error",
    "error-path": "/rest/login",
    "error-message": "Max limit for REST sessions reached",
    "error-info": {
     "error-code": 14,
     "error-module": "auth"
    }

BVQ Version: 6.2 and above

Suggested Action:

By default, the SSH session limits on Brocade switches is set to 3. The number of SSH sessions can be increased up to 10 by using CLI command mgmtapp --config -maxrestsession <1...10>



SAN (REST) scanner fails with "authentication failed"

Due to a bug in FOS version 8.2.3a and 8.2.3a1, communication via SNMP and REST APIs is broken after an update causing Brocade REST scanners to fail.

Root cause is a file descriptor leak that occurs in weblinker during LDAP authentication. Once all file descriptors are consumed a verify error is logged.  This also results in webtools authentication failing, causing SANnav, BNA or BVQ to be unable to authenticate with the switch.

BVQ Version: any

Suggested Action:

Workaround
Performing an hafailover on a director or an hareboot on a non-director will restore connectivity.  Once executed, disabling LDAP will prevent the issue from being hit. If LDAP cannot be disabled, reducing the number of login attempts via HTTP/Webtools will increase the timeframe before the issue is observed again. Downgrading from 8.2.3a or 8.2.3a1 to a lower release will also stop the issue from occurring.

Final Fix
FOS 8.2.3a2

...