NanoCloud AWS Installation Procedure

General Service Documentation

DOC2507368
Rev 10

© 2023 GE HealthCare. GE is a trademark of General Electric Company used under trademark License.

Reproduction and/or distribution is prohibited.

 NanoCloud AWS Installation DOC2507368_r10
IMPORTANT PRECAUTIONS
Language

ПРЕДУПРЕЖДЕНИЕ • ТОВА УПЪТВАНЕ ЗА РАБОТА Е НАЛИЧНО САМО НА АНГЛИЙСКИ ЕЗИК.

(BG) • АКО ДОСТАВЧИКЪТ НА УСЛУГАТА НА КЛИЕНТА ИЗИСКА ЕЗИК,
РАЗЛИЧЕН ОТ АНГЛИЙСКИ, ЗАДЪЛЖЕНИЕ НА КЛИЕНТА Е ДА
ОСИГУРИ ПРЕВОД.
• НЕ ИЗПОЛЗВАЙТЕ ОБОРУДВАНЕТО ПРЕДИ ДА СТЕ СЕ
КОНСУЛТИРАЛИ И РАЗБРАЛИ УПЪТВАНЕТО ЗА РАБОТА.
• НЕСПАЗВАНЕТО НА ТОВА ПРЕДУПРЕЖДЕНИЕ МОЖЕ ДА ДОВЕДЕ ДО
НАРАНЯВАНЕ НА ДОСТАВЧИКА НА УСЛУГАТА, ОПЕРАТОРА ИЛИ
ПАЦИЕНТ В РЕЗУЛТАТ НА ТОКОВ УДАР ИЛИ МЕХАНИЧНА ИЛИ ДРУГА
ОПАСНОСТ.
警告 • 本维修手册仅提供英文版本。
(ZH-CN) • 如果维修服务提供商需要非英文版本，客户需自行提供翻译服务。
• 未详细阅读和完全理解本维修手册之前，不得进行维修。
• 忽略本警告可能对维修人员，操作员或患者造成触电、机械伤害或其他形式的
伤害。

警告 • 本服務手冊僅提供英文版本。
(ZH-HK) • 倘若客戶的服務供應商需要英文以外之服務手冊，客戶有責任提供翻譯服務。
• 除非已參閱本服務手冊及明白其內容，否則切勿嘗試維修設備。
• 不遵從本警告或會令服務供應商、網絡供應商或病人受到觸電、機械性或其他
的危險。

警告 • 本維修手冊僅有英文版。
(ZH-TW) • 若客戶的維修廠商需要英文版以外的語言，應由客戶自行提供翻譯服務。
• 請勿試圖維修本設備，除非 您已查閱並瞭解本維修手冊。
• 若未留意本警告，可能導致維修廠商、操作員或病患因觸電、機械或其他危險
而受傷。

UPOZORENJE • OVAJ SERVISNI PRIRUČNIK DOSTUPAN JE NA ENGLESKOM JEZIKU.

(HR) • AKO DAVATELJ USLUGE KLIJENTA TREBA NEKI DRUGI JEZIK, KLIJENT JE DUŽAN
OSIGURATI PRIJEVOD.
• NE POKUŠAVAJTE SERVISIRATI OPREMU AKO NISTE U POTPUNOSTI PROČITALI I
RAZUMJELI OVAJ SERVISNI PRIRUČNIK.
• ZANEMARITE LI OVO UPOZORENJE, MOŽE DOĆI DO OZLJEDE DAVATELJA USLUGE,
OPERATERA ILI PACIJENTA USLIJED STRUJNOG UDARA, MEHANIČKIH ILI DRUGIH
RIZIKA.
VÝSTRAHA • TENTO PROVOZNÍ NÁVOD EXISTUJE POUZE V ANGLICKÉM JAZYCE.
(CS) • V PŘÍPADĚ, ŽE EXTERNÍ SLUŽBA ZÁKAZNÍKŮM POTŘEBUJE NÁVOD V
JINÉM JAZYCE, JE ZAJIŠTĚNÍ PŘEKLADU DO ODPOVÍDAJÍCÍHO JAZYKA
ÚKOLEM ZÁKAZNÍKA.
• NESNAŽTE SE O ÚDRŽBU TOHOTO ZAŘÍZENÍ, ANIŽ BYSTE SI PŘEČETLI
TENTO PROVOZNÍ NÁVOD A POCHOPILI JEHO OBSAH.
• V PŘÍPADĚ NEDODRŽOVÁNÍ TÉTO VÝSTRAHY MŮŽE DOJÍT
K PORANĚNÍ PRACOVNÍKA PRODEJNÍHO SERVISU, OBSLUŽNÉHO
PERSONÁLU NEBO PACIENTŮ VLIVEM ELEKTRICKÉHO PROUDU,
RESPEKTIVE VLIVEM MECHANICKÝCH ČI JINÝCH RIZIK.

3/87
 NanoCloud AWS Installation DOC2507368_r10
ADVARSEL • Denne servicemanual findes kun på engelsk.
(DA) • Hvis en kundes tekniker har brug for et andet sprog end engelsk, er det
kundens ansvar at sørge for oversættelse.
• Forsøg ikke at servicere udstyret medmindre
denne servicemanual har været konsulteret og er forstået.
• Manglende overholdelse af denne advarsel kan medføre skade på grund
af elektrisk, mekanisk eller anden fare for teknikeren, operatøren eller
patienten.
WAARSCHUWING • Deze onderhoudshandleiding is enkel in het Engels verkrijgbaar.
(NL) • Als het onderhoudspersoneel een andere taal vereist, dan is de klant
verantwoordelijk voor de vertaling ervan.
• Probeer de apparatuur niet te onderhouden voordat deze
onderhoudshandleiding werd geraadpleegd en begrepen is.
• Indien deze waarschuwing niet wordt opgevolgd, zou het
onderhoudspersoneel, de operator of een patiënt gewond kunnen raken
als gevolg van een elektrische schok, mechanische of andere gevaren.
WARNING • This Service Manual is available in English only.
(EN) • If a customer's service provider requires a language other than English, it
is the customer's responsibility to provide translation services.
• Do not attempt to service the equipment unless this service manual has
been consulted and is understood.
• Failure to heed this warning may result in injury to the service provider,
operator, or patient from electric shock, or from mechanical or other
hazards.
HOIATUS • Käesolev teenindusjuhend on saadaval ainult inglise keeles.
(ET) • Kui klienditeeninduse osutaja nõuab juhendit inglise keelest erinevas
keeles, vastutab klient tõlketeenuse osutamise eest.
• Ärge üritage seadmeid teenindada enne eelnevalt
käesoleva teenindusjuhendiga tutvumist ja sellest aru saamist.
• Käesoleva hoiatuse eiramine võib põhjustada teenuseosutaja, operaatori
või patsiendi vigastamist elektrilöögi, mehaanilise või muu ohu tagajärjel.

VAROITUS • Tämä huolto-ohje on saatavilla vain englanniksi.

(FI) • Jos asiakkaan huoltohenkilöstö vaatii muuta kuin englanninkielistä
materiaalia, tarvittavan käännöksen hankkiminen on asiakkaan vastuulla.
• Älä yritä korjata laitteistoa ennen kuin olet varmasti lukenut ja ymmärtänyt
tämän huolto-ohjeen.
• Mikäli tätä varoitusta ei noudateta, seurauksena voi olla huoltohenkilöstön,
laitteiston käyttäjän tai potilaan vahingoittuminen sähköiskun, mekaanisen
vian tai muun vaaratilanteen vuoksi.
ATTENTION • Ce manuel de service n'est disponible qu'en anglais.
(FR) • Si le technicien du client a besoin de ce manuel dans une autre langue
que l'anglais, c'est au client qu'il incombe de le faire traduire.
• Ne pas tenter d'intervenir sur les équipements
tant que le manuel service n'a pas été consulté et compris
• Le non-respect de cet avertissement peut entraîner chez le technicien,
l'opérateur ou le patient des blessures dues à des dangers électriques,
mécaniques ou autres.

4/87
 NanoCloud AWS Installation DOC2507368_r10
WARNUNG • Diese Serviceanleitung existiert nur in Englischer Sprache.
(DE) • Falls ein fremder Kundendienst eine andere Sprache benötigt, ist es
aufgabe des Kunden für eine Entsprechende Übersetzung zu sorgen.
• Versuchen Sie nicht diese Anlage zu warten,
ohne diese Serviceanleitung gelesen und verstanden zu haben.
• Wird diese Warnung nicht beachtet, so kann es zu Verletzungen des
Kundendiensttechnikers, des Bedieners oder des Patienten durch
stromschläge, Mechanische oder Sonstige gefahren kommen.

ΠΡΟΕΙΔΟΠΟΙΗΣΗ • Το παρόν εγχειρίδιο σέρβις διατίθεται στα αγγλικά μόνο.

(EL) • Εάν το άτομο παροχής σέρβις ενός πελάτη απαιτεί το παρόν εγχειρίδιο σε
γλώσσα εκτός των αγγλικών, αποτελεί ευθύνη του πελάτη να παρέχει
υπηρεσίες μετάφρασης.
• Μην επιχειρήσετε την εκτέλεση εργασιών σέρβις στον εξοπλισμό εκτός
εαν έχετε συμβουλευτεί και έχετε κατανοήσει το παρόν εγχειρίδιο σέρβις.
• Εαν δε λάβετε υπόψη την προειδοποίηση αυτή, ενδέχεται να προκληθεί
τραυματισμός στο άτομο παροχής σέρβις, στο χειριστή ή στον ασθενή
από ηλεκτροπληξία, μηχανικούς ή άλλους κινδύνους.
FIGYELMEZTETÉS • Ezen karbantartási kézikönyv kizárólag angol nyelven érhető el.
(HU) • Ha a vevő szolgáltatója angoltól eltérő nyelvre tart igényt, akkor a vevő
felelőssége a fordítás elkészíttetése.
• Ne próbálja elkezdeni használni a berendezést, amíg a karbantartási
kézikönyvben leírtakat nem értelmezték.
• Ezen figyelmeztetés figyelmen kívül hagyása a szolgáltató, működtető
vagy a beteg áramütés, mechanikai vagy egyéb veszélyhelyzet miatti
sérülését eredményezheti.
AÐVÖRUN • Þessi þjónustuhandbók er eingöngu fáanleg á ensku.
(IS) • Ef að þjónustuveitandi viðskiptamanns þarfnast annas tungumáls en
ensku, er það skylda viðskiptamanns að skaffa tungumálaþjónustu.
• Reynið ekki að afgreiða tækið nema að þessi þjónustuhandbók
hefur verið skoðuð og skilin.
• Brot á þessari aðvörun getur leitt til meiðsla á þjónustuveitanda,
stjórnanda eða sjúklings frá raflosti, vélrænu eða öðrum áhættum.
AVVERTENZA • Il presente manuale di manutenzione è disponibile soltanto in inglese.
(IT) • Se un addetto alla manutenzione richiede il manuale in una lingua
diversa, il cliente è tenuto a provvedere direttamente alla traduzione.
• Si proceda alla manutenzione dell'apparecchiatura solo dopo aver
consultato il presente manuale ed averne compreso il contenuto
• Il non rispetto della presente avvertenza potrebbe far compiere operazioni
da cui derivino lesioni all'addetto, alla manutenzione, all'utilizzatore ed al
paziente per folgorazione elettrica, per urti meccanici od altri rischi.

警告 • このサービスマニュアルには英語版しかありません。

• サービスを担当される業者が英語以外の言語を要求される場合、翻訳作
(JA)
業はその業者の責任で行うものとさせていただきます。

• このサービスマニュアルを熟読し理解せずに、装置のサービスを行わな
いでください。

• この警告に従わない場合、サービスを担当される方、操作員あるいは患
者さんが、感電や機械的又はその他の危険により負傷する可能性があり
ます。

5/87
 NanoCloud AWS Installation DOC2507368_r10

경고 • 본 서비스 지침서는 영어로만 이용하실 수 있습니다.

(KO) • 고객의 서비스 제공자가 영어 이외의 언어를 요구할 경우, 번역 서비스를

제공하는 것은 고객의 책임입니다.

• 본 서비스 지침서를 참고했고 이해하지 않는 한은 해당 장비를 수리하려고

시도하지 마십시오.

• 이 경고에 유의하지 않으면 전기 쇼크, 기계상의 혹은 다른 위험으로부터

서비스 제공자, 운영자 혹은 환자에게 위해를 가할 수 있습니다.

BRĪDINĀJUMS • Šī apkalpes rokasgrāmata ir pieejama tikai angļu valodā.

(LV) • Ja klienta apkalpes sniedzējam nepieciešama informācija citā valodā,
nevis angļu, klienta pienākums ir nodrošināt tulkošanu.
• Neveiciet aprīkojuma apkalpi bez apkalpes rokasgrāmatas izlasīšanas un
saprašanas.
• Šī brīdinājuma neievērošana var radīt elektriskās strāvas trieciena,
mehānisku vai citu risku izraisītu traumu apkalpes sniedzējam,
operatoram vai pacientam.
ĮSPĖJIMAS • Šis eksploatavimo vadovas yra prieinamas tik anglų kalba.
(LT) • Jei kliento paslaugų tiekėjas reikalauja vadovo kita kalba – ne anglų,
numatyti vertimo paslaugas yra kliento atsakomybė.
• Nemėginkite atlikti įrangos techninės priežiūros, nebent atsižvelgėte į šį
eksploatavimo vadovą ir jį supratote.
• Jei neatkreipsite dėmesio į šį perspėjimą, galimi sužalojimai dėl elektros
šoko, mechaninių ar kitų pavojų paslaugų tiekėjui, operatoriui ar pacientui.
ADVARSEL • Denne servicehåndboken finnes bare på engelsk.
(NO) • Hvis kundens serviceleverandør trenger et annet språk, er det kundens
ansvar å sørge for oversettelse.
• Ikke forsøk å reparere utstyret uten at denne servicehåndboken er lest og
forstått.
• Manglende hensyn til denne advarselen kan føre til at
serviceleverandøren, operatøren eller pasienten skades på grunn av
elektrisk støt, mekaniske eller andre farer.
OSTRZEŻENIE • Niniejszy podręcznik serwisowy dostępny jest jedynie w języku
angielskim.
(PL)
• Jeśli dostawca usług klienta wymaga języka innego niż angielski,
zapewnienie usługi tłumaczenia jest obowiązkiem klienta.
• Nie próbować serwisować wyposażenia bez zapoznania się i zrozumienia
niniejszego podręcznika serwisowego.
• Niezastosowanie się do tego ostrzeżenia może spowodować urazy
dostawcy usług, operatora lub pacjenta w wyniku porażenia
elektrycznego, zagrożenia mechanicznego bądź innego.
ATENÇÃO • Este manual de assistência técnica só se encontra disponível em inglês.
(PT-BR) • Se qualquer outro serviço de assistência técnica solicitar estes manuais
noutro idioma, é da responsabilidade do cliente fornecer os serviços de
tradução.
• Não tente consertar o equipamento sem ter consultado e
compreendido este manual de assistência técnica
• O não cumprimento deste aviso pode pôr em perigo a segurança do
técnico, do operador ou do paciente devido a choques elétricos,
mecânicos ou outros.

6/87
 NanoCloud AWS Installation DOC2507368_r10

ATENÇÃO • Este manual de assistência técnica só se encontra disponível em inglês.

(PT-PT) • Se qualquer outro serviço de assistência técnica solicitar este manual
noutro idioma, é da responsabilidade do cliente fornecer os serviços de
tradução.
• Não tente reparar o equipamento sem ter consultado e compreendido
este manual de assistência técnica.
• O não cumprimento deste aviso pode colocar em perigo a segurança do
técnico, do operador ou do paciente devido a choques eléctricos,
mecânicos ou outros.

ATENŢIE • Acest manual de service este disponibil numai în limba engleză.

(RO) • Dacă un furnizor de servicii pentru clienţi necesită o altă limbă decât cea
engleză, este de datoria clientului să furnizeze o traducere.
• Nu încercaţi să reparaţi echipamentul decât ulterior consultării şi
înţelegerii acestui manual de service.
• Ignorarea acestui avertisment ar putea duce la rănirea depanatorului,
operatorului sau pacientului în urma pericolelor de electrocutare,
mecanice sau de altă natură.

ОСТОРОЖНО! • Данное руководство по обслуживанию предлагается только на

английском языке.
(RU) • Если сервисному персоналу клиента необходимо руководство не на
английском, а на каком-то другом языке, клиенту следует
самостоятельно обеспечить перевод.
• Перед обслуживанием оборудования обязательно обратитесь к
данному руководству и поймите изложенные в нем сведения.
• Несоблюдение требований данного предупреждения может привести
к тому, что специалист по обслуживанию, оператор или пациент
получат удар электрическим током, механическую травму или другое
повреждение.

UPOZORENJE • Ovo servisno uputstvo je dostupno samo na engleskom jeziku.

(SR) • Ako klijentov serviser zahteva neki drugi jezik, klijent je dužan da obezbedi
prevodilačke usluge.
• Ne pokušavajte da opravite uređaj ako niste pročitali i razumeli ovo
servisno uputstvo.
• Zanemarivanje ovog upozorenja može dovesti do povređivanja servisera,
rukovaoca ili pacijenta usled strujnog udara ili mehaničkih i drugih
opasnosti.

7/87
 NanoCloud AWS Installation DOC2507368_r10
UPOZORNENIE • Tento návod na obsluhu je k dispozícii len v angličtine.
(SK) • Ak zákazníkov poskytovateľ služieb vyžaduje iný jazyk ako angličtinu,
poskytnutie prekladateľských služieb je zodpovednosťou zákazníka.
• Nepokúšajte sa o obsluhu zariadenia skôr, ako si neprečítate návod na
obluhu a neporozumiete mu.
• Zanedbanie tohto upozornenia môže vyústiť do zranenia poskytovateľa
služieb, obsluhujúcej osoby alebo pacienta elektrickým prúdom, do
mechanického alebo iného nebezpečenstva.
ATENCION • Este manual de servicio sólo existe en inglés.
(ES) • Si el encargado de mantenimiento de un cliente necesita un idioma que
no sea el inglés, el cliente deberá encargarse de la traducción del manual
• No se deberá dar servicio técnico al equipo, sin haber consultado y
comprendido este manual de servicio
• La no observancia del presente aviso puede dar lugar a que el proveedor
de servicios, el operador o el paciente sufran lesiones provocadas por
causas eléctricas, mecánicas o de otra naturaleza.
VARNING • Den här servicehandboken finns bara tillgänglig på engelska.
(SV) • Om en kunds servicetekniker har behov av ett annat språk än engelska
ansvarar kunden för att tillhandahålla översättningstjänster.
• Försök inte utföra service på utrustningen om du inte har läst och förstår
den här servicehandboken.
• Om du inte tar hänsyn till den här varningen kan det resultera i skador på
serviceteknikern, operatören eller patienten till följd av elektriska stötar,
mekaniska faror eller andra faror.

OPOZORILO • Ta servisni priročnik je na voljo samo v angleškem jeziku.

(SL) • Če ponudnik storitve stranke potrebuje priročnik v drugem jeziku, mora
stranka zagotoviti prevod.
• Ne poskušajte servisirati opreme, če tega priročnika niste v celoti prebrali
in razumeli.
• Če tega opozorila ne upoštevate, se lahko zaradi električnega udara,
mehanskih ali drugih nevarnosti poškoduje ponudnik storitev, operater ali
bolnik.
DIKKAT • Bu servis kilavuzunun sadece ingilizcesi mevcuttur.
(TR) • Eğer müşteri teknisyeni bu kilavuzu ingilizce dışında bir başka lisandan
talep ederse, bunu tercüme ettirmek müşteriye düşer.
• Servis kilavuzunu okuyup anlamadan ekipmanlara müdahale etmeyiniz.
• Bu uyarıya uyulmaması, elektrik, mekanik veya diğer tehlikelerden dolayı
teknisyen, operatör veya hastanın yaralanmasına yol açabilir.

8/87
 NanoCloud AWS Installation DOC2507368_r10
DAMAGE IN TRANSPORTATION
All packages should be closely examined at time of delivery. If damage is apparent write “Damage In Shipment” on
ALL copies of the freight or express bill BEFORE delivery is accepted or “signed for” by a General Electric
representative or hospital receiving agent. Whether noted or concealed, damage MUST be reported to the carrier
immediately upon discovery, or in any event, within 14 days after receipt, and the contents and containers held for
inspection by the carrier. A transportation company will not pay a claim for damage if an inspection is not requested
within this 14 day period.
To file a report:
• Call 1-800-548-3366 and use option 6.
• Fill out the GIQ workflow for any items missing, damaged, OBF/FOI for in process installs:
http://supportcentral.ge.com/ProcessMaps/form_new_request.asp?prod_id=268679&form_id=573167&node_id=19160
16&map_id=&reference_id=&reference_type
• Contact your local service coordinator for more information on this process.
CERTIFIED ELECTRICAL CONTRACTOR STATEMENT
All electrical Installations that are preliminary to positioning of the equipment at the site prepared for the equipment
shall be performed by licensed electrical contractors. In addition, electrical feeds into the Power Distribution Unit
shall be performed by licensed electrical contractors. Other connections between pieces of electrical equipment,
calibrations and testing shall be performed by qualified GE Medical personnel. The products involved (and the
accompanying electrical installations) are highly sophisticated, and special engineering competence is required. In
performing all electrical work on these products, GE will use its own specially trained field engineers. All of GE’s
electrical work on these products will comply with the requirements of the applicable electrical codes.

The purchaser of GE equipment shall only utilize qualified personnel (i.e., GE’s field engineers, personnel of third-
party service companies with equivalent training, or licensed electricians) to perform electrical servicing on the
equipment.

IMPORTANT...X-RAY PROTECTION
X-ray equipment if not properly used may cause injury. Accordingly, the instructions herein contained should be
thoroughly read and understood by everyone who will use the equipment before you attempt to place this
equipment in operation. The General Electric Company, Healthcare Group, will be glad to assist and cooperate in
placing this equipment in use.

Although this apparatus incorporates a high degree of protection against x-radiation other than the useful beam, no
practical design of equipment can provide complete protection. Nor can any practical design compel the operator to
take adequate precautions to prevent the possibility of any persons carelessly exposing themselves or others to
radiation.

It is important that anyone having anything to do with x-radiation be properly trained and fully acquainted with the
recommendations of the National Council on Radiation Protection and Measurements as published in NCRP
Reports available from NCRP Publications, 7910 Woodmont Avenue, Room 1016, Bethesda, Maryland 20814, and
of the International Commission on Radiation Protection, and take adequate steps to protect against injury.

The equipment is sold with the understanding that the General Electric Company, Healthcare Group, its agents, and
representatives have no responsibility for injury or damage which may result from improper use of the equipment.

Various protective materials and devices are available. It is urged that such materials or devices be used.

IMPORTANT…RADIOACTIVE MATERIAL HANDLING

Only employees formally trained in radioactive materials handling and this equipment are authorized by the GE
Healthcare Radiation Safety Officer to use radioactive materials to service this equipment.
GE Healthcare Services is required to notify the applicable U.S. state agency PRIOR to any source service event
involving pin source handling. See NUC/PET Radioactive material guides for specific instruction or contact your
EHS Specialist.

A radiation survey must be performed when a pin source has been removed and replaced. See Radiation Survey
Form Instructions or contact your EHS Specialist.
Rev 2 (July 21, 2005)
9/87
 NanoCloud AWS Installation DOC2507368_r10
OMISSIONS & ERRORS
Customers, please contact your GE Sales or Service representatives.
GE personnel, please use the GE Healthcare iTrak Process to report all omissions, errors, and defects in this
publication.

10/87
 NanoCloud AWS Installation DOC2507368_r10
REVISION HISTORY
Rev Date Author Reason For Change
1 07 Jan 2021 Wen Jianwei Initial version.
2 28 Jan 2021 Wen Jianwei Update contents.
3 06 Apr 2021 Yu Shasha Update document format to meet TW requirement.
Wen jianwei • Simplify the materias overview
• Add section acronyms and terms
• Separate the installation to 2 individualsections for AW3.2-3.4&ealier
and AW3.2-4.0&later
• Put the installation wizard procedure into section 6
• Remove the steps of configuring VM network for AW3.2-4.0&later
• Add description for new AWS name instead of the default name aws
• Add screens for reboot VM and AW server SSH enable
• Update the steps for solo client reinstall
4 01 Jul 2021 Wen jianwei 1, Separate the installation procedure to cover 4 cases:
• Section 5: Installation Procedure_AW3.2 EXT3.4 Or Earlier
• Section 6: Installation Procedure_AW3.2 EXT4.0 Or Later
• Section 7:Installation Procedure_AW3.2 EXT3.4 Or Earlier(Load
Image Files from USB directly)
• Section 8: Installation Procedure_AW3.2 EXT4.0 Or Later (Load
Image Files from USB directly)
2, Change the high threshold of image database auto-deletion to 80%
instead of 90%
3, Change the shell account from root to ctuser when mountUSB
5 06 Aug 2021 Wen jianwei 1. Statement “run installation wizard on CT console is recommended” in
section 6.2 and 8.2
2. Update section 6.2.3 and 8.2.3 by adding the steps of how to copy file
from Windows to CT console with no-using the command mountUSB
3. Correct the AW USB part number 5818084-4 in section 6.2 and 8.2
4. Add the installation time in the table of section 1
5. Add reinstall to be a troubleshooting way,as section9 step6
6. Add steps of remove the folder AWSVM in section 10
7. Add section 11.2 AWS upgrade from AW3.2 EXT3.4 to EXT4.0
8. Swap the section position of AWS uninstall and reinstall
6 22 Nov 2021 Wen jianwei 1. Remove ；
Section 7:Installation Procedure_AW3.2 EXT3.4 Or Earlier(Load
Image Files from USB directly)
Section 8: Installation Procedure_AW3.2 EXT4.0 Or Later (Load
Image Files from USB directly)
2. Put the section troubleshooting to be final section
3. Separate the section 8 client & AWS VM Uninstall in to 2 sub-section
8.1 and 8.2
4. Add uninstall Note in section 8.2
5. Update linux command of removing the VM folder
6. Update note for restore AWS configuration and user preference ,in
section 7.1
7. Change the instance of Install Wizard to that Windows based
8. Add autolaunch license installation and app configuration
9. Update command chown, add reference SN2469222 for smartscore
installation
7 28 Dec 2021 Wen jianwei 1. Add step install watchdog_new.sh in section 6.5 to fix issue of End
Of View (refer to DOC2449960)
2. Updated section 6.3.4 :the step of Configuring the platform setting
for installation wizard
8 30 May 2022 Wen jianwei 1. Updated the content typography architecture for the section 6
installation procedure_AW3.2 EXT4.0 ,based on the input/feedback
from Palermo, Dave and Cortez, Alejandro
2. Update the section 7 reinstall/update the NanoAWS
9 27 Jue 2022 Wen jianwei 1. Updated page 18,19，43,44 with the note and table for Workaround
for VV16 Ext. 4 USB which has 2 partitions
2. Added Appendix 2 - Renewal of Digital Certifcate
10 21 Mar 2023 1. Update the revision number
2. Add the rule for nanoAWS system ID in section 6.3.2 step17

11/87
 NanoCloud AWS Installation DOC2507368_r10
TABLE OF CONTENTS

Language ................................................................................................................................................................ 3
DAMAGE IN TRANSPORTATION ........................................................................................................................... 9
CERTIFIED ELECTRICAL CONTRACTOR STATEMENT .......................................................................................... 9
IMPORTANT...X-RAY PROTECTION ....................................................................................................................... 9
IMPORTANT…RADIOACTIVE MATERIAL HANDLING ............................................................................................ 9
OMISSIONS & ERRORS ........................................................................................................................................ 10
1 OVERVIEW ....................................................................................................................................................... 13
2 REFERENCE AND PREREQUISITES............................................................................................................. 13
3 MATERIALS OVERVIEW................................................................................................................................. 14
4 ACRONYMS AND TERMS............................................................................................................................... 14
5 INSTALLATION PROCEDURE_AW3.2 EXT3.4 OR EARLIER ...................................................................... 15
5.1 Image Files Preparation ............................................................................................................................... 16
5.1.1 Virtual Machine Image File Preparation ............................................................................................. 16
5.1.2 Volume Viewer APPS SW (*.iso) Image File Preparation .................................................................. 17
5.2 Virtual Machine Create ................................................................................................................................ 19
5.3 AWS VM Network Configuration .................................................................................................................. 21
5.4 AWS Configuration Using Service Tools ........................................................................................................ 23
5.5 SOLO Client Installation and Configuration on CT Console ............................................................................ 38
6 INSTALLATION PROCEDURE_AW3.2 EXT4.0 ............................................................................................. 41
6.1 Virtual Machine Image File Preparation ........................................................................................................ 42
6.2 Virtual Machine Create ................................................................................................................................ 44
6.3 Installation Wizard ...................................................................................................................................... 45
6.4 Displaying the AW Server Console ............................................................................................................... 52
6.5 Nano AWS Initial Launch of AWS Service Tool .............................................................................................. 53
6.6 Configure the Auto Delete to avoid running out of space in the Image Disk .................................................... 55
6.7 Installing Volume Viewer .............................................................................................................................. 57
6.8 System Configuration Registration ................................................................................................................. 58
6.9 Back up the Configuration/User Preferences if needed.................................................................................... 58
6.10 Finish the Maintenance Mode ....................................................................................................................... 59
6.11 Create the new watchdog_new.sh file on your laptop ..................................................................................... 60
6.12 SOLO Client Installation ................................................................................................................................ 61
6.13 Testing REFORMAT ....................................................................................................................................... 63
7 REINSTALL / UPDATE NAONOAWS ............................................................................................................. 64
7.1 Start to Reinstall An Existing AWS VM .......................................................................................................... 64
7.2 Open QEMU/KVM - Run virt-manager ........................................................................................................... 65
7.3 AWS-VM Configuration Status Check before Continuing ............................................................................... 66
7.4 Launch AWS Service Tool for the First Time .................................................................................................. 68
7.5 Nano AWS Configuration Check ............................................................................................................... 70
Note: or you can generate the registration key by following the steps in Section6.8 if required ............................. 73
7.6 Reinstall the AWS client ............................................................................................................................ 75
7.7 Configure AWS Application ....................................................................................................................... 76
7.8 AWS upgrade from AW3.2 ext3.4 to ext4.0 ................................................................................................... 78
8 SOLO CLIENT & AWS VM UNINSTALL PROCEDURE................................................................................. 79
8.1 Solo Client uninstall. .................................................................................................................................... 79
8.2 VM uninstall. ............................................................................................................................................... 79
9 COMMON TROUBLESHOOTING ................................................................................................................... 81
APPENDIX 1 - GENERATE LICENSES FOR AWS ............................................................................................ 85
APPENDIX 2 - RENEWAL OF DIGITAL CERTIFCATE...................................................................................... 86

12/87
 NanoCloud AWS Installation DOC2507368_r10

1 Overview
The main purpose is to describe the installation process for virtual machine based AWS(NanoCloud AWS) which is running on CT host.
This will be a guidance to execute the installation, uninstall, reinstall, troubleshooting and update of the NanoCloud AWS.

This installation procedure provides installation methods, includes:

• AW3.2 Ext 3.4 and earlier, refer to Section 5: Installation Procedure_AW3.2 EXT3.4 Or Earlier

• AW3.2 Ext 4.0 and later, refer to Section 6: Installation Procedure_AW3.2 EXT4.0

Labor required：2-2.5h / 1 person

2 Reference and Prerequisites

Table 1. Reference Document

Document Number Title
5719443-1EN AWS 3.2 Installation and Service Manual
5719443-8EN AW Server 3.2 Ext. 4.0 Installation and Service Manual
5818084 or 5818084-3 AW Server 3.2 Ext.3.2 (or Ext.3.4) SW and Docs for Virtual Machine
5812898 or 5837030-2 Volume Viewer Apps 15.0 Ext.2 (or Ext.6.x) SW and Docs for Virtual AW Server

Table 2. Required Conditions

Condition Reference Effectivity
Only trained service personnel should service the GE CT Scanner. - -
Some Linux shell command knowledge, familiar with vi editor for file modification. - -
Laptop and network for accessing the GE elicense web: - -

http://elicense.gehealthcare.com/elicense.

https://awcct.gehealthcare.com.

AW Server SW kit. - -
Volume Viewer Apps SW kit. - -

13/87
 NanoCloud AWS Installation DOC2507368_r10
3 Materials Overview

1. USB disk for AW Server 3.2 Ext *.* SW or later in AW Server SW ki (Similar with below figure).

2. DVD or USB media for Volume Viewer which will be used for AW Server configuration.

3. If DVD delivered for Volume Viewer, you need to confirm if the CD/DVD drive device is in filed, you have to:
Take a DVD drive (or GE CD/DVD tower) to the site.
4 Acronyms and terms
Acronym Description
AE Application Entity
AET Application Entity Title
AW Advanced Workstation
AWS AW Server
DICOM Digital Imaging and Communications in Medicine
DDC DICOM Direct Connect
iso iso is a kind of optical disc image file, ISO image is an archive file of optical disc, which is one of the types of disk
image
KVM Kernel-based Virtual Machine
NanoCloud A kind of Advanced Workstation server based on linux virtual machine, sometimes simplely call NanoAWS
AWS
QCOW2 The QCOW2 image format is one of the disk image formats supported by QEMU
QEMU QEMU is a generic and open source machine emulator and virtualizer
VM Virtual Machine
VV Volume Viewer
14/87
 NanoCloud AWS Installation DOC2507368_r10
5 Installation Procedure_AW3.2 EXT3.4 Or Earlier

Note: See Section 6 for AW3.2 EXT4.0 Installation Procedure

Confirm you have read Section1 Overview to understand and select your installation case correctly

This diagram represents the AWS installation and configuration procedure.

Figure 1. AWS Installation Procedure for AW3.2 EXT3.4 or earlier

Preparation:

You need to confirm the Host Name (Reconfig→Network→Host Name) with the customer , and configure the expected Hostname in
Reconfig if required, This Host Name will be use when configure the "DICOM Host" later and not suggest to modify after AWS
installation completed.

Open an Unix shell and check the Hostname by command: hostname

Below is example

15/87
 NanoCloud AWS Installation DOC2507368_r10
5.1 Image Files Preparation
The purpose of this section is to copy the required image files from USB disk or DVD to the CT Console.

NOTE:

The content with the symbol > means the Linux command you need to type in shell terminal.

The content with the symbol # means command notes, or action you need to execute.
In below contents, some file is described as aws-3.2-x.x-0-diskxxx.qcow2.iso, here the x.x x.x-0-diskxxx means you need to find the
specific file name from your USB or CD media, since this may changes as AWS new version release, such as aws-3.2-3.4-
1.qcow2.iso.
NanoAWS on CT host is only used for image post-processing,The other AWS features which are not mentioned in this manual are
not applicable.

5.1.1 Virtual Machine Image File Preparation

Copy the aws-3.2-x.x-0-diskxxx.qcow2.iso (or .qcow2) file of AW Server 3.2 Ext x.x SW from USB disk (mentioned in section 1) to CT
Console:

Steps below we use the format .qcow2.iso as an example, it may be .qcow2 in some version.

NOTE: For different AWS version, .qcow2.iso or .qcow2 file may be in /USB/ or /USB/image/ or the other folder of the USB media from
AWS Kit.

#Open a new unix shell terminal

>mkdir -p /usr/g/AWS_VM # NOTE: Make sure mkdir command is done under the ctuser account.
#Insert the usb disk to console
>mountUSB #run commands just under the shell account of ctuser
>cd /USB
>ls
>cp aws-3.2-3.4-1.qcow2.iso.md5 /usr/g/AWS_VM
>cp aws-3.2-3.4-1.qcow2.iso /usr/g/AWS_VM #it may take about 3-5 minutes
>cd /usr/g/AWS_VM
>ls #list the files in folder
>md5sum aws-3.2-3.4-1.qcow2.iso
#calculate the md5 value of the file
>more aws-3.2-3.4-1.qcow2.iso.md5
#check the md5 value, should be same with the value calculated in the step above (if different
you have to copy the *.qcow2.iso from USB again)
>unmountUSB
#Remove/Unplug the USB disk

16/87
 NanoCloud AWS Installation DOC2507368_r10
5.1.2 Volume Viewer APPS SW (*.iso) Image File Preparation

Copy the AWE-Voxtool-vxtl_xx.x-x.xx.x86_64.iso file of Volume Viewer APPS SW from DVD/USB to CT Console:

In the case of DVD delivery. (AWE-Voxtool-vxtl_15.0-2.0.x86_64.iso)

#Insert the DVD media into the CD/DVD drive for the console in site.
#Open a unix shell from Toolchest.
>su -
#type the password (usually "#bigguy"), then press enter
>lsscsi #check the name of CD/DVD is /dev/sr0
>mount /dev/sr0 /mnt/cdrom
>cd /mnt/cdrom
>ls #find out the file *.iso and *.md5
>cp *.iso /usr/g/AWS_VM/ #wait some minutes for the replication
>cp *.md5 /usr/g/AWS_VM/
>cd /usr/g/AWS_VM
>chown ctuser:ctuser AWE-Voxtool-vxtl_15.0-2.0.x86_64.iso
>md5sum AWE-Voxtool-vxtl_15.0-2.0.x86_64.iso #calculate the md5 value of the file
>more AWE-Voxtool-vxtl_15.0-2.0.x86_64.iso.md5 #open the file *.md5 and check the md5 value, should be same
with the value in the step above (if different you have to copy the *.iso from USB again)
>exit #Exit from root back to ctuser, then remove the DVD

In the case of USB delivery ( Here AWE-Voxtool-vxtl_15.0-6.2.x86_64.iso is an example)

Note: mountUSB maybe not available for the version AWE-Voxtool-vxtl_16.0-4.x or similar version which has 2 partition in the
USB ,please skip to the table below (Workaround for VV16 Ext. 4 USB which has 2 partitions)

#Insert the USB disk to the console USB port

>mountUSB #run commands just under the shell account of ctuser
>cd /USB/"the actual location of the .iso file"
>ls
>cp *.iso /usr/g/AWS_VM/
>cp *.md5 /usr/g/AWS_VM/
>cd /usr/g/AWS_VM
>md5sum AWE-Voxtool-vxtl_15.0-6.2.x86_64.iso #calculate the md5 value of the file
>more AWE-Voxtool-vxtl_15.0-6.2.x86_64.iso.md5 #open the file *.md5 and check the md5 value, should be same
with the value in the step above (if different you have to copy the *.iso from USB again)
>unmountUSB
# Remove/Unplug the USB

17/87
 NanoCloud AWS Installation DOC2507368_r10
• Workaround for VV16 Ext. 4 USB which has 2 partitions
In this case the command mountUSB will mount the unavailable partition , so it is required to mount the right partition by the steps below
>lsblk #The USB device will be displayed as the last item or top item in the USB block device, as highlighted sde2 in the example below
>su -
# type the password , then press enter
>mount /dev/sde2 /tmp
>cd /tmp
>ls # display the files in folder
>cp VV_Apps_16.0ext4._sw_aw_aws.iso /usr/g/AWS_VM
>cd /usr/g/AWS_VM
>ll # display the file details in folder
>chown ctuser:ctuser VV_Apps_16.0ext4._sw_aw_aws.iso
>ll # see example below permissions changed
>md5sum VV_Apps_16.0ext4._sw_aw_aws. iso #calculate the md5 value of the file
>more VV_Apps_16.0ext4._sw_aw_aws.iso.md5 #open the file *.md5 and check the md5 value, should be same with
the value in the step above (if different you have to copy the *.iso from USB again)
>umount /dev/sde2
# Remove/Unplug the USB

Example

18/87
 NanoCloud AWS Installation DOC2507368_r10
5.2 Virtual Machine Create

1. Run the script deployVMGUI.sh (Make sure the shell user is "ctuser", not at the user root):

> cd /usr/g/ctuser/VMDeploy/scripts
> deployVMGUI.sh

2. Select or confirm the information:

Select Nano Type and confirm the Current Memory, Max Memory
NOTE: The Memory size will change according to system type automaticity.

Product Nano Type Memory Size

Optima CT520/CT540/Advance/CT620, TAI-X 4k 24G
Revolution Maxima/Ace, Optima CT680 Current Memory: 12288MB
Expert
Max Memory: 24576MB

Autostart selected
Vm name: aws,( you can change the name if the customer required, e.g. change to nanoaws-ct as below,if so you must use this
new name at all steps below where need to setup the VM or AW server name instead of the default name “aws”)
Recommend to use the default name aws if there is no special requirement

aws vCPU number: 8

Just reinstall/replace the VM image disk: Default unselected, for first installation please skip this step. It only for the situation
you need to reinstall/replace the VM image disk.
VM graphical console port: 5908

3. Subnet. By default it is 192.168.101 .x/24. Please contact with the IT manager of the site to check whether the console IP use
192.168.101.* or not. If conflict, please select "Custom virt private subnet" and set this Subnet to 192.168.102 .x/24 to avoid
IP conflicts.

Recommend to use the default IP segment if there is no special requirement

4. Image Source.
For AW3.2 EXT3.4 or previous version.
Press Browse to choose the .qcow2.iso (or .qcow2) image. (/usr/g/AWS_VM )
19/87
 NanoCloud AWS Installation DOC2507368_r10
Destination directory: /usr/g/ctuser/AWSVM, no need modify. Click

click Deploy, enter CT root password to continue.

5. It will take several minutes, then the following message appears as below, please confirm it shows.

6. Run virt-manager.
Run command below with account ctuser
>virt-manager

#to open the Virtual machine manager, double click on QEMU/KVM-not connected.

Double click on the virtual machine to open the linux window, then login in the VM with user: root and password: Tbd&bu

20/87
 NanoCloud AWS Installation DOC2507368_r10

5.3 AWS VM Network Configuration

Type the following command in VM terminal:

>bash /root/sys-net-conf

1. Confirm / Set the network information by arrow keys on keyboard, as the picture below. Then press Tab to select OK(must).

NOTE: If you set IP segment to 192.168.102 in section Virtual Machine Create, the IP segment here should be also 102.
NOTE: if you changed the VM name in 5.2,you need to setup the new name for Hostname here

Network UI for AW3.2-3.4 or earlier:

2. For AW3.2-3.4 or earlier,Wait until the network configuration completes, then reboot the VM.
NOTE: you should pull the scroll bar to the bottom to monitor the latest status.

>reboot #to reboot the system, need about 3 minutes

Wait for restarting and logining again, user: root, and password: Tbd&bu

3. Ping the gateway, it should be successful. Type on the VM terminal:

21/87
 NanoCloud AWS Installation DOC2507368_r10
>ping 192.168.101.1 #or 192.168.102.1 if you set IP segment to 192.168.102.x in Virtual Machine Create

#"Ctrl+c" to stop ping

4. Update modgecsi.conf in VM.

Edit /etc/httpd/conf.d/modgecsi.conf in the <Location /gecsi> section and add 2 lines commands. Refer the commands
below :

>vi /etc/httpd/conf.d/modgecsi.conf
#Press Insert key on keyboard, then add the following lines, as shown in the image below:
Order Allow,Deny
Allow from 192.168.101.1 #or 192.168.102.1 if you set IP segment to 192.168.102.x in Virtual Machine Create
#Press Esc on keyboard, then pull down the scroll bar to bottom
>:wq! #type in ":wq!" and Press Enter on keyboard to save and quit from vi mode

Refer to the picture below:

22/87
 NanoCloud AWS Installation DOC2507368_r10
5.4 AWS Configuration Using Service Tools

1. Open the AWS service tool via: CSD→Configuration→Configuration AWS on VM →Launch AWS Service Tool, as below:

NOTE: You need to type 192.168.102.5 in browser address bar manually if you set the VM IP as 192.168.102.5 in AWS VM Network
Configuration.

2. AW Server page will appear, similar as below:

23/87
 NanoCloud AWS Installation DOC2507368_r10

3. Select the Service and Administrative Tools, press launch. (Attention: If the web page can not open the page and shows not
security, please press Advanced→Add Exception→Confirm Security Exception , or similar button in different browser version).

Then login with user: service, password: Geiaw&08.

NOTE:
For repeated installation, if you have saved System Configuration backup or User Preference, you can restore it before step 4
below (In AWS service tool: Maintenance→Restore). The license(s) of step 4 need apply again if the license ID changed.

24/87
 NanoCloud AWS Installation DOC2507368_r10

4. In Initial Configuration→Platform Configuration, use the License ID to generate the specific.

Platform license Key
CoLa enabler license Key
DICOM Direct Connect (DDC) Key
Floating license (depend on the program scope)

elicense web page: http://elicense.gehealthcare.com/elicense/

NOTE: You can find the license generation procedure in the section Appendix 1 - Generate Licenses for AWS.

The email from elicense web will include the information, below is example only may not cover some AW

applications due to the product PCM difference:

25/87
 NanoCloud AWS Installation DOC2507368_r10

5. Configure the platform Initial configuration→Platform Configuration. Select the appropriated Platform Enabler (SdC_Nano_4k, it
depends on the Platform License Key you got, see the red circle marked in the second figure of step 4) and enter the corresponding
Platform License Key previously generated.

6. Press Next. Then Select Single mode, press Next.

26/87
 NanoCloud AWS Installation DOC2507368_r10

7. Select the DICOM Direct Connect enabler. Enter the License key for DICOM Direct Connect, and enter the Authentication URL:
h ttp://192.168.101.1:9998/host (or h ttp://192.168.102.1:9998/host if you set IP segment to 192.168.102.x in Virtual Machine
Create).

Then Press Apply (no need Check Address), click OK on the pop-up windows and wait until a pop-up window shows Please reboot
the system.

8. Reboot the VM: go to Tools→Reboot, press Reboot AW Server.

27/87
 NanoCloud AWS Installation DOC2507368_r10

9. After the system rebooted, launch and login the AWS service tool again (user: service, password: Geiaw&08), and setup the Time
setting in Initial Configuration→Time Settings (press Apply after your selections).

10. Initial Configuration→Database Deletion Settings, configure as below, then press

Apply. Set "Auto delete status" to On
Set "Start when image database reaches" to 80%
Set "Stop when image database reaches" to 70%
Set "Remove image(s) from system database older than" to 2 hours
Set "Start auto delete process every" to 2 hours

28/87
 NanoCloud AWS Installation DOC2507368_r10

11. Configure CoLA server: Initial Configuration→Licensing→CoLA Server. Select the Built-in check box and enter the CoLA Server
enabler license key, then press Apply.

12. Optional: Configure Initial configuration->Licensing->Preprocessing

Select Preprocessing Enabler and type in the license key of AutoLaunch ,then click Apply,

29/87
 NanoCloud AWS Installation DOC2507368_r10

13. Select Administrative→Configuration→DICOM Hosts. Press add new host, and enter the box with *.
• Name, Host Name,Applicable Entity Title. All these 3 names should be same with the CT Host name
• IP Address. should be 192.168.101.1, or 192.168.102.1 if you set IP segment to 192.168.102.x in Virtual Machine Create
• Port:4006
Then press Apply. as picture below

NOTE: Make sure you have confirmed the Host Name (Reconfig→Network→Host Name)with the customer.

30/87
 NanoCloud AWS Installation DOC2507368_r10

14. Configure End Of Review via Administrative→Configuration→End Of Review, select Type: All, Modality: select all the options,
then press Apply.

15. Fill the Initial Configuration→Device Data with the corresponding information, then press Apply.

31/87
 NanoCloud AWS Installation DOC2507368_r10

16. Go to Tools→Terminal, turn on the SSH access. The purpose is to enable the remote access to VM via ssh connection

17. Install the floating licenses which you generated previously under Initial Configuration→Licensing→Floating License.

18. VV application preparation.

To make sure you have completed section 4.1.2 Volume Viewer APPS SW (*.iso) Image File Preparation.
19. Under Maintenance→Version management, click ok to close the prompt box ,click on Upload ISO,
In pop window select the .iso file of Volume Viewer APPs in /usr/g/AWS VM
In the next pop window click send to system
Then select Volume Viewer Apps 13.0-0.42(or later versions) as below, click Install, need 5-8 minutes.

32/87
 NanoCloud AWS Installation DOC2507368_r10

If customer has purchased more Applications, repeat this step to upload/install iso files, such as SmartScore4.0(reference SN2469222)
shown below.

20. After the installation is done, select the tab License Activation tab and press Select Available, then confirm the selected apps in
list (the Applications selected depends on the floating licenses you got, figure below is example only,the button Apply is gray and
un-clickable by default and it only requires click when you changed the app selection manually).

33/87
 NanoCloud AWS Installation DOC2507368_r10

21. Preprocessing ( optional )

If AutoLaunch license was install in step 12, please contact application specialist to configure the applications for Preprocessing，in
Administrative->Configuration->Preprocessing , below is an example only

34/87
 NanoCloud AWS Installation DOC2507368_r10

22. Register Configuration

Generate the register key and activate it. (Maintenance→Register Configuration), see the follow picture:
A. Press Export Configuration, in the pop window press Save File to export the configuration file to CTConsole, default saving
path: /usr/g/ctuser/Downloads/, it is a .txt file.
B. Copy the configuration file to your laptop, visit the site (https://awcct.gehealthcare.com), and upload the configuration file, press
submit to generate the Registration Key.
C. Enter the Registration Key into block, then press Install Registration Key.

23. Back up the Configuration/User Preferences if needed.

A. In service Tool and go to Maintenance→Backup→System configuration.
B. Keep everything selected and press Pull from system, waiting until completed.
C. The backup .tar.gz file will be saved to the CT Console system: /usr/g/ctuser/Downloads/.
D. Copy this backup file to a USB media in case of necessary restore in the future.

35/87
 NanoCloud AWS Installation DOC2507368_r10

NOTE: In some sites the application expert or the user creates new protocols(e.g. DMPR protocols) in nanoAWS, the new protocols
could be saved as backup for the reinstall in future,do it via Maintenance→Backup→User Preferences

36/87
 NanoCloud AWS Installation DOC2507368_r10
24. Finish the Maintenance mode and reboot the VM.
A. Finish the Maintenance mode. Maintenance→Maintenance→Finish Maintenance

B. Reboot the VM: go to Tools→Reboot, press Reboot AW Server.

Reboot may take 3-5 minuts, refresh this page until it shows the page of AW Serve, that means the VM reboot successfully. Then
you can close the browser and go to next.

37/87
 NanoCloud AWS Installation DOC2507368_r10

5.5 SOLO Client Installation and Configuration on CT Console

1. Open CSD→Service Configuration→ Configuration AWS on VM→AWS Client Install/Uninstall.

Then select Install.

2. Check the pop information as shown below (The IP Address should be the address you set in AWS VM Network Configuration,
the Host Name is "aws" by default,but if you changed the name in 5.2 and 5.3 ,you need to setup the new name as
Host Name here)
Then press Accept and wait until the installation completed.

38/87
 NanoCloud AWS Installation DOC2507368_r10

3. After installation, click the button Configure AWS Applications.

4. Select the applications which needed, then press Accept (Figure is an example, please select only the applications which the
customer has purchased).

Below shows the Apps catalog and the corresponding options.The actual purchased Apps may be more or less than below.

NOTE:

• DO NOT check the corresponding buttons in ImageWork window due to the display may not be correct before system reboot.

• For more AW apps which are not included in this figure please refer to the corresponding training material or ask for assist to
Application Specialist or service expert(TSE)

• This figure is example only , the AW apps name and BCAT may be changed due to the AW software update, please refer to the
corresponding training material or ask for assist to Application Specialist or service expert(TSE)

39/87
 NanoCloud AWS Installation DOC2507368_r10

5. Then Restart the CTConsole, check the AWS APPs buttons and run them to make sure they can work well. Below shows
the Apps catalog and the buttons.

If it pops up a window of AW Server Certificate ,click ok

40/87
 NanoCloud AWS Installation DOC2507368_r10

6 Installation Procedure_AW3.2 EXT4.0

Confirm you have read Section1 Overview to understand and select your installation case correctly

This diagram represents the AWS installation and configuration procedure for AW3.2 EXT4.0

Figure 2. AWS Installation Procedure for AW3.2 EXT4.0

Preparation:

You need to confirm the Host Name (Reconfig→Network→Host Name) with the customer , and configure the expected Hostname
in Reconfig if required, This Host Name will be use when configure the "DICOM Host" later and not suggest to modify after AWS
installation completed.

Open an Unix shell and check the Hostname by command: hostname

Below is example

41/87
 NanoCloud AWS Installation DOC2507368_r10

6.1 Virtual Machine Image File Preparation

Copy the aws-3.2-x.x-0-diskxxx.qcow2.iso (or .qcow2) file of AW Server 3.2 Ext x.x SW from the USB key to the CT
Console:
The below procedure use the format .qcow2.iso as an example, other version can be aws-3.2-x.x-0-diskxxx.qcow2

1. Select the Common Service Desktop (CSD), then press ALT + F3, open a Unix shell, DO NOT switch to root user.
In the Unix shell type:
whoami [enter]
ctuser  you are ctuser, continue. If the reply is root, type exit, then type whoami again
2. mkdir -p /usr/g/AWS_VM [enter]
3. Install the OS and AWS Server 3.2 Ext 4 USB disk, or later, into any USB port in the console
4. mountUSB [enter]
Ignore the warning message “You are not superuser. Watch out for permissions.”
5. cd /USB [enter]
6. ls -al [enter] (this command lists the files in the USB)
7. cp aws-3.2-4.0-4.qcow2.iso.md5 /usr/g/AWS_VM [enter]
Notes:
 The filename may be different depending on the AWS Server version
 You can highlight the file with the left button of the mouse, then press the middle button to paste
8. cp aws-3.2-4.0-4.qcow2.iso /usr/g/AWS_VM [enter]
it may take 10 minutes to copy the file
9. Unmount the OS and AWS Server 3.2 Ext 4 USB disk
cd / [enter]
unmountUSB [enter]
10. Remove the AWS Server 3.2 Ext 4 USB Disk
11. Install the Volume Viewer Apps Software (AWE-Voxtool-vxtl_15.0-8.25.x86_64 USB disk), into any USB port.
Note: mountUSB maybe not available for the version AWE-Voxtool-vxtl_16.0-4.x or similar version which has 2 partition in the
USB ,please skip to the table below (Workaround for VV16 Ext. 4 USB which has 2 partitions)
{ctuser@ct99} mountUSB [enter]
WARNING: “You are not superuser. Watch out for permissions.”  IGNORE THIS MESSAGE!
{ctuser@ct99} cd /USB [enter]
{ctuser@ct99} ls -al [enter]
{ctuser@ct99} cp AWE-Voxtool-vxtl_15.0-8.25.x86_64.iso /usr/g/AWS_VM [enter]
Note: The filename may be different depending on the AWS Server version.
{ctuser@ct99} cp AWE-Voxtool-vxtl_15.0-8.25.x86_64.iso.md5 /usr/g/AWS_VM [enter]
Note: The filename may be different depending on the AWS Server version
12. Unmount the AWE-Voxtool-vxtl_15.0-8.25.x86_64 USB disk
cd / [enter]
unmountUSB [enter]
Remove the USB Drive
13. cd /usr/g/AWS_VM [enter]
14. ls -al [enter]
15. md5sum aws-3.2-4.0-4.qcow2.iso [enter]
Calculates the md5 value of the file
16. more aws-3.2-4.0-4.qcow2.iso.md5 [enter]
 Checks the md5 value, should be the same value calculated in step 16, if the value is the same, continue to Section 2, if
different, you have to copy the *.qcow2.iso again.
 If this is the second (or more) attempt loading the Nano Software, the checksum value will be different between
steps 16 and 17, this is normal.
Note: If customer purchased SmartScore 4.0 option, copy the file to the /usr/g/AWS_VM directory
Example: {ctuser@ct99} cp SmartScore_4.0_317.iso /usr/g/AWS_VM
Notes:
o The filename may be different depending on the Smart Score version.
o You may need a CD/DVD Drive to copy the Smart Score iso file from the CD media to a USB Drive

42/87
 NanoCloud AWS Installation DOC2507368_r10
• Workaround for VV16 Ext. 4 USB which has 2 partitions
In this case the command mountUSB will mount the unavailable partition , so it is required to mount the right partition by the steps below
>lsblk #The USB device will be displayed as the last item or top item in the USB block device, as highlighted sde2 in the example
below
>su -
# type the password , then press enter
>mount /dev/sde2 /tmp
>cd /tmp
>ls # display the files in folder
>cp VV_Apps_16.0ext4._sw_aw_aws.iso /usr/g/AWS_VM
>cd /usr/g/AWS_VM
>ll # display the file details in folder
>chown ctuser:ctuser VV_Apps_16.0ext4._sw_aw_aws.iso
>ll # see example below permissions changed
>md5sum VV_Apps_16.0ext4._sw_aw_aws. iso #calculate the md5 value of the file
>more VV_Apps_16.0ext4._sw_aw_aws.iso.md5 #open the file *.md5 and check the md5 value, should be same
with the value in the step above (if different you have to copy the *.iso from USB again)
>umount /dev/sde2
# Remove/Unplug the USB

Example

43/87
 NanoCloud AWS Installation DOC2507368_r10

6.2 Virtual Machine Create

1. Run the following commands as ctuser, not as root.

In the Unix shell type:
 whoami [enter]
ctuser  you are ctuser, continue. If the reply
is root, type exit, then type whoami again.
 cd /usr/g/ctuser/VMDeploy/scripts [enter]
 deployVMGUI.sh [enter]

NOTE: DO NOT close this terminal window

2. Verify system type.

 Go to the Home page of the Common Service
Desktop
or
Type check_config in a Unix shell.

3. Select Nano Type, according to the System type,

refer to table below.
 Verify the Current Memory, Max Memory,
according to the Table below.
The Memory size will be updated automatically once
the system type is selected.

System Type Nano Type Memory Size

Optima 24G
CT520/CT540/Advance/CT620, TAI-X 4k  Current Memory: 12288MB
Revolution Maxima/Ace,  Max Memory: 24576MB
Optima CT680Expert,
Revolution Advance , Discovery RT

Revolution Ascend NGX 12K 26G

 Current Memory: 26624MB
 Max Memory: 26624MB

 Autostart selected
 Vm name: aws
You can change the name if customer requires. e.g., change it to nanoaws-ct, if so, you must use this new name in all the steps
44/87
 NanoCloud AWS Installation DOC2507368_r10
where the VM or server name needs to be setup, instead of the default name “aws”
Recommend to use the default name if there is no special requirement.
 vCPU number: 8
 Just reinstall/replace the VM image disk: Unselected.
 VM graphical console port: 5908
 Subnet: Default is 192.168.101 .x/24.
Contact the IT department to check if IP 192.168.101.* can be used. If conflict, please select "Custom virt private subnet" and
set the Subnet to 192.168.102 .*/24 to avoid IP conflicts.
Recommend using the default IP Address (192.168.101.*) if there is no special requirement.

4. Click [Image Source] Browse button

5. Select /usr/g/AWS_VM/aws-3.2-4.0-4.qcow2.iso
 Select /usr/g/
 Select the AWS_VM folder
 Select the aws-3.2-4.0-4.qcow2.iso or the proper
filename for the version you are loading.
 Click Open

Note: the filename may be different depending on the

AWS Server version.

6. A pop-up window appears, DO NOT click OK as this

window will close, this information will be used to
configure the AWS Server using the Installation
Wizard.

DO not re-browse the qcow2.iso file, this will change the

MAC Address, thus you have to regenerate new
licenses.

6.3 Installation Wizard

The Installation Wizard is included in the AW 3.2 Ext. 4.0

Software USB drive (P/N 5818084-4)
The Installation Wizard can be run in the CT Console or in
your laptop. It is recommended to run it in your
laptop.
Example below of the USB content:

6.3.1 Running the Installation Wizard

o On your laptop, create a folder and name the folder:

AWS Ext 4.0
o Install the OS & AW 3.2 Ext. 4 Software USB key in
any available USB port on the laptop.
 A window will popup listing the content of the
USB key.
o Copy the files highlighted in yellow to the AWS Ext
4.0 folder you just created on your laptop.
o Remove the OS & AW 3.2 Ext. 4 USB key.
o Go to the AWS Ext 4.0 folder on your laptop, double
click on startinstallwizard.bat

45/87
 NanoCloud AWS Installation DOC2507368_r10
6.3.2 Starting the Installation Wizard Configuration

In the Start New Configuration tab of the

Installation Wizard:
1. Select New, then click on Create

2. In the Network Tab, enter the following

information:
Host Name: aws
IP Address: 192.168.101.5 (see note*)
Network Prefix: 24
Gateway: 192.168.101.1 (see note*)
MAC Address as listed in the Generated
Network Information.
Example: 52:54:00:2f:ab:58

*Note: set IP to 192.168.102.*, if there is

a conflict with IP Address 192.168.101.*

3. Select the Region and City. No need to

enter any other information.

4. Select Next

46/87
 NanoCloud AWS Installation DOC2507368_r10

5. Write down the License ID

6. Click on Go to eLicense Site to access the eLicense
website or access the eLicense website from
http://elicense.gehealthcare.com/elicense/

this URL is available via GEHC VPN connectivity.

NOTE: See Appendix 1 - Generate Licenses for AWS for

elicense info

NOTE: Contact the OLC, if you can’t generate new

licenses.
The OLC will send you an email with the licenses, save this
file in your laptop.

7. Click on the Browse button to locate the eLicense file

generated in your laptop.

8. Select the eLicense file then click on Open to load the file. The licenses appear in the Upload Licenses list.
9. Click on Next

10. Platform Configuration, make sure the URL is entered correctly, as shown here: http://192.168.101.1:9998/host in the
Authentication URL field. If the IP Address 192.168.102.1 was used in section 3.2 step 2, enter the following URL:
http://192.168.102.1:9998/host
11. Click on Next

http://192.168.101.1:9998/host
or
http://192.168.102.1:9998/host
Refer to step 10 and enter the correct IP
Address.

47/87
 NanoCloud AWS Installation DOC2507368_r10
12. Cola Server Configuration, no input required on this page, click on Next

12

13. DICOM Hosts, enter the following information as shown on the picture below.
Notes:
 The Host Name can be found when you open a Unix shell.
The Host Name is immediately after ctuser@.

Example: ctuser@ct99
In the example above, the Host Name is ct99

 The Name, Host Name and the Application Entity Title are the same as the Host Name shown in the Unix
shell.
Make sure the Name, Host Name and the Application Entity Title are entered as it appears in the Unix shell, as it
is case sensitive.
14. Enter IP Address: 192.168.101.1 and Port: 4006
If the IP Address 192.168.102.1 was used in section 3.2 step 2, enter the following URL: http://192.168.102.1:9998/host

Example

Name, Host Name and

Application Entity Title are the
same and they are case
sensitive

48/87
 NanoCloud AWS Installation DOC2507368_r10

15. Click on Create host

16. Click on Next

17. Device Info, enter the System ID, Global

order number, Install date, Hospital name,
Address, City and Country.

Note：
The system ID here must be unique ，it is
suggested to use the rule of CT sysID plus nano,
Example：AB1410CT09nano (AB1410CT09 is
the CT sysID)

Note: Fields with an asterisk (*) are

mandatory

18. Click on Next

19. End of Review, check the Box

under the Status Hostname to enable the End
of Review process.
20. In the Type, select All.
21. In the Modality, Select All.
22. Click on Next

49/87
 NanoCloud AWS Installation DOC2507368_r10

23. Configuration Summary, use the

scroll bar and review the configuration.
To update the Configuration, click on
Back or select the proper tab.
24. Click on Browse and select the folder
where you want to save the ISO file
25. In the Export options, select Iso
format
26. Click on Export  Configuration
folder will be created in the folder,
containing an ISO and YAML files.

27. Select Exit, to save the configuration

and exit the Install Wizard

28. Go to the location in your laptop where the Configuration folder was saved.
29. Open the Configuration folder and copy the Configuration.iso file to a USB Drive.
Note: If you don’t see the Configuration.iso file, click on the View tab and select File name extensions

50/87
 NanoCloud AWS Installation DOC2507368_r10

30. Install the USB drive in the Console, press ALT + F3, open an Unix shell and type:
{ctuser@ct99} mountUSB [enter]
WARNING: You are not superuser. Watch out for permissions.  ignore this message!
{ctuser@ct99} cd /USB [enter]
Directory: /USB
{ctuser@ct99} ls [enter]
Configuration.iso* 'System Volume Information'/
{ctuser@ct99} cp Configuration.iso /usr/g/AWS_VM/ [enter]
{ctuser@ct99} cd /
{ctuser@ct99} unmountUSB
Remove the USB from the USB port

31. Click OK to close the Generated

Network Information window.

32. In the AW Server Deployment Tool

window, click on the Browse button
Cloud Init Data (iso) location:
33. Select /usr/g
34. Select /AWS_VM, then select
Configuration.iso file
35. Click on Deploy, you will be
prompt to enter the CT root
password in the Terminal window

36. Verify the “VM creation is done!!!!”

message in the Terminal window.

51/87
 NanoCloud AWS Installation DOC2507368_r10
6.4 Displaying the AW Server Console

1. Press ALT + F3, open a Unix shell and type the following command:
{ctuser@ct99} virt-manager [enter]

2. Double click on the

QEMU/KVM – Not connected

3. Double click on the AWS

Virtual Machine to open a
Linux shell.

4. The user login is root and

password: Tbd&bu

5. Wait 8 minutes, then verify the configuration has finished before proceeding to the next step. In the VM terminal, type:
cd /root/provisioning [enter]
./cicaws.py status [enter]

The VM will return one of the following:

status: configured Configuration has successfully finished, continue to the next section, AWS Configuration using Service
Tools
status: in progress Configuration in progress... repeat the command: ./cicaws.py status
DO NOT enter AWS Service Tools until you get status: configured

Notes:
 If you receive a “status: failed”, review the error:
less /var/log/gehc/sdc/logfiles/cloudinit_config_agent.log
Errors during the auto configuration will be posted in cloudinit_config_agent.log
 Launching the AWS Service Tool before the Status is configured will impact the AWS Nano software load
6. Close the aws on QEMU/KVM and the Virtual Machine Manager windows. DO NOT close the CT Unix Terminal
window below, as this window can be used to review details during troubleshooting.

52/87
 NanoCloud AWS Installation DOC2507368_r10

6.5 Nano AWS Initial Launch of AWS

Service Tool

1. Click on the CSD > Configuration > Configure

AWS on VM > Launch AWS Service Tool

When launching the AWS Service Tool, it may

display “Secure Connection Failed”, you need
to manually delete the certificate.

a. Close the Secure Connection Failed

Browser Window.

b. Open a Unix shell and type:

{ctuser@ct99} firefox -P xx [enter]

c. Select awe2_client_ct

d. Select Delete Profile

e. Select Delete Files

f. Click on Exit and close the Terminal
window.

2. Click on the CSD > Configuration > Configure

AWS on VM > Launch AWS Service Tool

If the web page cannot be opened, select

Advanced  Accept the risk and Continue
OR Add Exception  Confirm Security
Exception

53/87
 NanoCloud AWS Installation DOC2507368_r10

3. Scroll down > in the Service and

Administrative Tool click on Launch

4. Login: service
password: Geiaw&08

5. Verify Automatic Configuration Status

Summary Pass

54/87
 NanoCloud AWS Installation DOC2507368_r10
6.6 Configure the Auto Delete to avoid
running out of space in the Image Disk

1. Select Initial Configuration > Database

Deletion Settings.
Configure as shown below:
a. Set [Auto delete status] to On
b. Set [Start when image database reaches] to 80%
c. Set [Stop when image database reaches] to 70%
d. Set [Remove image(s) from system database
older than] to 2 hours
e. Set [Start auto delete process every] to 2 hours
f. Click on Apply

2. Confirm CoLA server is running: Initial

Configuration  Licensing  CoLA Server

3. Select Administrative > Configuration >

End Of Review
a. Select CT/XA/DX/OT
b. Select All
c. Select Apply
d. Select Apply

4. Select Tools > Terminal, Turn On SSH Access.

Wait for Enabled

55/87
 NanoCloud AWS Installation DOC2507368_r10
5. Select Initial Configuration > Platform
Configuration, verify the appropriate Platform
Enabler is selected:
o SdC_Nano_4k
(Optima CT520/540/Maxima)
o SdC_Nano_12k
(Revolution Ascend

6. Select Next

7. Select Single Mode, click Next

8. Verify the Authentication URL is correct:

http://192.168.101.1:9998/host

If the IP Address 192.168.102.1 was used in

section 3.2 step 2, verify the following URL was
entered: http://192.168.102.1:9998/host

DO NOT click on Check Address!

9. Click on Apply
a. Do you want to continue the configuration
now? Click OK
b. Do you want to proceed with the configuration
now? Click OK.
c. Wait 3 minutes for the Success message.
d. Click OK on the Reboot popup message
Do not reboot now, reboot will be performed
later.

10.Select Initial Configuration  Time settings 

Update the Region and Time zone  Apply 
Update Date and Time  Apply

11.Optional: Select Initial Configuration  Licensing

 Preprocessing

Select Preprocessing Enabler and type/check the

Auto Launch License key, then click Apply.

56/87
 NanoCloud AWS Installation DOC2507368_r10

6.7 Installing Volume Viewer

1. Select Maintenance > Version Management >

Click on OK

2. Select Upload ISO

3. Click on Browse
a. Navigate to /usr/g/AWS_VM
b. Select
AWE-Voxtool-vxtl_15.0-8.25x86_64.iso
(file name may be different depending on the
Volume Viewer version)
c. Click on Open
d. Send to System (It takes around 5 minutes).
Wait for Upload Successfully finished, click OK

4. Select Volume Viewer Apps

5. Select Install > Click OK to continue

Installing the Application Software.

It takes ~8 min.

6. Wait for the Install/Uninstall finished successfully

window, click OK

NOTE: Repeat steps 2 to 5 if customer purchased

SmartScore 4.0

7. Select License Activation > Verify selected

options match the ones provided through
eLicense.

Example

57/87
 NanoCloud AWS Installation DOC2507368_r10

6.8 System Configuration Registration

1. Select Maintenance > Register Configuration

a. Scroll down and select Export Configuration
b. A window will popup, select Save File > Click OK

Default saving path: /usr/g/ctuser/Downloads,

The file is a .txt file.

c. Copy the file to a USB Drive.

• Install a USB Drive in the Console
• Open a Unix shell and type:
- mountUSB [enter]
- cd /usr/g/ctuser/Downloads [enter]
- ls -altr [enter]
(This command lists the files in chronological order, if
more than one file is listed, copy the latest one, which is
the file in the bottom)
- cp xxx_systemid_xxxx_Configuration.txt /USB
[enter]
- unmountUSB [enter]

d. Go to the site: https://awcct.gehealthcare.com

Select Choose file > select the Configuration.txt
file from the USB Drive > Open
e. Select Submit to generate the Registration Key.

f. In the Service Tools GUI in the console scroll up

and enter/type the Registration Key > Select
Install Registration Key.
Scroll down and verify “Operation Success! The
registration key has been successfully
installed”

6.9 Back up the Configuration/User

Preferences if needed.
1. In Service Tool, go to Maintenance  Backup 
System Configuration
2. Keep everything selected and press Pull from
system.
3. Select Save File  OK
The backup.tar.gz file will be saved in the
/usr/g/ctuser/Downloads
4. Backup this file to a USB Drive, if you need to
restore it in the future.

58/87
 NanoCloud AWS Installation DOC2507368_r10

Note: Some sites the Application specialist or the

User may create new protocols (e.g. DMPR
protocols), the new protocols can be saved as
backup for reinstall in the future, do as follows:
Maintenance→Backup→User Preferences

6.10 Finish the Maintenance Mode

1. Select Maintenance > Maintenance >

Finish Maintenance > Finish Maintenance

2. Select Tools > Reboot > Reboot AW Server >

Close Service Tools GUI.

3. Wait 7 minutes > Select Launch AWS Service

Tools, verify the AWS Nano is up.

4. Close the Service Tools GUI

59/87
 NanoCloud AWS Installation DOC2507368_r10

6.11 Create the new watchdog_new.sh file on your laptop

1. Find the watchdog_new.txt file in the attachment tool of the PDF reader. The file looks like below

2. Save the attachment file to your laptop

3. Change the extension from .txt to .sh, the file name should be watchdog_new.sh
4. Copy the file to a USB Drive
5. Install the USB Drive in the Console and do as follows:
{ctuser@ct99} mountUSB [enter]
WARNING: You are not superuser. Watch out for permissions.  ignore this message!
{ctuser@ct99} cd /USB [enter]
Directory: /USB
{ctuser@ct99} cp watchdog_new.sh /usr/g/ctuser/Downloads [enter]
6. {ctuser@ct99} cd / [enter]
7. {ctuser@ct99} unmountUSB [enter]
8. Remove the USB from the USB port
9. Upload the watchdog_new.sh file into the AW Server

a. From the AWS Service Tools,

select Tools > File Transfer

b. In the To System tab, click on Browse,

navigate to the /usr/g/ctuser/Downloads
directory, select the watchdog_new.sh file, then
click on Open.

c. Click on Send to system to upload the

watchdog_new.sh file
d. Click on OK to the popup window

10. Type the following command in a terminal window:

{ctuser@ct99} virt-manager [enter]
11. Double click on the QEMU/KVM
12. Double click on the AWS Virtual Machine to open a Linux shell, select the window and press ENTER
13. The user login is root and password: Tbd&bu (you may need to press ENTER to get the prompt

60/87
 NanoCloud AWS Installation DOC2507368_r10
14. In the AW Server shell, navigate to the /usr/share/ServiceTools/scripts/coreWatchDog directory:
cd /usr/share/ServiceTools/scripts/coreWatchDog [enter]
15. Backup the current watchdog.sh file:
cp watchdog.sh watchdog.sh.orig [enter]
16. Overwrite the current watchdog.sh file with the watchdog_new.sh file previously uploaded:
\cp /var/lib/ServiceTools/upload/watchdog_new.sh watchdog.sh [enter]
Note : The command \cp is to copy and overwrite file
17. Restart watchdog service:
systemctl restart aws-watchdog.service [enter]
18. Check that the service is restarted:
systemctl status aws-watchdog.service [enter]
Output should be like following:

19. Close the AW Server shell, the Virtual Machine Manager and the AWS Service Tool

6.12 SOLO Client Installation

1. Select the CSD > Configuration >

AWS Client Install/Uninstall
2. Click on Install

3. Review the settings, click on Accept,

Window may close automatically.
Click on CANCEL if needed.

Note: It is required to manually change

the IP Address to 192.168.102.5, if
192.168.102.5 was used for this
installation.

61/87
 NanoCloud AWS Installation DOC2507368_r10
4. Select Configure AWS Application >
Select the appropriate applications
> Select Accept.

Tip: Refer to Section 7, Step 7 and

select the proper options.

Refer to the picture on the right to

know what options should be selected.

Example:
o If Volume Viewer is installed, then
you need to select Reformat and
3D Viewer.
o If AutoBone Xpress is installed,
select AutoBone Xpress GENERAL
and AutoBobe Xpress NECK

5. Select the CSD > Configuration >

Configure AWS on VM > Launch AWS
Service Tools

6. Scroll down > in the Service and

Administrative Tool click on Launch

7. Login: service
Password: Geiaw&08

8. Select Initial Configuration >

Platform Configuration > Click OK to
the System is not in Maintenance
mode window > Click Next > Next >
Click on Check Address, wait for the
Success message

9. Close the AWS Service Tools Browser

62/87
 NanoCloud AWS Installation DOC2507368_r10
6.13 Testing REFORMAT

Revolution Maxima, Optima 520, Optima 540, RT16 WB3.0, Discovery IQ and
StarGuide
1. Click on Image Works
2. Select an Exam, then select a Series (not scout)
3. Select Reformat
4. Click Yes to the AW Server Certificate

Revolution Ascend
1. Click on the File Manager Drawer
2. Select an Exam, then select a Series (not scout)
3. Right click on the Exam, select Reformat
4. Click Yes to the AW Server Certificate

63/87
 NanoCloud AWS Installation DOC2507368_r10
7 Reinstall / Update NaonoAWS
7.1 Start to Reinstall An Existing AWS VM

There are two different ways for the AW version AW3.2-3.4 & previous and AW3.2-4.0 due to the Installation Wizard was
introduced since AW3.2-Ext4.0.
Note:
• This “ reinstall ” will reinstall an existing AWS VM，and keep the AWS VM hostID and the elicense
generated ，so Do Not uninstall the AWS VM that already installed
• This “reinstall” does not mean to install nanoAWS VM from a system without nanoAWS, if you need to :
a. install nanoAWS VM after CT OS&App LFC , just follow the general install steps as shown in section
5 or 6, , the license will not be keep if by this way
b. install nanoAWS VM after AWS VM Uninstall (section 8 ) , follow the general install steps as shown
in section 5 or 6 , and need to perform some configuring about certificates/remote-connection, just refer
to the instance in section 7.2 ,the license will not be keep if by this way
Preparation：
if required, Save the User Preference to backup the user protocols which were created on nanoAWS，refer to:
Section 5.4 step 23, or Section 6.5 step 21
1. Prepare the installation mirror file (qcow2 or qcow2.iso) in /usr/g/AWS_VM/, it depends on the CT SW version which were shown
in Section1 Overview

NOTE: Do not forget to confirm the md5 value before reinstall. If failed you need to copy it from the delivered USB again
2. Launch the AWS installation script:
/usr/g/ctuser/VMDeploy/scripts/deployVMGUI.sh
3. Select the option Just reinstall/replace the VM image disk on the installation window as below.
Note:the VM name and the network configuration should be same with before-reinstall

4. Continue to complete installation process by referring the procedures that:

a. Installation procedure:
Case1: For the VM version AW3.2-3.4 or previous

Refer to section 5 to perform installation,in this way the VM hostID will keep the previous one ,so not need generate license
again.

Case2: For the VM version AW3.2-4.0

Press Browse to choose the .qcow2.iso (or .qcow2), a pop-up window displays with the note to select the old Cloud Init
configuration file (Configuration.iso), default location: usr/g/ctuser/AWSVM/aws/

64/87
 NanoCloud AWS Installation DOC2507368_r10

After selected the old Cloud Init configuration file, press Deploy to start the VM installation, then load the existing
Configuration.iso and continue to complete installation process by referring the procedure Section 6, in this way the VM
hostID will keep the previous one ,so not require to generate license again.

Note: During the VM re-install it may report connection lost , just click OK to close

7.2 Open QEMU/KVM - Run virt-manager

NOTE: Run command as ctuser to open the Virtual machine manager
1. Open a shell window
2. virt-manager
3. Double click on QEMU/KVM-not connected. It will show the created VM .
Note: it may take 3-5 minutes to bootup ,
4. Double click on the aws running Icon
Note: login in the VM with
5. Localhost login: Enter-return - Note: it may take 2 minutes for aws login to appear
6. Repeat above step
7. aws login: root
8. Password: Tbd&bu
9. If nothing happens in the above window use the pull down and select reboot.

65/87
 NanoCloud AWS Installation DOC2507368_r10

10. If VM does not boot in 7 minutes – try rebooting from the pulldown window and select reboot.

NOTE: If nothing happens in the above window use the pull down and select reboot.
11. Verify login was successful to the aws login

7.3 AWS-VM Configuration Status Check before Continuing

NOTE: Failure to wait for a successful configuration status will cause missing configuration information therefore causing another
software load.

66/87
 NanoCloud AWS Installation DOC2507368_r10

1. cd /root/provisioning
2. ./cicaws.py status
3. During first boot of the VM it will return one of the following:
status: in progress Configuration in progress... Wait do not enter AWS Service Tools
status: failed See Error log note below - cloudinit_config_agent.log
status: configured configuration has successfully finished, continue into AWS Service Tool

4. Repeat ./cicaws.py status until status response with “ configured “

Typically wait times range from 5-10 minutes, just repeat step 3 cicaws status commands
NOTE: If you receive a “status: failed” review the error located in
/var/log/gehc/sdc/logfiles/cloudinit_config_agent.log”
NOTE: Errors during the auto configuration will be posted in cloudinit_config_agent.log
NOTE: Launching the AWS Service Tool before the Status is “ configured “ will cause problems
loading the Wizard-Configuration.iso fille into the AWS Virtual Machine.

5. Close AWS on QEMU/KVM window.

6. Close the virt-manager window

67/87
 NanoCloud AWS Installation DOC2507368_r10
7.4 Launch AWS Service Tool for the First Time
1. Open the AWS service tool via:
CSD→Configuration→Configuration AWS on VM →Launch AWS Service Tool

NOTE: When launching the AWS service tool, it may display Secure Connection Failed, you need to manually delete the certificate,
see steps below.

2. Close the “Secure Connection Failed” Browser Window

3. Delete the certificate file manually, as shown below:
4. Enter firefox -P xx
5. Select awe2_client_ct
6. Select Delete Profile

68/87
 NanoCloud AWS Installation DOC2507368_r10
7. Select Delete Files

8. Close Browser if you haven’t done so already

9. Select Exit exit the Firefox profile window
10. Select Launch AWS Service Tool again
(Attention: If the web page can not open the page and shows not security, please press Advanced→Add
Exception→Confirm Security Exception , or similar button in different browser version)

By this way the AWS license ID will not change so the nano-AWS related license(s) which were generated in the previous
installation are still all available.

69/87
 NanoCloud AWS Installation DOC2507368_r10
7.5 Nano AWS Configuration Check
1. Login: service
2. Password: Geiaw&08
3. Save Password

4. The Health Page should shows an Automatic Configuration Status Summary Status should be Green Pass

5. Restore AWS System Configuration and User Preference:

A: For AW3.2-3.4 or previous,

if it has had AWS Configuration backup or the User Preference backup that has been saved in AWS service tool, you
can restore the backup file(s), After restore you only need to double check and confirm all the information. As shown below

B: For AW3.2-Ext4.0,
Although AWS configuration will be recovered based on Configuration.iso. You also need to double check and confirm all
the information after reinstall, it may take 3-5 minutes to recover the data in AWS service tool, you can repeatly refresh the
AWS service tool page for the information update.

If required, restore the User Preference (to restore the user protocols)

70/87
 NanoCloud AWS Installation DOC2507368_r10
5. Maintenance-> Version Management

6. Mandatory message click OK

7. Select Upload ISO
8. Select Browse
9. Browse to /usr/g/AWSVM AWE-Voxtool-vxtl_15.0-X-xx.x86_64.iso
10. Select Open
11. Select Send to system

71/87
 NanoCloud AWS Installation DOC2507368_r10
12. Select Ok to Upload Successful
NOTE: Repeat steps 37-42 Upload ISO for SmartScore only if the customer purchased the smart score option.

13. Repeat steps above 7-12 to Upload ISO for SmartScore only if the customer purchased the smart score option.

14. Select both Volume Viewer Apps 18.0-X.xx and If Smart Score 4.0 xxxxxxx.iso was purchased
Note :SmartScore is purchasable option
15. Select Install
16. Wait Volume Viewer load Pauses for 5 minute

72/87
 NanoCloud AWS Installation DOC2507368_r10

17. Wait Voxtool / Volume Viewer to load it could take over 10 minutes

18. Select OK to finished successfully

19. Enter Registration key use the Search to find xxxxxxxx_sys-ID_REG_KEY.txt file
Example: 0609b6f3_263574Ascendnano_REG_KEY.txt
20. Select Install registration Key
21. Green Operation Success registration key has been successfully installed
Note: or you can generate the registration key by following the steps in Section6.8 if required

22. Tools - > Terminal

73/87
 NanoCloud AWS Installation DOC2507368_r10

Select SSH On
Select Refresh
A successful message followed by SSh on showing Enabled
23. Backup configuration.
Backup the AWS configuration refer to the Section 6.9
24. Finish maintainance.
Maintenance -> Maintenance
Click the button Finish maintenance

25. Create the new watchdog_new.sh file by following Section 6.11

74/87
 NanoCloud AWS Installation DOC2507368_r10
7.6 Reinstall the AWS client

1. Select Uninstall AWS client

2. Wait 2 minutes
3. Select Install/Uninstall Client AWS client from CSD
4. Select Uninstall

5. Select Install

6. Select Accept

75/87
 NanoCloud AWS Installation DOC2507368_r10
7. Wait 2 minutes
8. Cancel when completed

7.7 Configure AWS Application

1. Select Configure AWS Application
Note: Select the applications which needed, then press Accept (Figure is an example, please select only
the applications which the customer has purchased).

2. Select Image works to select reformat

3. If reformat fails to launch – reboot the CT host computer
4. Select exam series and a number of images
5. Select Reformat
Example: Revolution Maxima Reformat

76/87
 NanoCloud AWS Installation DOC2507368_r10
Example: Revolution Maxima Reformat

6. Select Yes to accept certificate

Now the re-install is completed, you can launch an AW Apps to check the image processing.

Section 7.8 below is only used for upgrade the nanoAWS from AW3.2-Ext3.4 to AW3.2-Ext4.0 if required

77/87
 NanoCloud AWS Installation DOC2507368_r10
7.8 AWS upgrade from AW3.2 ext3.4 to ext4.0
Since the AW3.2 EXT4.0 introduced Installation wizard but AW3.2 ext3.4 did not , you have to uninstall EXT3.2 then install
EXT4.0 with the standard installation steps,and need some extra config ,refer to the steps below

1. Uninstall the solo client and AWS VM by refer to Section 8

2. Install AW3.2 ext4.0 ，refer to section 6

Note : When launch the AWS service tool of EXT4.0 first time , it may display like secure connection failed ,
perform as below

Then launch the AWS Service Tool again

(Attention: If the web page can not open the page and shows not security, please press
Advanced→Add Exception→Confirm Security Exception , or similar button in different
browser version)
3. After AW3.2 EXT4.0 installation completed, Run command below to enable remote ssh
connection for VM：
ssh-keygen -R 192.168.101.5 -f /usr/g/ctuser/.ssh/known_hosts

78/87
 NanoCloud AWS Installation DOC2507368_r10

8 Solo Client & AWS VM Uninstall Procedure

This section shows how to uninstall(clean up) the AWS client and the VM
8.1 Solo Client uninstall.

Uninstall Solo Client from the CT Console. On CSD→Service Configuration→ Configuration AWS on VM→AWS Client
Install/Uninstall. Select Uninstall, wait until the pop window disappeared, it completed.

8.2 VM uninstall.
Note： After this uninstall, it will require to generate license again for the next installation , if keeping license is expected just
refer to section 7.1

1. Virtual machine deletion

Delete the VM configuration from the CT console.
a. Open in terminal and run the virt-manager.
b. Select the AWS VM what you want to delete.
c. Make sure the VM is stopped. If not stopped you can shutdown from virt-manager by right click on the VM
name Shut Down/Shut Down or Force Off.

79/87
 NanoCloud AWS Installation DOC2507368_r10

d. After the VM is off, right click again on the VM and select the Delete option.
e. Make sure that the associated qcow2.iso image (storage file) is also deleted, then Press Delete (do not delete qcow2.iso
image if you need to repeat a installation based on the same qcow2.iso image).

2. virtnet deletion
a. To remove network “virtnet” in virt-manager, Edit→Connection Details , then select Virtual Networks.
b. Stop the virnet running and delete it ,as shown below

3. AWS folder deletion

Remove the old virtual machine folder by command: rm -rf /usr/g/ctuser/AWSVM

80/87
 NanoCloud AWS Installation DOC2507368_r10

9 Common Troubleshooting
If ping 192.168.101.1 (or 192.168.102.1 if you set IP segment to 192.168.102.x in Virtual Machine Create) failed , or the step AWS V
M & SOLO Client Update failed, you should check the configuration follow the steps below:

1. Check the VM Virtual Network.

Run command virt-manager in console shell to open VM manager
Select the VM aws then go to the menu Edit - Connection Details as shown below

Review the virtual network. As the figure below:

NOTE: make sure both the 2 networks default and virtnet are Active. ( if inactive,click , and the Autostart: □On Boot is
selected as ✓. Press Apply after done.

2. Check the authentication URL. the URL http://192.168.101.1:9998/host offen has type-in error
Note: If you need to change the configuration, you should make sure the service tool is in maintenance mode, if not, please
switch it to maintenance mode by click on Maintenance→Maintenance→Start maintenance, after change, go to finish
maintenance.

81/87
NanoCloud AWS Installation DOC2507368_r10

82/87
 NanoCloud AWS Installation DOC2507368_r10

3. Check the data of DICOM Host, especially the 3 names should be same with the Host name of CT.
Note: If you need to change the configuration, you should make sure the service tool is in maintenance mode, if not, please switch
it to maintenance mode by click on Maintenance→Maintenance→Start maintenance, after change, go to finish maintenance.

4. Check the network configuration on console side as screenshots below. The path is Imageworks→Tools→Network Configuration.
( Follow the corresponding method to check Network Configuration if the CT SW have a different UI from the example bellow )

83/87
 NanoCloud AWS Installation DOC2507368_r10

5. If the reconstructed images can not be saved to CT worklist, Check the configuration of End of View.

6.if all the troubleshooting items above were checked and looks correct，but the AW APP still can not launch successfully , re-install is an
efficient way to resolve unknown issue, refer to section 7.1 AWS VM Reinstall and 7.3 Solo Client reinstall

7. Remote access from FFA

1）Remotely Connect to the CT computer on FFA and open the command terminal on FFA
2）Connect from CT computer to the virtual machine of nanoAWS
Command： ssh root@192.168.101.5
Type in the password ：Tbd&bu
3）Check the nanoAWS configuration by running command ： conf

84/87
 NanoCloud AWS Installation DOC2507368_r10

Appendix 1 - Generate Licenses for AWS

Generate eLicense for Nano AWS

1. Click on the link below:
https://elicense.gehealthcare.com/elicense/
2. Enter System ID, Select System ID in the pulldown menu. Select CT, then click GO

3. Figure 1 or Figure 2 will appear, select Edit System Information.

4. Click on the Host ID field. You may or may not have access to update the Host ID, see figures below.
 If you have access, continue to step 5
 If you don’t have access, contact the OLC and they will generate the Licenses

Figure 1 Figure 2

5. Enter the Host ID, click Continue

6. Select Email Licenses or Save Licenses

85/87
 NanoCloud AWS Installation DOC2507368_r10
Appendix 2 - Renewal of Digital Certifcate

Contents below comes from 5719443-8EN Installation and Service Manual -4.5 Job Card SV004 - Renewal of Digital
Certifcate, please find the lastest conetents by reading the 5719443-8EN if any updates.

Job Card SV004 - Renewal of Digital Certifcate

This procedure concerns AW Server systems that are using the self-signed certifcate provided
by AW Server software. This procedure does not apply to AW Server systems using a certifcate
purchased by the customer.
Purpose of this procedure
This procedure introduces information concerning the digital certifcate used by AW Server to
authenticate itself at the time of AW Server client connection. By default, the validity of this
certifcate is set to 5 years after the installation of AW Server. Once this period of time is over,
the certifcate is considered as invalid. This procedure provides instructions to renew the digital
certifcate.
NOTE
This procedure may also refer to the "digital certifcate" as "authentication certifcate" or
"public-key certifcate": these namings are all equivalent.
1 How to determine if an AW Server needs certifcate renewal
To check if an AW server needs to have its certifcate renewed, check the following:
1. Check that the digital certifcate is not valid anymore. This typically happens when the AW
Server was installed more than 5 years ago and has not been upgraded or reinstalled since 5
years.
To check the digital certifcate validity, follow instructions below:
a. Check the Healthpage Certifcate expiration date field. If the feld is not green, then it
is needed to renew the certifcate, go to the next section for detailed steps on certifcate
renewal.
b. To check manually the validity date of the certifcate, open a Terminal:
• By using the Service Tools > Tools > Terminal > New modal Terminal. Click on Connect.
• OR by using PuTTY.
c. Login as root.
d. Enter the following command to display the validity of the certifcate:
cd /etc/pki/tls/certs/ <Enter>
openssl x509 -in server.crt -noout -text | grep -A2 Valid <Enter>
(do not forget the upper case for V in Valid)
e. Enter the following command to display the date of the system:
date <Enter>4
The results of previous commands should appear.
If the date of the system is later than the date indicated in the Not After feld, the
certifcate is not valid anymore. Apply the procedure below to renew the digital certifcate.
2. Check that the AWS Client displays a warning message at login.
When logging to the AWS Client an Invalid Certificate message appears in a pop-up. If
the user selects Yes, the AWS Client is able to launch normally. However, the message appears
again at each login.
2 Instructions to renew AW Server digital certifcate
1. Enter the Maintenance Mode. THIS WILL DISCONNECT ALL USERS USING THE AW SERVER .
a. In the Service Tools, go to Maintenance > Maintenance.
b. Select the Start maintenance tab.
c. Enter a disconnect message, then click on the Start Maintenance button.
d. When asked for confrmation, select OK.
A message confrms that the AW Server is now in Maintenance Mode.
For more details on Maintenance Mode, refer to A.4 Maintenance Mode on page 409.
2. Launch a Terminal in Service Tools, or connect through ssh with PuTTY and login as root.
Refer to the previous section for detailed steps.
86/87
 NanoCloud AWS Installation DOC2507368_r10
3. Type the following command:
/usr/sbin/gensslcertAWE -y 1825 <Enter>
Messages should appear as shown below. This command creates a new self-signed certifcate
valid for 1825 days (5 years).
4. The installation process requires a re-start of the httpd web services and will disrupt any
connected clients. Enter the following command:
systemctl restart httpd <Enter>
5. Check that the Validity date of the certifcate has been updated.
Either check the Healthpage, or use the same commands as in Section 4.5.1.1 How to determine
if an AW Server needs certifcate renewal on page 398:
a. Enter the following command to display the validity of the certifcate:
cd /etc/pki/tls/certs/ <Enter>
openssl x509 -in server.crt -noout -text | grep -A2 Valid <Enter>
(do not forget the upper case for V in Valid)
b. Enter the following command to display the date of the system:
date <Enter>
The results of previous commands should appear.
6. Check that the Certifcate is valid for the next 5 years, starting on the current date.
7. Finish the Maintenance Mode:
a. In the Service Tools, go to Maintenance > Maintenance.
b. Select the Finish maintenance tab.
c. Click on the Finish Maintenance button.
A message confrms that the AW Server is in Maintenance Mode.
d. Select OK.
For more details on Maintenance Mode, refer to A.4 Maintenance Mode on page 409 in 5719443-8EN.
8. Test the AW Server client:
a. On a client PC, launch AW Server and connect to the AW Server. A pop-up displays at the
frst connection to accept the Certifcate.
b. Accept the certifcate by clicking on Yes.
c. Logout of the AWS client.
d. Connect one more time to the AWS Client. This time, no pop-up should display for
certifcate. This confrms that certifcate has been successfully renewed

87/87