Hi Islam, Check this http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/VPNLoad/ch8_Dual.pdf HTH, Lei Tian Sent from Cisco Technical Support iPhone App
... View more
Hi, This is not working on Windows .. Is there a version that is working on Windows, or should I install Windows Server? I'm using this as a test lab
... View more
Hi Islam There is no special configuration required to add any windows DHCP server. And it is also not mandatory that the DHCP server should be in the same vlan where users are placed. You can place your DHCP server in any vlan just you need to enable dhcp helper-address command on all the vlans where DHCP users are placed. Example : Topology: ========= {Switch }------Vlan 10 {DHCP server/IP of DHCP server is 10.1.1.230} | | Vlan 15 {users} Configuration on Switch: ======================== Switch(conf)# inter vlan 15 switch(conf-if)# ip helper-address 10.1.1.230 Thanks & Regards Sandeep
... View more
The DHCP server will respond to all DHCP discover messages that are broadcast on the same segment / vlan. No extra configuration required. hth Please rate useful posts & remember to mark any solved questions as answered. Thank you.
... View more
Dear Bilal, Great work you did. I prefer HSRP but the drawback here is each Vlan's adding or Network adding, you need to create Groups. If it was an L3, PBR was the efficent. Is it.
Let me know what the config you did in the switch. I hope you added 2 Vlan database in it right.
... View more
Issues you could face are as follows: 1. Constant changes in requirement (hence try to focus on scalability and accomodation of new requirements in your design phase) 2. Underestimating the requirement for your Server Farm/Data Center (Sit with your server, storage & DB admins to carefully understand what they require, plan out server farm VLANs, understand etherchannel/channel bonding requirements, check if load balancers are needed, maybe a separate network is required for things like backup inside the prodcution network, this list could go on and still one might miss critical issues) 3. Losing focus on security (A possiblity especially if you're new, one tends to be too much focused on everything except security. Pay close attention to desiging your enterprise perimeter, if you have sites connected to your office spend time with ISPs to verify your bandwidth requirements, keep business stakeholders aware of security measures which are going to be placed in your network) 4. Test Configuration before implementation day (test, test and test. keep your configurations ready before implementation day. You don't want to spend too much time figuring out how to connect on the day rather you wanna have ample time to monitor the network behaviour for minor tweakings) 5. Manage stakeholders expectations Create scope for the project and ensure stakeholders understand what you're trying to achieve. You dont want to hear things later like "our network is sooo slow" or "wireless keeps disconnecting all the time". Agree on the functional capabilities of the network and propose budget accordingly. As is said "Everthing that can go wrong will go wrong", you can do your best but still miss out. Get in touch with experienced perosnnel like CISCO partners to check your plans/requirements.
... View more
Hello, also with explanation -> http://www.firewall.cx/cisco-technical-knowledgebase/cisco-routers/867-cisco-router-site-to-site-ipsec-vpn.html Best Regards Please rate all helpful posts and close solved questions
... View more
Check this link out for more details. http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_09.html#wp1015177 --Pls rate if this was helpful--
... View more
There are many docs that can help you configure an autonomous AP. You just need to search on, How to configure access point. Seamless roaming is tricker on autonomous than lightweight. You would have to be able to use the authentication and be able to setup WDS. Here is a link for that. http://www.cisco.com/en/US/docs/wireless/access_point/12.4_3g_JA/configuration/guide/s43roamg.html Sent from Cisco Technical Support iPhone App
... View more
Hi Islam, The best way to check this is use Feature navigator for next time. Link for the same : http://tools.cisco.com/ITDIT/CFN/jsp/compareImages.jsp I have attached the difference this time for you. Regards Inayath *Plz rate all usefull posts.
... View more
Islam, I agree with Rick. If your switches are POE capable and you want to connect your PCs to the back of the phones, then you want to put the voice traffic in one vlan/subnet and the data traffic in another vlan. The reason for that is that most of the time you apply QOS to voice traffic and not data and so if you have them in separate vlans, you can easily apply QOS to the voice vlan/subnet. Regarding the gateway, I am no voice expert, but as far as I know the voice gateway enables you to have VOIP in your LAN and PSTN on the WAN. For example: when your users in the office call each other, they use VOIP, but if they need to call home, they use PSTN and that is the gateways job to provide call routing between internal users and PSTN. http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/gatewy.html HTH
... View more
Hello, As pille said, if you use vrf-lite you need to connect Core1 and Core2 with links in respective VRFs. VRF is local to both routers and you connected them with link S0/0 <-> S0/0 in global routing table. Solution -> 1) create second link between Core1 and Core2, existing link will be added to first VRF and new link to second VRF, that way each vrf can communicate via restective link. 2) leave configuration as it is and create two GRE tunnels via existing link, one tunnel for one VRF. Core1 interface Tunnel 1 ip vrf forwarding C1 ip address 10.0.0.1 255.255.255.0 tunnel source s0/0 tunnel destination 192.168.0.2 interface Tunnel 2 ip vrf forwarding C2 ip address 10.0.0.1 255.255.255.0 tunnel source s0/0 tunnel destination 192.168.0.2 Core2 interface Tunnel 1 ip vrf forwarding C1 ip address 10.0.0.2 255.255.255.0 tunnel source s0/0 tunnel destination 192.168.0.1 interface Tunnel 2 ip vrf forwarding C2 ip address 10.0.0.2 255.255.255.0 tunnel source s0/0 tunnel destination 192.168.0.1 Traffic from particular VRFs will be transported between Core1 and Core2 thanks to GRE tunnels. Do not forget to configure static routing to work this properly. Best Regards Please rate all helpful posts and close solved questions
... View more
I would remove the ACLs from your interfaces and test again. Then you can see if its a routing or NAT issue. I see ACL 169 configured on your LAN port but no mention of it in your config. This could be causing problems for you as well. Elton Sent from Cisco Technical Support iPhone App
... View more