[Xorp-users] [OSPF]: xorpsh error

karnik.jain at einfochips.com karnik.jain at einfochips.com
Mon Sep 1 02:37:14 PDT 2008


when i tried to configure router id of router using xorpsh at that time
sometimes i get error like this :

Failed to register with router manager process
201 Resolve failed

i applied command :
set protocols ospf4 router-id 10.10.10.12

i did not understand any thing why it happens like this because many times this
commands works and sometimes it fails.



my configuration file is displayed
below.......................................................................

/* $XORP: xorp/rtrmgr/config.boot.sample,v 1.46 2007/03/12 10:16:05 atanu Exp $ */


interfaces {
    restore-original-config-on-shutdown: false
    interface eth0 {
	description: "data interface"
	disable: false
	/*default-system-config*/
	vif eth0 {
	    disable: false
	    address 192.168.14.16 {
		prefix-length: 24
		broadcast: 192.168.14.255
		disable: false
	    }
	}
    }
}

fea {
    unicast-forwarding4 {
	disable: false
	forwarding-entries {
	    retain-on-startup: false
	    retain-on-shutdown:	false
	}
    }
}

protocols {
   ospf4 {
	router-id: 10.10.10.16
	/* export: "static" */


	traceoptions {
	    flag {
		all {
		    disable: false
		}
	    }
	}


	area 0.0.0.0 {
	    interface eth0 {
		/* link-type: "broadcast" */
		vif eth0 {
		    address 192.168.14.16 {
			 priority: 3
			 hello-interval: 10
			 /*router-dead-interval: 40*/
			 /*interface-cost: 1*/
			 /*retransmit-interval: 5*/
			 /*transit-delay: 1 */

/*
			authentication {
			    simple-password: "password";

			    md5 @: u32 {
				password: "password";
				start-time: "2006-01-01.12:00"
				end-time: "2007-01-01.12:00"
				max-time-drift: 3600
			    }
			}
*/

			/* passive: false */

			/* disable: false */

		    }
		}
	    }
	}
    }
}

plumbing {
    mfea4 {
	disable: false
	interface eth0 {
	    vif eth0 {
		disable: false
	    }
	}
	interface register_vif {
	    vif register_vif {
		/* Note: this vif should be always enabled */
		disable: false
	    }
	}
	traceoptions {
	    flag all {
		disable: false
	    }
	}
    }
}

/*
 * Note: fib2mrib is needed for multicast only if the unicast protocols
 * don't populate the MRIB with multicast-specific routes.
 */
protocols {
    fib2mrib {
	disable: false
    }
}



With regards,
K at rN|K,
Embedded Dept.



-- 
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
__________________________________________________________________________
 



More information about the Xorp-users mailing list