Cisco 897VAW-E-K9 with Sky VDSL/FTTC

References:
IPv6 Config:
https://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113141-DHCPv6-00.html
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/enterprise-ipv6-solution/whitepaper_c11-689821.html
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6/configuration/15-2mt/ipv6-15-2mt-book/ip6-dhcp.html
https://community.cisco.com/t5/ipv6/ipv6-on-vlans/td-p/3343182
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6/configuration/xe-3s/ipv6-xe-36s-book/ip6-vfr-xe.html
Wireless Config:
https://www.cisco.com/c/en/us/td/docs/routers/access/800/software/configuration/guide/SCG800Guide/SCG800_Guide_BookMap_chapter_01001.html
https://www.cisco.com/en/US/docs/routers/access/800/880/software/configuration/guide/880_basic_device_wireless_config.html
https://community.cisco.com/t5/wireless-and-mobility/creating-new-bridge-group-names-in-cisco-5508-wlc/td-p/2587737
https://networklessons.com/uncategorized/cisco-1941w-wireless-configuration-example

Cisco 897VAW-E-K9 running connected to Sky UK VDSL running 15.9(3)M1 (local mirror for backup purposes: c800-universalk9-mz.SPA.159-3.M1.bin).

ICMP check: http://icmpcheck.popcount.org/

 

Full Config

Example available here. Some details are redacted from this config. There is no need to use the old trick of capturing the Sky Hub DHCPv4 client ID and DHCPv4 hostname strings with Wireshark when the Hub first boots, and then configuring that DHCP client-id and hostname on your Cisco router. IPv4 authentication is based on line ID, not DHCPv4 Opt 61 details. Any value like "foobar@skydsl|" can be used. When the DHCPv4 client ID and hostname aren't recognised or missing, Sky will simply synthesize them. It may take a little longer but DHCPv4 will eventually be allocated an address by the Sky BNG. IPv6 auth depends on prefix discovery being enabled on the client. DHCPv6-PD must be enabled on the WAN link so that the client sends IA_PD in the DHCHv6 solicit message, if prefix delegation isn't enabled and the client sends IA_NA, DHCPv6 auth won't complete. DHCPv6 depends on DHCPv4 completing (a dependency within the Sky RADIUS platform), DHCPv6 won't complete until DHCPv4 has, and when Sky have to synthesize the DHCPv4 client ID and hostname, it can take a little longer, but works just fine.

 

SSH Access

Due to using an old IOS, modern Ubuntu doesn't support the Key Exchange algorithm by default anymore:

ssh -oKexAlgorithms=+diffie-hellman-group-exchange-sha1 -oHostKeyAlgorithms=+ssh-rsa username@192.168.58.1

 

ADSL/VDSL Firmware Upgrade

Local mirror for backup purposes: VA_A_39m_B_38h3_24h.bin / fwrn_a2pv6c039m.pdf

Before firmware upgrade:

Firmware    Source      File Name 
--------    ------      ----------
VDSL        embedded    VDSL_LINUX_DEV_01212008

Modem FW  Version:  4.14L.04A
Modem PHY Version:  A2pv6C039t.d24o_rc1

 

After rebooting with the new firmware file:

897VAW-E-K9#show controllers vDSL 0
Controller VDSL 0 is UP

Daemon Status:		 Up 

			XTU-R (DS)		XTU-C (US)
Chip Vendor ID:		'BDCM'			 'BDCM'
Chip Vendor Specific:   0x0000			 0xA4A1
Chip Vendor Country:    0xB500			 0xB500
Modem Vendor ID:	'CSCO'			 '    '
Modem Vendor Specific:  0x4602			 0x0000
Modem Vendor Country:   0xB500			 0x0000
Serial Number Near:    FCXXXXXXXXX C897VAW- 15.9(3)M1
Serial Number Far:     eq nr port:02  oemid softwarerev
Modem Version Near:    15.9(3)M1
Modem Version Far:     0xa4a1

Modem Status:		 TC Sync (Showtime!) 

DSL Config Mode:	 AUTO 
Trained Mode:	G.993.2 (VDSL2) Profile 17a
TC Mode:		 PTM 
Selftest Result:	 0x00 
DELT configuration:	 disabled 
DELT state:		 not running 

Full inits:		1
Failed full inits:	0
Short inits:		0
Failed short inits:	0

Firmware	Source		File Name 
--------	------		----------
VDSL		user config	flash:VA_A_39m_B_38h3_24h.bin

Modem FW  Version:	140729_1209-4.02L.03.A2pv6C039m.d24h
Modem PHY Version:	A2pv6C039m.d24h
Trellis:		 ON			  ON
SRA: 			 disabled		 disabled
 SRA count: 		 0			 0
Bit swap: 		 enabled		 enabled
 Bit swap count:	 5416			 608
Line Attenuation:	  0.0 dB		  0.0 dB
Signal Attenuation:	  0.0 dB		  0.0 dB
Noise Margin:		  7.8 dB		  6.0 dB
Attainable Rate:	48929 kbits/s		 8774 kbits/s
Actual Power:		 12.4 dBm		  5.0 dBm
Per Band Status:       	D1 	D2 	D3 	U0 	U1 	U2 	U3
Line Attenuation(dB):   17.0	44.9	69.8	8.5	37.4	56.0	N/A	
Signal Attenuation(dB): 25.4	44.5	71.0	8.5	36.8	54.3	N/A	
Noise Margin(dB):       7.8	7.8	7.9	5.6	6.0	6.0	N/A	
Total FECC:		255348957			 39
Total ES:		0			 5
Total SES:		0			 0
Total LOSS:		0			 0
Total UAS:		1050			 1050
Total LPRS:		0			 0
Total LOFS:		0			 0
Total LOLS:		0			 0


 		  DS Channel1	  DS Channel0	US Channel1	  US Channel0
Speed (kbps):	          0	       39999	         0	        8781
SRA Previous Speed:       0	           0	         0	           0
Previous Speed:	          0	           0	         0	           0
Reed-Solomon EC:          5	   255348957	         0	          39
CRC Errors:	          0	           0	         5	           5
Header Errors:	          0	           0	         0	           0
Interleave (ms):       0.00	        0.00	      0.00	        0.00
Actual INP:	       2.01	       52.00	      0.00	        0.00

Training Log :	Stopped
Training Log Filename :	flash:vdsl.log

 

Wireless AP CLI

The primary method should be to enter the following command from the main router CLI:

897VAW-E-K9#service-module wlan-ap 0 session 
Trying 192.168.58.1, 2002 ... 
% Connection timed out; remote host not responding

As above, this almost never works for me. Instead, I ensure that interface wlan-ap0 is enabled and part of my LAN VLAN (VLAN 1, in this case using ip unnumbered to use the same IP address, not just be in the same VLAN/subnet) and then Telnet to the IP on port 2002

897VAW-E-K9#show run int wl0 
Building configuration...

Current configuration : 76 bytes
!
interface wlan-ap0
description WLAN Management
ip unnumbered Vlan1
end

Wireless AP Firmware Upgrade

This wireless AP can run the Lightweight (w8) AP IOS software. Local mirror for backup purposes: ap802-k9w8-tar.153-3.JC5.tar

It can also run the Autonomous (w7) AP IOS software. Local mirror for backup purposes: ap802-k9w7-tar.153-3.JC5.tar

# Copy the AP firmware to the router flash storage "flash:", then copy it to the separate flash storage used by the AP "flash:1:", then reboot the AP into rommon mode:
897VAW-E-K9#copy http://192.168.58.5/ap802-k9w7-tar.153-3.JC5.tar flash:

897VAW-E-K9#copy flash:ap802-k9w7-tar.153-3.JC5.tar flash:1:

897VAW-E-K9#service-module wlan-ap 0 reset bootloader

# Connect to the AP console, which will be in rommon mode
897VAW-E-K9#service-module wlan-ap 0 session

# Init the AP flash file system:
ap: flash_init
# Extract the firmware tar file
ap: tar -xtract flash:ap802-k9w7-tar.153-3.JC5.tar flash:
# Boot the unpacked firmware
ap: boot flash:ap802-k9w7-mx.153-3.JC5/ap802-k9w7-mx.153-3.JC5

# The AP will boot into it's CLI, the config the AP to always use this new image for future boots, and reload it to confirm:
# There is a default login:
# Default username is "cisco" and password is "Cisco" with a capital "C"
# Default enable password is "Cisco" with a capital "C"
conf t
boot system flash:ap802-k9w7-mx.153-3.JC5/ap802-k9w7-mx.153-3.JC5
end
wr
reload

# If there is an existing configuration on the AP with a password, the config can be defaulted.
# From the main router CLI, either use the following command:
897VAW-E-K9#service-module wlan-ap 0 reset default-config 
# Or delete the config file and reboot the entire router:
897VAW-E-K9#delete flash:1:config.txt

 

---