Browse Prior Art Database

Method to name network shared locally attached devices using Low Latency Transport (LLT) Protocol

IP.com Disclosure Number: IPCOM000246668D
Publication Date: 2016-Jun-24
Document File: 4 page(s) / 68K

Publishing Venue

The IP.com Prior Art Database

Related People

Vikram Shantilal Chouhan: INVENTOR [+3]

Abstract

i. There are no solutions available which uses Transport Layer protocol like LLT to generate short, human readable and unique names. Also this method generates names such that portion of it denotes the Node owning the storage, which is always very helpful in solutions that provide network sharing of local storage like Flexible Storage Sharing (FSS).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 4

Method to name network shared locally attached devices using Low Latency Transport (LLT) Protocol

Vikram Shantilal Chouhan
Vivek Satpute Hari Vemuri

Abstract

i. There are no solutions available which uses Transport Layer protocol like LLT to generate short, human readable and unique names. Also this method generates names such that portion of it denotes the Node owning the storage, which is always very helpful in solutions that provide network sharing of local storage like Flexible Storage Sharing (FSS).

Problem Statement

Network sharing of local storage requires names of storage to be unique across the network. Locally assigned names cannot be used as they would conflict with the names of local storage on other nodes. Following are few other ways names can be unique for local storage devices:

1. Using ID provided by standards like WWN(World Wide Name) or SCSI 3 based EUI-64/IEEE/Vendor based IDs. But these IDs are not human readable.


2. Attaching Hostname of the storage owner node to their respective local devices as prefix or suffix. This approach is used in Flexible Storage Sharing (FSS). But this requires names of the host name to be unique across the network & also for readability hostnames should be short leading to scalability issues.

Thus require an approach which provides unique names for local storage but also makes sure that names are shorter, readable, and portion of it represent node owning the storage.

1

© 2016 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.


Page 02 of 4

Publication Description

Summary:
Solutions that provide network sharing of local storage like FSS (Flexible Storage Sharing), names of storage devices is created using Transport Layer attributes from Low Latency Protocol (LLT). LLT assigns unique Node ID to each node in a LLT cluster & unique cluster ID for a cluster within which nodes can communicate. These IDs are short & human readable. These IDs can be suffixed or prefixed or added in between to form short and readable device names which are unique across the network. And these names will intuitively provide the information about node owning the storage.

Detailed explanation:

For solutions that provide network sharing of local storage, name of storage should be unique, short & human readable. It should also provide information about the node owning the storage.

With new approach storage name contains the Transport Layer attributes from LLT like Node Identifier and Cluster Identifier. Node Identifier is a unique ID assigned by LLT for each node in the LLT cluster. Cluster Identifier is assigned to cluster within which each of the node can communicate using LLT protocol. Node Identifier with Cluster Identifier forms a unique ID for a node in LLT network. Thus these Identifiers together can be use...