ISE Nodes both become Primary

Hi,
We are deploying 2 x 3415 ISE appliances for a customer as a Primary/Secondary admin cluster. We are running Version 1.2.0.899-5-93975. Everything was going to plan with the deployment and when we manually promoted the Secondary all worked well. We then attempted some testing prior to going into production. We simulated a switch port failure which in effect isolated our Primary ISE. We then promoted our Secondary ISE and resolved the switch issue so we then had both ISE's as Primary Admins. It would be good at this point to simply 'demote' the Secondary back to Secondary but this is not an option. We tried to break the cluster by de-registering the Secondary from the Primary. We then got into a situation where we couldn't fully break the cluster and the end result is that the secondary is showing a 500-Internal error (see attached) and we are unable to browse to the GUI. I suspect I need to re-image the secondary now and re-join it back to the cluster.
Is there anything documented as to how recover a situation when both appliances become Primary? You would think this should be fairly straightforward. Also has anyone come across the 500-Internal error when attempting to Log into the appliance and if so how did you resolve. From CLI all services are running.
Any assistance/guidence would be appreciated,
Dean

I have the same scenario as yours:  ise1 is primary Admin/MNT and ise2 is secondary Admin/MNT.  ise1 ip address is 192.168.1.1/24 and ise2 is 192.168.1.2/24.  They are both on the same subnet.
simulate a disaster: shutdown the switchport that ise1 is connected to.
1- manually promote ise to primary Admin/MNT.  After that make a bunch of changes to ise2.
2- bring back ise1.  At this point, both ise1 and ise2 are shown as Primary Admin
3- from the WebUI in ise2, highlight ise and hit the button "sync-up".  That will force ise1 to become Secondary Admin
4- Once everything is sync'ed, log into the ise1 WebUI and manually promote ise1 to be Primary Admin/MNT again.
Does that make sense?

Similar Messages

  • Ise node not becoming standalone after deregistration

    I am seeing a weird problem.
    I deregistered secondary admin/monitor node from primary admin/monitor node. I see successfully deregistered message.
    But the deregistered node is still showing SEC(A) and SEC(M). It is not changing to standalone mode.
    This is disrupting the upgrade of distributed deployment of ISE nodes.
    Any clues?

    Bug details:
    Secondary node never becomes standalone after de-registration
    The secondary node is de-registered successfully but a "The following deregistered nodes are not currently reachable: . Be sure to reset the configuration on these nodes manually, as they may not revert to Standalone on their own." message appears to the administrator.
    Workaround   Log in to the administrator user interface with internal Cisco ISE administrator credentials when de-registering a node.
    Actually we had two accounts in web gui, nodes were registered using one account and during upgrade, i used different account , which triggered this bug.

  • Getting Error while registering ISE Node

    Hi All,
    I am getting below error.
    Communication failure with the host 162.12.95.167. Please check the information for the target machine, or if the target machine is accessible and try again.                
    I am Able to ping as well from primary node
    Output of ping:
    PING 162.12.95.167 (162.12.95.167) 56(84) bytes of data.
    64 bytes from 162.12.95.167: icmp_seq=1 ttl=58 time=1.02 ms
    64 bytes from 162.12.95.167: icmp_seq=2 ttl=58 time=1.05 ms
    64 bytes from 162.12.95.167: icmp_seq=3 ttl=58 time=1.05 ms
    64 bytes from 162.12.95.167: icmp_seq=4 ttl=58 time=0.955 ms
    64 bytes from 162.12.95.167: icmp_seq=5 ttl=58 time=1.02 ms
    --- 162.12.95.167 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4000ms
    rtt min/avg/max/mdev = 0.955/1.019/1.051/0.053 ms

    Hello Sachin-
    Couple of questions:
    1. Is there a firewall between the two nodes that you are trying to cluster? If yes, then have you confirmed that all of the necessary ports and protocols are opened between them?
    2. What version of ISE are you using
    3. Can you confirm that both devices are added in DNS and that both devices can ping each other via their FQDNs
    On a side note here are the prerequisites for clustering nodes:
    • The fully qualified domain name (FQDN) of the standalone node that you are going to register, for
    example, ise1.cisco.com must be DNS-resolvable from the primary Administration ISE node.
    Otherwise, node registration will fail. You must enter the IP addresses and FQDNs of the ISE nodes
    that are part of your distributed deployment in the DNS server.
    • The primary Administration ISE node and the standalone node that you are about to register as a
    secondary node should be running the same version of Cisco ISE.
    • You must configure the Cisco ISE Admin password at the time you install the Cisco ISE. The
    previous Cisco ISE Admin default login credentials (admin/cisco) are no longer valid.
    • Use the username/password that was created during the initial Setup or the current password, if it
    was changed later.
    • The DB passwords of the primary and secondary nodes should be the same. If these passwords are
    set to be different during node installation, you can modify them using the following commands:
    – application reset-passwd ise internal-database-admin
    – application reset-passwd ise internal-database-user
    • You can alternatively create an administrator account on the node that is to be registered and use
    those credentials for registering that node. Every ISE administrator account is assigned one or more
    administrative roles. To register and configure a secondary node, you must have either the Super
    Admin or System Admin role assigned. See Cisco ISE Admin Group Roles and Responsibilities for
    more information on the various administrative roles and the privileges associated with each of
    them.
    • If you plan to register a secondary Administration ISE node for high availability, we recommend
    that you register the secondary Administration ISE node with the primary first before you register
    other Cisco ISE nodes. If Cisco ISE nodes are registered in this sequence, you do not have to restart
    the secondary ISE nodes after you promote the secondary Administration ISE node as your primary.
    • If you plan to register multiple Policy Service ISE nodes running Session services and you require
    mutual failover among those nodes, you must place the Policy Service ISE nodes in a node group.
    You must create the node group first before you register the nodes because you must select the node
    group to be used on the registration page.
    “Creating, Editing, and Deleting Node Groups”
    section on page 9-21 for more information.
    • Ensure that the Certificate Trust List (CTL) of the primary node is populated with the appropriate
    Certificate Authority (CA) certificates that can be used to validate the HTTPS certificate of the
    standalone node (that you are going to register as the secondary node).
    Thank you for rating!

  • ISE node registering after change domain-name

    At Customer Site I changed the domain name of our 4 ISE server before they were registered to any deployment. I regenerated a self signed certificate and started to register the other nodes to the deployment. This went well for the 2 PSN nodes which have a ip address in a different subnet. I tried to register the presumed secondarry PAN/MnT node and got the following error message "
    Node beiing registerd has FQDN 'ISE-PAN-AP02.office.intern' which cannot be resolved. Please check your DNS configuration."
    My DNS config is in order.
    Can anyone please tell me want possible can be the cause of this?

    Please check these Prerequisites:
    The fully qualified domain name (FQDN) of the standalone node that you are going to register, for example, ise1.cisco.com must be DNS-resolvable from the primary Administration ISE node.  Otherwise, node registration will fail. You must enter the IP addresses  and FQDNs of the ISE nodes that are part of your distributed deployment  in the DNS server.
    •The  primary Administration ISE node and the standalone node that you are  about to register as a secondary node should be running the same version  of Cisco ISE.
    •Node  registration fails if you provide the default credentials (username:  admin, password: cisco) while registering a secondary node. Before you  register a standalone node, you must log into its administrative user  interface and change the default password (cisco).
    •You  can alternatively create an administrator account on the node that is  to be registered and use those credentials for registering that node.  Every ISE administrator account is assigned one or more administrative  roles. To register and configure a secondary node, you must have one of  the following roles assigned: Super Admin, System Admin, or RBAC Admin.  See Cisco ISE Admin Group Roles and Responsibilities for more information on the various administrative roles and the privileges associated with each of them.
    •If  you plan to register a secondary Administration ISE node for high  availability, we recommend that you register the secondary  Administration ISE node with the primary first before you register other  Cisco ISE nodes. If Cisco ISE nodes are registered in this sequence,  you do not have to restart the secondary ISE nodes after you promote the  secondary Administration ISE node as your primary.
    •If  you plan to register multiple Policy Service ISE nodes running Session  services and you require mutual failover among those nodes, you must  place the Policy Service ISE nodes in a node group. You must create the  node group first before you register the nodes because you need to  select the node group to be used on the registration page. See "Creating, Editing, and Deleting Node Groups" section for more information.
    •Ensure  that the Certificate Trust List (CTL) of the primary node is populated  with the appropriate Certificate Authority (CA) certificates that can be  used to validate the HTTPS certificate of the standalone node (that you  are going to register as the secondary node). See the "Creating Certificate Trust Lists in the Primary Cisco ISE Node" section on page 12-24 for more information.
    •After  registering your secondary node to the primary node, if you change the  HTTPS certificate on the registered secondary node, you must obtain  appropriate CA certificates that can be used to validate the secondary  node's HTTPS certificate and import it to the CTL of the primary node.  See "Creating Certificate Trust Lists in the Primary Cisco ISE Node" section on page 12-24 for more information.

  • ISE Node Failure & Pre-Auth ACL

    Hi All,
    I would like to know that, what should be the best practice configuration for following points,
    1) Network access for end users/devices if both ISE nodes become unreachable ? how we can make sure that full network access should be granted if both ISE nodes become unavailable.
    2) What is the best practice for pre-auth ACL configuration if IP Phones are also in the network ?
    Here is the port configuration and pre-auth ACL which I am using in my network,
    Interface Fa0/1
    switchport access vlan 30
    switchport mode access
    switchport voice vlan 40
    ip access-group ISE-ACL-DEFAULT in
    authentication event fail action authorize vlan 30
    authentication event server dead action authorize vlan 30
    authentication event server alive action reinitialize
    authentication host-mode multi-domain
    authentication open
    authentication order dot1x mab
    authentication priority dot1x mab
    authentication port-control auto
    authentication periodic
    authentication timer reauthenticate server
    authentication violation protect
    mab
      dot1x pae authenticator
    dot1x timeout tx-period 5
    ip access-list extended ISE-ACL-DEFAULT
    remark DHCP
    permit udp any eq bootpc any eq bootps
    remark DNS and Domain Controllers
    permit ip any host 172.22.35.11
    permit ip any host 172.22.35.12
    remark Ping
    permit icmp any any
    remark PXE / TFTP
    permit udp any any eq tftp
    remark Deny All
    deny   ip any any log
    Thanks & Regards,
    Mujeeb

    Hi,
    I am using following configuration on the ports,
    Interface Fa0/1
    switchport access vlan 30
    switchport mode access
    switchport voice vlan 40
    ip access-group ISE-ACL-DEFAULT in
    authentication event fail action authorize vlan 30 ----> What would be the behaviour due to this command ?
    authentication event server dead action authorize vlan 30 ---> So in case if ISE nodes are unavailable then this port will be in VLAN 30 which is the actual VLAN ?
    authentication event server alive action reinitialize ---> This command will re-initialize the authentication process if ISE nodes becomes available ?
    authentication host-mode multi-domain
    authentication open
    authentication order dot1x mab
    authentication priority dot1x mab
    authentication port-control auto
    authentication periodic
    authentication timer reauthenticate server
    authentication violation protect
    mab
      dot1x pae authenticator
    dot1x timeout tx-period 5
    Since I am using following ACL on the ports then user will have network access according to following ACL in case ISE nodes are unavailable ??
    ip access-list extended ISE-ACL-DEFAULT
    remark DHCP
    permit udp any eq bootpc any eq bootps
    remark DNS and Domain Controllers
    permit ip any host 172.22.35.11
    permit ip any host 172.22.35.12
    remark Ping
    permit icmp any any
    remark PXE / TFTP
    permit udp any any eq tftp
    remark Deny All
    deny   ip any any log
    Thanks

  • Best Practise for rebooting ISE Nodes?

    Hello Community,
    I administer an ISE installation with two nodes (I am not an ISE Specialist, my job is just to manage the user/mac-adresses... but now I have to move my ISE Nodes from one VMWare Cluster to another VMWare Cluster.
    (Both VMWare environments are connected to our enterprise network, but are different environments. vMotion not possible)
    I would shutdown ISE02, move it to our new VMWare environment and start it again.
    Than I would do this with our ISE01 Node...
    Are there any best practises for doing this? (Shutdown application first, stopl replikation etc)?
    Can I really simply reboot an ISE Node - or have I consider something bevor I doing this? After I doing this?
    Any tasks after reboot?
    Thank you for any answer!
    ISE01    
    Administration, Monitoring, Policy Service    
    PRI(A), SEC(M)
    ISE02    
    Administration, Monitoring, Policy Service    
    SEC(A), PRI(M)

    There is a lot to consider here.  If changing environments means changing IP Address and IP Scopes, then your policies, profiles, and dACLs would also have to change among other things.  If this is the case, create a new ISE VM in the new environment using the built in evaluation license and recreate the deployment from the old environment using the addressing scheme of the new environment.  Then spin-up a new Secondary node and register it on the Primary.  Once this is done, you can re-host the license from your old environment onto your new environment.  You can use this tool to re-host:
    https://tools.cisco.com/SWIFT/LicensingUI/loadDemoLicensee?FormId=3999
    If IP Addressing is to remain the same, it gets simpler. 
    First, and always, perform a configuration and operational backup.
    If downtime is not an issue, or if you have a maintenance window of an hour or so: Simply shut down both nodes.  Transfer them to the New Environment and turn them on, Primary Node first, of course.
    If downtime is an issue, shut down the Secondary Node and transfer it to the New Environment.  Start the Secondary Node and when it is up, shut down the Primary Node.  Once services on the primary node have stopped, promote the Secondary Node to Primary Node.
    Transfer the OLD Primary Node to the New Environment and turn it on.  It should assume the role of Secondary Node.  If it does not, assign that role through the GUI.
    Remember, the correct way to shut down an ISE node is:
    application stop ise
    halt
    By using these commands, the risk of database corruption decreases by about 90% (Remember to always backup).
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

  • Error while registering ISE node

    Getting this error while trying to register a newly built standalone VM node  on primary admin node.
    'admin' is not authorized to register ISE Node <node name>. Please check the credentials and/or privileges.
    admin is the only account on the newly built VM node and admin has full privileges on primary admin node as well. I have done the registering process before as well and this is the first time I have seen this error... Any thoughts?

    Hello Kashish,
    Though I assume its been almost a week's time and you might have solved this by now, but it may help others facing similar problem
    When a node is registered with the primary, the primary node would  connect with the node to be registered and the primary node itself needs  to authenticate against that node which is to be registered.
    You need to specify the Admin user password of the ISE node that you  want to register. Make sure by logging on to the Web UI of the ISE node  you want to register that you have the admin user password. Otherwise  you should create / reset admin user for web UI of the node to be  registered.
    Regards,
    Ashok

  • ISE NODE NOT REACHABLE when building distributed deployment

    I am trying to build a distributed deployment with the following personas:
    2 policy admin nodes
    2 monitoring nodes
    4 policy service nodes
    This was a project that was partially implemented but never in production. It was in a distributed deployment, but half the nodes were no longer working (http errors or devices weren't reachable or could not sync). I decided to start from scratch. All nodes were:
    -de-registered
    -application was reset to factory defaults on all nodes
    -upgraded all 8 nodes to 1.1.4.218 patch 1
    -installed all new certs and joined all nodes to the domain
    -added to DNS forward and reverse lookup zones
    When I make 1 admin node primary and register the other nodes (secondary admin, monitoring, policy services) the nodes successfully register and show up in the deployment window of the primary; however, all the nodes show as NODE NOT REACHABLE. After registration, I've noticed that the registered nodes are still showing as STANDALONE if I access the GUI. I've tried rebooting them manually after registration and they are still unreachable. I have also tried resetting the database user password from the CLI on both admin nodes and the results are always the same.

    Originally I had added them all at the same time. I thought that maybe I just wasn't waiting long enough for the sync. I waited an entire day and all the nodes were still unreachable. At this point, I've de-registered all the nodes, rebooted all the nodes, converted the primary back to standalone (the remaining nodes never converted from standalone to distributed even when I rebooted them after registering despite a message that they were successfully registered), converted one node back to primary and tried to register just the secondary admin node giving it plenty of time to sync; this node is still not reachable from the primary.
    I've quadruple checked the certificates on all the nodes, these certs were all added on the same day (just last week) and the default self-signed certs were removed.
    I had restored from a backup on the primary so I might just rest the config on that node and try joining the other nodes before I restore again.

  • WLST - Failing to run nmConnect() command / node manager becomes unreachabl

    Hello guys,
    I'm facing some issues to setup some configurations of one application that I've deployed on weblogic 10.3.3.0.
    One of the needed steps in order to configure this applications is open the WLST in offline mode an run 2 commands:
    */bea/mytrack/wlserver_10.3/common/bin/wlst.sh*
    Then I try to connect in the nodemanager:
    * wls:/offline> nmConnect('admin30800','weblogic_password',port='30801',domainName='track30800')*
    The following error returns:
    Connecting to Node Manager ...
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 123, in nmConnect
    File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Access to domain 'track30800' for user 'admin30800' denied
    I did some research and found this thread here: http://kr.forums.oracle.com/forums/thread.jspa?threadID=788163
    that solves the initial problem, however after I performed the nmConnect and a storeUserConfig() command, I exit() from the WLST and restart the node manager with success, the node manager becomes unreachable.
    I used the WL adm console and access -> appdomain -> environments -> machines -> monitoring -> node manager status to check the unreachable status.
    Thanks in advance,
    Davinod

    Nice it worked!!
    However when I try to start the servers controlled by this node manager I got this error:
    -sh-3.2$ <Jul 14, 2011 8:43:42 AM> <WARNING> <Exception while starting server 'track30800-01'>
    java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
    at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Jul 14, 2011 8:43:42 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'track30800-01'
    java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
    at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    <Jul 14, 2011 8:43:42 AM CDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server track30800-01 : Exception while starting server 'track30800-01'>
    Edited: Should I change the chmod for 777 for this file in order to check that all users have write permission?
    -rw-r--r-- 1 root iluser 193 Jun 24 11:05 boot.properties
    Did I miss a step?
    Thanks,
    Davinod
    Edited by: davinod on Jul 14, 2011 6:58 AM

  • ISE....uh.......No response from ISE node again...

    What is up with No Response from ISE Node ??
    Even though it sounds like the PSN node can't communicate with AD, it does authenticate and retrieving Groups, and attrbitues.
    How can I fix this ?
    why is it saying 'No Response from ISE Node ?

    Hi,
    Communication is fine between all ISE nodes, replications is COMPLETE for all nodes.
    I am running 1.1.4.218 with Patch 4 on all servers.
    I have 4 servers in my 8 servers-deployment that are in that strange AD status.
    The command "show logging application ise tail" does not show bad things. The DisplayName is always equal to the HostName which is the same as the HostAlias (with the domain name). Please see below.é
    Any ideas ?
    David
    Wed Sep 04 11:49:44 CEST 2013 : Poller wakeup...
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gcncsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gcncsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : 9cec53f0-151f-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gcncsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gcncsl0001ise.na.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : SESSION
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : NONE
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PDP
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : SECONDARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : 9cec53f3-151f-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : 9cec53f2-151f-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : 9cec53f1-151f-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : 10.97.32.223
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : 255.255.255.0
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : 9cec53f4-151f-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gcncsl0001ise.na.givaudan.com is not an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Ignoring node configuration for host gcncsl0001ise.na.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gjucsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gjucsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : 346a29c0-1177-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gjucsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gjucsl0001ise.ap.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : SESSION
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : NONE
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PDP
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : SECONDARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : 346a29c1-1177-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : 10.32.67.223
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : 255.255.254.0
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : 346a29c2-1177-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : 346a29c3-1177-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : 346a29c4-1177-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gjucsl0001ise.ap.givaudan.com is not an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Ignoring node configuration for host gjucsl0001ise.ap.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gmicsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gmicsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : af067300-10b4-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gmicsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gmicsl0001ise.na.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : SESSION
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : NONE
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PDP
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : SECONDARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : af067304-10b4-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : af067302-10b4-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : af067301-10b4-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : 10.96.67.223
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : 255.255.252.0
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : af067303-10b4-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gmicsl0001ise.na.givaudan.com is not an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Ignoring node configuration for host gmicsl0001ise.na.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gsrcsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gsrcsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : 305e3f30-147c-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gsrcsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gsrcsl0001ise.ap.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : SESSION
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : NONE
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PDP
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : SECONDARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : 305e3f31-147c-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : 10.32.128.223
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : 255.255.255.0
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : 305e3f32-147c-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : 305e3f34-147c-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : 305e3f33-147c-11e3-86da-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gsrcsl0001ise.ap.givaudan.com is not an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Ignoring node configuration for host gsrcsl0001ise.ap.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gvecsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gvecsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : cf0e4260-b1a3-11e2-87c5-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gvecsl0001ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gvecsl0001ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : unknown
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : STANDBY
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PAP MNT
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : PRIMARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : cf0e4262-b1a3-11e2-87c5-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : cf0e4263-b1a3-11e2-87c5-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : cf0e4264-b1a3-11e2-87c5-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : cf0e4261-b1a3-11e2-87c5-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : 10.71.142.9
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : 255.255.255.0
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gvecsl0001ise.emea.givaudan.com is an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Node gvecsl0001ise.emea.givaudan.com has HA status STANDBY
    Wed Sep 04 11:49:45 CEST 2013 : Enabling propagation...
    Wed Sep 04 11:49:45 CEST 2013 : Checking node configuration...
    Wed Sep 04 11:49:45 CEST 2013 : Enable MNT
    Wed Sep 04 11:49:45 CEST 2013 : Enable PAP
    Wed Sep 04 11:49:45 CEST 2013 : Disable PDP PROFILER SESSION
    Wed Sep 04 11:49:45 CEST 2013 : Current/new node role status is PRIMARY PRIMARY
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig for standby MNT node exists: gvecsl0001ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gvecsl0002ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gvecsl0002ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : 11ffc710-ee17-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gvecsl0002ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gvecsl0002ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : unknown
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : ACTIVE
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PAP MNT
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : SECONDARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : 11ffc712-ee17-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : 11ffc713-ee17-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : 11ffc711-ee17-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : 10.71.142.10
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : 255.255.255.0
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : 11ffc714-ee17-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gvecsl0002ise.emea.givaudan.com is an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Node gvecsl0002ise.emea.givaudan.com has HA status ACTIVE
    Wed Sep 04 11:49:45 CEST 2013 : Ignoring node configuration for host gvecsl0002ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig for active MNT node exists: gvecsl0002ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gvecsl0003ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gvecsl0003ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : c532d1c0-0671-11e3-b3d7-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gvecsl0003ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gvecsl0003ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : SESSION
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : NONE
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PDP
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : SECONDARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : c532d1c4-0671-11e3-b3d7-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : c532d1c3-0671-11e3-b3d7-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : c532d1c1-0671-11e3-b3d7-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : 10.71.142.2
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : 255.255.255.0
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : c532d1c2-0671-11e3-b3d7-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gvecsl0003ise.emea.givaudan.com is not an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Ignoring node configuration for host gvecsl0003ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : HostConfig : gvecsl0004ise
    Wed Sep 04 11:49:45 CEST 2013 :   DisplayName     : gvecsl0004ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostId          : 86fe3b20-f53b-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :   HostName        : gvecsl0004ise
    Wed Sep 04 11:49:45 CEST 2013 :   HostAlias       : gvecsl0004ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 :   CreateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   UpdateTime      : null
    Wed Sep 04 11:49:45 CEST 2013 :   NodeServiceType : SESSION
    Wed Sep 04 11:49:45 CEST 2013 :   MasterStatus    : NONE
    Wed Sep 04 11:49:45 CEST 2013 :   NodeTypes       : PDP
    Wed Sep 04 11:49:45 CEST 2013 :   NodeRoleStatus  : SECONDARY
    Wed Sep 04 11:49:45 CEST 2013 :   NICInterfaces   :
    Wed Sep 04 11:49:45 CEST 2013 :     0 Id          : 86fe3b21-f53b-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     0 IPAddress   : 10.71.142.3
    Wed Sep 04 11:49:45 CEST 2013 :     0 SubNetMask  : 255.255.255.0
    Wed Sep 04 11:49:45 CEST 2013 :     0 NicCards    : eth0
    Wed Sep 04 11:49:45 CEST 2013 :     1 Id          : 86fe3b24-f53b-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     1 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     1 NicCards    : eth3
    Wed Sep 04 11:49:45 CEST 2013 :     2 Id          : 86fe3b23-f53b-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     2 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     2 NicCards    : eth2
    Wed Sep 04 11:49:45 CEST 2013 :     3 Id          : 86fe3b22-f53b-11e2-a024-6cae8b66e764
    Wed Sep 04 11:49:45 CEST 2013 :     3 IPAddress   : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 SubNetMask  : null
    Wed Sep 04 11:49:45 CEST 2013 :     3 NicCards    : eth1
    Wed Sep 04 11:49:45 CEST 2013 : Checking HA status...
    Wed Sep 04 11:49:45 CEST 2013 : Node gvecsl0004ise.emea.givaudan.com is not an MNT node
    Wed Sep 04 11:49:45 CEST 2013 : Ignoring node configuration for host gvecsl0004ise.emea.givaudan.com
    Wed Sep 04 11:49:45 CEST 2013 : Node configuration has not changed - nothing updated
    Wed Sep 04 11:49:45 CEST 2013 : Poller sleeping...

  • ISE 1.1.1 to ISE 1.2 upgrade path for ISE node

    Hi,
    Currently in ISE deployment , we have  2 ISE nodes with 1.1.1.268 version  with latest patch,
    ISE nodes hold following  personas
    Node1 :  Admin, Monitoring ,  PSN
    Node 2 : PSN
    How will above deplyoment should be upgrade to 1.2 ?
    In which order they should be upgraded  ?   Any supporting doc covering above deployment for ISE 1.2 upgrade .

    Kindly check the following links for references
                   http://www.cisco.com/en/US/docs/security/ise/1.2/release_notes/ise12_rn.pdf
                   http://www.cisco.com/en/US/docs/security/ise/1.2/upgrade_guide/b_ise_upgrade_guide_chapter_01.pdf
                   https://www.cisco.com/en/US/docs/security/ise/1.2/open_source_license/Cisco_Identity_Services_Engine_1.2_Open_Source_Documentation.pdf

  • Which node will become master

    Hi All,
    I have 4 node rac. My question is suppose the master node go evicted,
    In this case,which node will become master and who decide which node will become master.
    I have read somewhere that the node wilth least number will become master.
    How oracle decide the numbering which node will have least number?
    Could you please help me in cleairing my doubt?
    your suggestion are welcome.
    Thanks and Regards

    Hi,
    I have learned somewhere the node with the least node number will become master node.
    How oracle decides which node will have highest node and which will have lowest node number?The information which you want is not documented (far as I know). What is difficult to accurately tell you the truth.
    There's a reason to you want to know about this. Depending on what you need, we can to solve in another way without trying to figure out which node have OCR Master all the time.
    Markus is Principal Product Manager Oracle RAC and he is one of Contributors of documentation of Oracle Database see his answer.
    Markus words:
    Why are you interested in knowing which node the OCR Master resides on all the time?
    The OCR backup is taken only every 4 hours. If you are of bad luck, the OCR master could have changed between the time of the last backup and the check using ocrconfig -showbackup. Now, if this was the case, the CRSD.log(s) will probably tell you But again, you should not be required to find the OCR master permanently.
    Re: Identify the OCR master node for 11.2
    Levi Pereira

  • ISE node group behind load balancer

    I'm trying to gather info on distributed deployment w/ multiple PSN nodes.
    Having read through some documents, it looks like you can put multiple PSN's in a node group, and then place the node group behind a load balancer.
    Q1:
    Node group config requires multicast.
    Cisco ACE LB doesn't support multicast, except in brige mode.
    How do people support distributed deployment in node group behind Ciso ACE?
    Q2:
    User guide says: "We recommend that you have two, three, or a maximum of four nodes in a node group."
    http://www.cisco.com/en/US/docs/security/ise/1.1.1/user_guide/ise_dis_deploy.html#wp1134272
    What if we need more than 4 PSN nodes to support our network & user base?
    Q3:
    Has anyone been able to implement distributed deployment between two datacenters behind GSS?
    If GSS isn't possible, we'll be happy to just have it in working state behind ACE LB.
    thx!

    I have had close to zero experience with LBs so my answers will be limited:
    Q1: I don't think the multicast plays any role with the LB. The multicast address is needed for the ISE nodes for replication
    Q2: You will have to create a new node group with a new multicast address
    Q3: No help here
    Couple of other things to remember:
    1. The nodes must be layer 2 adjacent
    2. You must use routed mode...no NAT/SNAT. Each node must be reachable directly from the end clients
    3. You must perform sticky
    4. The Load balancers must be listed as NADs in ISE
    Hope this provides some help to you.
    Thank you for rating!

  • Using RAC One Node as a primary database in a Data Guard configuration

    Is it possible to use RAC One Node as a primary database in a Data Guard configuration ?
    Oracle doc states: "Supports Oracle Data Guard such that you can run physical or logical standby databases on it or even we can NOT run primary databases on it either if the primary databases have DG"
    I guess it is not possible but can you folks confirm?
    Alessio

    Hmmm.... still unclear.
    I've submitted a comment which the documentation team should pick up :
    "+This sentence : "Supports Oracle Data Guard such that you can run physical or logical standby databases on it or even we can NOT run primary databases on it either if the primary databases have DG"+
    +is not very clear.+
    +I can understand it upto the words "on it" but the second part of the sentence, beginning with "or even we can NOT ..." seems mangled and unclear.+
    +Can you clarify whether RAC One Node can be used as :+
    +a. A Primary in a DataGuard configuration+
    +b. A Standby in a DataGuard configuration ?+"
    Hemant K Chitale

  • HSRP both become active once tracked interface goes down

    Hi team,
    I was doing a fail-over testing for several sites for a customer.(dual CE router setup)
    I have two routers 08R & 09R with following HSRP config.
    with this configuration 08R is active & 09R is secondary.. all good
    but when I shutdown the Serial link on active router(08R). both become active and standby unknown
    they can ping each other, checked ARP table, all good.
    also removed track statement on backup router (09R) but no joy...
    put the debug on
    Please advise.
    08R#sh run int f0/0
    ip address 10.58.0.29 255.255.255.0
    standby 1 ip 10.58.0.30  <---hsrp ip
    standby 1 priority 105<------------------- when s0/0/0 down, becomes 95
    standby 1 preempt
    standby 1 track Serial0/0/0.100
    09R#sh run int f0/0
    ip address 10.58.0.31 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 priority 101  <-------
    standby 1 preempt
    standby 1 track Serial0/1/0:0.100<-----------also tracking its own serial interface (removed this as its not required but still not working)
    Debug on 08R
    Jun 25 08:51:33.554 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30  <---sending hellos with lower priority 95, no in pkts
    Jun 25 08:51:36.554 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:51:37.978 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Debug on 09R
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  in  10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Coup   out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  in  10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Coup   out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30

    Try this:
    Router 08R Configuration
    track 100 interface Serial0/0/0.100 ip routing
    interface FastEthernet0/0
    ip address 10.58.0.29 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 preempt
    standby 1 priority 105
    standby 1 track 100 decrement 10
    Router 09R Configuration
    track 100 interface Serial0/1/0:0.100 ip routing
    interface FastEthernet0/0
    ip address 10.58.0.31 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 preempt
    standby 1 priority 101
    standby 1 track 100 decrement 10
    Ref.: CCO
    /André

Maybe you are looking for

  • Keep having to 'Repair Disk permissions'.

    My MBP (2.53 GHZ Intel Core i5, running 10.6.8) keeps running slow, and only improves after Repairing Disk Permissions. I had to run this again this morning - and I'd only ran Permissions repair two days ago! This is what I got; 'Repairing permission

  • How do I access pictures outside of Aperture?

    When I import pictures from my camera, it automatically stores them into the Aperture Library. How do I access the files on the hard drive outside of Aperture? Say I want to upload a picture to a site using their basic uploader browsing tool thing, h

  • Why I cannot test sucessfully?

    I use oracle8i and jdev9i.I am doing the tutorial example "business components basic tutorial",I have complete all steps except the last step "testing the business logic tier",I chose "local in Middle Tier Server Type,jdbc url in connect Type".But I

  • Trackpad erratic in Safari

    I have a late 2011 MacBook Pro 13" running Mountain Lion. When surfing in Safari I have an intermittent problem regarding the trackpad.  The following symptoms have been observed: Multi-gesture movements stop working When moving the cursor text is er

  • Getting system Variables

    Hi. I'm creating jsp page, which uses ssl connection. I want to print information of user logged into page, but I can't understand - how to get system variables in JSP page? directory httpd.conf file: <Files ~ "\.(cgi|shtml|php)$"> SSLOptions StdEnvV