What other switch are you connecting the 5406 to.
In any event it is fine, just remember to use 802.1Q trunking on the Cisco, make sure they are both trunking the same vlans and the same management vlan.
Otherwise it's all good
Hello.
If you are running MSTP on the Procurves then you should be able to work with Cisco PVST, I have had this working not problems.
As with IST and CIST and CST think of 3 circles inside each other, IST is the inner circle it controls the local spanning instance of say MSTP, CIST controls...
If you want to stack them in the 3com XRN or Cisco Stackwise sense were you have dual redundant paths then the answer is no.
You can fix it up to make it look like the switches are stacked by using MSTP (Multiple Spanning Tree) so you have two (or one) root, the top switches switch traffic out...
Hello
You need to go to the interface command prompt of the interface you want to monitor an type in "monitor"
The go to the global configuration context and type in "mirrorport [port number]"
I think that's the right way around
Cheer lads
I have sorted mine out, I place both of the Softconsole machines into the voice vlan and hey presto, it all works, all of the P.C still work, i.e outlook, etc,etc
It is strange that the BLF's sometimes worked since a broadcast should not be forwarded across a Vlan interface.
Nice
Hello, I have the same issue with Softconsole not worlking on 3.1(65).
This company has three sites, all linked via LES circuits, the links are rounted so each office has IPPhones in thier own subnets.
They have two consoles, which are on different subnets to the IPO and the BLF do work...
IPStanding,
I have also seen this, but on a 412, every 30mins we lost connectivity to the IPO, only a reboot cured the problem.
we ran a protocol sniffer on the IPO port but did not see anything unusual. We suspected an IDS on the network or a LaBrea Tarpit. The customer was looking for a...
The command is:
(conf)#trunk A1,A2 trk1
The trunk configuration must be performed on both sides of the trunk before the redundant links are connected.
Port trunking has implications for VLAN configuration. Because aggregated ports cannot be configured individually for VLAN membership, the...
The IEEE standard 802.3ad, also known as LACP, is based on Cisco’s Port Aggregation Protocol (PAgP). LACP was standardized to allow a switch to automatically recognize coterminous, full duplex, same-speed links between itself
and another LACP-compliant switch.
Although LACP can automatically...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.