[Orca-users] RE: Adding Interfaces to netif.se

[Camron W. Fox]

"Camron W. Fox" wrote:
>>
>> "Camron W. Fox" wrote:
>> >> Blair,
>> >>
>> >>         We are running V1.34. The FJ GigE's naming conventions are
fjge0,
>> fjge1,
>> >> etc. and all we're seeing is in the output files are hme0, hme1, etc.
>> (Each
>> >> box has at least one of each).
>>
>> > Did you check the output orcallator* files for fjge0, fjge1, etc?
>>
>>         Yes. As you can see from the output below, no joy.
>>
>> bash-2.03# hostname
>> a01
>> bash-2.03# ifconfig -a
>> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
>>         inet 127.0.0.1 netmask ff000000
>> fjge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
2
>>         inet 133.40.148.181 netmask ffffff00 broadcast 133.40.148.255
>>         ether 0:0:e:25:7:56
>> fjge1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
3
>>         inet 133.40.148.182 netmask ffffff00 broadcast 133.40.148.255
>>         ether 0:0:e:25:7:56
>> fjge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
4
>>         inet 133.40.149.181 netmask ffffff00 broadcast 133.40.149.255
>>         ether 0:0:e:25:7:56
>> fjge3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
5
>>         inet 133.40.149.182 netmask ffffff00 broadcast 133.40.149.255
>>         ether 0:0:e:25:7:56
>> hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
>>         inet 133.40.159.181 netmask ffffff00 broadcast 133.40.159.255
>>         ether 0:0:e:25:7:56
>> bash-2.03# cd /admin/orca/a01
>> bash-2.03# ls -l
>> total 1960
>> -rw-r--r--   1 nobody4  other      49388 Jul 30 23:55
>> orcallator-2002-07-30-000.bz2
>> -rw-r--r--   1 nobody4  other     945249 Jul 31 07:05
>> orcallator-2002-07-31-000
>> -rw-r--r--   1 nobody4  other          6 Jul 30 10:39 orcallator.pid
>> bash-2.03# grep fjge orcallator-2002-07-31-000
>> bash-2.03#

> Which version of SE are you using?  If you're not using 3.3, try upgrading
> to that.

> Finally, I would try to see if any of the other SE example scripts can
> see these devices.  If they can, then it should be pretty straight forward
> to have orcallator.se modified.  If not, then I think you'll need to get
> SE modified to recognize the fjge* devices.  In the second case, I would
> email se-feedback at setoolkit.com.

	We're using 3.3, and we've tried. For example, net.se sees all 31 of the
hme interfaces (only one is plumbed), but none of the fjge. We've looked at
the include files netif.se and ndd.se and adding the fjge type network
shouldn't be to bad, we're mostly concerned with the kstat struct in
kstats.se.
	We also sent email twice last week to se-feedback at setoolkit.com, but no
response.
	Any other suggestions? The traffic over the FJ PRIMEPOWER (200-2000H)
machines is mainly on the multiple GB interfaces and we can't monitor them
very well at the moment (via orcallator, anyway).
	What I wouldn't give for another 50 Blade 2000s!

Best Regards,
Camron

Camron W. Fox
Hilo Office
High Performance Computing Group

Fujitsu America, INC.
E-mail:			cwfox at fujitsu.com
Phone:			(808) 934-4102
Pager:			(808) 934-1290
Cell:				(808) 937-5026