Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 5
Registered: ‎05-26-2012

DCX SNMPv3 Config DCFM

Hi, I have below setup for snmpv3 configuration on DCX switch.  But under the DCFM >>Discovery >> setup  it show error message.

The user and password are correct for MD5 and DES, It will be very help full, if some can suggest anything wrong in this configuration.

Discovered: SNMP communication failed. SNMP credentials may be invalid. : Seed Switch



:FID128:admin> snmpconfig --show accessControl

SNMP access list configuration:

Entry 0:  Access host subnet area XX:XX:XX:XX (rw)  MY DCFM gatway

Entry 1:  No access host configured yet

Entry 2:  No access host configured yet

Entry 3:  No access host configured yet

Entry 4:  No access host configured yet

Entry 5:  Access host subnet area XX:XX:XX:XX (rw)

FID128:admin>  snmpconfig --show systemGroup

          sysDescr = Fibre Channel Switch.

       sysLocation = End User Premise.

        sysContact = Field Support.

         authTraps = 1 (ON)

FID128:admin> snmpconfig --show secLevel

GET security level = 2, SET level = 2

SNMP GET Security Level: Authentication and Privacy

SNMP SET Security Level: Authentication and Privacy

FID128:admin> snmpConfig --show snmpv3

SNMP Informs = 1 (ON)

SNMPv3 USM configuration:

User 1 (rw): admin

        Auth Protocol: MD5

        Priv Protocol: 3DES

        Engine ID: 80:00:06:34:03:00:50:56:b2:00:28

User 2 (rw): snmpadmin2

        Auth Protocol: noAuth

        Priv Protocol: noPriv

        Engine ID: 00:00:00:00:00:00:00:00:00

User 3 (rw): snmpadmin3

        Auth Protocol: noAuth

        Priv Protocol: noPriv

        Engine ID: 00:00:00:00:00:00:00:00:00

User 4 (ro): snmpuser1

        Auth Protocol: noAuth

        Priv Protocol: noPriv

        Engine ID: 00:00:00:00:00:00:00:00:00

User 5 (ro): snmpuser2

        Auth Protocol: noAuth

        Priv Protocol: noPriv

        Engine ID: 00:00:00:00:00:00:00:00:00

User 6 (ro): admin2

        Auth Protocol: noAuth

        Priv Protocol: noPriv

        Engine ID: 00:00:00:00:00:00:00:00:00

SNMPv3 Trap configuration:

Trap Entry 1:     DCFM IP

    Trap Port: 162

    Trap User: admin

    Trap recipient Severity level: 4

Trap Entry 2:     No trap recipient configured yet

Trap Entry 3:     No trap recipient configured yet

Trap Entry 4:     No trap recipient configured yet

Trap Entry 5:     No trap recipient configured yet

Trap Entry 6:     No trap recipient configured yet

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: DCX SNMPv3 Config DCFM

Hi,

     Which user are you trying to use from DCFM?  SNMPv3 requires username and password and only the admin user (User 1) has auth set.

Thanks

Michael.

External Moderator
Posts: 5,046
Registered: ‎02-23-2004

Re: DCX SNMPv3 Config DCFM

--->>> ....on DCX switch.  But under the DCFM....

old DCFM support DCX only till FOS 6.4.x

If you are running in higher FOS Release, is not supported, in such case you have to switch to BNA

TechHelp24
Occasional Contributor
Posts: 5
Registered: ‎05-26-2012

Re: DCX SNMPv3 Config DCFM

Hi Michael,

     Thanks for reply, Yes I am using admin user as user 1 and same password has been given in the DCFM discovery setup.

Hi Techhelp24,

      FOS is 6.4.3d  and DCFM is at 10.4.5.

External Moderator
Posts: 5,046
Registered: ‎02-23-2004

Re: DCX SNMPv3 Config DCFM

->Discovered: SNMP communication failed. SNMP credentials may be invalid. : Seed Switch

if communication failed invalid "Seed Switch" , this error is usually caused due FOS Incompatibility or unsupported Plattforms.

Latest DCFM Patch v10.4.5a was released on May 06,2011

--->>>FOS is 6.4.3d  and DCFM is at 10.4.5.

FOS 6.4.3d which was released on February 22, 2013, report in Release Notes DCFM 10.4.5a is Supported.

I'll not insist, but is most probable you have to check if the patch is installed !!

TechHelp24
New Contributor
Posts: 2
Registered: ‎05-19-2014

Re: DCX SNMPv3 Config DCFM

I had this problem and it related a Firewall Rule between the Server and Switch. Apparently, there are two different Firewall rules that can be used for snmp get (UDP 161) - 'snmp' or 'snmp_read'. For some reason 'snmp_read' seems to be more restrictive and has 'application intelligence' and this was blocking the traffic. Please note that this might only relate to Checkpoint Firewalls.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook