C2S

Unique Identifier to be essentially adopted and implemented by all institutions for accessing the EDA Tools licenses under C2S Programme

The SPOC/ Chief Investigator (CI)/ Co-CI must ensure that all users at the institution (including students and faculty members) accessing the EDA Tools licenses under C2S Programme follow the Unique Identifier Approach outlined below (i.e. username@hostname.domainname) for identifying the unique users at the institution. This is required by MietY for effective license administration.

Guidelines for adopting the nomenclature of Unique Identifier : `username@hostname.domainname`

<username> : A username is a unique identifier for an user account on the System (Workstation, Server etc.), where the EDA tools are installed. This allows him the login access to the System.

Examples: vijay, shruti, user1
ChipIN Centre Requirement: Each username within the institution may be unique; as a non-mandatory requirement.
<hostname> : A hostname is a unique label assigned to a Computer, Device or Network node connected to a computer network. It identifies the Device within the network and can be used instead of an IP address to facilitate easier communication.
The hostname may be selected by the institute to align with the name of the Department, Division, Lab etc; wherein the Workstations/ Servers hosting the EDA Tools are positioned within the institute. There may be a number of hostnames in the institution.

Examples: vlsilab1, cse-ws04, edaserver09, simlab-ws7
ChipIN Centre Requirement: Each hostname within the institution must be unique; as a mandatory requirement.
<domainname> : A Fully Qualified Domain Name (FQDN) is the complete and specific name that uniquely identifies the institute through public DNS (Domain Name System) hierarchy.

Example: cdac.in, nielit.gov.in, iitm.ac.in
ChipIN Centre Requirement: The domainname must match to the institute's official website or official email domain; as a mandatory requirement.

User Manual and Bash-Script

User Manual: Download User Manual

Bash-Script for Changing the Hostname: Download Bash-Script

The institutions who have adopted & implemented the instructions of unique Host-ID(s) shall submit it's details at ChipIN support portal (https://chipin.cdacb.in/) as per steps mentioned - [ View ]

FAQs

1. What are the valid characters for username, hostname, and domainname?

Ans: Only the following characters are permitted as per "RFC 822": a-z, A-Z, 0-9 and "-"

2. Do username lists need to be shared with ChipIN Centre?

Ans: No, only the list of "hostname" with "domainname" need to be shared with ChipIN Centre for whitelisting.

3. Will the hostname be verified by ChipIN Centre?

Ans: No, only the "domainname" will be verified with the institute's official website or official email.

4. Will EDA tool license access be restricted based on the username?

Ans: No, license access will be restricted only for declared "hostname"s with the "domainname".

5. Will changing the "hostname" and "domainname" affect any other applications?

Ans: Any hosted-services on the server may be affected such as webserver, email-server but will not affect accessing such services. (Please check with your IT team for more clarification.)

6. Does changing the hostname require root/escalated privileges?

Ans: Yes, once, at the time of changing the hostname. (Please follow the manual and use the script for ease of changing hostname.)

7. Should the system-hostname consist of "domainname"?

Ans: Yes, the hostname of all the systems that are running EDA Tools must have "hostname.domainname". Hostname without the domainname is invalid. Example: "chipcentre03.cdacb.in" where "chipcentre03" is hostname and "cdacb.in" is the domainname.

8. Do access-terminals/thin-clients/dump-terminals also require a change of hostname?

Ans: No, required only on the system where the EDA Tools are installed and executed but not required on the systems used only for connecting to the remote server to execute the EDA Tools through X11 or VNC.

9. Can we use the same username on different systems?

Ans: Yes, the username must be unique within the system, but it can be the same in other systems across the network.