--- In Avid-L2@yahoogroups.com, "James Hoppe" <james.hoppe@...> wrote:
>
> The other chassis is probably media manager. That sounds similar to our
> Unity configuration:
>
> 2x Array chassis (mirrored)
> 2x File Managers (mirrored)
> 1x Media Manager
> 1x Portserver
> 1x Fiber switch
> 1x Gig-E
>
> The only boards in our PortServer box are a Fiber card and a Gig-E.
> Personally, I would try what Dom suggests and pull as much as possible from
> the chassis, then re-install things until it STOPS booting. Also making
> sure everything is properly seated of course!
>
> ----- Original Message -----
> From: "johnrobmoore" <bigfish@...>
> To: <Avid-L2@yahoogroups.com>
> Sent: Friday, December 04, 2009 3:28 PM
> Subject: [Avid-L2] Re: Older Unity Lanshare Portserver?
>
>
> It could be a standard Unity so I've been told. It has a JBOD a file
> manager chassis, a port server chassis and another unlabeled chassis in a
> half rack. Assuming that is what it is can the entire portserver be shot
> gunned without requiring massive reconfiguration to work on our system. As
> you can tell my experience is more with other sans so please forgive my
> basic questions.
>
> --- In Avid-L2@yahoogroups.com, "Dom Q. Silverio" <domqsilverio@> wrote:
> >
> > I am not familiar with older LANShares. I did not know they had an
> > external PortServer.
> > Are you sure that is just a standard Unity?
> >
> > Second, maybe it is not the mobo or RAM sticks. It could be one of the
> > PCI cards. I would pull out all RAM sticks except for one and all PCI
> > cards. Boot up. Place one RAM stick and boot.
> >
> > Do this until you figure out which hardware is causing the issue.
> >
> >
> >
> > Dom Q. Silverio
> >
> >
> >
> > On Fri, Dec 4, 2009 at 2:49 PM, John Moore <bigfish@> wrote:
> > > We're having problems with the Unity Portserver on our lanshare that is
> used primarily for project sharing over ethernet. They've swapped ram and I
> believe the mother board but now it won't boot. At first they restarted the
> port server and even though it gave a memory error it did work but now after
> replacing ram and then the motherboard it won't boot. I'm just curious if a
> totally different port server that works can plug right in without
> disturbing what's already stored on the unity. I see we have two chassis
> labeled port servers, can there be two on a system or is one a spare?
> There's tech support working but we've been down two days with this and I'd
> like to help make a somewhat informed decision.
> > >
> > >
> > > John Moore
> > >
> > > Barking Trout Productions
> > >
> > > Studio City, CA
> > >
> > > bigfish@
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Search the offical complete Avid-L archives at:
> http://archives.bengrosser.com/avid/
> > >
> > > Everything you MUST know about Color Correction in one book:
> http://tinyurl.com/ColorCorectionforvideo Get your copy todayYahoo! Groups
> Links
> > >
> > >
> > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> Search the offical complete Avid-L archives at:
> http://archives.bengrosser.com/avid/
>
> Everything you MUST know about Color Correction in one book:
> http://tinyurl.com/ColorCorectionforvideo Get your copy todayYahoo! Groups
> Links
>
------------------------------------
Search the offical complete Avid-L archives at: http://archives.bengrosser.com/avid/
Everything you MUST know about Color Correction in one book: http://tinyurl.com/ColorCorectionforvideo Get your copy todayYahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Avid-L2/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/Avid-L2/join
(Yahoo! ID required)
<*> To change settings via email:
Avid-L2-digest@yahoogroups.com
Avid-L2-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
Avid-L2-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
No comments:
Post a Comment