Calix EXA - E5 Series NIDs
Introduction
Calix has three primary NID models, the E5-306, E5-308, and E5-520. These run an earlier version of AOS for Metro services.
The E5 NID GUI is very confusing and hard to use. All configuration examples here will be done in CLI. The CLI is accessed via SSH with the login documented in Equipment Default Logins
Accessing the NID
Connect a laptop to the front craft Ethernet port and set your computer to DHCP. The SSH to 192.168.1.1.
Uplink Configuration
Configuring a network uplink or downlink as a simple tagged port is very simple, but removes all capabilities related to tag actions. In the E5 these are called INNI ports and are configured with transport service profiles. Transport service profiles are simple lists of VLANS, similar to how Cisco has switchport trunk vlan allowed. An example configuration follows.
transport-service-profile Uplink
vlan-list 40-41,45,50,70-71,85,87,700,3003
description "Uplink to Peridot Siding"
!
interface ethernet g4
description "Uplink to Peridot Siding"
no shutdown
service-role inni
transport-service-profile Uplink
!
!
LAG Configuration
The E5s also support LAG. An example configuration follows:
interface lag la1
description "Uplink Peridot Siding"
hash-method src-dst-mac
lacp-mode active
max-port 2
mtu 9600
no shutdown
service-role inni
transport-service-profile Uplink
!
!
interface ethernet g3
description "Peridot Siding 1/1/g1"
no shutdown
service-role lag
group la1
!
!
interface ethernet g4
description "Peridot Siding 1/2/g1"
no shutdown
service-role lag
group la1
!
!
Configure Management
Management configuration is similar to a B6 BVI configuration.
interface ip-host 1
vlan [ 70 ]
ip address 10.68.70.125
ip mask 255.255.255.0
ip gateway 10.68.70.1
pcp 7
config-download enable
no shutdown
!
Service Configuration
Service configuration requires configuring several nested configuration objects/profiles then connecting them together. Generally speaking different profiles should be used for an Ethernet circuit versus DHCP or static Internet.
The recommended configuration order is:
- Configure Bandwidth Limiters
- Configure match list
- Configure Service Profile
- Configure Service Instance
- Configure UNI service
Configure Bandwidth Limiters
There are two types of bandwidth limiters on the Calix NIDs: policers and shapers. Policers (called meter mef) in the config correspond to Accedian bandwidth regulators and are traditionally used for Metro services. Shapers are available in the downstream direction and should be used for Internet services because they play nicer with speed test servers.
Important Notes
- All bandwidth is entered in 64 bps increments. To figure out the nearest 64 bps increment, take your desired speed in bps (such as 20000), divide by 64, round up to the nearest whole number, then multiply by 64. For example, the nearest 64 bps increment to 20000 is 20032.
- Bandwidth limiters are profiles, not objects like they are in Accedian, so they same profile can be used for upstream and downstream for a symmetrical service
- If multiple services share a port, the E5-308 tracks CIR values so that combined CIR is less than the port speed. This means you can't have two 600m CIR services on the same port. This does not apply to EIR
- Some of our clients still report issues even when shapers are used. There seems to be an unexplained issue with speed tests when the speed test server is very close (low latency) to the E5. This issue has not been resolved and Calix has not been able to explain it.
Example Policer Configuration
A policer can be used for either upstream or downstream on an Ethernet service. Note that this policer is CIR based only. If multiple services need to be dropped that total more than the port speed, EIR can be used instead.
bandwidth-profile 30m_policer meter-mef
cir 30976
!
Example Shaper Configuration
A shaper is only used in the downstream direction and should be used for Internet services
bandwidth-profile 100m_shaper shaper
bandwidth maximum 100096
bandwidth minimum 100096
!
Configure Match List
Match lists define which frames are mapped into a service. Match-lists can also define a p-bit for matched traffic if desired. There are three primary kinds of match lists you might use. A simple match for untagged traffic to be mapped into an S-VLAN such as for Internet service. A second is basically a list that would match all tagged and untagged traffic to map into an E-Line service. The third is a list of C-VLANs that would map into an EVP-Line service.
Match List for Untagged Traffic
match-list untagged
match-rule 1 match untagged
!
Match List for All Traffic (E-Line)
match-list ALL
match-rule 1 match any
!
Match List for specified C-VLANs (EVP-Line)
Note that for a traditional cell site circuit, you would have two of these
match-list Verizon_Mentone_2656
match-rule 1 match vlan 2656
!
Configure Service Profile
Service profiles define the attributes for a specific type of service, such as E-Line, DHCP Internet, or Static Internet. Service profiles also define valid bandwidth packages for a service type. Examples are as follows:
Service profile for Ethernet Service
service-profile EP-Line
valid-service-bandwidth 20m
ingress 20m
egress 20m_shaper
!
valid-service-bandwidth 30m
ingress 30m_policer
egress 30m_shaper
!
!
Service Profile for DHCP Internet
Note that the NID supports IP Source Verify and MAC Forced Forwarding which are used here to secure the subscriber traffic through DHCP snooping. Also note the use of a downstream shaper.
service-profile DHCP_INET
dhcp-profile SNOOP
source-verify ENABLED
mff ENABLED
valid-service-bandwidth 100M_shaped
ingress 100m
egress 100m_shaper
!
!
Service Profile for Static Internet
service-profile MGMT706
!
service-profile StaticInternet
source-verify ENABLED
mff ENABLED
valid-service-bandwidth 40x40
ingress 40m
egress 40m_shaper
!
valid-service-bandwidth 50x50
ingress 50m
egress 50m_shaper
!
!
Configure Service Instance
The service instance ties a service profile to a specific VLAN. In theory the same service profile can be tied to multiple VLANs to support multiple E-Line services or EVP-Line services. Example Configurations follow. The format is:
service-instance <NAME> <VLAN ID> <SERVICE PROFILE NAME>
service-instance DHCPInet4 4 DHCPInternet
!
service-instance MGMT706 706 MGMT706
!
service-instance StaticInet103 103 StaticInternet
!
Configure UNI service
The last step is combine everything into a UNI service on a customer facing port.
Example DHCP Internet UNI Service
interface ethernet e1
description "TEST INTERNET"
service-role uni
service DHCP
match-list untagged
no shutdown
bandwidth 100M_shaped
!
!
!
!
Example Static Internet Service
Note the static L3 host that was specified
interface ethernet e1
description "Sand Plant"
no shutdown
service-role uni
service StaticInet103
match-list Untagged
no shutdown
bandwidth 50x50
!
ip-host 104.37.79.195
gateway1 104.37.79.193
!
!
!
!E-Line Example Ethernet Service UNI
interface ethernet e3
description "Clinic QinQ"
service-role uni
service CLINIC_QinQ
match-list All
no shutdown
bandwidth 20m
!
!
!
!
Example EVP-Line Service UNI
Note that this example has limiters applied to the port. This is only possible on the latest software
interface ethernet g1
description "To Verizon DETMN1707 (NTS)"
duplex full
mtu 9600
speed 1Gbs
no shutdown
service-role uni
bandwidth ingress [ 750M ]
bandwidth egress [ 750M ]
service Verizon_Mentone_2656
match-list Verizon_Mentone_2656
no shutdown
!
service Verizon_Mentone_3656
match-list Verizon_Mentone_3656
no shutdown
!
!
!
Troubleshooting and Maintenance Commands
Show MAC Table
Show Customer IP Associations
RFC2544 Loopback
Manually starting an RFC2544 loopback is kind of tricky. Unlike on Accedian, you loopback from the UNI port rather than the NNI port. Note also that the UNI service you are looping back needs to be shutdown before you can loopback. An example command follows:
start loopback interface ethernet g1 service-role uni loopback-duration 1000 stream-1 { remote-end-source-mac-addr 00:80:16:8A:63:92 service Verizon_Mentone_3656 }Note the information within the {}. Remote end source mac refers to the source MAC from the RFC tester, the service refers to the instantiated UNI service.
Don't forget to no shut the UNI service when you are done
Reference NIDs
Here are a list of some good NIDs to review for configuration options:
- DTC Verizon Mentone: 192.168.45.62
- SCATUI Hospital: 10.68.70.125
- Gila County Courthouse: 10.68.25.23