Computer A (GigE) Switch 1 (gigE) Media Converter (Fiber Run) Media Converter (gigE) Switch 2 (gigE) Computer B
We have a cross connect in our data center that uses media converters (fiber) to regular 1000FD on each end.
Each end of the 1000FD handoff is plugged into port 1 of the 3870's (switch 1 and switch 2).
Pinging from Computer A to Computer B we receive a 50% packet loss. Pinging from Computer B to Switch 1, no packet loss. Pinging from Computer A to Switch 2, 50% packet loss.
Looking in the interface, the port 1's on each switch auto negotiate to 1000FD, however flow control shows as off.
We asked our data center to run tests on the media converts and fiber runs and everything comes back 100% fine. Has anyone seen a weird issue like this before with 3com switches not playing nicely with media converters?
I have no clue whats going on and our data center said the fiber run/media converter is fine... [url]
We end our relationship with egihosting.com last year with only one owned 3Com 4526 switch left in their datacenter, we thought there might be some chance to come back with them, so we did not ship back our switch right away.
This year at May 29 we ask them to ship back the switch and they ask for $65 fee: ....
I need a basic L3 switch for maybe 25 mbps that will do hopefully up to 50 VLANs and which will not require me to hire someone to configure it.
As much as I like Cisco, that rules them out.
The reason I'd like a Layer 3 switch is so that I can run my backups and inter-server transfers without adding to my bandwidth bill. Also, VLANS are a critical requirement as i have a lot of customers with root on their managed servers.
So i am looking at HP [gasp] switches. How "easy" is the web-based configuration widget? [I'm an advanced unix admin but networking is a mystery to me.]
This is a starter switch and once i have a full cab of servers I'll be able to spend $7K on a pair of 3560s and hire someone to configure them for me ... but until then what can i get to meet my requirements?
I'm not sure exactly how to phrase the question. But, I'm researching how to PXE boot a server without having a DHCP/PXE server in each vlan.
Scenario: Datacenter with dozens of servers. 1 VLAN per server. Cisco switches and routers. Each server has a serial console available for remote management (OS and BIOS are configured for serial console). If an admin wants to re-install OS, they should be able to reboot the server and tell the BIOS to initiate a PXE boot request. A central install server is available to provide the DHCP and PXE boot images.
Has anyone tried this? I have been reading about the 'ip helper-address' for Cisco to relay DHCP requests. Interested in hearing about real-world setups. Or is there a better way to accomplish remote OS installs?
I'm looking for a solution that I can place a firewall between 2 vlans on a BigIron router with L3 enabled.
For this moment there is one big vlan2 with a ip-route 0.0.0.0 0.0.0.0 18.104.22.168 and a router-interface ve2 with the IP of the router, the address I use as gateway on the machines behind it.
The WAN port has the IP address to communicate with to the GW of the carrier-router (22.214.171.124)
Because I want to let the BigIron the routing I was thinking of 2 vlans, one for the lan-vlan and one for the wan-vlan, but this will be a problem because I only have one IP-block what I can use.
So the sitiuation must be as follow on the BigIron:
WAN => vlan2 => firewall => vlan3(lan)
Because of the fact that the firewall will be transparent, this should be no problem to place it between the vlans. The actual problem is how to manage this. In simple words, I should be able to replace the firewall with a cross-cable and it should still work.
Cisco for an example has a SVI solution for this, but I can't find such thing for a Foundry router.
Having a slight problem working with one of our Extreme Summit 48 (ugh) switches - I've figured out most of the basics, but I can't seem to find any way to add a secondary IP address to a VLAN! This, I would have thought, would be a pretty basic feature to have. Typing "config vlan [vlanname] ipaddress 126.96.36.199/24" works for setting the primary IP, but I can't figure out how to add any more - and doing the command again just overwrites the first one.
So... does anyone have any tricks up their sleeve, or is this something that Extreme neglected to add to this model switch?
I've read that all ethernet switches in a MST Region need the same Name, Revision number, and list of member vlans for each Instance. So what happens when you need to change the range of VLANs in a MSTI ? Let's say that you need to add a range of vlans to an instance that spans 20 switches? How would you do that?
Can you make a recommendation for a switch-based L3 router which can
- hold a moderate number of routes (interface routes, a few hundred statics + default) - OSPF and BGP - MST - 1024 layer-3 dot1q subinterfaces (or maybe VLAN interfaces) with + traffic policing in and out per subinterface/vlan + VRRP/HSRP/NSRP - IPv4 & IPv6 native - 2x GigE ports - Not tip-over under 1gbps DDoS towards a VLAN interface.
I've been using 3560Gs, but they seem to lack the output traffic policing. I'd prefer to have subinterfaces which don't run spanning-tree, versus Vlan Interfaces to a trunk interface which runs spanning-tree. These switches sit at the L3 boundary between two L2 networks.
Cost is a big factor; but I also must carry vendor licenses & support contract, if the vendor asserts that not doing so is illegal in US.
We are co-located at a datacenter and host web sites, and corporate email systems, as well as host dedicated servers for customers.
We currently have two /25 internet facing subnets from our provider. We have a Watchguard X5500e 8 port gigabit firewall that supports routing as well as VLANs. We also currently own QTY4 2848 HP Gigabit switches.
We currently have each switch connected in a loop with 2 gigabit ports trunked using static LCAP. The switches are connected as follows: A > B B > C C > D D > A
Rapid STP is turned on. One thing is - is this the ideal trunking scheme?
The more important question is this. We would like to separate ips from each other using VLANing.
IE: we might have a client with 5 different IPs in one or more subnets and we would like to group them together.
We ideally do not want to break up the subnets into smaller ones as it makes it hard to reconfigure and it wastes ip addresses, as we do not have that many.