IP Centric Control Plane for Survivable WDM Mesh Networks

1. THE OMEGA TESTBED Optical Mesh network for Emerging Gigabit Applications Sanjeev Lakshmanan, Dhruvish Shah, Kishore Gadhiraju, Marco Tacca, Andrea Fumagalli Optical Networking Advanced Research(OpNeAR) Lab The University of Texas at Dallas HARDWARE FEATURES MODULES • The hardware is emulated • 5 Linux PC’s act as controllers, run the software • 7 Fast Ethernet links to form a Mesh Topology • An electronic crossbar switch emulates a crossconnect and is controlled by a device driver • A delay element provides a configurable delay on the ethernet links with a maximum delay of 7.9ms • Generator – RWA & traffic generation • Receiver – RSVP & Protection switching • LMP – Link Management Protocol for detection of link and node failures • Synchronizer – Database synchronization • Cacher – For periodically discarding the old packets from the network • UNI - User to Network Interface for management and debugging • IP Centric Control Plane for Survivable WDM Mesh Networks • Overlay Model with a Distributed Architecture • Shared Path Protection with Differentiated Reliability • Graphical User Interface * *Project is in collaboration with CpQD, Brazil • Link Management Protocol (LMP) runs between adjacent nodes of every link • Each node sends HELLO messages every 5 ms • Failure is defined as the loss of 4 consecutive HELLO messages(20 ms) • Recovery is defined as the reception of 100 consecutive HELLO messages(500 ms) RSVP LINK MANAGEMENT PROTOCOL • A Resource Reservation protocol responsible for dynamic end-end lightpath setup and release • Incoming connection requests enter any node, which is then designated as the owner of that connection • The owner node runs the RWA, based on Shortest Path routing and Least Loaded Wavelength assignment, to find the working and protection paths • The owner node first sets up the working path and then reserves resources for the protection path WORKING PATH SETUP • It initiates the Reservation procedure by sending a LIGHTPATH_CREATE_TRY to the source node • Each node in the path switches the ports of the OXC, and forwards the message to the next node in sequence. • In case of a failure, the node sends a LIGHTPATH_CREATE_FAIL to the previous node in sequence and this message propagates all the way back to the owner node. • In case of a success on all the nodes in the path, the destination node sends a SUCCESS message to the source node • The source node floods the SUCCESS message LMP PROTECTION RESOURCES RESERVATION