FM has long been restarted.

Even re-installed.

Some pwwn alias are missing...

Hi Ivy,

This looks like bug ID
CSCtu03947 Device-alias add/delete doesn't update client cache.
It is fixed in 5.2(2a) to be released next year.

The workaround is to delete the fabric and re-discover it.

Example:
Log into Fabric Manager.  The first window is the Control Panel.
(Another way to get to the FM Control Panel is File > Open)
Select the Fabrics Tab.
Select the Fabric, then the Remove or Delete button.
Then the Discover button to re-discover the fabric.

Does this work for you?

Regards,
David

Hello David,

When we re-installed the Fabric Manager (now version 5.0(4d) ) we did a re-discover.

This did not help...

Waiting for the new version 5.2(2a) in 2012 now...

In the mean time there is still CLI ;-)

Rgds,

Ivy

Hi Ivy,

Can you check on all the switches in the fabric if cfs is properly enabled for device-alias?

# sh cfs application

and look for something that looks like this:

device-alias   Yes       Physical-fc

and make sure the device-alias changes are committed everywhere.

It's a long shot, but if the device-alias database isn't consistent across the fabric, FMS might pull in the incomplete data.

Hello Kris,

I checked all 18 directors and all were OK having a

device-alias   Yes       Physical-fc

For the moment 2 directors are being moved (offline)

Can this be a problem creator?

I recently created 14 new pwwn aliases. (on core directors)

They distributed OK over all the directors. (core - edge, two data centers)

But do not show up in the Fabric Manager ;-(

A bit agravating he!

Rgds,

Ivy

Hi Ivy,

Are there any authentication failures in fmserver.log?
The default location is c:\Program Files\Cisco Systems\dcm\fm\logs\fmserver.log

Is FM configured to use FC Alias or Device Alias?
Look at the control Panel Fabrics tab, there should not be a check mark for "Use FC Alias"

Regards,
David

Hello David,

I don't find authentication errors in fmserver.log

most are info

warn are like this:

2011.12.09 00:55:00  WARN  [Scheduler] sun.net.www.protocol.http.HttpURLConnection cannot be cast to javax.net.ssl.HttpsURLConnection

java.lang.ClassCastException: sun.net.www.protocol.http.HttpURLConnection cannot be cast to javax.net.ssl.HttpsURLConnection

at com.cisco.dcbu.sm.server.scheduler.jobs.ReportJob.generateReport(ReportJob.java:186)

at com.cisco.dcbu.sm.server.scheduler.jobs.ReportJob.execute(ReportJob.java:129)

at org.quartz.core.JobRunShell.run(JobRunShell.java:203)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

2011.12.09 00:55:00  WARN  [Scheduler] sun.net.www.protocol.http.HttpURLConnection cannot be cast to javax.net.ssl.HttpsURLConnection

java.lang.ClassCastException: sun.net.www.protocol.http.HttpURLConnection cannot be cast to javax.net.ssl.HttpsURLConnection

at com.cisco.dcbu.sm.server.scheduler.jobs.ReportJob.generateReport(ReportJob.java:186)

at com.cisco.dcbu.sm.server.scheduler.jobs.ReportJob.execute(ReportJob.java:129)

at org.quartz.core.JobRunShell.run(JobRunShell.java:203)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

All fabrics have the "Use FC Alias" unticked.

Rgds,

Ivy

Hi Ivy,

For the errors in fmserver.log, if you cannot open the web client, please open an SR with TAC.

For the device Alias not appearing in Fabric Manager,

I see you re-installed the Fabric Manager (now version 5.0(4d) ) and did a re-discover.

This did not help...

Did you remove the fabric first?

Example:

Log into Fabric Manager.  The first window is the Control Panel.

(Another way to get to the FM Control Panel is File > Open)

Select the Fabrics Tab.

Select the Fabric, then the Remove button.

If this does not work, you may need to open a TAC SR.

Regards,

David