Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Clifra-Jones
Clifra-Jones
Conversationalist
Member since Apr 5, 2022
Mar 7 2024
Cliff Williams
United States
33 year IT professional
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
Feb 15 2024
9:32 AM
Yes, you are right, the dashboard accepted it. Even though it will not work. The API throws an error.
... View more
Feb 15 2024
9:31 AM
Ya know what, you are right! I went back and looked at my networks and the next hop is always interface IP of the VLAN that is also configured on the MX. I guess I got confused when the dashboard allowed me to create the static route with the IP of the 192.168.132.1 as the next hop. Seems that should bark at you also! Thanks for the kick in the brain!
... View more
Feb 15 2024
9:18 AM
Yes, saw that, fixed it, same error. In the dashboard: Add Static Route Name: VLAN132 IPVersion: IPv4 Subnet: 192.168.132.0/24 Next Hop IP 192.168.132.1 It works.
... View more
Feb 15 2024
9:17 AM
192.168..132.1 is not the IP of the MX. The MX has an IP of 192.168.128.1 I did see an error where the 192.168.128.0/24 interface on the switch had an Interface IP the same as the MX. I corrected that and tried again and get the same error. We have over 200 sites in our network and I do this all the time through the dashboard. The Dashboard works.
... View more
Feb 15 2024
7:36 AM
I am working in the Enterprise DevNet. I am attempting to use this endpoint to create an appliance static route. I have 1 VLAN in the MX. id : 1
networkId : L_646829496481116086
name : Default
applianceIp : 192.168.128.1
subnet : 192.168.128.0/24
fixedIpAssignments :
reservedIpRanges : {}
dnsNameservers : upstream_dns
dhcpHandling : Run a DHCP server
dhcpLeaseTime : 1 day
dhcpBootOptionsEnabled : False
dhcpOptions : {}
interfaceId : 646829496481737561
ipv6 : @{enabled=False}
mandatoryDhcp : @{enabled=False} I have 2 interfaces in the switch: interfaceId : 646829496481104683
name : Bob
subnet : 192.168.128.0/24
interfaceIp : 192.168.128.1
multicastRouting : disabled
vlanId : 1
defaultGateway : 192.168.128.1
switchName : SW-F02
serial : Q2GW-2CPC-JCYZ
interfaceId : 646829496481104684
name : Joe
subnet : 192.168.132.0/24
interfaceIp : 192.168.132.1
multicastRouting : disabled
vlanId : 132
switchName : SW-F02
serial : Q2GW-2CPC-JCYZ When I try to pass the following JSON to the this endpoint I get an invalid next hop error. Configuring this Static Route in the dashboard works. {
"gatewayIp": "192.168.132.1",
"subnet": "192.168.132.0/24",
"name": "VLAN132"
} Error message is: "The static LAN route \u0022VLAN132\u0022 has an invalid next hop IP. The IP address 192.168.132.1 is not on a configured subnet."
... View more
Feb 3 2024
10:49 AM
That’s what I was wondering. I am using the dev sandbox. I can’t test this functionality on my production MXs. All the other methods I’ve tested so far seem to work. Good to know it works. I can move on to test other methods.
... View more
Feb 2 2024
12:45 PM
I am working with the V1 API function Update Network Appliance Firewall Cellular Firewall Rules. It seems the source and destination ports do not get updated when calling this method. This is my message body I am sending to the API method: {
"rules": [
{
"comment": "This is a test 3",
"policy": "allow",
"protocol": "any",
"srcPort": "8080",
"srcCidr": "192.168.129.0/24",
"destPort": "80",
"destCidr": "192.168.128.0/24",
"syslogEnabled": false
}
]
} It seems I can update any other property but the srcPort and destPort. I have successfully updated the comment and subnets several times.
... View more
© 2024 Cisco Systems, Inc.
