Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Alternatives for simple 8600 router config, with twists

Status
Not open for further replies.

Blissex

Technical User
Jun 10, 2007
1
GB
Hi I am looking at a relatively simple setup: a dozen networks,
each with its own switch and /24 IP subnet are linked to one
router which has a link to the campus net. The root router is an
8600 and the leaves are 5530s or 5520s.

The idea is that the 8600 is configured as a pure router, and
the 5530s/5520s as pure switches. So the 8600 has N+1 addresses,
where N addresses are the gateway addresses used by nodes in the
N leaf subnets, and the last one is the address on the link to
the campus net. Therefore I also need N+1 routes, N routes to
the leaf subnets, and 1 default route to the campus net.

To give some numbers, let's assume:

* The link to the campus net has the 192.168.0.0/30 subnet, the
8600 end is 192.168.0.2, the campus net gateway (which is
another 8600) is 192.168.0.1.

* The leaf subnets are 10.0.1.0/24 to 10.0.12.0/24, and the
gateway address each subnet expects is to be the .1 address in
each subnet.

* The 8600 then must have N ports with addresses 10.0.1-12.1,
and one port with the 192.168.0.2 address.

* The internet gateway must two routes back to the 8600, one
to 192.168.0.2/32 via 192.168.0.1 and the other to 10.0.0.0/8
via 192.168.0.2 (or similar).

* One of the leaf networks should be connectable with a MLT
connection between the 8600 and its 5530.

So far so good. My questions are:

* What address to give to the real or virtual management port?
Possibilities: 192.168.0.2, something like 10.0.0.1, something
arbitrary, ...

* User IP based brouter ports or port based VLANs to bind the
10.0.1-12.1 addresses (and related routes) to the ports to
which the leaf switches are connected?

* Assuming that this has to be done, how to relay DHCP queries
from the 10.0.1-12.0/24 subnets to the campus subnet and
responses back to them?

Ideally the choices would satisfy these constraints:

* Minimal use of VLANs, in particular avoid on-wire VLAN tags
(VLANs entirely internal to the 8600 are sort of OK).

* Other then DHCP, no relaying of broadcasts outside the network
they originated from. In other words, traffic among the leaf
networks (very little is expected anyhow) should be purely
routed, and so should traffic between the campus net and the
leaf networks, with the exception of DHCP.

* The config should be done with CLI commands. In particular the
config should be saveable to a text file and checked into a
version control system...

Any suggestions and example warmly welcomed, as while I am very
familiar with networking configuration in the UNIX/Linux/...,
rather less so with the Nortel CLI.
 
The management port on the CPU module doesn't participate
in routing so its best used in an out-of-band fashion.

I think port based VLANs are preferable to brouter
ports in most circumstances.

Assuming port-based VLANs your basic config for DHCP forwarding would be:

config
stg 2 create
stg 2 add ports 9/1
stg 2 priority 100
vlan 2 create byport 2
vlan 2 ports add 9/1
vlan 2 ip create 10.1.1.1/255.255.255.0
vlan 2 ip dhcp-relay enable
vlan 2 ip dhcp-relay mode dhcp
ip dhcp-relay create-fwd-path agent 10.1.1.1 server 192.168.1.100 mode dhcp state enable

Remember to do a 'save config' afterwards.

The config file (minus passwords) is stored as /flash/config.cfg by default,
and can be copied off via FTP periodically - that's want many people do to
exbackup configurations.

You might want to use RIP or better yet OSPF to make
sure your internal routing tables are updated correctly.

Nortel has a document called the 'Converged Campus Solutions Guide"
that you can Google for - its got lots of design guidelines.
If you're new to the 8600 platform make sure your on a 3.7, 4.0,
or 4.1 code release 3.5 and older are no longer supported.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top