Hotel Network Topology The following network topology has worked well for previous meetings:
a) Provide at least 20M of available bandwidth between the hotel and the commodity Internet. In addition to the interface to the hotel network, a private Ethernet segment is needed between the host router and Merit's IPv6 router: All IPv4 and IPv6 addresses are in AS236.
b) Provide a native (MSDP, MBGP, PIM-Sparse) multicast link from the meeting site to the Internet -- Merit can help with this. Tunneling makes it difficult to implement and troubleshoot the multicast broadcast and is not an acceptable substitute for native connectivity.
c) Please don't attempt to set up a VPN for the unicast portion of the external networkit adds unnecessary complexity to the network.
a) Wire the hubs and switches provided by Merit, and connect them to the hotel network.
b) Provide and install Ethernet cabling and power strips for laptop users.
c) Provide an adequate supply of electrical power to the room:
As food for thought, here's a diagram of a power layout that has worked well in the past.
d) Give Merit a network map (can be very informal!)
e) One area of the main room is set aside for laptop users who want to use Ethernet rather than the wireless network. 30 Ethernet cables should be made before the meeting to connect hubs and tables in this area. 15', 10', and 5' cables are needed.
f) 50 or so variable-length cables are needed as well. These can be made at the meeting to meet on-site needs.
Schedule:
Web Cache
Merit will configure the DHCP server so it returns a domain name to clients. In ISC's server, the command line is:
option domain-name "nanog.hostdomain.net";
b) Transparent caching should not be used for the meeting - attendees will complain :)