Autonomous APs' non-root radio tracking Questions
Hi guys,
As you know, we can configure an autonomous AP that is using its .11a radio as "non-root bridge" and its .11b/g as root to track the .11a radio so that if it is down for any reason, then it will shut down the Root Radio. I've some questions about this if someone tested the below scenarios:
(1) If the .11b/g radio has been shut down, will it stay shutdown and never comeback unless an administrator do it manually? Is there an automated feature like the switches 'errdisable recover cause' method?
(2) Is there a command like 'show fallback bla bla ..' that will allow us to see that the current radio state has been shut down due to radio tracking?
B.Regards
Mahmoud
Yes, these model you can configure as Root/Non-Root as long as you have an autonomous image loaded. Most of the time feature is depend on the software code.
Release notes available at below URL for details of the supported/unsupported features of each software version.
http://www.cisco.com/en/US/products/ps12555/prod_release_notes_list.html
Here is one basic config example of Root/Non-Root using different AP model, but it may help you to get basic config done for these AP model as well.
http://mrncciew.com/2013/11/09/wireless-bridge-with-eap-fast/
HTH
Rasika
**** Pls rate all useful responses ****
Similar Messages
-
Can a wireless router (station role non-root) associate to 2 APs ?
can a wireless router (as station role non-root) associate to 2 simultaneous APs ?
say something like this on an 18xx router:
dot11 ssid firstAP
dot11 ssid secondAP
interface Dot11Radio0/1/1
ssid firstAP
ssid secondAP
what I want is something like two virtual-radios/VLANs/whatever with two independent outside routes; say:
ip address dhcp for ssid firstAP
ip address dhcp for ssid secondAP
where firstAP is my AP and secondAP is a near free hot-spot AP (authentication open)Nice idea but unfortunatelty it won't work. You can only associate one radio to a single infrastructure device at any one time.
-
Clients no received ip address from Non-root APs
I have 3 AP, one roor and Non-root. The Root AP is connected to ADSL modem which provide DHCP.
the clients form root AP received IP without problem, but whe I try to associate to non-root AP I can not receive ip from DHCP.
What it could be the reason???
I hope any of you can help me...
regards
ROOT#sh cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
NON-ROOT1 Vi-Dot11 0 177 T I AIR-AP124 Vi-Dot11 0
NON-ROOT2 Vi-Dot11 1 145 T I AIR-AP124 Vi-Dot11 0
ROOT#
ROOT#
ROOT#sh dot11 associations
802.11 Client Stations on Dot11Radio0:
SSID [enlace] :
MAC Address IP address Device Name Parent Stat
e
0021.00d6.6459 169.254.32.107 Br-client - 003a.9924.2ba0 Asso
c
0025.9cab.3073 0.0.0.0 Br-client - 003a.9933.e070 Asso
c
003a.9924.2ba0 192.168.1.249 bridge NON-ROOT2 self Asso
c
003a.9933.e070 192.168.1.251 bridge NON-ROOT1 self Asso
c
58b0.3568.372c 169.254.68.25 Br-client - 003a.9924.2ba0 Asso
c
c417.fe02.645f 192.168.1.64 Br-client - 003a.9924.2ba0 Asso
c
d8a2.5e49.5a83 0.0.0.0 Br-client - 003a.9924.2ba0 Asso
c
ROOT#
ROOT#sh ver
Cisco IOS Software, C1240 Software (C1240-K9W7-M), Version 12.4(21a)JA1, RELEASE
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 16-Sep-09 19:06 by prod_rel_teamHi Surendra,
I set static IP on interface BVI1 on non-root1 and non-root2, also root-bridge I can ping to both of them, in fact I access to them via web and telnet.
I also set ip helper-address on interface Dot11Radio0 in all APs root and non-root..
My mind is about to crash...I don´t know what else to try.
thanks for your time. -
Greetings,
I have a small network that uses 1242 APs for clients machines. Our wired WAN link can be unreliable, so I would like to configure one of the 1242s as a bridge and connect it to one of the many wireless networks we have in our neighborhood.
I understand the 1242 APs can also operate in a bridge mode that could allow us to connect our network to one of these other wireless LANs. A couple of questions:
-Does the remote WLAN have to be a compatible cisco device in order for the 1242 to be able to bridge successfully?
-Which 'Role in Radio Network' do I choose for our 1242?
-How do I see what the SSIDs of the remote WLANS are and enter the relevant passwords (WEP, WPA, 802.1x, or WPA2)
-If this is not possible, what is the right device to use to connect our LAN to a remote WLAN without being able to control the hardware at 'both' ends of the bridge.
TIACan you please provide me with a network topology of what it is you would like to achieve. If you want the radio interfaces to associate to one another, then it is recommended to have them on the same channel, but for roaming instances, it is recommended that you have then at least 5 channels apart on the g radio so as to avoid any interference.
The 802.11A radios on the APs would be configured as bridges (one as
a "root" and the other two as "non-root") and the 802.11G radios
would service clients. Only one of the APs would require wired
connectivity in this scenario, as long as all of the APs are
communicating to each other on the 802.11A side. An important
consideration is that the 802.11A radios that are configured as "non-
root bridges" need only to communicate with the 802.11A radio that is
configured as the "root bridge". It is not necessary for the "non-
root bridges" to see each other. However, it is imperative that the
802.11A radio that is configured as the "root bridge" be able to
communicate with BOTH of the 802.11A "non-root" bridges. Therefore,
the antennas you choose for the devices is important. -
JTREE: Custom TreeModel does not update non-root nodes
I have a JTree that uses a custom TreeModel that wraps over (delegates to) a data class X which keeps track of all its children. The class X maintains its own data structure internally (references to other data objects). It also implements 'equals' and 'hashcode' methods. When the data changes in X, it invokes fireTreeStructureChanged on the TreeModel. (There is a TreeModelListener registered with the TreeModel). This works very well for the root node but not for the other non-root nodes. The JTree correctly calls 'equals' and I can see that equals returns 'false' but for non-root nodes the JTree does not refresh though I can see the underlying data structure has changed.
I am wondering if I may not have fully & correctly implemented fireTreeStructureChanged as it doesn't seem to do much. Or I may be looking at the wrong place. Any pointers would be appreciated.
BTW, this question is very similar to one asked years earlier http://forums.sun.com/thread.jspa?threadID=153854 but it didn't help me :(
Thanks.
ps: working with jdk1.6.0_06 on WinXP.I have a same problem. I got an error "Cannot Update Libray".
-
Non-root AP associates itself?
Hi,
I have three AP , one Root and two non-root. I notice something weird when I type command "sh dot11 associations" on Non-root APs.
If I type "sh dot11 associations" on NON-ROOT1 AP there is a lines that shows a client with the name NON-ROOT1 as a client associated, sometimes the line dissapeared but when I type " sh dot11 associations" on NON-ROOT2 AP a similar line is shown ; theres is a line that shows a client with the name NON-ROOT2
What could it be the reason???
NON-ROOT1#sh dot11 associations
802.11 Client Stations on Dot11Radio0:
SSID [enlace] :
MAC Address IP address Device Name Parent State
0018.de16.8d12 192.168.1.221 ccx-client NON-ROOT1 self Assoc
0023.4e6c.ec11 192.168.1.72 ccx-client casa self Assoc
0025.9cab.3073 192.168.1.70 ccx-client - self Assoc
0027.0c6b.7290 192.168.1.250 11g-bridge ROOT - Assoc
60fb.4242.aec1 192.168.1.79 unknown - self Assoc
c42c.0352.fbbb 192.168.1.71 unknown - self Assoc
NON-ROOT1#
Regards,Hi ,
I have few question for you
Are both the Non root associated to the same root bridge ?
Is it possible that one of the Non root is associated to another non root which is running in Non root bridge with clients mode ?
Can you verify the Mac and IP address of the Non root bridge and check if they are the same ?
Regards ,
Sharath K.P. -
1250 802.11N series in root/non-root bridge mode
Using Yagi's, low loss cable, antenna outside, AP inside.
When operating autonomous 1250 series in root/non-root bridge mode, can I use 802.11N radios? Is it supported?
Or would it be better to use 1242's? This is for a customer, no time for testing, need rock solid design, in and out configuration...@leolaohoo -
I was just asking for a definitive answer, weather its affirmative or negative, is there a benefit to using the 1252 over the 1242 giving the cost of each, since as you said the 802.11N can not be used to bridge, than I would say a 1242 is better fit for the AP bridge of 350', clear line of site over the 1252. -
SAP 1602 Wireless bridge issue. Non root bridge loses it's configuration
Hi guys,
Today I tried to configure wireless link between two autonomous AP 1602 APs.
There is a problem with Non-root bridge. I configured it with this command:
AP2(config-if)#station-role non-root wireless-clients
Non-root bridge successfully joins the root bridge (root AP). Anyway, this configuration does not work, if I reload my non-root bridge. Even without reload, If I check my non-root bridge configuration it looks like this:
interface Dot11Radio1
no ip address
no ip route-cache
encryption vlan 1 mode ciphers aes-ccm
ssid WiFi-Bridge
antenna gain 0
stbc
beamform ofdm
Command "station-role non-root wireless-clients" is missing here. But I just configured it few seconds ago... Does anyone know, where could be a problem?Okay... Everything works with OPEN ssid. Not with my WPA 2 configuration.
On both APs configuration looks like this:
dot11 ssid Private
vlan 10
authentication open
authentication key-management wpa version 2
guest-mode
wpa-psk ascii 7 01100F175804575D72
interface Dot11Radio0
encryption vlan 10 mode ciphers aes-ccm
ssid Private
infrastructure-client ( on Root AP)
station-role root bridge wireless-clients ( on Root AP)
Few debugs:
*Mar 2 09:57:30.554: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]
*Mar 2 09:57:30.938: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675
*Mar 2 09:57:30.938: dot11_auth_client_abort: No client entry to abort: 9c02.986d.9675 for application 0x1
*Mar 2 09:57:30.938: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675 Reason: Sending station has left the BSS
*Mar 2 09:57:30.986: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]
*Mar 2 09:57:31.350: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675
*Mar 2 09:57:31.350: dot11_auth_client_abort: No client entry to abort: 9c02.986d.9675 for application 0x1
*Mar 2 09:57:31.350: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675 Reason: Sending station has left the BSS
*Mar 2 09:57:31.398: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]
*Mar 2 09:57:31.766: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675
Everything works with android device and WPA2 if I change configuration to this:
dot11 ssid Private
vlan 10
authentication open
authentication key-management wpa version 2
mbssid guest-mode
wpa-psk ascii 7 01100F175804575D72
interface Dot11Radio0
encryption vlan 10 mode ciphers aes-ccm
ssid Private
station-role root
mbssid -
Hi Everyone,
I am setting up pair of 1242 APs as Root and Non-Root bridge, i am not able to find the Install Mode on the 1242 AP while setting the Non Root for Best signal.
any help will be appreciated.
HMHi HM,
AFAIK, we do not have the INSATALL mode on the 1242 AP if we are using it as ROOT and NONROOT.. this is available only on 1310 bridge or 1410 bridges.. not on 1242AP..
lemme know if this answered your question..
Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull -
Non root user can delete root files, bug?
We're having an odd permissions based problem on Solaris 10 u5 x86_64, (new install, fully patched as of 2 days ago) It means that non root users can delete root owned files, which is something I've never seen before, and I've been doing this for almost 10 years.
We're installing into an 80Gb container on VMware ESX server 3.0.1. The OS takes 20Gb (2 processors, 4Gb memory, 8Gb swap) most of the remaining 60Gb is being used as both file systems and raw devices under disksuite as soft partitions. It's one of the file systems, /apps (where we plan to install sybase) that is giving us "issues"
Essentially:
# more /etc/vfstab |grep apps
/dev/md/dsk/d0 /dev/md/rdsk/d0 /apps ufs 2 yes -
# newfs -v /dev/md/rdsk/d0
/dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
newfs: /dev/md/rdsk/d0 last mounted as /apps
newfs: construct a new file system /dev/md/rdsk/d0: (y/n)? y
mkfs -F ufs /dev/md/rdsk/d0 20971520 -1 -1 8192 1024 264 1 546 8192 t 0 -1 8 7 n
/dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
Warning: 4096 sector(s) in last cylinder unallocated
/dev/md/rdsk/d0: 20971520 sectors in 3414 cylinders of 48 tracks, 128 sectors
10240.0MB in 214 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
20055584, 20154016, 20252448, 20350880, 20449312, 20547744, 20646176,
20744608, 20843040, 20941472
# mount /apps
# ls -al /apps
total 20
drwxr-xr-x 3 root root 512 Sep 10 12:31 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
drwx------ 2 root root 8192 Sep 10 12:31 lost+found
# su - sybase
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
sol10% cd /apps
sol10% rm *
rm: lost+found is a directory
sol10% rm -rf *
rm: cannot read directory lost+found: Permission denied
sol10% ls -al
total 20
drwxr-xr-x 3 root root 512 Sep 10 12:31 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
drwx------ 2 root root 8192 Sep 10 12:31 lost+found
sol10% exit
sol10% logout
# chgrp sybase /apps
# chmod g+w /apps
# ls -ald /apps
drwxrwxr-x 3 root sybase 512 Sep 10 12:31 /apps
# ls -al /apps
total 20
drwxrwxr-x 3 root sybase 512 Sep 10 12:31 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
drwx------ 2 root root 8192 Sep 10 12:31 lost+found
# su - sybase
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
sol10% cd /apps
sol10% rm -rf *
sol10% ls -al
total 4
drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
sol10% id
uid=***(sybase) gid=***(sybase)
sol10% exit
sol10% logout
# pwd
# ls -ald /apps
drwxrwxr-x 2 root sybase 512 Sep 10 12:34 /apps
# ls -al /apps
total 4
drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
It's a new "bare metal" (in as much as there is no metal) install. I created the sybase user from scratch by hand editing passwd, group and shadow, buy copying and pasting the data out of the NIS maps. All I've done besides the install & patch is setup networking manually, and created the metadb's and the soft partitions and the mount points & newfs'ed & mounted three of them . I then changed ownership of /apps to be sybase:sybase, and handed it to the database team for the sybase install. they came back and said "should we be able to do this?" as they habitually run rm rf * knowing they can't delete root owned files, only now they can... This is true even if I just chgrp the directory and give them group write permissions. They can still delete anything owned by root, even if it doesn't have group permissions just like the lost+found directory. No other "real" machine we have, x86 or SPARC does this, but we've never installed u5 before either.
As you can imagine losing the lost+found directory is a bit of a problem, however what's really worrying me is if they can do that, what happens when they run sybase as the sybase user? If it borks can they trash the OS and write/overwrite random files?
It's a VM, so in as much that's not a problem, but the reason it's a VM is somebody wants to send a VM to a client as a demo, and at present it's highly unstable IMO.
Does anyone have any idea where to start? My thoughts are that it may be a VMware issue, (though the hardware and the guest OS is supported) it could be a bug, because I've never seen that weird newfs error before, and then I found this:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6622243
Or it could be me, and the fact that I'm hand configuring it, and u5 now requires I do it "properly" with useradd, etc. I'd like to test, but the guy wants it built, and wants it now, so I patched it up, and gave it back to the database team and told them to be careful.
I'd be interested in you opinions regardless.
The full spec of the "machine" is below, sol10 is not it's name for obvious reasons, and I've hashed out the ID & GIUD for similar reasons.
# uname -a
SunOS sol10 5.10 Generic_127128-11 i86pc i386 i86pc
# prtdiag
System Configuration: VMware, Inc. VMware Virtual Platform
BIOS Configuration: Phoenix Technologies LTD 6.00 09/06/2007
==== Processor Sockets ====================================
Version Location Tag
Pentium(R) Pro CPU socket #0
Pentium(R) Pro CPU socket #1
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
DRAM in use 0 RAM slot #0 RAM slot #0
DRAM in use 0 RAM slot #1 RAM slot #1
DRAM in use 0 RAM slot #2 RAM slot #2
DRAM in use 0 RAM slot #3 RAM slot #3
==== On-Board Devices =====================================
VMware SVGA II
ES1371
==== Upgradeable Slots ====================================
ID Status Type Description
0 unknown ISA ISA Slot J8
0 unknown ISA ISA Slot J9
0 unknown ISA ISA Slot J10
1 in use PCI PCI Slot J11
2 in use PCI PCI Slot J12
3 in use PCI PCI Slot J13
4 available PCI PCI Slot J14
# dmesg
Wednesday, 10 September 2008 15:33:35 BST
Sep 10 10:17:44 sol10 busra: [ID 490441 kern.info] NOTICE: ndi_ra_free: bad free, dip ffffffff803807a8, resource type memory
Sep 10 10:17:44 sol10 busra: [ID 883242 kern.info] NOTICE: ndi_ra_free: freeing base 0xe0000, len 0x4000 overlaps with existing resource base 0x0, len 0xf4000000
Sep 10 10:17:44 sol10 rootnex: [ID 349649 kern.info] pci0 at root: space 0 offset 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] pci0 is /pci@0,0
Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
Sep 10 10:17:44 sol10 Rev. 1 LSI, Inc. 1030 found.
Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci1000,30 (mpt) instance 0 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 0
Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
Sep 10 10:17:44 sol10 mpt0 Firmware version v0.0.0.0 (?)
Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
Sep 10 10:17:44 sol10 mpt0: IOC Operational.
Sep 10 10:17:44 sol10 pci: [ID 370704 kern.info] PCI-device: pci1000,30@10, mpt0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mpt0 is /pci@0,0/pci1000,30@10
Sep 10 10:17:44 sol10 scsi: [ID 193665 kern.info] sd0 at mpt0: target 0 lun 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] sd0 is /pci@0,0/pci1000,30@10/sd@0,0
Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /pci@0,0/pci1000,30@10/sd@0,0 (sd0) online
Sep 10 10:17:44 sol10 unix: [ID 190185 kern.info] SMBIOS v2.31 loaded (1695 bytes)
Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /cpus (cpunex0) online
Sep 10 10:17:44 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dld0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] dld0 is /pseudo/dld@0
Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: i8042 (i8042) instance 0 vector 0x1 ioapic 0x2 intin 0x1 is bound to cpu 1
Sep 10 10:17:44 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: i8042 (i8042) instance #0 vector 0xc ioapic 0x2 intin 0xc is bound to cpu 1
Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: keyboard@0, kb8042 # 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] kb80420 is /isa/i8042@1,60/keyboard@0
Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: mouse@1, mouse8042 # 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mouse80420 is /isa/i8042@1,60/mouse@1
Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
Sep 10 10:17:47 sol10 unix: [ID 557827 kern.info] cpu1 initialization complete - online
Sep 10 10:17:47 sol10 rootnex: [ID 349649 kern.info] iscsi0 at root
Sep 10 10:17:47 sol10 genunix: [ID 936769 kern.info] iscsi0 is /iscsi
Sep 10 10:17:52 sol10 genunix: [ID 454863 kern.info] dump on /dev/dsk/c1t0d0s1 size 8197 MB
Sep 10 10:17:53 sol10 pci: [ID 370704 kern.info] PCI-device: pci8086,7191@1, pci_pci0
Sep 10 10:17:53 sol10 genunix: [ID 936769 kern.info] pci_pci0 is /pci@0,0/pci8086,7191@1
Sep 10 10:17:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
Sep 10 10:17:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
Sep 10 10:17:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
Sep 10 10:17:54 sol10 pseudo: [ID 129642 kern.info] pseudo-device: zfs0
Sep 10 10:17:54 sol10 genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs@0
Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: power0
Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] power0 is /pseudo/power@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Sep 10 10:17:56 sol10 rootnex: [ID 349649 kern.info] xsvc0 at root
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] xsvc0 is /xsvc
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex@1
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
Sep 10 10:17:56 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 1
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 0
Sep 10 10:17:56 sol10 genunix: [ID 640982 kern.info] ATAPI device at targ 0, lun 0 lastlun 0x0
Sep 10 10:17:56 sol10 genunix: [ID 846691 kern.info] model VMware Virtual IDE CDROM Drive
Sep 10 10:17:56 sol10 genunix: [ID 479077 kern.info] ATA/ATAPI-4 supported, majver 0x1e minver 0x17
Sep 10 10:17:56 sol10 pci: [ID 370704 kern.info] PCI-device: ide@0, ata0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ata0 is /pci@0,0/pci-ide@7,1/ide@0
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 scsi: [ID 193665 kern.info] sd1 at ata0: target 0 lun 0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] sd1 is /pci@0,0/pci-ide@7,1/ide@0/sd@0,0
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: fdc (fdc) instance 0 vector 0x6 ioapic 0x2 intin 0x6 is bound to cpu 1
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: fdc0
Sep 10 10:17:56 sol10 fdc: [ID 114370 kern.info] fd0 at fdc0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] fd0 is /isa/fdc@1,3f0/fd@0,0
Sep 10 10:17:56 sol10 genunix: [ID 314293 kern.info] device pciclass,030000@f(display#0) keeps up device sd@0,0(sd#1), but the latter is not power managed
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dtrace0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: vol0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pool0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] pool0 is /pseudo/pool@0
Sep 10 10:17:57 sol10 ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running.
Sep 10 10:18:05 sol10 nfs4cbd[395]: [ID 867284 daemon.notice] nfsv4 cannot determine local hostname binding for transport tcp - delegations will not be available on this transport
Sep 10 10:18:10 sol10 sendmail[598]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
Sep 10 10:18:10 sol10 sendmail[600]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
Sep 10 10:18:17 sol10 mac: [ID 736570 kern.info] NOTICE: e1000g0 unregistered
Sep 10 10:19:10 sol10 sendmail[598]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
Sep 10 10:19:10 sol10 sendmail[600]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
Sep 10 10:20:10 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Sep 10 10:20:10 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Sep 10 10:24:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
Sep 10 10:24:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
Sep 10 10:24:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
Sep 10 10:24:59 sol10 e1000g: [ID 801725 kern.info] NOTICE: pci8086,100f - e1000g[0] : Adapter 1000Mbps full duplex copper link is up.
Sep 10 10:28:21 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
Sep 10 10:35:17 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 11:28:55 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 12:28:56 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 13:29:01 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 14:29:10 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 15:29:38 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
# prtconf
System Configuration: Sun Microsystems i86pc
Memory size: 4132 Megabytes
System Peripherals (Software Nodes):
i86pc
scsi_vhci, instance #0
isa, instance #0
i8042, instance #0
keyboard, instance #0
mouse, instance #0
lp, instance #0
asy, instance #0
asy, instance #1
fdc, instance #0
fd, instance #0
pci, instance #0
pci15ad,1976 (driver not attached)
pci8086,7191, instance #0
pci15ad,1976 (driver not attached)
pci-ide, instance #0
ide, instance #0
sd, instance #1
ide (driver not attached)
pci15ad,1976 (driver not attached)
display, instance #0
pci1000,30, instance #0
sd, instance #0
pci15ad,750, instance #0
iscsi, instance #0
pseudo, instance #0
options, instance #0
agpgart, instance #0
xsvc, instance #0
objmgr, instance #0
acpi (driver not attached)
used-resources (driver not attached)
cpus, instance #0
cpu (driver not attached)
cpu (driver not attached)
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 10440 alt 2 hd 255 sec 63>
/pci@0,0/pci1000,30@10/sd@0,0
Specify disk (enter its number): 0
selecting c1t0d0
[disk formatted]
Warning: Current Disk has mounted partitions.
/dev/dsk/c1t0d0s0 is currently mounted on /. Please see umount(1M).
/dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M).
/dev/dsk/c1t0d0s3 is currently mounted on /usr. Please see umount(1M).
/dev/dsk/c1t0d0s4 is currently mounted on /var. Please see umount(1M).
/dev/dsk/c1t0d0s5 is currently mounted on /opt. Please see umount(1M).
/dev/dsk/c1t0d0s6 is part of SVM volume sp:d8. Please see metaclear(1M).
/dev/dsk/c1t0d0s7 contains an SVM mdb. Please see metadb(1M).
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> p
Current partition table (original):
Total disk cylinders available: 10440 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 131 1.00GB (131/0/0) 2104515
1 swap wu 132 - 1176 8.01GB (1045/0/0) 16787925
2 backup wm 0 - 10439 79.97GB (10440/0/0) 167718600
3 usr wm 1177 - 1829 5.00GB (653/0/0) 10490445
4 var wm 1830 - 2091 2.01GB (262/0/0) 4209030
5 unassigned wm 2092 - 2614 4.01GB (523/0/0) 8401995
6 unassigned wm 2617 - 10439 59.93GB (7823/0/0) 125676495
7 unassigned wm 2615 - 2616 15.69MB (2/0/0) 32130
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0
partition> quit
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> q
# metastat -p
d8 -p c1t0d0s6 -o 109973513 -b 61440
d7 -p c1t0d0s6 -o 109461512 -b 512000
d6 -p c1t0d0s6 -o 109051911 -b 409600
d5 -p c1t0d0s6 -o 88080390 -b 20971520
d4 -p c1t0d0s6 -o 67108869 -b 20971520
d3 -p c1t0d0s6 -o 46137348 -b 20971520
d2 -p c1t0d0s6 -o 41943043 -b 4194304
d1 -p c1t0d0s6 -o 20971522 -b 20971520
d0 -p c1t0d0s6 -o 1 -b 20971520An easy way to think of it is this -- everything in Unix is a file. Including directories; they are just a file which contains a list of the files in that directory, and pointers to them.
If the 'sybase' user has write permission on the directory, they have permission to edit that "list", and can add or remove files to the list. It doesn't matter who the files on the list belong to, because the files are not what is being modified. Only the list of files is being modified. (Of course, in Unix, if you erase the file's listing from all of the lists it's on, the file itself goes away for housekeeping purposes.)
One thing that would have stopped the 'sybase' user from removing the lost+found directory is if that directory itself had files in it -- without write permission to the lost+found directory, that user could not have removed those files, and since one cannot remove a non-empty directory, that operation would have failed. Since lost+found was empty in this case, it could be removed simply by having permission to write to the /apps directory.
This behavior does change if you set the sticky bit on the directory -- in that case, files may only be removed by the owner of the file or directory, or if the user has write permission to the file. This would have prevented the sybase user from removing the lost+found directory. (Note, this also applies to the 'rename' function call.) This would probably be the best way to handle your situation, since you apparently do want the sybase user to be able to add files to /apps, but do not want them to be able to remove lost+found.
Edited by: MadBishop on Sep 12, 2008 7:46 AM -
Pretty gtk2 as root, ugly as non-root? [/SOLVED]
Heh, this is actually a little bit interesting. I've never ran anything that requires X as root until just a few minutes ago and realized that running applications such as pidgin and firefox as root, they are significantly prettier than what it looks like when I run it as non-root, even with the same gtk2 theme as you can see in the picture above. Oh, by the way, can you guys which one is my non-root and root running the above? The left is as non-root and the right is as root. See? A lot prettier... And I always questioned why Firefox was so damn ugly on Linux. It looks like it is suppose to as root.
Anyhow, I am curious on either what my non-root account is lacking (I think it is lacking the ability to read certain files), how could I configure it to look like what it does on root, or so on whatever the deal is. To me, this is just crazy. Heh, I am not saying how it looks is totally important, I've always been a fan of usability which is why I use dwm and stuff, but this is just crazy to me, lol, crazy...
Yeap.. So any ideas what I am doing wrong, missing, so on, lalala?
Edit: Blah, I feel like a fool. I played around with it more and realized it was clearlooks on root. My bad my bad my bad. :\ Well, at least y'all know what theme I'll be using. 8D
Last edited by Aprz (2009-04-20 11:35:42)how are you selecting the gtk theme as non-root? also, which DE/wm are you using?
Last edited by fuscia (2009-04-20 13:41:49) -
1300 Root-Bridge and Non-Root Bridge setup
I have two 1300s that I am trying to set up as Root Bridge and Non-Root Bridge, however, everytime i specify one of them as a Non-Root bridge, the radio0 interface becomes disabled. The only option that i am able to pick that enables the radio0 interface is "Access Point", which is what am trying to avoid it being.
Can anybody help me figure out how to go about thisA non-root's radio will show as disabled if it cannot find the root AP to associate to. Make sure you have "infrastructure-ssid" configured under the SSID on both the root and non-root bridges. Also depending on code versions you may have to configure the distance command under the radio interface on the root.
-
7920 associates to root bridge but not to non-root bridge
I have 7920s using open authentication with WEP128 cipher. I have two 1300 root AP's (with client support) and three non-root AP's (also client support) in the same lab area. The root AP's and non-Root AP's associate and link to each other no problem. However, the 7920's will only associate with the Root APs. If I power down the root APs, the 7920s show "no AP found". I've verified SSID and WEP128 keys. I've also noted that the root AP does have a channel specified under dot11radio0 but the non-roots do not. Do the 7920's just scan for any channel until it finds an association or do I need to specify a channel in the non-root bridges?
Thanks,
Mike.With static WEP, the authentication is happening at the AP level. Will want to ensure non-root is associated to a root though otherwise the interface may be in "reset" state.
The 7920 will look at these 2 as individual APs regardless of channel. Non-roots should have the same channel as the root, otherwise will not be able to communicate. -
How to create a domain for a non-root user using the JES installer
Some questions have been circulating on what are the steps to create a whole domain configuration using a non-root user. Here is one method that you can try....
- Login as user "testuser", all operations are using the user I want to start the whole domain with
- cd to the testuser home directory and created apptest (mkdir apptest)
-created domain
/opt/SUNWappserver/appserver/bin/asadmin create-domain adminuser admin adminport 4849 --domaindir /testuser/apptest testdomain
Please enter adminpassword>adminadmin
Please enter adminpassword again>adminadmin
Please enter the master password>adminadmin
Please enter the master password again>adminadmin
- created nodeagent
/opt/SUNWappserver/appserver/bin/asadmin create-node-agent user admin port 4849 password adminadmin agentdir /testuser/apptest testnode
Please enter the master password>adminadmin
- Start the domain
/opt/SUNWappserver/appserver/bin/asadmin start-domain domaindir /testuser/apptest user admin testdomain
Please enter password>adminadmin
Please enter the master password>adminadmin
Domain testdomain started.
- Start the nodeagent
/opt/SUNWappserver/appserver/bin/asadmin start-node-agent user admin agentdir /testuser/apptest/ testnode
Please enter password>adminadmin
Please enter the master password>adminadmin
Command start-node-agent executed successfully.
- create instance
/opt/SUNWappserver/appserver/bin/asadmin create-instance nodeagent testnode user admin i1
Please enter password>adminadmin
Command create-instance executed successfully.
- start instance
/opt/SUNWappserver/appserver/bin/asadmin start-instance --user admin i1
Please enter password>adminadmin
Command start-instance executed successfully.And this can be used to the incident priority (same technique can be used for problems):
private int GetIncidentPriority(EnterpriseManagementGroup emg)
try
//Get the incident settings class
ManagementPackClass mpc = emg.EntityTypes.GetClass(new Guid("613c9f3e-9b94-1fef-4088-16c33bfd0be1"));
//Get the emo for the incident settings
EnterpriseManagementObject emo = emg.EntityObjects.GetObject<EnterpriseManagementObject>(mpc.Id, ObjectQueryOptions.Default);
//Get the priority maxtrix and convert to XML
if (emo[mpc, "PriorityMatrix"].Value != null && emo[mpc, "PriorityMatrix"].Value.ToString() != "")
string sMatrixXML = emo[mpc, "PriorityMatrix"].Value.ToString();
XmlDocument xmlDoc = new XmlDocument();
xmlDoc.LoadXml(sMatrixXML);
//Get the guid strings for impact and urgency (note - xml goes by urgency then impact)
string sUrgencyGuid = "04b28bfb-8898-9af3-009b-979e58837852";
string sImpactGuid = "11756265-f18e-e090-eed2-3aa923a4c872";
foreach (XmlNode urgencynode in xmlDoc.ChildNodes[0].ChildNodes)
if (urgencynode.Attributes.Count == 1 && urgencynode.Attributes["Id"].Value.ToString().ToLower() == sUrgencyGuid)
foreach (XmlNode impactnode in urgencynode.ChildNodes)
if (impactnode.Attributes.Count == 1 && impactnode.Attributes["Id"].Value.ToString().ToLower() == sImpactGuid)
XmlNode prioritynode = impactnode.ChildNodes[0];
return Convert.ToInt32(prioritynode.InnerXml);
return 0;
catch
return 0;
Rob Ford scsmnz.net
Cireson www.cireson.com
For a free SCSM 2012 Notify Analyst app click
here -
Can one Root Bridge support multiple non-root bridges?
Hey gang,
I have a pretty simple question here I think
I have a wireless bridge currently setup to support a separate office building on our property about 200 yards away from the main building. The wireless bridge has been working great and was a much cheaper solution when compared to the cost of making a fiber drop to this building. The needs of our business have changed (go figure), to include a warehouse building also on the backside of the property. It's not feasible to run a cable between these two building either. So I need to create another wireless bridge to this back warehouse as well. My question is can I just use another non-root bridge to link to the root bridge already in place, or does each wireless bridge require one root bridge and one non-root bridge?
I have good LoS to both buildings from where the current root bridge is, so if two non-root bridges can talk to one root bridge I should be able to just an additional non-root bridge and be good to go. But if wireless bridges are meant to be a one to one setup, then I'll need to setup an additional root bridge to link to the new non-root bridge?
It seems like you should be able to have one root bridge link to multiple non-root bridges but I haven't been able to find any clear examples of this being done.
Thanks in advance for the help!That was just too easy.
I copied the configuration from the working non-root bridge to my laptop. I changed out the ip address of the BVI interface. I uploaded the configuration to the new 1300 bridge. I plugged it in and pointed the yagi antenna in the general direction of the original root bridge and started pinging the new 1300. Success!
I'll use my spare 1300 to get service up and running in the warehouse by the end of the week and I'll just need to order one more 1300 to make sure I have spare on hand if needed.
Thanks again!
Maybe you are looking for
-
How to get email as ABAP report through SAP.
hi all, here i am getting one error. i run the program in foreground i am getting mail. but when i run the report in back ground i get mail but contents no data?? whot could be the reason??
-
My application crashes and comes up with the following error message: The instruction at "0x303556ce" referenced memory at "0x3231206f". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program My appl
-
could not activate my new Iphone 5, get the following error message 80092013
-
CL_HTTP_CLIENT, authentication, alternatives
We are using CL_HTTP_CLIENT to access a service on the web (another part of the same project). In other words, the SAP-system acts as a client. We intended to use "basic authentication" (as in Internet RFC 2617), but that may be a problem for the "ot
-
HT1237 update is installed and showing in system info. Still open in App store.
Update after installation not removed from app store.