Forum Discussion
5 Replies
Sort By
- pete_71470CirrostratusWe did this as part of an RMA process. It was deceptively simple: insert blade. An existing blade will be cloned to it and for us that took about an hour. There was no way to know when the process was completed fully because a background rsync process keeps sending over traffic graph updates to the new blade. During the process there was no interruption in traffic. Since our old blade was to come out, we did have a problem with network configurations because the interface names are sensibly different (2/1.1 instead of 1/1.1). Easily resolved with vi.
- nitassEmployeeboth software and configuration should be pushed from primary blade automatically. to monitor, you may review /var/log/ltm and /var/log/liveinstall.log.
- Daniel_24760Nimbostratusall right, so while the primary blade is running some services i can just add the new blade without interrupting the other services and after the secondary blade is cloned, i can start configuring it, so i guess the vCMP license running in the primary blade will be duplicated in the secondary and it will give the option to add 4 more vCMP guests, am i right?
- nitassEmployeeall right, so while the primary blade is running some services i can just add the new blade without interrupting the other services and after the secondary blade is cloned, i can start configuring it, so i guess the vCMP license running in the primary blade will be duplicated in the secondary yes
- Daniel_24760Nimbostratusthank you so much nitass