Heterogeneous media packet bridging

• US 9,853,917 B2
• Filed: 06/24/2016
• Issued: 12/26/2017
• Est. Priority Date: 08/27/2003
• Status: Expired due to Term

• Current Assignee: Fortinet Inc.
• Original Assignee: Fortinet Inc.
• Inventors: Desai, Sachin, Balay, Rajesh, Sargor, Chandramouli
• Primary Examiner(s): Oveissi, David
• Application Number:
  US15/192,115
• Publication Number:
  US 20160308788A1
• Time in Patent Office: 550 Days
• CPC Class Codes: H04L 12/46 Interconnection of networks
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 49/25 Routing or path finding in a switch fabric
• CPC Class Codes: H04L 49/354 for supporting virtual local area networks [VLAN]

Abstract

Methods and systems for bridging network packets transmitted over heterogeneous media channels are provided. According to one embodiment, a network device maintains translation data structures defining translations among multiple framing media formats used for transmitting or receiving network packets via multiple supported media transmission channels, including (i) between a first framing media format and an intermediate format and (ii) between the intermediate format and a second framing media format. A virtual bridging application representing a single bridging domain for bridging all network traffic traversing the network device translates ingress network packets from the first framing media format to egress network packets of the second framing media format based the translation data structures.

Claims

1. A blade server comprising:

a plurality of network modules, including;

a first set of network modules within a first server blade that receives, via a first set of line interface ports, network packets having a first framing media format of a plurality of framing media formats; and

a second set of network modules within a second server blade that transmits, via a second set of line interface ports, network packets having a second framing media format of the plurality of framing media formats;

a plurality of processing resources within one or more server blades coupled to the plurality of network modules and shared by the plurality of network modules, including a first processing resource upon which a virtual bridging application executes, wherein the virtual bridging application represents a single bridging domain for bridging all media transmissions traversing the blade server;

a non-transitory memory, accessible to the first processing resource, having stored therein one or more translation data structures defining translations between the first framing media format and an intermediate format and between the intermediate format and the second framing media format;

the first set of network modules pass a received network packet to the virtual bridging application;

the virtual bridging application determines whether a relay location to which the received network packet is to be relayed is among the second set of network modules, which are associated with a disparate framing media format and a disparate media channel than that of the first set of network modules; and

responsive to an affirmative determination, the virtual bridging application translates the received network packet to the second framing media format based on the one or more translation data structures before relaying the received network packet to the relay location.

2. The blade server of claim 1, further comprising a switching fabric server blade, coupled to the plurality of network modules, forwarding the network packets received from the first set of network modules to one or more of the plurality of processing resources.

3. The blade server of claim 1, wherein the plurality of framing media formats include one or more of Asynchronous Transfer Mode (ATM), Gigabit Ethernet (GigE), Frame Relay (FR), Time-Division Multiplexing (TDM) and a wireless media format.

4. The blade server of claim 1, wherein the one or more translation data structures are dynamically configurable, thereby allowing the virtual bridging application to be dynamically configured to accommodate framing media translations among one or more other framing media formats outside of the plurality of framing media formats.

5. The blade server of claim 4, wherein a first application running on the second processing resource performs one or more translations/operations on the received network packet relating to:

forwarding, routing, encryption, decryption or authentication.

6. The blade server of claim 1, wherein the virtual bridging application assists in connection with bridging between a first media channel associated with a first network module of the first set of network modules and a second media channel associated with a second network module in the second set of network modules by relaying the received network packet to one or more other applications running on a second processing resource of the plurality of processing resources.

7. The blade server of claim 1, wherein the virtual bridging application is dynamically instantiated, configured or modified using a graphical user interface application.

8. The blade server of claim 7, wherein the API is provided in a form of one or more Dynamic Linked Libraries (DLLs).

9. The blade server of claim 7, wherein the API is provided in a form of a shared library.

10. The blade server of claim 1, wherein the virtual bridging application is implemented as an Application Programming Interface (API) library.

11. The blade server of claim 1, wherein the virtual bridging application is provided in a form of an object-oriented class object having public and private methods.

12. The blade server of claim 1, wherein the network packet comprises an Ethernet frame and the virtual bridging application permits media agnostic Ethernet bridging between the first set of network modules and the second set of network modules.

13. The blade server of claim 12, wherein the metadata includes Ethernet header data that is transmitted in a form of network packets encapsulated within a first plurality of media transmissions.

14. The blade server of claim 1, wherein the one or more translation data structures include metadata associated with network packets encapsulated within a first plurality of media transmissions.

15. A method comprising:

maintaining, within a memory of a network device, one or more translation data structures defining translations (i) between a first framing media format of a plurality of framing media formats and an intermediate format and (ii) between the intermediate format and a second framing media format of the plurality of framing media formats, wherein the plurality of framing media formats are used for transmitting or receiving network packets via a plurality of media transmission channels supported by the network device;

receiving, via a first media transmission channel of the plurality of media transmission channels by a first network interface of a first network module of a plurality of network modules of a network device, a network packet formatted in accordance with a first framing media format of the plurality of framing media formats;

directing, by the first network module, the network packet to a virtual bridging application running on a first processing resource of a plurality of processing resources of the network device, wherein the virtual bridging application represents a single bridging domain for bridging all network traffic traversing the network device having an inbound framing media format of the plurality of framing media formats that differs from an outbound framing media format of the plurality of framing media formats;

determining, by the virtual bridging application, whether a relay location to which the network packet is to be relayed is a second network module of the plurality of network modules that is associated with the second framing media format;

responsive to an affirmative determination, translating, by the virtual bridging application, the network packet to the second framing media format based on the one or more translation data structures before relaying the translated network packet to the relay location; and

transmitting, via a second media transmission channel of the plurality of media transmission channels that is associated with a second network interface of the second network module, the translated network packet to a destination specified by the translated network packet.

16. The method of claim 15, wherein the virtual bridging application assists in connection with bridging between the first media channel associated and a second media channel associated with the second network interface by relaying the translated network packet to one or more other applications running on a second processing resource of the plurality of processing resources.

17. The method of claim 16, further comprising performing, by a first application running on the second processing resource, one or more operations on the translated network packet relating to forwarding, routing, encryption, decryption or authentication.

18. The method of claim 15, further comprising, receiving, via a graphical user interface of the network device, information according to which the virtual bridging application is dynamically instantiated, configured or modified.

19. The method of claim 15, wherein the virtual bridging application is implemented as an Application Programming Interface (API) library, provided in a form of one or more Dynamic Linked Libraries (DLLs), provided in a form of a shared library or provided in a form of an object-oriented class object having public and private methods.

20. The method of claim 15, wherein the network packet comprises an Ethernet frame and the virtual bridging application facilitates media agnostic Ethernet bridging between the first media transmission channel and the second media transmission channel.

21. The method of claim 15, wherein the plurality of framing media formats include one or more of Asynchronous Transfer Mode (ATM), Gigabit Ethernet (GigE), Frame Relay (FR), Time-Division Multiplexing (TDM) and a wireless media format.