Exadata General (MOSC)

MOSC Banner

Exadata VLAN prerequisites in OEDA

edited May 19, 2016 12:00PM in Exadata General (MOSC) 1 commentAnswered ✓

I have a few questions on the concept of OEDA (v16.112.03:00 / p23125053):

1. Why does VLAN tagging require port bonding ? The Admin subnet does not set this requirement - so why is it introduced for Client and Backup network ?

2. Very likely due to the above assumption (requiring bonding) backup and client need to be shared. Is this correct ? (with bonding requirement we do not have enough ports available - probably therefore this dependency has been created)

3. Subnet2: Client Network Format: selecting copper or optical does principally exclude the unused ports (to be used for other functions). At least by OEDA possibilities. We have a customer, where ACS added a configuration where - in addition to the optical client network - the (so far unused) copper ports had been configured to be used for dataguard purpose. Is this compliant (to later patching procedures) ?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center