On 8/11/06, James K Barnett <[EMAIL PROTECTED]> wrote:
The nic interfaces seem to be setup correctly. ie) linux-00:~ # qethconf vipa list vipa add 10.115.20.185 eth0 vipa add 10.115.20.185 eth1here is the hcp q nic details (editted) Unicast IP Addresses: 10.115.20.185 ( this is the vipa addr) 10.115.136.51 (eth0) Unicast IP Addresses: 10.115.20.185 10.115.137.51 (eth1) Jim Barnett United Health Technologies Mainframe Systems 763-744-3066 email: [EMAIL PROTECTED] Ronald van der Laan <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 08/11/2006 12:54 AM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: zLinux VIPA setup. Jim, Your vipa should be registered to your NIC to be able to receive packets (unless you set up a layer 2 vswitch), you can check that using: $ hcp q nic xxxx details (xxxx being the address of your eth0 or eth1 virtual NIC) If it does not show your vipa, you can set it manually using: $ qethconf vipa add xxx.xxx.xxx.xxx eth0 $ qethconf vipa add xxx.xxx.xxx.xxx eth1 Ronald van der Laan ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Make sure your eth mtu's are the same as the ones used in your router. also have your network guy check what the router sees in terms of ospf. keep in mind that anything originated from the linux server will be tag as coming from the eth and not the vipa address. check out source-vipa. i don't remember where I have the command but I issue a route command during boot up process to ensure all my outgoing packets were tagged with my vipa ip address. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
