27.10.2013 Views

8.3.3.8 - Force10 Networks

8.3.3.8 - Force10 Networks

8.3.3.8 - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

www.dell.com | support.dell.com<br />

LLDP-MED Capabilities TLV<br />

The LLDP-MED Capabilities TLV communicates the types of TLVs that the endpoint device and the<br />

network connectivity device support. LLDP-MED network connectivity devices must transmit the<br />

Network Policies TLV.<br />

• The value of the LLDP-MED Capabilities field in the TLV is a 2 octet bitmap (Figure 21-4), each bit<br />

represents an LLDP-MED capability (Table 21-4).<br />

• The possible values of the LLDP-MED Device Type is listed in Table 21-5. The Dell <strong>Force10</strong> system<br />

is a Network Connectivity device, which is Type 4.<br />

When you enable LLDP-MED in FTOS (using the command advertise med) the system begins<br />

transmitting this TLV.<br />

Figure 21-4. LLDP-MED Capabilities TLV<br />

TLV Type<br />

(127)<br />

TLV Length<br />

(7)<br />

Table 21-4. FTOS LLDP-MED Capabilities<br />

Bit Position TLV FTOS Support<br />

432 | Link Layer Discovery Protocol<br />

0 LLDP-MED Capabilities Yes<br />

1 Network Policy Yes<br />

2 Location Identification Yes<br />

3 Extended Power via MDI-PSE Yes<br />

4 Extended Power via MDI-PD No<br />

5 Inventory No<br />

6-15 reserved No<br />

Table 21-5. LLDP-MED Device Types<br />

Value Device Type<br />

0 Type Not Defined<br />

1 Endpoint Class 1<br />

2 Endpoint Class 2<br />

3 Endpoint Class 3<br />

4 Network Connectivity<br />

5-255 Reserved<br />

Organizationally<br />

Unique ID<br />

(00-12-BB)<br />

Organizationally<br />

Defined Sub-type<br />

(1)<br />

LLDP-MED Capabilites<br />

(00000000 00001111)<br />

7 bits 9 bits 3 octets 1 octet 2 octets<br />

LLDP-MED Device<br />

Type<br />

(4)<br />

1 octet<br />

fnC0053mp

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!