Netflow is not supported on sup6E. It is supported on 7-E and 7L-E. with the help of netflow daughter cards we can enable netflow on supIV and supV, however daughter card is not applicable to sup6E. Regards, Somu Jayaraman ... View more

Version 5 netflow uses a default fixed record-fields. Remove the flow monitors from all the interfaces (config)# flow monitor test (config-flow-monitor)# no  record test (config-flow-monitor)# default record (config)# no flow record test Put back the flow monitors on all the interfaces and you should start seeing data on collector, please do this and let me know how it goes. ... View more

Good one Aninda!, Just to add few more things, we can have point to multipoint configurations as well, using the frame-relay ip statements. Some useful show commands, show frame-relay route, show frame-relay pvc <> show frame-relay lmi And LMI packets would be of this format, Cheers, Somu ... View more

Hi, You can check the mac-address using the ip address. ++ Go to the switch where the interface vlan is created for this vlan. ++ Issue show ip arp , it should show the ip to mac bindings. Hope this helps. Cheers Somu Rate helpful posts ... View more

Hi, Yes, the switch will still receive those BPDUs. Native vlan will still be in use eventhough we remove it from the allowed list. Cheers Somu ... View more

Hi, ++ Native vlan no can be changed but it cannot be blocked. For testing purpose i created this setup: ============================= sw1--fa0/19-----fa0/19--sw3 SW1 configs: ========= switch1#sh run inter fa 0/19 Building configuration... Current configuration : 175 bytes ! interface FastEthernet0/19 switchport trunk encapsulation dot1q switchport trunk native vlan 3 switchport trunk allowed vlan 1,99 switchport mode dynamic desirable end switch1#sh int fa 0/19 trunk Port        Mode             Encapsulation  Status        Native vlan Fa0/19      desirable        802.1q         trunking      3 Port        Vlans allowed on trunk Fa0/19      1,99 Port        Vlans allowed and active in management domain Fa0/19      1 Port        Vlans in spanning tree forwarding state and not pruned Fa0/19      1 switch1#sh int fa 0/19 sw Name: Fa0/19 Switchport: Enabled Administrative Mode: dynamic desirable Operational Mode: trunk Administrative Trunking Encapsulation: dot1q Operational Trunking Encapsulation: dot1q Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 3 (VLAN0003) Administrative Native VLAN tagging: enabled Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk Native VLAN tagging: enabled Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk associations: none Administrative private-vlan trunk mappings: none Operational private-vlan: none Trunking VLANs Enabled: 1,99 Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Protected: false Unknown unicast blocked: disabled Unknown multicast blocked: disabled Appliance trust: none SW2 configs: ========= switch3#sh run int fa 0/19 Building configuration... Current configuration : 164 bytes ! interface FastEthernet0/19 switchport trunk encapsulation dot1q switchport trunk native vlan 3 switchport trunk allowed vlan 1,999 switchport mode trunk end switch3#sh run int fa 0/19 trunk                            ^ % Invalid input detected at '^' marker. switch3#sh int fa 0/19 trunk Port        Mode             Encapsulation  Status        Native vlan Fa0/19      on               802.1q         trunking      3 Port        Vlans allowed on trunk Fa0/19      1,999 Port        Vlans allowed and active in management domain Fa0/19      1,999 Port        Vlans in spanning tree forwarding state and not pruned Fa0/19      1,999 switch3#sh int fa 0/19 sw Name: Fa0/19 Switchport: Enabled Administrative Mode: trunk Operational Mode: trunk Administrative Trunking Encapsulation: dot1q Operational Trunking Encapsulation: dot1q Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 3 (VLAN0003) Administrative Native VLAN tagging: enabled Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk Native VLAN tagging: enabled Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk associations: none Administrative private-vlan trunk mappings: none Operational private-vlan: none Trunking VLANs Enabled: 1,999 Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Protected: false Unknown unicast blocked: disabled Unknown multicast blocked: disabled Appliance trust: none ++ for testing purpose i have created interface vlan 3 on both sides and the pings went through fine. switch1#sh run inter vlan 3 Building configuration... Current configuration : 58 bytes ! interface Vlan3 ip address 10.1.1.2 255.255.255.0 end switch1# switch3#sh run inter vlan 3 Building configuration... Current configuration : 58 bytes ! interface Vlan3 ip address 10.1.1.1 255.255.255.0 end switch3#ping 10.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms switch3# ++ Eventhough you disallow this vlan, the native vlan wont be blocked since it carries all the control traffic. And without this native vlan stp, cdp, wont work. Regarding your third question, ++ There is no real value as such in changing the vlan numbers unless you use vlan 1 to carry data traffic. In that case you will mention a different vlan no as native vlan. ++ If the native vlan is not the same on both ends then you will see a native vlan mismatch error and referred as "vlan leaking" Hope this answers your question. Cheers Somu Rate helpful posts ... View more

Hi, could you pls try the below steps, rommon> priv rommon>dev  >>> the output of this command will show you the list of file systems present Based on that you can try accessing the memory device. if the internal memory device is not accessible, then try booting the device from an external flash. dir disk0: useful commands: ============= rommon> sync  >> used to save the configs rommon> BOOT=  >> clearing the present boot variable. rommon> BOOT= setting the boot variable rommon>set  >> output of this command will list you the present boot variable configured, configuration register etc. Dont forget to do a sync after configuring the boot variable & configuration register. You can try xmodem recovery in the rommon as well. Cheers Somu Rate helpful posts ... View more

Hi, Have you checked the cpu utilization at that time? Also if required enable port security & configure vtp pruning so that unwanted traffic flow can be avoided. ++ enable portfast with bpdu guard globally so that the removal of end device wont affect the entire vlan's mac to get flushed out. conf t spanning-tree port-fast default spanning-tree bpduguard default Hope this helps. Cheers Somu Rate helpful posts ... View more