Network Management

 View Only
last person joined: 10 hours ago 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

Airwave and IAP-GUI-Config role rules (IP)

This thread has been viewed 0 times
  • 1.  Airwave and IAP-GUI-Config role rules (IP)

    Posted Dec 08, 2015 01:15 PM

    Hi All,

    I'm currently deploying a customer's AMP-8.0.9.2, with IAPs on v6.4.2.6-4.1.1.10_51810.

    We're also using the Instant-GUI-Config in the groups.

    When configuring rules within a user role on the IAPs in this way, it doesn't seem to be possible to add a custom rule for anything other than TCP or UDP protocols. For example, I can't add IP protocol 51 for (ah).

    Is there a way to do this?



  • 2.  RE: Airwave and IAP-GUI-Config role rules (IP)

    EMPLOYEE
    Posted Dec 08, 2015 01:33 PM

    Hi, 

     

    There are options to configure customer rules other than TCP and UDP. 

     

    CLI command is for protocol 51 (ah), 

     rule any any match ah any any permit 

     

     

    GUI can be configured as below, 

    IAP-AH-1.JPG-- 

    IAP-AH-2.JPG

     

    Thanks, 

    Rajaguru Vincent 



  • 3.  RE: Airwave and IAP-GUI-Config role rules (IP)

    Posted Dec 08, 2015 01:36 PM

    Looking at those images you pasted, you're doing it directly in the IAP yes?

    I tried that, and agree, it's possible in there.

    When you try the same in the Instant-GUI within Airwave itself, that "other" option doesn't exist. Only TCP or UDP.

    Any thoughts?



  • 4.  RE: Airwave and IAP-GUI-Config role rules (IP)
    Best Answer

    EMPLOYEE
    Posted Dec 08, 2015 01:44 PM

    Hi, 

     

    You are correct. I tried that directly from IAP. I checked on Airwave and couldn't find the OTHERS option in Airwave IGC. Please raise a TAC case. 

     

    Thanks, 

    Rajaguru Vincent 



  • 5.  RE: Airwave and IAP-GUI-Config role rules (IP)

    Posted Dec 08, 2015 01:46 PM

    Thanks for the confirmation. Thought that might be the situation.

    Unfortunately I won't have time to log it with TAC (project timescales are tight on this one).

    I'll just work-around it.