Links to other applications in CM Topology View

[helexis]

In topology view when I right-click a device and select Device Fault Manager > Show DFM Alert a new window opens with this link https://ciscoworks.net.okstate.edu/campus/forwardToApp.jsp?MICEcookie=E0E1165BFBEBE6E36CF6C2928DA8707D&url=DFMCL&dsu=https://CISCOWORKS-RME:443&lid=/dfm/FHReports.do&deviceIP=10.193.239.249&deviceID=288&device=nclb-204a-av1 then immediately redirect to the portal-https://ciscoworks.net.okstate.edu/cwportal/c/portal/login...

What is wrong?

[helexis]

Another behavior the device I was right-clicking above was a VG224. I decided to see what a 3750 would do and it attempts to go to https://ciscoworks.net.okstate.edu/campus/forwardToApp.jsp?MICEcookie=E0E1165BFBEBE6E36CF6C2928DA8707D&url=DFMCL&dsu=DFMSERVERNOTKNOWN&lid=/dfm/Events.do&alarmid=-1&deviceIP=10.193.226.12&deviceID=27&device=c3750nclb204a10&userName=helexis but immediately redirects to 403 Forbidden-http://ciscoworks-rme:1741/dfm/AFDAreaBar.do (we are using 443).

[helexis]

LMS 3.2

Still cannot access "interface Report" from CM Topology Display view. The forward to application process is not using ssl paths.

Any ideas?

[Joe Clarke]

First, I can reproduce your first problem with the portal. There appears to be an issue with Internet Explorer. Can you try Fiefox 3.0.14, and see if it works for you? Things are working fine for me in Firefox.

As for the http/https thing, the remote server's protocol and port are installed on the master server's NMSROOT/lib/classpath/com/cisco/nm/dcr/DomainInfo.properties file. Verify that the protocol and port are correct for your remote server.

[helexis]

First: Firefox opens DFM from the Topology view just fine for me too.

Second, my DomainInfo.properties shows:

hostname=https,1741,443

I am assuming 1741 is either not supposed to be there or at least should be last. Which is it?

And if I modify it do I need to restart the Daemon Mgrs?

[Joe Clarke]

No, DomainInfo.properties is fine. The forwardToApp.jsp code will see that https is the protocol, and use the second port. Is the hostname here FQDN or short? If FQDN, make it short, or add a new entry for the short hostname. You shouldn't have to restart anything. Trying the cross-launch again should just work provided it's going through forwardToApp.jsp. I wasn't really clear to what "interface report" you were referring.

[helexis]

Oh sorry...Interface report is when I right-click a link.

What is UPM?

403 Forbidden

You don't have permission to access /upm/CrossLaunchServlet on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

[Joe Clarke]

UPM is HUM. That error definitely points to an issue with HTTP vs. HTTPS.

If you only have the one slave listed in DomainInfo.properties, then that is why you're seeing this. This file should be automatically updated when new slaves are added. Make sure all slave servers are listed.

[helexis]

Ok...that's what I thought...but yes I do have both servers in the file. Yet it still wants to redirect here...in IE and firefox btw...

initial URL (today):

https://ciscoworks/campus/forwardToApp.jsp?MICEcookie=00B75FC442D45967022FB3E2DAAA3E7D&JSESSIONID=00B75FC442D45967022FB3E2DAAA3E7D&userName=helexis&appName=HUMCL&dcrDeviceID=16,126&url=/upm/CrossLaunchServlet?deviceDetails=16~c3750cords100v~Gi1/0/1|126~c3750cordn300e~Gi1/0/2~^reportType=INTERFACE^fromCV=false

redirected url (today)

http://ciscoworks-hum:1741/upm/CrossLaunchServlet?deviceDetails=16^c3750cords100v^Gi1/0/1|126^c3750cordn300e^Gi1/0/2^&reportType=INTERFACE&fromCV=false

[helexis]

One more thing I failed to clarify...

DFM isn't remote anymore (lol) I forgot.

RME and HUM are now...and they both behave the same. When I originally posted DFM and RME were on the same remote server. Now DFM is local and RME is remote with the HUM trial added on a third server.

So let me test the firefox thing again...

DFM works fine ...but i know remember it isn't remote.

HUM & RME don't work in IE or Firefox 2.0.0.20

[Joe Clarke · Accepted solution]

I filed CSCtc92157 to track the problems with IE. There appears to be some cookie issues with IE causing this problem with cross-launch. For now, the workaround is to use Firefox.