Forum Discussion

werner_v_113449's avatar
werner_v_113449
Icon for Nimbostratus rankNimbostratus
Jan 07, 2014

adding blade & SSL license to VIPRION 2400

Hi ,

 

we are currently using 2 * 2400 Viprion chassis . Each chassis is equiped with 2 * B2100 blades and has an license for LTM & vCMP .Thus we have created 8 guest (4 per slot) on each chassis . The guests on first chassis are each time paired with guests on 2nd chassis . So we have 8 virtual LTM clusters.

 

WIthin a couple of weeks we have a timeslot to make some changes . And we're preparing 2 changes :

 

1) we are adding a 3rd blade B2100 to each chassis, in order to have 12 possible guests

 

2) we also are adding an SSL license , for activating SSL unlimited TPS.

 

When i look into documentation , performing these 2 topics seems straight forward

 

--> add the blade into chassis & wait long enough (1h?) .Blade will become available and it will be possible to configure new guest (log files ltm & liveinstall.log can be followed)

 

--> adding SSL license , is re-activating the license. And adding the necessary key. After this a reboot is needed.

 

I'm preparing intervention as follows :

 

1) fail over all traffic to 1st chassis (via traffic groups)

 

2) add blade , check ltm & liveinstall.log for messages

 

3) add SSL license (if blade install completed)

 

4) reboot chassis

 

5) perform steps 1 to 4 on 1st chassis

 

6) disperse traffic again via traffic groups

 

has anyone knowledge about possible pitfalls in this ? (chassis version is 11.3 , guests are using 11.2.1) there isn't much documentation about these kind of tasks.

 

deployment

2 Replies

Sort By
  • Pedro_Haoa's avatar
    Pedro_Haoa
    Ret. Employee
    Jan 07, 2014

    Hi,

     

    Just remember to back up all your configuration before the change. Keep both, the UCS files and the SCF files.

     

    I assume that you will add the 3rd Blade to the 3rd free slot of the chassis. The process can take up to 20 minutes, when you add a new blade. So be patient, and wait until VIPRION finish the whole process.

     

    Finally, keep your Internet access up and running if you detect an issue. The known issues in the release notes, devcentral and the F5 support will help you if anything goes wrong.