Save
Saving
  • Brett Ferrell

    Ronnie,

    Thanks, I was really just looking to have inter-vlan routing happen as deep in the network as possible, so everything doesn't have to go up to the core, which I now have working. Next stop is to try to get my Cisco switches to pass Airplay Bonjour multicasts. Thanks again.

    Brett

    posted in Cisco read more
  • Brett Ferrell

    @Brett-Ferrell Nevermind, I figured it out... left out a static route that I needed.

    posted in Cisco read more
  • Brett Ferrell

    This is more of a general good practices question, I suppose. I have a good size SOHO network, with fiber service. I want to segregate into VLANs to limit the number of devices per domain. I have several L3 capable switches to achieve this, and my wiring is a star topology. I note that almost every example I can find show the core switch doing the L3 routing and every other distribution switch in L2 mode. This seems sub-optimal for many of the same reasons as router-on-a-stick (traffic has to go all of the way to the core, even if the destination is on a different VLAN on the local distribution switch). I'd like to avoid that, but I'm having trouble making it work in my lab configuration. I think this is because either:

    1. I have multiple L3 switches trying to route for the same network or
    2. I need to have static routes setup between the L3 switches

    The question is, should this be able to work, and is it a good idea, or should I just put the distribution switches into L2 mode? Here's a diagram.

    alt text

    All 3 switches have all vlans configured, and SVI's created. The core has a 0.0.0.0 route to the internet gateway router, the distro switches have a 0.0.0.0 route to the core. PCs connected to the distro switchs on the native vlan work 100% (can access internet) but when connected to a non native VLAN port (with gateway of the distro switches VLAN SVI) they can only see computers on the VLAN (on any switch in the network) - so VLAN trunking is working at L2, but the L3 routing is not.

    Brett

    posted in Cisco read more
  • Brett Ferrell

    Ok, so if I give the login screen a few seconds, the "other" option does pop up, so I tried deleting my directory server and re-creating it, and still get the jiggly login on my MacBook (I also removed and added back the Directory server on it's UAC page)... thoughts?

    posted in Apple read more
  • Brett Ferrell

    When I open the directory utility (from the system preferences, users, login options, edit server), I see that I have 2 directory domains, "local/Default" and "ferrellmac.com". All of the accounts I have added are in the ferrellmac directory, all of the local and system ones are in Default. Is this an issue? The 'drag domains into preferred order for searching" would imply not.

    Also, sometimes when I go to the login window I don't get the "other" option. Why would that be?

    posted in Apple read more
  • Brett Ferrell

    Hey guys, I just watched the Open Directory episode and had a couple of questions.

    1. If I already have local-only accounts, how can I convert these on my server to be network accounts, and will it keep the directory contents (assuming I select Local and not services only)??

    2. I have created a test account (several, actually) and set the password, and set my MacBook to use the directory server, I see the server by name and have the green dot but it won't let me login with that account, it just 'jiggles'. Any troubleshooting thoughts?

    Brett

    posted in Apple read more
  • Brett Ferrell

    Hey guys,

    I've been working my way through the Net+ shows and enjoying them, but when I went through the Switches episode I came away a bit confused. Maybe it's just me, or maybe it can be clarified in a future episode.

    VLANs

    When the guys were talking about VLANs, they talked a lot about trunking and VTP and setting up trunk ports for inter VLAN communication. Great, that all sounded good. In this section the IP Routing command was not talked.

    Then they talked about setting up an IP address and default gateways, and how this was required for remote administration and routing VLAN traffic. Ronnie activated ip routing and added int fa0/13 for this.

    I can see needing IP routing enabled to route between VLANs, but I'm confused about what to do with the switchport he configured (13). Is this really only required if the switch is routing to a VLAN that it is not connected via a trunk port? For remote administration couldn't you just add the IP to vty rather than a physical port? Would I hook fa0/13 to my router?

    I just generally came away confused about inter VLAN routing and the connection to the IP address.

    Brett

    posted in CompTIA read more
  • Brett Ferrell

    Is there an update? I don't find the app, and we're late second quarter??

    posted in General Discussion read more