Configuring WLC and AP'S

Hi all, some questions
1.Do I need to put an ip on the ap manager interface?
2.does the ap manager interface go on the same subnet at the access points?
3.Im using 2 wlc's for redudancy, what special config do I need to do on them, do I need to tell each WLC what the other WLC is?
4.should I set the WLC addresses on the access points manually to avoid inter controller roaming?

1) Yes
2) Yes
3) They will participate in the same group
here are some good links:
wlc 4400 configuration
http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html
This is a great link
http://www.cisco.com/en/US/products/ps6366/prod_configuration_examples_list.html
failover example:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml
4) that depends... some people prefer to assign static ips to the APs, it really depends on your preference and how many APs.
Currently, I use dhcp with the scope split between 2 dhcp servers with a long lease

Similar Messages

  • Cisco NCS configuration backup and restore of WLC issues found

    Hi,
    I recently tested the process for a customer of defaulting a Cisco WLC to factory configuration and then restoring the configuration from Cisco NCS.  It was not seamless to say the least and I wonder if I have just gone about it the wrong way. 
    Have have set the NCS platform to configuration sync with the 5508 controllers at 04:00 every day and prior to the controller defaulting I ensured that NCS also reported that the config was in sync.
    I have also set NCS to complete a tftp backup of the controller every night 23:00 - interestingly though I have no idea where this is stored on the NCS platform ( a VM appliance ) or what it's filename is.
    Anyway my experiences where as follows:-
    1.  defaulted WLC and via serial CLI ended up at the configuration wizard.
    2.  Set the correct LAG, management IP, hostname that NCS knew this controller by.
    3.  To test things just created a dummy WLAN ( SSID ) as I assumed this would be overwritten ( big mistake ! ).
    At this point I connected the controller to the network and tried to restore the configuration from the config sync version.
    First problem - you have to remember to set up the SNMP community string you were using as it is needed by the configuration sync process.  After adding this to the controller I could push the configuration to the controller.
    Second problem - failed to add the first WLAN from the backup as I have added the temporary dummy WLAN via the wizard and NCS reported a conflict.  So had to delete WLAN ID 1 from the WLC GUI directly and then the config push no longer reported this error.
    Third problem - for some reason did not add the TACACS server details - reported the error that it could not added them.  I manually added these via a template via NCS and all was well.
    Fourth problem - all but the first WLAN was in the disabled state - had to re-enable all of the WLANs
    Fifth problem - any default items I had disabled or removed have not been saved - therefore I have removed the public and private SNMP communities - but these were still on the WLC after the restore.  I have disabled unused ports not in the LAG as they show an error in NCS - these where not disabled after the restore.
    So all in all not a very satisfactory restore process from NCS to an defaulted WLC ( ment to simulate to the customer what would be needed if they had to replace a controller due to hardware failure ).
    So - anybody like to comment on what I did wrong - is there a different / better way of achieving this ??
    Regards
    Robert

    Hello Robert,
    all the tasks you did seem to be fine for me.
    I was also wondering the process os restoring from NCS controller configuration backups ...
    If anyone else could give another method with less drawbacks, that would be appreciated, but i doubt about it.
    regards,
    Guillaume.

  • ISE 1.2 With WLC and AD

    Hi everyone,
    What is the steps and Procedure implement Wired and wireless authentication with ISE, WLC and AD for a LAB environment. currently the following are done.
    The wireless network is configured with 2 SSID (Staff and Guest) 
    Active Directory, DNS, DHCP, and  NTP configured & synced.
    ISE and AD running on C220 VMs, and WLC is 5760 Appliance.
    Please provide your thoughts and assistance.
    Regards

    You have to implement dot1x and radius between your NAD and ISE device.
    Using the switch 3850, that are the steps: 
    username RADIUS-HEALTH password radiusKey1 privilege 15
    aaa new-model
    aaa authentication login default local
    aaa authentication dot1x default group radius
    aaa authorization network default group radius
    aaa authorization auth-proxy default group radius
    aaa accounting update periodic 5
    aaa accounting auth-proxy default start-stop group radius
    aaa accounting dot1x default start-stop group radius
    !this password will be used to communicate with ISE and to verify reachability
    !between ISE and Switch
    aaa server radius dynamic-author
     client 172.16.1.18 server-key 7 radiuskey
     client 172.16.1.20 server-key 7 radiuskey
    ip domain-name lab.local
    ip name-server 172.16.1.1
    dot1x system-auth-control
    interface GigabitEthernet1/0/3
     switchport mode access
     switchport voice vlan 50
     switchport access vlan 10
     ip access-group ACL-ALLOW in
     authentication event fail action next-method
     authentication event server dead action authorize voice
     authentication event server alive action reinitialize
     authentication host-mode multi-auth
     authentication open
     authentication order dot1x mab
     authentication priority dot1x mab
     authentication port-control auto
     authentication periodic
     authentication timer reauthenticate server
     authentication violation restrict
     mab
     dot1x pae authenticator
     dot1x timeout tx-period 10
     spanning-tree portfast
    ip access-list extended ACL-ALLOW
     permit ip any any
    !the comm between radius and ise will occur on these Port
    ip radius source-interface Vlan100
    logging origin-id ip
    logging source-interface Vlan100
    logging host 172.16.1.20 transport udp port 20514
    logging host 172.16.1.18 transport udp port 20514
    ip radius source-interface Vlan100
    logging origin-id ip
    logging source-interface Vlan100
    logging host 172.16.1.20 transport udp port 20514
    logging host 172.16.1.18 transport udp port 20514
    snmp-server community ciscoro RO
    snmp-server community public RO
    snmp-server trap-source Vlan100
    snmp-server source-interface informs Vlan100
    radius-server attribute 6 on-for-login-auth
    radius-server attribute 8 include-in-access-req
    radius-server attribute 25 access-request include
    radius-server dead-criteria time 10 tries 3
    radius-server vsa send accounting
    radius-server vsa send authentication
    !defining ISE servers
    radius server ISE-RADIUS-1
     address ipv4 172.16.1.20 auth-port 1812 acct-port 1813
     automate-tester username RADIUS-HEALTH idle-time 15
     key radiusKey
    Please be sure that NTP servers and time are synchronized. 
    enable dot1X on windows machine, or using cisco NAM. 
    you can enable debugging on aaa authentication to see the events. 
    you have to create this user on ISE (RADIUS-HEALTH). 
    3850#test aaa group radius username password new-code 
    and observe the result. You are supposed to have user authenticated successfully. 
    You Must also have define these device in ISE on the radius interface.
    ip radius source-interface ..... use this interface ip address to define Ip address of the NAD device in ISE. 
    administration-->network resources -->Network Devices-->Add
    input the name
    input the Ip address for radius communication
    select the authentication settings and field the corresponding shared secret radius key
    select snmp settings and select version 2c. 
    snmp community : ciscoro
    you can customize the polling interval if you want and that all. 
    you are supposed to received message communication between your NAD and ISE. 
    After you can do the procedure for WLC device. 
    I will fill it after you have passed the first steps (3850 authentication). 

  • Problem share folder WLC and pc macbookpro

    I am doing a migration from my wireless network in the old network in the PC MacBookPro I can see shared files on the network. But when I connect to the SSID configured on the WLC and I can not see shared files on the network. I have no ACL configured on the SSID.

    Bonjour is a non-routabe multicast based service. A trick I use sometimes is to configure the WLAN to be in hreap mode if the ap is located locally to the target bonjour device.if your running in local mode, make sure they are on the same vlan and global multicast is enabled.
    Sent from Cisco Technical Support iPad App

  • WLC and WCS conflict

    Hi I am currently using 21 X WLC with N+1 Redundancy and 1X WCS with 1000++ of LAP1020. If had been observed that the antenna type and power TX had been changed with no reason. Is there any settings that may affect with AP customized Tx Power and antenna settings other than using the WCS template to push the configure to the APs instead of the WLC.

    Sorry for jumping in on the question with another question but it seemed the right place.
    I have an AIR-CT5508-25-K9 WLC and +25AP license : L-LIC-CT5508-25A.
    As far as I understand it the WLC should already have a 25AP license installed and with the adder license I should have a count of 50 APs.
    However, after installing the adder license the count is still 25.
    Could you please let me know if it's just something wrong in my reasoning or should a case be opened?
    Thank you,
    Barbara

  • Cisco wlc and steel belted radius

    we have cisco wlc controller  that have  two ssid  one for user and one for guest
    we need the  user in ssid 1 take user name and password from  user group in active directory through steel belted radiu
    please send to me any integrated guide between cisco wlc and steel belted radius
    regards

    Hi                                                      Mohammad,
    I am unaware of a specific Steel Belted RADIUS intrgration guide for the WLCs, however the configuration process on the controller will be the same:
    Cisco WLC Configuration Guide 7.0 - Configuring RADIUS:
    http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70sol.html#wp1388328
    You may wish to contact your RADIUS vendor for additional configuration steps on the server.
    Best,
    Drew

  • WLC and AP in L3

    Hello everyone
    I hope if anyone can help me.
    a Building has 3 companies (A,B and C)
    and I have one WLC
    in each company there is 3 AP
    I want to configure WLC whereas any AP in company A cant communicate to other AP in company B and C
    and the same to all companies
    I mean totally separate in IP scheme (no routing between them)
    can that done with WLC and LWAP ??
    PLZ advice

    thank you all for your reply
    I would like to ask you another question fo another scenario.
    I have one WLC installed in one subnet, let's say in the head quarter network, while the LAPs are installed in the branches and there is WAN connectivity between the HQ and the branch and OSPF routing is enabled between this WAN network. How can I do my configuration in order to register the LAPs installed in the branch with WLC installed in the HQ?
    Thanks,

  • Difference in client tables between WLC and AP controller d0

    Hello gang,
    Anyone know whether its normal to have an APs' d0/d1 controller output show clients that don't appear on the WLC's "sh client <AP>" output?
    Here's an example - 10 clients visible from a "sh client " on the controller, but 15 clients visible on AP4s "sh controller d0" debug.
    Granted the User Idle Timeout has been bumped up to 7200 seconds, but shouldn't the AP's d0/1 client table get updated if/when a client roams to another AP nonetheless? Wouldn't this otherwise cause confusion? Is the Split-MAC Split-brained?
    Thanks for your input,
    --Bruce Johnson
    (mcores2wlc1) >show client ap 802.11b mell9s1ap4
    MAC Address AP Id Status WLAN Id Authenticated
    00:40:9d:31:b0:79 130 Associated 6 Yes
    00:40:9d:34:1f:04 130 Associated 6 Yes
    00:40:9d:33:ee:04 130 Associated 6 Yes
    00:40:9d:2b:d1:6a 130 Associated 6 Yes
    00:40:9d:31:23:a3 130 Associated 6 Yes
    00:40:9d:33:e9:28 130 Associated 6 Yes
    00:40:9d:31:27:a5 130 Associated 6 Yes
    00:40:9d:33:eb:4b 130 Associated 6 Yes
    00:40:9d:31:22:1d 130 Associated 6 Yes
    00:40:9d:33:ee:cb 130 Associated 6 Yes
    (mcores2wlc1) >debug ap command "sh cont d0" mell9s1ap4
    (mcores2wlc1) >Thu Feb 26 18:54:10 2009: mell9s1ap4:
    Thu Feb 26 18:54:10 2009: mell9s1ap4: ---Clients AID VLAN Status Age Tx Mode Enc Key Rate
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.eaec 198 6 0000 0800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d30.efd1 197 6 0000 0800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.bc74 195 6 0000 2800001FF 7165/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.27a5 193 6 0000 0800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.eecb 192 6 0000 2800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.221d 190 6 0000 0800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.eb4b 186 6 0000 0800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0016.6faf.9d64 185 3 0000 0C00000FF 7186/7200 0-0 0191 200 0-10 10FC0000 06C
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.e928 177 6 0000 2800001FF 5818/7200 0-0 10111 200 0-10 10000000 016
    =>Thu Feb 26 18:54:10 2009: mell9s1ap4: 0016.6faf.9db8 176 3 0000 0C00000FF 7140/7200 0-0 0191 200 0-10 10FC0000 06C
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.23a3 174 6 0000 2800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d2b.d16a 165 6 0000 1800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.ee04 163 6 0000 0800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d34.1f04 151 6 0000 1800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
    Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.b079 147 6 0000 2800000FF 7194/7200 0-0 10111 200 0-10 10000000 016

    hi Leo,
      I tested this out, but i guess its not working as i thought it would work. I configured the backup primary controller IP and name in the global configuration of the Wireless tab of the WLC and left the AP high availability blank with no settings. I joined the AP to the WLC and show capwap client ha output on the AP shows the backup primary controller name. but if i shut down the primary controller, the AP does not join the back, it just tries to get WLC ip by renewing DHCP forever and stuck in that...   below are the outputs.. any idea why its like this ? I thot if there is no HA configured at the AP level, the global config on the controller level should take effect ?
    LWAP3-1042#sh cap cli ha
    fastHeartbeatTmr(sec)   7 (enabled)
    primaryDiscoverTmr(sec) 30
    primaryBackupWlcIp      0xA0A700A
    primaryBackupWlcName    WLC2-4402-50
    secondaryBackupWlcIp    0x0
    secondaryBackupWlcName  
    DHCP renew try count    0
    Fwd traffic stats get   0
    Fast Heartbeat sent     0
    Discovery attempt      0
    Backup WLC array:
    LWAP3-1042#
    *Apr 30 20:36:21.324: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    Not in Bound state.
    *Apr 30 20:36:31.829: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.114.49, mask 255.255.255.0, hostname LWAP3-1042
    *Apr 30 20:37:17.832: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    Not in Bound state.
    *Apr 30 20:37:28.337: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.114.50, mask 255.255.255.0, hostname LWAP3-1042
    *Apr 30 20:38:14.338: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    Not in Bound state.
    *Apr 30 20:38:24.842: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.114.51, mask 255.255.255.0, hostname LWAP3-1042
    regards
    Joe

  • 5760 WLC and 5760 HA WLC question

    Hi everyone,
    I assume this information must exist... I just cannot locate it. Customer purchasing two 5760 WLCs:
    1     AIR-CT5760-500-K9
    1     AIR-CT5760-HA-K9
    I am looking for info on how to configure these 2 WLCs to work together.  How do you inform the production WLC that a HA WLC is available to sync with? Do WLCs have to be L-2 adjacent, or will HA operate at L-3?  How does this HA setup work? etc.
    Any help would be really appreciated.

    Hi,
    Any news regarding this issue?
    We've have the same scenario:
    1     AIR-CT5760-500-K9
    1     AIR-CT5760-HA-K9
    Both running
    IOS XE 03.03.01SE
    I've activated Global AP Failover Priority in both WLC and from a total of 47 APs, i've configured 8 with Priority Critical, 7 APs with Priority High and  3 APs with Priority Medium.
    We've issued an reload to the primary WLC and it took 7 minutes for the APs recover from the Secondary to the Primary
    13:14 - reload issued on the primary WLC
    13:15 - service granted by the secondary WLC (required an shut/no shut to the "Network Status" of the radio interfaces)
    13:22 - service recovered to the primary WLC
    Edit - Forgot to mention that the priority values mentioned above didn't show much improvement in the AP recovery time...

  • [SOLVED] How to configure prosody and jitsi to work together?

    Hi,
    I want to use prosody to connect several jitsi accounts on different computers on a LAN. I have followed the Prosody page in our wiki to set up Prosody and some user accounts. The service starts and ss -tul indicates that it is listening on the expected ports. I have created the missing key and certificate files expected by the default setup and placed them in /etc/prosody/certs.
    I have created the account foo@localhost using prosodyctl adduser foo@localhost.
    In jitsi I have created an XMPP account (foo@localhost) on the same host as prosody. The account appears but it fails to connect to the server. Jitsi displays error messages on the console which indicates that the server does not support TLS connections even though these are enabled in the prosody configuration file (and lua51-sec is installed).
    I have tried numerous variations of disabling encryption in both prosody and jitsi but I either get the same error message or jitsi simply hangs while trying to connect to the server.
    So far the only thing that I've been able to find that deals specifically with prosody and jitsi is an episode of the Linux Action Show from last year that skimps on the details of the setup. The various online documentation that I've found seems to be for an older version or Prosody (e.g. Host entries in the configuration file).
    Does anyone have a similar setup working with the latest versions of Prosody and Jitsi? If so, please share your configurations.
    edit
    I went through the Prosody wiki page again today and managed to get it working. I think my problem was in misconfigured paths for the SSL server certificates in the VirtualHost section.
    Last edited by Xyne (2014-08-13 00:35:51)

    So, i tried both ways but it still didn't work.
    anrxc: i didn't know i could still prevent DNS leak without privoxy. Privoxy always blocked flash animations and videos (like youtube) here. I'll try to set up this better tomorrow when i have more time.
    By the way, after following your guide, i got this when executing /usr/bin/tor:
    Jan 10 19:29:16.993 [notice] Tor v0.2.1.21. This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
    Jan 10 19:29:16.994 [warn] Skipping obsolete configuration option 'Group'
    Jan 10 19:29:16.995 [notice] Initialized libevent version 1.4.12-stable using method epoll. Good.
    Jan 10 19:29:16.995 [notice] Opening Socks listener on 127.0.0.1:9050
    Jan 10 19:29:16.995 [notice] Opening Socks listener on 192.168.0.1:9050
    Jan 10 19:29:16.995 [warn] Could not bind to 192.168.0.1:9050: Cannot assign requested address
    Jan 10 19:29:16.995 [notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050
    Jan 10 19:29:16.995 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
    Jan 10 19:29:16.995 [err] Reading config failed--see warnings above.
    Last edited by ILoveJapaneseGirls (2010-01-10 22:00:12)

  • The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.

    We are in the process of removing a child domain from the forest and are down to two DCs. These are both Server 2008r2 sp1 servers, one physical and virtual (PDC). When I try to remove a DC (not the PDC emulator) I get the following error:
    The operation failed because:
    Active Directory Domain Services could not transfer the remaining data in directory partition DC=DomainDnsZones,DC=mydomain,DC=local to
    Active Directory Domain Controller \\V-Svr03.mydomain.local.
    The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles."
    I have checked replication with repadmin /showrepl and all connections were successful. The dcdiag /test:kccEvent test on all servers passed.
    Most DCdiag tests are successful. The only failure is on NCSecDesc when running dcdiag /test:NCSecDesc
       Testing server: Default-First-Site\DC1-DEV-OFC
          Starting test: NCSecDesc
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=hookemup,DC=local
             ......................... DC1-DEV-OFC failed test NCSecDesc
    In researching this I find "If you do not plan to add an RODC to the forest, you can disregard this error."
    We have not successfully run ADprep /rodcPrep nor do we plan on having any Read-Only DCs, so I think we can ignor this error. We did try running ADprep /rodcPrep but got an LDAP error which I can duplicate if this is important.
    Schema and Naming FSMOs are on a DC higher in the forest. RID, PDC, and Infrastructure FSMOs for the child domain are on the Virtual server (PDC).
    Any guidance on where to go from here would be greatly appreciated as I have no more hair on my head to pull.

    Ok... I ran repadmin /showreps /v again and it shows no errors
    C:\>repadmin /showreps /v
    Default-First-Site\DC1-DEV-OFC
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: b294c59f-8b46-4133-89c5-0f30bfd49607
    DSA invocationID: 1054285d-cffe-42b4-8074-e2d44adbb151
    ==== INBOUND NEIGHBORS ======================================
    CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381490/OU, 16381490/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114817/OU, 114817/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66047/OU, 66047/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098197/OU, 8098197/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    CN=Schema,CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8097482/OU, 8097482/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 65239/OU, 65239/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114149/OU, 114149/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381373/OU, 16381373/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=ForestDnsZones,DC=mydomain,DC=local
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66295/OU, 66295/PU
            Last attempt @ 2012-10-29 13:57:48 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098367/OU, 8098367/PU
            Last attempt @ 2012-10-29 13:58:13 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 115032/OU, 115032/PU
            Last attempt @ 2012-10-29 13:58:25 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381653/OU, 16381653/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
    DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114871/OU, 114871/PU
            Last attempt @ 2012-10-29 13:54:02 was successful.
    DC=DomainDnsZones,DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=mydomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 16381614/OU, 16381614/PU
            Last attempt @ 2012-10-29 13:56:52 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 66325/OU, 66325/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 8098385/OU, 8098385/PU
            Last attempt @ 2012-10-29 13:58:38 was successful.

  • Front end Backend Modeling Configuration Reporting and Extraction.

    Hi..All
    Can Any one plz explain the terms "Front end","Back end" related to Modeling,Configuration,Reporting and Extraction.
    Thanks & Regards
    Jonn
    <u>[email protected]</u>

    Hi,
    Frontend is the reporting aspect, i.e Workbooks, queries, Web reporting, Crystal reports, etc.
    Its called the frontend as that's what the users see and they don't see what goes on in the 'backend' i.e Config and Extraction, data manipulations, etc.
    Modeling is used to design the cube, ODS, etc. Also modeling concepts can be used to design frontend queries as well.
    Cheers,
    Kedar

  • BOM explosion in sales order for configurable materials and variants

    Hi,
    I have these materials:
    A: configurable material (header)
    B: variant material (header)
    C: configurable material 1 (position)
    D: configurable material 2 (position)
    E:variant material 1 (position)
    F:variant material 2 (position)
    I can in the sales order explode in this way the BOM (using SD01 application in the position type of the header material):
    1) A --> C+D
    2) B --> E+F
    while I can't make the explosion in this way: A --> EF and A --> CE
    is this possibile? I want to make an explosion of a BOM for a configurable material  and having variants material as sons, or having mix sons (one configurable and one variant)
    Thank you
    Sandra

    Hi Sandara,
    Just check the BOM in cs03 u have maintained !!! If u have maintain the variant material there in the config mat BOM with object dependencies than u can explode !!!!
    Please let me knwo if u any query and also if u elabore more than will help u out

  • UCSM 2.1 Local disk configuration policy and raid volumes

    Hi!
    If i use Any configuration as local disk configuration policy and do the raid settings directly to the RAID-cards, am i able to have two raid volumes on C-series under UCSM management?
    What i would like to do with C240M3 with 6 local disks: 2 disk raid1 and 4 disk raid0
    So i would use:
    "Any Configuration—For a server configuration that carries forward the local disk configuration without any changes."
    As UCS servers Raid guide indicates:
    "Maximum of One RAID Volume and One RAID Controller in Integrated Rack-Mount Servers
    A rack-mount server that has been integrated with Cisco UCS Manager can  have a maximum of one RAID volume irrespective of how many hard drives  are present on the server. "
    Is this paragraph limitation of GUI not able to set several volumes or hard fact without "Any configuration" workaround?

    I did some testing about this issue:
    Changed Local Disk Configuration to "Any Configuration"
    Two virtual disks can be created from Raid card's WebBIOS
    These disks are visible to RedHat Installation.
    UCSM shows Any configuration for the Storage Local Disk policy
    Actual Disk Configuration has faulty information - WebBios is the only place to check the RAID status?
    Next step: I'll do the same for the production

  • How to configure apache and weblogic in windows 2000

    i am novice,
    i want to configure apache and weblogic in windows 2000
    weblogic version is 6.1
    apache version is 2.0
    how to do?

    George,
    I would take the following 'first steps'
    1)Install Apache20 on your Windows machine following the Apache online documentation
    http://httpd.apache.org/docs-2.0/misc/tutorials.html
    2)Make sure you can 'serve up' static HTML content from your Apache Server
    3)Install Weblogic Server per our online documentation
    http://edocs.bea.com/wls/docs61/install/index.html
    4)Also, make sure you can 'serve up' both static and dynamic (e.g., JSP) content
    directly from WLS server
    5)Once you have both of the above 'sanity' checks attempt to configure a simple
    proxy by ppath or mime type via our online documentation
    http://edocs.bea.com/wls/docs61/adminguide/apache.html#103803
    Chuck Nelson
    DRE
    BEA Technical Support

Maybe you are looking for