<div class="content" name="BGP_TOC_ENTRY" uuid="b43a3cfe-4071-42d4-af4f-1c0f9497b6f6"><p>The <b>BGP_TOC_ENTRY</b> structure<a id="Appendix_A_Target_182"></a><a aria-label="Product behavior note 182" href="3bb906f0-b077-47ab-ad11-d8d807afde26#Appendix_A_182" data-linktype="relative-path">&lt;182&gt;</a> specifies the format in which
information pertaining to the type of data is stored in <a href="cf155bce-58dd-492d-8883-6a920c767d19" data-linktype="relative-path"><b>BGP_CONFIG_HEADER (section 2.2.1.2.252)</b></a>.
The following figure shows the relationships between the <b>BGP_CONFIG_HEADER</b>
and the entries.   </p><p><img id="MS-RRASM_pict0b2707d5-dcec-6109-14e2-d07c32b12757.png" src="ms-rrasm_files/image004.png" alt="Relationship between the BGP_CONFIG_HEADER and the entries" title="Relationship between the BGP_CONFIG_HEADER and the entries" data-linktype="relative-path"/></p><p><b>Figure 4: Relationship between the BGP_CONFIG_HEADER and
the entries</b></p><table>
 <tbody><tr>
  <th><p><br/>0</p></th>
  <th><p><br/>1</p></th>
  <th><p><br/>2</p></th>
  <th><p><br/>3</p></th>
  <th><p><br/>4</p></th>
  <th><p><br/>5</p></th>
  <th><p><br/>6</p></th>
  <th><p><br/>7</p></th>
  <th><p><br/>8</p></th>
  <th><p><br/>9</p></th>
  <th><p>1<br/>0</p></th>
  <th><p><br/>1</p></th>
  <th><p><br/>2</p></th>
  <th><p><br/>3</p></th>
  <th><p><br/>4</p></th>
  <th><p><br/>5</p></th>
  <th><p><br/>6</p></th>
  <th><p><br/>7</p></th>
  <th><p><br/>8</p></th>
  <th><p><br/>9</p></th>
  <th><p>2<br/>0</p></th>
  <th><p><br/>1</p></th>
  <th><p><br/>2</p></th>
  <th><p><br/>3</p></th>
  <th><p><br/>4</p></th>
  <th><p><br/>5</p></th>
  <th><p><br/>6</p></th>
  <th><p><br/>7</p></th>
  <th><p><br/>8</p></th>
  <th><p><br/>9</p></th>
  <th><p>3<br/>0</p></th>
  <th><p><br/>1</p></th>
 </tr>
 <tr>
  <td colspan="32">InfoType</td>
 </tr>
 <tr>
  <td colspan="32">InfoSize</td>
 </tr>
 <tr>
  <td colspan="32">Count</td>
 </tr>
 <tr>
  <td colspan="32">Offset</td>
 </tr>
</tbody></table><p><b>InfoType (4 bytes): </b>A 32-bit, unsigned integer
in <a href="fc2dfae9-0d04-4e1d-97c9-c51c2dc06c3b#gt_502de58c-ffc0-4dda-8fcb-b152b2c31fba" data-linktype="relative-path">network byte order</a>
that MUST indicate the type of data contained in the list. The value MUST be
one of the following values.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Value</p>
   </th>
   <th>
   <p>Meaning</p>
   </th>
   <th>
   <p>The structure pointed to at offset.</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>0x00000001 BGP_ROUTER_CONFIG</td>
  <td>This is the BGP router configuration.</td>
  <td>BGP_ROUTER_CONFIG (section 2.2.1.2.257)</td>
 </tr><tr>
  <td>0x00000002 BGP_POLICY_INFO</td>
  <td>This is the BGP policy configuration.</td>
  <td>BGP_POLICY (section 2.2.1.2.261)</td>
 </tr><tr>
  <td>0x00000003 BGP_PEER_INFO</td>
  <td>This is the BGP peer configuration.</td>
  <td>BGP_PEER (section 2.2.1.2.262)</td>
 </tr><tr>
  <td>0x00000004 BGP_PEER_POLICY_MAP</td>
  <td>This is the BGP peer to BGP policy mapping.</td>
  <td>BGP_PEER_TO_POLICIES (section 2.2.1.2.263)</td>
 </tr><tr>
  <td>0x00000005 BGP_ADVERTISE_INFO</td>
  <td>This is the BGP route advertise configuration.</td>
  <td>BGP_ADVERTISE (section 2.2.1.2.264)</td>
 </tr></tbody></table>
</dd></dl><p><b>InfoSize (4 bytes): </b>A 32-bit, unsigned
integer, in network byte order, that MUST specify the number of bytes in an
information structure of this type in this entry.</p><p><b>Count (4 bytes): </b>A 32-bit, unsigned integer in
network byte order that MUST specify the number of information structures of
this type in this entry.</p><p><b>Offset (4 bytes): </b>A 32-bit, unsigned integer
in network byte order that MUST specify the offset starting from
BGP_CONFIG_HEADER to start of the first structure for this entry.</p></div>