Administrator
|
Hi,
Just ensure that the port pool provided for Target Patch Edition File System is different from that of Target Run Edition File System.
Currently I have limited connection, so can't connect an EBS instance and check.
But the methodolgy should be like the following;
For instance, if you use port pool 10 for run edition; then you will use a different port pool for patch ediition.
You need to decide a correct port pool for patch edition and in order to decide this, the port range are important.
Check the apps context file and see the ranges..
Those port ranges shouldn't intersect with eachother.
Lets suppose you use port pool 10 for run filesystem and you have 30 EBS components of the same type and all those 30 components use the same port range..(which is let's say 20)
So now suppose that the starting port of those EBS components is 7211. (just suppose)
This is where it gets interesting..
Then those ports from 7211 to 7241 will be used by those EBS components.
So if you use a patch fileystem port pool which is less than 30 .. Then there will be an intersection there.
I hope you got the idea.
This kind of an issue is the only bad thing that can happen to you in a dual fs configuration..
There shouldn't be any intersection between the ports and port ranges.
However, this kind of an issue is not documented anywhere.. This is what I think and I didn't check the apps context file for any configuration that may cause this kind of an issue. So you should check the context file.. See the port ranges..
Lastly, it is always good idea to have a little difference between port pools of run and patch filesystems.
For ex: Patch fs port pool = 20 , run fs port pool = 10.. .However, as I mentioned you need to check the apps context file and see if there is a possibility for having an intersection between port ranges.. I m telling you this because you have a large number of managed servers and you already mentioned that you have some port conflict problems during your cloning activities.
|