# US 12,003,388 B1 · Path configuration in a network device using a user visible representative interface > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,003,388 B1 - Document ID: US12003388B1 - Status: Granted - Kind: B1 - Application number: 18/366,454 - Filed: 2023-08-07 - Granted: 2024-06-04 - Earliest claimed: 2023-08-07 - Assignees: Arista Networks, Inc. - Applicants: Arista Networks, Inc. - Inventors: Deepak Sebastian; Karthikeya Kumar Pandit - Web page: https://patentgrep.com/patent/US12003388B1 ## CPC - H04L 41/22: comprising specially adapted graphical user interfaces [GUI] - H04L 41/0883: {Semiautomatic configuration, e.g. proposals from system} - H04L 45/04: {Interdomain routing, e.g. hierarchical routing} - H04L 45/30: Routing of multiclass traffic - H04L 45/38: {Flow based routing} - H04L 49/111: Switch interfaces, e.g. port details - H04L 49/15: Interconnection of switching modules - H04L 49/25: Routing or path finding in a switch fabric - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Systems and methods that allow configuration of a path at a network device using a representative user visible interface for that path are disclosed. A feature of this path may thus be configured using this representative user visible interface through a configuration interface of the network device. When a feature for the path is configured by reference to its corresponding representative user visible interface, the interfaces of that path that correspond to that feature can be determined and the configuration for that feature can be applied to interfaces of the path, even where those interfaces reside in different subdomains. ## Claims ### Claim 1 A method for configuring paths in a network device, the method comprising: maintaining a set of subdomains, wherein each subdomain comprises packet processing hardware of the network device and interfaces of that subdomain; configuring a path at the network device, the path comprising a set of the interfaces across the subdomains; establishing a representative user visible interface for the path, wherein the path includes the representative user visible interface and corresponds to a physical front panel port of the network device; receiving a configuration for a feature through a configuration interface, the configuration specifying the representative user visible interface for the path; and individually configuring the set of interfaces of the subdomains comprising the path according to the feature based on the received configuration specifying the representative user visible interface. ### Claim 2 (depends on 1) The method of claim 1, wherein the set of interfaces comprising the path are associated with at least two different subdomains. ### Claim 3 (depends on 1) The method of claim 1, wherein each subdomain comprises an integrated circuit (IC) that is different from ICs corresponding to other subdomains. ### Claim 4 (depends on 3) The method of claim 3, wherein the interfaces of each subdomain comprise interfaces associated with the IC chip of that subdomain. ### Claim 5 (depends on 1) The method of claim 1, further comprising: determining a status associated with an interface of the set of interfaces of the subdomains; associating the determined status with the path; receiving a status request specifying the representative user visible interface for the path; returning the determined status in response to the status request. ### Claim 6 (depends on 5) The method of claim 5, further comprising: receiving one or more statuses associated with the set of interfaces of the subdomains comprising the path from one or more of the subdomains; and determining the status based on a status determination strategy. ### Claim 7 A network device, comprising: a set of subdomains, wherein each subdomain comprises associated packet processing hardware comprising interfaces of that subdomain and interfaces of that subdomain; a non-transitory computer readable medium, comprising instructions for: establishing a representative user visible interface for a configured path, wherein the path comprises a set of the interfaces across the subdomains and the set of interfaces includes the representative user visible interface and corresponds to a physical front panel port of the network device; receiving a configuration for a feature, the configuration specifying the representative user visible interface for the path; and individually configuring the set of interfaces of the subdomains comprising the path according to the feature based on the received configuration specifying the representative user visible interface. ### Claim 8 (depends on 7) The network device of claim 7, wherein each subdomain comprises packet processing hardware of the network device comprising an integrated circuit (IC) that is different from ICs corresponding to other subdomains. ### Claim 9 (depends on 8) The network device of claim 8, wherein the set of interfaces comprising the path are in the same subdomain. ### Claim 10 (depends on 7) The network device of claim 7, wherein the set of interfaces comprising the path are on the same IC. ### Claim 11 (depends on 7) The network device of claim 7, wherein each subdomain comprising a software agent adapted to: determine the configuration for the feature in association with the representative user visible interface; determine an interface of the subdomain is associated with that feature and that representative user visible interface; configure the determined interface according to the feature based on the received configuration by configuring the packet processing hardware of the subdomain in accordance with the configuration for the feature. ### Claim 12 A non-transitory computer readable medium, comprising instructions executable on a processor for: configuring a path at a network device, the path comprising a set of interfaces across a set of subdomains, each subdomain comprising packet processing hardware of the network device and interfaces of that subdomain: establishing a representative user visible interface for the path, wherein the path includes the representative user visible interface and corresponds to a physical front panel port of the network device; receiving a configuration for a feature through a configuration interface, the configuration specifying the representative user visible interface for the path; and individually configuring the set of interfaces of the subdomains comprising the path according to the feature based on the received configuration specifying the representative user visible interface. ### Claim 13 (depends on 12) The non-transitory computer readable medium of claim 12, wherein the set of interfaces comprising the path are associated with at least two different subdomains. ### Claim 14 (depends on 12) The non-transitory computer readable medium of claim 12, wherein each subdomain comprises packet processing hardware of the network device comprising an integrated circuit (IC) that is different from ICs corresponding to other subdomains. ### Claim 15 (depends on 14) The non-transitory computer readable medium of claim 14, wherein the interfaces of each subdomain comprise interfaces associated with the IC chip of that subdomain. ### Claim 16 (depends on 12) The non-transitory computer readable medium of claim 12, further comprising: determining a status associated with an interface of the set of interfaces of the domain; associating the determined status with the path; receiving a status request specifying the representative user visible interface for the path; returning the determined status in response to the status request. ### Claim 17 (depends on 16) The non-transitory computer readable medium of claim 16, further comprising: receiving one or more statuses associated with the set of interfaces of the subdomains comprising the path from one or more of the subdomains; and determining the status based on a status determination strategy.