Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 895
  • Last Modified:

Cisco 3020 Switch config

I have 4 Cisco 3020s inside a couple of HP Blade Chassis.  They function very similar to a normal switch with a few variations.  I am able to link the state of my incoming network connection to the internal connections to the blades so that when my incoming link goes down the internal links go down.  

I am using a very simple config of:
link state track 1
!      
interface GigabitEthernet 0/17
 link state group 1 upstream
interface range Gig0/1 - 16
 link state group 1 downstream

My problem is that the switch wont allow me to put Gig0/19 and Gig0/20 into this group as "downstream"
So my question is:
Is there a way to link the Gig0/19 and Gig0/20 link state to Gig0/17? (so that if Gig0/17 fails ports 0/19 and 0/20 will auto disable themselves)

0
Tory W
Asked:
Tory W
  • 2
  • 2
1 Solution
 
Jimmy Larsson, CISSP, CEHNetwork and Security consultantCommented:
It is by design in 3020 so that gi0/1-16 are the interfaces connected to the blades that are downstream. All other interfaces are classified as upstream ports. If I remember it correctly all ports 17 - 20 are external connectors and they are not designed to be downlinks.

How are you using gi0/19 and 20?

/Kvistofta
0
 
Tory WAuthor Commented:
We are connecting our SANs (basically network storage) on those ports.  What happens when we pull the main line cable to test failover is that the 16 internal ports failover to our B side, but the SANs connected to ports 0/19 and 0/20 do not fail over.  

We are trying to find out if there is another config that allows you to connect one ports link state to another (besides the link state tracking).

0
 
Jimmy Larsson, CISSP, CEHNetwork and Security consultantCommented:
Well, if you build your network the way Cisco likes, you do it in a hierarcical way. In such a solution there are upstreams and downstreams. Those ports are ment to be use to connect upwards to a distribution- or core-switch, not for SAN.

You are simply not using the gear how it is built to be used. Normally it shouldnt really matter because it is just a plain switchport. But for this tracking-functionality you cant configure the ports as downstream.

Been there, done that. Sorry.

/kvistofta
0
 
Tory WAuthor Commented:
Thanks bro.

Saved me hours of parsing HP and Cisco Tech documents.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now