# US 10,873,626 B2 · Target driven peer-zoning synchronization

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

- Number: US 10,873,626 B2
- Document ID: US10873626B2
- Status: Granted
- Kind: B2
- Application number: 15/767,316
- Filed: 2016-04-29
- Published: 2020-05-28
- Granted: 2020-12-22
- Earliest claimed: 2016-04-29
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Alice Terumi Clark; Rupin T. Mohan; Vivek Agarwal; Krishna Puttagunta; Christopher Robert Nichols
- Web page: https://patentgrep.com/patent/US10873626B2

## CPC

- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- H04L 49/356: for storage area networks
- H04L 63/104: {Grouping of entities}
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 63/0209: {Architectural arrangements, e.g. perimeter networks or demilitarized zones}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and method for target driven peer-zoning (TDPZ) synchronization can include a principal member device and a switch. The principal member device can include to send an active peer zone list request to a switch. In an example, the principal member device can store a first TDPZ database version number and a first TDPZ zone list. In an example, the switch may send a response based on the active peer zone list request. In an example, the response can include a second TDPZ database version number and a second TDPZ zone list. The principal member device may compare the first TDPZ database version number to the second TDPZ database version number.

## Claims

### Claim 1

A system for target driven peer-zoning (TDPZ) synchronization, comprising:
a principal member device to send an active peer zone list request to a switch, wherein the principal member device stores a first TDPZ database version number and a first TDPZ zone list;
the principal member device to receive a response to the active peer zone list request, the response comprising a second TDPZ database version number and a second TDPZ zone list, the principal member device to compare the first TDPZ database version number to the second TDPZ database version number;
when the first TDPZ database version number is less than the second TDPZ database version number, the principal member device is to update the first TDPZ database version number to equal the second TDPZ database version number, and store the second TDPZ zone list in place of the first TDPZ zone list; and
when the first TDPZ database version number is greater than the second TDPZ database version number, the principal member device is to send an update to direct the switch to add/replace a peer zone or to remove a peer zone.

### Claim 2 (depends on 1)

The system of claim 1, wherein the switch is to send a register state change notification (RSCN) to the principal member device, and the switch is to increment the second TDPZ database version number.

### Claim 3 (depends on 2)

The system of claim 2, wherein the principal member device is to send an RSCN response to the switch, and the principal member device is to increment the first TDPZ database version number.

### Claim 4 (depends on 1)

The system of claim 1, wherein the update comprises an add/replace active peer zone (AAPZ) command to direct the switch to add/replace a peer zone or a remove active peer zone (RAPZ) command to direct the switch to remove a peer zone.

### Claim 5 (depends on 4)

The system of claim 4, wherein the principal member device is to increment the first TDPZ database version number when sending the AAPZ command or the RAPZ command.

### Claim 6 (depends on 1)

The system of claim 1, wherein when the first TDPZ database version number is equal to the second TDPZ database version number, the system does not update either the principal member device or the switch.

### Claim 7

A method for target driven peer-zoning (TDPZ) synchronization, comprising:
sending, with a principal member device to a switch, an active peer zone list request, wherein the principal member stores a first TDPZ database version and a first TDPZ zone list;
receiving, with the principal member device from the switch, a response based on the active peer zone list request, the response comprising a second TDPZ database version and a second TDPZ zone list;
comparing, at the principal member device, the first TDPZ database version number to the second TDPZ database version number; and
when the first TDPZ database version number is greater than the second TDPZ database version number, the principal member device sending an update to direct the switch to add/replace a peer zone or to remove a peer zone.

### Claim 8 (depends on 7)

The method of claim 7, comprising:
sending, from the switch, a register state change notification (RSCN) to the principal member device; and
incrementing with the switch, the second TDPZ database version number.

### Claim 9 (depends on 7)

The method of claim 7, the update comprising an add/replace active peer zone (AAPZ) command to direct the switch to add/replace a peer zone or a remove active peer zone (RAPZ) command to direct the switch to remove a peer zone.

### Claim 10 (depends on 9)

The method of claim 9, comprising the principal member device incrementing the first TDPZ database version number when sending the AAPZ command or the RAPZ command.

### Claim 11 (depends on 7)

The method of claim 7, comprising:
when the first TDPZ database version number is less than the second TDPZ database version number, the principal member device updating the first TDPZ database version number to equal the second TDPZ database version number, and the principal member device storing the second TDPZ zone list in place of the first TDPZ zone list.

### Claim 12 (depends on 7)

The method of claim 7, comprising:
when the first TDPZ database version number is equal to the second TDPZ database version number, updating neither the principal member device nor the switch.

### Claim 13

A non-transitory computer-readable medium comprising instructions executable by a processor to:
send, with a principal member device to a switch, an active peer zone list request, wherein the principal member stores a first TDPZ database version and a first TDPZ zone list;
receive, with the principal member device from the switch, a response based on the active peer zone list request, the response comprising a second TDPZ database version and a second TDPZ zone list;
compare, at the principal member device, the first TDPZ database version number to the second TDPZ database version number;
when the first TDPZ database version number is less than the second TDPZ database version number, with the principal member device, update the first TDPZ database version number to equal the second TDPZ database version number, and store the second TDPZ zone list in place of the first TDPZ zone list; and
when the first TDPZ database version number is greater than the second TDPZ database version number, the principal member device is to send an update to direct the switch to add/replace a peer zone or to remove a peer zone.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein:
the update comprises an add/replace active peer zone (AAPZ) command to direct the switch to add/replace a peer zone or a remove active peer zone (RAPZ) command to direct the switch to remove a peer zone.

### Claim 15 (depends on 14)

The non-transitory computer-readable medium of claim 14, comprising instructions to:
increment the first TDPZ database version number when sending the AAPZ command or the RAPZ command.

### Claim 16 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the instructions are to update neither the principal member device nor the switch when the first TDPZ database version number is equal to the second TDPZ database version number.