[f-nsp] can't get ping on foundry

Mon Jun 14 16:20:13 EDT 2004

Yes, I know it's old, that's why I'm trying to upgrade it with the
current rev (7.4).

I have plugged a laptop directly into it and still cannot get ping. See
the original message for my results with getting it on the network.

Dan Norton
CCNA, MCP
Network Administrator
WareNet/SyncCast
dan at ware.net
dan at synccast.com
(949) 417 - 2300 x 2360
(888) 927 - 3329 (Fax)
Emergency Cell Phone: 949-300-4215
SMS: emergency at ware.net
aim: deveyn
WebSite Development, Web Hosting, Connectivity, Colocation 

"When the winds of change blow hard enough, the most trivial of things
can turn into deadly projectiles."

> -----Original Message-----
> From: Cliff Fogle [mailto:Cliff at ofoto.com] 
> Sent: Monday, June 14, 2004 1:11 PM
> To: Dan Norton
> Subject: RE: [f-nsp] can't get ping on foundry
> 
> Wow...what kind of serverIron is that?  That code rev is 
> rediculously old.  Can you get a laptop hooked up to it and 
> pinging?  Then you could maybe use solarwinds tftp server to 
> upload a new code base.  Depending on the model type, the 
> latest code revs are in 7.X to 9.X area...
> 
> -----Original Message-----
> From: foundry-nsp-bounces at puck.nether.net
> [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Dan Norton
> Sent: Monday, June 14, 2004 11:42 AM
> To: foundry-nsp at puck.nether.net
> Subject: [f-nsp] can't get ping on foundry
> 
> We have a new Serveriron going into production and are having 
> some difficulties with getting it connected to the network. 
> When it is directly connected to my router, neither the 
> router nor the foundry can ping each other. 
> 
> Here is the relevant information on the foundry, I'm trying 
> to get it connected to the network so we can upgrade the firmware:
> 
> 
> 
> ServerIron#ping 192.168.1.1
> Sending 1, 16-byte ICMP Echo to 192.168.1.1, timeout 5000 
> msec, TTL 64 Type Control-c to abort Request timed out.
> No reply from remote host.
> ServerIron#sh int
> Port Link State     Dupl Speed Trunk Tag Priori MAC            Name
> 01   Down None      None None  None  No  Normal 00e0.5201.f906
> 02   Down None      None None  None  No  Normal 00e0.5201.f907
> 03   Down None      None None  None  No  Normal 00e0.5201.f908
> 04   Down None      None None  None  No  Normal 00e0.5201.f909
> 05   Down None      None None  None  No  Normal 00e0.5201.f90a
> 06   Down None      None None  None  No  Normal 00e0.5201.f90b
> 07   Up   Forward   Full 100M  None  No  Normal 00e0.5201.f90c
> 08   Down None      None None  None  No  Normal 00e0.5201.f90d
> 09   Down None      None None  None  No  Normal 00e0.5201.f90e
> ServerIron#sh ver
>  SW: Version 3.1.11T12 Copyright (c) 1996-1998 Foundry Networks, Inc.
>      Compiled on Nov 19 1998 at 18:50:39 labeled as SLB03111
>  HW: ServerIron Switch, serial number 01f906  240 MHz Power 
> PC processor
> 603 (revision 7) with 32756K bytes of DRAM
>    8 100BaseT interfaces with Level 1 Transceiver LXT975
>    1 GIGA uplink interfaces, SX
>  256 KB PRAM and 8*2048 CAM entries for DMA 2, version 0807
>  256 KB PRAM and 4*1024 CAM entries for DMA 4, version 0104, 
> SEEQ GIGA MAC
>  128 KB boot flash memory
> 4096 KB code flash memory
>    0 KB BRAM, BM version 02
>  128 KB QRAM
>  512 KB SRAM
> Octal System, Maximum Code Image Size Supported: 1965568 
> (0x001dfe00) The system uptime is 8 minutes 42 seconds
> 
> ServerIron#wr term
> Current configuration:
> !
> global-protocol-vlan
> !
> !
> !
> !
> ip address 192.168.1.2 255.255.255.0
> ip default-gateway 192.168.1.1
> !
> interface e 1
> !
> interface e 2
> !
> interface e 3
> !
> interface e 4
> !
> interface e 5
> !
> interface e 6
> !
> interface e 7
> !
> interface e 8
> !
> interface e 9
> !
> end
> 
> 
> 
> And on the router, you can see that it has the foundry's MAC 
> address in the ARP tables:
> 
> router#ping 192.168.1.2
> 
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> nuclearworm#sh arp
> Protocol  Address          Age (min)  Hardware Addr   Type   Interface
> Internet  192.168.1.1             -   0003.6bba.2d60  ARPA
> FastEthernet0/0
> Internet  192.168.1.2             0   00a0.5201.f906  ARPA
> FastEthernet0/0
> 
> I've already tried different variations of hard-coding each 
> end of the link. It may be a firmware issue but I can't rule 
> that out until I can upgrade the firmware... and I can't 
> upgrade the firmware until I get it connected to the network.
> 
> I'm pretty sure it's not the firmware though.
> 
> I started it in boot monitor mode and get the following:
> 
> BOOT MONITOR> ip address 192.168.1.2 255.255.255.0 BOOT INFO: 
> set ip addr to 192.168.001.002, ip mask to 255.255.255.000 
> BOOT MONITOR> ip default_gateway 192.168.1.1 BOOT MONITOR> 
> ping 192.168.1.1 No reply from remote host
> 
> If it's a firmware issue I'd think that it would work even if 
> just in boot monitor mode.
> 
> I've tried all ports, it's an 8 port model and get the same results.
> 
> Anything else I should try? I couldn't find an option of 
> upgrading the firmware through the serial port nor could I 
> find any manuals for this older firmware.
> 
> Dan Norton
> Network Administrator
> 
> 
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
> 
> 
> 
> 