| 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 |
I'm trying to find out how the TCP/IP autoconfig works. When generating the IP autoconfig script, the MAKECONFIG procedure searches in UCX output file for 0.0.0.0 and uses this entry to find which router to query. My UCX is setup to match destination 0.0.0.0 to gateway OSLROW which has IP- address 16.181.192.7. My own node has IP-address 16.181.192.130. OSLROW is setup as a router, but is not running dynamic routing. When running the IP script, I get the message saying Running IP Autoconfiguration... This may take a while... Querying 16.181.192.7(oslrow) Timed out host 16.181.192.7 (oslrow) queues=[0,0,1,0] = 1 Fixing up stray links . . . 1 Nodes, ! Networks, 1 Edges . . . The timeout happens when I'm also manually entering routers to the IP script. When I'm entering non-routing IP hosts, they respond immediately. UCX LOOP OSLROW gives %UCX-I-LOOPACT, OSLROW is active Can anyone give any comment on this? What's the expected behavior and why is the routers not answering the Query from IP autoconfig? Bj�rn Olav Haugom
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2581.1 | IP/ICMP responds, but SNMP does not | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Tue Mar 17 1992 21:59 | 19 |
Two possibilities: 1) There is no SNMP agent on the routers 2) There is a differnt community name in use on the routers to protect them. Can you try using the SNMP AM to query the router, and see what happens? e.g. MCC> show snmp oslrow all char Unfortunately, if that fails you will have to go and ask whoever runs the router which of the two above possibilites is causing your problem. There is no way to distinguish between the two cases (that is a security feature of the SNMP protocol) -- Erik | |||||
| 2581.2 | Bug in IP Autoconfig when > 16 interfaces? | OSLACT::BJORN | Soon to be changing dipers | Wed Mar 18 1992 03:51 | 17 |
I found out what the problem was. OSLROW was set to DISALLOW any other hosts than itself to do monitoring, i.e. the community name was correct, SNMP was running, BUT the community name public didn't allow any other IP-adresses than it's own address. The other router is a PROTEON box, and we haven't figured out what is causing the problem, yet. Another problem is occuring during the autoconfig. When a concentrator which has more than 16 interfaces, the autoconfig fails to configure the rest of the interfaces. It doesn't show up on the map either, even if it has detected it. This is reported as a bug with MSU, where the IP autoconfig seems to have come from. Bj�rn Olav Haugom | |||||