1/ Change the IP on the SUB admin page. ( changes reflect correctly on sub and pub CLI following change )
2/ change the hostname of SUB on the CLI and rebooted.
3/ update to new IP and gateway address of SUB from the CLI and rebooted all nodes.. ( changes reflected correctly on sql tables on SUB and PUB following changes, however nodes are now on different subnets and cannot communicate to each other yet, so replication at this stage fails. )..
4/ change IP on PUB admin page ( again changes reflected correct on pub but not sub due to different network addresses ).
5/ updated to new IP of PUB on the SUB OS admin page.. ( this seems to update correct on admin page but does not update when checking on CLI ? ).
6/ update to new IP and gateway on PUB CLI page.. reboot all nodes again..
7/ run utils dbreplication reset all on the PUB..
From what I can see on RTMT, SUB and PUB admin pages, all the new ip addresses have updated correctly (in System servers ) but hostnames have not updated in listed Call Managers or Call Manager groups… Is this correct … However, they are all correctly listed in the Cluster overview on the OS admin page.
New SUB IP addresses and hostnames have updated when checking CLI on the PUB and SUB.. ( run sql select name,nodeid from ProcessNode )
New PUB IP address and hostname has updated on the PUB
However, new PUB IP address has not updated on the SUB ( but is correct on the OS admin page on the SUB ? )..
The replication does not start up because the PUB can only see one node on the network ( but the SUB is pingable )… PUB replication is State 0..
The replication on the SUB is stuck on 3.. ( bad in cluster ).
Does anyone have any ideas of what to do to fix this before I go back to my backups and start again..
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...