01-11-2011 07:07 AM
DCFM discovered some Switches runing in AG Mode (actually they are HP VC Sanmodules). The Modules are part of a Matrix Installation so they have no direkt IP Connectivity by the DCFM Server, but They are seen in the via the SAN. Is there a way to ignore these switches and get around the switch unreachable messages?
Greetings Cristoph Hauser
01-24-2011 01:37 AM
I have the same issue.
We have several HP VirtualConnect FC modules. These modules runs a special version of FOS, and are not supposed to be user manageble. But DCFM discovers them, and then can't login to them and lists them as "unmanageable". See attached screenshot.
I would like DCFM to ignore these units doing discovery.
Is that possible?
01-24-2011 01:57 AM
Also have similar issue.
Fabric has one old Cisco switch in the fabric, which of course DCFM cannot manage.
It would be really nice if DCFM could be told to ignore that switch and stop constantly telling me it is unreachable.
It ends up making the message notification pointless as I ignore all notifications as they are nearly always about this switch being unreachable.
One day I will ignore a real problem notification !
01-24-2011 02:02 AM
--->>> These modules runs a special version of FOS, and are not supposed to be user manageble.
FOS 6.4.0b is GA = General Available and not a special Version.
I believe by HP you must Make the Switch manegeble in the Chassis Management Module before can be maneged.
Q.: what you mean with: ?
--->>> ....connected to the Virtual Connect modules....
01-24-2011 02:09 AM
6.4.0b is the version of FOS that runs on our core switches.
The VC modules runs 6.1.0_uth4.
The VC modules are NOT normal blade enclosure switches.
To see more about the VC modules we are having trouble with, follow this link:
HP also has a Virtual Connect for DUMMIES book on the subject. Free of charge:
01-24-2011 02:23 AM
same as 6.4.0b, the FOS release 6.1.0_uth4 installed, - we can definied as special version - but is GA and only valid Package for the VC Module.
Is probable - I cannot test this - the VC become recharchable from Chassis IP and not due a FOS incompatibility,
and I don't see a way that DCFM should ignore any Switch.
01-24-2011 02:45 AM
Can you elaborate on this part:
Is probable - I cannot test this - the VC become recharchable from Chassis IP and not due a FOS incompatibility.
I don't understand what your point is?
The VCs are aasigned an IP, but HP will not give out the authentication information (eg. login/password)
and I don't see a way that DCFM should ignore any Switch
VC modules are not switches, they are special modules working in NPIV mode, and are to be manged by special HP Virtual Connect software only. Therefore HP will not allow any other management tools to manage them. So DCFM should ignore these "non-switches".
Is it possible to exclude specific switches or IPs from auto discovery?
01-24-2011 03:04 AM
I meaning, is probable that the VC become a recharchable from IP Chassis.
--->>> VC modules are not switches, they are special modules working in NPIV mode,....
I know that, AFAIK this are specially for HP Designed Embedded "Switch" that run only in NPIV Mode.
--->>> The VCs are aasigned an IP, but HP will not give out the authentication information (eg. login/password)
That is new to me. what is the reason that HP not give the login info ?
The reason can be, that the VC Module are set as DHCP, and then obtain automatically the IP From the Chassis.
have your opened a Call by HP about that ?
--->>> Is it possible to exclude specific switches or IPs from auto discovery?
I believe you can disable in DCFM Auto Discovery and add manually all other switch in the management.