Changing the PowerConnect Client
Changing Active Client for PowerConnect
Steps in Current Client
If you have made no manual change to the “Administrator” menu you will need to collect the following information.
Go to Administrator -> Setup Global Config
Record your license key which is value SERIAL_KEY
Go to Administrator -> Splunk Setup ->Setup Splunk
Record the details of your current Splunk Configuration
If you have added or changed any configuration in the “Administrator” menu you will need to record these and add them once you have setup the new client
Ensure all background jobs have been stopped
If they do not have a red cross next to them use the following buttons to stop the jobs. Once jobs have stopped you can proceed.
Go to transaction SE16 and enter table name /BNWVS/RT_CFG
On the next screen enter NAME – WORKING_CLIENT
Select the line and select
Update value to new client number and save
While installing and patching PowerConnect you would have created transports when you activated the BC Sets, if not already imported – import into new client.
When importing, since it is being imported into the same system (just a differentclient) please select “Import transport request again” to ensure it is written to the table –through testing I found that it will not work without this setting.
Also ensure the Authorisation Object transport (N71K900223) has been imported and then the roles are transported or uploaded to the new client. Allocate the “Batch” role to the user running the background job and the “Admin” role to anyone who needs to access the/bnwvs/main transaction.
If you get the following error when releasing your transports –please follow the following steps.
Double-click on the Customizing Task
Highlight the line /BNWVS/LOGS_CFG and click on key icon
Put into change mode
You will now be able to release your transport and import all into the new client
Steps in New Client
In the new client go to transaction/n/bnwvs/main
Enter license key
On the next pop-up choose cancel as you do not want to start the jobs yet.
The next step is to use the Splunk wizard to create the connection to Spunk.
You can use all the same values from the old client
Make connection active and select “Finish”
You now need to go through the “Administrator” menu and re-enter any changes or new entries you made in the previous client.
Once you have updated this information you use the following buttoning to start the background jobs –ensure you specify the user who the background jobs “run as”.