Component identification and transmission system
First Claim
Patent Images
1. A method comprising:
- determining if a first unit having a first local card manager is designated as a management unit or as a non-management unit, wherein the first unit is one of multiple units operably coupled using a virtual backplane, with each of the units comprising a local card manager;
if the first unit is designated as a management unit, running a first card manager protocol on the first local card manager; and
if the first unit is designated as a non-management unit, running a second card manager protocol on the first local card manager, wherein the first card manager protocol is a different protocol than the second card manager protocol,wherein the first card manager protocol includesreceiving card information from each of the local card managers, the card information including a status of each of card associated with each of the local card managers;
storing the card information as stored data;
receiving a status change message associated with a change of the status of one or more of the cards; and
updating the stored data based on the status change message.
7 Assignments
0 Petitions
Accused Products
Abstract
Embodiments of this invention comprise a modular, scalable architecture for building a variety of Layer 2/3/4+ Ethernet products and devices. Such devices comprise of a set modules. The invention provides a set of rules to handle such modules. The rules are controlled by the architectural component named card manager. The card manager uses a protocol to discover the modules that are entering or leaving the system/device. The protocol'"'"'s data provides a unique way of identifying the modules that belong to the system.
32 Citations
11 Claims
-
1. A method comprising:
-
determining if a first unit having a first local card manager is designated as a management unit or as a non-management unit, wherein the first unit is one of multiple units operably coupled using a virtual backplane, with each of the units comprising a local card manager; if the first unit is designated as a management unit, running a first card manager protocol on the first local card manager; and if the first unit is designated as a non-management unit, running a second card manager protocol on the first local card manager, wherein the first card manager protocol is a different protocol than the second card manager protocol, wherein the first card manager protocol includes receiving card information from each of the local card managers, the card information including a status of each of card associated with each of the local card managers; storing the card information as stored data; receiving a status change message associated with a change of the status of one or more of the cards; and updating the stored data based on the status change message. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
Specification