MSTP Topology Change not in Logging

Hello,
we are trying to get rid ofsome MSTP problems at our campus, for any reason we get 10-15 topology changes per day.
With spanning-tree portfast enabled on all ports, we are still getting 5-10 changes per day.
Now i am trying to get a trap whenever a topology change appears to our cpi, but this event didn't even appears in the logging of the switch.
Configured Trap:
snmp-server enable traps bridge newroot topologychange
Any suggestions?
Greetings

We found it:
Trap ist called "The value of vlanTrunkPortDynamicStatus"

Similar Messages

  • Frequent MSTP topology changes on SF-300-08 and SG-300-10

    Hi,
    I am trying to configure MSTP on Layer-2 network at work. We have multiple switches connected on Wireless point-to-point links with redundent links.
    MSTP is configured with multiple regions. All the servers are located in RegionA and other regions are connected to RegionA via multiple links.
    There are 3 SG-300-10 switches in RegionA  --- SwitchA_1, SwitchA_2 and SwitchA_3.
    One of the simple regions (RegionB) has a single SF-300-08 switch (SwitchB) connected to SwitchA_2 via port e7 and SwitchA_3 via port e8. Hello Time, Forward Delay and Max Age are at their default values of 2, 15 and 20 respectively. The link between SwitchB (port e7) ---- SwitchA_2 is the primary link with cost 200,000 and the link between SwitchB (port e8) ---- SwitchA_3 is the backup link with cost 500,000.
    The log on SwitchB is shows in the table below. As it is seen from the table there are frequent topology changes for very short duration (1-4 seconds) before the topology settles back to the configured one. (Primary link forwarding and secondary link blocking). During this time there have been no link failures reported.
    Same thing is also observed within RegionA (SwitchA_1, SwitchA_2 and SwitchA_3 are connected to each other).
    How to stop these frequent topology changes? The topology changes within RegionA causes a lot of PPPoE sessions to reset and re-establish.
    Is there any way to find out what triggers these topology changes? Has anyone experienced similar behaviour?
    2147464623
    2011-May-24 13:54:15
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464624
    2011-May-24 13:54:15
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464625
    2011-May-24 13:54:15
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464626
    2011-May-24 13:54:15
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464627
    2011-May-24 13:54:13
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464628
    2011-May-24 13:54:13
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464629
    2011-May-24 13:54:13
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464630
    2011-May-24 13:54:13
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464631
    2011-May-24 12:53:22
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464632
    2011-May-24 12:53:22
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464633
    2011-May-24 12:53:22
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464634
    2011-May-24 12:53:22
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464635
    2011-May-24 12:53:19
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464636
    2011-May-24 12:53:19
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464637
    2011-May-24 12:53:19
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464638
    2011-May-24 12:53:19
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464639
    2011-May-24 10:56:48
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464640
    2011-May-24 10:56:48
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464641
    2011-May-24 10:56:48
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464642
    2011-May-24 10:56:48
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464643
    2011-May-24 10:56:46
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464644
    2011-May-24 10:56:46
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464645
    2011-May-24 10:56:46
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464646
    2011-May-24 10:56:46
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464647
    2011-May-24 10:35:46
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464648
    2011-May-24 10:35:46
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464649
    2011-May-24 10:35:46
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464650
    2011-May-24 10:35:46
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464651
    2011-May-24 10:35:45
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464652
    2011-May-24 10:35:45
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464653
    2011-May-24 10:35:45
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464654
    2011-May-24 10:35:45
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464655
    2011-May-24 08:52:41
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464656
    2011-May-24 08:52:41
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464657
    2011-May-24 08:52:41
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464658
    2011-May-24 08:52:41
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464659
    2011-May-24 08:52:40
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464660
    2011-May-24 08:52:40
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464661
    2011-May-24 08:52:40
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464662
    2011-May-24 08:52:40
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464663
    2011-May-24 08:04:28
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464664
    2011-May-24 08:04:28
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464665
    2011-May-24 08:04:28
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464666
    2011-May-24 08:04:28
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464667
    2011-May-24 08:04:27
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464668
    2011-May-24 08:04:27
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464669
    2011-May-24 08:04:27
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464670
    2011-May-24 08:04:27
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464671
    2011-May-24 07:38:19
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464672
    2011-May-24 07:38:19
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464673
    2011-May-24 07:38:19
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464674
    2011-May-24 07:38:19
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464675
    2011-May-24 07:38:18
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464676
    2011-May-24 07:38:18
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464677
    2011-May-24 07:38:18
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464678
    2011-May-24 07:38:18
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464679
    2011-May-24 06:50:12
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464680
    2011-May-24 06:50:12
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464681
    2011-May-24 06:50:12
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464682
    2011-May-24 06:50:12
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464683
    2011-May-24 06:50:10
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464684
    2011-May-24 06:50:10
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464685
    2011-May-24 06:50:10
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464686
    2011-May-24 06:50:10
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464687
    2011-May-24 06:14:42
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464688
    2011-May-24 06:14:42
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464689
    2011-May-24 06:14:42
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464690
    2011-May-24 06:14:42
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464691
    2011-May-24 06:14:41
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464692
    2011-May-24 06:14:41
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464693
    2011-May-24 06:14:41
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464694
    2011-May-24 06:14:41
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464695
    2011-May-24 06:00:52
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464696
    2011-May-24 06:00:52
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464697
    2011-May-24 06:00:52
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464698
    2011-May-24 06:00:52
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464699
    2011-May-24 06:00:51
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464700
    2011-May-24 06:00:51
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464701
    2011-May-24 06:00:51
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464702
    2011-May-24 06:00:51
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464703
    2011-May-24 05:48:34
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464704
    2011-May-24 05:48:34
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464705
    2011-May-24 05:48:34
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464706
    2011-May-24 05:48:34
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464707
    2011-May-24 05:48:33
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464708
    2011-May-24 05:48:33
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464709
    2011-May-24 05:48:33
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464710
    2011-May-24 05:48:33
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464711
    2011-May-24 05:47:53
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464712
    2011-May-24 05:47:53
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464713
    2011-May-24 05:47:53
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464714
    2011-May-24 05:47:53
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464715
    2011-May-24 05:47:52
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464716
    2011-May-24 05:47:52
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464717
    2011-May-24 05:47:52
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464718
    2011-May-24 05:47:52
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464719
    2011-May-24 04:31:27
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464720
    2011-May-24 04:31:27
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464721
    2011-May-24 04:31:27
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464722
    2011-May-24 04:31:27
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464723
    2011-May-24 04:31:25
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464724
    2011-May-24 04:31:25
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464725
    2011-May-24 04:31:25
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464726
    2011-May-24 04:31:25
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464727
    2011-May-24 03:24:27
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464728
    2011-May-24 03:24:27
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464729
    2011-May-24 03:24:27
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464730
    2011-May-24 03:24:27
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464731
    2011-May-24 03:24:26
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464732
    2011-May-24 03:24:26
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464733
    2011-May-24 03:24:26
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464734
    2011-May-24 03:24:26
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464735
    2011-May-24 03:16:19
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464736
    2011-May-24 03:16:19
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464737
    2011-May-24 03:16:19
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464738
    2011-May-24 03:16:19
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464739
    2011-May-24 03:16:18
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464740
    2011-May-24 03:16:18
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464741
    2011-May-24 03:16:18
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464742
    2011-May-24 03:16:18
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464743
    2011-May-24 03:11:57
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464744
    2011-May-24 03:11:57
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464745
    2011-May-24 03:11:57
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464746
    2011-May-24 03:11:57
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464747
    2011-May-24 03:11:55
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464748
    2011-May-24 03:11:55
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464749
    2011-May-24 03:11:55
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464750
    2011-May-24 03:11:55
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464751
    2011-May-24 02:52:39
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464752
    2011-May-24 02:52:39
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464753
    2011-May-24 02:52:39
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464754
    2011-May-24 02:52:39
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464755
    2011-May-24 02:52:38
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464756
    2011-May-24 02:52:38
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464757
    2011-May-24 02:52:38
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464758
    2011-May-24 02:52:38
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464759
    2011-May-24 01:29:23
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464760
    2011-May-24 01:29:22
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464761
    2011-May-24 01:29:22
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464762
    2011-May-24 01:29:22
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464763
    2011-May-24 01:29:21
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464764
    2011-May-24 01:29:21
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464765
    2011-May-24 01:29:21
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464766
    2011-May-24 01:29:21
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464767
    2011-May-24 00:41:14
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464768
    2011-May-24 00:41:14
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464769
    2011-May-24 00:41:14
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464770
    2011-May-24 00:41:14
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464771
    2011-May-24 00:41:12
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464772
    2011-May-24 00:41:12
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464773
    2011-May-24 00:41:12
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464774
    2011-May-24 00:41:12
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464775
    2011-May-24 00:14:15
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464776
    2011-May-24 00:14:15
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464777
    2011-May-24 00:14:15
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464778
    2011-May-24 00:14:15
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464779
    2011-May-24 00:14:14
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464780
    2011-May-24 00:14:14
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464781
    2011-May-24 00:14:14
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464782
    2011-May-24 00:14:14
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
    2147464783
    2011-May-24 00:13:57
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
    2147464784
    2011-May-24 00:13:57
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
    2147464785
    2011-May-24 00:13:57
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
    2147464786
    2011-May-24 00:13:57
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
    2147464787
    2011-May-24 00:13:56
    Warning
    %STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
    2147464788
    2011-May-24 00:13:56
    Warning
    %STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
    2147464789
    2011-May-24 00:13:56
    Warning
    %STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
    2147464790
    2011-May-24 00:13:56
    Warning
    %STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking

    The best way to get this resolved is to open a case with the Support Center and reference this thread. We would need to have a look at your configs to determine the issue. One thing that would likely work is for you to assign a different STP priority on each switch for each STP group.You can open a case by calling the following:
    http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
    Ivor

  • Topology change not propagated to interface

    Hi all,
    Had a requirement that called for a topology change (adding a physical schema to existing data server and updating the logical schema to point to this new physical schema). In the end, this change is meant to eliminate the use of LKM. This affects, say 10 interfaces, which are being executed through a package scenario. Now when I regenerate the scenario after making the topology change and re-execute, I see the interfaces still using the LKM. BUT if I go and open the interfaces, make a minor change (e.g. move a datastore around), save and close them back, regenerate the package scenario and execute it, I can see the changes are there and it's not using the LKM. This is obviously tedious if we have to do it for hundreds of interfaces. Given this, is there anyway to propagate the topology change from the back end to all the interfaces? Maybe an update or something on the repository tables? It's bizarre since when I query the interfaces in the SNP_POP table, I see that I_TRT_KLM column is NULL which presumably means it's not using an LKM so I'm not sure why from the front end, we have to open and close the interfaces to see the change come through.
    Any ideas why?
    Thanks

    Hi,
    I believe what each Interface needs is to have the sourceset "recomputed". This is what happens when you open the Interface, click on the mapping tab, then over to the flow tab - which is why, after you save, it works. You should be able to write a Groovy script or Java code using the ODI SDK to handle this in a batch.
    Take a look at the InteractiveInterfaceHelperWithActions class. There is a method to check for dirty sourcesets and another to compute the sourcesets.
    http://docs.oracle.com/cd/E28280_01/apirefs.1111/e17060/index.html?overview-summary.html
    Regards,
    Michael Rainey

  • Changes are not being logged..!! Please help..!!!

    Hello Everybody,
    Do anyone have any idea why the changes in the database are not being logged..?? Any specific reasons behind that..??
    Any help will be greatly appreciated..
    Regards
    Harsh.

    So exactly what do you mean changes in the database not being logged?
    Are you doing insert, delete or updates and they are not being committed?
    Are you droping tables, creating tables, creating users and they are not appearing in the database?
    What do you mean logged? Logged in the audit table (file)?
    Please give more details.
    If they are transactions, make sure they are being committed.
    Regards
    Tim

  • PCL4 - Changes not logged

    Hi,
    I have an issue with PCL4. We have configured change documents to log in to PCL4 cluster. It works fine most of the times but in some cases, changes are not logged in PCL4. (All the tables V_T585A,  V_T585B & V_T585C) Field group used is * which means it should log for any field change. I could see change in infotype tables where as entry is missing in PCL4. Please help.
    Thank You,
    Sarika.

    Hi Sarika,
    What infotypes are you making changes to?
    Regards,
    Li

  • Spanning Tree Topology Changes notifications

    Hello All,
    I've configured RSTP in one of our branch divisions because we decided to add a backup wireless bridge in case one of our fibers gets cut out. Everything is working great , i am getting the desired result, however, i wanted to also syslog the trap msg when a topology change occurs and send it by email. The problem is, i cannot get the root switch to log such an event. 
    The root switch is a Catalyst 6509, i have tried every level of logging possible, to no avail. I know the trap msg is a notice so i have set my logging to informational, but no change.
    I know on c3560's and 3750 i can define to log spanning-tree events, and on my lab setup i do get the trap msgs to my syslog server and email.
    What am i missing?! How can i have my Root switch send me that syslog msg?
    I do appreciate your help
    Thanks in advance!

    Hi Sarbjit-2014 
    Thank you for your response, i dont get any traps msg's at all, doing a sh log on the catalyst will not show me those events.
    Below is the output of my sh log ,for obvious reasons i have masked the logging host
    Syslog logging: enabled (0 messages dropped, 2 messages rate-limited, 0 flushes,
     0 overruns)
        Console logging: level debugging, 608 messages logged
        Monitor logging: level debugging, 23 messages logged
        Buffer logging: level debugging, 608 messages logged
        Exception Logging: size (4096 bytes)
        Count and timestamp logging messages: disabled
        Trap logging: level notifications, 649 message lines logged
            Logging to x.x.x.x, 560 message lines logged
    I also tried to enter the command spanning-tree logging, but it doesnt seem to be available
    Thanks 

  • Upstream switch RSTP Topology changes and AP1210 APs

    We have AP1210's trunked to 3550/3560 access switches which are inturn trunked to two wireless core 4006 switches.
    RSPT is configured on all switches. When a topology change occurs, RPST is very fast in moving the root port (~1 sec) but the designated edge ports (trunk ports) go through the 30 sec 2 x FD STP cycle before going back to forwarding designated ports.
    We do not having spanning tree running on the AP1210s, so no bpdus are sent from the AP and we can't use portfast on the access switch to go straight to forwarding.
    A colleague felt there was a reason you don't turn on STP on the AP. We have 2 VLANs/Bridges on each AP.
    We're looking to speed up spanning tree convergence. Failover testing shows that the 3550 access switch desginated port does not go into forwarding quickly and WL clients lose pings/streaming audio etc during the convergence delay.
    Any inputs welcomed.

    Hi Sarbjit-2014 
    Thank you for your response, i dont get any traps msg's at all, doing a sh log on the catalyst will not show me those events.
    Below is the output of my sh log ,for obvious reasons i have masked the logging host
    Syslog logging: enabled (0 messages dropped, 2 messages rate-limited, 0 flushes,
     0 overruns)
        Console logging: level debugging, 608 messages logged
        Monitor logging: level debugging, 23 messages logged
        Buffer logging: level debugging, 608 messages logged
        Exception Logging: size (4096 bytes)
        Count and timestamp logging messages: disabled
        Trap logging: level notifications, 649 message lines logged
            Logging to x.x.x.x, 560 message lines logged
    I also tried to enter the command spanning-tree logging, but it doesnt seem to be available
    Thanks 

  • Error is not getting logged in error file while running dataload maxl

    Hello All,
    I am running a Maxl to load data in a database which is running fine but noted a weird issue that the errors are not getting logged in error file. Suppose i changed the name of data file then it should give error something like
    ERROR - {Error no.} - Unable to open file {filename} which should be logged in error file but my error file is still empty.
    I am using the Maxl -
    import database {dbname} data from data_file {filename} on error append to "D:/Error/errorfile.err";
    Any inputs please...
    Thanks

    Try to use single quotes and the backslash. It may depend on the operating system and /or the version of essbase used. This is an example from one of my maxls:
    on error append to 'D:\Hyperion\logfiles\myload.err';
    cheers, chris

  • In R12 how to change concurrent output/log file name prefix?

    how to change concurrent output/log file name prefix?

    but i want to change change concurrent output/log file name prefix?You cannot, and I believe it is not supported for all concurrent requests -- Please log a SR to confirm this with Oracle support.
    Thanks,
    Hussein

  • Email address change not showing on ipad after sync

    iTunes email address change not showing on ipad after sync

    So change it.
    Open iTunes, scroll to the bottom of the main page, tap your account name, log out then sign in with the correct name.

  • After updating to 10.10.3, now my Macbook Pro will not stay logged in. I log in after restarting, and it will stay logged in for 3-5 seconds then immediately log off and go back to the login screen. Any help?

    After updating to 10.10.3, now my Macbook Pro 15" (mid-2014) will not stay logged in. I log in after restarting, and it will stay logged in for 3-5 seconds then immediately log off and go back to the login screen. Any help?
    By the way, I also updated my Macbook Pro 17" (mid-2009) and it seems to be running fine, though I haven't tried to restart it and log in. I'm afraid I won't be able to get this one to work either if I do.

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Change documents or logs for Analysis authorisation access changes

    Is there a way to review the change history or table logs in BI 7.0 to show who assigned analysis authorizations and when it was assigned or removed?  I presume there should be a SUIM change document that shows the Analysis authorization access changes that are assigned directly to users via RSU01 or RESEADMIN when these analysis authorizations are not included in roles.
    An example area of concern is with the assignment of 0BI_ALL, having an accurate log or mechanism to track the assignments to users.

    Hi Srinivas,
    you can activate in DDIC that your entry changes will be logged.
    Go to SE11 -> Your Tablenname -> CHANGE
    Button TechnicalSettings -> Activate checkbox Log data changes.
    From now on any chenge will be logged in table DBTABLOG.
    Kind Regards
    Henner

  • ABAP Mapping - Message shown in Standard Change List Process Log

    Hi
    I am working with ABAP Mapping program. I had created ABAP class using ABAP workbench. Before this, in exchangeProfile..data was provided for com.sap.aii.repository.mapping.additionaltypes ==>> as " R3_ABAP|Abap-class;R3_XSLT|XSL (ABAP Engine) " and 'Saved'.
    In Interface Mapping, after providing the Class Name under 'Mapping Program' and activated. After activation (Standard Change List), it is showing the following messages under 'Processing Log'.
    --> Standard Change List - Process Log message
    Activation of the change list canceled Check result for Interface Mapping IM_ABAP_MAPPING | http://ABAP_Mapping_SREE:  Type R3_ABAP of
    program ZSREETEST is invalid because it is not registered in the exchange profile . Check the values for the exchange profile parameter
    IntegrationBuilder.Repository.com.sap.aii.repository.mapping.additionaltypes
    --> End of Log message
    Can some one please guide me in resolving the ABAP mapping issue.
    Thanks in advance.
    ..Sree

    Sree,
    The log says that there is ABAP mapping included in your exchange profile. Do the things what michal have told and also check your mapping program whether working fine or not in SXI_MAPPING transaction.
    You can see this weblog for reference:
    /people/sameer.shadab/blog/2005/09/29/testing-abap-mapping
    ---Satish

  • Lotus Notes password change not working

    Hi,
    I'm integrating Lotus Notus and currently we are able to create users in the Domino server, so we have many doubts:
    Lotus Notes Id Files are created in the Domino server, but this Id Files needs to be copied in the users own laptops or desktop pc's. What is the best way we can give the user the Id File?
    For password changes: I have test password change from OIM self-service, I mean, I create a user, then I provision the user account to Lotus and finally I login with the user account to OIM user self-service interface and try to change password, connector log says everything is ok and the user Id file is correctly modified but, in Domino's server, Lotus internet/http password is not modified, so it is correct? I expect the http/internet password to be changed too. For test purposes I have to copy the new Id file from the Domino server and paste it in the client pc where Lotus Notes client is installed, I put the new password and I'm able to login, but http/internet password is not changed.
    So I don't know if this is a limitation from the connector or if I miss something in order to be able to perform password changes, I have read many times connector documentation but this is not clear for me. I also have read oracle waveset Domino connector documentations but seems to work in a different way OIM do.
    Please help me
    Regards.

    Hi SaikatDas,
    Thank you for posting in MSDN forum.
    Since this forum is to discuss: Visual Studio WPF/SL Designer, Visual Studio Guidance Automation
    Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
    Based on your issue, it is related to the IIS, so I’m afraid that it is not the correct forum for this issue. therefore, I suggest you can post this issue directly to the IIS forum:http://forums.iis.net/
    , maybe you will get better support.
    Thanks for your understanding.
    Best Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Change the database log on parameters in the run time with CR10 Delphi2007?

    Hi,
    I'm using crystal report 10 and Crystal VCL for Delphi. How can I change the database log on parameters in the run time?

    You have to use the ConnectBuffer. See [this|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do] note for details.
    Also, consider searching the notes database:
    https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_ossnotes&query=&adv=true
    The search; VCL database crystal, returns a number of notes that may be of use.
    Ludek

Maybe you are looking for