Rempa device numbers in a zone?

Hi,
I have three zones and three tape drives in the global zone (rmt/0, rmt/1 and rmt/2). I can easily add one tape drive to each zone my puttnig the line:
<device match="/dev/rmt/X"/>
where X is a 0 a 1 or a 2
into the correct /etc/zones/xml file.
If I map drive 2 to the third zone the zone sees the device as /dev/rmt/2. All is well with the zones.
My questin follows. The 3 non global zones are replicas of one another. They each run the exact identical software. Currently when they write to tape they want to use /dev/rmt/0. Does anyone know of a wayt that I can remap the drives in the second and third zones so that even though drive 1 and 2 are in the zone the zone can see the drive as device 0?
I tried simply making a link in the zone:
cd /dev/rmt
ln -s 2 0
But the o/s will not let root write in that directory.
Any other ideas? I want to avoid having to write code into the application to figure out what zone it is in and then map the appropriate drive. I simply want the app to use /dev/rmt/0 all the time.
Thanks,
Eric

I haven't tried this myself, but according to Sun's
own Zones documentation
(http://www.sun.com/bigadmin/features/articles/zones_p
artition.html) you should be able to manually add
devices using zonecfg and then tell it which devices
to match. So shouldn't it be possible to make it
match the tape device on all zones?Yes, but the OP wants the name of the device in the global zone and the non-global zone to be different. You can't do that in zonecfg.
Darren

Similar Messages

Problem with exporting devices to non-global zone

Hi,
I've problem with exporting devices to my solaris zones (i try do add support to mount /dev/lofi/* in my non-global zone).
A create cfg for my zone.
Here it is:
$ zonecfg -z sapdev info
zonename: sapdev
zonepath: /export/home/zones/sapdev
brand: native
autoboot: true
bootargs:
pool:
limitpriv: default,sys_time
scheduling-class:
ip-type: shared
fs:
dir: /sap
special: /dev/dsk/c1t44d0s0
raw: /dev/rdsk/c1t44d0s0
type: ufs
options: []
net:
address: 194.29.128.45
physical: ce0
device
match: /dev/lofi/1
device
match: /dev/rlofi/1
device
match: /dev/lofi/2
device
match: /dev/rlofi/2
attr:
name: comment
type: string
value: "This is SAP developement zone"
global# lofiadm
Block Device File
/dev/lofi/1 /root/SAP_DB2_9_LUW.iso
/dev/lofi/2 /usr/tmp/fsfile
I reboot the non-global zone, even reboot global-zone, and after that, in sapdev zone, there is no /dev/*lofi/* files.
What i do wrong? Maybe I reduce my sol 10 u4 sparc instalation too much.
Can anybody help me?
Thanks for help,
Marek

I experienced the same problem on my system Sol 10 08/07.
Normally, when the zone enters the READY state during boot, it's zoneadmd will run devfsadm -z <zone>. In my understanding this is to create the necessary device files in ZONEPATH/dev.
This worked well until recently. Now only the directories are still created.
It seems as if devfsadm -z is broken. Somebody should issue a call to sun.
As a workaround you can easily copy the device files into the zone. It is important not to copy the symbolic link but the target.
# cp /dev/lofi/1 ZONEPATH/dev/lofi
Hope this helps,
Konstantin Gremliza

I'm tring to install two Daqcard700's in same computer running Win2000 and Nidaq6.9.2 and the cards are not given two different device numbers by the NIDAQ device configuration wizard.

One Daqcard 700 and one daqcard 16x-50e in same machine work fine but two Daqcard 700's are not assigned two diferrent device numbers by the device configuration wizard.

I have this same problem with the previously described observations. I tried two Daqcard-700s in three different laptops, two with Windows XP and One with Windows 2000. Tried all suggestions in Knowledgebase and Forum I could find with no luck. Single cards work ok. Removed and reinstalled drivers in Device Manager. Tried the Windows 2000 patch for this problem. Changed the PCMCIA adapters on the laptop to Generic Cardbus Controller from one suggestion. Running Labview 6.1 with Ni-Daq 6.9.3 and Max 3.1. Tried also Max 2.1.
Any help will be greatly appreciated.
thanks,
Ben1167

MAX 5.3.1 removed Device numbers from SCXI-1600

Meas. & Auto. (MAX) 5.3.1 removed Device numbers from SCXI-1600
Old system - Works! : Labview 9.0 on Dell laptop win XP.
I have a client that uses multiple laptops & multiple SCXI chassis with 1600 USB DAQ controller mod. Each time a “new” 1600 was used a new SCXI chassis was installed and the new 1600 was given the next device number (Ex. Dev1, Dev2, Dev3). I would use the DAQmx System class Node, DevNames property to see which device I had and go from there. (Note: this still worked on LV ver. 11 & MAX 5.x ?)
I upgraded to LV 2012 (32 bit) fix#3 with MAX 5.3.1 and the Device number (Dev1) is now replaced with “Mod1”! I know I could program a workaround, but I would rather have the names go back to the old Device numbers!
Solved!
Go to Solution.

Hi Tom,
Thank you for posting. I recently noticed this problem and reported it to R&D as CAR #362997. The change of SCXI-1600 default name from "Dev1" to "Mod1" seems to have been introduced in NI-DAQmx 9.4. I can't guarantee anything, but the fix is currently on track to go into the next version of NI-DAQmx (excluding patch releases).
For now, I'm afraid you'll have to work around the problem. Here are a few ways you can do that:
Manually rename the device in MAX on each system.
Programmatically rename the device using the NI System Configuration API. Look at <LabVIEW>/examples/nisyscfg/Rename Aliases.vi for an example.
Change your application to use a different default name or to detect the device differently (e.g. using the DAQmx System >> DevNames and DAQmx Device >> ProductType properties).
Brad
Brad Keryan
NI R&D

Table for EDM Profile with Installation or Device numbers

Hi
Can anybody answer Table for EDM Profile with Installation or Device numbers?
Thanks in advance.
DGR

Hello,
You allocate the profile to a register so you want to have your logical register number.
If you have the equipment number you could go to table ETDZ or call FM ISU_DB_ETDZ_SELECT and fetch the registers.
If you want to see the table of profile allocations you can check table EPROFASS.
If you use IS-U-EDM the tables which contains informations about profile values are EPROFVAL*...
Hopefully some of this infomation is useful for you.
Regards
Olivia

Internal disks changing device numbers

Cliff's Notes:
I have an SSD and an HDD (in place of the optical drive) in my MacBook Pro 6,2 (late '10). Originally, the SSD was reported as "disk0" and the HDD as "disk1"; but, as of last night, they seem to have switched designations. How did that happen? Is there a way to prevent it?
Long version:
I have a Western Digital 640GB HDD (WDC WD6400BEVT-22A0RT0) that was previously in my old (MBP1,1 '06) MacBook Pro and was the cause of a drop in performance because the drive heads were constantly parking (as discussed in this topic: http://discussions.apple.com/thread.jspa?threadID=2250690). The issue was resolved using hdapm (also described in the linked thread) to set the drive performance to maximum.
When I got my new (MBP6,2 late '10) MacBook Pro, I replaced the factory HDD with a 128GB SSD and the optical drive with the 640GB Western Digital HDD. As with my previous MBP, the drive heads were constantly trying to park; so I created a LaunchDaemon script to run hdapm on startup. hdapm takes the device number as an argument when setting the drive's performance level (e.g. "hdapm disk0 max"), so I checked which device numbers were assigned to my SSD and HDD, respectively, using "mount". Originally, "mount" showed the SSD as "disk0" and the HDD (using the SATA connection normally taken by the optical drive) as "disk1", so I set up the LaunchDaemon with "disk1" in the ProgramArguments list.
This trick worked perfectly until last night. I noticed the drive heads were trying to park again, so I checked the logs and saw that hdapm reported failure when attempting to set "disk1" to max performance. I then ran "mount" and, sure enough, it's now reporting the SSD as "disk1" and the HDD as "disk0". So why are the device numbers suddenly switched? And is there a way to prevent it from happening?

Hello Compuser84, let's get to the bottom of this together! The best way to swap devices on active phone numbers is online via My Verizon. You will first want to login as the account owner with your username and password. Have the device id's or ESN of both devices handy and follow these steps: http://vz.to/1jYPuCa If you are looking to cancel one of the number's, you would have to do so over the phone and give verbal consent. We can be reached at 800-922-0204.
WiltonA_VZW
VZW Support
Follow us on twitter @VZWSupport

Add tape device to non-global zone

Hi,
I have a SCSI attached Ultrium tape device attached and configured against the global zone.
The /dev/rmt/0* definitions in the global zone are links to ../../devices/pci@2*
I need to be able to use this tape device from the non-global zones.
To enable this, I have done the following:
zonecfg -z <zone name>
add device
set match=/dev/rmt/0
end
verify
commit
exit
I repeated the above for /dev/rmt/0m and /dev/rmt/0mn
Then I restarted the zone with the command:
zoneadm -z <zone name> reboot
After the reboot, I can see the device when using "mt -f /dev/rmt/0 status", but whenever I try to write a SAP brbackup to the new (initialised and not write protected) tape within the drive I get the following error:
BR0278E Command output of 'LANG=C cd /oracle/<SID>/sapbackup && /usr/sap/<SID>/SYS/exe/run/brtools -f detach LANG=C cpio -iuvB .tape
sh: /dev/rmt/0mn: cannot open
BR0280I BRBACKUP time stamp: 2012-04-04 08.21.41
BR0279E Return code from 'LANG=C cd /oracle/<SID>/sapbackup && /usr/sap/<SID>/SYS/exe/run/brtools -f detach LANG=C cpio -iuvB .tape.
BR0359E Restore of /oracle/<SID>/sapbackup/.tape.hdr0 from /dev/rmt/0mn failed due to previous errors
Have I created the device incorrectly, or does anyone have any ideas what could be the reason the write fails?
Any help appreciated.
Edited by: user11329299 on 04-Apr-2012 01:09

Hi,
Just to bring you up to speed, I have now fixed the issue.
The resolution was all within the iniSID.sap file that the backup is using. I have changed a number of parameters within this file:
1.     tape_copy_cmd = dd (was cpio)
2.     rewind = "mt     -f $ rew; sleep 30" (was " mt -f $ rew")
3.     rewind_offline = "mt -f $ offline; sleep 30" (was "mt -f $ offline")
4.     tape_pos_cmd = "mt -f $ fsf $: sleep 30" (was "mt -f $ fsf $")
5.     tape_size = 500G (was 18000M)
After making those changes, the backup started from within DB13. I believe that the main culprit was the tape_copy_cmd, but the others were changed to allow the tape drive time to become online again after any query.

Add device cdrom non global zone

Hi All ,
how to add device cdrom to non global zone ?
many thanks

Hi David,
Does your judgement that "you can definitely use a lofs mount to make /usr/local available inside the four zones" hold when /usr/local is an NFS mount in the global zone? James indicated that his /usr/local was an NFS mount, but I don't know if you targeted that specifically, or if you were just responding to the general case.
I have not had any success in performing lofs mounts of NFS mounts and making them visible in a local zone. I don't have any problems making a lofs mount of a NFS mount work in the global zone, I just can't NFS mount anything in the global zone and make it accessible in a local zone.
See http://www.opensolaris.org/jive/thread.jspa?threadID=2181&tstart=0 for a full description of what I tried and what happened. The short result is that when I try, accessing that directory in the local zone gives "I/O error" for file operations and "Not owner" for df.
Thanks,
Dab

Devices -- numbers in parentheses

In Finder, under Devices, it says John Smith's iMac G5 (2) or sometimes (3) or sometimes nothing. What are the numbers in parentheses? I get the queasy feeling that someone has gotten into my system and is using it for something nefarious. Thanks.

There are several possible causes for this behavior.
1. Two (or more) computers on the local network have the same Bonjour name, such as "X's-MacBook-Pro.local". Resolve the name conflict by renaming one or more of them in the Sharing preference pane.
2. You have two simultaneous connections to the same local network: probably Ethernet and Wi-Fi. If applicable, disconnect the Ethernet cable or turn off Wi-Fi.
3. A Mac wakes from sleep due to network traffic. This is a bug in OS X that may only affect some models. You can avoid it as follows:
Open the Energy Saver pane in System Preferences and unlock the settings, if necessary. Select the Power Adapter tab, if there is one. Uncheck the box marked
          Wake for Wi-Fi network access
if it's checked.
4. A device that gets its network address from the router wakes from sleep, and the address it was using before has been assigned to another device.
5. A third-party wireless router has incompatible settings or firmware. In that case, refer to the manufacturer or ISP for support. Restarting the router may help, temporarily.
6. If the router is an Apple device, it may need to be restarted.
7. A third-party Bonjour device on the network is malfunctioning. Finding out which is a process of elimination.
8. There is more than one DHCP server on the network. Typically, there would be two or more wireless access points configured to act as routers.
9. See this support article.
10. Back up all data. Make notes of your settings in the Network preference pane.
Triple-click the line below on this page to select it:
/Library/Preferences/SystemConfiguration
Right-click or control-click the highlighted line and select
          Services ▹ Reveal
from the contextual menu.* A folder should open with an item named "SystemConfiguration" selected. Move the selected item to the Trash. You may be prompted for your administrator password.
Restart the computer and empty the Trash. You will need to recreate the network settings.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select
          Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.

Changing device numbers

I have a tablet that the contract has run out. I want to swap the number it has with the number my phone has before I take the tablet off the account. What is the best way to accomplish this? Thanks.

Hello Compuser84, let's get to the bottom of this together! The best way to swap devices on active phone numbers is online via My Verizon. You will first want to login as the account owner with your username and password. Have the device id's or ESN of both devices handy and follow these steps: http://vz.to/1jYPuCa If you are looking to cancel one of the number's, you would have to do so over the phone and give verbal consent. We can be reached at 800-922-0204.
WiltonA_VZW
VZW Support
Follow us on twitter @VZWSupport

VLAN-tagged aggregates as physical device in exclusive-IP zone?

I have an aggregate defined in my global zone and using a VLAN#751-tagged device in the global:
bash-3.2# dladm show-aggr
key: 1 (0x0001) policy: L4      address: 0:c0:dd:c0:ff:ee (auto)
           device       address                 speed           duplex link    state
           qlge0        0:c0:dd:c0:ff:ee          10000 Mbps    full    up      attached
           qlge2        0:c0:dd:c0:ff:ed          10000 Mbps    full    up      attached
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
aggr751001: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
        inet XX.XX.XX.XX netmask ffffff00 broadcast XX.XX.XX.255
        ether 0:c0:dd:c0:ff:ee
bash-3.2#
May I use a different VLAN-tagged interface on aggr1 (say aggr771001) as a physical device in a zone?:
<zone name="my-zone" zonepath="/zoneroot/my-zone" autoboot="false" limitpriv="default" ip-type="exclusive">
<network address="" physical="aggr771001"/>
</zone>
TIA

I have an aggregate defined in my global zone and using a VLAN#751-tagged device in the global:
bash-3.2# dladm show-aggr
key: 1 (0x0001) policy: L4      address: 0:c0:dd:c0:ff:ee (auto)
           device       address                 speed           duplex link    state
           qlge0        0:c0:dd:c0:ff:ee          10000 Mbps    full    up      attached
           qlge2        0:c0:dd:c0:ff:ed          10000 Mbps    full    up      attached
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
aggr751001: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
        inet XX.XX.XX.XX netmask ffffff00 broadcast XX.XX.XX.255
        ether 0:c0:dd:c0:ff:ee
bash-3.2#
May I use a different VLAN-tagged interface on aggr1 (say aggr771001) as a physical device in a zone?:
<zone name="my-zone" zonepath="/zoneroot/my-zone" autoboot="false" limitpriv="default" ip-type="exclusive">
<network address="" physical="aggr771001"/>
</zone>
TIA

How do I enter the device numbers/channels in my vi?

(also posted this in PXI forum)
I have a PXI 1010 chassis with a 6040E in the #8 slot controlling an SCXI-1100 in the first slot of the SCXI section. This system ran flawlessly for 3 years. I recently upgraded the controller module to a 8176 running Windows 2000. All of the components show up in MAX, I can verify them, and I can run the test panels for the 6040E and look at the SCXI channels using the SXCI channel string sc1!md1!0, etc. In MAX, the 6040E is listed as device 9.
However, when I run my vi program, the same one I've been using for years, I am getting the error -10401. This error is occuring in AIConfig. I've narrowed the problem down to either the channel string or the device number. If I change
the device number in the VI to 9, like it is stated in MAX, I get error -10403. Any other device number gives error-10401. I am also using the traditional SCXI channel string sc1!md1!X:Y in the VI, same as I always have.
Can anyone provide some insight on what my device number and channel string should be for the VI, or a troubleshooting strategy? I am stumped.
-Sue K.

I do not know if the following suggestion will work. I can only try to help you troubleshoot this "unknown" device error. I had a similar (not identical) problem with AI config after I swapped out a DAQ card in the 1010 chassis - though MAX indicated (and verified) the new device, I could not run the new Device ID.
So here goes my best guess...
1) Get into MAX, choose the 6040E, and change the Device ID to some other number. Select apply.
2) Exit MAX
3) Now try the VI with the new Device ID.
For some reason, when I changed the Device ID to some other number, everything seemed to work fine. I can not explain why. Perhaps changes to MAX are only applied after MAX is closed and LabVIEW is launched. I try not to have labVIEW and MAX operating at the same time.

PCI device numbering whine

Anyone else use PCI expansion slots for their hard drives? I have a hard drive (IDE) connected through a PCI card. My primary hard drive is also IDE and connected straight into the motherboard. I have another IDE storage drive.
Back in my Ubuntu days, my PCI data drive and normal storage drive would (literally) swap every few reboots, which was quite annoying. After coming to Arch, I noticed that my PCI drive was consistantly sda, primary hdd was sdb, and storage drive was sdc. Always, which was nice. I thought it must've been some Ubuntu/Debian-specific patch that was causing my trouble.
I got a bit of a blast from the past today after I upgraded to kernel 2.6.25. Upon reboot, I got a kernel panic because my root file sytem wasn't found. I thought it'd been a faulty install (for other reasons) and lamented my multiple re-installation of the kernel, which changed my fallback image. So I booted my laptop, plugged my primary hdd in via USB, and used pacman to install the kernel (with --root) to the drive. I plugged it back into my desktop, but got nothing.
Frustrated, I started searching the forums, then, had a flashback. On a hunch, I rebooted and changed my Grub entry to pass the parameter root=/dev/sda2 instead of /dev/sdb2. Here I am.
Reminds me of the old joke...
Being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed.

Realtek Card Reader:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=15&PFid=25&Level=4&Conn=3&DownT...
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

Add pseudo device in zones

How can one add a pseudo device to a zone? We have a
pseudo device which serves as an application entry to a kernel module. It does ioctl's to the kernel module.
When I create the device in the global zone and then do an
add device
set match=/dev/rxp
end
in the zone configuration and then
configure the zone with zonecfg, it does not complain.
But when I check the /dev directory in the zone for the /dev/rxp, I do not see it. The documentation specifies that the zone configuration
will create some pseudo devices, /dev/null, /dev/zero and others.
If the answer is that the configuration does not let you add
pseudo devices today, then when will it?
thank you.
jim

Although I'm not positive in this I do think it may be a while before something like this will be implemented. After all; the primary task of a non-global zone is security by shielding it off from the main zone and thus seperating several resources.
However; do note that your /dev directory in the global zone is not fully shared with the one of the non-global zone. It has its own seperate dev directory which can be found in the same directory as the zone's rootpath. You may give it a try in there, but personally I have some serious doubts to the success of this approach.

Shared disk devices across zones/containers

Hi there,
To add a disk device to a zone i think that i can do this:
Add a device.
zonecfg:my-zone> add device
Set the device match, /dev/dsk/c1t0d0* in this procedure.
zonecfg:my-zone:device> set match=/dev/dsk/c1t0d0*
End the device specification.
zonecfg:my-zone:device> end
Could i then create another zone and add the same disk device?
I am thinking about installing 10g RAC across two zones for dev/training purposes.
Thanks
Dermot

Dermot,
There is a special forum for Solaris 10 Zones.
If you launch this question there, David Comay might answer you.
... Eric

Rempa device numbers in a zone?

Similar Messages

Maybe you are looking for