Pular para o conteúdo principal
GE Healthcare · MRSigna

Clarify #005674 TPS will Not Communicate After Running a mrload Due to vd0 is Not Configured

Symptom

TPS Will Not Communicate After Running A mrload See long description Did a mrload to edit something in the host config file. The system now fails to boot applications, the software crashes due to the nsp process. Looks like the Bit 3 link is down. Had the FE do a "netstat -i" to see if the Bit 3 interface ("vd0") was configured. It is a common problem with the 5X software to lose this after doing a "mrload". In this case we found that the "vd0" interface was not configured as suspected. See results below: insite @ MRS1_OC0 3: netstat -i Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue <-- The vd0 interface is not configured ei0 1500 142.76.62.0 MRS1_OC0 3955 0 31 0 0 0 lo0 1536 loopback localhost 1717 0 1717 0 0 0

Applies to

Models
Signa
Product
Signa Horizon (5X Horizon) 5X Horizon systems
Software
5.X
Area
MR

Full cause & step-by-step resolution

The complete cause analysis, the step-by-step remedy for this GE Healthcare MR issue are available to FSELIB subscribers — re-authored, web-first, searchable.

7-day free trial · no credit card required

Related GE Healthcare MR issues