SIM 5.1 and FC switch MIB information

[Pasi Koistinen]

HP SIM 5.1 is reporting HP c-class blade system FC switch errors about 30-50 times in day.

But data from switch is not in right format.

I think there is no correct MIB in SIM, and there is no MIB files with newest firmware.

Switch is c-class embedded 4gb Brocade.

Any ideas to find correct MIB, or something else?

SNMP error:

Print Report: Event DetailsEvent Details: connUnitPortStatusChange


Event Identification and Details

Event Severity Major
Cleared StatusNot cleared
Event Sourcexxx.xxx.xxx.xxx
Associated Systemxxx.xxx.xxx.xxx
Associated System Status Normal
Event Timeon, 2007-xx-xx, 11:14 EET

DescriptionThe overall status of the connectivity unit has changed.

Recommended severity level (for filtering): alert
Assignee
Comments


Trap Details

Variable DescriptionValue
NO DATA
An overall protocol status for the port. This value of connUnitPortState is not online, then this is reported Unknown.ready

The user selected state of the port hardware.online

Mib data does not match the trap, make sure the latest version of the MIB is registered.

The SNMP OID is
1.3.6.1.3.94.1.10.1.17.16.0.0.5.30.4.72.222.0.0.0.0.0.0.0.0.10

Mib Information
The associated MIB File Name for this trap is fa-mib40.mib and the MIB identifier FCMGMT-MIB

[Christopher Knight]

We are having the same problem. Have you found a fix for this?

[ICT System]

We are also having this exact same event.

[Frank Iglesias]

we have been having a similar issue. was a resolution ever found? Thanks.

[Brassen99]

we have it also!

[patrick haynes]

An overall protocol status for the port. This value of rea
connUnitPortState is not online, then this is reported Unknown. dy

The user selected state of the port hardware. onl
ine


Mib data does not match the trap, make sure the latest version of the
MIB is registered. The SNMP OID is
1.3.6.1.3.94.1.10.1.17.16.0.0.5.30.5.162.213.0.0.0.0.0.0.0.0.9


Mib Information
The associated MIB File Name for this trap is fa-mib40.mib and the
MIB identifier FCMGMT-MIB

[SCC (Kavanagh) Support]

Please can you advise if this issue was resolved.? If it was, what actions were taken?

Thanks
Mark

[Kenneth!]

Hi,

Having the same issue here, same hardware (c7000 with Brocade SAN switches.)

I was trying to filter out this event with the automatic event handling but I wasn't successful in only filtering something with keywords: connUnitPortStatusChange

Any help would be appreciated.
Maybe I can successfully use event handling when the correct MIB is loaded?

[Kenneth!]

Hi,

Anyone with some news on this?

Cheers,
Kenneth

[patrick haynes]

after speaking with HP, and they reviewed the logs and suggested to reboot it and see if it occurs again. So after rebooting it last weekend, the error has not re-occured. however its only been a week, i will update should it occur again.

[Kenneth!]

Hmmm... i'm quite sure that the error messages will stay after a reboot.. (at least in my case.)

Please let me know your experiences.
I get these messages after rebooting a blade (which causes the FC port to go down and up again)

[Octavio Gramajo]

Same problem... any idea?
Thanks!!!!

[Maxim Revutskiy]

"Mib data does not match the trap, make sure the latest version of the MIB is registered." Appears because switch send 3 variables, but in mib files defined only 2 variables for this trap.

I did next things to correct it:
1. Open fa-mib40.cfg
2. Found connUnitStatusChange TRAP-TYPE
3. Change VARIABLES ... to VARIABLES { connUnitPortStatus, connUnitPortState, connUnitPortName }
4. run "mxmib -a fa-mib40.cfg"

After that variable description seems correct

[mahesh jadhav]

To resolve the issue perform the following actions.

Edit the fa-mib40.mib as explained below

1) Edit the fa-mib40.mib file currently being used.

( It will be under c:\program files\HP\systems insight manager\mibs )

Change the last entry in the file on the VARIABLES line from: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


connUnitPortStatusChange TRAP-TYPE

ENTERPRISE fcmgmt

VARIABLES { connUnitPortStatus, connUnitPortState }

DESCRIPTION

"The overall status of the connectivity unit has changed.

Recommended severity level (for filtering): alert"

::= 6



+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

TO: [you will notice the addition of the connUnitPortName ]:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


connUnitPortStatusChange TRAP-TYPE

ENTERPRISE fcmgmt

VARIABLES { connUnitPortStatus, connUnitPortState, connUnitPortName }

DESCRIPTION

"The overall status of the connectivity unit has changed.

Recommended severity level (for filtering): alert"

::= 6

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2) Save the file.

3) Once this is done, go to command prompt & go to following path

( c:\program files\HP\systems insight manager\mibs\ )

Run the following commands.


mcompile fa-mib40.mib
mxmib -d fa-mib40.mib
mxmib -a fa-mib40.cfg



With the changes stated and commands run, the variable connUnitPortName will show correctly. Also, the connUnitPortName variable will send an empty string by default. You would need to assign the port name to all the switch ports to implement this feature on a port.


Let us know the results.

[Maxim Revutskiy]

mcompile fa-mib40.mib will overwrite fa-mib40.cfg with newly compiled one, doesn't it? So all changes we made would dissapear.

In my case it was not necessary to run mcompile and mxmib -d, i just add new variable to fa-mib40.cfg and run mxmib -a fa-mib40.cfg

[Simon Ho (UK)]

I recently set up SIM 5.3 on two separate servers on two identical sites, and was seeing the exact same event reports against four HP StorageWorks 4/8 SAN switches (two at each site).

I've just followed Mahesh's instructions precisely, i.e. editing, then recompiling to generate a new fa-mib40.cfg file, then deleting the old one with mxmib -d and implementing the new one with mxmib -a.

Subsequently when checking the SAN switch events through the SIM GUI, all the connUnitPortStatusChange events that were listed previously have disappeared.

Perfect! Thanks Mahesh.

[mahesh jadhav]

Hi Simon,

Good to know the issue is resolved after following the steps.

How about Assigning some points !!!!!!

Cheers,

[Simon Ho (UK)]

Mahesh, I would gladly assign points but I can't see how. I think it may be limited to only the thread originator, unless you can show me otherwise.

[mahesh jadhav]

You can click on the the link on the first post which reads

Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click here

[Simon Ho (UK)]

Sorry Mahesh, I'm not the author of the original question, so no link is provided for me to assign points. But thanks again for providing a solution.

[patrick haynes]

i received this error again about 6months later, implemented the fix as decribed by using mcompile and mxmib -d then mxmib -a on fa-mib40.mib/cfg and it worked, removed the events from the sim server automagically.