[Veritas-bu] 4.5 and vm.conf and REQUIRED

        As I said, my problem was slightly different.  I tried to restrict the
number of servers that could connect to vm.  I used their new "SERVER="
command.  That, in conjunction with REQURED_INTERFACE broke access for the
clustered media server and that is how I found out about the problem.  Once all
"SERVER=" enteries were removed, REQUIRED_INTERFACE alone was working fine.
 Let me rephrase that - it is functioning without a problem, but I am pretty
sure that the entry gets ignored.  So I got the functionality without security.
 Hope that helps.

paulg

On Jun 6,  3:04pm, Peter DrakeUnderkoffler wrote:
> Subject: Re: [Veritas-bu] 4.5 and vm.conf and REQUIRED_INTERFACES
> Paul,
>
> The problem showed up in MP3 and is still there in MP4.  I just
> heard that MP5 is due to us all around mid July.
>
> Did you require that traffic go through that alternate interface in the
> end?  If so, what did you do to get there?
>
> Thanks
> Peter
>
> Paul Gimpelev wrote:
>
> >No, they did not.  They said it was broken in general.
> >
> >paulg
> >
> >On Jun 6, 12:10pm, Peter DrakeUnderkoffler wrote:
> >
> >
> >>Subject: Re: [Veritas-bu] 4.5 and vm.conf and REQUIRED_INTERFACES
> >>Thanks for the response.  Did they say what was broken on it?
> >>It works between two of the hosts no problem.  It is quite
> >>specific to the third host.
> >>
> >>Thanks
> >>Peter
> >>
> >>
> >>Paul Gimpelev wrote:
> >>
> >>
> >>
> >>>I did not have an identical problem, but we did have an issue with SSO
which
> >>>lead to Veritas admision that REQUERED_INTERFACES in vm.conf was broken.
> >>>
> >>>
> >  It
> >
> >
> >>>did take a while for them to admit to it.  We have MP3, however.  They
might
> >>>have implemented the fix in time for MP/FP4.  Hope this helps.
> >>>
> >>>paulg
> >>>
> >>>On Jun 6, 11:39am, Peter DrakeUnderkoffler wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>Subject: [Veritas-bu] 4.5 and vm.conf and REQUIRED_INTERFACES
> >>>>
> >>>>Have a customer with 4.5 DC and MP4, there are three hosts,
> >>>>
> >>>>host = alpha
> >>>>  Master/Media
> >>>>  E450
> >>>>  Sol 2.8
> >>>>  backup net = alpha-bkup
> >>>>  vm/da host
> >>>>
> >>>>host = beta
> >>>>  Media Server
> >>>>   E10K
> >>>>  Sol 2.6
> >>>>  backup net = beta-bkup
> >>>>
> >>>>host = gamma
> >>>>  Media Server
> >>>>  E10K
> >>>>  Sol 2.6
> >>>>  backup net = gamma-bkup
> >>>>
> >>>>Each host has multiple net connections including a dedicated
> >>>>backup communications net. In addition, SSO is in place.
> >>>>In the vm.conf file I have "REQUIRED_INTERFACE = <host>-bkup"
> >>>>since that is allowed in 4.5 now.  On host alpha and beta, everything
> >>>>works fine and vmd communication take place over the backup net.
> >>>>Now when I place the "REQUIRED_INTERFACE = gamma-bkup"
> >>>>in the vm.conf, we get these problems:
> >>>>
> >>>>-on startup, ltid kicks of vmd then it kills itself
> >>>>-perform a "vmquery -h alpha-bkup -a" and vmquery dumps core
> >>>>-vmd communication from alpha-bkup to gamma-bkup fails
> >>>>
> >>>>I checked all the things I could such as /etc/hosts, /etc/nsswitch.com
> >>>>/etc/system, the NetBackup install, the maintenance pack install...
> >>>>
> >>>>When I leave the entry out of vm.conf, communications go over the
> >>>>default LAN interface (which will eventually be locked down)
> >>>>and everything performs fine.
> >>>>
> >>>>Anyone see anything like this elsewhere?
> >>>>
> >>>>
> >>>>Thanks
> >>>>Peter DrakeUnderkoffler
> >>>>
> >>>>
> >>>>_______________________________________________
> >>>>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> >>>>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >>>>-- End of excerpt from Peter DrakeUnderkoffler
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>-- End of excerpt from Peter DrakeUnderkoffler
> >>
> >>
> >
> >
> >
> >
> >
>
>
>-- End of excerpt from Peter DrakeUnderkoffler