I'm trying to configure Cisco Smart Install but it won't work.
My director is a 3750 E-Serie. I copied the IOS-image which I wanna install (c3750-ipservicesk9-tar.122-55.SE.tar) on some C3750-48TS-S into flash. As well I copied three TXT-files on the director. 1. client_cfg.txt, 2. smi_image_list.txt, 3. final_client_smi_config.txt.
2. The smi_image_list.txt has the name of the IOS-image (c3750-ipservicesk9-mz.122-55.SE) in it.
3. The final_client_smi_config.txt has in a little bit of configuartion in it:
username cisco priv 15 secret cisco
aaa new-model aaa authentication login default local enable secret 0 cisco ! interface vlan 1 ip address dhcp no shut exit ! vstack director 10.10.10.1 ! spaning-tree mode rapid-pvst ! end
DHCP- and TFTP-Server are configured on the director. And when I now boot up another switch connected via ethernet to the director it gets an ip-adress from the director but after a few seconds the following message appears:
00:01:33: AUTOINSTALL: Vlan1 is assigned 10.10.10.2
00:01:33: AUTOINSTALL: Obtain tftp server address (opt 150) 10.10.10.1
Loading client_cfg.txt from 10.10.10.1 (via Vlan1): !
The switches I'm trying to update run IP-Base12.2(35)SE.
Now I tried a 3750-48TS-S runnig C3750-IPSERVICESK9 12.2(52)SE and it won't work too. But the console-message was different:
*Mar 1 00:01:39.656: AUTOINSTALL: Vlan1 is assigned 10.10.10.2 got vend id vend spec. info ret: succeed got vend id vend spec. info ret: succeed Loading final_client_smi_config.txt from 10.10.10.1 (via Vlan1): ! [OK - 238 bytes]
*Mar 1 00:02:09.436: %SYS-5-CONFIG_NV_I: Nonvolatile storage configured from tftp://10.10.10.1/final_client_smi_config.txt by console Could not buffer tarfile...using multiple downloads examining image... %Error opening tftp://10.10.10.1/c3750-ipservicesk9-mz.122-55.SE (No such file or directory) %Error opening flash:update/info (No such file or directory) ERROR: Image is not a valid IOS image archive. *Mar 1 00:02:10.501: %SMI-6-UPGRD_SUCCESS: Switch (IP address: 10.10.10.2) startup-config has upgraded successfully *Mar 1 00:02:10.509: %SMI-6-UPGRD_STARTED: Switch (IP address: 10.10.10.2) image upgrade has started *Mar 1 00:02:11.558: %SMI-3-UPGRD_FAILED: Switch (IP address: 10.10.10.2) image upgrade failed
Alright so, first off... the telnet line in client_cfg.txt is wrong, it should be using port 39419, also with 12.2(55)SE these configuration files are automatically created by the director instead of having to create them manually.
Secondly, when you define vstack image, you need to define the .tar archive image filename itself or a text file containing the .tar image name (text file is more useful when dealing with switch stacks)
Oh, I forgot to mention, also... when upgrading a non-smart install capable switch (the telnet client_cfg.txt method) the process will appear to stall (it will look like nothing is happening) but i assure you, there is activity and if you be patient you'll start to see messages begin to scroll again.
I am doing smart install with 12.2.55.... You look like you dont have the actual tar file in your flash but instead are sharing the already extracted and installed image directory. I had to place the unextracted tar in my flash and then share it with tftp-server command just like you did with the client_cfg...
Your error msg looks like its telling the story. I dont understand all the different port numbers we have for the client_cfg yet :/
My client config file looks like this
W230#more flash:client_cfg.txt ! version 12.2 ! enable password cisco ! username cisco ! do telnet 10.10.10.1 58238 ! end !
[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...