Forum Discussion

Soap_111722's avatar
Soap_111722
Icon for Nimbostratus rankNimbostratus
Jan 29, 2015

Unable to ping B2250 blades

I have 2 viprion chassis and each have a B2250 blade. If I SSH to one of the blades I am unable to ping the other on the mgmt network or the peernet network self ip's. I created a self IP for another public subnet and I can ping that without any issues. I can also ping anything on our network without any issues. I just can't ping each blade from the other one. I have triple checked everything and can't seem to figure out why I can't ping. Any ideas?

vPC config

interface port-channel160
description F5-VIPRION
switchport mode trunk
switchport trunk allowed vlan 40,42,53-54,550,552,554,701,4092
spanning-tree port type edge trunk
spanning-tree guard root
vpc 160

TRUNK and VLAN's are setup correctly on the devices. 4092 = peernet

design

5 Replies

Sort By
  • Soap_111722's avatar
    Soap_111722
    Icon for Nimbostratus rankNimbostratus
    Jan 30, 2015
    The mgmt network which is on a separate 1GB port it's not part of the vPC trunk. Could that be causing my issues?
  • The_Bhattman's avatar
    The_Bhattman
    Icon for Nimbostratus rankNimbostratus
    Feb 02, 2015

    Have you tried tcpdump to validate the ICMP echo and reply are responding to interfaces you expect them to?

     

  • StephanManthey's avatar
    StephanManthey
    Icon for MVP rankMVP
    Feb 02, 2015

    Hi Soap,

     

    in a VIPRION you will assign a so called cluster IP address (hold by the current cluster master blade) and blade specific management IP addresses.

     

    It will be necessary, to connect each blades management interface to the management network. Traffic on the dedicated management interface will not be bridged internally.

     

    It´s best practice, to reserve management IP addresses for all slots in chassis (and already assign them) even the slots are still empty.

     

    Different story for TMOS interfaces (production or however you want to call it). Your aggregated link connects to all blades in the chassis and each blade is accepting traffic and selecting an internal TMM instance (perhaps on another blade) to handle it.

     

    Thanks, Stephan

     

  • Soap_111722's avatar
    Soap_111722
    Icon for Nimbostratus rankNimbostratus
    Feb 02, 2015

    I do have a cluster IP set, and each blade (only 1 blade per chassis currently) has a management IP set. Both the cluster IP and management IP are on the same subnet. I am reading over your comment about the dedicated management interface not being bridged internally and am trying to understand what and where I need to make changes. I have one external trunk configured but the only VLAN's I have defined are for the 'peernet' and another internal subnet. Still struggling to understand why I cannot ping the blades management IP's from each other.

     

  • StephanManthey's avatar
    StephanManthey
    Icon for MVP rankMVP
    Feb 02, 2015

    Hi Soap,

     

    your trunks can not forward traffic to the management interfaces of your blades.

     

    And the blades management IP addresses can be reached through the management interfaces only.

     

    That´s why it is important, to have a wired connection from each inserted blade to your management network switch.

     

    There is no internal loop or switch for the network management interface. No worries about spanning tree on these links.

     

    Thanks, Stephan