cisco 2811 with 2 fast ethernet ports and 4 vlans-2

pts.
Tags:
Bandwidth
Cabling
Cisco
DHCP
DNS
Hardware
Hubs
IPv4
Network protocols
Networking
Networking services
Routers
Switches
I need urgent help on this. I have a brand new cisco 2811 with 2 FE ports. The port f0/0 is connected to the internet and the f0/1 will be connected to the switch which has 4 vlans configured on it. I have no idea how to go about doing this. Can someone please help me with the configuration on the router. My responsibility is to configure the following: * A trunk on the router for the vlans. * 4 sub interfaces with IP address on the router. * Route this vlans out of the network. Our devices are hosted in a datacentre.Now we are going to place a cisco 2811 in the datacentre which will be uplinked to the backbone switch of the upstream provider.The cisco 2811 should carry vlans from a remote NOC to the internet.It is something like this:- Backbone switch---->(f0/0)-Cisco 2811(f0/1)--(trunk)--(Remote switch)[vlan1,vlan2,vlan3,vlan4] Now my queries are *On the f0/1 do I configure anything or I directly create start creating sub-interfaces with the IP Addresses? * What kind of encapsulation do I use on the vlans? * For this network we have a class 'C'(/24), I want to subnet them into 4 subnets. * Do I use static routes on the router? but can someone please tell me what will be my next hop?Will it be the f0/0 or the IP address of the back bone switch.

Answer Wiki

Thanks. We'll let you know when a new response is added.

First what is supplying DHCP? Or are you using static ip’s, which I couldnt imagine? Is the class C private address space or global?

The FE Int that connects to the LAN will have one ip from your class C. The Other will have a Global ip from the isp or in your case the backbone. If you have a full class C then you will setup NAT with a pool of the class c addresses.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Astronomer
    Given the limits of the information provided, I will have to make some assumptions. If some of them are wrong, please clarify them for me. You have four VLANs on your internal switch and this 2811 will be the router for these networks. You want to extend these VLANs to a "remote NOC". I find this term a little confusing. Is this remote NOC within your internal network? First things first. What tagging/encapsulation does your central switch use for its VLANs? Does it use ISL or 802.1Q? Your devices need to match. I prefer 802.1Q so I'm not using a proprietary protocol. Also remember that cisco defaults to not tagging VLAN 1. Other brands want you to choose the untagged VLAN as part of setting up VLAN aggragation. If your 2800 will be the router for the VLANs, you will need to provide subinterfaces for each VLAN/network on the interface connected to your switch. Set up your tagging and subinterfaces on f0/1. Configure the clients to use the respective IPs of the subinterfaces as their default gateways. Set a default route on the 2800 pointing to the ISP for all external traffic. If you are using private IPs, then NATing will have to be configured. If there are no other routers then you don't need more routes. The 2800 will know how to reach the four VLANs it's connected to and just needs to know where to send everything else. Configure your external interface without VLANs. If your router is a DHCP client, it should automatically receive a default route with the DHCP address. If you aren't using DHCP, your ISP will provide you with the address of the router in their net you should use as your default gateway. I hope this addresses most of your questions. If you wish to clarify your topology and have specfic issues with configuration commands, let us know. rt
    15 pointsBadges:
    report
  • R0berth1
    It should look something like this: interface FastEthernet0/0 description LAN Interface no ip address duplex full speed 100 ! interface FastEthernet0/0.1 description **MANAGEMENT VLAN - DO NOT USE** encapsulation dot1Q 1 native no snmp trap link-status ! interface FastEthernet0/0.100 <--equals the Vlan that you want to use description **VoIP-Vlan** encapsulation dot1Q 100 <--must match the number above ip address 10.10.10.1 255.255.255.0 no snmp trap link-status ! interface FastEthernet0/0.200 description **PC-Vlan** encapsulation dot1Q 200 ip address 10.20.20.1 255.255.255.0 no snmp trap link-status ! interface FastEthernet0/1 no ip address shutdown duplex full speed 100 ! interface Serial0/0/0 description **MPLS Circuit for ????** mtu 1600 bandwidth 1544 no ip address encapsulation frame-relay IETF load-interval 30 service-module t1 timeslots 1-24 frame-relay lmi-type ansi service-policy output voice-priority ! interface Serial0/0/0.100 point-to-point <--this should match the dlci that the bell assigned description **Circuit ID is ????** ip address 0.0.0.0 255.255.255.252 no cdp enable frame-relay interface-dlci 100 <--this is the assigned dlci
    175 pointsBadges:
    report
  • BlankReg
    Just a point of order, the subinterface number does not need to match the vlan ID. It is best to configure it that way, so it makes better reading, but the vlan is decided by the value after the 'encapsulation dot1Q ' command, and not by the interface command.
    12,325 pointsBadges:
    report
  • Yeah999
    How to install DNS on server 2003?????
    10 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following