SBUS and SCSI Controllers

I have a Sun box with a National Instruments SBUS
GPIB controller in it and need to add another GPIB
controller to the system. I am considering the
SCSI GPIB controller. Is it possible to mix these
two controller types on the same box? I'm
worried about driver/kernel problems doing so - is
it a valid concern? Has anyone else done this?
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Similar Messages

Sbus and scsi gpib controllers

I have a Sun box with an sbus gpib controller in it and need to another
controller.
I am considering adding the scsi bus gpib controller. Is this possible?
My main concern is over driver/kernel parameter conflicts - is it a
valid concern?
Has anyone else done this? What were your results?
thx.

It is difficult to specify the expected lifetime of the card.
You said that your system works if you change the cables, making the total cable length shorter. Can you change the cables without making the total cable length shorter? This may indicate a faulty cable rather than a drive problem with the controller.
When your system fails does the card lose context? By this I mean do the registers reset to their default values? You should be able to determine this by checking status to see if the board is still listen/talk addressed or CIC like it was before the failure.
Also, can you be more specific about the failure? How do you know it has failed and what do you do to fix it?

How to reconfigure numbering scheme of scsi-controllers manually after Inst

We installed an E420 with solaris 8. This machine should be part of a sun cluster
for this reason the numbering of the scsi-controllers which manage the ecternal diskarrays should be identical on all machines. Om on machine we had another external disk attaached to the external scsi-controller.
here the numbering for D1000 starts with c2 and on our other machine it starts with c1.
Is there any possibility to change this without doing a new installation ?

You may want to try devfsadm -C (cleanup) with your 2 external controllers disconnected (unplugged from 420r). This should remove c1 & c2 from /dev/desk & /dev/rdsk. Then install the controller you want to be c1 and do devfsadm -c disks. Install the controller you want to be c2 and do devfsadm -c disks gaian. Hopefully you now have the controllers numbered correctly. This assumes you are booting from c0.

Neo F and SCSI

I wanted to try Vista64 on my Neo-F (I have Vista32 on a Raptor now); I disconnected the Raptor (so that way I could keep my working boot of Vista) and am using an LSIU160 SCSI card and a 15K Fujitsu (both from another older system). Anyways, just wondering what the BIOS settings are in order to get this setup to work. If I disable the IDE/Raid in Integrated Peripherals-On Chip ATA devices, the LSI BIOS comes up and id's the SCSI drive (also bios shows Fujitsu as an option in the Disk Boot Priority) but then won't boot (gets stuck in CLIENT MAC ADRESS blah,blah..DHCP....DISK BOOT FAILURE)
If I enable IDE/Raid option, then LSI BIOS wont show; VISTA install sees ther drive but states that BIOS won't allow boot and then aborts the install.
Anybody got any ideas on how I can get this to work?? I did search archives but could not find any thing relative to my situation.
Thanks-
Joe

Quote from: Joe on 16-February-07, 13:16:30
Tried that; in fact, I tried disabled, tried int 18, int 19, still couldn't get it to load scsi bios (with IDE chosen in Peripherals sub-menu). The only way it sees LSI bios is if I disable IDE...then can't load vista because I have IDE (CDROM) disabled. I put everything back together (Vista32 on Raptor)....I may try again tomorrow; either that, or just use a spare IDE drive to setup Vista64 (if I like, then I will put it on Raptor). Thanks for your reply.
Check your bios version. I had problems with LSI AcceleRAID 1100 and Atto u3ls SCSI controllers with booting while using bios 1.5.
After updating to bios 1.6B9 or later beta I got Atto working. LSI is still unbootable. When I connect Adaptec 2100s or Atto u3ls controllers with scsi hdds and go to mainboard BIOS. I can see in harddrive boot priority list all my SCSI harddrives. My LSI card wont show any hdd's to mainboard BIOS and cannot boot.
So when bootpriority menu says like 1: floppy 2: cd-rom 3: hard-disk, check that the hard-drive bootpriority menu 1) has your SCSI HDD's shown and 2) they are in proper order.
What I noted with Jmicron, is that when u change devices in it, it may result your BIOS boot order list to reset.
Also if you got bad read/write performance with your SCSI card, it might be bios problem. As u see I have 3 scsi conrollers (2 of them raid) and none of the raid controllers worked well with msi 965 neo-f. Atto u3ls is working fine, but it is non-raid card so I have very little value for it. LSI was unusable, and Adaptec 2100s is seriously writebandwidth limitted due to bios or pci problems with the motherboard. (read 80-90mb/s, write 5-10mb/s)
I bought asus P5B-E+ yesterday and had serious problems with booting again. After bios flashing I got Adaptec 2100s bootable, but LSI stays unbootable. And I still got performance problems while my write performs now like 40-50mb/s, my read bottlenecs to ~55-60mb/s, while maximum bus burst bandwidth is only like 68mb/s. (32bit PCI)
What I noticed with this asus is that it does not understad any bootsettings my SCSI card might offer. Only way it tries to boot is like choosing the card and then trying HDD with smallest LUN ID, while on MSI i could actually choose which hdd i want to use.
This could happen with your LSI card too, so try to check you are using SCSI ID 0 for your boot drive.
Oh also, I had really serious issues with 965 neo-f and PCI Slot #2 with almost all PCI cards. If you use your SCSI card on pci slot2, try to change it to slot3 or slot1. I had some gfx problems and jmicron problems while stuff on slot2.
Hope it helps, tho cant do any debug with my machine anymore as I am mailing my neo-f today to its new owner.

Component and custom controllers

Hi! Can someone tell me the difference between custom and component controllers? and any guidelines as when to use what?

Hi,
Majority Component/Coustom controllers resembles same. Still I found following differences
There will be only one default Component controller (called global) in a particular project but there can be any number of coustom controllers (we can create depending upon the requirement).
Component controller has the follwing methods apart from wdDoInit(), wdDoExit()
public void wdDoPostProcessing(boolean isCurrentRoot)[
This method is called to handle data retrieval errors before rendering.After doModifyView(), the Web Dynpro Framework gets all context data needed
*for rendering by validating the contexts (which in turn calls the supply
functions and supplying relation roles). In this hook, the application
should handle the errors which occurred during validation of the contexts.
public void wdDoBeforeNavigation(boolean isCurrentRoot)[This allows you to flush the model queue and handle any
errors that occur. Firing outbound plugs is allowed.]
Genarally all the coustom code is coded in coustom controller for example if you want to add additional methods of your own, in case if you want to validate webdynpro UI elements input this validation code is coded in coustom controllers
go through the following URL
http://help.sap.com/saphelp_webas630/helpdata/en/eb/e1cb5eea012b4481f8077c6023a70e/content.htm
I hope it helped you
RK

URGENT!!! Can ATA and SCSI coexist?

hello fellas!
my case is similar of the post "Can SCSI and ATA coexist?', but with some differences:
I own a G4 Dual 500–MHz PowerPC G4, 40Gb ATA + 80GB ATA. (http://support.apple.com/specs/powermac/PowerMac_G4_GigabitEthernet.html)
now I've installed a PCI SCSI card to connect tree more SCSI HDs: two barracuda 18Gb and one quantum 36Gb)
my G4 only reads SCSI drives when I disconnect ATA tape from motherbard...
when I plug ATA to motherboard again, neither SCSI mount on desktop, nor system profile shows it as a device, even when I start Hard Drive Update 1.app...
I've read all manuals from apple, jumped all SCSI HDs, but for some reason, it doesn't work at all!
so, the question, again, is Can ATA and SCSI coexist?
does anyone knows how to config it??
thanks in advance!
b
G4 Dual 500–MHz PowerPC G4 Mac OS X (10.4.8) [email protected]

answering:
- as my primary language is portuguese, i didn't understand when you said 'booting off the OS X disk'. do you mean eject it in the disk utility?
- I have so many drives because e sold another G4 that used those drives atached with the pci card and I simply want to use it, because I'm short on cash... those drives are installed with OS 9.2 (the ATA ones are running OS 10.4.8)
when you said one ATA and 2 SCSI, you mean that if I simply disconnect the slave ATA and one of the SCSI it may works?
thanks again!
b

Udev and SCSI partitions not mounted

I have just attempted to convert devfs to udev on my dual AMD Opteron with two SCSI drives running fully up-to-date Arch Linux. The result of following the standard udev procedure (which has worked on three other IDE machines without a hitch) was that of the four mountable SCSI disk partititions, only swap and / were mounted properly
/dev/discs/disc0/part1 / reiserfs defaults 0 0
dev/discs/disc0/part2 swap swap defaults 0 0
while the /home and /data partitions were not recognized and mounted:
/dev/discs/disc0/part3 /home reiserfs defaults 0 0
/dev/discs/disc1/part1 /data reiserfs defaults 0 0
I was able to revert the machine back to its original devfs so the machine does work properly in its original configuration.
I noticed a bash script in the /etc/udev directory that seemed to be used to identify the SCSI devices present. Is it possible that this is not working correctly? Does anyone have any idea of how the SCSI configuration could have gone awry?
Thanks.
Some details about the machine:
arch version: Arch Linux 0.7 (Wombat)
kernel version: 2.6.7
two processors: AMD Athlon(tm) MP 2600+
two SCSI_storage_controllers: Adaptec AIC-7899P U160/m (rev 1).

Once again, I installed archlinux on an scsi machine, and have been cought in the boot-scsi-device-fails-udev-trap. This time, I had a bit of time. Instead of editing the fstab entries, I decided to find out why ide devices are handled well, and scsi devices are not.
Have a look at udev.rules. You will find an entry for ide block deviced there, that creates devfs symlinks:
# ide block devices
BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-devfs.sh %k %b %n", NAME="%k", SYMLINK="%c{1} %c{2}"
You will notice also there are no similar entries for scsi block devices. Therefore, their nodes will not fit devfs scheme. Now, let's have a look at /etc/udev/. You will find scsi-devfs.sh there. This script will create devfs-like nodes for scsi blocks. Now the problem is clear, isn't it. Add the following lines to udev.rules:
# scsi block devices
BUS="scsi", KERNEL="sd*", PROGRAM="/etc/udev/scsi-devfs.sh sd %b %n", NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
BUS="scsi", KERNEL="sr*", PROGRAM="/etc/udev/scsi-devfs.sh sr %b %n", NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
BUS="scsi", KERNEL="st*", PROGRAM="/etc/udev/scsi-devfs.sh st %b %n", NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
BUS="scsi", KERNEL="sg*", PROGRAM="/etc/udev/scsi-devfs.sh sg %b %n", NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
Now the devfs naming scheme should be used for scsi devices, too. Surprisingly, it isn't. Any hints are welcome.

Computer Blue Screen when VXI chassis is shutdown Using NI VXI-8360T MXI-VXI and PCIe8362 controllers

Problem Description :
Using NI VXI-8360T MXI-VXI and PCIe8362 controllers.
The software I have is Measurement and Automation Explorer version 5.5.0f0 Problem:
We have had both controllers set up and working together to include running other VXI instruments using the MXI bus. The problem we are having is that when the VXI chassis is shutdown, it causes the computer (that has the PCIe8362 card in it and connected to the VXI card bus) to experience a blue screen of death.
With our older 777178-01 VXI-MXI-2 configuration, our computer does not experience the blue screen when shutting down the VXI chassis while the computer is still on. Do you have information or past issues with the computer experiencing a blue screen due to VXI chassis shutdown?
NI Software : Other version
NI Hardware : VXI/VME/MXI device VXI-8360T
Driver Version :
OS :
Windows 7

Are you using NI-VXI 3.8.1 (or later) and supported hardware for VPO (variable power on) support?
http://digital.ni.com/public.nsf/allkb/6B1F05BB5C0E321186257950007424B2
I think you need to "warn" the hardware/driver you're going to turn the chassis off, either via MAX or a programatic call. Sorry I can't give any more specific help, but I've only heard about this and haven't ever done it myself.
- Robert

MSI Neo2 865PE and SCSI Controller Question

Hi All,
Im new here so be easy on me
Anyways im currently building a new system P4 System based on the new 800FSB, i have all the parts ready, ie. CPU, DDR400 RAM, Case, Adaptec SCSI Controller, HDD etc etc, but believe it or not i havent purchased a motherboard yet. The reason being i want to get clarification that my setup will actually work with the motherboard before i go out and buy it. WHAT SETUP you ask, please read on
Now the reason im posting here is because from what i can see on the internet this is a really top notch board (best performer in the recent THG test) so naturally its one of the boards im considering.
Now to the my QUESTION: I want to use my SCSI drive connected to the Adaptec as the OS drive and boot from it. However my main concern is that the Neo2 865PE wont let me boot of the SCSI Hard Disk attached to the Adaptec SCSI 21960 controller. Ive been told that certain motherboards eg. ASUS wont detect a SCSI controller on boot up because it will only detect the onboard RAID controller as the SCSI controller, therefore not letting you use the SCSI disk at the boot device.
Can anyone ease my mind and tell me the MSI 865 Neo2 will let me do what i intend??? ie. Boot of SCSI disk.
Any response/comments is appreciated
Cheers

Hi Domino,
Thanyou for testing the setup out for me.....
When you tested it did you have your onboard Intel S-ATA RAID controller enabled? because i believe this is where the problem will eventuate, when you enable the m/b's ONBOARD RAID controllers.
Cheers

OS 10.4.9 and SCSI card

Recently I installed OS 10.4 and prior to installation had to remove the SCSI card (wouldn't boot up off of disk with card in place). After removing the card installation was no problem. I tried a USB card but "Sleep" no longer works. Now that I have the system installed, do you think there will still be a conflict if I reinstall the SCSI card (use it for ZIP drive back up)either in operation or possible problems with update installations?
Any ideas?
Thanks,
Glen

Allan,
The SCSI card is Adaptec, AVA 2906(I think this is the model #). It was installed when I bought my computer years ago. I don't have any more info on it, other than what I find on the card. When I had problems with installation, I looked here in discussions and found some peripheral info on others with trouble having SCSI cards installed, that is how I decided to try removing it before installation. I thought the USB card would be the answer but as mentioned, trouble with that also.
Thanks,
Glen

WSUS and domain controllers

Has anyone arrived at a good GPO(s) for domain controllers to be updated by WSUS? Of course, one in which only half of the domain controllers at each facility receive the updates at one time and another half at a separate time.

Has anyone arrived at a good GPO(s) for domain controllers to be updated by WSUS? Of course, one in which only half of the domain controllers at each facility receive the updates at one time and another half at a separate time.
Well... the conventional wisdom is that Domain Controllers should not have automated installs, but rather monitored installs. So... AUOptions = '3', and a human being to launch the installs and monitor the reboot at a time when appropriate with consideration
to the other Domain Controllers.
However, if you must *schedule* these things, then you'll have to use Active Directory Security Group Filtering, create TWO GPOs for the Domain Controllers OU, and filter one GPO to one half (via Security Group 'A') and filter the other GPO to the other
half (via Security Group 'B').
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WLC mobility group between 4404 and 5508 controllers

Mobility 'Control and Data Path Down' between 4404 and 5508 WLC's.
Hello, we have 5 x 4404 WLC's running 7.0.240.0 with mobility configured fine between them.
We have installed a 5508 with HA running 7.4.110.0, and have tried to add it to the mobility group, however we see 'Control and Data Path Down' between the new 5508 and all the 4404 controllers.
All controllers have:
The same virtual address
Management interfaces are in the same VLAN, and indeed all the controllers connect via the same pair of 3750X stacked switches.
The default mobility domain name is the same
4404 output when issung the command 'show mobility summary'
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
5508 ouput when issueing the command 'show mobility summary'
Mobility Architecture ........................... Flat
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
I've spent quite some time double checking all the configurations to no avail.
Has anybody seen this problem before?
Kind regards
Dave Bell

Thanks Sandeep.
I am well versed with WLC's and mobility, however trying to add a 5508 to a mobility group with 4404's has come up with a bit of a curve ball.
All the 4404 controllers all joined the mobility group fine, no problems at all - its only the 5508 I am struggling with.
In theory its simple, populate the IP address, and MAC addres of the management interface of the remote WLC, as long as the management interfaces are in the same VLAN, and the Default Mobility Domain Name are the same it should come up.
Interestingly I have found the 5508 reports its own management interface MAC address incorrectly when viewing the Mobility Groups:
For example:
{Screen shot WLC1.jpg}
5508 management address is 10.95.x.x and when viewing the Mobility Management screen it shows its own MAC address as bc:16:65:f9:37:60.
however!
From our router is I do an sh arp | i 10.95.x.x (controller management address), I see:f872.eaee.becf.
{Screen shot wlc2.jpg}
Hence the WLC reports as: bc:16:65:f9:37:60
and
The network reports as: f872.eaee.becf for the same IP address.
I have changed the other WLC's to the MAC adress seen on the network for the new controller, aka changed from
bc:16:65:f9:37:60
to
f8:72:ea:ee:be:cf
I now see the controllers reporting the mobility with the new controller as 'Control Path Down', however I am at a loss as to what may be causing this?
Kind regards
Dave Bell

ASM Failure Groups and Disk Controllers

Hey guys,
I understand that it's considered a good idea to set different Failure Groups for disks which could fail at the same time because they share hardware, For example, disks that share the same disk controller.
Now, my question might be silly but I don't understand why we would configure multiple disks with the same disk controller.
Thank you,
Jerry.

Jerry wrote:
Hey guys,
I understand that it's considered a good idea to set different Failure Groups for disks which could fail at the same time because they share hardware, For example, disks that share the same disk controller.
Now, my question might be silly but I don't understand why we would configure multiple disks with the same disk controller.
Hi Jerry,
Your question is not silly.
Usually you have one or more disk controllers in a system
Each controller can handle up to x disks ( in the past this was 15, don't know if this still is )
If you wanted to be redundant, like with RAID1 ( mirrorring ) configurations a system was usually configured to have an even amount of disks
spread evenly over two controllers.
This then covered disk-failure and controller failure, as each logical disk in the mirror-set is accessible over two controllers and consists of -at least - two disks.
In ASM you would configure the main diskgroup on the first set of disks on the first controller.
The failure group would then be configured on the second set of disks on the second controller.
In the SAN world, with ASM using Host Based Mirroring, the Failure group can also be a diskset on a totally different storage-server
Edit: Totally forgot: More disks on one controller mean more parallel access to your data, as you can read all seperate disk seperately.
In the current days with the enormous disks it is quite easy to configure just one disk in your system, but that will bring you quite easy huge performance problems
HTH
FJFranken
Edited by: fjfranken on 20-jul-2011 6:53

Intel Xserve and SCSI Tape Autoloader - Not Being Seen

I have a brand new intel xserve with the added scsi card. I have a sun storedge L9 attached to the system and am unsure how to get the system to detect it. I am sure that the hardware and cables are all compatible. System profiler shows the scsi card and channels but doesnt show anything connected.
Is there a way to browse/search the scsi bus?

Yes, I am using that POS lsilogic. With the new card,
does the device show up in system profiler?
It does with the ATTO. It sometimes would with the 22320.
I am a little unsure where to look for my
autoloader... sys profiler, /dev/?, disk util?
System Profiler. There is no /dev/? for it.
Each backup program has to provide their own set of drivers
that access the SCSI card.
Tolis Group (makers of the BRU backup utility) sells a set
of tape tools that makes standard unix tools (tar, etc.) work
with autoloaders and tape drives. They also sell BRU, a
tape backup utility. Retrospect (EMC) also has drivers to
control autoloaders. Both BRU and Retrospect have trial
versions for download that you might try.
Russ
Xserve G5 2.0 GHz 2 GB RAM Mac OS X (10.4.8) Apple Hardware RAID, ATTO UL4D, Exabyte VXA-2 1x10 1u

Redhat linux and scsi

anybody has experience with oracle 9i RAC and parallel werver installation and configuration on redhat linux with SCSI card and external SCSI disk enclosure? where to find which SCSI card is supported by linux? how about SCSI enclosure. Some SCSI has 50pin connector, other has 68pin. which one should be used?
Thanks.
william

Here is the link where you can download the OVA,
if you still have issue let me know the exact error. let me see what i can do.
Downloading Virtual Machine Templates (OVA Templates)
The configuration of a Cisco Unified Communications Manager virtual machine must match a supported virtual machine template.
Perform the following procedure to obtain the virtual machine template for Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server:
Procedure
Step 1 Select this URL in your browser:
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
Step 2 If your browser prompts you to do so, type your Cisco.com User Name: and Password: in the text boxes, then click the Log In button.
Step 3 Choose IP Telephony > Call Control > Cisco Unified Communications Manager (CallManager) > Cisco Unified Communications Manager Version 8.0.
Step 4 Click the Unified Communications Manager Virtual Machine Templates link.
Step 5 In the Latest Releases folder, click the 1.0(1) link.
Step 6 Click the Download Now button. Follow the prompts and provide the required information to download the software.
Step 7 When the Download Cart window displays, click the "Readme" link to view the virtual machine template's release information.

SBUS and SCSI Controllers

Similar Messages

Maybe you are looking for