[Orca-users] Re: gigswift support

[orcausers]

ce0 isn't there - bummer.
the orcallator.cfg 1.35 file - right at the top says it requires Orca 
0.264 - so it's about time to upgrade. i will do that when i can see 
the data being recorded. 

when i could not find any ce0 columns in the data file - i upgraded 
the orcallator.ce file to 1.35 -the data still is not being recorded.
the only thing i can think of to do now is upgrade to setoolkit 3.3.


 --- In orca-users at y..., Blair Zajac <blair at o...> wrote:
> I would then upgrade to the latest orcallator.se file.  I believe
> that orcallator_column needs the exact column name, so try a
> 
>     grep ce0 orcallator-200.......
> 
> and see if it's there.
> 
> Best,
> Blair
> 
> orcausers wrote:
> > 
> > except i don't see any data columns in the orcallator file that 
would
> > indicate this data is being recorded at all - i believe i would be
> > looking for a ce0 column using the orcallator_column utility.
> > here is an edited  netstat -i
> > # netstat -i
> > Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs
> > Collis Queue
> > lo0   8232 loopback      localhost      481925989 0     481925989
> > 0     0      0
> > ce0                                    2456263904 0     1186215456
> > 0     0      0
> > qfe2                                      1979604 0     98     0
> > 0      0
> > qfe3                                        0      0     0      0
> > 0      0
> > so there is activity -
> > i am trying to get ce0 on the graphs -
> > 
> > the qfe2 graph shows data - the qfe3 (althought all 0's appears) 
but
> > my goal is to get the ce0 interface on the graphs - it is a cPCI
> > gigswift card (compact gigaswift card).
> > 
> > i must be missing something (either a concept or a config item).
> > thanks for the help.
> > mik
> > 
> > --- In orca-users at y..., Blair Zajac <blair at o...> wrote:
> > > orcausers wrote:
> > > >
> > > > sorry - i meant the newest orcallator.se file - 1.35 - .
> > >
> > > No, you shouldn't need that.  Just the latest orcallator.cfg 
file.
> > >
> > > Best,
> > > Blair
> > >
> > > >
> > > > --- In orca-users at y..., Blair Zajac <blair at o...> wrote:
> > > > > orcausers wrote:
> > > > > >
> > > > > > curently running orca o.26beta1 - sorry dont know .cfg 
level -
> > > > > > and setoolkit 3.2 with 1.25 se file.
> > > > > >
> > > > > > i need to upgrade to cfg 1.35 to get gig support - do i 
have
> > to
> > > > > > upgrade to se 1.35 at the same time?
> > > > >
> > > > > There is no SE 1.35.  You mean orcallator?  No, older 
versions
> > > > should
> > > > > pick up the card.  However, check the output data files from
> > your
> > > > > orcallator.se just to make sure the data is being 
measured.  If
> > not,
> > > > > then I would upgrade.
> > > > >
> > > > > >
> > > > > > do i have to upgrade to setoolkit 3.3 also?
> > > > > > and  to orca 0.264 ?
> > > > >
> > > > > No.  You should not need to.
> > > > >
> > > > > >
> > > > > > and do i have to do all the domains at once if i upgrade 
orca
> > to
> > > > cfg
> > > > > > 1.35 to get the gig support - i don't have these gig 
cards on
> > all
> > > > the
> > > > > > domains but i think in previous conversation - it was all 
had
> > to
> > > > go
> > > > > > at once.
> > > > >
> > > > > No, you just need to upgrade the orcallator.cfg file on the
> > system
> > > > that
> > > > > runs Orca (you should only have one system running Orca).
> > > > >
> > > > > Best,
> > > > > Blair