Tag Info

New answers tagged

0

There are couple of options: option 1(Simple but need multiple 3x routers) -Install a switch and connect to ISP router on WAN interface -Install a router for each individual company utilizing 1 x public IP Option 2(Use of 1 router and layer 3 switch) - install a single router with VLAN capability, setup 3 x VLAN (sub-interfaces) for each company. -install ...


2

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 ...


0

I accidentally got into this page again, so decided to answer my own question. I've found a solution that works for quite some time now: the wanted functionality is achieved by using Traffic segmentation and VLAN trunking features of the switch. Traffic segmentation lets you allow or deny traffic forwarding between ports (in any configuration) and VLAN ...


1

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. 10.55.7.0/31 and 10.55.7.1/31) a. You'll do by creating a new 802.1Q vlan ...


0

Generally it is either 1 of 2 ways: Either the phone is getting it's configuration information (including VLAN information) from some source (DHCP option/config download/etc) or the switch is using LLDP (Link Layer Discovery Protocol) to discover it's a phone because the phone is advertising with LLDP that it is a phone.


0

An aliased interface is really just a secondary address on the original interface the alias was created from (see how there are no packet counters for lan1:1). As such you can't create VLAN sub-interfaces on it. What you can do is create aliases or add secondary addresses to a VLAN interface.


1

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


4

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.


0

I don't think it is possible to have a port with tagging enable AND without.. Either you are in access mode with an id configured (no tagging), Either you configure multiple id on the port in access mode. Either you are tagging on that port,with à single id Either you are tagging multiple id to isolate trafic, it is called a trunk I think what you need ...


1

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 ...


3

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 ...


0

@Stuart I am working on similar project at the moment I am experiencing similar problems with the setup. Initially we used bonded DSL connection with Sharedband routers which despite ISP claims that 'there are no ports blocked', APs connected were not obtaining DHCP and failing to talk to controller. It was due to blocking TR-068 layer. We managed to solve ...


0

I'm not sure it's the best answer to the question of how to make this work, but in the absence of a better answer, I figured out a way to make it work myself. Basically, I went with the idea that if you are using what is essentially dynamic VLAN assignment (even though it's termed a voice feature), you have to use it for both the VOICE and DATA domains to ...



Top 50 recent answers are included