Conference lassie::ucx

	Tim,

	Here is what I was told from customer:

	SNMP behaviour with MOP (DECnet Phase IV) enabled:

	Two processes generated, UCX$ESNMP and UCX$OS_MIBS. The latter
	generates a network pseudo interface, like EWAn, runs out of
	BYTLM, interface disappears. The same thing happens again, un-
	til some limit on numbers of interfaces is reached, then nothing
	more happens.

	SNMP behaviour with MOP disabled:

	Process UCX$ESNMP is not generated, UCX$OS_MIBS creates a log
	file with something like 'timeout, restart protocol failed, lost
	connection with master agent'. Also, in ACCOUNTING, an entry with
	SYSTEM-F-ROPRAND, reserved operand fault, appears. No network in-
	terface is generated.

	Hope this helps,

	Poul

    What happens if you raise the BYTLM (say, x 10)?  Does the subagent
    continue to consume until it reaches quota and dies anyway?
    
    The MOP problem is known and will need a patch.  The BYTLM issue may
    simply be a configuraiton issue that can be worked around until the
    installation procedure is changed to set it up right.
    
    tim
    

    
    Tim,
    
    I'm not sure exactly where to raise it...in a command procedure, UAF,
    PQL? Please tell me..
    
    Poul
    

    In the UAF.
    

	Hi,

	Customer tried to raise BYTLM X10. SNMP then lived a little
	longer, then same thing happened:

UAF> sh *snmp*

Username: UCX$SNMP                         Owner:  UCX$SNMP
Account:  UCX$SNMP                         UIC:    [500,7] ([UCX$AUX,UCX$SN=
MP])
CLI:      DCL                              Tables: DCLTABLES
Default:  SYS$SYSDEVICE:[UCX$SNMP]
LGICMD:   LOGIN
Flags:  Restricted
Primary days:   Mon Tue Wed Thu Fri
Secondary days:                     Sat Sun
Primary   000000000011111111112222  Secondary 000000000011111111112222
Day Hours 012345678901234567890123  Day Hours 012345678901234567890123
Network:  ##### Full access ######            ##### Full access ######
Batch:    -----  No access  ------            -----  No access  ------
Local:    -----  No access  ------            -----  No access  ------
Dialup:   -----  No access  ------            -----  No access  ------
Remote:   -----  No access  ------            -----  No access  ------
Expiration:            (none)    Pwdminimum:  5   Login Fails:     0
Pwdlifetime:           (none)    Pwdchange:      (pre-expired)
Last Login:            (none) (interactive),  7-JAN-1997 10:44 (non-interac=
tive)
Maxjobs:         0  Fillm:        20  Bytlm:        52200
Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
Maxdetach:       0  BIOlm:        18  JTquota:       1024
Prclm:          10  DIOlm:        18  WSdef:          350
Prio:            8  ASTlm:       100  WSquo:          500
Queprio:         0  TQElm:        10  WSextent:       500
CPU:        (none)  Enqlm:       300  Pgflquo:      10240
Authorized Privileges:
  NETMBX    TMPMBX
Default Privileges
  NETMBX    TMPMBX
UAF> modi ucx$snmp/bytlm=522000
%UAF-I-MDFYMSG, user record(s) updated
UAF> exit
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-NAFNOMODS, no modifications made to network proxy database
%UAF-I-RDBNOMODS, no modifications made to rights database
$
$ @ucx$snmp_startup
%RUN-S-PROC_ID, identification of created process is 6060063F
%RUN-S-PROC_ID, identification of created process is 60600640
$ sh proc/id=6060063F

11-FEB-1997 10:36:38.24   User: SYSTEM           Process ID:   6060063F
                          Node: RISVX3           Process name: "ucx$esnmp"

Terminal:
User Identifier:    [UCX$AUX,UCX$SNMP]
Base priority:      4
Default file spec:  Not available

Devices allocated:  BG652:
                    BG653:
                    BG654:
                    BG655:
                    BG657
$ sh proc/id=60600640

11-FEB-1997 10:36:49.79   User: SYSTEM           Process ID:   60600640
                          Node: RISVX3           Process name: "ucx$os_mibs=
"

Terminal:
User Identifier:    [UCX$AUX,UCX$SNMP]
Base priority:      4
Default file spec:  Not available

Devices allocated:  ESA51:
                    ESA52:
                    ESA53:
                    ESA54:
                    BG651:
                    BG656:
                    BG658:
$

-- after a while:

$ sh proc/id=6060063F

11-FEB-1997 10:37:51.85   User: SYSTEM           Process ID:   6060063F
                          Node: RISVX3           Process name: "ucx$esnmp"

Terminal:
User Identifier:    [UCX$AUX,UCX$SNMP]
Base priority:      4
Default file spec:  Not available

Devices allocated:  BG652:
                    BG653:
                    BG654:
                    BG655:
                    BG657:
$ sh proc/id=60600640
%SYSTEM-W-NONEXPR, nonexistent process
$
$ acc/sin=10:30/full


DETACHED Process Termination
----------------------------
Username:          SYSTEM            UIC:               [UCX$AUX,UCX$SNMP]
Account:           SYSTEM            Finish time:       11-FEB-1997 10:37:0=
4.01
Process ID:        60600640          Start time:        11-FEB-1997 10:34:5=
7.91
Owner ID:                            Elapsed time:                0 00:02:0=
6.10
Terminal name:                       Processor time:              0 00:00:0=
3.14
Remote node addr:                    Priority:          4
Remote node name:                    Privilege <31-00>: FFFFFFFF
Remote ID:                           Privilege <63-32>: FFFFFFFF
Remote full name:
Queue entry:                         Final status code: 10002A14
Queue name:
Job name:
Final status text: %SYSTEM-F-EXBYTLM, exceeded byte count quota
Page faults:             1429        Direct IO:                 25
Page fault reads:          40        Buffered IO:              104
Peak working set:        1472        Volumes mounted:            0
Peak page file:          6347        Images executed:            1

$
$ type SYS$SYSDEVICE:[UCX$SNMP]UCX$OS_MIBS.LOG
 WARNING IFDEV.C;1 line 588: Unexpected error in iosb, starting adapter ESA=
0: (QIO).
ucx$os_mibs.exe WARNING IFDEV.C;1 line 588: Unexpected error in iosb, start=
ing adapter ESA0: (QIO).
ucx$os_mibs.exe WARNING IFDEV.C;1 line 588: Unexpected error in iosb, start=
ing adapter ESA0: (QIO).
ucx$os_mibs.exe WARNING IFDEV.C;1 line 588: Unexpected error in iosb, start=
ing adapter ESA0: (QIO).
ucx$os_mibs.exe WARNING IFDEV.C;1 line 773: Unexpected error in status, ass=
igning adapter channel.
$

 ----- Process ucx$esnmp still alive:

$ sh proc/id=6060063F

11-FEB-1997 10:47:03.86   User: SYSTEM           Process ID:   6060063F
                          Node: RISVX3           Process name: "ucx$esnmp"

Terminal:
User Identifier:    [UCX$AUX,UCX$SNMP]
Base priority:      4
Default file spec:  Not available

Devices allocated:  BG652:
                    BG653:
                    BG654:
                    BG655:
                    BG657:
$

    
    So, is this a known problem or what? Could someone tell if I need to
    IPMT this. I should also add that customer sees the problem on both of
    her VAXes - so someone else out there should have seen it as well???
    
    Poul
    

    I've got a customer, Dow Jones, seeing this same problem  and they
    want a resolution.  Is CFS.44438 still open?  Should I go ahead and
    officially elevate Dow Jones' case, too?
    
    Thanks in advance,
    
    Karen
    CSC

Karen,
     The CFS.44438 IPMT was fixed and closed about a week ago.
The new image required to fix this is:-
LASSIE::UCXAXP$DKA0:[UCX$INTERNAL]UCX$OS_MIBS.EXE_UCXV41_VAXVMS.

Note that this fixes the problem where SNMP fails if MOP is enabled. I have
opened another IPMT where SNMP fails with a ROPRAND/ACCVIO when two 
sessions access the UCX SNMP agent simultaneously. 

Geoff..

    Hi there,
    a customer of mine has VAX/VMS V6.1 and UCX V4.1 ECO04.
    He is having problems with SNMP; 
    When SNMP is started the UCX$OS_MIB process is started but it 
    dies immediately after.
    In the UCX$OS_MIBS.LOG file there is the following message:
    WARNING IFDEV.C;1 line 588 Unexpected error in iosb, starting adapter
    EZA0: (QIO)
    Is it there a patch which addresses this problem?
    Thanks
    		Marilena
    
    
    

    Hi there,
    more info about previous problem:
    MOP is enabled on this system.
    Tomorrow I'll be at customer site and I'll see what happens if I disable
    mop (DECnet/OSI).
    Thanks                                         
    		Marilena

    Hi there,
    
    I have just tried to disable MOP ( ncl> disable mop)
    but things still don't work as they should;
    Both the ucx$esnmp and ucx$os_mibs processes are running but the system
    does not respond to snmp queries executed by the Network Management 
    workstation (HP OpenView) or better, sometimes it responds, some other
    times it does not.
    Nothing is logged in the UCX SNMP log files.
    I read that there is a patch which addresses this problem (a new
    UCX$OS_MIBS.EXE image).
    Do you think this is going to fix this kind of problem?
    (Just to recap this is UCX V4.1 ECO04 on VAX/VMS V6.1)
    
    
    Additionally I have another problem on the ALPHA side:
    UCX V4.1 ECO04 on AXP/VMS V6.2-1H3 
    In one typology of systems, with these software products, 
    SNMP works fine.
    
    But, we have another typology (I mean different layered software products
    installed then previous systems) of systems with same version of VMS
    and UCX (same patch level as well) where SNMP does not work.
    This is what I get in the UCX$OS_MIBS.LOG file:
    
    
    %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
    address=00000008, PC
    =000536BC, PS=0000001B
    
      Improperly handled condition, image exit forced.
        Signal arguments:   Number = 00000005
                            Name   = 0000000C
                                     00000000
    				     00000008
                                     000536BC
                                     0000001B
     
    
        Register dump:
        R0  = 0000000000000A58  R1  = FFFFFFFF810A9500  R2  =
    0000000000012788
        R3  = 0000000000173F50  R4  = 00000000000274C0  R5  =
    0000000000000A58
        R6  = 00000000002531B0  R7  = 0000000000252128  R8  =
    000000000000000A
        R9  = 00000000000005A0  R10 = 000000007FFBF800  R11 =
    000000007FF3A1A2
        R12 = 0000000000000000  R13 = FFFFFFFFAFB3D1B0  R14 =
    0000000000000000
        R15 = 00000000009B4EEA  R16 = 0000000000252128  R17 =
    0000FFFE00007204
        R18 = 0000000000000000  R19 = FFFFFFFF85804200  R20 =
    000000007F9F54D0
        R21 = 0000000000000001  R22 = FFFFFFFF00000000  R23 =
    0000000000000000
    	R24 = FFFFFFFF85804AB0  R25 = 0000000000000001  R26 =
    0000000000000FD2
        R27 = 0000000000000000  R28 = 0000000000000000  R29 =
    000000007F9F53D0
        SP  = 000000007F9F53C0  PC  = 00000000000536BC  PS  =
    000000000000001B
    
    
	Can someone there help as soon as possible? (It is a very critical
    customer)
    
        If you need additional info, please let know.
    
        Thanks a lot
    		Marilena
    

    Hi everybody,
    
    can anyone give any help?
    
    Shall I formally escalate the two problems?
    
    Thanks
    		Marilena