# US 8,751,675 B2 · Rack server management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,751,675 B2 - Document ID: US8751675B2 - Status: Granted - Kind: B2 - Application number: 13/165,024 - Filed: 2011-06-21 - Published: 2012-12-27 - Granted: 2014-06-10 - Earliest claimed: 2011-06-21 - Assignees: Cisco Technology, Inc. - Applicants: Sriranjan Bose; Gururaja Nittur; Chidananda Satya Kumar Patchava - Inventors: Sriranjan Bose; Gururaja Nittur; Chidananda Satya Kumar Patchava - Web page: https://patentgrep.com/patent/US8751675B2 ## CPC - H04L 61/5014: using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP] - H04L 41/0809: {Plug-and-play configuration} - H04L 2101/604: Address structures or formats - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Techniques presented herein provide approaches for managing rack servers. In one embodiment, a message is received from a management controller of a rack server and via a switch port, where the message requests a lease for a network address under a first protocol. Upon determining that the management controller is a supported device, the switch port is configured to allow network traffic under at least a second protocol. ## Claims ### Claim 1 A method comprising: receiving a message from a management controller of a rack server, the message requesting a lease for a network address under a first protocol, the message storing one or more parameters characterizing the management controller in one or more fields defined by the first protocol as being reserved for vendor-specific extensions, and the message being received via a switch port configured to allow only network traffic under the first protocol; providing the lease for the network address to the management controller via the switch port; and upon determining that the management controller is a supported device based on the one or more parameters and an indication of one or more supported devices, configuring the switch port to allow network traffic under at least a second protocol. ### Claim 2 (depends on 1) The method of claim 1, further comprising: sending a request to the management controller via the second protocol. ### Claim 3 (depends on 2) The method of claim 2, wherein the request comprises at least one of: (i) a request for the management controller to undergo further authentication; (ii) a request for the management controller to execute a specified command; and (iii) a request for the management controller to retrieve a system parameter. ### Claim 4 (depends on 1) The method of claim 1, wherein the message stores at least one of a vendor field, a model field, and a serial number. ### Claim 5 (depends on 4) The method of claim 4, wherein determining the management controller is supported is based on at least one of the vendor field and the model field, and wherein the serial field is used to uniquely identify the management controller relative to other management controllers. ### Claim 6 (depends on 1) The method of claim 1, wherein the first protocol comprises a vendor-independent protocol, and wherein the second protocol comprises a vendor-specific protocol. ### Claim 7 (depends on 1) The method of claim 1, wherein determining the management controller is a supported device comprises: comparing the one or more parameters with the indication of one or more supported devices. ### Claim 8 Logic encoded in one or more non-transitory media for execution and when executed operable to: receive a message from a management controller of a rack server, the message requesting a lease for a network address under a first protocol, the message storing one or more parameters characterizing the management controller in one or more fields defined by the first protocol as being reserved for vendor-specific extensions, and the message being received via a switch port configured to allow only network traffic under the first protocol; provide the lease for the network address to the management controller via the switch port; and upon determining that the management controller is a supported device based on the one or more parameters and an indication of one or more supported devices, configure the switch port to allow network traffic under at least a second protocol. ### Claim 9 (depends on 8) The logic of claim 8, further operable to: send a request to the management controller via the at least one protocol other than the protocol. ### Claim 10 (depends on 9) The logic of claim 9, wherein the request comprises at least one of: (i) a request for the management controller to undergo further authentication; (ii) a request for the management controller to execute a specified command; and (iii) a request for the management controller to retrieve a system parameter. ### Claim 11 (depends on 8) The logic of claim 8, wherein the message stores at least one of a vendor field, a model field, and a serial number. ### Claim 12 (depends on 11) The logic of claim 11, wherein determining the management controller is supported is based on at least one of the vendor field and the model field, and wherein the serial field is used to uniquely identify the management controller relative to other management controllers. ### Claim 13 (depends on 8) The logic of claim 8, wherein the first protocol comprises a vendor-independent protocol, and wherein the second protocol comprises a vendor-specific protocol. ### Claim 14 (depends on 8) The logic of claim 8, wherein determining the management controller is a supported device comprises: comparing the one or more parameters with the indication of one or more supported devices. ### Claim 15 A system comprising: one or more computer processors; logic encoded in one or more tangible media for execution and, when executed by the one or more computer processors, operable to: receive a message from a management controller of a rack server, the message requesting a lease for a network address under a first protocol, the message storing one or more parameters characterizing the management controller in one or more fields defined by the first protocol as being reserved for vendor-specific extensions, and the message being received via a switch port configured to allow only network traffic under the first protocol; provide the lease for the network address to the management controller via the switch port; and upon determining that the management controller is a supported device based on the one or more parameters and an indication of one or more supported devices, configure the switch port to allow network traffic under at least a second protocol. ### Claim 16 (depends on 15) The system of claim 15, wherein the logic is further operable to: send a request to the management controller via the at least one protocol other than the protocol. ### Claim 17 (depends on 16) The system of claim 16, wherein the request comprises at least one of: (i) a request for the management controller to undergo further authentication; (ii) a request for the management controller to execute a specified command; and (iii) a request for the management controller to retrieve a system parameter. ### Claim 18 (depends on 15) The system of claim 15, wherein the message stores at least one of a vendor field, a model field, and a serial number. ### Claim 19 (depends on 18) The system of claim 18, wherein determining the management controller is supported is based on at least one of the vendor field and the model field, and wherein the serial field is used to uniquely identify the management controller relative to other management controllers. ### Claim 20 (depends on 15) The system of claim 15, wherein the first protocol comprises a vendor-independent protocol, and wherein the second protocol comprises a vendor-specific protocol.