Re: [cisco-voip] Naming conventions for Expressway-C / E

2017-09-04 Thread Ryan Huff
I try to stay away from uppercase, numbers and hyphens /special chars in 
hostnames (just superstitious like that).

Example Edge:

expedgea.domain.tld
expedgeb.domain.tld

This is the FQDN that will resolve to LAN2 on the inside with internal DNS and 
then the outside public address in external DNS if you're doing an Exp 
deployment going with CVD best practices, using the dual interface.

Example Control:

expcontrola.domain.tld
expcontrolb.domain.tld

Beyond that, it's really whatever makes sense for the business. I try to stay 
away from "themeing" (I.e using Greek Mythology in hostnames ... Ex. 
expasgard.domain.tld, thor.domain.tld). Aside from the novelty, it's like 
getting a bad tattoo you end up regretting later or trying to cover it up 
with alias records in the SAN field of the certs.

-RH


Sent from my iPhone
> On Sep 4, 2017, at 9:39 AM, Matthew Huff  wrote:
> 
> What about in a cluster?
> 
> Would it be a good idea to name it:
> 
> ny-expc-01.domain.com
> ny-expc-02.domain.com
> 
> ny-expe-01.domain.com
> ny-expe-02.domain.com
> 
> What about public/private names?
> 
> On Sep 4, 2017, at 7:58 AM, Bill Talley 
> > wrote:
> 
> Similar to Ryan, I usually try to include "expe" or "expc" as well when the 
> longer name isn't allowed, depending on customers naming standards.
> 
> Sent from a mobile device with very tiny touchscreen input keys. Please 
> excude my typtos.
> 
> On Sep 4, 2017, at 7:05 AM, Ryan Huff 
> > wrote:
> 
> I usually keep the names, "edge" and "control" incorporated in them somehow. 
> If I'm trying to save on typing and it's a single pair I might do, 
> "expcontrol" and "expedge". With clusters, I'll add more to the name that 
> denote its purpose or location.
> 
> Thanks,
> 
> Ryan
> 
> On Sep 4, 2017, at 6:17 AM, Matthew Huff > 
> wrote:
> 
> I’m about to deploy our first expressway cluster, what names do people use 
> form expressway DNS names?
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] Naming conventions for Expressway-C / E

2017-09-04 Thread Matthew Huff
What about in a cluster?

Would it be a good idea to name it:

ny-expc-01.domain.com
ny-expc-02.domain.com

ny-expe-01.domain.com
ny-expe-02.domain.com

What about public/private names?

On Sep 4, 2017, at 7:58 AM, Bill Talley 
> wrote:

Similar to Ryan, I usually try to include "expe" or "expc" as well when the 
longer name isn't allowed, depending on customers naming standards.

Sent from a mobile device with very tiny touchscreen input keys. Please excude 
my typtos.

On Sep 4, 2017, at 7:05 AM, Ryan Huff 
> wrote:

I usually keep the names, "edge" and "control" incorporated in them somehow. If 
I'm trying to save on typing and it's a single pair I might do, "expcontrol" 
and "expedge". With clusters, I'll add more to the name that denote its purpose 
or location.

Thanks,

Ryan

On Sep 4, 2017, at 6:17 AM, Matthew Huff > 
wrote:

I’m about to deploy our first expressway cluster, what names do people use form 
expressway DNS names?
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] Naming conventions for Expressway-C / E

2017-09-04 Thread Bill Talley
Similar to Ryan, I usually try to include "expe" or "expc" as well when the 
longer name isn't allowed, depending on customers naming standards.

Sent from a mobile device with very tiny touchscreen input keys. Please excude 
my typtos.

> On Sep 4, 2017, at 7:05 AM, Ryan Huff  wrote:
> 
> I usually keep the names, "edge" and "control" incorporated in them somehow. 
> If I'm trying to save on typing and it's a single pair I might do, 
> "expcontrol" and "expedge". With clusters, I'll add more to the name that 
> denote its purpose or location.
> 
> Thanks,
> 
> Ryan
> 
> On Sep 4, 2017, at 6:17 AM, Matthew Huff  wrote:
> 
>> I’m about to deploy our first expressway cluster, what names do people use 
>> form expressway DNS names?
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] Naming conventions for Expressway-C / E

2017-09-04 Thread Lelio Fulgenzi

What I had wished I known before coming up with a naming scheme was a couple of 
things. If using the two interface approach, the only way to distinguish 
between inside ip and outside IP is split view DNS entries.

Also, your expressway hostname and domain must match the SRV records.

You might be able to get away with aliases in the responses, but we weren't 
ready to risk it. We were on a tight timeline.

https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway-series/117811-configure-vcs-00.html

HTH

Sent from my iPhone

On Sep 4, 2017, at 6:17 AM, Matthew Huff > 
wrote:

I’m about to deploy our first expressway cluster, what names do people use form 
expressway DNS names?
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] Naming conventions for Expressway-C / E

2017-09-04 Thread Ryan Huff
I usually keep the names, "edge" and "control" incorporated in them somehow. If 
I'm trying to save on typing and it's a single pair I might do, "expcontrol" 
and "expedge". With clusters, I'll add more to the name that denote its purpose 
or location.

Thanks,

Ryan

On Sep 4, 2017, at 6:17 AM, Matthew Huff > 
wrote:

I’m about to deploy our first expressway cluster, what names do people use form 
expressway DNS names?
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


[cisco-voip] Naming conventions for Expressway-C / E

2017-09-04 Thread Matthew Huff
I'm about to deploy our first expressway cluster, what names do people use form 
expressway DNS names?
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip