# US 2023/0155981 A1 · Security group resolution at ingress across virtual networks

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

- Number: US 2023/0155981 A1
- Document ID: US20230155981A1
- Status: Published application
- Kind: A1
- Application number: 17/526,164
- Filed: 2021-11-15
- Published: 2023-05-18
- Earliest claimed: 2021-11-15
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Sanjay Kumar Hooda; Prakash C. Jain
- Web page: https://patentgrep.com/patent/US20230155981A1

## CPC

- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 63/0263: {Rule management}
- 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 45/745: Address table lookup; Address filtering
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0272: {Virtual private networks}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques and architecture are described for providing a service, e.g., a security service such as a firewall, across different virtual networks/VRFs/VPN IDs. The techniques and architecture provide modifications in enterprise computing fabrics by modifying pull-based overlay protocols such as, for example, locator/identifier separation protocol (LISP), border gateway protocol ethernet virtual private network (BGP EVPN), etc. A map request carries additional information to instruct a map-server that even though mapping (destination prefix and firewall service RLOC for the destination) is known within the map-server's own virtual network/VRF for firewall service insertion, the map-server still should do a lookup across virtual networks/VRFs and discover the final destination's DGT (destination group tag) and include that in the map reply.

## Claims

### Claim 1

A method within a network comprising:
configuring a border of a first virtual network (VN) as a service egress tunnel router (ETR) to monitor a service prefix advertised via a service in (i) the first VN and (ii) a second VN;
advertising, by the service, the service prefix in the first VN and the second VN;
mapping, by the border with a map server/map resolver (MSMR) of the first VN, registration of the border as the service ETR;
based at least in part on a first host onboarding with the first VN, determining a steering policy for traffic from the first host destined for a second host, wherein the second host is located in one of the first VN or the second VN; and
based at least in part on the steering policy, routing the traffic via at least one of the first VN and the second VN to the second host.

### Claim 2 (depends on 1)

The method of claim 1, wherein:
determining the steering policy comprises determining (i) the first host and the second host are permitted to communicate with one another and (ii) the traffic should be routed to the service; and
the method further comprises:
routing the traffic via the first VN to the service; and
routing the traffic from the service via the border and the second VN to the second host.

### Claim 3 (depends on 1)

The method of claim 1, wherein mapping registration of the service ETR by the border with the MSMR of the first VN comprises storing the service ETR in a source instance registration table.

### Claim 4 (depends on 1)

The method of claim 1, wherein mapping registration of the service ETR with the MSMR of the first VN comprises storing the service ETR in a service insertion table.

### Claim 5 (depends on 1)

The method of claim 1, wherein determining the steering policy for traffic from the first host destined for the second host comprises:
requesting, by a switch of the first VN from the MSMR of the first VN, a resolution of the steering policy for the service ETR; and
based at least in part on requesting a service mapping, receiving, by the switch of the first VN from the MSMR of the first VN, one or more of the service ETR, a destination routing locator (RLOC), a destination instance-identification (ID)/VN, or a destination group tag.

### Claim 6 (depends on 5)

The method of claim 5, wherein determining the resolution of the steering policy for the service ETR for traffic from the first host destined for the second host comprises:
searching, by the MSMR of the first VN, a source instance registration table for the service mapping comprising one or more of the service ETR, the destination routing locator (RLOC), the destination instance-ID/VN, and the destination group tag; and
if the steering policy is not available in the source instance registration table, searching, by the MSMR of the first VN, a service insertion table for the steering policy comprising one or more of the destination routing locator (RLOC), the destination instance-ID/VN, and the destination group tag.

### Claim 7 (depends on 1)

The method of claim 1, wherein determining the steering policy for traffic from the first host destined for the second host comprises:
receiving, at a switch of the first VN, traffic from the first host destined for the second host;
based at least in part on receiving the traffic, sending, by the switch of the first VN to the MSMR of the first VN, a map request relating to the second host in the second VN;
based at least in part on the map request, determining, by the MSMR of the first VN, that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is required to go to the service; and
based at least in part on the determining that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is required to go to the service, receiving, at the switch of the first VN from the MSMR of the first VN, a routing locator (RLOC) for the service, a destination VN, and a destination group tag.

### Claim 8 (depends on 1)

The method of claim 1, wherein determining the steering policy for traffic from the first host destined for the second host comprises:
receiving, at a switch of the first VN, traffic from the first host destined for the second host;
based at least in part on receiving the traffic, sending, by the switch of the first VN to the MSMR of the first VN, a map request relating to the second host in the second VN;
based at least in part on the map request, determining, by the MSMR of the first VN, that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is not required to go to the service; and
based at least in part on the determining that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is not required to go to the service, receiving, at the switch of the first VN from the MSMR of the first VN, one or more of a destination group tag, a destination VN, or a destination instance-ID.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
withdrawing, by the service, routes associated with the service; and
de-registering, with the MSMR of the first VN, registration of the border as the service ETR.

### Claim 10

A system comprising:
one or processors; and
one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform actions comprising:
configuring a border of a first virtual network (VN) as a service egress tunnel router (ETR) to monitor a service prefix advertised via a service in (i) the first VN and (ii) a second VN;
advertising the service prefix in the first VN and the second VN;
mapping registration of the border as the service ETR;
based at least in part on a first host onboarding with the first VN, determining a steering policy for traffic from the first host destined for a second host, wherein the second host is located in one of the first VN or the second VN; and
based at least in part on the steering policy, routing the traffic via at least one of the first VN and the second VN to the second host.

### Claim 11 (depends on 10)

The system of claim 10, wherein:
determining the steering policy comprises determining (i) the first host and the second host are permitted to communicate with one another and (ii) the traffic should be routed to the service; and
the actions further comprise:
routing the traffic via the first VN to the service; and
routing the traffic from the service via the border and the second VN to the second host.

### Claim 12 (depends on 10)

The system of claim 10, wherein mapping registration of the service ETR comprises storing the service ETR in a source instance registration table.

### Claim 13 (depends on 10)

The system of claim 10, wherein mapping registration of the service ETR comprises storing the service ETR in a service insertion table.

### Claim 14 (depends on 10)

The system of claim 10, wherein determining the steering policy for traffic from the first host destined for the second host comprises:
requesting a resolution of the steering policy for the service ETR; and
based at least in part on requesting a service mapping, receiving one or more of the service ETR, a destination routing locator (RLOC), a destination instance-identification (ID)/VN, or a destination group tag.

### Claim 15 (depends on 14)

The system of claim 14, wherein determining the steering policy for traffic from the first host destined for the second host comprises:
searching a source instance registration table for the service mapping comprising one or more of the service ETR, the destination routing locator (RLOC), the destination instance-ID/VN, and the destination group tag; and
if the steering policy is not available in the source instance registration table, searching a service insertion table for the steering policy comprising one or more of the destination routing locator (RLOC), the destination instance-ID/VN, and the destination group tag.

### Claim 16 (depends on 10)

The system of claim 10, wherein determining the steering policy for traffic from the first host destined for the second host comprises:
receiving traffic from the first host destined for the second host;
based at least in part on receiving the traffic, sending a map request relating to the second host in the second VN;
based at least in part on the map request, determining that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is required to go to the service; and
based at least in part on the determining that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is required to go to the service, receiving a routing locator (RLOC) for the service, a destination VN, and a destination group tag.

### Claim 17 (depends on 10)

The system of claim 10, wherein determining the steering policy for traffic from the first host destined for the second host comprises:
receiving traffic from the first host destined for the second host;
based at least in part on receiving the traffic, sending a map request relating to the second host in the second VN;
based at least in part on the map request, determining that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is not required to go to the service; and
based at least in part on the determining that (i) the first host in the first VN and the second host are permitted to communicate with one another and (ii) the traffic is not required to go to the service, receiving one or more of a destination group tag, a destination VN, or a destination instance-ID.

### Claim 18 (depends on 10)

The system of claim 10, further comprising:
withdrawing, by the service, routes associated with the service; and
de-registering registration of the border as the service ETR.

### Claim 19

A method comprising:
configuring a border of a first virtual network (VN) as a service-egress tunnel router (ETR) to monitor a service prefix advertised via a service in (i) the first VN and (ii) a second VN;
advertising, by the service, the service prefix in the first VN and the second VN;
mapping, by the border with a map server/map resolver (MSMR) of the first VN, registration of the border as the service ETR;
based at least in part on a first host onboarding with the first VN, determining (i) the first host and a second host located in the second VN are permitted to communicate with one another and (ii) traffic from the first host destined for the second host should be routed to the service; and
based at least in part on the determining:
routing the traffic via the first VN to the service; and
routing the traffic from the service via the border and the second VN to the second host.

### Claim 20 (depends on 19)

The method of claim 19, wherein determining (i) the first host and the second host located in the second VN are permitted to communicate with one another and (ii) traffic from the first host destined for the second host should be routed to the service comprises:
requesting, by a switch of the first VN from the MSMR of the first VN, a steering policy; and
based at least in part on the requesting the steering policy, receiving, by the switch of the first VN from the MSMR of the first VN, one or more of the service ETR, a destination routing locator (RLOC), a destination ID, or a destination group tag.
