Design your deployment around the use of logical names for Communications Suite servers. You should use logical names even on a single-system deployment, to position it for ease of future growth and expansion. Using logical names does not impose any additional deployment setup costs other than populating your DNS.
You can think of these logical names as falling into two categories: those that affect end users, such as settings in email client programs; and those affecting back-end administration, such as inbound SMTP servers.
The following tables describes these logical entities.
Table 5–1 User Facing Logical NamesTable 5–2 Maintenance Level Logical Names
Example |
Description |
---|---|
relay-in.siroe.com |
Corresponds to a bank of inbound SMTP servers. |
relay-out.siroe.com |
Corresponds to a bank of outbound SMTP servers. |
mmp.siroe.com |
Corresponds to a bank of MMP servers. |
storeAA.siroe.com |
Back-end message store. Select a naming scheme to work with your topology, for example, storeAA.siroe.com through storeZZ.siroe.com. |
calstoreAA.siroe.com |
Back-end calendar store. Select naming scheme to work with topology, for example, calstoreAA.siroe.com through calstoreZZ.siroe.com. |
Table 5–3 Mapping of User Level to Maintenance Level Logical Names
Maintenance Level |
User Level |
---|---|
relay-in.siroe.com |
N/A |
relay-out.siroe.com |
smtp.siroe.com |
mmp.siroe.com |
Any one or more of mmp.siroe.com, pop.siroe.com, and imap.siroe.com |
storeAA.siroe.com - storeZZ.siroe.com |
N/A, hidden from end users |
calstore_aa.siroe.com - calstore_az.siroe.com |
N/A, hidden from end users |