Advant Master Server configuration in 800XA 6.1 System
Hi,
800XA 6.1
Advant Connect
We have MB300 Net ( 11 and 12 ) during SCC deployment we have selected network group as 1 ( we missed to read the below note ) - after SCC deployment we have seen MB300Net aspect in control structure level showing Network as 1 ( Both screen shots are attached below)
We have tried to change the same but its was not allowed to do in SCC or Aspect level.
Please support what is significance of this setting , if this need to be 11 show we can change that ?
800XA 6.1
Advant Connect
We have MB300 Net ( 11 and 12 ) during SCC deployment we have selected network group as 1 ( we missed to read the below note ) - after SCC deployment we have seen MB300Net aspect in control structure level showing Network as 1 ( Both screen shots are attached below)
We have tried to change the same but its was not allowed to do in SCC or Aspect level.
Please support what is significance of this setting , if this need to be 11 show we can change that ?


Answers
The description next to the "Network Group Number" leaves room for improvement. MB300 network numbers lower than 10 are reserved for "local networks", rarely something you want to specify when setting up 800xA for Advant Master in System 800xA.
The 800xA for Advant Master network settings in SCC > Configure System are adjustable after deploy, but what was once deployed will not change. The reason is that the designer thought it must be possible to adjust the SCC:s values to match reality (e.g. if the system is restored or moved to another location where other numbers are in effect).

During the deploy (which only takes place once) the initial values are used to create a MB300 network and RTA Board objects. The RTA network & node numbers can be adjusted per RTA, but the number set on the MB300 Network object is fixed.

In your case, it looks like the initial deploy was made with MB300 Network number 1 (which is likely not a correct value).
I suggest to add a new MB300 network object (from the classic Configuration Wizard) by adding a new RTA using the correct network number.

Then drag & drop any Advant Master controllers you may have restored, imported or uploaded already over to the new MB300 Network after which you delete the obsolete MB300 network and associated Advant Master services from the Service Structure (some of the deletions are automated by Object Hooks).
Once you've got your Control Structure correct, update the values in SCC for later use when you e.g. call for "Replace Node" (when you need to trust the automation of the System Installer to recreate a damaged or lost node with the same features and settings as was lost with the damaged node).
You can attempt to delete features in SCC and try to add them again - but there is no automated removal of object and aspect data.

Deletion of features is not a function to be used commonly in the SCC - expert skills are often required to be able to complete the removal. Some features will only deploy once; just because you are able to "Manually Remove" Oracle or SQL Server, don't believe in that a second installation of Oracle will work after "uninstalling" the first by only clicking "Manually Remove"...
Use Murphy's First Law of Computers: Backup often, backup early!

The 800xA for Advant Master network settings in SCC > Configure System are adjustable after deploy, but what was once deployed will not change. The reason is that the designer thought it must be possible to adjust the SCC:s values to match reality (e.g. if the system is restored or moved to another location where other numbers are in effect).

During the deploy (which only takes place once) the initial values are used to create a MB300 network and RTA Board objects. The RTA network & node numbers can be adjusted per RTA, but the number set on the MB300 Network object is fixed.

In your case, it looks like the initial deploy was made with MB300 Network number 1 (which is likely not a correct value).
I suggest to add a new MB300 network object (from the classic Configuration Wizard) by adding a new RTA using the correct network number.

Then drag & drop any Advant Master controllers you may have restored, imported or uploaded already over to the new MB300 Network after which you delete the obsolete MB300 network and associated Advant Master services from the Service Structure (some of the deletions are automated by Object Hooks).
Once you've got your Control Structure correct, update the values in SCC for later use when you e.g. call for "Replace Node" (when you need to trust the automation of the System Installer to recreate a damaged or lost node with the same features and settings as was lost with the damaged node).
You can attempt to delete features in SCC and try to add them again - but there is no automated removal of object and aspect data.

Deletion of features is not a function to be used commonly in the SCC - expert skills are often required to be able to complete the removal. Some features will only deploy once; just because you are able to "Manually Remove" Oracle or SQL Server, don't believe in that a second installation of Oracle will work after "uninstalling" the first by only clicking "Manually Remove"...
Use Murphy's First Law of Computers: Backup often, backup early!

A senior colleague hinted that the Network Group Number can be chosen arbitrarily (but we recommend using the same as the MB300 network to be added).

The number must be kept same within two nodes that shall act redundant (primary/secondary) - see section marked with YELLOW.
When adding an additional service groups for the same MB300 network, the additional pair must be given a different Network Group Number than the first pair was set with. See section marked with BLUE. Up to four pairs can be configured for a single MB300 control network e.g. 1, 2, 3, 4 or 11, 13, 15, 17 or 11, 12, 13, 14. The actual MB300 Network Numbers are a different setting, they should be set identical for all four pairs, e.g 11 + 12.
Worth repeating: there is only one single deploy where the chosen setting are effectuated to the system, the very first deploy. Any modifications made later in SCC will not be reflected in the Control Structure or RTA Settings - only when performing "Replace Node".

The number must be kept same within two nodes that shall act redundant (primary/secondary) - see section marked with YELLOW.
When adding an additional service groups for the same MB300 network, the additional pair must be given a different Network Group Number than the first pair was set with. See section marked with BLUE. Up to four pairs can be configured for a single MB300 control network e.g. 1, 2, 3, 4 or 11, 13, 15, 17 or 11, 12, 13, 14. The actual MB300 Network Numbers are a different setting, they should be set identical for all four pairs, e.g 11 + 12.
Worth repeating: there is only one single deploy where the chosen setting are effectuated to the system, the very first deploy. Any modifications made later in SCC will not be reflected in the Control Structure or RTA Settings - only when performing "Replace Node".
Add new comment