3750 --ISL-- 1912 problem

When port on 3750 is in access mode (vlan 24), and port on 1912 is trunk off, everything is ok. But now I need to communicate the devices via ISL trunk. I had configured both machines by the appropriate tech docs, but i have troubles...
On 1912 machine:
ip address 10.195.60.2 255.255.255.0
ip default-gateway 10.195.60.1
interface FastEthernet 0/26
duplex full
trunk On
On 3750 machine:
interface GigabitEthernet2/0/20
description Trunk to Cisco 1912
switchport encapsulation isl
switchport mode trunk
no mdix auto
interface Vlan24
ip address 10.195.60.1 255.255.255.0
In this way configuration (trunking), there is no ping between them.
May be i do something wron? PLS HELP!

Hm... now i had configured `Meri` on both devices. But still the same problem. May be trouble in the difference of VTP versions?
Statistics:
3750s#show vtp counters
VTP statistics:
Summary advertisements received : 0
Subset advertisements received : 0
Request advertisements received : 46507
Summary advertisements transmitted : 147343
Subset advertisements transmitted : 46516
Request advertisements transmitted : 0
Number of config revision errors : 0
Number of config digest errors : 0
Number of V1 summary errors : 0
VTP pruning statistics:
Trunk Join Transmitted Join Received Summary advts received from
non-pruning-capable device
Gi1/0/1 0 0 0
Gi1/0/2 0 0 0
Gi1/0/4 0 0 0
Gi1/0/8 0 0 0
Gi1/0/12 0 0 0
Gi2/0/5 0 0 0
Gi2/0/8 0 0 0
Gi2/0/15 0 0 0
Gi2/0/19 0 0 0
Gi2/0/20 0 0 0
Catalyst_1912#show vtp statistics
Receive Statistics Transmit Statistics
Summary Adverts 4 Summary Adverts 5
Subset Adverts 0 Subset Adverts 4
Advert Requests 0 Advert Requests 50
Configuration Errors:
Revision Errors 0
Digest Errors 0
VTP Pruning Statistics:
Port Join Received Join Transmitted Summary Adverts received
with no pruning support
A 0 0 0
B 0 0 0

Similar Messages

  • Dividing ISL trunk problem

    I have a network design issue to solve and need some help. Current network uses ISL to trunk vlans between two sites. Some encryption devices need to be installed that do not understand ISL (or BPDUs for that matter). I need to split the ISL, or tunnel it, so that the inside devices cannot see the L2 stuff but the end devices can still communicate. Any ideas?
    Regards ... John

    Hi Josh
    I had to solve a very similar problem to yours, and the solution I came up with was to use L2TPv3 (layer 2 tunnelling protocol) over IPSEC. I used the same device (a pair of old 1700 series routers at each end) to create both the L2 tunnel and the IPSEC tunnel, but in your case you are using a separate device to do the encryption. You just need to create the L2 tunnel between 2 devices which are on the unencrypted side at each end. You need to ensure that the 2 devices can route to each other.

  • 6500 - 3750 rx oversizedpkts problems

    We have 2 3750 stacks connected to 2 6500 switches.
    One stach is connected to a 6513 switch and has no problems.
    The other stach is connected to a 6506 switch and on the truk ports we get a lot of rxoversizedpkts on the 6506.
    We don't use jumbosize and MTU size is equal.
    What is it we doing wrong?

    What version of code u r running :
    Here is the exp:
    Release Notes
    A Catalyst 6500 may increment giants on 67xx cards for ports that are trunking.
    This does not affect the performance of the switch, and is purely cosmetic.
    Fixed in Version: 8.6(0.21)TAL, 8.4(0.61)RCC03, 8.5(0.5)JAC, 12.2(17d)SXB11
    Found in 12.2(18)SXD
    HTH,
    -amit singh

  • ISL Port problems on 9513

    Hi, I have two shiny new MDS9513 directors which i am trying to link with two ISL's. The problem i am having is that the ports on both switches stay in a state of 'initializing' although the port light is green. My HDS USPV disk ports come up fine as do the host ports. Trunking is set to on. Anyone any ideas?

    VSANs require that both switches have the VSAN defined on
    them in order for them to access each other across the ISL. In
    other words, if Cisco switch A has 10 N_Ports in VSAN 1000, and
    Cisco switch B has 10 N_Ports in VSAN 1 (default), these N_Ports
    will not be able to access each other until the N_Ports in VSAN 1
    are moved into VSAN 1000, or vice versa, or some flavor of IVR is
    used.

  • WLC 5508 / 3750 Switch LAG Problems

    Hello Forum,
    for presenting to the client (customer wants to buy any Cisco) I have built up in our laboratory a WLAN environment.
    The structure is composed of: - WLC5508 HA cluster (7.6.110.0) - Some AP2602i - C3750E (12.2 (55) SE3)
    Which reminds me strange behavior with LAG noticed that I can not explain?
    The ports of the WLCs are in the LAG mode each WLC are connected with two cables at the switch. On the switch a port-channel are configured (no LACP = channel-group 8 mode on).
    Failure scenario:
    Deducted on the primary controller the cable from port 1 (it goes down), the port LED turns from green to orange >>>> no impact on the system, everything remains as it is and the system continues to operate. Deducted on the primary controller the cable from port 2 (goes down), the port LED remains green. HA >>>> the backup controller takes over? Primary controller boots?
    That can not be true that here changes the system to the redundant WLC. The system should, as yet just keep working at switch-switch LAG?
    Is this a configuration error or a BUG? Upon request, I can gladly send the WLC and Switch configuration.
    Best Regards, Alexander Weitzel 

    The HA kicks in when the primary looses gateway, do a small test, keep a continuous ping to WLC  from its gateway as source and break one of the link in the LAG and see if you drop any packet ?

  • 3550 - 3750 problem. Fiber type or configuration?

    I'm having trouble with a link that was working with a 3600 as an end device, but won't work when replaced with a stack of 3750 switches. A couple of co-workers in our group has looked at it, but can't find anything obvious.
    The path is from a 6500 on multimode trunked fiber to a converter to single mode fiber, (then under the street) to a 3550 Long Haul Gbic. Then we took copper from the 3550 to a 3660 10/half(?). To this point it used to work. We pulled the 3600 and put in a 3750 stack, and configured the copper port on the 3550 to 100/full, and the same on the 3750. The problem is that we can go to the middle device and then ping and telnet both ways from there. But we cannot go from the 6513 through the 3550 to the 3750. I turned debug icmp on the 3550, and it's not seeing anything from the 3750 when I try to go to the gateway.
    Both swiches have the default gateway pointing back to the HSRP Vlan VIP of the 6513. CDP is seeing its neighbors. All interfaces seem to be up/up. Here are the snippets of configs for all ports. Maybe someone can see something I'm missing? The only thing I can think could be a mismatch somewhere between the switches, or the multimode to single mode fiber is not translating.
    6513:
    interface GigabitEthernet1/23
    description To Building E
    no ip address
    udld port aggressive
    switchport
    switchport trunk encapsulation dot1q
    3550 from 6500
    interface GigabitEthernet0/1
    switchport mode dynamic desirable
    3550 out to 3750:
    interface FastEthernet0/1
    switchport trunk encapsulation dot1q
    switchport mode trunk
    speed 100
    duplex full
    3750 stack:
    interface FastEthernet5/0/1
    switchport trunk encapsulation dot1q
    switchport mode trunk
    duplex full
    speed 100
    Any direction would be most appreciated.
    Thanks,
    Jim

    I can't say the configuration is eithre good or not as it does not really show a lot. As far as L2 configuration they seem okay as all the ports are configured for trunking, however, the trunk port between 3550 and 3750 looks like the are "forced" to turnk with the mode trunk. are the vlans in forwarding mode in both sides (show int trunk). What happens when the port between 3550 and 3750 are in desirable mode, does it build the trunk? More important questions is what ip address are you pinging on the 3750? What vlan should it belong to?
    Maybe you can post the following:
    1. ping from 6513 to the 3550.
    2. ping from 6513 to the 3750.
    I want to keep it short so might have some question after seeing the above outputs.

  • 3750-E - hardware not supported by firmware

    Hello, I have got new 3750 e-series which has universal image installed on it. I need to put this switch in stackwise with non-e-series 3750. The problem is that non-e-series are running IP BASE IOS and I wanted to put the same IOS on 3750 e-series. But it gives me the following message when I try to boot the switch with c3750-ipbase-mz.122-35.SE5.bin image.
    Error: hardware not supported by firmware.
           Try loading newer software instead.
           System Resetting...
    Thank you!

    Hello, I have got new 3750
    e-series which has universal image installed on it. I need to put this
    switch in stackwise with non-e-series 3750. The problem is that
    non-e-series are running IP BASE IOS and I wanted to put the same IOS
    on 3750 e-series. But it gives me the following message when I try to
    boot the switch with c3750-ipbase-mz.122-35.SE5.bin image.
    Error: hardware not supported by firmware.
           Try loading newer software instead.
           System Resetting...
    Thank you!
    Hi,
    Catalyst 3750-E switches running Cisco IOS Release 12.2(35)SE2 are compatible with Catalyst*3750 switches and Cisco EtherSwitch service modules running Cisco IOS Release*12.2(35)SE. Catalyst 3750-E switches, Catalyst 3750 switches, and Cisco EtherSwitch service modules can be in the same switch stack. In this switch stack, we recommend that the Catalyst*3750-E switch be the stack master.
    Check out the below link for more information
    http://www.cisco.com/en/US/docs/switches/lan/catalyst3750e_3560e/software/release/12.2_35_se2/release/notes/OL9778.html
    Hope to Help !!
    Ganesh.H
    Remember to rate the helpful post

  • Arp Incomplete in BGP

    Hello,
    I have a BGP session established IPv4 and IPv6, with 2 ISP, and I have session established with PTT also.
    My router is a Cisco 7206VXR. Since the last week I'm haveing problem with a "ARP Incomplete" in the BGP session established with the PTT.
    To troubleshooting, replacing my Cisco 7206VXR to a Cisco 1800. The problem persisted!
    Replaced again by a Cisco Catalyst 3750 and the problem solved. But I need rollback to the Cisco 7206VXR.
    I don't have configuration for arp rate limit or arp inspection.
    Anyone have any idea about this problem?
    Tks
    Cesar

    Hi Cesar,
    can you elaborate on '"ARP Incomplete" in the BGP session established with the PTT.' ?
    Do you mean that the BGP session was Idle and when you checked 'show ip bgp neighbor x.x.x.x' you saw "ARP incomplete" as the cause of the problem, or you simply checked the ARP table and saw that the remote IP was incomplete?
    Generally speaking ARP incomplete indicate underlying connectivity issues, but I find weird that the issue is solved by replacing your router (2 times). Personally I think that it is just a coincidence that with the Cat3750 you don't see the problem.
    What you need to do is to connect the 7206 back and troubleshoot ARP related issue to see if the router correctly receives and sends ARP packets.
    Also I would check if some kind of CoPP was configured to rate limit the arp traffic. That could cause similar issues if your router receives tons of ARP packets and drop some due to CoPP.
    Riccardo

  • Communication problem between ASA 5510 and Cisco 3750, L2 Decode drops

    Having problem with communication between ASA 5510 an Cisco Catalyst 3750.
    Here is the Cisco switch port facing the ASA 5510 configuration:
    interface FastEthernet2/0/6
    description Trunk to ASA 5510
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 50
    switchport trunk allowed vlan 131,500
    switchport mode trunk
    switchport nonegotiate
    And here is the ASA 5510 port configuration:
    interface Ethernet0/3
    speed 100
    no nameif
    no security-level
    no ip address
    interface Ethernet0/3.500
    vlan 500
    nameif outside
    security-level 0
    ip address X.X.X.69 255.255.255.0
    There is a default route on ASA to X.X.X.1.
    When I try to ping from ASA X.X.X.1 i get:
    Sending 5, 100-byte ICMP Echos to 31.24.36.1, timeout is 2 seconds:
    Also in the output of show interface eth 0/3 on the ASA i can see that the L2 Decode drop counter increases.
    I have also changed the ports on the Switch and ASA but the same error stays.
    Any thoughts?

    I don't see anything wrong with your trunk configuration; I have a similar one working between an ASA 5520 and a Catalyst 3750G.
    Maybe you should adjust the "speed 100"?  In my experience, partial autoconfiguration results in duplex mis-matches, which results in dropped packets.
    I'd try removing the "speed 100" and letting the ASA port autonegotiate with the switch.  Alternatively, have both sides set
       speed 100
       duplex full
    and see if things improve.
    -- Jim Leinweber, WI State Lab of Hygiene

  • QOS problem (multicast) with 3750

    Hi,
    I need help to solve following problem.
    I have setup qos in our 3750, see below.
    Unicast traffic is handle correct, However with multicast streams the router set the dscp to 0
    Has somebody any idea what is missing?
    Too old sw?   Cisco IOS Software, C3750 Software (C3750-ADVIPSERVICESK9-M), Version 12.2(35)SE,
    Regards Niklas
    ip multicast-routing distributed
    ip multicast multipath
    mls qos srr-queue input priority-queue 1 bandwidth 10
    mls qos srr-queue input dscp-map queue 1 threshold 1  46
    mls qos srr-queue input dscp-map queue 2 threshold 1  11 24 30 48
    mls qos srr-queue output dscp-map queue 1 threshold 1  48
    mls qos srr-queue output dscp-map queue 2 threshold 1  46
    mls qos srr-queue output dscp-map queue 3 threshold 1  40
    mls qos srr-queue output dscp-map queue 4 threshold 1  11 24 30
    mls qos
    interface GigabitEthernet1/0/22
    switchport access vlan 41
    switchport mode access
    load-interval 30
    srr-queue bandwidth share 25 25 25 20
    priority-queue out
    mls qos trust dscp
    interface GigabitEthernet1/0/23
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 40
    switchport mode trunk
    load-interval 30
    srr-queue bandwidth share 25 25 25 20
    priority-queue out
    mls qos trust dscp

    Hi,
    Here comes the printouts:
    with mls qos enabled:
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/22 statistics
    GigabitEthernet1/0/22
      dscp: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :     8881981            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0          307            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :     8881981            0            0            0            0 
      5 -  7 :           0          307            0 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/23 statistics
    GigabitEthernet1/0/23
      dscp: incoming 
      0 -  4 :     8931330            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0          202            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0         1206            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :    11357772            0            0            0            0 
      5 -  7 :           0            2            0 
      cos: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0         1206            2 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#
    mls qos disabled:
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/22 statistics
    GigabitEthernet1/0/22
      dscp: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0         7371            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :        7371            0            0            0            0 
      5 -  7 :           0            0            0 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/23 statistics
    GigabitEthernet1/0/23
      dscp: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0        23281            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            2            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :       29272            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0            2            0 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#
    BR Niklas

  • Catalyst (3750 24 10/100/1000T) and (3750 12 SFP) Stacking Problems

    Dear all
    I'm having a very strange situation here (at least for me)
    we have 4 core switches
    2 x   WS-C3750G-24T-S Catalyst 3750 24 10/100/1000T + IPB Image
    and
    2 x   WS-C3750G-12S-S Catalyst 3750 12 SFP + IPB Image
    Stack configuration is done this way
    when the switches are powered on, the first two SFP core switches are seen as a single stack with the stack master LED turned green on the first switch
    the other two (24 10/100/1000T) switches have the RPS LEDs always green, mode cannot be changed, and cannot be accessed by Console connection
    but when the (24 10/100/1000T) are powered off, the first (SFP) switch in the stack reports that " Switch 3 and 4 has been removed from Stack "
    which means they are stacked but there's something wrong, because
    only the SFP ports are shown in the " Show interfaces status " , the ethernet ports of the bottom switches are not present !!!
    can you please tell me what's the poblem ?

    Dear Daniel
    Sorry for my delayed response but i was actually quite busy
    but the problem was actually in another sense
    the default profile for the Catalyst 3750 SFP is the Aggregate SDM Template
    while the 3750 10/100/1000 ethernet Switch Default SDM profile was Desktop profile
    so i had an SDM mismatch
    DATACENTER#sh switch detail
    Switch/Stack Mac Address : 081f.f3cf.1c80
                                               H/W   Current
    Switch#  Role   Mac Address     Priority Version  State
    *1       Master 081f.f3cf.1c80     1      0       Ready              
    2       Member 081f.f3cf.5900     1      0       Ready              
    3       Member aca0.16ac.0180     1      2       SDM Mismatch       
    4       Member aca0.16a3.bc80     1      2       SDM Mismatch 
             Stack Port Status             Neighbors    
    Switch#  Port 1     Port 2           Port 1   Port 2
      1        Ok         Ok                2        4
      2        Ok         Ok                3        1
      3        Ok         Ok                4        2
      4        Ok         Ok                1        3 
    all i did was changing the default profile of the SFP switches into the Desktop Profile and problem was solved
    switch 1 provision ws-c3750g-12s
    switch 2 provision ws-c3750g-12s
    switch 3 provision ws-c3750g-24t
    switch 4 provision ws-c3750g-24t
    system mtu routing 1500
    ip subnet-zero
    no file verify auto
    spanning-tree mode pvst
    spanning-tree extend system-id
    vlan internal allocation policy ascending
    interface GigabitEthernet1/0/1
    interface GigabitEthernet1/0/2
    interface GigabitEthernet1/0/3
    interface GigabitEthernet1/0/4
    interface GigabitEthernet1/0/5
    interface GigabitEthernet1/0/6
    interface GigabitEthernet1/0/7
    interface GigabitEthernet1/0/8
    interface GigabitEthernet1/0/9
    interface GigabitEthernet1/0/10
    interface GigabitEthernet1/0/11
    interface GigabitEthernet1/0/12
    interface GigabitEthernet2/0/1
    interface GigabitEthernet2/0/2
    interface GigabitEthernet2/0/3
    switchport trunk encapsulation dot1q
    switchport mode trunk
    interface GigabitEthernet2/0/4
    interface GigabitEthernet2/0/5
    interface GigabitEthernet2/0/6
    interface GigabitEthernet2/0/7
    interface GigabitEthernet2/0/8
    interface GigabitEthernet2/0/9
    interface GigabitEthernet2/0/10
    interface GigabitEthernet2/0/11
    interface GigabitEthernet2/0/12
    interface GigabitEthernet3/0/1
    interface GigabitEthernet3/0/2
    interface GigabitEthernet3/0/3
    interface GigabitEthernet3/0/4
    interface GigabitEthernet3/0/5
    interface GigabitEthernet3/0/6
    interface GigabitEthernet3/0/7
    interface GigabitEthernet3/0/8
    interface GigabitEthernet3/0/9
    interface GigabitEthernet3/0/10
    interface GigabitEthernet3/0/11
    interface GigabitEthernet3/0/12
    interface GigabitEthernet3/0/13
    interface GigabitEthernet3/0/14
    interface GigabitEthernet3/0/15
    interface GigabitEthernet3/0/16
    interface GigabitEthernet3/0/17
    interface GigabitEthernet3/0/18
    interface GigabitEthernet3/0/19
    interface GigabitEthernet3/0/20
    interface GigabitEthernet3/0/21
    interface GigabitEthernet3/0/22
    interface GigabitEthernet3/0/23
    interface GigabitEthernet3/0/24
    interface GigabitEthernet4/0/1
    interface GigabitEthernet4/0/2
    interface GigabitEthernet4/0/3
    interface GigabitEthernet4/0/4
    interface GigabitEthernet4/0/5
    interface GigabitEthernet4/0/6
    interface GigabitEthernet4/0/7
    interface GigabitEthernet4/0/8
    interface GigabitEthernet4/0/9
    interface GigabitEthernet4/0/10
    interface GigabitEthernet4/0/11
    interface GigabitEthernet4/0/12
    interface GigabitEthernet4/0/13
    interface GigabitEthernet4/0/14
    interface GigabitEthernet4/0/15
    interface GigabitEthernet4/0/16
    interface GigabitEthernet4/0/17
    interface GigabitEthernet4/0/18
    interface GigabitEthernet4/0/19
    interface GigabitEthernet4/0/20
    interface GigabitEthernet4/0/21
    interface GigabitEthernet4/0/22
    interface GigabitEthernet4/0/23
    interface GigabitEthernet4/0/24
    that's it !
    : D
    cheers

  • 3750 as a router and a switch. sub-optimal routing problem

    Objective: To limit the traffic on Vlan8. We are seeing traces from K1 or T1 to 192.168.1.4 like this:
    1- 10.10.10.5
    2- 10.10.20.1
    3- 192.168.1.4
    then
    1- 10.10.10.4
    2- 10.10.30.1
    3- 192.168.1.4
    or
    1- 10.10.10.5
    2- 10.10.200.1
    3- 192.168.1.4
    this causes the packets to travers vlan8 once to get routed by P61B then switched back across to reach the next hop 20.1 or vice versa.
    How can we avoid this behavior?
    Study the attached drawing carefully. Vlan 8 has 4 routers on it and the 3750s have routes to the 4 networks above them. packets are not routed between the 3750's

    Hello Todd,
    Could set up a debug ip icmp on the router 192.168.1.4 and ping it from both T-1 and K-1, I think this problem would be more clear to everyone.
    If not mabybe you could provide the output of "show ip route" on the routes on this issue,at least on the routers/switch 192.168.1.2 , 192.168.1.3 and 10.10.10.4 and 10.10.10.5 and T-1, K-1.
    for routes like 192.168.1.4, 10.10.10.2-5 and 20.20.20.2-3
    Hope thats not to much info.
    Thanks,
    Vlad

  • Problem in 3750 with multiple IP segment in same VLAN

    Hi,
    I've problems in 3750 and would like to ask for help.
    I've 3750 switch with standard image. Because of lacking IP addresses, I'm going to redesign the IP scheme. Before complete migrate to new IP range, I've to let new IP segment co-exist with old IP segment for a while (I've 3 VLANs that have same situation). For example, 10.10.13.0/24 (old) will co-exist with 10.10.32.0/21 (new) in same VLAN (let say VLAN 32).
    Below is the partial configuration in 3750:
    interface VLAN 32
    ip address 10.10.13.2 255.255.255.0 secondary
    ip address 10.10.32.2 255.255.248.0
    standby 14 ip 10.10.13.3
    standby 40 ip 10.10.32.3
    I've two PCs. PC-A is 10.10.13.250 and PC-B is 10.10.33.250, both are using HSRP IP as default gateway (the subnet mask are correct).
    My problem is:
    Two PCs can not ping to each other. I can not ping to both PCs from 3750. But if I'm using physical IP as their gateway (such as 10.2.13.2 for PC-A and 10.2.32.2 for PC-B), then both PCs can be ping each others.
    How can I solve the problems if I've to use HSRP IP as default gateway?

    I don't get it. What is the significance of standby 1 and 2 VS standby 14 and 40? The only difference I noticed is the lower number of standby group goes with primry and higher goes with secondary.
    If possible, can you also try the same config you used before except swapping the group number?
    e.g.
    interface VLAN 32
    ip address 10.10.13.2 255.255.255.0 secondary
    ip address 10.10.32.2 255.255.248.0
    standby 40 ip 10.10.13.3
    standby 14 ip 10.10.32.3

  • Vivitar 3750 problems

    I have a Vivitar Vivicam 3759 digital camera, it seems the only problem is that the down button on the controller on the back doesn’t seem to work. That and it doesn’t have the instructions or a memory card. It's been a long time since I've had a digital camera.
    I’m not sure what kind of memory card it will take or were to pick up the instructions on how to work it since the official site doesn’t have the model listed.
    It was free so I shouldn’t complain to loudly.

    Hi ClockworkKnight,
    I am not aware of a Vivitar Vivicam camera model 3759, but they did manufacture a Vivicam model 3750 and 3760. Both of these two models take Secure Digital (SD) memory cards, and if you need the manual for this camera I would suggest contacting the manufacturer at 1-800-592-9541. You could also try looking for a PDF Download on the internet by doing a search of the camera model, and user manual download.
    With that being said I have to say that digital cameras have come a long way since these two model cameras, and even the lowest end camera model today will far out perform either one of these models. If you want to take a look at our selection of Point-and-Shoot cameras you could look here.
    Thanks for posting,
    Allan|Senior Social Media Specialist | Best Buy® Corporate
     Private Message

  • MDS9513 Add ISL to Port Channel problem.

    Hi Experts,
    I have a problem when add a new ISL to an existing Port Channel config.
    The ISL port is up state and correctly configured like another ports in port channel.
    Looks bellow the error:
    MDS1300M6A# show port-channel summary
    Interface                 Total Ports        Oper Ports        First Oper Port
    port-channel 1                 4                 4                  fc12/48
    port-channel 2                 2                 2                  fc6/47
    MDS1300M6A# show port-channel database
    port-channel 1
        Administrative channel mode is active
        Operational channel mode is active
        Last membership update failed: port not compatible [Resources Unavailable]
        First operational port is fc12/48
        4 ports in total, 4 ports up
        Ports:   fc12/48  [up] *
                 fc10/48  [up]
                 fc11/48  [up]
                 fc9/48   [up]
    Anyone seen this?
    Tks
    Wellington

    That did the trick - specifically setting the port channel to rate-mode shared.  Certainly solved the problem as far as getting all the deisred ports up in the channel, but where I still have a knowledge gap is the operational difference between dedicated and shared.  Are there any Cisco docs (beyond the command reference guide to toggle the feature) that explains why you'd choose one versus the other, and what it means from a design perspective?
    On a different note, while I'm no expert, here's some background to consider for others who may encounter the same issue (whether on UCS or a Nexus 5K).  I  (and our network team) come from an IOS background, so while the IOS "parts" of NX-OS are pretty familiar, the SAN "parts" of NX-OS are a little new.  We're also more CLI oriented, and while not impossible to configure via CLI, in our environment, the GUI for UCS seems to be more popular across the board - and we're still learning that piece as well.
    Our storage team is very familiar with SAN-OS, so they're very comfortable with the SAN "parts" of NX-OS.  But, they're very used to configuring the MDS switches via the GUI, which is what got us off track a bit.  In our scenario, creating a SAN port channel on the MDS via the GUI didn't give us the option for setting "switchport rate-mode shared"  Not saying it's not there in the GUI, but we certainly couldn't find it.
    Long story short, if the configuration of the SAN port channel on the MDS is in question, check it via the CLI and make any necessary changes there as a quick workaroud.

Maybe you are looking for

  • Vid card works with adapter, not directly

    I have two monitors available: an old CRT that has VGA connector, and a new Dell E228WFP 22" LCD that has both VGA and DVI connector. My card is ATI Radeon 9000 Pro (DVI and ADC ports). The Dell has worked perfectly for almost a year. The problem beg

  • Cannot finally close a PO line

    Using version 12.1.3 Cannot finally close a PO line. I get the following error message when I open an purchase order summary form --> select the PO line to close --> click on Tools -> Control -> finally close: "You cannot finally close this line beca

  • Watermark will not display behind the page?

    I have been trying to set the watermark behind the page rather than on top. When set to display behind the page no watermark displays in any setting or page range. Very frustrating has any one else experienced this and if so how did you resolve the i

  • DAB Radio adapters

    has anyone bought one of these? i've found a couple, and have thought about buying one but was wondering if anyone has had any experience of them. http://www.amazon.co.uk/Roberts-Radio-Robi-POD1-Digital/dp/B000WZHJC0/ref=sr17?ie=UTF8&s=electronics&qi

  • Spool File not complete when spool recipient recieves email

    Hi, This is my Issue... We scheduled one of the Std SAP report (RLS10020/LX02). When defining the job, we have also specified a spool recipient and once the job was completed, the recipient got the spool as a html file. The spool actually had 15000 l