Conference npss::gigaswitch

951.0. "Gigaswitch problem" by ZPOVC::SHINYAW () Fri Mar 14 1997 01:03

Hi,

I have just installed a new Gigaswitch at one of my customer site and  
discover the following problems.
 

         	
		CISCO 7000(lakeside)

		|------|b	     a |------|	
		|      |---------------|      | GIGAswitch
		|      |---   |--------|      |
		|------|a |   |	     b |------|
		 a| |b	  |   |	
		  | |	  |   |		
     DECHUB900    | |a	  |   |	
		|------|  |   |
		|      |  |   |
     NMS(PC)----|      |  |   |
		|------|  |   |
			  |   |
			  |   |
 			  |   |	
		|------|b |   |
		|      |--|   |
		|      |------|
		|------|a

		CISCO 7000(queentown)

	Configuration details

	ipaddress for cisco(lakeside) is 165.21.80.1
	ipaddress for cisco(queentown) is 165.21.80.4
	ipaddress for gigaswitch is 165.21.80.20
	ipaddress for NMS(clearvisn) is 165.21.81.8
	subnet mark 255.255.255.0
		
	gigaswitch details
	firmware verion 3.1
	4 pieces of fg2 line card install on slot 1,2,13,14
	4 pieces of fg4 line card install on slot 5,6,9,10
	
	Cisco ios verion is 11.2-3

Problems
--------
when only one port(either port A or B) of the fg2 line card connect to the
ring,it looks normal that the PC can ping and manage the gigaswitch with 
clearvisn. 
However, if both a and b port of fg2 line card  connect to the  ring,
the pc can't ping and manage the gigaswitch, it does not reponsed to the 
ping from both cisco7000 as well. I check the fddi status, it seems normal 
and  the PCs can also ping to any other hosts accept gigaswitch.
I use OBM to examine the ip entry of both cisco7000 ip address, it show me 
the hardware address is 00-00-00-00-00-00 at this time. But I can see the 
hardware address 00-00-0c-xx-xx-xx, if one of port(a or b) of fg2 line 
card disconnect from the ring. 
I try on different fg2 line card same problem.

Many thanks in advance.

Regards
Shinyaw


 	

        Look at the existing answers to problems like this.  Lacking sufficient
    information, my guess is that it is the most common "I haven't assigned
    an IP address to the port over which I'm trying to communicate".
    
Notes> show keyword can't-ping/full


                                   GIGAswitch
Created: 29-JUL-1992 12:28         951 topics         Updated: 13-MAR-1997 22:03
          -< GIGAswitch/FDDI Jan 97 BL3.1 914.0 documentation 412.1 >-
 Keyword              Note
>Can't-PING           265.1, 544.0, 544.6, 714.3, 743.3, 764.1, 776.4
 End of requested listing

        On rereading your note, I see that it is not an IP configuration
    issue after all.
    
        IP communication takes place at a higher level than FDDI
    communication.  "A" and "B" ports are a single interface.  The fact
    that you lose connectivity implies that you have a FDDI configuration
    problem, *not* an IP configuration problem.
    
        I suggest the following:
    
    1) Report the problem through the normal problem reporting mechanisms
    
    2) Observe the LEDs on the FGLs to detect any unexpected behaviour
    
    3) Confirm *BY CHECKING EACH DEVICE* that they are actually all A/B DAS
    interfaces as you believe.
    
        My suspicion is that you have one of the following:
    
        FGL-2s configured as "S" ports and IP addresses not assigned to all
      the ports
    
        One of those "DAS" devices is actually set up with M ports, causing
    a bad (mixed tree/ring) configuration.
    
        Of course, you *are* running the current firmware, BL3.1?
    
    MDL

    Hi,
    
    Thanks for for reply, the problem was due to label on the fiber optic 
    cable not correctly done by customer and cause the FDDI problem.
    
    Regards
    Shinyaw