FaxFep

UserPreferences

A fax FEP (Front End Processor) is a 386 PC used as a front end processor that contains fax boards for submission and delivery of G3 faxes, and voice cards (inbound) that provide user interface. There are some 486's that are used as SSD feps for inbound fax guest access via customer specific 800 numbers.

For more information, see Node Hardware

rehoming

txbu_root > fepcontrol status all 
FEP     PROC   FEP   DMN        |- - - - - - - - -PORT STATUS- - - - - - - - -| 
NAME   STATUS  STAT  STAT  HOST 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 
-----  ------  ----  ----  ---- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
txauf  active    on    on  Ccab  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txavf  active    on    on  Ccab  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txawf  active    on    on  Aacb  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txaxf  active    on    on  Cacb  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txayf  active    on    on  Aabc  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txazf  active    on    on  Bbac  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
 [ etc. ] 

Note that for txaxf the first two characters in the HOST column do not match:

• The 1st character (upper case) indicates what machine the FEP should be on
• The 2nd is what it actually is on
• 3rd and 4th are alternates

To put the FEP back on its standard machine,

• fepcontrol -v stdhome fepname (e.g. in this case txaxf)

 
txbu_root > fepcontrol -v stdhome txaxf 
        /usr/lbin/dk txaxf 'SPREADDELAY=-1 /usr/faxbin/fepconfig' -R 
txcu:mail: 
  
txbu_root > fepcontrol status all 
FEP     PROC   FEP   DMN        |- - - - - - - - -PORT STATUS- - - - - - - - -| 
NAME   STATUS  STAT  STAT  HOST 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 
-----  ------  ----  ----  ---- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
txauf  active    on    on  Ccab  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txavf  active    on    on  Ccab  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txawf  active    on    on  Aacb  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txaxf  active    on    on  Aacb  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txayf  active    on    on  Aabc  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
txazf  active    on    on  Bbac  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  o  
 [ etc. ] 

Note that txaxf is now on the correct FEP.

Each 5-letter FaxFep (e.g. TXAUF) has remote file systems mounted on it, e.g. rtx1. If for some reason the connection between the machines is disturbed, the link to the filesystem may become severed. If this occurs, the filesystem must be unmounted and remounted.

To check for severed links, run the following command on the 4-letter node processor:

ckfeps -c ls  
Command options? : -ld rtx1? 

(-i for only inbound, -o for only outbound,)

Check the dates; if old then links are severed. To unmount and remount on multiple Feps:

ckfeps -o -c umount 

1. Do mount and check for spoolers.
2. df -t
3. If severed, type:

umount -d xx.rxxn (e.g. tx.rtx1)

4. mount -d xx.rxxn /rxxn
5. ps -ef|grep fsdemon (get pid)
6. kill pid
7. tail -f /usr/fx/logs/fsdemon (make sure rescanning)

idbu_root > ckfeps  -o -c ls 
Command options? : -ld rid* 
 
        Configured Outbounds: au av aw ax ay az ba 
 
************************* OUT ************************* 
s5/idauf (1)    : ================================= 
drwxrwxrwx  24 root     root         480 Apr 21 02:22 rid1 
drwxrwxrwx  23 root     root         464 Apr 20 22:48 rid2 
drwxrwxrwx  23 root     root         512 Apr 21 00:40 rid3 
drwxrwxrwx  23 root     root         480 Apr 20 23:31 rid4 
drwxrwxrwx  20 root     root         416 Apr 20 21:35 rid5 
drwxrwxrwx  20 root     root         512 Apr 21 00:17 rid6 
s5/idavf (2)    : ================================= 
drwxrwxrwx  24 root     root         480 Apr 21 02:22 rid1 
drwxrwxrwx  23 root     root         464 Apr 20 22:48 rid2 
drwxrwxrwx  23 root     root         512 Apr 21 00:40 rid3 
drwxrwxrwx  23 root     root         480 Apr 20 23:31 rid4 
drwxrwxrwx  20 root     root         416 Apr 20 21:35 rid5 
drwxrwxrwx  20 root     root         512 Apr 21 00:17 rid6 
s5/idawf (3)    : ================================= 
 
 
 
 
ndauf_root >mount 
/ on /dev/dsk/0s1 read/write on Mon Mar 27 23:37:23 1995 
/usr on /dev/dsk/0s3 read/write on Mon Mar 27 23:37:28 1995 
/rnd3 on nd.rnd3 read/write/remote on Mon Mar 27 23:44:36 1995 
/rnd4 on nd.rnd4 read/write/remote on Mon Mar 27 23:44:52 1995 
/rnd5 on nd.rnd5 read/write/remote on Mon Mar 27 23:45:41 1995 
/rnd6 on nd.rnd6 read/write/remote on Mon Mar 27 23:46:35 1995 
/mail on ndcu:mail read/write/remote on Tue Mar 28 00:01:08 1995 
/rnd1 on nd.rnd1 read/write/remote on Thu Mar 30 02:21:09 1995 
/rnd2 on nd.rnd2 read/write/remote on Fri Mar 31 21:49:23 1995 
 
ndauf_root >ls -ld /rnd? 
/rnd1: Link has been severed 
drwxrwxrwx  21 root     root         512 Mar 31 23:23 /rnd2 
drwxrwxrwx  21 root     root         512 Mar 31 23:26 /rnd3 
drwxrwxrwx  21 root     root         512 Mar 31 23:30 /rnd4 
drwxrwxrwx  21 root     root         512 Mar 31 23:23 /rnd5 
drwxrwxrwx  21 root     root         512 Mar 31 23:42 /rnd6 
 
ndauf_root >umount -d nd.rnd1 
ndauf_root >mount -d nd.rnd1 /rnd1 
 
ndauf_root >ls -ld /rnd? 
drwxrwxrwx  21 root     root         512 Mar 31 23:24 /rnd1 
drwxrwxrwx  21 root     root         512 Mar 31 23:23 /rnd2 
drwxrwxrwx  21 root     root         512 Mar 31 23:26 /rnd3 
drwxrwxrwx  21 root     root         512 Mar 31 23:30 /rnd4 
drwxrwxrwx  21 root     root         512 Mar 31 23:44 /rnd5 
drwxrwxrwx  21 root     root         512 Mar 31 23:42 /rnd6 

more needed, please add

To shutdown a fep, first type:

fepconfig -f off

Then:

shutdown -i6 -y -g0

After it comes up, type:

fepconfig -f on

Faxes not going out:

FaxQ:rln3,441638560699,lnauf,7 hrs,fax.96

This alarm occurs on FaxFep boxes. In this case, faxes have been waiting to go out for 7 hours. For the following examples, spooler rln3 will be assumed.

1. Go on the associated machine. In this case, LNBU. (Why? LNAUF is on LNAU/LNBU/LNCU, and spooler rln3 is located on the B node.)
2. fssum lists faxes waiting to go out on each spooler (rln3, rln4, etc.)
3. If faxes have been waiting and excessive time, go into the phone number's directory:
• cd /rln3/phone/441638560699/fax.96
4. rm rfep
5. run fssum again; it recreates the rfep files and reschedules

Faxes should canceled out after a certain number of hours of being attempted to be sent; sometimes for some reason this does not happen by itself. That's when we get the alarm and need to do the following:

1. Try to call number and see if valid fax tone
2. If not, use following command to cancel fax and send ndn to sender:
• prcancel -f rln3 -n 441638560699
3. If valid fax tone, check the rfep file to see if it is valid:
• cd /rln3/phone/441638560699/fax.96
• You can also ls -al /rln*/ph*/*/f*/rfep

If a number has an rfep file that is 0 size, rm rfep file, and it will recreate itself. Once you remove the rfep file, type orphan to assign a faxfep to the fax number you just removed the rfep file for; fax should reschedule itself.

Bringing up a crashed machine from firmware mode (shutdown -i5, or system crash into firmware hard boot)

Move file systems to proper backup machines, by running outage and checking where the abandoned file systems should go:

tjau_root > outage 
 
========================================== 
The following auth processes should be active on the tj node 
NO AUTH PROCESS'S FOUND 
========================================== 
The following filesystems can be moved off of tjau TO: 
05000     Mir001 Sa=62,94     Move to: tjbu Sb=82,74     ... 
15000     Mir003 Sa=72,84     Move to: tjcu Sc=92,64     ... 
rtj1      Mir002 Sa=63,95     Move to: tjbu Sb=83,75     ... 
rtj2      Mir004 Sa=73,85     Move to: tjcu Sc=93,65     ... 
=========================================== 
The following filesystems can be moved off of tjbu TO: 
25000     Mir005 Sb=62,94     Move to: tjcu Sc=82,74     ... 
35000     Mir007 Sb=72,84     Move to: tjau Sa=92,64     ... 
rtj3      Mir006 Sb=63,95     Move to: tjcu Sc=83,75     ... 
rtj4      Mir008 Sb=73,85     Move to: tjau Sa=93,65     ... 
============================================ 
The following filesystems can be moved off of tjcu TO: 
45000     Mir009 Sc=62,94     Move to: tjau Sa=82,74     ... 
55000     Mir011 Sc=72,84     Move to: tjbu Sb=92,64     ... 
rtj5      Mir010 Sc=63,95     Move to: tjau Sa=83,75     ... 
rtj6      Mir012 Sc=73,85     Move to: tjbu Sb=93,65     ... 

This shows that file system 45000, which normally runs on TJCU should be moved to TJAU if TJCU is not functioning. (No release is needed, since the machine has crashed and the filesystems are currently not being used.)

tjau_root > activate -y -f tj45000  

This will activate the dumped file system on its temporary machine TJAU (listed in outage above).

Repeat the above step for other orphaned file systems. In this case it would be 55000, which would need to be moved to TJBU.

Spoolers (rtj1, etc.) don't need to be moved to a temporary machine unless the machine is to be out of service for a while.

After activating file systems on the proper machine, bring up the downed machine. A phone call to the location may be needed for a hard reboot.

1. Enter mcp at the firmware mode prompt.
2. At prompt run filletd
3. Hit enter at the next 2 prompts (for SCSI and disk system scans)
4. At the next prompt run /etc/system to bring up the system. (It may prompt you for /unix, use /etc/system instead.)
• Most likely the machine will run file system scans. This can take from 15 minutes to an hour to run.
5. Hit enter at the next 2 prompts for scsi system scans.
6. Login to machine as root
7. Run /etc/startup to get the machine fully loaded for network use.
8. After you get the INITILIZATION COMPLETE prompt run service -B to get all the Easylink Services started
9. Release the file systems from the backup machines and activate them on the original machine, one at a time.
1. release file system name should be run on the machine the file system has been moved to
2. Activate the file systems (including spoolers (rtj1 etc)) on the original machine
• activate -y -f file system name (e.g. tj45000)
10. Check processes by running setsvc;showstatus. If the machine is an int'l node, then make sure AUTH is running on the proper machine by running outage

Miscellaneous

Logs are in:

• /usr/fx*/logs/fs*
• /usr/fx*/logs/fax*
• /usr/fx*/logs/out*

If a filesystem cannot be activated, and it seems there's something wrong with the mirrors, release, remove /xxnn000/crdir/mirrortable and reactivate.