Just make sure you do a resync. You’ll want to find out right away whether or
not all your product instances can talk or not.
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519-824-4120 Ext 56354
le...@uoguelph.ca
No.
From: Scott Voll [mailto:svoll.v...@gmail.com]
Sent: Tuesday, September 19, 2017 4:12 PM
To: Matthew Loraditch
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] PLM service affecting?
But if we patch it, will it affect anything when it boots back
But if we patch it, will it affect anything when it boots back up?
Scott
On Tue, Sep 19, 2017 at 1:02 PM, Matthew Loraditch <
mloradi...@heliontechnologies.com> wrote:
> PLM can be down for the entire grace period before it affects anything. As
> long as it’s standalone you are good.
>
>
>
>
+1 for stand alone PLM ☺
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
From:
PLM can be down for the entire grace period before it affects anything. As long
as it’s standalone you are good.
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Scott
Voll
Sent: Tuesday, September 19, 2017 4:01 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip]
Quick question. is PLM patching service affecting?
we just want to patch PLM in the middle of the day and afraid to poke the
button. ;-)
TIA
Scott
___
cisco-voip mailing list
cisco-voip@puck.nether.net
You can still have an FQDN in the certificate (which is I believe what the
commercial CA will look for), while in System > Server be defined with IP
addresses. As far as I know, the two are not related. What I'm not really
sure of, and I've never taken the time to fully quantify, is whether there
Same boat here. DNS however has proven quite reliable and in hindsight, we
did not need to fear it.
We are worried that turning on DNS could potentially invalidate the
certificates use to verify phones are talking to the right cluster.
If we did use DNS, I am sure we would have used FQDN to
So, we, like many others, went with IP addresses as hostname in our CUCM
cluster. Best practice, avoid DNS issues, etc.
But now, certificate authorities will not grant certificates to private IP
addresses and we need (would like) publicly signed certificates to avoid those
pesky errors.
I