I would say that is an anomaly. Real equipement vs dynamips?
Regards, Tyson Scott - CCIE #13513 R&S, Security, and SP Managing Partner / Sr. Instructor - IPexpert, Inc. Mailto: <mailto:[email protected]> [email protected] Telephone: +1.810.326.1444, ext. 208 Live Assistance, Please visit: <http://www.ipexpert.com/chat> www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, Audio Tools, Online Hardware Rental and Classroom Training for the Cisco CCIE (R&S, Voice, Security & Service Provider) certification(s) with training locations throughout the United States, Europe, South Asia and Australia. Be sure to visit our online communities at <http://www.ipexpert.com/communities> www.ipexpert.com/communities and our public website at <http://www.ipexpert.com/> www.ipexpert.com From: [email protected] [mailto:[email protected]] On Behalf Of Bojan Zivancevic Sent: Tuesday, September 21, 2010 11:34 AM To: 'CCIE_RS OnlineStudyList' Subject: [OSL | CCIE_RS] OSPF - network command did not enable ospf, but ip ospf did Just had a mental wrecking event. :) I am wondering if there is any logic behind this, or just "one of those things." Vol.1 Lab 10. OSPF. Task 10.14, entering the second process ID on R8. It has the first process ID already running on F0/1 interface, enabled with the network command. And, because it was a stub network at the beggining, I did passive F0/1. Now, it is time to add the second process, and it will run on that F0/1 interface. So, I put the network command - and nothing happened. OSPF showed that no process is running on that interface. So, debugging, looking, searching, you how it goes - I managed to do nothing. And it popped into my mind to try interface level command, to see what will happen. And the moment I entered the ip ospf 2 area 0 command, OSPF got started and formed a neighbor, like it should before. But then I removed that interface level command - and it continued to work, but with different router ID value... That is to say, it proves that the "ip ospf" process got killed, and then the new one from "network" command took over. So, the network command now works. So, now everything is ok. But it is interesting how this happened. Like this passive F0/1 from the first process killed any chance of running other OSPF processes... Temporarely. :) Best Regards, Bojan Zivancevic Network Engineer ---- Comutel d.o.o. Omladinskih brigada 65v 11070 Belgrade SERBIA Tel: +381 11 217 8000 Ext.109 Mob: +381 64 646 8401 Fax: +381 11 6164641 http://www.comutel.co.rs <http://www.comutel.co.rs/>
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
