Search results for query: *

Bit harsh...! -Blue The significant problems we face cannot be solved at the same level of thinking we were at when we created them

Thanks Burt that was my understanding, just wasn't sure with it having an access-group applied to the interface even though the access-list didn't exist... -Blue The significant problems we face cannot be solved at the same level of thinking we were at when we created them

Your interface Ethernet0/0 has an inbound rule (101) that is nonexistent and I'm not sure if that means a default deny any any is applied The outbound rule (102) has a strange deny... access-list 102 deny ip 0.0.0.0 255.0.0.0 any I believe that is saying a source network of anything in the...

Could do with seening your config file and a diagram if possible... I would have expected you to have multiple VLAN interfaces rather than the one and clearly broadcast traffic does not, by default, get propagated across subnets. -Blue The significant problems we face cannot be solved at the...

I suspect you need helpers on the vlan interfaces... interface Vlan-interface2 udp-helper server x.x.x.x -Blue The significant problems we face cannot be solved at the same level of thinking we were at when we created them

I don't believe you can with that device as Policy Based Routing is not supported on the 5500 range. The reason is that it is not possible to achieve wire speed routing using PBR, something that 3Com do not want to compromise on a switch. The alternative is to use a lollipop router (such as a...

The switch will route automatically if you have VLANs defined with interfaces that have an IP address, so assuming you have no VLAN interfaces defined it will not route. Remove any qos statements from the port interfaces. -Blue The significant problems we face cannot be solved at the same...

OK once more... Yes you can. Your router will have a /24 interface on the 10.1.1.1 network but a /16 route on it for the 10.1.0.0 network via your L3 device. Your L3 should have interfaces to all the 10.1.x.0/24 networks so does not need routes defining - as it has connected interfaces...

No problem... I was assuming there was some logical separation but you're obviously just using the ranges for convinience only... As stated by everyone, what you are proposing is quite standard, and straightforward to setup. So the answer is still yes! -Blue The significant problems we face...

Aren't they /24 ranges rather than /16... 10.1.2.x/16 is in fact 10.1.x.x/16 10.1.2.x/24 is 10.1.2.0 to 10.1.2.255 Essentially each site is a single /16 range split into a number of /24 subnets (VLANS). For each subnet you require you will need a VLAN interface (address) on your L3 device...

It should work for all the switches as there is no way to disable the recover facility... "The password recovery feature allows you to reset the admin user password by logging into the unit via the console port using the username recover and password recover. If you power cycle the unit within...

No, one of the benefits of XRN is to allow you to remove a single point of failure from the infrastructure, so rather than having an aggregation link back to one device you spread the links across two. Interestingly, 3Com engineers do NOT recommend using LACP, preferring to manually create the...

Is it a /24 network or two smaller networks that you are trying to link together? -Blue The significant problems we face cannot be solved at the same level of thinking we were at when we created them

The user manuals can be found at the following URL... http://www.3com.com/products/en_US/result.jsp?selected=2&sort=effdt&sku=3C17700-US&order=desc -Blue The significant problems we face cannot be solved at the same level of thinking we were at when we created them

The 4900 is an early L3 device so not particularly sophisticated, but L3 none the less... So, if you add an IP address to each of the VLAN interfaces the switch will automatically route between the VLANS. -Blue The significant problems we face cannot be solved at the same level of thinking we...

It should be on by default... The command is "jumboframe enable" and to turn it off is "undo jumboframe enable". This should be run from the interface context.. interface TenGigabitEthernet1/1/1 jumboframe enable To confirm run the "display interface TenGigabitEthernet1/1/1", part of the...

I believe this relates to WHERE the TFTP traffic is being generated on the ASA and if the traffic is being recognised as interesting and thus sent down the tunnel. The TFTP traffic never passes THROUGH an interface so is not identified as interesting, and thus sent down the tunnel. You'll have...

Normally jdoebling would be correct, however there's a known issue with frame size and the 10Gb modules.. . We had to enable jumbo frames at both ends in order to get them working correctly! In most instances Jumbo frames are not encountered even when such things as 802.1p and/or Q in Q...

If you have an interface (ip address) on the vlan you can get similar output the command is quite similar... display interface vlan 2 -Blue The significant problems we face cannot be solved at the same level of thinking we were at when we created them

Yes, there always has to be at least one VLAN, also by default VLAN 1 is used for the management interface, which is why you cannot delete it. -Blue The significant problems we face cannot be solved at the same level of thinking we were at when we created them