Fusion Manager Not Coming Back Up

Solution ID: 54

Created: 8/24/2008

DETAILS:

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6

3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-

font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri;

panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-

font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-

face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4; mso-font-charset:0; mso-

generic-font-family:modern; mso-font-pitch:fixed; mso-font-signature:-1610611985

1073750091 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal,

div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:"";

margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt;

font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-

font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-

family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p.MsoPlainText,

li.MsoPlainText, div.MsoPlainText {mso-style-noshow:yes; mso-style-priority:99; mso-

style-link:"Plain Text Char"; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-

orphan; font-size:10.5pt; font-family:Consolas; mso-fareast-font-family:Calibri; mso-

fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-

theme-font:minor-bidi;} span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-

style-noshow:yes; mso-style-priority:99; mso-style-unhide:no; mso-style-locked:yes;

mso-style-link:"Plain Text"; mso-ansi-font-size:10.5pt; mso-bidi-font-size:10.5pt; font-

family:Consolas; mso-ascii-font-family:Consolas; mso-hansi-font-family:Consolas;}

.MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-

family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-

fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-

font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-

bidi;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-

margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1

{page:Section1;} --> Windows Client had to be re-registered with new-named FM and

tuning had to be reapplied. Samba also broke at some point. Yan and I worked with the

customers via Microsoft Live-meeting with multiple Windows Client reboot required after

each change in configuration on FM, Segment Servers and Windows Client (due to

Socket 9005 lockup error). FM, Segment Servers and Client issues were resolved after

tedious modifications in /etc/hosts files to correspond DNS settings; verification that FM

name is correctly changed in the following places: