| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
More Accvios with SNMP/TCPIP AM and the iconic MAP. Customer is using
MCC V1.1 amd has install TCPIP 1.1 including the patch MCCTCPIP_A011.
SNMP entities can be registered and managed via the FCL fine. If a new
registration is attempted VIA the Iconic MAP it ACCVIOs. If an already
registered entity(via FCL) is placed on the map it shows up, but if
selected any show againest it returns 'no such entity', if he goes into
children of the entity all are displayed, but as soon as he selects any
of the children again it accvios.
The only add/non standard part of this set up is he is using TVG multinet
as his IP transport.
Any Ideas/suggestions Welcome.
Steve Woestemeyer
CSC/CS - Network Ssupport Team
---------------------------------------------------------------------------
MCC> sho mcc 0 tcpip_am all char
MCC 0 TCPIP_AM
AT 17-JUL-1992 15:18:26 Characteristics
Examination of attributes shows:
Component Version = V1.1.1
Component Identification = "DECmcc TCP/IP SNMP AM"
UDP Timeout = 5
UDP Retries = 2
MCC> sho snmp hub-cny-9000m7 all attr
SNMP hub-cny-9000m7
AT 17-JUL-1992 15:18:58 All Attributes
Address = 132.183.100.241
Name = hub-cny-9000m7
sysUpTime = 1140318025
ifNumber = 1
sysContact = -- Attribute Not Gettable
sysDescr = "MRXI Version 1.01.00
"
sysLocation = -- Attribute Not Gettable
sysName = -- Attribute Not Gettable
sysObjectID = "1.3.6.1.4.1.52"
sysServices = -- Attribute Not Gettable
Implementation Desc = ""
Location = ""
MAIL Account = ""
Phone Number = ""
Remarks = ""
Responsible Person = ""
Text File = ""
MCC> sho domain fred member *
Using default ALL IDENTIFIERS
Domain NOCDB_NS:.fred Member NOCDB_NS:.HUB-CNY-9000M7
AT 17-JUL-1992 15:19:34 Identifiers
Examination of attributes shows
MemberName = NOCDB_NS:.HUB-CNY-9000M7
MCC> exi
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3382.1 | Probably a Stack problem.... | CHRISB::BRIENEN | DECmcc LAN and SNMP Stuff... | Mon Jul 20 1992 13:58 | 26 |
RE: 3382.0 >SNMP entities can be registered and managed via the FCL fine. If a new >registration is attempted VIA the Iconic MAP it ACCVIOs... > > >The only add/non standard part of this set up is he is using TVG multinet >as his IP transport. This looks like the stack problem (i.e. stack too small) discovered some time ago with DECmcc V1.1 IMPM and SNMP AM /TGV Multinet. The symptoms were: 1. Works fine with FCL PM (which allowed the stack to grow practically forever) 2. Fails w ACCVIO when running with IMPM (which had a fixed stack size to allow multiple threads) I thought that there was a fix for this problem (patch or logical?), but don't remember the details off hand. More information shortly... Chris | |||||
| 3382.2 | sounds like a stack problem to me too | BMAJOR::PERRY | Mon Jul 20 1992 17:15 | 18 | |
The V1.1 TCPIP AM would ACCVIO occasionally when trying to load vendor private mibs from the mcc dictionary. The problem was that the AM would run out of stack space. We issued a patch (MCCTCPIP_A011.A) which basically reduced our stack space consumtion. This patch seemed to solve the problem. While testing the V1.2 TCPIP AM with TGV Multinet, we ran into stack problems again. We needed more stack space when using the Multinet software. Fortunately, in mcc V1.2 we could increase a management modules's stack space by simply defining a logical (or environment variable). For instance, we found that the TCPIP AM stack size needed to be set to 100 (define MCC_TCPIP_AM_STACK 100) to work with Multinet, otherwise, we would get an ACCVIO. Unfortunately, there is NO WAY that I know of to increase the stack size of the V1.1 TCPIP AM. We know the AM works with Multinet in V1.2 as long as the stack size is increased. Can the customer upgrade to mcc V1.2? Jim | |||||