I have a NAM 2304 at a remote location which apparently has a bad drive. It is beeping very loudly and causing some disturbance to those who work in the area.   Is it possible to silence this alarm while the RMA processes?   Thanks. ... View more

I have two IPS devices in an active/passive setup that each have two ports connected to a switch as an aggregate link. The switch in turn has two port-channels which consist of two ports each. The IPS device uses LACP.   One of these port-channels has the ports configured as "channel-group 1 mode on" and the other has its members configured as "channel-group 2 mode active".   When the active IPS is the one connected to the "channel-group 1 mode on" ports, traffic does not work properly. When the active IPS is the one connected to the "channel-group 2 mode active" ports, traffic works as expected.   However, when I change channel-group 1 to "active" (making it LACP) the links go into Suspended mode because they are not receiving LACP BPDUs from the passive IPS. The vendor has said that a passive IPS will not send these LACP BPDUs.   My question is, if there is a failover and the IPS with switch ports in suspended mode becomes active, will those suspended ports become active without user intervention or will they have to be shut/no shut manually for them to work properly?   Thanks. ... View more

So I'm trying to trace out this route in my environment running MPLS/MP-BGP. When I check for the route the switch returns a good route, but when I try to find the RD using show ip bgp the switch tells me there are no routes. I am wondering if this could be related to bug CSCum05295?   See the below output:     Core-Switch# sho ip ro vrf APP 10.10.10.200 IP Route Table for VRF "APP" '*' denotes best ucast next-hop '**' denotes best mcast next-hop '[x/y]' denotes [preference/metric] '%<string>' in via output denotes VRF <string> 0.0.0.0/0, ubest/mbest: 1/0 *via 10.0.10.10%default, [200/51456], 7w4d, bgp-65400, internal, tag 65400, (mpls-vpn) Core-Switch# sho ip bgp vrf APP 10.10.10.200 BGP routing table information for VRF APP, address family IPv4 Unicast BGP routing table entry for 10.10.10.128/25, version 0 Paths: (0 available, best #0) Flags: (0x090000) on no lists, is not in urib, is not in HW, vpn: version 0, (0x910000) on no lists VRF advertise information: Path-id 1 not advertised to any peer VPN AF advertise information: Path-id 1 not advertised to any peer       ... View more

I have a disaster recovery setup at a remote site that includes multiple 7K switches. Currently it is running RPVST+. The issue we are having is that we have a lot of trunk links set up between these switches that have a lot of VLANs going across them. Due to the nature of a per-VLAN ST protocol, we have a very large number of spanning-tree instances which puts our switches under considerable resource strain while also causing any re convergence issues to take an unacceptable amount of time. Further, we find that each we are having to allow more VLANs across those trunks each time we do a practice scenario as more equipment, links, lines of business, etc... are established in our production environment and must be mimicked (to a degree) in our disaster recovery environment.   I would like to move my environment to MST, but as we do not currently run MST anywhere I am seeking some guidance.   I understand the configuration aspects of it, but I am wondering, based on my topology, would it be best to run 1 or more regions.   The basic architecture of this environment is as follows:   Aggregate switch that connects to one of 3 VDC's on 7Ka.   7Ka connects to a "backbone" VDC on 7kb (this VDC does not run any spanning-tree). That backbone VDC on 7Kb connects to one of 7 VDCs, 4 are on 7Ka and 3 are on 7Kb. ... View more