Oracle RAC -- changing ethernet device name Post: 302751711

Sponsored Content

Operating Systems Linux Red Hat Oracle RAC -- changing ethernet device name Post 302751711 by s ladd on Friday 4th of January 2013 10:50:33 AM

01-04-2013

Registered User

Oracle RAC -- changing ethernet device name

I have a RAC setup that was configured before I started at my new company. I would like to reconfigure the network devices and change the names. How complex is this regarding the Oracle RAC environment? Does the Oracle RAC rely on the device name or is it only relying on the IP information?

ie.. I want to add two additional network interfaces to the server and change bond0.173 to bond0 and bond0.192 to bond1.

Thanks,
Shaun

s ladd

View Public Profile for s ladd

Find all posts by s ladd

2 More Discussions You Might Find Interesting

1. HP-UX

HP-UX oracle RAC problem

Hi all i have a problem which we can't fix we have 2 hp blades loaded with HP-UX11iv3 and Oracle RAC 11g R1 accessing HP Sotrage works xp 24000 the oracle cluster cannot access the /dev/oracle/ocr1 i ran #ioscan -em lun the result came as follows " please note output turncated for...

2. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ...

LEARN ABOUT HPUX

cm

cm(5)								File Formats Manual							     cm(5)

NAME

       cm - cluster monitor for high availability clusters

   Remarks
       Cluster	operations require the installation of the optional Serviceguard or Serviceguard Extension for RAC software, which is not included
       in the standard HP-UX operating system.

DESCRIPTION

       Serviceguard and Serviceguard Extension for RAC are high availability products which provide an environment such that after a failure of  a
       node,  services	(applications)	can be up and running again on another node within a very short amount of time.  In addition, Serviceguard
       Extension for RAC is the enabling software for the Real Application Clusters (RAC).  Working with the basic Serviceguard product,  Service-
       guard Extension for Faster Failover allows configuration of clusters for optimized failover.

   Commands
       The following set of commands is used to configure a high availability cluster:

		     cmquerycl(1M)
		     cmmakepkg(1M)
		     cmcheckconf(1M)
		     cmapplyconf(1M)

       The following commands are used to run or halt a cluster:

		     cmruncl(1M)
		     cmhaltcl(1M)
		     cmrunnode(1M)
		     cmhaltnode(1M)
		     cmviewcl(1M)

       Once a cluster is formed, the following commands are provided for manual operation on high availability packages:

		     cmrunpkg(1M)
		     cmhaltpkg(1M)
		     cmmodpkg(1M)

       The following commands are used within a package control script to control the services and networks configured for a package:

		     cmrunserv(1M)
		     cmhaltserv(1M)
		     cmmodnet(1M)

       A command is provided to aid in migrating from a SwitchOver/UX configuration to a Serviceguard cluster:

		     cmmigrate(1M)

       This command is not applicable with Serviceguard Extension for RAC.

SEE ALSO

       Managing Serviceguard.
       Configuring RAC Clusters with Serviceguard Extension for RAC.

						      Requires Optional Serviceguard Software						     cm(5)