Hi Leonid, The best approach when switching from another vendor SM to OpenSM is to delete the /var/cache/osm/guid2lid file.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:openib-general- > [EMAIL PROTECTED] On Behalf Of Hal Rosenstock > Sent: Tuesday, September 05, 2006 4:18 PM > To: Leonid Arsh > Cc: openib-general@openib.org > Subject: Re: [openib-general] OpenSM - guid2lid cache file questions > > Leonid, > > On Tue, 2006-09-05 at 09:13, Leonid Arsh wrote: > > Thanks, > > > > On 05 Sep 2006 08:46:22 -0400, Hal Rosenstock <[EMAIL PROTECTED]> wrote: > > > > I have a problem when OpenSM, being started, reads an out-if-date > guid2lid file. > > > > OpenSM changes LIDs in this case. > > > > > > How do you know the file is "out of date" ? > > > > > Actually, the LIDs were assigned by another SM. > > Different (vendor) SMs have different LID assignment and pathing > (routing) policies. It is inadvisable to failover across vendor SMs for this and > other reasons. > > -- Hal > > > When I start my new OpenSM, the old SM is already dead. > > Before starting the new OpenSM, the ibnetdiscover utility shows LIDs > > different from ones in the file. > > When I start OpenSM, the LIDs are reassigned on the fabric. > > > _______________________________________________ > openib-general mailing list > openib-general@openib.org > http://openib.org/mailman/listinfo/openib-general > > To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general _______________________________________________ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general