MPLS for small network

In the past we have always had point to point links between our 3 remote offices and our corporate office. We're now switching to a MPLS network for all four sites.
We currently use Cisco 1721 routers for our WAN. What protocol should we use for routing across this new MPLS network? I'm also looking for a document what else I may need to configure for this MPLS design on the router itself.
We will have 1721 routers at all sites.

Hi,
for you as a customer the most appropriate picture is: The MPLS VPN behaves like one single IP router interconnecting your sites.
In your case just consider your 4 1721 being connected to one ISP router. There is no MPLS specific config needed on your 1721, MPLS is only within your ISP network.
This means: you send IP routing updates from one site to the "MPLS IP router simulator" and the updates will be sent further on to the other 3 1721. You forward an IP packet to the "MPLS IP router simulator" and it forwards it as IP packet to one of your other 3 1721.
If you are not dual homed or using backups then RIP would address all your needs. Also static routing might be suitable and the most simple aproach in your scenario.
Hope this helps! Please rate all posts.
Regards, Martin

Similar Messages

Need a product recommendation for small network

Hello All!
I just started a small computer and network consulting company (in addition to my "day job"). I work for a huge company with several hundred sites, all Cisco networking of course. I am also setting up a small network and computer consulting company to do on the side and will be dealing with small companies and helping them with their network needs. Anyway, I am looking for a entry level Cisco product because my Linksys just isn't going to cut it any more. I want to set up 3 servers and I currently have 5 static IP's from Comcast. I want something that would operate like a PIX515 firewall but that would obviously be overkill for what I am doing. I want the capability to set up port forwarding to the inside from my 5 external IP's. Wi-Fi isn't critical but would be a "nice to have" if it didn't cost too much more. What would be a good product for my needs? I want a NICE CISCO product but not an EXPENSIVE one, either. I am also interested in certification and possibly becoming a VAR soon. Any pointers would be much appreciated.
Thanks,
--GREG--

I would steer clear of the 500 express. Since you seem to be new to cisco products, I would use the opportunity and buy what most of your potential customers already have. Get yourself a pix/asa and a 2900 series switch as first poster suggested. If you are interested in certifications, you will need to learn the command line interface. The 500 express will do you no good as it is all gui. This is only my opinion of course. Oh, and did I see not expensive and cisco in the same sentence. :)

Setting up a Server for Small Network

I have a workgroup of 3 people all on macs running OS X. I have a PowerMac Quad and I want to set it up as a server so that my entire workgroup can access files from it in order to run InDesign and InCopy. How do I do this?
Thanks in advance!

OK, so I guess that I had already figured out that this is your first network. Let's have some fun...
But in your your first post, you stated:
I have a PowerMac Quad and I want to set it up as a server so that my entire workgroup can access files from it in...
And no, 'server' won't be a separate user on the Quad. The Quad is the server, right?
Quad=Computer=server.
You are configuring the Quad with several new accounts.
You
Joe
MaryLou
Find this in SystemPreferences>Accounts. Unlock. Click the little Plus sign to add users.
I would suggest setting the Quad with a static IP address inside your little LAN (local area network). You can find the steps by searching this group for 'static ip', or looking into systempreferences>Network>Built-In...
You should really read up on some of these network basics (like finding IP address...)
Don't apologize for your ignorance. Ignorance can be cured, but you'll need more than a hand-holding here in the Discussions.
I will help, but show us that you're willing to help, too.
Stop back when you've learned how to:
a) find your IP address,
b)set the Quad with a static IP,
c)search the Discussions

Need configuration exmamples for 3560 small network

Hello,
I'm currently doing some lab exercises in Packet Tracer.
I'm trying to setup a small network with 2x 3560 switches and 3 vlans. 1 vlan for network management, one vlan for servers and one vlan for users.
I'm running into issues where my lab exercises don't seem to work properly, and i'm not sure what im doing wrong. I learn fairly well "by example" and was wondering if anyone can point me to some examples of such a setup.

further, here is the layout of my lab and the packet tracer file.
here are the configs of my 2 3560. i've cut out ports no important to the lab
CORE 3560
Current configuration : 1399 bytes
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
hostname CORE
ip routing
no ip domain-lookup
interface FastEthernet0/10
switchport access vlan 10
switchport mode access
interface GigabitEthernet0/1
description link_to_closet_switch
switchport trunk allowed vlan 1,10,20
switchport mode trunk
interface Vlan1
ip address 192.168.1.1 255.255.255.0
interface Vlan10
description server_vlan
ip address 192.168.10.1 255.255.255.0
interface Vlan20
description user_vlan
ip address 192.168.20.1 255.255.255.0
ip classless
============
CLOSET 3560
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
hostname CLOSET
ip routing
no ip domain-lookup
interface FastEthernet0/10
switchport access vlan 20
switchport mode access
interface FastEthernet0/11
switchport access vlan 20
switchport mode access
interface GigabitEthernet0/1
description link_to_core_switch
switchport trunk allowed vlan 1,10,20
switchport mode trunk
interface GigabitEthernet0/2
interface Vlan1
ip address 192.168.1.2 255.255.255.0
interface Vlan10
description server_vlan
no ip address
interface Vlan20
description user_vlan
no ip address
ip classless
line con 0
line vty 0 4
login

Looking for Mac network professional to setup our small business network.

I've installed OS X Server on an iMac within our office to act as a file server and also allow us to access files using a VPN. Probably should have purchased a Mac Mini Server and will likely go that route in the end.
I'm computer savy, but little networks experience and just can't get this working correctly. If we had more time to dedicate to this and with help from this forum, I'm sure we could get it up and running. The goal is to get a simple network going that will allow us to access files, etc in the field and at our home offices with the ability to grow as our business expands.
At this time I'd really like to have someone just handle the setup of the network so we can get functionality asap. I've done some searches and looked for a network professional in our area with experience in Mac networking within a business environment, but haven't had much luck.
If anyone point me in a direction of someone that can help get this going I'd be forever greatful:)
Location: Southern California (Rancho Cucamonga)

I'm not a rocket scientist but I do have a working mail server and website using a mini mac and os x server (Mavericks).
It all begins with your DNS and I recommend you do use a mac mini with OS X Server as it's designed for that very purpose. You absolutely must get your DNS situation working first. There's a guy in this forum named Mr. Hoffman who is particularly useful (there are others) in this area. He has a website with lots of helpful advice and, in particular, this: http://labs.hoffmanlabs.com/node/1436.
However, before you embark on that journey, this is what you'll basically need to do:
You're going to need a public (external/public facing) DNS and a private (internal) DNS. Your private DNS (served by your os x server) needs to live behind some kind of hardware firewall/router to prevent the great unwashed and curious from venturing into places they probably shouldn't be venturing. It's port(s) should never be exposed to the outside world.
Get a static IP from your ISP and register a domain name.
Let your domain registrar provide the external DNS.
You'll want to set up an internal DNS using OS X Server in the 10.0.0.0/16 subnet (it doesn't seem to let you use 10.0.0.0/8 and it really hates 192.168.0.0/24).
The server itself will need to be "self-aware" by setting it's System Preferences > Network Preferences > DNS Server to 127.0.0.1.
Of course, once you get the DNS working you'll want to turn on File Sharing and then (and only then) Open Directory. THen you can begin adding other services such as web, mail, vpn, etc...
I'm sure there is lots more that I've missed but this should do for now. Good luck.

Advice for Building Small Network Question

Hello,
I am building a small network environment which will connect to a larger office, scalability is important. We will begin having about 30 users which will all need VOIP services. The VOIP services will be hosted by a cloud provider. My question is as of now I am looking to obtain a Cisco 2921 ISR Router and then a Cisco 2960-X 48Gig POE, and my main question is I am confident the switch can handle the power and operation of the phones but just to make sure I should not run into any problems with the router as far as forwarding the data, correct? Any other comments or suggestions would be appreciated.
Thanks,
Joe

Duplicate post.
Go HERE.

How does a single cisco router network enable outgoing calls for small businesses if no dial plan is used

Hi Cisco techs,
I was recently asked this question at work from the rest of my team as they know I am doing studies for cisco ICND 1 & 2.
And couldn't answer them.
Or does this require more information like hardware used etc?
Had searched Google to ambiguous results.
Can someone give me a link to advise please
Thanks in advance again..

Dear,
For small business (up to max 450 users) we use Call Manager Express (CME) which is configured on Cisco Voice router.
If no dial plan is used or configured then none of callmanager can do external outgoing/internal calls. Dial plan is basic thing which must be configured on cisco voice router (e.g. CME).
If you have configured Phones (ephone & ephone dn) and if they are registered on callmanager express then for internal calls you dont need to configure dial plan because callmnager have all the information of its phones.
If you want to have external incoming/outgoing calls for CME then you will have to create dial peers/dial plan.
For a CME lab setup, you can visit below link.
http://cisco.jjc.edu/cnt208/PDF/CCNP4_lab_2_1_en.pdf
Suresh

NEED HELP TO SET UP SMALL NETWORK - WIRELESS SIGNAL FROM NOVATEL U760 USB

Hello -
I need help setting up a small network in my new home in Florida, which has no wired broadband capability - not cable, not dsl. My options are satellite (which I'd like to avoid) or wireless broadband via Millenicom (or now Virgin Mobile) using their Novatel U760 USB stick.
Here are the network components - someone please tell me how to set this up:
PC #1 (has wireless card, but I've connected it by ethernet to the router)
PC #2 (no wireless card; connected via ethernet to router)
MACBOOK, 1 1/2 years old (2.1 GHz Intel Core 2 Duo, 4 gigs RAM), running OS 10.58, connected wirelessly to router.
AIRPORT EXTREME BASE STATION, Model A1143.
I'm not thrilled about using a wireless 3G signal as my primary one, (sprint network, claims 600 - 1400 kbps speed), but it costs 1/2 to 1/3 of what a slightly faster satellite signal would.
I have not ordered this service yet. Before I do, I'd like a clear understanding that I can, in fact, set up my simple network, which I'd probably do the same as it's now configured with cable broadband - both PC's plug via
ethernet into the Airport Extreme router, the MacBook connects wirelessly - AND,
my question is this:
Can I plug the wireless card - a Novatel U760 USB-stick device - straight into that USB slot in the Airport Extreme base station and will it automatically recognize that device?
Or, do I have to plug it into the MacBook and somehow share that wireless signal between the 2 PC's (only 1 of which has a wireless card, so I'd have to get a card for PC #2)?
And help anyone can provide will be much appreciated!
Thanks,
Em

from the Airport FAQ #14:
"Question: Can I connect my Soundsticks or other USB speakers to AirPort Express?
Answer: No. The USB port is for connecting a printer, not for other devices."
Im assuming other devices include USB modems.
So, I would say your cheaper route would be to get a second wireless card and just share your internet connection from one of your PC.

Need advice for starting a Managed Cloud Service for Small Businesses

I hope this is in the right forum. I have done a lot of research and searching but havent found anything that specifically answers, in total, what I am wanting to accomplish. I live in a small town and want to start a Managed Cloud Services for
small to small-medium business in my area (2-30 users for each business). I want to market this to have businesses replace their in-house server(s) to virtual ones I would host in a local Data Center with my own equipment that I would maintain. I
am just starting off so I don't have any clients I do this for currently, but I get asked about this frequently. I want to run a 2012 R2 Domain Controller and a Hyper-V 2012 R2 server. The virtual servers I will host are going to be for AD, RDS,
FTP, and files. Software examples that people are going to be using these virtual servers for are Quickbooks, Sage Accounting, Remote Desktop or RemoteApp, custom CRM or small database software, Office 2013, etc. No Exchange currently but will
probably configure something for that in the future (maybe run 1-3 virtually for now if someone asks, but will only do it if the user base is fairly small ~under 10 users). I only have 1 static IP to work with over a 100Mbps connection up and down.
For hardware, I am figuring something along the lines of this:
(1) 1U, single CPU w/2-4 cores, 8GB, 2x73GB SAS 10k RAID 1, Dual PSU, running Windows Server 2012 R2
Domain Controller
(1) 2U, 2x 8-core Xeon ~2.6Ghz, 80GB RAM, 8x600GB SAS 15k in Raid 10 for Storage (VHDX files, etc), RAID 1 small Basic drives (or USB stick) for OS, Dual PSU, Quad GB Nic which I can use for load balancing/teaming, Hyper-V
2012 R2
Hyper-V Virtual Server
(1) GB Unmanaged Network Switch & (1) Cisco 5510 Firewall
Most of my questions are about the best way to configure this. I am planning on managing my Hyper-V from the physical Domain Controller server. Each virtual server will have RDS & (possibly) AD services on a single server.
1) I want to replicate the physical Domain Controller. Should I get another server or just virtualize the replica in Hyper-V? I understand that if the Hyper-V goes down, so does my DC replica.
2) Should I use my Domain Controller to manage ALL users on each virtual Server, by creating separate Organizational Units for each business?
3) Should I setup my domain controller with Hyper-V management and then each Virtual Server I setup be a separate domain (Ex. mydomain.local, business1.local, business2.local, etc)? Each one has no connection to any
other, completely seperate. Or should I do subdomains (business1.mydomain.local).
4) What I have read is that Subdomains are a pain to manage with user rights, etc. I want to keep each server complete separated from one another over a network connection, I suppose the VLan through Hyper-V options
do this? I dont want wondering users to stumble upon another businesses files (I know they would probably be prompted with a login for that business/domain).
5) For each virtual server, I want to create and have an HTTP subdomain point to that server from my domain name. (Ex: business1.mydomain.com, business2.mydomain.com, etc.) I want them to be able to have access to
only their RemoteApps or be able to type that address in their Remote Desktop program as the host name. This would be for viewing the RemoteApp login page and RemoteApps for that business over HTTP/S through a browser.
6) If I do not have separate DC's in each virtual and my main DC manages each one, is their a way to connect up each companies RemoteApps using a single site that only shows what they are assigned to based upon their login?
(Ex. http://login.mydomain.com which then shows that user what they are assigned on their own virtual server)
7) Since each business will use the same ports for RemoteApp (443) & RDC (3389 unless I change it), how would I setup the subdomains to point to their correct server and not overlap for mess with any of the other servers
since its all over 1 static WAN IP for all servers. Thats why I figured setting up IIS subdomains would solve this.
8) For backups or Hyper-V replication, is it better to have software that backs up the ENTIRE Hyper-V server (Acronis Advanced Backup for Hyper-V) as well as replication or just backups? Or should I do separate file
backup on each virtual with a replica? Can a replica be a slower server since its just a backup? (Ex. 1x 8 core, 80GB, 8x600GB 10k SAS)
9) For the servers that will be using FTP, can I again rely on the subdomains to determine which server to connect to on port 21 without changing each FTP servers ports? I just want each business/person to type in
the subdomain for their business and it connect up to their assigned FTP directory over port 21.
10) If the physical DC manages DNS for all Virtual servers, can I forward sub domain requests to the proper virtual server so they connect to the correct RemoteApp screen etc. Again all I have is 1 IP.
I hope all of these questions make sense. I just want every business to be independent of each other on the Hyper-V, each on their own virtual server, all without changing default ports on each server, each server running RDS, (possibly) AD, (a few) FTP,
and all over a common single WAN IP. Hoping subdomains (possibly managed through IIS on the physical DC) will redirect users to their appropriate virtual server.

If you really want to run your own multi-tenant service provider cloud, Microsoft has defined the whole setup needed.
They call it Infrastructure as a Service Product Line Architecture. You can find the full documentation here -
http://blogs.technet.com/b/yuridiogenes/archive/2014/04/17/infrastructure-as-a-service-product-line-architecture.aspx
There are several different ways of configuring and installing it. Here is a document I authored that provides step-by-step instructions for deploying into a Cisco UCS and EMC VSPEX environment -
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/ucs_mspc_fasttrack40_phase1.pdf
This document contains the basic infrastructure required to manage a private cloud. I will soon be publishing a document to add the Windows Azure Pack components onto the above configuration. That is what would more easily provide a multi-tenant
experience with a Azure look and feel. It is not Azure, but the Azure pack is a series of applications, some of which came from Azure, the provides Azure-like capabilities only in a service provider type of environment.
Whether you use my document or not (which has actually corrected errors found in the Microsoft documentation), you should take a look at it to see what it takes to put something like this up, if you are really serious about it. It is not a small undertaking.
It requires a lot of moving pieces to be coordinated. Yes, my document is designed to scale to a large environment, but you need the components that are there. No need re-inventing the wheel. Microsoft's documentation is based on a lot of
real hands on experience of their consulting organization that has been doing this for customers for years. This one is also know as Fast Track 4. I've done 2 (2008 R2) and 3 (2012), also and it just keeps getting more complicated based on customer
demands and expectations.
Good luck!
. : | : . : | : . tim

Small Network Setup Ideas

Looking for some recommendations for those that are more familiar with Linksys products and configuration interface. I would like to setup a small network (3 PC's) and also provide general use wifi utilizing the my businesses DSL connection. Concern - Does Linksys setup allow for me to segment my small network (i.e. 3 pc's) from the general use wifi network. For simplicity purposes I thought I would assign static IP address to my network segment (10.1.x.x range) and want to utilize DHCP for wireless network (different network segment). Also sense this is a shared service, I would like to prioritize my business traffic over the general access. Is this easily accomplished? Regarding the wireless, I only want to provide it to my clients. I suspect I can not broadcast the SSID, but how best to handle this via the Linksys setup? I have been looking at the Linksys Ultra RangePlus Wireless-N Broadband Router Model #: LKS WRT160N. My building has very think concrete walls and I would also like to provide access to an outside patio so I expect that I will likely have to deploy multiple wireless devices to maintain a strong signal. So for those Linksys experts, your advise greatly welcomed. Thanks in advance. TS

you can use WAP4400N for getting good signals from wireless router .... Also you can go for WPC600N (Dual Band Adapter) for good connectivity ....

How choose which partition of my external drive I use for my network

Hi,
I just bought a Linksys E3200 router for my network house. The setup was easy and everything work fine... well.. almost everything. I have a Iomega 1To external drive whit 2 partition ; the first one is a mac os extend for my Time Machine backup and the second one is NTSF for sharing my picture and music. I use the cisco connect software for setup my storage whit my external drive but I can't see the NTSF part. I can write/read in my mac partition but I don't want to use that part on my network.
My question is : Can I have 2 partition on my network? If not, how can I choose the partition I wanna use.
Thanks.
PS: I'm sur you notice it but english isnt my first language, sorry if isn't clear.

ksu62 wrote:
The infection names are: classload.jar-719ef6a5.zip
                                          classload.jar-5db452le31.zip
                                          ar3.jar-6ce3b2f-45l483f.zip
                                          classload.jar-lef99412-63bsd3fl.zip
Those look alot like file names and not infection names. I don't find any reference to anything like that on Norton or VirusTotal. Since you said these were Trojans, I would expect to see "Trojan" as part of the infection name.
".jar" files are executable Java applets. The random alpha-numerics would seem to indicate a cache file, likely from a browser with Java enabled. And we all know what ".zip" means.
Worst case is that you had Java enabled in a browser and were infected by one of the late variants of the Flashback Trojan over a year ago or one of a couple of other attacks using the same vulnerability but targetted against a small number of political sympathizers. Much more probable is that thes were Windows only Trojans. Hopefully you have a fully up-to-date OS X, including Java, and have disabled Java in all your browsers by now.

Setting Up Mailserver to received and Send Mail for external Network

I have a G5 currenty running 10.3.9 Server with Mail services run and working fine, we are upgrading to 10.4 Server and would like our Sales Reps the ability to send and Receive mail from outside the office. How do I configure my server, Router, ISP and/or Mail clients to do this??? we are currently able to recieve mail from outside just not send.

I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
# Global Postfix configuration file. This file lists only a subset
# of all 250+ parameters. See the sample-xxx.cf files for a full list.
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# sample-smtpd.cf).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see sample-local.cf).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# $inet_interfaces, while $local_recipient_maps is non-empty and the
# recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#unknown_local_recipient_reject_code = 550
unknown_local_recipient_reject_code = 450
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in file sample-smtpd.cf.
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions restriction in the
# file sample-smtpd.cf for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction in the file sample-smtpd.cf.
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = gateway.my.domain
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 50 SMTP server process
# limit, this limits the mail inflow to 50 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# Insert text from sample-virtual.cf if you need virtual domain support.
# "USER HAS MOVED" BOUNCE MESSAGES
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.
# TRANSPORT MAP
# Insert text from sample-transport.cf if you need explicit routing.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination
# and unknown@[$inet_interfaces] is returned as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see the sample-filter.cf file.
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#fast_flush_domains = $relay_domains
#fast_flush_domains =
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 10
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you don't have X installed on the Postfix machine, try:
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
# THE FOLLOWING DEFAULTS ARE SET BY APPLE
# bind to localhost only
inet_interfaces = all
# turn off relaying for local subnet
mynetworks_style = host
# mydomain_fallback: optional domain to use if mydomain is not set and
# myhostname is not fully qualified. It is ignored if neither are true.
mydomain_fallback = localhost
myhostname = jamestownpress.com
mailbox_transport = cyrus
enable_server_options = yes
luser_relay =
maps_rbl_domains = dun.dnsrbl.net
message_size_limit = 0
mydestination = $myhostname,localhost.$mydomain
smtpd_use_tls = no
smtpd_enforce_tls = no
smtpd_tls_loglevel = 0
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = plain
server_enabled = 1
relayhost =
smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
always_bcc =
mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
content_filter = smtp-amavis:[127.0.0.1]:10024
so what do I need to change

UPS for my network

OK guys, I am not electrical engineer, so I need some help here.
This is my issue:
I am planning to purchase a UPS to cover my small network. It consists of:
- iMac 24" (Lion) with two external hard disks, both powered from the USB ports.
- Mac Mini Server (previous year, Lion) with two external disks powered by small brick converters.
What I would like from the UPS, is to provide enough time for the iMac and the Mac Mini to shut down gracefully when the power fails. Ideally, the UPS should send a signal to the two machines instructing them to shut down (I think this is possible with the Apple computers, not sure, hence the question). I would also like the UPS to be capable of powering itself up, and hence power up the computers, after a power failure. Finally, of course, I would like the UPS to provide protection to the computers, in case of over- or under-voltage conditions.
My main questions are:
- How many VA should the UPS be, to cover these two computers and perhaps a couple of Linksys routers? I know there is a formula that allows you to calculate that, so if you can give it to me, I would appreciate it.
- What brands would you suggest? I know that you US residents have access to much more brands than we have here, but give me your thoughts and I'll see what I can find locally. APC does exist here, I think this is a brand you have in US too.
- Wbat else should I know before I buy the UPS? Anything that can help me make the right decision would be appreciated.
Many thanks for your attention.

I just thought of something. Is it possible for one UPS to notify more than one computers that the power is down, so that the computers can switch themselves off? If not, then I could purchase two smaller UPSs instead of a large one, and dedicate each one to one of my computers.
Again, many thanks

How to choose switches, ipphones and copy machine for small business?

Hello,
I'm designing a network system for Nextrio Company. Right now, I'm going to choose a copy machine which has fax function; a small switch which could connect this copy machine and several other computers; several ip phone for small business.
Could you tell me the type and cost of these devices I should choose?
Many thanks,

Hi Hanhan,
For the least amount of operational expernditure, and for great functionality at a small business price, I would suggest humbly that you look at the 300 series switch family.
The tolly group comparative report on our switch can be seen at the following link.
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps10898/Cisco300SeriesLANSwitchComparison.pdf
I would suggest you check out the following models and get pricing. the switches come in 10/100Mb/sec speed or Gigabit speeds depending on the switch port count and your needs;
Model Name
Your ordering P/N
Description
Fast Ethernet - access port 10/100MB/sec
SF300-08
SRW208-K9
• 8 10/100 ports
SF302-08
SRW208G-K9
• 8 10/100 ports• 2 combo* mini-GBIC ports
SF302-08P
SRW208P-K9
• 8/10/100 PoE ports• 2 combo mini-GBIC ports
SF302-08MP
SRW208MP-K9
• 8 10/100 Maximum PoE ports
• 2 combo mini-GBIC ports
SF300-24
SRW224G4-K9
• 24 10/100 ports
• 2 10/100/1000 ports
• 2 combo mini-GBIC ports
SF300-24P
SRW224G4P-K9
• 24 10/100 PoE ports
• 2 10/100/1000 ports
• 2 combo mini-GBIC ports
SF300-48
SRW248G4-K9
• 48 10/100 ports
• 2 10/100/1000 ports
• 2 combo mini-GBIC
SF300-48P
SRW248G4P-K9
• 48 10/100 PoE ports
• 2 10/100/1000 ports
• 2 combo mini-GBIC ports
Gigabit Ethernet - access ports 10/100/1000Mb/sec
SG300-10
SRW2008-K9
• 8 10/100/1000 ports
• 2 combo mini-GBIC ports
SG300-10P
SRW2008P-K9
• 8 10/100/1000 PoE ports
• 2 Combo mini-GBIC ports
SG300-10MP
SRW2008MP-K9
• 8 10/100/1000 Maximum PoE ports
• 2 combo mini-GBIC ports
SG300-20
SRW2016-K9
• 18 10/100/1000 ports
• 2 combo mini-GBIC ports
SG300-28
SRW2024-K9
• 26 10/100/1000 ports
• 2 combo mini-GBIC ports
SG300-28P
SRW2024P-K9
• 26 10/100/1000 PoE ports
• 2 combo mini-GBIC ports
SG300-52
SRW2048-K9
• 50 10/100/1000 ports
• 2 combo mini-GBIC ports
regards Dave

Redesigning a small network

I've been tasked with redesigning a small network (15-20) including wireless. Cisco recommends the RV220 as the entry point Firewall/Router/Wireless and researching there are apparently some good and bad sides of having everything all in one unit depending on who you ask. The other option would be to get a dedicated Firewall/Router and then run the wireless on a seperate device(vlan). I'm fine with either solution but my main concern is performance on the physical connections as well as reliability with the wireless having good range and not dropping or having to reboot the router continuously. Behind the router/firewall I will purchase one of the Cisco 24-port gig switches for physical connections through the office. Anyone have advice or suggestions on models to get for the router/firewall/wireless setup? Budget is not a problem although I don't want to pay for something that is overkill for 10-15 wired workstations and 5-10 wireless including a guest wireless. Thanks in advance.

I am going to sound like a broken record. I am no big fan of getting a wireless router. The reason is because of the location. It would be ideal to place your wireless access point (WAP) in the middle of your wireless clients. A router is normally installed in some far corner somewhere. I mean this is OK if you are bio-medical lab and you are testing wifi with rats.
Ok, next what model of the router. To answer that question, one has to ask you this: What is your WAN bandwidth now and are you expected to grow any larger (size of the office and WAN bandwidth)?
The argument as to get a dedicated firewall or get a router with firewall functionality all depends on the question.

MPLS for small network

Similar Messages

Maybe you are looking for