# US 9,521,065 B1 · Enhanced VLAN naming

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 9,521,065 B1
- Document ID: US9521065B1
- Status: Granted
- Kind: B1
- Application number: 13/922,325
- Filed: 2013-06-20
- Granted: 2016-12-13
- Earliest claimed: 2013-06-20
- Assignees: EMC IP Holding Company LLC
- Applicants: EMC Corporation
- Inventors: Ranjith Kumar Nuji
- Web page: https://patentgrep.com/patent/US9521065B1

## CPC

- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 41/12: Discovery or management of network topologies
- H04L 45/02: Topology update or discovery
- H04L 45/04: {Interdomain routing, e.g. hierarchical routing}
- H04L 45/12: Shortest path evaluation
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Providing unique VLAN names in a system containing a plurality of networks includes obtaining, for at least one of the networks, a unique identifier associated with each of the networks, obtaining a VLAN ID for at least one of the VLANs in the at least one of the networks, and forming a unique VLAN name by concatenating the unique identifier to the VLAN ID. The unique identifier may be associated with each of the networks is a root bridge ID for a root bridge associated with each of the networks. In response to a root bridge becoming non-operational, a new root bridge may be determined and the unique VLAN name may be changed to remove the old root bridge ID and to include the new root bridge ID. In response to a change in topology, a new root bridge may be determined.

## Claims

### Claim 1

A method of routing data in a system containing a plurality of networks and a plurality of devices, comprising:
obtaining, for each of the plurality of networks, a unique identifier associated with respective ones of the plurality of networks, wherein the unique identifier associated with respective ones of the networks includes a root bridge ID for a root bridge uniquely associated with respective ones of the plurality of networks;
obtaining a VLAN ID for at least one VLAN in each of the plurality of networks;
forming, for each of the plurality of networks, a unique VLAN name by concatenating the respective unique identifier to the VLAN ID, wherein, in response to a change in topology, a new root bridge is determined and, in response to a value for the new root bridge being less than a value for the old root bridge, the unique VLAN name is changed to remove the old root bridge ID and to include the new root bridge ID; and
routing data through the system to provide communication between devices that are part of the same VLAN in different ones of the plurality of networks.

### Claim 2 (depends on 1)

The method, according to claim 1, wherein, in response to a root bridge becoming non-operational, a new root bridge is determined and the unique VLAN name is changed to remove the old root bridge ID and to include the new root bridge ID.

### Claim 3 (depends on 1)

The method, according to claim 1, wherein a unique VLAN name is provided for all of the VLANs in the system.

### Claim 4 (depends on 3)

The method, according to claim 3, wherein there are at least 4096 different discoverable VLANs in the system.

### Claim 5 (depends on 4)

The method, according to claim 4, wherein each of the networks includes less than 4096 VLANs and wherein at least one of the networks has at least one VLAN.

### Claim 6

An article of manufacture, comprising:
a non-transitory computer-readable media containing software that provides unique VLAN names in a system containing a plurality of networks and a plurality of devices, the software comprising:
executable code that obtains, for each of the plurality of networks, a unique identifier associated with respective ones of the plurality of networks, wherein the unique identifier associated with respective ones of the networks is a root bridge ID for a root bridge uniquely associated with respective ones of the networks;
executable code that obtains a VLAN ID for at least one of the VLANs in each of the plurality of networks;
executable code that forms, for each of the plurality of networks, a unique VLAN name by concatenating the unique identifier to the VLAN ID, wherein, in response to a change in topology, a new root bridge is determined and, in response to a value for the new root bridge being less than a value for the old root bridge, the unique VLAN name is changed to remove the old root bridge ID and to include the new root bridge ID; and
executable code that routes data through the system to provide communication between devices that are part of the same VLAN in different ones of the plurality of networks.

### Claim 7 (depends on 6)

The article of manufacture according to claim 6, wherein, in response to a root bridge becoming non-operational, a new root bridge is determined and the unique VLAN name is changed to remove the old root bridge ID and to include the new root bridge ID.

### Claim 8 (depends on 6)

The article of manufacture according to claim 6, wherein a unique VLAN name is provided for all of the VLANs in the system.

### Claim 9 (depends on 8)

The article of manufacture according to claim 8, wherein there are at least 4096 different discoverable VLANs in the system.

### Claim 10 (depends on 9)

The article of manufacture according to claim 9, wherein each of the networks includes less than 4096 VLANs and wherein at least one of the networks has at least one VLAN.