Tag Info

Hot answers tagged


Put it on a dedicated storage-specific VLAN, chances are there won't be a need to route at all if you run all of your storage and servers into the same switches. This gives you the option to monitor JUST the SAN traffic and potentially to traffic-manage it if needed.


VLANs exist at layer 2 in most networking models. They do not communicate with anything automatically. They don't do IP. Since it has no IP we can also pretty assume your device is not configured as a layer 3 router. If communication is happening, some other device on your network is facilitating it. If there is no communication, and you are trying to ...


I had a firewall policy rule that was causing the pingability, ICMP echo permission hidden in a group service list and restricted to certain hosts and I didn't see it. :-0 Also had an issue getting VLAN 2 connectivity to a port on the Netgear that is tagged with that VLAN ID, but that appeared to resolve with a restart of that device. (Which wasn't clear in ...


VLan interfaces declared with no ip address are here to act at layer 2 only. However, you need to declare them to be able to setup mode access for specific vlan on physical interfaces. In its actual config, your switch does not route any VLan. For sure you have another router (may be a Firewall) with network defined so that your VLan can be routed. This ...


You can grep hosts in seastat -d entX (where entX is the SEA device). You need enable accounting to collect SEA stats Check if accounting is enabled on SEA: lsdev -dev entX –attr accounting Enable: chdev -dev entX -attr accounting=enabled


This is just one way to do this: you'll need to use the L3 capabilities of those switches to route between the sites. Move the MPLS onto the 4500-series switches. The 3500 is a L2 only switch and can't route. Assign IP addresses in a /31 to each switch on VLAN777 at both ends (e.g. and a. You'll do by creating a new 802.1Q vlan ...

Only top voted, non community-wiki answers of a minimum length are eligible