EDG System Administration

The BPL are separate from the Board Station package, so I didn’t install them when I installed the BST package. I downloaded the file from the Mentor site. It’s in the same location as the BST package, just further down the page.

After untarring the files, I ran the install program. These files should be installed in the MGC_HOME location. The installation went ok, but I was getting error messages when I tried to place a component from the BPL in Design Architect. Problem was that the post_install_script hadn’t run and I didn’t get any errors about this. The message that I got was that $BPL_LIB/components/… couldn’t be found. And that was true, there was no components directory in the $BPL_LIB location. After looking around the Mentor support site, I found that I needed to run the post_install_script. Here is the syntax:

./post_install_script -target /net/sw/BST2005/2005BST/MGC_HOME.ixl -msicmd /net/sw/BST2005/2005BST/MGC_HOME.ixl/_msidata -mgchome /net/sw/BST2005/2005BST/MGC_HOME.ixl -vco ixl

Had the problem where this wouldn’t run because it said I didn’t have a bplcaddata license. Not true. We did have that license in our file. Turns out that this program doesn’t use the MGLS_LICENSE_FILE variable. It only looks at LM_LICENSE_FILE. So once I set that, the script completed. There is now a components directory in the $BPL_LIB directory. Just make sure that the entry in mgc_location_map is correct.

We used to use horde to provide our webmail service, but redhat now provides squirrelmail for this purpose. So, installed the package with up2date:

up2date squirrelmail

This also installed package: php-mbstring

Instructions are to restart httpd and go to http:///webmail. Unfortunately, this doesn’t let me log in. Problem has to do with our only allowing imaps connections and not imap connections. To fix this, go to:

/usr/share/squirrelmail/config and run:

./conf.php

Then go through and change the settings to match our site. After changing everything, I was allowed to log in.

Eldo is part of the AMS package from Mentor Graphics. Download and untar this package and run instix to start the installation.

Installation Directory: /net/sw/ams_2006.1
Selected all packages

It wants the following environment variables set:

MGC_AMS_HOME /net/sw/ams_2006.1
PATH +$MGC_AMS_HOME/bin: $MGC_AMS_HOME/modeltech/bin

Installation test can then be done with:

systest eldo | adms | adtb | bmc | mach | all
I ran systest all

One complaint was that matlab was missing, so now I can finally order it and install it on the new server.

To run Mentor Graphics programs on windows machines in the shop, must first be start an X server. Either X-Win32 or XVision will work. Mentor’s fonts must be included in whichever program is started. They can be added by getting to the config window of either program, find fonts and add s:\mgc_fonts\edgfonts to the list. If these fonts were not already there, you will need to restart the X server for them to take effect. Also make sure that you are tunnelling your X connection. The easy way to check that X is working properly is to ssh to whichever machine you want to use and run xlogo. This should pop-up a window with an X in it. If it appears, X is working. If not, you need to fix X before proceeding.

On linux or mac machines, open a terminal and run:

xset fp+ tcp/:7100

This will add the fonts for Mentor Graphics. Then, ssh to whichever machine you want to use and run your Mentor programs.

The shop server xfs was set up by running the following commands:

mkdir $MGC_HOME/registry/mgcfonts
$MGC_HOME/bin/mgc_font_collect -p $MGC_HOME/registry/edgfonts
in $MGC_HOME/registry/edgfonts, run mkfontdir

Edit /etc/X11/fs/config and add the above edgfonts directory to the catalogue. I put in the hard path to it, instead of using the environment variable. Also comment out the line, no-listen=tcp, which didn’t allow xfs to listen to tcp ports. Then restart xfs.

To add printers to Mentor Graphics, create the fis and config files in /net/sw/mgc/printer/[config,fis]
for each printer.  Edit the pet file in /net/sw/mgc/printer/config/pet to show the new printer.  Note that MGC_PLOT_OPTIONS should be set to /net/sw/mgc/config/printer so that it can find the pet file.  It’s located here, so printers only have to be set once for all machines.  With linux, a problem arose that raw printing was not enabled by default.  According to technote mg44859, must edit the files /etc/cups/[mime.types,mime.conv] and uncomment out the lines application/octet-stream.  Restart cups and plot_test should work.

Turned off openldap because it just had too many problems. My biggest issue was that it would allow ssh logins to a machine, but it would not allow console logins. I have no idea why. Since, in our case, most of the logins are console logins, this turned out to be a HUGE problem. I’ll continue to test openldap with a test case, but definitely cannot yet use it on our production machines. I’ll have to come up with a different way of syncing passwords between machines.