Difference between revisions of "VMM 2008 Architecture and Port Usage"
(New page: Whilst an understanding of the architecture of VMM 2008 is not essential in order to bale to use this technology, having basic understanding of how the system works can be useful, especial...) |
(→VMM 2008 Port Usage) |
||
| Line 7: | Line 7: | ||
As outlined in the [[VMM 2008 Components]] chapter of this book, VMM 2008 consists of a number of different components which all communicate, both with each other and with virtualization hosts. This communication takes place using standard network transport ports. Because the VMM components may be distributed over a multiple systems, it is helpful to have an understanding of which ports are used, especially in terms of firewall configuration. An overview of these ports is provided in the following table: | As outlined in the [[VMM 2008 Components]] chapter of this book, VMM 2008 consists of a number of different components which all communicate, both with each other and with virtualization hosts. This communication takes place using standard network transport ports. Because the VMM components may be distributed over a multiple systems, it is helpful to have an understanding of which ports are used, especially in terms of firewall configuration. An overview of these ports is provided in the following table: | ||
| − | <table> | + | <table border="1" cellpadding="5" cellspacing="0" id="E3B" style="border-collapse: collapse; border-color:#cccccc; border-style: solid; border-width: 1px; margin-bottom:20px"> |
| + | <tr bgcolor="#cccccc" style="color:black" valign="top"> | ||
| + | <th> | ||
| + | <p>Comminication Description</p> | ||
| + | </th> | ||
| + | <th> | ||
| + | <p>Port</p> | ||
| + | </th> | ||
<tr> | <tr> | ||
<td>VMM Administrator Console to VMM Server (WCF)</td> | <td>VMM Administrator Console to VMM Server (WCF)</td> | ||
| Line 13: | Line 20: | ||
</tr> | </tr> | ||
| − | <tr> | + | <tr bgcolor="#e9e9e6"> |
<td>VMM Administrator Console to VMM Self-Service Portal (WCF)</td> | <td>VMM Administrator Console to VMM Self-Service Portal (WCF)</td> | ||
<td>80</td> | <td>80</td> | ||
| Line 23: | Line 30: | ||
</tr> | </tr> | ||
| − | <tr> | + | <tr bgcolor="#e9e9e6"> |
<td>VMM Server to VMM Agent - Data (BITS)</td> | <td>VMM Server to VMM Agent - Data (BITS)</td> | ||
<td>443</td> | <td>443</td> | ||
| Line 33: | Line 40: | ||
</tr> | </tr> | ||
| − | <tr> | + | <tr bgcolor="#e9e9e6"> |
<td>VMM Server to source of P2V image (WinRM)</td> | <td>VMM Server to source of P2V image (WinRM)</td> | ||
<td>135</td> | <td>135</td> | ||
| Line 43: | Line 50: | ||
</tr> | </tr> | ||
| − | <tr> | + | <tr bgcolor="#e9e9e6"> |
<td>VM Host to VM Host (BITS)</td> | <td>VM Host to VM Host (BITS)</td> | ||
<td>80</td> | <td>80</td> | ||
| Line 53: | Line 60: | ||
</tr> | </tr> | ||
| − | <tr> | + | <tr bgcolor="#e9e9e6"> |
<td>Browser to Hyper-V Host via Self-Service Portal (RDP)</td> | <td>Browser to Hyper-V Host via Self-Service Portal (RDP)</td> | ||
<td>3389</td> | <td>3389</td> | ||
| Line 63: | Line 70: | ||
</tr> | </tr> | ||
| − | <tr> | + | <tr bgcolor="#e9e9e6"> |
<td>Virtual Machine Connection Tool</td> | <td>Virtual Machine Connection Tool</td> | ||
<td>2719</td> | <td>2719</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Revision as of 14:50, 9 February 2009
Whilst an understanding of the architecture of VMM 2008 is not essential in order to bale to use this technology, having basic understanding of how the system works can be useful, especially when attempting to diagnose problems. Of particular significance, especially in distributed configurations, are the different transport ports used by the different VMM components in order to communicate both with each other and with host systems.
This chapter of VMM 2008 Essentials aims to provide a high level overview of the architecture of VMM 2008, together with a summary of the different ports used by VMM 2008 to communicate. The latter information will be of considerable use when configuring firewalls to allow remote administration of virtual machines using VMM 2008.
VMM 2008 Port Usage
As outlined in the VMM 2008 Components chapter of this book, VMM 2008 consists of a number of different components which all communicate, both with each other and with virtualization hosts. This communication takes place using standard network transport ports. Because the VMM components may be distributed over a multiple systems, it is helpful to have an understanding of which ports are used, especially in terms of firewall configuration. An overview of these ports is provided in the following table:
|
Comminication Description |
Port |
|---|---|
| VMM Administrator Console to VMM Server (WCF) | 8100 |
| VMM Administrator Console to VMM Self-Service Portal (WCF) | 80 |
| VMM Server to VMM Agent - Control (WinRM)) | 80 |
| VMM Server to VMM Agent - Data (BITS) | 443 |
| VMM Server to SQL Database (HTTP) | 1433 |
| VMM Server to source of P2V image (WinRM) | 135 |
| VMM Library to hosts (BITS) | 80 |
| VM Host to VM Host (BITS) | 80 |
| Browser to virtual host via Self-Service Portal (VMRC) | 5900 |
| Browser to Hyper-V Host via Self-Service Portal (RDP) | 3389 |
| VMM Administrator Console to System Center OpsMgr (HTTP) | 80 |
| Virtual Machine Connection Tool | 2719 |
