Dynamic service insertion in a fabric switch

Abstract

One embodiment of the present invention provides a switch. The switch includes a service management module and a packet processor. During operation, the service management module identifies a service provided by an appliance coupled to the switch via a local port. The packet processor constructs a notification message for a remote switch. The notification message includes information about the service and the appliance. In this way, the switch allows the remote switch to request the service.

Description

The present disclosure is related to:

U.S. patent application Ser. No. 13/087,239, titled “Virtual Cluster Switching,” by inventors Suresh Vobbilisetty and Dilip Chatwani, filed 14 Apr. 2011;

U.S. patent application Ser. No. 13/092,724, titled “Fabric Formation for Virtual Cluster Switching,” by inventors Shiv Haris and Phanidhar Koganti, filed 22 Apr. 2011;

U.S. patent application Ser. No. 13/092,580, titled “Distributed Configuration Management for Virtual Cluster Switching,” by inventors Suresh Vobbilisetty, Shiv Haris, Phanidhar Koganti, and Vidyasagara R. Guntaka, filed 22 Apr. 2011;

U.S. patent application Ser. No. 13/042,259, titled “Port Profile Management for Virtual Cluster Switching,” by inventors Dilip Chatwani, Suresh Vobbilisetty, and Phanidhar Koganti, filed 7 Mar. 2011; and

U.S. patent application Ser. No. 13/092,752, titled “Name Services for Virtual Cluster Switching,” by inventors Suresh Vobbilisetty, Phanidhar Koganti, and Jesse B. Willeke, filed 22 Apr. 2011;

the disclosures of which are incorporated by reference herein.

BACKGROUND

Field

The present disclosure relates to network management. More specifically, the present disclosure relates to dynamic insertion of services in a fabric switch.

Related Art

The exponential growth of the Internet has made it a popular delivery medium for multimedia applications, such as video on demand and television. Such applications have brought with them an increasing demand for bandwidth. As a result, equipment vendors race to build larger and faster switches with versatile capabilities, such as service insertion and provisioning, to move more traffic efficiently. However, the size of a switch cannot grow infinitely. It is limited by physical space, power consumption, and design complexity, to name a few factors. Furthermore, switches with higher capability are usually more complex and expensive. More importantly, because an overly large and complex system often does not provide economy of scale, simply increasing the size and capability of a switch may prove economically unviable due to the increased per-port cost.

A flexible way to improve the scalability of a switch system is to build a fabric switch. A fabric switch is a collection of individual member switches. These member switches form a single, logical switch that can have an arbitrary number of ports and an arbitrary topology. As demands grow, customers can adopt a “pay as you grow” approach to scale up the capacity of the fabric switch.

Meanwhile, layer-2 (e.g., Ethernet) switching technologies continue to evolve. More routing-like functionalities, which have traditionally been the characteristics of layer-3 (e.g., Internet Protocol or IP) networks, are migrating into layer-2. Notably, the recent development of the Transparent Interconnection of Lots of Links (TRILL) protocol allows Ethernet switches to function more like routing devices. TRILL overcomes the inherent inefficiency of the conventional spanning tree protocol, which forces layer-2 switches to be coupled in a logical spanning-tree topology to avoid looping. TRILL allows routing bridges (RBridges) to be coupled in an arbitrary topology without the risk of looping by implementing routing functions in switches and including a hop count in the TRILL header.

As Internet traffic is becoming more diverse, efficient and accurate configuration of essential services, such as firewalls, load-balancers, and intrusion detection, in a high-performance layer-2 network is becoming progressively more important as a value proposition for network architects. It is desirable to provide these services from a variety of physical and virtual appliances at distributed locations with flexibility and ease of deployment.

While a fabric switch brings many desirable features to a network, some issues remain unsolved in dynamic service insertion in the network.

SUMMARY

One embodiment of the present invention provides a switch. The switch includes a service management module and a packet processor. During operation, the service management module identifies a service provided by an appliance coupled to the switch via a local port. The packet processor constructs a notification message for a remote switch. The notification message includes information about the service and the appliance. In this way, the switch allows the remote switch to request the service.

In a variation on this embodiment, the switch also includes a virtualization module which operates in conjunction with the packet processor to represent the appliance as a virtual appliance in the notification message. The virtual appliance can be associated with one or more appliances providing the service.

In a further variation, the packet processor constructs a second notification message comprising a virtual identifier of a virtual switch. This virtual switch is associated with the switch and presented to be coupled to the virtual appliance. The virtualization module generates the virtual identifier.

In a further variation, the virtual switch is also associated with a second switch. The second switch is locally coupled to a second appliance, which is capable of providing the service and associated with the virtual appliance.

In a variation on this embodiment, during operation, the packet processor extracts information about a second service and a third appliance, which is capable of providing the second service and coupled to a third switch. The packet processor forwards a respective data requiring the second service toward the third switch.

In a further variation, the switch also includes a sequence module which receives a sequence of execution associated with the subnet, for the service and the second service. The sequence module also determines whether to forward a data frame belonging to the subnet to the appliance or the third appliance based on the sequence.

In a further variation, the packet processor encapsulates the data frame in a Transparent Interconnection of Lots of Links (TRILL) packet with a virtual routing bridge (RBridge) identifier as an egress RBridge identifier of the packet. This virtual RBridge identifier corresponds to the third switch.

In a variation on this embodiment, the service management module determines completion of the service for a data frame in response to receiving the data frame via the local port.

In a variation on this embodiment, the switch also includes a fabric switch management module which maintains a membership in a fabric switch. Such a fabric switch accommodates a plurality of switches and operates as a single logical switch.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A illustrates an exemplary fabric switch with dynamic service insertion capability, in accordance with an embodiment of the present invention.

FIG. 1B illustrates how a new appliance for an existing service is dynamically added to a fabric switch in conjunction with the example in FIG. 1A, in accordance with an embodiment of the present invention.

FIG. 1C illustrates how a new appliance for a new service is dynamically added to a fabric switch in conjunction with the example in FIG. 1B, in accordance with an embodiment of the present invention.

FIG. 2 illustrates an exemplary configuration of a fabric switch with dynamic service insertion capability, in accordance with an embodiment of the present invention.

FIG. 3A presents a flowchart illustrating the process of a member switch of a fabric switch dynamically adding an appliance to the fabric switch, in accordance with an embodiment of the present invention.

FIG. 3B presents a flowchart illustrating the process of a member switch of a fabric switch dynamically configuring a service, in accordance with an embodiment of the present invention.

FIG. 4 illustrates an exemplary sequence of execution among dynamically inserted services in a fabric switch, in accordance with an embodiment of the present invention.

FIG. 5A presents a flowchart illustrating the process of a member switch distributing a sequence of execution for a subnet among dynamically inserted services in a fabric switch, in accordance with an embodiment of the present invention.

FIG. 5B presents a flowchart illustrating the process of a member switch configuring a sequence of execution for a subnet among dynamically inserted services in a fabric switch, in accordance with an embodiment of the present invention.

FIG. 6A presents a flowchart illustrating the process of a member switch of a fabric switch processing a data frame received from an edge port, in accordance with an embodiment of the present invention.

FIG. 6B presents a flowchart illustrating the process of a member switch of a fabric switch processing a data frame received from an inter-switch port, in accordance with an embodiment of the present invention.

FIG. 7 illustrates an exemplary member switch with dynamic service insertion capability in a fabric switch, in accordance with an embodiment of the present invention.

In the figures, like reference numerals refer to the same figure elements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.

Overview

In embodiments of the present invention, the problem of dynamically adding a service in a fabric switch is solved by distributing configuration information of a respective appliance associated with the service across all member switches of the fabric switch. As a result, a respective member switch can obtain the service from any supporting appliance coupled to any member switch. An appliance coupled to a switch, which can be a fabric switch, provides specialized service to a network. Examples of an appliance can include, but are not limited to, a firewall, load balancer, intrusion detection/protection device, network analyzer, and network virtualizer. An appliance can be a physical device or a virtual machine running on a physical device. Typically, such an appliance is optimized for the performance of that specific service. In the traditional deployment of services in a network, when an appliance is added to a network, a respective switch in the network is required to be configured for accommodating the service provided by the appliance. For example, when a firewall is added, a respective switch in the network should be configured to forward traffic to the firewall. Such configuration can be tedious, repetitious, and error-prone.

Furthermore, a respective appliance is typically deployed in the data path of upstream or downstream traffic (which can be referred to as “north-south traffic”). For example, an appliance can be deployed at an aggregation router. However, recent growth in data centers has created demands for new services, often to traffic between servers and storage devices (which can be referred to as “east-west traffic”). Moreover, in today's networks, a respective appliance is required to be multitenant, where a single appliance can serve traffic belonging to different sub-networks (or subnets). On the other hand, the appliances providing a service can be located anywhere across a network, thereby distributing the traffic load of the network. As a result, traffic belonging to the same subnet can be served by different appliances. Configuring a network to support appliances which are simultaneously distributed and multitenant can be challenging.

To solve this problem, when an appliance is added to a member switch of a fabric switch (i.e., a switch which forms a fabric switch in conjunction with other member switches), the switch shares the location and the service provided by the appliance to the other member switches. In this way, the member switch exchanges operational and configuration data of the appliance with other member switches and integrates the appliance with the entire fabric switch. As a result, when connected to the fabric switch, the appliance automatically provides the service and its associated functionalities to the entire fabric switch. In some embodiments, one or more appliances providing a service are virtualized as a virtual appliance coupled to the fabric switch via a virtual member switch. The virtual switch is associated with the physical member switches coupled to the appliances providing the service. As a result, a respective member switch can simply forward a data frame belonging to a subnet which requires the service toward the virtual switch. Consequently, the data frame is eventually received by one of the member switches associated with the virtual switch. The member switch, in turn, forwards the data frame to the locally coupled appliance, which provides the service to the data frame. In this way, a service can be dynamically inserted via any member switch of a fabric switch without configuring individual switches in the fabric switch.

In some embodiments, the fabric switch is an Ethernet fabric switch. In an Ethernet fabric switch, any number of switches coupled in an arbitrary topology may logically operate as a single switch. Any new switch may join or leave the fabric switch in “plug-and-play” mode without any manual configuration. A fabric switch appears as a single logical switch to an end device. In some further embodiments, the fabric switch is a Transparent Interconnection of Lots of Links (TRILL) network and a respective member switch of the fabric switch is a TRILL routing bridge (RBridge).

Although the present disclosure is presented using examples based on the TRILL protocol, embodiments of the present invention are not limited to networks defined using TRILL, or a particular Open System Interconnection Reference Model (OSI reference model) layer. For example, embodiments of the present invention can also be applied to a multi-protocol label switching (MPLS) network. In this disclosure, the term “fabric switch” is used in a generic sense, and can refer to a network operating in any networking layer, sub-layer, or a combination of networking layers.

In this disclosure, the term “service” is used in a generic sense, and can refer to any operation or group of operations providing specific functionality to a standalone or fabric switch operating in any network layer. Any functionality required by a switch can be referred to as a “service.” Any physical or virtual device capable of providing a service to a switch can be referred to as an “appliance.” An “appliance” can be a device separate from a switch, or a hardware or software module running in the switch.

The term “end device” can refer to a device coupled to a fabric switch. An end device can be a host, a conventional layer-2 switch, or any other type of network device. Additionally, an end device can be coupled to other switches or hosts further away from a network. An end device can also be an aggregation point for a number of network devices to enter the network. The terms “device” and “machine” are used interchangeably.

The term “frame” refers to a group of bits that can be transported together across a network. “Frame” should not be interpreted as limiting embodiments of the present invention to layer-2 networks. “Frame” can be replaced by other terminologies referring to a group of bits, such as “packet,” “cell,” or “datagram.”

The term “switch” is used in a generic sense, and it can refer to any standalone or fabric switch operating in any network layer. “Switch” should not be interpreted as limiting embodiments of the present invention to layer-2 networks. Any device that can forward traffic to an end device or another switch can be referred to as a “switch.” Examples of a “switch” include, but are not limited to, a layer-2 switch, a layer-3 router, a TRILL RBridge, or a fabric switch comprising a plurality of similar or heterogeneous smaller physical switches.

The term “RBridge” refers to routing bridges, which are bridges implementing the TRILL protocol as described in Internet Engineering Task Force (IETF) Request for Comments (RFC) “Routing Bridges (RBridges): Base Protocol Specification,” available at http://tools.ietf.org/html/rfc6325, which is incorporated by reference herein. Embodiments of the present invention are not limited to application among RBridges. Other types of switches, routers, and forwarders can also be used.

The term “edge port” refers to a port in a fabric switch which exchanges data frames with an end device outside of the fabric switch. The term “inter-switch port” refers to a port which couples a member switch of a fabric switch with another member switch and is used for exchanging data frames between the member switches.

The term “switch identifier” refers to a group of bits that can be used to identify a switch. If the switch is an RBridge, the switch identifier can be an “RBridge identifier.” The TRILL standard uses “RBridge ID” to denote a 48-bit Intermediate-System-to-Intermediate-System (IS-IS) ID assigned to an RBridge, and “RBridge nickname” to denote a 16-bit value that serves as an abbreviation for the “RBridge ID.” In this disclosure, “switch identifier” is used as a generic term, is not limited to any bit format, and can refer to any format that can identify a switch. The term “RBridge identifier” is used in a generic sense, is not limited to any bit format, and can refer to “RBridge ID,” “RBridge nickname,” or any other format that can identify an RBridge.

The term “Ethernet fabric switch” refers to a number of interconnected physical switches which form a single, scalable logical switch. In a fabric switch, any number of switches can be connected in an arbitrary topology, and the entire group of switches functions together as one single, logical switch. This feature makes it possible to use many smaller, inexpensive switches to construct a large fabric switch, which can be viewed as a single logical switch externally.

Network Architecture

FIG. 1A illustrates an exemplary fabric switch with dynamic service insertion capability, in accordance with an embodiment of the present invention. As illustrated in FIG. 1, a fabric switch 100 includes member switches 101, 102, 103, 104, and 105. Member switches in fabric switch 100 use edge ports to communicate to end devices and inter-switch ports to communicate to other member switches. For example, switch 102 is coupled to end device 190 via an edge port and to switches 101, 104, and 105 via inter-switch ports. Examples of end device 190 include, but are not limited to, a layer-2 switch, layer-3 router, top-of-the-rack switch, and physical or virtual host machine. In some embodiments, fabric switch 100 is a TRILL network; switches 101, 102, 103, 104, and 105 are RBridges; and data frames transmitted and received via inter-switch ports are encapsulated in TRILL headers.

Appliances 122 and 124 provide service 152 to fabric switch 100 and are coupled to member switches 101 and 105, respectively. Similarly, appliances 132 and 134 provide service 153 to fabric switch 100 and are coupled to member switches 101 and 104, respectively. Examples of a service include, but are not limited to, firewall, load balancing, intrusion detection/protection, network analysis, and network virtualization. Though appliance 134 is a physical machine, appliance 132 is a virtual machine running on a physical machine 131. Hence, fabric switch 100 can receive the same service (e.g., service 153) from a physical and a virtual device.

In some embodiments, when an appliance, such as appliance 122 is added to switch 101, switch 101 creates a notification message, which specifies corresponding service 152 and the association of appliance 122 with switch 101. Switch 101 then sends this notification message to other switches in fabric switch 100. Upon receiving the message, a respective switch, such as switch 102, associates service 152 with switch 101. During operation, switch 102 receives from end device 190 a data frame belonging to a subnet which requires service 152. Switch 102 identifies switch 101 to be associated with service 152 and forwards the data frame to switch 101. As result, when connected to fabric switch 100, appliance 122 automatically provides service 152 and its associated functionalities to all member switches of fabric switch 100. In this way, service 152 can be dynamically inserted into fabric switch 100 without configuring individual switches in fabric switch 100.

In some embodiments, appliances which provide a service to fabric switch 100 are virtualized as a single virtual appliance. In the example in FIG. 1A, when appliances 122 and 124 are coupled to fabric switch 100, switches 101 and 105, in conjunction with each other, virtualize appliances 122 and 124 as a virtual appliance 120 coupled to fabric switch 100 via a virtual member switch 112. Switches associated with a virtual switch can be referred to as partner switches. For example, switches 101 and 105 are the partner switches associated with virtual switch 112. Switches 101 and 105 send notification messages about virtual switch 112 and virtual appliance 120 to the other switches in fabric switch 100. One such message specifies that virtual appliance 120 is associated with service 152 and coupled to virtual switch 112. The same or a different message further specifies that virtual switch 112 is reachable via switches 101 and 105. Upon receiving the notification messages, other switches become aware of service 152, associated virtual appliance 120, and virtual switch 112. Similarly, appliances 132 and 134 are virtualized as a virtual appliance 130 coupled to a virtual switch 113, which is reachable via switches 101 and 104. Switch virtualization in a fabric switch and its associated operations, such as data frame forwarding, are specified in U.S. Patent Publication No. 2010/0246388, titled “Redundant Host Connection in a Routed Network,” the disclosure of which is incorporated herein in its entirety.

During operation, switch 102 receives from end device 190 a data frame belonging to a subnet which requires service 152. Switch 102 identifies virtual appliance 120 to be associated with service 152. Switch 102 also identifies that virtual appliance 120 is coupled to virtual switch 112. Switch 102 then simply forwards the data frame toward virtual switch 112. In some embodiments, switch 102 encapsulates the data frame in a TRILL packet. The data frame is then forwarded to either switch 101 or 105. If only one of switches 101 and 105 is configured for the subnet, the data frame is forwarded to that specific switch. Suppose that switch 101 receives the frame. Switch 101, in turn, forwards the data frame to locally coupled appliance 122, which provides service 152 to the data frame. For example, if service 152 is a firewall service, appliance 122 checks whether the data frame should be forwarded to the subnet.

Upon receiving back the data frame from appliance 122, switch 101 checks whether the data frame requires any other service. If the data frame requires service 153 as well, switch 101 identifies appliance 132, which can provide service 153, to be a local appliance and forwards the data frame to appliance 132. When switch 101 receives the data frame back from appliance 132, switch 101 checks whether the data frame requires any other service. If not, switch 101 forwards the data frame toward its destination. In this way, fabric switch 100 receives services from appliances 122, 124, 132, and 134 without configuring individual switches in fabric switch 100.

Virtual switch 112 allows switches 102, 103, and 104 to simply forward data frames belonging to a subnet which requires service 152 toward virtual switch 112. The data frames reach either switch 101 or 105 based on the routing policy of fabric switch 100. In some embodiments, virtual appliance 120 can be logically coupled to switches 101 and 105, instead of virtual switch 112. Under such a scenario, instead of creating virtual switch 112, switches 101 and 105 advertise virtual appliance 120 to be a locally coupled appliance to switches 102, 103, and 104. As a result, switches 102, 103, and 104 send data frames belonging to a subnet which requires service 152 to either switch 101 or 105. However, without virtual switch 112, a respective switch has to explicitly choose either switch 101 or 105 to be an egress RBridge for sending the data frames. For example, switch 102 can choose switch 105, while switch 103 can choose switch 101 for forwarding data frames toward virtual appliance 120.

A new appliance is added to fabric switch 100 can be associated with either an existing service or a new service. FIG. 1B illustrates how a new appliance for an existing service is dynamically added to a fabric switch in conjunction with the example in FIG. 1A, in accordance with an embodiment of the present invention. In this example, appliance 136, which provides existing service 153, is added to fabric switch 100. Appliance 136 is a virtual machine running on a physical machine 135. Hence, a new appliance added to fabric switch 100 can be a virtual machine. Because virtual appliance 130 and virtual switch 113 are already associated with service 153 in fabric switch 100, switch 103 is aware of service 153, associated virtual appliance 130, and virtual switch 113. In some embodiments, switch 103 sends a query message to other member switches in fabric switch 100 to identify the switches associated with virtual switch 113 (e.g., switches 101 and 104).

Upon detecting appliance 136, switch 103, in conjunction with switches 101 and 104, associates appliance 136 with virtual appliance 130. Furthermore, switch 103 becomes a partner switch associated with virtual switch 113. As a result, other member switches, such as switches 102 and 105, still perceive that only one appliance (e.g., virtual appliance 130) is providing service 153 to fabric switch 100. During operation, switch 102 receives from end device 190 a data frame belonging to a subnet which requires service 153. Switch 102 identifies that virtual appliance 130 is coupled to virtual switch 113. Switch 102 simply forwards the data frame toward virtual switch 113. Because switch 103 is now associated with virtual switch 113, the data frame can be forwarded to any of switches 101, 103, and 104. Suppose that switch 103 receives the data frame. Switch 103 then forwards the data frame to locally coupled appliance 136, which provides service 153 to the data frame.

FIG. 1C illustrates how a new appliance for a new service is dynamically added to a fabric switch in conjunction with the example in FIG. 1B, in accordance with an embodiment of the present invention. In this example, appliance 142, which provides a new service 154, is added to fabric switch 100. Because service 154 is new, upon detecting appliance 142, switch 103 creates a virtual appliance 140 associated with service 154 in fabric switch 100. Switch 103 also creates a virtual switch 114 and sends a notification message to other member switches in fabric switch 100 notifying them that virtual switch 114 has joined fabric switch 100 and is reachable via switch 103. Switch 103 also notifies the other switches via the same or a different message that virtual appliance 140 can provide service 154 to fabric switch 100 and is coupled to virtual switch 114.

Upon receiving the messages, other switches detect virtual switch 114 to be another member switch and virtual appliance 140 to be a physical appliance coupled to virtual switch 114. These switches update their respective forwarding information accordingly. During operation, switch 102 receives from end device 190 a data frame belonging to a subnet which requires service 154. Switch 102 identifies that virtual appliance 140 is coupled to virtual switch 114. Switch 102 then forwards the data frame toward virtual switch 114. Because only switch 103 is associated with virtual switch 114, the data frame is forwarded to switch 103. When switch 103 receives the data frame, switch 103 forwards the data frame to locally coupled appliance 142, which provides service 154 to the data frame. In this way, service 154 can be dynamically inserted into fabric switch 100 only via switch 103 without manually configuring switches 101, 102, 104, and 105.

Dynamic Service Insertion

FIG. 2 illustrates an exemplary configuration of a fabric switch with dynamic service insertion capability, in accordance with an embodiment of the present invention. In this example, a fabric switch 200 includes switches 212, 214, and 216. Fabric switch 200 also includes switches 202, 204, 222 and 224, each with a number of edge ports which can be coupled to external devices. For example, switches 202 and 204 are coupled with end devices 262 and 264 via Ethernet edge ports. Upon learning the media access control (MAC) addresses of end devices 262 and 264, switches 202 and 204 share the learned MAC addresses with rest of fabric switch 200. Similarly, switches 222 and 224 are coupled to appliances 252 and 254, also via Ethernet edge ports. Appliances 252 and 254 provide service 270 to fabric switch 200.

In some embodiments, switches in fabric switch 200 are TRILL RBridges and in communication with each other using TRILL protocol. These RBridges have TRILL-based inter-switch ports for connection with other TRILL RBridges in fabric switch 200. Although the physical switches within fabric switch 200 are labeled as “TRILL RBridges,” they are different from conventional TRILL RBridge in the sense that they are controlled by the FC switch fabric control plane. In other words, the assignment of switch addresses, link discovery and maintenance, topology convergence, routing, and forwarding can be handled by the corresponding FC protocols. Particularly, each TRILL RBridge's switch ID or nickname is mapped from the corresponding FC switch domain ID, which can be automatically assigned when a switch joins fabric switch 200 (which is logically similar to an FC switch fabric).

Note that TRILL is only used as a transport between the switches within fabric switch 200. This is because TRILL can readily accommodate native Ethernet frames. Also, the TRILL standards provide a ready-to-use forwarding mechanism that can be used in any routed network with arbitrary topology (although the actual routing in fabric switch 200 is done by the FC switch fabric protocols). Embodiments of the present invention should be not limited to using only TRILL as the transport. Other protocols (such as multi-protocol label switching (MPLS) or Internet Protocol (IP)), either public or proprietary, can also be used for the transport.

When appliances 252 and 254 are coupled to fabric switch 200, switches 222 and 224, in conjunction with each other, virtualize appliances 252 and 254 as a virtual appliance 250 coupled to fabric switch 200 via a virtual member switch 240. In some embodiments, virtual switch 240 is a TRILL RBridge and assigned a virtual RBridge identifier 245. RBridges 222 and 224 send notification messages to RBridges 202, 204, 212, 214, and 216. The notification message specifies that virtual RBridge 240, which is associated with virtual RBridge identifier 245, is reachable via RBridges 222 and 224. RBridges 222 and 224 specify in the same message or in a different notification message that virtual appliance 250 is associated with service 270 and coupled to virtual switch 240.

Suppose that end devices 262 and 264 belong to a subnet which requires service 270. During operation, end device 262 sends a data frame to end device 264. RBridge 202 receives the data frame and detects the requirement of service 270 for the data frame. Based on the notification messages received from RBridges 222 and 224, RBridge 202 is aware of virtual appliance 250 and virtual RBridge 240. RBridge 202 encapsulates the data frame in a TRILL packet with virtual RBridge identifier 245 as the egress RBridge identifier and forwards the packet toward virtual RBridge 240.

RBridge 222 receives the packet via intermediate RBridge 212 and recognizes the packet to be destined to virtual RBridge 240. Because virtual RBridge 240 is associated with service 270 and the packet includes virtual RBridge identifier 245, RBridge 222 detects that the encapsulated data frame requires service 270. RBridge 222 extracts the data frame from the TRILL packet and forwards the data frame to locally coupled appliance 252. Upon receiving back the data frame from appliance 252, RBridge 222 identifies the destination MAC address of end device 264, encapsulates the data frame in a TRILL packet with an RBridge identifier of RBridge 204 as the egress RBridge identifier, and forwards the packet toward RBridge 204.

In the examples in FIGS. 1B and 1C, upon detecting appliance 136, switch 103 identifies appliance 136 to be associated with an existing service 153, and associates appliance 136 with corresponding virtual appliance 130. On the other hand, upon detecting appliance 142, switch 103 identifies appliance 142 to be associated with a new service 154 and creates a virtual appliance 140 for service 154. Hence, a respective member switch can dynamically add an appliance for an existing service, or insert a new service and a corresponding appliance in a fabric switch. FIG. 3A presents a flowchart illustrating the process of a member switch of a fabric switch dynamically adding an appliance to the fabric switch, in accordance with an embodiment of the present invention. Upon detecting a new appliance (operation 302), the switch marks the edge port coupling the appliance and identifies the service associated with the appliance (operation 304). In this way, the switch can take appropriate action to the data frames received from the edge port. The switch then checks whether the service exists in the fabric switch (operation 306).

If the service exists, the switch identifies the virtual appliance associated with the service (operation 320) and the virtual switch logically coupled to the virtual appliance (operation 322). The switch identifies the partner switches associated with the virtual switch (operation 324) and notifies the partner switches about the newly coupled appliance (operation 326). In some embodiments, the switch sends a notification message comprising information about the new appliance to notify the identified partner switches. The switch, in conjunction with the partner switches, associates the local switch with the virtual switch (operation 328). Through operation 328, the switch becomes logically coupled to the virtual switch, and other partner switches start considering the switch as a new partner switch for the virtual switch. The switch notifies other switches in the fabric switch about the virtual switch to be coupled to the local switch (operation 330). As a result, other switches can forward data frames destined to the virtual switch toward the switch.

If the service does not exist, the appliance is providing a new service. The switch creates a virtual appliance associated with the service (operation 310) and a virtual switch logically coupled to the virtual appliance (operation 312). The switch then generates a virtual switch identifier and assigns the virtual switch identifier to the virtual switch (operation 314). The switch notifies other member switches about the new virtual switch as a new member switch coupled to the local switch (operation 316). In some embodiments, the switch sends a notification message comprising the virtual switch identifier to notify other member switches. The switch notifies other member switches about the newly coupled appliance which provides a new service and is coupled to the virtual switch (operation 318). Note that other member switches may consider the virtual appliance and the virtual switch to be physical devices and physically coupled to each other.

FIG. 3B presents a flowchart illustrating the process of a member switch of a fabric switch dynamically configuring a service, in accordance with an embodiment of the present invention. The switch receives notifications about a new switch (operation 352) and a new appliance, which provides a new service and is coupled to the new switch (operation 354). The switch can receive these two notifications via a single message or a plurality of messages. Even though the new switch and new appliance are virtual devices logically coupled to each other, the switch may consider the appliance and the switch to be physical devices physically coupled to each other. The switch then becomes aware of the service available to the fabric. Hence, the switch configures the local switch to identify the data frames belonging to the subnet which requires the service (operation 356) and configures the local switch to forward the identified data frames to the new switch (operation 358).

Sequence of Execution

When a plurality of services are associated with a fabric switch, the services may require a specific sequence of execution. Such a sequence can be based on the interdependency and/or priority of the services. FIG. 4 illustrates an exemplary sequence of execution among dynamically inserted services in a fabric switch, in accordance with an embodiment of the present invention. As illustrated in FIG. 4, a fabric switch 400 includes member switches 401, 402, 403, 404, and 405. End devices 492 and 494 are coupled to fabric switch 400 via member switches 402 and 405, respectively. Examples of end devices 492 and 494 include, but are not limited to, a layer-2 switch, layer-3 router, top-of-the-rack switch, and physical or virtual host machine. In some embodiments, fabric switch 400 is a TRILL network; switches 401, 402, 403, 404, and 405 are RBridges; and data frames transmitted and received via inter-switch ports are encapsulated in TRILL headers.

Appliances 422 and 424 provide service 452 to fabric switch 400 and are coupled to member switches 401 and 404, respectively. Similarly, appliances 432 and 434 provide service 453 to fabric switch 400 and are coupled to member switches 403 and 404, respectively; and appliance 442 provides service 454 to fabric switch 400 and is coupled to member switch 403. Examples of a service include, but are not limited to, firewall, load balancing, intrusion detection/protection, network analysis, and network virtualization. Though appliance 434 is a physical machine, appliance 432 is a virtual machine running on a physical machine 431. Switches 401 and 404, in conjunction with each other, virtualize appliances 422 and 424 as a virtual appliance 420 coupled to fabric switch 400 via a virtual member switch 412. Similarly, appliances 432 and 434 are virtualized as a virtual appliance 430 coupled to a virtual switch 413; and appliance 442 is virtualized as a virtual appliance 440 coupled to a virtual switch 414.

Any of the member switches of fabric switch 400, such as switch 402, can receive a service configuration for a subnet. In some embodiments, a network administrator provides the service configuration to switch 402 (e.g., configures switch 402 with the service configuration). In this example, the service configuration specifies that the data frames belonging to the subnet require services 452, 453, and 454. The configuration also specifies the sequence of the required services to be services 452, 454, and 453. For example, if services 452, 453, and 454 correspond to firewall, load balancing, and intrusion detection, the sequence of the services specifies that a respective data frame belonging to the subnet should first be filtered with a firewall, then checked for intrusion, and finally forwarded based on a configured policy in a load balancer.

During operation, switch 402 receives from end device 492 a data frame, which belongs to the subnet and is destined to end device 494. Switch 402 identifies the initial service required for the data frame to be service 452, which is associated with virtual appliance 420. Switch 402 also identifies that virtual appliance 420 is coupled to virtual switch 412. Switch 402 forwards the data frame to virtual switch 412. The data frame is forwarded to switch 401 based on an internal routing policy of fabric switch 400. Switch 401 recognizes the received data frame to be destined to virtual switch 412 and realizes that the data frame requires service 452. Switch 401 forwards the data frame via port 462 to appliance 422, which provides service 452 to the data frame. For example, if service 452 is a firewall service, appliance 452 checks whether the data frame should be filtered or forwarded to the subnet. Because appliance 422 is coupled to switch 401 via port 462, when switch 401 receives the data frame back via port 462, switch 401 detects that appliance 422 has completed service 452.

Switch 401 checks for the next required service, if any, for the subnet and identifies service 454 to be the next service. Switch 401 identifies virtual appliance 440 associated with service 454. Switch 401 also identifies that virtual appliance 440 is coupled to virtual switch 414. Switch 401 forwards the data frame to virtual switch 414. Switch 403 receives the frame and detects that the data frame requires service 454. Switch 403 forwards the data frame via port 464 to appliance 442, which in turn, provides service 454 to the data frame. Because appliance 442 is coupled to switch 403 via port 464, when switch 403 receives the data frame back via port 464, switch 403 detects that appliance 442 has completed service 454.

Switch 403 then checks for the next required service, if any, for the subnet and identifies the next service to be service 453, which is associated with virtual appliance 430 coupled to virtual switch 413. Because switch 403 is a partner switch associated with virtual switch 413, switch 403 identifies locally coupled appliance 432 and forwards the data frame to appliance 432 via port 466. When switch 403 receives the data frame back via port 466, switch 403 realizes that appliance 432 has completed service 453. Upon completing the services, switch 403 forwards the data frame toward egress switch 405 based on the MAC address of end device 494.

FIG. 5A presents a flowchart illustrating the process of a member switch distributing a sequence of execution for a subnet among dynamically inserted services in a fabric switch, in accordance with an embodiment of the present invention. Upon receiving a service configuration for a subnet (operation 502), the switch identifies the sequence of execution for the services associated with the subnet (operation 504). In some embodiments, a respective member switch can belong to one or more subnets. The switch can optionally identify the member switches belonging to the subnet (operation 506). The switch creates a notification message comprising the sequence of execution (operation 508) and sends the message to a respective member switch (operation 510). The message can be a control message specific to the fabric switch. In some embodiments, the switch sends the message to only the member switches belonging to the subnet.

FIG. 5B presents a flowchart illustrating the process of a member switch configuring a sequence of execution for a subnet among dynamically inserted services in a fabric switch, in accordance with an embodiment of the present invention. The switch first receives a sequence of execution of services for a subnet (operation 552). The switch can receive the sequence of execution from a local configuration or a notification message from another member switch, as described in conjunction with FIG. 5A. The switch checks whether the initial service of the sequence is locally available (operation 554). If an appliance providing the service is coupled to the switch, the service is locally available. If the service is not locally available, the switch identifies the virtual appliance and the corresponding virtual switch associated with the initial service (operation 556). Note that the switch may consider the virtual appliance and the virtual switch to be physical devices and physically coupled to each other. The local switch configures itself to forward data frames of the subnet (i.e., data frames belonging to the subnet) to the identified virtual switch (operation 558). If the service is locally available, the local switch configures itself to forward frames of the subnet to the local appliance associated with the initial service (operation 560).

The switch checks whether the sequence has any other service (operation 562). If the sequence has more services, the switch configures the local switch to identify frames of the subnet received from the virtual or local switch associated with the current service in sequence (operation 564). For example, if the switch is a partner switch associated with the virtual switch, the switch can locally identify the frame, as described in conjunction with FIG. 4. Operation 564 ensures that the switch maintains the sequence of execution and facilitates detection of potential errors in the configuration of the sequence of execution.

The switch checks whether the next service of the sequence is locally available (operation 566). If the service is not locally available, the switch identifies the virtual appliance and the corresponding virtual switch associated with the service (operation 568). Note that the switch may consider the virtual appliance and the virtual switch to be physical devices and physically coupled to each other. The local switch configures itself to forward identified data frames to the identified virtual switch (operation 570). If the service is locally available, the local switch configures itself to forward the identified frames to the local appliance associated with the service (operation 572). The switch checks whether the sequence has any other service (operation 562) and continues to configure the local switch for the next services, if any.

Data Frame Processing

In the example in FIG. 2, member switches 202 and 222 couple an end device and an appliance via their respective edge ports. Hence, a member switch needs to distinguish between edge ports coupling an end device and an appliance. FIG. 6A presents a flowchart illustrating the process of a member switch of a fabric switch processing a data frame received from an edge port, in accordance with an embodiment of the present invention. Upon receiving a data frame via an edge port (operation 602), the switch checks whether the edge port couples an appliance (operation 604). In some embodiments, the switch marks an edge port coupling an appliance to distinguish the port from other edge ports, as described in conjunction with FIG. 3A.

If the port does not couple an appliance, the data frame is received from an end device. The switch identifies the subnet to which the data frame belongs (operation 606) and the initial service required for the data frame (operation 608). For a respective subnet, the switch can be configured with the required services and its corresponding order of execution, as described in conjunction with FIG. 5B. The switch checks whether the service is locally available (operation 610). A service is locally available if an appliance providing the service is coupled to a local edge port. If the service is not locally available, the switch identifies the virtual appliance associated with the service (operation 612) and forwards the frame toward the virtual switch coupled to the virtual appliance (operation 614).

If the service is locally available, the switch identifies the local edge port which couples the appliance associated with the service (operation 616) and transmits the frame to the identified edge port (operation 618). If the port couples an appliance (operation 604), the frame is from a local appliance after completion of a service. When the switch receives a data frame from an edge port coupling an appliance, the switch detects that the appliance has completed the associated service and the data frame is ready for further processing. For example, if the appliance is a firewall and if the data frame should not be forwarded to the subnet, the data frame is filtered at the firewall. If the switch receives the data frame back via the edge port coupling the firewall, the switch perceives the frame to be “allowable” for forwarding to the subnet.

The switch checks whether the sequence of execution for the subnet has any other service (operation 620). If so, the switch checks whether that service is locally available (operation 610) and continues to take action on the frame. If the sequence of execution for the subnet does not have any other service, the frame is ready for forwarding to its destination. The switch checks whether the destination of the frame is local (operation 622). If the destination is local, the switch transmits the frame based on the destination MAC address of the data frame (operation 624). For example, when the destination is a local end device, the switch transmits the frame to the edge port from which the switch has learned the MAC address of the end device. If the destination of the frame is not local, the switch identifies the member egress switch associated with the destination (operation 626) and forwards the data frame to the egress switch (operation 628). Because a respective member switch in a fabric switch shares the locally learned MAC addresses with other member switches, a respective member switch is aware of all end devices coupled to the entire fabric switch. In some embodiments, the switch encapsulates the data frame in a TRILL packet, sets the identifier of the egress switch as the egress RBridge identifier of the packet, and forwards the packet to the egress RBridge.

FIG. 6B presents a flowchart illustrating the process of a member switch of a fabric switch processing a data frame received from an inter-switch port, in accordance with an embodiment of the present invention. Upon receiving a data frame via an inter-switch port (operation 652), the switch checks whether the egress switch for the received data frame is the local switch (operation 654). If so, the switch transmits the data frame based on the destination MAC address of the data frame (operation 672), as described in conjunction with FIG. 6A. If the egress switch is not the local switch, the switch checks whether the egress switch for the received data frame is a virtual switch (operation 656). In some embodiments, the received data frame is encapsulated in a TRILL packet and the switch determines whether the egress switch for the received frame is the local or a virtual switch based on the egress RBridge identifier of the packet.

If the egress switch of the frame is not a local or virtual switch, the data frame is destined for another switch. The switch forwards the data frame to the next-hop switch based on the egress switch identifier (operation 674). In some embodiments, the data frame is encapsulated in a TRILL packet. Under such a scenario, the switch identifies the next-hop switch based on the egress RBridge identifier of the packet and sets the MAC address of the next-hop switch as the outer MAC address of the packet. If the egress switch of the frame is not the local switch but is a virtual switch (operations 654 and 656), the switch checks whether the virtual switch is logically coupled to a virtual appliance (operation 658). If the egress switch of the frame is not the local switch but is a virtual switch logically coupled to a virtual appliance, the switch identifies the local appliance associated with the virtual appliance, which is logically coupled to the virtual switch (operation 662) and transmits the data frame to the edge port coupling the identified appliance (operation 664).

If the egress switch of the frame is not the local switch but is a virtual switch not logically coupled to a virtual appliance (operations 654, 656, and 658), the virtual switch is associated with a different feature of the switch, such as virtual link aggregation, as specified in U.S. Patent Publication No. 2010/0246388, titled “Redundant Host Connection in a Routed Network;” or storage network virtualization, as specified in U.S. patent application Ser. No. 13/669,357, titled “Integrated Fibre Channel Support in an Ethernet Fabric Switch,” by inventors Phanidhar Koganti and Suresh Vobbilisetty, filed 5 Nov. 2012,” the disclosure of which is incorporated by reference herein. Hence, the switch forwards the data frame based on the switch feature associated with the virtual switch (operation 676).

Exemplary Switch

FIG. 7 illustrates an exemplary member switch with dynamic service insertion capability in a fabric switch, in accordance with an embodiment of the present invention. In this example, a switch 700 includes a number of communication ports 702, a sequence module 720, a service management module 730, a packet processor 710, and a storage 750. In some embodiments, switch 700 may maintain a membership in a fabric switch, wherein switch 700 also includes a fabric switch management module 760. Fabric switch management module 760 maintains a configuration database in storage 750 that maintains the configuration state of a respective switch within the fabric switch. Fabric switch management module 760 maintains the state of the fabric switch, which is used to join other switches. Under such a scenario, communication ports 702 can include inter-switch communication channels for communication within a fabric switch. This inter-switch communication channel can be implemented via a regular communication port and based on any open or proprietary format.

During operation, service management module 730 detects an appliance coupled to switch 700 via one of communication ports 702. Service management module 730 identifies the service provided by the appliance. Upon detecting the appliance, packet processor 710 constructs a notification message comprising information about the service and the appliance for a remote switch in the fabric switch. When the remote switch receives the notification message, the remote switch dynamically configures the local switch to send a respective data frame requiring the service to switch 700. Upon receiving a data frame belonging to a subnet which requires the service, packet processor 710 forwards the packet to the appliance via the communication port. When packet processor 710 receives the data frame back via the same communication port, service management module 730 considers the service to be completed for the data frame, as described in conjunction with FIG. 2.

In some embodiments, the switch also includes a virtualization module 732, which virtualizes the appliance and any other appliance providing the service as one virtual appliance, as described in conjunction with FIG. 3A. The virtualization module 732 can also virtualize the switch and any other switch in the fabric switch associated with the service as a virtual switch, as described in conjunction with FIG. 3A. While doing so, the virtualization module 732 generates a virtual identifier for the virtual switch. Packet processor 710 constructs a second notification message which presents the virtual switch to be coupled to the virtual appliance.

When a different member switch in the fabric switch notifies switch 700 about a second service, the packet processor forwards a respective data frame belonging to a subnet requiring the second service toward that other member switch. This other member switch can be a virtual switch identified by a virtual switch identifier. In some embodiments, the virtual switch identifier is a virtual RBridge identifier. Under such a scenario, packet processor 710 encapsulates the data frame in a TRILL packet with the virtual RBridge identifier as egress RBridge identifier of the packet, as described in conjunction with FIG. 2. Sequence module 720, upon receiving a sequence of execution associated with the subnet, determines whether to forward a data frame belonging to the subnet to the appliance or the appliance coupled to the virtual switch based on the sequence, as described in conjunction with FIG. 5B.

Note that the above-mentioned modules can be implemented in hardware as well as in software. In one embodiment, these modules can be embodied in computer-executable instructions stored in a memory which is coupled to one or more processors in switch 700. When executed, these instructions cause the processor(s) to perform the aforementioned functions.

In summary, embodiments of the present invention provide a switch and a method for dynamic service insertion in an Ethernet fabric switch. In one embodiment, the switch includes a service management module and a packet processor. During operation, the service management module identifies a service provided by an appliance coupled to the switch via a local port. The packet processor constructs a notification message for a remote switch. The notification message includes information about the service and the appliance. In this way, the switch allows the remote switch to request the service.

The methods and processes described herein can be embodied as code and/or data, which can be stored in a computer-readable non-transitory storage medium. When a computer system reads and executes the code and/or data stored on the computer-readable non-transitory storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the medium.

The methods and processes described herein can be executed by and/or included in hardware modules or apparatus. These modules or apparatus may include, but are not limited to, an application-specific integrated circuit (ASIC) chip, a field-programmable gate array (FPGA), a dedicated or shared processor that executes a particular software module or a piece of code at a particular time, and/or other programmable-logic devices now known or later developed. When the hardware modules or apparatus are activated, they perform the methods and processes included within them.

The foregoing descriptions of embodiments of the present invention have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit this disclosure. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. The scope of the present invention is defined by the appended claims.

Claims

1. A switch, comprising: service management circuitry configured to:identify an appliance and a service provided by the appliance via an edge port of the switch; andmarking the edge port of the switch to be associated with the appliance; andpacket processing circuitry configured to:in response to identifying the appliance, construct for a remote switch a notification message comprising information about the service and the appliance, wherein the switch and the remote switch are member switches of a network of interconnected switches, wherein a fabric identifier identifies the network of interconnected switches and is assigned to the switch and the remote switch, and wherein the information about the appliance indicates that the appliance is reachable via the switch; anddetermine that a data frame from the remote switch requires the service.

2. The switch of claim 1, wherein the appliance is a virtual appliance, wherein the virtual appliance is associated with one or more appliances providing the service.

3. The switch of claim 2, further comprising virtualization circuitry configured to generate a virtual switch identifier of a virtual switch associated with the switch; and wherein the packet processing circuitry is further configured to include in the notification message the virtual switch identifier, wherein the notification message indicates that the appliance is reachable via the virtual switch.

4. The switch of claim 3, wherein the virtual switch is further associated with a second switch; and wherein the second switch is coupled to a second appliance capable of providing the service and associated with the virtual appliance.

5. The switch of claim 1, wherein the packet processing circuitry is further configured to: extract information about a second service and a third appliance, wherein the third appliance is capable of providing the second service and reachable via a third switch; anddetermine the third switch as an egress switch for a respective data frame requiring the second service.

6. The switch of claim 5, further comprising sequence circuitry configured to: receive a sequence of execution for the service and the second service, wherein the sequence is associated with a subnet; anddetermine whether to forward a data frame belonging to the subnet to the appliance or the third appliance based on the sequence.

7. The switch of claim 5, wherein the packet processing circuitry is further configured to encapsulate the data frame with an encapsulation header comprising a switch identifier as an egress switch identifier; and wherein the switch identifier is associated with the third switch.

8. The switch of claim 1, wherein the service management circuitry is further configured to determine completion of the service for the data frame in response to receiving the data frame via the edge port.

9. The switch of claim 1, wherein inter-switch packets within the network of interconnected switches is encapsulated with an encapsulation header.

10. A method, comprising: identifying an appliance and a service provided by the appliance via an edge port of a switch;marking the edge port of the switch to be associated with the appliance;in response to identifying the appliance, constructing for a remote switch a notification message comprising information about the service and the appliance, wherein the switch and the remote switch are member switches of a network of interconnected switches, wherein a fabric identifier identifies the network of interconnected switches and is assigned to the switch and the remote switch, and wherein the information about the appliance indicates that the appliance is reachable the switch; anddetermining that a data frame from the remote switch requires the service.

11. The method of claim 10, wherein the appliance is a virtual appliance, wherein the virtual appliance is associated with one or more appliances providing the service.

12. The method of claim 11, further comprising: generating a virtual switch identifier of a virtual switch associated with the switch; andincluding in the notification message the virtual switch identifier, wherein the notification message indicates that the appliance is reachable via the virtual switch.

13. The method of claim 12, wherein the virtual switch is further associated with a second switch; and wherein the second switch is coupled to a second appliance capable of providing the service and associated with the virtual appliance.

14. The method of claim 10, further comprising: extracting information about a second service and a third appliance, wherein the third appliance is capable of providing the second service and reachable via a third switch; anddetermining the third switch as an egress switch for a respective data frame requiring the second service.

15. The method of claim 14, further comprising: receiving a sequence of execution for the service and the second service, wherein the sequence is associated with a subnet; anddetermining whether to forward a data frame belonging to the subnet to the appliance or the third appliance based on the sequence.

16. The method of claim 14, further comprising encapsulating the data frame with an encapsulation header comprising a switch identifier as an egress switch identifier; and wherein the switch identifier is associated with the third switch.

17. The method of claim 10, further comprising determining completion of the service for the data frame in response to receiving the data frame via the edge port.

18. The method of claim 10, wherein inter-switch packets within the network of interconnected switches is encapsulated with an encapsulation header.

19. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for securing a database configuration from undesired modifications, the method comprising: identifying an appliance and a service provided by the appliance via an edge port of a switch;marking the edge port of the switch to be associated with the appliance;in response to identifying the appliance, constructing for a remote switch a notification message comprising information about the service and the appliance, wherein the switch and the remote switch are member switches of a network of interconnected switches, wherein a fabric identifier identifies the network of interconnected switches and is assigned to the switch and the remote switch, and wherein the information about the appliance indicates that the appliance is reachable via the switch; anddetermining that a data frame from the remote switch requires the service, wherein the appliance is not coupled to a local port of the remote switch, and wherein the fabric identifier is assigned to the switch and the remote switch.

20. The computer-readable storage medium of claim 19, wherein the appliance is a virtual appliance, wherein the virtual appliance is associated with one or more appliances providing the service; andwherein the method further comprises: generating a virtual switch identifier of a virtual switch associated with the switch; andincluding in the notification message the virtual switch identifier, wherein the notification message indicates that the virtual appliance is reachable via the virtual switch.

21. A switch means, comprising: a service management means for: identifying an appliance means and a service provided by the appliance means via an edge port of the switch means; andmarking the edge port of the switch to be associated with the appliance; anda packet processor means for: in response to identifying the appliance, constructing for a remote switch means a notification message comprising information about the service and the appliance means, wherein the switch means and the remote switch means are member switches of a network of interconnected switch means, wherein a fabric identifier identifies the network of interconnected switch means and is assigned to the switch means and the remote switch means, and wherein the information about the appliance means indicates that the appliance means is reachable via the switch means; anddetermining that a data frame from the remote switch means requires the service.