- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LAN900:801
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2013 06:02 AM
06-12-2013 06:02 AM
LAN900:801
Hi,
i have configured two new HP-UX servers, for the database team to install the database and configure oracle rac cluster.
but the dba he request from me to configure the virtual and private IP of the cluster on server like below
lan900:801 1500 10.0.12.0 10.0.88.33 365885981 0 10611780 0 0
lan900:802 1500 10.0.12.0 10.0.88.37 6031497 0 359001 0 0
I know how to configure normal IP on lan card but how to do this trunk lan900:801 , lan900:802 , ... in hp ux ?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2013 06:14 AM - edited 06-12-2013 06:37 AM
06-12-2013 06:14 AM - edited 06-12-2013 06:37 AM
Re: LAN900:801
These are APA devices. Discuss with your DBA what kind of APA devices you need to configure (trunc or failover, etc ...).
Then use smh to create the APA device. After this you can configure the lan900 device just like a "normal" NIC.
Examples:
lan0 + lan1 = lan900 as a trunc
or
lan0 + lan1 = lan900 as failover
or even a combination
lan0 + lan1 = lan900 as a trunc
lan2 + lan3 = lan901 as a trunc
lan900 + lan901 = lan902 as failover
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Tags:
- APA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2013 10:21 PM
06-14-2013 10:21 PM
Re: LAN900:801
Hi,
i don't mean how to configure the APA on UNIX bu i mean with 801 and 802
lan900:801 1500 10.0.12.0 10.0.88.33 365885981 0 10611780 0 0
lan900:802 1500 10.0.12.0 10.0.88.37 6031497 0 359001 0 0
how to do this 801 and 802 and configure it for virtual and private IP of the cluster.
Thnaks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2013 01:57 AM
06-15-2013 01:57 AM
Re: LAN900:801
Hi,
i mean
How lanXX:802 or lanXX:803 .....etc got configured on unix server ?
is it from system side or database side ?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2013 02:40 AM
06-15-2013 02:40 AM
Re: LAN900:801
The questions you should be asking your DBA are:
- Are these addresses supposed to be fixed to this particular RAC cluster node, or movable to another node?
- If movable, is the RAC setup going to use HP Serviceguard or perhaps Oracle Clusterware to manage the movable cluster resources?
If these addresses are supposed to always stay on this node, then they are regular IP Aliases. There is no difference in setting them up on APA devices vs. regular NICs.
An IP Alias, also known as a secondary IP address, is automatically generated when you use ifconfig to assign an IP address to lan<existing interface>:<alias number> and deleted when you set its IP address to 0.0.0.0. In /etc/rc.config.d/netconf file, these are configured just like regular network interfaces.
Serviceguard also has a command for assigning an IP alias to a particular interface with a dynamically-chosen alias number, but you don't need it if you want to keep the alias numbers fixed. (Note: alias number 0 means the "main" IP adress for the interface, i.e. "lanXX:0" is the same as just "lanXX".)
If these addresses are supposed to be movable, then they should be configured to the cluster infrastructure that is supposed to move them when necessary. In HP-UX RAC setups, this is often HP Serviceguard, but I think it may be possible to use Oracle Clusterware for this purpose too.
If Oracle Clusterware is being used,
lan900:801 1500 10.0.12.0 10.0.88.33 365885981 0 10611780 0 0 lan900:802 1500 10.0.12.0 10.0.88.37 6031497 0 359001 0 0
These two lines look a bit odd. Are they from the output of "netstat -i" or a similar command?
Anyway, they don't quite have the right information for configuring the network interfaces. At minimum, you'll need two things for each interface (or alias): the desired IP address and the netmask. This output only reveals the IP addresses used, but it won't specify the netmask exactly: there is only the network address and the interface IP address.
Also, the information on those lines doesn't seem to be quite consistent: with a network address like 10.0.12.0, you would expect the netmask to be 255.255.255.0, but then 10.0.88.* does not fit into that network. If you relax the netmask enough to allow 10.0.12.* and 10.0.88.* to fit in the same IP network segment, then the network address won't be valid any more.
The tightest netmask that allows 10.0.12.* and 10.0.88.* to exist in the same IP segment is /17 = 255.255.128.0, but then the network address must be 10.0.0.0, according to the ipcalc tool on my Linux system:
$ ipcalc 10.0.12.0/17 Address: 10.0.12.0 00001010.00000000.0 0001100.00000000 Netmask: 255.255.128.0 = 17 11111111.11111111.1 0000000.00000000 Wildcard: 0.0.127.255 00000000.00000000.0 1111111.11111111 => Network: 10.0.0.0/17 00001010.00000000.0 0000000.00000000 HostMin: 10.0.0.1 00001010.00000000.0 0000000.00000001 HostMax: 10.0.127.254 00001010.00000000.0 1111111.11111110 Broadcast: 10.0.127.255 00001010.00000000.0 1111111.11111111 Hosts/Net: 32766 Class A, Private Internet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2013 05:35 AM
06-15-2013 05:35 AM
Re: LAN900:801
Hi,
This is oracle cluster RAC, when i try to create the VIP by using this steps
# ifconfig lan900:801 inet 10.0.18.22 netmask 255.255.255.0 up
# ifconfig lan900:802 inet 10.0.18.33 netmask 255.255.255.0 up
and edit this file /etc/rc.config.d/netconf and add the below
NTERFACE_NAME[4]="lan900:801"
IP_ADDRESS[4]="10.0.18.22"
SUBNET_MASK[4]="255.255.255.0"
BROADCAST_ADDRESS[4]=""
INTERFACE_STATE[4]=""
DHCP_ENABLE[4]=0
INTERFACE_MODULES[4]=""
INTERFACE_NAME[5]="lan900:802"
IP_ADDRESS[5]="10.0.18.33"
SUBNET_MASK[5]="255.255.255.0"
BROADCAST_ADDRESS[5]=""
INTERFACE_STATE[5]=""
DHCP_ENABLE[5]=0
INTERFACE_MODULES[5]=""
and i run this command to see the new VIP
# netstat -inw
lan900:801 1500 10.0.21.0 10.0.18.22 0 0 0 0 0
lan900:802 1500 10.0.21.0 10.0.18.33 0 0 0 0 0
but after reboot the server i can't find any thing
why ????
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2013 02:04 AM
06-17-2013 02:04 AM
Re: LAN900:801
INTERFACE_STATE[4]="" [...] INTERFACE_STATE[5]=""
Setting INTERFACE_STATE[4]="up" and INTERFACE_STATE[5]="up" would probably be a good idea.