Auto boot Guest Domains when control domain is restarted

We have a user who has asked us to set up the LDOMs to boot when the host machine boots up.
Can this be done?
All I found was this setting
ldm set-variable auto-boot\?=true goldldom
Or, do I need to write a script to do this.

http://www.opensolaris.org/jive/thread.jspa?threadID=109629&tstart=0
"If you save your configuration to the SP (ldm add-config foo) while
the guest domains are active then they will start & boot when the
system is powercycled (assuming auto-boot? is true also)."

Similar Messages

  • How to reboot a guest domain when hung and ldm stop-domain doesn't work

    Hi, the configuration is as follows.
    SF T1000 (32 threads/16gb) memory
    Latest Firmware and the LDOM patch (-02) applied.
    This is how the LDOMs are setup.
    Instance CPUs Memory
    Service domain 4 2g
    ldom1 4 2g
    ldom2 4 2g
    ldom3 4 2g
    ldom4 4 2g
    ldom5 4 2g
    ldom6 4 2g
    ldom7 4 1.9g
    All guest domains are running on disk-images on mirrored BE on service domain. Size around 7 gb and SUNWCXall installed.
    However, I have had a few hangs, especially when working over the virtual switch on the domains.
    At the moment ldom1 is totally hung. See below for info:
    bash-3.00# ldm list-domain
    Name State Flags Cons VCPU Memory Util Uptime
    primary active -t-cv SP 4 2G 0.5% 1d 1h 17m
    ldom1 active -t--- 5000 4 2G 25% 2h 14m
    ldom2 active -t--- 5001 4 2G 0.2% 2h 35m
    ldom3 active ----- 5002 4 2G 0.2% 47m
    ldom4 active ----- 5003 4 2G 0.2% 1d 1h 10m
    ldom5 active -t--- 5004 4 2G 0.3% 1d 1h 10m
    ldom6 active -t--- 5005 4 2G 0.2% 1d 1h 10m
    ldom7 active -t--- 5006 4 1900M 0.2% 7h 29m
    bash-3.00#
    bash-3.00# ldm stop-domain ldom1
    LDom ldom1 stop notification failed
    bash-3.00#
    bash-3.00# telnet localhost 5000
    Trying 127.0.0.1...
    Connected to localhost.
    Escape character is '^]'.
    Connecting to console "ldom1" in group "ldom1" ....
    Press ~? for control options ..
    <COMMENT: ~w sent!>
    Warning: another user currently has write permission
    to this console and forcibly removing him/her will terminate
    any current write action and all work will be lost.
    Would you like to continue?[y/n] y
    < COMMENT: I don't get any response when hitting enter and ~# (break) doesn't seem to work....>
    I cannot ssh to ldom1 since it appears to be dead!
    Anyone know if I can send some sort of reset to this hung domain? How can I troubleshoot it?
    Regards,
    Daniel

    UPDATE 2
    =========
    When I attached to ldom3 through the console services, this domain also had
    hung.
    Below is some LDOM information.
    bash-3.00# ldm list-services
    Vldc: primary-vldc0
    Vldc: primary-vldc3
    Vds: primary-vds0
    vdsdev: vol1 device=/ldoms/be/ldom_1.img
    vdsdev: vol5 device=/ldoms/be/ldom_5.img
    vdsdev: vol6 device=/ldoms/be/ldom_6.img
    vdsdev: vol7 device=/ldoms/be/ldom_7.img
    vdsdev: vol2 device=/ldoms/be/ldom_2.img
    vdsdev: vol3 device=/ldoms/be/ldom_3.img
    vdsdev: vol4 device=/ldoms/be/ldom_4.img
    Vcc: primary-vcc0
    port-range=5000-5100
    Vsw: primary-vsw0
    mac-addr=0:14:4f:f8:66:9f
    net-dev=bge0
    mode=prog,promisc
    Vsw: primary-vsw1
    mac-addr=0:14:4f:f9:dd:53
    net-dev=bge1
    mode=prog,promisc
    bash-3.00# ldm list-devices
    vCPU:
    vCPUID %FREE
    MAU:
    Free MA-Units:
    cpuset (0, 1, 2, 3)
    cpuset (4, 5, 6, 7)
    cpuset (8, 9, 10, 11)
    cpuset (12, 13, 14, 15)
    cpuset (16, 17, 18, 19)
    cpuset (20, 21, 22, 23)
    cpuset (24, 25, 26, 27)
    cpuset (28, 29, 30, 31)
    Memory:
    Available mblocks:
    PADDR SIZE
    0x3fec00000 20M (0x1400000)
    I/O Devices:
    Free Devices:
    bash-3.00# ldm list-domains
    Unknown command list-domains; use --help option for list of available commands
    bash-3.00# ldm list-domain
    Name State Flags Cons VCPU Memory Util Uptime
    primary active -t-cv SP 4 2G 0.7% 1d 4h 8m
    ldom1 active -t--- 5000 4 2G 0.3% 1h 24m
    ldom2 active -t--- 5001 4 2G 0.6% 5h 26m
    ldom3 active ----- 5002 4 2G 25% 3h 38m
    ldom4 active ----- 5003 4 2G 0.1% 1d 4h 1m
    ldom5 active -t--- 5004 4 2G 0.1% 1d 4h 1m
    ldom6 active -t--- 5005 4 2G 0.7% 1d 4h 1m
    ldom7 active -t--- 5006 4 1900M 0.1% 10h 20m
    bash-3.00#
    bash-3.00# ldm list-bindings
    Name: primary
    State: active
    Flags: transition,control,vio service
    OS:
    Util: 0.5%
    Uptime: 1d 4h 11m
    Vcpu: 4
    vid pid util strand
    0 0 0.9% 100%
    1 1 0.8% 100%
    2 2 0.2% 100%
    3 3 0.3% 100%
    Memory: 2G
    real-addr phys-addr size
    0x8000000 0x8000000 2G
    Vars: reboot-command=boot
    IO: pci@780 (bus_a)
    pci@7c0 (bus_b)
    Vldc: primary-vldc0
    [LDC: 0x0]
    [(HV Control channel)]
    [LDC: 0x1]
    [LDom primary   (Domain Services channel)]
    [LDC: 0x3]
    [LDom primary   (FMA Services channel)]
    [LDC: 0xb]
    [LDom ldom1     (Domain Services channel)]
    [LDC: 0x22]
    [LDom ldom5     (Domain Services channel)]
    [LDC: 0x27]
    [LDom ldom6     (Domain Services channel)]
    [LDC: 0x2d]
    [LDom ldom7     (Domain Services channel)]
    [LDC: 0x10]
    [LDom ldom2     (Domain Services channel)]
    [LDC: 0x18]
    [LDom ldom3     (Domain Services channel)]
    [LDC: 0x1d]
    [LDom ldom4     (Domain Services channel)]
    Vldc: primary-vldc3
    [LDC: 0x14]
    [spds (SP channel)]
    [LDC: 0xd]
    [system-management (SP channel)]
    [LDC: 0x6]
    [sunvts (SP channel)]
    [LDC: 0x7]
    [sunmc (SP channel)]
    [LDC: 0x8]
    [explorer (SP channel)]
    [LDC: 0x9]
    [led (SP channel)]
    [LDC: 0xa]
    [flashupdate (SP channel)]
    Vds: primary-vds0
    vdsdev: vol1 device=/ldoms/be/ldom_1.img
    vdsdev: vol5 device=/ldoms/be/ldom_5.img
    vdsdev: vol6 device=/ldoms/be/ldom_6.img
    vdsdev: vol7 device=/ldoms/be/ldom_7.img
    vdsdev: vol2 device=/ldoms/be/ldom_2.img
    vdsdev: vol3 device=/ldoms/be/ldom_3.img
    vdsdev: vol4 device=/ldoms/be/ldom_4.img
    [LDom  ldom1, dev-name: vol1]
    [LDC: 0xe]
    [LDom  ldom5, dev-name: vol5]
    [LDC: 0x25]
    [LDom  ldom6, dev-name: vol6]
    [LDC: 0x2a]
    [LDom  ldom7, dev-name: vol7]
    [LDC: 0x30]
    [LDom  ldom2, dev-name: vol2]
    [LDC: 0x13]
    [LDom  ldom3, dev-name: vol3]
    [LDC: 0x1b]
    [LDom  ldom4, dev-name: vol4]
    [LDC: 0x20]
    Vcc: primary-vcc0
    [LDC: 0xf]
    [LDom ldom1, group: ldom1, port: 5000]
    [LDC: 0x26]
    [LDom ldom5, group: ldom5, port: 5004]
    [LDC: 0x2c]
    [LDom ldom6, group: ldom6, port: 5005]
    [LDC: 0x31]
    [LDom ldom7, group: ldom7, port: 5006]
    [LDC: 0x15]
    [LDom ldom2, group: ldom2, port: 5001]
    [LDC: 0x1c]
    [LDom ldom3, group: ldom3, port: 5002]
    [LDC: 0x21]
    [LDom ldom4, group: ldom4, port: 5003]
    port-range=5000-5100
    Vsw: primary-vsw0
    mac-addr=0:14:4f:f8:66:9f
    net-dev=bge0
    [LDC: 0xc]
    [LDom ldom1, name: vnet1, mac-addr: 0:14:4f:fa:1e:4d]
    [LDC: 0x23]
    [LDom ldom5, name: vnet0, mac-addr: 0:14:4f:f9:ae:a1]
    [LDC: 0x28]
    [LDom ldom6, name: vnet0, mac-addr: 0:14:4f:f8:27:b8]
    [LDC: 0x2e]
    [LDom ldom7, name: vnet0, mac-addr: 0:14:4f:f9:1f:5d]
    [LDC: 0x11]
    [LDom ldom2, name: vnet0, mac-addr: 0:14:4f:f8:c9:7c]
    [LDC: 0x19]
    [LDom ldom3, name: vnet0, mac-addr: 0:14:4f:fb:d9:6d]
    [LDC: 0x1e]
    [LDom ldom4, name: vnet0, mac-addr: 0:14:4f:fb:df:2c]
    mode=prog,promisc
    Vsw: primary-vsw1
    mac-addr=0:14:4f:f9:dd:53
    net-dev=bge1
    [LDC: 0x2b]
    [LDom ldom1, name: vnet2, mac-addr: 0:14:4f:fa:b1:f0]
    [LDC: 0x24]
    [LDom ldom5, name: vnet1, mac-addr: 0:14:4f:f9:b2:b0]
    [LDC: 0x29]
    [LDom ldom6, name: vnet1, mac-addr: 0:14:4f:fb:f5:c3]
    [LDC: 0x2f]
    [LDom ldom7, name: vnet1, mac-addr: 0:14:4f:f8:3a:3e]
    [LDC: 0x12]
    [LDom ldom2, name: vnet1, mac-addr: 0:14:4f:f9:88:a0]
    [LDC: 0x1a]
    [LDom ldom3, name: vnet1, mac-addr: 0:14:4f:fa:aa:57]
    [LDC: 0x1f]
    [LDom ldom4, name: vnet1, mac-addr: 0:14:4f:f9:33:59]
    mode=prog,promisc
    Vldcc: vldcc1 [FMA Services]
    service: ldmfma
    service: primary-vldc0 @ primary
    [LDC: 0x4]
    Vldcc: vldcc2 [SP channel]
    service: spfma
    [LDC: 0x5]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x2]
    Vldcc: hvctl [Hypervisor Control]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    Vcons: SP
    Name: ldom1
    State: active
    Flags: transition
    OS:
    Util: 0.3%
    Uptime: 1h 27m
    Vcpu: 4
    vid pid util strand
    0 4 0.5% 100%
    1 5 0.6% 100%
    2 6 0.1% 100%
    3 7 0.0% 100%
    Memory: 2G
    real-addr phys-addr size
    0x8000000 0x88000000 2G
    Vars: auto-boot?=false
    boot-device=/virtual-devices@100/channel-devices@200/disk@0:a vdisk
    nvramrc=devalias vnet /virtual-devices@100/channel-devices@200/network@0
    use-nvramrc?=true
    Vnet: vnet1 [LDC: 0xb]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0xd]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0xf]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x4]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x6]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0x8]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
    mac-addr=0:14:4f:fa:1e:4d
    service: primary-vsw0 @ primary
    [LDC: 0x1]
    Vnet: vnet2 [LDC: 0xc]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xe]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0x10]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0x5]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x7]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0x9]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
    mac-addr=0:14:4f:fa:b1:f0
    service: primary-vsw1 @ primary
    [LDC: 0xa]
    Vdisk: vdisk1 vol1@primary-vds0
    service: primary-vds0 @ primary
    [LDC: 0x2]
    Vcons: [via LDC:3]
    ldom1@primary-vcc0 [port:5000]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    Name: ldom2
    State: active
    Flags: transition
    OS:
    Util: 0.1%
    Uptime: 5h 29m
    Vcpu: 4
    vid pid util strand
    0 8 0.6% 100%
    1 9 0.1% 100%
    2 10 0.0% 100%
    3 11 0.2% 100%
    Memory: 2G
    real-addr phys-addr size
    0x8000000 0x108000000 2G
    Vars: boot-device=vdisk
    Vnet: vnet0 [LDC: 0x2]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x3]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x4]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x5]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0xd]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0xf]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
    mac-addr=0:14:4f:f8:c9:7c
    service: primary-vsw0 @ primary
    [LDC: 0x1]
    Vnet: vnet1 [LDC: 0x7]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0x8]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0x9]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0xa]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0xe]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0x10]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
    mac-addr=0:14:4f:f9:88:a0
    service: primary-vsw1 @ primary
    [LDC: 0x6]
    Vdisk: vdisk2 vol2@primary-vds0
    service: primary-vds0 @ primary
    [LDC: 0xb]
    Vcons: [via LDC:12]
    ldom2@primary-vcc0 [port:5001]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    Name: ldom3
    State: active
    Flags:
    OS:
    Util: 24%
    Uptime: 3h 42m
    Vcpu: 4
    vid pid util strand
    0 12 100% 100%
    1 13 1.4% 100%
    2 14 1.4% 100%
    3 15 1.4% 100%
    Memory: 2G
    real-addr phys-addr size
    0x8000000 0x188000000 2G
    Vars: boot-device=vdisk
    Vnet: vnet0 [LDC: 0x2]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x3]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x4]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x5]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x6]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0xf]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
    mac-addr=0:14:4f:fb:d9:6d
    service: primary-vsw0 @ primary
    [LDC: 0x1]
    Vnet: vnet1 [LDC: 0x8]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0x9]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xa]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0xb]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0xc]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x10]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
    mac-addr=0:14:4f:fa:aa:57
    service: primary-vsw1 @ primary
    [LDC: 0x7]
    Vdisk: vdisk3 vol3@primary-vds0
    service: primary-vds0 @ primary
    [LDC: 0xd]
    Vcons: [via LDC:14]
    ldom3@primary-vcc0 [port:5002]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    Name: ldom4
    State: active
    Flags:
    OS:
    Util: 0.2%
    Uptime: 1d 4h 4m
    Vcpu: 4
    vid pid util strand
    0 16 0.4% 100%
    1 17 0.3% 100%
    2 18 0.1% 100%
    3 19 0.0% 100%
    Memory: 2G
    real-addr phys-addr size
    0x8000000 0x208000000 2G
    Vars: boot-device=vdisk
    Vnet: vnet0 [LDC: 0x2]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x3]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x4]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x5]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x6]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x7]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d]
    mac-addr=0:14:4f:fb:df:2c
    service: primary-vsw0 @ primary
    [LDC: 0x1]
    Vnet: vnet1 [LDC: 0x9]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xa]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xb]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0xc]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0xd]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0xe]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57]
    mac-addr=0:14:4f:f9:33:59
    service: primary-vsw1 @ primary
    [LDC: 0x8]
    Vdisk: vdisk4 vol4@primary-vds0
    service: primary-vds0 @ primary
    [LDC: 0xf]
    Vcons: [via LDC:16]
    ldom4@primary-vcc0 [port:5003]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    Name: ldom5
    State: active
    Flags: transition
    OS:
    Util: 0.2%
    Uptime: 1d 4h 4m
    Vcpu: 4
    vid pid util strand
    0 20 0.6% 100%
    1 21 0.0% 100%
    2 22 0.3% 100%
    3 23 0.0% 100%
    Memory: 2G
    real-addr phys-addr size
    0x8000000 0x288000000 2G
    Vars: boot-device=vdisk
    Vnet: vnet0 [LDC: 0x2]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0xd]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0xf]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x3]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x5]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0x9]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
    mac-addr=0:14:4f:f9:ae:a1
    service: primary-vsw0 @ primary
    [LDC: 0x1]
    Vnet: vnet1 [LDC: 0x7]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xe]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0x10]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0x4]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x8]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0xa]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
    mac-addr=0:14:4f:f9:b2:b0
    service: primary-vsw1 @ primary
    [LDC: 0x6]
    Vdisk: vdisk5 vol5@primary-vds0
    service: primary-vds0 @ primary
    [LDC: 0xb]
    Vcons: [via LDC:12]
    ldom5@primary-vcc0 [port:5004]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    Name: ldom6
    State: active
    Flags: transition
    OS:
    Util: 0.3%
    Uptime: 1d 4h 4m
    Vcpu: 4
    vid pid util strand
    0 24 0.5% 100%
    1 25 0.3% 100%
    2 26 0.5% 100%
    3 27 0.0% 100%
    Memory: 2G
    real-addr phys-addr size
    0x8000000 0x308000000 2G
    Vars: boot-device=vdisk
    Vnet: vnet0 [LDC: 0x2]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x6]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0xf]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x3]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x5]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0xa]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
    mac-addr=0:14:4f:f8:27:b8
    service: primary-vsw0 @ primary
    [LDC: 0x1]
    Vnet: vnet1 [LDC: 0x8]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xc]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0x10]
    [Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0x4]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x9]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0xb]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
    mac-addr=0:14:4f:fb:f5:c3
    service: primary-vsw1 @ primary
    [LDC: 0x7]
    Vdisk: vdisk6 vol6@primary-vds0
    service: primary-vds0 @ primary
    [LDC: 0xd]
    Vcons: [via LDC:14]
    ldom6@primary-vcc0 [port:5005]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    Name: ldom7
    State: active
    Flags: transition
    OS:
    Util: 0.4%
    Uptime: 10h 23m
    Vcpu: 4
    vid pid util strand
    0 28 0.6% 100%
    1 29 0.1% 100%
    2 30 0.3% 100%
    3 31 0.2% 100%
    Memory: 1900M
    real-addr phys-addr size
    0x8000000 0x388000000 1900M
    Vars: boot-device=vdisk
    Vnet: vnet0 [LDC: 0x2]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x6]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x7]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x3]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x5]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0xb]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
    mac-addr=0:14:4f:f9:1f:5d
    service: primary-vsw0 @ primary
    [LDC: 0x1]
    Vnet: vnet1 [LDC: 0x9]
    [Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xd]
    [Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xe]
    [Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0x4]
    [Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0xa]
    [Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0xc]
    [Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
    mac-addr=0:14:4f:f8:3a:3e
    service: primary-vsw1 @ primary
    [LDC: 0x8]
    Vdisk: vdisk7 vol7@primary-vds0
    service: primary-vds0 @ primary
    [LDC: 0xf]
    Vcons: [via LDC:16]
    ldom7@primary-vcc0 [port:5006]
    Vldcc: vldcc0 [Domain Services]
    service: primary-vldc0 @ primary
    [LDC: 0x0]
    bash-3.00#

  • Configure Solaris cluster to failover guest domain when NICs were down

    Hi,
    I am running Solaris 11 as the control domains on 2 clustered nodes running on Solaris Cluster 4. There is a Solaris 10 guest domain which is managed via the Solaris cluster in failover mode.
    2 virtual switches connected to 2 different network switches are presented to the guest domain. I would like to use link based IPMP to facilitate HA for the network connections. I understand that in this case the IPMP can only be configured within the guest domain. Now the question is how do I configure it in such a way that the guest domain fails over to the second cluster node (standby control domain) if both network interfaces are down? Thanks.
    Edited by: user12925046 on Dec 25, 2012 9:48 PM
    Edited by: user12925046 on Dec 25, 2012 9:49 PM

    The Solaris Cluster 4.1 Installation and Concepts Guide are available at :-
    http://docs.oracle.com/cd/E29086_01/index.html
    Thanks.

  • Can't mount 4Tb USB 3.0 drive on a Sparc T5-8 control domain

    Hello,
    I'm trying to mount a 4Tb USB 3.0 disk drive on a Sun Sparc T5-8 running Solaris 11.  It is also the LDOM primary and control domain.
    I've verified that hal, dbus and rmvolmgr are running:
    # svcs hal dbus rmvolmgr
    STATE          STIME    FMRI
    online         Jan_29   svc:/system/dbus:default
    online         16:21:51 svc:/system/hal:default
    online         16:21:51 svc:/system/filesystem/rmvolmgr:default
    but the server can't detect the drive:
    # rmformat -l
    Looking for devices...
    No removables found.
    # echo | format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
           0. c0t5000CCA022659884d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca022659884
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD0/disk
           1. c0t5000CCA022666330d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca022666330
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD1/disk
           2. c0t5000CCA0166F4D08d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca0166f4d08
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD2/disk
           3. c0t5000CCA022665404d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca022665404
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD3/disk
          4. c1t0d0 <drive not available>
              /pci@300/pci@1/pci@0/pci@4/pci@0/pci@6/usb@0/storage@3/disk@0,0
    Specify disk (enter its number): Specify disk (enter its number): ^C
    I verified the drive is good because I can mount it on a Sun T4 server running Solaris10 and was able to mount and see the data.
    Any ideas why the Sparc T5 can't access the drive?  I've also tried restarting hal and rmvolmgr, but issue still persist.
    Any assistance is appreciated as we need to access customer's data on the drive as soon as possible.
    Thanks,

    Hi,
    since your posting is a couple of weeks old I don't know if you already managed to get the disk working.
    You might want to consider one of the following options to get it working as the problem is seen when the disk drive draws more power as the USB port can deliver.  
    1)  use USB EXTENSION Y CABLE   
    2)  use external USB hub with power supply  
    3)  use USB disk with external power supply
    For more details you might want to review
    (Doc ID 1572327.1)  Solaris might be Unable to Mount certain USB Disks because of Overcurrent on USB Port
    regards
    Walter

  • How to Configure IPMP on Control Domain?

    Dear All i am configuring IPMP in Control Domain:
    and what i need to know exactly is how to setup the routing in the control domain to allaow the vsw to see the IPMP configration on physical network.
    this is my config now:
    primary-vsw2 00:11:22:33:44:55 switch@2 1 1 1500
    ifconfig -a
    e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 10.1.111.223 netmask ffffff00 broadcast 10.1.111.255
    groupname ipmp1
    ether 0:14:4f:cb:36:9
    e1000g1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
    inet 10.1.111.225 netmask ffffff00 broadcast 10.1.111.255
    e1000g3: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3
    inet 10.1.111.224 netmask ffffff00 broadcast 10.1.111.255
    groupname ipmp1
    ether 0:14:4f:cb:36:b
    vsw2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
    inet 10.1.111.221 netmask ffffff00 broadcast 10.1.111.255
    ether 0:14:4f:fb:e9:e3
    the proplem is that i can access VSW2 becuse i was not able to configure the control domain IPMP interfaces to work as a router.
    Can some one help me with it???plz

    I believe you'd need to do something similar to the following:
    In the Control Domain:
    # routeadm -e ipv4-forwarding
    # routeadm -e ipv4-routing
    # routeadm -u
    In the Guest Domain:
    # ifconfig vnet0 plumb
    # ifconfig vnet0 10.1.111.226 netmask + broadcast + up
    # route add default 10.1.111.221
    (Assuming the guest's IP is 10.1.111.226)
    Also, I know you didn't ask, but just in case you don't know, aggregated links created by dladm can be turned into virtual switches directly (not the same as IPMP I know, but depending on your use case it might provide the same abilities).

  • Install OBIEE Failed When Creating Domain

    Hi all,
    I tried to install OBIEE on 64bit redhat linux, but failed when creating domain, the error log shows:
    Starting the domain ...
    oracle.as.provisioning.util.ConfigException:
    Error while starting the domain.
    Cause:
    An error occurred while starting the domain.
    Action:
    See logs for more details.
         at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
         at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3180)
         at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3043)
         at oracle.as.provisioning.engine.WorkFlowExecutor._startAdminServer(WorkFlowExecutor.java:1645)
         at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:635)
         at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)
         at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
         at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
         at oracle.as.install.bi.biconfig.standard.DomainProvisioningTask.doExecute(DomainProvisioningTask.java:49)
         at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
         at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
         at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
         at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
         at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
         at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
         at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
         at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
         at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.as.provisioning.util.ConfigException:
    Error while starting the domain.
    Cause:
    An internal WLST operation has failed.
    Action:
    See logs for more details.
         at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
         at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3126)
         ... 19 more
    oracle.as.provisioning.exception.ASProvisioningException
         at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:872)
         at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
         at oracle.as.install.bi.biconfig.standard.DomainProvisioningTask.doExecute(DomainProvisioningTask.java:49)
         at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
         at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
         at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
         at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
         at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
         at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
         at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
         at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
         at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.as.provisioning.exception.ASProvWorkflowException: Error Executing workflow.
         at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:686)
         at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)
         at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
         ... 14 more
    the following steps(steps after creating domain) raised:
    Caused by: java.net.ConnectException: t3://hostname:7001: Destination unreachable; nested exception is:
        java.net.ConnectException: Connection refused; No available router to destination
    It's unlikely a hosts file issue which I've met before.
    Install OBIEE Failed on Linux 64bit
    the log caused by hosts file shows:
    Caused by: oracle.as.provisioning.util.ConfigException:
    Error while starting the domain.
    Cause:
    Starting the Admin_Server timed out.
    BTW, the port was tested to be available.
    any idea?
    thanks in advance
    Nathaniel

    we had this issue couple of days back ,,
    Resolved by doing below
    1. uninstall obiee 2. drop the repository 3, remount /tmp folder
    with this we could successfully install obiee 11.1.1.7

  • When the domain controller locator process happened

    HI Guys
      I read lots of articles about how domain controller located. And so far i thougth i knew most of the process, but still have some question.
    1.when the DC locator happend ,just start during computer boots up ,or started after user press CTRL+ALT+DEL and input username and credential.
    2.Based on following Technet article , step 7, what's the difference between  "If the client has found a DC in the site in which the DC claims the client is located" and "If the returned domain controller is in the cloest site "
    ? And step 8, if the domain that is being quried is same as the domain that the computer joined, was the first domain means the domain the user belongs to ? like xxx\username ?

    Hi Jacky,
    I assume that you are talking about this article:
    Active Directory: Using Catch-All Subnets in Active Directory
    http://technet.microsoft.com/en-us/forefront/2009.06.subnets.aspx
    >when the DC locator happend ,just start during computer boots up ,or started after user press CTRL+ALT+DEL and input username and credential.
    The DC locator initiates after we input domain credentials and press Enter.
    >what's the difference between "If the client has found a DC in the site in which the DC claims the client is located" and "If the returned domain controller is in the closest site "?
    “If the client has found a DC in the site in which the DC claims the client is located” means that the client and a DC are located in the same site. “If the returned domain controller is in the closest site” means that a DC which
    is located in the closest site is found (based on site link cost).
    >if the domain that is being queried is same as the domain that the computer joined, was the first domain means the domain the user belongs to ? like xxx\username ?
    Yes you are right that the first domain means the user account which tries to log on belongs to.
    More information for you:
    Enabling Clients to Locate the Next Closest Domain Controller
    http://technet.microsoft.com/en-us/library/cc733142(v=WS.10).aspx
    I hope this helps.
    Amy

  • Group Policy processing failure on 2008 when MIX Domain 2003 with DC 2008

    Dear I try to add additional Windows 2008 Domain to My Domain controller 2003  and I ma Receiving Group policy error in DC 2008  With Event ID 1055
    The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
    a) Name Resolution failure on the current domain controller. 
    b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" /> 
      <EventID>1055</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Opcode>1</Opcode> 
      <Keywords>0x8000000000000000</Keywords> 
      <TimeCreated SystemTime="2014-03-06T14:36:44.411955300Z" /> 
      <EventRecordID>3859</EventRecordID> 
      <Correlation ActivityID="{28DAD258-26D0-4C1E-A4B7-F37DEE04C8F1}" /> 
      <Execution ProcessID="952" ThreadID="3276" /> 
      <Channel>System</Channel> 
      <Computer>PRIMARYDC.Qtit.com</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="SupportInfo1">1</Data> 
      <Data Name="SupportInfo2">1632</Data> 
      <Data Name="ProcessingMode">0</Data> 
      <Data Name="ProcessingTimeInMilliseconds">1578</Data> 
      <Data Name="ErrorCode">5</Data> 
      <Data Name="ErrorDescription">Access is denied.</Data> 
      </EventData>
      </Event>
    I install See KB939820 for a hotfix applicable to Microsoft DC 2003 regrading to he KRBTGT account 
    Refer Url : http://support.microsoft.com/kb/939820 
    I run dcdiag /v on  and repadmin /showrepl at DC 2008
    the dcdiag /v result
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine PRIMARYDC, is a Directory Server. 
       Home Server = PRIMARYDC
       * Connecting to directory service on server PRIMARYDC.
       * Identified AD Forest. 
       Collecting AD specific global data 
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded 
       Iterating through the sites 
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers 
       Getting information for the server CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       Getting information for the server CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity 
             * Active Directory RPC Services Check
             ......................... PRIMARYDC passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Advertising
             The DC PRIMARYDC is advertising itself as a DC and having a DS.
             The DC PRIMARYDC is advertising as an LDAP server
             The DC PRIMARYDC is advertising as having a writeable directory
             The DC PRIMARYDC is advertising as a Key Distribution Center
             The DC PRIMARYDC is advertising as a time server
             The DS PRIMARYDC is advertising as a GC.
             ......................... PRIMARYDC passed test Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Starting test: FrsEvent
             * The File Replication Service Event log test 
             There are warning or error events within the last 24 hours after the
             SYSVOL has been shared.  Failing SYSVOL replication problems may cause
             Group Policy problems. 
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:18:56
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:53:21
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             ......................... PRIMARYDC passed test FrsEvent
          Starting test: DFSREvent
             The DFS Replication Event Log. 
             Skip the test because the server is running FRS.
             ......................... PRIMARYDC passed test DFSREvent
          Starting test: SysVolCheck
             * The File Replication Service SYSVOL ready test 
             File Replication Service's SYSVOL is ready 
             ......................... PRIMARYDC passed test SysVolCheck
          Starting test: KccEvent
             * The KCC Event log test
             Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
             ......................... PRIMARYDC passed test KccEvent
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Domain Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role PDC Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Rid Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             ......................... PRIMARYDC passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             Checking machine account for DC PRIMARYDC on DC PRIMARYDC.
             * SPN found :LDAP/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :LDAP/PRIMARYDC.Qtit.com
             * SPN found :LDAP/PRIMARYDC
             * SPN found :LDAP/PRIMARYDC.Qtit.com/QTIT
             * SPN found :LDAP/e3d8c76c-1b59-4de6-9f7f-c438df9a2863._msdcs.Qtit.com
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/e3d8c76c-1b59-4de6-9f7f-c438df9a2863/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com
             * SPN found :HOST/PRIMARYDC
             * SPN found :HOST/PRIMARYDC.Qtit.com/QTIT
             * SPN found :GC/PRIMARYDC.Qtit.com/Qtit.com
             ......................... PRIMARYDC passed test MachineAccount
          Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC PRIMARYDC.
             The forest is not ready for RODC. Will skip checking ERODC ACEs.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               DC=DomainDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=DomainDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=Qtit,DC=com
                (Schema,Version 3)
             * Security Permissions Check for
               CN=Configuration,DC=Qtit,DC=com
                (Configuration,Version 3)
             * Security Permissions Check for
               DC=Qtit,DC=com
                (Domain,Version 3)
             ......................... PRIMARYDC failed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             Verified share \\PRIMARYDC\netlogon
             Verified share \\PRIMARYDC\sysvol
             ......................... PRIMARYDC passed test NetLogons
          Starting test: ObjectsReplicated
             PRIMARYDC is in domain DC=Qtit,DC=com
             Checking for CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com in domain DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com in domain CN=Configuration,DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             ......................... PRIMARYDC passed test ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
                DC=ForestDnsZones,DC=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                DC=DomainDnsZones,DC=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                CN=Schema,CN=Configuration,DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                CN=Configuration,DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
             * Replication Site Latency Check 
             ......................... PRIMARYDC passed test Replications
          Starting test: RidManager
             * Available RID Pool for the Domain is 14607 to 1073741823
             * SecondAD.Qtit.com is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 14107 to 14606
             * rIDPreviousAllocationPool is 14107 to 14606
             * rIDNextRID: 14124
             ......................... PRIMARYDC passed test RidManager
          Starting test: Services
             * Checking Service: EventSystem
             * Checking Service: RpcSs
             * Checking Service: NTDS
             * Checking Service: DnsCache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... PRIMARYDC passed test Services
          Starting test: SystemLog
             * The System Event log test
             A warning event occurred.  EventID: 0x0000A001
                Time Generated: 03/06/2014   16:04:05
                Event String:
                The Security System could not establish a secured connection with the server ldap/PRIMARYDC.Qtit.com/[email protected]. No authentication protocol was available.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:06:35
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:11:36
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:16:38
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:21:39
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:26:41
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:46
                Event String:
                Driver TOSHIBA e-STUDIO16/20/25 PCL 6 required for printer TOSHIBA e-STUDIO16/20/25 PCL 6 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:48
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:49
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:14
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver WebEx Document Loader required for printer WebEx Document Loader is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:31:42
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             ......................... PRIMARYDC failed test SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Starting test: VerifyReferences
             The system object reference (serverReference)
             CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com and backlink on
             CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (serverReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on
             CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (frsComputerReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com are
             correct. 
             ......................... PRIMARYDC passed test VerifyReferences
          Test omitted by user request: VerifyReplicas
          Test omitted by user request: DNS
          Test omitted by user request: DNS
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : Qtit
          Starting test: CheckSDRefDom
             ......................... Qtit passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Qtit passed test CrossRefValidation
       Running enterprise tests on : Qtit.com
          Test omitted by user request: DNS
          Test omitted by user request: DNS
          Starting test: LocatorCheck
             GC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             PDC Name: \\SecondAD.Qtit.com
             Locator Flags: 0xe00001bd
             Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             Preferred Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             KDC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             ......................... Qtit.com passed test LocatorCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope
             provided by the command line arguments provided. 
             ......................... Qtit.com passed test Intersite
    repadmin /showrepl Result
    ******************************8
    ==== INBOUND NEIGHBORS ===================================
    DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:04 was successful.
    CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:39 was successful.
    CN=Schema,CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    DC=DomainDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:27:31 was successful.
    DC=ForestDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    I try to down the DC 2003 and access \\Qtit.com it success open the syslog on DC 2008
    Any help or advice 

    Hi,
    Were there other error codes logged in Event Viewer?
    Regarding Event ID 1055, the following article can be referred to for troubleshooting.
    Event ID 1055 — Group Policy Preprocessing (Security)
    http://technet.microsoft.com/en-us/library/cc727272(v=ws.10).aspx
    Based on the report you posted, this issue may be related to FRS replication service. As a result, we can use ntfrsutl tool to check whether the replication service is healthy.
    Regarding this point, the following articles can be referred to for more information.
    Troubleshooting File Replication Service
    http://technet.microsoft.com/en-us/library/bb727056.aspx
    Ntfrsutl
    http://technet.microsoft.com/en-us/library/hh875636.aspx
    In addition, we can also try doing a non-authoritative Sysvol restore on Windows Server 2008 DC to see whether the issue persists.
    Using the BurFlags registry key to reinitialize File Replication Service replica sets
    http://support.microsoft.com/kb/290762/en-us
    Hope it helps.
    Best regards,
    Frank Shen

  • How can I edit my iweb published site when the domain file is empty?

    How can I edit my iweb site when the domain file opens up empty? I have the site backed up in mobile me, on my computer, and on an external hard drive.
    How can I transfer these files into iweb?

    Hi there,
    To edit your site from one of your backed up versions, place the Domain file in User>Library>Application Support>iWeb & then launch iWeb. Update & publish.
    Ben

  • Which file gets updated in WebLogic domain when a user is created

    Hi All,
    I have a query regarding In a weblogic domain when we create a user or group in security realm--> myrealm in Dfault Authenticator, then which file or folder under Domain directory structure gets updated?
    Thanks in Advance!!

    In the ${DOMAIN_HOME}/security directory the ldift files for the embedded LDAP are located. Also every server gets its own copy (${DOMAIN_HOME}/servers/${SERVER_NAME}/cluster-server1/data/ldap).

  • SCCM 2012 and Exchange Connector some how getting wrong domain when associating devices to users

    I happen to go to the SCCM software catalog site and click devices and noticed that my mobile device was not included.
    After finding my device in All Mobile Devices I found the following:
    For my device the connect assigned Foo\UserName where it should have actually been Bar\UserName.
    Our domain is foo.domain but when we log in to computers we use bar\Username. If I login as
    [email protected] authentication works.
    So how do I get the SCCM Exchange connector to select Bar\UserName and not foo\username? I'm guessing that this is actually an Exchange issue but I figure I would ask here first.
    Thanks!

    Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Why Control Domain provisioning cannot on Linux Proxy Controllers?

    Hi Experts,
    Can we provision a ldom control domain from ops12cU1 enterprise controller with co-located proxy controller on linux?
    I saw some docs mention that the control domain provisioning is supported on Solaris sparc or x86 proxy controllers, but not on linux proxy controllers. Anyone know why there is this limitation?
    Thanks & Best Regards,
    Michael

    At what screen you got this error, can you also provide the steps that you followed? idealy if you uncheck the enable proxy option this error shouldn't appear
    and also you can avoid this error by decline the ccr license agreement and once agent config done configure ccr by command line by setupCCR command from AOH\ccr\bin

  • When exchange Domain Controller or Global Catalog servers?

    I have a few questions want to get your help.
    1,which situation exchange would contact with the Domain Controller, and which situation  exchange would contact with the Global Catalog servers?what's the difference?
    2,for the mailbox replication service, besides moving the mailbox ,and  DAD relevant operations, which situation mailbox replication service also contact with Dc?
    Please click the Mark as Answer button if a post solves your problem!

    Hi,
    About Question 1:
    For Exchange, GC is mainly for Address Book lookups. Exchange server access to the global catalog for address information.
    About DC, every domain controller contains the following three directory partitions.
    1. Configuration: Contains the Configuration container, which stores configuration objects for the entire forest in cn=configuration,dc= forestRootDomain.
    2. Schema: Contains the Schema container, which stores class and attribute definitions for all existing and possible Active Directory objects in cn=schema,cn=configuration,dc= forestRootDomain.
    3. Domain: Contains a < domain > container, which stores users, computers, groups, and other objects for a specific domain.
    For example, each Exchange Server object has the attribute Boolean messageTrackingEnabled. The Exchange server processes will turn on or off message tracking depending on the value of this attribute in the directory. This is an example of configuration data.
    Configuration data is stored in the Configuration partition of Active Directory, and this partition is replicated to every DC in the Forest. Therefore Exchange can potentially go to any DC to access this information.
    About Question 2:
    The Mailbox Replication Service is responsible for moving mailboxes, importing and exporting .pst files, and restoring disabled and soft-deleted mailboxes. All these options need to contact with DC.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support
    Thank you so much
    Please click the Mark as Answer button if a post solves your problem!

  • LDOMs guest hung when LDOM primary reboots

    Hi.
    I have a T5440 with LDOM sw v 1.3 and split bus configuration
    2 services domains, each one with a pair of buses that adresses:
    * 2 quad Gbit Ethernet card
    * 1 dual port FC HBA
    Now we are defining LUNs in a NetApp storage allowing visibility to both service domains.
    Configured MPGROUP and TOUT in order to get IO balancing in case of reboot of primary LDOM, but doesnt work. LDOMS guest keep freeze and qe have to stop (with -f) to continue working.
    We ara assuming that config is ok and supported, but we are totally lost.
    Some help will be appreciated.
    Thanks in advance
    P.D. Here is vdisk configuration
    # ldm ls -o disk
    NAME
    primary
    VDS
    NAME VOLUME OPTIONS MPGROUP DEVICE
    primary-vds0 t5k32c01-d2_rootdisk t5k32c01-d2 /dev/rdsk/c4t60A98000572D426F5434575573544D50d0s2
    t5k32c01-d2_zones t5k32c01-d2-1 /dev/rdsk/c4t60A98000572D426F5434575577706B63d0s2
    t5k32c01-d4_rootdisk t5k32c01-d4 /dev/rdsk/c4t60A98000572D426F543457557364654Fd0s2
    t5k32c01-d4_zones t5k32c01-d4-1 /dev/rdsk/c4t60A98000572D426F5434575577746231d0s2
    t5k32c01-d1_rootdisk t5k32c01-d1 /dev/rdsk/c4t60A98000572D426F54345755727A6A44d0s2
    t5k32c01-d1_zones t5k32c01-d1-1 /dev/rdsk/c4t60A98000572D426F5434575577784A52d0s2
    t5k32c01-d3_rootdisk t5k32c01-d3 /dev/rdsk/c4t60A98000572D426F54345755732F5772d0s2
    t5k32c01-d3_zones t5k32c01-d3-1 /dev/rdsk/c4t60A98000572D426F5434575578306F66d0s2
    NAME
    alternate
    VDS
    NAME VOLUME OPTIONS MPGROUP DEVICE
    alternate-vds0 t5k32c01-d2_rootdisk t5k32c01-d2 /dev/rdsk/c0t60A98000572D426F5434575573544D50d0s2
    t5k32c01-d2_zones t5k32c01-d2-1 /dev/rdsk/c0t60A98000572D426F5434575577706B63d0s2
    t5k32c01-d4_rootdisk t5k32c01-d4 /dev/rdsk/c0t60A98000572D426F543457557364654Fd0s2
    t5k32c01-d4_zones t5k32c01-d4-1 /dev/rdsk/c0t60A98000572D426F5434575577746231d0s2
    t5k32c01-d1_rootdisk t5k32c01-d1 /dev/rdsk/c0t60A98000572D426F54345755727A6A44d0s2
    t5k32c01-d1_zones t5k32c01-d1-1 /dev/rdsk/c0t60A98000572D426F5434575577784A52d0s2
    t5k32c01-d3_rootdisk t5k32c01-d3 /dev/rdsk/c0t60A98000572D426F54345755732F5772d0s2
    t5k32c01-d3_zones t5k32c01-d3-1 /dev/rdsk/c0t60A98000572D426F5434575578306F66d0s2
    NAME
    t5k32c01-d1
    DISK
    NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
    rootdisk t5k32c01-d1_rootdisk@primary-vds0 1 0 disk@0 primary t5k32c01-d1
    zones t5k32c01-d1_zones@primary-vds0 1 1 disk@1 primary t5k32c01-d1-1
    NAME
    t5k32c01-d2
    DISK
    NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
    rootdisk t5k32c01-d2_rootdisk@primary-vds0 1 0 disk@0 primary t5k32c01-d2
    zones t5k32c01-d2_zones@primary-vds0 1 1 disk@1 primary t5k32c01-d2-1
    NAME
    t5k32c01-d3
    DISK
    NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
    rootdisk t5k32c01-d3_rootdisk@alternate-vds0 1 0 disk@0 alternate t5k32c01-d3
    zones t5k32c01-d3_zones@alternate-vds0 1 1 disk@1 alternate t5k32c01-d3-1
    NAME
    t5k32c01-d4
    DISK
    NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
    rootdisk t5k32c01-d4_rootdisk@alternate-vds0 1 0 disk@0 alternate t5k32c01-d4
    zones t5k32c01-d4_zones@alternate-vds0 1 1 disk@1 alternate t5k32c01-d4-1
    Edited by: cesar.rivero on May 14, 2010 8:17 AM

    Hi.
    From your response I can't see clearly what is wrong.
    My config is showing two different VDS and each one defined in primary and alternate LDOM:
    t5k32c01:/root # ldm ls -l
    NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
    primary active -n-cv- SP 8 4G 1.8% 2d 23h 2m
    SOFTSTATE
    Solaris running
    IO
    DEVICE PSEUDONYM OPTIONS
    pci@400 pci_0
    pci@500 pci_1
    VCC
    NAME PORT-RANGE
    primary-vcc0 5000-5100
    VSW
    NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE
    vsw-backup-int 00:14:4f:fb:9e:3e aggr1 0 switch@0 1 1 3 1500
    vsw-prep 00:14:4f:fb:40:8a aggr2 1 switch@1 1 1 320,83,82 1500
    vsw-buses 00:14:4f:f8:46:42 aggr3 2 switch@2 1 1 24 1500
    vsw-ora 00:14:4f:fb:63:de aggr4 3 switch@3 1 1 7,8,9 1500
    VDS
    NAME VOLUME OPTIONS MPGROUP DEVICE
    primary-vds0 t5k32c01-d2_rootdisk t5k32c01-d2 /dev/rdsk/c4t60A98000572D426F5434575573544D50d0s2
    t5k32c01-d2_zones t5k32c01-d2-1 /dev/rdsk/c4t60A98000572D426F5434575577706B63d0s2
    t5k32c01-d4_rootdisk t5k32c01-d4 /dev/rdsk/c4t60A98000572D426F543457557364654Fd0s2
    t5k32c01-d4_zones t5k32c01-d4-1 /dev/rdsk/c4t60A98000572D426F5434575577746231d0s2
    t5k32c01-d1_rootdisk t5k32c01-d1 /dev/rdsk/c4t60A98000572D426F54345755727A6A44d0s2
    t5k32c01-d1_zones t5k32c01-d1-1 /dev/rdsk/c4t60A98000572D426F5434575577784A52d0s2
    t5k32c01-d3_rootdisk t5k32c01-d3 /dev/rdsk/c4t60A98000572D426F54345755732F5772d0s2
    t5k32c01-d3_zones t5k32c01-d3-1 /dev/rdsk/c4t60A98000572D426F5434575578306F66d0s2
    VCONS
    NAME SERVICE PORT
    SP
    NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
    alternate active -n--v- 5000 8 4G 14% 2d 23h 46m
    SOFTSTATE
    Solaris running
    IO
    DEVICE PSEUDONYM OPTIONS
    pci@600 pci_2
    pci@700 pci_3
    VSW
    NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE
    vsw-backup-int-alt 00:14:4f:f9:22:6d aggr11 0 switch@0 1 1 3 1500
    vsw-prep-alt 00:14:4f:f8:2a:03 aggr12 1 switch@1 1 1 320,83,82 1500
    vsw-buses-alt 00:14:4f:fa:76:8d aggr13 2 switch@2 1 1 24 1500
    vsw-ora-alt 00:14:4f:f8:d0:d0 aggr14 3 switch@3 1 1 7,8,9 1500
    VDS
    NAME VOLUME OPTIONS MPGROUP DEVICE
    alternate-vds0 t5k32c01-d2_rootdisk t5k32c01-d2 /dev/rdsk/c0t60A98000572D426F5434575573544D50d0s2
    t5k32c01-d2_zones t5k32c01-d2-1 /dev/rdsk/c0t60A98000572D426F5434575577706B63d0s2
    t5k32c01-d4_rootdisk t5k32c01-d4 /dev/rdsk/c0t60A98000572D426F543457557364654Fd0s2
    t5k32c01-d4_zones t5k32c01-d4-1 /dev/rdsk/c0t60A98000572D426F5434575577746231d0s2
    t5k32c01-d1_rootdisk t5k32c01-d1 /dev/rdsk/c0t60A98000572D426F54345755727A6A44d0s2
    t5k32c01-d1_zones t5k32c01-d1-1 /dev/rdsk/c0t60A98000572D426F5434575577784A52d0s2
    t5k32c01-d3_rootdisk t5k32c01-d3 /dev/rdsk/c0t60A98000572D426F54345755732F5772d0s2
    t5k32c01-d3_zones t5k32c01-d3-1 /dev/rdsk/c0t60A98000572D426F5434575578306F66d0s2
    VCONS
    NAME SERVICE PORT
    alternate primary-vcc0@primary 5000
    NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
    t5k32c01-d1 active -n---- 5005 16 8G 0.0% 3d 16h 38m
    SOFTSTATE
    Solaris running
    MAC
    00:14:4f:f9:92:aa
    HOSTID
    0x84f992aa
    CONTROL
    failure-policy=ignore
    DEPENDENCY
    master=
    VCPU
    VID PID UTIL STRAND
    0 16 0.2% 100%
    1 17 0.0% 100%
    2 18 0.0% 100%
    3 19 0.0% 100%
    4 20 0.0% 100%
    5 21 0.0% 100%
    6 22 0.0% 100%
    7 23 0.0% 100%
    8 24 0.0% 100%
    9 25 0.0% 100%
    10 26 0.0% 100%
    11 27 0.0% 100%
    12 28 0.0% 100%
    13 29 0.0% 100%
    14 30 0.0% 100%
    15 31 0.5% 100%
    MAU
    ID CPUSET
    2 (16, 17, 18, 19, 20, 21, 22, 23)
    3 (24, 25, 26, 27, 28, 29, 30, 31)
    MEMORY
    RA PA SIZE
    0x2000000 0x212000000 8G
    VARIABLES
    auto-boot?=true
    boot-device=disk
    NETWORK
    NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
    vnet-backup-int vsw-backup-int@primary 1 network@1 00:14:4f:fb:db:97 1 3 1500 phys-state
    vnet-backup-int-alt vsw-backup-int-alt@alternate 11 network@11 00:14:4f:f8:b3:5d 1 3 1500 phys-state
    vnet-apps vsw-ora@primary 2 network@2 00:14:4f:fa:98:b7 1 8 1500 phys-state
    vnet-apps-alt vsw-ora-alt@alternate 12 network@12 00:14:4f:f9:99:18 1 8 1500 phys-state
    vnet-ora vsw-ora@primary 3 network@3 00:14:4f:fa:25:c3 1 9 1500 phys-state
    vnet-ora-alt vsw-ora-alt@alternate 13 network@13 00:14:4f:f9:00:f3 1 9 1500 phys-state
    DISK
    NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
    rootdisk t5k32c01-d1_rootdisk@primary-vds0 1 0 disk@0 primary t5k32c01-d1
    zones t5k32c01-d1_zones@primary-vds0 1 1 disk@1 primary t5k32c01-d1-1
    VCONS
    NAME SERVICE PORT
    group1 primary-vcc0@primary 5005
    Thanks for your help
    Edited by: cesar.rivero on May 17, 2010 1:23 AM

  • ACL migration Error : 1210 could not find a domain controller for domain "Test Domain" (Old Domain)

    Hi
    We are migrating from old domain to new domain. Before live migration, we are trying to check the ACE/ACL migration through SubInACL. We are running the SubInACL on a cluster, which is a member of the Old Domain (Test Domain). We are able to resolve and
    ping both Old Domain and the New domain from this cluster machine. We have created a network share on this cluster, which is accessible to all Domain Users of the Old Domain. Both Domains have two way forest level trust. we are trying to migrate
    the ACL of this share (\\ClusterMachine\testshare$) to the new domain using SubInACL. We are trying to run the below command to get it done.  
    subinacl /outputlog=C:\Users\Administrator\Desktop\Migrationlog.txt /subdirectories
    \\ClusterMachine\testshare$\*.* /migratetodomain=OldDomain=NewDomain=mappingfile.txt
    Mapping file contains : Domain Users=NewDomain_Users
    But we are geeting the Error that "1210 could not find a domain controller for domain "Test Domain". Error finding domain name : 1210 the format of the specified computer name is invalid. Current Object "\\ClusterMachine\testshare$"
    will not be processed."

    Hello,
    how in detail is DNS set up in each domain?
    Any problems when using nslookup to verify?
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

Maybe you are looking for