I wiped an old config.text file out and started from scratch with a new setup. Setup an IP and verified VLAN1 had that address. I am now only intermittently able to ping the address. Is there any other files or settings that may be lingering that stick around after a factory reset or new config?
The only other thing that would still be on the switch after a 'wr erase' would be the vlan database file, since on the 3500xl platform you had to do all the vlan configs from 'vlan database' mode. However, I don't see how that would interfere with layer3 connectivity to your switches vlan1 SVI.
Where are you trying to ping the vlan1 SVI from? The same switch from a PC connected to a vlan1 interface, or have you trunked this 3500xl to another switch and are trying to ping it from there?
Where ever you are trying to ping the vlan1 SVI from, I would issue the 'sh int ' and check to see if you have any CRC, FCS, or other errors. Do your logs on the 3500xl have anything in them?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...