3 node networking

Hi
I need a little advice
I have migrated a 2 node 2008R2 cluster to 2012R2, so happy with myself.
However i wanted to introduce a 3rd node as we want to increase capacity. So here is the issue. Up to now the Heartbeat and live migration networks were simply nic to nic cabling. i have a NIC team on both current servers for these networks and it works
fine.
However to add the 3rd server can i continue to use this method by adding a team on the 3rd node and direct connectivity between the other 2, or do i need a 2nd or even 3rd live migration network and heartbeat network to triangulate?
I appreciate the best option is a switch, but the network guys wont let me use the core switch, so i am stuck trying to use direct cabling.
thanks
Olly

Hi Sir,
>>Up to now the Heartbeat and live migration networks were simply nic to nic cabling.
>>I appreciate the best option is a switch, but the network guys wont let me use the core switch,
I haven't seen this configuration for cluster communication .
Based on my understanding heart beat needs a physical connection to each other , that means each nodes need two connections to other two nodes  but I didn't find an article mentioned two heart beat NIC .
It seems that switch is needed .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Similar Messages

  • How to delete a node from a node network

    How do I delete a node from a node network?
    <P>
    <OL>
    <LI>Follow the instructions on page 30 of the Calendar Server (CS) 3.x Admin Guide,
    and page 62 of the CS 4.0 Admin Guide "Deleting (excluding) a Node from the
    Network".
    <LI>Shut down the Directory Server.
    <LI>Backup the LDAP directory to an LDIF file.
    <LI>Edit this LDIF file and delete references to the
    6 calendar reserved users for the node to be deleted.
    <LI>Restore the LDAP directory with this changed LDIF file.
    <LI>Run unidbfix -export -n all
    <LI>Edit the resulting remotenodes.ini
    files and delete all
    references to the node to be deleted.
    <LI>Run unidbfix -import -n all
    <LI>Start the Directory Server.
    <LI>Start the Calendar Server.
    <P>
    Note: This next step is for Calendar Server 3.x * ONLY *
    <P>
    <LI>Run unireqdump -delete
    to delete all requests to the node
    to be deleted.
    </OL>

    Divya wrote:
    Hi,
    I'm using forms6i.
    I want to delete unselected nodes from a tree
    How can it be done??
    ThanksIf you mean empty branches as unselected nodes,
    set Allow Empty Branches property to 'No' in the Trees property.

  • QMASTER hints 4 usual trouble (QM NOT running/CLUSTEREd nodes/Networks etc

    All, I just posted this with some hints & workaround with very common issues people have on this forum and keep asking concerning the use of APPLE QMASTER with FCP, SHAKE, COMPRESSOR and MOTION. I've had many over the last 2 years and see them coming up frequently.
    Perhaps these symptoms are fixed in FCS2 at MAY 2007 (now). However if not here's some ROTS that i used for FCP to compressor via QMASTER cluster for example. NO special order but might help someone get around the stuff with QMASTER V2.3, FCP V5.1.4, compressor.app V2.3
    I saw the latest QMASTER UI and usage at NAB2007 and it looked a little more solid with some "EASY SETUP" stuff. I hope it has been reworked underneath.. I guess I will know soon if it has.
    For most FCP/COMPRESSOR, SHAKE. MOTION and COMPRESSOR:
    • provide access from ALL nodes to ALL the source and target objects (files) on their VOLUMES. Simply MOUNT those volumes through the APPLE file system (via NFS) using +k (cmd+k) or finder/go/connect to server. OR using an SSAFS such as XSAN™ where the file systems are all shared over FC not the network. YOu will notice the CPU's going very busy for a small while. THhis is the APPLE FILE SYSTEM task,,, I guess it's doing 'spotlight stuff". This goes away after a few minutes.
    • set the COMPRESSOR preferences for "CLUSTER OPTIONS" to "Never copy source to Cluster". This means that all nodes can access your source and target objects (files) over NFS (as above). Failure to to this means LENGTHY times to COPY material back an forth, in some cases undermining the pleasure gained from initially using clustering (reduced job times)
    • DONT mix the PHYSICAL or LOGICAL networks in your local cluster. I dont know why but I could never get this to work. Physical mean stick with eother ETHERNET or FIREWIRE or your other (airport etc whic will be generally way to slow and useless), Logical measn leepin all nodes on the SAME subnet. You can do this siply by setting theis up in the system preferences/QMASTER/advanced tab under "Use Network Interfaces". In my currnet QUAd I set this to use BUILT IN ETHERNET1 and in the MPBDC's I set this to their BUILTIN ETHERNET.
    • LOGICAL NETWORKS (Subnet): simply HARDCODE an IP address on the ETHERNET (for eample) for your cluster nodes andthe service controller. FOr eample 3.1.1.x .... it will all connect fine.
    • Physical Networks: As above (1) DONT MIX firewire (IPoFW) and Ethernet(IPoE). (2) if more than extra service node USE A HUB or SWITCH. I went and bought a 10 port GbE HUB for about $HK400 (€40) and it worked fine. I was NEVER able to get a stable system of QMASTER mixing FW and ETHERNET. (3) fwiw using IP of FW caused me a LOAD of DISK errors and timouts (I/O errors) on thosse DISKs that were FW400 (al gone now) but it showed this was not stable overall
    • for the cluster controller node MAKE SURE you set the CLUSTER STORAGE (system preferences/QMASTER/shared cluster storage) for the CLUSTER CONTROLLER NODE IS ON A SHARED volume (See above). This seems essential for SHAKE to work. (if not check the Qmaster errors in the console.app [see below] ). IF you have an SSAFS like XSAN™ then just add this cluster storage on a share file path. NOte that QMASTER does not permit the cluster storage to be on a NETWORK NODE for some reason. So in short just MOUNT the volume where the SHARED CLUSTER file is maintained for the CLUSTER controller.
    • FCP - avoid EXPORT to COMPRESSOR from the TIMELINE - it never seems to work properly (see later). Instead EXPORT FROM SEQUENCE in the BROWSER - consistent results
    • FCP - "media missing " messages on EXPORT to COMPRESSOR.. seems a defect in FCP 5.1 when you EXPORT using a sequence that is NOT in the "root" or primary trry in the FCP PROJECT BROWSER. Simply if you have browser/bin A contains(Bin B (contains Bin C (contains sequence X))) this will FAIL (wont work) for "EXPORT TO COMPRESSOR" if you use EXPORT to COMPRESSOR in a FCP browser PANE that is separately OPEN. To get around this, simply OPEN/EXPOSE the triangles/trees in the BROWSER PANE for the PROJECT and select the SEQUENCE you want and "EXPORT to COMPRESSOR" from there. This has been documented in a few places in this forum I think.
    • FCP -> COMPRESSOR -> .M2V (for DVDSP3): some things here. EXPORTING from an FCP SEQUENCE with CHAPTER MARKERS to an MPEG2 .M2V encoding USING A CLUSTER causes errors in the placement of the chapter makers when it is imported to DVDSP3. In fact CONSISTENTLY, ALL the chapter markers are all PLACED AT THE END of the TRACK in DVD SP# - somewhat useless. This seems to happen ALSO when the source is an FCP reference movie, although inconsistent. A simple work around if you have the machines is TRUN OF SEGMENTING in the COMPRESSOR ENCODER inspector. let each .M2V transcode run on the same service node. FOr the jobs at hand just set up a CLUSTER and controller for each machine and then SELECT the cluster (myclusterA, hisclusterb, herclusterc) for each transcode job.. anyway for me.. the time spent resolving all this I could have TRANSCODED all this on my QUAD and it would all have ben done by sooner! (LOL)
    • CONSOLE logs: IF QMASTER fails, I would suggest your fist port of diagnosis should be /Library/Logs/Qmaster in there you will see (on the controller node) compressor.log, jobcontroller.com.apple.qmaster.cluster.admin.log, and lots of others including service controller.com.apple.qmaster.executorX.log (for each cpu/core and node) andd qmasterca.log. All these are worth a look and for me helped me solve 90% of my qmaster errors and failures.
    • MOTION 3 - fwiw.. EXPORT USING COMPRESSOR to a CLUSTER seems to fail EVERY TIME.. seems MOTION is writing stuff out to a /var/spool/qmaster
    TROUBLESHOOTING QMASTER: IF QMASTER seems buggered up (hosed), then follow these steps PRIOR to restarting you machines.
    go read the TROUBLE SHOOTING in the published APPLE docs for COMPRESSOR, SHAKE and "SET UP FOR DISTRIBUTED PROCESSING" and serach these forums CAREFULLY.. the answer is usually there somewhere.
    ELSE THEN,, try these steps....
    You'll feel that QMASTER is in trouble when you
    • see that the QMASTER ICON at the top of the screen says 'NO SERVICES" even though that node is started and
    • that the APPLE QMASTER ADMINSTRATOR is VERY SLOW after an 'APPLY" (like minutes with SPINNING BEACHBALL) or it WONT LET YOU DELETE a cluster or you see 'undefined' nodes in your cluster (meaning that one was shut down or had a network failure)..... all this means it's going to get worse and worse. SO DONT submit any more work to QAMSTER... best count you gains and follow this list next.
    (a) in COMPRESSOR.app / RESET BACKGROUND PROCESSES (its under the COMPRESSOR name list box) see if things get kick started but you will lose all the work that has been done up to that point for COMPRESSOR.app
    b) if no OK, then on EACH node in that cluster, STOP the QMASTER (system preferences/QMASTER/setup [set 0 minutes in the prompt and OK). Then when STOPPED, RESET the shared services my licking OPTION+CLICK on the "START" button to reveal the "RESET SERVICES". Then click "START" on each node to start the services. This has the actin of REMOVING or in the case where the CLUSTER CONTROLLER node is "RESET" f terminating the cluster that's under its control. IF so Simply go to APPLE QMASTER ADMINISTRATOR and REDFINE it. Go restart you cluster.
    c) if step (b) is no help, consult the QMASTER logs in /Library/Logs/Qmaster (using the cosole.app) for any FILE MISSING or FILE not found or FILE ERROR . Look carefully for the NODENAME (the machine_name.local) where the error may have occured. Sometimes it's very chatty. Others it is not. ALso look in the BATCH MONITOR OUTPUT for errors messages. Often these are NEVER written (or I cant find them) in the /var/logs... try and resolve any issues you can see (mostly VOLUME or FILE path issues from my experience)
    (d) if still no joy then - try removing all the 'dead' cluster files from /var/tmp/qmaster , /var/sppol/qmaster and also the file directory that you specified above for the controller to share the clustering. FOR shake issues, go do the same (note also where the shake shared cluster file path is - it can be also specified in the RENDER FILEOUT nodes prompt).
    e) if all this WONT help you, its time to get the BIG hammer out. Simply, STOP all nodes of not stopped. (if status/mode is "STOPPING" then it [QMASTER] is truly buggered). DISMOUNT the network volumes you had mounted. and RESTART ALL YOUR NODES. Tis has the affect of RESTARTING all the QMASTERD tasks. YEs sure you can go in and SUDO restart them but it is dodgy at best because they never seem to terminate cleanly (Kill -9 etc) or FORCE QUIT.... is what one ends up doing and then STILL having to restart.
    f) after restart perform steps from (B) again and it will be usually (but not always) right after that
    LAstly - here's some posts I have made that may help others for QMASTER 2.3 .. and not for the NEW QMASTER as at MAy 2007...
    Topic "qmasterd not running" - how this happened and what we did to fix it. - http://discussions.apple.com/message.jspa?messageID=4168064#4168064
    Topic: IP over Firewire AND Ethernet connected cluster? http://discussions.apple.com/message.jspa?messageID=4171772#4171772
    LAstly spend some DEDICATED time to using OBJECTIVE keywords to search the FINAL CUT PRO, SHAKE, COMPRESSOR , MOTION and QMASTER forums
    hope thats helps.
    G5 QUAD 8GB ram w/3.5TB + 2 x 15in MBPCore   Mac OS X (10.4.9)   FCS1, SHAKE 4.1

    Warwick,
    Thanks for joining the forum and for doing all this work and posting your results for our benefit.
    As FCP2 arrives in our shop, we will try once again to make sense of it and to see if we can boost our efficiencies in rendering big projects and getting Compressor to embrace five or six idle Macs.
    Nonetheless, I am still in "Major Disbelief Mode" that Apple has done so little to make this software actually useful.
    bogiesan

  • Users not able to see remote users on the node network

    Users that belong to one node are not able to see users in another calendar
    server node. Both calendar servers are pointing to the same directory server.
    Some errors that occur in the log files:
    DEXOTEK ERRCODE Ox13608 -> SchedBaseOpen: Section name too long
    DEXOTEK ERRCODE Ox13608 -> OpenConnection: SchedBaseOpenOnHost
    And when uninode -cws nodeID is run, it does not report being able to see all
    the users and resources on the remote nodes.
    uninode: connected to hostname.net.xxx.com, node 10000
    directory of items: 10 (USERS = 10/RESOURCES = 0)
    CONNECTION EX AV Q-SIZE IN-PROCESS IMPORT-DIR
    (10000)->xxxxxx.xxx.com(10001) 2 2 0 0 370 (U=370/R=0)
    Here is the nodes.ini file:
    + H=xxxxxxx.xxx.com/N=10000
    + H=xxxx.xxx.com/N=10001
    all=2
    There is a reported bug, that 16 chars is max on domain names for the nodes.ini
    file, which means that you need to change that file and use:
         a) an alias that can be resolved on the network with either DNS or local
         host files
         b) use the IP address.
    As documented in the release notes, here is the procedure on how to modify the
    hostname when it is too long. Or how to modify the hostname for any reason.
    Fix for long host names problem
    If the fully qualified domain name for your network exceeds 16 characters, it
    will be necessary to shorten the host name of all the servers in the Calendar
    Server network . These instructions must be carefully followed to avoid causing
    problems with the network. Ensure that the procedure is applied to ALL nodes in
    the Calendar network.
    1) The following procedure should be carried out on each server in the
    Calendar network:
    a) Bring the Calendar services down.
    % unistop -y
    b) Run the unidbfix command in export mode.
    % unidbfix -export -n node-id
    This will create a remotenode.ini file for each node on the server. The file is
    located in the node's perm directory.
    Example:
    If you have two nodes on the server ROCK, node 1(in N1) and node (in N2), the
    files are:
    /users/unison/db/nodes/N1/perm/remotenode.ini
    /users/unison/db/nodes/N2/perm/remotenode.ini
    The remotenode.ini file will look something like this:
    [1]
    RN_NUMCONNECT = 2
    RN_SURNAME = "unison"
    RN_GIVENNAME = "unison"
    RN_ORGUNIT1 = "uni2"
    RN_ORGUNIT2 = "openmail"
    RN_ORGANIZATION = "ABC Corp"
    RN_ACCESSMETHOD = 2
    RN_SERVICENAME = "unieng"
    RN_HOSTNAME = "rock"
    [2]
    RN_NUMCONNECT = 2
    RN_SURNAME = "unison"
    RN_GIVENNAME = "unison"
    RN_ORGUNIT1 = "uni4"
    RN_ORGUNIT2 = "openmail"
    RN_ORGANIZATION = "ABC Corp"
    RN_ACCESSMETHOD = 2
    RN_SERVICENAME = "unieng"
    RN_HOSTNAME = "rock"
    2) Once you have run unidbfix in export mode on all the servers, proceed as
    follows:
    a) Compare the remotenode.ini files and verify that the entries are the
    same. In each file, you will note that an entry for the local node is not
    included.
    b) Edit one of the files (on any of the servers). This file will be
    referred to as the master file. Add the appropriate entries for the
    local node (copy the section from one of the other files). Modify the
    RN_HOSTNAME in each of the sections of the master file to shorten the
    name.
    c) Copy the master file in the perm directories of each node on all the
    servers.
    3) Once the master file is in the perm directory of all the nodes, proceed as
    follows on each server:
    a) Run the unidbfix command in the -import mode.
    % unidbfix -import -n node-id
    b) Edit the nodes.ini file on the hub server and make the same changes to
    the host names. You do not need to apply the changes.
    c) Edit the [UTL] section of the /users/unison/misc/unison.ini file and
    change the host name.
    d) Start up the services.
    % unistart
    4) After all the changes have been made, run the uninode -cws all and
    uninode -snc all commands and verify that the results are accurate.

    See this:
    http://docs.info.apple.com/article.html?path=Mac/10.6/en/8203.html
    You should then see your pcs listed in Finder's sidebar under the shared section.
    Regards

  • Cluster node networking

    I have five node Windows Server 2008 R2 Hyper-V cluster. I put one node to Maintance mode and all VMs migrated to other hosts. I pulled out LAN cables form that node for testing (one out, waited a litte, put it back and pulled second and so on) and put
    them right back on.
    After that I had a lot of cluster errors and some VMs restarted.
    I have put many times nodes on maintance mode and restarted / shut down them and never had any cluster problems. Why did I have now when I pulled out LAN cables?

    Hi antesl,
    The
     failover behavior occurs because the cluster node has detect the cluster resource or node fail, such as network, storage, please refer the following related KB to confirm there have no potential single point failure configuration in your
    cluster.
    Failover Cluster
    http://msdn.microsoft.com/en-us/library/ff650328.aspx
    Failover Cluster Step-by-Step Guide: Configuring the Quorum in a Failover Cluster
    http://technet.microsoft.com/zh-cn/library/cc770620(v=ws.10).aspx
    How a Server Cluster Works
    http://technet.microsoft.com/en-us/library/cc738051(v=ws.10).aspx
    HYPER-V 2008 R2 SP1 Best Practices (In Easy Checklist Form)
    http://blogs.technet.com/b/askpfeplat/archive/2012/11/19/hyper-v-2008-r2-sp1-best-practices-in-easy-checklist-form.aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Hyper-v Physical SAN 2 Node network: Best practis

    Hi, I have been reading alot of articles and guides on how to set up this correct! all of the guides are driffrent.
    in my system:
    2 X server, they have 4 nics Gigabit each and 2 FC card each.
    1X SAN , 2 FC controller, with 2 connections points each ( 2 for each server)
    Whats the best practis for setting this up. The FB wil be connected directly to the servers.
    nic team 2 of the gigabit nics to live migratin and 2 For externaly and the rest over FB?

    Hi Martinbt,
    For the details configuring of FC storage , I would suggest you to contact the storage vendor .
    The goal is to create a shared LUN for each cluster node , please refer to following link regarding storage requirement :
    http://technet.microsoft.com/en-us/library/jj863389.aspx
    Also :
    http://technet.microsoft.com/en-us/library/cc732181(v=WS.10).aspx
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • I am upgrading to Calendar Server 4.0 on NT with more than 9 nodes (or I already have) and my server won't start

    I am upgrading to Calendar Server 4.0 on NT with more than 9 nodes
    (or I already have) and my server won't start.
    <P>
    The steps are the same whether you have already upgraded or are about to.
    <P>
    Calendar Server 4.0 on the Windows NT platform can only support up to nine
    nodes on one server, while 3.51 supported up to 14. If you have a Calendar
    Server 3.51 with more than 9 nodes that you want to upgrade to Calendar Server
    4.0, Netscape recommends that you migrate the extra nodes to another Calendar
    Server 3.51 on another Windows NT system. To accomplish this:
    <OL>
    <LI>Install Calendar Server on another Windows NT machine and configure it to
    use the same directory server as your current Calendar Server.
    <LI>Stop and backup your current Calendar Server.
    <LI>Individually zip up the node directories you want to move to the new
    server. (drive:\unsers\unison\db\Nx
    where "x" is the number of the node you want to use.)
    <LI>Stop the new Calendar Server.
    <LI>Unzip the files into the new Calendar Server in the same place as they
    were on the old server.
    <LI>Edit the unison.ini
    file on the new server to add the nodes you have just migrated.
    <LI>Edit the unison.ini
    file on the old server to remove the nodes you have moved to the new server.
    <LI>Edit the nodes.ini
    file on the old server to remove the nodes you just moved and then add them
    with the new hostname. Keep in mind that you will only be able to modify the
    node network from the old host.
    <LI>Run unidbfix -export
    on both servers for all nodes.
    <LI>Edit the remotenodes.ini
    file on both servers to reflect your node topology.
    <LI>Run unidbfix -import
    to import the changes into the node databases.
    <LI>Run unidbfix -c,
    then -f,
    then -c
    again on both servers for all the nodes.
    <LI>If you don't get any errors, run uninode -test all
    to test if your nodes connections are set properly. If they are not, <B>do not</B>
    start either of the servers; instead, fix the errors and try again.
    <LI>Start both servers.
    <LI>Log in and check to see if you can see people on remote nodes.
    <LI>Notify the users on the moved nodes of their new calendar host.
    <LI>If you did this in preparation of an upgrade, you can now run the upgrade to
    4.0 since both servers contain fewer than 9 nodes.
    </OL>

    Use Disk Utility whihc is in the Utilities Folder.
    Select your Boot Disk on the left.
    Select Verify Permissions
    If any errors the do Reapir permissions.
    You might have to repeat the process.
    see this:
    Steve

  • Mock RFP for SUN network management tool, desperate 4 help, just need specs

    OK, I have a project that in essence is a mock Request for Proposal (RFP), I play as an intern, & our instructor roleplays the manager we need to convince. The different network management tools that were available were for example; HP Openview, Cisco Works, Sniffer....& I of course chose SunNet. We need to gather information on the tool, then turn around & design a relatively simple network from the specs that were given, & finally discuss how the management tool's abilities could benefit the (mock) company...power point presentation & all.
    Here it is from the homework sheet given to us...."These products will need to be useful in a 5000 node network that has four main locations that are primarily Ethernet. There is a legacy 100 nodes of Token Ring attached to a mainframe. Cisco or Foundry routers connect the Four main locations, with swiches employed. Other connections to these sites are done via DSL or ISDN. Additional considerations are wireless communications, VOIP & Content delivery systems.
    I know this is a lot & I'm not asking for someone to do all this for me, just simply provide any information you know about Enterprise management tools 2.0 or 3.0,or anything you may feel better suits my needs, as the links I have surfed about them give little to nothing about specifics that I need to make any argument. If you have any links send them...if you have anyting in hard copy I will pay for postage... I need to get this done & have little time as I go to school & work full time at Motorola (but only as a contractor), so I'm starting to choke & need help....any u can give is so very appreciated....& sorry to make this request a publishable novel here on the board, but thats what it is. Thanks again......Mark

    A good solution. Liked it very much. Can you please make it a technet blog for others.
    [email protected]

  • Cant configure the node of my Integration Gateway

    So I've been trying to get web services exposed from my test PeopleSoft Installation so that they can be used by another PeopleSoft Installation. After some reading and searching I found that I have to configure the Integration Broker in order to do that. From there I've been trying for a while now (unsuccessfully as you can imagine) to configure the Integration Gateway of my PeopleTools installation. Right now I can ping my Integration Gateway which comes back with...
    PeopleSoft Integration Gateway
    PeopleSoft Listening Connector
    Tools Version : 8.53
    Status:ACTIVE
    and from there I can load the connectors, of which there are 11 different ones. After that I go to "Gateway Setup Properties", log in, and from there I have everything filled out with the following...
    Gateway Default App. Server_
    App Server URL: <the machinename>:<the port#>
    User ID: PS
    Password: <the password>
    Tools Release: 8.53
    Domain Password: <none>
    Virtual Server Node: <none>
    PeopleSoft Nodes_
    Node Name: PSFT_HR
    App Server URL: <the machinename>:<the port#>
    User ID: PS
    Password: <the password>
    Tools Release: 8.53
    Domain Password: <none>
    After that, I try to ping the node but it always errors with the following and I have no idea why...
    PeopleSoftTargetConnector - The appserver may be down.  Check Appserver URL or Domain Password.
    The problem is that I know I have the right URL and that the AppServer is running because I can see it's status in Command Prompt after running PSADMIN.EXE and navigating to the status of the server (not to mention I'm able to log into it). I've also looked at the "Configuration Status" in "Main Menu > PeopleTools > Integration Broker > Integration Network" and got checks on "Gateway Configured" and "Domain Active" but there's an X next to "Node Network Not Configured" which I'm not sure why it's there so if somebody could explain that to me, that'd be really helpful.
    So from "Node Network", I can see all the nodes and can see the node that I'm trying to use for the Integration Gateway, "PSFT_HR", that has checks in the boxes under everything except "Remote Gateway Node". After I click on the PSFT_HR node I can see the "Node Definitions" tab that has the Authentication set to "Password", the password set to what I'm entering with the "Gateway Setup Properties", the "Default User ID" set to "PS" and everything after that (Hub Node, Master Node, etc.) is blank. The check-boxes next to "Default Local Node", "Local Node", "Active Node", and "Segment Aware" are checked.
    In the "Connectors" tab I've tried pinging the node but came up with the same error from before. Also, towards the bottom there's a line that says "This connector does not have properties. Use Gateways Page to setup." where I log in to the "Gateway Setup Properties" again, the same info is used from before, and pinging the node gives the same error. As for the other tabs "Portal", "WS Security", and "Routings" I haven't done anything with them as I never read anything that said I needed too.
    Also, as a side note, every time I try to ping the node the application stops responding even after I click cancel or try to click the "x" on the window. I cant do anything until it times out and gives me the error so if somebody could tell me how to change that or stop it from happening, that'd also be really helpful in saving time with troubleshooting this issue
    I hope this wasn't too long with TOO MUCH information (or quotation marks) but I thought I'd get everything I've got right now out the way since I've tried a lot of different things and may get some suggestions that I've already found/tried up until now. I feel like it's something small that I'm missing (because that's always the case) so hopefully one of you can remedy my situation.
    Thanks a lot for any help/suggestions (even if I've tried them, but I'll try them again in case something changes because computers work that way :/ ).
    Edited by: 1006417 on May 17, 2013 10:59 AM
    Fixed the typos with "machinename:port#" to fit the overall naming convention I used.

    Since you didn't provide the "machinename" I'm wondering if that's your problem... you mention hanging while pinging... that sounds like name lookup or port connectivity problems, as if the gateway is waiting for something to time out in that arena. For communicating to yourself, depending on your config, that setting should match exactly whats in the <PS_HOME/PS_CFG_HOME>/webserv/peoplesoft/applications/peoplesoft/PORTAL.war/WEB-INF/psftdocs/ps/configuration.properties psserver line. Now if you created a domain just for PUBSUB it would need to match the jolt port for that domain (not the WSL). Since your logging in online already, we know the configuration.properties file has a good value, if your trying a different domain, I'd try switching back to using your domain for servicing online requests and try again.
    I recommend looking at Nicolas's write up on this topic, it's very detailed.
    http://gasparotto.blogspot.com/2013/05/integration-network-workcenter-853.html you may need to reference his 8.52 version for some pre-reqs as well but the link is in the 8.53 one. Also look for answers in the log file <PS_HOME/PS_CFG_HOME>/webserv/peoplesoft/applications/peoplesoft/PSIGW.war/errorLog.html (if you took default weblogic domain name). I just went through this process on a fresh demo 8.53 demo install and was able to start pinging the node after only a few steps. they were,
    1. define the gateway
    2. load the connectors
    3. define the default and additional node
    4. verified the PS user was able to logon (originally the password was expired)
    5. set the auth type to Password for the node I was using.
    6. success on ping, interestingly enough I didn't even have PUBSUB processes running yet, node network and active domain both show not configured at this time
    On your node network not getting the green check, look on the Node Network status page just below the title, there is a check box for Secure Keystore Value Defined. Is that checked? If not it needs to be. You probably need to set the secureFileKeystorePassword to your keystore password. The default is still password, you can change this from the Advanced Properties Page link of the Gateway Setup Properties page. Use the encryption tool because the password can't be clear text, it has to be saved encrypted to work. Then go back to the node network page and see if it's cleared up. I mentioned this briefly in a write I did on Unified Navigation http://remotepsadmins.com/2013/03/04/peoplesoft-unified-navigation-with-peoplesoft-applicatations-portal-interaction-hub. Nicolas's 8.52 write up has screenshots and such though he does it prior to showing that it will prevent configuration from passing. I've also seen in properly configured systems you may need to just save this page without changes to populate some data, but that was on upgrading to 8.52, i would expect 8.53 would not need that.
    continuing on, I did exactly what I just mentioned, and I've got a configured node network.
    i just bounced the domain, adding the PUB/SUB servers, and activating them on the Domain Status page. I've now got green lights across the board and I can still ping successfully. I used no domain password, but I also verified that none was set in the psappsrv.cfg file. I just hit the Network Integration Status button on my system and got the Status check successful message.
    Let us know how it goes.
    Edited by: RCC on May 17, 2013 1:13 AM
    Fixed a typo and changed a sentence to make it more clear

  • Failover Cluster Manager - Partioned Networks Server 2012

    Hello,
    I have a DR cluster that I am trying to validate. It has 3 nodes. Each has a teamed vEthernet adapter for Cluster Communications and Live Migration. I can start cluster service on 2 of the 3 nodes without the networks entering a partioned state. However,
    I can only ping the I
    Ps for those adapters from their own server . Also, It doesn't matter which 2 nodes are brought up. Any order will produce the same results. Validation gives the following error for connections between all nodes:
    Network interfaces DRHost3.m1ad.xxxxxx.biz - vEthernet
    (vNIC-LiveMig) and DRHost2.m1ad.xxxxxx.biz - vEthernet (vNIC-LiveMig) are on
    the same cluster network, yet address 192.168.xxx.xx is not reachable from
    192.168.xxx.xx using UDP on port 3343.
    Update: I have created a specific inbound rule on the server firewalls for port 3343. The networks no longer show as partitioned. However, I still receive the same errors about communication on port 3343 to and from all nodes on the LiveMig and ClustPriv
    networks. Any help would be appreciated.
    Brian Gilmore Lead IT Technician Don-Nan Pump & Supply

    Windows IP Configuration
       Host Name . . . . . . . . . . . . : DRHost1
       Primary Dns Suffix  . . . . . . . : m1ad.don-nan.biz
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : m1ad.don-nan.biz
    Ethernet adapter vEthernet (VM Public Network):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 14-FE-B5-CA-35-6C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::609a:8da3:7bce:c32f%31(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.9.113(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.9.1
       DHCPv6 IAID . . . . . . . . . . . : 1091894965
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : 192.168.9.21
                                           192.168.9.23
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter vEthernet (vNIC-ClusterPriv):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-14
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::2481:996:cf44:dc3d%32(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.108.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1258298840
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (vNIC-LiveMig):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #4
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-15
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::f884:a35d:aa43:720e%33(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.109.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1358962136
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI3 - iSCSI1:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #49
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI4 - iSCSI2:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #50
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3E
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.23(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (VM Public Network):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 14-FE-B5-CA-35-6C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::609a:8da3:7bce:c32f%31(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.9.113(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.9.1
       DHCPv6 IAID . . . . . . . . . . . : 1091894965
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : 192.168.9.21
                                           192.168.9.23
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter vEthernet (vNIC-ClusterPriv):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-14
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::2481:996:cf44:dc3d%32(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.108.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1258298840
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (vNIC-LiveMig):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #4
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-15
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::f884:a35d:aa43:720e%33(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.109.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1358962136
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI3 - iSCSI1:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #49
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI4 - iSCSI2:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #50
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3E
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.23(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : DRHost3
       Primary Dns Suffix  . . . . . . . : m1ad.don-nan.biz
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : m1ad.don-nan.biz
    Ethernet adapter vEthernet (VM Public Network):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : D0-67-E5-FB-A2-3F
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::9928:4d4f:4862:2ecd%31(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.9.115(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 192.168.9.119(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.9.1
       DHCPv6 IAID . . . . . . . . . . . : 1104177125
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-3C-E0-D0-67-E5-FB-A2-43
       DNS Servers . . . . . . . . . . . : 192.168.9.21
                                           192.168.9.23
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter vEthernet (vNIC-ClusterPriv):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-18
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::3d99:312c:8f31:6411%32(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.108.33(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1258298840
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-3C-E0-D0-67-E5-FB-A2-43
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (vNIC-LiveMig):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #4
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-19
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d859:b18a:71d6:8cef%33(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.109.33(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1358962136
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-3C-E0-D0-67-E5-FB-A2-43
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI3-iSCSI1:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #49
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-60
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.26(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI4-iSCSI2:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #50
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-62
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.27(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Brian Gilmore Lead IT Technician Don-Nan Pump & Supply

  • More information on configuring node connections.

    In the Netscape Calendar Server Admin Guide chapter on Managing a Node
    Network, there is not sufficient information on configuring SNC connections.
    The example provided shows "all:2" with no information on why 2 is a good number
    for the example case. Other examples demonstrate increasing the number of connections
    for specific nodes with no information on when this is appropriate.
    <P>
    We have configured our network with all:2, but we need documentation that details
    how this number should be determined.
    <p>
    Two connections is the minimum in cases where there is one
    node configured on each server. The unicwsd requires one connection for processing
    of remote node requests and there should be at least one additional connection available
    to be used by the clients.
    <p>
    Depending on how much traffic there is between nodes, two connections
    might not be sufficient. The 'uninode -snc all' output should give you an
    idea if there are not enough connections configured. An example of the output
    follows:
    <p>
    uninode: connected to server1, node 10000
    <br>Last reset: 29/6/99 13:00:51
    PST8PDT
    <br>----------------------------------------------------------------------------
    <br><b>CONNECTION
    EX CO AV US LOST RETRY QUEUE CANCEL CHECK GRANTED</b>
    <br>----------------------------------------------------------------------------
    <br>(10000)->server2(10001) 2
    2 2 0
    1
    0
    0
    0
    36
    <br>(10000)->server3(10002) 2
    2 2 1
    0
    0
    0
    5
    126
    <br>(10000)->server4(10003) 2
    2 2 2
    0
    1 91
    805
    22
    <br>(10000)->server5(10004) 2
    2 2 0
    0
    0
    0
    0
    181
    <br>----------------------------------------------------------------------------
    <p>In the example above, there are not enough connections available from
    server1 to server4. <b>"US"</b> indicates that there were two connections
    used at the time the uninode -snc all was run. <b>"QUEUE" </b>indicates that
    there is one unieng process currently waiting for a free connection. <b>"CANCEL"
    </b>means that there were x number of processes that did not get a connection, and
    <b>"CHECK"</b> indicates the number of times a process had to retry before the request
    for an snc connection was either granted or canceled. <b>LOST, QUEUE,
    CANCEL, CHECK and GRANTED</b> are values that are reset when the unisncd
    is shut down, or when 'uninode -reset' is run.
    <p>
    <b>Note:</b> In cases where there is more than
    one node configured on one server, the node connections on that server going <b>to</b> the
    other nodes are pooled. That means that any process on that server could use any snc
    connection going to a node. In these cases the number of connections
    configured could even be as low as all:1. Again, this depends on usage,
    and might be subject to fine-tuning.

    Hi,
    you have to enable this additional measurements by executing
    x_cons <dbname> time enable
    Kind regards
    Holger

  • Connecting nodes with uninode -apply is not taking affect

    Connecting nodes with uninode -apply
    is not taking affect.
    <P>
    There are two problems with the utility uninode. They address different issues
    and require different workarounds. Please review carefully.
    <P>
    <OL>
    <LI>Applying changes to a nodes.ini
    file using uninode where there is a mixture
    of + and - nodes.
    <P>
    There is a problem with uninode where the flag -ALL doesn't completely update
    all of the remote node information. If you are removing a node from a node
    network, keep in mind that it is really a two step process: <P>
    1)Connect to all "+" nodes and remove the "-" node from each of their databases.
    2)Connect to the "-" node and remove the "+" nodes from that database.
    <P>
    The best possible workaround is to run uninode -apply ALL followed by
    uninode -apply all.
    <P>
    <LI>Applying changes to a nodes.ini
    file using uninode where there are special
    rules of node connections (e.g. A->B: +1, etc.).
    <P>
    With this you are forced to use unidbfix -export
    to generate your remotenodes.ini
    file, and then you must manually edit this file as required. Run
    unidbfix -import to
    update the remotenode.dat file.
    <P>
    Run unidbfix -export
    and then unidbfix -import
    to update all the remote nodes
    with the new information.
    </OL>

    HI All,
    I've used the OITM along with the ITM1 and I still receive the "Updated Successful" message but no changes.
    I created another pricelist within SAP B1 Client and updated the prices within that pricelist and it worked just fine.
    I noticed when I queried everything from OPLN that the pricelists that I am trying to import have a different value for "Data Source" which is equal to O, I copied these price lists with Copy Express. The pricelist I created within SAP B1 Client has a Data Source = "I".
    I've included the OITM and ITM file I used which was returning a successful result but no change.
    ITM1
    ParentKey     LineNum     PriceList     Price     Currency
    ItemCode     LineNum     PriceList     Price     Currency
    85108     25     26     55.00     $
    OITM
    ItemCode
    ItemCode
    85108

  • Sharing files over a home network...

    I have a 2 year old iMac sitting in my basement.. I use it, and it is currently home to a ton of photos, videos and sound files (Logic as well as itunes). This week I plan on getting a Macbook to tootle with on the main floor (the basement is cold. ;))
    I would love to be able to share files (and back them up as well.. kinda a nother issue).
    As it stands right now, I have a 250 GB external drive which is backing up the iMac (but has hit it's limit).. need more space.
    in addition I have a D-Link DLR 655... great little router. I believe it has Network capability in that I think through something called SharePort it can help you share files across a network.. no idea how.
    So, yeah, that's about it.. anyone have any good tips in terms of building out a comprehensive backup system in conjunction with a file sharing capability across two macs (and maybe even a PC or two) across my home network?
    Finally, how would that even work.. let's say I have an image on the imac, when I open it on the macbook, would I see it in iPhoto?
    Lotsa questions.. thank you so much.
    Jay.

    Hi
    Its not that obvious from the supplied information if you're talking about OSX Server? Perhaps your question might get more attention if you posted here:
    http://discussions.apple.com/category.jspa?categoryID=235
    Which is the main Leopard Forum. You could also look here:
    http://discussions.apple.com/forum.jspa?forumID=599
    Click 'more options' in the Search field, select All, Last Year and key in 'networking'. Should reveal something? This article might help:
    http://support.apple.com/kb/HT1433
    What you're asking is simple enough. Connect all of your nodes (network devices; eg: macs, pcs, printers etc) to a switch or router or combination of the two. Depends on how many nodes you have. Wired (Ethernet) or Wireless will do. Make sure the router is providing IP addresses. Basically is its built-in DHCP Service switched on? By default most of them are. Once that's done and you've verified they can all access the internet, enable File Sharing. System Preferences > Sharing for the Macs and for the PCs right click the 'C' drive > Properties > Sharing.
    Backup is a vast subject and its difficult to be concise. A lot depends on your skill set, means, budget and location. You could search this and the XServe/XServe RAID Forums as it has been discussed many times. A basic principle is to make sure you can effectively restore what you backup. Most people forget this when implementing an effective backup strategy. To start you off purchase a large enough external hard drive. Connect to all your macs and simply drag/drop what you want. If you have Leopard use Time Machine. For the PCs use something appropriate. Photos & Music can be transferred from mac to mac by simply enabling the options in the applications themselves. ITunes > Preferences > Sharing: Look for Shared Libraries; Share this Library. When you launch iPhoto hold down the option key. It's fairly obvious after that.
    If you double-click on an image presented in the Finder (shared) on one mac then your mac will use whatever application it can find that it thinks can handle the file. For image files that could be Preview or Quicktime or if you have it installed an image editing application such as Photoshop. You can even define which application handles which type of file by control-clicking on the file itself and selecting 'Open With'. This is fairly basic 'how to use your mac' stuff which you should know?
    Tony

  • UCCX 8.5: first Node cable disconnect results

    After disconnecting the first Node network cable :
    - Forward busy/unregistered/failure triggers only after like 3-6 minutes. In the meantime we get silence.
    - CAD get unresponsive for about 2-6 minutes.
    - Agent can be place into ready after 2-6 minutes but the rest of the service don't workanother 3-5 minutes.
    - Sometimes CAD shows crazy messages like Jtapi error, user does not exist, etc for about 2-8 minutes.(clicking on OK will remove all errors eventually)
    NO FAILOVER MECHANISM WORKS DURING TRANSIENT (3 - 6 minutes)
    Any ideas?

    Hi Maxim,
    Page 39 of the below link states,
    http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/installation/guide/cad85ccxig-cm.pdf
    Privileges:
    By default, Windows Installer installations run in the context of the logged-on user. CAD installations, which use Windows Installer, require either administrative or elevated (system) privileges. If the CAD installation is run in the context of an administrative account, no additional privileges are required.
    You can also cross verify is the CAD has been installed after the UCCX HA setup is completetd, by running the
    PostInstall.exe from the path C:\Program Files\Cisco\Desktop\bin in the CAD\CSD boxes. If you dont find the second node ip address, please enter it here.
    And check the behaviour.
    Hope it helps,
    Anand

  • Node not functioning

    Hi,
    I've installed the node application on my macbook, and Logic seems to recognize the existence of the node. I'm able to select the node and to enable tracks to be processed by a node, but the enabled tracks never become active. That is, they are never actively processed by the node.
    I'm using a CAT6 ethernet cable and the two machines can see each other from the finder. The main machine is running Logic 8.0.2 and the node is 8.0.2.
    Any ideas?
    thanks!

    I don't know if this can help but here is my experience with the node network. Apple pretty much helped me through the setup, so i created the network so "Like you said both computers can communicate with each other using the ethernet cable. And i am using the apple G5 1.8 as my music computer, and using the mac pro to slave (Node computer). So the first thing i do is first start up the node computer(Mac pro) and click the node icon, then once that is enabled i will proceed to start up the music computer(G5 computer) once everything begins to start up i look for the node icon on the mac pro to see the nodes extend out around the node and i will know for a fact that the network is working. So what are you using for your music computer, you don't need a monitor for the node computer but it's good to see everything going on, on that computer. So on your music computer in logic go to audio and see if your node has been checked and configured in logic. I hope that this helps but i will keep an eye out for you if you need further help cheers.

Maybe you are looking for