| 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 |
Can anybody help ??
The following problem has also been seen with a domain. I have
already been through flushing the cache and reboot with the
customer which obviously hasn't fixed it.
dns> show object .snmp.cagt29
SHOW
OBJECT BT_MCC:.snmp.cat29
AT 16-AUG-1993:11:03:39
Error on entity: BT_MCC:.snmp.cat29
Requested name does not exist
Function:dnsEnumAttr
dnsEnumAttr:partial results - BT_MCC:.snmp
dns> exit
# manage
DECmcc(V1.3.0)
mcc> dir snmp .snmp.cagt29
SNMP BT_MCC:.snmp.cat29
AT 1993-08-16-11:04:30.414
Directory successful, entity has only been partially registered
Registered Name - BT_MCC:.SNMP.CAGT29
mcc>
mcc> show snmp .snmp.cagt29
Using default ALL IDENTIFIERS
SNMP .snmp.cagt29
AT 1993-08-16-11:05:00.984 Identifiers
Examination of attributes shows:
Registered name = BT_MCC:.snmp.cat29
Address = -- Attribute Not Gettable
Name = -- Attribute Not Gettable
Name = -- Attribute Not Gettable
mcc> show snmp .snmp.cagt29 all char
SNMP .snmp.cagt29
AT 1993-08-16-11:05:21.441 Characteristics
No internet name or internet address registered
mcc>
mcc> erase snmp .snmp.cagt29
SNMP .snmp.cagt29
AT 1993-08-16-11:05:58.676
The entity SNMP .snmp.cagt29 is not registered
Not registered Entity = SNMP .snmp.cagt29
mcc> dereg snmp .snmp.cagt29
SNMP .snmp.cagt29
AT 1993-08-16-11:06:22.473
The entity SNMP .snmp.cagt29 is not registered
Not registered Entity = SNMP .snmp.cagt29
mcc> register snmp .SNMP.CAGT29 ADDRESS=147.149.104.63 ! BINGLEY CC
SNMP BT_MCC:.SNMP.CAGT29
AT 1993-08-16-11:07:16.359
No such entity: SNMP BT_MCC:.SNMP.CAGT29
Unkown Entity = SNMP BT_MCC:.SNMP.CAGT29
Any clues what could be causing this ???
Gary Lowe NUK CSC comms..
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5489.1 | System Time Not Right??? | SPANKY::SAWYER | Tue Aug 17 1993 10:35 | 8 | |
Gary,
I would check the system time to make sure that it is accurate.
A lot of DNS problems occur when the TIME on your system is not
accurate.
Rob
| |||||
| 5489.2 | I'm not ignoring you just waiting for customer !! | PLUNDR::LOWEG | WANTED!! A modern day Robin Hood. | Thu Aug 19 1993 06:21 | 7 |
I have left a message on the customers answerphone for him to check
his system time and I will let you know the answer when he gets back to
me.
Gary Lowe NUK CSC comms..
| |||||
| 5489.3 | Thanks but the time is ok.. | PLUNDR::LOWEG | WANTED!! A modern day Robin Hood. | Mon Aug 23 1993 06:02 | 10 |
Unfortunately the time is correct, plus the MCC system is also the DNS
Server. So there can't be any time differences as the system is the
same.
Any other thoughts ?????
Gary Lowe NUK CSC comms..
| |||||
| 5489.4 | Found the answer by chance. | PLUNDR::LOWEG | WANTED!! A modern day Robin Hood. | Mon Oct 25 1993 14:34 | 22 |
I have just fixed this problem whilst on the customer site. I checked a
correctly registered snmp entity in dnscp and noticed it was registered
as an object. So out of sheer guess work I decided to try and create an
object using the correct snmp entity as a template :-
dnscp> create object .snmp.cagt36 DNS$Class MCC_ DNS$ClassVersion 1.0
This worked to my suprise, I then went into the mcc FCL and
mcc> dereg snmp .snmp.cagt36
To more suprise this worked as well. To cap it all off I was now able
to register the entity correctly and everything is working now.
So, I can only assume that it was originally registered in FCL
incorrectly and didn't tie up with DNS and this was causing the
problem.
Gary Lowe UK MCS Nets&Comms.
| |||||