From: Moffat, Ed (EMoffat@fsci.com)
Date: Sun Mar 28 2004 - 01:17:51 GMT-3
In a real lab I would verify with the proctor, but, no static typically
means no "ip route x.x.x.x..." command.
Practice labs I've worked with usually specifically state "no static routes"
or "no 0/0 routes" or "no ip default-network" or "no default-information" or
some combination of the above.
That usually points out what is permitted. If none are permitted then you
need to look at other methods like summarization or tunnels to work around
FLSM/VLSM issues.
Your statement about ip default-network command showing up as statics in the
route table means that you are not specifying a classful default network. If
you add a classless address as the default-network then it will actually
create a classful static route in your config. That will usually violate any
lab.
For instance, if I configure the following:
ip default-network 172.16.85.0
The following shows up in my config and my routing table:
R8#show run | include ip route
ip route 172.16.0.0 255.255.0.0 172.16.85.0
R8#show ip route static
S 172.16.0.0/16 [1/0] via 172.16.85.0
And no "ip default-network" statement will be in my config
R8#Show run | include ip default
R8#
Hope that is answers your question.
-Ed-
-----Original Message-----
From: trouse@cisco.com [mailto:trouse@cisco.com]
Sent: Saturday, March 27, 2004 7:04 PM
To: ccielab@groupstudy.com
Subject: no static routes vs default network
if a requirement says that you cannnot use static routes does that prohibit
"ip default network". Depending on how used you WONT get a 0/0 router but
is does show up as static in the route table.
so does "no static routes" mean not using the "ip route 0/0" command or does
that mean no router of type "S" in your routing table.
Thanks for clarification.
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:49 GMT-3