Applying EOS Licensing to the S-Series

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 15003 

Products
S-Series
S-EOS-L3-S130
S-EOS-L3-S150
S-EOS-PPC
S-EOS-VSB
S1-EOS-VSB
SSA-EOS-VSB
SSA-EOS-2XUSER 

Symptoms
Error: Unknown: "<command>"
Error: Unknown: "<long string ending with ==>"
Error: Failed to set this license key.
Error: This license key is per chassis and requires the chassis option.

Cause
In order to obtain the Activation Key to be configured as demonstrated below, it is first necessary to redeem and activate the purchased (or eval) license entitlement in "Enterasys Licensing" (10833). 

License applicability and configuration varies, depending upon the specific license part number. 

S-EOS-PPC  (11771

Supported with all firmware releases, this is a User license for increasing the authenticated users-per-port and overall system user capacity on S130 Class chassis-based ("Sx4xxx-xxxx(-xx)") fabrics or I/O modules, and on S130 Class SSA ("SSA-T4068-0252") systems.
See release notes applicable to your firmware version, for the exact design limits applied to the multiauth command set both with and without this license. 
Command format: set license port-capacity "<Activation Key>" [slot x]

S3(su)->set license port-capacity "0001:S-EOS-PPC:1:4d73c805:0:Demonstration Company:0:8d81264d:X6Kl0pIBwxrR8ss318CG06z8lkoFRMSwkCvWvPXKInxqlyibfV70K4TDhe8qLfKuIvSJ4DsUmbPYw0+OOspelQ=="
S3(su)->

With firmware 7.11.03.0002 and lower, a new license does not take effect until the system is rebooted.
With firmware 7.21.01.0015 and higher, the license is applied transparently with no system disruption, and is immediately active ('show license'). 

SSA-EOS-2XUSER 

Supported with firmware 7.31.03.0010 and higher, this is a User license for doubling the authenticated users-per-system capacity of S130 Class SSA ("SSA-T4068-0252") and S150 Class SSA ("SSA-T1068-0652", "SSA-G1018-0652") systems. For the S130 Class, it also increases the authenticated users-per-port capacity. 
See release notes applicable to your firmware version, for exact design limits applied to the multiauth command set both with and without this license. 
Command format: set license 2x-user-capacity "<Activation Key>" [slot x]

SSA(su)->set license 2x-user-capacity "0001:SSA-EOS-2XUSER:1:5119340c:0:Demonstration Company:0:8d86714d:WY+jEPBKn1TpMA8lhJ009LTOhn3OcvN95hgkvbvKjO46mMkuoMRhLQLm0fHtsMv1UAMyWPZTihr3ZVpGH6uJRw=="
SSA(su)->

The license is applied transparently with no system disruption, and is immediately active ('show license'). 

S-EOS-L3-S130 

Supported with firmware 7.21.01.0015 and higher, this is an Advanced Routing license for enabling VRF on S130 Class chassis-based ("Sx4xxx-xxxx(-xx)") fabrics or I/O modules, and on S130 Class SSA ("SSA-T4068-0252") systems. 
With firmware 7.31.03.0010 and higher, it enables both VRF and BGP for these products. 
Command format: set license l3-s130 "<Activation Key>" [slot x]

S3(su)->set license l3-s130 "0001:S-EOS-L3-S130:1:4db574ae:0:Demonstration Company:0:8d86264d:NR4SAsQJQNMh+AvJQLX68wBzCJuIEMIYNVv6ja/CsfazISZne/Mv9sA8+x9+Ra0SLNdXr6K8/Ze71vaEOzoX0g=="
S3(su)->

The license is applied transparently with no system disruption, and is immediately active ('show license'). 

S-EOS-L3-S150 

Supported with firmware 7.71.01.0010 and higher, this is an Advanced Routing license for enabling L3GRE (GRE) Tunnels and MPLS/MP-iBGP on S150 Class chassis-based ("Sx1xxx-xxxx(-xx)") fabrics or I/O modules, and on S150 Class SSA ("SSA-T1068-0652", "SSA-G1018-0652") systems. 
Command format: set license l3-s150 "<Activation Key>" [slot x]

S3(su)->set license l3-s150 "0001:S-EOS-L3-S150:1:4d92c803:90:Demonstration Company:0:8d86264e:RJSe2rr0mALI1tmltpmjvV7QyQwx2Bvdfc8F5dHVlTkyTX34I8pW7nzjxdzUhzqlqehkd/hjLPDsDtmE3dfCjQ=="
S3(su)->

The license is applied transparently with no system disruption, and is immediately active ('show license'). 

S-EOS-VSB 

Supported with firmware 7.71.01.0010 and higher, this is a Virtual Switch Bonding license for enabling VSB on S130 Class multi-slot chassis-based ("Sx4xxx-xxxx(-xx)") systems, and on S150 Class multi-slot chassis-based ("Sx1xxx-xxxx(-xx)") systems (16081). 
A multi-slot chassis may be bonded to a like chassis (S3<->S3, S4<->S4, S6<->S6, or S8<->S8) only. 
Two licenses are required, to bond the Chassis 1 and Chassis 2 peers. 
Command format: set license vsb "<Activation Key>" chassis x

S3(su)->set license vsb "0001:S-EOS-VSB:1:5112e662:0:Demonstration Company:0:8d86214d:i4doNr5aP89XNWO0vRlPucvBgVFiHmWKCtfL/aM8Z97rt7rj3qpVaR9zixnwjbQSFKToAaimo2rABHvO5HoncA==" chassis 1
S3(su)->

The license is applied transparently with no system disruption, and is immediately active ('show license'). 

S1-EOS-VSB 

Supported with firmware 7.71.01.0010 and higher, this is a Virtual Switch Bonding license for enabling VSB on S130 Class S1-CHASSIS based ("Sx4xxx-xxxx(-xx)") systems, and on S150 Class S1-CHASSIS based ("Sx1xxx-xxxx(-xx)") systems (16081). 
An S1-CHASSIS may be bonded to another S1-CHASSIS only (14584). 
Two licenses are required, to license the Chassis 1 and Chassis 2 peers. 
Command format: set license vsb "<Activation Key>" chassis x

S1(su)->set license vsb "0001:S1-EOS-VSB:1:500d401a:0:Demonstration Company:0:8d86714d:nGLNZkkGHdzULzVxoxXWVo3qKk2kUlaQNX+B8xW+eBisJ6EFCMlQmULI5j8TufY502AGyn2ruZQuKgaeVr6eyg==" chassis 1
S1(su)->

The license is applied transparently with no system disruption, and is immediately active ('show license'). 

SSA-EOS-VSB 

Supported with firmware 7.62.01.0009 and higher, this is a Virtual Switch Bonding license for enabling VSB on S130 Class SSA ("SSA-T4068-0252") and S150 Class SSA ("SSA-T1068-0652", "SSA-G1018-0652") systems (16081). 
A SSA standalone system may be bonded to another SSA standalone system only. 
Two licenses are required, to bond the Chassis 1 and Chassis 2 peers 
Command format: set license vsb "<Activation Key>" chassis x

SSA(su)->set license vsb "0001:SSA-EOS-VSB:1:4ffda4ac:0:Demonstration Company:0:8d86714d:Kz1NZ/9qu/ebju/+Kc25ccI5uLNiE3RQjBPANiMqeRF1MYnnr0qOl/NA8v7rWuYlHuVUsu8C9NxX/Y90r4BluA==" chassis 1
SSA(su)->

The license is applied transparently with no system disruption, and is immediately active ('show license'). 

* Error messages * 

Here are a few of the more common reasons for license-related error messages: 
  • Error: Unknown: "<command>"
    Reason: The system does not understand the issued CLI-based command. This may be due to an entry error, but may also be due to the absence of a license required to activate that particular command set. As examples; use of VRF or BGP may require a S-EOS-L3-S130, use of GRE may require a S-EOS-L3-S150, and use of VSB may require a xxx-EOS-VSB.
    Resolution: Either enter the command correctly, or first apply the necessary license.
  • Error: Unknown: "<long string ending with ==>"
    Reason: The company name embedded into the Activation Key during the license activation process contains at least one space character, and when issuing the 'set license...' command the user omitted the double-quotes necessary to delimit the entire Activation Key.
    Resolution: Bracket the entire Activation Key string with double-quotes, as shown in all the examples above.
  • Error: Failed to set this license key.
    Reason 1: The Activation Key portion of the 'set license...' command was incorrectly entered, possibly because it is being manually typed (rather than copied-and-pasted) and contains characters (e.g. "0" vs "O", "1" vs "I", "5" vs "S", "8" vs "B") that are easily mistaken for each other.
    Resolution 1: Identify the source of the problem and correct the command entry.
    Reason 2: The company name embedded into the Activation Key during the license activation process contains "special" characters; that is, other than a-z, A-Z, and 0-9 with punctuation (dash and quote characters formatted by a word processor are also considered to be a "special" characters) - and is now being rejected by the 'set license...' command.
    Resolution 2: The license will probably need to be re-Activated. Please send an email to licensing@enterasys.com, reporting the problem; and include both the Entitlement ID and a capture of the problematic command with error message.
    Reason 3: The wrong license is being used for the product. For example, an S-EOS-VSB license is being used for an SSA.
    Resolution 3: Confirm that the license is correct for the product.
  • Error: This license key is per chassis and requires the chassis option.
    Reason: The 'set license vsb...' command is being used to enter a VSB license, but is not specifying whether that system will be serving as peer Chassis 1 or peer Chassis 2. This is not an optional parameter.
    Resolution: Correct the licensing command, according to your network design and requirements.

Solution
FAD (Functions as Designed). 

Please contact the GTAC for further assistance, as necessary.
Photo of FAQ User

FAQ User, Official Rep

  • 13,610 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.