Zoning configuration and route advertisement

Abstract

Systems and methods use zoning configuration to construct border gateway protocol (BGP) route maps. The constructed route maps may be used to selectively advertise routes between BGP peer devices without having to advertise all available routes to all entities or subsystems in a network. Advantageously, this significantly reduces potential security risks to the network and improves scalability of services in non-volatile memory express over Fabric and other systems.

What is claimed is: 
     
         1 . An information handling system or system that uses one or more zoning configurations and one or more border gateway protocol (BGP) route maps to connect end-point devices, the information system comprising:
 one or more processors;   one or more network connections for receiving communication from a host that comprises a CDC client and for receiving communications from a subsystem; and   one or more non-transitory processor-readable media comprising one or more sets of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:   using a zoning configuration, create a route policy that associates the host and the subsystem; and   in response to receiving at the CDC client, in a border gateway protocol (BGP) route advertisement, at least some of the route policy, using the route policy to identify a route that should be advertised to the subsystem to establish a connection between the host and the subsystem.   
     
     
         2 . The information handling system of  claim 1 , further comprising, in response to receiving an asynchronous event notification (AEN) regarding a change in a discovery log page, communicating to the CDC a non-volatile memory express over Fabric (NVMe-oF) get log page command to obtain a response that comprises network information that comprises a subsystem IP address that the host should connect to. 
     
     
         3 . The information handling system of  claim 1 , wherein the host comprises a host interface and a first BGP peer database, the host using a BGP protocol to receive, at the host interface, first BGP peer information to and store it in the first BGP peer database. 
     
     
         4 . The information handling system of  claim 3 , wherein the first BGP peer information comprises a CDC IP address and a CDC autonomous system number (ASN), which the CDC client receives in response to sending out a multicast Domain Name System (mDNS) query. 
     
     
         5 . The information handling system of  claim 3 , wherein the host uses the first BGP peer information to establish with the CDC a persistent explicit network connection that specifies that traffic should egress from the host interface. 
     
     
         6 . The information handling system of  claim 5 , wherein the CDC client uses the persistent explicit network connection to perform steps comprising communicating asynchronous event registrations and keep-alive commands to the CDC. 
     
     
         7 . A processor-implemented method for using one or more zoning configurations and one or more border gateway protocol (BGP) route maps in a non-volatile memory express over Fabric (NVMe-oF) system, the method comprising:
 using a zoning configuration to create a route policy that associates a first BGP peer device and a second BGP peer device; and   communicating, in a BGP route advertisement, at least some of the route policy to the first BGP peer device, the first BGP peer device using the route policy to identify a route, which the first BGP peer device should advertise to the second BGP peer device to establish a connection.   
     
     
         8 . The processor-implemented method of  claim 7 , wherein the first BGP peer device uses the route policy to create an entry in a destination database that identifies the route. 
     
     
         9 . The processor-implemented method of  claim 7 , further comprising storing the zoning configuration in a zoning database of a discovery controller. 
     
     
         10 . The processor-implemented method of  claim 9 , wherein the discovery controller is a centralized discovery controller. 
     
     
         11 . The processor-implemented method of  claim 7 , further comprising storing BGP peer information in a BGP peer database that specifies an interface of the first BGP peer device that is to be used to establish the connection. 
     
     
         12 . The processor-implemented method of  claim 11 , further comprising storing, in a name server database, NVMe Qualified Names for the first BGP peer device and the interface. 
     
     
         13 . One or more non-transitory processor-readable media comprising one or more sequences of instructions which, when executed by at least one processor, causes steps to be performed comprising:
 using a zoning configuration to create a route policy that associates a first border gateway protocol (BGP) peer device and a second BGP peer device; and   communicating, in a BGP route advertisement, at least some of the route policy to the first BGP peer device, in which the first BGP peer device uses the route policy to identify a route that the first BGP peer device should advertise to the second BGP peer device to establish a connection.   
     
     
         14 . The one or more non-transitory processor-readable media of  claim 13 , wherein the first BGP peer device uses the route policy to create an entry in a destination database that identifies the route. 
     
     
         15 . The one or more non-transitory processor-readable media of  claim 13 , further comprising one or more sequences of instructions which, when executed by at least one processor, causes steps to be performed comprising:
 storing the zoning configuration in a zoning database of a discovery controller.   
     
     
         16 . The one or more non-transitory processor-readable media of  claim 15 , wherein the discovery controller is a centralized discovery controller. 
     
     
         17 . The one or more non-transitory processor-readable media of  claim 13 , further comprising one or more sequences of instructions which, when executed by at least one processor, causes steps to be performed comprising:
 storing BGP peer information in a BGP peer database that specifies an interface of the first BGP peer device that is to be used to establish the connection.   
     
     
         18 . The one or more non-transitory processor-readable media of  claim 13 , further comprising one or more sequences of instructions which, when executed by at least one processor, causes steps to be performed comprising:
 storing, in a name server database, an non-volatile memory express (NVMe) Qualified Name for the first BGP peer device.