Patent Grant
10701464
Network devices, such as switches, routers, hubs, servers (e.g., rackmount servers) may include a chassis with one or more slots. Network components, such as line cards, may be inserted into the slots. The network components may perform various functions that may be used during the operation of the network device. For example, a switch may include multiple line cards that are inserted into multiple slots in the chassis of the switch. Each of the line cards may be coupled to other network devices (e.g., to ports of other switches), to other line cards within the same network device, and/or to different networks. Each network component may be coupled to a fabric of the network device via one or more connectors inside the chassis of the network device. For example, each network component may include a connector that may be coupled to another connector on a fabric or a mid-plane of the network device. The fabric may allow the different network components to communicate data with each other. For example, the fabric may allow data received from a first port of a first line card to be communicated (e.g., routed) to a second port of a second line card.
In some implementations, an apparatus is provided. The apparatus includes a latching component configured to secure a network component within a chassis of a network device when the apparatus is in a first configuration. The latching component is also configured to allow removal of the network component from the chassis of the network device when the apparatus is in a second configuration. The apparatus also includes a handle component coupled to the latching component. The handle component is accessible from a first face of the network component. The handle component is oriented away from the first face. The handle component is configured to facilitate the removal of the network component from the chassis when the apparatus is in the first configuration. The handle component is also configured to facilitate the insertion of the network component into the chassis when the apparatus is in the second configuration.
In some implementations, an apparatus is provided. The apparatus includes a latching component configured to secure a network component within a chassis of a network device when the apparatus is in a first configuration. The latching component is also configured to allow removal of the network component from the chassis of the network device when the apparatus is in a second configuration. The apparatus also includes a handle component coupled to the latching component. The handle component is accessible from a first face of the network component. The handle component is oriented away from the first face. The handle component is configured to facilitate the removal of the network component from the chassis when the apparatus is in the first configuration. The handle component is also configured to facilitate the insertion of the network component into the chassis when the apparatus is in the second configuration.
In some implementations, an apparatus is provided. The apparatus includes a latching component configured to secure a network component within a chassis of a network device when the apparatus is in a first configuration. The latching component is also configured to allow removal of the network component from the chassis of the network device when the apparatus is in a second configuration. The apparatus also includes a handle component coupled to the latching component along with a spring. The handle component and the direction in which the handle component may move, may be configured to reduce the amount of space used on the face (e.g., a front face) of the network component. The spring may interface with the handle and the latching component to push the network device to the chassis. Thus although there may be manufacturing tolerances in the network device or chassis, the network device is pushed into the chassis and the mating of the connectors between the network device and the chassis is maintained more reliably.
In some implementations a method is provided. The method includes aligning a network component with a slot in a chassis of a network device. The network component includes a securing mechanism, and the securing mechanism includes a latching component and a handle component. The method also includes pushing the handle component towards the inside of the chassis of the network device. The handle component is accessible from a first face of the network component. The handle component is oriented away from the first face. Pushing the handle causes a spring of the handle component to compress, a set of contact features to interface with a set of prongs of a handle cover, and a set of engagement features of the latching component to engage with a set of retention features in the chassis of the network device to secure the network component in the chassis. The method further includes pulling the handle away from the inside of the chassis of the network device. Pulling the handle causes a set of tabs to interface with the set of prongs, the set of contact features to move past the set of prongs, the spring to decompress, the set of engagement feature to disengage with the set of retention features to allow removal of the network component from the chassis.
Certain embodiments of the invention will be described with reference to the accompanying drawings. However, the accompanying drawings illustrate only certain aspects or implementations of the invention by way of example and are not meant to limit the scope of the claims.
As discussed above, network devices may include a chassis with one or more slots. Network components, such as line cards, may be inserted into the slots. The network components (e.g., line cards) should generally be secured to the chassis of the network device once the network components are installed in the network device (e.g., inserted into the slots of the chassis of the network device). This may prevent damage to the network components. For example, this may prevent accidental removal of a network component from the network device while the network component and/or network device are in operation. Preventing the accidental removal may prevent the network device and/or network component from physical damage and/or electrical damage (e.g., electrical damage to circuits, processors, memory, etc., of the network device and/or network components). This may allow the network components to operate properly. For example, the chassis of the network device may have mechanical tolerances that may cause the connectors in a network component to have problems fully coupling with connectors within the network device (e.g., may cause the connectors in the network component to not be fully inserted into connectors in the network device). In addition, line cards with more functionality and/or component may use of more of the face of the line card (e.g., to support additional portions). Furthermore, the mating between the connectors of the line card and the connectors in the chassis should be mechanically reliable. This may help the line card and/or the connectors coupled to the line card operate more reliability and/or may increase the performance of the connectors. Thus it may be useful to have one or more components on the line card which can help achieve mechanical reliable mating of the connectors of the line card, while reduce the foot print or the amount of space used on the face (e.g., faceplate) of the line card.
As discussed above, the network components 160 should generally be secured to the chassis 105 of the network device 100 once the network components 160 are inserted into the slots 110 of the chassis 105 of the network device 100. As illustrated in
The ejectors 161 occupy space on the front face of the network components 160. Thus, the ejectors 161 reduce the amount of space on the front face of the network components 160. Reducing the amount of space on the front face of a network component 160 may reduce the number of ports, connectors, labels (e.g., stickers, writing, etc.), displays, light emitting diodes (LEDs), etc., that may be positioned on the face of the network component 160. This may result in a less efficient use of the network component 160 and may cause inconvenience to users of the network device 100. For example, if less space is available on the face of the network component, fewer LEDs may be used to convey the status of ports, links, etc., provided by the network component. In addition, if less space is available on the face of the network component, the cooling or air flow capability of the network component 160 may be reduced, because the space that was used by the ejectors 161 may prevent additional vents or openings from being positioned on the face of the network component 160. Also, a user generally operates both of the ejectors 161 at the same time using both hands. Failure to use both hands to operate both of the ejectors 161 at the same time may result in the tilting, bending, or warping of the network components 160 during removal and which may cause mechanical damage to the network component 160 or chassis 105.
As discussed above, the network components 260 should generally be secured to the chassis 205 of the network device 200 once the network components 260 are inserted into the slots 210 of the chassis 205 of the network device 200. This may prevent damage to the network components 160 and/or network device 110, and may allow the network components 260 and/or network device 200 to operate properly.
As illustrated in
As illustrated in
Also as illustrated in
As illustrated in
In one embodiment, the latching component 320 includes engagement features 321. The engagement features 321 may have a paw shape or a wrench shape. The paw shape of the engagement features 321 may interface (e.g., contact, push against, etc.) retention features in the chassis of the network device. For example, the engagement features 321 may push against one or more tabs on the chassis of the network device. This may prevent the network component from being removed. The engagement features 321 are illustrated as being in a first position when the securing mechanism 300 is in the locked/closed/secured configuration. The engagement feature 321 may move to a second position when the securing mechanism 300 is in an open/unsecured configuration, as illustrated by the curved dashed arrows and as discussed in more detail below.
In one embodiment, the latching component 320 includes a plate 322 coupled to engagement features 321 and the handle component 310. The plate 322 includes grooves 323A and 323B. Screws 324A couple the plate 322 to the housing 361. The screws 324A allow the plate 322 to move between a first position (illustrated in
The latching component 320 includes engagement features 321. The shape of the engagement features 321 may interface (e.g., contact, push against, etc.) retention features in the chassis of the network device. This may prevent the network component from being removed. The engagement features 321 are illustrated as being in a first position when the securing mechanism 300 is in the locked/closed/secured configuration. The engagement feature 321 may move to a second position when the securing mechanism 300 is in an open/unsecured configuration, as illustrated by the curved dashed arrows and as discussed in more detail below. The latching component 320 includes a plate 322 coupled to engagement features 321 and the handle component 310. The plate 322 includes grooves 323A and 323B. Screws 324A couple the plate 322 to the housing 361. The screws 324A allow the plate 322 to move between a first position (illustrated in
As illustrated in
In one embodiment, as the handle 319 is pulled downwards (e.g., as the handle is pulled away from the network device by a user), the tabs 317 of the handle 319 may push against the prongs 315. This may cause the prongs 315 to be bent outwards (e.g., away from the inside of the handle housing 311). When the prongs 315 are bent outwards, they may no longer engage, contact, or interface with the contact features 316. This may allow the handle component 310 to move away from the network device. For example, if the prongs 315 are no longer in contact with the contact features 315, the spring 313 may be allowed to decompress which may cause the spring 313 to exert a force that pushes the network component 300 out of the chassis of a network device.
As illustrated in
In one embodiment, the latching component 420 includes engagement features 421. The engagement features 421 may have a paw shape or a wrench shape. The paw shape of the engagement features 421 may interface (e.g., contact, push against, etc.) retention features in the chassis of the network device. The engagement features 421 may be in a second position, as illustrated in
In one embodiment, the latching component 420 includes a plate 422 coupled to engagement features 421 and the handle component 410. The plate 422 includes grooves 424A and 423B. Screws 424A couple the plate 422 to the housing 361. The screws 424A allow the plate 422 to move between a first position (illustrated in
As illustrated in
In one embodiment, as the handle 419 is pushed upwards (e.g., as the handle is pushed towards the network device by a user), the e. The spring 413 may compress and the contact features 416 may be pushed past the ends of the prongs 415. This may allow the contact features 416 to interface with the prongs 416 which may prevent the spring 413 from decompressing, as discussed above.
The network component is pushed into the slot using a handle of a handle component at block 510. As discussed above, pushing the handle of the handle component may compress a spring within the handle component. As the spring is compressed, a portion of the housing of the handle may move into the network component. A set of contact features may be pushed past a set of prongs of a housing cover. The handle component may cause a set of engagement features to interface (e.g., contact, push against, etc.) retention features in the chassis of the network device. For example, the engagement features may rotate until they interface or engage with the retention features. When the handle is no longer pushed (e.g., when the user stops pushing the handle), the spring may not be able to decompress because the set of contact features may interface or engage the set of prongs, as discussed above. This may cause the spring to exert a force that pushes the network component into the chassis which may allow the securing mechanism to help absorb mechanical tolerances of the chassis and help ensure that the connectors of the network component are properly inserted into connectors in the chassis.
At block 515, the network component is pulled from the slot using the handle. As discussed above, pulling the handle component may move a set of tabs past the set of prongs. The set of tabs may push the set of prongs outwards so that the set of prongs no longer interface or engage with the set of contact features. Pulling the handle also rotates the engagement features such that the engagement features no longer interface or engage with the retention features. This may allow the spring to decompress and exert a force towards the outside of the chassis (e.g., exert a force towards the direction in which the handle is pulled). This may allow the network component to be removed from the chassis more easily.
Although the present disclosure may refer to rails, slits, slots, grooves, tabs, holes, notches, prongs, springs, etc., which may be used to interface/engage with different components, prevent movement of different components, etc., various other mechanical features or components may be used in other embodiments.
It should be understood that although the terms first, second, etc. may be used herein to describe various steps or calculations, these steps or calculations should not be limited by these terms. These terms are only used to distinguish one step or calculation from another. For example, a first calculation could be termed a second calculation, and, similarly, a second step could be termed a first step, without departing from the scope of this disclosure. As used herein, the term “and/or” and the “/” symbol includes any and all combinations of one or more of the associated listed items.
As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. In addition, the term “set” includes one or more items within the set. It will be further understood that the terms “comprises”, “comprising”, “includes”, and/or “including”, when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Therefore, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.
It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
With the above embodiments in mind, it should be understood that the embodiments might employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Further, the manipulations performed are often referred to in terms, such as producing, identifying, determining, or comparing. Any of the operations described herein that form part of the embodiments are useful machine operations. The embodiments also relate to a device or an apparatus for performing these operations. The apparatus can be specially constructed for the required purpose, or the apparatus can be a general-purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general-purpose machines can be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
A module, an application, a layer, an agent or other method-operable entity could be implemented as hardware, firmware, or a processor executing software, or combinations thereof. It should be appreciated that, where a software-based embodiment is disclosed herein, the software can be embodied in a physical machine such as a controller. For example, a controller could include a first module and a second module. A controller could be configured to perform various actions, e.g., of a method, an application, a layer or an agent.
The embodiments can also be embodied as computer readable code on a tangible non-transitory computer readable medium. The computer readable medium is any data storage device that can store data, which can be thereafter read by a computer system. Examples of the computer readable medium include hard drives, network attached storage (NAS), read-only memory, random-access memory, CD-ROMs, CD-Rs, CD-RWs, magnetic tapes, and other optical and non-optical data storage devices. The computer readable medium can also be distributed over a network coupled computer system so that the computer readable code is stored and executed in a distributed fashion. Embodiments described herein may be practiced with various computer system configurations including hand-held devices, tablets, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. The embodiments can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.
Although the method operations were described in a specific order, it should be understood that other operations may be performed in between described operations, described operations may be adjusted so that they occur at slightly different times or the described operations may be distributed in a system which allows the occurrence of the processing operations at various intervals associated with the processing.
Various units, circuits, or other components may be described or claimed as “configured to” perform a task or tasks. In such contexts, the phrase “configured to” is used to connote structure by indicating that the units/circuits/components include structure (e.g., circuitry) that performs the task or tasks during operation. As such, the unit/circuit/component can be said to be configured to perform the task even when the specified unit/circuit/component is not currently operational (e.g., is not on). The units/circuits/components used with the “configured to” language include hardware—for example, circuits, memory storing program instructions executable to implement the operation, etc. Reciting that a unit/circuit/component is “configured to” perform one or more tasks is expressly intended not to invoke 35 U.S.C. 112, sixth paragraph, for that unit/circuit/component. Additionally, “configured to” can include generic structure (e.g., generic circuitry) that is manipulated by software and/or firmware (e.g., an FPGA or a general-purpose processor executing software) to operate in manner that is capable of performing the task(s) at issue. “Configured to” may also include adapting a manufacturing process (e.g., a semiconductor fabrication facility) to fabricate devices (e.g., integrated circuits) that are adapted to implement or perform one or more tasks.
The foregoing description, for the purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the embodiments and its practical applications, to thereby enable others skilled in the art to best utilize the embodiments and various modifications as may be suited to the particular use contemplated. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4840570 | Mann, Jr. | Jun 1989 | A |
| 6252514 | Nolan | Jun 2001 | B1 |
| 6619971 | Chen | Sep 2003 | B1 |
| 6739890 | Hirata | May 2004 | B2 |
| 7420820 | Lima | Sep 2008 | B1 |
| 7679933 | Makabe | Mar 2010 | B2 |
| 7684208 | Okamoto | Mar 2010 | B2 |
| 8289707 | Liao | Oct 2012 | B2 |
| 20020135987 | Baldwin | Sep 2002 | A1 |
| 20150237749 | Boetzer | Aug 2015 | A1 |
| 20160128230 | Lam | May 2016 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20200077165 A1 | Mar 2020 | US |
