Join configuration: 1 join to a separate master

Upon login to Plus or Viewer, as an end user (non-Adminstrator, not the Workbook creator) we get:
"Join configuration cannot be resolved. Reason: more than 1 of the detail folders has a join to sa separate master. Attempt to open the workbook failed."
What do we look for?
The workbook owner does NOT get this error.
Please help,
Karen

More info on the situation:
We have a region->state->group-> area hierarchy in the data.
The user can select Region, Region by State or State. (ie Mid-Atlantic, Mid-Atlantic by State, or Delaware, Virginia, etc) One parameter selection allowed.
We have a join from the main fact table to the lookup table by group, and one by area.
We think this is what causes the error .. but, changing this messes up the parameter selection and query output. We realize that ideally this is a compound join in one join, but earlier tires of this messed up the selection parameters.
What is the recommended way to set up such a selection list - one that crosses levels of a hierarchy?

Similar Messages

  • How to Configure ODI Console to Connect Multiple Master Repositories

    Hi,
    Can anybody help me in following,
    1. How to configure ODI Console to access Multiple Master Repositories and its corresponding Work Repository?
    2. Solutions are not supported by ODI Console? Is it possible to import scenarios as solutions in ODI Console?
    Thanks
    MT

    MT,
    1. I can only speak on my own experience in setting up the ODI console, but my understanding is that the console is configured against a single master repository - the connection details are picked up when the WebLogic server starts.  If I'm wrong, I'm sure one of the gurus will correct me.
    2. I haven't come across a way to do this - I'm using 11.1.1.5.  Aside from my initial go-live, I tend to only promote individual scenarios across environments.  For the rare occasion when I need to do a larger bulk import I'll just use ODI Studio.

  • Unable to join domain when OD Master is set up as PDC

    Hi all,
    I'm working on trying to get my OD server to authenticate our new windows vmware workstations. I have both LDAP and Kerberos set up, and everything works really well with my OS X clients, as do our Linux servers. However, I'm unable to get our windows clients authenticating. I can browse the "spidertracks" computer as well as the Samba shares, so the shares themselves are working. I'm simply unable to join our Windows 7 64Bit clients to the domain to authenticate with OD accounts. Here is what I have configured in the samba settings. Am I missing something? I've read the manual nearly 20 times, and joining the domain simply doesn't work, so I'm guessing I've missed a configuration somewhere when creating my Kerberos realm. Is there a command I can use to validate my samba settings are correctly running as a PDC?
    Thanks,
    Todd
    LDAP config dc=spidertracks,dc=local
    Kerberos Realm: SPIDERTRACKS.LOCAL
    Samba Settings
    MAIN
    Role: Primary Domain Controller
    Description: Spidertracks
    Computer Name: Spidertracks
    Domain: SPIDERTRACKS
    ACCESS
    Authentication: NTLMv2 & Kerberos, NTLM
    ADVANCED
    Wins Registration: Enable Wins Server
    DHCP Settings (on different machine, Free BSD Based)
    WINS Server: 10.0.1.11 (My OD server's IP)

    Bump:
    Rather than starting a new thread,
    I am fighting with the same thing on one of our servers, this is an issue that was fixed by the Samba guys, but I can't deploy their fix and still use OD.
    I'm starting to think that our experiment using OSX instead of linux as a server may be at an end, I keep spending a lot of effort chasing down issues that are solved months ago on linux.
    Somebody help, I dont want to be told to get rid of the shiny Mac ( or more likely bootcamp it to linux )
    --Bill

  • How to separate a single join into two separate join statement

    select PA0002NACHN PA0002PERNR PA0002VORNA KNVPKUNNR KNVPPARVW KNVPPERNR KNVPSPART KNVPVKORG KNVPVTWEG VBAKAUART
           VBAKERDAT VBAKERNAM VBAKERZET VBAKFAKSK VBAKKUNNR VBAKLIFSK VBAKSPART VBAKVBELN VBAKVKORG VBAKVTWEG VBUK~CMGST
           VBUKVBELN TVLSLIFSP
    into (PA0002-NACHN , PA0002-PERNR , PA0002-VORNA , KNVP-KUNNR , KNVP-PARVW , KNVP-PERNR , KNVP-SPART , KNVP-VKORG , KNVP-VTWEG
         , VBAK-AUART , VBAK-ERDAT , VBAK-ERNAM , VBAK-ERZET , VBAK-FAKSK , VBAK-KUNNR , VBAK-LIFSK , VBAK-SPART , VBAK-VBELN
         , VBAK-VKORG , VBAK-VTWEG , VBUK-CMGST , VBUK-VBELN , TVLS-LIFSP )
    from ( PA0002
           inner join KNVP
           on KNVPPERNR = PA0002PERNR
           inner join VBAK
           on VBAKKUNNR = KNVPKUNNR
           and VBAKSPART = KNVPSPART
           and VBAKVKORG = KNVPVKORG
           and VBAKVTWEG = KNVPVTWEG
           inner join VBUK
           on VBUKVBELN = VBAKVBELN
           inner join TVLS
           on TVLSLIFSP = VBAKLIFSK )
           where PA0002~NACHN in SP$00003
             and PA0002~PERNR in SP$00001
             and KNVP~KUNNR in SP$00004
             and KNVP~PARVW in SP$00014
             and VBAK~AUART in SP$00005
             and VBAK~ERDAT in SP$00011
             and VBAK~ERNAM in SP$00013
             and VBAK~ERZET in SP$00012
             and VBAK~KUNNR in SP$00006
             and VBAK~SPART in SP$00009
             and VBAK~VBELN in SP$00010
             and VBAK~VKORG in SP$00007
             and VBAK~VTWEG in SP$00008.

    Hi,
    1.Dont use joins.
    2.Create separate internal table and write select statement.
    Regards,
    Billa

  • Joining tables rom HR master to documents DB?

    SAP Gurus, I seek your wisdom
    I'm trying to join tables in quickviewer that show the personal information of who created the doc.(particularly the names) in my purchasing doc. reports.
    Is there a way to get data element ERNAM to link to USRID? Or some other method. Please help.

    Hi David,
    When saving documents using ArchiveLink, the actual document is saved in the Archive server and a reference link entry is saved in the link tables within SAP Basis. The link tables used are TOA01, TOA02, TOA03 or TOAHR. When saving the documents, a unique id is generated for each document, before storing the document in the archive system. This unique id is also stored in the link tables as DOCUMENT ID.
    Using ArchiveLink, you can store any kind of document like JPG, FAX, DOC, PDF...etc. Each document class would have its own size, for eg., the same file stored as JPG file would be probably of the size 150KB, but the same file when stored as BMP file would probably be of the size 2500 KB.
    ArchiveLink supports various kinds of connections to the Archive Server. You can use HTTP or RFC connection to the Archive server. Alternately, you can also store the documents in an R/3 Database repository.
    SAP provides SAP CONTENT SERVER which uses  HTTP type of connection. Depending on your business requirement, you can determine, what kind of documents you would mostly need to save. Once this has been determined, you can calculate how many documents you are planning to store approximately in a year. This would help you calculate the size of the server that you should be taking.
    For searching documents, you can use some transactions like OAAD, OADR..etc. However, please note that ArchiveLink does not support text searches within the stored documents.
    Please let me know if you should need any further information on this.
    Best Regards,
    Sindhu Sreedharan.

  • How to configure CVC automation process using SNP master data and BI customer master data

    Hi Gurus,
    How to configure CVC automation in MPOS structure technically, using SNP master data in CVC creation such as Product and location details
    and in parallel extract date from ECC to BI customer master data in DP. Where-in a APO BI cube should have only new combinations which are to be validated with ECC and existing combinations in the MPOS structure before creation of CVC in different regions of MPOS.
    Second the automation should also check certain validations of product, location and are part of SNP-ECC master data and are these new combinations.
    Could someone guide us in this process.
    Thanks
    Kumar

    Praveen,
    The short answer is to move the data into infoproviders or flat files for all of the 'characteristic-type' source data; and then copy CVCs from the infoproviders into the Planning area, probably using one or more Process Chains (program /SAPAPO/TS_PLOB_MAINTAIN).
    The long answer is that this is not a trivial undertaking; this could end up being a pretty involved solution.  If you do not have enough BW/DP expertise available locally to create this solution for you, then I recommend you consider engaging external resources to assist you.  I personally wouldn't even consider starting to work on such a solution without first knowing a lot more about the detailed business requirements, and about any existing solutions that may already in place.  An SCN forum is not really suitable for such an answer.  In my opinion, the BBP doc alone would be 20+ pages, assuming no enhancements..
    Best Regards,
    DB49

  • Can I Configure an Etherchannel from 2 Separate Modules?

    I want to setup a Gigabit channel on two separate modules, for redundancy. The channel would go from a Catalyst 6509 to a Catalyst 4006 using the 8-port Gigabit module on the Catalyst 6509 and the two Gigabit ports on the Supervisor Engine on the Catalyst 4006. For example, set port channel 3/1, 4/1

    Yes, an Etherchannel can span line cards on the Catalyst 6500 and 4000 switches. You need to configure the ports on different line cards in the same admin group to get this configuration to work.

  • Create Separate Master Rep for DEV, QA & PROD or just use Contexts

    In line with a previous question I posed on the usage of Contexts for the "ODI touted" one set of code for various environments, I'm wondering in implementation, how many architects have actually used Contexts in the place of different environments (and hence code sets) for DEV, QA and PROD.
    Example, I could have an ODI Master/Work for a DEV environment and then when I move to QA/TEST, I'll have another ODI Master/Work and another ODI Master/Work for PROD. This way, I have true change management and ODI Object Code will be locked from after it leaves the DEV environment. Export from the DEV Master/Work and Import into the QA Master/Work; as well import from QA to PROD Master/Work.
    I've been in an ODI application environment where we did just as above in order to ensure the integrity of the code set (i.e. locked after DEV).
    The other approach is to have just one Master/Work (or multiple Works for Execution or such) and then use the Contexts in the Topology to point to different physical servers. Although this allows for 1 set of code (in the previous approach when Export/Import from DEV to QA you still have to change the physical data server in QA), there's less integrity in the code set.
    So long story short, I'm just wondering what you all have done from an architecture standpoint; pros/cons and etc. Thanks for the input.

    1. One master for DEV & QA ( Multiple Work repository), One Master for prod (Execution work repository)
    Merits:
    -Easier to maintain.
    -If you need the complete project in QA without export/import of each object, solution will be the best approach to implement it. Just restore the solution in QA environment.
    -No need to take special care about the logical schema as you are using the same master repository that was in QA.
    -It will take less time to test each objects.
    -Once the testing is done promote scenarios to production.
    -The very common issue regarding id conflict will not occur frequently.
    Demerits:
    -Sharing the same topology between dev & qa will create unnecessary issues like a developer can have the privilege to change the physical dataserver details. Even if you restrict from editing/deleting, the number of logical schema will goes on increasing day by day. So here you have to have a dedicated admin who will take care of this topology part. But if I would have been there I must have given full privileges to the developers in dev env.
    -If QA env will be a work repository then you have to restrict all testers from modifying the objects or else you can only promote scenarios to QA.
    -If you have different physical connection for QA env, then security concerns may arise as the connection details going to shared between one master repository.
    2. Multiple master and work for each environment.
    Merits:
    -All teams are independent as you have different env.
    -There is nothing to be concerned about security related issues as you have different topology for different env.
    -Once the DEV team is done with the project, promote only scenarios/loadplans to PROD through QA.
    -Easier to maintain the versions as you have separate env.
    Demerits:
    -Chances of getting id conflict issues.
    -Difficult to maintain.
    -Special care must be taken to keep the logical schema name same across all env.
    Other experts also can share their experience. But the common thing for each of us is to keep production completely different in terms of work and master repository.
    Bhabani
    http://dwteam.in

  • Configure sender channel to use content master service

    Hi
    I was wondering what configurations i need to do to use the service which has been deployed using the content master studio.
    My Project Name: Text_Excel
    Service Name: Test_Excel_Serv
    Now i am not sure what are the module configuration parameters i need to use...
    Pls help...
    Dheeraj

    Hi Dheeraj -
    Assuming your on SP15 or greater, in the channel module tab, this is what you need:
    <u>Processing Sequence</u>
    Module Name: localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean  (this should come before the default (localejbs/CallSapAdapter)
    <u>Module Configuration</u>
    With localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean highlighted,
    Parameter Name: TransformationName
    Parameter Value: <your CM Service Name>
    Regards,
    Jin

  • Can I configure a new imac with separate ssd and hd

        I don't know for sure if it's been announced so this information may not be out there and I realize we are not supposed to speculate. Havinvg said that can anyone comment on whether it will be possible to configure a new iMac with both and SSD and HD drive without using a fusion drive?
       For video editing I don't think I want a fusion drive. I'm either going to get a refurb soon or wait ... and the whole fusion thing is such an unknown for video editing. If I order without more vid editing information  with regard to a fusion drive I'd probably want an SSD boot and internal.... I'd use my externals for most work but an ssd plus internal hd would be nice.
       thoughts?

    Based on the tech specs here, it appears the 27" iMac has one space for hard drive, fusion drive, or SSD, which are orderable on a build-to-order system.

  • Where can i find configuration related to documents in customer master reco

    hi,
    good morning all,
    i am creating customer master data, while creating i kept documents are mandatory option in obd2.
    after creating when i checked it is saying that documents entry is mandatory.
    but i am not able to insert any values.
    in order to insert the values where should i go and insert in SPRO.
    thanks in
    regards,
    balajit

    Hi,
    The path is SPRO>Financial Accounting (New)>Accounts Receivable and Accounts Payable>Customer Accounts>Master Data>Preparations for Creating Customer Master Data>Define Account Groups with Screen Layout (Customers)
    Select your account group
    Double click on it
    Double click on sales data
    Select Group sales or etc and double click on it
    Then change field status as you require and save it
    Regards
    Kiran

  • The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliant check cannot be completed, the server will automatically shut down in 0

    i need a help. I am new in company and have to solve this problem.
    My colleague did a migration from Small Business server 2003 to Foundation 2008, about 1 year ago. After few days, he got this error message in title. Server turn off about once a month. He worked following:
    joined new server Foundation to the Domain
    dcpromo on new Server
    migration (he said that he worked step-by-step with tutorial)
    demote on old Server SBS 2003
    disconnect old server from domain. This old is not in function now.
    New server have just 3 computer accounts. The Forest functional level is Server 2003.
    I've did dcdiag:
    C:\Users\Administrator>slmgr.vbs /dli
    C:\Users\Administrator>dcdiag
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = server2008
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\SERVER2008
          Starting test: Connectivity
             ......................... SERVER2008 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\SERVER2008
          Starting test: Advertising
             ......................... SERVER2008 passed test Advertising
          Starting test: FrsEvent
             ......................... SERVER2008 passed test FrsEvent
          Starting test: DFSREvent
             ......................... SERVER2008 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... SERVER2008 passed test SysVolCheck
          Starting test: KccEvent
             ......................... SERVER2008 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... SERVER2008 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... SERVER2008 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... SERVER2008 passed test NCSecDesc
          Starting test: NetLogons
             ......................... SERVER2008 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... SERVER2008 passed test ObjectsReplicated
          Starting test: Replications
             ......................... SERVER2008 passed test Replications
          Starting test: RidManager
             ......................... SERVER2008 passed test RidManager
          Starting test: Services
             ......................... SERVER2008 passed test Services
          Starting test: SystemLog
             A warning event occurred.  EventID: 0x8000001D
                Time Generated: 03/08/2012   09:59:45
                Event String:
                The Key Distribution Center (KDC) cannot find a suitable certificate
     to use for smart card logons, or the KDC certificate could not be verified. Sma
    rt card logon may not function correctly if this problem is not resolved. To cor
    rect this problem, either verify the existing KDC certificate using certutil.exe
     or enroll for a new KDC certificate.
             An error event occurred.  EventID: 0xC0001B61
                Time Generated: 03/08/2012   10:09:56
                Event String:
                A timeout was reached (30000 milliseconds) while waiting for the Liv
    eUpdate service to connect.
             An error event occurred.  EventID: 0xC0001B58
                Time Generated: 03/08/2012   10:09:56
                Event String:
                The LiveUpdate service failed to start due to the following error:
             ......................... SERVER2008 failed test SystemLog
          Starting test: VerifyReferences
             ......................... SERVER2008 passed test VerifyReferences
       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 : BREG
          Starting test: CheckSDRefDom
             ......................... BREG passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... BREG passed test CrossRefValidation
       Running enterprise tests on : BREG.local
          Starting test: LocatorCheck
             ......................... BREG.local passed test LocatorCheck
          Starting test: Intersite
             ......................... BREG.local passed test Intersite
    C:\Users\Administrator>
    I did nslookup:
    C:\Users\Administrator>nslookup
    Default Server:  UnKnown
    Address:  ::1
    and this:
    C:\Users\Administrator>ntdsutil
    ntdsutil: roles
    fsmo maintenance: connections
    server connections: connect to server server2008
    Binding to server2008 ...
    Connected to server2008 using credentials of locally logged on user.
    server connections: q
    fsmo maintenance: select operation target
    select operation target: list roles for connected server
    Server "server2008" knows about 5 roles
    Schema - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=BREG,DC=local
    Naming Master - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-
    Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
    PDC - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Si
    tes,CN=Configuration,DC=BREG,DC=local
    RID - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Si
    tes,CN=Configuration,DC=BREG,DC=local
    Infrastructure - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site
    -Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
    select operation target:
    Did also slmgr.vbs /dli and got:
    name:Windows Server(R) ServerWinFoundation edition
    Description: Windows operating System - Windows Server(R),
    OEM_COA_NSLP channel
    Partial product key:.......
    License Status:Licensed
    thanks for help, in advance

    I forgot to say that it is the only DC in the domain.
    and this is DNS test
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine server2008, is a Directory Server.
       Home Server = server2008
       * Connecting to directory service on server server2008.
       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BREG,DC=local,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=BREG,DC=local
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BREG,DC=local,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=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 1 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\SERVER2008
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity
             * Active Directory RPC Services Check
             ......................... SERVER2008 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\SERVER2008
          Test omitted by user request: Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Test omitted by user request: FrsEvent
          Test omitted by user request: DFSREvent
          Test omitted by user request: SysVolCheck
          Test omitted by user request: KccEvent
          Test omitted by user request: KnowsOfRoleHolders
          Test omitted by user request: MachineAccount
          Test omitted by user request: NCSecDesc
          Test omitted by user request: NetLogons
          Test omitted by user request: ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Test omitted by user request: Replications
          Test omitted by user request: RidManager
          Test omitted by user request: Services
          Test omitted by user request: SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: VerifyReferences
          Test omitted by user request: VerifyReplicas
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
             See DNS test in enterprise tests section for results
             ......................... SERVER2008 passed test DNS
       Running partition tests on : ForestDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : DomainDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Schema
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Configuration
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : BREG
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running enterprise tests on : BREG.local
          Starting test: DNS
             Test results for domain controllers:
                DC: server2008.BREG.local
                Domain: BREG.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS
                      Microsoft Windows Server 2008 R2 Foundation  (Service Pack level: 1.0)
                      is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter
                      [00000007] Intel(R) 82566DM-2 Gigabit Network Connection:
                         MAC address is 00:19:99:86:E9:62
                         IP Address is static
                         IP address: 192.168.1.250
                         DNS servers:
                            192.168.1.250 (server2008.breg.local.) [Valid]
                            127.0.0.1 (server2008.breg.local.) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: d.root-servers.net. IP: 128.8.10.90 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: BREG.local.
                         Delegated domain name: _msdcs.BREG.local.
                            DNS server: server2008.breg.local. IP:192.168.1.250 [Valid]
                   TEST: Dynamic update (Dyn)
                      Warning: Failed to add the test record dcdiag-test-record in zone BREG.local
                      [Error details: 9017 (Type: Win32 - Description: DNS bad key.)]
                      Test record dcdiag-test-record deleted successfully in zone BREG.local
                   TEST: Records registration (RReg)
                      Network Adapter
                      [00000007] Intel(R) 82566DM-2 Gigabit Network Connection:
                         Matching CNAME record found at DNS server 192.168.1.250:
                         cb30439d-35e0-4add-ae6c-e7f281295520._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         server2008.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.221dc40b-9d51-48cf-a3a3-e3daf251197f.domains._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._udp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kpasswd._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.gc._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _gc._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.pdc._msdcs.BREG.local
                         Matching CNAME record found at DNS server 192.168.1.250:
                         cb30439d-35e0-4add-ae6c-e7f281295520._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         server2008.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.221dc40b-9d51-48cf-a3a3-e3daf251197f.domains._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._udp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kpasswd._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.gc._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _gc._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.pdc._msdcs.BREG.local
             Summary of test results for DNS servers used by the above domain
             controllers:
                DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:1::803f:235              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:2d::d (d.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2d::d              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:2f::f (f.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2f::f              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:3::42 (l.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:3::42              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:ba3e::2:30              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:c27::2:30              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:7fd::1 (k.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fd::1              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:7fe::53 (i.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fe::53              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:dc3::35 (m.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:dc3::35              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 128.63.2.53 (h.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 128.8.10.90 (d.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.112.36.4 (g.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.168.1.250 (server2008.breg.local.)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                   DNS delegation for the domain  _msdcs.BREG.local. is operational on IP 192.168.1.250
                DNS server: 192.203.230.10 (e.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.228.79.201 (b.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.33.4.12 (c.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.36.148.17 (i.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.5.5.241 (f.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.58.128.30 (j.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 193.0.14.129 (k.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 198.41.0.4 (a.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.83.42 (l.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 202.12.27.33 (m.root-servers.net.)
                   All tests passed on this DNS server
             Summary of DNS test results:
    Auth Basc Forw Del  Dyn  RReg Ext
                Domain: BREG.local
                   server2008                   PASS PASS PASS PASS WARN PASS n/a  
             ......................... BREG.local passed test DNS
          Test omitted by user request: LocatorCheck
          Test omitted by user request: Intersite

  • How do i ensure the new access point is joined the controller or not

    How do i ensure the new access point is joined the controller or not

    To Verifying that Access Points Join the Controller or not there are two ways as below.
    Please go through the step by step to find the APs joined state
    When replacing a controller, you need to make sure that access points join the new controller.
    Using the GUI to Verify that Access Points Join the Controller
    Follow these steps to ensure that access points join the new controller.
    Step 1 Follow these steps to configure the new controller as a master controller.
    a. Click Controller > Advanced > Master Controller Mode to open the Master Controller Configuration page.
    b. Check the Master Controller Mode check box.
    c. Click Apply to commit your changes.
    d. Click Save Configuration to save your changes.
    Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.
    Step 3 Restart the access points.
    Step 4 Once all the access points have joined the new controller, configure the controller not to be a master controller by unchecking the Master Controller Mode check box on the Master Controller Configuration page.
    Using the CLI to Verify that Access Points Join the Controller
    Follow these steps to ensure that access points join the new controller.
    Step 1 To configure the new controller as a master controller, enter this command:
    config network master-base enable
    Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.
    Step 3 Restart the access points.

  • Nexus 5596 to join Brocade fabric

    Hi all, I tried to search but didn't find a "real" answer, it is not clear if it is possible or not...
    Problem: I always worked with homogeneous Brocade fabrics. Some days ago my company asked me if it is possible to add a Nexus 5596UB to an existing (6 switches) production Brocade fabric. I underlined production as we should not interrupt SAN traffic on joining the fabric nor we should reboot and/or reconfigure existing switches.
    I found a lot of info about "interoperability mode" on MDS switches but nothing on Nexus.
    Can someone help me? Thanks.

    According to the datasheet
    http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-618603.html
    Native interop 1,2,3 and 4 is supported !
    Therefore you are ok, and have a TAC supported configuration.
    Fibre Channel and FCoE Features (Requires Storage Services License)
    ●  T11 standards-compliant FCoE (FC-BB-5)
    ●  T11 FCoE Initialization Protocol (FIP) (FC-BB-5)
    ●  Any 10 Gigabit Ethernet port configurable as FCoE
    ●  SAN administration separate from LAN administration
    ●  FCP
    ●  Fibre Channel forwarding (FCF)
    ●  Fibre Channel standard port types: E, F, and NP
    ●  Fibre Channel enhanced port types: VE, TE, and VF
    ●  F-port trunking
    ●  F-port channeling
    ●  Direct attachment of FCoE and Fibre Channel targets
    ●  Up to 240 buffer credits per native Fibre Channel port
    ●  Up to 32 VSANs per switch
    ●  Fibre Channel (SAN) PortChannel
    ●  Native Interop Mode 1
    ●  Native Interop Mode 2
    ●  Native Interop Mode 3
    ●  Native Interop Mode 4
    ●  VSAN trunking
    ●  Fabric Device Management Interface (FDMI)
    ●  Fibre Channel ID (FCID) persistence
    ●  Distributed device alias services
    ●  In-order delivery
    ●  Port tracking
    ●  Cisco N-Port Virtualization (NPV) technology
    ●  N-port identifier virtualization (NPIV)
    ●  Fabric services: Name server, registered state change notification (RSCN), login services, and name-server zoning
    ●  Per-VSAN fabric services
    ●  Cisco Fabric Services
    ●  Diffie-Hellman Challenge Handshake Authentication Protocol (DH-CHAP) and Fibre Channel Security Protocol (FC-SP)
    ●  Distributed device alias services
    ●  Host-to-switch and switch-to-switch FC-SP authentication
    ●  Fabric Shortest Path First (FSPF)
    ●  Fabric binding for Fibre Channel
    ●  Standard zoning
    ●  Port security
    ●  Domain and port
    ●  Enhanced zoning
    ●  SAN PortChannels
    ●  Cisco Fabric Analyzer
    ●  Fibre Channel traceroute
    ●  Fibre Channel ping
    ●  Fibre Channel debugging
    ●  Cisco Fabric Manager support
    ●  Storage Management Initiative Specification (SMI-S)
    ●  Boot from SAN over VPC/EVPC

  • ESI deduction for mid joining employees

    Hi Friends
    For an employee joined in 05th Feb, master data salary is Rs.14768.77 (sum of wagetypes considered for ESI calculation)  and the actual salary calculated is Rs.12941.43.
    For the purpose of ESI deduction the calculated salary is projected for the full month and arrived at Rs.15098.34 which is higher than ESI limit Rs. 15000.
    Is there any provision to avoid this calculation, since ESI not getting deducted for the first month and from Mar-14 onwards, ESI getting deducted normally.
    regards
    Raghu.

    Hi Raghu,
    Rs.14768.77-- is this ESI Basis(/112) for Feb 2014?
    Rs.12941.43-- what is this amount/wage type?
    Rs.15098.34-- what is this amount/wage type?
    Regards
    Dixit

Maybe you are looking for